[opensuse-buildservice] SLES for Raspberry Pi 3
I have just installed SLES on my Raspberry PI 3. It seems to be working great. I had previously been trying openSUSE on this device, but it is always dead. Which seems odd because there is only one version of the PI 3. So I cannot see how it can work for some and not others. Anyway, SLES works great. My goal is to try to get a hardware interface running on openSUSE (porting some local embedded code to what will be a kernel driver). So, I thought I would play with the SLES until the openSUSE variant works. Part of this post is being happy to report that SLES works. The other part is to ask a question or two about SLES and OBS. I'm not certain this is the best place to ask my question. But I am trying to find my way around. When I tried to build some libraries, various include files were missing. Which is expected. So, I thought I would install the various -devel packages. I had expected them to be in the repositories that SLES enabled when I registered it. Oddly, there are almost no -devel packages. Like the one that contains X11/keysym.h Which brings me to my question: Since Leap is supposed to have brought SUSE and openSUSE closer together, should I be able to use OBS repositories with SLES? If so, must I restrict myself to SLES repos? That is, might I be able to install packages from Factory? I see that SLES is not enabled for most of OBS.Where is a good source of SLES repositories? Beyond the three that SLES enables upon registration. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Roger,
Roger Oberholtzer
[...] When I tried to build some libraries, various include files were missing. Which is expected. So, I thought I would install the various -devel packages. I had expected them to be in the repositories that SLES enabled when I registered it. Oddly, there are almost no -devel packages. Like the one that contains X11/keysym.h
Which brings me to my question:
Since Leap is supposed to have brought SUSE and openSUSE closer together, should I be able to use OBS repositories with SLES? If so, must I restrict myself to SLES repos? That is, might I be able to install packages from Factory? I see that SLES is not enabled for most of OBS.Where is a good source of SLES repositories? Beyond the three that SLES enables upon registration.
What repos are enabled? For x86_64 most -devel packages are in SDK repo. If thats not enough there is the Backports repo (aka SUSE Package Hub) with more software in Leap/Tumbleweed quality. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 13, 2016 at 10:50 AM,
What repos are enabled? For x86_64 most -devel packages are in SDK repo.
If thats not enough there is the Backports repo (aka SUSE Package Hub) with more software in Leap/Tumbleweed quality.
The ARCH is aarch64. I see these, which were added when I registered the install: # | Alias | Name | Enabled | GPG Check | Refresh | URI --+---------------------------------------------------------------------------------------------------+----------------------------------+---------+-----------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2-RPI-Debuginfo-Pool | SLES12-SP2-RPI-Debuginfo-Pool | No | ---- | No | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/product_debug?... 2 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2-RPI-Debuginfo-Updates | SLES12-SP2-RPI-Debuginfo-Updates | No | ---- | Yes | https://updates.suse.com/SUSE/Updates/SLE-RPI/12-SP2/aarch64/update_debug?mb... 3 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2-RPI-Pool | SLES12-SP2-RPI-Pool | Yes | (r ) Yes | No | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/product?BjDiOX... 4 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2-RPI-Source-Pool | SLES12-SP2-RPI-Source-Pool | No | ---- | No | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/product_source... 5 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2-RPI-Updates | SLES12-SP2-RPI-Updates | Yes | (r ) Yes | Yes | https://updates.suse.com/SUSE/Updates/SLE-RPI/12-SP2/aarch64/update?jc_rc9ZD... roger@acme:~/source> I tried to see what else may be in https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64, but access is not allowed. I am guessing access to the repositories are restricted to those with a license. But I thought that the Raspberry Pi3 SLES came with a one year license. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Roger Oberholtzer
On Tue, Dec 13, 2016 at 10:50 AM,
wrote: What repos are enabled? For x86_64 most -devel packages are in SDK repo.
If thats not enough there is the Backports repo (aka SUSE Package Hub) with more software in Leap/Tumbleweed quality.
The ARCH is aarch64.
Yes, just wanted to say: I don't know how it is for RasPi, only for x86_64.
I see these, which were added when I registered the install:
# | Alias | Name | Enabled | GPG Check | Refresh | URI --
+---------------------------------------------------------------------------------------------------
+----------------------------------+---------+-----------+---------
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12- SP2-RPI-Debuginfo-Pool | SLES12-SP2-RPI-Debuginfo-Pool | No | ---- | No | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/ product_debug?
gaPTTFj0yRrzXe77mKVqRWDEYlv9Numi3p-3NDewhTGMtaXEGO0HR34mulUp7g_KOz23bxuRRBeaSNEqC-
xhq_eaBPn49yj98EeH5VxlhMHDx_faiPdBLyArl9U4exJBHPxA1a4B0HwXS11VabpK6JE 2 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12- SP2-RPI-Debuginfo-Updates | SLES12-SP2-RPI-Debuginfo-Updates | No | ---- | Yes | https://updates.suse.com/SUSE/Updates/SLE-RPI/12-SP2/aarch64/ update_debug? mbxQQQ6xcEb0NQRXkaOgLIijHfKHwMXhcnGfLRsobHk9F9GkwLPTBuMmdv8wuXcNNndy- yNUP6M8YhpsTcrgcRjBcfR- es5nZUoN4mj8Q22AHOOZ8t1uZ6Jefq0lpafehChD7Xsq1avAJ4qJ6iIk 3 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12- SP2-RPI-Pool | SLES12-SP2-RPI-Pool | Yes | (r ) Yes | No | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/ aarch64/product?
BjDiOXwK4eARGgTJcV9Xk_S1Sb1yiygTDAA7PwKe2t15M1YKzmiaSqzUKfD-7kacLPijhxRgmPzkXKbspffKZdX0Dk8w740jsfOWB9OoeHx9IjT1EPMoq5SrXHPPBe5LZm7JKU6aKAF5A9s
4 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12- SP2-RPI-Source-Pool | SLES12-SP2-RPI-Source-Pool | No | ---- | No | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/ product_source? WSb_6x9C9EZ4eQlsuxdY9qzzfb-6Q7ud_n-4veYi07boh6nQF0o_8SpnKxVhjBFQzD-
Ho4IJbDqDL4iQZHuQPhpJ2f_kRTwhhPqg3AXPZg_4MSnh1f2L6uT-7qtahggMyqMLXf1vf2abcyJBd_hpFFJc
5 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12- SP2-RPI-Updates | SLES12-SP2-RPI-Updates | Yes | (r ) Yes | Yes | https://updates.suse.com/SUSE/Updates/SLE-RPI/12-SP2/ aarch64/update?jc_rc9ZDFrLlCTrUk8jNpdLahEb0XQGFqyRFr6wzMa9gLgWDS- fIcP1Z8-wL5PLA-
zJcUo4gZi1crSDJQjpaDMzcvspjs6zBJvdg8iHPfjyfHWOm_F5SACPk5bsS1r2VD1nML1J88tHm
roger@acme:~/source>
I tried to see what else may be in https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64, but access is not allowed.
I am guessing access to the repositories are restricted to those with a license. But I thought that the Raspberry Pi3 SLES came with a one year license.
Judging from your repos: You are registered. Did you have to type in a code or did you just use a image and its preregistered? Disclaimer: I don't know if this works for RasPi, but x86_64 and its worth a try. To find Extensions and Modules, start: yast2 repositories Add Repository Check "Extensions and Modules from Registration Server..." and click Next Then you see all available extensions/modules. For some you might need a special license, but SDK should be included. Every extension/module will add you a Pool and a Update repo. Cheers! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, 2016-12-13 at 11:06 +0100, Roger Oberholtzer wrote:
On Tue, Dec 13, 2016 at 10:50 AM,
wrote: What repos are enabled? For x86_64 most -devel packages are in SDK repo.
If thats not enough there is the Backports repo (aka SUSE Package Hub) with more software in Leap/Tumbleweed quality.
The ARCH is aarch64.
Same as x86_64, -devel packages are on the SDK.
I see these, which were added when I registered the install:
<snip>
I tried to see what else may be in https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64, but access is not allowed.
I am guessing access to the repositories are restricted to those with a license. But I thought that the Raspberry Pi3 SLES came with a one year license.
Did you register? What does SUSEConnect --list-extensions show? -Scott
On Tue, Dec 13, 2016 at 11:51 AM, Scott Bahling
Did you register? What does SUSEConnect --list-extensions show?
I have registered and entered a code. That is when the repos that I have were added. No extensions were listed by SUSEConnect. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 13, 2016 at 11:29 AM,
Judging from your repos: You are registered.
Yes. I entered a code and then these repos were added.
Did you have to type in a code or did you just use a image and its preregistered?
Disclaimer: I don't know if this works for RasPi, but x86_64 and its worth a try.
To find Extensions and Modules, start: yast2 repositories Add Repository Check "Extensions and Modules from Registration Server..." and click Next Then you see all available extensions/modules. For some you might need a special license, but SDK should be included. Every extension/module will add you a Pool and a Update repo.
I selected that. I got a message that it was contacting a server. The list was empty. I deselected something about betas jic. But that made no difference. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On mardi, 13 décembre 2016 11.06:04 h CET Roger Oberholtzer wrote:
On Tue, Dec 13, 2016 at 10:50 AM,
wrote: What repos are enabled? For x86_64 most -devel packages are in SDK repo.
If thats not enough there is the Backports repo (aka SUSE Package Hub) with more software in Leap/Tumbleweed quality.
The ARCH is aarch64.
I see these, which were added when I registered the install:
# | Alias
| Name |
Enabled | GPG Check | Refresh | URI --+------------------------------------------------------------------------- --------------------------+----------------------------------+---------+---- -------+---------+---------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- -------------------- 1 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2 -RPI-Debuginfo-Pool | SLES12-SP2-RPI-Debuginfo-Pool | No | ---- | No | | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/product_debu | g?gaPTTFj0yRrzXe77mKVqRWDEYlv9Numi3p-3NDewhTGMtaXEGO0HR34mulUp7g_KOz23bxuR | RBeaSNEqC-xhq_eaBPn49yj98EeH5VxlhMHDx_faiPdBLyArl9U4exJBHPxA1a4B0HwXS11Vab | pK6JE 2 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2 -RPI-Debuginfo-Updates | SLES12-SP2-RPI-Debuginfo-Updates | No | ---- | Yes |
https://updates.suse.com/SUSE/Updates/SLE-RPI/12-SP2/aarch64/update_debug?mb xQQQ6xcEb0NQRXkaOgLIijHfKHwMXhcnGfLRsobHk9F9GkwLPTBuMmdv8wuXcNNndy-yNUP6M8Yh psTcrgcRjBcfR-es5nZUoN4mj8Q22AHOOZ8t1uZ6Jefq0lpafehChD7Xsq1avAJ4qJ6iIk 3 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2 -RPI-Pool | SLES12-SP2-RPI-Pool | Yes | (r ) Yes | | No | | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/product?BjD | iOXwK4eARGgTJcV9Xk_S1Sb1yiygTDAA7PwKe2t15M1YKzmiaSqzUKfD-7kacLPijhxRgmPzkX | KbspffKZdX0Dk8w740jsfOWB9OoeHx9IjT1EPMoq5SrXHPPBe5LZm7JKU6aKAF5A9s 4 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2 -RPI-Source-Pool | SLES12-SP2-RPI-Source-Pool | No | ---- | No | | https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64/product_so | urce?WSb_6x9C9EZ4eQlsuxdY9qzzfb-6Q7ud_n-4veYi07boh6nQF0o_8SpnKxVhjBFQzD- | Ho4IJbDqDL4iQZHuQPhpJ2f_kRTwhhPqg3AXPZg_4MSnh1f2L6uT-7qtahggMyqMLXf1vf2a | bcyJBd_hpFFJc 5 | SUSE_Linux_Enterprise_Server_for_the_Raspberry_Pi_12_SP2_aarch64:SLES12-SP2 -RPI-Updates | SLES12-SP2-RPI-Updates | Yes | (r ) Yes |
Yes | https://updates.suse.com/SUSE/Updates/SLE-RPI/12-SP2/aarch64/update?jc_rc9Z DFrLlCTrUk8jNpdLahEb0XQGFqyRFr6wzMa9gLgWDS-fIcP1Z8-wL5PLA-zJcUo4gZi1crSDJQjp aDMzcvspjs6zBJvdg8iHPfjyfHWOm_F5SACPk5bsS1r2VD1nML1J88tHm roger@acme:~/source>
I tried to see what else may be in https://updates.suse.com/SUSE/Products/SLE-RPI/12-SP2/aarch64, but access is not allowed.
I am guessing access to the repositories are restricted to those with a license. But I thought that the Raspberry Pi3 SLES came with a one year license.
I determine that under openSUSE you need to install xproto-devel package for the keysym.h Aren't there available in the Source Pool ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 13, 2016 at 12:18 PM, Bruno Friedmann
I determine that under openSUSE you need to install xproto-devel package for the keysym.h
Aren't there available in the Source Pool ?
Nope. There are very few -devel packages there. Installing them was my first thought. But I cannot find them! Perhaps SUSE do not expect anyone to compile anything for this test release and only install what they have made available? I can't find any statement of this. SUSE (at least since the advent of openSUSE) is not something we usually develop for. So I don't have all the details sorted yet... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 13, 2016 at 01:07:37PM +0100, Roger Oberholtzer wrote:
On Tue, Dec 13, 2016 at 12:18 PM, Bruno Friedmann
wrote: I determine that under openSUSE you need to install xproto-devel package for the keysym.h
Aren't there available in the Source Pool ?
Nope. There are very few -devel packages there. Installing them was my first thought. But I cannot find them!
Perhaps SUSE do not expect anyone to compile anything for this test release and only install what they have made available? I can't find any statement of this.
SUSE (at least since the advent of openSUSE) is not something we usually develop for. So I don't have all the details sorted yet...
After you register it, try adding the SDK extension. The SDK extension should have been added, but was done only halfway. And yes, the intention is to have this as enablement/development platform. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 13, 2016 at 1:14 PM, Marcus Meissner
After you register it, try adding the SDK extension.
The SDK extension should have been added, but was done only halfway.
And yes, the intention is to have this as enablement/development platform.
Ciao, Marcus
In yast, when adding repos, I checked Check "Extensions and Modules from Registration Server...". I got a message that it was getting the list from a server. In the page it makes after this, there is nothing listed. I am guessing that list is where I should find an SDK extension? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 13.12.2016 12:04, Roger Oberholtzer wrote:
On Tue, Dec 13, 2016 at 11:51 AM, Scott Bahling
wrote: Did you register? What does SUSEConnect --list-extensions show?
I have registered and entered a code. That is when the repos that I have were added.
No extensions were listed by SUSEConnect.
Hi Roger, unfortunately there are no extensions (like SDK) released by SUSE for the Raspberry Pi product. You would need a full SLES for ARM64 license for that. Greetings -- Thomas Schmidt (tschmidt [at] suse.de) SUSE Linux GmbH :: Research & Development :: SUSE Customer Center "Don't Panic", Douglas Adams (1952 - 11.05.2001) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, 2016-12-13 at 12:04 +0100, Roger Oberholtzer wrote:
On Tue, Dec 13, 2016 at 11:51 AM, Scott Bahling
wrote: Did you register? What does SUSEConnect --list-extensions show?
I have registered and entered a code. That is when the repos that I have were added.
No extensions were listed by SUSEConnect.
Investigating this internally at SUSE because it doesn't seem right. Might be an oversight. In the meantime, what exactly do you want to do? This is the open build service mailing list. If you which build some packages in OBS for aarch64 on SLES 12 SP2, that you can do now as OBS has (or at least should have) all packages required for building. If missing something, report it here and it will be addressed. If you want to build locally without using OBS, then yes, you would need the -devel packages. Stay tuned on that. -Scott
On mardi, 13 décembre 2016 16.33:12 h CET Roger Oberholtzer wrote:
On Tue, Dec 13, 2016 at 1:14 PM, Marcus Meissner
wrote: After you register it, try adding the SDK extension.
The SDK extension should have been added, but was done only halfway.
And yes, the intention is to have this as enablement/development platform.
Ciao, Marcus
In yast, when adding repos, I checked Check "Extensions and Modules from Registration Server...". I got a message that it was getting the list from a server. In the page it makes after this, there is nothing listed. I am guessing that list is where I should find an SDK extension?
Can you try to just keep the reply to list (no need to receive duplicates) :-) Yes I know how terrible some provider are .... -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 13, 2016 at 5:30 PM, Scott Bahling
On Tue, 2016-12-13 at 12:04 +0100, Roger Oberholtzer wrote:
No extensions were listed by SUSEConnect.
Investigating this internally at SUSE because it doesn't seem right. Might be an oversight.
In the meantime, what exactly do you want to do? This is the open build service mailing list. If you which build some packages in OBS for aarch64 on SLES 12 SP2, that you can do now as OBS has (or at least should have) all packages required for building. If missing something, report it here and it will be addressed.
What I really want to do is install openSUSE on the PI3. I have tried the images on OBS and they simply never work. So, I tried SLES. And it works great. I suspect SLES, if it is ever really released for the Raspberry, would be priced such that using it on the Raspberry might be difficult. I don't know what the plans are for this. I suspect it is just an interesting exercise more than the start of a new product. But I have not seen a discussion of this. I want to compile some of our libraries to run on the Raspberry. They are not in OBS as they are very local in interest (not many openSUSE users collecting data from lasers, accelerometers, GPS and such devices). And, some use proprietary libraries that we cannot place on OBS. Part of this exercise is to make those dependencies conditional. I know that I could probably do the same as a cross-compile on my desktop openSUSE. But, eventually, I need to test them. So I thought, why not see what the Raspberry can do?
If you want to build locally without using OBS, then yes, you would need the -devel packages. Stay tuned on that.
I will. I also thought that SUSE probably like people to try different things so they can see what they may have overlooked in making the Raspberry release. I'm curious if the openSUSE Raspberry release might improve as a result of the SLES release. I do not know how much they cooperate. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, Dec 14, 2016 at 8:51 AM, Roger Oberholtzer
What I really want to do is install openSUSE on the PI3.
Have you seen https://en.opensuse.org/HCL:Raspberry_Pi3#Installing_the_64-bit_openSUSE_Lea... ? Leap works just fine on my Pi 3. I did not have time to run it through all the tests, but I found no problems so far. Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, Dec 14, 2016 at 8:29 AM, Robert Munteanu
On Wed, Dec 14, 2016 at 8:51 AM, Roger Oberholtzer
wrote: What I really want to do is install openSUSE on the PI3.
Have you seen https://en.opensuse.org/HCL:Raspberry_Pi3#Installing_the_64-bit_openSUSE_Lea... ?
Leap works just fine on my Pi 3. I did not have time to run it through all the tests, but I found no problems so far.
I have tried the following: openSUSE-13.1-ARM-JeOS-raspberrypi.armv7l-1.12.1-Build38.15.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.06-Build6.1.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.armv7l-2016.04.06-Build2.1.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.06.28-Build1.5.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.08.20-Build1.4.raw.xz And they do not even boot. What has worked is: SLES-12-SP2-ARM-X11-raspberrypi3_aarch64.aarch64-2016.10.04-GM.raw.xz I will try a newer openSUSE image to see if it works. Exactly which image have you used? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, Dec 14, 2016 at 10:18 AM, Roger Oberholtzer
On Wed, Dec 14, 2016 at 8:29 AM, Robert Munteanu
wrote: On Wed, Dec 14, 2016 at 8:51 AM, Roger Oberholtzer
wrote: What I really want to do is install openSUSE on the PI3.
Have you seen https://en.opensuse.org/HCL:Raspberry_Pi3#Installing_the_64-bit_openSUSE_Lea... ?
Leap works just fine on my Pi 3. I did not have time to run it through all the tests, but I found no problems so far.
I have tried the following:
openSUSE-13.1-ARM-JeOS-raspberrypi.armv7l-1.12.1-Build38.15.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.06-Build6.1.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.armv7l-2016.04.06-Build2.1.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.06.28-Build1.5.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.08.20-Build1.4.raw.xz
And they do not even boot. What has worked is:
SLES-12-SP2-ARM-X11-raspberrypi3_aarch64.aarch64-2016.10.04-GM.raw.xz
I will try a newer openSUSE image to see if it works. Exactly which image have you used?
I tried a Leap 42.2 image, I think it was one similar to openSUSE-Leap42.2-ARM-JeOS-raspberrypi3.aarch64-2016.11.25-Build1.9.raw.xz Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (7)
-
Bruno Friedmann
-
Marcus Meissner
-
Robert Munteanu
-
Roger Oberholtzer
-
Scott Bahling
-
Thomas Schmidt
-
vetter@physik.uni-wuerzburg.de