LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-17-2010, 08:39 PM   #1
ColdSQL
LQ Newbie
 
Registered: May 2010
Distribution: Slackware
Posts: 9

Rep: Reputation: 0
Slackware 13.0 Fusion MPT Kernel Panic


Hi,
I am trying to install slackware 13 on a dell poweredge. However I am getting a kernel panic on the "Fusion MPT 3.04.07" driver. This is preventing the installer from detecting the SCSI hard drives.

I have been able to install sucessfully with 12.0.

Can anyone suggest how to fix this?
 
Old 05-17-2010, 08:44 PM   #2
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,486

Rep: Reputation: 426Reputation: 426Reputation: 426Reputation: 426Reputation: 426
Which image did you select for the installer?
 
Old 05-17-2010, 09:15 PM   #3
ColdSQL
LQ Newbie
 
Registered: May 2010
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: 0
Im not sure I understand what you mean by which image?

I downloaded slackware 13.0 iso and burnt to disk. When I tried to boot from these I got an error that the fusion mpt 3.04.07 driver is not working. Eventually the boot sequence continues to where I can run fdisk but fdisk cannot see the scsi hard drive. The same happens when I try to run setup. The hard drive is not found.

I then downloaded and tried the earlier versions of slackware and only the 12.0 slackware does not have this problem.

I have been able to partially get around this problem by recompiling the install cd kernel hugesmp on another machine and buring a new install cd with this kernel. This did allow me to boot up the installer, run fdisk and install from the cd's. However when I restart I get a kernel panic on loading the fusion mpt driver.

It seems I need to make an initrd but I no longer have easy access to the machine I built the kernel on.

Is there a way that I can take the initrd.img from the install cd and place it on the hard drive? I also cant seem to run the lilo or mkinitrd when I boot up using the slackware cd.
 
Old 05-17-2010, 09:17 PM   #4
ColdSQL
LQ Newbie
 
Registered: May 2010
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: 0
Oh I get what you mean now. I have tried both the huge and hugesmp images that came with the slackware 13.0 cds. I was only able to boot up the setup system when I replaced with the recompiled kernel.
 
Old 05-17-2010, 10:23 PM   #5
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,486

Rep: Reputation: 426Reputation: 426Reputation: 426Reputation: 426Reputation: 426
Oops. I missed that the scsi.s image no longer exists in 13.0. My bad.

Well, if you can boot with the install CD and see all of your drives then it's almost easy to generate an initrd.

First thing is to mount your installation root partition on /mnt. Then you should be able to look at /mnt/etc/fstab to mount the other partitions accordingly. Then run
Code:
chroot /mnt
, which will then allow you to run the mkinitrd command (it will be able to find the kernel modules and binaries that you installed). Make sure to specify the kernel that you want via the "-k" flag as well as checking lilo.conf prior to re-running lilo. (I've converted to grub, myself, so I won't be of much help with lilo.)

Then give the "exit" command to get out of the chroot and reboot. Hopefully, things will work now.
 
1 members found this post helpful.
Old 05-18-2010, 06:18 AM   #6
ColdSQL
LQ Newbie
 
Registered: May 2010
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: 0
Thankyou so much. That was the final piece of the puzzle I needed. Ill give that a try tonight and let you know if it worked.
 
Old 05-18-2010, 09:06 AM   #7
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,486

Rep: Reputation: 426Reputation: 426Reputation: 426Reputation: 426Reputation: 426
Thank Eric Hameleers (also known as Alien Bob) for telling me about using the "chroot /mnt" command. See this too. According to that link, you will have to enter these commands...
Code:
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
mount -o bind /dev /mnt/dev
chroot /mnt
...instead of just "chroot /mnt". The stuff at the link was written for Slackware 12.0, but I believe that it would apply in your case.

Last edited by Richard Cranium; 05-18-2010 at 09:07 AM.
 
Old 05-18-2010, 05:16 PM   #8
ColdSQL
LQ Newbie
 
Registered: May 2010
Distribution: Slackware
Posts: 9

Original Poster
Rep: Reputation: 0
Actually all I needed was the "chroot /mntpoint" command. Once I did that I was able to rebuild the installed kernel and run lilo.

Turns out I did not need to make an initrd after all.

I still have a few problems with the new version but at least now I have a bootable system that I can work with.
 
  


Reply

Tags
scsi, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panic on boot with new SATA drive Slackware 12 kernel: 2.6.21.5 theapodan Linux - Hardware 3 05-18-2009 03:02 PM
What's the difference between MPT fusion and original driver? PhillipHuang Linux - Software 0 12-11-2007 03:37 AM


All times are GMT -5. The time now is 06:50 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration