LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] A problem with my dvd devices...
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-22-2011, 01:40 AM   #1
trist007
Senior Member
 
Registered: May 2008
Distribution: Slackware
Posts: 1,052

Rep: Reputation: 70
A problem with my dvd devices...

When I boot up the Slackware64 13.37 install image, I can easily see /dev/sr0 and /dev/sr1. I have two DVD drives of course. Anyhow, I have no problem mounting /dev/sr0 to /mnt/dvd. However, after I install and boot up into slackware runlevel 3, I don't see a /dev/sr0 or a /dev/sr1.

I put in a dvd in a drive and check /var/log/messages for messages but nothing. I have tried with both hald and without, however I prefer not using hald. I like mounting things on my own.

I am booting kernel image with "acpi=off". Would that have anything to do with it? What else can I do to start troubleshooting?

Here's my /etc/udev/rules.d/70-persistent-cd.rules
Code:
# DVD_A_DH20A4H (pci-0000:06:00.1-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdrom0", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdr0", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdr", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdwriter0", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdwriter", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdrw0", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="writer", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="dvd0", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="dvdrw0", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="dvdwriter0", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:0:0", SYMLINK+="dvdwriter", ENV{GENERATED}="1"

# DVD_D_DH16D2P (pci-0000:06:00.1-scsi-0:0:1:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:1:0", SYMLINK+="cdrom1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:1:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:1:0", SYMLINK+="dvd1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:06:00.1-scsi-0:0:1:0", SYMLINK+="dvd", ENV{GENERATED}="1"
Last edited by trist007; 10-22-2011 at 01:47 AM.
 
Old 10-22-2011, 04:32 AM   #2
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Hi trist007,

I had similar issues when my (selfbuilt) kernel lacked the appropriate modules or there is missing an option in the kernel-configuration.

Unfortunately I don't remember which module and which option there were missing.

Did you build your own kernel? do you have any exotic hardware?

Markus
 
Old 10-22-2011, 10:56 AM   #3
trist007
Senior Member
 
Registered: May 2008
Distribution: Slackware
Posts: 1,052

Original Poster
Rep: Reputation: 70
No, just running plain old 2.6.37.6 #3 SMP kernel.
 
Old 10-22-2011, 11:30 AM   #4
trist007
Senior Member
 
Registered: May 2008
Distribution: Slackware
Posts: 1,052

Original Poster
Rep: Reputation: 70
My two hard drives use IDE flat cable. One thing I have noticed are these smartd error messages on boot, from /var/log/messages. I don't get these when I boot up slackware64 13.37 install image.
Code:
ata3.00: configured for UDMA/133
ata3.01: configured for UDMA/133
ata3: EH complete
ata3.00: configured for UDMA/133
ata3.01: configured for UDMA/133
ata3: EH complete
ata4.00: configured for UDMA/133
ata4.01: configured for UDMA/100
ata4: EH complete
ata4.00: configured for UDMA/133
ata4.01: configured for UDMA/100
ata4: EH complete
ata6.00: configured for UDMA/100
ata6: EH complete
Or is smartd just for hard drives?
Basically my /var/log/messages file would look like this when it worked.
Code:
Oct 21 22:43:30 darkstar kernel: [    1.479228] scsi 6:0:0:0: CD-ROM            ATAPI    DVD A  DH20A4H   QP53 PQ: 0 ANSI: 5
Oct 21 22:43:30 darkstar kernel: [    1.484801] cdrom: Uniform CD-ROM driver Revision: 3.20
Oct 21 22:43:30 darkstar kernel: [    1.486626] scsi 6:0:1:0: CD-ROM            ATAPI    DVD D  DH16D2P   HP57 PQ: 0 ANSI: 5
Oct 21 22:43:30 darkstar kernel: [    3.128036] sd 2:0:0:0: Attached scsi generic sg0 type 0
Oct 21 22:43:30 darkstar kernel: [    3.128142] sd 2:0:1:0: Attached scsi generic sg1 type 0
Oct 21 22:43:30 darkstar kernel: [    3.128238] sd 3:0:0:0: Attached scsi generic sg2 type 0
Oct 21 22:43:30 darkstar kernel: [    3.128331] sd 3:0:1:0: Attached scsi generic sg3 type 0
Oct 21 22:43:30 darkstar kernel: [    3.128426] sd 5:0:0:0: Attached scsi generic sg4 type 0
Oct 21 22:43:30 darkstar kernel: [    3.128520] sr 6:0:0:0: Attached scsi generic sg5 type 5
Oct 21 22:43:30 darkstar kernel: [    3.128614] sr 6:0:1:0: Attached scsi generic sg6 type 5
Now it simply does not output those lines.
Last edited by trist007; 10-22-2011 at 11:49 AM.
 
Old 10-22-2011, 11:42 AM   #5
hen770
Member
 
Registered: Oct 2010
Distribution: Arch
Posts: 136

Rep: Reputation: 7
Did you try otge dev names? such as /dev/cdrom or dvd and so on as you see in your udev rule file.
 
Old 10-22-2011, 11:52 AM   #6
trist007
Senior Member
 
Registered: May 2008
Distribution: Slackware
Posts: 1,052

Original Poster
Rep: Reputation: 70
Yes none of these device names listed in the udev rules I pasted above exist in /dev.
 
Old 10-22-2011, 11:58 AM   #7
trist007
Senior Member
 
Registered: May 2008
Distribution: Slackware
Posts: 1,052

Original Poster
Rep: Reputation: 70
Ah yes one thing I forgot to mention is that I append kernel boot line with "acpi=off". I currently have two nvidia 9500 GT graphics card in the comp hooked up to 4 monitors. When I boot without this append option I get a blank screen on all monitors around the time when dmesg stop it's logging during boot. I bet this option is related. Maybe there's an alternative to "acpi=off" so that I won't reach a blank screen after boot into runlevel 3.
Last edited by trist007; 10-22-2011 at 12:20 PM.
 
Old 10-22-2011, 12:35 PM   #8
trist007
Senior Member
 
Registered: May 2008
Distribution: Slackware
Posts: 1,052

Original Poster
Rep: Reputation: 70
I tried it without "acpi=off", I get the blank screen so I SSH from another box. And there they are, the two dvdrom devices sr0 and sr1 under /dev. On the blank screen console I try logging in and starting startx by carefully typing it in. I confirm on the other box that I ssh'd from that I see another user start startx. Then X loads kde and I can now see 2 monitors all in disarray. I had all 4 monitors working perfectly via nvidia-config. I run a lsmod and I see both nvidia and nouveau.

This is strange because there used to be a blacklist-nouvea.conf file in /etc/modprobe.d (added in by the NVIDIA.run script) that would blacklist it. Now for some reason that file is missing. So I add in "blacklist nouveau" to blacklist.conf and reboot. This is without the "acpi=off" append option. Now it boots up into runlevel 3 without the blank screens. Problem solved.

I don't understand how that blacklist-nouveau.conf file disappeared. Anyways, it's working. Thanks everyone.
Last edited by trist007; 10-22-2011 at 12:38 PM.
 
Old 10-22-2011, 06:47 PM   #9
hen770
Member
 
Registered: Oct 2010
Distribution: Arch
Posts: 136

Rep: Reputation: 7
Is anybody could explain the relation to acpi?

For the poster, mark the post as solved would help others.
 
  


Reply



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
Automounting CD/DVD and USB devices Tux-Slack Slackware 16 06-26-2007 02:04 PM
RAID volume using DVD-RW devices BerzinTehvs Linux - Hardware 1 02-02-2007 08:08 AM
dvd and cdrom devices Kroenecker Fedora 3 12-22-2004 01:06 PM
Does anyone have *any* external DVD-RW devices working? bulletdog7 Linux - Hardware 4 08-27-2004 08:31 AM
Cd-rw And Dvd-rom Disappeared From The Devices Risetaker2003 General 2 09-30-2003 07:40 PM

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

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

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
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