please choosego to mobile | Continue to access the PC version
View: 12795|Reply: 21

PC 2 ubuntu video problems

[Copy link]

1

threads

5

posts

39

credits

Novice

Rank: 1

credits
39
Published in 2016-11-30 01:49:28 | Show all floors |Read mode
Edited by michaelofrai at 2016-11-30 01:48

I have two problems with the video on my Orange pi PC 2 (with H5).

Problem 1:  Can't set video resolution

If I list the video modes, I only get one choice:

cat /sys/class/graphics/fb0/modes
U:1280x720p-0



Problem 2:  Can't get display with DVI cable to work

I have an older monitor that only has a DVI connector.  I have a HDMI to DVI cable that works with other computers (including raspberry pi 2).
I think the monitor goes into power saving mode when I use PC2.

Thanks,
Michael

1

threads

5

posts

39

credits

Novice

Rank: 1

credits
39
 Author| Published in 2016-12-3 22:59:08 | Show all floors
I used dtc to set "screen0_output_mode = <0xa>;"
The dtc was updated, but it didn't seem to make any difference in the video.  That's what I expected, given your comments.

It guess this means that:
  • Everyone using the current images can only get 1280x720.
  • This is a know problem and is being worked on.
  • I should probably wait for a new image.

Also, should I expect a new image to work with my DVI monitors (using a hdmi to dvi cable)?

Thanks

P.S.  There was a time when I thought 1280 was awesome.  I think it was 1280x1024 back then.
Published in 2016-12-3 23:30:22 | Show all floors
Edited by Christos at 2016-12-3 23:31

I don't think anyone from the sunxi-linux community has done significant progress on the H5, from what I read it is most likely 6-months away from anything useful even with the minimal of functionality.

For the images that Buddy is providing, those that we currently all use, I do not know either if he is gonna look into it or not.

1

threads

65

posts

240

credits

Intermediate member

Rank: 3Rank: 3

credits
240
Published in 2016-11-30 16:35:52 | Show all floors
Not sure for H5, but H3 based OPI's needed different script.bin for different resolution and different video interfaces. Example :
script.bin.OPI-2_1080p60
script.bin.OPI-2_1080p60_dvi
script.bin.OPI-2_1080p60_hdmi
script.bin.OPI-2_480p
script.bin.OPI-2_480p_dvi
script.bin.OPI-2_480p_hdmi
script.bin.OPI-2_720p50
script.bin.OPI-2_720p50_dvi
script.bin.OPI-2_720p50_hdmi
script.bin.OPI-2_720p60
script.bin.OPI-2_720p60_dvi
script.bin.OPI-2_720p60_hdmi
script.bin.OPI-PC_1080p50
script.bin.OPI-PC_1080p50_dvi
script.bin.OPI-PC_1080p50_hdmi
script.bin.OPI-PC_1080p60
script.bin.OPI-PC_1080p60_dvi
script.bin.OPI-PC_1080p60_hdmi
script.bin.OPI-PC_480p
script.bin.OPI-PC_480p_dvi
script.bin.OPI-PC_480p_hdmi
script.bin.OPI-PC_720p50
script.bin.OPI-PC_720p50_dvi
script.bin.OPI-PC_720p50_hdmi
script.bin.OPI-PC_720p60
script.bin.OPI-PC_720p60_dvi
script.bin.OPI-PC_720p60_hdmi
script.bin.OPI-PLUS_1080p50
script.bin.OPI-PLUS_1080p50_dvi
script.bin.OPI-PLUS_1080p50_hdmi
script.bin.OPI-PLUS_1080p60
script.bin.OPI-PLUS_1080p60_dvi
script.bin.OPI-PLUS_1080p60_hdmi
script.bin.OPI-PLUS_480p
script.bin.OPI-PLUS_480p_dvi
script.bin.OPI-PLUS_480p_hdmi
script.bin.OPI-PLUS_720p50
script.bin.OPI-PLUS_720p50_dvi
script.bin.OPI-PLUS_720p50_hdmi
script.bin.OPI-PLUS_720p60
script.bin.OPI-PLUS_720p60_dvi
script.bin.OPI-PLUS_720p60_hdmi

look here: http://www.orangepi.org/orangepi ... &extra=page%3D1
for a new scriptbin pack

1

threads

5

posts

39

credits

Novice

Rank: 1

credits
39
 Author| Published in 2016-11-30 22:32:22 | Show all floors
I think, it must be different for the H5.

What output do you get, on the H3, for:
cat /sys/class/graphics/fb0/modes

Thanks

1

threads

65

posts

240

credits

Intermediate member

Rank: 3Rank: 3

credits
240
Published in 2016-12-1 17:37:40 | Show all floors
I have two framebuffer devices now on a OPI one, fb0 is a standard gpu for HDMI output, fb8 is a fbtft device for 2.2 SPI 240x320 LCD.
Here is output for both:

  1. root@OrangePI:~# cat /sys/class/graphics/fb0/modes
  2. U:1280x720p-0
  3. root@OrangePI:~# cat /sys/class/graphics/fb8/modes
  4. U:240x320p-0
  5. root@OrangePI:~#
Copy code

1

threads

5

posts

39

credits

Novice

Rank: 1

credits
39
 Author| Published in 2016-12-2 00:35:29 | Show all floors
Thanks.

I thought that "modes" would list all the available video resolution modes.  I guess I was wrong about that.

I don't think the H5 version of linux uses script.bin.  It does have a file called uEnv.txt:
  1. orangepi@Orangepi:/boot$ cat uEnv.txt
  2. console=tty0 console=ttyS0,115200n8 no_console_suspend
  3. kernel_filename=orangepi/uImage
  4. initrd_filename=initrd.img
  5. ethaddr=96:62:08:fb:22:8a
Copy code


Do you think I should change uEnv.txt?
If so, what should it look like?

Thanks

1

threads

65

posts

240

credits

Intermediate member

Rank: 3Rank: 3

credits
240
Published in 2016-12-2 23:29:10 | Show all floors
Here is a short description - http://linux-sunxi.org/UEnv.txt
Try to modify extraargs=...............disp.screen0_output_mode=EDID:1280x720p50

1

threads

5

posts

39

credits

Novice

Rank: 1

credits
39
 Author| Published in 2016-12-3 00:48:40 | Show all floors
It looks like you have to set "optargs".

Here's my uEnv.txt:
  1. root@Orangepi:~# cat /boot/uEnv.txt
  2. console=tty0 console=ttyS0,115200n8 no_console_suspend
  3. kernel_filename=orangepi/uImage
  4. initrd_filename=initrd.img
  5. ethaddr=96:62:08:fb:22:8a
  6. optargs=disp.screen0_output_mode=EDID:1920x1080p60
Copy code


Here's the resulting kernel command:
  1. root@Orangepi:~# cat /proc/cmdline
  2. console=tty0 console=ttyS0,115200n8 no_console_suspend disp.screen0_output_mode=EDID:1920x1080p60 earlycon=uart,mmio32,0x01c28000 mac_addr=96:62:08:fb:22:8a root=/dev/mmcblk0p2 ro rootwait
Copy code


But the display is still 1280x720p50.

Is 1920x1080 valid?  I know my monitor (4k TV) can support it.
Other ideas would be appreciated.

Thanks
Published in 2016-12-3 17:11:11 | Show all floors
The uEnv mentioned in wiki obviously covers the script.bin method and it is for older 32bit cpu eg armv7 (sun7,sun8), whereas H5 is 64bit armv53 (sun50) and it is using another intialization method, the one that is in mainline and is named device tree.

The images provided are using the device tree method (.dts/.dtb).
That means we need to get the current device tree file used (/boot/orangepi/OrangePiH5orangepi.dtb)
de-compile it via the dtc tool (dtc tool needs to be installed first though with apt-get install device-tree-compiler)
modify the resulted .dts file to have 'screen0_output_mode = <0xa>;' in disp@01000000 definition
re-compile the previously resulted .dts into a new dtb, copy that over the older /boot/orangepi/OrangePiH5orangepi.dtb and reboot.

That was suposedly needed in order for any new resolution to work.
Yet we tested it and it is not working as it should..
that means most likely there is a bug in the newly released image.

Hopefully at some point, Buddy could release the required u-boot repository used to generate this image's uboot.bin and this could actually help us find a solution on how to change the resolution.
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list