abefroman99
Posts: 10
Joined: Thu May 28, 2015 12:39 am

Does anyone know why this won't boot?

Thu Jun 18, 2015 6:27 pm

Does anyone know why this won't boot? (or what I can check).

I followed the instructions from here: http://jonarcher.info/2015/02/getting-f ... erry-pi-2/

Code: Select all

$ sudo cp -r firmware/boot/* /mnt/sdcard/boot/
$ sudo cp -r firmware/modules/3.18.16-v7+/* /mnt/sdcard/lib/modules/
$ sudo blkid /dev/sdc1
/dev/sdc1: SEC_TYPE="msdos" UUID="6429-A171" TYPE="vfat" 
$ sudo pico /mnt/sdcard/boot/cmdline.txt
$ sudo pico /mnt/sdcard/boot/config.txt
$ sudo cat /mnt/sdcard/etc/fstab 
UUID=fe0fbdbc-e734-4f07-9b1c-7564e3a356b9  / xfs    defaults,noatime 0 0
UUID=6429-A171  /boot vfat    defaults,noatime 0 0
UUID=fce4766e-54c4-487d-98fa-eeed60e7aca0  swap swap    defaults,noatime 0 0
$ sudo cat /mnt/sdcard/boot/cmdline.txt
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 rootfstype=xfs elevator=deadline rootwait
$ sudo cat /mnt/sdcard/boot/config.txt
#uncomment to overclock the arm. 700 MHz is the default.
arm_freq=700# NOOBS Auto-generated Settings:
hdmi_force_hotplug=1
config_hdmi_boost=4
overscan_left=24
overscan_right=24
overscan_top=16
overscan_bottom=16
disable_overscan=0
core_freq=250
sdram_freq=400
over_voltage=0
In the commandline.txt, how can I verify this is the correct dev name?
root=/dev/mmcblk0p3 rootfstype=xfs

myoung008
Posts: 55
Joined: Mon Mar 18, 2013 9:56 pm

Re: Does anyone know why this won't boot?

Thu Jun 18, 2015 9:36 pm

Where does it get hung up?

No display at all?
Rainbow screen?
After kernel init?
Userland setup?

As for the cmdline.txt question, post output of:

Code: Select all

sudo blkid /dev/sdc*

nowantregister
Posts: 1
Joined: Sat Jan 23, 2016 5:37 am

Re: Does anyone know why this won't boot?

Sat Jan 23, 2016 5:59 am

Going to guess we have the same problem. I'm using the ua-netinstall though.

We'd have to make sure the the case is defined and the system has the tools for creation. A lack of case for XFS is the initial bounce. xfsprogs is not in the original install, at least raspbian, and will need to be added as well.

Why am I crazy and want XFS? selinux. Yes, insane. I know. Doing testing.

https://github.com/debian-pi/raspbian-u ... init.d/rcS

Code: Select all

# prepare rootfs mount options
case "$rootfstype" in
  "btrfs")
    kernel_module=true
    rootfs_mkfs_options=${rootfs_mkfs_options:-'-f'}
    rootfs_install_mount_options=${rootfs_install_mount_options:-'noatime'}
    rootfs_mount_options=${rootfs_mount_options:-'noatime'}
    ;;
  "ext4")
    kernel_module=true
    rootfs_mkfs_options=${rootfs_mkfs_options:-''}
    rootfs_install_mount_options=${rootfs_install_mount_options:-'noatime,data=writeback,nobarrier,noinit_itable'}
    rootfs_mount_options=${rootfs_mount_options:-'errors=remount-ro,noatime'}
    ;;
  "f2fs")
    kernel_module=true
    rootfs_mkfs_options=${rootfs_mkfs_options:-''}
    rootfs_install_mount_options=${rootfs_install_mount_options:-'noatime'}
    rootfs_mount_options=${rootfs_mount_options:-'noatime'}
    ;;
"xfs")
    kernel_module=true
    rootfs_mkfs_options=${rootfs_mkfs_options:-'-i size=512'}
    rootfs_install_mount_options=${rootfs_install_mount_options:-'noatime'}
    rootfs_mount_options=${rootfs_mount_options:-'noatime'}
    ;;
  *)
    echo "Unknown filesystem specified: $rootfstype"
    fail
    ;;
esac

Code: Select all

# minimal
    minimal_packages="fake-hwclock,ifupdown,net-tools,ntp,openssh-server,xfsprogs"
Probably want a real adult to look over that. Making guesses. I just copy pasted f2fs and added the needed preset for selinux and added the xfs package to base. About to test it out in a bit.

User avatar
hexelpdkk
Posts: 177
Joined: Fri Feb 24, 2012 4:40 pm

Re: Does anyone know why this won't boot?

Wed Feb 03, 2016 8:55 pm

From memory, I don't think the kernel from the foundation has xfs compiled in (I seem to remember hitting this myself) which is why the instructions work for F21 but not F23 (where the fedora arm root partition is xfs). Instead, look at the thread on a respin by vaughan - viewtopic.php?f=51&t=125548. I have done similar (using some of his bits, and sometimes my own kernel) successfully for various F23 versions - XFCE and minimal, as far as I remember.

User avatar
rpdom
Posts: 15601
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: Does anyone know why this won't boot?

Thu Feb 04, 2016 7:27 am

hexelpdkk wrote:From memory, I don't think the kernel from the foundation has xfs compiled in
It's fairly easy to check

Code: Select all

[email protected] ~ $ sudo modprobe configs
[email protected] ~ $ zgrep XFS /proc/config.gz
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_XFS_WARN is not set
# CONFIG_XFS_DEBUG is not set
# CONFIG_VXFS_FS is not set
That would imply that it is included in the standard 4.1.13-v7+ kernel that I'm running, at least.

User avatar
hexelpdkk
Posts: 177
Joined: Fri Feb 24, 2012 4:40 pm

Re: Does anyone know why this won't boot?

Thu Feb 04, 2016 7:48 am

rpdom wrote:That would imply that it is included in the standard 4.1.13-v7+ kernel that I'm running, at least.
It's a module, not compiled in to the kernel image itself, and so can not be used to mount the root file system. This is why Jon Archer's method works on F21 (which has the second partition as ext4) but F23 doesn't (where the second partition is xfs).

User avatar
rpdom
Posts: 15601
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: Does anyone know why this won't boot?

Thu Feb 04, 2016 8:10 am

hexelpdkk wrote:
rpdom wrote:That would imply that it is included in the standard 4.1.13-v7+ kernel that I'm running, at least.
It's a module, not compiled in to the kernel image itself, and so can not be used to mount the root file system. This is why Jon Archer's method works on F21 (which has the second partition as ext4) but F23 doesn't (where the second partition is xfs).
In that case, use an initrd with the modules in.

Return to “Pidora / Fedora”