Opened 20 months ago

Last modified 7 months ago

#14668 new bug

Dlink DWA-525 PCI rev A2 wi-fi adapter can't find any networks

Reported by: Haiker Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Network/ralinkwifi Version: R1/Development
Keywords: driver, network, ralinkwifi, wi-fi Cc:
Blocked By: Blocking: #11548, #14721
Platform: x86

Description

After connecting Dlink DWA-525 PCI rev A2 wlan adapter to my PC and booting Haiku, the system properly detects this card via ralinkwifi driver, but in the dropdown menu from the Network Preferences's tray icon, there are no any wi-fi networks aviable. Network Preferences dialog shows the same empty list of the wi-fi networks. Also I see the empty list when trying to scan aviable networks via ifconfig using

ifconfig /dev/net/ralinkwifi/0 list

or

ifconfig /dev/net/ralinkwifi/0 scan

commands.

Although listdev detects this wlan card correctly too:

device Network controller [2|80|0]
  vendor 1814: Ralink corp.
  device 5360: RT5360 Wireless 802.11n 1T/1R

And this adapter is also supported by FreeBSD 11.1 release: https://www.freebsd.org/releases/11.1R/hardware.html#wlan what is said in the Haiku user guide: https://www.haiku-os.org/docs/userguide/en/workshop-wlan.html

I can confirm - this wi-fi card is fully functional and works & detects wi-fi networks correctly in Linux (Lubuntu 16.04.5 x32).

Motherboard of my PC is MSI MS-7267.

Tested with the latest hrev52462.

See attachments for details.

Attachments (10)

syslog (312.2 KB ) - added by Haiker 20 months ago.
previous_syslog (128.7 KB ) - added by Haiker 20 months ago.
ifconfig.txt (1.1 KB ) - added by Haiker 20 months ago.
network_preferences.png (43.7 KB ) - added by Haiker 20 months ago.
network_status.png (70.6 KB ) - added by Haiker 20 months ago.
listdev.txt (2.4 KB ) - added by Haiker 20 months ago.
screenshot1.png (108.4 KB ) - added by Haiker 18 months ago.
hrev53174.png (123.7 KB ) - added by Haiker 13 months ago.
screenshot2.png (86.7 KB ) - added by Haiker 7 months ago.
syslog.2 (95.8 KB ) - added by Haiker 7 months ago.

Download all attachments as: .zip

Change History (23)

by Haiker, 20 months ago

Attachment: syslog added

by Haiker, 20 months ago

Attachment: previous_syslog added

by Haiker, 20 months ago

Attachment: ifconfig.txt added

by Haiker, 20 months ago

Attachment: network_preferences.png added

by Haiker, 20 months ago

Attachment: network_status.png added

by Haiker, 20 months ago

Attachment: listdev.txt added

comment:1 by diver, 20 months ago

Probably a dupe of #11548.

comment:2 by waddlesplash, 20 months ago

Blocking: 11548 added

comment:3 by waddlesplash, 20 months ago

It is, but this one has more information.

comment:4 by waddlesplash, 18 months ago

Blocking: 14721 added

comment:5 by waddlesplash, 18 months ago

Please retest after hrev52744.

comment:6 by Haiker, 18 months ago

Retested with hrev52749. Nothing has changed.

by Haiker, 18 months ago

Attachment: screenshot1.png added

comment:7 by waddlesplash, 13 months ago

Please retest after hrev53174.

by Haiker, 13 months ago

Attachment: hrev53174.png added

comment:8 by Haiker, 13 months ago

In hrev53174 still the same issue. Although now I tested it on another PC with another motherboard, Asus A7V8X-X, but Wi-Fi card is the same. I think it doesn't affect the problem.

comment:9 by waddlesplash, 8 months ago

Please retest after hrev53592; there is a chance this fixes the problem.

comment:10 by Haiker, 7 months ago

Retested with hrev53644. Now my wifi card is not recognized at all, although I didn't disconnect it. It is not visible as in Network Preferences, same in ifconfig.

by Haiker, 7 months ago

Attachment: screenshot2.png added

by Haiker, 7 months ago

Attachment: syslog.2 added

comment:11 by waddlesplash, 7 months ago

KERN: usb_disk: operation 0x35 failed at the SCSI level
KERN: usb_disk: request_sense: key: 0x05; asc: 0x20; ascq: 0x00; Invalid command operation code
KERN: Name is too long (306 < 372)
KERN: error: long file name too long
KERN: dosfs_readdir: error returned by get_next_dirent (File name too long)

These are at the end of your syslog, and it appears the ralinkwifi driver is not even attempted to be loaded. Is it blacklisted, or not present somehow? Or are these errors preventing something...

comment:12 by Haiker, 7 months ago

No, I didn't blacklist or delete ralinkwifi manually. I only selected failsafe graphics driver at boot, since the system fails to initialize display with default video driver on that PC. Probably that log is not full, because I copied it from the system when it was running. Although ideally driver should initialize during the system boot, so then it should be visible in copied part of the log... Looks like some kind error(s) are indeed preventing successful ralinkwifi loading.

comment:13 by waddlesplash, 7 months ago

Well, the point is that the driver file is not even loaded at all, which is very strange.

Note: See TracTickets for help on using tickets.