Hi,
I am using the HDMI output of the BB to connect the LCD monitor, but I
have a problem. I have installed Ubuntu 10.10 netbook on microSD card.
After restarted the board, not every time sometimes only, the screen
does not show up. When it occurs, I changed the microSD card with the
xmTest card that includes Angstrom demo files, and screen is O.K.
after boots, then I change the SD Card with my Ubuntu Netbook, at that
time screen comes.
at uboot printevn;
dvimode =1024x768MR-16@60
default display = dvi
Is there enyone who has same issue? Do you know how can I solve this ?
Thanks Best Regards
First you'll need to provide more info:
add "omapfb.debug=y" to your bootarg's and copy your full boot log
from the serial port to pastebin.com so we can see it..
Regards,
First you'll need to provide more info:
add "omapfb.debug=y" to your bootarg's and copy your full boot log
from the serial port to pastebin.com so we can see it..
Regards,
--
Robert Nelsonhttp://www.rcn-ee.com/
On minicom only theese mesages are visible boot log - Pastebin.com
after compressing line I can not see anything for log
to add this line to bootarg is it enough writing only
#setenv bootargs omapfb.debug=y
#savenev
nope it's not...
"reading boot.scr"
It's using the boot.scr for boot, so your going to have to edit that..
https://wiki.ubuntu.com/ARM/BeagleEditBootscr
add: console=ttyS2,115200n8 too.. (or ttyO2 if it's 2.6.36++)
PS.. Reread: https://wiki.ubuntu.com/ARM/OMAPMaverickInstall
You followed the note: "On Beagleboard xM rev A3 and B" right???
Regards,
Beagle xM Rev A
But my board is RevB,
You followed the note: “On Beagleboard xM rev A3 and B” right???
I am not sure but I remember that I did
I found a boot.script file in the file system /boot and it includes only ;
fatload mmc 0:1 0x80000000 uImage
fatload mmc 0:1 0x81600000 uInitrd
setenv bootargs quiet splash ro elevator=noop vram=12M omapfb.mode=dvi:1280x720MR-16@60 root=UUID=8555d495-322b-4dcc-b9c6-ddbe8c11f1b2 fixrtc
bootm 0x80000000 0x81600000
is it normal ?
Is this file to add a new option to bootargs ?
BeagleBoard-xM Rev B will report themselves as a Rev A,. This is normal.
Gerald
Beagle xM Rev A
But my board is RevB,
There are B's with the A gpio setting's, no big deal..
You followed the note: "On Beagleboard xM rev A3 and B" right???
I am not sure but I remember that I did
That would explain the broken dvi... All boards after A3 (so
including the B) moved the dvi enable line.. Since Canonical/Ubuntu
can't upgrade a kernel after release, you need to use the fixed on
listed there.
That's the main reason i still push out my own demo images:
BeagleBoardUbuntu - eLinux.org (with newer kernel's..)
I found a boot.script file in the file system /boot and it includes only ;
fatload mmc 0:1 0x80000000 uImage
fatload mmc 0:1 0x81600000 uInitrd
setenv bootargs quiet splash ro elevator=noop vram=12M
omapfb.mode=dvi:1280x720MR-16@60
root=UUID=8555d495-322b-4dcc-b9c6-ddbe8c11f1b2 fixrtc
bootm 0x80000000 0x81600000
is it normal ?
Is this file to add a new option to bootargs ?
Yes, that's their normal boot settings.. It's fine when things work,
but useless for debugging.. 
Regards,
That’s the main reason i still push out my own demo images:
>http://elinux.org/BeagleBoardUbuntu#Demo_Image (with newer kernel’s…)
I have installed demo ibage with GUI but there are alot of losted applets. Also I could not find terminal konsole and network connections. How can I add them to system ?