LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-11-2004, 04:57 AM   #31
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 244Reputation: 244Reputation: 244

One good practice when configuring kernel is to disable the CONFIG_MODVERSIONS feature.

Whan you say The config file points to config-ide-2.4.26, which config do you talk ? The one in /boot? If yes, it does not matter.

I would re-configure kernel without mod version, re-compile, re-install it and see if it works.
 
Old 08-11-2004, 05:03 AM   #32
mm3000
Member
 
Registered: Jul 2004
Location: Victoria, OZ
Distribution: Slackware x64_Current
Posts: 82

Original Poster
Rep: Reputation: 15
Cedrik, it is the one in the /boot.
How do I dis-able CONFIG_MODVERSIONS feature. Does this happen before I re-configure the kernel.
 
Old 08-11-2004, 05:08 AM   #33
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 244Reputation: 244Reputation: 244
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
 
Old 08-11-2004, 05:15 AM   #34
mm3000
Member
 
Registered: Jul 2004
Location: Victoria, OZ
Distribution: Slackware x64_Current
Posts: 82

Original Poster
Rep: Reputation: 15
Ok Cedrik I will give that a go. Will that update the /boot/config file?
Cheers
 
Old 08-11-2004, 05:19 AM   #35
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 244Reputation: 244Reputation: 244
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.
 
Old 08-18-2004, 07:52 AM   #36
mm3000
Member
 
Registered: Jul 2004
Location: Victoria, OZ
Distribution: Slackware x64_Current
Posts: 82

Original Poster
Rep: Reputation: 15
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'.
Any ideas??
 
Old 08-18-2004, 09:41 AM   #37
samwwwblack
Member
 
Registered: Apr 2003
Location: Midlands, UK
Distribution: Lapwing-Linux 2009.1
Posts: 64

Rep: Reputation: 15
Is there a /dev/sr0 or /dev/cdrom? If there is just

su
ln -s /dev/cdrom /dev/pg0

where /dev/cdrom is you're cdrom drive (it could be /dev/hdc /dev/sr0 etc), and then retry cdrecord -scanbus as root

If it picks it up, then as root

mcedit /etc/udev/rules.d/udev.rules and change it to the following:

# permissions for IDE CD devices
#BUS="ide", KERNEL="*[!0-9]", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom*", NAME="%k", GROUP="cdrom", MODE="0777" SYMLINK="pg0 dvd"

# permissions for SCSI cd/sg/tape devices
BUS="scsi", KERNEL="s[grt][0-9]*", SYSFS_type="5", NAME="%k", GROUP="cdrom", MODE="0777", SYMLINK="cdrom dvd pg%n"

Hopefully this'll work for you (and it appears right with people more worthy than myself ),
Cheers, Sam
 
Old 08-19-2004, 04:54 AM   #38
mm3000
Member
 
Registered: Jul 2004
Location: Victoria, OZ
Distribution: Slackware x64_Current
Posts: 82

Original Poster
Rep: Reputation: 15
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
 
Old 08-19-2004, 07:37 AM   #39
mm3000
Member
 
Registered: Jul 2004
Location: Victoria, OZ
Distribution: Slackware x64_Current
Posts: 82

Original Poster
Rep: Reputation: 15
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
scsi cdrom problems emilryge Linux - Hardware 4 09-25-2004 06:25 PM
Install from SCSI cdrom? cootcraig Slackware - Installation 1 09-25-2004 03:10 PM
9.1 install, boot from cdrom, select source as cdrom, Can't find disk jake555 Slackware 1 10-30-2003 10:34 AM
mounting SCSI CDROM MetalStorm Linux - Hardware 0 03-23-2003 11:30 AM
Mandrake 8.1 CDROM and SCSI Ashes Linux - Software 6 02-05-2002 08:33 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:06 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration