Hi all,
Is this the proper venue for listing bugs (or probable bugs) found in cooker
rpms? If not, I'd appreciate a pointer to the right place.
I recently attempted a kernel upgrade (to 2.4.13-8mdk), but it was unsuccessful. LILO
gives me a "EBDA too big" error, which I've read about a little, but I can't seem to
find a unilateral fix. vmlinuz-2.4.13-8mdk is 1073187 bytes long, and since the
kernel's precompiled, I haven't any clue how to decrease its size. I'm curious why
more people wouldn't run into this kind of limitation -- it must have to do with some
obscure hardware I'm using (it is a pretty old BIOS...)?
The original rpm install claimed that the postinstall script had an exit code of 1
(detectloader couldn't find the bootloader?), which I had no clue how to address.
I've reinstalled the rpm (w/ --force) quite a few times, and it hasn't worked yet (so
it wasn't just a fluke, I would imagine), though it no longer complains about the
postinstall script failing (see debug below):
This is not the first kernel upgrade where I've encountered an "EBDA too big" error.
I'd really appreciate it if someone could tell me how to fix this (or confirmed that
it is some kind of bug). The one kernel that I can boot from is 2.4.9 (I believe I
might have compiled this one on my own), is 1046303 bytes -- not much smaller than
2.4.13-8mdk (but just under 2^20....?).
~~~~~~~
rpm --upgrade --force -vvh output:
D: running preinstall script (if any)
kernel #################################################GZDIO:
1901 reads, 15567340 total bytes in 31.395 secs
#
D: --- 427 kernel-2.4.13-8mdk
D: removing "kernel" from Name index.
D: removing 1221 entries from Basenames index.
D: removing "System/Kernel and hardware" from Group index.
D: removing 9 entries from Requirename index.
D: removing 5 entries from Providename index.
D: removing 2 entries from Conflictname index.
D: +++ 428 kernel-2.4.13-8mdk
D: adding "kernel" to Name index.
D: adding 1221 entries to Basenames index.
D: adding "System/Kernel and hardware" to Group index.
D: adding 9 entries to Requirename index.
D: adding 5 entries to Providename index.
D: adding 2 entries to Conflictname index.
D: running postinstall scripts (if any)
+ cd /boot
+ '[' -x /sbin/installkernel ']'
+ /sbin/installkernel -a -c 2.4.13-8mdk
not adding entry, 2413-8 already exists
+ depmod -a -F /boot/System.map-2.4.13-8mdk 2.4.13-8mdk
D: closed db index /var/lib/rpm/Depends
...(various other rpm db closes)
~~~~~~~
[root@guild brian]# file /boot/vmlinuz-2.4.13-8mdk
/boot/vmlinuz-2.4.13-8mdk: x86 boot sector
~~~~~~~
[root@guild brian]# grep "x86 boot" /usr/share/magic/magic
0x1FE leshort 0xAA55 x86 boot sector
~~~~~~~
[root@guild brian]# lilo -vvvvv -T EBDA
LILO version 21.7, Copyright (C) 1992-1998 Werner Almesberger
Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 24-Feb-2001 and compiled at 18:11:44 on Apr 8 2001.
Extended BIOS Data Area (EBDA) = 1K
Conventional Memory = 639K 0x09FC00
The First stage loader boots at: 0x00007C00 (07C0:0000)
The Second stage loader runs at: 0x0009D600 (9D60:0000)
The kernel cmdline is passed at: 0x0009FA00 (9000:FA00)
~~~~~~~
[root@guild brian]# ls -lF /boot/vmlinuz-2.4.13-8mdk
-rw-r--r-- 1 root root 1073187 Nov 17 13:00 /boot/vmlinuz-2.4.13-8mdk
~~~~~~~
[root@guild brian]# lilo -v
LILO version 21.7, Copyright (C) 1992-1998 Werner Almesberger
Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 24-Feb-2001 and compiled at 18:11:44 on Apr 8 2001.
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Mapping message file /boot/message-graphic
Boot image: /boot/vmlinuz
Added linux *
Boot image: /boot/vmlinuz
Added failsafe
Boot image: /boot/vmlinuz-2.4.9
Added linux-2.4.9
Boot other: /dev/fd0, loader /boot/chain.b
Pseudo partition start: 0
Added floppy
Skipping /boot/vmlinuz-2.4.13-1mdk
Boot image: /boot/vmlinuz-2.4.13-8mdk
Added 2413-8
/boot/boot.0300 exists - no backup copy made.
Writing boot sector.
~~~~~~~
Also, my most recent samba upgrade (to 2.2.2-?mdk) has been fraught with peril. I
believe that the "network recycle bin" patch might be the cause of one problem I've
noticed -- I have trouble deleting files on samba shares (about 95% of the files I
attempted to delete, I could not. Windows told me that the file might be in use --
which is a different error message than a sharing violation, I believe). Also, Domain
logons don't seem to work either (though I fear that's probably a generic samba bug,
probably not limited to the cooker build).
I can include my smb.conf and debug level 10 logs, if anyone thinks it'll help.
--
Brian Cain
