Hi,
What do you think about adding couple of test cases for ARM to our
openQA? I remember two cases when our JeOSes were broken independently
of hardware. First one, when u-boot was looking for boot.scr in wrong
place, second one, when the kernel 3.14 was broken due to bug in depmod.
So, I think that we could test JeOS-vexpress and JeOS-vexpress64 for
armv7 and aarch64 using qemu emulation (I know that it is slow ;) )
Then just check that the image is booted for the first time, and for the
second time, controlling the process through serial console.
At the moment I have no idea how many efforts are needed to implement this.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I'm trying to use
openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build36.2.raw.xz from
http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Raspbe…,
write to SD card with xzcat as described in HCL:Raspberry_Pi
Is this a working image file?
For me, the boot process hangs at "Loading kernel" (no progress after
several minutes)
Same hardware (including same SD card) boots raspian 2014-12-24 version
perfectly. FWIW it's an early model B (type 0002)
My image file (.raw.xz) has md5sum f61450a3eb30ff5419463d153271fe0c, but
I can't find an expected sum to compare with. Also, xzcat reports no
issues when copying to SD card.
If this image file is no good, can someone point me to the last good one?
Many thanks
Richard (MQ)
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi List,
While setting up my new rpi B+, I noticed that my eth0's MAC address
would change after each boot which was causing a new ip address to be
issued by my router after every boot.
I found this post roughly describing my issue:
http://www.raspberrypi.org/forums/viewtopic.php?p=90975
My /proc/cpuinfo shows my Revision as 0000 (instead of 0010) and my
Serial is also just 0s. Adding: program_serial_random=1 and
program_board_rev=2 to Config.txt didn't fix the issue.
Other raspberry pi distributions do show my Serial and Revision as
expected, and eth0's MAC address isn't random.
It appears that the command line doesn't get updated with the proper
bcm2708.boardrev and bcm2708.serial (and possibly smsc95xx.macaddr)
options.
I have built an upstream kernel (3.18.0 branch) and that doesn't seem to
help (I thought the default kernel may not be parsing the options). And
I even tried updating the boot firmware to the raspberrypi's next branch
with no impact.
I'm not too familiar with opensuse's rpi boot process, but it looks
fairly different from what I've seen on arch and raspbian (i.e. the vfat
partition is used to start the boot.scr on the ext4's /boot directory).
As this is my first rpi, I'm still trying to figure things out...
Is it possible that the kernel parameters are not being passed properly
when the kernel on the /boot/zImage is loaded?
Also, do the previous pi revisions work or is this new to the B+? Or
could this be an issue with the Factory port?
Thanks
--
Evan McClain
/* No Comment */
https://keybase.io/aeroevan
Hi,
I'm working on get openSUSE working with ODROID-C1 board. I prepared
u-boot and kernel in my repo:
https://build.opensuse.org/project/show/home:Fisiu:odroid-c1
Now I want to create new JeOS image with those packages but I'm quite
new in kiwi images creating... What should I add/edit in JeOS package
to build new image?
Can you share some info, point to some examples/howto?
--
Pozdrawiam / Best regards,
Mariusz Fik,
openSUSE Community Member
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi all,
I am trying to run the cubietruck JeOS image from
d.o.o://ports/armv7hl/factory/images/, but so far without success.
I have the image on a sd card, and put both partitions also on a
connected sata disk. As far as I can see the kernel starts, but
everything comes to a sudden stop where - I believe - the init/systemd
process should take over.
I also tried the 13.2 image, but that did not work either, for sure
because of the uboot version (mentioned here on the list earlier).
Is there any magic to perform? Can I help?
Thank you,
Stefan
--
Stefan Botter zu Hause
Bremen
Hello,
This weekend I got openSUSE Factory running on the HTC Nexus 9 tablet:
https://en.opensuse.org/HCL:Nexus9
My current setup is using a USB hub with flash stick, keyboard, mouse
and Ethernet, so is limited by battery runtime (and probably won't last
a full day at FOSDEM).
Our latest Nouveau X11 driver does not work with the Android kernel, but
fbdev works out of the box (e.g., IceWM).
Plasma5 complained about dbus, Xfce4 came up but hung.
Have a lot of fun,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (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, Raspi-friends.
I am installing the 13.2-version for the raspberry.
As a mostly operating in the text-mode, I am using a 7inch-monitor
connected to the FBAS-connector. In works but on the left sind, the
first 2 letters and on the bottom the last two lines are missing.
Using the Raspberry with the Debian-Squueze OS, I changed settings in
the /boot/boot.conf
file.
Who can I do it with the Raspi-OS13.2-version.
Thanks for your advice
Edgar, DJ3PU, Munich
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hallo, RasperryPi-friends.
I just have installed the OpenSuSe-13.2 on my raspi.
When trying to install the midnightcommander, the system says that there
in repos available.
Any advice would be appreciated
Best regards
Edgar, DJ3PU, from Munich
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I'm rookie in ARM world. I bought recently odroid-c1 board, but it
doesn't work with openSUSE yet. I'll try to make it happens (or fail
trying). I read so far, I need vendor u-boot and kernel. All sources
for those things are on gihub, so it should be quite simple. But...
I started with packaging u-boot. I tried to build it locally (openSUSE
13.2 x86_64 host) but I need some help here. How to setup osc to build
arm packages? This is what I've done so far:
Installed qemu-linux-user, kvm, qemu-kvm packages.
In ~/.oscrc build-type = qemu
According to wiki page[1] I should run osc with --alternative-project
switch, so I run:
osc build --alternative-project=openSUSE:Factory:ARM qemu armv7l
u-boot-odroid-c1.spec
But build with vm kernel crash:
WARNING: source service from package or project will not be executed.
This may not be the same build as on server!
Building u-boot-odroid-c1.spec for qemu/armv7l
Getting buildinfo from server and store to
/home/fisiu/Devel/obs/home:Fisiu:odroid-c1/u-boot-odroid-c1/.osc/_buildinfo-qemu-armv7l.xml
Getting buildconfig from server and store to
/home/fisiu/Devel/obs/home:Fisiu:odroid-c1/u-boot-odroid-c1/.osc/_buildconfig-qemu-armv7l
Updating cache of required packages
0.0% cache miss. 97/97 dependencies cached.
Verifying integrity of cached packages
using keys from openSUSE:Factory
Writing build configuration
Running build
VM_IMAGE: /var/tmp/build-root/img, VM_SWAP: /var/tmp/build-root/swap
mkswap /var/tmp/build-root/swap
mkswap: /var/tmp/build-root/swap: warning: wiping old swap signature.
Setting up swapspace version 1, size = 1048572 KiB
no label, UUID=108923a7-e64b-4487-8fb7-df36e147b003
logging output to /var/tmp/build-root/.build.log...
[ 0s] Using BUILD_ROOT=/var/tmp/build-root/.mount
[ 0s] Using BUILD_ARCH=armv7l:armv6l:armv5tel
[ 0s] Doing qemu build in /var/tmp/build-root/img
[ 0s]
[ 0s]
[ 0s] pendrak started "build u-boot-odroid-c1.spec" at Tue Jan 13
00:03:01 UTC 2015.
[ 0s]
[ 0s]
[ 0s] processing recipe
/home/fisiu/Devel/obs/home:Fisiu:odroid-c1/u-boot-odroid-c1/u-boot-odroid-c1.spec
...
[ 0s] running changelog2spec --target rpm --file
/home/fisiu/Devel/obs/home:Fisiu:odroid-c1/u-boot-odroid-c1/u-boot-odroid-c1.spec
[ 0s] init_buildsystem --configdir /usr/lib/build/configs
--cachedir /var/cache/build --prepare --rpmlist /tmp/rpmlist.FsoZyp
/home/fisiu/Devel/obs/home:Fisiu:odroid-c1/u-boot-odroid-c1/u-boot-odroid-c1.spec
...
[ 0s] copying packages...
[ 1s] reordering...cycle: libcrack2 -> cracklib
[ 1s] breaking dependency libcrack2 -> cracklib
[ 1s] done
[ 1s] /usr/lib/build/build-vm-qemu: line 22: vm_setup_kvm: command not found
[ 1s] booting qemu...
[ 1s] /usr/bin/qemu-kvm -no-reboot -nographic -vga none -net none
-kernel /boot/vmlinuz -initrd /boot/initrd -append root=/dev/sda
panic=1 quiet no-kvmclock nmi_watchdog=0 rw rd.driver.pre=binfmt_misc
elevator=noop console=ttyS0 init=/.build/initvm.x86_64 -drive
file=/var/tmp/build-root/img,if=none,id=disk,serial=0,cache=unsafe
-device ide-hd,drive=disk -drive
file=/var/tmp/build-root/swap,if=none,id=swap,serial=1,cache=unsafe
-device ide-hd,drive=swap -smp 2
[ 4s] [ 0.122139] Failed to access perfctr msr (MSR c1 is 0)
[ 6s] [ OK ] Started Show Plymouth Boot Screen.
[ 6s] [ OK ] Reached target Paths.
[ 6s] [ OK ] Reached target Basic System.
[ 6s] [ OK ] Found device QEMU_HARDDISK.
[ 6s] [ OK ] Started dracut initqueue hook.
[ 6s] [ OK ] Reached target Remote File Systems (Pre).
[ 6s] [ OK ] Reached target Remote File Systems.
[ 6s] Starting File System Check on /dev/sda...
[ 6s] [ OK ] Started File System Check on /dev/sda.
[ 6s] Mounting /sysroot...
[ 6s] [ OK ] Mounted /sysroot.
[ 6s] [ OK ] Reached target Initrd Root File System.
[ 6s] Starting Reload Configuration from the Real Root...
[ 7s] [ OK ] Started Reload Configuration from the Real Root.
[ 7s] [ OK ] Reached target Initrd File Systems.
[ 7s] [ OK ] Reached target Initrd Default Target.
[ 7s] [ 2.596209] Kernel panic - not syncing: Attempted to kill
init! exitcode=0x00000100
[ 7s] [ 2.596209]
[ 7s] [ 2.597593] CPU: 1 PID: 1 Comm: initvm.x86_64 Tainted: G
W 3.16.7-7-desktop #1
[ 7s] [ 2.597593] Hardwarname: QEMU Standard PC (i440FX + PIIX,
1996), BIOS rel-1.7.5-0-ge51488c-20141015_183547-build31 04/01/2014
[ 7s] [ 2.597593] ffff88000694bed8 ffffffff8161bd03
ffffffff81a1d340 ffffffff81616032
[ 7s] [ 2.597593] 0000000000000010 ffff88000694bee8
ffff88000694be88 ffffffff8113afe2
[ 7s] [ 2.597593] 0000000000000100 ffff880006944510
0000000000000015 0000000000000001
[ 7s] [ 2.597593] Call Trace:
[ 7s] [ 2.597593] [<ffffffff810051ee>] dump_trace+0x8e/0x350
[ 7s] [ 2.597593] [<ffffffff81005556>] show_stack_log_lvl+0xa6/0x190
[ 7s] [ 2.597593] [<ffffffff81006c51>] show_stack+0x21/0x50
[ 7s] [ 2.597593] [<ffffffff8161bd03>] dump_stack+0x49/0x6a
[ 7s] [ 2.597593] [<ffffffff81616032>] panic+0xc8/0x1fc
[ 7s] [ 2.597593] [<ffffffff8105f76e>] do_exit+0xa8e/0xa90
[ 7s] [ 2.597593] [<ffffffff8105f7e9>] do_group_exit+0x39/0xa0
[ 7s] [ 2.597593] [<ffffffff8105f860>] SyS_exit_group+0x10/0x10
[ 7s] [ 2.597593] [<ffffffff81622a2d>] system_call_fastpath+0x1a/0x1f
[ 7s] [ 2.597593] [<0000000000432699>] 0x432698
[ 7s] [ 2.597593] Kernel Offset: 0x0 from 0xffffffff81000000
(relocation range: 0xffffffff80000000-0xffffffff9fffffff)
[ 8s] [ 2.597593] Rebooting in 1 seconds..No buildstatus set,
either the base system is broken (glibc/bash/perl)
[ 8s] or the build host has a kernel or hardware problem...
The buildroot was: /var/tmp/build-root/.mount
Could You help me with cross compilation using osc?
[1] - https://en.opensuse.org/openSUSE:ARM_distribution_howto
--
Pozdrawiam / Best regards,
Mariusz Fik,
openSUSE Community Member
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org