Am 29.08.19 um 10:18 schrieb Guillaume Gardet:
> Hi,
>
>> -Original Message-----
>> From: Frank Kunz
>> Sent: 15 August 2019 21:39
>> To: opensuse-arm@opensuse.org
>> Subject: [opensuse-arm] RFC Espressobin install procedure
>>
>&
sorry, here the correct mailing list.
Weitergeleitete Nachricht
Betreff: Tumbleweed on espressobin
Datum: Mon, 1 Apr 2019 21:27:29 +0200
Von: Frank Kunz
An: opensuse-factory
Hello,
I try to get a recent Tumbleweed running on Espressobin[1]. According to
the wiki page [2
Am 06.12.18 um 21:27 schrieb Matwey V. Kornilov:
>
> It is a long story...
>
> First, you have to clone appropriate branch of
> https://kernel.opensuse.org/cgit/kernel-source/log/?h=master
>
> Then modify config and run ./scripts/tar-up.sh to create tarball and
> ./scripts/osc_wrapper to create
Hello,
I want to debug a kernel problem on a armv7 board. For that I want to
temporary enable the CONFIG_PROVE_LOCKING config. My idea was to branch
the used kernel (lpae) build in obs, add the config to the cloned
kernel, and install then the build result on my board.
I tried to modify the
Am 14.08.2018 um 11:44 schrieb Matwey V. Kornilov:
>
> By the way, could you please tell which u-boot do you use at EspressoBin?
>
I tried
U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800)
and
U-Boot 2017.03-armada-17.10.3-g06ad760c88 (Aug 10 2018 - 21:59:24 +0200)
but
Am 20.06.2018 um 08:58 schrieb Guillaume Gardet:
>> there is also some effect for the efi part. So also other boards might
>> be affected by that missing path?
>
> It should not hurt here, as it will just not switch folder.
> But /usr/src/packages/KIWIROOT-oem/boot/u-boot-with-spl.sfp should be
Am 05.06.2018 um 12:37 schrieb Guillaume Gardet:
> Hi,
>
> here are some results of my tests of Leap 15.0 images.
> * JeOS-beagle : OK. (DVI output not working on BBxM, as on Tumbleweed)
> * JeOS-beaglebone: OK on BB Black. HDMI not tested.
> * XFCE-raspberrypi2: OK
> * XFCE-sabrelite : USB not
Am 31.12.2017 um 12:17 schrieb Alexander Graf:
Am 30.12.2017 um 23:26 schrieb Frank Kunz <mailingli...@kunz-im-inter.net>:
I try to control a few gpio pins via bash script. Board and OS version is:
cat /proc/device-tree/compatible
olimex,a13-olinuxinoallwinner,sun5i-a13
cat /etc/os-r
I try to control a few gpio pins via bash script. Board and OS version is:
cat /proc/device-tree/compatible
olimex,a13-olinuxinoallwinner,sun5i-a13
cat /etc/os-release
NAME="openSUSE Leap"
VERSION="42.3"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.3"
PRETTY_NAME="openSUSE Leap 42.3"
Am Freitag, 13. Oktober 2017, 14:42:31 CEST schrieb Andreas Färber:
>
> Both issues - dtb on the wrong partition and lack of fdt apply -
> indicate that you're not using an openSUSE-built U-Boot. Please re-test.
>
Ups, my fault. I had an upstream u-boot installed. With an openSUSE u-boot the
Am Freitag, 13. Oktober 2017, 12:10:47 CEST schrieb Andreas Färber:
> Am 13.10.2017 um 11:22 schrieb Alexander Graf:
> > On 13.10.17 11:17, Frank Kunz wrote:
> >> I'm doing some test with EFI boot on an olinuxino board here: https://
> >> buil
Hi,
I'm doing some test with EFI boot on an olinuxino board here: https://
build.opensuse.org/package/show/home:frank_kunz:branches:openSUSE:Factory:ARM/
JeOS-olinuxinolime
The image works and the kernel has a device-tree visible under /proc/device-
tree. With non EFI configurations the
Am 09.08.2017 um 18:09 schrieb 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
>>> <mailingli...@kunz-im-inter.net>:
>>>
>>> Hello,
>>>
>>> I'm
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 there is no dtb file on the boot partition. When Linux is
running the device-tree is visible on /proc/device-tree and
/sys/firmware, so there is
Am 24.01.2017 um 18:29 schrieb Andreas Färber:
> Hi,
>
> Am 24.01.2017 um 17:30 schrieb Frank Kunz:
>> But the watchdog triggers anyway during the system partition rewrite. So
>> nothing pings the watchdog during that operation. I think there is still
>> a service miss
Am 25.01.2017 um 09:24 schrieb Alexander Graf:
>
>
>> Am 24.01.2017 um 19:49 schrieb Frank Kunz <mailingli...@kunz-im-inter.net>:
>>
>>> Am 24.01.2017 um 18:29 schrieb Andreas Färber:
>>> Hi,
>>>
>>>> Am 24.01.2017 um 17:30 s
Am 24.01.2017 um 18:29 schrieb Andreas Färber:
> Hi,
>
> Am 24.01.2017 um 17:30 schrieb Frank Kunz:
>> But the watchdog triggers anyway during the system partition rewrite. So
>> nothing pings the watchdog during that operation. I think there is still
>> a service miss
Am 23.01.2017 um 21:10 schrieb 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 seco
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
resizing at first startup. To get watchdog support enabled I added the
Hi,
successfully tested images for A10-OLinuXino-LIME and
A20-OLinuXIno-LIME2 (HDMI, network, USB keyboard) and A13-OLinuXino-WIFI
(VGA, onboard WiFi, USB keyboard).
Great work. Thanks.
Br,
Frank
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail:
I tested
openSUSE-Tumbleweed-ARM-JeOS-olinuxinolime2.armv7l-2016.04.22-Build1.1.raw.xz
and there is no ethernet working with that build.
the journal lists
Jan 01 01:00:29 nohostname systemd[1]: Starting wicked managed network
interfaces...
Jan 01 01:00:29 nohostname kernel: libphy: PHY
Am 17.02.2016 um 15:47 schrieb Andreas Färber:
> I started
> a cleanup but never finished and don't have access to all boards to
> check, in particular the Olimex ones.
I can do that tests. While testing
openSUSE-Tumbleweed-ARM-E20-olinuxinolime2.armv7l-1.12.1-Build377.1.raw.xz
I faced some
attached the /var/log/boot.kiwi
Br,
Frank
boot.kiwi.xz
Description: application/xz
Hello,
unfortunately the GMAC kernel configuration for Allwinner A20 and A31
devices is disabled in armv7l kernel 4.2. Therefore the A20 Olimex bards
do not have network anymore.
What needs to be done to get that enabled again:
config DWMAC_SUNXI
tristate "Allwinner GMAC support"
Am 12.06.2015 um 11:23 schrieb Guillaume Gardet:
It should. ;)
It does!
Successfully tested one of the todays sunxi Images.
Thanks.
Br,
Frank
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Am 08.06.2015 um 11:36 schrieb Guillaume Gardet:
Could you give us the kiwi version from working image, please?
That's what I found out of the image:
kiwi_iversion='1.12.1'
kiwi_revision='a1b5148889afb4530f8f202f4175f58e5c5bf171'
Br,
Frank
--
To unsubscribe, e-mail:
Hi,
also with new builds from today the situation is still the same. it
seems that all sunxi based board images are broken. I tried to find out
what is wrong but up to now without success. 'Old' images with kernel
3.19 (Factory) still work.
Br,
Frank
--
To unsubscribe, e-mail:
Am 28.05.2015 um 16:32 schrieb Guillaume Gardet:
after testing some factory images, it appears that boot.scr/boot.script
are not updated, so board is unbootable after first boot.
Anything changed in config or kiwi?
I have the same problem. Image is
Am 11.05.2015 um 23:12 schrieb Dirk Müller:
Should be fixed relatively soon (new packages have already been build,
just publishing takes hours as usual).
The dependency between those two packages is not easy, my previous
attempt at adding requires makes it difficult to upgrade packages or
Am 11.05.2015 um 19:54 schrieb Andreas Färber:
I wondered whether there might simply be no difference between 4.0.0 and
4.0.1 for dtb-sun4i, but the build log does not indicate such a cleanup,
the last build was indeed a 4.0.0 one:
The dtb-sun4i is not really affected, it was just the newest
Hi,
it seems that the sunxi device trees are not rebuild ans still have
kernel 3.19 data included instead of version 4. This prevents (at least)
the sun4i based boards from booting due to changes in the mmc drivers
and device trees. It look that there is a build dependency missing when
the kernel
31 matches
Mail list logo
