LinuxQuestions.org
Visit Jeremy's Blog.
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 03-26-2009, 05:18 PM   #1
songangel
Member
 
Registered: Mar 2009
Location: West Point, GA
Distribution: Arch
Posts: 42

Rep: Reputation: 16
SOLVED: Generic SMP kernel with no initrd?


I have just finished reading all the posts in the HAL with slack 12 sticky and found it extremely helpful. I am running a custom version of the generic SMP kernel using an initrd.gz to load my ext2 filesystem module and HAL works great.

My question is this:

Is it possible to compile the necessary filesystem support into this kernel directly to avoid using the initrd.gz? When I was creating the config file I didn't see an option for ext2 (don't ask me why I chose this partition type) and I don't want to go back to the huge kernel and lose HAL functionality.

On the other hand, is it possible to change the partition type to ext3 without losing data?

Thanks in advance and HI PAPPY_MCFAE if you're out there. I really enjoyed reading your posts.

Last edited by songangel; 03-28-2009 at 11:48 AM. Reason: Problem solved
 
Old 03-26-2009, 05:37 PM   #2
manwithaplan
Member
 
Registered: Nov 2008
Location: ~/
Distribution: Arch || Sidux
Posts: 393

Rep: Reputation: 45
I haven't had the experience with Slack, but I have compiled many kernels.

And I never use a initrd. I compile filesystem support directly into the kernel and install any modules separately.

Have you tried any git sources from kernel.org?

My kernel compiles are quick and completely custom to my hardware. I might be totally wrong with what your asking, but it seems in your case, its a matter of creating and compiling a new kernel.

Quote:
e.g.

# cd /usr/src/linux

# make oldconfig

# make menuconfig #Here under filesystems add the filesystem support

# make -j3 && make modules_install

# cp arch/(ARCH x86 or x86_64)/boot/bzimage /boot/whatevernameyouwant

Last edited by manwithaplan; 03-26-2009 at 05:42 PM.
 
Old 03-26-2009, 05:43 PM   #3
songangel
Member
 
Registered: Mar 2009
Location: West Point, GA
Distribution: Arch
Posts: 42

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by manwithaplan View Post
I haven't had the experience with Slack, but I have compiled many kernels.

And I never use a initrd. I compile filesystem support directly into the kernel and install any modules separately.

Have you tried any git sources from kernel.org?

My kernel compiles are quick and completely custom to my hardware. I might be totally wrong with what your asking, but it seems in your case, its a matter of creating and compiling a new kernel.
Thanks for the response but the problem I had was that I didn't see an option to compile the ext2 filesystem into the kernel. Again, I am using a customized version of the generic SMP kernel from the slack CD.

It almost seems that I have to choose between the generic kernel to have HAL but having to use an initrd, or the huge kernel as a base with no initrd and no HAL support.

Last edited by songangel; 03-26-2009 at 05:45 PM.
 
Old 03-26-2009, 05:47 PM   #4
General Failure
Member
 
Registered: Jan 2007
Location: Germany
Distribution: Slackware 13.37
Posts: 384

Rep: Reputation: 34
It's the first option in the File systems menu entry in 'make menuconfig'. It's called "Second extended fs support".
 
Old 03-26-2009, 05:47 PM   #5
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,042

Rep: Reputation: 977Reputation: 977Reputation: 977Reputation: 977Reputation: 977Reputation: 977Reputation: 977Reputation: 977
The configure option for ext2 is the first in the "File systems" sub-menu if you "make menuconfig", it's called "Second extended fs support". Of course you can choose to have it built-in the kernel.

If you prefer "make xconfig", the same apply: highlight "File systems", it's the first option again. Don't go in one of the sub-directories of the sub-tree, it's at the root of it.

EDIT Screenshots added to make it more clear.
Attached Images
File Type: png xconfig.png (100.6 KB, 8 views)
File Type: png menuconfig.png (15.4 KB, 9 views)

Last edited by Didier Spaier; 03-26-2009 at 05:55 PM.
 
Old 03-26-2009, 05:49 PM   #6
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 12,131

Rep: Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987
Yes you can select ext2 for buildt-in; try this to see you current selections
Code:
grep -iE 'ext[[:digit:]]_' <your config file>
And yes you can convert back and forward (on the fly) between ext2 and 3.
 
Old 03-26-2009, 05:49 PM   #7
manwithaplan
Member
 
Registered: Nov 2008
Location: ~/
Distribution: Arch || Sidux
Posts: 393

Rep: Reputation: 45
I'm saying is customize your own.... download the source and create your own... and leave the old kernel in place and troubleshoot if there are any problems by using grub.

In make menuconfig you'll see under

Quote:
File systems -->
<> Second extended fs support
put an asterisks in there ... and re-compile

Better yet and get your own sources and compile a new kernel and symlink the source when fully tested
 
Old 03-26-2009, 05:53 PM   #8
songangel
Member
 
Registered: Mar 2009
Location: West Point, GA
Distribution: Arch
Posts: 42

Original Poster
Rep: Reputation: 16
Thanks!

Thanks everyone for the great responses. I probably just missed it when running make xconfig. I haven't compiled too many kernels so I appreciate the responses.

I will give it a shot when I get home tonight.
 
Old 03-26-2009, 06:12 PM   #9
manwithaplan
Member
 
Registered: Nov 2008
Location: ~/
Distribution: Arch || Sidux
Posts: 393

Rep: Reputation: 45
quick posters on this one... before I could repost your answers where there. Though compiling your own kernel and avoiding unnecessary modules, will help with a faster boot and not having to worry about a initrd.gz file.
 
  


Reply

Tags
hal


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
Atheros wireless does not work with MadWifi and generic SMP kernel (12.2) Nylex Slackware 10 01-04-2009 01:46 AM
generic-smp kernel doesn't boot in 12.2 samac Slackware 7 12-12-2008 12:01 PM
DMA not working slackware 12.1 Generic Stock SMP kernel duryodhan Slackware 8 09-18-2008 12:54 PM
ndiswrapper and generic smp kernel Bazzaah Slackware 13 05-17-2008 02:31 AM
smp oops in kernel 2.6.20-16-generic anirudhvij Linux - Kernel 0 08-19-2007 06:02 AM


All times are GMT -5. The time now is 10:30 PM.

Main Menu
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