You are not logged in.

#1 2017-07-09 11:16:17

eugen-b
Member
Registered: 2017-07-09
Posts: 56

Install medium lacks archlinux32-keyring

Hello guys!
I'm active on Manjaro forum. My impression there is that there is quite a lot of demand for continuation i686. The decission to drop i686 by Arch was justified with download numbers, but it is a mere quantitative analysis, it doesn't measure the value of the 32bit hardware for the users. I would argue that all the 32bit netbooks have a higher value to some of the users than the specs of the machines would suggest.
I hope and many other I know, too, that you project succeeds. It would be not improbable that projects like Manjaro would use your packages as upstream. I will post about my testing experience with archlinux32 on Manjaro forums, this will help you get more testers, I hope.

So, I was able to boot the ISO on this machine (data from different distro, will update when I got more than base + Xorg installed on Archlinux32):

$ inxi -Fxxxz
System:    Host: antix17 Kernel: 4.10.1-antix.1-486-smp i686 (32 bit gcc: 6.3.0)
           Desktop: JWM 2.3.6 dm: slim
           Distro: antiX-17.a2_386-full keerfa 19 March 2017
Machine:   Device: laptop System: ASUSTeK product: 1001HA v: x.x
           Mobo: ASUSTeK model: 1005HA v: x.xx
           BIOS: American Megatrends v: 1601 date: 04/18/2011
           Chassis: type: 10 v: x.x
Battery    BAT0: charge: 12.4 Wh 100.0% condition: 12.4/21.5 Wh (57%) volts: 12.3/10.8
           model: ASUS 1005HA Li-ion serial: N/A status: Full cycles: 0
CPU:       Single core Intel Atom N270 (-HT-) cache: 512 KB
           flags: (nx pae sse sse2 sse3 ssse3) bmips: 3199
           clock speeds: min/max: 800/1600 MHz 1: 1600 MHz 2: 1600 MHz
Graphics:  Card: Intel Mobile 945GSE Express Integrated Graphics Controller
           bus-ID: 00:02.0 chip-ID: 8086:27ae
           Display Server: X.Org 1.19.2 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1024x600@60.00hz
           GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2
           GLX Version: 2.1 Mesa 13.0.5 Direct Rendering: Yes
Audio:     Card Intel NM10/ICH7 Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:27d8
           Sound: Advanced Linux Sound Architecture v: k4.10.1-antix.1-486-smp
Network:   Card-1: Qualcomm Atheros AR8132 Fast Ethernet
           driver: atl1c v: 1.0.1.1-NAPI port: ec00 bus-ID: 01:00.0 chip-ID: 1969:1062
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-2: Ralink RT3090 Wireless 802.11n 1T/1R PCIe
           driver: rt2800pci v: 2.3.0 bus-ID: 02:00.0 chip-ID: 1814:3090
           IF: wlan0 state: down mac: <filter>
Drives:    HDD Total Size: 32.0GB (61.0% used)
           ID-1: /dev/sda model: SAMSUNG_SSD_PM83 size: 32.0GB serial: S0XLNSACA03025
Partition: ID-1: / size: 30G used: 19G (63%) fs: btrfs dev: /dev/sda1
           ID-2: /home size: 30G used: 19G (63%) fs: btrfs dev: /dev/sda1
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 158 Uptime: 6 min Memory: 159.2/2008.6MB
           Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.111 running in lxterminal) inxi: 2.3.8

I was able to install with the available mirrors in /etc/pacman.d/mirrorlist following https://wiki.archlinux.org/index.php/Installation_guide .
But I failed when I added http://mirror.archlinux32.org/$arch/$branch/ on top of the mirrorlist. I kept getting "corrupted package, wrong singnature of" a devoper whose name I forgot. This issue got resolved after installing archlinux32-keyring, then I was able to install from archlinux32 repo.
The systems installed from archlinux32 repo boots, I'm able to connect with wifi-menu and everithing is fine so far. But the pacakges are a bit old, this will prevent some test users from testing your distro at this point.

Thank you for your work and commitment to keep 32bit harware usable! (Because for those who know, Linux is only usable with pacman.)
Regards
eugen-b

Offline

#2 2017-07-11 04:43:15

tyzoid
Administrator
From: Ann Arbor, MI
Registered: 2017-06-17
Posts: 86

Re: Install medium lacks archlinux32-keyring

Thanks Eugene-b.

This is a known issue. The current iso uses the 32bit packages from our repo as we begin testing, but is still provided as a service to install mainline arch in i686 mode (they discontinued their i686 isos back in February).

We will be adding in the archlinux32-keyring in next month's ISO as we get more infrastructure in place.

We certainly look forward to working with the Manjaro group, as well as others that rely on Arch's repos as upstream, and are certainly keeping these projects in mind during the transition process.

Thanks for helping test this.

Offline

#3 2017-07-18 08:57:23

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 617

Re: Install medium lacks archlinux32-keyring

I moved pacman from testing to core, so archlinux32-keyring should be automatically installed as a dependency for upcoming isos (and installations).

The lag in the package versions is due to build issues, we haven't figured out yet. These prevent all dependent packages from being built.

Any help/hints regarding the failing builds are appreciated.

Cheers,
deep42thought

Offline

#4 2017-07-18 22:56:27

eugen-b
Member
Registered: 2017-07-09
Posts: 56

Re: Install medium lacks archlinux32-keyring

deep42thought wrote:

I moved pacman from testing to core, so archlinux32-keyring should be automatically installed as a dependency for upcoming isos (and installations).

Great, congratulation!

The lag in the package versions is due to build issues, we haven't figured out yet. These prevent all dependent packages from being built.

Any help/hints regarding the failing builds are appreciated.

I know little about building a set of packages. I will create a topic on Manjaro forum to get people interested in archlinux32 and hope some people with knowledge come to help.

Offline

#5 2017-07-19 21:24:20

jonathon
Member
From: UK
Registered: 2017-07-19
Posts: 40
Website

Re: Install medium lacks archlinux32-keyring

I've had a quick look at the `xz` build log, and the failure is down to the compiler is treating warnings as errors. Now - this might well be the correct behaviour if it's the same for the normal Arch packaging process. If not, though, it's a compiler flag change.

Offline

#6 2017-08-03 01:01:14

eugen-b
Member
Registered: 2017-07-09
Posts: 56

Re: Install medium lacks archlinux32-keyring

New ISO 2017-08-01 has the same issues.
NetworkManager adds confusion, becasue you cannot blindly follow the Arch installation guide. If you want to use wifi-menu you have to stop NetworkManager.
I installed a base system using archlinux32 mirror. I hoped archlinux32-keyring was already installed on the ISO, but no, I had to install it myself and repeat the pacstrap download.
All are probably known issues.
Thanks for your insanely hard work!

PS: You changed the ISO structure, why? I know because I use Grub2 to boot the ISO from disk.

Last edited by eugen-b (2017-08-03 01:03:20)

Offline

#7 2017-08-03 06:01:55

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 617

Re: Install medium lacks archlinux32-keyring

The idea was to include aif-ng, so we could automatically test the install from the iso and experienced users could automatically install a large bunch of installations.

Regarding the keyring: Tyzoid, did you maybe use an old version of the pacman package? (I'm not sure if I bumped the $pkgrel when including archlinux32-keyring)

Offline

#8 2017-08-04 02:03:03

tyzoid
Administrator
From: Ann Arbor, MI
Registered: 2017-06-17
Posts: 86

Re: Install medium lacks archlinux32-keyring

It's definately included, so I'm not sure why you're getting those errors. Can you post a screenshot of what you see?
t9TMkIRl.png

Offline

#9 2017-08-04 03:26:01

tyzoid
Administrator
From: Ann Arbor, MI
Registered: 2017-06-17
Posts: 86

Re: Install medium lacks archlinux32-keyring

Ah, I see what you're referring to. The package definately is installed, but for some reason the keys did not properly add themselves to the pacman keyring, and so packages are failing to verify. I'll need to work out why with deep42thought.

Offline

#10 2017-08-07 14:17:50

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 617

Re: Install medium lacks archlinux32-keyring

I found the issue: for the official archlinux-keyring, there is a systemd-unit on the iso which runs 'pacman-key --init' and 'pacman-key --populate archlinux' after booting -- I added 'pacman-key --populate archlinux32'.
Apparently, pacstrap (which installs archlinux(32)-keyring) does not (properly) run the post-install script(s).

Offline

Board footer

Powered by FluxBB