Jump to content


Photo

OS MIO+ 4K - no framebuffer available


  • Please log in to reply
24 replies to this topic

Re: OS MIO+ 4K - no framebuffer available #21 XRayhTec

  • Senior Member
  • 449 posts

+8
Neutral

Posted 25 September 2024 - 11:03

Looks like driver issue.
Did you try another firmware?

607xRAYHTECV13

ET4x00RAYHTEC4.0

XP1000RAYHTEC7B

H9COMBORAYHTEC9b


Re: OS MIO+ 4K - no framebuffer available #22 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 25 September 2024 - 12:35

@el bandido

 

That pinout can not be right. "Ground" is on Ring 2 and only on Ring 2 (assuming Ring 2 is the one near Sleeve).

 

I'll have to try now which is TX and which RX.

If  my pinout is wrong, then what is the Correct pinout?
Thanks.



Re: OS MIO+ 4K - no framebuffer available #23 WanWizard

  • PLi® Core member
  • 70,365 posts

+1,807
Excellent

Posted 25 September 2024 - 12:44

Looks like driver issue.
Did you try another firmware?

 

I already mentioned that. Corruption was ruled out by the TS by flashing a newly downloaded image.

 

The drivers are from 20211103, so other firmware will have the same drivers, unless it is very old.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OS MIO+ 4K - no framebuffer available #24 XRayhTec

  • Senior Member
  • 449 posts

+8
Neutral

Posted 25 September 2024 - 13:17

I noticed the dvb modules for Osmio4kplus in Open Alliance are dated 20211228.

607xRAYHTECV13

ET4x00RAYHTEC4.0

XP1000RAYHTEC7B

H9COMBORAYHTEC9b


Re: OS MIO+ 4K - no framebuffer available #25 Stan

  • Senior Member
  • 377 posts

0
Neutral

Posted 25 September 2024 - 16:15

@el bandido

Your pinout is correct. I was using the wrong plug (14mm instead of 17mm lenght), and therefore the contacts were misaligned.




3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users