I typed in the “install-wifi-firmwares.sh” and it said it installed successfully, but I can’t connect to wifi.
When I hook up to lan, it said “/dev/net/broadcom570x/0”. But if I disconnect from lan and use “ifconfig /dev/net/broadcom570x/0 dlink” it says that “’/dev/net/broadcom570x/0’ is not a WLAN device!”
I can’t comment on your broadcom card, but I had very little problem in getting a wifi connection on my EeePC 901 which has a Ralink RT2860 card with WPA2 encryption.
Essentially, I just followed what’s explained in the wiki on wireless connections.
One difference, however, is that I didn’t have to install a binary firmware module for this card.
The steps I followed were:
Install optional package wpa_supplicant
run the command ifconfig /dev/net/ralink2860/0 list
to list available networks.
Choose one network and run this command ifconfig /dev/net/ralink2860/0 join wifi_interface_name wifi_interface_password
(obviously substituting the relevant name and password for your network).
Nothing more than this and I had a wifi connection.
I was checking the WiFi connection on my Acer Laptop (Travelmate 4280) in order to help “nitt” and some funny/strange things are happening:
(the Acer WiFi has a prowifi3945 -Intel- chipset)
1- after booting, checking the Deskbar icon for network I can see all netcards listed but no WiFi network name.
2- checking the settings of the prowifi3945 in “Open network preferences…” in the Deskbar network icon the prowifi3945 is listed as if it were a LAN-Ethernet card only (not WLAN-WiFi)
3- launching “wpa_supplicant” from a terminal I got no messages but the cursor goes new-line (then I do Ctrl-C to get rid of the “pending” command).
4- after a while of the command 3- above and going back to 2- I see finally the prowifi3945 listed as WiFi along with other settings like Network: name and Mode:
5- doing apply on the screen of 4- I get a screen for Open/WEP/WPA/WPA2 selection and password input.
6- I can go no further because I don’t know the password (this is NOT my network) and I do Cancel.
7- However if from a terminal I enter “ifconfig /dev/net/prowifi3945/0 join network-name” OR the same but only with “join” (no network-name) I got this message:
ifconfig: “/dev/net/prowifi3945/0” is not a WLAN device!
which sounds quite strange indeed because I know it is a WLAN device and almost connected to a WiFi network (missing password…)
What happens?! (the graphical part seems to work better than the CLI commands).
Running wpa_supplicant from a terminal is also quite strange (it should be launched automatically from somewhere else) - what am I doing wrong?!
PS.: the broadcom570x (/dev/net/broadcom570x/0) is always seen/listed as a LAN card (NOT WLAN-WIFI) under Open network preferences… (as in 2- above)
The message that firmware was installed “successfully” does not mean that now WiFi will work, it only means that the files were installed ready for Haiku to use them. This message would appear if you have a WiFi device that’s not supported by Haiku, or even if you don’t have any wireless chipset at all.
The device /dev/net/broadcom570x/0 you have provided information about is a wired network chip, hence the “not a WLAN device” message.
You need to find information about your wireless network chipset.
This could be considered an heresy but…
why porting drivers from bsd if they really suck at them? wouldn’t it be better port them from GNU/Linux? is this impossible?
The reason for using BSD drivers instead of Linux drivers is that Haiku has a compatibility layer for FreeBSD network drivers. That means that we’ll get all those drivers for free, without having to port and maintain them. As to why exactly FreeBSD was chosen, I don’t know. Maybe that was easier, cleaner, more licence-compatible, or all of that…
As a quick websearch turned out, the Atheros AR5B97 isn’t yet supported by FreeBSD, but has a chance to appear in FreeBSD 9. They planned to release v9 in September, so I guess that’ll be available Real Soon Now.
I suggest filing an enhancement ticket at Haiku’s bugtracker as a reminder to have another look once FreeBSD 9 is out.
Same problem here with a HP laptop (from 2017 and almost impossible to identify due to the model number being printed underneath in like 2.2 point picas (too small for any human to possibly read). Really there should be a website that could identify any computer and what it contains. You would just go there and get a list of things. Most common things would be listed too that way. Without wifi, sadly, as it is a laptop, Haiku might have to leave me even though I’ve had fond memories of BeOS for well over 20 years.
If you have problems getting wifi to work on your machine please open a bugreport on http://dev.haiku-os.org . Include the output of the “listdev” command at a minimum so we can know which wifi chipset it is.
For Apple/Macs from all the way back to System 7 to present have either (Apple) System Profiler or System Information, which in 7-9 sits in the Apple Menu (Items), and in Mac OS X 10.0 to macOS Catalina, sits in Utilities and will show the Mac serial number. “About This Mac” in 10.7 “Lion” and later from the Apple menu also will show it. But, if no Mac OS is installed, there’s generally a model identifier on the bottom or a serial somewhere on the box or notebook. Two databases I’ve come to rely on are the lookup engine in EveryMac (link: Lookup Mac Specs By Serial Number, Order, Model & EMC Number, Model ID @ EveryMac.com) and the Mactracker app for both macOS and iOS.
Also, here’s a few links for major PC hardware OEMs:
For Asus, it appears their Download Center can search by model name (Download Center | Official Support | ASUS USA) but I’m not sure if it can do a direct search like the others I’ve listed.
Unfortunately, unlike with a Mac, each PC OEM is somewhat different so I can’t really list out the steps to fetch it for each. For instance, Lenovo, HP, etc. have their own hotkeys for getting to the BIOS (or EFI on newer machines) and their own support tools (mostly bundled along with Windows) for support (and fetching the serial), so short of reading the sticker or etched number on the chassis, the best universal advice on PCs I could give would be to check the manual for the key (Esc, F9, F12, Del, the Lenovo support key, etc.), and then enter UEFI or the BIOS and read it there – as it’s usually listed under the Main tab, and of course works regardless of whether a BSD, Gnu/Linux, Haiku, ReactOS, etc. is installed.
As for hardware lists of Haiku compatible machines, please check out the BeSly Hardware List and the (unofficial) Haiku Computer List page comprised of contributions from Haiku users around the world for a list of hardware, as well as the HardwareInfo page at dev.haiku-os.org.
(this is NOT my network) and I do Cancel.