[opensuse-arm] Re: openGL ES vs openGL on aarch64 for Qt

Hi Guillaume, I'm okay with aligning aarch64 more with x86_64.. the timing is however funny because Qt just announced that over the long run they will stop embracing OpenGL. > openGL ES is fine for armv6 and armv7, but I am thinking of switching aarch64 > from openGL ES to openGL as aarch64

Re: [opensuse-arm] Continuously rebuilt and tested Leap 15.1 images

Hi Fabian, Am Do., 24. Jan. 2019 um 13:43 Uhr schrieb Fabian Vogt : > The main difference is that decoupling ARM:Live from :ARM would allow > building, > testing and releasing images built with updates after Gold. Wouldn't that be done under openSUSE:Leap:15.1:Update:Images then instead? At

Re: [opensuse-arm] Re : VPP

Am Mi., 2. Jan. 2019 um 09:24 Uhr schrieb Guillaume GARDET : > > explicitly be tuned for a particular target platform. Then build the > > binary n times - one for each optimization target. That doesn't sound very appealing to me. > > The long term fix is to work with OSEC for example and make

[opensuse-arm] Factory/Tumbleweed for ARM: gcc8 rebuild running

Hi, as of this monday morning we have gcc8 in Factory:ARM (it entered x86 end of last week). a full rebuild of aarch64 and armv7l with that compiler is running, expect some delays in the publish of the next snapshot. hopefully this is finished by the end of this week. Greetings, Dirk -- To

Re: Re : Re: [opensuse-arm] Tests of ARM Leap 15.0

> >> OK. Where can I find it? I looked for it at the usual > >> http://download.opensuse.org/ports/aarch64/distribution/leap/ location, > >> but could not find it. I'd give it a try on a SoftIron OverDrive 1000.

Re: [opensuse-arm] armv7l tw updates? (was: armv6 tumbleweed updates?)

Hi, > > http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/ > > > > Last update was snapshot 20180319 but no updates since then. > Same is true for armv7... > > Anything got stuck? > Any updates on this? We managed to publish it once manually, currently we have massive performance

[opensuse-arm] Change to the rebuild behavior of openSUSE:Factory:ARM

Hi, We had a couple of issues related to getting a new build of Factory into openqa recently. This was partially caused by ARM not able to catch up with the check in frequency of x86. To some extend this was bad luck (the critial long running build job hitting the slowest / misconfigured worker

Re: [opensuse-arm] http://download.opensuse.org/ports/aarch64/debug/tumbleweed is missing

Hi Andreas, 2018-01-03 17:10 GMT+01:00 Andreas Schwab : > Still missing. I filed https://progress.opensuse.org/issues/29951 for you. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

[opensuse-arm] Nue OpenSUSE Build Service power outage / ARM

Hi all, due to a large area power cut planned for this Saturday (tomorrow) affecting the building the SUSE and openSUSE server rooms are hosted we're going to shut down the OBS ARM architecture workers later today in a controlled fashion in order to not have them a hard power loss when this

[opensuse-arm] Cargo bootstrap

Hi, is anyone working already on the rust/cargo bootstrap for armv6/v7/aarch64 ? I don't want to waste/duplicate work. TIA, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Tumbleweed AArch64 not publishing anymore?

2017-09-05 23:59 GMT+02:00 Dirk Müller <d...@dmllr.de>: > well,the interesting thing is that there aren't really any blocking > (all of the failing ones are blacklisted). and inbetween Dimstar > manually published ARM. not sure why. Ok, the current build is bein

[opensuse-arm] network issues in ARM build worker network (build.opensuse.org)

Hi, not sure for how long, but there were network issues due to a misconfiguration on the admin server in the ARM build network that caused almost all jobs to fail with things like "connect to opensuse-src:5252 timed out" and similar issues. I only stumbled over it because I was watching a few

Re: [opensuse-arm] Tumbleweed AArch64 not publishing anymore?

2017-08-28 10:09 GMT+02:00 Adrian Schröter : > aarch64 products are only published after success ... so I suppose the > failures there are blocking it: > > https://openqa.opensuse.org/group_overview/3 well,the interesting thing is that there aren't really any blocking (all of

Re: [opensuse-arm] Re: Converting products to the new system

Hi Adrian, 2017-07-12 13:29 GMT+02:00 Adrian Schröter : > It would just regulary break, because of changes in openSUSE:Factory. > > This makes only sense when we plan to submit the changes back to > openSUSE:Factory. Not sure I understand that. 90%+ of the changes we do are in

Re: [opensuse-arm] tumbleweed updates for armv6hl ?

Hi Ralph, 2017-07-11 13:48 GMT+02:00 BWC Illmensee GmbH - Ralph Gauer : > I'm using Rpi1 and Rpi2 with tumbleweed in several places as mini server for > OpenVPN, Hylafax (with USB-modem), DHCP, DNS (bind), Apache and NTP, > some of them even as SuSEFirewall2 with a

Re: [opensuse-arm] tumbleweed updates for armv6hl ?

Hi Ralph, 2017-07-05 15:13 GMT+02:00 BWC Illmensee GmbH - Ralph Gauer : > When will the armv6hl arch of tumbleweed get updates like for example the > current bind package, etc.? Unfortunately armv6hl is in a pretty bad state because it is still built in qemu

[opensuse-arm] [FYI] larger amount of rebuild on TW aarch64

Hi, in order to get rid of some older lib dependencies and enable ruby 2.4 stack I need to rebuild larger amounts of packages. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Aarch64 openQA workers are broken

Hi Stefan, 2017-06-17 12:12 GMT+02:00 Stefan Bruens : > obviously the os-autoinst package installed on the workers has been built > against perl 5.24.*1*, while the installed perl is 5.24.0. > > As a result, perl does not find the tinycv.pm module and fails to

[opensuse-arm] larger amount of rebuilds in Tumbleweed for aarch64/arm

Hi, as a result of https://news.opensuse.org/2017/06/01/gnu-compiler-collection-7-now-opensuse-tumbleweed-default/ I'll be doing a larger than usual amount of rebuilds for the ARM and AArch64 distributions in tumbleweed so that we're rebuilding everything that has been settling dust for a while.

Re: [opensuse-arm] Filesystem crashes with Leap 42.2 on rpi3

Hi Frank, 2017-04-09 12:01 GMT+02:00 Frank Schreiner : > and now it is the second time that the filesystem crashed in a few weeks. When > it happend the first time, I changed the SD Card to prevent HW errors. did you ever reboot the rpi after the first boot? did it have

Re: [opensuse-arm] Re: Attempt to run KIWI on unsupported architecture 'armv8l'

Hi Matwey, 2017-04-08 21:29 GMT+02:00 Matwey V. Kornilov : > 01.04.2015 12:54, Adrian Schröter пишет: > Dirk, could you please explain how to fix it? I am facing the same at my > private OBS instance while trying to build JeOS for 42.2:Ports. Well, I don't really

Re: [opensuse-arm] Raspberry Pi JeOS cleanups

Hi Andreas, I'd appreciate if you could check with the maintainer before changing links in a project that you're always pointing out that you're not maintaining, *especially* in non-Staging projects that are supposed to be stable. if you want to do a change, you're welcome to try it out in the

Re: [opensuse-arm] Raspberry Pi JeOS cleanups

Hi Andreas, 2016-10-18 12:21 GMT+02:00 Andreas Färber : > There is nothing to try out in a Staging project here, this is all about > creating JeOS-raspberrypi2 and JeOS-raspberrypi3 in Factory! That is completely unrelated. The point is that you're changing a project that is

Re: [opensuse-arm] JeOS structure and _links

Hi Fabian, > and the SRs are ready. However, due to the current structure > of _links in the ARM projects on OBS merging will probably > break some if not most of those, as told by afaerber. it only breaks those that have real modifications, which should be rare (modifications should be

Re: [opensuse-arm] openSUSE AArch64, 64k vs 4k PAGE_SIZE

Hi Alex, 2016-09-19 10:32 GMT+02:00 Alexander Graf : > Yes, but it's a can of worms that we have to open anyway unfortunately. > Systems are growing and I doubt 42 bits are going to get us very far. sure, I still prefer to have tests, and even tests that are passing over just

Re: [opensuse-arm] hanging armv7l builds?

Hi Adrian, > I can not see that, all armv7 workers are used (check the graphs at the > bottom). All workers that are *online* are being used. we have a lot more workers that need repair right now though. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To

Re: [opensuse-arm] hanging armv7l builds?

Hi Michael, > last days OBS was quite busy but currently the number of active build workers > is > below 200. yeah, there are network issues again in the obs transfer network, most jobs are failing to setup, which slows down the build results. This unfortunately needs to be fixed by a sysadmin

Re: [opensuse-arm] state of tumbleweed repositories - last update on 26-Jun-2016 20:09

Hi Ralph, > why the tumbleweed repositories at > http://download.opensuse.org/ports/armv6hl/ > and > http://download.opensuse.org/ports/armv7hl/ > had the last update on "26-Jun-2016 20:09"? No good reason, but we're currently waiting for the person who has access to the servers to fix

[opensuse-arm] Re: JFYI: armv7l kernel for Leap 42.2

Hi Matwey, >> According to Michal, OBS Kernel:openSUSE-42.2 repo should be built >> automatically for armv7hl once when armv7hl is enabled in >> openSUSE:Leap:42.2:Ports (listed in rpm/config.sh). > > kernel-source repo looks for Update project (not Ports): >

Re: [opensuse-arm] Tumbleweed Raspberry Pi2 i2c-tools not work

Hi, 2016-05-19 12:00 GMT+02:00 Денислав Радославов : > After two months (first report for this bug -forum and mailing list), > bcm2835 modules working fine, but i2c-tools again not working. Missing > packages python-smbus is big problem. Have ready packages, Is it so hard >

Re: [opensuse-arm] kdump on arm

Hey Matwey, 2016-05-20 22:10 GMT+02:00 Matwey V. Kornilov : > Is kdump supposed to work on armv7l? Which kernel should I use as kdump > kernel? kdumptool doesn't like -default for me: > > # kdumptool find_kernel > Kernel '/boot/vmlinux-4.6.0-1.gd9e67cc-default' is not

Re: [opensuse-arm] Leap 42.2 ARM: Ring 0 status

Hi Matwey, > Could you please take(aggregate) kernel-obs-build for > openSUSE:Leap:42.2:Ports [...] Thanks, I'm working on it (just returned from vacation today). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail:

Re: [opensuse-arm] RaspberryPi3 and Aarch64

>> Let me know what happens. I am using the 32bit image right now, but for sure >> 64bit is more interesting. :) > The file above shouldn't exist really. Why? its (supposed to be) the regular Tumbleweed image, which in theory after we sorted out the pending u-boot and raspberrypi-firmware image

Re: [opensuse-arm] Leap 42.2 ARM: Ring 0 status

Hi Matwey, > Could you please, remove the following from project config? It seems, > that the following is not required. > > # for bootstrap > Support: !rpmlint-Factory-strict !rpmlint-Factory Correct, those lines marked with "for bootstrap" were only there temorary to resolve a few

Re: [opensuse-arm] Raspberry Pi 1

Hi Duncan, 2016-05-12 8:59 GMT+02:00 Duncan Mac-Vicar P. : > https://gist.github.com/dmacvicar/de59bc59af24c027ba03f623cdccf4ef > > It looks like boot.scr is not passing init= correctly to the kernel. essential error message is: [2.832442] Initramfs unpacking failed:

Re: [opensuse-arm] Pine64 and RPi3

Hi Duncan, > I am trying to boot Tumbleweed on a Pine64 and RPi3, without success. > > Output: > https://gist.github.com/dmacvicar/78eb884883c3b53e8b8098e71820d53d Well, this means it is actually much better than a week ago when you pinged alex (who pinged me). it looks like it gets beyond

Re: [opensuse-arm] Leap 42.2 ARM: Ring 0 status

Hi Matwey, > Something strange with argyllcms package. Could you please trigger rebuild? Yep, fixed now. Thanks! Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Leap 42.2 ARM: Ring 0 status

Hi Matwey, Guillaume, > Once ring 1 will be in a good shape, I think we should move to an official > project such as Leap:42.2:Ports or even Leap:42.2 with armv7l. I've used that tree for bootstrapping Leap:42.2:Ports/armv7l, thanks for those efforts! (it is still building). There are a few

Re: [opensuse-arm] Different Releases

Hi Andy, 2016-05-03 20:01 GMT+02:00 Andy Norrie : > There seem to be several sources for the Raspberry Pi distribition for > the Pi 2 and Pi 3. Can someone tell me which is the definative one for > the 2 and 3. I have looked at some of the forums but some seem to be > the

Re: [opensuse-arm] raspberrypi image 2016.03.24-Build2.1 almost working [solved]

Hi Alex, > I think more people read the mailing list rather than bugzilla, so I'd keep > it the current way :). Those two methods are not exclusive - we could have the mailing list be the default assignee I guess. Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] Suse ARM Problem.

Hi Andy, 2016-04-04 10:12 GMT+02:00 Andy Norrie : > ARM factory there seem to be two directories for the Pi 2 downloads > with builds with 5.2 amd 3.1 as well as the 6.x builds so I am not > sure which one is correct. Which download should I try? Please use the image from

Re: [opensuse-arm] Missing typelib(LOKDocView) in published Factory repo

Hi Andreas, >> Problem: typelib(LOKDocView) benötigt von >> gnome-documents_books-common-3.20.0-1.2.armv7hl wird nirgends zur FYI, full list of current issues is attached. Feel free to help out.. Greetings, Dirk can't install tulip-doc-4.6.1-2.2.noarch: package tulip-doc-4.6.1-2.2.noarch

[opensuse-arm] failing openQA for aarch64

Hi, https://openqa.opensuse.org/group_overview/3 in case anyone has time to look into it. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Support for Wi-Fi and bluetooth on Raspberry Pi 3

Hi *, > Do you think you could update the rpi firmware package to include them? This has nothing to do with the rpi firmware package, it was blacklisted in the JeOS image. Fixed now. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail:

Re: [opensuse-arm] RPi 3 in transit via UPS

Hi Jimmy, > Anybody tested: > https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi2:Staging/JeOS-raspberrypi3 > ? Yes, it seems to work right now, however the Staging media is my personal playground. don't use it if you expect something that works. please use

Re: [opensuse-arm] Support for RPi camera in openSUSE for Rasberry Pi?

Hi Freek, >> >>> mmal: Failed to create camera component >> >>> mmal: main: Failed to create camera component >> >>> mmal: Failed to run camera app. Please check for firmware updates did you raise gpu memory to at least 128MB as advertised in

Re: [opensuse-arm] Tumbleweed Raspberry Pi2 i2c-tools not work

Hi Denislav, > rtc-ds1307, snd-bcm2835. Driver i2c-bcm2835 not > add to load - error modprobe: FATAL: Module i2c-bcm2835 not found in > directory /lib/modules/3.18.14-5-rpi2 Thank you for the report, this problem has been fixed in 4.1.19 (which is currently in :Staging) and later. Greetings,

Re: [opensuse-arm] RPi2, Tumbleweed and "official" 7" RPi touchscreen

Hi Ariel, > I downloaded several images over months and none of them worked on my > devices. I already purchased a serial adapter in order to get debug info, > but it is comming from China. Could you provide "proven" links to images? could you share a bit of information which image you used and

Re: [opensuse-arm] opensuse on odroid u3?

Hi, > Ethernet wasn't connected, but it looks as if the kernel doesn't support the > exynos again.. hmm, exynos support is in. I think the issue is a mismatched dtb, I'm fixing this, lets wait for the next image rebuild. TIA, Dirk -- To unsubscribe, e-mail:

[opensuse-arm] (Untested) RPI3 image - testers wanted

Hi, http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2:/Staging/images/ (yeah, I know its the Pi2 path, I was lazy) contains an untested raspberrypi3 image. I already know that serial is broken, that seems to be an upstream issue (due to the changed clock

Re: [opensuse-arm] Raspberry Pi 1 downstream strange behavior

Hi, > > It was just updated to Build 388.1 and the result is the same. > > Here is a workaround: > umount /boot/efi > umount /boot/ > mount /boot/ > mount /boot/efi > dracut -H -f sounds a bit as if the partition resizing / reloading of the kernel fails on first boot, so the

Re: [opensuse-arm] problems with JeOS on RPi2

Hi Bernhard, > not sure who is caring for those atm, feel free to assign RPi2 issues to me. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] glibc update for ARM

Hi Michael, >> armv6 does not receive any updates at all. > Not true at all! I even have kernel-4.4.2 on all my rpi1 systems which started > from an image file a year ago! And there were glibc updates to > glibc-2.22-7.1.armv6hl recently. Correct. Raspberry Pi1 is updated by openSUSE Tumbleweed

Re: [opensuse-arm] Raspberry Pi 3 - 64-bit

Hi, > The advantage of this version over previous is an increase in > performance and also integrated ethernet/wifi/bluetooth. Yeah, the wifi thing is a big thing for me, I immediately ordered one. I created a test image for the Rpi3 here:

Re: Re : Re: [opensuse-arm] Re: armv7 images broken: Initramfs unpacking failed: write error

2016-02-21 10:45 GMT+01:00 : > Thanks for taking care of this problem. I'm down to 32MB now, which seems okayish for a few hours of hacking. Next problem I noticed that we have enabled "CMA" in our kernel config for arm (it is disabled on other architectures), which

Re: [opensuse-arm] Re: armv7 images broken: Initramfs unpacking failed: write error

Hi Frank, > + echo '[1455926389.155528] Checking ext4 filesystem on /dev/mmcblk0p2...' > + '[' 0 = 0 ']' > + set +x > + checkFilesystem Yeah, I've seen that in my testing as well. it is a kiwi bug (https://github.com/openSUSE/kiwi/pull/551) and I submitted a fix for it, next build should have

Re: [opensuse-arm] First attempt to check ARM image

Hi Jimmy, > Chich primarily image that you want tested please? depends on what you want to achieve. the JeOS image is minimal text only, ideal for small remote servers that are only used for SSH. XFCE/LXQT are graphical images, but I have personally not tested them as I don't own a HDMI capable

Re: [opensuse-arm] Re: armv7 images broken: Initramfs unpacking failed: write error

Hi Guillaume, > Only kiwi-desc-oemboot-requires and kiwi-desc-vmxboot-requires are requiring > it (except grub2* packages). > It was not the case with older kiwi. > > It could explain it or not? yes, the pullin of grub2 is currently a mistake, at least until Alex grub2/uboot unification kicks

Re: [opensuse-arm] Root device not found

Hi Frank, 2016-02-14 19:35 GMT+01:00 Frank Kunz : > attached the /var/log/boot.kiwi Thanks, found the problem. It was an (ARM local) patch in our systemd (the one that was added to fix the kiwi builds for armv6) that entirely breaks all armv7/v8 images.

[opensuse-arm] Tumbleweed for AArch64 being converted to OpenQA publishing

Hi, Over the last couple of months, a couple of contributors have been working on enabling openQA for aarch64, and the current state looks good enough for a start. To learn more about openQA , visit http://os-autoinst.github.io/openQA/ (there is also openqa.org which is however completely

Re: [opensuse-arm] opensuse on odroid u3?

Hi Dieter, > Copying the SUSE image into that and booting it, also fabulously worked. > Even updating that 13.1 image to the latest state was possible. We have exynos 4 support disabled in the tumbleweed kernel, thats why. if you have patience to retest an image, I can branch a kernel with

Re: [opensuse-arm] opensuse on odroid u3?

Hi Michael, > I have to say as someone who is new to opensuse-arm but a long time > user/admin of opensuse that the -arm channels seem a bit chaotic and > hostile and totally void of useful info and what it sounds like is > being promoted to me is that if you can't figure it out on your own, > do

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Andreas, > The people that took action here - myself, Alex, Andreas - all are, and > we're less than the users asking. .. action that you *perceived* to take action. A strong difference! > It could be documented a) in the spec file, b) in the package or project > description. And some

Re: [opensuse-arm] pihwm package relocated

Hi Andreas, > If you want to get this submitted to Factory, please step up as > maintainer and start the process: do an SR from hardware to > openSUSE:Factory and write an email to opensuse-factory mailing list > pointing to SR# and explaining the package (cf. raspberrypi-firmware). Just to

[opensuse-arm] Temporary outage

Hi, There is a network connectivity issue to the ARMv7 Build cluster right now on OBS. It is being investigated today. Hopefully workers are back up before the weekend. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail:

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Andreas, > Further I had repeatedly said that if you guys care about a Contrib > repository, such as RaspberryPi2, then you need to update and clean it > up yourselves. Guess how many people did since then. Well, normally the responsibility of fixing something is with the one who broke it.. I

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Andreas, > Actually I think it is unfair of users to expect that SUSE engineers > must be the ones to fix things if random boards break I don't think anyone was calling for a "suse engineer". Users were asking for the openSUSE ARM contributors to take a look at the regression. I don't think

Re: [opensuse-arm] kpartx hangs in armv6 images builds

Hi Freek, > I don't think it is the proper way to use a serial cable to test images for > the Raspberry Pi 1. I made a wild guess on what the problem might be for the rpi1 image (I don't own such hardware), since the issue is imho universal (it broke all armv6/7 images). I've submitted a fix for

Re: [opensuse-arm] Current Pi2 image

Hi Michael, 2016-02-03 21:05 GMT+01:00 Michael Emory Cerquoni : > I also had good success the only problem I am having now is I am stuck > in 800x480 resolution the raspberrypi-userland package needs to be > uninstalled Do you mean it needs to be *installed* ? Because

Re: [opensuse-arm] Current Pi2 image

Hi, > Please note that Tumbleweed images are currently broken for all > flavors and architectures, it seems there is a kiwi (?) change that > breaks rootdevice detection. I"ve not find a single image that > boots... :-( ok, documenting findings .. the issue is that mmc_block.ko isn't loaded on

[opensuse-arm] all recent builds failed on aarch64

Hi, sorry, I recently updated the build workers to QEMU 2.5.0 which seems to have all builds to hang after an hour or so and then being marked as failed. I've now reverted the upgrade and did a osc rebuildpac -f on those projects that I have access to. Feel free to do it yourself where you care

Re: [opensuse-arm] Leap for armv7l

Hi Michal, >> Apparently you didn't search the list archives: >> http://lists.opensuse.org/opensuse-arm/2015-11/msg00011.html > Yep, I was searching in OBS, didn't expected answer this bad. Not sure how that answer is related to the question anyway.. So to summarize: Leap 42.1 is in sync with

Re: [opensuse-arm] No new JeOS images for Raspberry Pi 1, also meant for Raspberry Pi Zero?

Hi Freek, > Since September there are new images for other environments than JeOS, but not > anymore for this environment. These last images did not work, I don't know > why. Is that the reason there are no new images? Yeah, we're having issues with the build emulation. A fix is in preparation,

Re: [opensuse-arm] Udoo Quad (IMX6Q) hangs at kernel boot

Hi Oscar, > Now I would like to debug why it doesn't work with a current kernel. First > step (IMHO) is to try the same kernel version but with the default config. > Is there a way in OBS to recover a package to a point in time? If that's not > possible, what should I do now? you can recover the

Re: [opensuse-arm] Tumbleweed fails to boot in a Cubietruck

Hi, > According to [1] this should be fixed in Kiwi with: > https://github.com/openSUSE/kiwi/pull/521 > > It was merged. Is that maybe not checked into Tumbleweed yet? > Guillaume/Matwey, did you notice any improvement yet? Its not in tumbleweed, I'll add an overlay again. Greetings, Dirk --

Re: [opensuse-buildservice] Re: [opensuse-arm] Most ARM v7 workers are broken

Hi Adrian, > That was the version which caused the problems on arm 32bit > with the the kernel/qemu startup Not really :-) the change fixed the problem. the issue was that somebody ,while editing the build script, forgot to remove the reference to the -pci device and only added the -device

Re: [opensuse-buildservice] Re: [opensuse-arm] Most ARM v7 workers are broken

Hi Adrian, > the current git master is the one with caused the armv7 failures, do > you speak about that one? When we talk about why armv7 fails, then yes, thats because https://github.com/openSUSE/obs-build/pull/210 is not merged in git master. Don't be confused by the "merged" state in github,

Re: [opensuse-arm] Most ARM v7 workers are broken

Hi, > Actually, I wonder if the rng stuff is really worth the effort > when the majority of our systems is not supporting it. passing through virtio-rng is definitely a good idea especially with the terrible openssl on SLE12 that requires several kilobytes of entropy for generating a trivial RSA

Re: [opensuse-arm] Most ARM v7 workers are broken

Hi Adrian, > I have disabled for now kernel RNG support in the build script for arm, > but we need to discuss if we want to have this in future (by having > proper kernel and initrd support for it) or if we should disable it in > general for arm. Not all ARMv7 workers have support hardware

Re: [opensuse-arm] cuboxi tumbleweed images don't boot

Hi, > Sounds good. Does that mean we can build JeOS in openSUSE:Factory:ARM > proper then or are there further dependencies? it looks like there was a really old kernel in there. I removed it now and switched to the factory kernel. can anyone verify that it boots ? Thanks, Dirk -- To

[opensuse-arm] Re: Factory:ARM publishing is disabled

Hi, >> It's always disabled, because publishing happens via product building and >> testing. I just checked, we have recently published a new tree (a day ago) >> and have worked on openqa the last few days. >> Is there any particular problem that you're looking for? > I'm trying to build u-boot

Re: [opensuse-arm] armv6hl excluded for Kernel:stable?

Hi Stefan, > ARMv8/7 are likely to deal with a whole range of boards, configured in detail > by device tree blobs, so there is a range of SoCs and pheripherals (PMICs, > GPUs, ...) covered by these architectures. Correct. > > ARMv6 is mostly/only? targeted at Raspberries. So no PMIC, VC4 GPU,

Re: [opensuse-arm] 13.2 ARM updates

Hi, > I filed another ticket with the sysadmin team since the previous one > got closed as fixed, although nothing changed so far. It seems mirroring to the outside got fixed, a bunch of new updates got pushed today. Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] 13.2 ARM updates

Hi, >> AFAIK there will not be any update on 13.2 for armv6hl, only armv7hl. > That's fine, I'm interested in armv7hl updates. I filed another ticket with the sysadmin team since the previous one got closed as fixed, although nothing changed so far. Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] 13.2 ARM updates

Hi Volker, > Loading repository data... > Warning: Repository 'openSUSE-13.2-repo-update' appears to be outdated. > Consider using a different mirror or server. Looks like the publishing got stuck again. filed a ticket against infra team.. Thanks, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] Buiding Libreoffice 5.0

Hi Bill, I am trying now to build LO 5.0. It runs for a day and then starts over again. Can someone explain why this never builds? I've been trying to debug that myself, it is an instability on the build host.. it probably doesn't help that we have multiple projects trying to build

[opensuse-arm] Re: Factory/Tumbleweed and the switch to GCC 5.x

Hi *, To find those issues before they happen, I've created a Staging project of Factory which builds against GCC 5: https://build.opensuse.org/project/show/openSUSE:Factory:ARM:Staging:A Since we switched to GCC 5.x now in Factory, I've deleted the project (and triggered a rebuild of

Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library

Hi Freek, A new factory ftp tree has been published (finally). Does that one work as well for you? It works for RPi2 (date is June 3), but for RPi1 it is not published yet (date still February). Great, thanks for confirming. ARMv6hl also published now, but the package is old due to it no

Re: [opensuse-arm] Image repos needs cleanup

Hi Guillaume, Repo still needs cleanup. :( I know. I've mailed the OBS admins and still have not gotten a reply :-( Pinging again.. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

[opensuse-arm] ARM build workers updated

Hi, I just finished updating the majority of armv7l/aarch64 build workers to newer software versions (qemu 2.3.0, kernel 4.0.4, various bug + security fixes). It looks good to me, and I also fixed a few broken ones alongway, so we have more build power than before. Let me know if there are new

Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library

Hi Freek, I tried to find the project on build.opensuse.org that builds libstorage-ruby, but could not find it. its a subpackage of libstorage: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/libstorage Greetings, Dirk -- To unsubscribe, e-mail:

Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library

Hi Freek, I reported a bug in http://bugzilla.suse.com/show_bug.cgi?id=933274 about an Internal error in YaST. This problem is caused by a non-up-to-date ruby module on armv7l which is blocked by a boost library. Is it possible to look into the problem with the boost library in armv7l? The

Re: [opensuse-arm] openQA : ARM qemu and real hardware?

Hi Guillaume, 2015-05-27 14:32 GMT+02:00 Guillaume Gardet guillaume.gar...@free.fr: I know that some work have been done to get openQA working on ARM through qemu, but also on real hardware. That work was so far only on aarch64/kvm (e.g. running on aarch64 hardware inside a KVM virtual

[opensuse-arm] aarch64 build workers updated

Hi, I just updated the aarch64 build workers to a newer host kernel. Let me know if there are new issues. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] sunxi device tree outdated

Hi Andreas, There is in fact a BuildRequires: kernel-source, which should in theory trigger a rebuild once kernel-source is updated. No, only new sources trigger a rebuild. Not true either. Any change that causes a package to become uninstallable which was previously in succeeded state will

[opensuse-arm] Factory rebuild for icu / boost / ruby 2.2

Hi, a couple of updates went into Factory in the last few days that broke ARM, mainly due to bootstrap loops that needed to be resolved manually. I've done that now, and things are rebuilding. Hopefully tomorrow morning there should be a working tree again (unless something else enters factory

[opensuse-arm] Factory/Tumbleweed and the switch to GCC 5.x

Hi, as you might know, Factory is currently in preparation of transitioning to use GCC 5.0.x as the system compiler. There are several oddities to sort out with that, and I would expect additional issues for our ARM architectures in the form of miscompiles and ICE's. To find those issues before

Re: [opensuse-arm] openSUSE:Factory:ARM/armv6 outage, recovering

Hi Andreas, Why wasn't it tested? Good question. Why does this suddenly depend on Factory? IIRC this was changed March 23rd based on your announcement that there are issues with 2.3.0-rc0. openSUSE:Factory:ARM uses qemu-linux-user from Virtualization, which means that if there were a

Re: [opensuse-arm] openSUSE:Factory:ARM/armv6 outage, recovering

HI Andreas, its a bad worker and restarts the job on a different host, only to fail there the same way. It is only noticed then by an admin seeing You don't need to be admin to notice the problem. well, either that or actively waiting for a job to start, reloading the webui often enough so

Re: [opensuse-arm] openSUSE:Factory:ARM/armv6 outage, recovering

Hi Alex, The easy fix is to s/g_new/g_new0/ to expose the same allocation semantics as before. I've changed the code accordingly and submitted a fixed qemu package to the Virtualization project. Ah great, thanks for the quick fix. I've switched openSUSE:Factory:ARM to that new version now!

  1   2   >