Bug 130277 - Sony laptop pcmcia cdrom conflict hangs anaconda
Sony laptop pcmcia cdrom conflict hangs anaconda
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Depends On:
  Show dependency treegraph
Reported: 2004-08-18 14:04 EDT by Paul Wouters
Modified: 2015-01-04 17:09 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-08 01:50:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Wouters 2004-08-18 14:04:20 EDT
Description of problem:

On my Sony SR11K laptop with pcmcia cdrom drive, installs are always
painful. Only redhat 7.x worked properly. Once you boot from cdrom,
you must specify ide1=0x180,0x386 for the cdrom to keep working. This
creates an hdc device. Stuff boots on until it loads the yenta_socket,
when it finds another ide device. this becomes hde,
From this point on, the cdrom logs ide timeout errors and fails.
note that I cannot disable the idex= line because then it won't find
the cdrom and won't load the initrd, modules and pcmcia tools. But I
also cannot disable pcmcia detection from Anaconda (AFAIK). I can also
not disable pcmcia in the very limited award bios that Sony ships.

I tried all combinations i could think of as specified in the linux
kernel documention's ide.txt (eg idex=noprobe, hdc=noprobe, and even
things like hdc=scsi or hdc=0x0,0x0)

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

How reproducible:

Steps to Reproduce:
1. Find Sony SR11K with cdrom
2. Insert FC 3 test 1
3. wait
Actual results:
ide timeouts

Expected results:
perfectly smooth installation :)

Additional info:
Comment 1 Jeremy Katz 2004-08-18 14:07:15 EDT
You also need to add pci=off if I remember correctly.
Comment 2 Paul Wouters 2004-08-18 14:13:33 EDT
Jeremy: I love you :)

That fixed the problem indeed.

Note You need to log in before you can comment on or make changes to this bug.