Opened 14 years ago
Closed 14 years ago
#6295 closed bug (fixed)
dhcp on rtl81xx
Reported by: | tonestone57 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Network | Version: | R1/Development |
Keywords: | Cc: | khallebal@… | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
dhcp and internet works on hrev37423
dhcp and internet do not work on hrev37453. Giving me an IP address of 169.254.0.11
device Network controller (Ethernet controller) [2|0|0] vendor 10ec: Realtek Semiconductor Co., Ltd. device 8136: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
Could be affected by change in hrev37425? (just guessing)
Syslog to follow in next couple of days.
Attachments (1)
Change History (14)
comment:1 by , 14 years ago
by , 14 years ago
Attachment: | syslog_37453 added |
---|
comment:2 by , 14 years ago
I was hoping for best guess but to make things easier I attached syslog to ticket. :-)
comment:3 by , 14 years ago
Same here, cannot set DHCP on RTL81xx on new rev's.
BTW. DHCP jumps to STATIC after restarting PC.
Setting STATIC IP also dont work. Internet connection cannot be used.
comment:5 by , 14 years ago
Took quick look and believe the no PHY (in syslog)
"KERN: [rtl81xx] (miibus) No PHY module found (20/20)!"
could relate to change in hrev37425
from:
HAIKU_FBSD_MII_DRIVER(rlphy);
to:
HAIKU_FBSD_MII_DRIVER(rgephy);
comment:6 by , 14 years ago
Yes, that's what I figured out as well, but thanks for looking into it. I will fix this in the next few weeks; in the mean time, you could revert that particular change in your local copy to make it work again (you will also have to revert the Jamfile changes).
comment:7 by , 14 years ago
Cc: | added |
---|
comment:9 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
dhcp still not working with RTL81xx with rev:38259 gcc4 hybrid.when assigning a static adress i can connect to internet,but not with dhcp.
follow-up: 11 comment:10 by , 14 years ago
I can confirm the problem with ipro1000 as well, so don't expect it's driver specific. I think I've seen it working once, after a reboot, with the wifi hardware button disabled, but mostly it doesn't work in that situation either. Static configuration seems to work mostly.
comment:11 by , 14 years ago
comment:13 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
That should definitely be related; without a syslog, it's hard to do anything about it, though :-)