SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I once changed the smp kernel running in my system by another one in /boot. What I did was to relink /boot/System.map, /boot/vmlinuz and /boot/config. But I don't remember if I did something else. Would that alone be OK.
ok. An according to CHANGES_AND_HINTS.txt I should make an initrd? I mean, if I use a generic kernel? That thing of the two kernels I like it. I'll do it. Another question.
Advanced Linux Sound Architecture - Driver
1) You must have full configured source for the Linux kernel which you
want to use for the ALSA drivers. Note that ALSA drivers are part
of the kernel, so there is necessary to resolve all symbol dependencies
between the used kernel and ALSA driver code. Partly installed kernels
(for example from distributor makers) can be unuseable for this action.
What is the meaning of "full configured source for the Linux kernel"?
Well then, lilo says the ram disk will be loaded above 16M, OK. But what is this token 'large-memory' that can be put in /etc/lilo.conf. I am having trouble booting with a live Linux CD, which is unobjectionable. May it be related to 'large-memory'?
I think your /etc/lilo.conf is still using the huge kernel. You can append "large-memory" to /etc/lilo.conf if you want, but I would just recommend using the smaller, generic kernel in your /etc/lilo.conf instead (and then running lilo).
After reading this link: http://manpages.ubuntu.com/manpages/...lo.conf.5.html it appears that actually large-memory option specifies that your system is new enough to be able to handle the initrd location beyond 15Mb limit. Without it, the Initrd will be put within the first 15Mb. As I haven't had any problems with loading initrd from the first 15Mb never ever then I haven't investigated about the large-memory option. It is just one of many lilo's capabilities and there might be some special cases where it would be necessary. But usually you can live without it.
The 15MB limit was a problem back in the days of 486 CPUs, if I remember correctly, on modern machines that specific option isn't even available in the BIOS settings. Nonetheless, I only had this message when I misconfigured mkinitrd and it bloated the initrd and when I attempted to run Slackware entirely from the initrd. Usually the initrd shouldn't be that large that you get this message.
What was your command to create the initrd?
I must tell you I didn't got any message from lilo about the memory limit. I only read /etc/lilo.conf_example and saw that command (large_memory). I suspected it to be obsolete (not deprecated but of little use, I you explained). The command I issued was
mkinitrd -c -k 3.2.29 -m ext2
where 3.2.29 is my kernel version and ext2 the fs I use in the hard.