SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Is this with the huge kernel? If so you may have better results with the generic kernel and an initial ram disk.
Don't know if you've done this before but there are instructions in /boot/Readme.initrd. Be aware that the instructions with 12.2 are slightly out of date as the kernel quoted 2.6.27.4 is in fact 2.6.27.7. You also will need to supply the -r option to mkinitrd to tell it where the root device is and -f to tell it what filesystem as well as -m to tell it what filesystem module to include.
Then you'll have to amend /etc/lilo.conf and re-run lilo. When you do be sure to leave the old huge kernel there in case of problems.
Thanks for the suggestion - it worked. This wasn't a fatal problem but am trying to get things working correctly so revisited things again and reread your message and gave it a try.
I was able to do the mkinitrd and used -m aic7xxx:mbcache:fbd:ext3 -f ext3 etc., and it worked. Some additional magic took place because the mpt modules loaded and the drives were accessable too.
Unfortunately another problem surfaced but I would like to start a new thread for that.
I have a similar adaptec controller on a PowerEdge 1600SC, and in order for me to boot from a drive on the adaptec controller, I had to add the a few more fusion driver modules to the initrd as follows:
I am having the same problem with mptbase failing when trying to install Slackware 12.2 on a Dell PowerEdge 1850 (no RAID, single SCSI drive). Neither hugesmp.s nor huge.s work.
It seems that you already have to have an installed system in order to set up and use the generic kernel and initrd. I have to tried to specify generic.s and gensmp.s when the install program asks for a boot kernel, but it says it can't find them.
So the questions is, if you can't set up your system with hugesmp or huge what do you do?
BTW, I tried setting up the machine with Slackware 10.1 and it worked fine.
In my case, I installed an ATA adapter so I could install the system on a spare IDE drive first. But, there are other ways to get a working system where you can build an initrd from. In the case of the PE1600, it couldn't boot from USB, so I couldn't install a minimal system that way.
Another obvious method that comes to mind is to modify your installation CD to include the initrd as required to start up the adapter.
I am having the same problem, but I don't quite understand the solution. I have a Poweredge 1750 and I've tried slackware 10.2, 12.0 (or 12.1 I'm not sure), 12.2 and current. 10.2 does not find the "mptbase: ioc0: WARNING - Unexpected doorbell active" error, but also does not seem to detect the drives. This system has the 3 SCSI drives in it. I tested an install with Ubuntu, and it worked fine (the Fusion MPT SPI Host driver was one version older, 3.04.06) Does someone know an easy way to get around this and install slackware 12.2 or current?
Hi I also have this problem. I have a poweredge 1750 that was running slackware 12.0. I tried to do a clean install of slackware 13 but get stuck at
Unknown Doorbell
Fusion MPT SPI 3.04.07
I see some suggestions to rebuild kernel? Problem is I am a noob and not familiar with this. Also I only have this one machine running slackware right now. I really dont have the knowledge to rebuild the kernel and I've been on google all day now trying to figure what I need to do.
If I need to I will revert to 12.0 but I would prefer to go to 13. Can someone please tell me how to resolve this?
Slackware 12.0 was the only out-of-the-box install that I could get working with the PowerEdge 1750. I did upgrade it to 12.2 at the time by recompiling the kernel, but honestly, as this is running as a small server not a desktop, I'd just keep up on the updates (as I do on my other 1750). If I remember right, I removed unused modules and I may have even built in support for the SCSI controller. If this machine was 64bit capable, I'd try to re-install with Slack64 13.0, but it's not worth the hassle to me. YMMV
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.