|
Bugzilla – Full Text Bug Listing |
| Summary: | forcedeth driver cannot send packets | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Herbert Graeber <herbert> |
| Component: | Kernel | Assignee: | Karsten Keil <karsten.keil> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Output of /sbin/lspci -vn -s 00:0a.0
Output of /sbin/lspci -vnb -s 00:0a.0 |
||
|
Description
Herbert Graeber
2005-09-16 21:44:39 UTC
*** Bug 117577 has been marked as a duplicate of this bug. *** Did you try the various ACPI options (like "acpi=off")? (In reply to comment #2) Yes, I have tried "acpi=off". Using this my system doesn't boot at all. I think most x86_64 systems need acpi. "acpi=noirq" doesn't make any change, except that there are some additional powersave related error messages in /var/log/messages. "pci=noacpi" has no effect. Please submit the output of /sbin/lspci -vn -s 00:0a.0 and if it is different /sbin/lspci -vnb -s 00:0a.0 Created attachment 54212 [details]
Output of /sbin/lspci -vn -s 00:0a.0
Created attachment 54213 [details]
Output of /sbin/lspci -vnb -s 00:0a.0
After Installing the final version SUSE 10.0 the bug remains. I added another network adapter to my machine, configured the NIC controlled by forcedeth to a fixed IP address (I have used DHCP before) and verfied that it doesnt't work again. So that i would be able to check the not working NIC agin as often as neccessary. <snd so I did from time to time. Now directly after providing the output of /sbin/lspci -vn -s 00:0a.0 and /sbin/lspci -vnb -s 00:0a.0, I discovered that it works now. So only to verify that I understand the last comment correctly: The adapter is now working with the 10.0 final version. Does this be also the case after a reboot, if yes we can close this issue I think. Yes it doesn't work for some days, so I inserted a additional network card to keep the system running. After gathering the information you requested, i discovered that it worked. Now I have done a completely new installation, because of defect harddisk, and the adapter works from the beginning. So, the bug can be closed. Maybe also a temporary hardware problem (contacts ...) Hello, This is a critical bug that is in forcedeth 0.35, (Bug 119026) and should be fixed in 0.42 (see http://bugzilla.kernel.org/attachment.cgi?id=5234&action=view). However, it is not YET fixed. Jens *** This bug has been marked as a duplicate of 119026 *** |