I would like to share the whole story in case someone with a similar machine finds this problem.
Scenario. xSeries 346 + qlogic 2312
The Qlogic driver wouldnt load correctly.
So after trying to load it in all ways, built-in, module, etc.. and paying attention to one of the errors it was giving "irq 3 nobody cared".
and googling about this error a bit, figured that after all and so many tries maybe something was wrong about the IRQ config in these machines after all (previously I considered this option but deestimated it when I saw a vmware esx installing perfectly with its qlogic 2.4 driver)...
...and I remembered when it boots the qlogic banner says its using irq 3, but if you enter its config with Ctrl+Q it says it is using IRQ 5 and you cant change that config option...
and I tried with all kinds of kernel approaches for PCI IRQ Routing (Any, BIOS, etc...) maybe Im just very ignorant in this matter...
So very pesismistic about the issue I went to advanced options in the BIOS config, selected PCI IRQ ROUTING and placed all devices to Select IRQ 3 (later I will find which of this really need it to make it work), like let the caballary arrive!! well, it worked.
So if any of you find the same problem with this kind of IBM machine.. check the IRQ's first!
Regards and thanks for everything
Ezra.
2005/12/20, Brian Elliott Finley <[EMAIL PROTECTED]>:
You might try the experimental UYOK (Use Your Own Kernel) code in 3.6.x.
After running "si_prepareclient" on your golden client, you'll end up
with a kernel and initrd.img in /etc/systemimager/boot. If you use that
kernel and initrd.img to boot, it will be using the same kernel,
modules, and device files that were in use on your golden client when
you ran si_prepareclient.
It will still try to auto-detect any other hardware that might be
present.
When you pull your image with si_getimage, those files will come over to
your imageserver as part of the image (naturally).
Now here's the hack part -- this will be automated in 3.8.x:
* If you manipulate your boot files on your own, just copy those
files into "the right place".
* If you want to use si_mkautoinstallcd, then copy that kernel and
initrd.img over the ones in here...
/usr/share/systemimager/boot/i386/standard/
...then you _may_ be able to run si_mkautoinstallcd like normal.
And of course, let us know of your success or failure.
Cheers!
-Brian
Thus spake ezra resnedan ([EMAIL PROTECTED]):
>Anyone is autoinstalling machines like this with system imager? It seems it
>does not matter how I compile the 2.6 the qlogic driver gives errors and
>cant use the hard disks assigned through this card.. sometimes i even get
>"kernel panic".
>
>Any recommendations?
>
>Thx
--
Brian Elliott Finley
Mobile: 630.631.6621
