Bug 770990 - Fedora 16 x86_64 installation fails on Dell Optiplex 390
Summary: Fedora 16 x86_64 installation fails on Dell Optiplex 390
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-30 19:36 UTC by Ray Mikkelson
Modified: 2012-09-05 13:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-05 13:55:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
anaconda.log (58.15 KB, text/plain)
2012-01-03 20:44 UTC, Ray Mikkelson
no flags Details
ifcfg.log (2.75 KB, text/plain)
2012-01-03 20:45 UTC, Ray Mikkelson
no flags Details
program.log (155.47 KB, text/plain)
2012-01-03 20:45 UTC, Ray Mikkelson
no flags Details
storage.log (251.97 KB, text/plain)
2012-01-03 20:46 UTC, Ray Mikkelson
no flags Details
syslog (114.78 KB, text/plain)
2012-01-03 20:46 UTC, Ray Mikkelson
no flags Details
X.log (27.05 KB, text/plain)
2012-01-03 20:47 UTC, Ray Mikkelson
no flags Details
yum.log (140.85 KB, text/plain)
2012-01-03 20:47 UTC, Ray Mikkelson
no flags Details

Description Ray Mikkelson 2011-12-30 19:36:41 UTC
Description of problem:

I have a new (MFG date 12/21/11) Dell Optiplex 390 with a TSSTcorpDVD-ROM TS-H353C DVD-ROM. In the BIOS, the SATA chip is enabled (only options are Disabled and ATA). The DVD drive is plugged into the white SATA connector on the motherboard. I am unable to install Fedora 16 x86_64 on this machine. It appears that the installation software (anaconda?) does not see the DVD drive (I never get prompted to verify the DVD installation media & the installer doesn't detect the repository on the installation DVD) and it also fails to download from the Fedora repositories on the internet (problems with the ethernet controller config?). DVD is known good (used successfully several times previously). The installer does see the SATA hard drive and is able to format it. The installer claims that I have a p4p1 controller: Realtek RTL8111/8168B PCI Express card.

Errors I get when booting the installer:

[0.450766] pnp 00:0b can't evaluate _CRS: 12311

As I said, I do not get prompted to test the DVD install media. The installer does see the correct MAC address for the ethernet controller, and sees the hard drive. Later in the install, the installer somehow checks for dependencies, but then cannot download (any?) of the RPM's (it fails on the firewall RPM), then says "Retry Download", and eventually gives up.

This PC has the Intel H61 Express Chipset (according to the documentation), and both the DVD and disk drives are SATA.



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

Fedora 16 x86_64 complete DVD ISO image downloaded from the Fedora website.


How reproducible:


Steps to Reproduce:
1. Download the Fedora 16 x86_64 complete DVD ISO image
2. Burn the DVD
3. Boot the installation DVD, using either legacy boot or UEFI boot (both fail)
  
Actual results:

Installation fails (every time).  Installer does not detect the SATA DVD drive nor can it access the remote Fedora repositories on the internet, booting the Ethernet interface using DHCP.

Expected results:

successful Fedora install


Additional info:

Some interesting facts:

1) Booting legacy (a BIOS setting), I cannot enter any additional repositories
2) Booting UEFI, I am able to specify additional repositories
3) If I boot UEFI, create a local repository and specify it during the install, the installer is able to download the RPM packages from it.  (but, not from the usual external repositories -- the DHCP settings aren't recognizing the default gateway??)
4) I've used this DVD (and procedure) many times to install on older Dell PC's successfully.
5) The parameters specified by the DHCP server are correct (all other PC's on network obtain the correct parameters)

Comment 1 Brian Lane 2012-01-03 17:53:01 UTC
Please switch to tty2 (ctrl-alt-f2) and attach the logs from /tmp/*log to this bug as individual plain/text files.

Comment 2 Ray Mikkelson 2012-01-03 20:44:34 UTC
Created attachment 550523 [details]
anaconda.log

requested by Brian C. Lane

Comment 3 Ray Mikkelson 2012-01-03 20:45:19 UTC
Created attachment 550525 [details]
ifcfg.log

requested by Brian C. Lane

Comment 4 Ray Mikkelson 2012-01-03 20:45:50 UTC
Created attachment 550526 [details]
program.log

requested by Brian C. Lane

Comment 5 Ray Mikkelson 2012-01-03 20:46:27 UTC
Created attachment 550527 [details]
storage.log

requested by Brian C. Lane

Comment 6 Ray Mikkelson 2012-01-03 20:46:51 UTC
Created attachment 550529 [details]
syslog

requested by Brian C. Lane

Comment 7 Ray Mikkelson 2012-01-03 20:47:18 UTC
Created attachment 550530 [details]
X.log

requested by Brian C. Lane

Comment 8 Ray Mikkelson 2012-01-03 20:47:48 UTC
Created attachment 550531 [details]
yum.log

requested by Brian C. Lane

Comment 9 Ray Mikkelson 2012-01-03 20:50:54 UTC
NOTE:  The logs were created with a USB memory stick inserted into the target machine.  (The thought was that I was going to use it to transfer the /tmp/*log files to my desktop machine.)  Normally, the memory stick is not used during the installation process.  The presence of the USB memory stick had no effect on the initial problems reported.

I hope that there's enough info in the logs to help debug the problem.

Comment 10 Brian Lane 2012-01-06 21:45:18 UTC
It looks like there may be something wrong with the DVD hardware or driver. I see this in the logs:

14:11:02,862 INFO kernel:[    2.628710] ata2.00: ATAPI: TSSTcorpDVD-ROM TS-H353C, D100, max UDMA/100
14:11:02,862 INFO kernel:[    2.650576] ata2.00: configured for UDMA/100
14:11:02,862 WARNING kernel:[    2.750927] ata2.00: TEST_UNIT_READY failed (err_mask=0x2)
14:11:02,862 WARNING kernel:[   14.111206] ata2.00: qc timeout (cmd 0xa0)
14:11:02,862 WARNING kernel:[   14.111211] ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
14:11:02,862 WARNING kernel:[   14.111216] ata2.00: limiting SATA link speed to 1.5 Gbps
14:11:02,862 WARNING kernel:[   14.111220] ata2.00: limiting speed to UDMA/100:PIO3
14:11:02,862 WARNING kernel:[   20.581501] ata2.00: qc timeout (cmd 0xa0)
14:11:02,862 WARNING kernel:[   20.581505] ata2.00: TEST_UNIT_READY failed (err_mask=0x4)
14:11:02,862 WARNING kernel:[   20.581508] ata2.00: disabled
14:11:02,862 INFO kernel:[   20.581530] ata2.00: hard resetting link

Moving this to kernel, maybe they have a better idea.

Comment 11 Ray Mikkelson 2012-01-09 19:15:24 UTC
I assure you that there is nothing wrong with the hardware.  I used the exact same hardware to install Windows 7 using the DVD drive.  I then used the DVD drive to subsequently install Microsoft Office 2010.  I never had any problems with the DVD drive during either of these installs.  Also note that the BIOS successfully booted the Fedora installer from the DVD.

I have to believe that the problem is software-related.

Comment 12 Ray Mikkelson 2012-01-09 19:21:04 UTC
Also, please don't lose sight that there are 2 (related?) problems:
   1) The installer doesn't correctly handle/see the DVD drive
   2) The installer is unable to access the Fedora repository on the internet.  However, it is able to access a repository that I created on the same subnet.

I believe that both of these functions go through the Intel H61 Express chipset.

Comment 13 Brian Lane 2012-01-10 01:16:10 UTC
Well, it may not be broken hardware, but the kernel is not able to initialize the drive so there is nothing anaconda can do. The network repo problem may or may not be related or a side effect.

Comment 14 Dave Jones 2012-03-22 17:04:54 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 15 Dave Jones 2012-03-22 17:08:04 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 16 Dave Jones 2012-03-22 17:18:55 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 17 Ray Mikkelson 2012-03-29 22:14:22 UTC
I finally got some time to test your fix using the Fedora 17 -- Alpha installation ISO.  Here are the results of my testing.  BTW, on these same boxes (Optiplex 390's), the "restart" function does not work properly.  However, "power off" does.  (Restart will shutdown Fedora, print the restart message, and then just sit there for hours...)

| Problem reported in 770990 | UEFI Boot | Legacy Boot |
| pnp 00:0b can't evaluate _CRS: 12311 message | not fixed | not fixed |
| install DVD doesn't find/see the DVD drive (asks to verify media) | fixed | fixed |
| installer doesn't see RPM pkgs on DVD |fixed | fixed |
| installer fails to download from (remote) Fedora repositories | not fixed | not fixed |


I still see the pnp 00:0b can't evaluate _CRS: 12311 messages.  BTW, this message also prints when Fedora 16 (my machine is current with updates as of 3/28/12) boots as well (so, it's not just an installer issue).

The installer now sees the DVD drive just fine.  It now asks to verify the installation media and is able to install from the RPMs on the DVD.  So that problem has been fixed.

The installer is still unable to use the standard Fedora repositories.  Behavior is the same as reported in 770990 -- the installer does the dependency checks, supposedly gets the repo data, but then cannot download the RPM's themselves.  When I use my local repository, I can get the installer to work by "Editing" the repo information after the one specified in the kickstart file "fails", making absolutely no modifications, then doing a save, and then the installer can successfully access the local repo.  This same trick doesn't work for the standard remote Fedora repository.

Comment 18 Andrew 2012-06-22 00:15:30 UTC
I have just repeated an almost identical set of problems using the Fedora i686 install DVD on a brand new computer.

The motherboard is a Gigabytes GA-B75M-D3H with an intel dual core processor and 4 gB Corsair 1333 mhz ram. The only add in card is a pci card with 4 extra usb ports on it.

intel B75 chipset
built in intel graphics
realtek audio
realtek ethernet 
SATA hard drive and DVD running in ahci mode

With the install dvd I couldn't get the graphical display to work correctly but could use the tab key and a little trial and error to go through the install. Kernel options like resolution= and xdriver= were completely ignored by the installer and I still got the same size screen with the buttons off screen.

The install would hang during the network setup process where it would identify my lan card as a p4p1 controller with a mac address of all F's. Not being able to change the controller means you can't go forward and clicking the Back button exits the installer.

Repeated identical results using the text mode install as well.

I downloaded the Fedora 16 Live CD iso (605 mb) and installed it onto a USB stick and successfully booted the computer using that. (hooray I thought) It also went through the install process without a flaw. (think I'm on a winner here) System boots fine, and fast, but there's no dvd drive, my realtek lan is still a p4p1 controller with a mac address of all F's, and the terminal won't let me sudo or use su. I can look but I can't touch.

The computer is dual boot running WinXP and everything is working flawlessly under windows. There's no problem with any of the fedora media either, I'm about to try and use the same media to do a full install on an external usb drive and see if that boots on the new computer. Have already used the same media to install on several other computers including a mac pro and had no problems.

The computer that has the problems is not mine, and it's currently in use by it's owner so I can't just jump on it when I want and get any log files you may require. I can get them, just not straight away, please supply a list of any you may need. I also need concise instructions on how to get the log files as I'm really only a beginner with shell commands.

Cheers,

Andrew

Comment 19 Josh Boyer 2012-09-05 13:55:24 UTC
We can't fix install media after release.  If you are having issues with the F18 Alpha install media once it is available, please open a new bug against F18 with the relevant details.  We can try and get it fixed before F18 goes Gold.

Our apologies for the inconvenience.


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