You are not logged in.
Pages: 1
Hello!
I have been trying (for now a long time) to set up a functional Arch Linux install on my Acer Switch One 10, with varied levels of success. This particular post is for getting the WiFi working. The card is not recognized, and I have been unable to get it to work, relying on an Android to tether via USB. The Arch Wiki mentions installing the corresponding drivers from the AUR, but both of the drivers fail to even build at all. I tried using the Testing Kernel, but no luck either. I'm currently running the 4.14.28-1-lts kernel. I have also tried installing a number of drivers from github, but they usually fail to build or do nothing at all (my current install is fresh, I have only tried to install the AUR drivers).
I'll be grateful for any help.
Offline
Welcome to the forums vijuarez
I'm afraid 'failed to build' isn't an error message and contains no useful information at all for us to help you.
Please read https://bbs.archlinux.org/viewtopic.php?id=57855 and try again.
Offline
Hello Slithery, thanks for answering and sorry for my late reply! (busy week)
When I posted I had lost all hope of getting the drivers to work, so I forgot to specify how the builds failed. I was expecting a different solution, sorry about that!!
1) AUR Driver
2) AUR Driver DKMS edition
This one actually builds and installs, but fails when building from DKMS:
[vijuarez@luna ~]$ sudo dkms autoinstall
Kernel preparation unnecessary for this kernel. Skipping...
Building module: cleaning build area.... CONFIG_RTL8723BS=m make -C /usr/lib/modules/4.14.28-1-lts/build M=/var/lib/dkms/8723bs/9ea0240/build modules............................................(bad exit status: 2) Error! Bad return status for module build on kernel: 4.14.28-1-lts (x86_64) Consult /var/lib/dkms/8723bs/9ea0240/build/make.log for more information.
When using make and sudo make install, they produce no output. I can now use modprobe to load the r8723 module, but there seems to be no change. iw dev reports nothing and it doesn't show up in KDE Information Center.
This is marked as obsolete as the driver was merged into linux, I tried to install it anyways. It failed. As I mentioned in the first post, I have used the regular linux kernel, the testing one and currently LTS without change.
Thanks!
Offline
As the kernel contains the r8723bs module what does dmesg show? What is the VID:PID of the device from lspci / lsusb?
Offline
Hello loqs and thanks for answering!
The device doesn't seem to be recognized at all... I'm certain it's there, because I used it on Windows, but...
[vijuarez@luna ~]$ lspci
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 22)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers (rev 22)
00:03.0 Multimedia controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit (rev 22)
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 22)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 22)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 22)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 22)
[vijuarez@luna ~]$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:3016 Elan Microelectronics Corp.
Bus 001 Device 005: ID 22b8:2e24 Motorola PCS
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Thanks you!
Offline
Does rfkill list any devices?
Offline
Does rfkill list any devices?
Nope, no output at all.
Offline
What is the output of lsmod. Does adding the boot option pci=nocrs have any effect?
Offline
Adding the pci=nocrs boot option seems to have no effect, at least no changes in lsusb/lspci output.
Offline
Pages: 1