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
Hi guys,
I have tumbleweed running on my cubox-i pro, and the wireless card is
working. But I set it up when 13.2 just came up (to give you an idea)
and now, on a fresh Tumbleweed or Leap 42.2 I don't remember anymore
how I did it. The system doesn't seem to recognize the card. In yast
when I add the wireless interface, I'm not able to select a pertaining
kernel module, nor I'm able to scan the network. Any hint on how I
should proceed?
Many thanks.
Regards
Alessio
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I am currently building software for a Raspberry using a Raspberry as
the build computer. It works surprisingly well. Nonetheless, I am
considering setting up doing cross compiling on an intel x86 (non ARM)
computer. I guess installing cross compilers and such tools from OBS
is okay. I already do this for doing Windows (32- and 64-bit) cross
compiling.
I also install from OBS the various libraries needed for the Windows
cross compile. They are nicely put in
/usr/i686-w64-mingw32/sys-root/mingw or
/usr/x86_64-w64-mingw32/sys-root/mingw. They are not installed in the
Linux /usr/bin/ or /usr/lib/ trees.
Unfortunately, I am guessing this would not be the case for ARM
packages (e.g., libjpeg8-8.1.2-40.2.aarch64 and
libjpeg8-devel-8.1.2-40.2.aarch64). They would be installed in the
/usr/bin/ or /usr/lib/ trees, as that's where they are expected to be.
Which is perhaps not what I want on a cross-compiling system
Am I missing some brilliant thing to get these types of things
installed in some other tree? Or is cross-compiling going to be more
problematic than maintaining a Raspberry to do this work?
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hallo, Raspbi-friends.
I have download last sunday 2 Versions, but after installation te
boot-activity stopped.
1. Version:
openSUSE-Tumblewéed-ARM-E20-raspberrypi3-2ß16-11-23-Build4.21.raw.gz
2. Installation on a 16GB-SD-stick
/dev/sdc1 200 MB
/dev/sdc2 ext3 207 MB BOOT
/dev/sdc3 btrfs 4,38 GB ROOT
3. When starting I get the following messages
Menue: openSuse (vmx) (early messages
not copied, to fast)
FailSafe openSuse (vmx)
Booting OpenSUSE.vmx
(no text)
loading linux.vmx
loading initrd.vmx
( approx. 10 lines no text)
EFI stub: Booting Linux Kernel
EFI stub: UEFI Secure Boot is enabled
EFI stub: Using DTB from configuration table
EFI stub:Exiting boot servies and installing address map....
Thank you for any advice
Regards
Edgar Dombrowski, DJ3PU, Munich
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
It looks like none of the current TW images for Rpi2 are working. Am I correct
or struck by the coincedence of three faulty SD cards that do work with other
distros?
--
Gertjan Lettink, a.k.a. Knurpht
openSUSE Board Member
openSUSE Forums Team
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Retesting my JeOS-hikey image with U-Boot I noticed that with the recent
btrfs enablement the dtb folder is on the wrong partition (btrfs instead
of ext3) and thus cannot be loaded by U-Boot.
I am assuming this is also the reason why people reported recent rpi3
images as non-working!
Could one of you guys who made that change please look into why this is
misbehaving or revert that change?
Thanks,
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
Hi,
Currently, I am seeing the strange things. Some packages are missed in
repo cache of armv7l Factory. I did zypper clean -all, zypper refresh
-f, but still.
For instance, gcc-c++ is missed. The file itself is present:
http://download.opensuse.org/ports/armv7hl/tumbleweed/repo/oss/suse/armv7hl…
But the package is not searchable:
dyn-221:/ # zypper se gcc
Loading repository data...
Reading installed packages...
S | Name | Summary
| Type
--+---------------------+-----------------------------------------------------------+--------
| gcc5-info | Documentation for the GNU compiler collection
| package
| gcc6-info | Documentation for the GNU compiler collection
| package
| gccmakedep | Utility to list the resource database of an X
application | package
i | libgcc_s1 | C compiler runtime library
| package
| libstdc++6-gcc5-doc | Documentation for the GNU C++ standard library
| package
| libstdc++6-gcc6-doc | Documentation for the GNU C++ standard library
| package
dyn-221:/ # zypper lr -r -d
Repository priorities are without effect. All enabled repositories share
the same priority.
# | Alias | Name
| Enabled | GPG Check | Refresh | Priority | Type | URI
| Service
--+------------------------------------+------------------------------------+---------+-----------+---------+----------+-------+-----------------------------------------------------------------+--------
1 | openSUSE-Ports-Tumbleweed-repo-oss |
openSUSE-Ports-Tumbleweed-repo-oss | Yes | (r ) Yes | Yes |
99 | yast2 |
http://download.opensuse.org/ports/armv7hl/tumbleweed/repo/oss/ |
Is it just for me?
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I am trying to update my Raspberry PI3, and have a couple issues:
1. I can't seem to get zypper to download
http://download.opensuse.org/ports/aarch64/factory/repo/oss/suse/noarch/ker…
It gets 3 MB or so and then claims
Timeout exceeded when accessing
2. I have a repository in OBS with some ARM packages
(http://download.opensuse.org/repositories/home:/rogeroberholtzer/openSUSE_F…).
When installing from there, I get this kind of error:
blt-3.0a-57.5.aarch64.rpm:
Header V3 DSA/SHA1 Signature, key ID 605a090d: NOKEY
V3 DSA/SHA1 Signature, key ID 605a090d: NOKEY
blt-3.0a-57.5.aarch64 (RSofT ARM): Signature verification failed
[4-Signatures public key is not available]
I can ignore it and the install continues. But I don't know why I get
the error. I have repositories for other platforms and they have
always worked fine.
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hallo, Linuxer.
Vielen Dank für die vielen Hinweise. Es hat "natürlich" geklappt.
Schönen 4. Advent
MfG
Edgar Dombrowski, DJ3PU, München
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Thanks to Roger Oberholtzer I installed the Raspipi 3B file
/openSUSE-Leap42.2-ARM-JeOS-raspberrypi3.aarch64-2016.11.25-
Build1.9.raw.xz
It took approx. 10 min. to ask for Username and Password.
Can anny give this words when fist boot?
Thanks for your help and all best for ete weekend.
Edgar Dombrowski, DJ3PU, Munich
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
