SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This hardware works like champ in windows, unfortunatly after a migration to Slackware10.2 it fails to work even the basic functions
The first problem I like to mention is it seems that it doesn't want to eject. The result of eject -v gave the following
Code:
arvel@northstar:~$ eject -v
eject: using default device `cdrom'
eject: device name is `cdrom'
eject: expanded name is `/dev/cdrom'
eject: `/dev/cdrom' is a link to `/dev/hdc'
eject: `/dev/hdc' is not mounted
eject: `/dev/hdc' is not a mount point
eject: `/dev/hdc' is a multipartition device
eject: trying to eject `/dev/hdc' using CD-ROM eject command
eject: CD-ROM eject command failed
eject: trying to eject `/dev/hdc' using SCSI commands
eject: SCSI eject failed
eject: trying to eject `/dev/hdc' using floppy eject command
eject: floppy eject command failed
eject: trying to eject `/dev/hdc' using tape offline command
eject: tape offline command failed
eject: unable to eject, last error: Invalid argument
marvel@northstar:~$
Suggestions in this board is to gave chmod 666 /dev/cdrom. I followed the instruction but the error still occurs. No matter as root or normal user. Is this partically burner model BENQ DW16/40 has compatibility probelm with linux?
strangly, when I gave a command dmesg, (while I got a disk stuck up in the drive) yeilded for following result. Is this related to the problem?
Code:
ide: failed opcode was: unknown
hdc: drive not ready for command
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdc: drive not ready for command
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdc: drive not ready for command
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdc: drive not ready for command
hdc: ATAPI reset complete
marvel@northstar:~$
You have something strange going on there in Slack mine works fine in Debian.
Code:
>$ eject -v /dev/hdd
eject: device name is `/dev/hdd'
eject: expanded name is `/dev/hdd'
eject: `/dev/hdd' is not mounted
eject: `/dev/hdd' is not a mount point
eject: `/dev/hdd' is a multipartition device
eject: trying to eject `/dev/hdd' using CD-ROM eject command
eject: CD-ROM eject command succeeded
Now in Debian you have to be in the cdrom group to access is there such a thing in Slack that maybe you have to use as well?
That second part looks like dma errors what does the following commands tell you.
Do you get the dma in both after a fresh bootup? Again in Debian I had to install the hdparm program and enable the dma on mine otherwise the burning speed sucked. Another thing you may want to check/consider is if you have the burner on an old cdrom cable you might want to put a newer 80 pin cable in there.
Your dma is not being set use hdparm -c1 -u1 -d1 /dev/hdc that will give you the same settings I use you should put this command in a startup script or if the Slack setup is like Debian it is set in a config file /etc/hdparm.conf.
thanks, I've given the suggested command hdparm -c1 -u1 -d1 /dev/hdc and now I got the same resualt as you.
Code:
root@northstar:/home/marvel# hdparm -c1 -u1 -d1 /dev/hdc
/dev/hdc:
setting 32-bit IO_support flag to 1
setting unmaskirq to 1 (on)
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 0 (off)
root@northstar:/home/marvel#
But.... it still doesn't want to eject the cdrom
Code:
root@northstar:/home/marvel# eject -v /dev/hdc
eject: device name is `/dev/hdc'
eject: expanded name is `/dev/hdc'
eject: `/dev/hdc' is not mounted
eject: `/dev/hdc' is not a mount point
eject: `/dev/hdc' is a multipartition device
eject: trying to eject `/dev/hdc' using CD-ROM eject command
eject: CD-ROM eject command failed
eject: trying to eject `/dev/hdc' using SCSI commands
eject: SCSI eject failed
eject: trying to eject `/dev/hdc' using floppy eject command
eject: floppy eject command failed
eject: trying to eject `/dev/hdc' using tape offline command
eject: tape offline command failed
eject: unable to eject, last error: Invalid argument
root@northstar:/home/marvel#
Details: Since I made the jugment based on a set of funky CDroms a friend of mine burned for me on his Windows machine - possibly a multi session disk or some thing that linux might not like. I can sucessfully burned CD in linux with k3b at high speed. Then be able to mount it, umount and eject all very smoothly now. This is a user fault. Thanks so much
Well, I hate to say this, but actually, the problem is still there. I was tricked into beleaving that the problem lies in the disk (hence previous post), but the drive is still not yet functional. This time I can't read from a newly bought Quake4 DVD :-(
HappyTux, what kernel are you using? 2.4 or 2.6. I've been told that 2.6's DVD burner compatibility is broken.... ? I'm now on 2.6.13 going to try downgrade to 2.4 this weekend.
HappyTux, what kernel are you using? 2.4 or 2.6. I've been told that 2.6's DVD burner compatibility is broken.... ? I'm now on 2.6.13 going to try downgrade to 2.4 this weekend.
I'm using 2.6.12 with the Con Kolivas kernel patch 2.6.12-ck6 the burning or anything else for that matter works fine here I burn dvd on a regular basis and use the IDE not IDE-SCSI for the access so my drive shows up as /dev/hd? not a /dev/sd?.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.