- openSUSE ARM

[opensuse-arm] Re: [obs submit-request 144281] devel:Factory:ARM/v8: created by Guillaume_G
by Adrian Schröter 06 Dec '12

06 Dec '12

Hi Guillaume, Am Mittwoch, 5. Dezember 2012, 10:11:02 schrieb guillaume.gardet(a)opensuse.org: > > home:Guillaume_G:branches:devel:Factory:ARM/v8 -> devel:Factory:ARM/v8 > > > https://build.opensuse.org/request/show/144281 > > Description: Fix armv7 using new flag (hardfp=on) Your sources did still fail (not checked why), but I accepted this request nevertheless. I have added you also as maintainer in devel:Factory:ARM. Hopefully this helps to collaborate more on our arm fixes :) thanks a lot for all your work so far! adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] openSUSE:Factory:ARM cleanup
by Adrian Schröter 05 Dec '12

05 Dec '12

Hi, walking through the additional packages of our official openSUSE:Factory:ARM project: Some of them got just have removed, because they got merged into factory meanwhile. Some more arm changes are at least merged into devel projects and needs to be submitted to factory: * qemu (Andreas, can you submit?) * python3 (asked the maintainer already, it is a generic failure) Quite some more packages were in unclear or only half-fixed state, but I considered it as not harmful when moving them to the new project: devel:Factory:ARM We agreed that this project should be used for working on arm specific fixes and stuff should be submitted to devel projects. openSUSE:Factory:ARM should stay as clean as possible, only exception are temporary package fixes which are needed to unbreak the general build of signification number of other packages (to be specified ;) Currently we basically still following packages in there: * Current kernel stack. Can we move it to the devel:Factory:ARM as well? We may need to add the repo to some appliances. * gcc stack due to the thumb/gcj problem => my job * some additional packages not yet in factory. - u-boot*: can we submit them now? - qemu-accel stuff => should be possible to submit it as well IMHO - x-loader-omap3beagle - xf86-video-sisusb both should be either go to official devel projects and factory or to a :Contrib: project. Dirk/Alex can you do that? - JeOS image descriptions. We need to find a place for them. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] Updating images built from Contrib sources
by Ciaran Farrell 05 Dec '12

05 Dec '12

I see that the openSUSE image for the CuBox at http://download.opensuse.org/ports/armv7hl/distribution/12.2/images/contrib… is still the original 12.2 version. That means that it doesn't have the various fixes for booting. How can we update the image there from the sources in: https://build.opensuse.org/package/show?package=JeOS-cubox&project=openSUSE… -- Ciaran Farrell, Attorney at Law SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE 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

3 3

[opensuse-arm] PI
by Daniel Hodges 04 Dec '12

04 Dec '12

I am not sure if this went through I sent one to the artwork team that didnt not go through, so I am sorry if I am repeating this. I need some help with getting openSUSE on the Raspberry PI, I have tried to look for this on google but I have not had much luck. I am going to be working Scale this year with and I was wanting to show case openSUSE on the Raspberry Pi. So any help would be appreciated Thank you -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] Trigger rebuild of all perl-* packages for armv5 Factory
by Guillaume Gardet 03 Dec '12

03 Dec '12

Hi, Someone could trigger a rebuild of all perl-* packages in succeded state for armv5 Factory, since they have been built with perl 5.16.1 and now, 5.16.2 is in use. So, others perl-* packages are unresolvable since perl 5.16.1 is no more available. And lots of packages are also blocked (kiwi for example). Moreover, perl 5.16.2 fails to build for armv7 factory, but I don not know how to fix it. Any idea? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] armStoneA8: Failed to mount /dev
by Andreas Färber 02 Dec '12

02 Dec '12

Hello, On the armStoneA8 board, using NBoot V14 and U-Boot, I'm trying to boot the downstream 3.3.7 kernel (BSP V1.1) from SD with a LimeJeOS rootfs on SD. I had to reconfigure the kernel with CONFIG_LBDAF to mount the ext3[*] rootfs r/w. This is what I get now: [...] mmc0: new high speed SDHC card at address b368 IPv6 over IPv4 tunneling driver mmcblk0: mmc0:b368 NCard 7.48 GiB NET: Registered protocol family 17 can: controller area network core (rev 20090105 abi 8) mmcblk0: p1 NET: Registered protocol family 29 can: raw protocol (rev 20090105) can: broadcast manager protocol (rev 20090105 t) Registering the dns_resolver key type VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 s3c-rtc s3c64xx-rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p1): using internal journal EXT3-fs (mmcblk0p1): recovery complete EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:1. Freeing init memory: 148K Failed to mount /dev: No such device Our rootfs definitely contains /dev, so what is this complaining about? Thanks, Andreas [*] U-Boot seemed to hang loading zImage from ext4. -- 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

3 6

[opensuse-arm] Re: [obs submit-request 143674] openSUSE:12.2:ARM:Contrib:Cubox/JeOS-cubox: created by babelworx
by Alexander Graf 02 Dec '12

02 Dec '12

On 30.11.2012, at 14:59, Ciaran Farrell wrote: > > > home:babelworx:branches:openSUSE:12.2:ARM:Contrib:Cubox/JeOS-cubox -> openSUSE:12.2:ARM:Contrib:Cubox/JeOS-cubox > > > https://build.opensuse.org/request/show/143674 This version is missing the .tgz change, no? Alex > > Description: this revision boots for me > > > To REVIEW against the previous version: > osc request show --diff 143674 > > To ACCEPT the request: > osc request accept 143674 --message="reviewed ok." > > To DECLINE the request: > osc request decline 143674 --message="declined for reason xyz (see ... for background / policy / ...)." > > To REVOKE the request: > osc request revoke 143674 --message="retracted because ..., sorry / thx / see better version ..." > -- > Hermes messaging (http://hermes.opensuse.org) > openSUSE Build Service (https://build.opensuse.org/) > Collaboration: http://en.opensuse.org/Build_Service/Collaboration > -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] owncloud for ARM
by endym 02 Dec '12

02 Dec '12

Hi all, I want to use owncloud (http://www.owncloud.org) on a Pandaboard. Since "zypper se owncloud" does not found anything and the OBS does not provide an ARM version, I guess I have to install it manually, right? Best regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] Network interface not coming up at boot time on CuBox
by Ciaran Farrell 30 Nov '12

30 Nov '12

One thing I've been noticing on the CuBox is that, at each reboot, the network interface is not brought up. Strangely, the system tries to set up ethX where X increments by one at each reboot. For example, I now see the following in /var/log/boot.log: network[398]: Setting up (localfs) network interfaces: network[398]: lo network[398]: lo IP address: 127.0.0.1/8 network[398]: ..done eth4 network[398]: No configuration found for eth4 network[398]: ..unusedWaiting for mandatory devices: eth0 network[398]: 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 [...] network[398]: eth0 No interface found network[398]: ..failed The last time, eth3 was involved; before that eth2. Next time it will be eth5. In yast (network settings), there were two interfaces - eth0 and eth4 (not configured). I deleted eth0 and configured eth4 (basically just set it to dhcp rather than static). After saving, the network was back up again. Any idea what is causing this? Ciaran -- Ciaran Farrell, Attorney at Law SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE 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

5 37

[opensuse-arm] GCC 4.7, cross-*-icecream-backend and others are broken in Factory
by Guillaume Gardet 30 Nov '12

30 Nov '12

Hi, GCC 4.7, cross-*-icecream-backend and others are broken in Factory. See: https://build.opensuse.org/project/monitor?arch_armv7l=1&broken=1&defaults=… Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0