[ARM Testing Update] 2021-11-04 - Firefox, Thunderbird, Foot and kernels

nl.smart · 4 November 2021 19:41

Thanks for your reply

The boot ini file is looking so, I open the file with kate and konsole

Strange, how is it possible ? something wrong with the font ?

The c4 boot ini file is looking so, is looking good
Odroid c4 not up to date for the moment.

ODROIDC4-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyAML0,115200n8"   # on both

# Boot Args
setenv bootargs "root=LABEL=ROOT_MNJRO rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 clk_ignore_unused bootsplash.bootfile=bootsplash-themes/manjaro/bootsplash"

# Set load addresses
setenv dtb_loadaddr "0x20000000"
setenv loadaddr "0x1080000"
setenv initrd_loadaddr "0x3080000"

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-sm1-odroid-c4.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.uimg
#fdt addr ${dtb_loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

c4 detail :-)

[nlc4@c4 ~]$ stat / | awk '/Birth: /{print $2}'
2020-05-14
[nlc4@c4 ~]$

to reproduce the n2 issue, build a stable image, boot on it.
after the boot with the stable branch image switch to the testing branch, up date the device with the testing update and see what happen.

Strit · 4 November 2021 20:11

Yeah. The Odroid N2 boot.ini seems to have been corrupted.

Please use this as your boot.ini on the Odroid n2:

ODROIDN2-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyAML0,115200n8"   # on both

# Boot Args
setenv bootargs "root=LABEL=ROOT_MNJRO rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 clk_ignore_unused quiet splash plymouth.ignore-serial-consoles"

# Set load addresses
setenv dtb_loadaddr "0x20000000"
setenv loadaddr "0x1080000"
setenv initrd_loadaddr "0x4080000"

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-g12b-odroid-n2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.uimg
#fdt addr ${dtb_loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

Please replace LABEL=ROOT_MNJRO with PARTUUID=$PARTUUID where $PARTUUID is the PARTUUID of your / partition as shown by lsblk -o NAME,PARTUUID.

damon · 5 November 2021 01:48

Hello, this update caused two very noticeable changes on my PBP with a GNOME image: Night color now works and Firefox does not start. Or, the window manager acts like it starts, but the window itself doesn’t appear. When started from a terminal it says the message below, but keeps running and doesn’t error out.

(firefox:4360): Gtk-WARNING **: 21:38:05.844: Theme parsing error: gtk.css:1:45: Expected a valid selector
ATTENTION: default value of option mesa_glthread overridden by environment.

appelgriebsch · 5 November 2021 06:38

Have you tried resetting your Firefox profile?

damon · 5 November 2021 11:17

I moved the .mozilla folder to .mozilla.old and there was no apparent difference. Would that have done it or is there another way to reset the profile without being able to interact with the firefox UI?

appelgriebsch · 5 November 2021 13:01

Japp, that should be it…. Just upgraded my sway installation and have not found any issues… only difference I see is: in sway I explicitly set the environment variable to force Firefox to run with Wayland (which is also the default for GNOME)…

Maybe try those two lines (23-24) overlays/sway/etc/environment · master · manjaro-arm / applications / arm-profiles · GitLab

damon · 5 November 2021 15:06

Thanks! That was it. Which is surprising because I’ve been using Wayland and Firefox for several months and thought I had forced Firefox to use Wayland already, but maybe something had changed since then.

I tested launching from the command line and it worked, so I assume it’ll keep working now that I copied those lines to /etc/environment

I saw this in the Arch Wiki, is it still relevant and helpful in our situation?

On native Wayland Firefox rendering performance can be significantly improved by setting gfx.webrender.compositor.force-enabled to true in about:config . As of Firefox 89, this feature is experimental and Firefox Nightly is recommended for testing.

appelgriebsch · 5 November 2021 15:33

Not sure about the webrender thing. I found Firefox more stable on ARM platforms when disabling it… YMMV though

nl.smart · 5 November 2021 18:04

thanks for your reply.

I copy past your boot.ini
my emmc module lsblk is looking so, but it doesn’t start, I deed something wrong, but where ?

sdc         
├─sdc1      f42d575e-01 #BOOT
└─sdc2      f42d575e-02 #ROOT

ODROIDN2-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyAML0,115200n8"   # on both

# Boot Args
setenv bootargs "PARTUUID=f42d575e-01 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 clk_ignore_unused quiet splash plymouth.ignore-serial-consoles"

# Set load addresses
setenv dtb_loadaddr "0x20000000"
setenv loadaddr "0x1080000"
setenv initrd_loadaddr "0x4080000"

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-g12b-odroid-n2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.uimg
#fdt addr ${dtb_loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

post scriptum : the odroid c4 is up to date, no issue.

Strit · 5 November 2021 19:07

This here

PARTUUID=f42d575e-01

needs to be changed to:

root=PARTUUID=f42d575e-01

nl.smart · 6 November 2021 06:55

I tried, it doesn’t work.

Strit · 6 November 2021 07:21

Ah, it should be

root=PARTUUID=f42d575e-02

Since we are defining the root partition.

nl.smart · 6 November 2021 07:36

the blue led stay fix

I build a KDE image, the only difference the only boot ini file is the label

root=PARTUUID=2449c037-02 # kde image built yesterday

how to find the original PARTUUID number ?

siemsenit · 6 November 2021 07:45

X11 Apps are invisible on a Pinebook Pro running GNOME. X clients do start an run fine, but there is no visible window on screen.

Wayland Apps work without issue.

Strit · 6 November 2021 07:52

That is the PARTUUID of the new image.

nl.smart · 6 November 2021 07:56

Ok, I find this, I keep the build report for every image

  -> Flashing bootloader...
  -> Writing PARTUUIDs...
Boot PARTUUID is f42d575e-01...
Root PARTUUID is f42d575e-02...
  -> Cleaning up image...
  -> Compressing Manjaro-ARM-lxqt-on2-2021.10.28.img...
Manjaro-ARM-lxqt-on2-2021.10.28.img (1/1)
  100 %   1 201,1 MiB / 5 840,0 MiB = 0,206    15 MiB/s       6:37             
  -> Removing rootfs_aarch64
==> Time : 25.22 minutes...
[nls@nls-pc ~]$

appelgriebsch · 6 November 2021 09:57

X11 apps on Wayland need the xorg-xwayland server as a kind of bridge between both environments.

Is the xwayland server running?

appelgriebsch · 6 November 2021 10:50

Tested it on my RPI4 GNOME setup by upgrading to latest testing, reboot and launch Gimp…

nl.smart · 6 November 2021 17:06

I rebuilt a LXQt KDE image for the n2, it works.

the boot ini file is looking so

ODROIDN2-UBOOT-CONFIG

# Default Console Device Setting
setenv condev "console=ttyAML0,115200n8"   # on both

# Boot Args
setenv bootargs "root=PARTUUID=ebd5d5f5-02 rootwait rw ${condev} ${amlogic} no_console_suspend fsck.repair=yes net.ifnames=0 clk_ignore_unused quiet splash plymouth.ignore-serial-consoles"

# Set load addresses
setenv dtb_loadaddr "0x20000000"
setenv loadaddr "0x1080000"
setenv initrd_loadaddr "0x4080000"

# Load kernel, dtb and initrd
load mmc ${devno}:1 ${loadaddr} /Image
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-g12b-odroid-n2.dtb
load mmc ${devno}:1 ${initrd_loadaddr} /initramfs-linux.uimg
#fdt addr ${dtb_loadaddr}

# boot
booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

nl.smart · 6 November 2021 17:20

@Strit

the swap by default on arm devices, is it a file or a partition ?
on the x86 devices I prefer the partition, I’m maybe old school.