Skip to contentSkip to conversation

Why SCSI module needed for PCI-IDE ATA only disks ?

DISCUSSION Bernard Pidoux 4 participants 4 messages Dec 4, 2006 – Dec 5, 2006

lore
Share & tools
lore
#0 lore raw

I am asking why need to compile the following modules while I do not have any SCSI device ?

Modules Loaded

rose netrom mkiss ax25 crc16 mach64 drm nfsd exportfs lockd nfs_acl sunrpc ipv6 snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq ne2k_pci 8390 snd_pcm_oss snd_mixer_oss snd_ens1371 gameport snd_rawmidi snd_seq_device snd_ac97_codec snd_ac97_bus af_packet snd_pcm snd_timer snd_page_alloc snd soundcore floppy ide_cd binfmt_misc loop supermount

ahci ata_piix libata scsi_mod dm_mod

cpufreq_ondemand cpufreq_conservative cpufreq_powersave speedstep_lib freq_table intel_agp agpgart uhci_hcd usbcore evdev tsdev ext3 jbd

Hardware is :

00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:04.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) 00:04.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:04.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) 00:04.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS) 00:0c.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06) 00:0d.0 Mass storage controller: Promise Technology, Inc. PDC20262 (FastTrak66/Ultra66) (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c)

ata_piix needs scsi_mod

When making menuconfig, the need to select SCSI submenu options seems rather surprising to me for an IDE ATA disk only system.

Bernard Pidoux

#1 lore raw
Quoted 2 lines · Bernard Pidoux

I am asking why need to compile the following modules while I do not have any SCSI device ?

Because your hardware is driven by a libata based driver. This means it is a scsi bus driver and thus, requires mod_scsi and the scsi disk module to access disks on the bus.

#2 lore raw
In reply to Bernard Pidoux
Quoted 2 lines · Bernard Pidoux

I am asking why need to compile the following modules while I do not have any SCSI device ?

libata uses SCSI to provide a lot of infrastructure that it would otherwise have to recreate. Also, using SCSI meant that it automatically worked in existing installers.

Jeff

#3 lore raw
Quoted 8 lines · Jeff Garzik
Quoted 2 lines · Bernard Pidoux

I am asking why need to compile the following modules while I do not have any SCSI device ?

libata uses SCSI to provide a lot of infrastructure that it would otherwise have to recreate. Also, using SCSI meant that it automatically worked in existing installers.

Jeff

This confusion could easily be remedied by explaining the requirement in the Help output for libata drivers/section. Also, making a dependency in the menu (since there is one) or automatically selecting the required scsi items when you select a libata driver would seem logical. As it is, nothing is said of scsi requirements in menuconfig. Trying to boot a machine without compiling the scsi drivers (something you're allowed to do) results in a system that boots and initializes the ata busses but can't communicate to any of the drives on them, (useless).

Then maybe later down the road, moving those scsi drivers shared by scsi and libata to the generic block layer would seem logical. That is, when ide is gone from the kernel and all the kernel speaks is scsi, there would be no need to differentiate scsi from the generic block layer devices, and no need to compile "scsi" drivers to have libata driver support, eliminating any possible further confusion.