Call For Testers (18.07)

testing
images
manjaroarm

#41

Is there not a typo?
Should be ?

setcap cap_net_raw+ep usr/bin/ping 2>/dev/null || chmod u+s usr/bin/ping

#42

My test:

What image did you test?
Manjaro-ARM-minimal-rpi2-18.06-rc4.img
(burned with Etcher)

What device did you test on?
Raspberry Pi 3 Model B

Does it boot to a CLI login prompt?
Yes

Can you login with both root and manjaro users?
Yes

Can you install/update packages?
Yes (with some errors,keys related)

Can you run ping 8.8.8.8 from the manjaro user?
Yes (wired)

Other notes

  • Resize-sd script > OK
  • Rii wireless keyboard with usb adapter > OK
  • 7 urandom warning(s) missed due to ratelimiting (seen in second reboot)

#43

@Quemandoacromo
What was the package errors? (i’m not gonna go through multiple hoops just to see a pacman log)

Thanks for testing, all!


#44

Sorry,my error :frowning:

Pastebin > https://pastebin.com/pBLiXkQV


#45

I only see one error:

[2018-06-06 17:37] [ALPM-SCRIPTLET] dirmngr[456]: error opening '/root/.gnupg/dirmngr_ldapservers.conf': No such file or directory
[2018-06-06 17:37] [ALPM-SCRIPTLET] dirmngr[456.0]: permanently loaded certificates: 1
[2018-06-06 17:37] [ALPM-SCRIPTLET] dirmngr[456.0]:     runtime cached certificates: 0
[2018-06-06 17:37] [ALPM-SCRIPTLET] dirmngr[456.0]:            trusted certificates: 1 (0,0,0,1)
[2018-06-06 17:37] [ALPM-SCRIPTLET] # Home: /root/.gnupg
[2018-06-06 17:37] [ALPM-SCRIPTLET] # Config: [none]
[2018-06-06 17:37] [ALPM-SCRIPTLET] OK Dirmngr 2.2.7 at your service

Which is only a “file does not exist” error for a file/service we don’t use.


#46

This?:

> [2018-04-24 02:35] [ALPM-SCRIPTLET] e[1;1me[1;32m==>e[1;0me[1;1m Get Manjaro ARM Build Server's signature...e[1;0m
> [2018-04-24 02:35] [ALPM-SCRIPTLET] gpg: keyserver receive failed: No route to host
> [2018-04-24 02:35] [ALPM-SCRIPTLET] ==> ERROR: Remote key not fetched correctly from keyserver.
> [2018-04-24 02:35] [ALPM-SCRIPTLET] gpg: key 7D84FD49C15D4241 was created 36 days in the future (time warp or clock problem)
> [2018-04-24 02:35] [ALPM-SCRIPTLET]   -> Locally signing key B338D5DF...
> [2018-04-24 02:35] [ALPM-SCRIPTLET] ==> ERROR: B338D5DF could not be locally signed.
> [2018-04-24 02:35] [ALPM-SCRIPTLET] e[1;1me[1;32m==>e[1;0me[1;1m Get Oberon's signature for the manjaro keyring..e[1;0m
> [2018-04-24 02:35] [ALPM-SCRIPTLET] gpg: keyserver receive failed: No route to host
> [2018-04-24 02:35] [ALPM-SCRIPTLET] ==> ERROR: Remote key not fetched correctly from keyserver.
> [2018-04-24 02:35] [ALPM-SCRIPTLET] gpg: key 7D84FD49C15D4241 was created 36 days in the future (time warp or clock problem)
> [2018-04-24 02:35] [ALPM-SCRIPTLET]   -> Locally signing key 663CA268...
> [2018-04-24 02:35] [ALPM-SCRIPTLET] ==> ERROR: 663CA268 could not be locally signed.

#47

Look at the date.
It’s from an earlier RC test. :slight_smile: Which reminds me, I should delete logs before making images. :slight_smile:


[RPI2/3] Manjaro-ARM 18.06 Minimal Released
#48

What image did you test?
Odroid C1 image

What device did you test on?
OTT MXQ TV Box S805

Does it boot to a CLI login prompt?
Yes.

Can you login with both root and manjaro users?
Yes.

Can you install/update packages?
No. I have not wired network connection.

Can you run ping 8.8.8.8 from the manjaro user?
No. I have not wired network connection.


#49

Do you have a link to this box?
Is it just an odroid-c1 with a fancy case? :slight_smile:


#50

Yes, it is a odroid C1 with a customized board.
The link:


#51

Should I do a new thread for each testing cycle, or keep them all in one like I have so far?

Making new ones, will keep them clean and better to understand what images was tested.
Keeping it, will make less noise in the overall forum.


#52
-What image did you test?

Manjaro-Arm_Mate_rpi2_18.05.img

-What device did you test on?

Raspberry Pi 3B+

-Does it boot to a CLI login prompt?

Yes

-Can you login with both root and manjaro users?

Yes

-Can you install/update packages?

cannot install anything due to limited disk space.

-Does the resize-sd script work? If not, what if you remove yes from line 39?

uncertain - maybe need a run-down on how this test works…

Additional Notes: Mozilla Firefox is not working in the “manjaro” user profile but does work in “root”.

-Both “root” and “manjaro” users are claiming to have 0 bytes remaining on disk.

Used this to write the card (16 GB):

sudo dd if=/home/ajamese/Downloads/Manjaro-Arm_Mate_rpi2_18.05.img of=/dev/mmcblk0 bs=4M

-Text is funky in the terminal


#53

You should run the resize-sd script like so:
sudo resize-sd
To enlarge the partition.

This is odd. Maybe @GrayJack knows what’s going on there.

What do you mean funky?


#54

In the “root” profile the terminal text is not spaced properly causing the individual characters to run together- maybe just that it’s not a mono-spaced font?

The resize-sd did say it was successfully done but upon reboot it did not change the Low disk space warning.

Here is the output:

_start
[root@manjaro-arm ~]# sudo resize-sd
cat: ‘/sys/block/*/PARTUUID=5a237278-02/partition’: No such file or directory
expr: syntax error: unexpected argument ‘0’

This will attempt to grow the ‘Root (/)’ partition to the maximum space on the SDcard
after it is finished, it will grow the filesystem to fill the partition and reboot the device

There is a chance of corruption, loss of data, or even worse so proceed with caution

Press any key to continue …
Error: The device /dev/autofs is so small that it cannot possibly store a file
system or partition table. Perhaps you selected the wrong device?
Warning: Error fsyncing/closing /dev/autofs: Invalid argument
Retry/Ignore? ignore
Resize parition successful. Growing filesystem to fit partition …

resize2fs 1.44.1 (24-Mar-2018)
open: No such file or directory while opening PARTUUID=5a237278-02
Filesystem Size Used Avail Use% Mounted on
dev 461M 0 461M 0% /dev

Resize Filesystem successful
Press any key to reboot device …
_end

Uncertain of what file to change line 39 in.