You are not logged in.
Pages: 1
Hello.
I'm trying to install Arch Linux on my Surface Pro 4.
I managed to connect to my wifi via the wifi-menu.
Problem: when downloading I get a very high fluctuation in download speeds from 1000KB/s to 10KB/s.
I tried solving that by:
- Getting closer to the hotspot -> fluctuatuions persist
- Trying different faster mirrors -> no change
Then I noticed those kernel messages right after I connect: protocol 0003 buggy, dev wlp0s2.
So I wondered If the fluctuations have to do with that messages?
Last edited by beppo (2018-04-04 22:19:45)
Offline
Some actual details would help: card, driver, logs, etc...
Moving to NC.
Offline
Currently running pacstrap, was hoping the error was enough to confirm the cause of the issue.
Will add more info as soon as its finished.
Offline
Alright, in the eantime I‘ve also checked my internetspeed on my desktop in the same network via various benchmarks all of them showing normal consistent speeds.
Following the Wiki for setting up the wifi connection I get the following:
lspci -k:
Ethernet controller: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless
Subsystem: device 0003:045e
Kernel Driver in use: mwifiex_pcieip link
wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> ntu 1500 qdisc mq state UP mode DORMANT group default qlen 100 link/ether .....after
ip link wlp2s0
dmesg | grep firmware
[drm] finished loading DMC firmware i915/skl_dmc_ver1_26.bin
platform regulatory.0: Direct firmware load for regulatory.db failed with error 2dmesg | grep mwifiex_pcie
returns nothing
Offline
Why the grep for firmware rather than posting the output of dmesg?
The results from the grep are from the i915 iGPU and cfg80211 failing to load the regulatory database as firmware file which is expected as arch does not ship that file.
Does the issue persist when you perform a pacman system update?
Did you try downloading files from the same mirrors pacman uses with the same command that pacman uses?
Edit:
spelling tot not to.
Last edited by loqs (2018-04-01 21:14:34)
Offline
The system is up to date.
Is there a way to upload the dmesg log from the commandline?
I cant access my desktop atm. writing from an ipad
Edit: just checked the wiki about uploading from boot. Brb.
Last edited by beppo (2018-04-01 21:12:10)
Offline
Tried pbpst and gist to upload the dmesg log, but both failed at uploading.
Checked my connection with speedtestcli and it reported good download and upload speeds.
forking a project atm. we‘ ll see how that turns out.
Offline
What is the problem of posting the dmesg output here inside code tags?
Is the desktop also using a wifi card or is it wired?
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
The problem with uploading either with pbpst or gist is that the upload fails. And the desktop is of course also connected via wifi...
Is there another option to upload?
Offline
Offline
The solution was to install the proper marvel drivers like so:
git clone git://git.marvell.com/mwifiex-firmware.git
sudo mkdir -p /lib/firmware/mrvl/
sudo cp mwifiex-firmware/mrvl/* /lib/firmware/mrvl/ Last edited by beppo (2018-04-04 22:26:07)
Offline
Please use code tags for commands and there outputs. The directory /lib/firmware/mrvl should already have existed unless your system did not have the linux-firmware package installed.
Which firmware files did your device need to be updated? You could ask marvell to submit updated firmware to linux-firmware repo so others can benefit.
Edit:
All the files from the git://git.marvell.com/mwifiex-firmware.git/mrvl/ match the files already provided by linux-firmware which should have been present in /lib/firmware/mrvl/
Last edited by loqs (2018-04-04 01:22:04)
Offline
Oh, well thats embarasing. I'll try reproducing what I did.
Offline
Alright I might have to admit that I jumped to conclusions too early. Having good speeds for a while not checking if its fixed does not fix it. Who would have thought, shame on me.
Now here are the dmesg and jorunalctl -k -b -0 logs.
Last edited by beppo (2018-04-04 22:33:44)
Offline
Pages: 1