|
n8oay
|
 |
« on: December 17, 2011, 10:29:54 AM » |
|
This is the first time I have tried to burn a DVD since I installed PCLOS 2011-9. K3B is telling me that it does not see any optical drives. Both drives worked OK with the previous PCLOS installation. I think the problem is the way the drives are being detected. Copies of my FSTAB and PCLOS Control Center info and the K3B error message follows: FSTAB # Entry for /dev/hda6 : UUID=744ee5de-1fec-4444-81f2-ff25d4c751c3 / ext4 defaults 1 1 none /dev/pts devpts defaults 0 0 # Entry for /dev/hda8 : UUID=b5aef7a5-2996-4d38-9b1a-b402126c5f01 /home ext4 defaults 1 2 # Entry for /dev/sda1 : UUID=2762e0a3-bd02-4fb6-8a91-549ac06e44e6 /home/n8oay/disks/sda1 reiserfs defaults 1 2 # Entry for /dev/sda5 : UUID=1a6f1f0f-779e-49cc-9ef7-6329a4d64162 /home/n8oay/disks/sda5 reiserfs defaults 1 2 # Entry for /dev/sda6 : UUID=df1e311a-5352-4bd6-9821-2c6c7320ce50 /home/n8oay/disks/sda6 reiserfs defaults 1 2 none /proc proc defaults 0 0 # Entry for /dev/hda1 : UUID=fad27fa5-b98b-4b09-b931-90d0a08511ac swap swap defaults 0 0 # Entry for /dev/hda7 : UUID=44b8c165-4738-43cd-9bad-743910ac0dc5 swap swap defaults 0 0 # Entry for /dev/sda9 : UUID=670d7a1c-8b6e-47f7-88d7-684ff9e56ec9 swap swap defaults 0 0 PCLOS Control Center Info for IDE Master DVDRW drive Mount point: /media/cdrom Device: hdc Name: LITE-ON DVDRW LH-20A1P Type: auto Options: umask=0,users,iocharset=utf8,noauto,ro,exec PCLOS Control Center Info for IDE Slave DVDRW drive Mount point: /media/cdrom Device: hdd Name: PHILIPS SPD2413P Type: auto Options: umask=0,users,iocharset=utf8,noauto,ro,exec K3B Error Message No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Synaptic shows that HAL 05.14-4pclos201 is installed. Obviously, at least one of these optical drives is working correctly because I installed PCLOS 2011-9 from a Live CD. I have no clue what to do to get them to work correctly. I appreciate your help! Thank you Dave
|
|
|
|
|
Logged
|
N8OAY Dave Marshall
Genealogists Collect Dead People!
Toshiba L505D-S5983 AMD Athlon™ II Dual-Core M300 2.0GHz (No Linux Yet)
PCLOS 2011-9 KDE (Athlon 64x2 Dual Core Desktop) PCLOS & WinXP Dual Boot (Pentium 4 Desktop) PCLOS-Gnome 2009.2 (Mitac 8375 Athlon 1900+ Laptop)
|
|
|
AS
Global Moderator
Hero Member
   
Offline
Posts: 4082
Have a nice ... night!
|
 |
« Reply #1 on: December 17, 2011, 07:06:21 PM » |
|
K3B Error Message No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Synaptic shows that HAL 05.14-4pclos201 is installed. PCLinuxOS Control Center-> System -> Manage System services, verify haldaemon is enabled and running  AS
|
|
|
|
|
Logged
|
|
|
|
|
n8oay
|
 |
« Reply #2 on: December 20, 2011, 07:18:54 PM » |
|
Haldaemon is running and is set to start on boot.
|
|
|
|
|
Logged
|
N8OAY Dave Marshall
Genealogists Collect Dead People!
Toshiba L505D-S5983 AMD Athlon™ II Dual-Core M300 2.0GHz (No Linux Yet)
PCLOS 2011-9 KDE (Athlon 64x2 Dual Core Desktop) PCLOS & WinXP Dual Boot (Pentium 4 Desktop) PCLOS-Gnome 2009.2 (Mitac 8375 Athlon 1900+ Laptop)
|
|
|
|
|
|
n8oay
|
 |
« Reply #4 on: December 21, 2011, 07:45:44 PM » |
|
please, post the output of the command: lspci | grep ide
The command lspci | grep ide does not do anything. With no results, I am not sure what to do with the link that you provided.
|
|
|
|
|
Logged
|
N8OAY Dave Marshall
Genealogists Collect Dead People!
Toshiba L505D-S5983 AMD Athlon™ II Dual-Core M300 2.0GHz (No Linux Yet)
PCLOS 2011-9 KDE (Athlon 64x2 Dual Core Desktop) PCLOS & WinXP Dual Boot (Pentium 4 Desktop) PCLOS-Gnome 2009.2 (Mitac 8375 Athlon 1900+ Laptop)
|
|
|
Old-Polack
Administrator
Hero Member
   
Online
Posts: 9688
----IOFLU----
|
 |
« Reply #5 on: December 21, 2011, 08:00:24 PM » |
|
please, post the output of the command: lspci | grep ide
The command lspci | grep ide does not do anything. With no results, I am not sure what to do with the link that you provided. The proper command is lspci |grep -i ideor lspci |grep IDE
|
|
|
|
|
Logged
|
Old-Polack Of what use be there for joy, if not for the sharing thereof? Lest we forget... 
|
|
|
AS
Global Moderator
Hero Member
   
Offline
Posts: 4082
Have a nice ... night!
|
 |
« Reply #6 on: December 21, 2011, 08:02:19 PM » |
|
please, post the output of the command: lspci | grep ide
The command lspci | grep ide does not do anything. With no results, I am not sure what to do with the link that you provided. my bad sorry, should have been: lspci | grep IDE or lspci | grep -i ide and please post also the result of: uname -r If, as I believe (based on docs found on googles), your drives are IDE (as opposed to SATA), very probably you need to load some specific kernel module to support your IDE controller. EDIT: old-polack is always faster!
|
|
|
|
|
Logged
|
|
|
|
Old-Polack
Administrator
Hero Member
   
Online
Posts: 9688
----IOFLU----
|
 |
« Reply #7 on: December 21, 2011, 08:26:40 PM » |
|
please, post the output of the command: lspci | grep ide
The command lspci | grep ide does not do anything. With no results, I am not sure what to do with the link that you provided. my bad sorry, should have been: lspci | grep IDE or lspci | grep -i ide and please post also the result of: uname -r If, as I believe (based on docs found on googles), your drives are IDE (as opposed to SATA), very probably you need to load some specific kernel module to support your IDE controller. EDIT: old-polack is always faster!I just happened to be here. I reread the thread you linked to, and found a typo on a later reply of mine so corrected it while there. That might avoid any confusion if anyone else follows it to the end. If you hadn't linked to that thread, I might never have spotted it until someone got themselves into trouble because of it, so thanks. 
|
|
|
|
|
Logged
|
Old-Polack Of what use be there for joy, if not for the sharing thereof? Lest we forget... 
|
|
|
|
darkages
|
 |
« Reply #8 on: December 22, 2011, 01:34:30 AM » |
|
n8oay, I had a similar issue with a recent PC build... So I changed motherboard SATA connections to SATA 1&2 for HDDs, and SATA 3&4 for optical drives. My burner problem was solved - all drives detected in PCLOS 2011.! Cages
|
|
|
|
|
Logged
|
|
|
|
|
n8oay
|
 |
« Reply #9 on: January 04, 2012, 07:30:43 PM » |
|
Both of these burners are IDE, and worked OK with the previous installation of PCLOS 2010. No hardware in the computer has been changed. [n8oay@localhost ~]$ lspci |grep -i ide 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
[n8oay@localhost ~]$ uname -r 2.6.38.8-pclos3.bfs [n8oay@localhost ~]$
|
|
|
|
|
Logged
|
N8OAY Dave Marshall
Genealogists Collect Dead People!
Toshiba L505D-S5983 AMD Athlon™ II Dual-Core M300 2.0GHz (No Linux Yet)
PCLOS 2011-9 KDE (Athlon 64x2 Dual Core Desktop) PCLOS & WinXP Dual Boot (Pentium 4 Desktop) PCLOS-Gnome 2009.2 (Mitac 8375 Athlon 1900+ Laptop)
|
|
|
AS
Global Moderator
Hero Member
   
Offline
Posts: 4082
Have a nice ... night!
|
 |
« Reply #10 on: January 04, 2012, 07:45:24 PM » |
|
Both of these burners are IDE, and worked OK with the previous installation of PCLOS 2010. No hardware in the computer has been changed. [n8oay@localhost ~]$ lspci |grep -i ide 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
[n8oay@localhost ~]$ uname -r 2.6.38.8-pclos3.bfs [n8oay@localhost ~]$
Check if the module pata_amd is currently loaded: lsmod | grep pata_amdif not, try (from a root terminal): modprobe pata_amdthen test your drives (k3b, manual mounting of an ISO image ...) if it will work, to make the changes permanent, append the module name pata_amd to the content of the file /etc/modprobe.preload, copy & paste the following command (from a root terminal): echo pata_amd >> /etc/modprobe.preload
|
|
|
|
|
Logged
|
|
|
|
|
n8oay
|
 |
« Reply #11 on: January 07, 2012, 09:44:47 PM » |
|
I have performed the above steps. K3B still does not recognize blank DVDs. However, when I insert a blank DVD, the Notifications on the right side of the Task Bar pops up showing that a blank DVD is available to record with K3B. Both drives recognize data DVDs and I can access files on them through Dolphin. Neither drive recognizes a movie DVD. And I have one other problem. When I open either drive to place something in it. the drive's tray closes by itself, giving me just enough time to place a disc in the drive. If I open either drive while the computer is booting before it displays the splash screen, the trays stay open. This is the current result of lsmod | grep pata_amd [n8oay@localhost ~]$ lsmod | grep pata_amd pata_amd 8204 0 libata 154591 4 sata_nv,ata_generic,pata_acpi,pata_amd [n8oay@localhost ~]$
Thanks again for your help! Dave
|
|
|
|
|
Logged
|
N8OAY Dave Marshall
Genealogists Collect Dead People!
Toshiba L505D-S5983 AMD Athlon™ II Dual-Core M300 2.0GHz (No Linux Yet)
PCLOS 2011-9 KDE (Athlon 64x2 Dual Core Desktop) PCLOS & WinXP Dual Boot (Pentium 4 Desktop) PCLOS-Gnome 2009.2 (Mitac 8375 Athlon 1900+ Laptop)
|
|
|
AS
Global Moderator
Hero Member
   
Offline
Posts: 4082
Have a nice ... night!
|
 |
« Reply #12 on: January 07, 2012, 11:50:56 PM » |
|
I have performed the above steps. K3B still does not recognize blank DVDs.
both drives ?  Try a different media/brand DVD. However, when I insert a blank DVD, the Notifications on the right side of the Task Bar pops up showing that a blank DVD is available to record with K3B. Both drives recognize data DVDs and I can access files on them through Dolphin.
Which version of k3b is installed on your system ? Should be k3b-2.0.2-2pclos2011 Neither drive recognizes a movie DVD.
Doesn't recognize ... or doesn't play ? And I have one other problem. When I open either drive to place something in it. the drive's tray closes by itself, giving me just enough time to place a disc in the drive. If I open either drive while the computer is booting before it displays the splash screen, the trays stay open.
I remember to have read few days ago about some flag specific for this issue ... only don't remember which flag and where to apply it ... nor where I read it ... possibly a kernel-module option ... stay tuned ... This is the current result of lsmod | grep pata_amd [n8oay@localhost ~]$ lsmod | grep pata_amd pata_amd 8204 0 libata 154591 4 sata_nv,ata_generic,pata_acpi,pata_amd [n8oay@localhost ~]$
Thanks again for your help! Dave
|
|
|
|
|
Logged
|
|
|
|
|
djohnston
|
 |
« Reply #13 on: January 08, 2012, 03:14:08 AM » |
|
Just a suggestion. Try running K3B setup again. It doesn't make sense that the system sees the drives, but K3B doesn't. Just open a terminal and enter k3bsetup. You don't need root privileges.
|
|
|
|
|
Logged
|
Bare metal VBox AMD Athlon 7750 Dual-Core Single core 4GiB RAM 1GiB RAM nVidia GeForce FX 5200 64MB video LXDE 32bit KDE 64bit
Registered Linux User #416378
|
|
|
AS
Global Moderator
Hero Member
   
Offline
Posts: 4082
Have a nice ... night!
|
 |
« Reply #14 on: January 09, 2012, 12:37:35 PM » |
|
And I have one other problem. When I open either drive to place something in it. the drive's tray closes by itself, giving me just enough time to place a disc in the drive. If I open either drive while the computer is booting before it displays the splash screen, the trays stay open.
I remember to have read few days ago about some flag specific for this issue ... only don't remember which flag and where to apply it ... nor where I read it ... possibly a kernel-module option ... stay tuned ... There is a possible solutions, it may or may not work, but it's enough easy to try/test: edit the file /etc/systcl.conf and find the fragment below: # If you set this variable to 1 then cd tray will close automatically when the # cd drive is being accessed. # Setting this to 1 is not advised when supermount is enabled # (as it has been known to cause problems) dev.cdrom.autoclose=1
edit the file (from a root account terminal) and change it to dev.cdrom.autoclose=0, reboot and report back the result. if it doesn't work, reverse back the change. AS
|
|
|
|
|
Logged
|
|
|
|
|