LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 02-26-2005, 07:36 AM   #46
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30

Quote:
Originally posted by auditek747
Heck of thing you guys are doing here.
I'll be building one of these kernels in a couple weeks.
I can't wait !

Thanks to all involved.
Thank you
 
Old 02-26-2005, 07:37 AM   #47
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by samac
This is the first time I had seen this, my /etc/modprobe.conf now looks much less sparce.

Thanks

Samac
semac, not sure if it is a wise thing to use this if you already have the /etc/modprobe.conf file, or if it's not empty. it is generated on kernel only and will not have any additional driver modifications that you may have added...
 
Old 02-26-2005, 10:37 AM   #48
grx
LQ Newbie
 
Registered: Feb 2005
Posts: 15

Rep: Reputation: 0
.
Quote:
Originally posted by acidjuice you shouldn't leave the old .config as it points to the old kernel, and the driver might therefore not work. i think it actually points to /usr/src/.config. i personally have modified it to point at /usr/src/config instead (which is one of the symlinks in the optional part of the guide). not sure if this is the best way to go, though.

Agreed--but the nvidia installer gave me an error and would not compile a kernel interface until I copied /boot/config-2.6.10 back to /usr/src/.config. (See the thread "nvidia install error" where we worked out the problem.) I don't know if any other programs would ever need to see this or not.

Looking back at the guide, the optional step doesn't appear to include making a symlink to /usr/src/config. It does have you make one for /boot/config, however. I haven't tried to see if a /usr/src/config link would work with the nvidia installer as opposed to /usr/src/.config.

Also--how different would this guide have to be for other distributions? It seemed to work smoothly enough to me that anyone could follow it step by step and get a new kernel compiled. Maybe people outside the Slackware community could benefit from such a thing. (Admittedly, I haven't checked to see if they exist in other places as well or not.)


Last edited by grx; 02-26-2005 at 10:48 AM.
 
Old 02-26-2005, 11:18 AM   #49
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 138Reputation: 138
Quote:
not sure if it is a wise thing to use this if you already have the /etc/modprobe.conf file, or if it's not empty. it is generated on kernel only and will not have any additional driver modifications that you may have added...
I made sure all the items in the old one were included in the new one, so no harm done.

Thanks for the concern though.

Samac
 
Old 02-26-2005, 01:55 PM   #50
comprookie2000
Gentoo Developer
 
Registered: Feb 2004
Location: Fort Lauderdale FL.
Distribution: Gentoo
Posts: 3,291
Blog Entries: 5

Rep: Reputation: 58
Another way is to just do;
Code:
make
make modules_install
make install
the new kernel will be /boot/vmlinuz
 
Old 02-28-2005, 04:59 AM   #51
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
thank you all

this guide has now been submitted to the HOWTO section of the site.

thank you all for the inputs,

cheers,

aj.
 
Old 02-28-2005, 06:23 AM   #52
Darin
Senior Member
 
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024

Rep: Reputation: 45
Great guide, it looks very similar to the way I've been compiling 2.4.x kernels in Slack for what seems like forever.

You have a code line: /boot# pico /etc/modprobe.conf
It might be simpler to just dump the file to screen using cat /etc/modprobe.conf or even less /etc/modprobe.conf since there is no editing done in that step

For the symlinks and backups in /boot:
I do the same steps you do of renaming the old files and symlinking to the new ones. I see the same thing in "other distros" and assumed there was something besides LILO that used them. Whether or not there are other things need them I don't see much of a reason to leave the steps out of your guide. Things like this will likely be followed strictly by the inexperienced user and will do no harm, while the kernel vetrans may still use the guide but can safely chose to skip this step if they wish ;-)

For compiling as root:
OK so Linus says it's a bad idea, there are probably good arguments either way. I think in the strict Linux philosophy we wouldn't run a kernel compile as root, but how many of you do almost nothing as root? For new users IMO, it's likely you will introduce more chance of mistakes by moving stuff around to compile as a user than you would risk by compiling as root.

NVidia drivers and other schtuff that needs to compile against the kernel:
Here is where those symlinks in /boot may be needed, hard to tell. With NVidia drivers I make sure that all of this is in place, most if it is probably overkill but I prefer the shotgun to the scalpel in this case:
- /usr/src/linux symlinks to my currently running kernel's source tree /usr/src/linux-2.x.xx
- System map left in the source tree and a copy placed in /boot by version number, with generic symlink (just like your tutorial)
- .config left in the source tree and a copy placed in /boot by version number, with generic symlink (just like your tutorial)

As a note, you can use the /boot/config as a good starting guide, even using the 2.4.xx one with make newconfig for a 2.6.xx is preferred to starting from scratch although using Patrick's 2.6 configuration is probably the best place to start.

In your SATA section you may be able to word it so it's understandable that whatever bus your boot device is on has to be left in the kernel, not just SATA but for those with SCSI or people who don't understand that they need a non-modularized IDE driver. An interesting note is that RedHat and some other distros use the initrd to have those modules available at boot. That seems so un-Slack and I wouldn't suggest doing it, but it's helpful to know why you have to compile this way in Slackware and not other distros.

Maybe include a list of other things that Slackware needs in the kernel. I know when I was newer to Linux I've unchecked things like devfs and then wondered why it didn't work. This will probably mean some work to find everything, maybe we can start with stuff people have personally left out and had problems with and build from there.
 
Old 03-11-2005, 05:13 PM   #53
auditek747
Member
 
Registered: Feb 2004
Location: Ohio, USA
Distribution: Arch Linux
Posts: 464

Rep: Reputation: 30
Well I tried your guide. (thanks to all)
It took me a couple of trys to get my .config just right,
But I'm up and running fine.
I've got TV, Alsa, Internet, The Works!
Performance is vastly improved over 2.4.x on my
kt600 based board.

I did have to make one change, however.
As "GRX" mentioned I had to copy my /usr/src/.config
instead of moving it, in order to get the NVIDIA driver to build.
(version 6629)
 
Old 03-11-2005, 05:46 PM   #54
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
real glad this was of help.

i posted this as tutorial, but nothing came out... maybe it needs approval. oh well. at least i see that it's still here

cheers,

aj.
 
Old 03-11-2005, 06:16 PM   #55
auditek747
Member
 
Registered: Feb 2004
Location: Ohio, USA
Distribution: Arch Linux
Posts: 464

Rep: Reputation: 30
It's up...

http://www.linuxquestions.org/questi...iewcat&catid=6
 
  


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
Newbie Guide To Compiling A Kernel! DrOzz Linux - General 318 08-20-2008 06:21 AM
I'm interested in compiling a 2.6.x kernel, is this is a decent guide? Erik_the_Red Linux - Newbie 7 08-14-2005 07:03 AM
Kernel compiling guide for newbies... DaOne Slackware 127 04-17-2005 05:20 AM
Guide for snort+mysql+acid at Debian Woody Tredo Debian 1 02-03-2005 10:30 AM
: Kernel compiling guide for newbies Question Anibal Slackware 6 08-01-2003 08:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:50 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
Open Source Consulting | Domain Registration