Skip to contentSkip to conversation

new scsi hardware detection in 2.4.7(pre)

DISCUSSION Olaf Hering 3 participants 5 messages Jul 23, 2001 – Jul 30, 2001

lore
Share & tools
lore
#0 lore raw

Hi,

I get this on non-scsi systems with scsi compiled into the kernel:

SCSI subsystem driver Revision: 1.00 request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted

iBook, PowerBook etc.

#
# SCSI support
#
CONFIG_SCSI=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs #
# CONFIG_SCSI_DEBUG_QUEUES is not set CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set CONFIG_SCSI_AIC7XXX=y CONFIG_AIC7XXX_CMDS_PER_DEVICE=8 CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
# CONFIG_SCSI_DPT_I2O is not set CONFIG_SCSI_ADVANSYS=m

Any ideas whats wrong here? I see that in all 2.4.7pre kernels.

Gruss Olaf

Signature · 4 lines
 $ man clone

BUGS
       Main feature not yet implemented...
#1 lore raw
Quoted 6 lines · Olaf Hering

I get this on non-scsi systems with scsi compiled into the kernel:

SCSI subsystem driver Revision: 1.00 request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted

The SCSI midlayer is trying to load the SCSI host adapter, that is an unavoidable side effect of including SCSI support. Because no adapter is found, kmod tries to automatically load a module that can find a host adapter. The "Root fs not mounted" message occurs when you try to load any module before / is mounted.

#2 lore raw
In reply to Olaf Hering
Quoted 9 lines · Keith Owens
Quoted 6 lines · Olaf Hering

I get this on non-scsi systems with scsi compiled into the kernel:

SCSI subsystem driver Revision: 1.00 request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted

Quoted 5 lines

The SCSI midlayer is trying to load the SCSI host adapter, that is an unavoidable side effect of including SCSI support. Because no adapter is found, kmod tries to automatically load a module that can find a host adapter. The "Root fs not mounted" message occurs when you try to load any module before / is mounted.

Does that make any sense? I mean, there are some scsi drivers, none of them found a valid device, why do we look for more drivers? It would make sense if there are no low level device drivers in the kernel binary.

Gruss Olaf

Signature · 4 lines
 $ man clone

BUGS
       Main feature not yet implemented...
#3 lore raw
Quoted 17 lines · Olaf Hering
Quoted 9 lines · Keith Owens
Quoted 6 lines · Olaf Hering

I get this on non-scsi systems with scsi compiled into the kernel:

SCSI subsystem driver Revision: 1.00 request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted

Quoted 5 lines

The SCSI midlayer is trying to load the SCSI host adapter, that is an unavoidable side effect of including SCSI support. Because no adapter is found, kmod tries to automatically load a module that can find a host adapter. The "Root fs not mounted" message occurs when you try to load any module before / is mounted.

Quoted 4 lines

Does that make any sense? I mean, there are some scsi drivers, none of them found a valid device, why do we look for more drivers? It would make sense if there are no low level device drivers in the kernel binary.

There is no way for the mid layer to distinguish between "no SCSI card configured into kernel" and "SCSI card configured but failed to detect hardware". Even when there is a card built into the kernel, it still makes sense to scan for modules if the initial card failed. That gives you fallback to modules when you change your hardware.

If you boot a SCSI kernel on a non-SCSI box then you should alias scsi_hostadapter off. You still get the 'Root fs not mounted' warning messages, just ignore them. If you are using one kernel build for lots of different hardware you should be using initrd, then the root fs messages go away as well.

#4 lore raw

It makes more sense if U can send a copy to SCSI group too.People like Eric and many others only looks at the linux-scsi group.I think by doing this U can cater to a wider group of people and more specifically this sort
of issues are relavant to both -kernel and scsi group. I hope and expect that in future this will be taken care of.
Thanx

Quoted 56 lines · --- Keith Owens
Quoted 5 lines · Olaf Hering
Quoted 3 lines · Keith Owens
Quoted 1 line · Olaf Hering

I get this on non-scsi systems with scsi

compiled into the kernel:

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not

mounted

Quoted 1 line
Quoted 1 line
Quoted 1 line

request_module[scsi_hostadapter]: Root fs not

mounted

Quoted 1 line
Quoted 1 line
Quoted 1 line

request_module[scsi_hostadapter]: Root fs not

mounted

Quoted 2 lines
Quoted 2 lines

The SCSI midlayer is trying to load the SCSI host

adapter, that is an

Quoted 1 line
Quoted 1 line

unavoidable side effect of including SCSI

support. Because no adapter

Quoted 1 line
Quoted 1 line

is found, kmod tries to automatically load a

module that can find a

Quoted 1 line
Quoted 1 line

host adapter. The "Root fs not mounted" message

occurs when you try to

Quoted 3 lines
Quoted 1 line

load any module before / is mounted.

Does that make any sense? I mean, there are some

scsi drivers, none of

Quoted 1 line

them found a valid device, why do we look for more

drivers? It would

Quoted 1 line

make sense if there are no low level device drivers

in the kernel

Quoted 1 line

binary.

There is no way for the mid layer to distinguish between "no SCSI card
configured into kernel" and "SCSI card configured but failed to detect
hardware". Even when there is a card built into the kernel, it still
makes sense to scan for modules if the initial card failed. That gives
you fallback to modules when you change your hardware.

If you boot a SCSI kernel on a non-SCSI box then you should alias
scsi_hostadapter off. You still get the 'Root fs not mounted' warning
messages, just ignore them. If you are using one kernel build for lots
of different hardware you should be using initrd, then the root fs
messages go away as well.

Quoted 7 lines

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/