Bug 155384

Summary:	ide-scsi broken again
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Michael Glockenstein <mail>
Component:	Kernel	Assignee:	Jens Axboe <axboe>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Beta 3
Target Milestone:	---
Hardware:	i686
OS:	SuSE Pro 9.2
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael Glockenstein 2006-03-06 12:07:25 UTC

with the previous 2.6.15.x kernels the ide-scsi module worked fine. but
since 2.6.16.rc1 it is broken again. last what i could check was the rc3,
where the problem still exist, although the kernel changelog says it was
fixed with rc1. the problem is, that i can load the ide-scsi module but
no drive is detected. from my point of view, it is not a good idea to change
to a rc kernel version in the middle of the beta phase.
regards michael

Comment 1 Olaf Kirch 2006-03-06 15:11:43 UTC

Jens, I think you'll love this one.

Comment 2 Jens Axboe 2006-03-07 12:30:15 UTC

Are you sure this isn't just because ide-cd is loaded and thus claims the device? Does it work if you do:

# rmmod ide-cd; modprobe ide-scsi

?

Comment 3 Michael Glockenstein 2006-03-07 13:27:06 UTC

No, I don't think so. With kernel 2.6.15 it was possible to boot with
  hdc=ide-cd hde=ide-scsi,
where hdc is a dvd and hde a mo drive. This mo drive only works with
ide-scsi. With all older kernels <2.6.10 it was only possible to load
either ide-cd or ide-scsi. I was very surprised that 2.6.15 was able
to load both modules and every module handles only one device.
That was the best I have seen so far.
But with 2.6.16rcs it was different. I tried what you suggested. What
happened sounds dangerous: rhythm noises of my hard drive. And
still no scsi mo drive to be seen. There is really something wrong.

Comment 4 Jens Axboe 2006-03-07 13:40:06 UTC

There was never an hde=ide-scsi parameter, do you mean hde=scsi? Please post a full boot log of your system.

Comment 5 Jens Axboe 2006-03-07 13:41:25 UTC

Sorry you are right, ide-foo was a special case handled in the IDE layer for assigning sub drivers. The old and original method is =scsi though, please use that instead and report if it works or not.

Comment 6 Michael Glockenstein 2006-03-07 21:16:12 UTC

I was not able to install the 10.1 beta6 because of problems of the package manager, so I used the rescue boot with the hde=scsi parameter. The result is that it does not change anything. But now I was able now to assign the correct drivers with this sequence:
load ide-floppy first (assigned to my zip, which is hdg)
modprobe ide-cd ignore='hde' (assigned to my dvd, which is hdc)
modprobe ide-scsi (assigned to my mo drive, which is hde)
The other way loading only ide-scsi for all the three drives is possible too.
So I have to say, the reason for my original error message is gone with beta6.
But nevertheless it does not work.
udev recognizes only /dev/sda for the mo drive. after "fdisk -l /dev/sda" also
the partition /dev/sda1 is created. I think this can be solved with special udev configuration. but now the real error:
"mount /dev/sda1 /mnt" needs very long. the fat partition is recognized as ext2. no data access possible. after unmounting it and remounting with
"mount -t vfat /dev/sda1" it tells me "/dev/sda1 is not a valid block device".
this error message I have seen also with many kernel versions from 2.6.11
to 2.6.14, when I tried to access the mo drive via the ide subsystem.
summary: improvements: yes, working: no.

Comment 7 Jens Axboe 2006-03-21 19:43:54 UTC

Received a private note to just drop this bug, as it doesn't work on other OS's either.