probably wont work due to the sad face, why is there no power off button, if it hangs i have to pull the plug, corrupting the install?
The sad face has nothing to do with SSH access that is just Kodi crashing.
Because it is designed for 24x7 operation
started again on 16:9 screen, sad face went away, went into power exit, press esc got command line
did EDID command as asked on 16:9 screen, then on 21:9 screen to confirm different results (recognises new screen change, see results
OK without a network connection this is going to be tricky. Can you, when connected to the 21:9 screen, insert a USB stick and grab the result like this:
ls /media/* to see the name of your USB stick.
cat /sys/class/amhdmitx/amhdmitx0/rawedid > /media/<nameofyourUSBstick>/edid.txt
Then read edid.txt from the stick in a PC (eg in notepad) and cut and paste in here.
00ffffffffffff001e6d1477efb40600051d010380502278eaca95a6554ea1260f5054256b807140818081c0a9c0b300d1c08100d1cfcd4600a0a0381f4030203a001e4e3100001a023a801871382d40582c45001e4e3100001e000000fd00384b1e5a19000a202020202020000000fc004c472048445220574648440a200165020337f1230907074c100403011f1359da125d5e5f830100006d030c001000b83c20006001020367d85dc4013c8000e305c000e3060501295900a0a038274030203a001e4e3100001a565e00a0a0a02950302035001e4e3100001a000000ff003930354e54475943583533350a0000000000000000000000000000000000005a
1 Like
OK, thanks. You will have to leave it with us for a bit. Meanwhile, if you set the GUI resolution to 1080p60Hz with your 16:9 screen attached, can you boot afterwards with the 21:9 screen attached?
i can run 16:9 on the 21:9 but the osd is sort of broke, i canāt read all the items on the screen, 16:9 movies are cropped on it and i try to change the zoom level on it but itās not recognising it correctly, mostly ignoring it, surprisingly it does play scope movies correctly but hard to navigate osd, itās not really usable, for example i canāt even switch sub-titles off in my scope movies as canāt see options very well, usually use 1920x1080 or 3840x2160 on the scope monitor.
Hi @MicroM
Hopefully the issue is now addressed.
Iād appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:
- Login via the command line
- Edit the file
/etc/apt/sources.list - Add the following line:
deb http://apt.osmc.tv buster-devel main - Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot - Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.
ok my monitor is in the repair shop, will let you know likely in 2 weeks time, so after i have tested this i remove the
deb http://apt.osmc.tv buster-devel main
line in the text file?
Sorry to hear that. I was reading the reviews of that monitor which seem ā¦ mixed. Otherwise it looks like a good choice for anyone who wants HDR but on a smaller screen.
Yes, remove that line after testing if you want to avoid bleeding-edge updates.
it just has backlight bleed, they all do as they are just producitivty monitors so they donāt bother fixing it, they will fix it though if you ask, only way to get 2.39 screen for media consumption.
i take it you need to have a network connection on the device for this to work.
You will need a network connection to do the update, yes. Why exactly canāt you get the Vero online if you can access the internet from a PC?
itās in a different room, i will try to get wifi working on it, i havenāt tried that yet, otherwise i will move the monitor + verk into another room with it.
tried editing the file using nano sudo, added the line, tried command, got error, am i meant to edit the last line rather than add new line?
Difficult to tell, but is that http;// you have typed? Should be http://
Adding a new line is correct.
you were right, ok i did it, it installed the new update, it didnāt fix the issue, same result.
Please lost logs again, then.
post logs you mean?
what logs, is it my EDID info, because i donāt think that would change.
there is no error anyway, it just displays incorrectly.
Unfortunately some devices do change EDID depending on the state they are in or the devices connected to them, which defeats the point of having an EDIDā¦
We need to see the kernel message log. That should tell us the timings the chip is using for your display.