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.
If everything works, look what modules your system need and trim your kernel. Why monolithic?
Kernel is already about as trimmed as can be
Monolithic, because I simply don't need modules, and appreciate the better performance of having my drivers compiled in, and as I'm quite security minded, I also prefer not having the possible security risk there.
Ok, you can turn on KMS for radeon. You will get native resolution even in VESA.
Hmm, that's a staging driver, right? I disabled all the experimental stuff. How have you found it? Is it simply a matter of enabling it, and you will be able to choose the correct vga mode?
It is better than the radeonfb driver, and if so how? How does it differ?
What about usb (for instance)? Do you build:
a) every HCI variation in;
b) just the ones your laptop usb needs?
If a) - it 's against the idea of small, fast kernel (you load drivers you don't need).
If b) - you miss the chance to have various usb devices you may meet in the future working.
What about usb (for instance)? Do you build:
a) every HCI variation in;
b) just the ones your laptop usb needs?
If a) - it 's against the idea of small, fast kernel (you load drivers you don't need).
If b) - you miss the chance to have various usb devices you may meet in the future working.
Just curious
Why would I need to compile in every HCI variation? USB 2.0 is just EHCI, and to add in UHCI and OHCI for compatability is hardly a burden. Unless I am unsure of what you mean?
HID devices are generic, and don't change to much, and honestly, what devices am I going to need on my laptop? USB keys are the only thing really, and that is easy enough. I'm not worried about things like joysticks and such.
At the moment, scanners and cameras and such won't work, but it would not be difficult, or violate b) to add in further generic support.
I don't use slackware for a replacement for Windows, or as a desktop system. I watch movies and play music under it while doing stuff, but still prefer Windows for most desktop stuff. I use slack for my programming work , research, pen testing, virtual machines, all of this sort of fun stuff.
Having a very small and optimized kernel, without modules(which have some performance and security issues) makes far more sense for my configuration
Example:
1. You run out of usb slots
2. You take first usb hub available
3. Unfortunately, it's OHCI.
So - do you have ohci support built-in "just in case" (IMO negation of fast'n'small kernel idea) or leave it as a module (kernel stays small, module loads only when you need it) ?
Seems like I'm in kernelosophical mood this morning
Example:
1. You run out of usb slots
2. You take first usb hub available
3. Unfortunately, it's OHCI.
So - do you have ohci support built-in "just in case" (IMO negation of fast'n'small kernel idea) or leave it as a module (kernel stays small, module loads only when you need it) ?
Seems like I'm in kernelosophical mood this morning
Well, that is quite an unlikely scenario. I have never run out of slots, don't own and have no intention of buying a hub, nor know anyone who would own a hub.
Even so, enabling ohci support, if you felt it was needed, even only in some cases, would still be small enough that it would not negate the fast'n'small kernel philosphy, and is preferable to having many modules that might be needed just-in-case, and the security and performance concerns that go along with that decision.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.