Acer Chromebook R13 Network Problem

This is for ARMv8 based devices

Acer Chromebook R13 Network Problem

Postby 59zxrop » Tue Jan 31, 2017 11:20 am

I got an Acer Chromebook R13 and installed arch as described here:
https://archlinuxarm.org/platforms/armv ... mebook-r13

Dual boot and the basic system is working. I had some problem with wifi-menu so I set up my connection as follows:
Code: Select all
ip link set mlan0 up
wpa_supplicant -D nl80211,wext -i wlan0 -c <(wpa_passphrase "your_SSID" "your_key")
dhcpcd mlan0


This worked basicly an an I got an IP and can ping my router. And here comes my problem.
No matter what other network request I run (with DNS) I get following error (journalctl dump).
I also tried different setups and alternative installation paths, but I didnt get any furhter.

Code: Select all
Jan 31 10:10:56 alarm systemd[1]: Starting Network Name Resolution...
Jan 31 10:10:56 alarm systemd-resolved[5724]: Positive Trust Anchors:
Jan 31 10:10:56 alarm systemd-resolved[5724]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Jan 31 10:10:56 alarm systemd-resolved[5724]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Jan 31 10:10:56 alarm systemd-resolved[5724]: Using system hostname 'alarm'.
Jan 31 10:10:56 alarm systemd[1]: Started Network Name Resolution.
Jan 31 10:11:06 alarm systemd-resolved[5724]: Switching to fallback DNS server 8.8.8.8.
Jan 31 10:11:07 alarm systemd-resolved[5724]: Using degraded feature set (UDP) for DNS server 8.8.8.8.

Jan 31 10:11:07 alarm kernel: systemd-resolve[5724]: unhandled level 1 translation fault (11) at 0x00000004, esr 0x92000005
Jan 31 10:11:07 alarm kernel: pgd = ffffffc0ba2a7000
Jan 31 10:11:07 alarm kernel: [00000004] *pgd=0000000000000000, *pud=0000000000000000
Jan 31 10:11:07 alarm kernel:
Jan 31 10:11:07 alarm kernel: CPU: 3 PID: 5724 Comm: systemd-resolve Tainted: G        W      3.18.0-4-ARCH #1
Jan 31 10:11:07 alarm kernel: Hardware name: Mediatek Elm rev3 board (DT)
Jan 31 10:11:07 alarm kernel: task: ffffffc0b9199900 ti: ffffffc0b9c88000 task.ti: ffffffc0b9c88000
Jan 31 10:11:07 alarm kernel: PC is at 0x7fb0b6de2c
Jan 31 10:11:07 alarm kernel: LR is at 0x7fb0b6de20
Jan 31 10:11:07 alarm kernel: pc : [<0000007fb0b6de2c>] lr : [<0000007fb0b6de20>] pstate: 60000000
Jan 31 10:11:07 alarm kernel: sp : 0000007ff49aa2c0
Jan 31 10:11:07 alarm kernel: x29: 0000007ff49aa2c0 x28: 0000000000000000
Jan 31 10:11:07 alarm kernel: x27: 0000000000000000 x26: 0000000000000000
Jan 31 10:11:07 alarm kernel: x25: 0000000000000000 x24: 0000000000000000
Jan 31 10:11:07 alarm kernel: x23: 0000000000000000 x22: 0000000000000005
Jan 31 10:11:07 alarm kernel: x21: 0000007fb0ca16d0 x20: 0000000000000000
Jan 31 10:11:07 alarm kernel: x19: 0000007fb0ca16d0 x18: 0000000000000000
Jan 31 10:11:07 alarm kernel: x17: 0000007fb0990368 x16: 0000007fb0b1bd00
Jan 31 10:11:07 alarm kernel: x15: 003b9aca00000000 x14: 0016d1c865000000
Jan 31 10:11:07 alarm kernel: x13: ffffffffa76fa3ab x12: 0000000000000018
Jan 31 10:11:07 alarm kernel: x11: 0000000021f41441 x10: 0000000000000666
Jan 31 10:11:07 alarm kernel: x9 : 0000000000050016 x8 : 00000000000000d4
Jan 31 10:11:07 alarm kernel: x7 : 0000000000001010 x6 : 0000000000000f60
Jan 31 10:11:07 alarm kernel: x5 : 0000000061aa96b8 x4 : 000000000000000c
Jan 31 10:11:07 alarm kernel: x3 : 0000000000000000 x2 : 0000000000008105
Jan 31 10:11:07 alarm kernel: x1 : 0000007fb0c9f530 x0 : 0000000000000000
Jan 31 10:11:07 alarm kernel:
Jan 31 10:11:07 alarm systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV
Jan 31 10:11:07 alarm systemd[1]: systemd-resolved.service: Unit entered failed state.
Jan 31 10:11:07 alarm systemd[1]: systemd-resolved.service: Failed with result 'signal'.


Since I m just a user in this area can someone help me solving this problem?
59zxrop
 
Posts: 1
Joined: Tue Jan 31, 2017 10:47 am

Return to ARMv8 Devices

Who is online

Users browsing this forum: Google [Bot] and 2 guests