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 04-13-2009, 06:14 PM   #16
joutlancpa
Member
 
Registered: Apr 2009
Location: Orlando, FL
Distribution: Scientific Linux 6 x64
Posts: 211
Blog Entries: 1

Rep: Reputation: 31

I have a new install, and new to Slackware....is there a current guide somewhere to tell me how to install a generic kernel? I think I'm at the point now I'd to tackle that one... thanks
 
Old 04-13-2009, 06:55 PM   #17
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,145
Blog Entries: 52

Rep: Reputation: Disabled
Get this script and run it, it will give you a suitable command to run to create an .initrd:

http://www.slackware.com/~alien/tool...d_generator.sh

Then edit your lilo.conf (example in my earlier post), run lilo, and that's it. Pretty easy.
 
Old 04-13-2009, 07:21 PM   #18
joutlancpa
Member
 
Registered: Apr 2009
Location: Orlando, FL
Distribution: Scientific Linux 6 x64
Posts: 211
Blog Entries: 1

Rep: Reputation: 31
Quote:
Originally Posted by brianL View Post
Get this script and run it, it will give you a suitable command to run to create an .initrd:

http://www.slackware.com/~alien/tool...d_generator.sh

Then edit your lilo.conf (example in my earlier post), run lilo, and that's it. Pretty easy.
here is my uname -a output...am I already using a generic kernel?

bash-3.1$ uname -r
2.6.27.7-smp
bash-3.1$ uname -a
Linux m4400 2.6.27.7-smp #2 SMP Thu Nov 20 22:32:43 CST 2008 i686 Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz GenuineIntel GNU/Linux
bash-3.1$
 
Old 04-13-2009, 07:42 PM   #19
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
here is my uname -a output...am I already using a generic kernel?
You will not automatically be running the generic kernel. Besides - you have to create an initial ram disk and rerun lilo (after having edited /etc/lilo.conf). There is instructions in /boot/README.initrd to help creating the initrd. Plus there's been instructions in this thread. Personally I think the main thing is to keep the huge kernel in case something goes wrong.
 
Old 04-14-2009, 07:30 AM   #20
mcnalu
Member
 
Registered: Dec 2006
Location: Glasgow, UK
Distribution: Slackware 13.37 and 13.1
Posts: 398

Rep: Reputation: 64
On my last laptop I did what was recommended and switched to the generic kernel after the install was completed.

On my current laptop I'm still running with huge. Why? Because I completely forgot to make the switch!!!

But, like samac I am wondering if there's a compelling reason for me to switch to the generic one given that I've had many happy months of intensive day-to-day use with the huge kernel.

Doesn't PV say that there's no real reason why you can't use huge day-to-day?

Last edited by mcnalu; 04-14-2009 at 07:31 AM. Reason: typo
 
Old 04-14-2009, 07:41 AM   #21
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,145
Blog Entries: 52

Rep: Reputation: Disabled
Apparently there's no real need to switch to the generic kernel. From ANNOUNCE.12_2:
Quote:
There are two kinds of kernels in Slackware -- the huge kernels, which
contain support for just about every driver in the Linux kernel. These are
primarily intended to be used for installation, but there's no real reason
that you couldn't continue to run them after you have installed.
 
Old 04-14-2009, 09:08 AM   #22
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by niels.horn View Post
I leave the "vmlinuz" link alone, as it always comes back after an update of the kernel from -current or a new release.

The generic and -custom (compiled kernel) I add to the lilo menu, with the -custom as a default. The huge kernel stays there, in case I mess up something, so I don't need to find a bootable CD.
Exactly as I do. Install the huge-smp kernel, compile my own as -$CPU. I maintain a universal config for all of our machines. Luckily they are all Intel chipsets, and only 3 AMD/nVidia combos. This makes it easy to just change the CPU type from K8 to Core2, to PIII, what ever, and tick the correct libata option from module to built in.


Quote:
Originally Posted by samac View Post
I'm still at a loss. PV says that we should use the generic kernel, but it seems that we have to take this on faith, why should we not use the hugesmp.s kernel?

Just to clarify, I am using the generic kernel, I would just like to know for curiosities sake.

samac
The huge kernel has everything compiled in. On our AMD/nVidia systems, the huge kernel is using both libata and the older IDE/PATA drivers. This has caused issues for me between the IDE bus, add on Promise IDE cards, and SATA bus. Not errors, just confusion.

Other people have reported issues with their add in SCSI cards. If certain drivers are loaded they will conflict.

The huge kernel also takes quite a bit longer to load

If you don't have module conflicts with your hardware, and don't mind the slightly longer load times, the huge kernels can still be used.
 
Old 04-14-2009, 09:15 AM   #23
mcnalu
Member
 
Registered: Dec 2006
Location: Glasgow, UK
Distribution: Slackware 13.37 and 13.1
Posts: 398

Rep: Reputation: 64
Quote:
The huge kernel has everything compiled in. On our AMD/nVidia systems, the huge kernel is using both libata and the older IDE/PATA drivers. This has caused issues for me between the IDE bus, add on Promise IDE cards, and SATA bus. Not errors, just confusion.

Other people have reported issues with their add in SCSI cards. If certain drivers are loaded they will conflict.
Could this be why my asus eee pc 1000h's 160gb sata disk shows up as hda instead of sda unless I add append=" hda=noprobe" in lilo.conf?

If so, looks like I may have a good reason to switch to generic
 
Old 04-14-2009, 11:34 AM   #24
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.1 64-bit with multilib
Posts: 2,092

Rep: Reputation: 222Reputation: 222Reputation: 222
It was mostly out of sheer laziness is why I kept using the huge kernels for so long, until about a year ago when I decided to finally switch. Since then I noticed an improvement in performance on my ancient AMD desktop. Faster boot ups, and less memory usage.
 
Old 04-14-2009, 11:56 PM   #25
joutlancpa
Member
 
Registered: Apr 2009
Location: Orlando, FL
Distribution: Scientific Linux 6 x64
Posts: 211
Blog Entries: 1

Rep: Reputation: 31
Quote:
Originally Posted by brianL View Post
Get this script and run it, it will give you a suitable command to run to create an .initrd:

http://www.slackware.com/~alien/tool...d_generator.sh

Then edit your lilo.conf (example in my earlier post), run lilo, and that's it. Pretty easy.
I get a permission denied running that script...wonder why? probably me thanks edit: I tried to run it as root. I'm a newb...you're probably gonna need to spell it out for me if you could be so kind...I'm trying to switch kernels, and have no clue. I think that huge kernel is hosing my usb in VB somehow with some usb devices working, some not.

Maybe I'd better start a new thread....thanks

Last edited by joutlancpa; 04-15-2009 at 12:16 AM.
 
Old 04-15-2009, 05:04 AM   #26
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,145
Blog Entries: 52

Rep: Reputation: Disabled
See your new thread.
 
  


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
Generic vs Huge kernel in Slack 12 techyranger Slackware 4 01-23-2008 02:30 PM
slack 12, switch to generic kernel from huge kernel, using grub? jaguarrh Slackware 8 09-19-2007 07:29 AM
GART TLB error generic level generic Clydesdale Linux - Software 1 08-13-2007 07:47 PM
GART TLB error generic level generic Clydesdale Linux - Hardware 0 08-13-2007 07:18 PM
Switch from huge-smp-2.6.21.5 to generic-2.6.21.5 tronayne Slackware 1 07-30-2007 09:34 AM


All times are GMT -5. The time now is 11:13 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