wrong monitor setting selected at boot

Moderators: odroid, mdrjr

wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 8:51 am

Hello. I just received my Odroid U3 today. At boot, I believe I have selected the wrong monitor output setting, since once I rebooted the unit (also expanded the file system), the monitor no longer displays anything. Is there a way to 'factory reset' the unit, so I can boot from scratch and get into the config screen?
Thank you.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby odroid » Fri Jan 17, 2014 10:08 am

Do you have a Linux host PC?
If yes, plug your SD or eMMC to your host PC via USB card reader.
And follow below instruction.

1. sudo rm -rf /media/ddd/etc/init/lightgm.conf
2. sudo cp /media/ddd/usr/local/hardkernel/tty1-first.conf /media/ddd/etc/init/tty1.conf
3. sudo cp /media/ddd/usr/local/hardkernel/odroid-config.sh /media/ddd/etc/profile.d/

Note that the "/media/ddd/" is the mounting point of the SD/eMMC.


If you don't have any Linux PC, use the Ubuntu Live CD/USB or reinstall the OS image.
User avatar
odroid
Site Admin
 
Posts: 21746
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 10:57 am

Thank you for the quick reply. I was successful in running those three commands, via my RaspberryPi. However, once I replace the emmc card, and reboot the Odroid U3, there is still nothing coming up on my monitor screen. Any further suggestions? Many thanks. Chris
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby Minou666 » Fri Jan 17, 2014 1:01 pm

Is the blue light flashing?
For me I have to disconnect the power and hdmi then connect power and quickly after that the hdmi cable. It doesn't boot otherwise. I have no such issue on the U2 or XU.
I get same results on both of my Odroid U3. I have a fan and battery on both.
My Monitor is a HP 2711x LED 1920x1080

Michel
Minou666
 
Posts: 142
Joined: Sat Sep 14, 2013 9:40 pm
Location: White Pigeon Michigan
languages_spoken: French and English
ODROIDs: Odroid C1 and XU3LITE

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 1:14 pm

Thanks for the reply Michael. Yes, the blue light flashes per the "heartbeat" definition on the Odroid pamphlet that shipped with the device.
No fan or battery on my U3. And I've tried connecting to the following monitors/TV's:
1) BenQ LCD monitor 1600x1050 (this is the monitor I first booted on; where I was able to see the config screen)
2) Samsung LCD TV 720p
3) LG LED 22EC33 (1920x1080 I think). Strangely enough, this monitor works with my (also new) SolidRun Cubox-i4 Pro, but not with the Odroid U3.
4) an old Dell 19inch LCD monitor (don't have the model # handy)
So the story is that I booted the Odroid U3 originally with the LG. Nothing showed on the screen (actually it flickered on/off non-stop, seemed to be between signal/no signal, but nothing really showing). Then, I moved the Odroid to the old BenQ, where it came up with the Config screen.
I wanted to use the LG, so I selected a monitor setting (don't recall now which one) that I thought was 'safe' for the LG (I believe it was a 720p selection). Then rebooted. Now, nothing works - it won't come up on any of the 4 monitors/TV listed above.
I just tried your trick of plugging in the HDMI connector only after plugging in the power. No difference in observed behavior unfortunately.
Again, thanks for the reply. Best regards,
Chris
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby mdrjr » Fri Jan 17, 2014 2:15 pm

Easy..

ssh to the board.

login as odroid/odroid

and run sudo odroid-config
:)

OR

connect the eMMC or SD to your PC.. the first partition, a fat partition will have a file named boot-auto.scr copy it to boot.scr (replace the old boot.scr there).
mdrjr
Site Admin
 
Posts: 11575
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 2:26 pm

So I was able to get the Odroid back alive by reflashing the emmc with the image located here: viewtopic.php?f=77&t=3238.
Next issue: if I set the Odroid to not boot into GUI, it boots fine into the command prompt. Username and password = odroid work fine.
However, if I set XOrg to run at boot, then it's not successful. I receive an error msg:
plymouthd: ply-terminal.c:611: ply_terminal_open: Assertion 'terminal != ((void *)0)' failed.

Apologies, but I don't understand this error message. This is repeatable; I've been able to reproduce this error 3 times now.

How can I boot to the desktop environment? I'd like to use this device as a Linux PC.
Thanks again for all the help.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby mdrjr » Fri Jan 17, 2014 2:36 pm

Plymounth has nothing to do with Xorg not starting..

PLease post the xorg.0.log its on /var/log

Does the console works fine ?
mdrjr
Site Admin
 
Posts: 11575
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 2:46 pm

Thanks for the quick reply mdrjr. I appreciate the help.
Forgive the noob question, but how do I go about locating the xorg.0.log?
I'm at the base command prompt, and I do not see /var/log when I enter 'dir'
Again, thanks for the help.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 2:49 pm

OK sorry, nm. I figured out how to get into /var/log. However, I don't see the xorg.0.log file.
thx
C
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 3:05 pm

If, at the command prompt, I type "sudo startx", the next line is:
[sudo] password for odroid:
I type in "odroid", hit enter
Nothing happens for about a minute or two
then, I get the following line returned:
xauth: timeout in locking authority file /home/odroid/.Xauthority

If then I let it sit - about another minute goes by, and then the screen clears, and at the top, I receive the plymouthd line I had noted earlier in this thread.

Any suggestions?

Many thx
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby mdrjr » Fri Jan 17, 2014 3:08 pm

I'm not understanding what you did here..

Here's what you have to do..

Reflash the sdcard or eMMC again.. clear image.

Let it first boot..
It will first boot onto ODROID Configurator.
Select JUST Expact Filesystem
Leave ODROID Configurator
it will ask for reboot
reboot it..
It will drop you to the X window
mdrjr
Site Admin
 
Posts: 11575
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 3:21 pm

Thanks. OK, I ran through that routine. It worked fine, but, I do not enter X. Instead, after reboot, I end up with the plymouthd error.

To confirm, here's what I did:
- reflashed the emmc (using Win32 diskimager on Win7 PC)
- booted the Odroid
- it booted fine into odroid-config
- I selected "expand". It zipped through that in ~2 seconds
- then, back at the odroid-config menu, I selected "Finish".
- asked me to reboot now, I did

Reboot, next screen I see is the blank screen with the plymouthd line. Then, sits there....

Background: I am comfortable with the process outlined above. It's the same as what I've been doing with my RPi, which I've owned since 10/2012. I don't understand why this isn't working...

Thanks again for the help.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby mdrjr » Fri Jan 17, 2014 3:33 pm

Hmmm.....

edit /etc/X11/xorg.conf
and change the line

Driver "mali"
to
Driver "fbdev"

reboot the board, let me know if X starts..
mdrjr
Site Admin
 
Posts: 11575
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: wrong monitor setting selected at boot

Unread postby chrisa » Fri Jan 17, 2014 9:45 pm

Hi. Thanks. OK, I used nano to edit the xorg.conf file. No luck. After making the change you requested, then rebooting, then launching GUI with "sudo startx", I get the same problem as before, beginning with the "auth" message. After waiting a minute or two, nothing more - except that the screen goes completely blank this time. I do not end up with the plymouthd message like I was seeing yesterday.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby mdrjr » Fri Jan 17, 2014 9:48 pm

chrisa wrote:Hi. Thanks. OK, I used nano to edit the xorg.conf file. No luck. After making the change you requested, then rebooting, then launching GUI with "sudo startx", I get the same problem as before, beginning with the "auth" message. After waiting a minute or two, nothing more - except that the screen goes completely blank this time. I do not end up with the plymouthd message like I was seeing yesterday.


check if the permissions of the ~odroid/.Xauthority file is correct. it should be odroid:odroid
mdrjr
Site Admin
 
Posts: 11575
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: wrong monitor setting selected at boot

Unread postby Minou666 » Sat Jan 18, 2014 3:25 am

then rebooting, then launching GUI with "sudo startx",


Make sure you log as odroid and not root.

With sudo you would be logging as root. Do not use sudo, just startx. Check files to make sure they are not owned by root.
ls -la will show you even the hidden files (ones starting with a .)

If files that are supposed to be owned by odroid are owned by root you will get errors.

As mdrjr said .Xauthority is supposed to be owned by odroid, if not do this :

sudo chown odroid.odroid .Xauthority

When it is the whole directory that needs to change you add -R after chown
For example if a gnome directory is owned by root you will have some serious issues. Normally every files and directory on your user are supposed to be owned by that user.

Michel
Minou666
 
Posts: 142
Joined: Sat Sep 14, 2013 9:40 pm
Location: White Pigeon Michigan
languages_spoken: French and English
ODROIDs: Odroid C1 and XU3LITE

Re: wrong monitor setting selected at boot

Unread postby chrisa » Sat Jan 18, 2014 1:14 pm

Thanks mdrjr, Minou666 for the comments and continued support.
Finally, after a day at work and evening with the kiddos, I'm back in front of the Odroid.
@mdrjr, I need a little more help on your suggestion. How do I "check if the permissions of the ~odroid/.Xauthority file is correct. it should be odroid:odroid"? I tried to nano open that file, but it seems to be a binary so not readable? How do I perform this check?
@Minou666, I tried your suggestion of launching X with simply "startx" instead of "sudo startx". Unfortunately, I get the same xauth error. I confirm that I am logging into the Odroid with username & pword as "odroid".
I then tried the command "sudo chown odroid.odroid .Xauthority" per Minou666's suggestion. That was accepted fine, no error. However, when I try "startx" or "sudo startx" i still get nothing, no change. I end up with the xauth error.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby Minou666 » Sun Jan 19, 2014 2:02 am

How do I "check if the permissions of the ~odroid/.Xauthority file is correct


Do "ls -la"

odroid@odroid:~$ ls -la
total 196
drwxr-xr-x 28 odroid odroid 4096 Jan 18 08:39 .
drwxr-xr-x 3 root root 4096 Apr 2 2013 ..
-rw------- 1 odroid odroid 18 Jan 16 20:54 .bash_history
-rw-r--r-- 1 odroid odroid 220 Dec 3 17:56 .bash_logout
-rw-r--r-- 1 odroid odroid 3637 Dec 3 17:56 .bashrc
drwx------ 35 odroid odroid 4096 Jan 18 08:39 .cache
drwx------ 48 odroid odroid 4096 Jan 16 20:49 .config
drwx------ 3 odroid odroid 4096 Jun 5 2013 .dbus
drwxr-xr-x 2 odroid odroid 4096 Dec 20 22:08 Desktop
-rw------- 1 odroid odroid 61 Dec 13 16:19 .directory
-rw-r--r-- 1 odroid odroid 35 Jan 16 20:49 .dmrc
drwxr-xr-x 2 odroid odroid 4096 Jun 8 2013 Documents
drwxr-xr-x 2 odroid odroid 4096 Dec 21 00:37 Downloads
drwx------ 4 odroid odroid 4096 Jan 18 08:39 .gconf
drwx------ 2 odroid odroid 4096 Dec 19 22:38 .gnome2
drwxrwxr-x 2 odroid odroid 4096 Jan 16 20:49 .gstreamer-0.10
-rw-rw-r-- 1 odroid odroid 184 Jun 13 2013 .gtk-bookmarks
drwx------ 2 root root 4096 Jun 4 2013 .gvfs
-rw------- 1 odroid odroid 22598 Jan 18 08:39 .ICEauthority
drwx------ 3 odroid odroid 4096 Dec 3 14:46 .icons
-rw------- 1 root root 1729 Jan 7 07:02 .joe_state
drwxr-xr-x 3 odroid odroid 4096 Apr 16 2013 .local
drwxr-xr-x 2 odroid odroid 4096 Dec 21 00:23 .mplayer
drwxr-xr-x 2 odroid odroid 4096 Dec 31 1999 Music
-rw-r--r-- 1 odroid odroid 259 Jun 4 2013 .pam_environment
drwxr-xr-x 3 odroid odroid 4096 Dec 21 00:20 Pictures
drwx------ 3 odroid odroid 4096 Apr 1 2013 .pki
-rw-r--r-- 1 odroid odroid 675 Dec 3 17:56 .profile
drwxr-xr-x 2 odroid odroid 4096 Dec 31 1999 Public
drwx------ 2 odroid odroid 4096 Dec 10 08:36 .pulse
drwx------ 2 odroid odroid 4096 Jun 6 2013 .synaptic
drwxr-xr-x 2 odroid odroid 4096 Dec 31 1999 Templates
drwxrwxr-x 2 odroid odroid 4096 Jan 16 20:49 .themes
drwx------ 4 odroid odroid 4096 Dec 19 22:38 .thumbnails
drwxr-xr-x 2 odroid odroid 4096 Dec 31 1999 Videos
-rw------- 1 odroid odroid 102 Jan 18 08:39 .Xauthority
-rw------- 2 odroid odroid 0 Jan 3 15:29 .Xauthority-c
-rw------- 2 odroid odroid 0 Jan 3 15:29 .Xauthority-l
drwxr-xr-x 8 root odroid 4096 Jan 3 15:37 .xbmc
-rw-rw-r-- 1 odroid odroid 26 Dec 5 20:11 .Xdefaults
drwxr-xr-x 2 odroid odroid 4096 Dec 21 00:24 .xine
drwxrwxr-x 2 odroid odroid 4096 Apr 4 2013 .xinput.d
-rw-r--r-- 1 odroid odroid 14 Apr 25 2013 .xscreensaver
-rw------- 1 odroid odroid 1445 Jan 18 08:44 .xsession-errors
-rw------- 1 odroid odroid 1994 Jan 18 08:38 .xsession-errors.old
-rw-rw-r-- 1 odroid odroid 43 Oct 3 07:53 .xsessionrc

As you can see there is something bizarre here, I don't understand why .gvfs is owned by root. As for joe this is weird and ubuntu is probably the culprit.
On archlinux it writes the joe status file on root if I access as root. Now if I try to use joe as a user it bombs out. The cure will be to change to be owned by the user.

odroid@odroid:~$ sudo chown odroid.odroid .joe_state
[sudo] password for odroid:
odroid@odroid:~$ ls -la .joe_state
-rw------- 1 odroid odroid 1729 Jan 7 07:02 .joe_state

Changing owner is rather simple, you need to get root privileges with sudo to do that


Michel
Minou666
 
Posts: 142
Joined: Sat Sep 14, 2013 9:40 pm
Location: White Pigeon Michigan
languages_spoken: French and English
ODROIDs: Odroid C1 and XU3LITE

Re: wrong monitor setting selected at boot

Unread postby chrisa » Sun Jan 19, 2014 3:05 am

Thanks Mike. OK, what I have for the two items you pointed out:
drwx------ 2 root root 4096 Jun 4 2013 .gvfs
-rw------- 1 root root 1729 Jan 7 2014 .joe_state

(note that my .joe_state says "2014" but yours says "07:02". Not sure if that matters.)

I then did the chown command and now have:
-rw------- 1 odroid odroid 1729 Jan 7 2014 .joe_state

Also, in looking through the rest of what's printed on the screen, I see:
-rw------ 1 odroid odroid 102 Jan 3 2014 .Xauthority

So it looks like odroid should have permissions to launch X? (after making & confirming the above change, I tried startx but no luck, no change in behavior).

Should I change gvfs to odroid odroid?

Thanks again for the help.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby mdrjr » Sun Jan 19, 2014 7:16 am

you haven't post so far the Xorg.0.log and the dmesg log...
mdrjr
Site Admin
 
Posts: 11575
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: wrong monitor setting selected at boot

Unread postby chrisa » Sun Jan 19, 2014 10:28 am

Ah correct. Sorry about that. Please see:

dmesg

[ 0.000000] Booting Linux on physical CPU 0xa00
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Linux version 3.8.13.14 (root@sa1) (gcc version 4.8.2 20130902 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.09 - Linaro GCC 2013.09) ) #1 SMP PREEMPT Sat Dec 21 00:55:27 CST 2013 ()
[ 0.000000] Kernel was built at commit id 'de53ccf'
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: ODROIDU2
[ 0.000000] cma: CMA: reserved 64 MiB at 43000000
[ 0.000000] cma: CMA: reserved 64 MiB at 51000000
[ 0.000000] cma: CMA: reserved 128 MiB at 67800000
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] CPU EXYNOS4412 (id 0xe4412220)
[ 0.000000] exynos4_init_clocks: initializing clocks
[ 0.000000] S3C24XX Clocks, Copyright 2004 Simtec Electronics
[ 0.000000] s3c_register_clksrc: clock armclk has no registers set
[ 0.000000] s3c_register_clksrc: clock audiocdclk has no registers set
[ 0.000000] audiocdclk: no parent clock specified
[ 0.000000] exynos4_setup_clocks: registering clocks
[ 0.000000] exynos4_setup_clocks: xtal is 24000000
[ 0.000000] EXYNOS4: PLL settings, A=1000000000, M=880000000, E=96000000 V=350000000
[ 0.000000] EXYNOS4: ARMCLK=1000000000, DMC=440000000, ACLK200=176000000
[ 0.000000] ACLK100=110000000, ACLK160=176000000, ACLK133=146666666
[ 0.000000] sclk_pwm: source is ext_xtal (0), rate is 24000000
[ 0.000000] sclk_csis: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_csis: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_cam0: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_cam1: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[ 0.000000] sclk_fimd: source is mout_mpll_user (6), rate is 55000000
[ 0.000000] sclk_mfc: source is mout_mfc0 (0), rate is 55000000
[ 0.000000] sclk_g3d: source is mout_g3d0 (0), rate is 55000000
[ 0.000000] On node 0 totalpages: 524032
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 193040 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2574 pages used for memmap
[ 0.000000] HighMem zone: 326898 pages, LIFO batch:31
[ 0.000000] Running under secure firmware.
[ 0.000000] PERCPU: Embedded 7 pages/cpu @c16c1000 s7936 r8192 d12544 u32768
[ 0.000000] pcpu-alloc: s7936 r8192 d12544 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 519938
[ 0.000000] Kernel command line: console=tty1 console=ttySAC1,115200 mem=2047M fbcon=map:1111111111111111111111111111 console=tty1 console=ttySAC1,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro mem=2047M
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] Memory: 2047MB = 2047MB total
[ 0.000000] Memory: 1806352k/3612704k available, 579552k reserved, 1317888K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc05de148 (5977 kB)
[ 0.000000] .init : 0xc05df000 - 0xc0609f00 ( 172 kB)
[ 0.000000] .data : 0xc060a000 - 0xc066f760 ( 406 kB)
[ 0.000000] .bss : 0xc066f760 - 0xc06abb10 ( 241 kB)
[ 0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:549
[ 0.000000] MCT clocksource init timer with clk_rate=24000000 hz
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty1] enabled
[ 0.000736] Calibrating delay loop... 1992.29 BogoMIPS (lpj=4980736)
[ 0.045057] pid_max: default: 32768 minimum: 301
[ 0.045315] Mount-cache hash table entries: 512
[ 0.046296] Initializing cgroup subsys cpuacct
[ 0.046328] Initializing cgroup subsys devices
[ 0.046383] CPU: Testing write buffer coherency: ok
[ 0.046685] CPU0: thread -1, cpu 0, socket 10, mpidr 80000a00
[ 0.046804] Setting up static identity map for 0x40454b68 - 0x40454bc0
[ 0.046877] L310 cache controller enabled
[ 0.046903] l2x0: 16 ways, CACHE_ID 0x4100c4c8, AUX_CTRL 0x7e470001, Cache size: 1048576 B
[ 0.097029] CPU1: Booted secondary processor
[ 0.116737] CPU1: thread -1, cpu 1, socket 10, mpidr 80000a01
[ 0.127020] CPU2: Booted secondary processor
[ 0.146737] CPU2: thread -1, cpu 2, socket 10, mpidr 80000a02
[ 0.157032] CPU3: Booted secondary processor
[ 0.176737] CPU3: thread -1, cpu 3, socket 10, mpidr 80000a03
[ 0.176767] Brought up 4 CPUs
[ 0.176834] SMP: Total of 4 processors activated (7969.17 BogoMIPS).
[ 0.177652] devtmpfs: initialized
[ 0.183819] regulator-dummy: no parameters
[ 0.191168] NET: Registered protocol family 16
[ 0.198473] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.203478] s5p_hdmi_cec_set_platdata()
[ 0.207753] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.207776] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.207866] S3C Power Management, Copyright 2004 Simtec Electronics
[ 0.207949] EXYNOS4x12 PMU Initialize
[ 0.209815] EXYNOS: Initializing architecture
[ 0.210583] s3c24xx-pwm s3c24xx-pwm.0: tin at 110000000, tdiv at 110000000, tin=divclk, base 0
[ 0.210658] s3c24xx-pwm s3c24xx-pwm.1: tin at 110000000, tdiv at 110000000, tin=divclk, base 8
[ 0.223485] bio: create slab <bio-0> at 0
[ 0.224039] hdmi_5v: 5000 mV
[ 0.225425] usbcore: registered new interface driver usbfs
[ 0.225541] usbcore: registered new interface driver hub
[ 0.225674] usbcore: registered new device driver usb
[ 0.226227] i2c-gpio i2c-gpio.2: using pins 6 (SDA) and 7 (SCL)
[ 0.226397] i2c-gpio i2c-gpio.4: using pins 200 (SDA) and 199 (SCL)
[ 0.226571] s3c-i2c s3c2440-i2c.0: slave address 0x10
[ 0.226593] s3c-i2c s3c2440-i2c.0: bus frequency set to 214 KHz
[ 0.227127] max77686 0-0009: device found
[ 0.229063] LDO1 VDD_ALIVE: 1000 mV
[ 0.230684] LDO2 VDDQ_M1_1V8: 1800 mV
[ 0.232169] LDO3 VDDQ_AUD_1V8: 1800 mV
[ 0.233694] LDO4 VDDQ_MMC2_2V8: 2800 mV
[ 0.235152] LDO5 VDDQ_MMC1_1V8: 1800 mV
[ 0.236756] LDO6 VDD10_MPLL_1V0: 1000 mV
[ 0.238362] LDO7 VDD10_EPLL_1V0: 1000 mV
[ 0.239799] LDO8 VDD10_MIPI_1V0: 1000 mV
[ 0.241200] LDO9 VT_CORE_1V0: ODROIDU2: Disabled regulator
[ 0.241218] LDO9 VT_CORE_1V0: 1000 mV
[ 0.242192] LDO10 VDD18_MIPI_1V8: 1800 mV
[ 0.243652] LDO11 VDD18_ABB1_1V8: 1800 mV
[ 0.244625] vdd_ldo12 range: 3300 mV
[ 0.246069] LDO13 VDD18_MIPIHSI_1V8: 1800 mV
[ 0.247526] LDO14 VDD18_ADC_1V8: 1800 mV
[ 0.248509] vdd_ldo15 range: 1000 mV
[ 0.249951] LDO16 VDD18_HSIC: 1800 mV
[ 0.251494] LDO17 VDDQ_CAM_1V8: 1800 mV
[ 0.252787] LDO18 VDDQ_ISP_1V8: ODROIDU2: Disabled regulator
[ 0.252805] LDO18 VDDQ_ISP_1V8: 1800 mV
[ 0.253430] LDO19 VT_CAM_1V8: ODROIDU2: Disabled regulator
[ 0.253447] LDO19 VT_CAM_1V8: 1800 mV
[ 0.254420] vddq_emmc_1V8: 1800 <--> 3000 mV at 1800 mV
[ 0.255812] LDO21 TFLASH_2V8: 2800 mV
[ 0.257364] vddf_emmc_2V85: 2850 mV
[ 0.258756] LDO23 VDD_TOUCH_2V8: ODROIDU2: Disabled regulator
[ 0.258774] LDO23 VDD_TOUCH_2V8: 2800 mV
[ 0.260170] LDO24 VDD_TOUCHLED_3V3: ODROIDU2: Disabled regulator
[ 0.260189] LDO24 VDD_TOUCHLED_3V3: 3300 mV
[ 0.261801] LDO25 VDDQ_LCD_3V0: 1800 mV
[ 0.263039] LDO26 VDD_MOTOR_3V0: ODROIDU2: Disabled regulator
[ 0.263056] LDO26 VDD_MOTOR_3V0: 3000 mV
[ 0.263666] BUCK1 vdd_mif: 1100 mV
[ 0.264493] BUCK2 vdd_arm: 800 <--> 1500 mV at 1100 mV
[ 0.265114] BUCK3 vdd_int: 1125 mV
[ 0.265939] BUCK4 vdd_g3d: 850 <--> 1200 mV at 1000 mV
[ 0.267379] BUCK5 VDDQ_CKEM1_2: 1200 mV
[ 0.268829] BUCK6 1V35: 1350 mV
[ 0.270275] BUCK7 2V0: 2000 mV
[ 0.270902] ODROIDU2: Regulator BUCK8
[ 0.392007] BUCK8 3V0: 3300 mV
[ 0.393245] BUCK9 1V2: ODROIDU2: Disabled regulator
[ 0.393262] BUCK9 1V2: 1200 mV
[ 0.393813] s3c-i2c s3c2440-i2c.0: i2c-0: S3C I2C adapter
[ 0.393894] s3c-i2c s3c2440-i2c.1: slave address 0x10
[ 0.393915] s3c-i2c s3c2440-i2c.1: bus frequency set to 214 KHz
[ 0.394190] s3c-i2c s3c2440-i2c.1: i2c-1: S3C I2C adapter
[ 0.394255] s3c-i2c s3c2440-i2c.3: slave address 0x10
[ 0.394276] s3c-i2c s3c2440-i2c.3: bus frequency set to 214 KHz
[ 0.394440] s3c-i2c s3c2440-i2c.3: i2c-3: S3C I2C adapter
[ 0.394499] s3c-i2c s3c2440-i2c.7: slave address 0x10
[ 0.394519] s3c-i2c s3c2440-i2c.7: bus frequency set to 214 KHz
[ 0.394671] s3c-i2c s3c2440-i2c.7: i2c-7: S3C I2C adapter
[ 0.394735] s3c-i2c s3c2440-hdmiphy-i2c: slave address 0x10
[ 0.394755] s3c-i2c s3c2440-hdmiphy-i2c: bus frequency set to 214 KHz
[ 0.395027] s3c-i2c s3c2440-hdmiphy-i2c: i2c-8: S3C I2C adapter
[ 0.395142] media: Linux media interface: v0.10
[ 0.395247] Linux video capture interface: v2.00
[ 0.395983] Advanced Linux Sound Architecture Driver Initialized.
[ 0.396941] cfg80211: Calling CRDA to update world regulatory domain
[ 0.397541] Switching to clocksource mct-frc
[ 0.409116] NET: Registered protocol family 2
[ 0.409583] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.409712] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[ 0.409880] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.409940] TCP: reno registered
[ 0.409961] UDP hash table entries: 512 (order: 2, 24576 bytes)
[ 0.410004] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[ 0.410231] NET: Registered protocol family 1
[ 0.410391] Trying to unpack rootfs image as initramfs...
[ 0.553816] Freeing initrd memory: 2848K
[ 0.554018] CPU PMU: probing PMU on CPU 1
[ 0.554044] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.555835] bounce pool size: 64 pages
[ 0.565123] msgmni has been set to 1471
[ 0.565922] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 0.565945] io scheduler noop registered
[ 0.565958] io scheduler deadline registered
[ 0.566169] io scheduler cfq registered (default)
[ 0.571850] s3c-fb exynos4-fb.0: start latency exceeded, new value 583 ns
[ 0.571903] s3c-fb exynos4-fb.0: state restore latency exceeded, new value 31208 ns
[ 0.581538] s3c-fb exynos4-fb.0: window 0: fb
[ 0.586050] dma-pl330 dma-pl330.0: Loaded driver for PL330 DMAC-267056
[ 0.586072] dma-pl330 dma-pl330.0: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 0.590397] dma-pl330 dma-pl330.1: Loaded driver for PL330 DMAC-267056
[ 0.590419] dma-pl330 dma-pl330.1: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 0.591751] dma-pl330 dma-pl330.2: Loaded driver for PL330 DMAC-267056
[ 0.591773] dma-pl330 dma-pl330.2: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[ 0.662480] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.663746] exynos4210-uart.0: ttySAC0 at MMIO 0x13800000 (irq = 84) is a S3C6400/10
[ 0.664035] exynos4210-uart.1: ttySAC1 at MMIO 0x13810000 (irq = 85) is a S3C6400/10
[ 1.682449] console [ttySAC1] enabled
[ 1.686412] exynos4210-uart.2: ttySAC2 at MMIO 0x13820000 (irq = 86) is a S3C6400/10
[ 1.694085] exynos4210-uart.3: ttySAC3 at MMIO 0x13830000 (irq = 87) is a S3C6400/10
[ 1.702108] [drm] Initialized drm 1.1.0 20060810
[ 1.706453] i2c i2c-2: attached s5p_ddc into i2c adapter successfully
[ 1.712695] i2c i2c-8: attached s5p_hdmiphy into i2c adapter successfully
[ 1.719698] exynos-mixer s5p-mixer: probe start
[ 1.724386] s5p-g2d s5p-g2d.0: The exynos g2d(ver 4.1) successfully probed
[ 1.731591] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 1.737267] [drm] No driver support for vblank timestamp query.
[ 1.743858] exynos-drm exynos-drm: No connectors reported connected with modes
[ 1.750380] [drm] Cannot find any crtc or sizes - going 1024x768
[ 1.773092] Console: switching to colour frame buffer device 128x48
[ 1.783895] exynos-drm exynos-drm: fb1: frame buffer device
[ 1.789528] exynos-drm exynos-drm: registered panic notifier
[ 1.795173] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[ 1.800986] Mali<2>: Inserting Mali v19 device driver.
[ 1.806112] Mali<2>: Compiled: Dec 21 2013, time: 00:52:10.
[ 1.811670] Mali<2>: Driver revision:
[ 1.815363] Mali<2>: mali_module_init() registering driver
[ 1.820919] Mali<2>: mali_probe(): Called for platform device mali-utgard
[ 1.827666] Mali<2>: Memory system initializing
[ 1.832117] Mali<2>: Using device defined memory settings (dedicated: 0x00000000@0x00000000, shared: 0x10000000)
[ 1.842389] Mali<2>: Mali OS memory allocator created with max allocation size of 0x10000000 bytes, cpu_usage_adjust 0x00000000
[ 1.853867] Mali<2>: Using device defined frame buffer settings (0x00000000@0x00000000)
[ 1.866506] mali-utgard mali-utgard.0: start latency exceeded, new value 500 ns
[ 1.873866] mali-utgard mali-utgard.0: state restore latency exceeded, new value 2917 ns
[ 1.881892] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
[ 1.887526] Mali<2>: Mali PP: Base address of PP core: 0x13008000
[ 1.893638] Mali<2>: Found Mali GPU Mali-400 MP r1p1
[ 1.899648] Mali<2>: Mali L2 cache: Creating Mali L2 cache: Mali_L2
[ 1.905022] Mali<2>: Mali MMU: Creating Mali MMU: Mali_GP_MMU
[ 1.910736] Mali<2>: Mali GP: Creating Mali GP core: Mali_GP
[ 1.916313] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP0_MMU
[ 1.922073] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
[ 1.927728] Mali<2>: Mali PP: Base address of PP core: 0x13008000
[ 1.933772] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP1_MMU
[ 1.939521] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP1
[ 1.945165] Mali<2>: Mali PP: Base address of PP core: 0x1300a000
[ 1.951274] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP2_MMU
[ 1.957042] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP2
[ 1.962705] Mali<2>: Mali PP: Base address of PP core: 0x1300c000
[ 1.968743] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP3_MMU
[ 1.974486] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP3
[ 1.980171] Mali<2>: Mali PP: Base address of PP core: 0x1300e000
[ 1.986246] Mali<2>: 4+0 PP cores initialized
[ 1.990526] Mali<2>: Mali GPU Utilization: No utilization handler installed
[ 1.997534] Mali<2>: = clk_set_rate : 533 , 1000000
[ 2.002779] Mali<2>: = clk_get_rate: 533
[ 2.006894] Mali: init_mali_clock mali_clock c0631aa8
[ 2.011690] Mali<1>: = regulator_enable -> use cnt: 1
[ 2.016479] Mali<2>: = regulator_set_voltage: 1125000, 1125000
[ 2.023653] Mali<1>: = regulator_get_voltage: 1125000
[ 2.027618] Mali<2>: MALI Clock is set at mali driver
[ 2.032792] Mali<2>: mali_probe(): Successfully initialized driver for platform device mali-utgard
[ 2.041442] mali-utgard mali-utgard.0: stop latency exceeded, new value 584 ns
[ 2.048749] mali-utgard mali-utgard.0: state save latency exceeded, new value 3750 ns
[ 2.056880] Mali: Mali device driver loaded
[ 2.061206] UMP: UMP device driver loaded
[ 2.072768] brd: module loaded
[ 2.080788] loop: module loaded
[ 2.084878] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.089990] s5p-ehci s5p-ehci: S5P EHCI Host Controller
[ 2.094996] s5p-ehci s5p-ehci: new USB bus registered, assigned bus number 1
[ 2.102357] s5p-ehci s5p-ehci: irq 102, io mem 0x12580000
[ 2.112603] s5p-ehci s5p-ehci: USB 2.0 started, EHCI 1.00
[ 2.116399] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.122804] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.129949] usb usb1: Product: S5P EHCI Host Controller
[ 2.135135] usb usb1: Manufacturer: Linux 3.8.13.14 ehci_hcd
[ 2.140727] usb usb1: SerialNumber: s5p-ehci
[ 2.145434] hub 1-0:1.0: USB hub found
[ 2.149004] hub 1-0:1.0: 3 ports detected
[ 2.152970] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 2.158900] exynos-ohci exynos-ohci: Already power on PHY
[ 2.164228] exynos-ohci exynos-ohci: EXYNOS OHCI Host Controller
[ 2.170200] exynos-ohci exynos-ohci: new USB bus registered, assigned bus number 2
[ 2.177799] exynos-ohci exynos-ohci: irq 102, io mem 0x12590000
[ 2.241640] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 2.246409] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.253649] usb usb2: Product: EXYNOS OHCI Host Controller
[ 2.259083] usb usb2: Manufacturer: Linux 3.8.13.14 ohci_hcd
[ 2.264714] usb usb2: SerialNumber: exynos-ohci
[ 2.269656] hub 2-0:1.0: USB hub found
[ 2.273309] hub 2-0:1.0: 3 ports detected
[ 2.407840] usb3503 0-0008: USB3503_SP_ILOCK = 0x32
[ 2.413475] usb3503 0-0008: switched to HUB mode
[ 2.462608] usb 1-2: new high-speed USB device number 2 using s5p-ehci
[ 2.517607] usb3503 0-0008: usb3503_probe: probed on hub mode
[ 2.521549] max77686-rtc max77686-rtc: max77686_rtc_probe
[ 2.592985] usb 1-2: New USB device found, idVendor=0424, idProduct=9730
[ 2.597749] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.628287] max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as rtc0
[ 2.636343] s5p-fimc exynos4-fimc.0: sclk_fimc rate is 176000000
[ 2.640568] s5p-fimc exynos4-fimc.0: start latency exceeded, new value 625 ns
[ 2.647714] s5p-fimc exynos4-fimc.0: state restore latency exceeded, new value 16208 ns
[ 2.655726] s5p-fimc exynos4-fimc.0: stop latency exceeded, new value 583 ns
[ 2.662685] s5p-fimc exynos4-fimc.0: state save latency exceeded, new value 3417 ns
[ 2.667665] s5p-fimc exynos4-fimc.1: sclk_fimc rate is 176000000
[ 2.676210] s5p-fimc exynos4-fimc.1: start latency exceeded, new value 459 ns
[ 2.683315] s5p-fimc exynos4-fimc.1: state restore latency exceeded, new value 15000 ns
[ 2.691320] s5p-fimc exynos4-fimc.1: stop latency exceeded, new value 458 ns
[ 2.698347] s5p-fimc exynos4-fimc.1: state save latency exceeded, new value 2333 ns
[ 2.702659] s5p-fimc exynos4-fimc.2: sclk_fimc rate is 176000000
[ 2.711967] s5p-fimc exynos4-fimc.2: start latency exceeded, new value 458 ns
[ 2.719092] s5p-fimc exynos4-fimc.2: state restore latency exceeded, new value 14834 ns
[ 2.727083] s5p-fimc exynos4-fimc.2: stop latency exceeded, new value 416 ns
[ 2.734089] s5p-fimc exynos4-fimc.2: state save latency exceeded, new value 2458 ns
[ 2.734175] s5p-fimc exynos4-fimc.3: sclk_fimc rate is 176000000
[ 2.747677] s5p-fimc exynos4-fimc.2: stop latency exceeded, new value 458 ns
[ 2.754723] s5p-fimc exynos4-fimc.3: start latency exceeded, new value 458 ns
[ 2.761824] s5p-fimc exynos4-fimc.3: state restore latency exceeded, new value 14875 ns
[ 2.769822] s5p-fimc exynos4-fimc.3: stop latency exceeded, new value 458 ns
[ 2.776839] s5p-fimc exynos4-fimc.3: state save latency exceeded, new value 2250 ns
[ 2.778140] s5p-fimc-md: Registered fimc.0.m2m as /dev/video0
[ 2.778311] s5p-fimc-md: Registered fimc.0.capture as /dev/video1
[ 2.778478] s5p-fimc-md: Registered fimc.1.m2m as /dev/video2
[ 2.778645] s5p-fimc-md: Registered fimc.1.capture as /dev/video3
[ 2.778813] s5p-fimc-md: Registered fimc.2.m2m as /dev/video4
[ 2.778977] s5p-fimc-md: Registered fimc.2.capture as /dev/video5
[ 2.779142] s5p-fimc-md: Registered fimc.3.m2m as /dev/video6
[ 2.779309] s5p-fimc-md: Registered fimc.3.capture as /dev/video7
[ 2.780128] sclk_mfc rate is: 220
[ 2.780344] s5p-mfc s5p-mfc: decoder registered as /dev/video8
[ 2.780514] s5p-mfc s5p-mfc: encoder registered as /dev/video9
[ 2.781085] Exynos: Kernel Thermal management registered
[ 2.781317] cpuidle: using governor ladder
[ 2.781409] sdhci: Secure Digital Host Controller Interface driver
[ 2.781411] sdhci: Copyright(c) Pierre Ossman
[ 2.781499] s3c-sdhci exynos4-sdhci.2: clock source 2: mmc_busclk.2 (440000000 Hz)
[ 2.781561] mmc0: no vqmmc regulator found
[ 2.781568] mmc0: no vmmc regulator found
[ 2.807603] mmc0: SDHCI controller on samsung-hsmmc [exynos4-sdhci.2] using ADMA
[ 2.889284] s5p-fimc exynos4-fimc.3: stop latency exceeded, new value 625 ns
[ 2.893028] dw_mmc dw_mmc: Using internal DMA controller.
[ 2.927615] DWMMC: Div 2 = 130
[ 2.927655] dw_mmc dw_mmc: Version ID is 240a
[ 2.927662] dw_mmc dw_mmc: DW MMC controller at irq 109, 32 bit host data width, 128 deep fifo
[ 2.942173] mmc_host mmc1: Bus speed (slot 0) = 104000000Hz (slot req 400000Hz, actual 400000HZ div = 130)
[ 2.943521] usbcore: registered new interface driver usbhid
[ 2.943523] usbhid: USB HID core driver
[ 2.943642] cec: Probe start
[ 2.943645] s5p_cec_probe: pdata=e70e9640
[ 2.943664] s5p_cec_mem_probe(): mapped cec_base to f0096000, size 0x1000
[ 2.943848] cec: Requesting irq 146 for s5p-cec
[ 2.943884] cec: probe successful
[ 2.967824] max98090 1-0010: MAX98090 REVID=0x43
[ 2.987209] usb 1-3: new high-speed USB device number 3 using s5p-ehci
[ 2.996308] hkdk-snd-max98090 hkdk-snd-max98090: HiFi <-> samsung-i2s.0 mapping ok
[ 3.005385] hkdk-snd-max98090 hkdk-snd-max98090: HiFi <-> samsung-i2s.0 mapping ok
[ 3.012719] TCP: cubic registered
[ 3.016443] NET: Registered protocol family 17
[ 3.020206] NET: Registered protocol family 15
[ 3.023888] NET: Registered protocol family 35
[ 3.027974] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 3.035369] ThumbEE CPU extension supported.
[ 3.039632] Registering SWP/SWPB emulation handler
[ 3.046474] LDO10 VDD18_MIPI_1V8: incomplete constraints, leaving on
[ 3.050858] mmc1: BKOPS_EN bit is not set
[ 3.051317] DRM: mali_platform_drm_probe()
[ 3.051321] mali_drm_init(), driver name: mali_drm, version 0.1
[ 3.051609] DRM: mali_driver_load()
[ 3.051636] [drm] Initialized mali_drm 0.1.0 20100520 on minor 1
[ 3.074434] max77686-rtc max77686-rtc: setting system clock to 2000-01-01 01:00:06 UTC (946688406)
[ 3.084416] DWMMC: Div 2 = 1
[ 3.088447] mmc_host mmc1: Bus speed (slot 0) = 104000000Hz (slot req 52000000Hz, actual 52000000HZ div = 1)
[ 3.097280] mmc1: new high speed DDR MMC card at address 0001
[ 3.102721] exynos4_dvfs_hotplug_init, max(2000000),min(0)
[ 3.102879] mmcblk0: mmc1:0001 008G92 7.28 GiB
[ 3.102987] mmcblk0boot0: mmc1:0001 008G92 partition 1 4.00 MiB
[ 3.103034] mmcblk0boot1: mmc1:0001 008G92 partition 2 4.00 MiB
[ 3.103083] mmcblk0rpmb: mmc1:0001 008G92 partition 3 512 KiB
[ 3.103887] mmcblk0: p1 p2
[ 3.105161] mmcblk0boot1: unknown partition table
[ 3.106150] mmcblk0boot0: unknown partition table
[ 3.122983] usb 1-3: New USB device found, idVendor=0424, idProduct=3503
[ 3.122987] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.123467] hub 1-3:1.0: USB hub found
[ 3.123602] hub 1-3:1.0: 3 ports detected
[ 3.162044] ALSA device list:
[ 3.164886] #0: Built-in Audio
[ 3.168434] Freeing init memory: 168K
[ 3.209688] systemd-udevd[1356]: starting version 204
[ 3.395160] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null)
[ 3.408005] usb 1-3.1: new high-speed USB device number 4 using s5p-ehci
[ 3.519235] usb 1-3.1: New USB device found, idVendor=0bda, idProduct=8176
[ 3.522974] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.530353] usb 1-3.1: Product: 802.11n WLAN Adapter
[ 3.535238] usb 1-3.1: Manufacturer: Realtek
[ 3.539480] usb 1-3.1: SerialNumber: 00e04c000001
[ 3.627745] usb 1-3.3: new full-speed USB device number 5 using s5p-ehci
[ 3.735861] usb 1-3.3: New USB device found, idVendor=046d, idProduct=c52b
[ 3.739397] usb 1-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.746643] usb 1-3.3: Product: USB Receiver
[ 3.750916] usb 1-3.3: Manufacturer: Logitech
[ 3.777560] init: ureadahead main process (1411) terminated with status 5
[ 4.229194] systemd-udevd[1568]: starting version 204
[ 4.500043] input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
[ 4.614558] s5p-fimc exynos4-fimc.0: state restore latency exceeded, new value 19916 ns
[ 4.614614] s5p-fimc exynos4-fimc.0: stop latency exceeded, new value 584 ns
[ 4.616988] s5p-fimc exynos4-fimc.3: start latency exceeded, new value 583 ns
[ 4.617021] s5p-fimc exynos4-fimc.3: state restore latency exceeded, new value 19125 ns
[ 4.617423] s5p-fimc exynos4-fimc.1: start latency exceeded, new value 500 ns
[ 4.617444] s5p-fimc exynos4-fimc.2: state restore latency exceeded, new value 16375 ns
[ 4.617457] s5p-fimc exynos4-fimc.1: stop latency exceeded, new value 500 ns
[ 4.617469] s5p-fimc exynos4-fimc.3: state save latency exceeded, new value 3709 ns
[ 4.630379] s5p-mfc s5p-mfc: start latency exceeded, new value 458 ns
[ 4.630391] s5p-mfc s5p-mfc: state restore latency exceeded, new value 2250 ns
[ 4.632387] init: plymouth main process (1420) killed by ABRT signal
[ 4.633158] init: plymouth-splash main process (1607) terminated with status 2
[ 4.819251] s5p-mfc s5p-mfc: stop latency exceeded, new value 1208 ns
[ 4.819266] s5p-mfc s5p-mfc: start latency exceeded, new value 500 ns
[ 4.819274] s5p-mfc s5p-mfc: state save latency exceeded, new value 1709 ns
[ 4.826768] logitech-djreceiver 0003:046D:C52B.0003: hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-s5p-ehci-3.3/input2
[ 4.847320] input: Logitech Unifying Device. Wireless PID:4024 as /devices/platform/s5p-ehci/usb1/1-3/1-3.3/1-3.3:1.2/0003:046D:C52B.0003/input/input1
[ 4.848267] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:4024] on usb-s5p-ehci-3.3:1
[ 4.890739] smsc95xx v1.0.4
[ 4.898405] [smsc95xx_read_mac_addr] Mac address = 1E:26:DC:10:00:96
[ 4.948465] smsc95xx 1-2:1.0 eth0: register 'smsc95xx' at usb-s5p-ehci-2, smsc95xx USB 2.0 Ethernet, 1e:26:dc:10:00:96
[ 4.948569] usbcore: registered new interface driver smsc95xx
[ 4.987641] rtl8192cu: Chip version 0x10
[ 5.144371] rtl8192cu: MAC address: 00:a8:2b:00:06:f6
[ 5.144386] rtl8192cu: Board Type 0
[ 5.144620] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 5.144723] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
[ 5.144872] usbcore: registered new interface driver rtl8192cu
[ 5.152233] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 5.157645] rtlwifi: wireless switch is on
[ 5.262351] mousedev: PS/2 mouse device common for all mice
[ 8.982183] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 9.179642] init: Failed to spawn smbd main process: unable to execute: No such file or directory
[ 9.284820] init: plymouth-log main process (1833) terminated with status 1
[ 9.334632] init: failsafe main process (1837) killed by TERM signal
[ 9.405994] init: plymouth-upstart-bridge main process (1894) terminated with status 1
[ 9.543567] Bluetooth: Core ver 2.16
[ 9.543622] NET: Registered protocol family 31
[ 9.543627] Bluetooth: HCI device and connection manager initialized
[ 9.543646] Bluetooth: HCI socket layer initialized
[ 9.543654] Bluetooth: L2CAP socket layer initialized
[ 9.543673] Bluetooth: SCO socket layer initialized
[ 9.572539] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.572549] Bluetooth: BNEP filters: protocol multicast
[ 9.572570] Bluetooth: BNEP socket layer initialized
[ 9.583494] Bluetooth: RFCOMM TTY layer initialized
[ 9.583529] Bluetooth: RFCOMM socket layer initialized
[ 9.583535] Bluetooth: RFCOMM ver 1.11
[ 9.779270] NET: Registered protocol family 10
[ 9.929248] init: zram-config pre-start process (2006) terminated with status 1
[ 9.981692] Bridge firewalling registered

Xorg.0.log

[ 99.368]
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 99.368] X Protocol Version 11, Revision 0
[ 99.368] Build Operating System: Linux 3.2.0-51-highbank armv7l Ubuntu
[ 99.368] Current Operating System: Linux odroid 3.8.13.14 #1 SMP PREEMPT Sat Dec 21 00:55:27 CST 2013 armv7l
[ 99.369] Kernel command line: console=tty1 console=ttySAC1,115200 mem=2047M fbcon=map:1111111111111111111111111111 console=tty1 console=ttySAC1,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro mem=2047M
[ 99.369] Build Date: 15 October 2013 09:25:29AM
[ 99.369] xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support)
[ 99.369] Current version of pixman: 0.30.2
[ 99.369] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 99.369] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 99.370] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 31 17:01:42 1999
[ 99.370] (==) Using config file: "/etc/X11/xorg.conf"
[ 99.371] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 99.376] (==) No Layout section. Using the first Screen section.
[ 99.376] (**) |-->Screen "Default Screen" (0)
[ 99.376] (**) | |-->Monitor "<default monitor>"
[ 99.377] (**) | |-->Device "Mali-Fbdev"
[ 99.377] (==) No monitor specified for screen "Default Screen".
Using a default monitor configuration.
[ 99.377] (==) Automatically adding devices
[ 99.377] (==) Automatically enabling devices
[ 99.377] (==) Automatically adding GPU devices
[ 99.377] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 99.377] Entry deleted from font path.
[ 99.377] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 99.377] Entry deleted from font path.
[ 99.377] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/cyrillic,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/75dpi,
built-ins
[ 99.377] (==) ModulePath set to "/usr/lib/arm-linux-gnueabihf/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[ 99.377] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 99.377] (II) Loader magic: 0xb6f5aee0
[ 99.377] (II) Module ABI versions:
[ 99.377] X.Org ANSI C Emulation: 0.4
[ 99.377] X.Org Video Driver: 14.1
[ 99.377] X.Org XInput driver : 19.1
[ 99.377] X.Org Server Extension : 7.0
[ 99.378] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 99.378] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 99.378] Initializing built-in extension Generic Event Extension
[ 99.378] Initializing built-in extension SHAPE
[ 99.378] Initializing built-in extension MIT-SHM
[ 99.379] Initializing built-in extension XInputExtension
[ 99.379] Initializing built-in extension XTEST
[ 99.379] Initializing built-in extension BIG-REQUESTS
[ 99.379] Initializing built-in extension SYNC
[ 99.379] Initializing built-in extension XKEYBOARD
[ 99.379] Initializing built-in extension XC-MISC
[ 99.379] Initializing built-in extension SECURITY
[ 99.379] Initializing built-in extension XINERAMA
[ 99.379] Initializing built-in extension XFIXES
[ 99.379] Initializing built-in extension RENDER
[ 99.379] Initializing built-in extension RANDR
[ 99.380] Initializing built-in extension COMPOSITE
[ 99.380] Initializing built-in extension DAMAGE
[ 99.380] Initializing built-in extension MIT-SCREEN-SAVER
[ 99.380] Initializing built-in extension DOUBLE-BUFFER
[ 99.380] Initializing built-in extension RECORD
[ 99.380] Initializing built-in extension DPMS
[ 99.380] Initializing built-in extension X-Resource
[ 99.380] Initializing built-in extension XVideo
[ 99.380] Initializing built-in extension XVideo-MotionCompensation
[ 99.380] Initializing built-in extension SELinux
[ 99.380] Initializing built-in extension XFree86-VidModeExtension
[ 99.381] Initializing built-in extension XFree86-DGA
[ 99.381] Initializing built-in extension XFree86-DRI
[ 99.381] Initializing built-in extension DRI2
[ 99.381] (II) "glx" will be loaded by default.
[ 99.381] (WW) "xmir" is not to be loaded by default. Skipping.
[ 99.381] (II) LoadModule: "dri2"
[ 99.381] (II) Module "dri2" already built-in
[ 99.381] (II) LoadModule: "glamoregl"
[ 99.382] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 99.420] (II) Module glamoregl: vendor="X.Org Foundation"
[ 99.420] compiled for 1.14.3, module version = 0.5.1
[ 99.420] ABI class: X.Org ANSI C Emulation, version 0.4
[ 99.420] (II) LoadModule: "glx"
[ 99.420] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 99.427] (II) Module glx: vendor="X.Org Foundation"
[ 99.427] compiled for 1.14.3, module version = 1.0.0
[ 99.427] ABI class: X.Org Server Extension, version 7.0
[ 99.427] (==) AIGLX enabled
[ 99.427] Loading extension GLX
[ 99.427] (II) LoadModule: "mali"
[ 99.427] (II) Loading /usr/lib/xorg/modules/drivers/mali_drv.so
[ 99.432] (II) Module mali: vendor="X.Org Foundation"
[ 99.432] compiled for 1.14.3, module version = 0.4.2
[ 99.432] ABI class: X.Org Video Driver, version 14.1
[ 99.432] MaliSetup
[ 99.432] MaliIdentify
[ 99.432] (II) MALI: driver for Mali Framebuffer: mali
[ 99.432] (--) using VT number 7

[ 99.447] (WW) Falling back to old probe method for mali
[ 99.447] MaliProbe
[ 99.447] MaliHWProbe
[ 99.447] (II) MALI(0): using /dev/fb1
[ 99.447] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 99.447] (II) MALI(0): MaliPreInit: ENTER
[ 99.447] (II) MALI(0): MaliGetRec: ENTER
[ 99.447] (II) MALI(0): MaliHWInit: ENTER
[ 99.447] (II) MALI(0): MaliHWGetDepth: ENTER
[ 99.447] (II) MALI(0): Creating default Display subsection in Screen section
"Default Screen" for depth/fbbpp 24/32
[ 99.447] (**) MALI(0): Depth 24, (--) framebuffer bpp 32
[ 99.447] (==) MALI(0): RGB weight 888
[ 99.447] (==) MALI(0): Default visual is TrueColor
[ 99.447] (==) MALI(0): Using gamma correction (1.0, 1.0, 1.0)
[ 99.447] (II) MALI(0): MaliHWGetVidmem: ENTER
[ 99.447] (II) MALI(0): MaliHWGetName: ENTER
[ 99.447] (II) MALI(0): hardware: (video memory: 6890kB)
[ 99.447] (**) MALI(0): Option "DRI2" "true"
[ 99.447] (**) MALI(0): Option "DRI2_PAGE_FLIP" "false"
[ 99.447] (**) MALI(0): Option "DRI2_WAIT_VSYNC" "true"
[ 99.447] (**) MALI(0): Option "UMP_CACHED" "true"
[ 99.447] (**) MALI(0): Option "UMP_LOCK" "false"
[ 99.448] (**) MALI(0): DRI Fullscreen page flip disabled. No support in config file
[ 99.448] (**) MALI(0): DRI Fullscreen page flip VSYNC'd
[ 99.448] (**) MALI(0): Use cached UMP memory
[ 99.448] (**) MALI(0): Don't use umplock across processes
[ 99.448] (EE) MALI(0): mali_drm_open_master DRM OPEN (fd: 0x8)
[ 99.448] (**) MALI(0): DRI Fullscreen page flip disabled. No support in config file
[ 99.448] (**) MALI(0): DRI Fullscreen page flip VSYNC'd
[ 99.448] (**) MALI(0): Use cached UMP memory
[ 99.448] (**) MALI(0): Don't use umplock across processes
[ 99.448] (II) MALI(0): MaliHWGetFD: ENTER
[ 99.448] (II) MALI(0): FBDev_crtc_config: ENTER
[ 99.448] (II) MALI(0): FBDev_crtc_config: EXIT
[ 99.448] (II) MALI(0): Output LCD has no monitor section
[ 99.448] (II) MALI(0): Mode 1680 x 1050 valid
[ 99.448] (II) MALI(0): Printing probed modes for output LCD
[ 99.448] (II) MALI(0): Modeline "1680x1050"x60.0 119.33 1680 1700 1720 1760 1050 1070 1090 1130 (67.8 kHz e)
[ 99.448] (II) MALI(0): Output LCD connected
[ 99.448] (II) MALI(0): Using sloppy heuristic for initial modes
[ 99.448] (II) MALI(0): Output LCD using initial mode 1680x1050
[ 99.448] (II) MALI(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 99.448] (II) MALI(0): MaliHWSetVideoModes: ENTER
[ 99.448] (--) MALI(0): Virtual size is 1680x1050 (pitch 1680)
[ 99.448] (**) MALI(0): Driver mode "1680x1050": 119.3 MHz (scaled from 0.0 MHz), 67.8 kHz, 60.0 Hz
[ 99.448] (II) MALI(0): Modeline "1680x1050"x60.0 119.33 1680 1700 1720 1760 1050 1070 1090 1130 (67.8 kHz e)
[ 99.448] (==) MALI(0): DPI set to (96, 96)
[ 99.448] (II) Loading sub module "fb"
[ 99.448] (II) LoadModule: "fb"
[ 99.449] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 99.452] (II) Module fb: vendor="X.Org Foundation"
[ 99.452] compiled for 1.14.3, module version = 1.0.0
[ 99.452] ABI class: X.Org ANSI C Emulation, version 0.4
[ 99.452] (==) Depth 24 pixmap format is 32 bpp
[ 99.452] (II) MALI(0): MaliScreenInit: ENTER
[ 99.454] (II) MALI(0): DRI2 version: 1.2
[ 99.454] (II) MALI(0): [DRI2] Setup complete
[ 99.454] (II) MALI(0): [DRI2] DRI driver: Mali DRI2
[ 99.454] (II) MALI(0): MaliHWMapVidmem: ENTER
[ 99.454] (II) MALI(0): MaliHWLinearOffset: ENTER
[ 99.454] (II) MALI(0): MaliHWSave: ENTER
[ 99.454] (II) MALI(0): MaliHWModeInit: ENTER
[ 99.454] (II) MALI(0): MaliHWSetMode: ENTER
[ 99.454] (II) MALI(0): MaliHWSaveScreen: ENTER
[ 99.524] (II) MALI(0): MaliHWAdjustFrame: ENTER
[ 99.525] (II) Loading sub module "exa"
[ 99.525] (II) LoadModule: "exa"
[ 99.526] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 99.528] (II) Module exa: vendor="X.Org Foundation"
[ 99.528] compiled for 1.14.3, module version = 2.6.0
[ 99.528] ABI class: X.Org Video Driver, version 14.1
[ 99.528] (II) MALI(0): maliSetupExa: ENTER
[ 99.528] (II) MALI(0): Mali EXA driver is loaded successfully
[ 99.528] (II) MALI(0): maliSetupExa: EXIT
[ 99.528] (WW) MALI(0): Initializing EXA Driver!
[ 99.528] (II) EXA(0): Driver allocated offscreen pixmaps
[ 99.528] (II) EXA(0): Driver registered support for the following operations:
[ 99.528] (II) Solid
[ 99.528] (II) Copy
[ 99.528] (II) Composite (RENDER acceleration)
[ 99.528] (==) MALI(0): Backing store disabled
[ 99.528] (==) MALI(0): Silken mouse enabled
[ 99.528] (II) MALI(0): Changing mode to 1680 1050 1680 2100
[ 99.528] (II) MALI(0): Unable to set mode!
[ 99.592] (II) MALI(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 99.592] (--) RandR disabled
[ 99.610] (II) SELinux: Disabled on system
[ 99.613] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/Mali DRI2_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/Mali DRI2_dri.so: cannot open shared object file: No such file or directory)
[ 99.613] (EE) AIGLX: reverting to software rendering
[ 99.613] (II) AIGLX: Screen 0 is not DRI capable
[ 99.649] (II) AIGLX: Loaded and initialized swrast
[ 99.649] (II) GLX: Initialized DRISWRAST GL provider for screen 0
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby mdrjr » Sun Jan 19, 2014 12:27 pm

I see.. your monitor isn't 720p or 1080p
try the 720p EDID or the 1080p NOEDID


sudo odroid-config
Resolution
mdrjr
Site Admin
 
Posts: 11575
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: wrong monitor setting selected at boot

Unread postby chrisa » Sun Jan 19, 2014 12:59 pm

Thanks. OK:
1) I tried option HDMI3 (720P EDID). Reboot. No luck, same result
2) I tried option HDMI4 (1080P NO EDID). Reboot. No luck, same result.

The monitor I am using is a BenQ model Q22W6. Natively I believe it supports 1050 lines.

I should also add that about half the time, I need to unplug/replug the HDMI cable out/in the ODROID. Each time I boot, only half the time does the monitor "wake up".

As mentioned earlier in this thread, I've tried other monitors, yet none of them work even to show the odroid-config screen on initial boot of the unit. For instance, I just now connected the ODROID to a Dell E2213H. It won't even recognize that a signal is present. This is with HDMI4 selected.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby chrisa » Sun Jan 19, 2014 1:34 pm

OK, I did some searching on the xauth error. Ran into this: http://www.geekvenue.net/chucktips/jaso ... index_html

Thought, well, why not...gave it a shot. Ran "xauth -b", which took me to a "xauth>" prompt. Not sure what to do there, so I simply typed "exit".
Then, i tried startx and low and behold, something happened! Not launched completely, but a bunch of text spit out. Looking through it, my eye was caught by this one line:
Fatal server error:
(EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
and then a few lines down:
xinit: unable to connect to X server: Connection refused
xinit: server error

And then back to
odroid:odroid:~$

Does that get us anywhere?
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby chrisa » Sun Jan 19, 2014 2:03 pm

Not entirely sure what just happened, but I am into Xfce!
What I did:
- since I had been playing around with changing ownership etc., I decided to completely wipe the emmc and start over
- I reflashed the image
- went into odroid-config on the first boot, changed to HDMI4 and expanded the file system. BUT, CRUCIALLY - i forgot to change it not to boot into the GUI
- rebooted
Whamo, I am in Xfce!
Rebooted, again, works.
Rebooted again, works.
Guys, thanks for the help. And I really hope this can be helpful to someone else. But at this point, it looks like I am good!
I'll repost if this changes.
Again, thank you for your time and patience.
chrisa
 
Posts: 15
Joined: Fri Jan 17, 2014 8:48 am
languages_spoken: english
ODROIDs: Odroid U3

Re: wrong monitor setting selected at boot

Unread postby peepo » Sat Feb 15, 2014 8:18 pm

not to cross threads, but I just received U3, boots fine to X, nad after sudo odroid-config edit, boots to console fine,
however startx just seems to hang. re-edit and boots to X fine.

it would be nice to have a howto or troubleshoot for this....
User avatar
peepo
 
Posts: 75
Joined: Mon Feb 03, 2014 7:01 am
languages_spoken: English
ODROIDs: U3 eMMC, XU lite emmc


Return to Issues

Who is online

Users browsing this forum: No registered users and 2 guests