>I recently upgraded my linux kernel to 2.2.x and encountered some serious
>problems with my HP SureStore 7200i CD-RW. Apparently, the kernel does
>not even recognize my HP :-(
2 root@red:/burner# uname -r
2.2.3
2 root@red:/lib/modules/2.2.3/misc# mount /dev/sr0 /burner/ -r
2 root@red:/lib/modules/2.2.3/misc# cd /burner/
2 root@red:/burner# dir
total 1549
dr-xr-xr-x 12 root root 4096 Nov 13 17:03 ./
drwxr-xr-x 28 root root 3072 Mar 9 21:13 ../
-r--r--r-- 1 root root 436 Oct 15 15:30 .buildlog
-r--r--r-- 1 root root 19686 May 28 1997 COPYING
-r--r--r-- 1 root root 3017 Oct 12 17:14 README
-r--r--r-- 1 root root 12657 Nov 13 16:43 README.1ST
-r--r--r-- 1 root root 2751 Sep 19 1997 RPM-PGP-KEY
dr-xr-xr-x 5 root root 2048 Oct 27 12:58 RedHat/
dr-xr-xr-x 2 root root 2048 Nov 12 05:46 SRPMS.pt2/
-r--r--r-- 1 root root 874 Nov 13 17:03 TRANS.TBL
dr-xr-xr-x 6 root root 2048 Oct 30 14:56 doc/
dr-xr-xr-x 6 root root 4096 Oct 30 16:30 dosutils/
dr-xr-xr-x 5 root root 2048 Oct 30 16:44 gnome/
dr-xr-xr-x 2 root root 2048 Nov 13 16:52 images/
dr-xr-xr-x 2 root root 2048 Nov 13 16:50 infomagc/
lr-xr-xr-x 1 root root 8 Nov 13 16:14 infomagic -> infomagc/
-r--r--r-- 1 root root 33719 Nov 13 16:58 locatedb.1
-r--r--r-- 1 root root 214903 Nov 13 17:02 locatedb.ldr
-r--r--r-- 1 root root 1089807 Nov 13 17:01 ls_lR
-r--r--r-- 1 root root 164791 Nov 13 16:57 ls_lR.1
dr-xr-xr-x 4 root root 2048 Oct 26 18:40 misc/
dr-xr-xr-x 2 root root 2048 Nov 13 17:03 rr_moved/
dr-xr-xr-x 4 root root 2048 Nov 11 12:35 updates/
2 root@red:/burner# dmesg
[filtered]
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
scsi : 1 host.
Vendor: HP Model: CD-Writer+ 7200 Rev: 3.01
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
Vendor: TOSHIBA Model: CD-ROM XM-5302TA Rev: 2095
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
sr0: scsi3-mmc drive: 2x/6x writer cd/rw xa/form2 cdda tray
Uniform CDROM driver Revision: 2.52
I had problems initially using my CDROM's too. I then realized
that I didn't have the cdrom modules compiled the same way that I
did with 2.0.x. With 2.0.x I had no IDE-CDROM compiled in, but
rather SCSI emulation compiled in. In 2.2.x I have both
IDE-CDROM and IDE-SCSI compiled as modules. So, I have to
manually load the driver prior to using the burner or CDROM. I
could have it autoload easily enough I suppose, but I still boot
2.0.x and I'm not sure how to keep my conf.modules separate for
both without boot script kludges, or other trickery.
>Therefore, does anyone know if there are any known problems with this
>CDR and kernel 2.2.1 or 2.2.2, perhaps related to a situation where
>two CD-ROMs are connected to secondary IDE interface (IRQ 15)?
My HP is on hdc and my Toshiba is on hdd, both on the secondary.
>Here's the full story:
>
>I've got redhat 5.2, patched to support kernel 2.2
>kernel 2.2.2
>two IBM 6.4 GB hard disks connected to primary IDE (IRQ14)
>Toshiba 6202B 32x CD-ROM connected to secondary IDE (IRQ 15) as master
>HP SureStore 7200i CD-RW connected to secondary IDE (IRQ 15) as slave
>Loadlin 1.6a as the linux boot method
I've got 5.1, manually upgraded partially to 5.2, with many other
stuff upgraded beyond 5.2, also with 2.2.x stuff applied.
>With the kernel compiled according to the instructions on CD-writing howto
>(IDE/ATAPI CD-ROM disabled, SCSI hostadapter emulation and generic SCSI
>CD-ROM support compiled into the kernel), the kernel boots, after
>displaying a few screens of various SCSI errors & warnings, finally
>recognizing only the Toshiba CD-ROM. (see dmesg output at the end)
That is for 2.0.x, the rules are different with 2.2.x.
>With the kernel compiled without SCSI-support (using HP only for reading),
>I can't get the kernel to boot at all. Instead, it hangs up with several
>"Interrupt lost" or similar errors. With special boot parameters
>hdd=cdrom hdd=noprobe I can get the kernel to boot and even mount
>both CD-ROMs nicely.
Can't say... perhaps hdc=cdrom hdd=ide-scsi ?
>Unfortunately, I have not been able to test different combinations of
>the HD and CD hardware, but do you think such a hardware setup would be
>the reason to my problems or perhaps only some unfortunate guesses with
>configuration before compiling the new kernel?
Misconfiguration most likely.
-- Mike A. Harris Linux advocate GNU advocate Computer Consultant Open Source advocateThe DVORAK keyboard layout RULES! I memorized it in 45 minutes and I don't think I'm ever going back to QWERTY!
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/