LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 11-26-2007, 09:20 AM   #16
bjdodo
Member
 
Registered: Dec 2006
Location: Ireland
Distribution: Slackware 12, kubuntu
Posts: 35

Original Poster
Rep: Reputation: 16

Hi Gary,

Thanks for the answer :-) Just one comment:

> As PV states, you should try to use one of the smp kernels if possible.
I have read this text, but I had a problem that I had to fix: my computer does not boot with the SMP kernel on the CD, that is why I have started this whole thing (I think I have this issue: http://lkml.org/lkml/2007/8/3/129 I also have a 32 bit system installed on a 64x2 system). I have no idea if this is the only solution for the problem, but I am able to boot the SMP .config file (on the install dvd) with kernel 2.6.20.19. Therefore if there is no other way, anyone having this configuration has to install a different kernel version if he wants to use both cores of his processor. As other way all I can think of is playing with the settings in BIOS, but I ran out of possible combinations :-) probably I missed something, but I have tried to help the situation in that way without success.

About the boot time, I am serious that I could reduce the kernel extract time (while the dots are displayed) on my computer by 20 percent. It used to be over a minute, now it is less than that. All in all, I think rebuilding the kernel was a very useful experience for me, I have learnt a lot about many things.

Thanks for the links, I will check them out!!!

Regards,
Jozsi
 
Old 11-26-2007, 09:45 AM   #17
bjdodo
Member
 
Registered: Dec 2006
Location: Ireland
Distribution: Slackware 12, kubuntu
Posts: 35

Original Poster
Rep: Reputation: 16
Hi Gary,

May I ask one question? I have read the readme file about initrd, but I do not understand how it would speed up the boot process in my case.

The only FS I built statically was the FS that is on my boot partition, the rest is loaded as modules. This has to be loaded anyway.

I see a reason if there was a kernel with minimum statically linked stuff and with everything else built as module (including all FS modules), then instead of modifying the .config file and rebuilding the kernel I could create an initrd - this seems simpler and quicker, I understand this. But I could not find such a kernel on the Slackware 12 CD (but I have to admit I have no idea what the speakup kernel is good for, but I think I have found this info once and I have decided that it is not for me) I think probably in previous Slackware versions the generic kernels were like this? But I do not understand how it would achieve quicker load time than building the necessary modules statically to the kernel and removing all the unnecessary things otherwise, or turning the rest into modules.

Thank you, and sorry if the question is very stupid :-))

Regards,
Jozsi
 
Old 11-26-2007, 12:03 PM   #18
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,699
Blog Entries: 37

Rep: Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897
Quote:
Originally Posted by bjdodo View Post
Hi Gary,

Thanks for the answer :-) Just one comment:

> As PV states, you should try to use one of the smp kernels if possible.
I have read this text, but I had a problem that I had to fix: my computer does not boot with the SMP kernel on the CD, that is why I have started this whole thing (I think I have this issue: http://lkml.org/lkml/2007/8/3/129 I also have a 32 bit system installed on a 64x2 system). I have no idea if this is the only solution for the problem, but I am able to boot the SMP .config file (on the install dvd) with kernel 2.6.20.19. Therefore if there is no other way, anyone having this configuration has to install a different kernel version if he wants to use both cores of his processor. As other way all I can think of is playing with the settings in BIOS, but I ran out of possible combinations :-) probably I missed something, but I have tried to help the situation in that way without success.

About the boot time, I am serious that I could reduce the kernel extract time (while the dots are displayed) on my computer by 20 percent. It used to be over a minute, now it is less than that. All in all, I think rebuilding the kernel was a very useful experience for me, I have learnt a lot about many things.

Thanks for the links, I will check them out!!!

Regards,
Jozsi
Hi,

If you downloaded the iso for the cd(s)/dvd did you check the md5sum?

If you did downloaded the cd/dvd iso then be sure to check the md5sum for the original iso. From the cli;

Code:
~#cd /downloadisolocation      #cdromiso.iso cdromiso.md5 

~#md5sum -c cdromiso.md5       #substitute the correct name to check
This will check the download iso with the known md5sum that you also get with the iso.

You could have a bad burn, to check the cd/dvd with the original iso md5, use this CdromMd5sumsAfterBurning.

A little work on your part to check the cd/dvd to original iso but worth the effort.

As for the dots, by compiling, you may be omitting things that could be effected by the load. The kernel it self is loaded into the memory then the init is started. As I stated before you could pickup some time by using a initrd for the file system. Also you should have the compact option in the 'lilo.conf' global section, this will affect the sector read.
 
Old 11-26-2007, 12:44 PM   #19
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,699
Blog Entries: 37

Rep: Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897
Quote:
Originally Posted by bjdodo View Post
Hi Gary,

May I ask one question? I have read the readme file about initrd, but I do not understand how it would speed up the boot process in my case.

The only FS I built statically was the FS that is on my boot partition, the rest is loaded as modules. This has to be loaded anyway.

I see a reason if there was a kernel with minimum statically linked stuff and with everything else built as module (including all FS modules), then instead of modifying the .config file and rebuilding the kernel I could create an initrd - this seems simpler and quicker, I understand this. But I could not find such a kernel on the Slackware 12 CD (but I have to admit I have no idea what the speakup kernel is good for, but I think I have found this info once and I have decided that it is not for me) I think probably in previous Slackware versions the generic kernels were like this? But I do not understand how it would achieve quicker load time than building the necessary modules statically to the kernel and removing all the unnecessary things otherwise, or turning the rest into modules.

Thank you, and sorry if the question is very stupid :-))

Regards,
Jozsi
Hi,

As I stated it will just speed up the file system. When you use the initrd, then load and structure of the handler for the filesystem will expedite. I would suggest that you look at 'Using the initial RAM disk (initrd)'. A little dated but worth the read for understanding the initrd along with the filesystem.

You are mistaken about the the static vs dynamic module/driver usage. The kernel is interrupt driven from a device table. Once the device is initiated it doesn't matter if it is static or a dynamic module.

A lot of people make the mistake that by trimming the kernel it would speed things up. Not so! Just the kernel load time. After the kernel is loaded and once the device tables are initialized then the modules(s) are installed if needed along with any associative modules for the device(s) if not static to the kernel.

As an example whenever you do a modprobe for a device the module(s) are loaded. The kernel then performs the necessary actions for said device.

Linux Device Drivers, 2nd Edition and Linux Device Drivers, Third Edition are two good kernel references. The 2nd edit covers the 2.4 kernel while the 3rd covers the 2.6 kernel.

Another would be the 'SlackwareŽ rc init tour'. 'This document is guided tour through the SlackwareŽ init process, guided by the scripts and man pages.'

No such thing as a stupid question!
 
Old 11-27-2007, 05:52 AM   #20
bjdodo
Member
 
Registered: Dec 2006
Location: Ireland
Distribution: Slackware 12, kubuntu
Posts: 35

Original Poster
Rep: Reputation: 16
Hi Gary

Kernel bug:

> If you downloaded the iso for the cd(s)/dvd did you check the md5sum?
Yes, and it is ok. Also, I have built kernels newer than 2.6.21.5 with the same config file that hugeSMP was built with and the same problem was occurring. Someone who seems to be a regular kernel tester was complaining about this issue, so this issue has most probably become an official bug from kernel 2.6.21.x, and I have no idea if it has been fixed. You can find the link to this complaint in my previous posts. This issue is surely there with some configurations. I have no idea if I could have solved it in any other ways, but I am happy because I have solved it by building an older version of the kernel.

Boot time, dots appearing:
Compact lilo was the solution. I was always thinking about trying it, I was just not "brave" enough to try it before, because of the comment in lilo.conf saying that it does not work on all systems. But since you have suggested it, I took a deep breath :-) and tried it, and it is working amazingly quick now.

Thanks a lot for all, I am happy to have Slackware on my laptop :-))

Best Regards,
Jozsi
 
Old 11-27-2007, 06:49 AM   #21
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,699
Blog Entries: 37

Rep: Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897
Hi,

Glad to see that you have a beautiful solution to your journey into the world of Slackware Linux.

Happy to help!

Especially when someone is working to enhance their understanding in order to complete the journey.
 
  


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
understanding kernel .config file (for kernel compilation) sudhirkumar Linux - General 2 09-07-2007 06:55 PM
Can't run kernel config after APT kernel install rollo Debian 9 04-12-2006 05:06 PM
INFO: creating a special secured kernel (grsecurity kernel patch) w sysctl config markus1982 Linux - Security 0 05-25-2003 05:29 AM
I lost rmed my kernel config file. Anyway to create one from the kernel? severedhead Linux - Software 3 07-12-2002 07:54 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

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