can you get the EDID from monitor? maybe you need apt install libdrm-tests, after that, please input modetest -M starfive -c to get EDID info.
1 Like
This is for the Samsung Monitor:
modetest -M starfive -c
Connectors:
id encoder status name size (mm) modes encoders
116 115 connected HDMI-A-1 160x90 12 115
modes:
index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
#0 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: preferred, driver
#1 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver
#2 1920x1080 30.00 1920 2008 2052 2200 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
#3 1920x1080 29.97 1920 2008 2052 2200 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver
#4 1920x1080 24.00 1920 2558 2602 2750 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
#5 1920x1080 23.98 1920 2558 2602 2750 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver
#6 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
#7 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
#8 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver
#9 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver
#10 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver
#11 640x480 59.94 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver
props:
1 EDID:
flags: immutable blob
blobs:
value:
00ffffffffffff004c2d030500000000
30120103801009780aee91a3544c9926
0f505420000001010101010101010101
010101010101023a801871382d40582c
4500a05a0000001e011d007251d01e20
6e285500a05a0000001e000000fd0018
3c1a4417000a202020202020000000fc
0053414d53554e470a202020202001ae
02031e71469004050320222309070783
010000e2000f67030c003000b82d011d
8018711c1620582c2500a05a0000009e
8c0ad08a20e02d10103e9600a05a0000
00180000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000031
2 DPMS:
flags: enum
enums: On=0 Standby=1 Suspend=2 Off=3
value: 0
5 link-status:
flags: enum
enums: Good=0 Bad=1
value: 0
6 non-desktop:
flags: immutable range
values: 0 1
value: 0
4 TILE:
flags: immutable blob
blobs:
value:
My problem: My cable was not entirely hdmi. I had a dvi to hdmi adapter on that one cable.
I replaced it with entirely different and only hdmi cable.
All good with Seiki Monitor:
root@starfive:/home/user# modetest -M starfive -c
Connectors:
id encoder status name size (mm) modes encoders
116 115 connected HDMI-A-1 700x390 16 115
modes:
index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
#0 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
#1 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver
#2 1920x1080 50.00 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
#3 1920x1080 30.00 1920 2008 2052 2200 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
#4 1920x1080 29.97 1920 2008 2052 2200 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver
#5 1920x1080 25.00 1920 2448 2492 2640 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
#6 1920x1080 24.00 1920 2558 2602 2750 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver
#7 1920x1080 23.98 1920 2558 2602 2750 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver
#8 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
#9 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
#10 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver
#11 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver
#12 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver
#13 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver
#14 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver
#15 640x480 59.94 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver
props:
1 EDID:
flags: immutable blob
blobs:
value:
00ffffffffffff004cab339300000000
051a0103804627960a6755a55b479c25
1e4f54a10800614081c0810081407140
010101010101662156aa51001e30468f
330056005300001e0e1f008051001e30
4080370055005300001c000000fc0053
45333248595443410a202020000000fd
00383f1e5009000a2020202020200102
020325714e010384050610121314151f
20212226150750095707830100006603
0c003000808f0ad08a20e02d10103e96
00c48e210000188c0ad08a20e02d1010
3e9600138e210000188c0ad090204031
200c405500138e210000188c0ad09020
4031200c405500c48e210000188c0ad0
8a20e02d10103e9600c48e21000018e7
2 DPMS:
flags: enum
enums: On=0 Standby=1 Suspend=2 Off=3
value: 0
5 link-status:
flags: enum
enums: Good=0 Bad=1
value: 0
6 non-desktop:
flags: immutable range
values: 0 1
value: 0
4 TILE:
flags: immutable blob
blobs:
value:
like @cwt comments, I also google this seiki model, it only support upto 1366x768 Seiki SE32HYT 32" 720p LED-LCD TV - 16:9 - HDTV - Black - ATSC - 178° / 178° - 1366 x 768 - Surround Sound - 16 W RMS - LED - Smart TV - 3 x HDMI - USB - Ethernet - Wireless LAN - - Newegg.com
yes, Currently, there are relatively few display resolutions supported by HDMI. We are working to modify the register configuration of the HDMI PHY to support more resolutions including CEA-861-D standard.
1 Like
Please recommend hdmi-only cables to other users. hdmi-to-dvi adapters give unwanted behaviour and not detecting available hdmi resolutions.
1 Like
I’m impressed by the sound quality. I’m also appreciating the synchronized audio/video from the streaming websites. VF2 is rocking! Looking forward to seeing the VF2 GPU/ffmpeg/gnome settling into the standard Debian riscv64 repos. The board is shining. Can you see the sparkles?
They are certainly not ideal but can be used (although also discouraged…)
As a data point I have a HDMI->VGA adaptor on a 16:10 (1280x1024) monitor from the late 2000’s. I get 640x480, 1280x720 and 1920x1080 as matching resolutions via cat /sys/class/drm/card1-HDMI-A-1/modes
I know from experience with my PI’s that this (very cheap) adaptor gives a fixed edid for a big list of common resolutions and frequencies no matter what monitor is attached. So I’m guessing the current driver selects these as the best matches from that, and for me this works since 1280x720 scales well. The monitor also handles downscaling from 1920x1080 during boot etc, but pops a ‘overdrive’ complaint on screen until I fix the resolution.
I’m hoping the work mentioned above by @Michael.Zhu will improve this too.
do you notice the status of red led when you input reboot command. it should be off for a second then turn to light.
1 Like
Some TV report it is support resultion higher their physical resultion.These TVs will convert to physical resultion.
I’m not really interested in a custom disto. I’m waiting for things to be upstreamed so we can use a regular distribution and a non-ancient kernel.
2 Likes
ok for 1 the color scheme sucks for color blind people. 2 the img should be auto resizing itself .
3 is the code for building the desktops avaible. I would prefer xfce over gnome.
1 Like
- Read the release notes to fix color
- No it shouldn’t, this is an engineering release, it expects you to read and follow the release notes.
apt install xfce4will do that. Just select it in GDM instead of gnome or makelightdmthe default when asked during xfce installation. No ‘code’ necessary.
1 Like
For the wayland image, attempting to do an xfce4 install results in missing package dependencies. Not all packages for both xfce and gnome have been built and available for riscv for this snapshot repo. I get a bunch of broken/red in aptitude when attempting to install xfce and gnome from there.
2 Likes
Am I the only one who doesn’t have fdisk? I have it in /sbin but not in /usr/bin
It requires root access to modify anything so is typically a System administration BINary, which can be useful in disaster recovery, to bring a dead machine back to life. I do not think that I have ever seen a tool for modifying partitions in /use/bin.
1 Like
Alrighty, thx. I’ve never actually paid attention to this before
You can typically run some System administration BINaries as normal users if all you want to do is list information (and not modify anything, provided you have access).
e.g.
$ /sbin/fdisk -l starfive-jh7110-VF2-SD-wayland.img
Disk starfive-jh7110-VF2-SD-wayland.img: 2.64 GiB, 2831155200 bytes, 5529600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5BDD0F8F-36BE-4C36-B1D9-1A904F6B5393
Device Start End Sectors Size Type
starfive-jh7110-VF2-SD-wayland.img1 4096 8191 4096 2M HiFive Unleashed BBL
starfive-jh7110-VF2-SD-wayland.img2 8192 16383 8192 4M HiFive Unleashed FSBL
starfive-jh7110-VF2-SD-wayland.img3 16384 221183 204800 100M EFI System
starfive-jh7110-VF2-SD-wayland.img4 221184 5527518 5306335 2.5G Linux filesystem
$
1 Like
This was not my experience with the wayland SD image yesterday. It installed xfce4 without any errors. It also installed lightdm as part of that and dpkg offered me the option to switch to it. I also installed i3 (my actual desktop of choice) and that was fine too. I can switch to them in GDM or lightdm, and Gnome, xfce4 and i3 run fine on my install.
1 Like
With this release (202303), what is the output of -
cat /proc/mtd
Regards
Aubrey
Hello @Stromkiller
damian@starfive:~/data/gccbuild_1$ sudo cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00001000 “spl”
mtd1: 00300000 00001000 “uboot”
mtd2: 00100000 00001000 “data”
damian@starfive:~/data/gccbuild_1$