Installing -current on a Chromebook

linus72 · 02-21-2019, 06:10 PM

Lysander666 whats the update bro?

Lysander666 · 02-22-2019, 03:26 AM

Quote:

Originally Posted by linus72

Lysander666 whats the update bro?

It still doesn't worth with the audio, unfortunately. However, rokytnji's suggestion of using a three-finger tap on the touchpad did work for a right-click menu so that's good.

I tried MX as well last night, and it didn't work with the audio either. So Ubuntu is the only distro to make it work so far. I am wondering what they have that Slack and others don't which makes the audio work [it can't be the kernel since Ubuntu 18.04 is using 4.15 and -current 4.19]. I wonder if it's anything to do with GNOME, though I can't think why that would make any difference. I'm getting interested in this chtmax98090 and trying to work out what's happening with it - if Ubuntu can do it then surely it is possible. Here's the original Arch thread on the issue to comb over:

https://bugs.archlinux.org/task/48936

EDIT: This is interesting, did it make it natively into 4.20?

Apparently it was in the queue for 4.19 as well.

Quote:

diff --git a/queue-4.19/series b/queue-4.19/series
index 48f5655a0..e9c6f7fff 100644
--- a/queue-4.19/series
+++ b/queue-4.19/series
@@ -118,3 +118,6 @@ ext2-initialize-opts.s_mount_opt-as-zero-before-using-it.patch
ext2-fix-potential-use-after-free.patch
asoc-intel-cht_bsw_max98090_ti-add-quirk-for-boards-using-pmc_plt_clk_0.patch
asoc-pcm186x-fix-device-reset-registers-trigger-value.patch
+arm-dts-rockchip-remove-0-from-the-veyron-memory-node.patch
+dmaengine-at_hdmac-fix-memory-leak-in-at_dma_xlate.patch
+dmaengine-at_hdmac-fix-module-unloading.patch

More interesting stuff here:

https://bugzilla.kernel.org/show_bug.cgi?id=115531

EDIT: Just found this - is it just matter of installing this [I'm not actually sure how to]?

https://github.com/torvalds/linux/bl...ecs/max98090.c

EDIT2: I may be getting somewhere, apparently someone has got it to work under -current

Quote:

Logan Rathbone 2019-01-27 19:57:00 UTC
In case anyone is searching the web to seek solutions, I'll put on the record that 4.20.4, with the patch as generated above, along with the UCM files that have been posted on git at https://github.com/heikomat/linux/tr...ual/chtcx2072x - sound is now functioning on my Asus Transformer Mini T103HA.

Shouldn't really matter as I am using an updated but otherwise vanilla kernel from ftp.kernel.org, but again, for the record, this is under Slackware Current (live ISO from alienBob 1.3.0.2, 20190117).

Thanks all. I hope these efforts can be merged into mainline Linux and ALSA, but I'm sure there are reasons above my head as to why they have not.

This patch is the one referred to as far as I can see. I just have to work how to install these things.

https://bugzilla.kernel.org/attachment.cgi?id=280807

Lysander666 · 02-22-2019, 05:39 AM

I think I'm just going to have to try for a full install on -current though 14.2. Since the screen keeps blacking out during the 14.2 install due to the lack of correct drivers, I just have to keep trying and hope it works and then update to -current.

Unless it's possible to update to the most recent -current through Eric's live iso?

Can anyone confirm which kernel Slackware live is on? My last foray into this showed kernel 4.14.68 in January. The audio needs the latest 4.19.xx to work natively in view of the above.

Another option is disabling all the other codecs:

Quote:

The simple fix is easy: disable all other codecs and the
BYT_MAX98090 option will be enabled. BYT_MAX98090 relies on the 'old'
non-dpcm driver which is used only for Chromebooks with Baytrail, which
never enable any other codecs, so there was never any issue before.

kgha · 02-22-2019, 09:18 AM

Since Eric's slackware iso bears the date 2019-01-17 I would guess that it has the 4.19.15 kernel.
EDIT: If not, if you maka a bootable live usb stick from the iso, you may upgrade the kernel on the stick and then make the install to the chromebook.

Lysander666 · 02-22-2019, 10:13 AM

Quote:

Originally Posted by kgha

Since Eric's slackware iso bears the date 2019-01-17 I would guess that it has the 4.19.15 kernel.
EDIT: If not, if you maka a bootable live usb stick from the iso, you may upgrade the kernel on the stick and then make the install to the chromebook.

That is an amazing idea. So presumably just do a slackpkg update having commented out the -current mirror and then setup2hd?

It seems the kernel upgrade process is different than in 14.2. Or should I run upgradepkg on this?

kgha · 02-23-2019, 01:41 AM

Eric's LiveSlaks have a special command for upgrading, check the section "Updating the kernel (and more) on a USB stick" in Eric's documentation, https://docs.slackware.com/slackware:liveslak

Since the worst thing that could happen is that you'll have to re-create your live usb stick, I would say that you don't have to worry about theoretical risks when upgrading kernel, glibc* and so on.

When you've upgraded, rebooted, and found everything working you can install with the setup2hd command.

LuckyCyborg · 02-23-2019, 07:02 AM

I suggest to OP to install in his Chromebook something like OpenSuse, because it gives you KDE Plasma 5 on 5GB occupied space. Or Ubuntu. It gives you Gnome3 on a similar occupied space.

I would like to note that I struggled for several years to put the Whaleware on a 8GB device. It is not worth the effort, in my opinion.

Lysander666 · 02-23-2019, 07:06 AM

Well, I'm going to have to go back a step first.

I installed -current though the setup2hd script. It took about 1.5 hours to extract and install everything. On reboot, I had the same issue as before, I had a grub rescue prompt and "normal.mod not found".

The following steps worked to get me to a grub prompt:

Code:

set prefix=(hd0,msdos1)/usr/lib64/grub
insmod normal
normal

However, after entering "boot" I was told "you need to load the kernel first".

Code:

insmod linux
linux /vmlinuz root=/dev/mmcblk0p1

worked, but then I need to enter

Code:

initrd /initrd.img

and I cannot find where initrd.img is on the system.

Also I don't know why this system is insisting on using grub rather than LILO.

linus72 · 02-23-2019, 07:35 AM

should be /boot/vmlinuz and /boot/initrd.img thats where they are on my dvd...

Lysander666 · 02-23-2019, 07:37 AM

Quote:

Originally Posted by linus72

should be /boot/vmlinuz and /boot/initrd.img thats where they are on my dvd...

Sorry, I meant /boot. But there is no /boot/initrd.img, only /boot/initrd.gz - then if I try that it says it is not a valid file name.

linus72 · 02-23-2019, 07:38 AM

thats weird, can you extract it from mounted dvd to your usb? I use isomaster or cp command

Lysander666 · 02-23-2019, 11:19 AM

Quote:

Originally Posted by linus72

thats weird, can you extract it from mounted dvd to your usb? I use isomaster or cp command

Good suggestion - thanks for that, I tried it and it worked, kind of. When I say 'kind of' I mean I booted into the installation and it kept booting into the live device. 14.2 had this problem too - actually it was worse because I couldn't get past grub rescue with 14.2. I have done loads of Slackware installs over time and the only computer I had a consistent issue with is the Chromebook.

I keep taking one step forward and two back. Still nothing with the audio - I even did a test install with MX Linux and the sound didn't work either.

So I'm going to put this on hold for now and take the advice of LuckyCyborg. This is taking a lot of time and Ubuntu does work more or less perfectly on the machine, so for now, I'm going to stick with it. I may try again soon enough.

rokytnji · 02-23-2019, 01:29 PM

Sounds pragmatic to me. Sometimes I bite the bullet and move on. Like when I fought a broken write protect circuit < hardware > and decided chrooting ubuntu was a better compromise over maybe bricking the unit even further. Spent tons of time before giving in. Even bought chemical solder and such.

I can be pretty stubborn.

linus72 · 02-23-2019, 04:05 PM

Yeah lysander666 Ive been in that situation with a few older laptops and pcs, you keep trying but no dice
At least Ubuntu works- I'm like you a Slacker so aint into Dubuntu lol
Since arch had a workaround have you tried a arch live usb like arcolinux, or archbang?
I have arcolinux on my lappy its a pretty cool distro

kgha · 02-24-2019, 05:11 AM

Makes sense sticking to ubuntu for the time being and return to fiddling with slackware on a rainy day. Experimenting with a live usb stick might be the best way forward.

I find it odd, though, that you end up with grub. I installed 64 bit -current with Eric's MATE iso on my ordinary laptop and 32 bit -current with his slackware iso on an old eee900. In both cases I got lilo.

About the storage space: On my eee900, I use 10.3 GB on the / partition, and that's with openoffice, palemoon, gimp, vlc, audacity, calibre, qbittorrent (which means I aso have Eric's Qt5). I've uninstalled firefox, thunderbird, pidgin, texlive and maybe some other package that I don't use.

Not much space left for /home, but with an SD card in the slot that's not a big issue.