Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#9131 closed bug (fixed)

No internet or network adaptor shown in Network preferences

Reported by: HAL Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/rtl81xx Version: R1/Development
Keywords: Cc: HAL
Blocked By: Blocking:
Platform: All

Description

I have no internet access and my network chip RTL8111/8168B is not shown in Network application. Browsers WebPositive and Bezilla wont connect to any internet address neither will any ping command in Terminal work. I noticed this after installing a new mainboard ASUS M5A97 R2.0. I was testing in haiku-hrevr1alpha4-44663. I will attach output of lspci from Ubuntu and a screenshot of Network.

Attachments (4)

lspci in ubuntu.txt (3.0 KB ) - added by HAL 12 years ago.
No Adaptor.png (14.5 KB ) - added by HAL 12 years ago.
Network window
syslog.txt (62.6 KB ) - added by HAL 12 years ago.
Message in syslog Unknown H/W revision
syslog.2.txt (349.4 KB ) - added by HAL 12 years ago.

Download all attachments as: .zip

Change History (19)

by HAL, 12 years ago

Attachment: lspci in ubuntu.txt added

by HAL, 12 years ago

Attachment: No Adaptor.png added

Network window

comment:1 by anevilyak, 12 years ago

Component: Network & InternetDrivers/Network/rtl81xx
Milestone: R1/alpha4Unscheduled
Priority: blockernormal

Please attach a syslog. A screenshot of empty net prefs tells us nothing useful whatsoever.

by HAL, 12 years ago

Attachment: syslog.txt added

Message in syslog Unknown H/W revision

comment:2 by HAL, 12 years ago

I added syslog with a extra space added from where the network device detection starts then another gap at end where memory is freed up.

comment:3 by diver, 12 years ago

91	KERN: [rtl81xx] (re) Using 1 MSI message
92	KERN: [rtl81xx] (re) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x2)
93	KERN: [rtl81xx] (re) Chip rev. 0x48000000
94	KERN: [rtl81xx] (re) MAC rev. 0x00000000
95	KERN: [rtl81xx] (re) Unknown H/W revision: 0x48000000

http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/drivers/network/rtl81xx/dev/re/if_re.c#n1339

comment:4 by korli, 12 years ago

This revision is supported on FreeBSD 9 branch, so we should get it with the next round of FreeBSD drivers update.

comment:5 by HAL, 12 years ago

I tested with hrev45142. Network device is now detected but not configured properly. The default gateway and the 2 DNS addresses are missing with DHCP. I have not tried with static because I did not know all the addresses. I might try again but having difficulty in getting haiku to boot without KDL.

comment:6 by korli, 12 years ago

Did you check if your gateway dhcp worked OK with Haiku on another machine/network card? If yes, a syslog would be welcome.

in reply to:  6 comment:7 by HAL, 12 years ago

Replying to korli:

Did you check if your gateway dhcp worked OK with Haiku on another machine/network card? If yes, a syslog would be welcome.

Yes I am writing this on another computer with a VT6102 Rhine-II. With DHCP the numbers are a bit different than I had for Static so I will copy them from the network settings here and try again. I will attach a syslog if it works or not because it wont work on static at least.

comment:8 by HAL, 12 years ago

The settings I copied from the second computer did not work in static mode. In dhcp mode I compared the IP, netmask, gateway, dns # 1 and # 2 and domain. Compared from dhcp on working network on second computer to dhcp on non working network main computer. DHCP Working VT6102 Rhine IP: 192.168.1.5 Netmask: 255.255.255.0 Gateway: 192.168.1.1 DNS # 1: 192.168.1.1 DNS # 2: blank Domain: Home

RTL8169 IP:169.254.0.157 Netmask: 255.255.0.0 Gateway: 192.169.1.1 DNS # 1: 0.0.0.0 DNS # 2: 0.0.0.0 Domain: blank I tried to save the syslog on the USB stick I booted haiku on but it did not save. I got a message general operating system error. I think that was because the USB haiku partition is full with virtual memory set, so I tried to save to another HD partition but the menu to select it was frozen. I will try again tomorrow.

comment:9 by phoudoin, 12 years ago

RLT8169 IP:169.254.0.157

That's a local-link address, so clearly DHCP discover/request failed somewhere, question is why. And only a syslog will show why.

comment:10 by phoudoin, 12 years ago

I'll bet that's due to misworking network driver and DHCP discover simply timeout without any offers received, but that's just speculation.

by HAL, 12 years ago

Attachment: syslog.2.txt added

comment:11 by HAL, 12 years ago

In the syslog I uploaded most of the information about rtl81xx is near the end lines but some is nearer the middle and seems to be mixed with radeon card detection. I have a radeon HD 7850. Easier just to search the syslog with "rtl81xx".

comment:12 by phoudoin, 12 years ago

DHCP discovery timed-out. Unfortunately, I failed to see in the syslog why the network card failed to send and/or receive anything over its ethernet link.

comment:13 by HAL, 12 years ago

This bug now looks similar to #8930. That bug was reported 2 months ago. I am not certain if the FreeBSD 9 driver updates were applied just before.

comment:14 by korli, 11 years ago

Resolution: fixed
Status: newclosed

Your syslog is incomplete, the first part is missing, but this should be fixed in hrev45925.

comment:15 by HAL, 11 years ago

Yes network and internet is working now in.hrev45929. Thanks for fixing this.

Note: See TracTickets for help on using tickets.