EasyOS Daedalus-series version 6.6.5

[BarryK]

I've upgraded from the (downgraded) 6.5.5 version to 6.6.4 and the system is back to normal.
Thank you.

It might be a good idea to delete the folder /mnt/wkg/releases/easy-6.6.3

But, 6.6.4 is not much different from 6.6.3, so I don't know why you had a problem with Xorg not starting.

If it happens again, choose to bootup to the commandline only, no X -- you can do this from the menu in the initrd.
Then, type "xwin" and see if X starts.
Reason for trying this, is I'm wondering if normal bootup requires more delay before trying to start X.

If X still doesn't start, you can try "xorgwizard"

[james2]

Update to 6.6.4 quick and easy. thx again perpetually, to all capable and involved. these 2 easy's are brilliant. Very taken too with F96 ce- 4. wish it was capable of a long life. Now i've got the bug off Barry, finally busy putting my electric bike on paper.

[libertas]

I've upgraded from the (downgraded) 6.5.5 version to 6.6.4 and the system is back to normal.
Thank you.

It might be a good idea to delete the folder /mnt/wkg/releases/easy-6.6.3

But, 6.6.4 is not much different from 6.6.3, so I don't know why you had a problem with Xorg not starting.

If it happens again, choose to bootup to the commandline only, no X -- you can do this from the menu in the initrd.
Then, type "xwin" and see if X starts.
Reason for trying this, is I'm wondering if normal bootup requires more delay before trying to start X.

If X still doesn't start, you can try "xorgwizard"

The problem I had with 6.6.3 was regarding the graphic driver not being detected.

Now, with 6.6.4, I can boot, but there are some problems.
It's maybe a question of the speed of the booting process.
My disk sometimes is rated with '5', other times as '6', so it's fast.

When I login, the boot process gets suspended showing a black screen with the login root prompt.
I cannot do anything, not even Ctrl+C.
Have to press the power button for twenty seconds to hard reboot the system.

The second time to boot, a file check is done and the boot process stops with the same black screen with the login prompt.
This time, the system is already logged in and I can type the command you suggested above 'xwin'.
And the graphical interface boots fine.

[don570]

On Youtube I came across this fascinating video showing a conversion of a regular bike
to an electric bike.

https://www.youtube.com/watch?v=rRknvFlk8Ks
__________________________________________________________

[james2]

@ don570 A Pro biker racer was caught with a motor inside the tube that run down to the pedals. Batteries were also in the tubes. Grinder with right angle drive is a good set up. Drill wont last long. I'm attempting a direct drive set up -no reliance on battery power for cruise. It will be fixed speed -no throttle, and hoping to addition 2 or 3 speed box with a clutch. I want it for breakdowns on long trips- getting to town for car parts etc. Long distances in Australia between towns. Yes a small trail motorbike may be easier. Power laws for bikes in Australia are ridculous for capable people. I've had an open motorbike licence for 44 years , built my own motorbikes, had bikes up to 1200 cc but limited to 250 watts by laws here for a pushbike.

[BarryK]

@ don570 A Pro biker racer was caught with a motor inside the tube that run down to the pedals. Batteries were also in the tubes. Grinder with right angle drive is a good set up. Drill wont last long. I'm attempting a direct drive set up -no reliance on battery power for cruise. It will be fixed speed -no throttle, and hoping to addition 2 or 3 speed box with a clutch. I want it for breakdowns on long trips- getting to town for car parts etc. Long distances in Australia between towns. Yes a small trail motorbike may be easier. Power laws for bikes in Australia are ridculous for capable people. I've had an open motorbike licence for 44 years , built my own motorbikes, had bikes up to 1200 cc but limited to 250 watts by laws here for a pushbike.

Except if you live in NSW, the maximum motor power for a pedal-bike is now 500W.
I think that happened early in 2024. All other Australian States are still on 250W.

The downside would be, if you want to go touring on your 500W bike, as soon as you leave NSW, you will be illegal.

Yeah, it was January 2024:
https://vamosbikes.com.au/blogs/vamos/n ... ebike-laws

[BarryK]

Have moved back to the 6.12.x kernel, with AVS audio drivers enabled:

https://bkhome.org/news/202503/kernel-6 ... abled.html

[BarryK]

New "NeoAPT" with simple replacement for the 'apt' package management utility:

https://bkhome.org/news/202503/neoapt-s ... ility.html

This will also work in Easy Scarthgap.

[Vverve]

I see no ploblem switching from Scarthgap to Daedalus-series , with latest kernel ,
if you choose to let one aside !
and get spare time for biking !!
Thank you for sharing it all BK

[BarryK]

6.6.5 released.

Blog announcement:

https://bkhome.org/news/202503/easyos-d ... eased.html

[tallboy]

Dell Latitude E6400 laptop updated from Daedalus 6.6.3 to 6.6.5 with a delta file.
Thank you, Barry!

tallboy

[BarryK]

Now on the 6.12.19 kernel with AVS enabled, I'm interested to know if anyone has audio fail after updating.

The AVS problem was reported here:

https://bkhome.org/news/202502/intel-so ... ature.html

...which also explains how you can disable AVS, by blacklisting the snd_soc_avs.ko kernel module.

[bugnaw333]

For my HP Elite Desktop, so far so good.

[Vverve]

@BarryK ,
updated to 6.6.5 here .
What's the ''keyring default'' option new thing when opening chrome ?
why it does not recognise input from xvkbd ?
all desktop seems frozen ,no window closing or moving enabled, but,
touch input does work to hit cancel on keyring prompt.
Searching about it , only found james2 in 6.3.92 .
to;Did you install Vivaldi via the "Download latest Vivaldi" menu entry ?
- i did install chrome from menu
to;did not moved icon ?
no
-but did edited exec argument for disk-cache of it.

kernel 6.12.19 is happy snappy here , all good

Thanks for all BK & all.

[libertas]

I've upgraded to 6.6.5.
The problems booting to 6.6.4 still remain, as described viewtopic.php?p=144622#p144622.
Had to hard reboot the laptop three times to be lucky enough to have a prompt boot that allowed me to type

Code: Select all

xinit

.
I've been not using EasyOS because of this problem, it's a no go for me, unfortunately.

@BarryK, you have previously mentioned something about the boot process being too quick, if you have some correction that I can test to see if it solves this problem, I can try it.

[BarryK]

@BarryK, you have previously mentioned something about the boot process being too quick, if you have some correction that I can test to see if it solves this problem, I can try it.

You can find out if Xorg is trying to use the GPU too soon, by booting to commandline only.

In the early boot menu, in the initrd, where it asks for password, you can choose to boot to commandline no X.

Then when at commandline, wait a few seconds then type "xwin" to start X.

Bootup like this several times, if X always starts, then you will know it is a problem with GPU trying to be used too early.

Report back here afterward.

[Federico]

Dear Barry,
please forgive me for having been absent for such a long time. It came to be, that I actually don't have much free time available.
Anyway, as you know, I prefer Daedalus over Scarthgap, not because Scarthgap isn't good enough, but because I think that Daedalus has superior features.
However, I'm still using Scarthgap and testing Daedalus, because Daedalus still has unfortunately some problems, the biggest one for me seems to be the incompatibility between QEmu and hardware drivers (I already described that when installing QEmu on Daedalus the audio disappears. I managed afterwards to restore the audio driver. I haven't tested if this is still happenig on more recent releases jet.).

First of all I would like to thank you because since the latest releases there haven't been any further compatibility issues between the system updates and the KDE apps: no more need to uninstall and reinstall any packages and all of the KDE apps keep working just fine. This is just beautiful (especially on Scarthgap)!

Anyway: I updated recently my Daedalus installation from v 6.6.3 to v 6.6.5 and now I'm experiencing the following after the update:

• The Network Manager Applet does not start at all, regardless of how many times I restart the system

• I have no audio, but the speaker icon is there and if I do right mouse click --> MSCW I get a message saying that no audio cards were detected on my system

What could this be related to? I remind you that I'm using the german locale.

I'm planning to switch totally to Daedalus from Scarthgap as soon as these small issues are solved and I can also use QEmu on it (I will also update the QEmu guides for Daedalus as soon as this becomes possible).

Thank you very much in advance!

Best regards.

[BarryK]

I'm planning to switch totally to Daedalus from Scarthgap as soon as these small issues are solved and I can also use QEmu on it (I will also update the QEmu guides for Daedalus as soon as this becomes possible).

I might have to deprecate the Scarthgap-series, due to lack of time.

Personally, I like the Scarthgap-series, as all packages are compiled by me; however, I understand that users like the large Devuan/Debian package repository.

Would you mind conducting an experiment:

Write the Daedalus 6.6.5 .img file to a usb drive and boot it, and choose English.

Then see what works with a pristine new English system.

That will help to narrow down whether the update or German locale are cause of problems.

[Federico]

I might have to deprecate the Scarthgap-series, due to lack of time.

Personally, I like the Scarthgap-series, as all packages are compiled by me; however, I understand that users like the large Devuan/Debian package repository.

Would you mind conducting an experiment:

Write the Daedalus 6.6.5 .img file to a usb drive and boot it, and choose English.

Then see what works with a pristine new English system.

That will help to narrow down whether the update or German locale are cause of problems.

Dear Barry,

I did exactly what you told me and this is the result after first boot and QuickSetup execution:

missing firmware message.jpg (92.19 KiB) Viewed 606 times

As usual, here is my hardware (as seen by Scarthgap 6.6.3):

Code: Select all

# inxi -Fxz
System:    Host: EASYPCSCART Kernel: 6.6.75 x86_64 (64 bit) Desktop: JWM 2.4.7 Distro: EasyOS Scarthgap64
Machine:   Device: laptop System: ASUSTeK product: ZenBook UX325EA_UX325EA v: 1.0
           Mobo: ASUSTeK model: UX325EA v: 1.0 UEFI: American Megatrends LLC. v: UX325EA.321 date: 02/27/2024
Battery    BAT0: charge: 16.7 Wh 75.0% condition: 22.2/42.2 Wh (53%) model: ASUSTeK UX325 status: Charging
CPU:       Quad core 11th Gen Intel Core i5-1135G7 (-HT-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 19360
           clock speeds: max: 2401 MHz 1: 600 MHz 2: 1200 MHz 3: 648 MHz 4: 1194 MHz 5: 400 MHz 6: 1200 MHz
           7: 500 MHz 8: 506 MHz
Graphics:  Card: Intel TigerLake-LP GT2 [Iris Xe Graphics] bus-ID: 00:02.0
           Display Server: X.org 1.21.1.14 drivers: modesetting (unloaded: fbdev,vesa)
           tty size: 186x35 Advanced Data: N/A for root
Audio:     Card Intel Tiger Lake-LP Smart Sound Audio Controller driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k6.6.75
Network:   Card: Intel Wi-Fi 6 AX201 driver: iwlwifi bus-ID: 00:14.3
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 123.0GB (Used Error!)
           ID-1: /dev/nvme0n1 model: N/A size: 512.1GB
           ID-2: USB /dev/sda model: SanDisk_3.2Gen1 size: 123.0GB
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 232 Uptime: 7 min Memory: 856.3/15712.6MB Init: SysVinit runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 5.2.211) inxi: 2.3.8 

[BarryK]

I did exactly what you told me and this is the result after first boot and QuickSetup execution:

OK, blacklist snd_soc_avs.ko kernel module.

The link posted here explains how:

viewtopic.php?p=145677#p145677

Then report back if that fixes your sound.

[Federico]

OK, blacklist snd_soc_avs.ko kernel module.

The link posted here explains how:

viewtopic.php?p=145677#p145677

Then report back if that fixes your sound.

So, first of all my apologies for not having read the previous posts. What happens is the following:

• If I install the Sid firmware intel-firmware-sound nothing changes: no audio devices are detected

• If I blacklist the snd_soc_avs module I get my audio back and audio cards are detected, also the network card gets working again (may this also be related to the module?)

However, my microphone still doesn't work / isn't recognized. And now I know that this must be related to this immature driver. I find really unbelivable that in 2025, with Linux getting more and more important over time, there are still some microchips not supported or not fully supported: how can this even be true?

Anyway, I can use the system as well as Scarthgap (obviously also on Scarthgap my mic is not detected). I will test QEmu on this latest release and report back what happens.
Thank you so much for everything.

[libertas]

@BarryK, you have previously mentioned something about the boot process being too quick, if you have some correction that I can test to see if it solves this problem, I can try it.

You can find out if Xorg is trying to use the GPU too soon, by booting to commandline only.

In the early boot menu, in the initrd, where it asks for password, you can choose to boot to commandline no X.

Then when at commandline, wait a few seconds then type "xwin" to start X.

Bootup like this several times, if X always starts, then you will know it is a problem with GPU trying to be used too early.

Report back here afterward.

Hi @BarryK,

Did two times as you suggested.
It made no difference. Still get the same black terminal as before where I cannot type anything.
Had to hard reset the laptop.
Any other trick to try?
Thank you very much.

[Caramel]

After upgrading to 6.6.3, cannot boot.

The boot processo stops até the
Waitng for kernel video drivers to load:

This is in a Dell laptop Latitude 5430.

What version was used before the upgrade?
If it was 6.5.5 or older, the problem could come from the modifications of /usr/bin/xwin between 6.5.5 and last versions

I can't tell for sure, but I think it was 6.5.5.

...

Try with the xwin before 6.5.6

xwin-easyos6.5.3.tar

(20 KiB) Downloaded 9 times

[libertas]

Thank you @Caramel.
The file you provided didn't solve the issue.
The misbehaviour was the same.

[powpu]

I am trying to boot Daedalus or Scarthgap 6.x versions to my Lenovo Ideapad 120S|11ap but I get a black screen after the boot manager loads the vmlinuz and initrd.

The machine does work with EasyOS Kirkstone 5.8.5 though.

Any idea of what could be the black screen or other options I could try in the boot loader to troubleshoot? I already tried the fix video option but got the same issue.

Thank you!

[Caramel]

Thank you @Caramel.
The file you provided didn't solve the issue.
The misbehaviour was the same.

Here is the same file xwin with addition of echo commands to help to follow the execution of the script.

xwin.gz

(16.34 KiB) Downloaded 2 times

Remove the fake .gz extension and make xwin executable.

When this script xwin is launched, it creates a text file testxwin in /mnt/wkg (the installation directory of EasyOS)

Could you try and share the content of this file (/mnt/wkg/testxwin) and, if it's possible, the content of /tmp/xerrs.log just after the test of xwin?

[Vverve]

Back to 6.6.4 ,as problem occured in 6.6.5 with intel loosing sound , no logs about it , but did appeared after using bluetooth speakers .
Can confirmed my weird ''keyring'' chrome observation is gone with 6.6.4 .