I'd like to thank you all for your kind and generous advice. I seem to
have fixed all of the problems I was having, and an absolute minimum of
new ones have appeared in their place ;). I finally found the SuSE rpm
for kernel 2.2.5, removed my generic source tree, installed the SuSE one,
and made the kernel. Much to my suprise (well, not really), the new
kernel worked, as did most of the modules I built along with it. I do
have a couple of weird things I'd like to get rid of, however.
The boot messages list two modules (actually three, but I only have a par-
tial name for the third) that it cannot load. The first one, that I only
have a partial name for, is something like cp437. The next is a codepage
nls_iso8859-1. The final rogue module is char_major_4, which the screen
reports to be missing some eight or nine times.
A final thorn in my side is my ATAPI Zip drive. The firmware revision is
13A, so the drive is aged. I made an entry in my /etc/fstab to mount my
Zip as /dev/hdb4, which puts the volume as the fourth partition on the
secondary device of my primary controller. According to all of the FAQ's,
the disks that come IBM pre-formatted have the meat of the disk (some
96megs) on this fourth partition. The entry in /etc/fstab tries to mount
it as vfat, which I can only assume is correct. However...
When I look at /var/log/boot.msg, this line stands out:
<5>hdb: The drive reports both 100663296 and 100646912 bytes as its
capacity
And when I try to mount the device at /zip, I get this:
mount: wrong fs type, bad option, bad superblock on /dev/hdb4, or too
many mounted file systems
Any ideas?
-=|JP|=-
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
