Hello,
On the armStoneA8 board, using NBoot V14 and U-Boot, I'm trying to boot
the downstream 3.3.7 kernel (BSP V1.1) from SD with a LimeJeOS rootfs on
SD. I had to reconfigure the kernel with CONFIG_LBDAF to mount the
ext3[*] rootfs r/w. This is what I get now:
[...]
mmc0: new high speed SDHC card at address b368
IPv6 over IPv4 tunneling driver
mmcblk0: mmc0:b368 NCard 7.48 GiB
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
mmcblk0: p1
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
s3c-rtc s3c64xx-rtc: setting system clock to 2000-01-01 00:00:00 UTC
(946684800)
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:1.
Freeing init memory: 148K
Failed to mount /dev: No such device
Our rootfs definitely contains /dev, so what is this complaining about?
Thanks,
Andreas
[*] U-Boot seemed to hang loading zImage from ext4.
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi ARM :-), Hi Jos,
Alex and I have worked yesterday a few hours to finish up the last remaining
bugs for a 12.2 RC2 release. we plan that this is the last RC before final
12.2 for ARM, which is scheduled for November 6th.
The changes over RC1 are:
* various bugfixes in the imaging
* add an update repository to the images for maintenance
* adding various fixes for booting machines without RTC with a reasonable
system time
* Adding a YaST firstboot stage for configuring the country, language, root
password and creating the first user login
* various smaller fixes in packaging
We have also enabled support for the following SoCs'
* Calxeda Highbank
* CuBox
* IMX 53
* Samsung Origen
In addition, we added XFCE images for panda and beagle board. We know that
those still have some bugs that need to be fixed for the final release. the
JeOS images are good though.
We've personally tested some of the variations, but not all of them. We'd like
to get more feedback about it. In addition to that, we've also worked on
graphics support for a few of the boards, with varying results.
The Raspberry Pi image is not part of this release, it will come at a later
point in time as a separate announcement.
The images are available for download from:
http://download.opensuse.org/ports/armv7hl/distribution/12.2-RC2/
This link is not yet up, I'm still waiting for the build service team to sign
and upload the images there.
This link:
http://download.opensuse.org/ports/armv7hl/distribution/openSUSE-stable/
will point to RC2 once it is available so we could use that one as well.
I hope that we can do the announcement on sunday evening latest, but it might
slip to monday I'm afraid :(
Please work on the promo bits, and fire at will once the link above (with -
RC2) is working. The rest of the announcement can be reused from the RC1
announcement that Andrew did.
Thanks!
Dirk
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
kiwi is broken due to an update on Virtualization:Appliances which lead to a conflict in kiwi.changes.
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I tested quickly JeOS and XFCE beagle images on a beagleboard xM.
YaST firstboot is launched, so it is very nice to have a configured board. But it is launched on the serial port and not on the DVI output. Is it configurable? I guess it is launched on the debug console?
It could be nice to have it on serial for JeOS and on graphical user interface on XFCE image.
Moreover, XFCE (and X) is (are) not launched automatically on boot. I needed to do a "sudo startxfce4".
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
with my first pacthes for armv5 support to kiwi, I am nearly done but I have a problem with vmlinuz.
I get the following error during Raspberry Pi image build:
[ 1927s] mv: cannot stat 'vmlinuz-3.1.10-1.17-raspberrypi': No such file or directory
Which lead to the final error:
[ 1928s] Oct-31 15:43:23 <1> : Extracting kernel
[ 1928s] Oct-31 15:43:23 <1> : EXEC [pwd]
[ 1928s] Oct-31 15:43:24 <3> : Can't find kernel for extraction: No such file or directory
It seems that the kiwi source code is:
********************************************************************************
#==========================================
# create common kernel files, last wins !
#------------------------------------------
pushd /boot
if [ -f uImage-$VERSION ];then
mv uImage-$VERSION vmlinuz
elif [ -f vmlinux-$VERSION.gz ];then
mv vmlinux-$VERSION.gz vmlinux.gz
mv vmlinuz-$VERSION vmlinuz
elif [ -f vmlinuz-$VERSION.el5 ];then
mv vmlinux-$VERSION.el5 vmlinuz
elif [ -f vmlinuz-$VERSION ];then
mv vmlinuz-$VERSION vmlinuz
elif [ -f image-$VERSION ];then
mv image-$VERSION vmlinuz
else
rm -f vmlinux
cp vmlinux-$VERSION vmlinux
mv vmlinux-$VERSION vmlinuz
fi
********************************************************************************
So, "mv" should occur only when the file exist. In my case it should not stop in vmlinuz-$VERSION but in image-$VERSION.
Any idea what is going on?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi Marcus,
I'm wondering how the kiwi initrd determines which drivers need to be included in the initrd. To be precise, I'm missing the drivers/mtd directory which renders the vexpress image unusable, because it doesn't contain disk drivers ;).
Do you manually pick modules during the creation of the initial kiwi initrd?
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
On 29.10.2012, at 15:30, <guillaume.gardet(a)opensuse.org> wrote:
>
>
> home:Guillaume_G:branches:openSUSE:12.2:ARM/JeOS -> openSUSE:12.2:ARM/JeOS
>
>
> https://build.opensuse.org/request/show/139673
>
> Description: * Fix /etc/sysconfig/windowmanager hack to get XFCE as default
> * Boot in runlevel 5 (gfx mode) instead of 3 (default)
>
> ++++++ config.sh
> --- config.sh
> +++ config.sh
> @@ -88,8 +88,26 @@
> #--------------------------------------
> # XXX only do for XFCE image types
> if [ -e /etc/sysconfig/displaymanager ]; then
> - sed -i 's/^DISPLAYMANAGER=.*/DISPLAYMANAGER="lightdm"' /etc/sysconfig/displaymanager
> - sed -i 's/^DEFAULT_WM=.*/DEFAULT_WM="xfce"' /etc/sysconfig/windowmanager
> + baseUpdateSysConfig /etc/sysconfig/displaymanager DISPLAYMANAGER lightdm
> +# baseUpdateSysConfig is working only on existing vars and DEFAULT_WM is not always defined, so test if exist
In which case is it not defined? Can we assume that any case we care about it is defined? If so, we can just shove it into another if [ -e /etc/sysconfig/windowmanager ] && ! grep -q DEFAULT_WM /etc/sysconfig/windowsmanager; then ... block
> + grep_result=$(grep DEFAULT_WM /etc/sysconfig/windowmanager)
> + if [ "$grep_result" == "" ]; then
> + echo '
Better use the EOF variant used in other spots in this file. I'm not sure we really need this path though. Please verify.
> +## Path: Desktop/Window manager
> +## Description:
> +## Type: string(gnome,kde4,kde,lxde,xfce,twm,icewm)
> +## Default: xfce
> +## Config: profiles,kde,susewm
> +#
> +# Here you can set the default window manager (kde, fvwm, ...)
> +# changes here require at least a re-login
> +DEFAULT_WM="xfce"' >> /etc/sysconfig/windowmanager
> + else
> + baseUpdateSysConfig /etc/sysconfig/windowmanager DEFAULT_WM xfce
> + fi
> +# We want to start in gfx mode
Wrong indent :)
> + baseSetRunlevel 5
> + suseConfig
Do we need this really?
Alex
> fi
>
> #======================================
>
>
> To REVIEW against the previous version:
> osc request show --diff 139673
>
> To ACCEPT the request:
> osc request accept 139673 --message="reviewed ok."
>
> To DECLINE the request:
> osc request decline 139673 --message="declined for reason xyz (see ... for background / policy / ...)."
>
> To REVOKE the request:
> osc request revoke 139673 --message="retracted because ..., sorry / thx / see better version ..."
> --
> Hermes messaging (http://hermes.opensuse.org)
> openSUSE Build Service (https://build.opensuse.org/)
> Collaboration: http://en.opensuse.org/Build_Service/Collaboration
>
>
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
In my OBS home repo I get this error during armv5 environment setup:
file /usr/bin/qemu-arm-binfmt from install of qemu-accel-armv5tel-0.2-21.1.x86_64 conflicts with file from package qemu-linux-user-1.2.0-138.4.x86_64
Same with a local build. To fix it it seems that a rebuild of qemu (for qemu-linux-user package) is needed. I did it in local repo and this error is fixed.
So, please trigger a rebuild of qemu.
But I get another error: ARCHITECTURE PERSONALITY IS UNKNOWN. Log:
[ 27s] booting XEN kernel ...
[ 27s] xm create -c /var/tmp/build.xen.conf-hxGya4ErF name=build_2 disk=phy:/dev/dm-2,hda1,w disk=phy:/dev/dm-3,hda2,w extra=quiet init=/.build/initvm elevator=noop panic=1 console=ttyS0
[ 32s] Using config file "/var/tmp/build.xen.conf-hxGya4ErF".
[ 32s] Started domain build_2 (id=26220)
[ 32s] [ 0.260031] PCI: Fatal: No config space access function found
[ 32s] [ 0.264046] Unable to read sysrq code in control/sysrq
[ 32s] [ 0.367346] i8042: No controller found
[ 32s] [ 0.369526] /home/abuild/rpmbuild/BUILD/kernel-xen-3.4.6/linux-3.4/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 32s] doing fast boot
[ 33s] FATAL: Module kqemu not found.
[ 33s] FATAL: Module ext2 not found.
[ 33s] Creating device nodes with udev
[ 34s] Waiting for device /dev/hda1 to appear: ok
[ 34s] fsck from util-linux 2.21.2
[ 34s] [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/hda1
[ 34s] /dev/hda1: clean, 3618/897600 files, 161407/3584000 blocks
[ 34s] fsck succeeded. Mounting root device read-only.
[ 34s] Mounting root /dev/hda1
[ 34s] mount -o ro,defaults -t ext4 /dev/hda1 /root
[ 1028s] ARCHITECTURE PERSONALITY IS UNKNOWN
Any idea why?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org