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.
No, it is at the configure step, with make menuconfig or make xconfig, up to you...
go to Loadable module support ---> and make sure that :
Enable loadable module support is set
Module unloading is set
Forced module unloading is set (or is not set, that does not matter, for me it is not set)
Module versioning support is not set
Automatic kernel module loading is set
Well try to follow kernel compile guide as you ask some basic question (and it is normal when beginning to learn it).
The /boot/config link is created by hand, for my part I don't use the kernel Makefile to install kernel with make install. So after a kernel compile, I used to copy the .config file to /boot and rename it accordingly to the kernel version, then I delete and remake the /boot/config link so it points to the new config file.
Ok finally recomplied the kernel to 2.6.8.1. Now when I dmesg | grep SCSI I get
Code:
SCSI subsystem initialized
Now how do I get slack to see my scsi cdrom, is the a ./configure or make that I have not found yet. Scanbus still gives me
Code:
root@linux:/# cdrecord -scanbus
Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
still no luck,but thanks samwwwblack. Now I think it has to do with the advansys drivers, not starting at boot, which stops the cdrom from being found. Will try recomple again with new drivers. and see how it goes.
cheers
Thanks everybody for all your help, I have finally fixed it. I recomplyed 2.6.7 with advansys drivers and now it works.
Again thanks to everybody who took the time to help me.
Cheers
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.