Bug 128333

Summary: unable to mount cdrom drive
Product: [Fedora] Fedora Reporter: Phil B. <familyb>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED NEXTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: pfrields, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-16 04:40:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Phil B. 2004-07-21 20:26:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
I can't seem to mount the cdrom drive. There are no suspicious 
messages during boot or in dmesg.

Version-Release number of selected component (if applicable):
kernel-2.6.5-1.358

How reproducible:
Always

Steps to Reproduce:
1.Boot
2.su root
3.place media in cdrom drive
4.hear cdrom drive spin
5.mount /dev/hdc /mnt/cdrom
    

Actual Results:  mount command hangs - never returns.

Expected Results:  device mounted on /mnt/cdrom filesystem and data 
on disc available.

Additional info:

/etc/grub.conf has following kernel command:
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/123 rhgb quiet 
psmouse.proto=imps


Running on a Dell Inspiron 3000, 200Mhz, 3.2GB hard drive, 144MB ram, 
2 pcmcia cards (ethernet & wireless NICs)

Comment 1 Phil B. 2004-09-02 23:23:20 UTC
This bug was entered in July.  It is now September.  Can someone 
please help?

Comment 2 Michael Schwendt 2004-10-07 12:18:52 UTC
*** Bug 128503 has been marked as a duplicate of this bug. ***

Comment 3 Dave Jones 2005-04-16 04:40:49 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.