You are not logged in.
I am using lightdm with Mate or Cinnamon, no issues, uses elogind.
I am using openrc since ASCII.
Don't break your Devuan ...
I guess you overlooked that per Default the XFCE desktop is ticked.
rolfie
From man wipefs:
wipefs allows to erase filesystem or raid signatures (magic strings) from the device to make the filesystem invisible for libblkid. wipefs does not erase the whole filesystem or any other data from the device. When used without options -a or -o, it lists all visible filesystems and offsets of their signatures.
I am not 100% sure what you try to tell us. You say are aware of the bit that only on "Apply" the actual changes are written to the SD cards. Ok, another bit: gparted is a tool that works on partition information and everything around that, not on file systems directly. Its basically a graphical interface for fdisk and mkfs.
Well, after the "Apply" has finished gparted re-reads the partitioning information for all the devices that are available. If then the same structures are presented for the SD card, then obviously the write operation wasn't successful. I would claim that gparted works quite well. And I would conclude that the involved HW isn't working correctly. If gparted displays that the SD card now is empty, then that is the information that came back from the HW.
What exactly means:
The bit I have a problem with is that gparted tells me it had success in deleting the partition, when it clearly didnt, if I unplug and then plug it in again, I can read the files straight away, no windows involved.
This would be some sort of miracle. Maybe SD card and reader are not compatible, or some sort of buffer is involved, or the SD cards are simply crap.
You seem to have tried dd also, also with no result.
If you sum up all these bits and bytes, what do you think about cards and reader?
rolfie
Some thoughts to the issues:
When plugging in the SD card reader and the card itself: inspect dmesg for hints if the device is write protected.
To gparted: I am using gparted for many years and never had it fail. I started of with gparted life versions, still use them every now and then.
There may be a trap for the unexperienced user: you can prepare a lot of operations, but these are not executed on the real HW before you don't tick the apply button. Are you aware of this?
In addition I suggest to tick the Device Information box in the View menu. Gives you confirmation that you are working on the right device.
If that does not work the card may be defective.
rolfie
Works again for me.
rolfie
Same with FF 91.5.0 ESR since today.
rolfie
Can't this simply be the su/su - issue with paths?
@OP: have you read the release notes of Beowulf/Chimaera and the changed path setting?
rolfie
Well, I want to scan a lot of private documents. My flatbed LIDE220 is fine for a few pages, for more stuff it takes too much time to feed the paper and to turn it if its double sided.
So I am searching for a Linux supported document scanner, holding 20-50 pages, duplex unit, preferred USB3 interface, maybe with ultrasound sensor for a double pull detection.
Suggestions welcome,
rolfie
My experience is that a reboot past the last upgrade step clears away one or the other hickup with configurations that get lost during such a process.
rolfie
I own two old USB2 memory sticks with 512 MByte, formatted as FAT16. They work fine with Cinnamon/Mate Desktop being automounted etc.
Your stick has an issue with the entries in the partition table:
1.) sdc: detected capacity change from 0 to 521928192
2.) sdc: p1 size 1019340 extends beyond EOD, enabling native capacity
3.) sdc: p1 size 1019340 extends beyond EOD, truncated
Unmount and run a file system check on that device.
rolfie
For private use you may set up a file server with Linux, holding the data on any file system you like. I run mine with ext4. Some specialists claim that zfs may be better.
I have Samba installed to be able to serve Windows PCs via network, the same files are available to my Linux workstations via nfs.
I have started my file server nearly 20 years ago based on Sarge, still working on Windows. 10 years ago I switched my private family network to Linux workstations, still keeping the ability to use WinXP, Win7 on older PCs and in VMs. The file server in the background still does the job, though I have migrated it to Chimaera. The Samba setup is ages old, just no more SMB1 supported.
I don't care about defrag, thats a Windows topic for me nowadays. I see no need to care ...
HTH, rolfie
Please check the Release Notes (https://files.devuan.org/devuan_chimaer … _notes.txt) for the path/su issue.
How did you do your install? Sounds a bit like Expert Mode and leaving out one or the other step ...
rolfie
Running an up to date Chimaera with Cinnamon installed from netinstall a year ago, no issues seen.
I am using Crux/Adwaita/Adwaita/Adwaita/Cinnamon in the Themes settings.
rolfie
Not any file system on any USB stick will found on /dev/sd(X), it always will be on /dev/sd(X)1 or higher.
Use any stick with FAT32, you have to mount it with /dev/sd(X)1.
rolfie
# mount /dev/sdc /mnt/ mount: /mnt: unknown filesystem type 'exfat'.
This is obvious. You can't have an exfat file system at /dev/sdc, at the most you'll find a partition table there.
Try to use:
# mount /dev/sdc1 /mnt/rolfie
On the top of the forum page is a link to Devuan.org where you can find the official documentation and several howtos.
Myself I have upgraded my wifes PC and my file server from Beowulf to Chimaera without any issues. My PC is using parallel installation of Arch/Beowulf/Chimaera. I have moved my activities from Beowulf to Chimaera early summer this year before Chimaera even got stable.
General advice: disable any foreign repositories during the upgrade.
rolfie
I think your last post more concerns this topic: https://dev1galaxy.org/viewtopic.php?id=4701
rolfie
Thank you, drilling down into modules and devices showed no /dev/mapper nor cryptsetup traces.
Rebooted from the netinstall in rescue mode: installed cryptsetup-bin and cryptsetup-initramfs, now it works. Both packages need to be added to the installer.
rolfie
Installed from the Daedalus netinstall preview dated Nov. 29th in VBox 6.1.28. Efi mode, encrypted LVM,, just basic system install, no GUI. Install went fine, the first reboot ends in an endless loop of messages "Volume group vgsys not found. Cannot process volume group vgsys." Does not ask for the PW, eventually ends in the initramfs shell. When I try to open the encrypted volume I get "cryptsetup not found".
An upgraded VM based on Chimaera works fine.
Whats wrong?
rolfie
Wouldn't be that optimistic. Devuan uses a different mode than Debian for efi boot, and that works fine on real HW. Just causes issues in VBox. Haven't got anything that the admins work on this topic.
The workaround described in my lengthy post works, just managed to install from the Daedalus preview.
rolfie
Have a look at https://dev1galaxy.org/viewtopic.php?pid=31475#p31475 and what follows ....
rolfie
Chimaera: On my lightdm login screen I have a small icon in the middle of the bottom that opens a screen keyboard that can be operated with the mouse. Maybe that helps.
rolfie