Help needed with IDE CD-ROM and 2.4.21 kernel

Hi! Ok, I've just upgraded my Slackware 8 system with the latest official 2.4.21 kernel release. I built it with gcc-3.3 and glibc-2.3.2. The build went smoothly but I can't seem to read any mount any CDs with Microsoft Joliet extensions. I HAVE enabled Joliet Extension support in the kernel. The CD-ROM IS detected when the machine boots.

I can mount the SAME CD that can't be read in the IDE CD-ROM in the SCSI CD-RW I used to burn the CD with.

Now, when I built my kernel I used the ".config" file from the 2.4.20 kernel I upgraded from. This way, the same config options I used during my 2.4.20 kernel build would be carried over. The bizarre thing is when I boot my 2.4.20 kernel, I can mount CDs with Joliet Extensions just fine. I just can't mount them with the 2.4.21 kernel.

Here is the output from my mount command:

tom@linux:~$ su
Password:
root@linux:/home/tom# mount /dev/cdrom /cdrom
/dev/cdrom: Input/output error
mount: block device /dev/cdrom is write-protected, mounting read-only
/dev/cdrom: Input/output error
mount: you must specify the filesystem type
root@linux:/home/tom#

Here is output from dmesg:

hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev 16:00 (hdc), sector 0
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev 16:00 (hdc), sector 4
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev 16:00 (hdc), sector 0
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50
end_request: I/O error, dev 16:00 (hdc), sector 4
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 16:00.
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 16:00.
root@linux:/home/tom#

I DO have "Use multi mode by default" enabled in the kernel.

Any ideas?

Thanks in advance!

Peace...

I would check if in your .21 kernel you have all the file system supports you had in .20.

cat /proc/filesystems

Great idea! I'll be sure to do that.

Thanks!

Peace...

Well, I booted my 2.4.20 kernel and saw the SAME filesystems listed in /proc/filesystems as I do with my 2.4.21 kernel.

Additionally, I found I could NOT mount the RedHat CD I burned either. So my guess is it's something with the 2.4.21 kernel I built.

Has anyone had problems building 2.4.21 with gcc-3.3?

Thanks...

Peace...

I have had many problems with 2.4.21. It is very buggy and my hardware configuration seems to exercise all of the bugs. There are some HUGE patches for 2.4.21. I suggest that you download patches ac1, ac2, ac3, and ac4, apply them, and do your kernel compile over again.

Look at the changelog for ac4 and I think that you will find your cdrom problem mentioned.

Originally posted by jailbait I suggest that you download patches ac1, ac2, ac3, and ac4, apply them, and do your kernel compile over again.

Thanks! Are these patches accumulative (ac4 contains the ac3 patches plus new patches)?

Look at the changelog for ac4 and I think that you will find your cdrom problem mentioned.

Where can I find the ChangeLog for ac4? There isn't a link to one on http://www.kernel.org/

Thanks!

Peace...

----------------------------------------------------------------------------------
Are these patches accumulative (ac4 contains the ac3 patches plus new patches)?

No, You have to apply all four in order.
To apply the patches you put the unpacked linux directory in /usr/src and change its name to linux21-ac1. You put the packed patch bz2 in /usr/src
and do:
cd /usr/src
bunzip2 patch-2.4.21-ac4.bz2 | patch -p0 -E

rename /usr/src/linux21-ac1 to linux21-ac2

and carry on.

at the end ln -s linux to linux21-ac4
----------------------------------------------------------------------------------
Where can I find the ChangeLog for ac4?

http://linuxtoday.com/developer/2003062702026NWKNDV

I think that you want the ide-scsi fix. If that isn't the right one there are several other possibilities scattered through the changelogs.
-----------------------------------------------------------------------------------

Originally posted by jailbait ---------------------------------------------------------------------------------- No, You have to apply all four in order. To apply the patches you put the unpacked linux directory in /usr/src and change its name to linux21-ac1. You put the packed patch bz2 in /usr/src and do: cd /usr/src bunzip2 patch-2.4.21-ac4.bz2 | patch -p0 -E rename /usr/src/linux21-ac1 to linux21-ac2 and carry on. at the end ln -s linux to linux21-ac4

Thanks for the info. I'm applying the patches now and patch-2.4.21-ac1 applied just fine but I get:

patching file arch/alpha/kernel/entry.S
Reversed (or previously applied) patch detected! Assume -R? [n]

for just about every file (with the file names changing of course) when I apply patch-2.4.21-ac2, which looks like ac2 contains the ac1 patches.

Am I missing something here?

Peace...

patching file arch/alpha/kernel/entry.S
Reversed (or previously applied) patch detected! Assume -R? [n]

I remember getting that message but I think that it was because I applied a patch twice while I was trying to figure out how the patch system worked.

Originally posted by jailbait I remember getting that message but I think that it was because I applied a patch twice while I was trying to figure out how the patch system worked.

Yeah, that's why I was thinking the patch files were accumulative. If patch-2.4.21-ac2 contained the patch-2.4.21-ac1 patches plus the new stuff, then applying patch-2.4.21-ac2 after applying patch-2.4.21-ac1 would cause that message since the 2.4.21-ac1 patches had already been applied.

Based on that, I applied patch-2.4.21-ac4 (which turned out to be the largest of the four patches I downloaded after I uncompressed them) to the stock 2.4.21 kernel and re-built.

I'm still getting the problem, so I'll see what 2.4.22 does for me. In the meantime, I can still mount CDs in my SCSI CD-RW so I can use that for now.

I also wonder what would happen if I compiled 2.4.21 (with patches appled) with gcc-3.2.x vs gcc-3.3. My 2.4.20 kernel, which DOES work, was built with gcc-3.2.1.

In any event, thanks very much for your help!

Peace...

It looks like I'm STILL having this problem with the 2.4.22 kernel I just installed from source.

Does anyone have any other ideas or know where I can possibly get more info on this problem?

Thanks...

Peace...

You could try using the ide-scsi driver as a workaround.
Haven't tried this myself as I'm not using that kernel, but it may be worth a try.