Wi-Fi & Ethernet Testers Wanted


#79

hmm… I supose is the same valid for BCM 4311?

Tried one of the latest nightlies over the weekend and can’t get WiFi to work on my old faithfull netbook.


#80

No, because B43 depends on restricted firmware that means it needs too much work to implement it and that doesn’t imply your wi-fi will work. Perhaps you should try some gnu/linux where that driver is supported on the restricted repos.


#81

~> listimage | grep dev/net
1330 0xffffffff8147a000 0xffffffff814fd000 0 0 /boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965
1555 0xffffffff81f03000 0xffffffff81f6b000 0 0 /boot/system/add-ons/kernel/drivers/dev/net/ipro1000
TEAM 879 (/bin/grep --color=auto dev/net):
~> uname -v
hrev52139 Jul 29 2018 21:03:40

I’m adding my info even though Waddlesplash has marked the iprowifi4965 driver as “OK” because my computer will either connect to my WPA2 access point the first time or try to connect and fail four or five times before finally connecting.

I am using a Thinkpad X230 if that helps.

What could be causing this?


#82

Failed auto-join is a known issue. As for the repeated failures, that’s probably DHCP, also a known issue. So the driver is probably working fine, at least. :slight_smile:


#83

Thanks! Just wanted to let the devs know.

Is there a way to get debug messages about the DHCP lease?


#84

Open a terminal window and type this in:
tail -F /var/log/syslog

That will show you DHCP activity, and everything else logged by the system.


#85

realtekwifi not stable, I had it booting and showing up, but last runs (hrev52245) sends me to KDL:


#86

I just remembered I have a netbook with a defective LCD output that still has a working HDMI output and it’s identical to a model I still use. Could you use that if I sent it to you?


#87

Unfortunately I probably won’t have any time to look at it :confused:

Actually I think @mmu_man made some potentially relevant fixes lately, but I dunno if it was enough to get those devices to work. (I think he has a similar netbook.)


#88

Mine are Dell Inspiron Mini 10 - they were quite popular back in their day, although they’re 32-bit only with 1GB RAM soldered on the same card the CPU is soldered on, which is connected in a slot on the motherboard. So the upgrade to 2GB RAM was more expensive than worth the trouble, and now they’re rare. But its size and the fact that it’s still good for basic communication makes it quite comfortable and useful compared to any phone, as long as you know what software to put on it. :slight_smile:


#89

HP Pavilion G6 running R1/Beta1 x86_64, latest system update.

Ethernet:
device Network controller (Ethernet controller) [2|0|0]
device 8136: RTL8101/2/6E PCI Express Fast Ethernet controller
Works great so far.

Wireless:
device 5390: RT5390 Wireless 802.11n 1T/1R PCIe

Wireless device ralinkwifi shows up in Networking preferences. Can’t connect, no wireless networks found. My other laptops, other wireless devices connect fine w/R1/Beta1. FreeBSD shows driver working since 2013. Wifi on this laptop is working in OpenBSD, sorry, I don’t run FreeBSD at this time, working on it soon.


Computers compatible with Haiku (v2)
#90

Please post a syslog somewhere so that I can take a look.


#91

Would posting the file on Trac be preferable? var/log/syslog, correct?

update: posted to trac with syslog attachment


#92

Permission to add this into the Hardware List for Haiku?


#93

Permission granted.:stuck_out_tongue_closed_eyes:


#94

Cool; I’ll add it in sometime after Thursday then. :slight_smile:


#95

Hi,
Wireless isn’t working.

uname -a
Haiku shredder 1 hrev52295+117 Nov 20 2018 15:41 x86_64 x86_64 Haiku

listimage | grep dev/net
1121 0xffffffff9a432000 0xffffffff9a4b2000 0 0 /boot/system/add-ons/kernel/drivers/dev/net/iprowifi4965
1172 0xffffffff8051b000 0xffffffff80547000 0 0 /boot/system/add-ons/kernel/drivers/dev/net/broadcom570x
TEAM 1033 (/bin/grep --color=auto dev/net):

listdev | grep Wireless.
device 0895: Centrino Wireless-N 105


#96

You should open a ticket for that describing exactly happens when you try to connect and the relevant syslog passages.
As the above shows, the driver knows your chipset and is loaded.


#97

If you see the APs but cant connect or connection drops you could try the -ht flag.

https://www.haiku-os.org/docs/userguide/en/workshop-wlan.html#tips


#98

ralinkwifi work very fine.

Welcome to the Haiku shell.

~> listimage |grep dev/net
2040 0xffffffffa6929000 0xffffffffa69ae000 0 0 /boot/system/add-ons/kernel/drivers/dev/net/ralinkwifi
2138 0xffffffffa9f9e000 0xffffffffa9fc3000 0 0 /boot/system/add-ons/kernel/drivers/dev/net/rtl81xx
~> uname -a
Haiku shredder 1 hrev52295+117 Nov 20 2018 15:41 x86_64 x86_64 Haiku
~>