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,
--
Robert Nelson
http://www.rcn-ee.com/
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 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
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...
[ 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.. ;)
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
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..
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..