LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices



Reply
 
Search this Thread
Old 12-19-2012, 02:49 PM   #1
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,616

Rep: Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585
Kernelk Config woes w/slackware & SSD


This is the SSD
http://www.ebay.ie/itm/261075990495?

I have kernel 3.7.1 and I can't get a boot. Here's the lilo.conf boot choices
Quote:
image=/boot/vmlinuz-3.7.1-dec root=/dev/sda3
label=Slackware
image=/boot/vmlinuz-huge-3.2.29 root=/dev/sda3
label=huge.s
3.2.29 boots, 3.7.1 doesn't. The boot error reads
Quote:
EFI Variables Facility 0.00 2004-May-17
Key type dns resolver registered
Registered taskstats version 1
hd: no drives specified - use hd=cyl,head,sectors on kernel command line
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Bios EDD facility v0.16 2004-Jun-25, 1 devices found
VFS: Cannot open root device "803" or unknown block (8,3); error -6
Please append a correct "root=" partition; here are the available partitions:
Kernel Panic - not syncing VFS: Unable to mount root fs on unknown-block(8,3)
The box is a Samsung 350V - Intel Panther Point (HM76?) chipset.

It looks like there's something fairly fundamental wrong. It's obviously not finding the disk. The kernel config is so massive these days it's hard for a luser to be sure he has everything. I obviously don't. What I found online was to enable AHCI in the bios and I did that. No dice.

Any pointers - even a submenu would be good?
 
Old 12-19-2012, 03:29 PM   #2
whizje
Member
 
Registered: Sep 2008
Location: The Netherlands
Distribution: Slackware64 current
Posts: 583

Rep: Reputation: 129Reputation: 129
In linuxdocs is a clear howto http://docs.slackware.com/howtos:sla...kernelbuilding.
 
1 members found this post helpful.
Old 12-19-2012, 04:15 PM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,652
Blog Entries: 2

Rep: Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095
Seems to me that you have disabled something you need.
My tip:
Use the config of the 3.6 generic kernel as a starting point, use make oldconfig to generate a valid config file.
Then compile that kernel and test if it boots (don't forget to generate an initrd for that kernel with the modules you need).
If it works simply use that kernel or use it as starting point for further trimming. If you decide to trim further at first disable all things that are not needed for sure (like floppy support or similar things). Make notes what you change, so that troubleshooting is easier. Compile and test again.
If you don't want to use an initrd enable the drivers you need (disk controller, AHCI support should be sufficient for you, and filesystems). Compile and test again.
And so on.
 
1 members found this post helpful.
Old 12-20-2012, 05:12 AM   #4
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,616

Original Poster
Rep: Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585
I should have been clearer. I started with 3.2.29(Known working on an AMD box), went through it after a make oldconfig removing AMD options and adding INTEL ones (This is an intel based box). Because of UEFI issues I never actually booted 3.6.10. But I have the working kernel config from 3.2.29 with Slackware's huge kernel so I can use that

Probably a more direct route would be
take 3.2.29 (Known working) and make oldconfig. That's an hour choosing, but it's safer.
 
Old 12-20-2012, 05:58 AM   #5
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,210

Rep: Reputation: 55
Pat has configs for newer kernels in testing.
 
1 members found this post helpful.
Old 12-20-2012, 05:58 AM   #6
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,210

Rep: Reputation: 55
Pat has configs for newer kernels in testing.
 
1 members found this post helpful.
Old 12-20-2012, 03:14 PM   #7
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,616

Original Poster
Rep: Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585
Quote:
Probably a more direct route would be
take 3.2.29 (Known working) and make oldconfig. That's an hour choosing, but it's safer.
I don't go for Pat's configs too much. They have the basics right, but at some point he does a make allmodconfig or the like and I like a lightweight kernel - old habits. Thanks though.

I got there, and I'm sorted. But the kernel config has become a real nightmare if you don't know all about everything they're trying out. And who does?

Now to try ans sort this crazy touchpad. If my fingers are cold the mouse doesn't move; and if i Blink at it, it jumps the page or sends half an email or buys at an auction(!) or the like.
 
Old 12-20-2012, 03:25 PM   #8
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,616

Original Poster
Rep: Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585Reputation: 585
Quote:
Originally Posted by whizje View Post
Thanks for the link. I'm sorted and running on 3.7.1.

I have a better chance than a lot of users at understanding this because of my background, but it's things like CEPH, Netlink, Various Namespaces, ciphers and the like which are new concepts hacked out by gigabytes of debate on lmkl and numerous patches. On a new box, it's getting tough to work up your config. Even simple old usb now has ohci, uhci, ehci, xhci, & vhci drivers at least. As this is a new box, how do I find the hardware? I ran lsusb, lspci, and sensors-detect as appropriate. I wanted to find a driver for the Sony Microvault card reader in the box - it's read only, but other sd card readers are rw on the same card. SSD options are all over the place.
 
Old 12-20-2012, 05:07 PM   #9
whizje
Member
 
Registered: Sep 2008
Location: The Netherlands
Distribution: Slackware64 current
Posts: 583

Rep: Reputation: 129Reputation: 129
What helps is determining which modules are loaded when you use 3.2.29 with lsmod.
And make sure those modules are also selected in your new config.
 
  


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
Slackware on an SSD Jeebizz Slackware 59 07-21-2012 07:10 AM
[SOLVED] Slackware 13.37 Config issues (wirless & compiling) tysteven Slackware 8 10-17-2011 08:54 PM
Sackware64 -current & EXT4 & SSD mlpa Slackware 15 09-12-2010 03:20 PM
ssd and Slackware hemp4fuel Slackware 5 02-26-2010 12:21 PM
zsnes && logitech dual action gamepad && dpad woes John5788 Linux - Games 5 10-29-2008 10:56 PM


All times are GMT -5. The time now is 07:07 AM.

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