Messages in this thread |  | | Date | Tue, 5 Nov 1996 23:43:19 -0800 (PST) | From | babydr <> | Subject | Re: objdump -k -q -o 0xC0100000 in 2.1.7 |
| |
On Sun, 3 Nov 1996, Michael L. Galbraith wrote: > Greetings, > > I seem to be the only person in the universe who is having trouble > getting 2.1.7 to build a bootable kernel. I'm beginning to worry that > my system has mutated into something that merely "resembles" linux. > It started out as 0.99.6 SLS a.out, I don't have a clue as to what I > should call it today. DebiSlackHatSLS? down boy!, back! Aieee!! > > This is a fresh tree retrieved from ftp.funet.fi. (no tinkering) > > The way I understand the build, you... > ld -m elf_i386 -Ttext 0xC0100000... link kernel high > objdump -k -q -o 0xC0100000... dump high: gift wrap kernel > <compression omitted> > ld -m elf_i386 -Ttext 0x100000... link boot tools low > objdump -k -q -o 0xC0100000... dump high: gift wrap what? > tools/bbuild bbootsect setup... low(boot)+high(kernel)=bootable kernel > > Why does this work for everyone in the world but me?? Me=dipstick?? > I can hand-make a kernel with other than 0 size if I change the second > objdump to match the start address of the link. > > Thanks in advance, > Mike
By chance are you attempting to compile NCR53c8xx & AHA154x in the same kernel ? Even have AHA154x as a module ?
A while back I sent off a note about trying to do this & get an output (using 'make bzdisk') of 0+1 data in 0+1 data out for the 'dd' of the boot image.
This sound simular, JimL
|  |