I have brand new machine shipped with Intel Server Board S5500BC and Adaptec 1405 SAS card and plan to have openSUSE 11.2 to be install. I was compile the driver’s module asc1xx5.ko successfully in the same machine under openSUSE 11.2 that run from USB stick.
The question is, how do i able to supply this compiled module during openSUSE 11.2 installation? here are steps that i’ve done:
put the module into the floppy disk and press F6 (YES) during installation. The result, openSUSE installer won’t load the module and my SAS harddisk still undetectable/unrecognize by openSUSE installer.
During the installation wizard, i press ctrl+alt+f2 to login into shell command and type:
'module in usb stick, so i mount it frist
**# mount -t vfat /dev/sda1 /mnt
**'load the module
**#modprobe libsas**
**#insmod /mnt/asc1xx5/asx1xx5.ko**
*insmod: error inserting 'asc1xx5.ko': -1 Invalid module format*
I’m newbie on openSUSE so please be gentle, and frustrate already with this kind of situation.
Any workaround will much appreciate.
I am a little confused about what you did to compile your module and whether it would work with a 2.6.31 kernel (Suse 11.2).
Did you download the source file ‘adpinv_linux_src_2.0.0.0.tgz’ from the Adpatec site and attempt to ‘make’ that? If so, in the Changelog in the tgz it says only kernels 2.6.24 to 2.6.27 are supported so you may have problem getting it to work on 2.6.31.
When you make the module what evidence do you have that it compiled and linked correctly? Can you post the last 15 lines of the output of the make command? If that is not available do the make again with:
Did you download the source file ‘adpinv_linux_src_2.0.0.0.tgz’ from the Adpatec site and attempt to ‘make’ that? If so, in the Changelog in the tgz it says only kernels 2.6.24 to 2.6.27 are supported so you may have problem getting it to work on 2.6.31.
Yes I did download it and compile it with successfully. When i said successfully, means, when this module loaded (with command ‘insmod asc1xx5.ko’) , openSUSE 11.2 able to recognize all installed harddisk including the SAS disk. So, the driver provided works fine with openSUSE 11.2
Can you post the last 15 lines of the output of the make command? If that is not available do the make again with:
I currently away from my machine at the moment, but i’ll provide it later.
And the question still remain, how do i can supply this ‘compiled driver’ on openSUSE 11.2 installation? Should i put asc1xx5.ko on the floppy disk and press F6? If yes, I did it, and openSUSE won’t load it
I think I misunderstood your original problem. Alas I have never used the F6 floppy facility and have just tried to track down some further info but to little avail. But some further clarification may help:
When you say:
When i said successfully, means, when this module loaded (with command ‘insmod asc1xx5.ko’) , openSUSE 11.2 able to recognize all installed harddisk including the SAS disk. So, the driver provided works fine with openSUSE 11.2
, do you mean you are booting from your USB stick (which I presume has a live system with persistent partition, containing your compiled module) and you can insert the module from that? However, do you then mean, if you install using the same USB stick neither of the methods you list work?
If that is the case and the module works with the live system, it seems the module is compiled correctly so the make output will be of little use.
One interesting fact I did dig up was that the F6 floppy method only seemed to apply to an internal floppy drive. It would not work with an external floppy drive. Which sort are you using? When you press F6 and YES do you get any sort of confirmation screen such as (roughly) ‘use floppy /dev/fd0?’ or something similar or does it just ignore F6/Yes?
When you use the alternative method from the shell, does dmesg give any further information about the module being in the wrong format?
I am afraid I may not be the best person to ask about all this but maybe activity on this thread will attract a response from someone in the know.
Hi Plodder,
I do appreciate your reply. Probably, due to my limitation on english that makes me unclear to describe my own problem
, do you mean you are booting from your USB stick (which I presume has a live system with persistent partition, containing your compiled module) and you can insert the module from that? However, do you then mean, if you install using the same USB stick neither of the methods you list work?
Let start over, with different approach of problem’s description
Target to achieve: To install openSUSE 11.2 into the machine which have SAS HD using controller Adaptec 1405
**Problem/Situation:**The installation end up fail due to harddisk is not found
Step/tricks that i have done:
**1 - Compile the Adaptec’s driver, and put it on floppy disk. **
Install the openSUSE into USB stick (I have USB stick with 32GB capacity)
re-scan the harddisk, and i can found the entries of my SAS harddisk
I do copy the compiled module (asc1xx5.ko) into external floopy, and shutdown the machine and remove the USB stick
Turn on the machine again, and boot from DVD (openSUSE 11.2 Installer DVD), select Installation
After welcome screen, press F6 and select yes
Select my floppy drive
Installer scan for updated drive on my floppy and nothing happen/change (It seem the installer cannot found any updated driver inside of my floppy)
The rest wizard installation step is useless, because it cannot found my SAS HD as target’s installation
2 - Load the module directly from ‘wizard installation’ shell
I put the asc1xx5.ko into the external storage (USB stick)
Turn on the machine again, and boot from DVD (openSUSE 11.2 Installer DVD), select Installation
While in the wizard screen, i press CTRL+ALT+F2 to enter the shell command
mount the external storage that contain module asc1xx5.ko
try to load the module by supplying the ‘insmod’ command
Ended with error message: insmod: error inserting ‘asc1xx5.ko’: -1 Invalid module format
Conclusion:
Both of above steps none to work, the openSUSE 11.2 installer not found my SAS HD. What should i do to make it done, and openSUSE 11.2 found my SAS HD?
Since the install on the USB disk works, I suggest you use ‘dd’ to copy the entire disk to the SAS disk, then mount the partitions on the SAS disk (is it empty?), chroot to the SAS disk’s mountpoint, mount /proc and /sys, then run ‘yast’ to configure and install the bootloader, run the partitioner to get the proper mountpoints, reboot. Since the driver is already on the USB install and it works…
Well yes I must confess I was coming round to that way of thinking myself. My only theory about the invalid format for the module was that for the kernel for the USB installation and that for the install mode from the DVD were somehow different.
Anyway Carlos, as I predicted, activity on this thread did attract the attention of someone in the know and sure enough a guru materialized out of a pink cloud right in front of our eyes!
And I feel I’m just shooting in the dark, hoping that somehow a solution will get closer. Don’t even know what a SAS-disk is ;)rotfl!
My thought was just to find a way to get the working install copied to the disk. Accessing the disk has already been achieved by OP. But I’ll feel guru for 5 minutes lol!
At the first time i read your post, it brings a new light of my hope!! But…
the objective not only to have successful install openSUSE 11.2 onto my SAS HD, the SAS HD must configure as soft RAID-1 (LVM) sorry to forget this objective at my initial post and ‘dd’ is not support to whole copy of physical disk into LVM.
Boot machine with LiveUSB installer… stopped, got an error here
Install ‘make’ and ‘gcc’ since LiveCD installer doesn’t come with ‘make’ and ‘gcc’ as required to do compile the module …not sure if this can be done? any comment?
Compile the module, re-scan the HD … it’s not proven yet, depend on previous step
Start yast, and do install openSUSE onto HD’s and configure it as LVM (RAID-1) …have no idea, depend on previous step.
Reboot the machine, remove LiveUSB and boot openSUSE from physical HD
Taaddaaaa…openSUSE 11.2 now up and running …i wish
Another option could be ‘yast2-dirinstall’. It would mean booting from the working USB device, perform the install in the folder where the root partition of the SAS-disk is supposed to be coming. You could then chroot to it etc. Don’t have any experience there. Guess it means you have to configure the lot manually.
Another option would be to create your own install media !!! Welcome – SUSE Studio It should be possible to create a copy of 11.2 with the driver added to it. That would solve everything, wouldn’t it ?
I’m interesting SUSE Studio solution, but how do i insert the drivers and load it automatically everytime the installer run? Adaptec’s provide a RPM package and source code of driver module. Which the convenient way should i choose? insert RPM package or insert the compiled driver module? Do you mind to give me sample script that will load this driver every time installer boots?
From what I have read elsewhere in the forums, brewing your own installation via Suse Studio has been judged as ‘not for the faint hearted’. In other words, you may find it heavy going. But things could have improved since that comment was written.
I had a think about your difficulties with the Live USB technique but you hit a snag here apparently:
Now the other alternative solution that i’m working on by creating LiveUSB installation, the strategy that came into my mind as follow:
* Create LiveUSB installer, by converting LiveCD into USB stick .... done
* Create second partition on liveUSB ..... done
* Boot machine with LiveUSB installer.... stopped, got an error here
The reason for this problem has not been determined satisfactorily. It may have appeared on the list of the ‘most vexatious problems’ for suse 11.2. To check that I would need to get into the bug data base which requires an account (I think) so I will leave that to you. It may be that booting from USB is problematic for some MB’s.
It turns out that the Suse 11.2 Live CD image (and I think the Live DVD image is the same) is just a hard disk image with some non conventional partitioning. The first sector looks like a conventional MBR ending in hex 55AA (that may be round the wrong way) and a conventional partition table. However, the partition starts at sector 0 (instead of 63) so includes the MBR.
The important thing is that it doesn’t have to written to a CD or USB. It could also be DD’ed to an ordinary IDE or SATA drive. I have simulated this with qemu and it does boot OK. If you can find, even the most humble, IDE or SATA drive to temporarily slot into your machine you could boot the live system from that instead of USB. May work.
I notice that Suse 11.3 should be here in about a month. That may have better support for you hardware and the problem with the Live USBs may have been solved. You could wait until then and try it with a new system. The pre-release milestone 7(?) is available now if you cannot wait that long.
and i hope more gurus will coming to this thread.