[SOLVED] Waveshare 5" DSI - Touch does not work -

[Tim Curtis]

Configure the WiFi static address, plug in an ethernet cable, reboot and then post the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

[TheOldPresbyope]

I can add that as an option. Added to the TODO list.

....
Now another small problem arises, it is not possible to configure a wifi connection in STATIC mode, but only in DHCP. Do you by any chance have any ideas on how to resolve this?

Huh? Static mode works for me.  Just tried it again on a fresh 9.0 install to be sure.

Are you sure you entered the correct information needed----static address, network mask, gaterway address, at least a primary DNS address if not both primary and secondary?


Regards,
Kent

Yes, I entered all the correct parameters, the same ones I used without problems with version 8.3.9. The connection is visible with a network scanner, but it is impossible to access the web server even via an SSH connection. It's not just me who has this problem, but also some users in my FB group who have reported the exact same bug.   The only way to access via wifi is to put the connection in DHCP

Without a lot more details about your setup it’s impossible to say more than it works for me.

[TheOldPresbyope]

Actually, after my first cup of coffee for the day I do have a thought.

Recall I mentioned setting correct interface values including network mask?

The default network mask value offered by the moOdeUI is 255.255.255.255

This value is incorrect for almost any networking environment. It renders the player unreachable via IP even though it is properly connected to the router.

For my home network the correct network mask is 255.255.255.0 but YMMV. For example, it would have been wrong in the lab I used to work in.

As a test, just now I configured two players with static WiFi addresses and correct network mask and one with static WiFi address and the default network mask. My router confirms that all three are connected, but only the first two are reachable from other hosts on the LAN.


Regards,
Kent

[ECELO]

Actually, after my first cup of coffee for the day I do have a thought.

Recall I mentioned setting correct interface values including network mask?

The default network mask value offered by the moOdeUI is 255.255.255.255

This value is incorrect for almost any networking environment. It renders the player unreachable via IP even though it is properly connected to the router.

For my home network the correct network mask is 255.255.255.0 but YMMV. For example, it would have been wrong in the lab I used to work in.

As a test, just now I configured two players with static WiFi addresses and correct network mask and one with static WiFi address and the default network mask. My router confirms that all three are connected, but only the first two are reachable from other hosts on the LAN.


Regards,
Kent

I confirm. In WIFI connection I reached the STATIC condition by changing the subnet mask from 255.255.255.255 to 255.255.255.0 Now the webserver is perfectly reachable without problems from the browser.

[Tim Curtis]

Right its prolly the netmask.
In moode 9 all possible netmasks are listed in the dropdown starting with 255.255.255.255.

My thinking around static addresses is that specifying one is pretty technical to begin with and so things like the netmask, gateway, and DNS would be known and set correctly but maybe 255.255.255.0 should be listed as 255.255.255.0 (Default) in the dropdown and be the displayed default ??

[ECELO]

Configure the WiFi static address, plug in an ethernet cable, reboot and then post the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

I changed the subnet mask from 255.255.255.255 to 255.255.255.0 as suggested by TheOldPresbyope and everything was back to normal.

[TheOldPresbyope]

Right its prolly the netmask.
In moode 9 all possible netmasks are listed in the dropdown starting with 255.255.255.255.

My thinking around static addresses is that specifying one is pretty technical to begin with and so things like the netmask, gateway, and DNS would be known and set correctly but maybe 255.255.255.0 should be listed as 255.255.255.0 (Default) in the dropdown and be the displayed default ??

Either way there probably should be some sort of warning or brief explanation that the user has to  confirm the correctness of whatever value they use.

I suspect that most home routers allocate 256 addresses to the LAN subnet but certainly mine can be configured differently.

Regards,
Kent

[ECELO]

Configure the WiFi static address, plug in an ethernet cable, reboot and then post the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

I changed the subnet mask from 255.255.255.255 to 255.255.255.0 as suggested by TheOldPresbyope and everything was back to normal.

Unfortunately it didn't solve the problem because despite having entered the new subnet mask and the correct DNS, upon restarting the system, although STATIC is displayed in the GUI, in moodeutl -l it confirms that it is still a DHCP type connection

20240522 181628 worker: Wireless: method  dhcp
20240522 181628 worker: Wireless: address 192.168.1.203
20240522 181628 worker: Wireless: netmask 255.255.255.0
20240522 181628 worker: Wireless: gateway 192.168.1.1
20240522 181628 worker: Wireless: pri DNS none found
20240522 181628 worker: Wireless: domain  none found

[TheOldPresbyope]

Configure the WiFi static address, plug in an ethernet cable, reboot and then post the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

I changed the subnet mask from 255.255.255.255 to 255.255.255.0 as suggested by TheOldPresbyope and everything was back to normal.

Unfortunately it didn't solve the problem because despite having entered the new subnet mask and the correct DNS, upon restarting the system, although STATIC is displayed in the GUI, in moodeutl -l it confirms that it is still a DHCP type connection

20240522 181628 worker: Wireless: method  dhcp
20240522 181628 worker: Wireless: address 192.168.1.203
20240522 181628 worker: Wireless: netmask 255.255.255.0
20240522 181628 worker: Wireless: gateway 192.168.1.1
20240522 181628 worker: Wireless: pri DNS none found
20240522 181628 worker: Wireless: domain  none found

I think what you've found is that there is an error in the moodeutl script where it reports the Wireless: method rather than in the actual networking configuration code.

I just tried rebooting one of the players which I'd configured to have a static IP address. After the reboot, the player still has the static address I assigned it but moodetl -l reports "Wireless: method dhcp" just as you show. 

To confirm, I dug down to the system-connections directory for the NetworkManager in my player and see, for my WiFi connection, the stanza

Code:

...
[ipv4]
method=manual
address1=10.0.0.252/24
gateway=10.0.0.1
dns=1.1.1.1,1.0.0.1
...

"method=manual" means static on our context and the address is the one I assigned.


@Tim Curtis  another item for your TODO list  

Regards,
Kent

[Tim Curtis]

Added.