arm October 2009

arm@lists.fedoraproject.org

8 participants
8 discussions

SELinux on F11 on ARM (in QEMU)?
by Per Nystrom 24 Oct '09

24 Oct '09

Hello, I am having one heck of a time getting SELinux working on ARM in QEMU. I compiled the 2.6.31.4 kernel following the instructions here: http://fedoraproject.org/wiki/Architectures/ARM/HowToQemu#Build_Kernel_Imag… And I added these lines to the .config: CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1 CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 And I used menuconfig to switch on Auditing support, Security labels for ext[234]. During boot I see this message, so I know there's at least *something* in there: SELinux: Initializing. I also see selinuxfs in /proc/filesystems. But it doesn't seem to actually be working: [root@fedora-arm ~]# sestatus -v SELinux status: disabled Any help is appreciated. Thanks, Per

4 13

prebuilt kernel 2.6.31.5 for Kirkwood available
by Dan Horák 23 Oct '09

23 Oct '09

Hello, I have built kernel 2.6.31.5 with modules and ramdisks for some combinations of Kirkwood-based devices (Sheevaplug and QNAP TS-[12]19) and devices carrying the root filesystem. They are available together with my build scripts at http://fedora.danny.cz/arm/ the kernels are: uImage-2.6.31.5-kw uImage-2.6.31.5-kw-ts219 => U-Boot images, generic, but the -ts219 explicitly sets the correct machine ID for the QNAP, because otherwise the ID of the related development board will be used. more details about the available ramdisks: - .padded = padded to 9MB which is the size of flash dedicated to ramdisk on QNAP TS-[12]19 - .uboot = ramdisk converted to an U-Boot image initrd-2.6.31.5-kw-lvm-sata.img initrd-2.6.31.5-kw-lvm-sata.img.padded initrd-2.6.31.5-kw-lvm-sata.img.uboot => use on QNAP with root filesystem on HDD(s) with LVM logical volume /dev/Linux/Root initrd-2.6.31.5-kw-sda1-sata.img initrd-2.6.31.5-kw-sda1-sata.img.padded initrd-2.6.31.5-kw-sda1-sata.img.uboot => use on QNAP with root filesystem on 1st HDD partition /dev/sda1 initrd-2.6.31.5-kw-sdmmc.img initrd-2.6.31.5-kw-sdmmc.img.uboot => use on Sheevaplug with root filesystem on 1st partition of SD card initrd-2.6.31.5-kw-usb.img initrd-2.6.31.5-kw-usb.img.uboot => use on Sheevaplug with root filesystem on 1st partition of USB attached storage (/dev/sda1) and how to test on Sheevaplug with root filesystem on 1st partition of SD card with network boot: > tftpboot 0x400000 uImage-2.6.31.5-kw > tftpboot 0x800000 initrd-2.6.31.5-kw-sdmmc.img.uboot > setenv bootargs 'console=ttyS0,115200 root=/dev/mmcblk0p1 ro' > bootm 0x400000 0x800000 Dan

1 0

Fedora-11 Status
by Kedar Sovani 23 Oct '09

23 Oct '09

Since the last announcement of F-11 packages, a large number of packages have further been built. There currently are above 9000 rpms in the Fedora-11 repositories. Our effort has been to make available the following package groups: Base Core Web-server Gnome Desktop Xfce desktop Development Tools X server Web development Admin Tools System Tools Java The Fedora-11 updates for a large set of packages are also now available. For Fedora-12, we would like to start tracking packages preferably when all the shared lib .so version updates are settled for f12 (thus avoiding any additional rebuild cycles at our end). Most likely this will happen by the Fedora-12 Beta Freeze date (29 Sept, in 3/4 days). Kedar.

2 6

prebuilt kernel 2.6.31.4 for Kirkwood available
by Dan Horák 22 Oct '09

22 Oct '09

Hello, I have built kernel 2.6.31.4 with modules and ramdisks for some combinations of Kirkwood-based devices (Sheevaplug and QNAP TS-[12]19) and devices carrying the root filesystem. They are available together with my build scripts at http://fedora.danny.cz/arm/ Dan

1 0

Fedora ARM Big endian Support
by Rocky Marrone 21 Oct '09

21 Oct '09

Hi I already install qemu with armv5tel-redhat-linux-gnueabi-g++ but this support little endian support. I want to have a Big endian support on Fedora ARM on QEMU. Can anybody help me out on that Thnx & Best Regards Rocky

1 0

kernel syscall register assignments?
by Steve Grubb 05 Oct '09

05 Oct '09

Hello, The Linux Audit System does not work for arm based systems. It is pretty easy to add audit support if someone can help me figure out the calling convention for the kernel. The place that needs to be hooked is here: http://lxr.linux.no/#linux+v2.6.31/arch/arm/kernel/ptrace.c#L844 I need to figure out which registers have syscall arg0, arg1, arg2, and arg4. For comparison, the MIPS processor is hooked into the audit system: http://lxr.linux.no/#linux+v2.6.31/arch/mips/kernel/ptrace.c#L565 Thanks, -Steve

1 0

success with Fedora on QNAP TS-219P
by Dan Horák 05 Oct '09

05 Oct '09

Hello, I have succeeded with booting and running Fedora/ARM on QNAP TS-219P [1]. I have used Debian howtos written by Martin Michlmayr [2] as a basis for QNAP specific information [2], root filesystem from [3] and an own kernel and initrd [4]. Available are 2 variants of the initrd - one boots into /dev/sda1 (ext3 partition on disk) and second one boots into a /dev/Linux/Root logical volume. The steps are 1. prepare a HDD with unpacked root filesystem on a partition (or a LV), you should also unpack the modules-*.tar.bz2 into the newly created filesystem 2. connect serial console to QNAP 3. start TFTP server on your workstation 4. set client/server IP addresses in U-Boot to match your network 5. from U-Boot prompt run tftpboot 0x800000 uImage-2.6.31.1-kw-ts219 tftpboot 0xa00000 initrd-2.6.31.1-kw-ts219-sda1.img.uboot setenv bootargs 'console=ttyS0,115200 ro root=/dev/sda1' bootm 0x800000 0xa00000 6. login as root, password should be marvell The kernel/initrd should work on TS-119, TS-219 and TS-219P. I know this mail is very brief, but if you have questions just ask me here or on the #fedora-arm IRC channel (my nick is sharkcz). final notes: - the init ramdisks are prepared by hand from a template created by mkinitrd - the *.padded files are supposed to be written to the QNAP's flash memory (2 MB kernel, 9 MB ramdisk) - red/green blinking of the power led is expected Dan [1] http://www.qnap.com/pro_detail_feature.asp?p_id=122 [2] http://www.cyrius.com/debian/kirkwood/qnap/ts-219/ [3] http://fedoraproject.org/wiki/Architectures/ARM#Latest_Release:_Fedora_11 [4] http://fedora.danny.cz/arm/ts-219p/

1 0

RPM problems with Fedora 11 on Sheevaplug
by Eric Moody 04 Oct '09

04 Oct '09

Hello everybody, I have a SheevaPlug that I have loaded Fedora 11 onto. When I use a USB memory key as my storage device RPM works great. However I would like to run the system from the MTD. I have create a jffs file system and flashed it onto the MTD. However RPM just flat out refuses to works. I keep getting errors accessing the Packages database. I have tried rebuilding that the database, and even creating new databases from scratch. Below is the output I receive. -bash-4.0# rpm -qa -vvv D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key D: loading keyring from rpmdb D: opening db environment /var/lib/rpm/Packages cdb:mpool:joinenv rpmdb: mmap: Invalid argument error: db4 error(22) from dbenv->open: Invalid argument D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 error: cannot open Packages index using db3 - Invalid argument (22) error: cannot open Packages database in /var/lib/rpm D: opening db environment /var/lib/rpm/Packages cdb:mpool:joinenv rpmdb: mmap: Invalid argument error: db4 error(22) from dbenv->open: Invalid argument D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 error: cannot open Packages database in /var/lib/rpm -bash-4.0# -bash-4.0# rpm --rebuilddb -vvv D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.1753 D: creating directory /var/lib/rpmrebuilddb.1753 D: opening old database with dbapi 3 D: opening db environment /var/lib/rpm/Packages cdb:mpool:joinenv rpmdb: mmap: Invalid argument error: db4 error(22) from dbenv->open: Invalid argument D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 error: cannot open Packages index using db3 - Invalid argument (22) D: removing directory /var/lib/rpmrebuilddb.1753 -bash-4.0# mv rpm rpmBorked -bash-4.0# mkdir rpm -bash-4.0# rpm --initdb -vvv D: opening db environment /var/lib/rpm/Packages cdb:mpool:joinenv rpmdb: mmap: Invalid argument error: db4 error(22) from dbenv->open: Invalid argument D: opening db index /var/lib/rpm/Packages create mode=0x42 error: cannot open Packages index using db3 - Invalid argument (22) I am thinking it has something to with the JFFS2 filesystem. Running my USB memory key with ext3 works just file. I used the same tarball to generate both filesystems. This is the command I used to generate the JFFS2 filesystem. mkfs.jffs2 -l -e 0x20000 --pad -r /home/rootfs-f11 -o fedora.jffs2 Thanks, Eric

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm October 2009