> Here is what I tried in /boot/uboot/uEnv.txt:
> omapfb.mode=dvi:1280x1024MR-24@60 omapdss.def_disp=dvi
we use omapdrm not omapfb so none of those options will have any
effect. its all auto detected and auto setup. if the edid data is not
read from the monitor you will get 1024x768 only. ive not tried the 3.5
based kernels as im not at home where i have access to a monitor.
Thanks Dennis.
The information about omapdrm was good, gave something to troubleshoot.
On the working (3.4.2-3) kernel, you can do this:
# cd /sys/devices/platform/omapdrm.0/drm/card0/card0-HDMI-A-1/
# cat modes
1024x768
800x600
848x480
640x480
On the latest kernel 3.5.2-3 that sysfs path does not exist. :(
So I guess the omapdrm driver is not happy.
The output of lsmod does not have as much stuff as the 3.4.2-3 kernel had.
Here I tried to load omapdrm module:
# insmod /lib/modules/3.5.2-3.fc17.armv7hl.omap/kernel/drivers/staging/omapdrm/omapdrm.ko
Error: could not insert module
/lib/modules/3.5.2-3.fc17.armv7hl.omap/kernel/drivers/staging/omapdrm/omapdrm.ko:
Unknown symbol in module
On the working kernel, lsmod:
# lsmod
Module Size Used by
lockd 76647 0
sunrpc 229730 1 lockd
aes_generic 31238 0
bnep 10592 2
bluetooth 177728 7 bnep
arc4 1269 0
nls_ascii 3508 1
vfat 9199 1
fat 48924 1 vfat
wl12xx 145546 0
mac80211 442857 1 wl12xx
cfg80211 169876 2 mac80211,wl12xx
rfkill 16628 5 cfg80211,bluetooth
smsc95xx 12138 0
evbug 1926 0
rtc_twl 5447 0
wl12xx_sdio 3387 0
autofs4 22550 2
omapdrm 62957 2
fb_sys_fops 1376 1 omapdrm
syscopyarea 3028 1 omapdrm
sysfillrect 3304 1 omapdrm
sysimgblt 2131 1 omapdrm
drm_kms_helper 28433 1 omapdrm
drm 201384 2 drm_kms_helper,omapdrm
And the unhappy kernel...
# lsmod
Module Size Used by
lockd 76997 0
sunrpc 230092 1 lockd
bnep 10600 2
bluetooth 179620 7 bnep
rfkill 16628 2 bluetooth
nls_ascii 3508 1
vfat 9199 1
fat 49092 1 vfat
evbug 1926 0
smsc95xx 12162 0
rtc_twl 5447 0
autofs4 22550 2
As you can see there are some differences. :(
--
-Jon