LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-28-2006, 03:14 PM   #31
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33

rkrishna says...

Quote:
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

Last edited by tamtam; 11-28-2006 at 03:54 PM.
 
Old 11-28-2006, 03:57 PM   #32
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
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
 
Old 11-29-2006, 02:35 AM   #33
rkrishna
Member
 
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654

Rep: Reputation: 32
Quote:
Does anyone think installing a newer 2.18 kernel would fix this.
no idea, whether it is something to do with acpi.

instead you can try test26.s kernel, rather going for huge

1.disable dma support, i think u can do it by hdparm(hdparm -d0 /dev/hdc)check this, i am not sure

dont go for someother linux that wont help, if slackware cant, others cant.
 
Old 11-29-2006, 05:05 AM   #34
duryodhan
Senior Member
 
Registered: Oct 2006
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054

Rep: Reputation: 46
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.

Last edited by duryodhan; 11-29-2006 at 05:11 AM.
 
Old 11-30-2006, 02:07 AM   #35
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
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.
 
Old 11-30-2006, 03:50 AM   #36
rkrishna
Member
 
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654

Rep: Reputation: 32
did you try disable dma, as i suggested?
 
Old 11-30-2006, 05:59 AM   #37
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
sorry rkrishna, at work at the moment, try it when I get home.
 
Old 11-30-2006, 03:08 PM   #38
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
rkrishna you are the man....

Quote:
1.disable dma support, i think u can do it by hdparm(hdparm -d0 /dev/hdc)check this, i am not sure
At last YOU have the cdrom drive working.

Thanks for your patience.

One quick question, will have to run this command every time I boot into the 2.16 kernel.
 
Old 11-30-2006, 03:17 PM   #39
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,928

Rep: Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612
This is a CRC error:
DriveReady SeekComplete Error
Try 'modprobe crc' before mounting
 
Old 11-30-2006, 04:47 PM   #40
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
What exactly is a CRC error and what is the fix.
 
Old 11-30-2006, 04:53 PM   #41
tamtam
Member
 
Registered: May 2004
Distribution: Slackware.
Posts: 323

Original Poster
Rep: Reputation: 33
result of...
Quote:
modprobe crc
FATAL: Module crc not found.
The significance?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Mount problems after kernel upgrade npuetz Linux - Hardware 2 06-13-2005 01:28 PM
CDROM cannot mount after upgrade to kernel 2.6.10 geeman2.0 Slackware 6 05-05-2005 06:57 AM
gnome trouble after kernel upgrade blish_blash Linux - Software 3 08-16-2004 05:00 PM
unable to mount floppy after kernel upgrade andrew001 Linux - Hardware 1 12-07-2003 06:51 PM
Kernel upgrade trouble katmai90210 Red Hat 3 11-07-2003 09:32 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:34 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration