-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El Mon, 27 Aug 2012 20:35:06 -0500
Jon <jdisnard(a)gmail.com> escribió:
>> 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
you should just do "modprobe omapdrm" not insmod the .ko as it takes
care of its deps.
do a lsinitrd on the initramfs file in /boot and make sure that it has
the omapdrm module in it.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAlA8LCkACgkQkSxm47BaWfdf8wCgpiDNySKePw33HWjNPk+5HQBr
d2AAoIhCKIOR0FCSS+xHQpb5I0uNuDrO
=Z3wq
-----END PGP SIGNATURE-----