EasyOS Dunfell-series version 2.8 for Raspberry Pi4

[BarryK]

Works great!

This is a 64-bit distribution, for the Pi4, though should work on the Pi3. Blog announcement and download links:

https://bkhome.org/news/202106/easyos-d ... y-pi4.html

Feedback welcome!

[bigpup]

First time startup on a Raspberry Pi 400

Only problem was getting the WIFI setup.

First I got this error message, but the WIFI firmware and driver is in EasyOS 2.8 for my Pi 400.
The hardware uses this driver and firmware.
I did nothing about this error. Just continued to try and connect using WIFI.
Did do a reboot before trying to connect.
No error on the reboot.
.

Screenshot.jpg (26.83 KiB) Viewed 789 times

.
In the Internet Connection Wizard->Connect to Internet By:
Had to use the Network Manger to make a working connection.
It had no problems finding the hardware of finding a WIFI signal.

Selecting wired or wireless LAN->SNS or Frisbee
They would see the hardware and provide Wlan0 option.
But would not find any WIFI signal.

I tried with firewall turned on and turned off.
Had no affect on SNS or Frisbee.

rerwin is doing some work on all these different connection wizards.
viewtopic.php?f=89&t=445

[bigpup]

JWMDesk Manager

The window opens not wide enough.
See image of example:
.

Screenshot(2).jpg (35.53 KiB) Viewed 780 times

.
Other tabs show the issue, but some not so bad.
.
Update:
Fixed this by making a modification to the jwmdesk file located in /usr/local/jwmdesk/
Changed line 408 in jwmdesk file.

Code: Select all

[ ! "$WINDOW_WIDTH" ] && WINDOW_WIDTH="500"

To this:

Code: Select all

[ ! "$WINDOW_WIDTH" ] && WINDOW_WIDTH="600"

Now it opens with wide enough window.

Screenshot(3).jpg (38 KiB) Viewed 655 times

[BarryK]

Selecting wired or wireless LAN->SNS or Frisbee
They would see the hardware and provide Wlan0 option.
But would not find any WIFI signal.

I tried with firewall turned on and turned off.
Had no affect on SNS or Frisbee.

I am planning to remove SNS, Frisbee, etc., and only have Network Manager.

Network Manager works well, and switching to the others can cause problems. So, simple solution, remove them.

[bigpup]

Raspberry Pi computers do not have a internal hardware RTC clock.

The only way to set the correct time is by using menu->Desktop->Qsync Set Time from Internet
Uses a time server to provide the correct time.

To keep costs low, the Raspberry Pi does not include a Real Time Clock module.
Instead, users are expected to have it always connected to WiFi or Ethernet and keep time by checking the network.

[BarryK]

Raspberry Pi computers do not have a internal hardware RTC clock.

The only way to set the correct time is by using menu->Desktop->Qsync Set Time from Internet
Uses a time server to provide the correct time.

To keep costs low, the Raspberry Pi does not include a Real Time Clock module.
Instead, users are expected to have it always connected to WiFi or Ethernet and keep time by checking the network.

With 2.8, this now defaults to "on". First bootup, QuickSetup has a checkbox for sync to Internet NTP server, which now defaults to ticked.

[bigpup]

With no hardware clock in the Pi.
Does menu->Desktop->Set Hardware Clock Type, do anything or is needed?

[BarryK]

With no hardware clock in the Pi.
Does menu->Desktop->Set Hardware Clock Type, do anything or is needed?

Yes, you need to set whether your hardware clock is local time or UTC.

That is also in the QuickSetup window. There is a checkbox labelled "Hardware clock set to UTC", with a help button beside it to explain what that means. It defaults to local time, checkbox unticked, so you would need to tick it for UTC.

It would be expected that first time someone boots EasyOS, when the QuickSetup window appears, they would look through all the settings and make sure everything is set as they require.

[bigpup]

This being a specific version of EasyOS for the Raspberry Pi computers.

The info in the Quicksetup->Hardware Clock set to UTC->help info some is bad info for the Pi computer.
.

Screenshot(2).jpg (73.79 KiB) Viewed 661 times

.
First paragraph does not apply to the Pi computer.
It needs to say that the Pi does not have a hardware clock.
.
The last paragraph is talking about other operating systems that are not going to be used.
So why have anything about them?.

[bigpup]

Running on a Pi 400
Samsung average ability computer monitor.

The Screen Brightness and Tint Control
(icon on right side of tray)
Click on tray icon and program setting window opens.
Nothing seems to work in this program.
Nothing I do with it has any affect.

This monitor does have a lot of internal settings, but I do not think they would keep this from working.

[bigpup]

See update to this post:
viewtopic.php?p=27278#p27278

[BarryK]

bigpup reported earlier that "update" is broken. I did post a fixed script, but it still had a bug.

The attached one should be ok for when you update to 2.8.1. It has a false ".gz", remove that and place at /usr/local/easy_version, set executable flags.

[BarryK]

See update to this post:
viewtopic.php?p=27278#p27278

JWMDesk is in the PupControl PET, created by radky. It is version 3.2.

I have been more conservative, bumped the width from 500 to 520, and updated the PET, it is now 3.2.1.

Note, I think that the PupControl used in EasyOS is slightly different from the one in Puppy. My memory is not too certain on this, but i think that radky did do some EasyOS-specific tweaks to the PET. So I will have to update the version separately from whatever version is currently used in Puppy.

Searched this forum, seems no updates to PupControl. Searched old forum, looks like PupControl reached 3.3, July 2019:

https://oldforum.puppylinux.com/viewtop ... &start=105

[bigpup]

checking something.