EasyOS Dunfell-series 64-bit version 4.3.4

[bugnaw333]

encountered error in copy or move file going to NTFS.

[mistfire]

encountered error in copy or move file going to NTFS.

Make sure that the Windows was not hibernated. If hibernated just start the windows to resume and restart the computer then boot to puppy
If the Windows was not hibernated, the NTFS partition might unclean. You need to boot on Windows and run chkdsk

Code: Select all

chkdsk c: /f

[rcrsn51]

Few USB bluetooth adaptors will work in Linux ... In Easy linux my bluetooth device won't appear on list ... My advice is to check for compatibility when buying bluetooth devices.

Please identify the model that failed to work and where you obtained it.

Did you check for missing firmware?

[bugnaw333]

encountered error in copy or move file going to NTFS.

Make sure that the Windows was not hibernated. If hibernated just start the windows to resume and restart the computer then boot to puppy
If the Windows was not hibernated, the NTFS partition might unclean. You need to boot on Windows and run chkdsk

Code: Select all

chkdsk c: /f

It works! thanks.

[rudyt]

Does sda1 show up in /sys/block/sda/?

Code: Select all

# ls /sys/block/sda/
alignment_offset  discard_alignment  ext_range  power      sda2  slaves
bdi               diskseq            hidden     queue      sda3  stat
capability        events             holders    range      sda5  subsystem
dev               events_async       inflight   removable  sda6  uevent
device            events_poll_msecs  mq         ro         size

Nope

Also, run:

# probepart

Code: Select all

# probepart
/dev/sda2|ext4|83886080
/dev/sda3||83886080
/dev/sda5||79691776
/dev/sda6||4194304

sda3 is a FreeBSD UFS partition, which is an MBR primary partition. sda5 and sda6 are also UFS partitions created by FreeBSD, but are not primary partitions.

And:

# blkid /dev/sda1

blkid returns nothing for /dev/sda1

Note: I tweaked my partitions after my last post, so here is the new partition layout from fdisk. This time, /dev/sda1 was a 38GB NTFS partition, before I deleted it. It still shows up in EasyOS, and if I hover over the sda1 icon, the tooltip indeed says Filesystem: ntfs Size: 38.0GB.

Code: Select all

Device     Boot     Start       End  Sectors Size Id Type
/dev/sda2        80000008 163886087 83886080  40G 83 Linux
/dev/sda3  *    163886088 247772167 83886080  40G a5 FreeBSD

[BarryK]

Does sda1 show up in /sys/block/sda/?

Code: Select all

# ls /sys/block/sda/
alignment_offset  discard_alignment  ext_range  power      sda2  slaves
bdi               diskseq            hidden     queue      sda3  stat
capability        events             holders    range      sda5  subsystem
dev               events_async       inflight   removable  sda6  uevent
device            events_poll_msecs  mq         ro         size

Nope

OK, right-click on one of the partition icons, choose "Desktop drive icon manager", then tick the "redraw and realign exsting icons", then restart X.

[rudyt]

OK, right-click on one of the partition icons, choose "Desktop drive icon manager", then tick the "redraw and realign exsting icons", then restart X.

Thanks - that cleaned things up. Is it something I'll have to do every update, or just once on any new or existing installation? I guess I'll answer my own question at the next update

[BarryK]

encountered error in copy or move file going to NTFS.

Make sure that the Windows was not hibernated. If hibernated just start the windows to resume and restart the computer then boot to puppy
If the Windows was not hibernated, the NTFS partition might unclean. You need to boot on Windows and run chkdsk

Code: Select all

chkdsk c: /f

It works! thanks.

Also, have you turned off Fast Startup in Windows 10?
That can also cause f.s. corruption in a dual-boot situation.
See how to turn it off here:

https://easyos.org/install/prepare-your ... linux.html

[don570]

Note to Barry K:
Would you check your instructions for a frugal install of Easy?
I have an old Dell optiplex 900 series desktop that uses older method of booting.
I followed your instructions carefully and had a lot of trouble installing Easy to my hard drive.
https://easyos.org/install/easy-frugal- ... tion.html

I finally did the following to get it to install...

I copied 3 files ['vmlinuz', 'initrd' and 'easy.sfs'] in a folder (easyos)
Then I copied easy.sfs to higher level (Not sure if this is needed??? but I did it anyway.)
Then booted with this grub menu

Code: Select all

title EasyOS Dunfell (partition sda3 folder easyos)
  find --set-root-uuid () 054a04b8-0f00-11ed-aeb9-287fcfeb4376
  kernel /easyos/vmlinuz rw wkg_dir=easyos
  initrd /easyos/initrd

of course replacing your uuid with my own

This didn't allow the boot to desktop to succeed but it does expand easy.sfs into folders.
Next I booted again with standard grub menu
and it booted like it was a first time boot.

Code: Select all

title EasyOS Dunfell (partition sda3 folder easyos)
  find --set-root-uuid () 054a04b8-0f00-11ed-aeb9-287fcfeb4376
  kernel /easyos/vmlinuz rw wkg_uuid=054a04b8-0f00-11ed-aeb9-287fcfeb4376 wkg_dir=easyos
  initrd /easyos/initrd

I'm not sure what I did but it did work!!
____________________________________________

[don570]

Odd behaviour...

There is a brief sound crackle when I begin to play a sound in mhwaveedit
method:
mouse click or tap on spacebar
Maybe a strange latency effect...????

Other multimedia programs play the sound fine, including video editor shotcut imageapp.

...But I found that the crackle goes away if I change over to a different driver which is possible in preferences

screenshot-mhwaveEdit-driver.png (33.66 KiB) Viewed 671 times

[charlie6]

Hi don570,
Hi Barry

Just a warning to Linux users .......

Few USB bluetooth adaptors will work in Linux,
and they don't work well in Windows either due to overlap in frequency spectrum
they both use.
Changing frequency spectrum is recommended

Bluetooth only does its work on a 2.4GHz frequency, whereas many WiFI networks these days will run on both 2.4GHz and 5GHz frequencies. You’ll find many of today’s newest wireless devices taking advantage of WiFi’s 5GHz frequency, which isn’t nearly as congested as the 2.4GHz frequency and helps to reduce any potential interference between WiFi and Bluetooth networks.

In Easy linux my bluetooth device won't appear on list.
My advice is to check for compatibility when buying bluetooth devices._
_____________________________________

Here trying to get a «Bluetooth v4.1 audio Headset» which works OOTB on windows 10 together with a BT v4.0 USB dongle from Cambridge Silicon Radio
CSR8510 A10 Bluetooth controller

Code: Select all

root# lsusb
...
Bus 003 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
...

Got a try on EasyOS 4.5.5 (*), and found that there is a /lib/udev/rules.d/97-bluetooth-hid2hci.rules, but which cannot be used as the file /lib/hid2hci is missing (whereas it is present in another Puppy distro - Fossapup64-9.5 - for instance).
Mention of that udev rule can be read in the post: https://troglobit.com/2017/01/03/trust- ... -in-linux/
Moreover, on Fossapup64-9.5 the following code inside /lib/udev/rules.d/97-bluetooth-hid2hci.rules

Code: Select all

...
RUN+="hid2hci --method=csr --devpath=%p"
...

returns the comment:

Code: Select all

root# ./hid2hci --mode=hci --method=csr2 --devpath=%p
error: could not find '%p'
root#

My question is:
1st / any idea where can be found /lib/hid2hci ;
and 2nd/ which --devpath to set instead of «%p» ? (I presume that devpath would appear in /dev once the usb dongle is plugged in?

Digging and googling the web a bit more, this post entitled «Fixing chinese Bluetooth dongle for Linux - February 20, 2020»
https://unam.re/blog/fixing-chinese-blu ... ngle-linux
tells how the «btusb.c» kernel module to be edited/modified and recompiled in order to fix the error (**)

root# sudo hcitool -i hci1 lescan
Invalid device: No such device
root#

assuming the dongle is configured hci1

I am totally ignorant about how Bluetooth can work and pair, but I am trying to understand how it can work. So I cannot give techincal explanation. I only make analogy with usb drawing tablet which also uses udev rules.

(*) because my thought was it could also work with a BT dongle, as on EasyOS I could get file exchange working using the Bluetooth BluePup gui (thanks Barry!) and the builtin BT interface on this Acer Aspire VA70 i5 Laptop.
(**) here got a try to recompile btusb.c on FossaPup64-9.5 without success as yet asI could not find the requested linux-headers-k-5.4.53 (I've only found the «k5.4.0-53» believing it could work, but nope!.. - The ones inside huge-5.4.53-fossapup64.tar.bz2 do no help )

(I apologize mentionning some results on another distro outside this EasyOS thread).
Thanks for any further development, answer or help.

Best regards, Charlie

[BarryK]

Charlie,
Thanks for reporting that.

In Easy 5.1.1, the 'hid2hci' utility is missing.
I found that this is part of the 'bluez5' package, but in OpenEmbedded bluez5 is compiled without the "--enable-hid2hci" option.

I won't be fixing bluez5 in the 4.* versions, but I am right now doing a recompile in OE for the 5.x Kirkstone series, so will put in that configure option.

Actually, you have reported this at the right time.
All of the packages in Easy Kirkstone-series (and the previous Dunfell-series) are compiled from source, using OpenEmbedded.
I have updated the package versions and started a compile this morning, just after midnight. Right now it is just after 8am.
The complete build takes about 4 days, depending on what computer I use.

bluez5 has already compiled, but as it is a dep of a lot of packages, I decided to start the compile again, from scratch. I fixed the bluez5 recipe to enable hid2hci, and have set it off again ...now have to wait 4 days.