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.
|
 |
|
04-20-2006, 09:08 AM
|
#16
|
Member
Registered: Dec 2005
Location: UK
Distribution: Slackware 12.1
Posts: 249
Rep:
|
I had similar problems when I first started to build my own Linux kernel.
I tracked the problem down to 'tangled up' symbolic links.
I have learnt my lesson now and avoid having any symlinks if at all possible. Also, when building a new kernel, I never do a 'make install'. I always install the kernel image, system.map and modules manually, then I know exactly what is happening.
Toods.
|
|
|
04-20-2006, 09:18 AM
|
#17
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
To Toods: You can install modules with make install_modules. It doesn't create any symlinks, just copy modules to /lib/modules/kernel-version.
To NNP: Check that your filesystem support is compiled not as module but into the kernel;
Check that you haven't enabled SATA or SCSI disk support (they shouldn't cause problems. but it's better to check), if you have and IDE disk.
Use Slackware 2.6 kernel config and check additional required options. If it works, you can reduce the number of selected options and finally find what was causing kernel panic.
|
|
|
04-20-2006, 11:16 AM
|
#18
|
Member
Registered: Dec 2005
Location: UK
Distribution: Slackware 12.1
Posts: 249
Rep:
|
Quote:
Originally Posted by Alien_Hominid
To Toods: You can install modules with make install_modules----
|
That's good to know. Is 'make install_modules' the same effectively as 'make modules_install'?.
|
|
|
04-20-2006, 01:50 PM
|
#19
|
Member
Registered: Nov 2004
Distribution: Debian/Ubuntu
Posts: 156
Original Poster
Rep:
|
Toods: I think it was a typo, so yes (damn will i feel silly if it wasnt  )
Alien_Hominoid: What do you mean by 'Use Slackware 2.6 kernel config'. Do you mean create a fresh .config file?
Thanks,
NNP
|
|
|
04-20-2006, 02:19 PM
|
#20
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
To Toods: Sorry for very stupid previous post.  It should be make modules_install. My fault. But it works as I said.
To NNP: ftp://ftp.slackware.com/pub/slackwar...est26.s/config.
|
|
|
All times are GMT -5. The time now is 05:53 AM.
|
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
|
|