LinuxQuestions.org
Review your favorite Linux distribution.
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 02-15-2012, 09:31 AM   #1
Sum1
Member
 
Registered: Jul 2007
Distribution: Slackware and Gentoo
Posts: 238

Rep: Reputation: 25
Installed/Recompiled kernel 3.2.2 -- /dev/sda now /dev/hda and kernel panics


Hi Slack Group:

I must have overlooked something very fundamental in recompiling kernel 3.2.2 to remove PAE and cx8 for my VIA 600Mhz mini-itx home server.

The hard drive upon which Slack 13.37 is installed is an EIDE Western Digital 500 gig. drive. Under Slack 13.37 it had two partitions -- /dev/sda1 (swap) and /dev/sda2 (/).

After upgrade to slackware-current, including kernel 3.2.2, the kernel panics on boot stating something about ide-gd and that I need to put one of the recognized partitions (/dev/hda1 and/or /dev/hda2) into the "root =" option of lilo.conf.

I changed the following in lilo.conf:

boot = /dev/hda
root = /dev/hda2
save and exit
and then /sbin/lilo
reboot

Kernel panics again with the same message upon reboot.

I then did this:

boot = /dev/hda2
root = /dev/hda2
save and exit /etc/lilo.conf
and then /sbin/lilo
reboot

Same kernel panic.

lilo doesn't seem to like the (h)da because it states something about not recognizing those partitions when I do /sbin/lilo while chrooted using the Slack 13.37 install dvd. I didn't give it much attention, thinking it had something to do with being chrooted.

How do I get to a bootable kernel 3.2.2 using either /dev/hda or /dev/sda.

Thanks for your help.
 
Old 02-15-2012, 09:34 AM   #2
Sum1
Member
 
Registered: Jul 2007
Distribution: Slackware and Gentoo
Posts: 238

Original Poster
Rep: Reputation: 25
oh for goodness sake, i just realized now after stepping away from it --- i probably need to edit my /etc/fstab.
it probably still has the hard drive partitions stated as /dev/sda1 and /dev/sda2.

i'll check this when i get home tonight.

Last edited by Sum1; 02-15-2012 at 09:38 AM.
 
Old 02-15-2012, 09:38 AM   #3
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad W520
Posts: 4,681

Rep: Reputation: 1240Reputation: 1240Reputation: 1240Reputation: 1240Reputation: 1240Reputation: 1240Reputation: 1240Reputation: 1240Reputation: 1240
Did you try to boot your system from the Slackware installer on the DVD ?

Anyhow, you can run fdisk or cfdisk from the installer and see which partitions are recognized.

PS I didn't see your second message before posting, there likely is the rub.

Last edited by Didier Spaier; 02-15-2012 at 09:43 AM.
 
1 members found this post helpful.
Old 02-15-2012, 09:42 AM   #4
Sum1
Member
 
Registered: Jul 2007
Distribution: Slackware and Gentoo
Posts: 238

Original Poster
Rep: Reputation: 25
Quote:
Originally Posted by Didier Spaier View Post
Anyhow, you can run fdisk or cfdisk from the installer and see which partition are recognized.
Thanks Mr. Spaier, definitely will do.
 
Old 02-16-2012, 05:15 AM   #5
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 1,808

Rep: Reputation: 234Reputation: 234Reputation: 234
Changing the entries in /etc/fstab should fix it.

But what this means is that you've left SCSI support out of your kernel. SCSI support is quite important. Even though your hard drive is IDE and you may not have a SCSI controller in your computer, SCSI support under Linux is a lot more flexible than IDE. We know that your system works with a SCSI driver, because your drive was previously recognised as /dev/sda.

At a minimum, I'd build in SCSI disk support, and enable the MULTI_LUN option. It helps with USB sticks, card readers, etc. You may also need to enable SATA support for your chipset.
 
1 members found this post helpful.
Old 02-16-2012, 12:54 PM   #6
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 242Reputation: 242Reputation: 242
Maybe you had to make an initrd after the kernel upgrade ?
 
Old 02-17-2012, 06:24 AM   #7
Sum1
Member
 
Registered: Jul 2007
Distribution: Slackware and Gentoo
Posts: 238

Original Poster
Rep: Reputation: 25
Thank you all for responding.
Issue resolved.
I had SCSI support built into the kernel.

My first problem was that I had ext3 and ext4 items built as modules.
I then compiled them directly into the kernel.

I believe the next problem was in my effort to insure full EIDE support, I built the now "deprecated" ATA support items into the kernel along with the newer libSATA/PATA items.
When I removed the deprecated items, and compiled the others into the kernel, then my hard drive was recognized again as /dev/sda and all good from there.

Thanks again for your guidance; when you're trying stuff and it won't work, it helps alot to have others' keep your attempts at logical deduction on track. :-)
 
Old 02-17-2012, 06:38 AM   #8
Sum1
Member
 
Registered: Jul 2007
Distribution: Slackware and Gentoo
Posts: 238

Original Poster
Rep: Reputation: 25
sidenote for yuks and historical reference:

When i built this mini-itx box with 600Mhz VIA cpu and 1 gig. RAM, the linux kernel was likely 1/8 - 1/4 of its current size and able to be compiled/built in approx. 2 hours. Now, in 2012, the same box and specs. requires 9 - 9.5 hours for a kernel build. The downtime associated with 3 build attempts equaling 30 hours and 3 days of no home server access has persuaded other household officials to approve acquisition of newer gear.
 
Old 02-17-2012, 07:48 AM   #9
fgcl2k
Member
 
Registered: Jan 2011
Distribution: Slackware 14.1
Posts: 108

Rep: Reputation: 29
Quote:
Originally Posted by Sum1 View Post
sidenote for yuks and historical reference:

When i built this mini-itx box with 600Mhz VIA cpu and 1 gig. RAM, the linux kernel was likely 1/8 - 1/4 of its current size and able to be compiled/built in approx. 2 hours. Now, in 2012, the same box and specs. requires 9 - 9.5 hours for a kernel build. The downtime associated with 3 build attempts equaling 30 hours and 3 days of no home server access has persuaded other household officials to approve acquisition of newer gear.
Software bloat can have positive side effects :-)
 
  


Reply


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
/dev/sda to /dev/hda - Slack 13.37 b0f Linux - Newbie 4 06-07-2011 04:26 PM
[SOLVED] restore systemu form /dev/hda to /dev/sda czezz Linux - Server 1 06-21-2010 06:08 PM
/dev/sda (SATA) devices detected as /dev/hda Please help ayvazyan Linux - Newbie 2 01-23-2010 03:17 AM
Is it /dev/hda or /dev/sda? in opensuse 10.3 BK2 Suse/Novell 3 11-29-2007 09:13 PM
Install lilo on external drive (/dev/sda), then boot as INTERNAL (/dev/hda)? slackware-elf Slackware 3 08-18-2007 05:51 PM


All times are GMT -5. The time now is 01:04 PM.

Main Menu
Advertisement
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