Unanswered topics | Active topics


Board index » »

All times are UTC-06:00



Post new topic  Reply to topic  Page 2 of 2
  [ 22 posts ] 
  Previous topic | Next topic 
Author Message
beewoolie
 Post subject:
PostPosted: Fri Sep 02, 2011 10:11 am 
Offline

Joined: Fri Aug 19, 2011 1:18 pm
Posts: 18
Location: Seattle, WA US
Quote:
How my LCDs work changed with almost every release. I have three LCDs, all with DVI, so I use a HDMI->DVI converter.
The latest release works fine with an LG Flatron, but has trouble with my main LCD, a 22" Samsung. But it can be worked around: just by pushing the buttons on the Samsung it does not go to sleep mode, where the smarttop does not recognize it. AFAIR, earlier releases had no problem using the Samsung even without pushing its buttons on boot.
And the ARMHF port also uses a completely different kernel...
Release of SW or HW? My monitor worked fine with a previous device of the same generation.
Top
   
Reply with quote  
czp
 Post subject:
PostPosted: Fri Sep 02, 2011 2:00 pm 
Offline

Joined: Thu Jul 28, 2005 12:41 am
Posts: 1066
I meant SW (kernel) release.

_________________
CzP
http://czanik.blogs.balabit.com/
Top
   
Reply with quote  
beewoolie
 Post subject:
PostPosted: Fri Sep 02, 2011 2:55 pm 
Offline

Joined: Fri Aug 19, 2011 1:18 pm
Posts: 18
Location: Seattle, WA US
Quote:
I meant SW (kernel) release.
I don't think we're talking about the same thing.

In my case, I have the same SW release and a different piece of hardware. The maverick installer worked OK on the first system. On the second system there is no video output and the kernel hangs during bootup.

I suspect some sort of hardware variation, though it is not catastrophic because the armhf image boots OK.
Top
   
Reply with quote  
Neko
PostPosted: Fri Sep 02, 2011 8:06 pm 
Offline
Site Admin

Joined: Fri Sep 24, 2004 1:39 am
Posts: 1589
Location: Austin, TX
Quote:
Quote:
I'm looking into your problem right now.
Any news on figuring out what could be the root cause? Do you need me to send the box back?
I'm still trying to figure it out. The fact the installer did not bring up any SIIHDMI mode culling debug means.. no EDID was presented to the system, therefore it cannot possibly work out what mode to set (although it should shove it into 640x480, even then some monitors seem to refuse to display this standard mode, which is infuriating).

Can you paste full dmesg of each one, so I can compare versions? I can't tell from the snippet of SIIHDMI debug what kernel that is. They may be different, which would be weird from my point of view, but could also point to using an old installer card or.. I dunno.

_________________
Matt Sealey
Top
   
Reply with quote  
Neko
PostPosted: Fri Sep 02, 2011 8:08 pm 
Offline
Site Admin

Joined: Fri Sep 24, 2004 1:39 am
Posts: 1589
Location: Austin, TX
Quote:
Quote:
Quote:
I'm looking into your problem right now.
Any news on figuring out what could be the root cause? Do you need me to send the box back?
I'm still trying to figure it out. The fact the installer did not bring up any SIIHDMI mode culling debug means.. no EDID was presented to the system, therefore it cannot possibly work out what mode to set (although it should shove it into 640x480, even then some monitors seem to refuse to display this standard mode, which is infuriating).

Can you paste full dmesg of each one, so I can compare versions? I can't tell from the snippet of SIIHDMI debug what kernel that is. They may be different, which would be weird from my point of view, but could also point to using an old installer card or.. I dunno.
Oh.. also can you get into the armhf image and get me a copy of the EDID. It should be a file located at

/sys/class/graphics/fb0/edid

(if it is then that's a frustratingly old kernel, too..)

_________________
Matt Sealey
Top
   
Reply with quote  
beewoolie
PostPosted: Fri Sep 02, 2011 10:50 pm 
Offline

Joined: Fri Aug 19, 2011 1:18 pm
Posts: 18
Location: Seattle, WA US
Quote:
Quote:
Quote:
Any news on figuring out what could be the root cause? Do you need me to send the box back?
I'm still trying to figure it out. The fact the installer did not bring up any SIIHDMI mode culling debug means.. no EDID was presented to the system, therefore it cannot possibly work out what mode to set (although it should shove it into 640x480, even then some monitors seem to refuse to display this standard mode, which is infuriating).

Can you paste full dmesg of each one, so I can compare versions? I can't tell from the snippet of SIIHDMI debug what kernel that is. They may be different, which would be weird from my point of view, but could also point to using an old installer card or.. I dunno.
Oh.. also can you get into the armhf image and get me a copy of the EDID. It should be a file located at

/sys/class/graphics/fb0/edid

(if it is then that's a frustratingly old kernel, too..)
It's interesting that you say that because the version number of the kernel is only one less than the kernel in the maverick installer.
Code:
root@armhf:/sys/class/graphics/fb0# uname -a
Linux armhf 2.6.31.14.23-efikamx #7 PREEMPT Thu Jun 9 21:29:48 CDT 2011 armv7l GNU/Linux
root@armhf:/sys/class/graphics/fb0# hd edid
00000000 00 ff ff ff ff ff ff 00 10 ac 15 40 4c 46 30 34 |...........@LF04|
00000010 0d 10 01 03 80 26 1e 78 2e ce 50 a3 54 4c 99 26 |.....&.x..P.TL.&|
00000020 0f 50 54 a5 4b 00 71 4f 81 80 01 01 01 01 01 01 |.PT.K.qO........|
00000030 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70 |......0*..Q.*@0p|
00000040 13 00 78 2d 11 00 00 1e 00 00 00 ff 00 36 34 31 |..x-.........641|
00000050 38 30 36 34 31 34 30 46 4c 0a 00 00 00 fc 00 44 |8064140FL......D|
00000060 45 4c 4c 20 31 39 30 37 46 50 0a 20 00 00 00 fd |ELL 1907FP. ....|
00000070 00 38 4c 1f 53 0e 00 0a 20 20 20 20 20 20 00 7a |.8L.S... .z|
00000080
Top
   
Reply with quote  
beewoolie
 Post subject:
PostPosted: Fri Sep 02, 2011 11:07 pm 
Offline

Joined: Fri Aug 19, 2011 1:18 pm
Posts: 18
Location: Seattle, WA US
I have one other data point that I cannot quite resolve.

What I've been doing with this efikamx is porting the APEX boot loader to it. As of today, APEX can boot the armhf kernel to the login prompt and it can boot the stock kernel and initramfs to the login prompt. Uboot on my efikamx won't do the latter.

The thing that APEX seems to prevent is the kernel initializing USB. In neither the armhf nor the stock kernel does the Linux find the USB keyboard or ethernet devices. I'll look into the cause of this next. I didn't think I needed to initialize anything ahead of time for USB.
Top
   
Reply with quote  
Display posts from previous:  Sort by  
Post new topic  Reply to topic  Page 2 of 2
  [ 22 posts ] 

Board index » »

All times are UTC-06:00

Who is online

Users browsing this forum: No registered users and 0 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
PowerDeveloper.org: Copyright © 2004-2012, Genesi USA, Inc. The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are trademarks and service marks licensed by Power.org.
All other names and trademarks used are property of their respective owners. Privacy Policy
Powered by phpBB® Forum Software © phpBB Group