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.
|
 |
10-18-2014, 11:36 AM
|
#1
|
|
Member
Registered: Apr 2004
Location: Scotland
Distribution: Slackware
Posts: 218
Rep: 
|
Slackware 14.1 Generic Kernel
Evening guys.
I have just installed Slackware 14.1. Following from This Site i have got as far as Switching to a Generic Kernel once i have done lilo -v and rebooted i can get past lilo but it freezes half way through, i have only managed to get the tail end of the error image Here
Any help appreciated or any help where too look. |
|
|
|
|
10-18-2014, 11:43 AM
|
#2
|
|
Member
Registered: Oct 2010
Location: Bowling Green, KY
Distribution: Slackware
Posts: 288
Rep:
|
So you made the initrd?
I'm not sure why the site still says 'recommended to switch to the generic kernel'... with a modern pc, there is really no need.
|
|
|
|
|
10-18-2014, 12:23 PM
|
#3
|
|
Member
Registered: Dec 2013
Location: Moscow, Russia
Distribution: Slackware, EndeavourOS
Posts: 91
Rep: 
|
What command did you use to create initrd? Did you use a mkinitrd_command_generator.sh script? What are the contents of lilo.conf?
|
|
|
|
|
10-18-2014, 12:53 PM
|
#4
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Quote:
Originally Posted by WhiteWolf1776
So you made the initrd?
I'm not sure why the site still says 'recommended to switch to the generic kernel'... with a modern pc, there is really no need.
|
Without an inird you can not use advanced functionality like LVM or LUKS. And the huge kernel does not boot with an initrd because it is too big.
Eric |
|
|
1 members found this post helpful.
|
|
10-18-2014, 01:07 PM
|
#5
|
|
Member
Registered: Dec 2013
Location: Moscow, Russia
Distribution: Slackware, EndeavourOS
Posts: 91
Rep:
|
Quote:
Originally Posted by Alien Bob
the huge kernel does not boot with an initrd because it is too big.
|
Strange. Two weeks ago I booted my system without a problem using a huge kernel and an initrd for encrypted LVM support. |
|
|
|
|
10-18-2014, 01:46 PM
|
#6
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Good for you. I should rephrase "it used to be impossible to boot a huge kernel with an initrd".
Last time I tried - and failed - was months ago.
Eric
|
|
|
|
|
10-18-2014, 04:40 PM
|
#7
|
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
Quote:
Originally Posted by WhiteWolf1776
So you made the initrd?
I'm not sure why the site still says 'recommended to switch to the generic kernel'... with a modern pc, there is really no need.
|
With an Intel video card, you need to switch to the generic kernel and build the 'i915' driver into the initrd to use KMS. The free 'nouveau' and 'radeon' drivers work similarly. Staying with the huge.s kernel and without an initrd means poor video performance in these cases.
Another case for generic+initrd is a software RAID setup, where it's mandatory. |
|
|
|
|
10-19-2014, 04:36 PM
|
#8
|
|
Member
Registered: Apr 2004
Location: Scotland
Distribution: Slackware
Posts: 218
Original Poster
Rep:
|
Im going to mark this thread as solved, i done a stupid thing and forgot to add initrd = /boot/initrd.gz in lilo  silly mistake with me not paying attention cheers for the help guys |
|
|
|
All times are GMT -5. The time now is 12:19 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
|
|
