The latest upgrade to 4.7.2-201.fc24.armv7hl fails to boot on Odroid XU4.
by Stewart Samuels
Dracut fails to build a bootable image for Odroid XU4 for the 4.7.2-201 fc24 initramfs.
it seems that Dracut fails to create the Early CPIO image it needs to boot the system.
Following are initial comparisons from the previous 4.6.6-300.fc24.armv7hl initramfs
image.
################################################
lsinitrd initramfs-4.6.6-300.fc24.armv7hl.img | less
------------------------------------------------------------------------------
Image: initramfs-4.6.6-300.fc24.armv7hl.img: 44M
========================================================================
Early CPIO image
========================================================================
drwxr-xr-x 3 root root 0 Jul 8 06:27 .
-rw-r--r-- 1 root root 2 Jul 8 06:27 early_cpio
drwxr-xr-x 3 root root 0 Jul 8 06:27 kernel
drwxr-xr-x 3 root root 0 Jul 8 06:27 kernel/x86
drwxr-xr-x 2 root root 0 Jul 8 06:27 kernel/x86/microcode
-rw-r--r-- 1 root root 24070 Jul 8 06:27 kernel/x86/microcode/AuthenticAMD.bin
========================================================================
Version: dracut-044-20.fc24
Arguments: --add-drivers 'dw_mmc-exynos exynosdrm ehci-exynos ohci-exynos'
dracut modules:
bash
systemd
systemd-initrd
modsign
nss-softokn
i18n
network
:
---------------------------------------------------------------------------------------------
################################################
lsinitrd initramfs-4.7.2-201.fc24.armv7hl.img | less
------------------------------------------------------------------------------
Image: initramfs-4.7.2-201.fc24.armv7hl.img: 16M
========================================================================
Version: dracut-044-20.fc24
Arguments: --add-drivers 'dw_mmc-exynos exynosdrm ehci-exynos ohci-exynos'
dracut modules:
bash
systemd
systemd-initrd
nss-softokn
i18n
network
ifcfg
drm
plymouth
kernel-modules
kernel-network-modules
resume
rootfs-block
terminfo
udev-rules
dracut-systemd
:
---------------------------------------------------------------------------------------------
###########################################################
[root@myodroid boot]# ls -l initramfs*
-rw------- 1 root root 44642406 Jun 14 12:46 initramfs-0-rescue-b08cce8b3b174044a96690bec89c2b5c.img
-rw------- 1 root root 45330243 Aug 16 20:31 initramfs-4.6.6-300.fc24.armv7hl.img
-rw------- 1 root root 16408397 Sep 8 07:28 initramfs-4.7.2-201.fc24.armv7hl.img
6 years, 7 months
48-bit support in F26?
by Jon Masters
Hi Jeremy, all,
I was just catching up with some folks and we discussed the status of
48-bit VA support. It seems to me that it would make most sense to have
an official coordination effort between those vendors/community members
who are interested, to ensure that they help with the necessary package
updates ahead of the kernel, and work with a test kernel to identify any
additional packages or issues that need resolving. I believe it would
make most sense to have a Fedora feature page (or something less grand,
but similar in concept) tracking this for F26, with the deps.
Perhaps Jeremy can update us on the status, and then he and others can
help drive this forward (someone should nominate themselves as the ring
leader too). I spoke with Cavium earlier today, and I know they'll be
keen to help. I know Qualcomm had expressed interest during our IRC
meetings in helping out. To that end, I'm copying at least those I know
so far who are interested here.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
6 years, 8 months
Fedora 25 on Raspberry PI 2 - SPI, I2C - device tree overlays?
by Jan
Hi,
I'm trying to understand if it is possible, and if yes then how, to enable
I2C and SPI.
On Raspbian one had to edit config.txt, but here overlays directory on
partition is empty.
Is there somewhere documented how to populate folder?
FAQ on https://fedoraproject.org/wiki/Raspberry_Pi is a bit unclear for me,
when it says no support for HATs.
It describes that some manual steps are required. That's fine, however I'm
not kernel developer,
I just play with some simple sensors. Using simple python scripts.
Is a quick answer to such usage: "Not yet"?
Right now Fedora 25 installed nicely on PI, and works great as Fedora box,
imap server, some www page.
Regards
Jan
6 years, 8 months
Preparing Fedora 25 for Chromebook fails
by dwella＠cock.li
Following the instructions at https://fedoraproject.org/wiki/Architectures/ARM/Chromebook, I have encountered this issue. I use the default workstation build (I guess it's Gnome) instead of an spin here, however I have tested all the spins and they fail to build also. Basically the fs seems to be corrupt:
```sh
$ cd /var/tmp
```
```sh
$ wget http://download.fedoraproject.org/pub/fedora/linux/releases/25/Workstatio...
```
Unpack the archive
```sh
$ unxz -v -k Fedora-Workstation-armhfp-25-1.3-sda.raw.xz
```
Next you mount the raw disk image
```sh
$ sudo kpartx -av /var/tmp/Fedora-Workstation-armhfp-25-1.3-sda.raw
```
The device mapping output:
```sh
add map loop0p1 (253:4): 0 59392 linear /dev/loop0 2048
add map loop0p2 (253:5): 0 999424 linear /dev/loop0 61440
add map loop0p3 (253:6): 0 999424 linear /dev/loop0 1060864
add map loop0p4 (253:7): 0 10741760 linear /dev/loop0 2060288
```
Extract the root file system
```sh
$ sudo dd if=/dev/mapper/loop0p3 of=/var/tmp/Fedora-25-Workstation-rootfs.ext4 conv=fsync status=progress
```
Delete the raw disk image mappings
```sh
$ sudo kpartx -d /var/tmp/Fedora-Workstation-armhfp-25-1.3-sda.raw
```
Check the root file system copy
```sh
$ sudo e2fsck -f /var/tmp/Fedora-25-Workstation-rootfs.ext4
```
e2fsck fails, error message
```sh
e2fsck 1.43.1 (08-Jun-2016)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /var/tmp/Fedora-25-Workstation-rootfs.ext4
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
/var/tmp/Fedora-25-Workstation-rootfs.ext4 contains a swap file system labelled '_swap'
```
6 years, 10 months
Missing bcm2835-gpiomem kernel module in Fedora 25
by Michal Sladek
Hello!
I use Fedora 25 on my Raspberry Pi 3. I would like to use DHT22 driver from Adafruit but there is no /dev/gpiomem device in Fedora 25. It seems that bcm2835-gpiomem kernel module is missing.
Many drivers and libraries use this device for GPIO access. Is there a package with bcm2835-gpiomem kernel mdule?
Michal
6 years, 10 months
Resizing Micro SD card
by Rafael Leiva-Ochoa
Hi Everyone,
I have recently installed Fedora Server 25 on my Raspberry PI 3, and
the install was really easy. But, I am having problems resizing the
hardrive using the following instructions:
https://fedoraproject.org/wiki/Raspberry_Pi#Resize_after_initial-setup. I
only get the following error when issuing the resize command:
[test@localhost ~]$ sudo resize2fs /dev/mmcblk0p4
[sudo] password for test:
resize2fs 1.43.1 (08-Jun-2016)
resize2fs: Bad magic number in super-block while trying to open
/dev/mmcblk0p4
Couldn't find valid filesystem superblock.
[test@localhost ~]$
Any ideas?
Thanks,
Rafael
6 years, 10 months
Re: Resizing Micro SD card
by Rafael Leiva-Ochoa
Ok thanks.
On Thu, Nov 24, 2016 at 5:32 PM Daniel Laczi <dlaczi(a)t-online.de> wrote:
> Hi Rafael,
>
> Fedora 25 was released this week:
> https://fedoramagazine.org/fedora-25-released/
>
> So yes, it is no longer Beta ;)
>
>
> Daniel
>
>
> On November 25, 2016 12:15:11 AM GMT+01:00, Rafael Leiva-Ochoa <
> spawn(a)rloteck.net> wrote:
>
> Thanks Paul. sudo xfs_growfs /dev/mmcblk0p4 worked..
>
> By the way, the current release posted on the wiki is the production
> release correct? it's no longer Beta?
>
> On Thu, Nov 24, 2016 at 6:48 AM Paul Whalen <pwhalen(a)redhat.com> wrote:
>
>
> Hi Rafael,
>
> ----- Original Message -----
> > Hi Everyone,
> >
> > I have recently installed Fedora Server 25 on my Raspberry PI 3, and the
> > install was really easy. But, I am having problems resizing the hardrive
> > using the following instructions:
> > https://fedoraproject.org/wiki/Raspberry_Pi#Resize_after_initial-setup
> . I
> > only get the following error when issuing the resize command:
> >
> >
> >
> > [test@localhost ~]$ sudo resize2fs /dev/mmcblk0p4
> >
> > [sudo] password for test:
> >
> > resize2fs 1.43.1 (08-Jun-2016)
> >
> > resize2fs: Bad magic number in super-block while trying to open
> > /dev/mmcblk0p4
> >
> > Couldn't find valid filesystem superblock.
>
> Please try:
>
> sudo xfs_growfs /dev/mmcblk0p4
>
> I've also updated the wiki, thanks for pointing that out.
>
>
> Paul
>
> >
> > [test@localhost ~]$
> >
> > Any ideas?
> >
> > Thanks,
> >
> > Rafael
> >
> > _______________________________________________
> > arm mailing list -- arm(a)lists.fedoraproject.org
> > To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> >
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
> ------------------------------
>
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
>
6 years, 10 months
