Bug 158410
| Summary: | Failure to recognise Broadcom NetXtreme NIC | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sean Bruno <sbruno> | ||||
| Component: | kernel | Assignee: | John W. Linville <linville> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4 | CC: | davej, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2005-05-27 01:05:33 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
Sean Bruno
2005-05-22 01:25:58 UTC
When you install 32bit FC4, UP kernel works, but SMP kernel gets stuck during bootup? http://people.redhat.com/wtogami/temp/kernel-smp-2.6.11-1.1267_FC4.i686.rpm Please test if it gets stuck during bootup with this older SMP kernel and report back. You may need to install it manually with rpm --oldpackage --nodeps. The x86_64 issue you mention is probably a different bug than the 32bit SMP problem. I'm seeing the 32bit SMP problem too on my dual opteron. Haven't tested x86_64 yet. Bug #158413 is the 32bit SMP kernel unable to boot, while UP kernel does. Thanks for the information, I have updated Bug #158413 with my test info on the kernel that you posted. I was able to boot that SMP kernel, but the ethernet(Broadcom) seems to be having issues. Please email me if you folks want to get into my machine and poke around. Nothing sensitive on it as I just built the box. The boot.iso (x86_64) from today's rawhide still fails to use the Broadcom adapter on my machine correctly. I have attached the output of lspci -vv to this ticket. Does it seem that it should work? Created attachment 114784 [details]
Output of lspci -vv on ASUS K8N-DL, dual 246, 6gb ram
I was able to install Fedora directly from Rawhide last night. I disabled the Broadcom NetXtreme Ethernet adapter and installed an Intel 10/100 pro to get past the first set of problems I was having. I currently am seeing a "garbled" screen when firstboot starts. It doesn't appear that I can interact with the screen in anyway. This is a PCI-E based video card(Nvidia 6200 from Asus). I can't seem to move any further along once the screen goes into this "garbled" state. Any ideas? The following errors appear just as the kernel starts(post grub but before "Nash starting" PCI: Cannot allocate region 9 of device 0000:00:0e.0 PCI: Cannot allocate region 3 of device 0000:04:00.0 Failed to allocate mem resource 1000000@fe0000000 for 0000:04:00.0 According to the lspci from the attachment in Comment #5, the first error is from the nVidia Corporation CK804 PCIE Bridge. The second error is from nVidia Corporation NV44 [GeForce 6200 TurboCache] which would explain the mem resource error and the garbled screen. These errors do no manifest themselves in the i386 version. The garbled screen could be an xorg bug. As you've mentioned a number of different problems in this bug (SATA, Ethernet, and now the garbled display), I can't reassign this as an X bug, so I recommend opening a separate bug for that. The hang with the SATA drive you mentioned as the first entry in this bug sounds like its now fixed, leaving just your failing Broadcom card, correct ? Please file seperate bugs for multiple issues in future, it makes the bug-history very difficult to read at times when the subject jumps back and forth between different issues. No problem. At this point it would be better to track the Broadcom stuff off of Bug #158468. This is one of three tickets that I have filed in regards to my new MoBo. Since this ticket is basically a "stream-of-conciousness" type of rambling on my part, I am closing it in order to simplify my issues. |