https://bugzilla.novell.com/show_bug.cgi?id=298726#c2 --- Comment #2 from Matej Horvath 2007-08-13 02:08:25 MST --- Petr Zejdl wrote in an e-mail: ------------------------------------------ After installation I didn't have aic94xx-seq.fw in /lib/firmware nor initrd /lib/firmware. I added it into initrd manually, but no change. But if i do modprobe -r aic94xx followed by modprobe aic94xx in initrd shell, it will successfully load aic94xx. Then booting can be resumed. Later I installed aic94xx firmware package in yast a try newer kernel, but the result is the same. Initrd will not load aic94xx module for the first time. I have to manually modprobe -r/modprobe. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwalle@novell.com Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c6 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |cthiel@novell.com --- Comment #6 from Bernhard Walle 2007-08-22 13:29:09 MST --- I tried to reproduce this problem on a machine here. I discovered several problems related to this: 1. The aic94xx driver got not included into the initrd. This was due to an empty proc_name in the driver. This is perfectly legal from kernel side (see bug 247049) as the proc_name interface is deprecated. The current "way" is to execute $(basename $(readlink /sys/class/scsi_host/host${hostnum}/device/../driver)) That's basically the same as lsscsi -H does and this work. This is fixed now in initrd. Alexander Graf will submit a new package. 2. The "adaptec-firmware" is *not* installed. Without that package, it's also not possible to include the firmware in initrd. Christoph, do you know when the package gets installed or who is responsible for this (Yast team? patterns?). 3. If the driver is in INITRD_MODULES of /etc/sysconfig/kernel, than this module gets automatically loaded by an insmod call in initrd *before* udev is started. Because there's no udev, the firmware is also not loaded because that's part of the udev event handling. According to Alexander Graf who wrote the initrd scripts, YaST should remove (or at least not add) that module (and QLogic modules are also affected) from INITRD_MODULES because it's not necessary any more since the initrd automatically adds module for SCSI devices that are used in the system. Christoph, can you also handle this, i.e. reassign to YaST people? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c10 Bernhard Walle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|snwint@novell.com | --- Comment #10 from Bernhard Walle 2007-08-23 10:34:53 MST --- (In reply to comment #7 from Christoph Thiel)

Bernhard, the adaptec-firmware is pulled in automatically in case the right hardware is found:

quoting adaptec-firmware.spec Supplements: modalias(pci:v00009005d00000410sv*sd*bc*sc*i*) Supplements: modalias(pci:v00009005d00000412sv*sd*bc*sc*i*) Supplements: modalias(pci:v00009005d0000041Esv*sd*bc*sc*i*) Supplements: modalias(pci:v00009005d0000041Fsv*sd*bc*sc*i*) Supplements: modalias(pci:v00009005d00000430sv*sd*bc*sc*i*) Supplements: modalias(pci:v00009005d00000432sv*sd*bc*sc*i*) Supplements: modalias(pci:v00009005d0000043Esv*sd*bc*sc*i*) Supplements: modalias(pci:v00009005d0000043Fsv*sd*bc*sc*i*)

I guess the package just wasn't present on the media --> ie. it couldn't get installed. I'll add the package to the CDs now.

Looks reasonable, yes.

On 3, I'm not sure if this really is an issue?

? This is the bug the reporter was talking about (adding manually firmware to initrd, still not loaded, but loaded if rmmod/insmod in shell invoked by initrd). So it's the main issue ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726 Christoph Thiel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|snwint@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c18 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@novell.com Status|NEW |NEEDINFO Info Provider| |agraf@novell.com --- Comment #18 from Thomas Fehr 2007-08-28 02:48:59 MST --- What exactly is the proposal? Do not add any drivers related to disk controllers to INITRD_MODULES? If this is the case we also need to drop "yast2 controller" since it only deals with adding/ordering controller modules in INITRD_MODULES. If these drivers should also be removed during update then this needs also be handling in Initrd.ycp (added Jiri Srain to cc:). BTW: Really interesting that we already start thinking about basic working concepts of SL 10.3 after beta#2, I would have expected to start developing such concepts not before RC3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c22 Christoph Thiel changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|cthiel@novell.com |agraf@novell.com --- Comment #22 from Christoph Thiel 2007-08-28 06:43:43 MST --- We just figured out that only those drivers that require a firmware to be loaded in addition to the actual kernel module don't need to be added to the list of modules anymore. NEEDINFO to agraf, to provide a list / regex of affected modules. Please also check the current mkinitrd implementation, if it really pulls in the firmware and also the module, in case it's not in INITRD_MODULES! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c23 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@novell.com Status|NEEDINFO |NEW Info Provider|hare@novell.com | --- Comment #23 from Hannes Reinecke 2007-08-28 06:51:06 MST --- The affected storage modules are aic94xx qla2xxx -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c25 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jsrain@novell.com --- Comment #25 from Thomas Fehr 2007-08-28 07:31:10 MST --- Jiri, AFAIK there is code in Initrd.ycp that prevents certain modules from showing up in INITRD_MODULES. Wouldn't it be best to add the two above modules there. So we could handle first installation und update with the same mechanism. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c27 --- Comment #27 from Bernhard Walle 2007-08-28 13:41:13 MST --- The shell snippet for module in $(find /lib/modules/$(uname -r) -name '*.ko') ; do [ $(/sbin/modinfo -F firmware $module | wc -l) -ge 1 ] && \ echo $(basename $module) done generates a list of all modules that load firmware dynamically. It might make sense to add something like this into the build process because the list of drivers with firmware might change every release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=298726#c30 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #30 from Jiri Srain 2007-08-30 02:31:47 MST --- Preventing modules listed in #23 from being inserted to initrd. Please, test with Beta3 or next internal build (submitting to autobuild in a moment). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.