Re: Built 2.6.8 kernel without ext3 bug and working qlogic driver
Did you use the default kernel-config file (you can find it in
boot/config-2.6.8-xxxxx after installing a 2.6.8 image)? If not, just copy
it to kernel-source/.config. After that try to make menuconfig and change
your kernel configuration. This ensures that all debian default modules are
installed in the kernel in the default configuration. In menuconfig disable
the module qlogicisp and enable qla1280 with the new extra option for
* After that compile kernel.
* Before install: open /usr/sbin/mkinitrd in text editor and replace the
module in the line containing "qlogicisp" by "qla1280".
* Install kernel image with dpkg
* edit aboot.conf
If there is still the FATAL about sym53c8xx_2 there is something other in
your kernel configuration missing.
At 14:37 12.01.2005, you wrote:
The recent discussion between Norbert and Uwe is beyond my knowledge, but
I seems to me I just got touched by the topic. I compiled a new kernel
from the latest kernel-source-2.6.8-12. If I want to install the
corresponding deb, when trying to make the initrd, it tells me:
Setting up kernel-image-2.6.8-rawhide-smp (alphaente.20) ...
/usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
FATAL: Module sym53c8xx_2 not found.
FATAL: Module qlogicisp not found.
WARNING: This failure MAY indicate that your kernel will not boot!
but it can also be triggered by needed modules being compiled into
I understood, that it's a problem in initrd-tools not yet updated...
Anyway: Can I choose some different options in a way, that I will be able
to run mkinitrd? I have chosen:
sym53c8xx_2 as module --> my boot disk (or is it called sym53c8xx?)
qla1280 as module --> my root disk
Do I have compile it into the kernel for a workaround? Do I need to
compile qlogicisp, too? As a module? Can I build my mkinitrd with the
setting in mkinitrd.conf modules=dep?
...or do I have to wait until fixed? (Unfortunately there are still some
bugs in 2.4.27 which let my alpha crash* when resyncing its md raid in
runlevel > 1...I need to try a newer kernel).
Thank you for your help.
*) There are two symptoms: "Timeout in mbox command on qlogicisp" -> the
machine can't reboot nor anything else no more, but seems to run. Or, the
second is an "Aieee, killing interrupt handler". This happens mostly on
RAID5 but also on RAID1, towards the end of a syncing process. The excact
message is lost, it can't write to syslog no more, when it happened. I
know that my layout of md-disks is a bit strange, it has many disks taking
part in multiple arrays.
Norbert Tretkowski wrote:
* Uwe Schindler wrote:
At 01:03 08.01.2005, Norbert Tretkowski wrote:
It contains both drivers, but I think we'll change the driver from
qlogicisp to qla1280 with the next initrd-tools upload.
I did not download your kernel-image, but in your description you
wrote that qlogicisp is removed, and support for 1020/1040 in
You catched an outdated package... currently there are qla1280 and
qlogicisp enabled in svn.
This works for all kernels (2.4 and 2.6). But then you have to
definitely disable qlogicisp.
I'm thinking about enabling qla1280 for qla1040 contollers only on
alpha running a 2.6 kernel.
To UNSUBSCRIBE, email to debian-alpha-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de - http://www.schindlers-software.de
eMails: email@example.com (private); firstname.lastname@example.org (company)
Tel./Fax: +49 700 PCLATEIN (+49 700 72528346)
Schindlers Software - Home of Schindlers PC-LATEIN 3.10
DIE Software zum Lateinlernen!