Today Dennis Gilmore asked me on #fedora-arm “Are you a packager in Fedora?” so I answered that I am in “packager” group but do not own a package in Fedora and do not have plans to change it.
It turned out that the question was part of thinking that maybe I should get membership in the secondary arch group which would allow me to commit my fixes directly. Normally I prefer to grab maintainer’s attention with new reported bug or even IRC discussion about an issue. But sometimes there is no response and fix is aarch64 related without any changes for primary architectures.
So now I can commit fixes to Fedora packages directly to git repositories. Will not overuse this privilege and make it only when it is really required.
Took me some time but finally I managed to workaround all issues and got X11 running on real AArch64 hardware.
Two years ago I started X11 on AArch64 using emulator. But planned to make it on real hardware one day. And that day came today.
What took so long? Several things. First I lacked hardware – but APM Mustang arrived one day. Then lack of PCI-Express support but it got solved.
So I started collecting graphic cards. Finally ended with Radeon HD5450 and Geforce GTS250 – both with 512MB ram. After last firmware update (to 0.14) they even got whole memory assigned. But none of them worked ;(
After few discussions it got finally confirmed that something is going on with supporting more than 64MB of memory on PCI cards. I prefer not to go to details. Anyway I digged and found Matrox G550 card in local computer scrapyard. Seller wrote that it has 32MB ram (Linux says that only 16MB is present).
Bought card, inserted into pinkiepie (Mustang) and after kernel rebuild I got nice 1920x1080x32-60 framebuffer and X11 over it. Maybe it is not the fastest but it works.
Tomorrow will reconfigure kernel to get USB working (and submit patch for Fedora config) which will give me keyboard, mouse and audio.
Next step? XFCE, GNOME, KDE testing of course ;D And building MPlayer so I will be able to watch movies too.
Today Peter Robinsson released RC5 of Fedora 21 installation ISO for AArch64 architecture. As usual I grabbed it for tests.
As usual I used “clean Mustang, just hdd” method as it is one of easiest to setup. Grabbed fresh F21 RC5 ISO, prepared partitions and rebooted.
There was an issue with “fs0:\EFI\BOOT\BOOTAA64.EFI” as it tried to run “\EFI\BOOT\grubx64.efi” instead of “\EFI\BOOT\grubaa64.efi” but if second one is started then installer booted fine.
New EFI binary was added: MokManager.efi – can be used it for managing keys used to sign kernel modules. Not tried that yet but good to have.
Also noticed that ‘this is testing’ nagging requester got removed. Also nice side/top graphics with “fedora SERVER” information were added.
Installed without issues and rebooted into fresh Fedora 21 Server installation. Things look good for final release.
When I got APM Mustang at home I knew that one day I will use it to test desktop environments. Lack of graphics and USB kept me away from it. And I am closer now…
Yesterday Mark Langsdorf wrote two patches which allow to use USB3 ports from Mustang’s backplate. I applied first version of them, altered DeviceTree blob a bit and after reboot I got that:
16:36 hrw@pinkiepie-rawhide:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1234:2088 Brain Actuated Technologies
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
All with slightly modified 3.18-rc2 kernel from Fedora rawhide.
Now need to sort out graphics… But first need to buy yet another card…
After my previous posts I got an email with question “how to install Fedora 21 on Mustang without DVD and network?” so decided to describe hard drive based method.
- APM Mustang with UEFI
- hard drive
- another computer to prepare hdd
- Fedora 21 installation ISO
- serial cable connected to Mustang and other computer
- Ethernet cable to get network on Mustang
- VNC viewer to control installation (not needed but recommended)
First step is preparing hard drive. Create 100MB GPT partition type “ef00″ (EFI System), format it as FAT and copy “/EFI” and “/images” directories from DVD. Edit “/EFI/BOOT/grub.cfg” file and change “Fedora-S-21_A-aarch64″ to “Fedora-S-21_A” because ext4 labels are shorter than ISO9660 ones.
Then do another partition — 2GB size. I used ext4 (other ones may work too). Format and label it as ‘Fedora-S-21_A’ using e2label or other tool. Copy content of DVD image into it.
Now put hard drive into Mustang and power on. From UEFI menu select shell and start run “FS0:\EFI\BOOT\BOOTAA64.efi” to get into GRUB. Press Enter to begin installation.
As before I went VNC way, selected hard drive and automatic partitioning. After few minutes system was installed and ready to reboot.
This time there were no issues with adding bootloader into UEFI boot order. Maybe because I left previous entries there?
And layout of partitions was not changed:
Fedora release 21 (Twenty One)
Kernel 3.17.0-301.fc21.aarch64 on an aarch64 (ttyS0)
localhost login: hrw
[hrw@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 298.1G 0 disk
├─sda1 8:1 0 127M 0 part /boot/efi
├─sda2 8:2 0 2G 0 part
├─sda3 8:3 0 500M 0 part /boot
└─sda4 8:4 0 294.1G 0 part
├─fedora--server-swap 253:0 0 8G 0 lvm [SWAP]
├─fedora--server-root 253:1 0 50G 0 lvm /
└─fedora--server-home 253:2 0 236G 0 lvm /home
So if you have APM Mustang with one hdd and no external network connection on site then looks like this is an easiest way. Sure, it requires some work but allows to make an installation without any extra hardware connected to Mustang.
Today I took a small break and decided to install Debian on APM Mustang. How it went? Read on.
– kernel and initramfs from Debian daily d-i builds
– USB stick with GRUB from Fedora (one from my second Fedora installation
– APM Mustang with UEFI
– serial cable connected to Mustang and other computer
– Ethernet cable to get network on Mustang
Why did I used GRUB from Fedora? Debian one had issues with finding own modules (or something like that).
Ok, so let’s boot into GRUB. Once there load kernel and initramfs:
linux /debian/vmlinux console=ttyS0,115220
Installation went smooth. To the point when installer tried to install GRUB :(
Rebooted, loaded freshly installed kernel/initramfs from Fedora boot loader but still failed:
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
So will not check how Debian works on APM Mustang. But bug will be reported.