Latest nightly breaks wireless again

using hrev58933, my iaxwifi200 chipset won’t connect to the internet anymore, after a new error with an unsupported opcode, DHCP fails.
Same works fine under hrev58926 in the same environment:

KERN: openbsd wlan_control: 9235, 16 (not supported)
KERN: iwx: SCAN -> INIT
KERN: Last message repeated 2 times.
KERN: iwx: SCAN -> AUTH
KERN: iwx: AUTH -> ASSOC
KERN: iwx: ASSOC -> RUN
KERN: /dev/net/iaxwifi200/0: link up, media 0x870080 quality 1000 speed 0
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Timeout shift: 500 msecs (try 1)
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Timeout shift: 1000 msecs (try 2)
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Timeout shift: 2000 msecs (try 3)
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Timeout shift: 4000 msecs (try 4)
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
KERN: slab memory manager: created area 0xffffffffc9801000 (15382)
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Timeout shift: 8000 msecs (try 5)
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Timeout shift: 60000 msecs (try 6)
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
2 Likes

Also my usb tethering is broken (usb_rndis)

Please open a ticket, this does not belong on the forum.

Ok, was just thinking it’s maybe only short term anyway and didn’t want to overload Trac, but it’s actually cleaner.
Forum should be too discuss and track down issues, not for reporting.

I don’t think you need to worry too much about overloading trac, we do ticket triaging ourselves (as developers) to make it easier to report issues there. It’s no biggy if you forget some information for example, it will just be asked later on then.
Tracking down issues should also be on the bugtracker, if you have an issue with a current version but don’t know if it is a regression or not you can still post it. :slight_smile:

1 Like

https://dev.haiku-os.org/ticket/19652#comment:1

2 Likes

Ah couldn’t get around to do it yet, will add my syslog there.

I don’t think it’s just wireless. I’m running on QEMU/KVM and have no connectivity after going from hrev58930 to hrev58933.

1 Like

Ethernet on a bare metal machine is broken here as well.
Reverting the latest update helps.

1 Like

Problem was fixed in hrev58935, so the next nightly should work again.

8 Likes

too hard to make one

yesterday, after the update and rebooting, I switched off
Today, USB tethering, wifi hotspot not working…I thought it was some issue with mobile network…
Thank God…

Now, I cannot connect to network in any way
Even to download patch/ next update, it is not possible for me…no LAN connection…
How can I resolve my issue? Pl. Guide
I don’t keep old data…I delete last hrev’s with filwip

Don’t do that then :person_facepalming:. This is exactly what states guard against. You could atleast have tested the new state before deleting the old one

You have two options: if you have the skill configure your LAN manually without dhcp.

And if you do not: download the newer nightly on another pc, burn it to a stick. Mount it in your computer, manually install packages from it with pkgman.

You can ask @kallisti5 for help… I don’t manage the bugtracker

just set a static IP in the Network preferences, see attached screenshot.
Be sure to use a free IP that is not managed/reserved by your router or used by another device.

1 Like

As I wrote earlier, I do not have any gadgets required for LAN connection…only mobile hotspot or mobile USB tethering…much as I don’t want to re-install, this is the third time I am forced to…maybe I will stop using filwip to delete old hrev’s…

Ah I see, but a mobile hotspot is just like a wireless connection to Haiku, so it should work in the same way. You might need to configure the hotspot to assign a static IP to your MAC, though.
Update: oh no, seems this is not really possible. You need to check the IP of your hotspot and set it manually for every session, unfort. Everyhing else requires a rooted phone.

Thank you for your suggestion…but I was impatient…re-install again…thanks…

1 Like

Yes, if you use the nightly builds, you get all the latest experiments from developers, and sometimes something breaks. So that requires being careful, keeping backups, and following on the current developments to “smell” when it’s safe to update and when someone just pushed a big change that’s likely to break something critical.

If you want to not think too much about that, better stay with the beta releases.

2 Likes

I have to say the advantages of all improvements by far outweighs the occasional issues. I find the nightlies quite stable.

Just keep your old snapshots, at least the last working version, so you can revert just in case.

1 Like