I finally succumbed and installed Alpha 5, fixed the plasma and display problems but I am stuck as to why the networking is screwed. I cannot get either ethernet or wireless to work, this is amazing really that after all the previous releases something as basic as that is not working. Any ideas?
Announcement
Collapse
No announcement yet.
Networking Screwed (Solved)
Collapse
This topic is closed.
X
X
-
Re: Networking Screwed
Originally posted by tomp01
I am having to compose this post with XP, oh the shame of it all!!
Well, I haven't worked up the nerve (or time) to fool with 9.04 yet -- I'm holding off for the Beta release later this month. But, did you try the normal network diagnostic stuff?
Code:sudo ifconfig
Code:sudo iwconfig
- Top
- Bottom
Comment
-
Re: Networking Screwed
Originally posted by diblOriginally posted by tomp01
I am having to compose this post with XP, oh the shame of it all!!
Well, I haven't worked up the nerve (or time) to fool with 9.04 yet -- I'm holding off for the Beta release later this month. But, did you try the normal network diagnostic stuff?
Code:sudo ifconfig
Code:sudo iwconfig
- Top
- Bottom
Comment
-
Re: Networking Screwed
[quote=tomp01 ]
Originally posted by diblOriginally posted by tomp01
I am having to compose this post with XP, oh the shame of it all!!
Code:sudo ifconfig
Code:sudo iwconfig
This is the output from those commands:
eth0 Link encap:Ethernet HWaddr 00:17:31:b6:9f:47
inet6 addr: fe80::217:31ff:feb6:9f47/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:684 (684.0 B) TX bytes:1184 (1.1 KB)
Interrupt:23 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:372 errors:0 dropped:0 overruns:0 frame:0
TX packets:372 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28928 (28.9 KB) TX bytes:28928 (28.9 KB)
wlan0 Link encap:Ethernet HWaddr 00:11:50:8f:5b:7f
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wmaster0 Link encap:UNSPEC HWaddr 00-11-50-8F-5B-7F-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tom@tompc:~$ sudo iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=23 dBm
Retry min limit:7 RTS thrff Fragment thr=2352 B
Encryption keyff
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
- Top
- Bottom
Comment
-
Re: Networking Screwed
Hmmm. And this same machine connects OK with Windows?
Comparing your output to what I get on my Intrepid box, your number of Tx and Rx packets is incredibly small -- mine are 2,000 plus. But, there aren't errors.
Can you ping anything? In the console, try (as a user)Code:ping [url]www.google.com[/url]
- Top
- Bottom
Comment
-
Re: Networking Screwed
Originally posted by diblHmmm. And this same machine connects OK with Windows?
Comparing your output to what I get on my Intrepid box, your number of Tx and Rx packets is incredibly small -- mine are 2,000 plus. But, there aren't errors.
Can you ping anything? In the console, try (as a user)Code:ping [url]www.google.com[/url]
- Top
- Bottom
Comment
-
Re: Networking Screwed
Originally posted by tomp01Originally posted by diblHmmm. And this same machine connects OK with Windows?
Comparing your output to what I get on my Intrepid box, your number of Tx and Rx packets is incredibly small -- mine are 2,000 plus. But, there aren't errors.
Can you ping anything? In the console, try (as a user)Code:ping [url]www.google.com[/url]
- Top
- Bottom
Comment
-
Re: Networking Screwed
Well, if I were you and interested in seeing it fixed, I would first search Launchpad to see if this bug has already been filed, and if not, then I would file it there.
As far as getting a fix for it, I think you have little choice but to await the updates and hope one of them has the corrected code in it.
Also, since it could be specific to your hardware (your ethernet chip), you might want to search around for reports of driver issues under the 2.6.28 kernel, for that chip. 8.10 runs the 2.6.27 kernel, so a faulty kernel module in 9.04 could be the problem.
- Top
- Bottom
Comment
-
Re: Networking Screwed
Originally posted by diblWell, if I were you and interested in seeing it fixed, I would first search Launchpad to see if this bug has already been filed, and if not, then I would file it there.
As far as getting a fix for it, I think you have little choice but to await the updates and hope one of them has the corrected code in it.
Also, since it could be specific to your hardware (your ethernet chip), you might want to search around for reports of driver issues under the 2.6.28 kernel, for that chip. 8.10 runs the 2.6.27 kernel, so a faulty kernel module in 9.04 could be the problem.
- Top
- Bottom
Comment
-
Re: Networking Screwed
Originally posted by tomp01Originally posted by diblWell, if I were you and interested in seeing it fixed, I would first search Launchpad to see if this bug has already been filed, and if not, then I would file it there.
As far as getting a fix for it, I think you have little choice but to await the updates and hope one of them has the corrected code in it.
Also, since it could be specific to your hardware (your ethernet chip), you might want to search around for reports of driver issues under the 2.6.28 kernel, for that chip. 8.10 runs the 2.6.27 kernel, so a faulty kernel module in 9.04 could be the problem.
I manually edited /etc/network/interfaces and added eth0, it now works. I am now downloading 200 odd meg of updates so hopefully this will fix knetworkmanager.
- Top
- Bottom
Comment
Comment