Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Solved: 9.01 does not start
#11
(06-01-2024, 09:19 PM)Nutul Wrote:
(06-01-2024, 08:56 PM)Venerdi Wrote: 20240601 224321 worker: Ethernet: address 192.168.1.26
20240601 224321 worker: Ethernet: netmask 255.255.255.0

20240601 224321 worker: Wireless: address 192.168.1.192
20240601 224321 worker: Wireless: netmask 255.255.255.0

Not trying to investigate your issue, but as a rule of thumb, you better not have both wired and wireless network enabled...

HI,
I can tell you that I had this problem with old versions of moOde, if I remember correctly up until moOde 5.*
Then he never showed up again.
v.
Reply
#12
(06-02-2024, 05:42 AM)Iacov Wrote:
(06-01-2024, 03:39 PM)Venerdi Wrote:
(06-01-2024, 02:01 PM)Tim Curtis Wrote: This message "** To set a new password for your userid type 'passwd'." is ok. It's how you would change your password if desired.

@Venerdi the WebUI does not automatically appear on an attached display. Open a Browser, type http://moode, http://moode.local, or http://IP_ADDRESS_OF_PI.

Menu, Configure, Peripherals has the section the Local Display, Pi Touch etc.

@Tim
Thanks, I solved the problem, but now I have two more questions to ask.
1) Until now I turned on the Pi4 and I was immediately in moOode. Now, it always asks me for login and password. How can I avoid this?
2) The picture on the TV was perfect; now, at the beginning it's full of artifacts, then it goes back to normal, but it goes partly off screen. I don't see a part on the right and the whole top part. In moOde options there is GPIO pin mappings. It can be useful?

v.

what do you mea by "always asks for user/pw"? the console/command line or when you are actually in the moode GUI? when accessing moode via a browser... under system/peripherals... is local display active?

Hi,
I'll try to explain myself better. The Raspberry is connected with HDMI output to the TV. When I turn on the Raspberry, on the television screen I see all the boot. Towards the end of boot, the system asks for userid and password.
When I enter them, after 2 or 3 seconds, I access the moOde GUI.
This morning, doing other checks, I realized that if I don't enter the userid and psw, after exactly 20 seconds of waiting, he enters the moOde GUI.
Unfortunately, viewing problems remain on the TV screen, the image is off-centre and too large. If I connect remotely from my PC, the image is perfect. Up until version 8.39, I didn't have this problem.
v.
Reply
#13
(06-02-2024, 09:43 AM)Venerdi Wrote: Hi,
I'll try to explain myself better. The Raspberry is connected with HDMI output to the TV. When I turn on the Raspberry, on the television screen I see all the boot. Towards the end of boot, the system asks for userid and password.
When I enter them, after 2 or 3 seconds, I access the moOde GUI.
This morning, doing other checks, I realized that if I don't enter the userid and psw, after exactly 20 seconds of waiting, he enters the moOde GUI.
Unfortunately, viewing problems remain on the TV screen, the image is off-centre and too large. If I connect remotely from my PC, the image is perfect. Up until version 8.39, I didn't have this problem.
v.

this delayed GUI bootup is expected behavior, at least for me and since i'm a user (moode 8.x)
it always takes 10-30 seconds to start the GUI/chromium after the system has booted

have you tried editing the resolution in /boot/firmware/cmdline.txt? i don't know the syntax unfortunately, but that's where i would start looking if settings/peripherals in the GUI doesn't help
Reply
#14
(06-01-2024, 10:08 PM)Tim Curtis Wrote: I don't see anything suspicious in the log. 

Try turning the Display off/on, re-seat the HDMI cable and then reboot the Pi.

@Tim

I solved the display problem, I made a change, using intuition (or unconsciousness, since I don't understand anything about it).
The point is that I made this change by viewing old backups where everything seemed to work and studying the differences with that of 9.01, everything was resolved, but I absolutely don't know what the changes I made mean.
I changed these two lines from the config.txt file
dtoverlay=vc4-kms-v3d
max_framebuffers=2
with
#dtoverlay=vc4-kms-v3d
#max_framebuffers=2
I disabled them.
Now I wonder... what did I do? Why does everything work now? What do those two lines mean? Booting is also faster.
v.
Reply
#15
@Venerdi you can read the official config.txt documentation here: https://www.raspberrypi.com/documentatio...g_txt.html

That's not to say I fully understand what all those options do, but it's a start.
Reply
#16
(06-04-2024, 08:37 AM)radu- Wrote: @Venerdi you can read the official config.txt documentation here: https://www.raspberrypi.com/documentatio...g_txt.html

That's not to say I fully understand what all those options do, but it's a start.


Thanks, interesting.
I don't really understand the issue either, but I have confirmation that my problem was due to the vc4-kms-v3d driver.
If I understand correctly, it's not a moOde problem, but a kernel problem. Maybe because version 9 uses a new kernel...
And finally, maybe I can enable the command again
max_framebuffers=2
which concerns the number of monitors used, and I don't think it created any problems.
...you always learn something new...
v.
Reply


Forum Jump: