Opened 6 weeks ago

Last modified 6 weeks ago

#19110 assigned bug

RTL8192CU based TP-Link WiFi Dongle slow/unstable connection.

Reported by: andi4567 Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/realtekwifi Version: R1/beta5
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Hi,

as the title already suggests, the driver for the RTL8192CU chipset loads, it connects to the router (with wpa2), but is very slow. A ping response from the router takes more than 20ms on average and should be around 2ms, I suppose.

That's why, HaikuDepot does not receive any packages from the internet. (It would be nice to be informed by the package manager about this btw..)

As far as I can tell the signal strength seems to be very low although it should be pretty high, indeed, because it is not too far away from the router.

After a certain period of time the connection is lost and the device is either reconnected or stays offline. I could not recognize a pattern.

I did not manage to enter the kernel debug land, as I don't have a print key on my laptop's keyboard. Anyhow, I'll provide the other information required according to https://www.haiku-os.org/docs/welcome/en/bugreports.html

Kind regards

Attachments (5)

listdev-output.txt (5.3 KB ) - added by andi4567 6 weeks ago.
listimage-output.txt (57.7 KB ) - added by andi4567 6 weeks ago.
listusb-v-output.txt (34.4 KB ) - added by andi4567 6 weeks ago.
syslog.txt (45.6 KB ) - added by andi4567 6 weeks ago.
syslog.zip (22.1 KB ) - added by andi4567 6 weeks ago.
This is the complete syslog of the last boot with the corresponding wifi dongle.

Download all attachments as: .zip

Change History (11)

by andi4567, 6 weeks ago

Attachment: listdev-output.txt added

by andi4567, 6 weeks ago

Attachment: listimage-output.txt added

by andi4567, 6 weeks ago

Attachment: listusb-v-output.txt added

by andi4567, 6 weeks ago

Attachment: syslog.txt added

comment:1 by waddlesplash, 6 weeks ago

Component: Drivers/USBDrivers/Network/realtekwifi
Keywords: Wifi wireless RTL8192CU removed
Owner: changed from mmlr to nobody
Platform: x86-64All
Status: newassigned

comment:2 by waddlesplash, 6 weeks ago

Your syslog is incomplete/cut off, but the disconnects are logged at least:

KERN: [net/realtekwifi/0] [88:03:55:95:cc:8b] station deauth via MLME (reason: 3 (sending STA is leaving/has left IBSS or ESS))

I don't see any firmware errors or other driver problems, just information from the WiFi stack like this. So I'm not sure what there is to do here.

Does this device work better in Linux?

comment:3 by waddlesplash, 6 weeks ago

Ah, there's also this:

KERN: [net/realtekwifi/0] beacon miss, mode STA state RUN

I'm not sure what's going on with all the DHCP requests at the end.

comment:4 by andi4567, 6 weeks ago

Oh, I'm not familiar with the handling of then haiku-terminal and just used my Linux routines, I'll add the complete syslog tomorrow.

Under Linux the device works quite well with the rtl8xxxu module. The older rtl8192cu module has also been quite unstable, as far as I do remember.

The dhcp requests are probably due to the fact that the connection is being reestablished quite often.

by andi4567, 6 weeks ago

Attachment: syslog.zip added

This is the complete syslog of the last boot with the corresponding wifi dongle.

comment:5 by waddlesplash, 6 weeks ago

The full syslog just has more of the same errors I noted above, it appears.

I don't think this driver has changed much in FreeBSD lately, so the problem is likely also one in upstream (unless somehow this is a Haiku compatibility issue.)

in reply to:  5 comment:6 by andi4567, 6 weeks ago

Replying to waddlesplash:

The full syslog just has more of the same errors I noted above, it appears.

I don't think this driver has changed much in FreeBSD lately, so the problem is likely also one in upstream (unless somehow this is a Haiku compatibility issue.)

Ok, I'll check, if the dongle works with freebsd. After some researching on the web it seems that one needs to be content with a speed around 200kb/s. Not very much, indeed.

Note: See TracTickets for help on using tickets.