trash can wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Success!
I downloaded kernel-2.6.24-0.81.rc4.git7.fc9.src.rpm from the Fedora
development tree. Went through "rpm dependecy hell" and solved all
dependencies by installing other fc9 rpms. I used
config-2.6.23.1-42.fc8 as my starting point. My
config-2.6.24-0.81.rc4.git7.local.fc8 is attached.
After compilation and installation of the kernel rpm, upon boot I could
see a device sdc4 being created, but boot failed with
"mount: missing mount point", some errors in mounting from setuproot and
switchroot.
I believe the problem was with the Red Hat/Fedora anaconda installer
and/or grub, and my multiboot machine setup. I had not been able to boot
updated fc8 kernel packages, only the originally installed kernel.
Note that my Fedora 7 and Fedora 8 distributions share no directories
(one exception) and all this work is taking place in the Fedora 8
distribution. The /boot partition IS shared among my distributions.
I found my /etc/fstab file had two "/" mount point entries. The last line
contained LABEL=/ and is a reference to my Fedora 7 root partition.
I deleted this line from fstab as I did not want to change the mount
point for this line to mount my Fedora 7 distribution on Fedora 8.
This kernel installation process was appending LABEL=/ to my kernel
line in grub.conf:
kernel /vmlinuz-2.6.24-0.81.rc4.git7.local.fc8 ro root=/dev/VGf800/LogVol00 rhgb quiet LABEL=/
LABEL=/ was removed from the line.
I then needed to recreate my initrd image:
mkinitrd /boot/initrd-2.6.24-0.81.rc4.git7.local.fc8.img \
2.6.24-0.81.rc4.git7.local.fc8
Finally I was able to boot (Zip disk inserted) to the local kernel and the
Zip drive works as expected.
# blkid
/dev/sdc4: SEC_TYPE="msdos" LABEL="ZIP-100" UUID="4910-1305" TYPE="vfat"
dmesg:
ata9.00: ATAPI: LITE-ON DVDRW SOHW-1693S, KS0B, max UDMA/66
ata9.01: ATAPI: IOMEGA ZIP 100 ATAPI, 05.H, max MWDMA1, CDB intr
ata9.00: limited to UDMA/33 due to 40-wire cable
ata9.00: configured for UDMA/33
ata9.01: configured for MWDMA1
scsi 8:0:0:0: CD-ROM LITE-ON DVDRW SOHW-1693S KS0B PQ: 0 ANSI: 5
scsi 8:0:1:0: Direct-Access IOMEGA ZIP 100 05.H PQ: 0 ANSI: 5
sd 8:0:1:0: [sdc] 196608 512-byte hardware sectors (101 MB)
sd 8:0:1:0: [sdc] Write Protect is off
sd 8:0:1:0: [sdc] Mode Sense: 00 40 00 00
sd 8:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 8:0:1:0: [sdc] 196608 512-byte hardware sectors (101 MB)
sd 8:0:1:0: [sdc] Write Protect is off
sd 8:0:1:0: [sdc] Mode Sense: 00 40 00 00
sd 8:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc4
My thanks to all the great people who solved this problem and those who patiently
responded to my queries.
- -RoyBoy626
I've been behing reading this list, I was going to say that I have
always had best luck with those drives using the old idescsi driver,
although I haven't used a kernel newer than... 2.6.18 or so on the old
machines. Since you have a solution I won't suggest you try that with an
old kernel ;-)
--
Bill Davidsen <[email protected]>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
