Listed below are links to blogs that reference this entry: Fedora Diagnostics.
TrackBack URL for this entry: http://www.transterrestrial.com/admin/mt-tb.cgi/10066
20 Comments
Leland wrote:
I assume you tried Carl's suggestion. I'm not a Linux person, so I've skipped the previous post. However, your screenshot reminded me of the Windows OS install "Hit F6 to load device drivers". If you don't hit F6 for the latest hard drive drivers, you are typically SOL for seeing the harddrive and continuing the install. I went back in read the previous comments, and like you, I think Carl is right. He typically is.
Hal Duston wrote:
Looking at the top screenshot, it appears to have a problem loading the RealTek RTL-8169 Gigabit Ethernet driver as near as I can tell. Are you attempting to install over the network either via http, nfs, or ftp?
Rand Simberg wrote:
No, I'm installing from a DVD.
Pete Zaitcev wrote:
Damn shame for the oops in the Realtek driver. I think I can guess why it happened. The driver was unable to extract the MAC from this chip in rtl8169_get_mac_version, but when it tried to report the problem, it crashed in because in 2.6.25 the tp->pci_dev is assigned after rtl8169_get_mac_version is called.
This does not help us with the main problem much, unfortunately. Rand cannot install F8 and then upgrade, because it's very likely that F8 has the same old r8169 and dies the same way. And it's a lot of hassle. Although the updated kernel for F9 (2.6.25.11-97.fc9) is likely fixed, it is not on the installation media.
Unlike many UNIXes, Linux shrugs off crashes in kernel if it can (e.g. if the CPU wasn't keeping an essential lock, in which case everyone else will quicky die). So perhaps we can just ignore the Realtek problem, which is only keeping a modprobe process. But there's more.
The second screen just tells us that libata was unable to initialize SATA (this is why I suggested pci=nomsi, it's a common issue for F9 vintage kernels). The long hang seemed like the delay that happens when libata is trying to coax MSI interrupts out of AHCI and times out -- a minute for every SATA port, which can be several. It may still be the case, depending at what moment the first screenshot was taken. But if they were taken together, it's prossible that the crash in the r8169 prevents libata from working.
If it were my system, I would coax it into working (I can, for instance, build my own installation media with relevant patches), but in Rand's case it looks like a total loss (unless he feels adventurous and wants to give F10 alpha a try -- I'm using it on this laptop right now, works great :-)). So, seems like Ubuntu time. Hitting a correct version of Ubuntu should to avoid the unlucky patch of 2.6.25 with broken r8169.
Rand Simberg wrote:
What's the potential downside of F10 alpha?
Pete Zaitcev wrote:
F10 may not work for you for any number of silly reasons. For example, the official update kernel from a couple of days ago does not allow graphics to work on my Radeon (I use the older one from Alpha itself while this problem is being fixed). It can be said that it's exactly the kind of wrong F9 has done to you with r8169. But statistically F10 is probably buggier. Not as big a use base. So it's a game of chance.
Also, you'll have to update to Beta and release, because the 3rd party software will gradually be updated and require newer libraries.
Rand Simberg wrote:
But no harm in giving it a try? I assume that I can upgrade to beta and release via yum? Or just burn another DVD?
Pete Zaitcev wrote:
I use yum. But there's a chance that we're just wasting your time.
Hmm... you could try installing in text mode, assuming F9 still has that option. (Haven't read the previous post, so not sure if this was already tried.) It would bypass the need for a lot of higher-level drivers. You could get a base install on, update the kernel to get around the broken driver(s), then do a graphical install of any packages you want that weren't in the base. It's a lot of hassle though; you would likely be better off just going to a distro that works with your h/w. Depends on whether you want to get working quickly or learn more on the way there.
Andy wrote:
Get a Mac.
Josh Reiter wrote:
"
Andy wrote:
Get a Mac.
August 12, 2008 6:01 AM
Into the Pit of Doom with him!
Charlie wrote:
It sounds to me like you need to DISABLE the onboard ethernet in the BIOS before installing. If the Realtek is disabled Fedora won't look for a driver for it.
Bet you a virtual quarter that would get you to the next step in the installation.
You wouldn't need to LEAVE the ethernet disabled. After Fedora is fully installed, you should be able to re-activate it in the BIOS and load a working driver.
Rand Simberg wrote:
It sounds to me like you need to DISABLE the onboard ethernet in the BIOS before installing.
If I could find a way to do that in the BIOS, it would be a great idea. But as far as I've found, the BIOS provides very little capability to tinker with the configuration.
Hey halfwits. Looking at the moronic comments about the little kerrfuffle in Georgia brought me here. You have no idea do you?
Your install: The DVD drive not being found is the problem with the second screener. You lot should probably leave the stream of consciousness booting messages alone as they will just confuse you.
Rand Simberg wrote:
Hey halfwits.
Well, if we're "halfwits" we seem to be way ahead of you.
The DVD drive not being found is the problem with the second screener [sic].
Yes.
Right.
Because the fact that it is being installed from the DVD up until this point means that it can't find the DVD...
You lot should probably leave the stream of consciousness booting messages alone as they will just confuse you.
Well, pseudonymous moron, you certainly seem to speak from experience.
Charlie wrote:
It sounds to me like you need to DISABLE the onboard ethernet in the BIOS before installing.
If I could find a way to do that in the BIOS, it would be a great idea.
Ok, I've got another idea.
1) Create a small (
2) Install VMware or other virtual machine SW.
3) In the VM confguration, disable any problematic devices.
4) in the VM session, install Fedora.
5) Boot the laptop from your Live Ubuntu CD.
6) Install the boot manager to enable your Linux Fedora partition.
7) ???
8) Profit
Charlie wrote:
Hmm. my #1 above failed HTML conversion.
It should read:
1) Create a small (under 4GB) partition and install XP.
2) Install VMware or other virtual machine SW.
Pete Zaitcev wrote:
VmWare? If we want to talk far-fetched workarounds, it's always possible to install F9 to a USB drive on other computer, replace its kernel with one from updates to have Realtek working, make a USB boot device with syslinux and boot that. Copying to the internal hard drive is optional. It's only a question of desire to spend time and money on it.
Godzilla wrote:
I would just use Ubuntu. I have switched from Fedora years ago, and never looked back.
PenGun sounds like the tech support guys in India we sometimes talk to. "What do you mean, it doesn't work? You idiot, try plugging it in, and if that doesn't work, install from the old 2.6B CD. Now go away and find someone else to bother with your silly questions."
Toshiba and Panasonic laptops sometimes have a similar problem installing RH Linux.
The note about AHCI (in an earlier thread) seems to be relevant - I came across that in a Search for the problam.
Leave a comment
Note: The comment system is functional, but timing out when returning a response page. If you have submitted a comment, DON'T RESUBMIT IT IF/WHEN IT HANGS UP AND GIVES YOU A "500" PAGE. Simply click your browser "Back" button to the post page, and then refresh to see your comment.
About this Entry
This page contains a single entry by Rand Simberg published on August 11, 2008 11:38 AM.
I assume you tried Carl's suggestion. I'm not a Linux person, so I've skipped the previous post. However, your screenshot reminded me of the Windows OS install "Hit F6 to load device drivers". If you don't hit F6 for the latest hard drive drivers, you are typically SOL for seeing the harddrive and continuing the install. I went back in read the previous comments, and like you, I think Carl is right. He typically is.
Looking at the top screenshot, it appears to have a problem loading the RealTek RTL-8169 Gigabit Ethernet driver as near as I can tell. Are you attempting to install over the network either via http, nfs, or ftp?
No, I'm installing from a DVD.
Damn shame for the oops in the Realtek driver. I think I can guess why it happened. The driver was unable to extract the MAC from this chip in rtl8169_get_mac_version, but when it tried to report the problem, it crashed in because in 2.6.25 the tp->pci_dev is assigned after rtl8169_get_mac_version is called.
This does not help us with the main problem much, unfortunately. Rand cannot install F8 and then upgrade, because it's very likely that F8 has the same old r8169 and dies the same way. And it's a lot of hassle. Although the updated kernel for F9 (2.6.25.11-97.fc9) is likely fixed, it is not on the installation media.
Unlike many UNIXes, Linux shrugs off crashes in kernel if it can (e.g. if the CPU wasn't keeping an essential lock, in which case everyone else will quicky die). So perhaps we can just ignore the Realtek problem, which is only keeping a modprobe process. But there's more.
The second screen just tells us that libata was unable to initialize SATA (this is why I suggested pci=nomsi, it's a common issue for F9 vintage kernels). The long hang seemed like the delay that happens when libata is trying to coax MSI interrupts out of AHCI and times out -- a minute for every SATA port, which can be several. It may still be the case, depending at what moment the first screenshot was taken. But if they were taken together, it's prossible that the crash in the r8169 prevents libata from working.
If it were my system, I would coax it into working (I can, for instance, build my own installation media with relevant patches), but in Rand's case it looks like a total loss (unless he feels adventurous and wants to give F10 alpha a try -- I'm using it on this laptop right now, works great :-)). So, seems like Ubuntu time. Hitting a correct version of Ubuntu should to avoid the unlucky patch of 2.6.25 with broken r8169.
What's the potential downside of F10 alpha?
F10 may not work for you for any number of silly reasons. For example, the official update kernel from a couple of days ago does not allow graphics to work on my Radeon (I use the older one from Alpha itself while this problem is being fixed). It can be said that it's exactly the kind of wrong F9 has done to you with r8169. But statistically F10 is probably buggier. Not as big a use base. So it's a game of chance.
Also, you'll have to update to Beta and release, because the 3rd party software will gradually be updated and require newer libraries.
But no harm in giving it a try? I assume that I can upgrade to beta and release via yum? Or just burn another DVD?
I use yum. But there's a chance that we're just wasting your time.
Hmm... you could try installing in text mode, assuming F9 still has that option. (Haven't read the previous post, so not sure if this was already tried.) It would bypass the need for a lot of higher-level drivers. You could get a base install on, update the kernel to get around the broken driver(s), then do a graphical install of any packages you want that weren't in the base. It's a lot of hassle though; you would likely be better off just going to a distro that works with your h/w. Depends on whether you want to get working quickly or learn more on the way there.
Get a Mac.
"
Andy wrote:
Get a Mac.
August 12, 2008 6:01 AM
Into the Pit of Doom with him!
It sounds to me like you need to DISABLE the onboard ethernet in the BIOS before installing. If the Realtek is disabled Fedora won't look for a driver for it.
Bet you a virtual quarter that would get you to the next step in the installation.
You wouldn't need to LEAVE the ethernet disabled. After Fedora is fully installed, you should be able to re-activate it in the BIOS and load a working driver.
It sounds to me like you need to DISABLE the onboard ethernet in the BIOS before installing.
If I could find a way to do that in the BIOS, it would be a great idea. But as far as I've found, the BIOS provides very little capability to tinker with the configuration.
Hey halfwits. Looking at the moronic comments about the little kerrfuffle in Georgia brought me here. You have no idea do you?
Your install: The DVD drive not being found is the problem with the second screener. You lot should probably leave the stream of consciousness booting messages alone as they will just confuse you.
Hey halfwits.
Well, if we're "halfwits" we seem to be way ahead of you.
The DVD drive not being found is the problem with the second screener [sic].
Yes.
Right.
Because the fact that it is being installed from the DVD up until this point means that it can't find the DVD...
You lot should probably leave the stream of consciousness booting messages alone as they will just confuse you.
Well, pseudonymous moron, you certainly seem to speak from experience.
It sounds to me like you need to DISABLE the onboard ethernet in the BIOS before installing.
If I could find a way to do that in the BIOS, it would be a great idea.
Ok, I've got another idea.
1) Create a small ( 2) Install VMware or other virtual machine SW.
3) In the VM confguration, disable any problematic devices.
4) in the VM session, install Fedora.
5) Boot the laptop from your Live Ubuntu CD.
6) Install the boot manager to enable your Linux Fedora partition.
7) ???
8) Profit
Hmm. my #1 above failed HTML conversion.
It should read:
1) Create a small (under 4GB) partition and install XP.
2) Install VMware or other virtual machine SW.
VmWare? If we want to talk far-fetched workarounds, it's always possible to install F9 to a USB drive on other computer, replace its kernel with one from updates to have Realtek working, make a USB boot device with syslinux and boot that. Copying to the internal hard drive is optional. It's only a question of desire to spend time and money on it.
I would just use Ubuntu. I have switched from Fedora years ago, and never looked back.
PenGun sounds like the tech support guys in India we sometimes talk to. "What do you mean, it doesn't work? You idiot, try plugging it in, and if that doesn't work, install from the old 2.6B CD. Now go away and find someone else to bother with your silly questions."
Toshiba and Panasonic laptops sometimes have a similar problem installing RH Linux.
The note about AHCI (in an earlier thread) seems to be relevant - I came across that in a Search for the problam.