Kernel compiled from source won't read /parts/ of a CD?
This is one of the strangest situations I have ever seen: my re-compiled Linux 2.4.18 kernel now /refuses/ to read /only/ the "/Mandrake" directory branch of all three of the Mandrake distribution CDs. It /has/ to be some kernel option, but I can't figure which one; any advice or debugging hints at all are greatly appreciated.
I had to recompile a Mandrake 8.2 kernel to remove pcmcia support (so I could use the sf release of it) Using the stock Mandrake 8.2 binary kernel, the CDs can be read just fine, it is only the kernel that I compiled from the linux-2.4.18-6mdk.src package that has this trouble. There are no warning messages, only one line returned to the console to say "ls /Mandrake: Invalid argument" and one line in syslog to say "ISO 9660: RRIP_1991A" and that's the total diagnostic information I have.
Using /usr/bin/isoinfo, I can list the CD contents just fine; all the unix tools (ls, cd, cp ...) and rpm cannot read /Mandrake.
What could I have possibly omitted from the kernel config to cause this? How could that one directory be singled out by a simple kernel config problem? (or could it be a gcc 2.96 problem?)
Signature · 3 lines
Gary Lawrence Murphy <[email protected]> TeleDynamics Communications Inc Business Innovations Through Open Source Systems: http://www.teledyn.com "Computers are useless. They can only give you answers."(Pablo Picasso)
Signature · 4 lines
-- Gary Lawrence Murphy <[email protected]> TeleDynamics Communications Inc Business Innovations Through Open Source Systems: http://www.teledyn.com "Computers are useless. They can only give you answers."(Pablo Picasso)
Quoted 6 lines · Gary Lawrence Murphy
This is one of the strangest situations I have ever seen: my re-compiled Linux 2.4.18 kernel now /refuses/ to read /only/ the "/Mandrake" directory branch of all three of the Mandrake distribution CDs. It /has/ to be some kernel option, but I can't figure which one; any advice or debugging hints at all are greatly appreciated.
I had some problem like this. I don't know what caused it because it was 'fixed' by a re-boot. I think it was that the kernel 'thought' the block-size was wrong for the CD.
Anyway, the next time it happend, I copied the entire contents of a CD to a file (ising 'cp'). I then mounted the file through the loop device. I figured it might be quicker than re-booting (it wasn't). It worked anyway.
The next time it happens, I will try to mount the CD through the loop device. Anyway, you can try that now.
Maybe it will help you read it.
mount -t iso9660 -o loop /dev/cdrom /mnt
Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips). The US military has given us many words, FUBAR, SNAFU, now ENRON. Yes, top management were graduates of West Point and Annapolis.
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"R" == Richard B Johnson <[email protected]> writes:
R> I had some problem like this. I don't know what caused it R> because it was 'fixed' by a re-boot. I think it was that the R> kernel 'thought' the block-size was wrong for the CD.
Glory be, that did fix it -- overnight since I posted this we had a power out and this morning the problem is gone. Who would have thought of rebooting a /linux/ machine??!!! :)
Thanks for the tip; if it does ever happen again, I'll also try the loopback thing to see if that gives any clues.
Signature · 3 lines
Gary Lawrence Murphy <[email protected]> TeleDynamics Communications Inc Business Innovations Through Open Source Systems: http://www.teledyn.com "Computers are useless. They can only give you answers."(Pablo Picasso)