|
Urgent need of drivers
I badly need the drivers for my computer. My computer crashed and I lost almost everything. This was a catastrophe for me. I was doing some work with scripting languages and trying to install apache server, PHP, etc with the help of our friends in this forum. Recently Xavier was in the process of helping me. Everything went to hell. I must learn to live with these problems. The loses were severe as far as I am concerned. I haven't done any backup work for about 10 months. This was due to pressure of work and studies.
I bought a second-hand computer. Now my Linux works. I have some problems with the screen colors and I can't mount the CD. The DVD player is completely dead. I believe all those problems will be solved when I install the drivers. Linux works well. I can use the word processor and can access the Internet. --------------------------------------------------------------------------- A DVD player called Benq which is 16 speed [ I need a driver.] I can't find any more details about the DVD player. A CD RW player from Samsung. [ I need a driver.] Geforce MMX 64 bit graphic card. [ I need a driver.] -------------------------------------------------------------------------------------------------------------- When it comes to Windows, you can easily find drivers. Please help me. I mean tell me the places to download the drivers. I am running Mandrake Linux 10.0 version. Your help is profoundly appreciated. |
You can get the driver for the Geforce card at Nvidia's driver page. As far as the other two things are concerned... they are supported by the base kernel. If you read your dmesg log after boot (type dmesg | less in a terminal) you should be able to see what the device tags are for those (/dev/hdx). Typically most distributions map the first one to /dev/cdrom.
|
Thanks jtshaw
The dmseg command gave a blank page. -------------------------------------------------- [nissanka@c83-250-91-54 nissanka]$ dmseg | less Lines ? -?/? END ------------------------------------------------------------------------------------- I didn't log on as a root user. Please tell me what to do now. |
Try dmesg | less instead of dmseg | less and see what that does for you.
|
Linux version 2.6.3-7mdk (nplanel@n3.mandrakesoft.com) (gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)) #1
Wed Mar 17 15:56:42 CET 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000017ef0000 (usable) BIOS-e820: 0000000017ef0000 - 0000000017ef3000 (ACPI NVS) BIOS-e820: 0000000017ef3000 - 0000000017f00000 (ACPI data) BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) 382MB LOWMEM available. On node 0 totalpages: 98032 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 93936 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 DMI 2.2 present. ACPI: RSDP (v000 IntelR ) @ 0x000f6f90 ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x17ef3000 ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x17ef3040 ACPI: DSDT (v001 INTELR AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: PM-Timer IO Port: 0x4008 Built 1 zonelists Kernel command line: auto BOOT_IMAGE=linux ro root=309 devfs=mount splash=silent acpi=ht bootsplash: silent mode. Local APIC disabled by BIOS -- reenabling. Found and enabled local APIC! Initializing CPU#0 PID hash table entries: 2048 (order 11: 16384 bytes) Detected 901.852 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Memory: 384108k/392128k available (1816k kernel code, 7240k reserved, 849k data, 272k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 1785.85 BogoMIPS lines 1-33 Calibrating delay loop... 1785.85 BogoMIPS Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 53k freed CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000 CPU: After vendor identify, caps: 0383fbff 00000000 00000000 00000000 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 128K CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: Intel Celeron (Coppermine) stepping 0a Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Using local APIC timer interrupts. calibrating APIC timer ... ..... CPU clock speed is 901.0512 MHz. ..... host bus clock speed is 100.0168 MHz. NET: Registered protocol family 16 EISA bus registered PCI: PCI BIOS revision 2.10 entry at 0xfb290, last bus=1 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040211 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay PnPBIOS: Disabled PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Transparent bridge - 0000:00:1e.0 PCI: Using IRQ router PIIX/ICH [8086/2410] at 0000:00:1f.0 apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac) ikconfig 0.7 with /proc/config* VFS: Disk quotas dquot_6.5.1 devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x1 Initializing Cryptographic API isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found pty: 1024 Unix98 ptys configured Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A PCI: Found IRQ 3 for device 0000:00:1f.6 PCI: Sharing IRQ 3 with 0000:00:1f.5 RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH: IDE controller at PCI slot 0000:00:1f.1 ICH: chipset revision 2 ICH: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:DMA hda: IC35L060AVER07-0, ATA DISK drive Using anticipatory io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdd: SAMSUNG CD-R/RW SW-252B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 120103200 sectors (61492 MB) w/1916KiB Cache, CHS=65535/16/63, UDMA(33) /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 < p5 p6 p7 p8 p9 p10 p11 > mice: PS/2 mouse device common for all mice serio: i8042 AUX port at 0x60,0x64 irq 12 input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard on isa0060/serio0 md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 EISA: Probing bus 0 at eisa0 NET: Registered protocol family 2 IP: routing cache hash table of 4096 buckets, 32Kbytes TCP: Hash tables configured (established 32768 bind 65536) NET: Registered protocol family 1 BIOS EDD facility v0.13 2004-Mar-09, 1 devices found Please report your BIOS at http://linux.dell.com/edd/results.html PM: Reading pmdisk image. PM: Resume from disk failed. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). Mounted devfs on /dev Mounted devfs on /dev Freeing unused kernel memory: 272k freed Real Time Clock Driver v1.12 drivers/usb/core/usb.c: registered new driver usbfs drivers/usb/core/usb.c: registered new driver hub drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1 PCI: Found IRQ 9 for device 0000:00:1f.2 uhci_hcd 0000:00:1f.2: UHCI Host Controller PCI: Setting latency timer of device 0000:00:1f.2 to 64 uhci_hcd 0000:00:1f.2: irq 9, io base 0000d000 uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected usb 1-1: new full speed USB device using address 2 drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x6104 drivers/usb/core/usb.c: registered new driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected an Intel i810 Chipset. agpgart: Maximum main memory to use for agp memory: 320M agpgart: detected 4MB dedicated video ram. agpgart: AGP aperture is 64M @ 0xd0000000 Supermount version 2.0.4 for kernel 2.6 NTFS driver 2.1.6 [Flags: R/O MODULE]. NTFS volume version 3.1. 8139too Fast Ethernet driver 0.9.27 eth0: RealTek RTL8139 at 0xd8826000, 00:90:47:01:cd:50, IRQ 11 eth0: Identified 8139 chip type 'RTL-8100B/8139D' NET: Registered protocol family 17 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Intel 810 + AC97 Audio, version 0.24, 15:45:24 Mar 17 2004 PCI: Found IRQ 3 for device 0000:00:1f.5 PCI: Sharing IRQ 3 with 0000:00:1f.6 PCI: Setting latency timer of device 0000:00:1f.5 to 64 i810: Intel ICH 82801AA found at IO 0xd800 and 0xd400, MEM 0x0000 and 0x0000, IRQ 3 i810_audio: Audio Controller supports 2 channels. i810_audio: Defaulting to base 2 channel mode. i810_audio: Resetting connection 0 ac97_codec: AC97 Audio codec, id: ADS72 (Analog Devices AD1881A) i810_audio: AC'97 codec 0 Unable to map surround DAC's (or DAC's not present), total channels = 2 lines 127-160 parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP] parport0: irq 7 detected parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) lp0: using parport0 (polling). lp0: console ready atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. inserting floppy driver for 2.6.3-7mdk Floppy drive(s): fd0 is 2.88M AMI BIOS FDC 0 is a post-1991 82077 hdd: ATAPI 52X CD-ROM CD-R/RW CD-MRW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 SCSI subsystem initialized st: Version 20040122, fixed bufsize 32768, s/g segs 256 NET: Registered protocol family 10 Disabled Privacy Extensions on device c035fe60(lo) IPv6 over IPv4 tunneling driver eth0: no IPv6 routers present The output is very large. Would you gather some information? Please tell me. |
hdd: SAMSUNG CD-R/RW SW-252B, ATAPI CD/DVD-ROM drive
This tells you that /dev/hdd is your Samsung burner and that the kernel knows all about it. More info can be gathered here later in the output: hdd: ATAPI 52X CD-ROM CD-R/RW CD-MRW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 It doesn't appear from what you've shown above that the DVD drive was detected at all. Are you sure the hardware is all physically installed properly? |
Yes, I can put a CD into the Benq DVD and take it out. It physically works. It doesn't read. This old computer had this Benq DVD player. That fellow worked with Windows. The Samsung CD is from my old computer. Its motherboard was burnt. The graphic card was burnt. The power supply was burnt. The SDRAM modules were burnt.
Samsung is my old CD burner. It doesn't work with DVD's. I can't mount it. It doesn't accept. It doesn't read the CD's as it did it before. I had difficulties installing Mandrake Linux 10.0 version. I had to try 30 or 40 times. It doesn't read the way it did it before. I believe the problems are in the driver. The colors are not good on the screen. You mentioned the right place to download the drivers. I will dowonload soon.What shall I do? Please tell me. ------------------------------------------------------------------------------------------------------------ The following is the message when I tried to mount the cd [root@c83-250-91-54 nissanka]# mount /dev/cdrom /mnt/cdrom mount: block device /dev/cdrom is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/cdrom, or too many mounted file systems [root@c83-250-91-54 nissanka]# |
Just a guess, but if everything else in the old computer was messed up then you might want to try removing the Samsung drive. If it is on the same bus as the BenQ drive it could causing your problem.
Once you install the nvidia drivers (make sure to follow all the directions) your display quality under X should improve. |
The following is the message when I tried to mount the cd
[root@c83-250-91-54 nissanka]# mount /dev/cdrom /mnt/cdrom mount: block device /dev/cdrom is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/cdrom, or too many mounted file systems [root@c83-250-91-54 nissanka]# --------------------------------------------------------------------------------- I removed the CD and tried again. The following is the message. [root@c83-250-91-54 nissanka]# mount /dev/cdrom /mnt/cdrom mount: block device /dev/cdrom is write-protected, mounting read-only mount: No medium found [root@c83-250-91-54 nissanka]# |
Now I am leaving for the gym. I must do circuit training. I will be back after about 5 hours. I got to attend a few other things in town affter the training.
Please leave your message. I profoundly appreciate your help. |
The fact that your DVD driver drawer opens and closes only means the molex connector is plugged in and there is power. If they are on the same IDE channel make sure the master/slave settings are right and that the IDE cable isn't damaged or not properly plugged in. If so, take out the Samsung (the one from the damaged computer) drive as said before and try mounting a CD or DVD in the DVD drive, make sure the CD/DVD is a good'un.
the nvidia drivers as pointed out by jtshaw will take care of your graphics card just make sure to follow the instructions |
I thank both phll.d.g and jtshaw for the replies. I will download the Nvida drivers and install. Please keep a good watch on this thread for the next 48 hours or so. My top priority is fixing the computer.
|
It was difficult for me to judge the correct driver for my graphic card. They have several drivers. I asked their forum to help selecting the correct driver. I am waiting an answer from them.
http://www.nvnews.net/vbulletin/showthread.php?t=57991 |
They want to know my Linux architecture. Is it IA32 or IA64?
How do I find out this? |
I just wrote the dmesg command and got the following output. This is not the entire output. This is just a part of the output. It is very long.
------------------------------------------------------------------------------------------ parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP] parport0: irq 7 detected parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) lp0: using parport0 (polling). lp0: console ready atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. inserting floppy driver for 2.6.3-7mdk Floppy drive(s): fd0 is 2.88M AMI BIOS FDC 0 is a post-1991 82077 ide-cd: cmd 0x5a timed out hdd: lost interrupt SCSI subsystem initialized st: Version 20040122, fixed bufsize 32768, s/g segs 256 ide-floppy driver 0.99.newide ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) NET: Registered protocol family 10 Disabled Privacy Extensions on device c035fe60(lo) IPv6 over IPv4 tunneling driver eth0: no IPv6 routers present ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) ide-cd: cmd 0x5a timed out hdd: lost interrupt hdd: cdrom_pc_intr: The drive appears confused (ireason = 0x03) [nissanka@c83-250-90-204 nissanka]$ It mentions about a confusion. What is it? |
Well I don't know what is wrong with it, but have you made sure the IDE cable is plugged in and the master/slave setting is correct. Are you sure the drive works?
Since dmesg says that the CD is on hdd I suspect not, unless you have not followed our reccommendations and removed the potentially damaged samsung optical drive |
Thanks Phll
My Samsung CD Burner works. It doesn't work for its full capacity. For example, I can't mount it. So I can't use my CDs. The BenQ is complely dead. Now I must shut down the computer and look for the faulty cables. I will come back to you all soon. |
IA32 = x86 processors. 486's, Pentiums (I-IV), Athlon, Athlon XP, Duron, Sempuron, ect.
IA64 = Itanium I & II processors AMD64/x86_64 = Pentium IV w/ EMT64, Athlon 64/FX, Opterons, Xeons w/ EMT64 <edit=sorry, appears you are already tring this....> Are those drive errors occuring with the Samsung drive? It sounds like it got damaged when the other equipment got damaged. Have you tried removing it completely and just using the benQ DVD drive and seeing if that will work by itself? |
Quote:
Can you tell us if you have the Samsung on the Secondary Master or Secondary Slave or elsewhere, the errors in dmesg are for the slave device on the secondary IDE cable |
Quote:
|
I was thinking maybe the DVD drive is broken, or he has master/slave settings mixed up
|
Ya... this reeks of a hardware problem....
|
I thank everybody for helping me
I must find out which is Master and which is slave. This will take time. I will find this out and come back to you again. I have a diskette called 'Hwinfo' . I must start the computer with the diskette inside. It will tell me the details. This diskette is 2 or 3 years old. I got it from a friend of mine. I hope it will work. Please keep a good watch on this thread when time permits. |
It was IDE Secondary Slave --- Samsung CD -R /RW SW 25
No more. Then I changed the jumper of the BenQ DVD-ROM to Master. Afterwards, the things have changed. Please read the following: IDE Secondary Master is BenQ DVD-ROM 16X IDE Secondary Slave is Samsung CD -R /RW SW-25 [When your computer starts, you press the 'Delete' button to have a look into the configuration. I got the above details from doing it.] { The harddrive is the Primary Master.} However, I can't mount the CDs. I get the same old message. -------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------- [nissanka@c83-250-90-204 nissanka]$ dmesg | less The above command gave me the following strange output. tatus=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x51 { DriveReady SeekComplete Error } hdd: request sense failure: error=0x64Aborted Command LastFailedSense 0x06 hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: packet command error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: packet command error: error=0x04 hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete cdrom: This disc doesn't have any tracks I recognize! hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } hdd: packet command error: error=0x04 hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command cdrom: This disc doesn't have any tracks I recognize! hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: packet command error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: packet command error: error=0x04 hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } hdd: packet command error: error=0x04 hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x51 { DriveReady SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: ATAPI reset complete hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error } hdd: request sense failure: error=0x04Aborted Command hdd: status error: status=0x19 { SeekComplete DataRequest Error } hdd: status error: error=0x04Aborted Command hdd: drive not ready for command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command hdd: status error: status=0x11 { SeekComplete Error } hdd: status error: error=0x04Aborted Command What is the problem? What shall I do now? |
Can you mount a cd in /dev/hdc (which should be the device tag for the BenQ DVD drive)?
|
Thanks jtshaw for the reply. I really appreciate your help.
[root@c83-250-90-204 nissanka]# mount /dev/cdrom /mnt/cdrom mount: block device /dev/cdrom is write-protected, mounting read-only mount: No medium found [root@c83-250-90-204 nissanka]# The above is without the CD in the BenQ drive. --------------------------------------------------------------------------------- [root@c83-250-90-204 nissanka]# mount /dev/cdrom /mnt/cdrom mount: block device /dev/cdrom is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/cdrom, or too many mounted file systems [root@c83-250-90-204 nissanka]# The above is with the CD in the BenQ drive. [ It seems now the system doesn't recognize the Samung drive.] How do I do the mounting you suggested. Please tell me the command. ---------------------------------------------------------------------------------------------------------------- I tried the following; it didn't work. [root@c83-250-90-204 nissanka]# mount /dev/hdc/cdrom /mnt/hdc/cdrom mount: mount point /mnt/hdc/cdrom does not exist [root@c83-250-90-204 nissanka]# ------------------------------------------------------------------------------------------------------------- [root@c83-250-90-204 nissanka]# mount /dev/hdc/cdrom /mnt/cdrom mount: special device /dev/hdc/cdrom does not exist (a path prefix is not a directory) [root@c83-250-90-204 nissanka]# What shall I do now? |
I badly need your help. Please tell me how to proceed.
|
Looks like the drive is dead, can you try it with a other drive?
|
I got a boot CD called Hiren's Boot CD.
You could start the computer with it. I tried with it. Both of the drives recognized it. It has a program called 'HWinfo'. It tells you the details as to the computer. So both of the drives recognize the Boot CD. I wouldn't think it is dead. |
Put a CD in the BenQ drive and type as root
Code:
mount /dev/hdc /mnt/cdromand please post the output of this command Code:
ls -l /dev/cdrom |
I put a CD in the BenQ and did exactly what you suggested.
[nissanka@c83-250-90-204 nissanka]$ su root Password: [root@c83-250-90-204 nissanka]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/hdc, or too many mounted file systems [root@c83-250-90-204 nissanka]# ---------------------------------------------------------------------------------------------------------------------------- Here is the output of the other command '[root@c83-250-90-204 nissanka]# ls -l /dev/cdrom lr-xr-xr-x 1 root root 13 okt 13 13:15 /dev/cdrom -> cdroms/cdrom0 [root@c83-250-90-204 nissanka]# ls -l /dev/cdrom ----------------------------------------------------------------------------------------------------------- I repeated the above without logging on as a root user. Please read the following: [nissanka@c83-250-90-204 nissanka]$ ls -l /dev/cdrom lr-xr-xr-x 1 root root 13 okt 13 13:15 /dev/cdrom -> cdroms/cdrom0 [nissanka@c83-250-90-204 nissanka]$ |
post the contents of
Code:
cat /etc/fstab |
Here it is.
[nissanka@c83-250-90-204 nissanka]$ cat /etc/fstab /dev/hda9 / ext2 defaults 1 1 /dev/hda10 /boot ext2 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdd /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0 /dev/hda5 /mnt/win_d ntfs umask=0,nls=iso8859-1,ro 0 0 /dev/hda2 /mnt/win_h vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hda11 /tmp ext2 defaults 1 2 [nissanka@c83-250-90-204 nissanka]$ |
By the way, those hda9, hda10 and hda11 belong to Linux.
Those hda2, hda5 are Windows XP partitions. Don't care about them. I am not interested in them. Now I will leave for the gym and will be away for a few hours. I deeply appreciate your help. Leave your messages. I will attend them as soon as possible. I am in Europe. Are you based in the USA or in Europe? |
What shall I do now? Please tell me.
I badly need your help. |
Quote:
|
Thanks IOerror
My urgent requirement is to fix the problem. I can't mount the CDs. Please tell me how to solve the problem. The following is the outpput: [nissanka@c83-250-90-204 nissanka]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 8 model name : Celeron (Coppermine) stepping : 10 cpu MHz : 901.863 cache size : 128 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1785.85 [nissanka@c83-250-90-204 nissanka]$ |
A Celeron is IA32.
As for the CD, hmm, you say you can boot from it, so it obviously works? What boot parameters are you using? If you're using ide-scsi (although that should be mentioned in dmesg I think), then /dev/cdrom should be pointing to a SCSI device such as /dev/sr0 (though it looks like you're using devfs, so it'll be something different). |
Thanks Ioerror
I have already posted the message from 'dmesg' command. You could read it. I am clueless about the message from this 'dmseg' command. |
Ok, try this. Put your CD in the samsung and just issue a
Code:
mount /mnt/cdrom |
The Samsung gave the following:
[root@c83-250-90-204 nissanka]# mount /mnt/cdrom mount: No medium found [root@c83-250-90-204 nissanka]# --------------------------------------------------------------------------------------- The BenQ gave the following: [root@c83-250-90-204 nissanka]# mount /mnt/cdrom /dev/hdd: Input/output error mount: /dev/hdd: can't read superblock [root@c83-250-90-204 nissanka]# |
Quote:
Copy /etc/fstab to your home dir so you have a backup, then edit this line: Code:
/dev/hdd /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec 0 0Code:
/dev/hdd /mnt/cdrom iso9660 user,noauto,ro,exec 0 0Code:
mount /mnt/cdrom |
This is how it looks like.
--------------------------------------------------------------- /dev/hda9 / ext2 defaults 1 1 /dev/hda10 /boot ext2 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdd /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0 /dev/hda5 /mnt/win_d ntfs umask=0,nls=iso8859-1,ro 0 0 /dev/hda2 /mnt/win_h vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hda11 /tmp ext2 defaults 1 2 ~ ------------------------------------------------------------------------------------------------------------ I will edit it as you have suggested. |
I edit it. Now it is as follows:
[root@c83-250-90-204 etc]# vi fstab [root@c83-250-90-204 etc]# cat fstab /dev/hda9 / ext2 defaults 1 1 /dev/hda10 /boot ext2 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdd /mnt/cdrom iso9660 user,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0 /dev/hda5 /mnt/win_d ntfs umask=0,nls=iso8859-1,ro 0 0 /dev/hda2 /mnt/win_h vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 none /proc proc defaults 0 0 /dev/hda11 /tmp ext2 defaults 1 2 |
It seems the CD has gone to hell. The following is the output.
[nissanka@c83-250-90-204 nissanka]$ su root Password: [root@c83-250-90-204 nissanka]# mount /mnt/cdrom mount: No medium found |
and?
...Does the CD mount? |
No.
[root@c83-250-90-204 mnt]# ls cdrom/ cdrom2/ floppy/ win_d/ win_h/ [root@c83-250-90-204 mnt]# cd cdrom [root@c83-250-90-204 cdrom]# ls [root@c83-250-90-204 cdrom]# |
Well whats the error when you try and mount it?
Code:
mount /mnt/cdrom |
Here are the two outputs.
[root@c83-250-90-204 nissanka]# mount /dev/cdrom /mnt/cdrom mount: block device /dev/cdrom is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/cdrom, or too many mounted file systems [root@c83-250-90-204 nissanka]# ---------------------------------------------------------------------------- [root@c83-250-90-204 nissanka]# mount /mnt /cdrom mount: mount point /cdrom does not exist [root@c83-250-90-204 nissanka]# |
this isn't a music cd is it?
|
| All times are GMT -5. The time now is 10:02 AM. |