[Buildroot] BR 2012.rc1 :: DVI not activated on pandaboard?

[Buildroot] BR 2012.rc1 :: DVI not activated on pandaboard?

[MERCADIER Johann]

Hi all,
  Now that I try to switch to a graphical output. As the uImage generated
by BR still does work I compile one manually (3.2.7), it works great till
It's used on console mode then I add all options needed to get DVI
activated as explained on the following website:
http://omappedia.org/wiki/Bootargs_for_enabling_display
http://omappedia.org/wiki/DSS_CONFIG_options

modify the boot script in the following way:
___[ BOOT.SCRIPT
]________________________________________________________________________________________
mmc rescan
fatload mmc 0:1 0x80000000 uImage
setenv bootargs vram=32M console=ttyO2,115200n8
mem=456M at 0x80000000mem=512M at 0xA0000000 omapdss.def_disp=dvi
omapfb.mode=dvi:1280x1024MR-24 at 60smsc95xx.macaddr=76:2F:97:85:4F:56
root=/dev/nfs rw
nfsroot=192.168.1.44:/home/johann/rootfs_TEST,nolock,wsize=1024,rsize=1024
ip=192.168.1.235 rootdelay=4 init=/linuxrc
bootm 0x80000000

when booting I get there, the pandaboard probably still continue the boot
process but nothing is displayed on the monitor?...
___[ MINICOM O/P
]________________________________________________________________________________________
...
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
??????

If someone can understand why nothing is displayed on monitor, please tell
me or us (probably not the only stuck with it!)

thanks
-- 
Cordialement.

___Johann MERCADIER___

:(){ :|:& };:
"I am the Unknown lead by the Unknowing.
I have done so much with so little for so long
that I am now qualified to do anything with nothing."
HOOSEEK (http://www.hooseek.com/) 1?moteur de recherche solidaire!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120307/4a3d0bf6/attachment-0001.html>

[Buildroot] BR 2012.rc1 :: DVI not activated on pandaboard?

[Thomas Petazzoni]

Hello,

Le Wed, 7 Mar 2012 23:16:21 +0000,
MERCADIER Johann <johann.mercadier@imerir.com> a ?crit :

> mmc rescan
> fatload mmc 0:1 0x80000000 uImage
> setenv bootargs vram=32M console=ttyO2,115200n8
> mem=456M at 0x80000000mem=512M at 0xA0000000 omapdss.def_disp=dvi
> omapfb.mode=dvi:1280x1024MR-24 at 60smsc95xx.macaddr=76:2F:97:85:4F:56
> root=/dev/nfs rw
> nfsroot=192.168.1.44:/home/johann/rootfs_TEST,nolock,wsize=1024,rsize=1024
> ip=192.168.1.235 rootdelay=4 init=/linuxrc
> bootm 0x80000000
> 
> when booting I get there, the pandaboard probably still continue the boot
> process but nothing is displayed on the monitor?...
> ___[ MINICOM O/P
> ]________________________________________________________________________________________
> ...
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> Uncompressing Linux... done, booting the kernel.

If you don't have the kernel messages after this, then it means that
something is wrong in your configuration. Don't expect to see anything
on the video output before you get your kernel to boot properly, i.e to
display messages on the serial console after "Uncompressing Linux...
done, booting the kernel".

However, this discussion is really not Buildroot-specific, it is really
about configuring a kernel for a particular hardware platform, so you
should probably rather ask in support places (forums, mailing lists,
etc.) that are related to this particular piece of hardware.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] BR 2012.rc1 :: DVI not activated on pandaboard?

[MERCADIER Johann]

You are right, just checked it on console mode only and it doesn't boot
anymore. I've changed from a 3.0.2 to a 3.2.7 kernel version? I am going to
check this to make sure kernel version has nothing to do with that?
For those questions, related to kernel stuff, I will post to the right
forum.
 thanks

On 8 March 2012 08:21, Thomas Petazzoni <thomas.petazzoni@free-electrons.com
> wrote:

> Hello,
>
> Le Wed, 7 Mar 2012 23:16:21 +0000,
> MERCADIER Johann <johann.mercadier@imerir.com> a ?crit :
>
> > mmc rescan
> > fatload mmc 0:1 0x80000000 uImage
> > setenv bootargs vram=32M console=ttyO2,115200n8
> > mem=456M at 0x80000000mem=512M at 0xA0000000 omapdss.def_disp=dvi
> > omapfb.mode=dvi:1280x1024MR-24 at 60smsc95xx.macaddr=76:2F:97:85:4F:56
> > root=/dev/nfs rw
> > nfsroot=192.168.1.44:
> /home/johann/rootfs_TEST,nolock,wsize=1024,rsize=1024
> > ip=192.168.1.235 rootdelay=4 init=/linuxrc
> > bootm 0x80000000
> >
> > when booting I get there, the pandaboard probably still continue the boot
> > process but nothing is displayed on the monitor?...
> > ___[ MINICOM O/P
> >
> ]________________________________________________________________________________________
> > ...
> >    Verifying Checksum ... OK
> >    Loading Kernel Image ... OK
> > OK
> >
> > Starting kernel ...
> >
> > Uncompressing Linux... done, booting the kernel.
>
> If you don't have the kernel messages after this, then it means that
> something is wrong in your configuration. Don't expect to see anything
> on the video output before you get your kernel to boot properly, i.e to
> display messages on the serial console after "Uncompressing Linux...
> done, booting the kernel".
>
> However, this discussion is really not Buildroot-specific, it is really
> about configuring a kernel for a particular hardware platform, so you
> should probably rather ask in support places (forums, mailing lists,
> etc.) that are related to this particular piece of hardware.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>



-- 
Cordialement.

___Johann MERCADIER___

:(){ :|:& };:
"I am the Unknown lead by the Unknowing.
I have done so much with so little for so long
that I am now qualified to do anything with nothing."
HOOSEEK (http://www.hooseek.com/) 1?moteur de recherche solidaire!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120308/1a6f33ab/attachment.html>

[Buildroot] BR 2012.rc1 :: DVI not activated on pandaboard?

[Samuel Martin]

Hi Johann, all,

2012/3/8 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
> Hello,
>
> Le Wed, 7 Mar 2012 23:16:21 +0000,
> MERCADIER Johann <johann.mercadier@imerir.com> a ?crit :
>
>> mmc rescan
>> fatload mmc 0:1 0x80000000 uImage
>> setenv bootargs vram=32M console=ttyO2,115200n8
>> mem=456M at 0x80000000mem=512M at 0xA0000000 omapdss.def_disp=dvi
>> omapfb.mode=dvi:1280x1024MR-24 at 60smsc95xx.macaddr=76:2F:97:85:4F:56
>> root=/dev/nfs rw
>> nfsroot=192.168.1.44:/home/johann/rootfs_TEST,nolock,wsize=1024,rsize=1024
>> ip=192.168.1.235 rootdelay=4 init=/linuxrc
>> bootm 0x80000000
>>
>> when booting I get there, the pandaboard probably still continue the boot
>> process but nothing is displayed on the monitor?...
>> ___[ MINICOM O/P
>> ]________________________________________________________________________________________
>> ...
>> ? ?Verifying Checksum ... OK
>> ? ?Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing Linux... done, booting the kernel.
>
Last time, i got this kind of log, i was messing up the console
parameter in kernel args.


Sam

[Buildroot] BR 2012.rc1 :: DVI not activated on pandaboard?

[MERCADIER Johann]

Hi Sam, all
  I just finished compiling a 3.0.2 kernel version that I knew that was
working, adding options for DVI support and everything works as a charm
except that I still do not have any DVI o/p on the monitor?!
  Do you mean "boot args"? I didn't change anything and it was working
Thomas is right is more likely something messing up with the kernel config
in the 3.2.7 version.
  But you are right probably I do not send the right args to activate the
DVI. I will try to have look how Angstrom & ubuntu distro have managed this
part, may be I will get something out of there...
  At the moment I am not good enough to know how to light this up. Do you
know a good website, tutorial where I could learn these stuff(seeking and
finding where mistakes takes place...) coz at the moment I just feel
"useless" ;o)

  Bye



On 8 March 2012 10:03, Samuel Martin <s.martin49@gmail.com> wrote:

> Hi Johann, all,
>
> 2012/3/8 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
> > Hello,
> >
> > Le Wed, 7 Mar 2012 23:16:21 +0000,
> > MERCADIER Johann <johann.mercadier@imerir.com> a ?crit :
> >
> >> mmc rescan
> >> fatload mmc 0:1 0x80000000 uImage
> >> setenv bootargs vram=32M console=ttyO2,115200n8
> >> mem=456M at 0x80000000mem=512M at 0xA0000000 omapdss.def_disp=dvi
> >> omapfb.mode=dvi:1280x1024MR-24 at 60smsc95xx.macaddr=76:2F:97:85:4F:56
> >> root=/dev/nfs rw
> >> nfsroot=192.168.1.44:
> /home/johann/rootfs_TEST,nolock,wsize=1024,rsize=1024
> >> ip=192.168.1.235 rootdelay=4 init=/linuxrc
> >> bootm 0x80000000
> >>
> >> when booting I get there, the pandaboard probably still continue the
> boot
> >> process but nothing is displayed on the monitor?...
> >> ___[ MINICOM O/P
> >>
> ]________________________________________________________________________________________
> >> ...
> >>    Verifying Checksum ... OK
> >>    Loading Kernel Image ... OK
> >> OK
> >>
> >> Starting kernel ...
> >>
> >> Uncompressing Linux... done, booting the kernel.
> >
> Last time, i got this kind of log, i was messing up the console
> parameter in kernel args.
>
>
> Sam
>



-- 
Cordialement.

___Johann MERCADIER___

:(){ :|:& };:
"I am the Unknown lead by the Unknowing.
I have done so much with so little for so long
that I am now qualified to do anything with nothing."
HOOSEEK (http://www.hooseek.com/) 1?moteur de recherche solidaire!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120308/8f37844c/attachment.html>