More info and a possible solution:
Here's the error output from the make bzImage:
pdc202xx.c: In function `config_chipset_for_dma':
pdc202xx.c:528: warning: `drive_pci' might be used uninitialized in this
function
make[4]: Circular passthrough.h <- hwaccess.h dependency dropped.
sb_card.c:512: warning: `id_table' defined but not used
dpcm.c: In function `dpcm_transport':
dpcm.c:46: warning: unused variable `ret'
namei.c: In function `msdos_lookup':
namei.c:237: warning: implicit declaration of function `fat_brelse'
namei.c: In function `msdos_add_entry':
namei.c:266: warning: implicit declaration of function
`fat_mark_buffer_dirty'
dmi_scan.c:181: warning: `disable_ide_dma' defined but not used
Root device is (3, 66)
Boot sector 512 bytes.
Setup is 4529 bytes.
System is 1153 kB
warning: kernel is too big for standalone boot from floppy
Someone recently mentioned to me that the last error regarding "kernel
is too big..." oftentimes results in an unbootable kernel. His
recommendation was to build everything in as modules and not to compile
anything extra into the kernel.
Sound feasible?
Tim
Tim Wunder wrote:
> Previously, Tim Wunder wrote:
>
>>Net Llama wrote:
>>
>>>--- Tim Wunder <[EMAIL PROTECTED]> wrote:
>>>
>>>>Trying to compile the 2.4.9 kernel on my eD2.4 box. I'm going from the
>>>>2.2.14
>>>>kernel, so I had to do a lot of updating: modutils, e2fsprogs, ppp,
>>>>bison,
>>>>byacc, reiserfs-utils. Some from tarball (modutils, e2fsprog, ppp),
>>>>some from
>>>>eW3.1 SRPM (bison, byacc, reiserfs-utils).
>>>>
>>>>I managed to get thru make xconfig (although resierfs options didn't
>>>>show --
>>>>why would that be?), make dep, make clean, but it fails on make
>>>>
>>>Because you never patched the kernel with the Reiser code
>>>
>>OK. I guess I gotta learn how to do that, now. I'm sure it's "easy".
>>
>>
>>>>bzImage when
>>>>it tries to compile support for my SCSI card -- aic7xxx.
>>>>Here is the error output:
>>>>pdc202xx.c: In function `config_chipset_for_dma':
>>>>pdc202xx.c:528: warning: `drive_pci' might be used uninitialized in
>>>>this
>>>>function
>>>>/tmp/ccZhgkxz.o: In function `yyparse':
>>>>/tmp/ccZhgkxz.o(.text+0xc50): undefined reference to `yylex'
>>>>/tmp/ccZhgkxz.o(.text+0x10b6): undefined reference to `include_file'
>>>>/tmp/ccZhgkxz.o(.text+0x10d0): undefined reference to `include_file'
>>>>/tmp/ccZhgkxz.o(.text+0x24f8): undefined reference to `yylex'
>>>>/tmp/ccVnaMqk.o: In function `main':
>>>>/tmp/ccVnaMqk.o(.text+0x3a3): undefined reference to `include_file'
>>>>make[5]: *** [aicasm] Error 1
>>>>make[4]: *** [aicasm/aicasm] Error 2
>>>>make[3]: *** [first_rule] Error 2
>>>>make[2]: *** [_subdir_aic7xxx] Error 2
>>>>make[1]: *** [_subdir_scsi] Error 2
>>>>make: *** [_dir_drivers] Error 2
>>>>
>>>>Previous to this error, I had a problem with not finding lex. I
>>>>symlinked
>>>>/usr/bin/flex to /usr/bin/lex. After that, I get the above error.
>>>>Should I not have linked flex and lex? Is that not related to this?
>>>>Should I
>>>>try to make xconfig again and review my SCSI settings?
>>>>Anyone have a big clue stick?
>>>>
>>>You did the symlink backwards. It should be /usr/bin/lex -> flex
>>>
>>Actually, I didn't, I just phrased what I did incorrectly. I executed:
>>ln -s /usr/bin/flex /usr/bin/lex
>>
>>Any other suggestions? Is there something other than the bison and flex
>>RPMs from eW31 that I need?
>>
>>Thanks,
>>Tim
>>
>>
>>
>
>
> OK. I reconfigured the SCSI support. Didn't do anything earth-shattering,
> just removed some things that shuldn't have been there (turned off SYM53C8XX
> SCSI support, turned off verbose SCSI error reporting) and the compile seems
> to have worked. I did get a bzImage file in linux-2.4.9/arch/i386/boot. I
> then execute make modules and make modules_install, which seemed to work ok
> (no errors). I then copied the bzImage file to /boot/vmlinuz-athlon and made
> an entry in my /boot/grub/menu.lst file.
>
> title = Caldera 2D2.4 with 2.4.9 kernel
> root = (hd1,1)
> kernel = /boot/vmlinuz-athlon vga=normal debug=2 root=/dev/hdb2 hdd=ide-scsi
>
> When I try to boot with it, I get this error:
> invalid compressed format (err=1)
> System Halted
>
> Obviously, it didn't work. What did I do wrong? There's a script in the same
> directory where the bzImage was placed called install.sh. Am I supposed to
> run that? I hope not, it looks like it'll run lilo, which would certainly
> cause problems with grub.
>
> Please CC to [EMAIL PROTECTED], I'm only getting about have of the posts on
> the list thru the twunder@iwmail address. I don't know if the problem is with
> @home's mail servers or my mail forwarder, but there's a problem somewhere.
>
> Thanks,
> Tim
> _______________________________________________
> http://linux.nf -- [EMAIL PROTECTED]
> Archives, Subscribe, Unsubscribe, Digest, Etc
>->http://linux.nf/mailman/listinfo/linux-users
>
>
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
