Jon Pennington wrote:
>
> 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.
>
Edit /etc/conf.modules and add:
alias char-major-4 off
and notice that it is hyphens, not underscores.
> 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
See the attached file about my experiments with a zip drive connected to
a second parallel port.
>
> Any ideas?
>
> -=|JP|=-
--
JLK
Linux, because it's STABLE, the source code is included, the price is
right.
#!/bin/bash
# this script must be run as root or su. Keeping the su term open
# allows you to jump back and forth to mount and unmount zip drives.
# You can unmount as a user but you cannot mount as a user. I need
# to put this module loading command in a boot-time script some
# place.
#
# the lilo.conf has the following line: append="ppa=0x278,0" prior
# to any device stanzas, and /bin/sbin/lilo has been run to update
# the loader.
#
# formatting or reformatting a zipdrive:
# first, be sure a previously formatted disk is in the drive before running
# the modprobe command below. This allows the modprobe to get the correct
# size from the hardware. After the modeprobe is run then either the
# mount command is executed to mount the disk that is in the drive, or that
# disk is replaced with an unformated disk and the following command is run:
# mkfs -t ext2 /dev/sda4 98288
# or
# mke2fs /dev/sda4
#
# the value 98288 was reported by the fsck program. The following was reported
# by the modprobe program:
# Cylinders: 96
# Sectors: 196608 [96 MB]
# Bytes/Sector: 512
#
# I computed 96 * 512 * 2048 = 100,663,296 bytes per disk, or 98304 blocks.
# When I used that value in the mkfs command it seemed to work, and still
# does, but when I checked with fsck it reported an error and gave the
# "should be" value of 98288 given above, which is 100,646,912 bytes per disk.
#
# mounting a formatted drive:
#mount -t ext2 /dev/sda4 /mnt/zipdrv
#
/sbin/modprobe /lib/modules/2.0.35/scsi/ppa.o 0x278,0
