You are not logged in.
fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
Check your kernel to see if it indeed has that support enabled and modprobe the module before starting the install again.
zeus@9600k:~/Downloads$ grep -i toshiba /boot/config-6.12.8-amd64
CONFIG_YENTA_TOSHIBA=y
CONFIG_PATA_TOSHIBA=m
CONFIG_MMC_TOSHIBA_PCI=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_TOSHIBA_BT_RFKILL=m
CONFIG_TOSHIBA_HAPS=m
CONFIG_TOSHIBA_WMI=mThe CONFIG_ACPI_TOSHIBA=m seems the likely candidate needed. Check your running kernel config for it being enabled there.
Hooray for progress! Linux (without the GNU, because we shouldn't scare away newbies) is finally letting go of stability and embracing on-demand updates
Yes they truly have gone downhill in that regards, though it is not the first time they have dropped an arch. With mostly the same reaction seen here every time as it happens. Same with the systemd garbage they foist onto their users forgetting the one tool for every action keep it simple *nix philosophy. While it expands ever more into every god damn part of the system with each release. So the Microsoft plants in Linux can slowly gain more control over ever f'n thing done on those systems. They don't even hide the agenda anymore and Debian still goes along with it. Here in a couple of days it will be four months (according to the Ubuntu changelog for the fix) since they ship a broken KDE that will not connect to a samba share at all. Despite the fix being in Ubuntu for all of those months and all it is, is a simple re-compile of the Ubuntu packages to fix it as they are binary compatible now that will install and work on a Debian based system. Having seen it in the past I have no doubt that they will ship those packages in that same broken state with Trixie when it goes out the door..
https://www.devuan.org/os/documentation … o-daedalus
Is the link to it, the procedure is fairly simple.
i was not clear enough. i loop-mounted the iso file not the USB drive.
in an error about not being able to mount /cdrom.
my next idea is to disassemble the machine, extract the nvme drive,
Ah I was wondering if you had done the copy the iso to the install drive many do and you did not. That is same error I got when trying to use the installer. Save yourself the wasted time and effort use an installer that works a Debian one. Then convert the install to Devuan using the instructions they give for doing it that work perfectly fine when starting with that as a base to get it on the box. There are very few changes made from a stock Debian to this operating system. The main one being removing the systemd infestation from it and installing sysvinit.
i loop-mounted the iso and all the EFI bits appear to be there, so i must be doing something wrong.
to get around this problem, i copied the netinstall iso to a ventoy USB drive and booted netinstall
from there.just curious if anyone knows what is going on with UEFI boot? is it a 7700X thing?
If you loop mounted the iso from on the USB drive then you did it wrong when making the install USB with dd. There is nothing wrong with your booting UEFI as if there was the ventoy drive would have had the same problem booting when using it as UEFI selected from your boot menu.
So, in which of the Base Files should I be looking to see the difference? There was no difference in os-release.
You would download the both and compare the files. All that matters is the system thought there was a change and displayed the normal message for that change. You see it every time the . release updates go from the 12.7 to 12.8 for instance you get to see it. Now I scroll back the old version last update was in July of 2023 definitely a few version . changes in that period of time thus the reason for the message being displayed.
You have solved the mystery, it got updated at just past 3:06PM Dec. 27 2024 by synaptic when it installed the new base-files:i386 package.
What would have caused the other 2 Notes to no longer be displayed?
It is only or should only be displayed when the base-files package is updated and the information in the os-release file changes.
root@9600k:~# cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 6 (excalibur/ceres)"
NAME="Devuan GNU/Linux"
VERSION_ID="6"
VERSION="6 (excalibur/ceres)"
VERSION_CODENAME="excalibur ceres"
ID=devuan
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"
root@9600k:~# apt-file search /etc/os-release
base-files: /etc/os-release
snip....Check in your /var/log/apt/history.log to see if it (base-files) has been updated recently to tell if it should have displayed.
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Check to make sure you have the libgtk3-nocsd0 package installed that is the package that contains that file.
zeus@9600k:~$ apt-file search libgtk3-nocsd.so.0
libgtk3-nocsd0: /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0If installed and it does not start then no clue on solution to garbage programming.
but on ubuntu have received fax (via webservice), it was bit strange noises
obviously never used a phone modem to connect to the internet. Those strange noises are the handshake as it is called when the machines negotiate the connection. A common sound heard in the old days before ethernet became the connection of choice and you had no choice but to use the telephone modem to connect. And got to connect at a whopping speed of ~4k/s for the fastest of them modems. See if one of them services have a test number to send to and of course get them to send another to confirm you can receive. If receiving then you can send.
PC-FAX (old version)
does install and need no "systemctl"
but could be that in future version this solution no longer works since cups is giving some message that in future CUPS some feature may be disabled or similar.
It is definitely possible they disable the feature you rely on, it would not be the first time they have done things like that. So looking at that, did it work with installing the old package?
/opt/epson/epson-pc-fax2/
I highly doubt that fax directory is in the path so will never be found.
zeus@9600k:~$ echo $PATH
/sbin:/home/zeus/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
root@9600k:~# echo $PATH
/root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binTry.
ln -s /opt/epson/epson-pc-fax2 /usr/local/bin/epson-pc-fax2To link it to a directory that should be in the path. I think I have the link command correct, I have to look it up most times, if not try it the other way round.
Edit: can you link to the download page you got the file from so I can look at it, I do not seem to be able to find it.
I used to love lilo very much
Indeed me too but we needed to yet again chase the new shinny, a wide spread disease in Linux, get something working great then they have to blow it all up and start with the latest fad yet again. I do not know how many times I have seen it happen in these few decades of using it, to numerous to list really.
Damn looks like you either need to edit the package or give up on the fax in it. I would think there is not a lot times you need a fax machine.
Edit: Another option is just extract the package and manually move the files to where they would normally be installed. I would think the systemctl is just restarting the CUPS daemon for it to find the new .ppd file(s) is should probably be installing, plus maybe a binary for the fax function.
Does a Debian arm64 installer iso boot syslinux?
From playing around with my Pi4 they use uboot I believe it is as they have all the files required to boot in the /boot directory with the device tree overlays (.dtb files) that are used. They do not boot the same way as other machines. Now I mount the drive for it they are in the / of the drive.
root@9600k:~# mount /dev/sdb1 /tmp/root
root@9600k:~# ll /tmp/root/
total 128528
-rwxrwxr-x 1 root root 26538 Sep 10 05:54 bcm2711-rpi-4-b.dtb
-rwxrwxr-x 1 root root 27111 Sep 10 05:54 bcm2711-rpi-cm4-io.dtb
-rwxrwxr-x 1 root root 14723 Sep 10 05:54 bcm2837-rpi-3-a-plus.dtb
-rwxrwxr-x 1 root root 14995 Sep 10 05:54 bcm2837-rpi-3-b.dtb
-rwxrwxr-x 1 root root 15351 Sep 10 05:54 bcm2837-rpi-3-b-plus.dtb
-rwxrwxr-x 1 root root 14369 Sep 10 05:54 bcm2837-rpi-cm3-io3.dtb
-rwxrwxr-x 1 root root 52456 Jul 1 22:58 bootcode.bin
-rwxrwxr-x 1 root root 99 Sep 10 05:54 cmdline.txt
-rwxrwxr-x 1 root root 289 Sep 10 05:54 config.txt
-rwxrwxr-x 1 root root 3187 Jul 1 22:58 fixup4cd.dat
-rwxrwxr-x 1 root root 5448 Jul 1 22:58 fixup4.dat
-rwxrwxr-x 1 root root 8452 Jul 1 22:58 fixup4db.dat
-rwxrwxr-x 1 root root 8454 Jul 1 22:58 fixup4x.dat
-rwxrwxr-x 1 root root 3187 Jul 1 22:58 fixup_cd.dat
-rwxrwxr-x 1 root root 7314 Jul 1 22:58 fixup.dat
-rwxrwxr-x 1 root root 10298 Jul 1 22:58 fixup_db.dat
-rwxrwxr-x 1 root root 10298 Jul 1 22:58 fixup_x.dat
-rwxrwxr-x 1 root root 27165545 Aug 11 04:17 initrd.img-5.10.0-31-arm64
-rwxrwxr-x 1 root root 27166803 Sep 10 05:54 initrd.img-5.10.0-32-arm64
-rwxrwxr-x 1 root root 793116 Jul 1 22:58 start4cd.elf
-rwxrwxr-x 1 root root 3722504 Jul 1 22:58 start4db.elf
-rwxrwxr-x 1 root root 2228800 Jul 1 22:58 start4.elf
-rwxrwxr-x 1 root root 2981192 Jul 1 22:58 start4x.elf
-rwxrwxr-x 1 root root 793116 Jul 1 22:58 start_cd.elf
-rwxrwxr-x 1 root root 4794472 Jul 1 22:58 start_db.elf
-rwxrwxr-x 1 root root 2952960 Jul 1 22:58 start.elf
-rwxrwxr-x 1 root root 3704808 Jul 1 22:58 start_x.elf
-rwxrwxr-x 1 root root 1076 Oct 1 23:58 sysconf.txt
-rwxrwxr-x 1 root root 27469760 Aug 11 04:17 vmlinuz-5.10.0-31-arm64
-rwxrwxr-x 1 root root 27469760 Sep 10 05:54 vmlinuz-5.10.0-32-arm64Edit: Now I remember and clue in that was the firmware partition that is mounted as /boot/firmware.
root@9600k:~# mount /dev/sdb2 /tmp/root
root@9600k:~# cat /tmp/root/etc/fstab
# The root file system has fs_passno=1 as per fstab(5) for automatic fsck.
LABEL=RASPIROOT / ext4 rw 0 1
# All other file systems have fs_passno=2 as per fstab(5) for automatic fsck.
LABEL=RASPIFIRM /boot/firmware vfat rw 0 2
root@9600k:~# blkid |grep RASPI |sort -n
/dev/sdb1: SEC_TYPE="msdos" LABEL_FATBOOT="RASPIFIRM" LABEL="RASPIFIRM" UUID="0570-6A9B" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="a2760bd5-f1e2-4765-a0ec-ca7ed959c066"
/dev/sdb2: LABEL="RASPIROOT" UUID="b00e7b01-391c-4729-85b4-7aa97205664a" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="08aa064e-f0a4-492e-a096-45b797c76e22"BIOS to specify what type of time was being set in the BIOS when what he was saying was to use the UTC time for my Region and Location to set the time in the BIOS. big_smile
Yes as has been pointed out you set the time in the BIOS/UEFI to the offset from UTC for your time zone. For instance in mine it is set to 4 hours less than UTC as my offset is -4 this makes everything work properly when the systems use UTC as most all *nix systems use it, like Linux, the BSDs & MacOS. Only Windows usually defaults to using local time as the multitude of postings of "why does my clock change when dual booting" can attest to.
Give the replacement package for it a try, it does not get installed by default. Either that or download the package extract it then make the edit to not call systemctl after that using the dpkg-repack to get new package to install.
zeus@9600k:~$ apt info systemctl
Package: systemctl
Version: 1.4.4181-1.1
Priority: optional
Section: admin
Source: docker-systemctl-replacement
Maintainer: Dmitry Smirnov <onlyjob@debian.org>
Installed-Size: 279 kB
Depends: python3:any
Recommends: procps
Suggests: tini | dumb-init
Conflicts: systemd
Homepage: https://github.com/gdraheim/docker-systemctl-replacement
Download-Size: 79.8 kB
APT-Sources: http://deb.devuan.org/merged excalibur/main amd64 Packages
Description: daemonless "systemctl" command to manage services without systemd
"systemctl" is a replacement command to control system daemons without
systemd. "systemctl" is useful in application containers where systemd is
not available to start/stop services.
.
This script can also be run as init of an application container (i.e. the
main "CMD" on PID 1) where it will automatically bring up all enabled
services in the "multi-user.target" and where it will reap all zombies
from background processes in the container. When stopping such a container
it will also bring down all configured services correctly before exit.When I reload Synaptic, I get the following message at the end:
That is not what is needed, we need to see the contents of the /etc/apt/sources.list file to confirm the correct lines in there.
# normal devuan sources
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmwareYou should see a line similar to what I have above listed for the main updates, then the daedalus-updates & daedalus-security on their own lines in the file too.
What is the correct way to fix this?
Set the BIOS time to UTC or change the /etc/adjtime to say LOCAL instead of the UTC time it is now set too.
zeus@9600k:~$ cat /etc/adjtime
0.000000 1735138312 0.000000
1735138312
UTCEdit#3: sleuthing around the internet today, I guess I should have used su - to get the correct path.
From my install notes when I seen this come through.
SU changes not noticed here but may be in future so may as well set it up.
Changes in su
- The behavior of su has changed. Use 'su -' to get root's path or use
the full path to commands if you use only 'su'.
- There are several ways to get the old behavior. The easiest is to
edit /etc/default/su to add the line:
ALWAYS_SET_PATH yes
root@9600k:~# cat /etc/default/su
cat: /etc/default/su: No such file or directory
root@9600k:~# nano /etc/default/su
root@9600k:~# cat /etc/default/su
# Added to always have the PATH set for su.
ALWAYS_SET_PATH yesYou might want to create that file on your installs and install the lovely little program apt-listchanges which tells you thing like this when updating your packages..
A necro post to say thanks for the solution to getting even more of that scumbags code off my machine. Did not know I was even running it until I saw pulseaudio getting updated. Search and found this page with one of the easiest solutions I have ever done I do believe. Create an .xsessionrc with the contents from above the first one with the sleep 1 posting in it, install the pipewire-audio that removes the pulseaudio package then reboot to have working audio on the pipewire server. Perfect thanks again.
Well just chain them together like any other commands you can do.
update-rc.d cups enable; update-rc.d bluetooth enable; update-rc.d cups-registryd enablezeus@9600k:~$ ls ; pwd ; whoami
bin Documents mbox Pictures rtorrent Templates
Desktop Downloads Music Public src Videos
/home/zeus
zeusThat will execute each command one after the other when used on the command line, like I show above.