Re: [opensuse-arm] Rock64

2020-02-12 Thread Brüns , Stefan
On Mittwoch, 12. Februar 2020 16:37:28 CET ITwrx wrote: > On 2/12/20 8:59 AM, ITwrx wrote: > > On 2/12/20 1:49 AM, Matwey V. Kornilov wrote: > > Ok, i misspoke earlier. The first time i didn't extract, then run > dd_rescue per your instructions. i ran "xzcat [image].raw.xz | dd bs=4M > of=/dev/sdX

Re: [opensuse-arm] Raspi Update of Leap 15: DNS broken

2018-10-30 Thread Brüns , Stefan
On Dienstag, 30. Oktober 2018 15:37:57 CET Guillaume GARDET wrote: > - Axel Braun a écrit : > > Am Dienstag, 30. Oktober 2018, 15:24:47 CET schrieb Guillaume GARDET: > > > Hi, > > > > > > Which Raspberry Pi is it? Model 2B, 3B or 3B+ ? > > > > I'm not sure, it may be a 3B or 3B+ > > hwinfo d

Re: [opensuse-arm] Raspi LXQT Image_: Falkon crashes

2018-10-30 Thread Brüns , Stefan
On Dienstag, 30. Oktober 2018 15:15:38 CET Axel Braun wrote: > Hi, > > I installed a new image with LXQT desktop today, together with falkon as > browser. > > When calling it, it crashes. From the command line: > linux:~ # falkon > libEGL warning: DRI2: failed to authenticate > [1030/140331.13733

Re: [opensuse-arm] Re: Control output pin on RPi

2018-09-05 Thread Brüns , Stefan
On Mittwoch, 5. September 2018 13:01:26 CEST Volker Kuhlmann wrote: > On Wed 05 Sep 2018 21:06:28 NZST +1200, Alexander Graf wrote: > > rpi:~ # grep 'pin 4 ' /sys/kernel/debug/pinctrl/3f20.gpio/pins > > pin 4 (gpio4) function gpio_in in hi; irq 83 (none) > > rpi:~ # echo $(( 458 + 4 )) > /sys/c

Re: [opensuse-arm] UHD 4k support

2018-06-25 Thread Brüns , Stefan
On Montag, 25. Juni 2018 23:06:29 CEST Steve Moring wrote: > Hi, > > I've seen a few people have UHD monitors working with their raspberry > pi3's. I'm confused by a constraint that appears to be an X > constraint, and that's the size of the desktop. > > Has anyone gotten this to work successful

Re: [opensuse-arm] Problem running python script using GPIO

2018-06-14 Thread Brüns , Stefan
On Donnerstag, 14. Juni 2018 17:50:56 CEST Alexander Graf wrote: > On 06/14/2018 05:43 PM, Freek de Kruijf wrote: > > Op woensdag 13 juni 2018 15:58:25 CEST schreef Alexander Graf: > >> On 13.06.18 14:27, Freek de Kruijf wrote: > > > > I used the strace and found that in fact the equivalent bash c

Re: [opensuse-arm] Factory ARM packages failing due to wrong rpmlint errors on licenses

2018-03-22 Thread Brüns , Stefan
On Donnerstag, 22. März 2018 15:57:50 CET Guillaume Gardet wrote: > Le 22/03/2018 à 15:48, Andreas Schwab a écrit : > > On Mär 22 2018, Guillaume Gardet wrote: > >> Currently, some packages are failing in Factory ARM (aarch64 and armv6 only, armv7 seems to be ok) because of wrong rpmlint errors o

Re: [opensuse-arm] Tumbleweed image for Raspberry Pi 2 contains a corrupt ext4 partition after first boot

2018-01-12 Thread Brüns , Stefan
On Freitag, 12. Januar 2018 22:43:16 CET Brüns, Stefan wrote: > On Freitag, 12. Januar 2018 21:30:48 CET Freek de Kruijf wrote: > > > which shows the same behavior. > > > > Tried again with a new 16 GB microSD card, which succeeded. > > I collected on the console

Re: [opensuse-arm] Tumbleweed image for Raspberry Pi 2 contains a corrupt ext4 partition after first boot

2018-01-12 Thread Brüns , Stefan
On Freitag, 12. Januar 2018 21:30:48 CET Freek de Kruijf wrote: > > > > which shows the same behavior. > > Tried again with a new 16 GB microSD card, which succeeded. > I collected on the console the boot output, logged in and typed "fdisk -l > /dev/mmcblk0", both using this 16 GB card and an 8 G

Re: [opensuse-arm] Fail with openSUSE JeOS pine 64 image

2018-01-08 Thread Brüns , Stefan
On Dienstag, 12. Dezember 2017 13:27:50 CET Duncan Mac-Vicar P. wrote: > Ludwig Nussel writes: > > Works for me. HDMI output turns black as soon as the kernel takes over > > though. > > Is the Leap 42.3 release working with Pine64? The 42.3 kernel has to many missing parts to really work on A64.

Re: [opensuse-arm] Packet fake-hwclock generated

2017-12-06 Thread Brüns , Stefan
On Mittwoch, 6. Dezember 2017 15:23:19 CET Freek de Kruijf wrote: > In Raspbian I noticed a packet always included in the image called fake- > hwclock. I used the tar.gz file together with a .spec file to generate this > packet for openSUSE distributions for systems without a Real Time Clock. > >

Re: [opensuse-arm] Fail with openSUSE JeOS pine 64 image

2017-12-04 Thread Brüns , Stefan
On Montag, 4. Dezember 2017 10:31:41 CET Paul Gonin wrote: > Hi, > > I tried today the pine64 JeOS ipage on pine64 board with 2GB RAM > Connected on ethernet (with dhcp server) > > Collected boot output with serial access on EXP port > http://paste.opensuse.org/54338867 Can you try: https://down

Re: [opensuse-arm] [aarch64] Tumbleweed repositories is outdated

2017-11-13 Thread Brüns , Stefan
On Montag, 13. November 2017 12:55:54 CET Alexander Graf wrote: > Hi Manu, > > On 11/13/2017 11:52 AM, Manu Maier wrote: > > The last images are from the 17-Jun-2017 > > http://download.opensuse.org/ports/aarch64/tumbleweed/images/?C=M;O=D > > > > and the latest packages from 21-Sep-2017 > > http

Re: [opensuse-arm] Wireless interface on Raspberry Pi 3

2017-08-28 Thread Brüns , Stefan
On Montag, 28. August 2017 09:59:22 CEST Roger Oberholtzer wrote: > On Fri, Aug 25, 2017 at 6:06 PM, Andreas Färber wrote: > > Hi, > > > > Am 25.08.2017 um 12:57 schrieb Roger Oberholtzer: > >> 2. Does one run mkinitrd and not dracut on the Raspberry? I really do > >> not want to mess up the init

Re: [opensuse-arm] ARM-EFI: Where is the device-tree?

2017-08-09 Thread Brüns , Stefan
On Mittwoch, 9. August 2017 15:55:48 CEST Alexander Graf wrote: > > Am 09.08.2017 um 12:45 schrieb Frank Kunz > > : > > > > Hello, > > > > I'm trying to get the USB-OTG interface working on the DE0-nano-SoC > > (socfpga) board by using openSUSE tumbleweed. The image uses ARM-EFI > > boot and ther

Re: [opensuse-arm] tumbleweed updates for armv6hl ?

2017-07-18 Thread Brüns , Stefan
On Dienstag, 18. Juli 2017 10:39:48 CEST BWC Illmensee GmbH - Ralph Gauer wrote: > I had a look at this link to see if I could help, > but I can't tell were to start there to find the problems and solutions. > (too little experience with the build system I guess) > > One thing I could see is that

Re: [opensuse-arm] ntp, a couple of minor issues

2017-03-20 Thread Brüns , Stefan
On Montag, 20. März 2017 16:11:10 CET Eric Curtin wrote: > Yeah "iburst" was all that this needed. It's perfect for my needs at > least. Haven't seen anything like that in my dracut scripts either. > Similar to Per, I may not be looking for the right thing. > > On 17 March 2017 at 12:14, Per Jesse

Re: [opensuse-arm] NTP on nanopi neo (air) ?

2017-03-15 Thread Brüns , Stefan
On Mittwoch, 15. März 2017 08:52:28 CET Per Jessen wrote: > I don't seem to be able to run NTP on my nanopi neo air - when I try to > start it, it enters a loop of stopping and starting, reporting "0.0.0.0 > c01d 0d kern kernel time sync disabled". Are you sure this is the complete message? Please

Re: [opensuse-arm] Tumbleweed on RPi3 for aarch64

2017-03-08 Thread Brüns , Stefan
On Mi, 2017-03-08 at 14:33 +0100, Freek de Kruijf wrote: > I wonder what in blocking the update of Tumbleweed for aarch64 on the > RPi3.  > The last update was on Feb. 2. Have a look yourself: https://build.opensuse.org/project/show/openSUSE:Factory:ARM Kind regards, Stefan

Re: [opensuse-arm] MAC address on Raspberry PI 3

2017-03-06 Thread Brüns , Stefan
On So, 2017-03-05 at 09:39 -0500, Greg Freemyer wrote: > On Sun, Mar 5, 2017 at 7:48 AM, Michael Ströder > wrote: > > Ken Schneider - openSUSE wrote: > > > I cannot understand the need for the system to creat a MAC > > > address when every device is > > > asigned an address by the manufacturer. >

Re: [opensuse-arm] MAC address on Raspberry PI 3

2017-03-06 Thread Brüns , Stefan
On Mo, 2017-03-06 at 16:51 +0100, Roger Oberholtzer wrote: > On Mon, Mar 6, 2017 at 4:43 PM, Michal Kubecek > wrote: > > > I understand how they are set up. But this is not matter of setup. > > Making sure poster who is not subscribed gets the replies is only > > one of > > reasons to send replie

Re: [opensuse-arm] MAC address on Raspberry PI 3

2017-03-03 Thread Brüns , Stefan
On Fr, 2017-03-03 at 10:05 -0500, Ken Schneider - openSUSE wrote: > On 03/03/2017 09:34 AM, Roger Oberholtzer wrote: > > On Fri, Mar 3, 2017 at 2:37 PM, Ken Schneider - openSUSE > > wrote: > > > > > Most modern routers allow you to assign a fixed address to a mac > > > address. > > > > Of course

Re: [opensuse-arm] MAC address on Raspberry PI 3

2017-03-03 Thread Brüns , Stefan
On Fr, 2017-03-03 at 07:02 +0100, Michal Kubecek wrote: > On Thursday, 2 March 2017 8:19 Roger Oberholtzer wrote: > > I have just updated my previously working RI 3 to the latest kernel > > for openSUSE 42.2 > > > > It seems that the device now generates a unique MAC address on the > > wired Ether

Re: [opensuse-arm] Watchdog trigger during first boot

2017-01-23 Thread Brüns , Stefan
On Montag, 23. Januar 2017 20:56:06 CET Frank Kunz wrote: > Hello, > > I have a problem when adding a new board to openSUSE (DE0-nano-SoC). The > upstream u-boot for that board enables the watchdog with a 30 seconds > timeout. That causes the board to get reset during the system partition > resizi

Re: [opensuse-arm] First boot of Leap 42.2 aarch64 image on RPI3

2016-11-18 Thread Brüns , Stefan
On Freitag, 18. November 2016 14:03:55 CET Freek de Kruijf wrote: > Op vrijdag 18 november 2016 13:15:34 schreef Alexander Graf: > > Hi Freek, > > > > Where does it hang? Before U-Boot? In U-Boot? In Linux? > > I don't know if it is before or in U-boot. I see a message about scanning > USB device

Re: [opensuse-arm] wlan getting new hw-address every 5 minutes on raspberry pi 3

2016-11-09 Thread Brüns , Stefan
On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote: > Hi Stefan, > > The results: > > - journalctl -b -u NetworkManager > (there is much more output, but I take it this is what you mean:) > > nov 09 17:04:11 nohostname NetworkManager[548]: > [1478707451.7727] device (wlan0): set

Re: [opensuse-arm] wlan getting new hw-address every 5 minutes on raspberry pi 3

2016-11-09 Thread Brüns , Stefan
On Dienstag, 8. November 2016 21:44:11 CET Jogchum Reitsma wrote: > Hi, > > After succeeding in getting wifi enabled on the pi 3 (see my previous > posting 6th of nov., 20:31 WET, and follow ups) the next problem arises: > every 5 minutes the wifi connection gets another hw-address, and hence > an

Re: [opensuse-arm] Image for RPi3, using architecture aarch64 works

2016-09-30 Thread Brüns , Stefan
On Freitag, 30. September 2016 13:20:54 CEST Freek de Kruijf wrote: > Op vrijdag 30 september 2016 10:54:04 schreef Freek de Kruijf: > > Just tried the image for the Raspberry Pi 3 > > openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.27- > > Build6.1.raw.xz and I have a working sys

Re: [opensuse-arm] Raspberry Pi 3 images broken (was: ARM images broken!)

2016-09-14 Thread Brüns , Stefan
On Mittwoch, 14. September 2016 11:15:47 CEST Freek de Kruijf wrote: > Op maandag 12 september 2016 14:52:54 CEST schreef Freek de Kruijf: > > I tried the image 2016.09.06 but first it hanged on a connected USB > > storage > > device. After disconnecting the USB device it hangs on "stub: Exiting bo

Re: [opensuse-arm] ARM images broken!

2016-09-06 Thread Brüns , Stefan
On Dienstag, 6. September 2016 16:10:49 CEST Andreas Färber wrote: > Am 06.09.2016 um 16:01 schrieb Alexander Graf: > > On 09/06/2016 03:30 PM, Guillaume Gardet wrote: > >> I noticed that latest ARM images running u-boot (e.g. JeOS-beagle) are > >> broken because: > >> * Mke2fs now creates file sy

Re: [opensuse-arm] New package for ARM: raspberrypi-firmware

2015-12-02 Thread Brüns , Stefan
Hi Andreas, the dtb was not renamed, but added. RPi 1 B really has revisions 1.x and 2.0 with hardware differences. Rev 2.0 has 2 mounting holes, the P6 reset header, and most importantly the (unpopulated) P5 header with GPIOs 28-31, providing the I2S signal needed for HifiBerry and the like.

Re: [opensuse-arm] Re: Support for device-tree overlays

2015-07-30 Thread Brüns , Stefan
On Thursday, July 30, 2015 11:04:21 Matwey V. Kornilov wrote: > Hello Andreas and Stefan, > > That is correct. But you tell about bootloader, I am not sure why does > a bootloader need device tree overlay support in kernel. I mean it can > merge device tree before actual kernel loaded and run. >