SlackwareThis 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.
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.
This is not a problem, just a bit puzzling.
I'm not getting all those:
Code:
kobject_add failed for uhci_hcd with -EEXIST
that occurred with 12.0 using the huge kernel, and which can be avoided by switching to the generic. Boot up is fast enough, everything seems to run OK. I ran Eric's mkinitrd_command_generator.sh, and got different results to what I got with 12.0:
For 12.0:
As this is a different kernel than from 12.0, it's no surprise that a new module appear.
Just put two entries in your /etc/lilo.conf ("generic + initrd" and "Huge") so that if initrd is not adequate, you can fall back to the huge kernel.
Yeah, that's what I was thinking of doing, to see if there's any difference in the boot up messages. The differences were very noticable in 12.0 with huge and generic. But, as it says in CHANGES_AND_HINTS.TXT, those error messages can be ignored. I will make an initrd though, and try the generic kernel.
Just to satisfy my curiosity (killed the cat, but I'm still here (who said "Unfortunately"?)), yesterday when I had the huge, then generic, kernels running, I did:
brianL, interesting, but not terribly significant. Modules built into the kernel are not shown in `lsmod` output, and so though it may appear that the generic kernel is running more modules, this is not actually the case. A better approach would be to start the system up using each kernel, let it sit there for a few minutes, and then run `free` and `top` and see how much RAM is being used and the state of the CPU. That would prove definitively whether or not the generic kernel saves resources over the huge kernel.
Thanks for the explanation of the lsmod findings. I did try htop on both, but the differences in cpu and RAM and swap usage shown by that were very small.
The "tests" I did were just out of curiosity caused by the lack of those error messages, which were so obvious when using the huge kernel in 12.0, I wasn't intending any significant research. It gave me a chance to use lsmod and diff, anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.