Re: ide-scsi and initrd
Herbert Xu was roused into action on 2002-11-24 02:32 and wrote: David P James <[EMAIL PROTECTED]> wrote: # more /var/log/dmesg [snip] PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio scsi1 : SCSI host adapter emulation for IDE ATAPI devices OK, the problem is that ide-probe isn't loaded at this point in time so there is nothing for ide-scsi to use. Perhaps this is something that modprobe could do by default. Try pre-install ide-scsi modprobe -k ide-probe-mod Thanks Herbert - that seems to have worked. I get an error early in the boot process where it reports that 'ide-scsi' is not available but when it works out later on and the CDRW is identified as a device on scsi1. Also, is there any way to get rid of these warning messages that tell me that modules.conf is newer than modules.dep? Now all I have to do is solve the problem of the soundcard module not loading at boot despite being in /etc/modules and working just fine when insmod is run on it after I've logged in... -- David P. James 4th Year Economics Student Queen's University Kingston, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
David P James <[EMAIL PROTECTED]> wrote:
> Herbert Xu was roused into action on 2002-11-23 16:11 and wrote:
>> David P James <[EMAIL PROTECTED]> wrote:
>>
>>>options ide-cd ignore=hdb
>>>alias scd0 sr_mod
>>>alias scsi_hostadapter ide-scsi
>>>pre-install sg modprobe ide-scsi
>>>pre-install sr_mod modprobe ide-scsi
>>>pre-install ide-scsi modprobe ide-cd
>
> # more /var/log/dmesg
> [snip]
> PIIX4: IDE controller on PCI bus 00 dev 39
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
> ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
> scsi1 : SCSI host adapter emulation for IDE ATAPI devices
OK, the problem is that ide-probe isn't loaded at this point in time
so there is nothing for ide-scsi to use. Perhaps this is something
that modprobe could do by default.
Try
pre-install ide-scsi modprobe -k ide-probe-mod
You will need to run update-modules and then regenerate the initrd image by
mkinitrd -o /boot/initrd.img- /lib/modules/
and run lilo if you use that.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
Shyamal Prasad was roused into action on 2002-11-23 22:54 and wrote: "David" == David P James writes: David> Herbert Xu was roused into action on 2002-11-23 16:11 and David> wrote: >> David P James <[EMAIL PROTECTED]> wrote: >> When ide-cd gets loaded, you should see the message >> ide-cd: ignoring drive hdb >> If you don't, then ide-scsi is not going to work. David> I do see it, but it's too late... it's coming after hdb is David> already identified. The CDRW should be identified David> immediately after scsi1 as a device on scsi1, should it David> not? That's how my SCSI HD is identified on scsi0 and my David> scanner when it is attached and on for scsi2. I'm new to initrd and a lot of other things, and Herbert can probably tell right away what is going on. Having said that, I do have a suggestion, and then a few questions for more knowledgeable folks: Have you looked in the etc/modules.conf file inside your initrd image (/boot/initrd.img-2.4.18-k7)? Does it have the changes from the 'cdrw' file you created? (BTW, if you don't already know, you look at the file with 'mount -t cramfs -o loop initrd.img /mnt). Yes, the contents of 'cdrw' (in my case 'ide-scsi') are contained in etc/modules.conf inside /boot/initrd.img-2.4.18-686. I did not even know you could examine the contents of initrd images... I am guessing (I can't tell from you dmesg snippet, but I'm confident since there was no 'change_root' from cramfs in the snippet) that all the stuff you described is actually happening *before* your root disk partition is mounted. So ide-cd is being loaded during the initrd phase, and the etc/modules file in that image does not have the 'ignore' lines and so on, so ide-cd grabbed the device. Why it did that (if I'm on the right track) I don't know, and I'm hoping to be educated. Well there was a cramfs entry that I snipped out: "cramfs: wrong magic" not that I know what that means... Somehow, my initrd image *does* include my cdrw file changes. The modules.conf file in the image is exactly the same as in /etc. In addition, I noticed the the kernel-image package does not include the initrd image. So it is being created after installation. It is also seemingly being updated when I'm running update-modules (?). I have not been able to figure out how all this magic happened just yet. I'm hoping some one can tell me where to RTFM (Herbert?). I imagine mine was updated when I ran update-modules after creating the file as well. I cannot see any difference between your system and mine that should account for this oddity. -- David P. James 4th Year Economics Student Queen's University Kingston, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
"David" == David P James writes: David> Herbert Xu was roused into action on 2002-11-23 16:11 and David> wrote: >> David P James <[EMAIL PROTECTED]> wrote: David> > pre-install ide-scsi modprobe ide-cd David> David> The thing I don't understand is the ordering in the last David> line, yet every example I've ever seen online is like David> this. I'm tempted to flip it one day just to see what David> happens. I'm guessing it won't make any difference. See below. Besides, you did the Right Thing (tm). >> When ide-cd gets loaded, you should see the message >> ide-cd: ignoring drive hdb >> If you don't, then ide-scsi is not going to work. David> I do see it, but it's too late... it's coming after hdb is David> already identified. The CDRW should be identified David> immediately after scsi1 as a device on scsi1, should it David> not? That's how my SCSI HD is identified on scsi0 and my David> scanner when it is attached and on for scsi2. I'm new to initrd and a lot of other things, and Herbert can probably tell right away what is going on. Having said that, I do have a suggestion, and then a few questions for more knowledgeable folks: Have you looked in the etc/modules.conf file inside your initrd image (/boot/initrd.img-2.4.18-k7)? Does it have the changes from the 'cdrw' file you created? (BTW, if you don't already know, you look at the file with 'mount -t cramfs -o loop initrd.img /mnt). I am guessing (I can't tell from you dmesg snippet, but I'm confident since there was no 'change_root' from cramfs in the snippet) that all the stuff you described is actually happening *before* your root disk partition is mounted. So ide-cd is being loaded during the initrd phase, and the etc/modules file in that image does not have the 'ignore' lines and so on, so ide-cd grabbed the device. Why it did that (if I'm on the right track) I don't know, and I'm hoping to be educated. Somehow, my initrd image *does* include my cdrw file changes. The modules.conf file in the image is exactly the same as in /etc. In addition, I noticed the the kernel-image package does not include the initrd image. So it is being created after installation. It is also seemingly being updated when I'm running update-modules (?). I have not been able to figure out how all this magic happened just yet. I'm hoping some one can tell me where to RTFM (Herbert?). Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
Herbert Xu was roused into action on 2002-11-23 16:11 and wrote: David P James <[EMAIL PROTECTED]> wrote: options ide-cd ignore=hdb alias scd0 sr_mod alias scsi_hostadapter ide-scsi pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd The thing I don't understand is the ordering in the last line, yet every example I've ever seen online is like this. I'm tempted to flip it one day just to see what happens. When ide-cd gets loaded, you should see the message ide-cd: ignoring drive hdb If you don't, then ide-scsi is not going to work. # more /var/log/dmesg [snip] SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 10 for device 00:0d.0 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs Vendor: SEAGATE Model: ST39175LW Rev: 0001 Type: Direct-Access ANSI SCSI revision: 02 (scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset 8, 16bit) scsi0:A:0:0: Tagged Queuing enabled. Depth 8 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 [snip] PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio scsi1 : SCSI host adapter emulation for IDE ATAPI devices aha152x: BIOS test: passed, detected 1 controller(s) aha152x: resetting bus... aha152x2: vital data: rev=1, io=0x340 (0x340/0x340), irq=9, scsiid=7, reconnect=enabled, parity=enabled, synchronous=enabled, delay=1000, extended translation=disabled aha152x2: trying software interrupt, ok. scsi2 : Adaptec 152x SCSI driver; $Revision: 2.4 $ hub.c: USB new device connect on bus1/2, assigned device number 2 input0: USB HID v1.00 Mouse [Logitech Logitech] on usb1:2.0 apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16) hda: FUJITSU MPC3043AT, ATA DISK drive hdb: CR-48XATE, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide-cd: ignoring drive hdb hda: 8448300 sectors (4326 MB), CHS=8940/15/63 /dev/ide/host0/bus0/target0/lun0: [PTBL] [525/255/63] p1 p2 < p5 > I do see it, but it's too late... it's coming after hdb is already identified. The CDRW should be identified immediately after scsi1 as a device on scsi1, should it not? That's how my SCSI HD is identified on scsi0 and my scanner when it is attached and on for scsi2. -- David P. James 4th Year Economics Student Queen's University Kingston, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
David P James <[EMAIL PROTECTED]> wrote:
>
> options ide-cd ignore=hdb
> alias scd0 sr_mod
> alias scsi_hostadapter ide-scsi
> pre-install sg modprobe ide-scsi
> pre-install sr_mod modprobe ide-scsi
> pre-install ide-scsi modprobe ide-cd
>
> The thing I don't understand is the ordering in the last line, yet every
> example I've ever seen online is like this. I'm tempted to flip it one
> day just to see what happens.
When ide-cd gets loaded, you should see the message
ide-cd: ignoring drive hdb
If you don't, then ide-scsi is not going to work.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
On 22 Nov 2002, Shyamal Prasad wrote: > "David" == David P James writes: > > David> problems. Despite having "hdb=ide-scsi" in my grub config > David> file ide-cd is still getting loaded first. So I have to > David> manually run 'rmmod ide-scsi' and then 'insmod ide-scsi', > David> which for some reason actually works. Just plain silly. > > What kernel are you running? I presume you are not running a IDE boot > device, so perhaps you want to tell ide-cd to ignore hdd instead? I'm running 2.4.18-686-smp from woody. My boot device is /dev/sda1, the two cd-rom devices are /dev/hdb and /dev/hdc. I don't remember why one is master and one slave, but it doesn't matter as there are no other ide devices. > I'm curious why my set up works (no SCSI devices, lots of IDE of which > only one requires SCSI emulation). I have almost the dual of that. I have several SCSI devices and only two IDE devices of which both require ide-scsi. I've got it working now, see my other post today. -- -| Bob Hauck -| To Whom You Are Speaking -| http://www.haucks.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
On Fri, 22 Nov 2002, David P James wrote: > Bob Hauck was roused into action on 2002-11-22 08:01 and wrote: > > When I upgraded, that stopped working because the ide-cd driver is now a > > module. So I added an /etc/modultils entry "cdrw" per the CD-Writing > > HOWTO: > > > > options ide-cd ignore="hdb hdc" > > alias scd1 sr_mod > > pre-install sg modprobe ide-scsi > > pre-install sr_mod modprobe ide-scsi > > pre-install ide-scsi modprobe ide-cd > > > > > That "works" in that all the right modules get loaded, but I still can't > > use the cd burner. > I've got practically the same setup and configuration (including a SCSI > HD and card) and the same problems. Ok, I think I've got a handle on this. First, with the 2.4.18-686-smp kernel the "append=hdb=ide-scsi" thing doesn't work. The reason being that ide-cd is a module rather than being built into the kernel as it was with 2.2 kernels and the bf2.4 kernel that's installed by default. Next, the reason I was getting a spew of error messages with the above modutils options was that ide-cd does not like it if you tell it to ignore all of the ide devices in the system. If I gave it only one device to ignore the error messages went away. I think the reason why ide-cd was getting loaded at all was because I was calling hdparm to enable DMA (which my previous 2.2 kernel did not turn on by default) and make sure the cd-rom devices were in the best mode. So what I did was this: 1. Built a new initrd.img with just the drivers I need to boot. I put this list in /etc/mkinitrd/modules: ext3 aic7xxx Then I ran: "mkintrd -o /boot/initrd.img-2.4.18-686-smp /lib/modules/2.4.18" to build a new initial ramdisk image, followed by "lilo" to make sure lilo knew where it was. This seems to have returned everything to the initial working state I had after first upgrading to 2.4.18-686-smp. 2. In /etc/modultils/cdrw: alias ide-cd off I have no ide devices except for my cd-rom and cd-rw and I want both of them to be treated as scsi so they will show up in kreatecd. Thus I don't need ide-cd. If you have some ide devices that you want to be treated as ide, then I think you'll need to put "options ide-cd ignore=hdb" instead as suggested in the CD-Writing-HOWTO. Then run update-modules. 3. Added these modules to /etc/modules: ide-probe-mod ide-scsi The ide-probe-mod causes the two ide devices to exist as /dev/hdb and /dev/hdc so that hdparm will work, but it doesn't load any cd-rom support. Now everything works fine. The "sg" and "sr_mod" modules seem to get loaded automagically when I try to write to a cd. The rest of my settings in /etc/modutils are basically stock, except for one to load NVdriver for my NVidia card. -- -| Bob Hauck -| To Whom You Are Speaking -| http://www.haucks.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
Shyamal Prasad was roused into action on 2002-11-23 00:10 and wrote: "David" == David P James writes: David> problems. Despite having "hdb=ide-scsi" in my grub config David> file ide-cd is still getting loaded first. So I have to David> manually run 'rmmod ide-scsi' and then 'insmod ide-scsi', David> which for some reason actually works. Just plain silly. What kernel are you running? I presume you are not running a IDE boot device, so perhaps you want to tell ide-cd to ignore hdd instead? Now I'm curious why my set up works (no SCSI devices, lots of IDE of which only one requires SCSI emulation). I'm running kernel 2.4.18-686 hda: IDE HD with Windows98 hdb: IDE CDRW sda: SCSI HD attached to AHA2940UW card (set as BIOS boot device) with Debian 3.0 I had absolutely no problems getting the device to work; it just won't set up properly at boot. I don't know if it has anything to do with having two other SCSI hosts on the system or not... SCSI0 - AHA2940UW SCSI1 - ide-scsi SCSI2 - AHA1502A (for a scanner) the 2940uw module (which has another name) is loaded first then ide-cd module is apparently loaded then ide-scsi and finally aha152x is loaded So the problem seems to be ide-cd independent of the other SCSI hosts. Here's my /etc/modutils/ide-scsi (practically identical to Bob Hauck's): options ide-cd ignore=hdb alias scd0 sr_mod alias scsi_hostadapter ide-scsi pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd The thing I don't understand is the ordering in the last line, yet every example I've ever seen online is like this. I'm tempted to flip it one day just to see what happens. -- David P. James 4th Year Economics Student Queen's University Kingston, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
"David" == David P James writes: David> problems. Despite having "hdb=ide-scsi" in my grub config David> file ide-cd is still getting loaded first. So I have to David> manually run 'rmmod ide-scsi' and then 'insmod ide-scsi', David> which for some reason actually works. Just plain silly. What kernel are you running? I presume you are not running a IDE boot device, so perhaps you want to tell ide-cd to ignore hdd instead? Now I'm curious why my set up works (no SCSI devices, lots of IDE of which only one requires SCSI emulation). /Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
Bob Hauck was roused into action on 2002-11-22 08:01 and wrote: I just upgraded one of my machines to kernel-image-2.4.18-686-smp. This box has an IDE cd burner that previously worked with 2.2.20-udma100-ext3. It also has a regular IDE cd-rom that I've been treating as a scsi device just because. All filesystems are on SCSI (Adaptec on the motherboard). For the 2.2.20 kernel, I had the following line in /etc/lilo.conf: append="hdb=ide-scsi hdc=ide-scsi" And then installed ide-scsi from /etc/modules. When I upgraded, that stopped working because the ide-cd driver is now a module. So I added an /etc/modultils entry "cdrw" per the CD-Writing HOWTO: options ide-cd ignore="hdb hdc" alias scd1 sr_mod pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd That "works" in that all the right modules get loaded, but I still can't use the cd burner. It seems that ide-cd is getting loaded earlier in the boot process and grabbing the cd-rom devices. I mounted the initr.img and looked around and it appears that for some reason ide-cd is getting loaded in the loadmodules script. I've got practically the same setup and configuration (including a SCSI HD and card) and the same problems. Despite having "hdb=ide-scsi" in my grub config file ide-cd is still getting loaded first. So I have to manually run 'rmmod ide-scsi' and then 'insmod ide-scsi', which for some reason actually works. Just plain silly. -- David P. James 4th Year Economics Student Queen's University Kingston, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi and initrd
#include * Bob Hauck [Fri, Nov 22 2002, 08:01:10AM]: > That "works" in that all the right modules get loaded, but I still can't > use the cd burner. It seems that ide-cd is getting loaded earlier in the > boot process and grabbing the cd-rom devices. I mounted the initr.img and > looked around and it appears that for some reason ide-cd is getting loaded > in the loadmodules script. Well, on my system ide-cd seems to honor the boot command line and does not take control of the devices when they are noted in the hdX=ide-scsi arguments. So I load ide-scsi later and it works fine. Gruss/Regards, Eduard. -- Für manche ist es Windows, für andere der längste Virus der Welt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ide-scsi and initrd
I just upgraded one of my machines to kernel-image-2.4.18-686-smp. This box has an IDE cd burner that previously worked with 2.2.20-udma100-ext3. It also has a regular IDE cd-rom that I've been treating as a scsi device just because. All filesystems are on SCSI (Adaptec on the motherboard). For the 2.2.20 kernel, I had the following line in /etc/lilo.conf: append="hdb=ide-scsi hdc=ide-scsi" And then installed ide-scsi from /etc/modules. When I upgraded, that stopped working because the ide-cd driver is now a module. So I added an /etc/modultils entry "cdrw" per the CD-Writing HOWTO: options ide-cd ignore="hdb hdc" alias scd1 sr_mod pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd That "works" in that all the right modules get loaded, but I still can't use the cd burner. It seems that ide-cd is getting loaded earlier in the boot process and grabbing the cd-rom devices. I mounted the initr.img and looked around and it appears that for some reason ide-cd is getting loaded in the loadmodules script. So I did "mkinitrd" to update my initrd.img with the new modules.conf. That causes a spew of "can't create /var/log/ksym[date].log, read-only filesystem" right after the Adaptec driver gets loaded (before switching root filesystems). So, I put everything back to the original configuration, rebuilt initrd.img, and got it all working again. Then I wrote a script to remove the ide-cd and cdrom modules and install ide-scsi. Made that run as S99local in /etc/rc2.d. This works, but sure is ugly. So my questions is what is the proper Debian way of getting ide-scsi working with an initrd kernel? And along the same lines, what is the proper procedure when upgrading from non-initrd kernels to initrd ones when the root filesystem is scsi? What I did was to add the proper Adaptec driver to /etc/modules and then run mkinitrd. -- -| Bob Hauck -| To Whom You Are Speaking -| http://www.haucks.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
