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.
Well, I've been trying to upgrade my kernel for slackware 10.1 with out success as it keeps crashing. I have been downloading the .tar.gz kernel source from kernel.org for the 2.6.11.7 kernel. I have tried twice now but it has been to no success both times I tried it following shilo's tutorial.
I was wonding if there is anyway of installing another source of the kernel right during the slackware 10.1 install. I know that the automatic install is the 2.4.9 source i believe, but the 4 files i downlaoded and burned to cd's (from here http://slackware.com/getslack/torrents.php
come with the 2.6.10 kernel source on like the 3rd or 4th cd. Does anyone know how I would choose to install that kernel instead. I have to upgrade to a 2.6.x kernel in order to use ndiswrapper on my win xp driver for my usb wireless network adapter. It is stated that it is only possible for my specific driver to use ndiswrapper in a 2.6.x kernel. I've tried googling but I have not found any good sites that explain how I would go about doing this.
Thanks a lot for any help.
~slackware1299
Last edited by slackware1299; 04-30-2005 at 06:41 PM.
You did compile the new kernel, right? Sorry if you did, it may seem like a stupid question but I was talking to someone yesterday who tried to install a new kernel source but didn't know he had to configure and compile it first.
One suggestion that may make it easier for you to correctly configure the new kernel; copy the config file for your currently working kernel to the source directory of your new kernel. That way all of the options that you know already work are selected. Then you can simply make any changes you KNOW to make without borking your new kernel config. Then compile the new kernel and install it.
Well, I just followed all of Shilo's tutorial from here http://www.linuxquestions.org/questi...hreadid=174447
i went through all the configurations which took forever, and then i did all the make install, make modules commands, and then I edited Lilo, and ran sbin/lilo for it to take effect, but when i restarted it crashed. Do you know how to install right from cd wehn you first install slackware?
~slackware1299
EDIT: I found this and it kind of looks interesting im gonna give it a try
Quote:
It's simple mate.
Simply insert CD #2 AKA Rescue Disc.
Go Under
Code:
/mnt/cdrom/testing/packages/linux-2.6.10
]
Then do:
Code:
installpkg kernel-generic-2.6.10-i486-1.tgz
installpkg kernel-modules-2.6.10-i486-1.tgz
installpkg mkinitrd-1.0.1-i486-1.tgz (this last one I didn't do)
Then cd back to /boot/ and do:
Code:
mkinitrd -c -k 2.6.10 -m <your FS type>
Don't forget to update lilo.
Mine looks like this
1st:
Code:
pico /etc/lilo.conf
After your regular image enter the following:
Code:
image = /boot/vmlinuz-generic-2.6.10
initrd = /boot/initrd.gz
root = /dev/hdb3
label = Linux2.6.10
read-only
Save and Exit.
2nd: Back on the console type:
Code:
lilo
3rd: Reboot and pray!
Mental Note: Don't delete your 2.4.* image, it might come in handy!
----- POST UPDATED-----
GL.[/code]
Last edited by slackware1299; 04-30-2005 at 06:58 PM.
hmmm
i followed the instructions above
but when i got to installpkg mkinitrd-1.0.1-i486-1.tgz
i got the message:
Cannot install mkinitrd-1.0.1-i486-1.tgz: package does not end in .tgz
I am not quite sure why, both of the other 2 commands worked fine. I currently have the bare.i kernel if that has any importance.
Also for the part once I have done that wehre it says
mkinitrd -c -k 2.6.10 -m <your FS type>
would i put ext2 or Ext2? is it case sensative? thanks for help
~slackware1299
Last edited by slackware1299; 04-30-2005 at 09:58 PM.
For future reference if you boot with the sata.i kernel it will support IDE interfaces, the standard kernel bare.i however doesn't support SATA Sad. sata.i is a version of bare.i with support for SATA controllers made by Promise, Silicon Image, SiS, ServerWorks / Apple K2, VIA, and Vitesse.
as I said earlier I installed w/ bare.i, do i have toinstall w/ sata.i for this to work?
thanks
so is it necessary for me to do the following two codes?
Code:
installpkg mkinitrd-1.0.1-i486-1.tgz (this last one I didn't do)
Then cd back to /boot/ and do:
Code:
mkinitrd -c -k 2.6.10 -m <your FS type>
or shoulod i just install the first two packages and then change lilo?
i tried the second code with putting ext2 as my filesystem type and I got the error that it could not find the module for ext2, so according to you i can just skip these two steps?
alright thank you, I worked fine, and I upgraded to the 2.6.10 kernel
however as soon as i did startx and went into KDE for the first time I got the following error message about the sound
Quote:
Informational - Arts Message
Sound server informational message:
Error while initializing the sound driver.
device /dev/dsp can't be opened (No such file or directory)
The sound server will continue, using the null output device.
I dont know if the following is importnant or not but I still havent ran alsaconfig to setup my sound, but I still never got this error message at start when runnigng with teh old kernel. Second, I noticed that on my cd from which i installed the kernel there were two files which looked like patches for alsa.
Has anyone had this problem?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.