Bug 296961

Summary: Install fails to recognise PCMCIA network card
Product: [Fedora] Fedora Reporter: Michael De La Rue <mvyynqbgerqungqbgpbz.yeuhc>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-10 17:06:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
FC4 Output from lsmod / lspci / cardctl ident / cat /proc/interrupts,/proc/ioports,/proc/iomem none

Description Michael De La Rue 2007-09-19 21:02:09 UTC 
Description of problem:
If I try to install Fedora 7 on my old Satellite 4090XCDT laptop, the install
fails since it doesn't recognise the existence of the network card

Version-Release number of selected component (if applicable):
current boot.iso disk with sha1sum 3f5c4b9fb31a7e0f24e3b47a797a1a1340cb197c

How reproducible:
every time

Steps to Reproduce:
1. burn boot.iso to a cd
2. boot and step through till choice of install mechanism
3. choose http

  
Actual results:
No suitable device is found

Expected results:
install should continue using Xircom 

Additional info:
This computer works with fedora core 4 kernel 2.6.16-1.2115_FC4
attached are various hardware diagnostic outputs taken under FC4.  I think that
it stopped working with kernel 2.6.17.
Comment 1 Michael De La Rue 2007-09-19 21:02:09 UTC 
Created attachment 200081 [details]
FC4 Output from lsmod / lspci / cardctl ident / cat /proc/interrupts,/proc/ioports,/proc/iomem
Comment 2 Chris Lumens 2008-01-10 17:06:41 UTC 
This should be working in rawhide.  Please retest if possible and reopen this
bug if you continue to see problems.  We've done a lot of work in this area
recently so it's likely that your bug has been taken care of.  Thanks.