K3B killed my Burner
I installed a version of k3b 11.20-3 and now my machine doesn't know how to burn. In k3b it says "no burner found" or something to that effect (even though I can se the burner in k3b setup. Also, I can see the burner under Hardware Information in Yast and under the CD-ROM option. I get the follow when I do a "cat /var/log/messages" and I believe this is why my burner no longer works. This is after restarting the machine so this is mostly from the boot process itself: Mar 11 14:58:41 raphael kernel: subfs: unsuccessful attempt to mount media (256) Mar 11 14:59:01 raphael /usr/sbin/cron[6347]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Mar 11 15:02:13 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:15 raphael last message repeated 41 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:15 raphael last message repeated 2 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:15 raphael last message repeated 7 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:15 raphael last message repeated 2 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:54 raphael last message repeated 42 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:54 raphael last message repeated 2 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:54 raphael last message repeated 7 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:54 raphael last message repeated 2 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 502 Mar 11 15:03:06 raphael k3b: resmgr: server response code 502 Mar 11 15:03:07 raphael last message repeated 41 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 501 Mar 11 15:03:07 raphael last message repeated 2 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 502 Mar 11 15:03:07 raphael last message repeated 7 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 501 Mar 11 15:03:07 raphael last message repeated 2 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 502 Mar 11 15:03:07 raphael k3b: resmgr: server response code 502 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:08 raphael kernel: isofs_fill_super: bread failed, dev=hdd, iso_blknum=16, block=16 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=1252, limit=4 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=1028, limit=4 Mar 11 15:03:08 raphael kernel: UDF-fs: No partition found (1) Mar 11 15:03:08 raphael submountd: mount failure, Invalid argument Mar 11 15:03:08 raphael kernel: subfs: unsuccessful attempt to mount media (256) Mar 11 15:03:08 raphael kernel: ISO 9660 Extensions: RRIP_1991A Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:09 raphael kernel: isofs_fill_super: bread failed, dev=hdd, iso_blknum=16, block=16 Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=1252, limit=4 Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=1028, limit=4 Mar 11 15:03:09 raphael kernel: UDF-fs: No partition found (1) Mar 11 15:03:09 raphael submountd: mount failure, Invalid argument Mar 11 15:03:09 raphael kernel: subfs: unsuccessful attempt to mount media (256) Please advise and thanks in advance! -- Cheers, wmeler
Here is some more information...this is what happens when I start k3b...this hopefully provides a clue: k3b: (K3bPluginFactory) creating K3bPluginFactory. k3b: (K3bPluginFactory) creating K3bPluginFactory. k3b: (K3bPluginFactory) creating K3bPluginFactory. k3b: (K3bPluginFactory) creating K3bPluginFactory. k3b: (K3bPluginFactory) creating K3bPluginFactory. k3b: (K3bPluginFactory) creating K3bPluginFactory. k3b: (K3bPluginFactory) creating K3bPluginFactory. k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, suidroot, plain-atapi, hacked-atapi k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, suidroot, plain-atapi, hacked-atapi k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version >= 1.11a02, using burnfree instead of burnproof k3b: (K3bExternalBinManager) seems to be cdrecord version >= 1.11a31, support for Just Link via burnfree driveroption k3b: /dev/hdd resolved to /dev/hdd k3b: (K3bDevice::Device) resmgr open: -1 k3b: /dev/hdd is block device (64) k3b: /dev/hdd seems to be cdrom k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice) /dev/hdd: init() k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: GET CONFIGURATION (46) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 20 k3b: ascq: 0 k3b: (K3bCdDevice) /dev/hdd: GET_CONFIGURATION failed. k3b: (K3bCdDevice::CdDevice) /dev/hdd: dataLen: 60 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: MODE SELECT (55) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 26 k3b: ascq: 0 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: MODE SELECT (55) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 26 k3b: ascq: 0 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: MODE SELECT (55) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 26 k3b: ascq: 0 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: GET PERFORMANCE (ac) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 20 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/hdd: GET PERFORMANCE length det failed. k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/hdd: MODE SENSE length det failed. k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) setting current write speed of device /dev/hdd to 706 k3b: /dev/hdc resolved to /dev/hdc k3b: (K3bDevice::Device) resmgr open: -1 k3b: /dev/hdc is block device (0) k3b: /dev/hdc seems to be cdrom k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice) /dev/hdc: init() k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bCdDevice) /dev/hdc: GET_CONFIGURATION length: 84. k3b: (K3bCdDevice) /dev/hdc feature: Core k3b: (K3bCdDevice) /dev/hdc feature: Morphing k3b: (K3bCdDevice) /dev/hdc feature: Removable Medium k3b: (K3bCdDevice) /dev/hdc feature: Random Readable k3b: (K3bCdDevice) /dev/hdc feature: CD Read k3b: (K3bCdDevice) /dev/hdc feature: Power Management k3b: (K3bCdDevice) /dev/hdc feature: Timeout k3b: (K3bCdDevice) /dev/hdc: unknown feature: -34 k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/hdc: MODE SENSE length det failed. k3b: (K3bCdDevice::CdDevice) /dev/hdc: modeSense 0x05 failed! k3b: (K3bCdDevice::CdDevice) /dev/hdc: Cannot check write modes. k3b: (K3bCdDevice::ScsiCommand) failed: fd: 13 k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/hdc: MODE SENSE length det failed. k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) Link: /dev/disk/by-id/Lite-On_LTN486S_48x_Ma -> /dev/hdc k3b: (K3bDeviceManager) Link: /dev/disk/by-id/CD-RW_CRX100 -> /dev/hdd k3b: (K3bDeviceManager) Link: /dev/cdrom -> /dev/hdc k3b: (K3bDeviceManager) Link: /dev/cdrecorder -> /dev/hdd k3b: (K3bDevice::DeviceManager) SCANNING FOR GENERIC DEVICES. k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg0for reading k3b: could not open device /dev/sg0 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg1for reading k3b: could not open device /dev/sg1 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg2for reading k3b: could not open device /dev/sg2 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg3for reading k3b: could not open device /dev/sg3 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg4for reading k3b: could not open device /dev/sg4 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg5for reading k3b: could not open device /dev/sg5 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg6for reading k3b: could not open device /dev/sg6 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg7for reading k3b: could not open device /dev/sg7 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg8for reading k3b: could not open device /dev/sg8 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg9for reading k3b: could not open device /dev/sg9 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg10for reading k3b: could not open device /dev/sg10 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg11for reading k3b: could not open device /dev/sg11 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg12for reading k3b: could not open device /dev/sg12 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg13for reading k3b: could not open device /dev/sg13 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg14for reading k3b: could not open device /dev/sg14 (No such device or address) k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sg15for reading k3b: could not open device /dev/sg15 (No such device or address) k3b: (K3bDeviceManager) scanning fstab: /dev/hda2 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: /dev/hdb1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: /dev/sda1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sda1for reading k3b: could not open device /dev/sda1 (No such device or address) k3b: (K3bDeviceManager) scanning fstab: /dev/hda1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: devpts k3b: Could not resolve devpts k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device devptsfor reading k3b: could not open device devpts (No such file or directory) k3b: (K3bDeviceManager) scanning fstab: proc k3b: Could not resolve proc k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device procfor reading k3b: could not open device proc (No such file or directory) k3b: (K3bDeviceManager) scanning fstab: usbdevfs k3b: Could not resolve usbdevfs k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device usbdevfsfor reading k3b: could not open device usbdevfs (No such file or directory) k3b: (K3bDeviceManager) scanning fstab: /dev/cdrecorder k3b: (K3bDeviceManager) found device for /dev/cdrecorder: /dev/hdd k3b: (K3bDeviceManager) scanning fstab: /dev/cdrom k3b: (K3bDeviceManager) found device for /dev/cdrom: /dev/hdc k3b: (K3bDeviceManager) scanning fstab: /dev/fd0 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: /dev/sda1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sda1for reading k3b: could not open device /dev/sda1 (No such device or address) k3b: /dev/hdd resolved to /dev/hdd k3b: (K3bDevice::Device) resmgr open: -1 k3b: /dev/hdd is block device (64) k3b: /dev/hdd seems to be cdrom k3b: (K3bDeviceManager) dev /dev/hdd already found k3b: /dev/hdc resolved to /dev/hdc k3b: (K3bDevice::Device) resmgr open: -1 k3b: /dev/hdc is block device (0) k3b: /dev/hdc seems to be cdrom k3b: (K3bDeviceManager) dev /dev/hdc already found k3b: (K3bDeviceManager) found config entry for devicetype: SONY CD-RW CRX100E k3b: (K3bDeviceManager) found config entry for devicetype: Lite-On LTN486S 48x Max k3b: (K3bDeviceManager) scanning fstab: /dev/hda2 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: /dev/hdb1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: /dev/sda1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sda1for reading k3b: could not open device /dev/sda1 (No such device or address) k3b: (K3bDeviceManager) scanning fstab: /dev/hda1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: devpts k3b: Could not resolve devpts k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device devptsfor reading k3b: could not open device devpts (No such file or directory) k3b: (K3bDeviceManager) scanning fstab: proc k3b: Could not resolve proc k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device procfor reading k3b: could not open device proc (No such file or directory) k3b: (K3bDeviceManager) scanning fstab: usbdevfs k3b: Could not resolve usbdevfs k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device usbdevfsfor reading k3b: could not open device usbdevfs (No such file or directory) k3b: (K3bDeviceManager) scanning fstab: /dev/cdrecorder k3b: (K3bDeviceManager) found device for /dev/cdrecorder: /dev/hdd k3b: (K3bDeviceManager) scanning fstab: /dev/cdrom k3b: (K3bDeviceManager) found device for /dev/cdrom: /dev/hdc k3b: (K3bDeviceManager) scanning fstab: /dev/fd0 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDeviceManager) scanning fstab: /dev/sda1 k3b: (K3bDevice::Device) resmgr open: -1 k3b: (K3bDevice::Device) Error: could not open device /dev/sda1for reading k3b: could not open device /dev/sda1 (No such device or address) k3b: Devices: k3b: ------------------------------ k3b: Blockdevice: /dev/hdd k3b: Vendor: SONY k3b: Description: CD-RW CRX100E k3b: Version: 2.0h k3b: MountDevice: /dev/cdrecorder k3b: Mountpoint: /media/cdrecorder k3b: Write speed: 700 k3b: Profiles: Error k3b: Devicetype: CD-R; CD-RW; CD-ROM k3b: Writing modes: SAO; TAO k3b: Reader aliases: /dev/hdd, /dev/disk/by-id/CD-RW_CRX100, /dev/cdrecorder k3b: ------------------------------ k3b: Blockdevice: /dev/hdc k3b: Vendor: Lite-On k3b: Description: LTN486S 48x Max k3b: Version: YDS6 k3b: MountDevice: /dev/cdrom k3b: Mountpoint: /media/cdrom k3b: Write speed: 0 k3b: Profiles: CD-ROM k3b: Devicetype: CD-ROM k3b: Writing modes: None k3b: Reader aliases: /dev/hdc, /dev/disk/by-id/Lite-On_LTN486S_48x_Ma, /dev/cdrom k3b: ------------------------------ k3b: Version: 1.0 k3b: WARNING: KGenericFactory: instance requested but no instance name or aboutdata passed to the constructor! k3b: (K3b::cutToWidth) not able to cut text to 1! On Fri, 11 Mar 2005 15:24:51 -0500, wmeler <wmeler@gmail.com> wrote:
I installed a version of k3b 11.20-3 and now my machine doesn't know how to burn. In k3b it says "no burner found" or something to that effect (even though I can se the burner in k3b setup. Also, I can see the burner under Hardware Information in Yast and under the CD-ROM option.
I get the follow when I do a "cat /var/log/messages" and I believe this is why my burner no longer works. This is after restarting the machine so this is mostly from the boot process itself:
Mar 11 14:58:41 raphael kernel: subfs: unsuccessful attempt to mount media (256) Mar 11 14:59:01 raphael /usr/sbin/cron[6347]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Mar 11 15:02:13 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:15 raphael last message repeated 41 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:15 raphael last message repeated 2 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:15 raphael last message repeated 7 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:15 raphael last message repeated 2 times Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:15 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:54 raphael last message repeated 42 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:54 raphael last message repeated 2 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:54 raphael last message repeated 7 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 501 Mar 11 15:02:54 raphael last message repeated 2 times Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 502 Mar 11 15:02:54 raphael kcmshell: resmgr: server response code 502 Mar 11 15:03:06 raphael k3b: resmgr: server response code 502 Mar 11 15:03:07 raphael last message repeated 41 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 501 Mar 11 15:03:07 raphael last message repeated 2 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 502 Mar 11 15:03:07 raphael last message repeated 7 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 501 Mar 11 15:03:07 raphael last message repeated 2 times Mar 11 15:03:07 raphael k3b: resmgr: server response code 502 Mar 11 15:03:07 raphael k3b: resmgr: server response code 502 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:08 raphael kernel: isofs_fill_super: bread failed, dev=hdd, iso_blknum=16, block=16 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=1252, limit=4 Mar 11 15:03:08 raphael kernel: attempt to access beyond end of device Mar 11 15:03:08 raphael kernel: hdd: rw=0, want=1028, limit=4 Mar 11 15:03:08 raphael kernel: UDF-fs: No partition found (1) Mar 11 15:03:08 raphael submountd: mount failure, Invalid argument Mar 11 15:03:08 raphael kernel: subfs: unsuccessful attempt to mount media (256) Mar 11 15:03:08 raphael kernel: ISO 9660 Extensions: RRIP_1991A Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:09 raphael kernel: isofs_fill_super: bread failed, dev=hdd, iso_blknum=16, block=16 Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=68, limit=4 Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=1252, limit=4 Mar 11 15:03:09 raphael kernel: attempt to access beyond end of device Mar 11 15:03:09 raphael kernel: hdd: rw=0, want=1028, limit=4 Mar 11 15:03:09 raphael kernel: UDF-fs: No partition found (1) Mar 11 15:03:09 raphael submountd: mount failure, Invalid argument Mar 11 15:03:09 raphael kernel: subfs: unsuccessful attempt to mount media (256)
Please advise and thanks in advance!
-- Cheers, wmeler
-- Cheers, wmeler
wmeler wrote:
k3b: /dev/hdd resolved to /dev/hdd k3b: (K3bDevice::Device) resmgr open: -1 k3b: /dev/hdd is block device (64) k3b: /dev/hdd seems to be cdrom
What does ls -l /dev/cdr* /dev/dvd* give you. I just fixed mine last night and learned resmgr acts on the links, and if they are not there, it doesn't change the permissions to allow your user access to the cdrom.
k3b: /dev/hdc is block device (0) k3b: /dev/hdc seems to be cdrom k3b: (K3bDeviceManager) Link: /dev/cdrom -> /dev/hdc k3b: (K3bDeviceManager) Link: /dev/cdrecorder -> /dev/hdd
Are these links there?
k3b: (K3bDevice::DeviceManager) SCANNING FOR GENERIC DEVICES.
What does /sbin/resmgr list show (as user)? -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
1) as user or root: ~> ls -l /dev/cdr* /dev/dvd* /bin/ls: /dev/dvd*: No such file or directory lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrecorder -> hdd lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrom -> hdc 2) as user or root: /sbin/resmgr does not do *anything*. it just sits there until i CTRL-C it to death. 3) k3b does not work as root either...complains about not knowing about the drive still, even though it seems to see it when i run k3b_setup no idea what is going on, wmeler On Fri, 11 Mar 2005 17:14:15 -0600, Joe Morris (NTM) <Joe_Morris@ntm.org> wrote:
wmeler wrote:
k3b: /dev/hdd resolved to /dev/hdd k3b: (K3bDevice::Device) resmgr open: -1 k3b: /dev/hdd is block device (64) k3b: /dev/hdd seems to be cdrom
What does ls -l /dev/cdr* /dev/dvd* give you. I just fixed mine last night and learned resmgr acts on the links, and if they are not there, it doesn't change the permissions to allow your user access to the cdrom.
k3b: /dev/hdc is block device (0) k3b: /dev/hdc seems to be cdrom k3b: (K3bDeviceManager) Link: /dev/cdrom -> /dev/hdc k3b: (K3bDeviceManager) Link: /dev/cdrecorder -> /dev/hdd
Are these links there?
k3b: (K3bDevice::DeviceManager) SCANNING FOR GENERIC DEVICES.
What does /sbin/resmgr list show (as user)? -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Cheers, wmeler
wmeler wrote:
lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrecorder -> hdd lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrom -> hdc
OK, what does "ls -l /dev/hdc /dev/hdd" give you?
2) as user or root: /sbin/resmgr does not do *anything*.
No, that was "/sbin/resmgr list".
3) k3b does not work as root either...complains about not knowing about the drive still, even though it seems to see it when i run k3b_setup
Hopefully the above commands should give us some clues. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe, answers below...thanks... On Tue, 15 Mar 2005 22:09:59 -0600, Joe Morris (NTM) <Joe_Morris@ntm.org> wrote:
wmeler wrote:
lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrecorder -> hdd lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrom -> hdc
OK, what does "ls -l /dev/hdc /dev/hdd" give you?
YES
2) as user or root: /sbin/resmgr does not do *anything*.
No, that was "/sbin/resmgr list".
output: ~> /sbin/resmgr list rw-- /dev/audio rw-- /dev/mixer rw-- /dev/dsp rw-- /dev/sequencer rw-- /dev/video rw-- /dev/modem rw-p /dev/cdrom rw-p /dev/cdrom1 rw-- /dev/cdrecorder rw-p /dev/dvd rw-p /dev/dvd1 rw-- /dev/sr0 rw-- /dev/sr1 rw-- /dev/sr2 rw-- /dev/sr3 rws- /dev/scanner r--- /dev/console rw-- /dev/pilot rw-- usb:any
3) k3b does not work as root either...complains about not knowing about the drive still, even though it seems to see it when i run k3b_setup
Hopefully the above commands should give us some clues. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Cheers, wmeler
wmeler wrote:
On Tue, 15 Mar 2005 22:09:59 -0600, Joe Morris (NTM) <Joe_Morris@ntm.org> wrote:
OK, what does "ls -l /dev/hdc /dev/hdd" give you?
YES
We are having a little communication gap. ls -l /dev/hdc /dev/hdd should not give you YES. I am asking you to type the above in a console, hit enter, then copy/paste the result in the reply.
No, that was "/sbin/resmgr list".
output: ~> /sbin/resmgr list rw-- /dev/audio rw-- /dev/mixer rw-- /dev/dsp rw-- /dev/sequencer rw-- /dev/video rw-- /dev/modem rw-p /dev/cdrom rw-p /dev/cdrom1 rw-- /dev/cdrecorder rw-p /dev/dvd rw-p /dev/dvd1 rw-- /dev/sr0 rw-- /dev/sr1 rw-- /dev/sr2 rw-- /dev/sr3 rws- /dev/scanner r--- /dev/console rw-- /dev/pilot rw-- usb:any
That looks OK. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
OK, what does "ls -l /dev/hdc /dev/hdd" give you?
~> ls -l /dev/hdc /dev/hdd brw------- 1 wmeler disk 22, 0 2004-12-03 13:50 /dev/hdc brw------- 1 wmeler disk 22, 64 2004-12-03 13:50 /dev/hdd Sorry about the confusion, but it seems okay to me. wmeler
Can someone please help me? My burner is still not working. HELP PLEASE! Thanks, wmeler On Thu, 17 Mar 2005 19:10:45 -0500, wmeler <wmeler@gmail.com> wrote:
OK, what does "ls -l /dev/hdc /dev/hdd" give you?
~> ls -l /dev/hdc /dev/hdd brw------- 1 wmeler disk 22, 0 2004-12-03 13:50 /dev/hdc brw------- 1 wmeler disk 22, 64 2004-12-03 13:50 /dev/hdd
wmeler
-- Cheers, wmeler
My DVD/CD-RW is listed as # ls -l /dev/hda brw------- 1 rich disk 3, 0 2004-10-02 04:38 /dev/hda k3b works fine with it. The 3,0 is the major/minor device number .... /dev/dvd is linked to /dev/hda on my system. That does not look to be the problem. I did have an issue under FC1 k3b - there was something else I had to do - and I'm drawing a blank right now. HTH Rich On Fri, 2005-03-25 at 10:00 -0500, wmeler wrote:
Can someone please help me? My burner is still not working.
HELP PLEASE!
Thanks, wmeler
On Thu, 17 Mar 2005 19:10:45 -0500, wmeler <wmeler@gmail.com> wrote:
OK, what does "ls -l /dev/hdc /dev/hdd" give you?
~> ls -l /dev/hdc /dev/hdd brw------- 1 wmeler disk 22, 0 2004-12-03 13:50 /dev/hdc brw------- 1 wmeler disk 22, 64 2004-12-03 13:50 /dev/hdd
wmeler
-- Cheers, wmeler
-- Remember, all Windows-based machines are, by definition, fault tolerant. They run Windows don't they?!?!?!?
I still have no idea what the problem is. Someone please help me! wmeler
The Saturday 2005-03-26 at 00:58 -0500, wmeler wrote:
I still have no idea what the problem is.
I'm not familiar with k3b, I prefer xcdroast. I understand you installed a new version, and it has problems with resmgr. Why not revert to the original shiped by SuSE? -- Cheers, Carlos Robinson
I tried to re-install k3b. Yast says that the old version is available, however, when I select it for update it says "Package k3b-11.19.0.pm.0.i586 was not found on the medium." When I click on more details it says "Err: 11283:ERROR(Media:file not found)". I originally installed Suse 9.2 over the network using a single ISO image (not the DVD). I used to be able to install stuff just fine with Yast, but all of a sudden it's not working. On Mar 26, 2005 7:33 AM, Carlos E. R. <robin1.listas@tiscali.es> wrote:
I'm not familiar with k3b, I prefer xcdroast. I understand you installed a new version, and it has problems with resmgr. Why not revert to the original shiped by SuSE?
-- Cheers, Carlos Robinson
The Wednesday 2005-04-06 at 00:37 -0400, wmeler wrote:
I tried to re-install k3b. Yast says that the old version is available, however, when I select it for update it says "Package k3b-11.19.0.pm.0.i586 was not found on the medium." When I click on more details it says "Err: 11283:ERROR(Media:file not found)".
I don't know, but you can always install manually using "rpm". Probably you will have to add --oldpackage or similar, check the man page.
I originally installed Suse 9.2 over the network using a single ISO image (not the DVD). I used to be able to install stuff just fine with Yast, but all of a sudden it's not working.
That's a diferent problem. You may have changed something, installed something that broke Yast, I don't know now. -- Cheers, Carlos Robinson
On Tue, Mar 15, 2005 at 09:39:13PM -0500, wmeler wrote:
1) as user or root: ~> ls -l /dev/cdr* /dev/dvd* /bin/ls: /dev/dvd*: No such file or directory lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrecorder -> hdd lrwxrwxrwx 1 root root 3 2005-01-27 20:53 /dev/cdrom -> hdc
2) as user or root: /sbin/resmgr does not do *anything*. it just sits there until i CTRL-C it to death.
You were asked to run "/sbin/resmgr list". /sbin/resmgr just waits for input from stdin. Ciao, Marcus
Marcus Meissner wrote:
You were asked to run "/sbin/resmgr list". /sbin/resmgr just waits for input from stdin.
Ciao, Marcus
resmgr(1) NAME resmgr - resource manager client SYNOPSIS resmgr [-s socket] [-u user] [-t] command ... DESCRIPTION The resmgr command is a command line client for the resource manager daemon resmgrd(8). It passes the specified command to the daemon, and prints the response. Mark
Mark Hounschell <dmarkh@cfl.rr.com> [Wed, 16 Mar 2005 04:20:14 -0500]:
NAME resmgr - resource manager client
And you wanted to tell us what? Sorry, but posting a man page is neither question nor answer and you didn't send anything else. Philipp
participants (7)
-
Carlos E. R. -
Joe Morris (NTM) -
Marcus Meissner -
Mark Hounschell -
Philipp Thomas -
Rich Goodwin -
wmeler