November 2014

[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 … [View More]

10 30

[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] 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

[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 … [View More]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 [View Less]

2 2

[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 … [View More]

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 > > > … [View More]

3 2

Main

Development

Information

Community

Social Media

Other

openSUSE ARM