November 2017

[opensuse-arm] http://download.opensuse.org/ports/aarch64/debug/tumbleweed is missing
by Andreas Schwab 11 Mar '18

11 Mar '18

... and the last published snapshot is Build20170831. This may be related. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- 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] rock64
by Matwey V. Kornilov 10 Mar '18

10 Mar '18

Hello, I will receive my rock64 board soon. https://www.pine64.org/?page_id=7147 I would like to run some openSUSE on it. There are no upstream support but lets see what we could do. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

8 58

[opensuse-arm] openSUSE-Tumbleweed ARM JeOS-efi.armv7
by Matwey V. Kornilov 17 Feb '18

17 Feb '18

Hi, I am trying to run openSUSE-Tumbleweed-ARM-JeOS-efi.armv7l-2017.10.29-Build1.7.raw using qemu. When I use qemu-system-aarch64 with 64-bit UEFI code aavmf-aarch64-code.bin then the only I see is the EFI console: UEFI Interactive Shell v2.287477C2-69C7-11D2-8E39-00A0C969723B B8F1C820 EDK IIlProtocolInterface: 752F3136-4E16-4FDC-A22A-E5F46812F4CA B8F1FF18 UEFI v2.60 (EDK II, 0x00010000)008-7F9B-4F30-87AC-60C9FEF5DA4E B8348710 Mapping table FS0: Alias(s):HD1a0b:;BLK2: VenHw(… [View More]837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(1,GPT,E30D92E4-F475-4D50-9D3D-DF05DA812008,0x800,0x64004) BLK5: Alias(s): VenHw(F9B94AE2-8BA6-409B-9D56-B9B417F53CB3) BLK0: Alias(s): VenHw(8047DB4B-7E9C-4C0C-8EBC-DFBBAACACE8F) BLK1: Alias(s): VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0) BLK3: Alias(s): VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(2,GPT,3DF8DD35-94BC-4FF0-B74C-12853D4B1811,0x65000,0x83004) BLK4: Alias(s): VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(3,GPT,38C4AA8C-4A7F-49C4-BCFD-6C2C755496BD,0xE8800,0x3DE781) Press ESC in 1 seconds to skip startup.nsh or any other key to continue. FSOpen: Open '\startup.nsh' Success FSOpen: Open '\startup.nsh' Success FSOpen: Open '\startup.nsh' Success Shell> bootarm FSOpen: Open '\efi\boot\bootarm.EFI' Success FSOpen: Open '\efi\boot\bootarm.EFI' Success FSOpen: Open '\efi\boot\bootarm.EFI' Success FSOpen: Open '\efi\boot\bootarm.EFI' Success [Security] 3rd party image[0] can be loaded after EndOfDxe: VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(1,GPT,E30D92E4-F475-4D50-9D3D-DF05DA812008,0x800,0x64004)/\efi\boot\bootarm.EFI. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B B8EDE440 Unloading driver at 0x00000000000 Shell> Error Status: Unsupported (line number 1) As far as I understand, 64-bit Qemu UEFI code doesn't expect to see and run 32-bit EFI executable. When I try to use qemu-uefi-aarch32.bin as firmware, then I see the following: Initialization of device cfi.pflash01 failed: failed to read the initial flash content As far as I understand, qemu-uefi-aarch32.bin is in wrong format, but there are no other files in ovfm rpm package. What is the proper way to run JeOS-efi.armv7? Is it supposed to work in qemu? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org [View Less]

3 23

[opensuse-arm] Raspberry Pi 3 interrupt handling
by Roger Oberholtzer 13 Dec '17

13 Dec '17

We have written a minimal kernel interrupt handler for the Raspberry Pi 3. It is running the current 64-bit Tumbleweed kernel. I am curious about the rate of interrupts that we might be able to capture. The ISR does little other than run when a raising edge interrupt happens. We are looking at /proc/interrupts to see how many interrupts have happened. We see that at around 23 kHz we begin to loose interrupts. The system is not doing anything else. Does that seem reasonable? I have not seen … [View More]

4 9

[opensuse-arm] [aarch64] TW on Pinebook?
by Alex Naumov 12 Dec '17

12 Dec '17

Hello, yesterday I finally got my 14'' Pinebook [1]. There is Ubuntu 16.04 MATE as a default OS, but I would like to use openSUSE TW on it of course. So, I found raw.xz XFCE-image for aarch64 [2] and used this command "to burn" image on the microSD card: # unxz -c openSUSE-Tumbleweed-ARM-XFCE-efi.aarch64-2017.06.10-Build2.3.raw.xz | sudo dd of=/dev/mmcblk1p No success. Pinebook tried to boot from microSD card, but... it seems that there is something wrong with bootloader. Here [3] I found … [View More]

5 7

[opensuse-arm] Re: [opensuse-factory] New Tumbleweed snapshot 20171120 released!
by Andreas Färber 27 Nov '17

27 Nov '17

Hi Daniel, Let's move the discussion to opensuse-arm list. Am 23.11.2017 um 12:07 schrieb Daniel Molkentin: > On 11/22/2017 06:31 PM, Andreas Färber wrote: >> Am 22.11.2017 um 04:25 schrieb Dominique Leuenberger: >>> ==== kernel-source ==== >>> Version update (4.13.12 -> 4.14.0) >>> Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms >>> >>> - Update to 4.14-final. >> On the aarch64 … [View More]based Pine64 board it has been observed that the updated >> dtb-allwinner package now requires the axp20x-regulator module in the >> initrd for using the MMC driver, and its parent module axp20x-rsb does >> not get loaded automatically even if added to the initrd. > I would prefer if that would be fixed in the kernel by adding the proper > dependencies. > Is there any chance for that? There's multiple issues at play here: 1) This is not a module compile-time dependency issue, but rather a run-time dependency issue, which AFAIU dracut is not resolving today. As a result the JeOS images in openSUSE:Factory:ARM etc. contain a number of add_drivers entries to load such extra modules: https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/JeOS/conf… That is of course ugly and would be nice to get resolved differently. Dracut would need to parse the Device Tree in /sys/firmware/ to discover what regulator, clock, power domain, etc. nodes are being referenced, then read their "compatible" strings and resolve them to the modules to add. The kernel uses generic API calls such as clk_get() and regulator_get(), thus no compile-time dependency for e.g. mmc modules. However when updating from 4.13 to 4.14 or from 4.14-rc4 to -rc8 it would've still read the current Device Tree and not discovered this new dependency for next boot. And Kiwi images get built in KVM, which will have a different Device Tree than the user's system or even ACPI. So I don't see a full solution yet. Let me know if I should report this somewhere upstream - it didn't seem a distro-specific issue for our Bugzilla. https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_troubleshoo… explains what info to include in a bug report, but not actually where to file it. ;) No link on dracut.wiki.kernel.org either. 2) axp20x-rsb driver does have MODULE_DEVICE_TABLE(of, ...), so it is unclear to me why the DT -> module resolution for auto-loading is not working here. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/dri… It is almost certainly an upstream kernel issue, possibly in sunxi-rsb bus driver. Stefan has already reported this on #linux-sunxi. > Otherwise, the "proper" dracut patch would > looks something like the attached one. Hm, instmod is just the equivalent of "add_drivers", is it? That would not be enough here. Also not all ARM systems need this driver, it's an extra chip on some boards only. What you could do is more generally add all =drivers/mfd drivers. But if we keep adding drivers by category instead of addressing the underlying discovery issue, we risk at some point the initrd getting too large for low-RAM systems. Regards, 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 [View Less]

2 1

Re: [opensuse-arm] Re: EspressoBin
by Matwey V. Kornilov 27 Nov '17

27 Nov '17

2017-10-22 9:31 GMT+03:00 Rick Ashford <Rick.Ashford(a)suse.com>: > There is a great thread on the Armbian forum about the EspressoBin, and it > helped me get things up and running with Tumbleweed. > > One of the guys there has a public Dropbox link that includes their images > for flashing the u-boot loader: > https://www.dropbox.com/sh/kmgmo1uubhcczx5/AAAYEvTIFxpBr0dHG2QcapTza?dl=0 > > The thread: > https://forum.armbian.com/index.php?/topic/4089-espressobin-… [View More]support-develop… > > With their boot loader I was able to finally use BTRFS images as well as PXE > boot. It also has an EFI load function in the help that I need to get around > to trying. Well, If armian u-boot is able to boot our standard EFI-Grub JeOS, then we can recommend to use it with openSUSE and don't reinvent the wheel. > > Rick Ashford > Sales Engineering Manager - West > SUSE Linux > rick.ashford(a)suse.com > Office: 512-782-4318 > Mobile: 512-731-3035 > > On Oct 21, 2017, at 12:32 PM, Matwey V. Kornilov <matwey.kornilov(a)gmail.com> > wrote: > > 2017-10-21 19:47 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-21 19:35 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-20 18:02 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-20 17:37 GMT+03:00 Alexander Graf <agraf(a)suse.de>: > > > > On 20.10.17 16:21, Matwey V. Kornilov wrote: > > 20.10.2017 17:12, Alexander Graf пишет: > > > > On 20.10.17 13:57, Matwey V. Kornilov wrote: > > Hi, > > > I've just received EspressoBin 1G. Any success stories how to run openSUSE? > > > > I think you'll basically have to somehow flash a working U-Boot with > > distro boot onto it and then just dd the tumbleweed/42.3 iso onto a usb > > stick and cross your fingers that gets you to a point where you can > > install :) > > > It has microsd card, I think it should be able to boot from sd, no? > > I also need to to find serial console pins on the board :) > > > There seems to be a lengthy discussion on the mailing list. I guess you > > can select the boot device using DIP switches though? > > > Yes, I can. I think it is preferred way. Need to find expected layout > > to place u-boot image. > > > Well, at least while booting from SATA, they say that BootRom looks > > for code starting with zero offset, which implies that there can not > > be any GPT partition table. > > Probably, it is similar for SD. If so, we need to flash our EFI-aware > > u-boot instead of upstream one. > > > > Well, SATA flash image from here > > > http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+… > > > suits for booting from microsd card, when it is flushed from zero > > offset and boot selection switchs are set to 7. > > > At least, there is non-destructive way to check out u-boot image. > > > Double checked. Seems that microsd boot doesn't work and is not > supported. At least for my V5 board. > It just falls back to SPINOR > > > > > http://espressobin.net/forums/topic/how-to-flash-u-boot/ > > > > Alex > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > With best regards, > Matwey V. Kornilov > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > > -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org [View Less]

2 10

[opensuse-arm] Re: [opensuse-factory] New Tumbleweed snapshot 20171120 released!
by Andreas Färber 22 Nov '17

22 Nov '17

Am 22.11.2017 um 04:25 schrieb Dominique Leuenberger: > ==== kernel-source ==== > Version update (4.13.12 -> 4.14.0) > Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms > > - Update to 4.14-final. > - commit c152297 > - rpm/kernel-binary.spec.in: rename kGraft to KLP (fate#323682) > - commit 0ed191d On the aarch64 based Pine64 board it has been observed that the updated dtb-allwinner package now requires the axp20x-… [View More]

1 0

[opensuse-arm] Error in C++ compiler on Rasberry Pi 2
by Freek de Kruijf 22 Nov '17

22 Nov '17

Recently I tried to use all Tumbleweed images on my three Raspberry Pi's (1B, 2B, and 3B). I did not experience problems with booting the image. Also upgrading to the newest version works OK. After that I tried to generate a third party package from GitHub, SBFspot, om my Raspberry Pi 2B. Generating means a.o. compiling a C++ module. The compiler produced a fatal internal error, which I reported on bugzilla. https://bugzilla.opensuse.org/show_bug.cgi?id=1068967 I would not expect such an … [View More]

1 0

[opensuse-arm] Samsung Chromebook (Snow) status?
by Daniel Bischof 20 Nov '17

20 Nov '17

Hi, I tried openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 recently, but it just beeps and kicks me back to the boot screen immediately. No messages on screen, partition resizing, etc. Any hints? Some cgpt magic I could try from ChromeOS perhaps? Best regards, --D. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 10

[opensuse-arm] armvl7 guest kernel crashes on build.opensuse.org
by Harald Welte 20 Nov '17

20 Nov '17

Since about Novebmer 15 I'm experiencing guest kernel crashes on build.opensuse.org when building armv7l packages. I reported this to the OBS folks in https://lists.opensuse.org/opensuse-buildservice/2017-11/msg00035.html but in https://lists.opensuse.org/opensuse-buildservice/2017-11/msg00036.html I was redirected to opensuse-arm, as the problem appears to be with the guest kernel and not with the build node. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http:… [View More]

3 2

[opensuse-arm] Moving SoC specific files from JeOS/KIWI config.sh to separate packages
by Stefan Brüns 18 Nov '17

18 Nov '17

Hi, currently config.sh creates several SoC specific files ad-hoc (i.e. using echo). This has several drawbacks: - it bloats config.sh (e.g 840 lines for the omap beagle /var/lib/alsa/ asound.state) - it creates files which are not tracked by RPM - most importantly, these files are never updated All these files could be moved into some SoC specific package, e.g. soc- config-$(kiwi-iname). If there are no objections, I will prepare an appropriate package and submit to Factory. The next … [View More]

4 4

[opensuse-arm] xf86-video-armsoc crashes X server
by Guillaume Gardet 18 Nov '17

18 Nov '17

Hi, I did not tested Chromebook for a while... and it was quite broken. I fixed our JeOS image boot, and now, I am working on graphic images. The problem is if we use xf86-video-armsoc, it crashes X server. A workaround is to use FBDEV driver, but it would be nice to fix ARMSOC driver! If you have any idea or want to join to help to fix it, please do it. :) GDB output: ******************************************************************************** Program terminated with signal SIGABRT, … [View More]Aborted. #0 0xb6967e5c in raise () from /lib/libc.so.6 Thread 1 (Thread 0xb6fc3010 (LWP 1967)): #0 0xb6967e5c in raise () from /lib/libc.so.6 No symbol table info available. #1 0xb69695e0 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x005cf7b8 in OsAbort () at utils.c:1361 No locals. #3 0x00497f20 in ddxGiveUp (error=EXIT_ERR_ABORT, error@entry=6184816) at xf86Init.c:1011 i = <optimized out> #4 0x0049800c in AbortDDX (error=6184816, error@entry=EXIT_ERR_ABORT) at xf86Init.c:1055 i = <optimized out> #5 0x005d590c in AbortServer () at log.c:874 No locals. #6 0x005d6490 in FatalError (f=0x60142c "Caught signal %d (%s). Server aborting\n") at log.c:1015 args = {__ap = 0xbef1e024} args2 = {__ap = 0xbef1e024} beenhere = 1 #7 0x005cc49c in OsSigHandler (signo=11, sip=0xbef1e040, unused=<optimized out>) at osinit.c:154 unused = <optimized out> sip = 0xbef1e040 signo = 11 #8 <signal handler called> No symbol table info available. #9 xf86InitViewport (pScr=0x835398) at xf86Cursor.c:104 No locals. #10 0x0049a1cc in InitOutput (pScreenInfo=0xbef1e604, pScreenInfo@entry=0x639464 <screenInfo>, argc=6440076, argc@entry=4534188, argv=0x833c88, argv@entry=0x0) at xf86Init.c:634 i = 0 j = <optimized out> k = <optimized out> scr_index = <optimized out> modulelist = <optimized out> optionlist = 0x859008 screenpix24 = <optimized out> pix24 = <optimized out> pix24From = X_DEFAULT pix24Fail = 0 autoconfig = <optimized out> sigio_blocked = 0 want_hw_access = <optimized out> configured_device = <optimized out> #11 0x00452fac in dix_main (argc=4534188, argv=0x0, envp=<optimized out>) at main.c:197 i = <optimized out> alwaysCheckForInput = {0, 1} #12 0xb6950b68 in __libc_start_main () from /lib/libc.so.6 No symbol table info available. #13 0x0043affc in _start () at ../sysdeps/arm/start.S:110 No locals. Backtrace stopped: previous frame identical to this frame (corrupt stack?) ******************************************************************************** Xorg.0.log is here: ******************************************************************************** [ 46.639] X.Org X Server 1.19.5 Release Date: 2017-10-12 [ 46.639] X Protocol Version 11, Revision 0 [ 46.639] Build Operating System: openSUSE SUSE LINUX [ 46.639] Current Operating System: Linux linux 4.13.12-1-lpae #1 SMP PREEMPT Wed Nov 8 11:21:09 UTC 2017 (9151c66) armv7l [ 46.639] Kernel command line: root=/dev/disk/by-id/mmc-SU04G_0x06500ce9-part3 loader=uboot disk=/dev/disk/by-id/mmc-SU04G_0x06500ce9 resume=/dev/disk/by-id/mmc-SU04G_0x06500ce9-part4 loglevel=3 splash=silent plymouth.enable=0 console=ttySAC3,115200n8 console=tty [ 46.639] Build Date: 16 November 2017 01:04:09PM [ 46.640] [ 46.640] Current version of pixman: 0.34.0 [ 46.640] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 46.640] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 46.640] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 26 14:30:03 2017 [ 46.653] (==) Using config file: "/etc/X11/xorg.conf" [ 46.653] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 46.653] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 46.671] (==) ServerLayout "DefaultLayout" [ 46.671] (**) |-->Screen "DefaultScreen" (0) [ 46.671] (**) | |-->Monitor "<default monitor>" [ 46.672] (**) | |-->Device "Mali FBDEV" [ 46.672] (**) | |-->GPUDevice "Mali FBDEV" [ 46.672] (**) | |-->GPUDevice "DefaultDevice" [ 46.672] (==) No monitor specified for screen "DefaultScreen". Using a default monitor configuration. [ 46.672] (**) Option "DontZap" "false" [ 46.672] (**) Option "StandbyTime" "0" [ 46.672] (**) Option "SuspendTime" "0" [ 46.672] (**) Option "OffTime" "0" [ 46.672] (==) Automatically adding devices [ 46.672] (==) Automatically enabling devices [ 46.672] (==) Automatically adding GPU devices [ 46.672] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 46.684] (WW) The directory "/usr/share/fonts/Type1/" does not exist. [ 46.684] Entry deleted from font path. [ 46.684] (WW) The directory "/usr/share/fonts/100dpi" does not exist. [ 46.684] Entry deleted from font path. [ 46.687] (WW) The directory "/usr/share/fonts/cyrillic" does not exist. [ 46.687] Entry deleted from font path. [ 46.687] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 46.687] Entry deleted from font path. [ 46.688] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/truetype/, built-ins [ 46.688] (==) ModulePath set to "/usr/lib/xorg/modules" [ 46.688] (**) Extension "XFree86-DGA" is disabled [ 46.688] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 46.688] (II) Loader magic: 0x6f0ed0 [ 46.688] (II) Module ABI versions: [ 46.688] X.Org ANSI C Emulation: 0.4 [ 46.688] X.Org Video Driver: 23.0 [ 46.688] X.Org XInput driver : 24.1 [ 46.689] X.Org Server Extension : 10.0 [ 46.692] (++) using VT number 7 [ 46.692] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 46.695] (II) xfree86: Adding drm device (/dev/dri/card0) [ 46.702] (II) no primary bus or device found [ 46.702] falling back to /sys/devices/platform/exynos-drm/drm/card0 [ 46.702] (II) LoadModule: "glx" [ 46.708] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 46.863] (II) Module glx: vendor="X.Org Foundation" [ 46.863] compiled for 1.19.5, module version = 1.0.0 [ 46.863] ABI class: X.Org Server Extension, version 10.0 [ 46.863] (II) LoadModule: "armsoc" [ 46.864] (II) Loading /usr/lib/xorg/modules/drivers/armsoc_drv.so [ 46.871] (II) Module armsoc: vendor="X.Org Foundation" [ 46.871] compiled for 1.19.5, module version = 1.4.1 [ 46.871] Module class: X.Org Video Driver [ 46.871] ABI class: X.Org Video Driver, version 23.0 [ 46.871] (II) ARMSOC: Driver for ARM Mali compatible chipsets [ 46.891] (WW) Falling back to old probe method for armsoc [ 46.891] (II) No BusID or DriverName specified - opening /dev/dri/card0 [ 46.891] (II) Got BusID exynos-drm [ 46.916] (II) Opened DRM [ 46.916] (II) DeviceName is [/dev/dri/card0] [ 46.916] (II) bus_id is [exynos-drm] [ 46.916] (II) DriverName is [exynos] [ 46.916] (II) version is [1.0.0] [ 46.917] (II) Screen:0, CRTC:0 [ 46.933] (II) No BusID or DriverName specified - opening /dev/dri/card0 [ 46.933] (II) Got BusID exynos-drm [ 46.966] (II) Opened DRM [ 46.966] (II) DeviceName is [/dev/dri/card0] [ 46.966] (II) bus_id is [exynos-drm] [ 46.966] (II) DriverName is [exynos] [ 46.966] (II) version is [1.0.0] [ 46.966] (II) Screen:1, CRTC:1 [ 46.983] (EE) Screen 1 deleted because of no matching config section. [ 46.983] (II) UnloadModule: "armsoc" [ 46.983] (**) ARMSOC(0): Depth 24, (--) framebuffer bpp 32 [ 46.983] (==) ARMSOC(0): RGB weight 888 [ 46.983] (==) ARMSOC(0): Using gamma correction (1.0, 1.0, 1.0) [ 46.983] (==) ARMSOC(0): Default visual is TrueColor [ 46.983] (II) No BusID or DriverName specified - opening /dev/dri/card0 [ 46.983] (II) Got BusID exynos-drm [ 47.016] (II) Opened DRM [ 47.016] (II) DeviceName is [/dev/dri/card0] [ 47.016] (II) bus_id is [exynos-drm] [ 47.016] (II) DriverName is [exynos] [ 47.016] (II) version is [1.0.0] [ 47.016] (II) ARMSOC(0): Chipset: Mali [ 47.016] (**) ARMSOC(0): Option "Debug" "true" [ 47.016] (II) ARMSOC(0): Buffer Flipping is Enabled [ 47.017] (II) ARMSOC(0): umplock is Enabled [ 47.017] (II) ARMSOC(0): Setting the video modes ... [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1654: Entering [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1671 Got KMS resources [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1674 4 connectors, 3 encoders [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1677 3 crtcs, 0 fbs [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1680 0x0 minimum resolution [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1683 4096x4096 maximum resolution [ 47.017] (II) ARMSOC(0): drmmode_crtc_init:882: Entering [ 47.017] (II) ARMSOC(0): Got CRTC: 0 (id: 36) [ 47.017] (II) ARMSOC(0): drmmode_crtc_init:897: Exiting [ 47.017] (II) ARMSOC(0): drmmode_output_init:1337: Entering [ 47.036] (II) ARMSOC(0): Output eDP-1 has no monitor section [ 47.036] (II) ARMSOC(0): drmmode_output_init:1404: Exiting [ 47.050] (II) ARMSOC(0): drmmode_output_get_modes:980 count_modes: 0 [ 47.051] (II) ARMSOC(0): Not using default mode "640x350" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x175" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x400" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x200" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "720x400" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "360x200" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (unknown reason) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (unknown reason) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "1024x768i" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "512x384i" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "1024x768" (unknown reason) [ 47.051] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "1024x768" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1024x768" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1024x768" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1152x864" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "576x432" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x960" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x480" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x960" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x480" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x1024" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x512" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x1024" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x512" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x1024" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x512" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1792x1344" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "896x672" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1792x1344" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "896x672" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1856x1392" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "928x696" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1856x1392" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "928x696" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1920x1440" (hsync out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "960x720" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1920x1440" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "960x720" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "832x624" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "416x312" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1400x1050" (hsync out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "700x525" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1400x1050" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "700x525" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1920x1440" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "960x720" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "2048x1536" (hsync out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "1024x768" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "2048x1536" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "1024x768" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "2048x1536" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "1024x768" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): No remaining probed modes for output eDP-1 [ 47.053] (II) ARMSOC(0): Output eDP-1 connected [ 47.053] (WW) ARMSOC(0): Unable to find initial modes [ 47.053] (EE) ARMSOC(0): Output eDP-1 enabled but has no modes [ 47.053] (II) ARMSOC(0): drmmode_pre_init:1715: Exiting [ 47.053] (II) ARMSOC(0): Got KMS resources [ 47.069] (==) ARMSOC(0): DPI set to (96, 96) [ 47.069] (II) Loading sub module "dri2" [ 47.069] (II) LoadModule: "dri2" [ 47.069] (II) Module "dri2" already built-in [ 47.069] (II) Loading sub module "exa" [ 47.069] (II) LoadModule: "exa" [ 47.069] (II) Loading /usr/lib/xorg/modules/libexa.so [ 47.076] (II) Module exa: vendor="X.Org Foundation" [ 47.076] compiled for 1.19.5, module version = 2.6.0 [ 47.076] ABI class: X.Org Video Driver, version 23.0 [ 47.076] (II) Loading sub module "fb" [ 47.076] (II) LoadModule: "fb" [ 47.077] (II) Loading /usr/lib/xorg/modules/libfb.so [ 47.086] (II) Module fb: vendor="X.Org Foundation" [ 47.086] compiled for 1.19.5, module version = 1.0.0 [ 47.086] ABI class: X.Org ANSI C Emulation, version 0.4 [ 47.086] (II) ARMSOC(0): ARMSOCPreInit:940: Exiting [ 47.086] (EE) [ 47.086] (EE) Backtrace: [ 47.086] (EE) 0: /usr/bin/X (xorg_backtrace+0x54) [0x699dec] [ 47.086] (EE) 1: /usr/bin/X (0x4e2000+0x1bc440) [0x69e440] [ 47.087] (EE) 2: /lib/libc.so.6 (__default_rt_sa_restorer+0x0) [0xb68d6480] [ 47.087] (EE) 3: /usr/bin/X (xf86InitViewport+0xb8) [0x561ba0] [ 47.087] (EE) 4: /usr/bin/X (InitOutput+0xddc) [0x56c1cc] [ 47.087] (EE) 5: /usr/bin/X (0x4e2000+0x42fac) [0x524fac] [ 47.087] (EE) 6: /lib/libc.so.6 (__libc_start_main+0x120) [0xb68bdb68] [ 47.087] (EE) [ 47.087] (EE) Segmentation fault at address 0x18 [ 47.087] (EE) Fatal server error: [ 47.087] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 47.087] (EE) [ 47.087] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 47.088] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 47.088] (EE) [ 47.105] (EE) Server terminated with error (1). Closing log file. ******************************************************************************** Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org [View Less]

2 3

[opensuse-arm] [aarch64] Tumbleweed repositories is outdated
by Manu Maier 14 Nov '17

14 Nov '17

The last images are from the 17-Jun-2017 http://download.opensuse.org/ports/aarch64/tumbleweed/images/?C=M;O=D and the latest packages from 21-Sep-2017 http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/suse/aarch64… The repositories should be updated. Greetings, Manu N��r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0��Ǩ�

6 5

[opensuse-arm] JeOS-2017-03-13 image for RPi 1 installs OK, Grub fails on reboot
by Alex Armstrong 14 Nov '17

14 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I was testing: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2017.03.13-Build1.8.raw.xz from: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… On RaspberryPi 1 Model B It installs fine - expands the file system, creates the dracut based init and boots to a usable system. But when I reboot, grub fails with: error: attempt to read or write outside of partition. and drops me to the grub rescue system. … [View More]

3 9

Main

Development

Information

Community

Social Media

Other

openSUSE ARM