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.
try some more and i am givenup
1.try mount as root
2.put your slack cd and try!!
mount -t iso9660 /dev/hdc /mnt/cdrom
3.try oounting to some other moutn point like /home/name/mycd
mount -t iso9660 /dev/hdc /home/name/mycd
4.try mountin /dev/sr0 to /mnt/cdrom manually(just to check the permission)
i think $dmesg |grep -i hdc without any cd must give some info
Results:
Quote:
1. Cannot mount a cdrom in hdc as root.
2. Comment mount: block device /dev/hdc is write protected, mounting read-only and cursor sat below this comment for an eternity, eventually had to eject the cdrom after 20 minutes of the device whirling.
3. Comment mount: block device /dev/hdc is write protected, mounting read-only and cursor sat below this comment for an eternity, eventually had to eject the cdrom after 20 minutes of the device whirling.
4. Mounts cdrom in device sr0 correctly.
Output of dmesg | grep -i hdc
Quote:
ide1: BM-DMA at 0x0868-0x086f, BIOS settings: hdcMA, hddio
hdc: CD-ROM CDR_U200, ATAPI CD/DVD-ROM drive
hdc: ATAPI 16X CD-ROM drive, 128kB Cache, DMA
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
end_request: I/O error, dev hdc, sector 120
isofs_fill_super: bread failed, dev=hdc, iso_blknum=30, block=30
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
end_request: I/O error, dev hdc, sector 84
isofs_fill_super: bread failed, dev=hdc, iso_blknum=21, block=21
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
end_request: I/O error, dev hdc, sector 76
isofs_fill_super: bread failed, dev=hdc, iso_blknum=19, block=19
Does anyone think installing a newer 2.18 kernel would fix this. I seem to be getting nowhere fast. A definite fix would be installing a different distro of course
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054
Rep:
Are you sure its an issure only in Slack? I mean did you try using it in Windows or something? cos maybe after you installed 2.6 kernel, by some freak chance, some wires of your drive might have gone loose.
Yes it's only in slack and specifically the 2.6.17.13 kernel as I still have the 2.4.33.3 kernel and it still mounts no problem there. I previously had Suse and a 2.6 kernel on the same machine and it worked okay.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.