search

quarkscript / linux-armv7-xe303c12-only

Linux kernel for old google-snow chromebook
GNU General Public License v2.0
18 stars 2 forks source link

Networking issue #30

Open kronn opened 2 months ago

kronn commented 2 months ago

I wanted to start easy and use the arch/console-image. It booted fine, but I could not connect to a network.

Currently, I use the arch/xfce4-image. It boot equally fine (a bit longer because the UI has to load), but it allowed to connect to a network. I did a gparted-resize of the sd-card and a pacman -Syu and rebooted. Now, I am directly connected to the same network as before, but xfce4 does not boot anymore (well... lightdm fails). The xfce4-situation is not ideal, but I can log into tty2, am connected to my network and work from there.

I am totally fine with the chromebook becoming a console-only machine, however: do you have any ideas why wifi-menu could not establish a connection in the console-image? The interface is called mlan0 in both cases.

Ideally, I could just use the console-only image and omit the whole GUI-thing. I just like being connected to a network to transfer work-status between the chromebook and other devices.

quarkscript3 commented 1 month ago

It's hard to say what caused your problems. It could be a system update or the use of a non-specialized ChromeOS disk partitioning tool. On my Chromebook with unmodified firmware (uboot), any changes to the disk made without cgpt cause subsequent boot failures. That's why this script was written. Script demonstration.

Here is a more recent version of the console variant of archlinuxarm. (login: root pass: q) The wifi-menu connects successfully for me. The DE can be installed at your choice. This is http://os.archlinuxarm.org/os/ArchLinuxARM-armv7-chromebook-latest.tar.gz with default kernel and firmware removed, updated, custom kernel and needed firmware installed. Disk image created by 'edim' script. Kernel package taken from gitlab

By the way, on the latest system with the latest mesa, I had fewer applications running due to the unsupported GPU than on earlier ones.

kronn commented 1 month ago

Thanks for getting back. I specifically do not want a graphical interface as it distracts me too much. I want a powerful typewriter with network. :-)

I'll give the updated version you mentioned a whirl. If that does not work, I'll try to use the systemd-unit that the graphical-version creates.