mptbase module from linux kernel drivers to support LSI storage adapters

SliTaz Forum » English Support » Live and installation

mptbase module from linux kernel drivers to support LSI storage adapters

(9 posts) (4 voices)

Started 6 years ago by st_user
Latest reply from st_user
This topic is not resolved

Tags:

No tags yet.

st_user

offline
Member

Hi,

I'm trying to get a family of LSI storage adapters to work on my SliTaz.

I've noticed that one of the important modules (mptbase from drivers/message) is not included in the kernel default configuration. I would assume it should be in the linux-scsi SliTaz package but it's not there either.

Generally speaking, I've gone through all the linux kernel packages (starting with linux- for kernel 3.x) and am not seeing that modules from drivers/message are included anywhere.

Are they excluded due to particular reason? What would be the best way for me to proceed in order not to diverge too far from the default SliTaz kernel and kernel packages?

As a test case, without this module no disks are detected behind VirtualBox SCSI storage adapter switched to LSI logic emulation mode.

Posted 6 years ago #
kultex

offline
Key Master

as root:

tazpkg -gi linux-scsi

to install SCSI drivers - to see, if the drive is in, I need the output of lspci...

Posted 6 years ago #
st_user

offline
Member

linux-scsi package is installed but the module is not included.

this is the controller:

00:14.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI

Posted 6 years ago #
kultex

offline
Key Master

are you able to compile the kernel?

http://doc.slitaz.org/en:guides:kernel

and try this config

CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
# CONFIG_FUSION_LOGGING is not set

Posted 6 years ago #
st_user

offline
Member
Yes, I've tried steps described on that page but /usr/bin/get-linux-source script fails to apply some of the patches to the vanilla kernel. I'm using default SliTaz 32 bit kernel. What I see in /usr/src is this:
```
drwxr-xr-x    3 root     root          4096 May 16 19:02 kernel-patches
lrwxrwxrwx    1 root     root            28 Mar 19 19:31 linux -> /usr/src/linux-3.2.71-slitaz
drwxrwxr-x   25 root     root          4096 May 16 19:05 linux-3.2.71
drwxr-xr-x   21 root     root          4096 May 16 19:05 linux-3.2.71-slitaz
```
The make prepare also fails if I run in linux-3.2.71-slitaz folder. What I see in the linux-3.2.71-slitaz folder is just config files:
```
scripts/Makefile.build:44: /usr/src/linux-3.2.71-slitaz/arch/x86/tools/Makefile: No such file or directory
make[1]: *** No rule to make target '/usr/src/linux-3.2.71-slitaz/arch/x86/tools/Makefile'.  Stop.
/usr/src/linux-3.2.71-slitaz/arch/x86/Makefile:121: recipe for target 'archscripts' failed
```
I haven't read the scripts, but my guess is that running /usr/bin/get-linux-source script should copy sources to the slitaz kernel folder after applying patches but since patching fails, it remains empty?..

I've managed to compile kernel using cooklinux but now I'm trying to understand how to get this kernel to the image built from a slitaz flavor with tazlito gen-distro.
Posted 6 years ago #
kultex

offline
Key Master

I did not compile a kernel since two years with SliTaz - maybe somebody else can help - I have no time now....

Posted 6 years ago #
gibor

offline
Moderator

You run make menuconfig on folder /usr/src/linux-3.2.71-slitaz
not on /usr/src/linux-3.2.71-slitaz/arch/x86/tools
after save menuconfig, run make and make modules_install
copy bzImage from /usr/src/linux-3.2.71-slitaz/arch/x86/boot/bzImage to your folder /boot and rename it to vmlinuz-3.2.71-slitaz and reboot

Posted 6 years ago #
Ceel

offline
Administrator

@ st_user,

I compiled the kernel with kultex's config. You can download it @ http://www.partage-fichiers.com/upload/33nat9w1

Posted 6 years ago #
st_user

offline
Member

@ gibor

Yup, sure I was running make in the /usr/src/linux-3.2.71-slitaz folder and that was the error.

@ Ceel, thanks I'll check it. cooklinux has been working fine for me so far but giving it configuration other than /proc/config and without manual interaction is something I couldn't figure out how to do yet.

Posted 6 years ago #

RSS feed for this topic

Reply

You must log in to post.