vc4-kms-v3d driver not working with custom HDMI mode ...

The max pixel clock for vc4-kms-v3d is dictated by the driver, and there's no override provided. https://github.com/raspberrypi/linux/blob/rpi- ... Skiptocontent {{message}} raspberrypi / linux Public Notifications Fork 4.2k Star 9k Code Issues 634 Pullrequests 46 Actions Projects 0 Wiki Security Insights More Code Issues Pullrequests Actions Projects Wiki Security Insights Newissue Haveaquestionaboutthisproject?SignupforafreeGitHubaccounttoopenanissueandcontactitsmaintainersandthecommunity. Pickausername EmailAddress Password SignupforGitHub Byclicking“SignupforGitHub”,youagreetoourtermsofserviceand privacystatement.We’lloccasionallysendyouaccountrelatedemails. AlreadyonGitHub? Signin toyouraccount Jumptobottom vc4-kms-v3ddrivernotworkingwithcustomHDMImode(group2,mode87) #4516 Open MakerMatrixopenedthisissue Aug8,2021 ·16comments Open vc4-kms-v3ddrivernotworkingwithcustomHDMImode(group2,mode87) #4516 MakerMatrixopenedthisissue Aug8,2021 ·16comments Labels KMSIssue IssuesrelatedtoKMS/DRMdrivers Comments Copylink MakerMatrix commented Aug8,2021 • edited Isthistherightplaceformybugreport? Ithinkso-thevc4-kms-v3ddriverisakerneloverlayAFAIK Describethebug WhenIhaveacustomHDMItiminglistedinmyconfig.txt,withvc4-kms-v3denabled,theconsolescreengoesblankandstopsoutputtingavideosignal.Thisappearstooccuratthepointwheretheinitprocesslaunchestheservicewherethegpudriverisdetected/enabled.WhenIputthedefaultconfig.txtbackandenablethefullGLdriver,videoworks(onaregular1080pscreen,whichisnotmydisplayofinterest). Toreproduce Installabasicraspbianlite,fullyupdateit,enablethefullGLdriver,thenenterlinesinconfig.txtlikethis: #ForceaspecificHDMImode(group2mode87willforcethecustomtiming) hdmi_pixel_freq_limit=300000000 hdmi_timings=2560012310501600012440005002220000005#222MHziswhattheEDIDreportshttps://pastebin.com/4u9DV7L1 Additionalcontext Thedisplayinquestionisahi-resRGBMIPILCDwithanHDMI->MIPIconvertersittingbetweenthePIandtheLCD.However,whenIhookittoa1080Pdisplay,thesamethinghappensatthesamespot.Everythingworksfinewithlegacyorfkms(otherthanthefactthatIcan'tseemtogetSDL2workingwithouthavingtheextraX11layerinbetweenmyappandthevideodriver). Thetextwasupdatedsuccessfully,buttheseerrorswereencountered: MakerMatrix mentionedthisissue Aug8,2021 RPI4failingtocreatecontextforopenglwithoutXwithpropersdl2 #4328 Closed Copylink Collaborator popcornmix commented Aug9,2021 Thehdmi_*entriesinconfig.txtarehandledbythefirmwareanddonotgenerallyaffectthekmsdriver. Youneedtoconfiguredisplaytimingsusingstandardlinuxmechanisms.e.g.withxrandr. 👍 1 MakerMatrixreactedwiththumbsupemoji Sorry,somethingwentwrong. Copylink Contributor 6by9 commented Aug9,2021 • edited IdeallyyourdisplaywouldhaveavalidEDIDthatwillbereadandfullyprocessedbyvc4-kms-v3d.Sometimesitneedsdisable_fw_kms_setup=1inconfig.txttostopthefirmwaretryingtoinfluenceit. Ifitdoesn'thaveanyEDID,thenyoucouldcreateone,putitin/lib/firmware,andadddrm.edid_filename=foo.edidto/boot/cmdline.txttotellDRMtoloadthatinsteadoftryingtoreaditfromthedisplay. 👍 1 MakerMatrixreactedwiththumbsupemoji Sorry,somethingwentwrong. Copylink Author MakerMatrix commented Aug9,2021 • edited TheHDMI->MIPIadapterboarddoeshaveanEDID.Iused/opt/vc/bin/tvservice-d,followedbythecompanionedidparsertocraftthemodelineIwaspassingtothefirmwareinconfig.txt. So,Ihavecommentedallthehdmi*stuffoutofconfig.txt,addeddisablefw_kms_setup=1,enabledthekmsdriveranditsortofworks.Butitlookslikethetimingsarealloff.Thelefthalfofthescreenisshowingwhatshouldbeontherighthalfandthereis3.x-foldsymmetryontheverticalaxiswhereI'mseeing~1/3rdoftheverticalscreenresolutionoutput3.xtimes.Thisiswhatraspi-configlookslike: Majorstepintherightdirectionthough!Thisistheedidparseroutput: Enablingfuzzyformatmatch... Parsingfoo... HDMI:EDIDversion1.3,1extensions,screensize12x7cm HDMI:EDIDfeatures-videodef0x80!standby!suspend!activeoff;colourencoding:RGB444|YCbCr422;sRGBisnotdefaultcolourspace;preferredformatisnative;doesnotsupportGTF HDMI:EDIDfoundmonitornamedescriptortag0xfc HDMI:EDIDmonitornameisZHDISP08901 HDMI:EDIDignoredunknowndescriptortag0x10 HDMI:EDIDignoredunknowndescriptortag0x10 HDMI:EDIDdoesnotyetknowmonitorverticalrange,settingtodefault24to120Hz HDMI:EDIDfailedtofindamatchingdetailformatfor2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDcalculatedrefreshrateis50Hz HDMI:EDIDguessingtheformattobe2560x1600p@50Hz HDMI:EDIDfoundunknowndetailtimingformat:2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDestablishedtimingI/IIbytesare000000 HDMI:EDIDstandardtimingsblockx8:0x01010101010101010101010101010101 HDMI:EDIDparsingv3CEAextension0 HDMI:EDIDmonitorsupport-underscanITformats:no,basicaudio:yes,yuv444:yes,yuv422:yes,#nativeDTD:4 HDMI:EDIDfailedtofindamatchingdetailformatfor2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDcalculatedrefreshrateis50Hz HDMI:EDIDguessingtheformattobe2560x1600p@50Hz HDMI:EDIDfoundunknowndetailtimingformat:2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDfailedtofindamatchingdetailformatfor2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDcalculatedrefreshrateis50Hz HDMI:EDIDguessingtheformattobe2560x1600p@50Hz HDMI:EDIDfoundunknowndetailtimingformat:2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDfailedtofindamatchingdetailformatfor2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDcalculatedrefreshrateis50Hz HDMI:EDIDguessingtheformattobe2560x1600p@50Hz HDMI:EDIDfoundunknowndetailtimingformat:2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDfailedtofindamatchingdetailformatfor2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDcalculatedrefreshrateis50Hz HDMI:EDIDguessingtheformattobe2560x1600p@50Hz HDMI:EDIDfoundunknowndetailtimingformat:2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDfailedtofindamatchingdetailformatfor2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDcalculatedrefreshrateis50Hz HDMI:EDIDguessingtheformattobe2560x1600p@50Hz HDMI:EDIDfoundunknowndetailtimingformat:2560x1600phfp:123hs:10hbp:50vfp:12vs:4vbp:4pixelclock:222MHz HDMI:EDIDdoesnotunderstandCEAformatcode0 HDMI:EDIDdoesnotunderstandCEAformatcode0 HDMI:EDIDdoesnotunderstandCEAformatcode0 HDMI:EDIDdoesnotunderstandCEAformatcode0 HDMI:EDIDdoesnotunderstandCEAformatcode0 HDMI:EDIDdoesnotunderstandCEAformatcode0 HDMI:EDIDdoesnotunderstandCEAformatcode0 HDMI:EDIDfoundaudioformat2channelsPCM,samplerate:32|44|48|88|96|176|192kHz,samplesize:16|20|24bits HDMI:EDIDfoundHDMIVSDBlength6 HDMI:EDIDHDMIVSDBhasphysicaladdress3.0.0.0 HDMI:EDIDHDMIVSDBsupportsAI:yes,duallinkDVI:no HDMI:EDIDHDMIVSDBdeepcoloursupport-48-bit:no36-bit:no30-bit:noDC_yuv444:no HDMI:EDIDHDMIVSDBhasnolatencyinformation HDMI:EDIDaddingmandatorysupportforDMT(4)640x480p@60Hz HDMI:EDIDaddingmandatorysupportforCEA(1)640x480p@60Hz HDMI:EDIDfilteringformatswithpixelclockunlimitedMHzorh.blankingunlimited HDMI:EDIDnoknownpreferredformathasbeenset HDMI:EDIDfilteringpreferredgrouphasbeenchangedfromInvalidtoCEA HDMI:EDIDbestscoremodeinitialisedtoCEA(1)640x480p@60Hzwithpixelclock12MHz(score25) HDMI:EDIDbestscoremodeisnowCEA(1)640x480p@60Hzwithpixelclock25MHz(score61864) HDMI:EDIDDMTmode(4)640x480p@60Hzwithpixelclock25MHzhasascoreof18432 HDMI0:EDIDpreferredmodeisupdatedtoCEA(1)640x480p@60Hzwithpixelclock25200000Hz HDMI:EDIDhasHDMIsupportandaudiosupport /opt/vc/bin/edidparserexitedwithcode0 Sorry,somethingwentwrong. Copylink Contributor 6by9 commented Aug10,2021 PleaseposttherawEDIDforanalysis. edid-decodeshouldbeusedinpreferencetoedid-parser. (Minortypocorrectedinmyearlierpost-disable_fw_kms_setup=1asI'dmissedanunderscore.Itshouldmeanthatthereisnoentrystartingvideo=HDMI-1...in/proc/cmdline) Sorry,somethingwentwrong. Copylink Author MakerMatrix commented Aug10,2021 • edited Irepaireddisable_fw_kms_setupandverifiedthatindeedthereisnolongeravideo=HDMI*entryin/proc/cmdline.Thescreenisnowblankagain,afterthekmsdriverloads.ChangingtheHDMIcableovertoanLG1080Pscreenresultsin"nosignal".dmesgsays: pi@shrimp:~$dmesg|grepvc4 [10.011657]fb0:switchingtovc4drmfbfromsimple [10.017115]vc4-drmsoc:gpu:bound3f400000.hvs(opsvc4_hvs_ops[vc4]) [10.022947]rcrc0:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0 [10.023223]input:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0/input5 [10.106689]vc4_hdmi3f902000.hdmi:Couldnotregistersoundcard:-517 [10.385062]vc4-drmsoc:gpu:bound3f400000.hvs(opsvc4_hvs_ops[vc4]) [10.392436]rcrc0:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0 [10.392718]input:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0/input13 [10.402211]vc4_hdmi3f902000.hdmi:Couldnotregistersoundcard:-517 [10.523289]vc4-drmsoc:gpu:bound3f400000.hvs(opsvc4_hvs_ops[vc4]) [10.525500]rcrc0:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0 [10.525825]input:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0/input21 [10.532012]vc4_hdmi3f902000.hdmi:Couldnotregistersoundcard:-517 [10.856045]vc4-drmsoc:gpu:bound3f400000.hvs(opsvc4_hvs_ops[vc4]) [10.863206]rcrc0:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0 [10.863518]input:vc4as/devices/platform/soc/3f902000.hdmi/rc/rc0/input22 [10.872939]vc4-drmsoc:gpu:bound3f902000.hdmi(opsvc4_hdmi_ops[vc4]) [10.873294]vc4-drmsoc:gpu:bound3f806000.vec(opsvc4_vec_ops[vc4]) [10.873677]vc4-drmsoc:gpu:bound3f004000.txp(opsvc4_txp_ops[vc4]) [10.874031]vc4-drmsoc:gpu:bound3f206000.pixelvalve(opsvc4_crtc_ops[vc4]) [10.874647]vc4-drmsoc:gpu:bound3f207000.pixelvalve(opsvc4_crtc_ops[vc4]) [10.875013]vc4-drmsoc:gpu:bound3f807000.pixelvalve(opsvc4_crtc_ops[vc4]) [10.875267]vc4-drmsoc:gpu:bound3fc00000.v3d(opsvc4_v3d_ops[vc4]) [10.926578][drm]Initializedvc40.0.020140616forsoc:gpuonminor0 [10.976380]vc4-drmsoc:gpu:[drm]Cannotfindanycrtcorsizes [20.979661]vc4-drmsoc:gpu:[drm]Cannotfindanycrtcorsizes edid-decode(thanks,Ialsoincludetherawedid.datinsidetheattachedzip)says: edid.zip pi@shrimp:~$edid-decodefoo EDIDversion:1.3 Manufacturer:ZHDModel1807SerialNumber0 Madeinweek8of2018 Digitaldisplay Maximumimagesize:12cmx7cm Gamma:2.20 RGBcolordisplay Firstdetailedtimingispreferredtiming Displayx,yChromaticity: Red:0.6250,0.3398 Green:0.2802,0.5947 Blue:0.1552,0.0703 White:0.2832,0.2978 Establishedtimingssupported: Standardtimingssupported: Detailedmode:Clock222.190MHz,640mmx400mm 2560268326932743hborder0 1600161216161620vborder0 +hsync+vsync VertFreq:50Hz,HorFreq:81002Hz Monitorname:ZHDISP08901 Dummyblock Dummyblock Has1extensionblocks Checksum:0xd5(valid) CTAextensionblock Extensionversion:3 19bytesofCTAdata Videodatablock Audiodatablock LinearPCM,maxchannels2 Supportedsamplerates(kHz):192176.49688.24844.132 Supportedsamplesizes(bits):242016 Vendor-specificdatablock,OUI000c03(HDMI) Sourcephysicaladdress3.0.0.0 Supports_AI Basicaudiosupport SupportsYCbCr4:4:4 SupportsYCbCr4:2:2 4nativedetailedmodes Detailedmode:Clock222.180MHz,1080mmx1920mm 2560268326932743hborder0 1600161216161620vborder0 -hsync-vsync VertFreq:49Hz,HorFreq:80998Hz Detailedmode:Clock222.180MHz,1080mmx1920mm 2560268326932743hborder0 1600161216161620vborder0 -hsync-vsync VertFreq:49Hz,HorFreq:80998Hz Detailedmode:Clock222.180MHz,1080mmx1920mm 2560268326932743hborder0 1600161216161620vborder0 -hsync-vsync VertFreq:49Hz,HorFreq:80998Hz Detailedmode:Clock222.180MHz,1080mmx1920mm 2560268326932743hborder0 1600161216161620vborder0 -hsync-vsync VertFreq:49Hz,HorFreq:80998Hz Detailedmode:Clock222.180MHz,1080mmx1920mm 2560268326932743hborder0 1600161216161620vborder0 -hsync-vsync VertFreq:49Hz,HorFreq:80998Hz Checksum:0x9b(valid) Sorry,somethingwentwrong. Copylink Contributor 6by9 commented Aug10,2021 DTD1:2560x160050.002Hz8:581.003kHz222.190MHz(640mmx400mm) Hfront123Hsync10Hback50HpolP Vfront12Vsync4Vback4VpolP Horizontalfrontporchof123isgoingtoberejectedasamodeasthePi4hardwarecanonlysupportevenvaluesinhorizontaltimings(https://www.raspberrypi.org/documentation/computers/config_txt.html#raspberry-pi-4-hdmi-pipeline) Advertisingthesamedetailedtimings6timesintheEDIDseemsalittleodd,butnotinvalid.Itoffersnoothermodes,whichexplainsthe [10.976380]vc4-drmsoc:gpu:[drm]Cannotfindanycrtcorsizes [20.979661]vc4-drmsoc:gpu:[drm]Cannotfindanycrtcorsizes asDRMendsupwithnovalidmodesforthedisplay. Withoutdisable_fw_kms_setup=1thefirmwarewouldhavestuckavideo=HDMI-1:lineinbasedonthestandardmodethatitbelievedshouldbeused,andDRMthenusesthestandardCVTalgorithmtogeneratethetimingsusingthat. SeeingasthisisrunningthroughanHDMItoDSIbridge,theporchtimingsareunlikelytobethatcritical.AquickhacktotheEDIDsuchastheattached(decreasesthefrontporchto122)maymakeithappy,orgoingtheotherwayto124. linux_4516_2.zip Seeabovefordetailsofputtingitin/lib/firmwareandalteringcmdline.txt. Sorry,somethingwentwrong. Copylink Author MakerMatrix commented Aug11,2021 • edited I'mlearningalot.Stillnotquitethere. pi@shrimp:~$dmesg|grepedid [0.000000]Kernelcommandline:coherent_pool=1M8250.nr_uarts=1snd_bcm2835.enable_compat_alsa=0snd_bcm2835.enable_hdmi=1vc_mem.mem_base=0x3ec00000vc_mem.mem_size=0x40000000console=ttyS0,115200console=tty1root=PARTUUID=86178334-02rootfstype=ext4elevator=deadlinefsck.repair=yesrootwaitdrm.edid_firmware=HDMI-A-1:edid/6by9-2560x1600_50-edid.dat [10.769520][drm]GotexternalEDIDbaseblockand1extensionfrom"edid/6by9-2560x1600_50-edid.dat"forconnector"HDMI-A-1" [10.770714][drm]GotexternalEDIDbaseblockand1extensionfrom"edid/6by9-2560x1600_50-edid.dat"forconnector"HDMI-A-1" [20.956193][drm]GotexternalEDIDbaseblockand1extensionfrom"edid/6by9-2560x1600_50-edid.dat"forconnector"HDMI-A-1" Andverifying(thisisadifferentblobandadifferentbootfromtheoneabove): pi@shrimp:~$diff-s/lib/firmware/edid/edid.dat/sys/devices/platform/soc/soc\:gpu/drm/card0/card0-HDMI-A-1/edid Files/lib/firmware/edid/edid.datand/sys/devices/platform/soc/soc:gpu/drm/card0/card0-HDMI-A-1/edidareidentical Soloadingtheedidblobseemstohaveworked.Howeverstillablankscreenwhenthedriverloads,and: pi@shrimp:~$dmesg|grepvc4|tail-2 [10.771716]vc4-drmsoc:gpu:[drm]Cannotfindanycrtcorsizes [20.957209]vc4-drmsoc:gpu:[drm]Cannotfindanycrtcorsizes Ialsotriedtheedid.datrightofftheHDMI->DSIboard(I'mon3B+,thinkingmaybetheeven-pixel-clock-valuesissuedoesn'tapply)andhadtheexactsameresult. AreyouusingDeltacastE-EDIDtobuild/editedidfilesoristheresomethingbetter?OncethisgetssortedIplantowriteitupinablogpostforposterity(alreadydraftingit). Edit:IhaveswitchedtomyLGultrawide(2560x1080)screen,attemptingtogetthe3B+todrivethepanelatitsnativeresolution.ItseemstosufferasimilarissueinthatIcannotgetthehighest-resolutiondetailedtimingtowork.AmIhittingthemaxpixelclockforPi3Bandsothosemodesgettossedout?Iwasoverridingthatwithhdmi_pixel_freq_limitwhenusingthefirmwaremode. Sorry,somethingwentwrong. Copylink Author MakerMatrix commented Aug11,2021 • edited Okay,theremayhaveactuallybeentwobrokenthings.Iswitchedthe3B+outfora4BandnowtheLGultrawideworksat2560x1080.So,thepixelclocklimitwasprobablyresponsibleforthatmodenotworkingonthatscreen. Then,loadingyourEDIDintoDeltacast,IsawthatH.Blankwasanoddnumber(183).Changeditto184andBOOM! pi@pi4-msla:~$fbset-i-v LinuxFrameBufferDeviceConfigurationVersion2.1(23/06/1999) (C)Copyright1995-1999byGeertUytterhoeven Openingframebufferdevice`/dev/fb0' Usingcurrentvideomodefrom`/dev/fb0' mode"2560x1600" geometry256016002560160016 timings0000000 acceltrue rgba5/11,6/5,5/0,0/0 endmode Gettingfurtherframebufferinformation Framebufferdeviceinformation: Name:vc4drmfb Address:0 Size:8192000 Type:PACKEDPIXELS Visual:TRUECOLOR XPanStep:1 YPanStep:1 YWrapStep:0 LineLength:5120 Accelerator:No Thankyouverymuch. IwouldstillbecurioustoknowifthereisakernelwaytooverridethemaxpixelclockonthePi3series,orifIneedtogiveuponthatunderKMS.Isearchedforkernelcommandlineparametersthatmightbehavelikehdmi_pixel_freq_limitbutdidnotfindanything.Itriedsettingitinconfig.txtbutIsuspectthatthisisoverriddenbydisable_fw_kms_setup=1 Sorry,somethingwentwrong. Copylink Contributor 6by9 commented Aug11,2021 IwaseditingtheEDIDbyhand.Usexxd-g0edid.binedid.txttoconverttoatextfile,edit(inthiscaseconvert123tohex7b,findthat,andreplace),andthenxxd-r-g0edid.txtedid_new.bintoconvertbacktohex. Runthroughedid-decodeandittellsyouthechecksumsfailandwhattheyshouldbe.Theyarebytes128&256,sotheendofline8and16respectively.Fixthoseup.Runthroughxxd-r...again,andyoushouldbegoodtogo. Ifyouadddrm.debug=0x14to/boot/cmdline.txtthenDRMlogsallthemodeselectionandvalidationinformationtothekernellog. Themaxpixelclockforvc4-kms-v3disdictatedbythedriver,andthere'snooverrideprovided.https://github.com/raspberrypi/linux/blob/rpi-5.10.y/drivers/gpu/drm/vc4/vc4_hdmi.c#L2444dictates162MHzforPi0-3.222MHzisquitealongwayabovethespecforPi3. Pi0-3donothavethelimitationofeventimingsastheyonlyrunat1pixelperclockcycle. 👍 1 MakerMatrixreactedwiththumbsupemoji Sorry,somethingwentwrong. Copylink Author MakerMatrix commented Aug11,2021 Oooh,thedebugoptionwillbehandy.Ihavemorescreenslikethisinmyfuture. That'sarealshameaboutthepixelclock.Thefirmwareoptionsaroundthatare/wereveryhandy.Iwillsuggestthat222MHzisnottoocrazy.InmyexperiencetogetthattoworkreliablyyoujusthavetotelltheCPUtoneverrunbelow800MHz(arm_freq_min).OrmaybeoneoftheGPUclockoptionswouldwork-Ijustdiscoveredthosewhenwadingthroughdocsforthisissue.So,222MHzdoesnotreallyrequireoverclocking,justtrimmingsomeofthepowersavingfeatures.Similarly,toget4K/30toworkonPi3,youneed~1GHzIIRC,sorightnearthelimitbutdoableundermanycircumstances.Theseareveryhandythingsandofcourse,youknowthatnowI'mgoingtonaivelyaskbecauseIhavenoideawhatkindofeffortI'msuggesting-cansuchafeaturegetaddedtothedriver?:-D Thankyouagain,thishasbeenextremelyenlighteningandhelpful.Iwillfinishmypostontheweekendandreportbackheretoaskforyourfeedback,ifyouhavetime. Sorry,somethingwentwrong. MakerMatrix mentionedthisissue Aug17,2021 display.initbindstoX11clientinsteadofconsole. pygame/pygame#2107 Open Copylink lesar commented Nov3,2021 Metoohavethesameproblem. Iuse disable_overscan=1 dtoverlay=vc4-kms-v3d hdmi_drive:0=1 hdmi_group:0=2 hdmi_mode:0=82 hdmi_drive:1=1 hdmi_group:1=2 hdmi_mode:1=82 andonlyfkmswork Sorry,somethingwentwrong. Copylink Contributor 6by9 commented Nov3,2021 Metoohavethesameproblem. Noyoudon't-you'retryingtoforceanalternatemode,notusinggroup2/mode87tospecifycustomtimingsviahdmi_timingsorhdmi_cvt. #4516(comment)and#4516(comment)bothstillapply-vc4-kms-v3ddoesnotusethehdmi_*entriesfromconfig.txt. Group2(DMT)mode82appearstobeastandard1080p60mode.Whytheneedtoforceit? vc4-kms-v3dlargelyreliesonvalidEDIDs. Sorry,somethingwentwrong. Copylink lesar commented Nov4,2021 • edited Thanks@6by9 issometimeIrunUbuntuonPIand,atinitialtime,ifIdonotusegroupandmodeIgetonlyablackscreen. Itrytoremovethissettingsandallworkwellbutworkonlyonfkms. IfIusekms,monitorarenotrecognizedandIgetonlyonescreenworking. thisismyconfignow: disable_overscan=1 boot_delay=2 dtparam=audio=on dtoverlay=vc4-fkms-v3d #dtoverlay=vc4-kms-v3d#thisnotwork ifIusevc4-kms-v3dinusercfg.txtanddo: $sudoxrandr--outputHDMI-1--auto--left-ofHDMI-2 Iget: xrandr:Failedtogetsizeofgammaforoutputdefault warning:outputHDMI-1notfound;ignoring andonlyonescreenisworking I'monUbuntu20.04.35.4.0-1045-raspiaarch64 Sorry,somethingwentwrong. Copylink Contributor juergh commented Nov15,2021 issometimeIrunUbuntuonPI ThenyoushouldfileabugagainsttheUbunturaspikernelsinceit'sdifferentfromtheRaspiOSkernel.https://bugs.launchpad.net/ubuntu/+source/linux-raspi Sorry,somethingwentwrong. Copylink lesar commented Nov21,2021 OpssorryIhavemisunderstoodthisgithubaccountpurpose. Sorry,somethingwentwrong. Copylink Tintin-Asterix commented Nov23,2021 Ifthehdmi_*commandsdon'tworkwiththeKMSdriver,thenhowamIsupposedtoforceRGBfull(0-255)withthehdmi_pixel_encoding=2command?Ican'tfindawaytoforcefullRGBonmydisplay,italwaysdefaultstolimitedRGB.IfIgobacktotheFKMSdriver,thenitworks. Sorry,somethingwentwrong. pelwell added the KMSIssue IssuesrelatedtoKMS/DRMdrivers label Mar3,2022 Signupforfree tojointhisconversationonGitHub. Alreadyhaveanaccount? Signintocomment Assignees Nooneassigned Labels KMSIssue IssuesrelatedtoKMS/DRMdrivers Projects Noneyet Milestone Nomilestone Development Nobranchesorpullrequests 7participants Youcan’tperformthatactionatthistime. Yousignedinwithanothertaborwindow.Reloadtorefreshyoursession. Yousignedoutinanothertaborwindow.Reloadtorefreshyoursession.