- openSUSE ARM

[opensuse-arm] openQA: ARM
by Matwey V. Kornilov 24 Feb '15

24 Feb '15

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

10 30

[opensuse-arm] kiwi v7.02 failed
by Matwey V. Kornilov 23 Feb '15

23 Feb '15

Hi, kiwi 7.02 is failed to Factory:ARM: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/kiwi… -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] Error message after installation of kernel-firmware
by Freek de Kruijf 22 Feb '15

22 Feb '15

Hi all, I got the following error message after the update of firmware-kernel in openSUSE 13.2 for Raspberry Pi. Warning: kernel-firmware-20141122git-5.1.noarch.rpm %posttrans script failed (returned 1) Bug report? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] WiFi does not come up on Raspberry Pi B
by Freek de Kruijf 21 Feb '15

21 Feb '15

I have a Raspberry PI B with openSUSE 13.2 (JeOS) which has two USB interfaces, a Bluetooth and WiFi (Realtek RTL8192cu). It worked OK during installation at home, but at its destination the WiFi connection does not come up. I can do "iwlist wlan0 scan" and I get the list of Access Points it the neighborhood. The device is configured with wicket. For access I use the Ethernet port (it works headless). I have the same system on another device, same software, same type of devices, same network configuration and that one works as expected. I can bring the interface down with "ifdown wlan0" and up again with "ifup wlan0 -o debug" and the last lines of the output are: wicked: waiting for 1 devices to become ready (1 explicitly requested) wicked: wlan0: state=firewall-up want=network-up, wait-for=link-up wicked: waiting for 1 devices to become ready (1 explicitly requested) wicked: wlan0: state=firewall-up want=network-up, wait-for=link-up wicked: waiting for 1 devices to become ready (1 explicitly requested) wicked: device wlan0 failed: operation timed out wicked: waiting for 0 devices to become ready (0 explicitly requested) wicked: finished with all devices. wicked: wlan0: changed state none -> device-exists, still waiting for event wlan0 setup-in-progress wicked: Exit with status: 162 On the device that does work, instead of the timeout I get: wicked: ... great, we were expecting this event wicked: wlan0: changed state firewall-up -> link-up, resuming activity wicked: wlan0: state=link-up want=network-up, trying to transition to link- authenticated wicked: wlan0: changed state link-up -> link-authenticated wicked: wlan0: successfully transitioned from link-up to link-authenticated wicked: wlan0: state=link-authenticated want=network-up, trying to transition to lldp-up wicked: wlan0: calling org.opensuse.Network.LLDP.lldpUp() wicked: wlan0: changed state link-authenticated -> lldp-up wicked: wlan0: successfully transitioned from link-authenticated to lldp-up wicked: wlan0: state=lldp-up want=network-up, trying to transition to network- up wicked: wlan0: calling org.opensuse.Network.Addrconf.ipv4.static.requestLease() wicked: wlan0: changed state lldp-up -> network-up wicked: wlan0: cancel timeout wicked: wlan0: successfully transitioned from lldp-up to network-up wicked: waiting for 0 devices to become ready (0 explicitly requested) wicked: finished with all devices. wicked: wlan0: tentative addresses check wlan0 up wicked: Exit with status: 0 I found on the Internet problems with the power drawn via the USB ports. But it that case the WiFi connection got established, but was unstable. The same device with the same interfaces and the same power supply worked for almost 9 month without any problem with openSUSE 13.1. Because the SD card broke down I had to reconfigure the software. I have a similar device doing the same thing, with the same type of devices and also with openSUSE 13.2 working OK. Any suggestions? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] Please accept SR #286292 for JeOS
by Guillaume Gardet 20 Feb '15

20 Feb '15

Hi, could you please accept my SR #286292 to update JeOS. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Kernel testing at Linaro
by Andrew Wafaa 19 Feb '15

19 Feb '15

Hi, Could someone confirm that it is OK to forward our aarch64 config to Linaro for them to integrate into the kernelci loop? Currently kernelci.org only tests defconfigs which are rather minimal. Also can someone confirm what the stance is on page sizes? Will openSUSE support both 4K and 64K page sizes or just focus on one? Thanks, Andy -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] openSUSE 13.2 on the Acer Chromebook 13 CB5-311-T6R7 (nyan-big)
by Simon Gleissner 19 Feb '15

19 Feb '15

Hello, currently I try to install openSUSE 13.2 for armv7hl on my Acer Chromebook 13 CB5-311-T6R7 (nyan-big, 4 GB, FullHD-display). It is working, but there are some problems. For those who are interested, I have used the approach described here: https://github.com/lgeek/gnu-linux-on-acer-chromebook-13 The kernel is quite old and WLAN is not working, but the rest seems to be stable enough. I use XFCE and can compile, sign and install the kernel natively on the Chromebook. However, I am not happy with the missing WLAN, so I have tried to exchange the Chromeos-based kernel 3.10.18 against a vanilla 3.18.5 kernel, which has support for the tegra124/nyan-big plattform. This kernel does not work at all (just a black screen), so my question is: Does anyone have an approach for compile a working kernel with WLAN, e.g. a working .config file? Greetings, Simon -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] How to .tbz files in ARM factory?
by Freek de Kruijf 19 Feb '15

19 Feb '15

Hi All, In ARM factory http://download.opensuse.org/ports/armv6hl/factory/images/ I see a E17 version with extension raw.xz and I assume this one can be used as described in https://en.opensuse.org/HCL:Raspberry_Pi. However I am interested in the JeOS version which is only available as .tbz. How do use this .tbz version? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] OpenSusee-version 13.2 JeOS: Boot-Fragen
by Edgar Dombrowski 18 Feb '15

18 Feb '15

Hi, Rasperry-friends. I am actually playing around with the Build-Version 32,1. When booting I am getting the following error messages: 1. Just at the start: > reading ./uEnv.txt > unable to read file ./uEnv.txt missing ** 2. At the end of the boot process: > unable to start X-Display Manager How shall I proceed to solve these problems. Thanks to all of you 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

3 2

[opensuse-arm] Wrong type of connection between Rasberry Pi and Zyxel P-2812HNU-F1?
by Freek de Kruijf 17 Feb '15

17 Feb '15

Hi all, I am having problems with the wired connection, UTP, between the Rasberry Pi and the Zyxel router P-2812HNU-F1. Quite often after connecting the Raspberry Pi with openSUSE 13.2, the 5 indicator lights on the RPi should come up. However only PWR is on and there is no connection between the RPi and the Zyxel. After a power down/up of the Zyxel the normal connection comes up. I assume that the handshaking of the Ethernet connection goes wrong. The Zyxel should assume the master role and the RPi the slave role and apparently this goes wrong. Is there another way to establish a proper connection? Is there a command to make the Ethernet interface in the RPi the slave and to start a new negotiation? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Why is packet e2fsprogs not present in Rasberry Pi image?
by Freek de Kruijf 17 Feb '15

17 Feb '15

Hi all, Reading through the dmesg output on my Raspberry Pi I found an error message about missing programs fsck.ext3 and fsck.ext4, which I found in package e2fsprogs. This package is missing in the Raspberry Pi image. Shouldn't it be included? Bug report? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] UIM package
by Andrew Wafaa 17 Feb '15

17 Feb '15

Does anyone know if we havea package for UIM - User Mode Init Manager for TI shared transport? I've looked on OBS and can't see one, but I may be missing something. This is needed for the Hikey from 96Boards. Linaro have a couple of patches and have also added a systemd service file and udev rule for uim. Thanks, Andy -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 6

[opensuse-arm] Boot camp Raspberry Pi 2 - 21FEB
by Jimmy PIERRE 17 Feb '15

17 Feb '15

Hi Guys! I have this problem, I am having a boot camp on Raspberry Pi 2 next Saturday, *but* the process of installing openSUSE ARM might jeopardize all efforts. I see that Debian, Feudora, openelec, Ubuntu, xbmc Risc OS have a simple installation... Give me some thoughts please... Best, Jimmy Pierre Twitter handle : @jpierre76 #openSUSE #suse #Raspberry PI #libreoffice #jmll.fr #nui.fr #Rouen http://www.agendadulibre.org/events/9116 #nui.fr #interopérabilité -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Raspberry Pi version 2
by Bill Merriam 14 Feb '15

14 Feb '15

I imagine everyone is aware that a quad-core, ARMv7 version of the RPi is available. Does anybody know what is involved in using Opensuse on that device? I am hoping that I can use the normal ARMv7 repository for everything but the RPi specific packages. Should I branch those RPi packages and try building them for V7 or is someone already doing that? Thanks. Bill -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

[opensuse-arm] Latest Raspi JeOS image
by Richard (MQ) 13 Feb '15

13 Feb '15

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

9 20

[opensuse-arm] Raspberry Pi B+, No Revision or Serial?
by Evan McClain 11 Feb '15

11 Feb '15

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

2 1

[opensuse-arm] Graphic Terminal
by Edgar Dombrowski 10 Feb '15

10 Feb '15

Hi, Raspberry Friends and Supporters. I finally got the Build-Version36.2 installed with the help of the HCL-homepage. However I find some problems, which I will notify to you for any assistance, Problems will be detailed in separate mailings. Question 1: I would like to use the graphic mode by starting "startx" using an HDMI-Monitor. However the answer is: startx not found. How can I solve the problem. Thanks for your help. Regards 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

2 1

[opensuse-arm] kwrite and kate packages missing for openSUSE 13.2 armv7hl
by Simon Gleissner 03 Feb '15

03 Feb '15

Hello, I have tried to install KDE and KDevelop for openSUSE 13.2 armv7hl, but the depending packages kate and kwrite are not included in the repository. I have used http://download.opensuse.org/ports/armv7hl/distribution/13.2/repo/oss/suse/… . According to https://build.opensuse.org/project/show/openSUSE:13.2 , the armv7l build for kate is 'unresolvable', but kwrite is neither listed at 'succeded', nor anywhere else. Any chance that this might change? Greetings, Simon -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Create new JeOS image
by Mariusz Fik 30 Jan '15

30 Jan '15

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

3 2

[opensuse-arm] ports image on cubietruck - no luck so far
by Stefan Botter 27 Jan '15

27 Jan '15

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

3 6

[opensuse-arm] Nexus 9 aarch64 how-to
by Andreas Färber 27 Jan '15

27 Jan '15

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

3 2

[opensuse-arm] Fwd: Build failure of devel:ARM:Factory:Contrib:RaspberryPi/raspberrypi-userland in standard/armv6l
by Andreas Färber 26 Jan '15

26 Jan '15

Hi Guillaume et al., Could someone who cares about the proprietary userland stuff please investigate and fix this recurring build error? Thanks, Andreas -------- Weitergeleitete Nachricht -------- Betreff: Build failure of devel:ARM:Factory:Contrib:RaspberryPi/raspberrypi-userland in standard/armv6l Datum: Mon, 26 Jan 2015 00:11:07 +0100 Von: OBS Notification <obs-email(a)opensuse.org> An: afaerber(a)suse.de Visit https://build.opensuse.org/package/live_build_log/devel:ARM:Factory:Contrib… Package devel:ARM:Factory:Contrib:RaspberryPi/raspberrypi-userland failed to build in standard/armv6l Check out the package for editing: osc checkout devel:ARM:Factory:Contrib:RaspberryPi raspberrypi-userland Last lines of build log: [ 1109s] [ 67%] Built target mmal_components [ 1110s] [ 67%] Built target mmal [ 1110s] [ 67%] Built target debug_sym [ 1111s] Linking C executable ../../../../../bin/mmal_vc_diag [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_list_create' [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_list_push_back' [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_list_insert' [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_list_pop_front' [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_rational_equal' [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_list_push_front' [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_list_destroy' [ 1112s] ../../../../../lib/libmmal_core.so: undefined reference to `mmal_rational_to_fixed_16_16' [ 1112s] collect2: error: ld returned 1 exit status [ 1112s] interface/mmal/vc/CMakeFiles/mmal_vc_diag.dir/build.make:94: recipe for target '../../bin/mmal_vc_diag' failed [ 1112s] make[2]: *** [../../bin/mmal_vc_diag] Error 1 [ 1112s] CMakeFiles/Makefile2:1024: recipe for target 'interface/mmal/vc/CMakeFiles/mmal_vc_diag.dir/all' failed [ 1112s] make[1]: *** [interface/mmal/vc/CMakeFiles/mmal_vc_diag.dir/all] Error 2 [ 1112s] Makefile:137: recipe for target 'all' failed [ 1112s] make: *** [all] Error 2 [ 1112s] error: Bad exit status from /var/tmp/rpm-tmp.rz3fnC (%install) [ 1112s] [ 1112s] [ 1112s] RPM build errors: [ 1112s] line 110: second %files [ 1112s] Bad exit status from /var/tmp/rpm-tmp.rz3fnC (%install) [ 1112s] ### WATCHDOG MARKER START ### [ 1115s] [ 1105.570479] SysRq : Power Off [ 1115s] [ 1105.576394] reboot: Power down [ 1116s] ### WATCHDOG MARKER END ### -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/) -- 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

2 1

[opensuse-arm] Raspi-OS 13.2: with FBAS connection
by Edgar Dombrowski 16 Jan '15

16 Jan '15

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

3 3

[opensuse-arm] Midnight-Commander
by Edgar Dombrowski 14 Jan '15

14 Jan '15

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

2 1

[opensuse-arm] Build armv7l rpm on x86_64 host
by Mariusz Fik 13 Jan '15

13 Jan '15

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

4 7

[opensuse-arm] OS13.1: Raspi started den Grafik Modus nicht
by Edgar Dombrowski 13 Jan '15

13 Jan '15

Hallo, Rasberry-Friends. With assistance of some of you finally succeded to install the OpenSUSE-13.1-ARM-JeOS.... version as discribed in HCL:Rasperry Pi-Document. I have although installed the YAST2-files as listed in the above mentioned file. However when trying to go to the graphic window by calling "startx" nothing happens. What is wrong? Thank you for your help Regards 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

2 2

[opensuse-arm] Speed up devel:libraries:c_c++ armv7 building
by Oscar C 02 Jan '15

02 Jan '15

Hi, I couple of armv7 packages that depends on libraries on devel:libraries:c_c++ are blocked because package building is progressing very slowly. Almost 48 hours later and only 25 of 187 packages have been built so far. aarch64 had all of the packages built in less than 24 hours. What can be done to speed it up? Thanks! -- Cheers -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] raw.xy-File
by Edgar Dombrowski 26 Dec '14

26 Dec '14

OS for Raspbi-Pi Hi Raspi-Friends. Thanks first to Alex and others for telling me not to use the Build.tbz-Version but the xx.raw.xy-file in the same directory. But - sorry - how to extract the raw-file? Thank you for your assistance Edgar, DJ3PU -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] OS für Raspi
by Edgar Dombrowski 21 Dec '14

21 Dec '14

Hallo, Raspi-Friends Some friends have instructed me to download the latest version for the Raspi.. > openSUSE-Factory-ARM -XFCE....Build252.tar,tbz But I was unable, to unpack the basic file for putting it on a sd-stick. With "tar -tjf name" I am getting the ist of included packages, but with "tar -xfj name" I getting error messages. Any advice would be welcomed. Merry Xmas and happy New Year 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

3 2

[opensuse-arm] CX-919 RK3188
by medwinz 19 Dec '14

19 Dec '14

Hi, I got a CX-919 RK3188 with android 4.2 [1] I'm a newbie for this arm thing and want to boot this mini pc using microsd card. While I'm succeed to boot this mini pc with ubuntu image from linuxium [2] [3], I failed to boot it with image from openSUSE arm image from [4]. I try several xfce rootfs and JeOS rootfs image from 12.3 to 13.2 but nothing succeed. I read on the net that someone success with rk3188 but no luck for me after following the instruction on his blog [5]. Can someone point me to the right direction? Should I make a new image with the new kernel-arm and follow the instruction on openSUSE wiki [6]? Is there any instruction for a newbie? Any help would be much appreciate. [1] http://www.amazon.com/CX-919-RK3188-Bluetooth-Android-Google/dp/B00CRTCTVA [2] https://sites.google.com/site/ianwmorrison/Downhome/Topic2 [3] https://drive.google.com/file/d/0B99O3A0dDe67NmIyLTl4Z3ZFRmc [4] http://download.opensuse.org/ports/armv7hl/distribution [5] http://hwswbits.blogspot.com/2013_12_01_archive.html [6] https://en.opensuse.org/openSUSE:OpenSUSE_on_your_ARM_board regards, -- medwinz http://about.me/medwinz -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] BananaPi
by Matwey V. Kornilov 18 Dec '14

18 Dec '14

Hi, Does anyone have experience with openSUSE on Banana Pi. I think to buy this one as home router: http://aliexpress.com/store/product/Freeshipment-Newest-arrive-Banana-PI-BP… -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Disabling frameworks that are known to fail
by Andrew Wafaa 18 Dec '14

18 Dec '14

Hi, Looking at the current failures/unresolvables for AArch64, I notice that a large chink of these are language frameworks that are known not to have been ported yet to the architecture. In the interest of seeing the wood for the trees, is it worth disabling those known not to work? Ones I'm thinking of are Mono, Go, Haskell (ghc), NodeJS. By disabling these it will make it much easier to see the outstanding packages that need work. Regards, Andy -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] WHICH IMAGE?
by Edgar Dombrowski 18 Dec '14

18 Dec '14

Hi, RaspiFriends- I am lost. I have looked into http://download.opensuse.org/ports/armv6hl/factory/repo/oss/ , but I can not find the Starter-Image which has to be copied on a SD-card. I would appreciate any advice, beeing an OpenSuSefan since 4.2. Thanks 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

3 3

[opensuse-arm] Which repo for rasperry pi
by Michael Ströder 17 Dec '14

17 Dec '14

HI! Frankly I'm lost in all the ARM-related repo URLs... Currently I'm using on my rasperry pi: http://download.opensuse.org/ports/armv6hl/factory/repo/oss/ Does this repo receive all the openSUSE updates? Or is there an openSUSE 13.2 repo available for rasperry pi? Ciao, Michael.

4 7

Re: [opensuse-arm] Chromebook factory image problems
by Misha Komarovsky 13 Dec '14

13 Dec '14

Hello, I think cgpt repair is crucial part, after i added it right to dd_snow.sh i was able to boot hand crafted u-boot. I can now confirm black screen right after kernel start, it look like same behaviour i have with paz00, after waiting for couple minutes xorg started with garbled screen, this is probably because drm/lcd modules not injected to initrd by dracut (only guess yet, based on this patch series https://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=49fe860b22afd… ) Switching to console vty not working, because no logind services started, noticed by killing xorg with double ctrl+alt+backspace. On Fri, Dec 12, 2014 at 12:41 PM, Guillaume Gardet <guillaume.gardet(a)free.fr> wrote: > Forgot to say something on the repair part. You should make a cgpt repair > (sudo cgpt repair /dev/sdX) but then, you must run dd_snow.sh again. > > > Guillaume > > > > Le 12/12/2014 10:24, Misha Komarovsky a écrit : > > Hello, > I compiled myself rc3 from your update to base:system u-boot and doing all > steps from script pointing to correct device. Already double checked couple > times, but maybe still something will try to create partition myself from > scratch. > > On Dec 12, 2014 11:39 AM, "Guillaume Gardet" <guillaume.gardet(a)free.fr> > wrote: >> >> Hi, >> >> The image I gave you is a patched -rc2. So, you will get -rc2 as u-boot >> version. ;) >> >> Did you edit dd_snow.sh script to point to your device ? Check if there is >> no remaining /dev/sdX1 file when your USB stick is unplugged. >> >> U-boot is loaded from 1st partition (as raw image), where the script >> should copy it. >> >> I updated u-boot in Base:System but I am waiting for Dirk to update some >> packages (I have no admin rights in Base:System project) before pushing it >> to Factory. :( >> >> >> Guillaume >> >> >> >> >> Le 12/12/2014 01:47, Misha Komarovsky a écrit : >>> >>> Hello Guillaume, >>> I cant understand where u-boot now lives in snow images. >>> I tried dd_snow.sh script, it asks for run cgpt repair first on fresh >>> created usb stick but no luck, u-boot version still same on start. >>> Filled first partition of usb stick with /dev/zero, still same u-boot >>> 2015.01-rc2, mystic. >>> Got crazy idea maybe it is loaded from lxroot/boot/u-boot.img, >>> replaced it with custom binary, no luck still 2015.01-rc2. >>> Tried deleting gpt partitions one by one and only after partition 1 >>> deleted, it stops to work, but whole partition filled >>> with zeros. >>> >>> On Sun, Dec 7, 2014 at 5:55 PM, Guillaume Gardet >>> <guillaume.gardet(a)free.fr> wrote: >>>> >>>> new_kern is built using vbutil_kernel command. So, you need the vboot >>>> package to be installed: >>>> http://software.opensuse.org/package/vboot?search_term=vboot >>>> >>>> >>>> Guillaume >>>> >>>> >>>> Le 07/12/2014 15:43, Misha Komarovsky a écrit : >>>>> >>>>> dd_snow.sh script need also /tmp/newkern is it symlink to u-boot.img >>>>> or real new kernel? >>>>> >>>>> >>>>> On Sun, Dec 7, 2014 at 4:21 PM, Guillaume Gardet >>>>> <guillaume.gardet(a)free.fr> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Le 06/12/2014 22:19, Misha Komarovsky a écrit : >>>>>>> >>>>>>> Hello, >>>>>>> Just tried to book chromebook images version 253. >>>>>>> Usb wont boot sayin no kernel found, maybe so trick is required? >>>>>> >>>>>> >>>>>> You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be >>>>>> out >>>>>> in 2 or 3 days) to push my changes because there are lots of problem >>>>>> with >>>>>> -rc2. >>>>>> If you want to test now, please use this u-boot (based on a modified >>>>>> GIT >>>>>> version): >>>>>> http://guillaume.gardet.free.fr/openSUSE/u-boot.img >>>>>> >>>>>> Then, copy it to your USB stick with this script (update path to >>>>>> u-boot.img >>>>>> and fix your device: /dev/sdX): >>>>>> http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh >>>>>> >>>>>> >>>>>> SD card booting is not working ATM, so please boot from USB (black >>>>>> USB2 >>>>>> slot, not blue USB3 slot). >>>>>> >>>>>> JeOS is working fine. X11 images are broken (strange display once Xorg >>>>>> is >>>>>> booted, only the cursor is ok.) >>>>>> >>>>>> >>>>>> Guillaume >>>>>> >>>>>> >>>>>>> VbTryLoadKernel() start, get_info_flags=0x1 >>>>>>> USB: Register 1313 NbrPorts 3 >>>>>>> USB EHCI 1.00 >>>>>>> 2 USB Device(s) found >>>>>>> USB: Register 1313 NbrPorts 3 >>>>>>> USB EHCI 1.00 >>>>>>> 2 USB Device(s) found >>>>>>> scanning bus for storage devices... 1 Storage Device(s) >>>>>>> found >>>>>>> MMC: no card present >>>>>>> mmc_init err -16, time 1986 >>>>>>> boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail >>>>>>> MMC Device 4 not found >>>>>>> VbTryLoadKernel() found 0 disks >>>>>>> VbSetRecoveryRequest(90) >>>>>>> VbBootDeveloper() - no kernel found on USB >>>>>>> utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. >>>>>>> VbSetRecoveryRequest(0) >>>>>>> leaving VbDisplayScreenFromGBB() with 0 >>>>>>> VbBootDeveloper() - trying fixed disk >>>>>>> >>>>>>> >>>>>>> >From SD i can reach u-boot, it said unknow partition for mmc dev 1 >>>>>>> and >>>>>>> detect capacity is wrong. >>>>>>> >>>>>>> snow # mmc dev 1 >>>>>>> dwmci_send_cmd: DATA ERROR! >>>>>>> dwmci_send_cmd: DATA ERROR! >>>>>>> switch to partitions #0, OK >>>>>>> mmc1 is current device >>>>>>> snow # mmc info >>>>>>> Device: EXYNOS DWMMC >>>>>>> Manufacturer ID: 3 >>>>>>> OEM: 5344 >>>>>>> Name: SL08G >>>>>>> Tran Speed: 50000000 >>>>>>> Rd Block Len: 512 >>>>>>> SD version 3.0 >>>>>>> High Capacity: Yes >>>>>>> Capacity: w.4 GiB >>>>>>> Bus Width: 4-bit >>>>>>> snow # mmc part >>>>>>> ## Unknown partition table >>>>>>> snow # >>>>>>> >>>>>>> If i try to use SD card and USB stick at same time, mainline u-boot >>>>>>> start only XHCI hub and wont detect any storage devices here: >>>>>>> >>>>>>> U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow >>>>>>> >>>>>>> CPU: Exynos5250@1700MHz >>>>>>> Board: Google Snow >>>>>>> I2C: ready >>>>>>> DRAM: 2 GiB >>>>>>> trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 >>>>>>> trace: enabled >>>>>>> Board PMIC init >>>>>>> TPS>5090 PMIC init >>>>>>> MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 >>>>>>> SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl >>>>>>> total >>>>>>> 4 >>>>>>> MiB >>>>>>> *** Warning - bad CRC, using default environment >>>>>>> >>>>>>> Exynos DP init done >>>>>>> RKɽ͵ec-keyb >>>>>>> _ut: lcd >>>>>>> Err: lcd >>>>>>> Net: No ethernet found. >>>>>>> Hit any key`to stop autoboot: 0 >>>>>>> mmc - MMC sub system >>>>>>> >>>>>>> Usage: >>>>>>> mmc info - display info of the current MMC device >>>>>>> mmc read addr blk# cnt >>>>>>> mmc write addr blk# cnt >>>>>>> mmc erase blk# cnt >>>>>>> mmc rescan >>>>>>> mmc part - lists available partition on current mmc device >>>>>>> mmc dev [dev] [part] - show or set current mmc device [partition] >>>>>>> mmc list - lists available devices >>>>>>> mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode >>>>>>> - Set the BOOT_BUS_WIDTH field of the specified device >>>>>>> mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> >>>>>>> - Change sizes of boot and RPMB partitions of specifiel device >>>>>>> mmc partconf dev boot_ack boot_partition partition_access >>>>>>> - Change the bits of the PARTITION_CONFIG field of the specified >>>>>>> device >>>>>>> mmc rst-function dev value >>>>>>> - Change the RST_n_FUNCTION field of the specified device >>>>>>> WARNING: This is a write-once field and 0 / 1 / 2 are the only >>>>>>> valid >>>>>>> values. >>>>>>> mmc setdsr <value> - set DWR register value >>>>>>> >>>>>>> snow # usb storage >>>>>>> USB is stoppel. Please issue 'usb start' first. >>>>>>> snow # usb start >>>>>>> (Re)start USB... >>>>>>> USB0: Register 2000140 NbrPorts 2 >>>>>>> Starting the controller >>>>>>> USB XHCI 1.00 >>>>>>> scanning bus 0 for devices... 1 USB Device(s) found >>>>>>> scanning usb for storage devices... 0 Storage Device(s) >>>>>>> found >>>>>>> snow # usb storage >>>>>>> No storage devices, perhaps not 'usb start'ed..? >>>>>>> snow # >>>>>>> >>>>>>> On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet >>>>>>> <guillaume.gardet(a)free.fr> wrote: >>>>>>>> >>>>>>>> Le 02/12/2014 13:57, Guillaume Gardet a écrit : >>>>>>>>> >>>>>>>>> Le 02/12/2014 00:34, Alexander Graf a écrit : >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 02.12.14 00:19, Misha Komarovsky wrote: >>>>>>>>>>> >>>>>>>>>>> Hello, >>>>>>>>>>> I found that kernel or dtb file in current Chromebook contrib >>>>>>>>>>> factory >>>>>>>>>>> image, tested on version 245, have boot problems. After kernel >>>>>>>>>>> start >>>>>>>>>>> no signs of activity on stdout or serial console. >>>>>>>>>>> >>>>>>>>>>> If i replace linux.vmx and dtb on lxboot partition and modules on >>>>>>>>>>> lxroot with same files from 12.3 dist image for chromebook im >>>>>>>>>>> able >>>>>>>>>>> to >>>>>>>>>>> boot and pass installation fine. >>>>>>>>>>> >>>>>>>>>>> Also after installation and reboot, sd card not bootable at all, >>>>>>>>>>> first >>>>>>>>>>> partition on sdcard changed type code to 0700 and size to 32mb, >>>>>>>>>>> probably cgpt script failed to fix it after installation for some >>>>>>>>>>> reason. >>>>>>>>>>> >>>>>>>>>>> Bundled armsoc x11 driver fail to start because it is for abi 13 >>>>>>>>>>> not >>>>>>>>>>> abi >>>>>>>>>>> 18. >>>>>>>> >>>>>>>> >>>>>>>> I updated armsoc driver just now from 0.0.1 to 1.1.0. It may help. >>>>>>>> :) >>>>>>>> >>>>>>>>>> That does indeed sound pretty broken. I think someone needs to sit >>>>>>>>>> down >>>>>>>>>> and check which of all those components is already done well >>>>>>>>>> enough >>>>>>>>>> upstream to drop our hacks. >>>>>>>>>> >>>>>>>>>> For example, I think u-boot has upstream snow support now, so we >>>>>>>>>> could >>>>>>>>>> just use that. The kernel should be ok as well. >>>>>>>>> >>>>>>>>> >>>>>>>>> Current Factory u-boot-snow (2015.01-rc2) does boot but is not >>>>>>>>> really >>>>>>>>> usable. It seems there is a problem to access SD card. But LCD and >>>>>>>>> keyboard >>>>>>>>> are working fine. :) >>>>>>>>> >>>>>>>>> I will have a look at it. >>>>>>>> >>>>>>>> >>>>>>>> With some patches, I am able to use a USB stick (no external SD) >>>>>>>> with >>>>>>>> upstream u-boot-snow and Factory kernel-lpae does boot ! >>>>>>>> On kernel start, you must wait a little bit because at the >>>>>>>> beginning, >>>>>>>> there >>>>>>>> is just a black screen, followed later by a normal screen and a blue >>>>>>>> YaST >>>>>>>> Firstboot screen. :) >>>>>>>> >>>>>>>> But the are some problems: >>>>>>>> * upstream u-boot does not handle external SD card for an unknown >>>>>>>> reason >>>>>>>> (internal eMMC is usable). Downstream u-boot has no bootz support. >>>>>>>> * keyboard does not work under Linux (you must use an USB keyboard). >>>>>>>> * Second boot is deeply broken. U-Boot is not launched at all >>>>>>>> because >>>>>>>> "cgpt" >>>>>>>> command is applied to /dev/mmcblk0 (internal eMMC) instead of >>>>>>>> /dev/sda >>>>>>>> (USB >>>>>>>> stick) (Kiwi bug?). Once this one manually fixed, u-boot load the >>>>>>>> kernel >>>>>>>> and >>>>>>>> then hang with a black screen. Probably due to missing modules in >>>>>>>> dracut >>>>>>>> initrd. (I will submit a JeOS update once tested) >>>>>>>> * No wifi (at least on 1st boot) >>>>>>>> >>>>>>>> I will send an update (and SR) once tests are passed. >>>>>>>> >>>>>>>> >>>>>>>> Guillaume >>>>>>>> >>>>> >>> >>> >> > -- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

[opensuse-arm] Chromebook factory image problems
by Misha Komarovsky 12 Dec '14

12 Dec '14

Hello, I found that kernel or dtb file in current Chromebook contrib factory image, tested on version 245, have boot problems. After kernel start no signs of activity on stdout or serial console. If i replace linux.vmx and dtb on lxboot partition and modules on lxroot with same files from 12.3 dist image for chromebook im able to boot and pass installation fine. Also after installation and reboot, sd card not bootable at all, first partition on sdcard changed type code to 0700 and size to 32mb, probably cgpt script failed to fix it after installation for some reason. Bundled armsoc x11 driver fail to start because it is for abi 13 not abi 18. -- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 10

[opensuse-arm] libisl missing
by Michael Ströder 11 Dec '14

11 Dec '14

HI! It seems something broke in openSUSE_Factory_ARM during the last hour. My builds are marked unresolvable with this message: nothing provides libisl.so.10 needed by gcc48, nothing provides libisl.so.10 needed by libcloog-isl4, nothing provides libisl.so.10 needed by cpp48 Ciao, Michael.

3 5

[opensuse-arm] New version clamav for Raspberry Pi
by Freek de Kruijf 09 Dec '14

09 Dec '14

openSUSE 13.2 has an updated version for clamav. I don't see that version yet in the repositories for the Raspberry Pi. Is there anything I can do to fix that? Should this new version end up the oss repository or in update? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 5

[opensuse-arm] Hello
by Thatsanawan 06 Dec '14

06 Dec '14

Dearest, I am Miss.Thatsanawan Thiansanat,the daughter of Mr.Anuwat Thiansanat former personal adviser to Mr.Sondhi Limthongkul he work under an exiled but still-popular former Prime Minister Thaksin Shinawatra who was ousted in military coup that resulted in the overthrow of the Thai Rak Thai government in September 2006 and I am writing to you regarding a legitimate business proposition/deal in my control which will be executed under a legitimate arrangement. I am writing for the investment of the money left to me by my father,thus I am impelled to request for your assistance to receive this money since I am under surveillance from the authorities herein.Copy and paste below link on your browser for your perusal and better understanding to my email.LINK: http://www.th4u.com/sondhi_limthongkul.htm Very sorry if my mail is against your moral ethics and try to read with understanding and if you find it interested in partnering with me on this project,should write back to me,I shall give you full detail of the money Note:I am contacting you independently and this is absolutely confidential. If you accept this offer, I will appreciate your timely response. Yours Sincerely. Miss.Thatsanawan Thiansanat. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Kernel-default for 13.2
by Oscar C 05 Dec '14

05 Dec '14

Hi, Does anyone know where can I get the kernel of the 13.2 version? I though I would it find in here http://download.opensuse.org/repositories/openSUSE:/13.2/ports but the repository is not published. :( Thanks, -- Cheers -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] Re: [opensuse-factory] Wanted: Correct power-switch for ARM based Chromebook
by Dr. Werner Fink 04 Dec '14

04 Dec '14

Hi, just to be noted, that is not required to boot with openSUSE. Any nmodern Linux is enough, that is that there should be is the /sys file system and the filled /dev/input/ directory. I'd like to know the output of for n in /dev/input/event*; do udevadm info -a --name=$n done then we might catch the input device for gpio-keys.8 and the power switch therein. Werner > Le 01/10/2014 14:35, Andreas Färber a écrit : > > Hi, > Let's CC opensuse-arm for such ARM questions... > Am 30.09.2014 um 09:29 schrieb Dr. Werner Fink: > > Hi, > > just to be noted that the patch > > rules-add-lid-switch-of-ARM-based-Chromebook-as-a-power-sw.patch > > which includes the line > > SUBSYSTEM=="input", KERNEL=="event*", KERNELS=="gpio-keys.8", > > TAG+="power-switch" > > in the 70-power-switch.rules can not be fully corect. This because the > > "gpio-keys.8" > > is much to general and may cause trouble with other keyboard layouts. > > Therefore I'd like to see the output of such a Chromebook of the command: > > udevadm info -a /dev/input/by-path/*kbd > > which may give the more specific name of the power button. > > > > Werner > > Alex? Guillaume? Can any of you provide the requested information for > the Samsung Chromebook? > > From Chrome OS (kernel 3.8.11), "udevadm info -a > --name=/dev/input/by-path/*kbd" returns: > ********************************************************************** > Udevadm info starts with the device specified by the devpath and then > walks up the chain of parent devices. It prints for every device > found, all possible attributes in the udev rules key format. > A rule to match, can be composed by the attributes of the device > and the attributes from one single parent device. > > looking at device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0/event0': > KERNEL=="event0" > SUBSYSTEM=="input" > DRIVER=="" > > looking at parent device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0': > KERNELS=="input0" > SUBSYSTEMS=="input" > DRIVERS=="" > ATTRS{name}=="cros-ec-i2c" > ATTRS{phys}=="i2c-4-mux (chan_id 0)" > ATTRS{uniq}=="" > ATTRS{properties}=="0" > > looking at parent device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3': > KERNELS=="cros-ec-keyb.3" > SUBSYSTEMS=="platform" > DRIVERS=="cros-ec-keyb" > > looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e': > KERNELS=="104-001e" > SUBSYSTEMS=="i2c" > DRIVERS=="cros-ec-i2c" > ATTRS{name}=="cros-ec-i2c" > > looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104': > KERNELS=="i2c-104" > SUBSYSTEMS=="i2c" > DRIVERS=="" > ATTRS{name}=="i2c-4-mux (chan_id 0)" > > looking at parent device '/devices/12ca0000.i2c/i2c-4': > KERNELS=="i2c-4" > SUBSYSTEMS=="i2c" > DRIVERS=="" > ATTRS{name}=="s3c2410-i2c" > > looking at parent device '/devices/12ca0000.i2c': > KERNELS=="12ca0000.i2c" > SUBSYSTEMS=="platform" > DRIVERS=="s3c-i2c" > ********************************************************************** > > My openSUSE SD card is currently broken, so I cannot test under openSUSE. > > > Independent of the exact GPIO key, the term "ARM based Chromebook" in > > the subject and patch name seems to be rather broad given that there's > > the original Samsung Chromebook, plus the HP Chromebook 11, plus an Acer > > Chromebook based on Tegra, plus some based on Rockchip, etc. which > > likely all use different GPIO configurations. > > Mine is a Samsung Chromebook. > > > Guillaume > -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

2 2

Re: [opensuse-arm] Chromebook factory image problems
by Andreas Färber 04 Dec '14

04 Dec '14

Hi, the black screen may be related to leftover fbdev xorg.d config file - linux-next plus drm patchset is needed for eDP-LVDS bridge or u-boot with simplefb. Having both results in black screen. Regards, Andreas P.S. Sorry for top-posting. Guillaume Gardet <guillaume.gardet(a)free.fr> schrieb: >Le 02/12/2014 13:57, Guillaume Gardet a écrit : >> Le 02/12/2014 00:34, Alexander Graf a écrit : >>> >>> On 02.12.14 00:19, Misha Komarovsky wrote: >>>> Hello, >>>> I found that kernel or dtb file in current Chromebook contrib factory >>>> image, tested on version 245, have boot problems. After kernel start >>>> no signs of activity on stdout or serial console. >>>> >>>> If i replace linux.vmx and dtb on lxboot partition and modules on >>>> lxroot with same files from 12.3 dist image for chromebook im able to >>>> boot and pass installation fine. >>>> >>>> Also after installation and reboot, sd card not bootable at all, first >>>> partition on sdcard changed type code to 0700 and size to 32mb, >>>> probably cgpt script failed to fix it after installation for some >>>> reason. >>>> >>>> Bundled armsoc x11 driver fail to start because it is for abi 13 not abi 18. > >I updated armsoc driver just now from 0.0.1 to 1.1.0. It may help. :) > >>> That does indeed sound pretty broken. I think someone needs to sit down >>> and check which of all those components is already done well enough >>> upstream to drop our hacks. >>> >>> For example, I think u-boot has upstream snow support now, so we could >>> just use that. The kernel should be ok as well. >> >> Current Factory u-boot-snow (2015.01-rc2) does boot but is not really usable. It seems there is a problem to access SD card. But LCD and keyboard are working fine. :) >> >> I will have a look at it. > >With some patches, I am able to use a USB stick (no external SD) with upstream u-boot-snow and Factory kernel-lpae does boot ! >On kernel start, you must wait a little bit because at the beginning, there is just a black screen, followed later by a normal screen and a blue YaST Firstboot screen. :) > >But the are some problems: >* upstream u-boot does not handle external SD card for an unknown reason (internal eMMC is usable). Downstream u-boot has no bootz support. >* keyboard does not work under Linux (you must use an USB keyboard). >* Second boot is deeply broken. U-Boot is not launched at all because "cgpt" command is applied to /dev/mmcblk0 (internal eMMC) instead of /dev/sda (USB stick) (Kiwi bug?). Once this one manually fixed, u-boot load the kernel and then hang with a black screen. Probably due to missing modules in dracut initrd. (I will submit a JeOS update once tested) >* No wifi (at least on 1st boot) > >I will send an update (and SR) once tests are passed. > > >Guillaume > >-- >To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org >To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org >

1 0

[opensuse-arm] Fwd: Data corruption/crash bug in Firefox for armhf
by Guillaume Gardet 03 Dec '14

03 Dec '14

Hi, I forward you an e-mail received on cross-distro ML which may be useful for openSUSE arm. Guillaume -------- Message transféré -------- Sujet : Data corruption/crash bug in Firefox for armhf Date : Wed, 3 Dec 2014 09:44:29 +0000 De : Steve Capper <steve.capper(a)linaro.org> Pour : cross-distro(a)lists.linaro.org <cross-distro(a)lists.linaro.org> Hi folks, As a heads-up, there's a long standing bug in the way Firefox handles register assignment in XPCOM for 32-bit ARM: https://bugzilla.mozilla.org/show_bug.cgi?id=1050258 The symptoms are random data corruption and crashes. (details of bug and fix in the link above). Whilst upstream go through the motions of getting this fix merged, I would encourage you to pull in the fix for now into your packages (or at least keep an eye on this bug report). Cheers, -- Steve _______________________________________________ cross-distro mailing list cross-distro(a)lists.linaro.org http://lists.linaro.org/mailman/listinfo/cross-distro -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] BeagleBone Black updates: HDMI
by Matwey V. Kornilov 01 Dec '14

01 Dec '14

Hi, JeOS from here https://build.opensuse.org/package/show/home:matwey:JeOS-hdmi/LXQT-beaglebo… have HDMI support (not perfect one, I suppose there is some issue with hot-pluging) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] aarch64 emulator
by Matwey V. Kornilov 01 Dec '14

01 Dec '14

Hi, I need an instruction how to run aarch64 Factory system on my x86_64 hardware. There is an issue with gcc, so I have to fill bug-report somehow. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] BeagleBone Black updates
by Matwey V. Kornilov 29 Nov '14

29 Nov '14

Hi, JeOS from the link above equipped with the kernel from Kernel:HEAD (3.18.0-rc6-1.g961dff7-default) boots fine. USB works. You are welcome to test. http://download.opensuse.org/repositories/home:/matwey:/JeOS-next/images/ u-boot 2015.01-rc1 from Factory was found not working on this board. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] bbb: u-boot 2015.01-rc1: Please RESET the board
by Matwey V. Kornilov 29 Nov '14

29 Nov '14

Hi, I am trying to boot the image from here: https://build.opensuse.org/package/show/home:matwey:JeOS-next/JeOS-beaglebo… And see the following: U-Boot SPL 2015.01-rc1 (Nov 20 2014 - 18:11:04) ### ERROR ### Please RESET the board ### Resetting the board doesn't help. Any ideas? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Problem with freshclam and clamd and ntp
by Freek de Kruijf 28 Nov '14

28 Nov '14

I am trying to set up a mail server on my RPi and need freshclam and clamd. A problem seems to be that they start before ntp has properly set the date and time. I tried adding in the files /usr/lib/systemd/system/freshclam.service and /usr/lib/systemd/system/clamd.service that they should run after finishing the ntpd.service and also tried ntp-wait.service but that did not work. When asking for the systemctl status for these services I still see log entries with "Jan 01" as date. Only the last log line has the than current date. Any suggestions? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 2

[opensuse-arm] USB problems with BeagleBone.
by Zack Piper 28 Nov '14

28 Nov '14

I am currently experiencing some problems with USB on the BeagleBone. Whenever a USB secice is plugged in, this happens: [ 4580.135459] usb 2-1: new high-speed USB device number 9 using musb-hdrc [ 4580.545440] usb 2-1: device not accepting address 9, error -32 [ 4580.545542] usb usb2-port1: unable to enumerate USB device -- I have nothing fancy or intelligent to put here.

3 3

Re: [opensuse-arm] BananaPi
by Matwey V. Kornilov 28 Nov '14

28 Nov '14

Why is the kernel so outdated? Do you know if there is a upstream kernel support for this device? If so, you could try to make official openSUSE JeOS image for 13.2. 2014-11-28 13:42 GMT+03:00 Ingo Hoffmann <ingo(a)hoffmann-augsburg.de>: > I'm using it with the image provided by lemaker ( > http://www.lemaker.org/resources/9-101/opensuse_for_bananapi.html ). It > works great but I'ld like to get an upgrade to opensuse 13.2 and also a > later kernel! > Ingo > > > > On 28. November 2014 10:57:26 MEZ, "Matwey V. Kornilov" > <matwey.kornilov(a)gmail.com> wrote: >> >> Hi, >> >> Does anyone have experience with openSUSE on Banana Pi. >> I think to buy this one as home router: >> >> >> http://aliexpress.com/store/product/Freeshipment-Newest-arrive-Banana-PI-BP… -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2