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.
Hi. I'm using Slackware 10.0. The original version came with kernel 2.4.26, and I just finished compiling kernel 2.6.12 and adding to lilo and starting the new slack.
There are a few problems though. I can't remember the exact messages during booting, but the two that caused trouble were:
Something about adding a fast USB device, tried addresses 2, 3, 4 and 5 before it fails and goes to the next task.
And something about using udev dynamic device system or something, that takes ~5 minutes to load.
Anything I can do about this? It's my first kernel compile, so I was a little giving with the stuff that should be loaded in the kernel, and not module, so I might have gone overboard with some things >_<
EDIT: I also have no internet access, and "lsmod" as root returns no modules loaded.
Dont worry, you will recompile a few times before you get it just right....
for starters:
make sure you have the udev package installed, and that you
set the options in
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
also make sure you have a directory /SYS in the root directory of your file system
as for the modules, did you compile everything into the kernel? if so, you will not see any modules, or maybe you forgot the step make modules && make modules_install ?
?
I do have /sys in this computer, I think it was there already, at least I didnt make it during the install >_>
I followed these instructions.
It was strange, because make_modules and make_install both took less than 10 seconds in total, while the bzImage took around 15 minutes, and the HOWTO said the former would take longer.
Also, another problem, ALSA dies, couldn't get the exact error messages, but it said xx_xxxxx_xx and xx_xxxxxx_xxx was missing, ALSA: FATAL was the starter of the sentence.
Im used to use make menuconfig (not make xconfig or make gconfig), you dont need to have everything compiled in the kernel. If you havent any module in lsmod its probably that you compiled everything in the kernel, im not here to say how to connect in the internet (its not what you' re asking) so I will assume you did everything to check if its a config problem or module problem. If so, you may have not compiled the right Module for you Ethernet card chipset. This is the same for your snd card.
you can use some commands to help help you find the right module:
#lspci
#cat /proc/pci
#dmesg
okay. Now to find those lines you can try #grep -in <argument to search> /usr/src/linux/.config
Try this, with the lines that you want to ask to see if they are with Y or if they are Not set.
(dont include the =y in the argument string to search)
sorry I should have made myself more clear. The .config file as keefaz (listen to this guy, he's always right on the money) says, is in the directory linux-2.6.12 from which you ran your'make'commands. most likely you were in /usr/src as most people compile their kernels here. The file is generated after you have gone through the menu options with xconfig or menuconfig etc., and you can use it to check what options you chose.
You compiled most stuff directly into the kernel, hence the short time it took at the modules stage. I would recommend reading the help that goes with each option as you make your choices. Many will be exactly the same as from your older kernel.I like using as many modules as I can get away with, but others prefer a more 'monolithic' kernel.
by the way, please check that /etc/fstab has something like
Also, I re-recompiled it just now, did everything exactly how it was before this new kernel, and still no dice >_< lsmod returns no modules. I used to have /etc/rc.d/rc.modules, now it talked about /etc/modprobe.conf (which used to be empty), might this be important?
Gackt, now it says a the superblock or something is corrupted >.< It gave me a e2fsck -v -y hda2 but it just outputs the same thing. I also tried -b 8193 (I think that was the number) and it says the same message again XP
keefaz, nope, not eth0, only lo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.