| View previous topic :: View next topic |
| Author |
Message |
Luka21
n00b
Joined: 24 Aug 2004
Posts: 39
|
 Posted: Mon Jul 04, 2005 12:27 pm Post subject: Xorg kills network connectivity - solved |
 |
|
For some strange reason xorg's configuration can resault in loosing network connectivity even pinging dies (perhaps other hardware problms as well).
Systems affected (the list might grow):
Acer aspire 1600 notebook using radeon 9000 mobility with 2.6.11 and 2.6.12 kernerl's opensource radeon driver for drm.
Solution:
Use ati's proprietary drivers and enjoy lockups - although ati marked my ticked as resolved 
Last edited by Luka21 on Tue Jul 05, 2005 4:37 pm; edited 3 times in total |
|
| Back to top |
|
 |
SuperJudge
Apprentice
Joined: 08 Jun 2004
Posts: 177
Location: Albany, GA
|
| Posted: Mon Jul 04, 2005 12:42 pm Post subject: |
|
|
I haven't ever had that happen, may just have been an anomaly.
_________________
---Powered by Honda |
|
| Back to top |
|
|
Luka21
n00b
Joined: 24 Aug 2004
Posts: 39
|
| Posted: Tue Jul 05, 2005 1:40 pm Post subject: |
|
|
Now I am really confused - nothing I do solves the problem this is really strange.
I tried unmerging / emerging xorg. removing /etc/X11, and still the moment that I strar X (just the server) the ping reports network unreachable.
I am using -nolisten tcp flag and I don't even care for x's network abilities, as I don't requier it.
I tried both 6.8.2-r1 and 6.8.2-r2 versions of xorg. Dmesg and other logs don't indicate any problems, route tables stay untouched. equery check xorg-x11 reports only font changes which are normal. The problem is kernel independant.
Any suggestions? |
|
| Back to top |
|
|
Jake
Veteran
Joined: 31 Jul 2003
Posts: 1132
|
| Posted: Tue Jul 05, 2005 2:38 pm Post subject: |
|
|
| Luka21 wrote: | | The problem is kernel independant. |
Do you mean you have the same problem on other systems that support Xorg, like *BSD, Solaris, etc, or that there's no difference between Linux 2.6.x and Linux 2.6.y?
I think what would really help here is knowing when the problem started. Have you ever been able to run X on this machine? |
|
| Back to top |
|
|
Luka21
n00b
Joined: 24 Aug 2004
Posts: 39
|
| Posted: Tue Jul 05, 2005 4:26 pm Post subject: |
|
|
My original post needs alot of editing to make it comprehensive.
The riddle is finaly solved and I think more people will have this problems - it's just that it will show in different ways.
The problem seems to be in kernels open source radeon driver for drm. (I have radeon mobility 9000, R250lf chip)
The moment that Xorg loaded dri module, kernel reported that it detected R200 (don't know if this is caused the problem), but dmesg actulay did hold some valuable information in outputet something about irq 193 that nobody cared! - it litteraly said that . Seems like this influenced on my ethernet card.
Same simptoms were detected with 2.6.11-r9, 2.6.12 and 2.6.12-r3 gentoo sources on x86 platform
Solution:
Switching to ati's closed sorce drivers fixed the problem. so dmesg now says:
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 193
and this is the address of my video card.
Maybe this is just a bad hardware combination or whatever, but I am curious if anyone else using kernel's ati radeon driver for dri is affected. |
|
| Back to top |
|
|
|
Networking & Security
