Bug 232360 - Installation does not find the hard drive
Summary: Installation does not find the hard drive
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-03-14 23:34 UTC by Pete Zaitcev
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-04-23 16:31:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
dmesg (16.00 KB, text/plain)
2007-03-14 23:36 UTC, Pete Zaitcev 		no flags Details
dmesg FC6 (16.00 KB, text/plain)
2007-03-15 05:58 UTC, Pete Zaitcev 		no flags Details
/proc/interrupts FC6 (616 bytes, text/plain)
2007-03-15 05:59 UTC, Pete Zaitcev 		no flags Details
View All

Description Pete Zaitcev 2007-03-14 23:34:01 UTC 
Description of problem:

When installing FC7T2 on Inspiron 1501, hard drive is not found.

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

Linux version 2.6.20-1.2949.fc7 (brewbuilder.redhat.com) (gcc
version 4.1.2 20070222 (Red Hat 4.1.2-3)) #1 SMP Mon Feb 26 18:33:03 EST 2007

How reproducible:

100%

Steps to Reproduce:
1. Attempt to install FC7T2
  
Actual results:

No hard drive is visible.

Expected results:

Hard drive present (as sda)

Additional info:

I find it odd that nobody has reported this. I have not just searched,
but reviewed all kernel bugs in Rawhide.

I'm going to attach dmesg. It contains some suspicious timeouts...

I have no idea if the hard drive is. Vista works fine on this box,
maybe I can ask it?
Comment 1 Pete Zaitcev 2007-03-14 23:36:55 UTC 
Created attachment 150102 [details]
dmesg
Comment 2 Pete Zaitcev 2007-03-15 05:58:53 UTC 
Created attachment 150108 [details]
dmesg FC6
Comment 3 Pete Zaitcev 2007-03-15 05:59:54 UTC 
Created attachment 150109 [details]
/proc/interrupts FC6
Comment 4 Pete Zaitcev 2007-03-15 16:27:29 UTC 
This appears to be an MSI issue. Booting with pci=nomsi fixes the problem.
Comment 5 Dave Jones 2007-04-23 16:31:24 UTC 
we now default to msi off by default (users who want it can boot with pci=msi)
It seems to cause more problems than its worth to have it on by default right now.
Note You need to log in before you can comment on or make changes to this bug.