From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hans" Subject: Re: Still having a problem building elks kernel Date: Mon, 8 Mar 2010 16:43:01 -0000 Message-ID: References: <4B929115.7070201@gmail.com> Reply-To: "Hans" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; format="flowed"; charset="us-ascii"; reply-type="original" To: linux-8086@vger.kernel.org For what it is worth, it builds OK under Gentoo Linux. The only problem is that the output is somewhat broken :-( ELKS Boot........: Console: BIOS(0000000000000000000000000000015x0000000000000000000000000000025) PC/ XT class machine, 80188 CPU 0000000000000000000000000000640K base RAM. ELKS kernel (-0000000000000000000000000014560 text + 0000000000000000000000000007044 data + -0000000000000000000 000000016516 bss) Kernel text at 0000000000000000000000000001002:0000, data at 0000000000000000000000000001c74:0000 0000000000000000000000000000471 K of memory for user processes. Serial driver version 0.02 ttyS0000000000000000000000000000000 at 0x00000000000000000000000000003f8 (irq = 0000000000000000000000000000004) is a 16450 ttyS0000000000000000000000000000001 at 0x00000000000000000000000000002f8 (irq = 0000000000000000000000000000003) is a 16450 rd driver Copyright (C) 1997 Alistair Riddoch hd Driver Copyright (C) 1994 Yggdrasil Computing, Inc. Extended and modified for Linux 8086 by Alan Cox. doshd: found 0000000000000000000000000000000 floppy drive s ELKS version 0.1.3-pre1 Release not defined VFS: Insert root floppy and press ENTER If anybody has seen this bug or can send me an 80(1)86 build floppy image using BIOS calls I would very much appreciate it. Hans www.ht-lab.com ----- Original Message ----- From: "Dieter Kedrowitsch" To: Sent: Monday, March 08, 2010 4:17 PM Subject: Re: Still having a problem building elks kernel I just created a new VM and installed Arch Linux last night. I'll try installing the bcc x86 packages this evening and cross my fingers that this distro does the trick. I wonder what the difference is? On Fri, Mar 5, 2010 at 4:47 PM, Harley Laue wrote: > Sorry, I meant to get back to you sooner. I run into the exact same > thing with Debian, but not Arch Linux. > Here's the last little bit from Make on Arch which seems to work (I > don't have the means to actually test it though) > > as86 -0 -o boot/crt0.o boot/crt0.s > (cd ../.. ; ld86 -0 -i \ > -t -M -o arch/i86/boot/system \ > arch/i86/boot/crt0.o arch/i86/boot/crt1.o \ > init/main.o kernel/kernel.a fs/fs.a lib/lib.a > net/net.a fs/minix/minixfs.a arch/i86/kernel/akernel.a > arch/i86/lib/lib86.a arch/i86/mm/mm.a arch/i86/drivers/char/chr_drv.a > arch/i86/drivers/block/blk_drv.a \ > > System.tmp ; \ > sort -k4 System.tmp > System.map ; rm -f System.tmp ) > tools/build boot/bootsect boot/setup boot/system > boot/Image > Root device is (3, -128) > Boot sector 512 bytes. > Setup is 1596 bytes. > System is 117788 B (58784 B code, 7728 B data and 51276 B bss) > System is 66544 > make[2]: Leaving directory `/home/harley/Source/elks-project/elks/arch/i86' > > > Obviously the ld86 is failing in Debian/Ubuntu, but like I said, I > haven't looked into why yet other then the fact that it looks like "-t > -M -o arch/i86/boot/system \" isn't in the Debian/Ubuntu's ld86's > command for some reason... -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html