On boot/load process from "install_amd64_minimal" the loader check initio-scsi-card (2-3sek), go on without loading. Message "waiting of devices" pop up and mostly system hangs. Sometimes the system can reboot with ctrl-alt-del.
Workaround: Don't know.
Further description on another bug. Search for "initio amd64 2.6.15"
I'm guessing that you're booting with "doscsi" then. At any rate, it is well-documented that you can use noload to stop a module from loading. Either that, or you're going to have to give us a more exact error message within context so we know where the problem is occurring. I would try to first use noload=initio and see if it boots.
(In reply to comment #1)
Sorry, I forgot to say: I need the initio-module for my scsi-only system. I update my old AthlonXP-system to a new AMD64 system (Venice, MoBo: K8NGM2-FID).
Self-evident therefore I try "doscsi". The noload=initio works great but I need the initio.
The problem seems to be the initio-driver itself. I have reboot without scsi-interface-card, but with a IDE-HDD. Then I build the kernel for x86_64 with initio inside (named bzImage-initio) and also with initio as module (named bzImage-inimod). Also I have the old kernel (2.6.12) for x86 (AthlonXP on A7V8X) with initio inside.
Then I start the new system with x86er kernel (2.6.12) without problems (initio-card activ). Copy over the kernels from IDE-HDD to the SCSI-HDD, modify the bootloader and testing the following (IDE-HDD removed-> SCSI-only):
1.) reboot with 2.6.12 OK
2.) reboot with bzImage-initio (x86_64) crash with kernel-panic
plugged in the IDE-HDD
3.) reboot with bzImage-inimod from IDE-HDD, modprobe the initio -->crash with kernel-panic
After a Kernel-panic I can't copy the output for you, sorry.
Ahh, so you actually have an initio card. This makes a bit more sense now.
*** This bug has been marked as a duplicate of 90282 ***
(In reply to comment #4)
> *** This bug has been marked as a duplicate of 90282 ***
You are sure?
I don't have a "A100u2w" (A100u2w.o). I have a INI9100 (initio.o).
You're right. I apologize. I'm not familiar with these cards.
If anyone with one of these cards wishes to help in testing, please see bug #126602 and assist there. We will then be able to REOPEN this bug and resolve the issue.