Trouble with android tethering [Solved]

Vofan · 2019-01-25 03:14:10

After exhausting all the other options (mostly due to fiddliness of having to copy over every ****ing dependency that I'm too dumb to get over there with pacman) I've decided to install the proprietary drivers for my ancient PC's wifi using tethering (and now the grub, seeing as it seems that I- hmm. I went to check which files it said it was missing and now I get

Installing for i386-pc platform.
WARNING: failed to connect to lvmetad. Falling back to device scanning.
WARNING: failed to connect to lvmetad. Falling back to device scanning.
WARNING: failed to connect to lvmetad. Falling back to device scanning.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition: embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for RAID and LVM install.

- it is, to my knowledge, a BIOS/MBR and not a BIOS/GPT setup. But I could naturally be wrong, in which case I'll have to go back).

When I type

dhcpcd enp0s26f7u3u1

I get

sending commands to master dhcpcd process

. I have set the ip link to up. I'm unsure how to proceed, or what information would be useful.

If your advice is to just bypass this issue by somehow illuminating me as to how to transfer the necessary driver and its dependencies easily, (which I have been trying for over a day to do, every method just throws wall after wall at me), the driver is https://aur.archlinux.org/packages/rtl8812au-dkms-git/. Or, you know, it may even be the *21au* driver, kinda forgot in the frustration.

Thanks a whole lot.

Last edited by Vofan (2019-01-26 10:44:12)

Vofan · 2019-01-25 03:15:59

As an addendum, yes, I have read, reread, and reread the offline installation of packages page - it's just that a lot of the dependencies I lack are assumed to be there (but aren't) or aren't stored in the mentioned directory. I guess I'll do some googling to find what other directories might be storing them.

ewaller · 2019-01-25 03:22:57

What is the output of ip addr at the end of post #1?

Vofan · 2019-01-25 03:37:38

ewaller wrote:

[...]ip addr[...]

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/0 scope host lo
    valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST> mtn 1500 qdisc fq_codel state DOWN group default qlen 1000
  link/ether 00:30:1b:bc:3b:20 brd ff:ff:ff:ff:ff:ff
5: enp0s26f7u3u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtn 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
  link/ether ee:ac:32:cc:1d:fa brd ff:ff:ff:ff:ff:ff
  inet6 fe00::ecac:32ff:fecc:1dfa/64 scope link
   valid_lft forever preferred_lft forever

ewaller · 2019-01-25 03:46:01

It is not seeing a DHCP server, apparently. Does this phone work with other computers when tethered? And that phone has a connection to the Internet through one of its radios?

Vofan · 2019-01-25 23:31:32

Yes, it works fine on my more contemporary laptop.

There, ip link:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether fc:45:96:56:3e:88 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether 58:00:e3:bb:f0:a3 brd ff:ff:ff:ff:ff:ff
4: enp0s16u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether aa:0e:b4:37:17:3d brd ff:ff:ff:ff:ff:ff

ip addr:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether fc:45:96:56:3e:88 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 58:00:e3:bb:f0:a3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.90/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 86096sec preferred_lft 86096sec
4: enp0s16u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether aa:0e:b4:37:17:3d brd ff:ff:ff:ff:ff:ff
    inet 192.168.42.216/24 brd 192.168.42.255 scope global dynamic noprefixroute enp0s16u3
       valid_lft 3435sec preferred_lft 3435sec
    inet6 fe80::44d5:c236:369:a08/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

However, I did notice that:

$ dhcpcd enp0s16u3
main: pidfile_lock: Permission denied

But I am guessing this is normal, as it works..?

ewaller · 2019-01-26 03:13:20

No, I would run it as sudo dhcpcd enp0s16u3

Vofan · 2019-01-26 10:43:52

ewaller wrote:

No, I would run it as sudo dhcpcd enp0s16u3

Well, I was running it as root on the other machine.

Anyway, it was just a dumb mistake: I forgot to exit chroot before running dhcpcd. Thanks though.

Arch Linux

#1 2019-01-25 03:14:10

Trouble with android tethering [Solved]

#2 2019-01-25 03:15:59

Re: Trouble with android tethering [Solved]

#3 2019-01-25 03:22:57

Re: Trouble with android tethering [Solved]

#4 2019-01-25 03:37:38

Re: Trouble with android tethering [Solved]

#5 2019-01-25 03:46:01

Re: Trouble with android tethering [Solved]

#6 2019-01-25 23:31:32

Re: Trouble with android tethering [Solved]

#7 2019-01-26 03:13:20

Re: Trouble with android tethering [Solved]

#8 2019-01-26 10:43:52

Re: Trouble with android tethering [Solved]

Board footer