>________________________________
>
>From: Zhang, Austin 
>Sent: Wednesday, October 29, 2008 4:53 PM
>To: Lee, Anthony; [EMAIL PROTECTED]
>Subject: RE: Impetuously built binary of
Intel-GMA500-2.2.2.32L.0021-Ubuntu-hardy source on moblin2's
kernel-crown-beach->>devel-2.6.27.rc6-12.1.moblin2
>       
>       
>>(In fact, I still cannot see any X desktop running on CrownBeach by
moblin2)
>Do you have a try on vesa driver?

Not yet. That is because I still stuggle with the strange issue of
booting

Checking device /dev/sda for installation source...
Checking device /dev/sdb for installation source...
Checking device /dev/sdc for installation source...
Checking device /dev/sdd for installation source...
Sleeping for 5 seconds
Sleeping finished
...

In fact, I even cannot see the login prompt :-( Gezz...


>        
>        
>>kernel-crown-beach-devel-2.6.27.rc6-12.1.moblin2.i586.rpm
>>and 
>>Intel-GMA500-2.2.2.32L.0021-Ubuntu-hardy.tar.bz2 
>>Anyway, I tried to compile GMA500 on a moblin2 jailed rootfs with
core-dev and x-dev ready
>You are trying to compile gfx driver for ubuntu-hardy (which is kernel
2.6.24) under moblin kernel 2.6.27?

Well... It is just a trying because I cannot find any new version source
of GMA500.

>        
>                
>>Or I should choose other source tree which is verified to be
compatible with moblin2?
>Gfx driver for menlow seemed to be private driver rather than open
source. 
                
Uh... Is it inappropriate to discuss close source project on this
mailing list?
Oh.. Forgive me if this disclosed any confidential material and I
apologized for that foolish question.

If you have any technical suggestion, please send me via internal mail.
Thanks a lot.

_______________________________________________
Moblin dev Mailing List
[email protected]

To manage or unsubscribe from this mailing list visit:
https://lists.moblin.org/mailman/listinfo/dev or your user account on 
http://moblin.org once logged in.

For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists

Reply via email to