LinuxQuestions.org
Review your favorite Linux distribution.
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 11-25-2006, 09:59 AM   #16
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 -current
Posts: 2,299

Rep: Reputation: 89

Quote:
Originally Posted by tamtam
fstab is the same as the one which mounts hdc successfully with the 2.4 kernel...
Looks ok to me.

Try the command "mount /mnt/cdrom" and see what happens.

BTW, what kind of disk do you have in the CDROM?
 
Old 11-25-2006, 10:23 AM   #17
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
Within slack disk 2 /extras is the directory /udev-alternate-versions...

the answer maybe within the README file...

Quote:
From the desk of Patrick Volkerding, Mon Aug 7 16:08:08 CDT 2006.

Hello,

Some people have reported problems with the newer style udev, and I've seen
some myself. However, newer kernels are about to require a very recent udev
so it was time to upgrade to the latest, in spite of the possible pain.

One issue that's being reported is that udev sometimes chooses a different
module that would be desired. In those cases, add the module that you don't
want to the blacklist (with udev-096 or higher this would be
/etc/modprobe.d/blacklist), and then edit /etc/rc.d/rc.modules to load the
module that you want.

In some cases where you want to run udev it might be easier to run one of
these old versions than to fight with it. Feel free to try them if you run
into problems with the latest. Just "upgrade" to one of these with
upgradepkg, copy rc.S and rc.M over the ones in /etc/rc.d/, and finally
go into /etc/rc.d and move rc.udev.new to rc.udev (and make sure that it
is executable). Also, check to make sure that there aren't new config or
rules files that need to be moved into place. You can find these with:

find /etc -name "*.new"

Good luck! :-)

Pat
I was thinking of copying the appropriate module for the cdrom drive from the 2.4 kernel to the 2.6. Any thoughts anyone...
 
Old 11-25-2006, 10:27 AM   #18
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
It's the same no matter what cdrom I have in the drive...at the moment it's slack disk 2.

Since I can mount the drive with the 2.4 kernel, I think it maybe using the wrong driver for 2.6. I have no idea as yet on how to rectify this or where to begin.
 
Old 11-25-2006, 10:55 AM   #19
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 -current
Posts: 2,299

Rep: Reputation: 89
Did you try the command "mount /mnt/cdrom"?

One way to determine if the wrong module is being loaded is to boot the working kernel and do a lsmod and then the nonworking one and compare it's lsmod to the original to spot any differences.
 
Old 11-25-2006, 11:12 AM   #20
Franklin
Senior Member
 
Registered: Oct 2002
Distribution: Slackware, Windows 7
Posts: 1,257

Rep: Reputation: 61
You seem to be getting nowhere fast, so I will offer up a wild-ass guess.

One difference between 2.4 and 2.6 kernels in slackware 11.0 is that hotplug runs with 2.4 and not with 2.6 kernels (udev only). I suggest booting with 2.4.33.3 and print out the output of lsmod. Then boot with 2.6 and compare loaded modules. You may note a difference that you can create a work around for when booting with a 2.6 kernel and no hotplug.

Along these lines:

Quote:
One issue that's being reported is that udev sometimes chooses a different
module that would be desired. In those cases, add the module that you don't
want to the blacklist (with udev-096 or higher this would be
/etc/modprobe.d/blacklist), and then edit /etc/rc.d/rc.modules to load the
module that you want.
I do not think that copying a module as you seem to be suggesting will work.

Last edited by Franklin; 11-25-2006 at 11:15 AM.
 
Old 11-25-2006, 02:19 PM   #21
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
will have a go tomorrow, been all day trying to find a solution to this.
 
Old 11-26-2006, 03:32 PM   #22
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
Okay, still trying to resolve this problem with my cdrom drive and mounting.

Quote:
lsmod on the 2.4.33.3 kernel

Module Size Used by Not tainted
snd-seq-oss 23104 0 (unused)
snd-seq-midi-event 3208 0 [snd-seq-oss]
snd-seq 33552 2 [snd-seq-oss snd-seq-midi-event]
snd-seq-device 3716 0 [snd-seq-oss snd-seq]
snd-pcm-oss 28928 0 (unused)
snd-mixer-oss 11928 0 [snd-pcm-oss]
usb-storage 63520 0
uhci 23804 0 (unused)
usbcore 56812 1 [usb-storage uhci]
snd-maestro3 14052 0
snd-ac97-codec 68160 0 [snd-maestro3]
snd-pcm 52804 0 [snd-pcm-oss snd-maestro3 snd-ac97-codec]
snd-timer 13168 0 [snd-seq snd-pcm]
snd 34304 0 [snd-seq-oss snd-seq-midi-event snd-seq snd-seq-device snd-pcm-oss snd-mixer-oss snd-maestro3 snd-ac97-codec snd-pcm snd-timer]
snd-page-alloc 4980 0 [snd-seq-oss snd-seq snd-seq-device snd-mixer-oss snd-pcm snd-timer snd]
soundcore 3300 5 [snd]
3c59x 25520 0
ds 6612 2
yenta_socket 10532 2
pcmcia_core 39492 0 [ds yenta_socket]
ide-scsi 9392 0
agpgart 45092 0 (unused)
Quote:
lsmod on the 2.6.17.13 kernel

Module Size Used by
nls_iso8859_1 3968 1
nls_cp437 5632 1
vfat 10112 1
fat 45980 1 vfat
snd_seq_dummy 2820 0
snd_seq_oss 28928 0
snd_seq_midi_event 5888 1 snd_seq_oss
snd_seq 43984 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 6284 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 38048 0
snd_mixer_oss 15616 1 snd_pcm_oss
ipv6 223584 10
sg 26524 0
capability 3336 0
commoncap 5376 1 capability
lp 9800 0
parport_pc 24132 1
parport 30024 2 lp,parport_pc
pcspkr 2432 0
psmouse 34952 0
snd_maestro3 20900 0
pcmcia 30116 0
evdev 8064 1
usb_storage 78528 1
shpchp 33816 0
snd_ac97_codec 86304 1 snd_maestro3
firmware_class 7424 1 pcmcia
snd_ac97_bus 2048 1 snd_ac97_codec
serio_raw 5252 0
snd_pcm 73736 3 snd_pcm_oss,snd_maestro3,snd_ac97_codec
snd_timer 19332 2 snd_seq,snd_pcm
snd_page_alloc 7560 1 snd_pcm
snd 43364 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_maestro3,snd_ac97_codec,snd_pcm,snd _timer
uhci_hcd 19724 0
soundcore 7136 1 snd
i2c_piix4 7696 0
i2c_core 16528 1 i2c_piix4
intel_agp 19612 1
3c59x 38056 0
mii 4864 1 3c59x
agpgart 28080 1 intel_agp
yenta_socket 23436 2
rsrc_nonstatic 10752 1 yenta_socket
pcmcia_core 34192 3 pcmcia,yenta_socket,rsrc_nonstatic
reiserfs 239088 2
Needing a experts help here to dicipher the above. I am looking for the module used in conjunction with my cdrom drive, bearing in mind this is a laptop. Any help will be welcomed.
 
Old 11-26-2006, 05:23 PM   #23
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
Anybody? Been at this for 3 days now.
 
Old 11-26-2006, 05:32 PM   #24
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 -current
Posts: 2,299

Rep: Reputation: 89
Nothing jumps out there. shpchp can sometime be problem. I had to blacklist it on a Compaq laptop I used to have.

Just a thought, but is your user in the cdrom group?
 
Old 11-27-2006, 03:10 AM   #25
rkrishna
Member
 
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654

Rep: Reputation: 32
i got you.
Quote:
/dev/hdc /mnt/cdrom auto noauto,user,ro 0 0
/dev/sr0 /mnt/cdrecorder auto noauto,user 0 0
where is ro in the /dev/sr0 line??

do you have 2 seperate cd drives???

IF U HAVE 1 CD DRIVE
scsi emulation made /dev/sr0 and the corresponding divice is changed. so you need to mount /mnt/cdrecorder, not /mntcdrom
(always remove unwanted links in /dev)
when you were using 2.4 kernel u need scsi emu and your devices has to be changed, if there is only one drive tehn, do
rm -rf /dev/cdrom
ln -sf /dev/sr0 /dev/cdrom
(this has to be done in 2.4 kernel, if you have a single cd drive)

also while using a 2.6 kernel, you dont need append line in lilo remove that for 2.6 kernel section

IF U HAVE 2 CD DRIVES
do $ls -al /dev |grep -i cd
$ls -al /dev |grep -i dvd
remove all unwanted links, make new links there.
http://rkrishna.tp.googlepages.com/slackerbasics#cd

http://rkrishna.tp.googlepages.com/s...basics#scsiemu

Last edited by rkrishna; 11-27-2006 at 03:26 AM.
 
Old 11-27-2006, 03:55 PM   #26
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
rkrishna says...

i got you.
/dev/hdc /mnt/cdrom auto noauto,user,ro 0 0
/dev/sr0 /mnt/cdrecorder auto noauto,user 0 0
where is ro in the /dev/sr0 line??
dev/sr0 is a cdrw drive...it is the one that works okay in both 2.4 and 2.6


do you have 2 seperate cd drives???
YES...
I have a laptop, with a cdrom drive module in place, this works in 2.4, but not in 2.6.
I also have a usb iomegaZIP cdrw drive attached, which works in both 2.4 and 2.6.
 
Old 11-27-2006, 06:13 PM   #27
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
rkrishna says
Quote:
IF U HAVE 2 CD DRIVES
do $ls -al /dev |grep -i cd
$ls -al /dev |grep -i dvd
remove all unwanted links, make new links there.
All very well, but this would have to be repeated every time I boot into 2.6.

Tried it once, and guess what it made no difference. Still unable to mount a cdrom in 2.6 which I can mount easily enough in 2.4 kernel.


5 days at this now and still cant figure out the solution.

How do you blacklist a module like masonm suggested.
 
Old 11-27-2006, 11:25 PM   #28
rkrishna
Member
 
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654

Rep: Reputation: 32
sorry i cant help more but some suggestions, actually i didnt ment the earlier commands . really it was"$ls -al /dev |grep -i hdc"
do "$dmesg |grep -i hdc" without any cd inserted.
do "$dmesg |grep -i cd" that msut endup within 2-3 lines as it is for sr0

Quote:
All very well, but this would have to be repeated every time I boot into 2.6.
when i install slackware there were many simlinks pointing towards teh drive,(it was causing problems) so i removed all simlinks, created new, editted fstab.
Quote:
Tried it once, and guess what it made no difference.
it is because your fstab has correct device entry not simlinks.
ur problem is not that. i went through yur dmesg, and i hope u were trying to mount a cd made from windows.
is there any append line in lilo. like append "hdc = ide-scsi"?? i dont think so.

Last edited by rkrishna; 11-27-2006 at 11:26 PM.
 
Old 11-27-2006, 11:32 PM   #29
rkrishna
Member
 
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654

Rep: Reputation: 32
try some more and i am givenup
1.try mount as root
2.put your slack cd and try!!
mount -t iso9660 /dev/hdc /mnt/cdrom
3.try oounting to some other moutn point like /home/name/mycd
mount -t iso9660 /dev/hdc /home/name/mycd
4.try mountin /dev/sr0 to /mnt/cdrom manually(just to check the permission)
i think $dmesg |grep -i hdc without any cd must give some info

sorry tht i couldnt help regards
 
Old 11-28-2006, 03:34 PM   #30
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
rkrishna says...

Quote:
when i install slackware there were many simlinks pointing towards teh drive,(it was causing problems) so i removed all simlinks, created new, editted fstab.
I also edited /dev by deleting all symlinks pointing to hdc and sr0, I then added my own links to the appropriate drives. Unfortunately, after a reboot, the new kernel recreates the old symlinks and permissions, so therefore I have to go through the whole process again.

Quote:
it is because your fstab has correct device entry not simlinks.
ur problem is not that. i went through yur dmesg, and i hope u were trying to mount a cd made from windows.
is there any append line in lilo. like append "hdc = ide-scsi"?? i dont think so.
I do not know exactly what you mean here. fstab points to the correct symlinks I created in dev. More than likely the cd I am trying to mount will have been burned using software running under windows, including the slack install disks. There is no append line in lilo.
 
  


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
Mount problems after kernel upgrade npuetz Linux - Hardware 2 06-13-2005 02:28 PM
CDROM cannot mount after upgrade to kernel 2.6.10 geeman2.0 Slackware 6 05-05-2005 07:57 AM
gnome trouble after kernel upgrade blish_blash Linux - Software 3 08-16-2004 06:00 PM
unable to mount floppy after kernel upgrade andrew001 Linux - Hardware 1 12-07-2003 07:51 PM
Kernel upgrade trouble katmai90210 Red Hat 3 11-07-2003 10:32 PM

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

All times are GMT -5. The time now is 12:58 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration