Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
|
05-24-2006, 12:18 PM
|
#16
|
Member
Registered: Sep 2003
Distribution: Arch
Posts: 89
Original Poster
Rep:
|
Ok thanks i guess thats the best thing to do, so to do it correctly do I need to include full ext3 support as a module rather than built in?
My main hard drive has 2 partitions ext3 and a linux swap.
This is a screeshot of what i compiled in to the kernel with regards to the file system:
http://www.x-rev.net/fs.jpg
Thanks,
Jck
Last edited by tntcoder; 05-24-2006 at 12:50 PM.
|
|
|
05-24-2006, 02:50 PM
|
#17
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
General rule of thumb:
Include as 'y' the filesytems you are using, not as module, because the kernel will need them long before modules get loaded.
|
|
|
05-25-2006, 02:49 AM
|
#18
|
Member
Registered: Oct 2005
Location: Australia
Distribution: slackware 12.1
Posts: 753
Rep:
|
yes you must compile all the filesystem modules your system will use as built-in (by pressing 'Y') and all others as modules (by pressing 'M'). and as cwwilson721 pointed out your system will be loading your filesystem long before your system probes and loads other neccessary modules hence you shouldn't or can't compile your kernel with essential filesystem options as loadable modules and expect it to work.
|
|
|
05-25-2006, 03:49 AM
|
#19
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
Well, you can, but you have to use 'initrd', which to me, is kind of a kludge. If you compile right, you don't need it.
But if you want to look into it, check out /boot/README.initrd for how to use it.
|
|
|
05-25-2006, 01:50 PM
|
#20
|
Senior Member
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,526
Rep:
|
These exact error messages occurred for me when I did a recent kernel compile. The solution for me was to recompile using the correct SATA driver (I had thought my SATA chip was Silicon Image when in fact I should chosen nVidia.) I dont know if this will help, but it worked for me.
Bob
|
|
|
All times are GMT -5. The time now is 12:14 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|