openSUSE ARM May 2013

arm@lists.opensuse.org

17 participants
17 discussions

by J.Witvliet＠mindef.nl

-----Original Message----- You complained about no browser and no email client in your Xfce Internet menu. I am telling you as an Xfce arm user, both are installable (and then show up there) if you actually look for them. The Xfce images are just as minimal as the JeOS images in that they do not contain the whole contents of an openSUSE x86 .iso image. Sorry if that hint on how to resolve the issue you complained about offends you. Andreas -----Original Message----- Hi Andreas, I followed the instructions from: https://en.opensuse.org/HCL:ARMChromebook And at point 4) Download the latest image at http://download.opensuse.org/repositories/devel:/ARM:/12.3:/Contrib:/Chrome… and choose between: JeOS image (1GB) for a minimal system openSUSE-12.3-ARM-JeOS-chromebook-*.raw.xz or XFCE image (4GB) for a graphical system openSUSE-12.3-ARM-XFCE-chromebook-*.raw.xz I opted for the graphical image. Everyone who has been using suselinux, openSUSE, sles or sled knows how to install things. That's beside the point. If you opt for the "just enough" image, it's obvious that it is indeed just enough to install whatever you need/like. I just wanted to express my surprise that the "graphical system openSUSE-12.3-ARM-XFCE-chromebook-*.raw.xz" does include gimp and a softphone, while missing more essential parts. Could very well be a well thought of decision, no problems with that. Perhaps I was mislead by "XFCE image 4GB" and it might be wiser to rename it to: "Just enough X" When examining the size of the image (497MB), obviously not everything fits is there, though the name suggest a sort of "live arm image", just like the general openSUSE live (iso) images.... So absolutely no problem with that. Actually, what did worry me, was the amount of time needed to startup... At one point I feared that something was wrong with the image, despite the correct sha256 hash. Let me note that I transferred the image to an USB-stick, not a sd-disk. I don't expect something like the original OS, which is probably 200% tuned for turbo-startup. Any other experiences regarding chromebook startup time? Hans ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

7 years, 10 months

[opensuse-arm] Applications can't find libraries in /usr/local/lib

by Sid Boyce

openSUSE 12.3 on ODROID-X. I reinstalled glibc but still getting the problem. ODROID-X:/3/ODROID-X/SUSE/hamlib # ldd /usr/local/bin/rigctl libhamlib.so.2 => not found libltdl.so.7 => /usr/lib/libltdl.so.7 (0xb6f6c000) libm.so.6 => /lib/libm.so.6 (0xb6ef9000) libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0xb6eec000) libdl.so.2 => /lib/libdl.so.2 (0xb6edf000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6eb5000) libpthread.so.0 => /lib/libpthread.so.0 (0xb6e95000) libc.so.6 => /lib/libc.so.6 (0xb6d5d000) /lib/ld-linux-armhf.so.3 (0xb6f96000) libusb-1.0.so.0 => /usr/lib/libusb-1.0.so.0 (0xb6d47000) librt.so.1 => /lib/librt.so.1 (0xb6d38000) # cat /etc/ld.so.conf /usr/local/lib include /etc/ld.so.conf.d/*.conf # /lib64, /lib, /usr/lib64 and /usr/lib gets added # automatically by ldconfig after parsing this file. # So, they do not need to be listed. # ldconfig -v /usr/local/lib: librtlsdr.so.0 -> librtlsdr.so.0.0.0 libcodec2.so.0 -> libcodec2.so.0.0.0 libhamlib++.so.2 -> libhamlib++.so.2.1.0 libhamlib.so.2 -> libhamlib.so.2.1.0 ODROID-X:/3/ODROID-X/SUSE/hamlib # rigctl rigctl: error while loading shared libraries: libhamlib.so.2: cannot open shared object file: No such file or directory ODROID-X:/3/ODROID-X/SUSE/hamlib # LD_LIBRARY_PATH=/usr/local/lib rigctl -l | less Rig # Mfg Model Version Status 1 Hamlib Dummy 0.5 Beta 2 Hamlib NET rigctl 0.3 Beta 101 Yaesu FT-847 0.5 Beta 103 Yaesu FT-1000D 0.0.6 Alpha 104 Yaesu MARK-V FT-1000MP 0.0.5 Alpha 105 Yaesu FT-747GX 0.4.1 Beta ldconfig -p also lists it in the cache. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 10 months

[opensuse-arm] Issues with Arndale

by Andrew Wafaa

Hi All, I've been contacted by a company that is trying to use openSUSE on the Arndale and have encountered an issue. It looks like for some reason the single zImage isn't supported. I'm unavailable atm to look further as I'm at a conference. If someone could have a look and advise I will happily forward on fixes etc. Thanks, Andy ====== I'm trying to use the latest opensuse image for the arndale board: http://download.opensuse.org/repositories/devel:/ARM:/12.3:/Contrib:/Arndal… But I'm unable to go after U-boot: May 14 15:41:27.333982 Loading file "uEnv.txt" from mmc device 0:1 May 14 15:41:27.348625 ** File not found uEnv.txt May 14 15:41:27.353010 ext2load - load binary file from a Ext2 filesystem May 14 15:41:27.353029 May 14 15:41:27.353632 Usage: May 14 15:41:27.359233 ext2load <interface> <dev[:part]> [addr] [filename] [bytes] May 14 15:41:27.364093 - load binary file 'filename' from 'dev' on 'interface' May 14 15:41:27.368299 to address 'addr' from ext2 filesystem May 14 15:41:27.371872 Loading file "boot.scr" from mmc device 0:1 May 14 15:41:27.383901 1646 bytes read May 14 15:41:27.387415 Running bootscript from mmc0 ... May 14 15:41:27.390125 ## Executing script at 40007000 May 14 15:41:27.396179 kerneladdr=0x40007000 May 14 15:41:27.398516 ramdiskaddr=0x4f000000 May 14 15:41:27.404527 mmc0 is current device May 14 15:41:27.409725 Loading file "boot/linux.vmx" from mmc device 0:1 May 14 15:41:28.092472 3743856 bytes read May 14 15:41:28.096727 Loading file "boot/initrd.uboot" from mmc device 0:1 May 14 15:41:33.938595 33233176 bytes read May 14 15:41:33.943601 Loading file "exynos5250-arndale.dtb" from mmc device 0:1 May 14 15:41:33.964079 16936 bytes read May 14 15:41:33.967523 Unknown command 'bootz' - try 'help' If I replace bootz by bootm with: setenv boottype bootm I'm able to boot OpenSuse. ====== -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 10 months

[opensuse-arm] Demo of openSUSE on ARM

by Guillaume Gardet

Hi, We have an openSUSE booth at "Solutions Linux" [0] in 2 weeks and I would like to make some ARM demo. Of course, I will bring the Chromebook but I would like to make a demo of openstack on Arndale board (or another one) if it is feasible. Any kernel/software repo/image ready or not? If you have any suggestion to show some cool stuff, let me know! ;) Guillaume [0]: https://en.opensuse.org/openSUSE:Solutions_Linux_2013 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 10 months

[opensuse-arm] Building using native builders

by Andrew Wafaa

Hi, I'm trying to verify some build failures are not as a result of using qemu, but for the life of me I can't work out how to get things built on the arndales rather than the x86 hosts. I would build locally on my chromebook, but I appear to have forgotten how. Problem is I have three packages that I'm trying to build and one of those three is a dep for the others. What's the best way to go about it? How can one get projects to build using the native builders? Thanks, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 10 months

[opensuse-arm] New Arndale board - Exynos Octa 5410 (big.LITTLE arch)

by Guillaume Gardet

Hi, just for information, a new Arndale board is coming. See: http://www.howchip.com/shop/item.php?it_id=ARNOctaA It is based on an Exynos Octa 5410 with a big.LITTLE arch. No price yet, but seems very interesting. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 10 months

Re: [opensuse-arm] chromebook

by Andreas Färber

Please keep the list CC'ed. Am 26.05.2013 01:33, schrieb Hans Witvliet: > -----Original Message----- > From: Andreas Färber <afaerber(a)suse.de> > To: J.Witvliet(a)mindef.nl > Cc: opensuse-arm(a)opensuse.org, hwit(a)a-domani.nl > Subject: Re: [opensuse-arm] chromebook > Date: Sat, 25 May 2013 15:31:10 +0200 > > Hi, > > Am 16.05.2013 16:11, schrieb J.Witvliet(a)mindef.nl: >> Just been playing with a chromebook. >> Looks great under xfce. >> Touchpad should be avoided: I guess I have to find an ordinary mouse somewhere. >> Also networkmanager worked OK! >> >> I was surprised to find gimp on it, but I didn't dare to start that beast up. >> What made me wonder, is that (at least from the xfce-menu-thingy) there is little under "Internet". >> I did see a voip-client, bit I missed any email-client or even a webbrowser. > > Sounds as if you're new to openSUSE? From the minimal JeOS image you can > use the usual YaST and zypper tools to install additional packages such > as Thunderbird or Firefox. :) > > Andreas > > -----Original Message----- > > You can say a lot about me Andreas, though not that i'm new to SuSE. > I started at 6.3 Great, but not obvious from your message: > If you read my message again, you would see that i did __NOT__ installed > jeos, but an complete X environment. If you read your message again, you did __NOT__ say *how* you installed xfce. On my AC100 I installed it from a JeOS rootfs via the regular openSUSE xfce pattern. There is nothing special about arm there, except that one may need to fiddle with fbdev xorg config. > Furthermore, if you think again, as i said that i did find a voip client > and even GIMP, these are things one should certainly not expect in an > "just enough os". On the contrary, GIMP is just too much for ARM ;-) > The inclusion of these two surprised me. You complained about no browser and no email client in your Xfce Internet menu. I am telling you as an Xfce arm user, both are installable (and then show up there) if you actually look for them. The Xfce images are just as minimal as the JeOS images in that they do not contain the whole contents of an openSUSE x86 .iso image. Sorry if that hint on how to resolve the issue you complained about offends you. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 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

7 years, 11 months

[opensuse-arm] chromebook

by J.Witvliet＠mindef.nl

Hi, Just been playing with a chromebook. Looks great under xfce. Touchpad should be avoided: I guess I have to find an ordinary mouse somewhere. Also networkmanager worked OK! I was surprised to find gimp on it, but I didn't dare to start that beast up. What made me wonder, is that (at least from the xfce-menu-thingy) there is little under "Internet". I did see a voip-client, bit I missed any email-client or even a webbrowser. When your machine remains dual-bootable, one might say: switch back to chrome-OS, but in case you want the book to be single-boot with Gecko...... I presume my usb-stick isn't the fastest device, because start-up-time is, eh.. not for hasty people ;-))) Good work anyway! ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 11 months

[opensuse-arm] Upgrade from 12.2 to 12.3

by endym

Hi all! Is it possible to upgrade my pandaboard installation (12.2 image) to the current 12.3 version? Regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 11 months

[opensuse-arm] qemu package split

by Andreas Färber

Hi everyone, Ever since I've been involved with openSUSE, the qemu package has had an unusual setup of configuring and building twice: once for the regular binaries, then moving them to a temporary directory and finally configuring and building statically for the qemu-linux-user subpackage, used for arm chroot builds among others. In our quest to finally unify the kvm and qemu packages, I have updated the qemu package to 1.5.0 (SR#176307 pending for Factory) and have subsequently prepared to split the qemu.spec[.in] to build qemu-linux-user in a separate linked package similar to gcc or kernel: https://build.opensuse.org/request/show/176308 AFAICS the RPM package name stays the same that way, so armv7/armv5el should hopefully be unaffected and the change transparent to end users. A nice side-effect is that we can limit the SLE_11_SP2 build breakage to qemu-linux-user package (BNC#820754: SLE_11_SP2 is missing a glibc maintenance update for static builds). Also the dependencies for qemu-linux-user get significantly less and no *-static deps for qemu. If I don't hear any objections, I'll accept the changed qemu package into Virtualization project later today and will setup qemu-linux-user package there. For Factory this is a heads-up that we will require to copy/setup the additional qemu-linux-user package once we've tidied up and submit the package split to Factory at some future point towards 13.1. Further 13.1 work still under discussion is to create further subpackages inside qemu so that the kvm package won't need to depend on mips etc. emulation binaries. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 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

7 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

openSUSE ARM May 2013