Hi all,
My beagleboard with angstrom works fine on my LCD tv. But ubuntu
distro of rcn-ee doesnt work. I have already created boot.scr with
omapfb.mode=dvi:hd720 and intalled xserver-xorg-video-omap3 package.
Someone on chat told me to recompile kernel with 2.6.32 but. Ubuntu
already has newer version (6.37). What should i do next? any
suggestions?
So did the default setting of
1280x720MR-16@60
work?
otherwise "hd720" is enabled by this patch:
Really no difference, other then 16/32 bit between the two..
ps, there was an lcd regression early in my kernel, what does 'uname
-r' return..
Regards,
Hi Robert,
Default settings of 1280X720MR-16@60 doesnt work. Kernel version is :
2.6.37.2-x3.
Btw i am quite new to this; i am trying to patch it, ihave downloaded
the kernel src(bzr branch lp:~beagleboard-kernel/+junk/2.6-stable):
but it seems there is no modedb.c file when i try to patch it gives
following error
ubuntu@omap:~/2.6-stable$ patch < 0001-video-add-timings-for-
hd720.patch
patching file modedb.c
Hunk #1 FAILED at 102.
1 out of 1 hunk FAILED -- saving rejects to file modedb.c.rej
Hi Robert,
Default settings of 1280X720MR-16@60 doesnt work. Kernel version is :
2.6.37.2-x3.
okay, that one had the fix.. so the default should have worked..
Please add "omapfb.debug=y" to your bootarg, and post your full boot
log using the serial port..
Btw i am quite new to this; i am trying to patch it, ihave downloaded
the kernel src(bzr branch lp:~beagleboard-kernel/+junk/2.6-stable):
but it seems there is no modedb.c file when i try to patch it gives
following errorubuntu@omap:~/2.6-stable$ patch < 0001-video-add-timings-for-
hd720.patch
patching file modedb.c
Hunk #1 FAILED at 102.
1 out of 1 hunk FAILED -- saving rejects to file modedb.c.rej
For one, that link isn't the kernel 'SRC' it's a script build the
"SRC" in the KERNEL directory.. Besides, that patch is enabled by
default...
Regards,
[ 4.336334] fbcvt: 1280x720@60: CVT Name - .921M9-R
[ 4.362792] Console: switching to colour frame buffer device 160x45
Humm, nothing obvious.. looks like it started up just fine..
What version of angstrom's kernel worked?
What model lcd are you using?
One quick test, downgrade to this kernel:
http://rcn-ee.net/deb/maverick/v2.6.37.2-x2/install-me.sh
It was the version, right before i fixed the display regression on one
of my cheap monitors..
One oddity:
Image Name: Linux-2.6.37.2-x5
I don't remember releasing that version.. 
Regards,
Angstrom kernel is 2.6.32
I have tested it with two LCDs : one is Philips 42PFL740 the other is
47" Vestel. After suspicious kernel version here is what i have done;
redownloaded http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-r5-minimal-armel.tar.xz
and deployed it with ./setup_sdcard.sh script.
Just added some script files to connect wireless network.
checked kernel version and boot.scr file. Kernel is now 2.6.37.2-x3,
and boot.scr is with 1280x720MR-16@60
on my philips tv says video format not supported
downgraded to 2.6.36.2-x2 it still doesnt work.
here is the debug log of ubuntu with 36.2-x2
http://home.anadolu.edu.tr/~cagdask/dvi_ubuntu.txt
and here is the log of angstrom
Humm, this is going to be fun to track down.
First, let's see if maybe it's fixed in mainline: v2.6.38-rc8:
wget http://rcn-ee.net/deb/maverick/v2.6.38-rc8-d5/install-me.sh
/bin/bash install-me.sh
reboot...
if not, does my old 2.6.35.9-l9 work?
wget http://rcn-ee.net/deb/maverick/v2.6.35.9-l9/install-me.sh
/bin/bash install-me.sh
Note, before you reboot with 2.6.35, change ttyO2 -> ttyS2 in boot.cmd
and regenerate the boot.scr file..:
cd /boot/uboot/
sudo nano boot.cmd
and then run this script to update all boot files:
./tools/update_boot_files.sh
Regards,
unfortunately, none of them works.
Just to be sure, here are my environment variables. Can you check? are
they correct?
OMAP3 beagleboard.org # printenv
bootcmd=if mmc init ${mmcdev}; then if run loadbootscript; then run
bootscript;
else if run loaduimage; then run mmcboot; else run nandboot; fi; fi;
else run na
ndboot; fi
bootdelay=3
baudrate=115200
loadaddr=0x82000000
usbtty=cdc_acm
console=ttyS2,115200n8
vram=12M
defaultdisplay=dvi
mmcdev=1
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
nandroot=/dev/mtdblock4 rw
nandrootfstype=jffs2
mmcargs=setenv bootargs console=${console} mpurate=${mpurate} buddy=$
{buddy} vra
m=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=$
{defaultdisplay} root=${m
mcroot} rootfstype=${mmcrootfstype}
nandargs=setenv bootargs console=${console} mpurate=${mpurate} buddy=$
{buddy} vr
am=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=$
{defaultdisplay} root=${
nandroot} rootfstype=${nandrootfstype}
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run nandargs; nand read $
{loadaddr} 280000
400000; bootm ${loadaddr}
dieid#=105c000400000000040373051400d018
dvimode=hd720
buddy=unknown
beaglerev=Cx
mpurate=720
Environment size: 1234/131068 bytes
unfortunately, none of them works.
Bummer, even 2.6.35? so there's something very special in angstrom to
make it work..
Normally, i'd try a bisect, but from Angstrom's 2.6.32-psp to
mainline's 2.6.35/37 would be a pain..
I guess, right now, you will need to either run the Angstrom
Kernel/Modules on ubuntu.. Or use Angstrom..
Just to be sure, here are my environment variables. Can you check? are
they correct?
nah they are fine.. since, this is showing up in your dmesg....
[ 4.336334] fbcvt: 1280x720@60: CVT Name - .921M9-R
[ 4.362792] Console: switching to colour frame buffer device 160x45
It's passing the correct environment variables in the boot.scr correctly..
Regards,
angstrom is really minimal, besides it does not recognize my wireless
adapter.
So using angstrom kernel/modules sounds more logical. But I really
have no idea how to do that.
Any suggestions or articals to read?
angstrom is really minimal, besides it does not recognize my wireless
adapter.
Which wireless adapter? If your luckly and it's just a vid/pid
change, it should be pretty easy to patch angstrom..
So using angstrom kernel/modules sounds more logical. But I really
have no idea how to do that.
Any suggestions or articals to read?
It's actually pretty straight forward, you just need Angstrom's uImage/modules..
Copy the uImage to the fat file system, and untar the modules into the
root partition..
Regards,
It's railink RT2573.
Which wireless adapter? If your luckly and it's just a vid/pid
change, it should be pretty easy to patch angstrom..
It's railink RT2573. I have downloaded reqired firmware to lib/
firmware directory but nope it lists it with lsusb but
wlan0 is not listed
It's actually pretty straight forward, you just need Angstrom's uImage/modules..
Copy the uImage to the fat file system, and untar the modules into the
root partition..
Copyying only modules did not work but uImage, but again no wireless
adapter etc...
omapdss.def_disp parameter is not specifed at bootargs. does setting
it to a value change something? What should i set it to? dvi or lcd?