| View previous topic :: View next topic |
| Author |
Message |
sanddv
n00b
Joined: 22 Jan 2008
Posts: 13
Location: Tunis
|
 Posted: Tue Jan 22, 2008 4:41 pm Post subject: Problem to eject dvd |
 |
|
Hi,
I've a problem to eject my dvd ; I don't know if a dvd is in my drive, I can't mount it :
| Code: | linux ~ # mount /dev/hdc
mount: Aucun medium trouvé
|
And nothing appends while I try to eject it (no error message).
I also tried to eject it with cdrecord command :
| Code: | linux ~ # cdrecord -eject dev=1001,0,0
Cdrecord-ProDVD-Clone 2.01.01a25 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling
scsidev: '1001,0,0'
scsibus: 1001 target: 0 lun: 0
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'DVD RW 8XMax '
Revision : '140D'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
cdrecord: Success. start/stop unit: scsi sendcmd: no error
CDB: 1B 00 00 00 02 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.003s timeout 40s
cdrecord: Cannot eject media.
|
I can give you hdparm command result :
| Code: | linux ~ # hdparm /dev/hdc
/dev/hdc:
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
|
Can somebody help me ?
Sandrine |
|
| Back to top |
|
 |
piewie
Guru
Joined: 26 Sep 2002
Posts: 489
Location: old Europe
|
| Posted: Tue Jan 22, 2008 6:52 pm Post subject: |
|
|
| Quote: | linux ~ # mount /dev/hdc
mount: Aucun medium trouvé |
French error messages do not really help in an English forum.
| Quote: | | cdrecord dev=1001,0,0 -eject |
You should decide, if you have a scsi or an ide drive or if you are using ide-scsi emulation.
Your cdrtools are old like a stone.
dmesg | grep CD-ROM
cdrecord dev=ATA -scanbus (for IDE)
cdrecord -scanbus (for SCSI or one-drive systems)
cdrecord dev=ATA:x,y,z -minfo (for media-info in IDE drives - apply scanbus output)
Check your mainboard chipset and current kernel
Device Drivers ---> Serial ATA (prod) and Parallel ATA (experimental) drivers
for your chipset support. Probably you can switch to a PATA. |
|
| Back to top |
|
|
schachti
Advocate
Joined: 28 Jul 2003
Posts: 3765
Location: Gifhorn, Germany
|
| Posted: Tue Jan 22, 2008 8:25 pm Post subject: |
|
|
| piewie wrote: | | Quote: | linux ~ # mount /dev/hdc
mount: Aucun medium trouvé |
French error messages do not really help in an English forum.
|
If I remember correctly, it means "no medium found" or something similar (I only had French in school, and that's quite a few years ago  ).
_________________
Never argue with an idiot. He brings you down to his level, then beats you with experience.
How-To: Daten verschlüsselt auf DVD speichern. |
|
| Back to top |
|
|
piewie
Guru
Joined: 26 Sep 2002
Posts: 489
Location: old Europe
|
| Posted: Wed Jan 23, 2008 12:44 am Post subject: |
|
|
Which would mean, that hdc is not the correct name for the device. So let's wait at least for: | Code: | | dmesg | grep CD-ROM |
|
|
| Back to top |
|
|
sanddv
n00b
Joined: 22 Jan 2008
Posts: 13
Location: Tunis
|
| Posted: Wed Jan 23, 2008 7:45 am Post subject: |
|
|
Thank for your responses.
So :
| Code: | linux ~ # dmesg | grep CD
hdc: ATAPI DVD RW 8XMax, ATAPI CD/DVD-ROM drive
hdd: LTN486S, ATAPI CD/DVD-ROM drive
hdc: ATAPI 63X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X CD-ROM drive, 120kB Cache, DMA
|
And :
| Code: | linux ~ # cdrecord dev=ATA:1001,0,0 -minfo
Cdrecord-ProDVD-Clone 2.01.01a25 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling
scsidev: 'ATA:1001,0,0'
devname: 'ATA'
scsibus: 1001 target: 0 lun: 0
Warning: Using badly designed ATAPI via /dev/hd* interface.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'DVD RW 8XMax '
Revision : '140D'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
cdrecord: CD/DVD-Recorder not ready.
|
Is there something strange ?
I'm sorry, I've "some" (a lot of !) gaps in my linux skills, I look for technical documentations at the same time I post questions. Thank for your help. (and sorry for my bad english ; still these **** of gaps !). |
|
| Back to top |
|
|
piewie
Guru
Joined: 26 Sep 2002
Posts: 489
Location: old Europe
|
| Posted: Wed Jan 23, 2008 1:05 pm Post subject: |
|
|
Keep cool, we are all just a collection of many gaps.  | Quote: | | cdrecord: CD/DVD-Recorder not ready. |
looks not good to me.
| Quote: | hdc: ATAPI DVD RW 8XMax, ATAPI CD/DVD-ROM drive
hdc: ATAPI 63X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) |
kernel seems not to be able to recognize the drive manufacturer. (what manufacturer, what kernel?) I would search for a firmware update.
Can you read a written cd/dvd in hdd/hdc? Is your LiteOn drive working fine?
# cdrecord dev=ATA:1001,0,0 -prcap
# cdrecord dev=ATA:1001,1,0 -prcap
Before we get more technical, we should ensure that some basics are fullfilled to exclude some basic errors:
update cdrtools (current version is a37)
use 80pol semiconductor cable
update firmware
ensure that the drive is not defective
boot a live linux cd/dvd to check drive's functionality
try different media manufacturers |
|
| Back to top |
|
|
piewie
Guru
Joined: 26 Sep 2002
Posts: 489
Location: old Europe
|
| Posted: Wed Jan 23, 2008 1:39 pm Post subject: |
|
|
By the way:
cdrecord dev=ATA:x,y,z -eject is not ejecting media on my notebook with old ide driver.:
| Code: | | cdrecord: Sorry, no supported CD/DVD/BD-Recorder found on this target |
Since the -eject command is working fine with my PATA driver, this seems to be an ide driver problem. Probably you should look for
eject /dev/hdc (how about eject /dev/hdd?) Do you get some output in /var/log/messages?
Update cdrtools to a37 to see if we get identical error messages, before I report this bug to Jörg. |
|
| Back to top |
|
|
sanddv
n00b
Joined: 22 Jan 2008
Posts: 13
Location: Tunis
|
| Posted: Thu Jan 24, 2008 10:31 am Post subject: |
|
|
A really big collection of many gaps is back !
I tried to update cdrtools, I get a message to update glibc, so I did :
| Code: | | emerge --update glibc |
... 4 packets well emerged, and ...
| Code: | | >>> Emerging (5 of 5) sys-libs/glibc-2.6.1 to |
... many emerging messages, and ...
| Code: | checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc
checking version of i686-pc-linux-gnu-gcc... 3.3.6, bad
checking for gnumake... no
checking for gmake... gmake
checking version of gmake... 3.81, ok
checking for gnumsgfmt... no
checking for gmsgfmt... gmsgfmt
checking version of gmsgfmt... 0.17, ok
checking for makeinfo... makeinfo
checking version of makeinfo... 4.8, ok
checking for sed... sed
checking version of sed... 4.1.5, ok
checking for autoconf... autoconf
checking whether autoconf works... yes
configure: error:
*** These critical programs are missing or too old: gcc
*** Check the INSTALL file for required versions.
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* glibc-2.6.1.ebuild, line 155: Called eblit-run 'src_compile'
* glibc-2.6.1.ebuild, line 150: Called eblit-glibc-src_compile
* src_compile.eblit, line 179: Called toolchain-glibc_src_compile
* src_compile.eblit, line 120: Called glibc_do_configure 'nptl'
* src_compile.eblit, line 97: Called die
* The specific snippet of code:
* "${S}"/configure ${myconf} || die "failed to configure glibc"
* The die message:
* failed to configure glibc
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/portage/sys-libs/glibc-2.6.1/temp/build.log'.
*
* Regenerating GNU info directory index...
* Processed 5 info files.
* IMPORTANT: 3 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files. |
So I emerged gcc to, without problem (only a little bit time), and I new tried to emerge glibc, and I get the same error message.
What can I do ? Now I start looking for the way to emerge glibc, tell me if I do wrong. |
|
| Back to top |
|
|
piewie
Guru
Joined: 26 Sep 2002
Posts: 489
Location: old Europe
|
| Posted: Fri Jan 25, 2008 7:20 am Post subject: |
|
|
| Code: | echo "app-cdr/cdrtools" >> /etc/portage/package.keywords
emerge -uvD cdrtools |
If this fails, probably a | Code: | emerge --sync
emerge -uvD system |
is necessary before. If this all fails: | Code: | emerge gentoolkit
revdep-rebuild |
and start from the beginning. |
|
| Back to top |
|
|
sanddv
n00b
Joined: 22 Jan 2008
Posts: 13
Location: Tunis
|
| Posted: Fri Jan 25, 2008 10:03 am Post subject: |
|
|
| Code: | echo "app-cdr/cdrtools" >> /etc/portage/package.keywords
emerge -uvD cdrtools |
I get the same last error messages :
| Code: | configure: error:
*** These critical programs are missing or too old: gcc
*** Check the INSTALL file for required versions.
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* glibc-2.6.1.ebuild, line 155: Called eblit-run 'src_compile'
* glibc-2.6.1.ebuild, line 150: Called eblit-glibc-src_compile
* src_compile.eblit, line 179: Called toolchain-glibc_src_compile
* src_compile.eblit, line 120: Called glibc_do_configure 'nptl'
* src_compile.eblit, line 97: Called die
* The specific snippet of code:
* "${S}"/configure ${myconf} || die "failed to configure glibc"
* The die message:
* failed to configure glibc
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/portage/sys-libs/glibc-2.6.1/temp/build.log'.
*
* GNU info directory index is up-to-date.
* IMPORTANT: 3 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files. |
Now I try the second way, see you soon. |
|
| Back to top |
|
|
sanddv
n00b
Joined: 22 Jan 2008
Posts: 13
Location: Tunis
|
| Posted: Fri Jan 25, 2008 10:34 am Post subject: |
|
|
...
finish with following messages :
| Code: | Number of files: 131497
Number of files transferred: 1074
Total file size: 175798315 bytes
Total transferred file size: 4216193 bytes
Literal data: 4216193 bytes
Matched data: 0 bytes
File list size: 3193957
File list generation time: 418.073 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 28233
Total bytes received: 4682329
sent 28233 bytes received 4682329 bytes 7831.36 bytes/sec
total size is 175798315 speedup is 37.32
>>> Updating Portage cache: 100%
* IMPORTANT: 3 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
q: Updating ebuild cache ...
q: Finished 25302 entries in 28.153646 seconds |
and
with... same error messages :
| Code: | configure: error:
*** These critical programs are missing or too old: gcc
*** Check the INSTALL file for required versions.
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* glibc-2.6.1.ebuild, line 155: Called eblit-run 'src_compile'
* glibc-2.6.1.ebuild, line 150: Called eblit-glibc-src_compile
* src_compile.eblit, line 179: Called toolchain-glibc_src_compile
* src_compile.eblit, line 120: Called glibc_do_configure 'nptl'
* src_compile.eblit, line 97: Called die
* The specific snippet of code:
* "${S}"/configure ${myconf} || die "failed to configure glibc"
* The die message:
* failed to configure glibc
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/portage/sys-libs/glibc-2.6.1/temp/build.log'.
*
* Regenerating GNU info directory index...
* Processed 137 info files.
* IMPORTANT: 24 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files. |
I start the last solution. |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5934
|
|
| Back to top |
|
|
sanddv
n00b
Joined: 22 Jan 2008
Posts: 13
Location: Tunis
|
| Posted: Mon Jan 28, 2008 3:28 pm Post subject: |
|
|
Thanks, Bunder, this doc helped me ; my cdrtools and all dependencies are now updated.
So, I tried to eject hdd and hdc with 2 methods seen before :
and
| Code: | # cdrecord dev=1001,1,0 -eject
Cdrecord-ProDVD-ProBD-Clone 2.01.01a36 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling
scsidev: '1001,1,0'
scsibus: 1001 target: 1 lun: 0
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
cdrecord: Warning: controller returns wrong size for CD capabilities page.
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'COMPAQ '
Identifikation : 'CD-ROM LTN486S '
Revision : 'YQS8'
Device seems to be: Generic mmc CD-ROM.
cdrecord: Warning: controller returns wrong size for CD capabilities page.
cdrecord: Warning: controller returns wrong size for CD capabilities page.
cdrecord: Warning: controller returns wrong size for CD capabilities page.
Using generic SCSI-3/mmc CD-ROM driver (mmc_cd).
Driver flags : MMC SWABAUDIO
Supported modes: |
can eject the hdd with no problem, just little time for the second command.
But any of those 2 commands can eject my dvd (plugged on hdc) :
take few minutes with no result, and
| Code: | # cdrecord dev=1001,0,0 -eject
Cdrecord-ProDVD-ProBD-Clone 2.01.01a36 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling
scsidev: '1001,0,0'
scsibus: 1001 target: 0 lun: 0
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'DVD RW 8XMax '
Revision : '140D'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
cdrecord: Success. start/stop unit: scsi sendcmd: no error
CDB: 1B 00 00 00 02 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 40s
cdrecord: Cannot eject media. |
has the same result on my beautiful dvd RWriter... Maybe its physical engine is stupidly out of service, but I'd like be sure. Maybe I now should search for a firmware update, what do you think about this (your ) good idea ? |
|
| Back to top |
|
|
piewie
Guru
Joined: 26 Sep 2002
Posts: 489
Location: old Europe
|
| Posted: Mon Jan 28, 2008 11:37 pm Post subject: |
|
|
What does happen when you switch the position of the drives (don't forget to change Master/Slave jumpers). How is the situation with eject /dev/hdc and /dev/hdd?
Opening a drive should normally not need a firmware update (although you should always use an up to date firmware). This behavior is really strange.
Have you already told the manufacturer and type of the device? (this is not a Plextor drive - so I would not waste that much time for this drive) Check http://club.cdfreaks.com/ for you drive (manufacturer and type)
How is the situation when you boot knoppix? |
|
| Back to top |
|
|
Shadow AOK
n00b
Joined: 26 Jun 2006
Posts: 48
Location: Lyon, France
|
| Posted: Thu Feb 14, 2008 6:42 pm Post subject: |
|
|
If my memory is still operational, i think the writer is a LG drive (she replaced me when i left, that's why i have some answers).
But, the mother board had hardware problems before (and i'm pretty sure there's still some - at least with the battery), so it can be related.
One solution can be to put the writer in another computer (under windows) and try to eject it using the OS, to see if it's a hardware problem or not.
Last edited by Shadow AOK on Fri Feb 15, 2008 12:19 pm; edited 1 time in total |
|
| Back to top |
|
|
Shadow AOK
n00b
Joined: 26 Jun 2006
Posts: 48
Location: Lyon, France
|
| Posted: Fri Feb 15, 2008 12:17 pm Post subject: |
|
|
I've digged a little into my memory and i remembered some things.
Before I install gentoo on this computer (it's a workstation), it was running with mandriva and the writer was connected using an usb rack.
As i wanted to use the gentoo dvd iso, i needed a dvd player so i took the writer and mounted it into the computer.
So, the writer was fully operationnal (it ejected and everything so no firware upgrade is needed).
Next, we had some hardware issues with the motherboard, which were fixed, but maybe the motherboard still encounter some problems (given what I got through with it, i would bet on that) ?
I still think that the writer is fine, but you can put it into your workstation under windows to test it. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Multimedia
