If the page is no longer relevant, perhaps it should be hidden or deleted?
Maybe move the link on the firmware instructions to under some hardware that needs it ? Or maybe, if nothing needs that download of firmware, bury the instructions somewhere where people just looking for setup instructions would not find it ?
( it seems to me this sounded a little bit harsh, but I could not find a better way to phrase it. Like, if people should not be doing that, how about put the instructions in some place where normally they wouldn´t find them ? )
It is relevant for the affected hardware, but not for any modern cards. That older hardware is still supported by Haiku, so removing or hiding the page is not the right thing to do.
Really, what we need is more feedback in Haiku UI. The Network or Devices preferences should show a little “checklist”: driver OK, firmware OK, network enumeration OK, association with AP OK, password authentication Ok‚ etc. Rigqt now it’s difficult to see how far things went.
8 Likes
Yepp, that’s it for booting too … but it is not specific for Haiku only.
Simple feedback about reached states are missing generally for many apps / solutions. Of course logs contains all the infos, sometimes more than an average user can read to ‘grock’ easily where is the stucking stuff.
Good to know that I don’t need to manually load the firmware.
So how do I get it working?
I think the “scan” command is not supported on OpenBSD-based drivers at the moment. You can try “list” which will display already-completed scan results, or just use Network preferences in the GUI.
There are a variety of different Intel firmware licenses. Some do permit redistribution, and Linux bundles these (while the BSDs usually do not); we package those and ship them with builds. Some very old firmwares have stricter terms, and we don’t ship those by default.
2 Likes
I have no idea, but WLAN works for me:
I made some adjustments in hrev56940 that should make ifconfig ... scan behave identically to ifconfig ... list on OpenBSD drivers, so the confusing error message should now be gone regardless.
2 Likes
I just tried hrev56953, the scan command now returns a different error. Also this revision seems to PANIC if I try and shutdown after I have run those net commands. See attached screenshots.
The KDL might be a bit of a fluke caused by the driver getting into an invalid state.
Can you please open a ticket and attach a syslog?
@waddlesplash Is there any documentation about how to do this please? Sorry I used to use BeOS many years ago and I have probably forgotten more than I remember about that, also I am relatively new to Haiku.
@waddlesplash Can I also ask what steps I should take next to work towards getting my Wifi card working? As I understand it, it is suggested that this card should be supported by Haiku. What can I try next and/or what information can I provide next to assist in debugging?
Thanks @Starcrasher so, do I just need to attach the photo from above to a new ticket? @waddlesplash mentioned a syslog but I am not clear where that comes from in KDL?
See the dev as a detective and the bug as a murder. The screenshot of the KDL is like a picture that shows that the victim has a bullet hole in the chest. You can say that a gun has been used but it won’t give you the one who took the shot. To understand what really happened, the detective needs more information on the context and will look for a CCTV that caught the scene. That’s exactly the role of the syslog. It can give the dev intel about your hardware, the version of Haiku that you’re running, and what happened right before you entered KDL. With a bit of luck and perspicacity, you can catch your bug…
So yes, open a ticket and provide all the info that you can give. In addition, put also a link to this thread. And, don’t worry, if a similar ticket already exists, the triage team will find it.
3 Likes
/boot/system/var/log is the directory you can find syslog
~> ls -l /boot/system/var/log/
total 860
-rw-r–r-- 1 user root 109 máj. 3 22:44 es1370.log
-rw-r–r-- 1 user root 211656 ápr. 29 21:41 previous_syslog
-rw-r–r-- 1 user root 111978 máj. 4 12:36 syslog
-rw-r–r-- 1 user root 524335 máj. 4 11:06 syslog.old
~>
Supportable… on Haiku…
Basic info to include in the bug ticket:
- Host machine (make/model)
- Wifi device (make/model)
- Output of ‘uname -a’ in terminal
- Output from ‘listdev’ in terminal
- Output from ‘listimage|grep "dev/net’ in terminal
- Output from ‘listusb’ in terminal
- Copy of /var/log/syslog
- Screenshot of any “KDL” condition (use commands in debug console)
Currently nightly is: hrev56966
1 Like
I just tried this again after almost a year using Haiku hrev57708 but unfortunately I am getting the same results and errors as last year (hrev56932). I will try and find the time to report more detailed information soon…
FYI my Wifi AX210 works in with AMD PC (5800H/B550).
~> uname -a
Haiku shredder 1 hrev56578+96 Apr 21 2024 06:25: x86_64 x86_64 Haiku
~> lspci | grep Net
06:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)
~> ifconfig /dev/net/iaxwifi200/0
/dev/net/iaxwifi200/0
Hardware type: Ethernet, Address: a4:f9:33:a1:b6:5c
Media type: 802.11ac
Network: JRU, Address: 78:98:e8:d8:75:60, WPA2, PSK/CCMP
inet addr: 192.168.1.107, Bcast: 192.168.1.255, Mask: 255.255.255.0
MTU: 2294, Metric: 0, up broadcast link auto-configured
Receive: 2786 packets, 0 errors, 1981755 bytes, 0 mcasts, 0 dropped
Transmit: 1157 packets, 0 errors, 132108 bytes, 0 mcasts, 0 dropped
Collisions: 0
~> listusb | grep -i intel
8087:0032 /dev/bus/usb/0/10/3 “Intel Corp.” “AX210 Bluetooth” ver. 0000
1 Like
~> listdev ?