Read the statement by Michael Teeuw here.
Display Help
-
@Mykle1 ok i will try that and see if it makes a difference. Could it be in the main.css? i just dont under stand why it wants to stay in the upper 1/4 of the monitor
-
No, that belongs in the custom.css file. You should not be editing the main.css file unless you absolutely know what you are doing. That’s why I asked if you made any changes to the MM system files.
-
@Mykle1 ok i see what you are saying. no i’ve not edited it. looked at it but not made changes. just the custom
-
Someone will know how to solve your issue. I’m sure of it.
-
@Mykle1 hah i hope so, i’ve been going at this for about 3 hours now. not just the resolution issue but configuring modules and what not.
-
Be patient. Someone will help you when they find this topic. Take your time with the modules. It gets easier with time
-
@hnperkins said in Display Help:
disable_overscan=1
hdmi_group=1
hdmi_mode=16Just curious. Have you tried without this?
-
@Mykle1 yeah originally i just a clean boot and left everything stock from the install of noobs, that was just one of the things i had found to try via searching the forums and google
-
ok, cool. And the custom res was because Raspbian did not support your res? Was there a res close to what you wanted?
-
@Mykle1 no i just tried the custom because on first boot it was exactly how it is in the picture so i tried the custom and nothing changed. i just tried again with an empty custom and its still doing the same thing. almost tempted to start all over from fresh
-
Did you change the res in the raspi config at all?
-
@Mykle1 yeah i tried that before i edited the hdmi settings in the config.txt
-
Just out of curiosity have you checked the settings on the actual monitor itself?
I’ve had to adjust the settings on the monitor itself to achieve the desired resolution.
Sometimes cycling between Wide - Normal - Full can make all the difference.
You may need to reboot you pi after the changes (unless it detects automatically). -
@stacywebb i got it working finally. i ended up just reformatting the card and redoing everything from scratch. its now properly displaying but now having issues with a few modules lol
-
-
@Mykle1 getting the mmm-pir-sensor to work right which might not be a module issue at all and then awesome alexa which is an amazon issue, not matter what i try i am unable to get a refresh token, i can get the access token using different methods i have found here but not the refresh token
-
Ah, well, I don’t use either of those modules but plenty of people do. You can do a search on the forum and/or post a new question and I’m sure you’ll get some help.
Glad you solved the display issue
-
@Mykle1 yeahe im still digging around for the alexa issue and did post in a thread about the sensor. so far everything else is running great with no issues. i do have one question though. does it matter where in the string of module code you add certain modules. like would they cause the entire mirror to not load if there is a problem with a module in the middle of the them or does it not matter?
-
It can matter. If a troublesome module loads early it can cause problems with the modules that load later in the sequence
-
@Mykle1 ok thats what i was wonder, if it would be best to add new modules at the end of the pre loaded modules in the config or not
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login