I wish I could say the DVI overlay worked, but it doesn't. It loads fine,
and I get the login prompt at the monitor, so basically the tfp410 driver
seems to work. But the X-Server unloads claiming it can find no acceptable
modes. Here is the the Xorg.0.log <http://paste.ubuntu.com/7045149/>.
[ 136.094] (II) modesetting(0): Supported detailed timing:
[ 136.094] (II) modesetting(0): clock: 108.0 MHz Image Size: 338 x 270 mm
[ 136.095] (II) modesetting(0): h_active: 1280 h_sync: 1328 h_sync_end 1440
h_blank_end 1688 h_border: 0
[ 136.095] (II) modesetting(0): v_active: 1024 v_sync: 1025 v_sync_end 1028
v_blanking: 1066 v_border: 0
[ 136.095] (II) modesetting(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H
max: 81 kHz, PixClock max 145 MHz
[ 136.095] (II) modesetting(0): Monitor name: LCD175M
[ 136.096] (II) modesetting(0): Serial No: 3X556306NA
[ 136.096] (II) modesetting(0): EDID (in hex):
[ 136.096] (II) modesetting(0): 00ffffffffffff0038a3cb6701010101
[ 136.096] (II) modesetting(0): 2917010308221b78ea3095a6554b9a25
[ 136.096] (II) modesetting(0): 125054bfef80714f814f010101010101
[ 136.097] (II) modesetting(0): 010101010101302a009851002a403070
[ 136.097] (II) modesetting(0): 1300520e1100001e000000fd00384b1f
[ 136.097] (II) modesetting(0): 510e000a202020202020000000fc004c
[ 136.097] (II) modesetting(0): 43443137354d0a2020202020000000ff
[ 136.098] (II) modesetting(0): 0033583535363330364e410a2020000a
[ 136.098] (II) modesetting(0): No remaining probed modes for output DVI-0
[ 136.098] (II) modesetting(0): Output DVI-0 connected
[ 136.098] (WW) modesetting(0): Unable to find initial modes
[ 136.098] (EE) modesetting(0): Output DVI-0 enabled but has no modes
[ 136.099] (EE) modesetting(0): No modes.
[ 136.099] (II) UnloadModule: "modesetting"
[ 136.100] (EE) Screen(s) found, but none have a usable configuration.
[ 136.100] (EE)
Fatal server error:
[ 136.100] (EE) no screens found(EE)
[ 136.101] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 136.101] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 136.102] (EE)
[ 136.194] (EE) Server terminated with error (1). Closing log file.
Without the X server working the whole exercise seems pretty pointless...
Weirdly, if I don't hook up the I2C1 (i.e. just use the included
cape-bone-dvi-00A0.dts, I get somewhat *better* results. The X server
starts up and stays up, but the default resolution of 1152x864 is not
supported by my VGA monitors. I can xrandr -d :0 -s 1024x768 and get the
picture. But it seems like the wrong way to go about it. xrandr offers a
few options, but without I2C1 the EDID from the monitor is not read.
I also tried forcing resolution by specifying the LCD-cape-like tilcdc
panel, but this would lock me into one particular type of monitor, so
that's not good either.
On Wednesday, March 5, 2014 12:17:19 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Mar 5, 2014 at 10:58 AM, porkupan <vladimi...@gmail.com<javascript:>>
> wrote:
> > No, I definitely cannot afford any more bootup delay. I am already not
> > meeting my 25 second startup requirement, and I have to figure out why.
> The
> > dmesg is not much help, but it seems that the init scripts are too
> heavy.
>
> the biggest delay with ubuntu is usually dhcp.
>
> I have no problem on adding your custom cape dts, to the build script,
> then it'll be builtin..
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
