[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Stewart Samuels 
I can ssh in now, after rebooting without the cma=64M appended.  But not 
when I boot up with it appended.


___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Peter Robinson 
On Fri, Aug 12, 2016 at 11:02 PM, Stewart Samuels  wrote:
> Ok.  I appended cma=64M to the end of the "append" line in
> /boot/extlinux/extlinux.conf and rebooted the system.  That had the effect
> when I rebooted to cause my monitor to constantly flash on and off
> repeatedly and would not let me get to the point of being able to ssh into
> the system.  Nor was I able to login via an alternate console.  I have since
> removed the cma=64M and rebooted to where I was without the cma=64M
> appended.

Seems to be an improvement to some degree then, can you ssh in to debug?

> Any other suggestions?  They are most appreciated.

Not off hand, there might be a newer version of the driver, I'll add
it to my todo list.
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Stewart Samuels 
Ok.  I appended cma=64M to the end of the "append" line in 
/boot/extlinux/extlinux.conf and rebooted the system.  That had the 
effect when I rebooted to cause my monitor to constantly flash on and 
off repeatedly and would not let me get to the point of being able to 
ssh into the system.  Nor was I able to login via an alternate console.  
I have since removed the cma=64M and rebooted to where I was without the 
cma=64M appended.


Any other suggestions?  They are most appreciated.
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Stewart Samuels 

Will I need to rebuilt the initramfs with this parameter as well?
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Peter Robinson 
On Fri, Aug 12, 2016 at 10:12 PM, Stewart Samuels  wrote:
> Ok.  It seems I got a lot further with the armsoc driver but Xorg still
> fails.  This time _CREATE_GEM cannot allocate memory for a scanout buffer.

You might need to increase the cma memory allocation try adding
cma=64M to the end of the append line in /boot/extlinux/extlinux.conf

> Here is what I did.  I actually copied the Ubuntu /etc/X11/xorg.conf file to
> my /etc/X11 directory.
>
> The following is the content of both the /etc/X11 directory and the
> xorg.conf file but ONLY the xorg.conf file is non-stock Fedora:
>
> ls -l
> total 28
> drwxr-xr-x 2 root root 4096 Feb  3  2016 applnk
> drwxr-xr-x 2 root root 4096 Jun 14 12:36 fontpath.d
> drwxr-xr-x 5 root root 4096 Jun 29 05:30 xinit
> -rw-r--r-- 1 root root  547 Feb  5  2016 Xmodmap
> -rw-r--r-- 1 root root  687 Aug 11 07:18 xorg.conf
> drwxr-xr-x 2 root root 4096 Jul 21 02:32 xorg.conf.d
> -rw-r--r-- 1 root root  493 Feb  5  2016 Xresources
>
> ***
> cat xorg.conf
> Section "Device"
> Identifier  "Mali-Fbdev"
> Driver  "armsoc"
> Option  "fbdev" "/dev/fb0"
> Option  "Debug" "false"
> Option  "DPMS"  "false"
> EndSection
>
> Section "Screen"
> Identifier  "Default Screen"
> Device  "Mali-Fbdev"
> DefaultDepth24
> EndSection
>
> Section "ServerLayout"
> Identifier  "Default Layout"
> Option  "BlankTime" "0"
> Option  "StandbyTime"   "0"
> Option  "SuspendTime"   "0"
> Option  "OffTime"   "0"
> EndSection
>
> Section "DRI"
> Mode0666
> EndSection
>
> ***
> Following is the "startx" output:
>
> [root@myodroid X11]# startx
> xauth:  file /root/.serverauth.17042 does not exist
>
>
> X.Org X Server 1.18.4
> Release Date: 2016-07-19
> X Protocol Version 11, Revision 0
> Build Operating System:  4.6.3-300.fc24.armv7hl
> Current Operating System: Linux myodroid 4.6.5-300.fc24.armv7hl #1 SMP Thu
> Jul 28 03:09:19 UTC 2016 armv7l
> Kernel command line:
> rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro
> root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=en_US.UTF-8
> Build Date: 19 July 2016  06:13:15PM
> Build ID: xorg-x11-server 1.18.4-1.fc24
> Current version of pixman: 0.34.0
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 12 17:00:51 2016
> (==) Using config file: "/etc/X11/xorg.conf"
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> (EE)
> Fatal server error:
> (EE) AddScreen/ScreenInit failed for driver 0
> (EE)
> (EE)
> Please consult the Fedora Project support
>  at http://wiki.x.org
>  for help.
> (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional
> information.
> (EE)
> (EE) Server terminated with error (1). Closing log file.
>
> xinit: giving up
> xinit: unable to connect to X server: Connection refused
> xinit: server error
>
>
> 
>
> And here is the content of /var/log/Xorg.0.log
>
> [root@myodroid log]# cat Xorg.0.log
> [116289.200]
> X.Org X Server 1.18.4
> Release Date: 2016-07-19
> [116289.200] X Protocol Version 11, Revision 0
> [116289.200] Build Operating System:  4.6.3-300.fc24.armv7hl
> [116289.200] Current Operating System: Linux myodroid 4.6.5-300.fc24.armv7hl
> #1 SMP Thu Jul 28 03:09:19 UTC 2016 armv7l
> [116289.200] Kernel command line:
> rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro
> root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=en_US.UTF-8
> [116289.201] Build Date: 19 July 2016  06:13:15PM
> [116289.201] Build ID: xorg-x11-server 1.18.4-1.fc24
> [116289.201] Current version of pixman: 0.34.0
> [116289.201] Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [116289.201] Markers: (--) probed, (**) from config file, (==) default
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [116289.202] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 12 17:00:51
> 2016
> [116289.203] (==) Using config file: "/etc/X11/xorg.conf"
> [116289.203] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> [116289.205] (==) ServerLayout "Default Layout"
> [116289.205] (**) |-->Screen "Default Screen" (0)
> [116289.205] (**) |   |-->Monitor ""
> [116289.206] (**) |   |-->Device "Mali-Fbdev"
> [116289.206] (==) No monitor specified for screen "Default Screen".
> Using a

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Stewart Samuels 
Ok.  It seems I got a lot further with the armsoc driver but Xorg still 
fails.  This time _CREATE_GEM cannot allocate memory for a scanout buffer.


Here is what I did.  I actually copied the Ubuntu /etc/X11/xorg.conf 
file to my /etc/X11 directory.


The following is the content of both the /etc/X11 directory and the 
xorg.conf file but ONLY the xorg.conf file is non-stock Fedora:


ls -l
total 28
drwxr-xr-x 2 root root 4096 Feb  3  2016 applnk
drwxr-xr-x 2 root root 4096 Jun 14 12:36 fontpath.d
drwxr-xr-x 5 root root 4096 Jun 29 05:30 xinit
-rw-r--r-- 1 root root  547 Feb  5  2016 Xmodmap
-rw-r--r-- 1 root root  687 Aug 11 07:18 xorg.conf
drwxr-xr-x 2 root root 4096 Jul 21 02:32 xorg.conf.d
-rw-r--r-- 1 root root  493 Feb  5  2016 Xresources

***
cat xorg.conf
Section "Device"
Identifier  "Mali-Fbdev"
Driver  "armsoc"
Option  "fbdev" "/dev/fb0"
Option  "Debug" "false"
Option  "DPMS"  "false"
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "Mali-Fbdev"
DefaultDepth24
EndSection

Section "ServerLayout"
Identifier  "Default Layout"
Option  "BlankTime" "0"
Option  "StandbyTime"   "0"
Option  "SuspendTime"   "0"
Option  "OffTime"   "0"
EndSection

Section "DRI"
Mode0666
EndSection

***
Following is the "startx" output:

[root@myodroid X11]# startx
xauth:  file /root/.serverauth.17042 does not exist


X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System:  4.6.3-300.fc24.armv7hl
Current Operating System: Linux myodroid 4.6.5-300.fc24.armv7hl #1 SMP 
Thu Jul 28 03:09:19 UTC 2016 armv7l
Kernel command line: 
rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro 
root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=en_US.UTF-8

Build Date: 19 July 2016  06:13:15PM
Build ID: xorg-x11-server 1.18.4-1.fc24
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 12 17:00:51 2016
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 0
(EE)
(EE)
Please consult the Fedora Project support
 at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.

(EE)
(EE) Server terminated with error (1). Closing log file.

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error




And here is the content of /var/log/Xorg.0.log

[root@myodroid log]# cat Xorg.0.log
[116289.200]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[116289.200] X Protocol Version 11, Revision 0
[116289.200] Build Operating System:  4.6.3-300.fc24.armv7hl
[116289.200] Current Operating System: Linux myodroid 
4.6.5-300.fc24.armv7hl #1 SMP Thu Jul 28 03:09:19 UTC 2016 armv7l
[116289.200] Kernel command line: 
rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro 
root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=en_US.UTF-8

[116289.201] Build Date: 19 July 2016  06:13:15PM
[116289.201] Build ID: xorg-x11-server 1.18.4-1.fc24
[116289.201] Current version of pixman: 0.34.0
[116289.201] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[116289.201] Markers: (--) probed, (**) from config file, (==) default 
setting,

(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[116289.202] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 12 
17:00:51 2016

[116289.203] (==) Using config file: "/etc/X11/xorg.conf"
[116289.203] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[116289.205] (==) ServerLayout "Default Layout"
[116289.205] (**) |-->Screen "Default Screen" (0)
[116289.205] (**) |   |-->Monitor ""
[116289.206] (**) |   |-->Device "Mali-Fbdev"
[116289.206] (==) No monitor specified for screen "Default Screen".
Using a default monitor configuration.
[116289.206] (**) Option "BlankTime" "0"
[116289.206] (**) Option "StandbyTime" "0"
[116289.206] (**) Option "SuspendTime" "0"
[116289.206] (**) Option "OffTime" "0"
[116289.206] (==) Automatically adding devices
[116289.206] (==) Automatically enabling devices
[116289.206] (==) Automatically adding GPU devices
[116289.206] (==) Max clients allowed: 256, resource mask: 0x1f
[116289.207] (==)

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Peter Robinson 
On Fri, Aug 12, 2016 at 6:26 PM, Stewart Samuels  wrote:
> I am using stock system.  No external software here.
>
> BTW, I notice also that Xorg seems to be trying to use the Mesa driver here 
> rather than the Mali driver when the Odroid-Xu4 has Mali hardware.  Is this 
> normal?

There is no open source mali driver, mesa is 3D and does numerous
hardware. It depends on a number of things. You might have to add a
xorg snippet to explicitly load the xorg-x11-drv-armsoc driver as it
might not be properly detecting the hardware.

Peter
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Fedora 25 Alpha blocker status mail #1

2016-08-12 Thread Adam Williamson 
Hi folks! We're in Alpha freeze and Alpha go/no-go is scheduled for
next week (2016-08-18), so it's time for the first blocker status mail.

tl;dr action summary


1. https://bugzilla.redhat.com/show_bug.cgi?id=1365661
ACTION: releng/Cloud teams to figure out the problem, if it persists.

2. https://bugzilla.redhat.com/show_bug.cgi?id=1352680
ACTION: pjones to do a new fwupdate build and create an update with
efivar, efibootmgr and all the other efivar-dependent packages.

3. https://bugzilla.redhat.com/show_bug.cgi?id=1324623
ACTION: FESCo to decide on whatever they've been asked to decide, glibc
maintainers (fweimer), ARM team and releng to agree on a fix.

4. https://bugzilla.redhat.com/show_bug.cgi?id=1353054
ACTION: QA and FreeIPA folks to help test and karma the update for
pushing.

5. https://bugzilla.redhat.com/show_bug.cgi?id=1366403
ACTION: blocker reviewers to vote on blocker status (will happen at
Monday's blocker meeting), sssd devs to investigate and fix.

Also note that some validation tests have still not been run, QA folks
we should be aiming to fill out all the Alpha validation tests ASAP :)

bug-by-bug detail
=

1. https://bugzilla.redhat.com/show_bug.cgi?id=1365661 - distribution - NEW
   Cloud images fail to compose from 20160809.n.0

Cloud images stopped showing up with the 20160809 compose. We are not
yet sure why. We *did* get cloud images for today's Rawhide compose, so
it's possible they'll show up again with the next successful 25 compose.

ACTION: releng/Cloud teams to figure out the problem, if it persists.

2. https://bugzilla.redhat.com/show_bug.cgi?id=1352680 - efibootmgr - NEW
   efibootmgr calls in anaconda crashing since efivar-0.24-1.fc25 landed

efivar API/ABI changed and broke efibootmgr. As of yesterday there are
new builds of efivar and efibootmgr and they do appear to solve the
bug, but there's a problem: another package which depends on efivar -
fwupdate - has not been rebuilt, and it is part of the Workstation
package set. We need fwupdate to be built and included in the update
submitted to fix this bug.

ACTION: pjones to do a new fwupdate build and create an update with
efivar, efibootmgr and all the other efivar-dependent packages.

3. https://bugzilla.redhat.com/show_bug.cgi?id=1324623 - glibc - ASSIGNED
   glibc: split libcrypt into separate package and package libcrypt-nss with 
NSS-based implementation

A consequence of this package split has been to break the ARM Xfce
image build, which is a release-blocking image. Relevant folks are
broadly aware of the issue, but it doesn't seem like a fix has been
agreed yet, and the issue has been referred to FESCo for some reason.

ACTION: FESCo to decide on whatever they've been asked to decide, glibc
maintainers (fweimer), ARM team and releng to agree on a fix.

4. https://bugzilla.redhat.com/show_bug.cgi?id=1353054 - pki-core - MODIFIED
   FreeIPA server deployment fails due to pki-core dangling symlinks

This bug has now been fixed, with this update:
https://admin.fedoraproject.org/updates/FEDORA-2016-0a384ead60
I have tested and confirmed the fix, the update ideally needs a couple
more karma points to be pushed stable.

ACTION: QA and FreeIPA folks to help test and karma the update for pushing.

5. https://bugzilla.redhat.com/show_bug.cgi?id=1366403 - sssd - NEW
   [abrt] sssd-common: ipa_dyndns_update_send(): sssd_be killed by SIGSEGV

This is a proposed blocker, but it does seem quite worrying; we run
into it with the openQA test that enrols a FreeIPA client via an
anaconda kickstart file. The enrolment works, but on boot of the
installed system, sssd_be crashes and this seems to prevent login as a
FreeIPA user. sssd team is looking into this one.

ACTION: blocker reviewers to vote on blocker status (will happen at
Monday's blocker meeting), sssd devs to investigate and fix.
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Fedora 24 Mate Spin fails to start all cpus on Odroid-Xu4

2016-08-12 Thread Stewart Samuels 
Hello,

I've notice on both Fedora 24 4.5.5-300 and 4.6.5-300 systems, that Fedora 24 
starts 5 out of 8 cpus.  Is there a limit being set somewhere or is this a bug?

U-Boot 2016.05 (May 30 2016 - 20:03:50 +) for ODROID-XU3

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
*** Warning - bad CRC, using default environment

In:serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
936 bytes read in 18 ms (50.8 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command:  autoboot
Ignoring malformed menu command:  hidden
Ignoring unknown command: totaltimeout
Ignoring unknown command: default=Fedora
Fedora-Mate-armhfp-24-1.2 Boot Options.
1:  Fedora (4.6.5-300.fc24.armv7hl) 24 (Twenty Four)
2:  Fedora-Mate-armhfp-24-1.2 (4.5.5-300.fc24.armv7hl)
Enter choice: 1:Fedora (4.6.5-300.fc24.armv7hl) 24 (Twenty Four)
Retrieving file: /initramfs-4.6.5-300.fc24.armv7hl.img
17514609 bytes read in 1641 ms (10.2 MiB/s)
Retrieving file: /vmlinuz-4.6.5-300.fc24.armv7hl
6102880 bytes read in 587 ms (9.9 MiB/s)
append: rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro 
root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=en_US
.UTF-8
Retrieving file: /dtb-4.6.5-300.fc24.armv7hl/exynos5422-odroidxu4.dtb
47808 bytes read in 124 ms (376 KiB/s)
Kernel image @ 0x4200 [ 0x00 - 0x5d1f60 ]
## Flattened Device Tree blob at 4300
   Booting using the fdt blob at 0x4300
   Loading Ramdisk to 4ef4b000, end 4071 ... OK
   Loading Device Tree to 4ef3c000, end 4ef4aabf ... OK

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x100
[0.00] Linux version 4.6.5-300.fc24.armv7hl 
(mockbu...@arm04-builder03.arm.fedoraproject.org) (gcc version 6.1.1 20160621 
(Red Hat 6.1.1-3) (GCC) ) #1 SMP Thu Jul 28 03:09:19 UTC 2016
[0.00] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[0.00] CPU: div instructions available: patching division code
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] Machine model: Hardkernel Odroid XU4
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 16 MiB at 0xbd80
[0.00] Memory policy: Data cache writealloc
[0.00] Samsung CPU ID: 0xe5422001
[0.00] Running under secure firmware.
[0.00] percpu: Embedded 13 pages/cpu @eed8a000 s24332 r8192 d20724 
u53248
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 512832
[0.00] Kernel command line: 
rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro 
root=UUID=dfac3a15-7d31-46ed-
842f-2f7599871202 LANG=en_US.UTF-8
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Memory: 1991052K/2058240K available (7609K kernel code, 1140K 
rwdata, 3376K rodata, 1108K init, 854K bss, 50804K re
served, 16384K cma-reserved, 1271808K highmem)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xf080 - 0xff80   ( 240 MB)
[0.00] lowmem  : 0xc000 - 0xf000   ( 768 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
[0.00]   .text : 0xc0208000 - 0xc0cc28f8   (10987 kB)
[0.00]   .init : 0xc0cc3000 - 0xc0dd8000   (1108 kB)
[0.00]   .data : 0xc0dd8000 - 0xc0ef52b4   (1141 kB)
[0.00].bss : 0xc0ef52b4 - 0xc0fcabb8   ( 855 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[0.00] Hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] Switching to timer-based delay loop, resolution 41ns
[0.00] clocksource: mct-frc: mask: 0x max_cycles: 0x, 
max_idle_ns: 79635851949 ns
[0.07] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 
89478484971ns
[0.005176] Console: colour dummy device 80x30
[0.006058] console [tty0] enabled
[0.006118] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 48.00 BogoMIPS (lpj=12)
[0.006177] pid_max: default: 32768 minimum: 301
[0.006426] Security Framework initialized
[0.006461]

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Stewart Samuels 
I am using stock system.  No external software here.

BTW, I notice also that Xorg seems to be trying to use the Mesa driver here 
rather than the Mali driver when the Odroid-Xu4 has Mali hardware.  Is this 
normal?
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24 Mate Spin fails in Xorg to boot into graphical mode on Odroid-Xu4.

2016-08-12 Thread Peter Robinson 
> I cannot seem to get past Xorg failures to boot into graphical mode on my 
> Odroid-Xu4 running either the downloaded 4.5.5-300 based kernel system or the 
> "dnf update" 4.6.5-300 kernel based system and packages.  It appears that gbm 
> cannot find /usr/lib/dri/exynos_dri.so.
>
> Can someone help me get past this problem?  Do I need to install another 
> package containing the exynos_dri.so?  If so, which package?

It's in the libdrm package, not sure why it's looking for the
unversioned one. Are you using a binary driver from elsewhere or just
pure Fedora rpms?

Peter

> Thanks.
>
> Following are both the messages from my Xorg.0.log and the messages from 
> "startx" when I try to start it manually:
>
> Xorg.0.log
> -
> cat /var/log/Xorg.0.log
> [ 15846.637]
> X.Org X Server 1.18.4
> Release Date: 2016-07-19
> [ 15846.637] X Protocol Version 11, Revision 0
> [ 15846.637] Build Operating System:  4.6.3-300.fc24.armv7hl
> [ 15846.637] Current Operating System: Linux myodroid 4.6.5-300.fc24.armv7hl 
> #1 SMP Thu Jul 28 03:09:19 UTC 2016 armv7l
> [ 15846.637] Kernel command line: 
> rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro 
> root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=en_US.UTF-8
> [ 15846.637] Build Date: 19 July 2016  06:13:15PM
> [ 15846.637] Build ID: xorg-x11-server 1.18.4-1.fc24
> [ 15846.638] Current version of pixman: 0.34.0
> [ 15846.638]Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [ 15846.638] Markers: (--) probed, (**) from config file, (==) default 
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [ 15846.638] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 11 13:06:48 
> 2016
> [ 15846.643] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> [ 15846.644] (==) No Layout section.  Using the first Screen section.
> [ 15846.644] (==) No screen section available. Using defaults.
> [ 15846.644] (**) |-->Screen "Default Screen Section" (0)
> [ 15846.644] (**) |   |-->Monitor ""
> [ 15846.646] (==) No monitor specified for screen "Default Screen Section".
> Using a default monitor configuration.
> [ 15846.646] (==) Automatically adding devices
> [ 15846.647] (==) Automatically enabling devices
> [ 15846.647] (==) Automatically adding GPU devices
> [ 15846.647] (==) Max clients allowed: 256, resource mask: 0x1f
> [ 15846.647] (==) FontPath set to:
> catalogue:/etc/X11/fontpath.d,
> built-ins
> [ 15846.648] (==) ModulePath set to "/usr/lib/xorg/modules"
> [ 15846.648] (II) The server relies on udev to provide the list of input 
> devices.
> If no devices become available, reconfigure udev or disable 
> AutoAddDevices.
> [ 15846.648] (II) Loader magic: 0x1fcf3c
> [ 15846.648] (II) Module ABI versions:
> [ 15846.648]X.Org ANSI C Emulation: 0.4
> [ 15846.649]X.Org Video Driver: 20.0
> [ 15846.649]X.Org XInput driver : 22.1
> [ 15846.649]X.Org Server Extension : 9.0
> [ 15846.659] (--) using VT number 2
>
> [ 15846.659] (II) systemd-logind: logind integration requires -keeptty and 
> -keeptty was not provided, disabling logind integration
> [ 15846.669] (II) xfree86: Adding drm device (/dev/dri/card0)
> [ 15846.727] (II) no primary bus or device found
> [ 15846.727]falling back to /sys/devices/platform/exynos-drm/drm/card0
> [ 15846.727] (II) LoadModule: "glx"
> [ 15846.730] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
> [ 15846.810] (II) Module glx: vendor="X.Org Foundation"
> [ 15846.810]compiled for 1.18.4, module version = 1.0.0
> [ 15846.811]ABI class: X.Org Server Extension, version 9.0
> [ 15846.811] (==) AIGLX enabled
> [ 15846.812] (==) Matched modesetting as autoconfigured driver 0
> [ 15846.812] (==) Matched fbdev as autoconfigured driver 1
> [ 15846.812] (==) Assigned the driver to the xf86ConfigLayout
> [ 15846.812] (II) LoadModule: "modesetting"
> [ 15846.815] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> [ 15846.824] (II) Module modesetting: vendor="X.Org Foundation"
> [ 15846.824]compiled for 1.18.4, module version = 1.18.4
> [ 15846.824]Module class: X.Org Video Driver
> [ 15846.824]ABI class: X.Org Video Driver, version 20.0
> [ 15846.825] (II) LoadModule: "fbdev"
> [ 15846.827] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
> [ 15846.832] (II) Module fbdev: vendor="X.Org Foundation"
> [ 15846.832]compiled for 1.18.0, module version = 0.4.3
> [ 15846.832]Module class: X.Org Video Driver
> [ 15846.833]ABI class: X.Org Video Driver, version 20.0
> [ 15846.833] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [ 15846.833] (II) FBDEV: driver for framebuffer: fbdev
> [ 15846.924] (II) modeset(0): using drv /dev/dri/card0
> [ 15846.925] (WW) Falling back to old probe method for fbdev
> [ 15846.925] (II) Loading sub module