Hi,
this is a known OBS bug, asked the admins to deploy a fix shortly.
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hello,
I have submitted the raspberrypi-firmware package for inclusion in Factory:
https://build.opensuse.org/request/show/341314
This package contains VideoCore IV binaries that are read from a FAT
partition by the Raspberry Pi boot ROM. Without these files neither the
ARM U-Boot bootloader nor an ARM kernel can be booted on that device.
It is not really needed on x86 systems, so as alternative we could
submit it to openSUSE:Factory:ARM instead. However, since in the past
some non-free binaries snuck into this package (disguised as
SUSE-Firmware instead of SUSE-NonFree license and probably without
obtaining permission first), I think it makes sense to have it go
through the full legal review process of openSUSE:Factory.
Similarly, I would like to split out arndale-bl1.img from u-boot package
as arndale-firmware (a signed version of GPL'ed U-Boot Secondary Program
Loader) and to submit odroid{,xu}-firmware at some point, possibly more.
This will allow us to build JeOS images for boards with upstream U-Boot
and upstream kernel support centrally in openSUSE:Factory:ARM rather
than in some Contrib project. In particular my intent here is to drop
the devel:ARM:Factory:Contrib:RaspberryPi:upstream project in favor of
openSUSE:Factory:ARM.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, 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
I have downloaded several images and written them to an SD card with SD Image Writer but can not get anything to boot. Am I using the correct software to write the SD card and what image should I be using.
Thanks, Andy
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Sorry for cross post (-arm and -buildservice) but not sure who should fix this problem.
Some ARM v7 workers are broken. They start to boot and then fail. Thus, lots of packages go to building state but return quickly to scheduled state.
armbuild numbers 13, 16, 17, 18 and 19 are failing workers.
armbuild15 does not seem to be ok but it seems to be a slightly different bug.
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
[I am not subscribed to this list, thank you]
21.11.2015 01:28, Andreas Färber пишет:
> @arvidjaar: Wherever we have a UEFI bootloader available, we _are_
> using grub2. This however is for U-Boot bootloader, which is stopping
> to support its by default disabled `CONFIG_API` option that grub2's
> `uboot` platform support relies on - I reported this on their mailing
> list and they refused to fix, e.g., sunxi for v2015.10, pointing to
That's not the impression I got from this discussion. They (U-Boot
developers) do not see it as priority task, but they won't refuse fixing
it, especially as there are other consumers of API besides GRUB.
> this extlinux.conf mechanism, which they
> [document](http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.distro;h=9e4722a86ee562fdc80b675f5be9d30e30e61597;hb=HEAD)
> as their preference for distros over the single-kernel boot.scr
> mechanism we use today. Another problem with grub2 is that it needs
> to be patched per board, so a single package does not work. See for
It is trivial to expose link address as configure parameter; would it be
useful for you?
Ultimate solution is to support relocation in U-Boot. Do you know if it
was considered, and what is opinion of U-Boot developers to it?
> example my [Jetson TK1 grub2 installation
> guide](https://en.opensuse.org/HCL:JetsonTK1#Installing_GRUB2). Even
> worse, my modified grub2 builds proved to be rather unreliable on the
> Jetson TK1, often not getting to any prompt or menu. If you want to
Well, there was not much activity w.r.t. ARM post original submission of
Leif; there was one specific fix I can remember. Someone would of course
need to debug it. Sure, we miss active ARM maintainer in GRUB.
> discuss grub2 further, I suggest you post to opensuse-arm mailing
> list instead.
>
I still think that from distribution PoV focusing on single bootloader
is beneficial and hope we can find solution.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hello,
I've found that boot partition of JeOS-beaglebone image from
openSUSE:Factory:ARM doesn't have any dtb files. I don't think that it
is ok.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hello,
Why bootmenu command is not used atm? Are there any reasons?
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Build336.2 from
repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the
SD is partitioned and the resulting system boots. However the Ethernet
connection does not become active. The lights stay off. I could not find a
method to list the journal on the SD partition on a system where the SD is
mounted.
Build325.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ does
the low level boot, but after that, like before, can't find the boot image on
the 3rd partition.
Upgrading a system build earlier with a working image works OK. Finally the
problem using the command "yast lan" is solved.
--
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
Hello,
What do you think about adding possibility to use nbd (network block
device) as a root partition for JeOSes?
It could be useful for hardware-testing farms. For instance, u-boot
takes kernel and initrd via tftp and then kiwi-based initrd mounts root
device /dev/nbd0 feed by qemu-nbd.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
please be patient with me, cross-compilation is completely new to me.
I have an x86_64 host with opensuse 13.1 and want to cross-compile my own
linux system for a raspberry pi.
In my opensuse-repositories I found the two packages
cross-arm-binutils (2.23.2-8.1.2)
cross-armv7hl-gcc48-icecream-backend (4.8.1_20130909-3.2.1)
>From what I unterstand, I should be able to cross-compile a linux system for
armv7 after installing these two packages. Is this correct? In [1] it is
stated that "openSUSE does not currently ship a cross-compiler for ARM." which
is -- as far as I understand this -- a contradiction.
Ref [1] describes another solution which seems suboptimal to me.
And from [2] I gather that cross-compilation currently does not work. This
thread, however, deals with other versions of the packages given above. Do I
have to expect the same problems?
Thanks in advance for your help!
Regards,
Karl
[1] https://en.opensuse.org/openSUSE:OpenSUSE_on_your_ARM_board
[2] http://lists.opensuse.org/opensuse-arm/2015-07/msg00007.html
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org