| 09:45 | Kiranos | I'm tyring out geekbox, theres a big jump in resolution between 1360*768 to 1920*1080 is there a limitation why there are no more inbetween? |
| 09:52 | jnettlet | Kiranos, there are more but it is possible your TV does not support them. There is a spec for CEA timings which is standard modes/timings HDMI can use with audio. There is then HDMI Vesa timings which is DVI-D modes that HDMI can support without audio. Those are the base standards for the spec. There are ways to manipulate the timings to get more things to work, but that is above and beyond the standards spec. |
| 09:53 | jnettlet | First you need to look at the EDID your display provides and see what modes it reports that it supports. |
| 09:59 | Kiranos | ok I'll look into it but now on my TV it doesnt show the whole picture |
| 10:13 | jnettlet | Kiranos, is your TV 1080p or 720p? |
| 10:35 | Kiranos | 720p |
| 10:37 | jnettlet | okay that is why the larger resolutions are getting cut off. Your TV isn't auto-scaling the higher resolutions. Regardless your native picture is 1280x720 |
| 10:38 | jnettlet | If you select that option then everything will work optimally |
| 10:39 | Kiranos | ok thanks! |
| 10:42 | jnettlet | if that doesn't work let me know. I work on graphics drivers so it is good to know why things don't work right. |
| 10:51 | Kiranos | jnettlet: took 1280x720 and the sceen when haywire :) cropped but I reset the box and see if it fixes itself after a reboot |
| 10:53 | Kiranos | http://www.lcd-compare.com/televiseur-SAMLE22B450-SAMSUNG-LE22B450.htm |
| 10:53 | Kiranos | says my tv is 1366 x 768 :) |
| 10:53 | Kiranos | sorry I'm kinda new to this |
| 10:55 | Kiranos | geekbox only allow 1360*768 so it doesnt work as it should |
| 10:56 | jnettlet | Kiranos, oh you have one of those TV's :-) |
| 11:00 | jnettlet | Kiranos, looking at the specs for your monitor, It is trying to use 1360x768 in PC mode. However for TV mode it wants 720p. If you want audio then to work then use 720p and let the hardware scale it to full screen. Otherwise 1360x720 is the proper resolution. |
| 11:00 | jnettlet | I have to run now, but let me know how things work out. |
| 11:00 | Kiranos | jnettlet: ok thanks I'll investigate |
| 13:38 | pioj_ | hi |
| 13:40 | pioj_ | I just post at the Success Story forums. Please take a look and see if you can help me with my cubox... |
| 13:54 | KaZeR | help about a success story? |
| 14:46 | dv_ | "i've had too much success with my cubox. help me!" |
| 14:58 | jnettlet | a good problem to have |
| 15:45 | Kiranos | anyone know why geekbox for cubox has lirc hardware.conf |
| 15:45 | Kiranos | DRIVER="mplay" |
| 15:45 | Kiranos | DEVICE="/dev/ttyUSB0" |
| 15:45 | Kiranos | ? |
| 15:58 | Kiranos | might be that it just the dfault for general purpose geekbox |
| 16:45 | KaZeR | dv_, ;à |
| 16:45 | KaZeR | gah |
| 16:45 | KaZeR | dv_, :) |
| 18:09 | Kiranos | -rwxr-xr-x 1 1000 1000 43372 /usr/sbin/eventlircd |
| 18:09 | Kiranos | -rwxr-xr-x 1 1000 1000 157368 /usr/sbin/lircd |
| 18:09 | Kiranos | I'm using geekbox and lircd seems to use the above: eventlircd instead of normal lircd anyone know why? |
| 18:09 | Kiranos | 795 root /usr/sbin/eventlircd --evmap=/etc/eventlircd.d --socket=/var/run/lirc/lircd --release=_UP |
| 18:10 | Kiranos | is my process it starts |