I stopped by on irc but the channel didn't respond to my questions. I don't want to do an install but rather boot off of the network and mount the root file system via nfs. Seems like this might allow for faster OS access without having to use an SSD. Thumb drive and microsd are rather slow :)
On Wed, May 30, 2018, 10:30 AM Paul Whalen pwhalen@redhat.com wrote:
----- Original Message -----
----- Original Message -----
I have a raspberry pi 3b+ and I have a few questions
- I try to boot the Fedora 28 aarch64 raw image I run into an issue
with
the " Rx: failed to receive: -5".. I believe someone has a bug report
opened
already.. any idea on when this might be fixed?
https://bugzilla.redhat.com/show_bug.cgi?id=1573261
I can only boot the armhfp release as of right now. I guess I'm just looking for more detail about this issue.
It will be fixed as soon as possible, unfortunately we don't have an ETA. You should be able to boot the aarch64 image, it just takes a while. Disconnecting the ethernet cable until the kernel is booted is likely the fastest option.
- if I want to network boot and I can't use aarch64 because of the
above
issue what could I use for the boot file for armhfp? I'm familiar with booting x86 systems and you can typically use pxelinux.0 to start the process. If you could provide a download link that would be great on instructions on how to create the boot file would be fine.
You need to create a folder named 'pxelinux.cfg' in your tftp directory and put a file named using the MAC address of the client, eg pxelinux.cfg/01-02-02-01-07-15-80, where the mac address is 02:02:01:07:15:80. If you run 'bootcmd_pxe' in Uboot you will see the file name it expects.
=> run bootcmd_pxe starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Waiting for Ethernet connection... done. BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.0.215 (1005 ms) Using sms0 device TFTP from server 192.168.0.99; our IP address is 192.168.0.215 Filename 'pxelinux.0'. Load address: 0x82000000 Loading: ## 1.5 MiB/s done Bytes transferred = 26764 (688c hex) missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-02-01-07-15-80 Waiting for Ethernet connection... done. Using sms0 device TFTP from server 192.168.0.99; our IP address is 192.168.0.215 Filename 'pxelinux.cfg/01-02-02-01-07-15-80'. Load address: 0x80100000 Loading: # 1.2 MiB/s done Bytes transferred = 12067 (2f23 hex) Config file found Rawhide Boot Options 1: Fedora 27 Final - Everything 2: Fedora-27 Final Server Kickstart Defaults 3: Fedora-27 Final Kickstart Minimal 4: Fedora-28-20180425.0 Everything 5: Fedora-28-20180425.0 Server Kickstart Defaults 6: Fedora-28-20180425.0 Kickstart Minimal
Hopefully that helps!
Paul
Couple things I forgot- Anaconda needs a minimum of 2G ram to do a straightforward pxe installation, this is because it downloads a copy of the initramfs from the network. To work around this you will need to use an NFS mount for the initramfs. Below is an example of a pxe config file entries. The first one is for an interactive install, the second a kickstart install
menu title Rawhide Boot Options
default prompt 1 timeout 100
label Fedora 27 Final - Everything kernel fedora/Fedora-27-20171105.0/vmlinuz initrd fedora/Fedora-27-20171105.0/initrd.img fdtdir fedora/Fedora-27-20171105.0/dtb/ append console=ttyO2,115200 ip=eth0:dhcp inst.stage2=nfs:// 192.168.0.99:/srv/fedora/fedora-release/Fedora-27-20171105.0/everything/armhfp/ inst.repo= https://kojipkgs.fedoraproject.org/compose/27//Fedora-27-20171105.0/compose/...
label Fedora-27 Final Server Kickstart Defaults kernel fedora/Fedora-27-20171105.0/vmlinuz initrd fedora/Fedora-27-20171105.0/initrd.img fdtdir fedora/Fedora-27-20171105.0/dtb/ append console=ttyO2,115200 ip=eth0:dhcp inst.stage2=nfs:// 192.168.0.99:/srv/fedora/fedora-release/Fedora-27-20171105.0/server/armhfp/ inst.ks=http://192.168.0.99/kickstarts/armhfp/f27-server-sata.ks
If you run into any issues, do stop by #fedora-arm on Freenode, will be easier to help there.
Paul
thanks, Mike
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/me...
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/me...