You are not logged in.
Let it remove it
Do I use apt or dpkg to remove it?
Open a terminal and sudo dpkg --configure -a
The following output is produced:
Setting up fnfxd (0.3-18) ...
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <thoenig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxd
Have you tried the install again with the module loaded?
fnfxd is still installed.
When I attempt to remove it or I install other packages (e.g. apt-file), I get the following responses:
The following dialogue window is displayed:
An error occurred
The following details are provided:
E: fnfxd: installed fnfxd package pre-removal script subprocess returned error exit status 1
Close Button
After closing the above window, the Changes applied dialogue window appears and the following details are output:
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.
invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error while cleaning up:
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxd
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up fnfxd (0.3-18) ...
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <thoenig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxd
After closing the Changes applied window, fnfxd is still marked with an icon indicating "Marked for complete removal".
Should I attempt to run the modprobe and lsmod commands with the fnfxd package in this state?
Thanks!!
Debian and their BS breaking things
I used find -name *modprobe* | grep modprobe as apt-file was not installed.
discover-modprobe and modprobe are in the /sbin directory.
I installed apt-file which confirmed it.
Do I have to create the .bashrc file or should it already exist?
Using sudo /sbin/modprobe toshiba_acpi produced no output.
Thanks!!
The CONFIG_ACPI_TOSHIBA=m should be the one.
$ locate toshiba produced the following output:
/lib/modules/6.1.0-10-686-pae/kernel/drivers/char/toshiba.ko
/lib/modules/6.1.0-10-686-pae/kernel/drivers/platform/x86/toshiba-wmi.ko
/lib/modules/6.1.0-10-686-pae/kernel/drivers/platform/x86/toshiba_acpi.ko
/lib/modules/6.1.0-10-686-pae/kernel/drivers/platform/x86/toshiba_bluetooth.ko
/lib/modules/6.1.0-10-686-pae/kernel/drivers/platform/x86/toshiba_haps.ko
/lib/modules/6.1.0-27-686-pae/kernel/drivers/char/toshiba.ko
/lib/modules/6.1.0-27-686-pae/kernel/drivers/platform/x86/toshiba-wmi.ko
/lib/modules/6.1.0-27-686-pae/kernel/drivers/platform/x86/toshiba_acpi.ko
/lib/modules/6.1.0-27-686-pae/kernel/drivers/platform/x86/toshiba_bluetooth.ko
/lib/modules/6.1.0-27-686-pae/kernel/drivers/platform/x86/toshiba_haps.ko
/lib/modules/6.1.0-28-686-pae/kernel/drivers/char/toshiba.ko
/lib/modules/6.1.0-28-686-pae/kernel/drivers/platform/x86/toshiba-wmi.ko
/lib/modules/6.1.0-28-686-pae/kernel/drivers/platform/x86/toshiba_acpi.ko
/lib/modules/6.1.0-28-686-pae/kernel/drivers/platform/x86/toshiba_bluetooth.ko
/lib/modules/6.1.0-28-686-pae/kernel/drivers/platform/x86/toshiba_haps.ko
/usr/share/doc/libgphoto2-6/camlibs/README.toshiba-pdrm11
/usr/share/libinput/50-system-toshiba.quirks
$ modprobe toshiba_acpi produced the following output:
bash: modprobe: command not found
$ sudo modprobe toshiba_acpi produced nothing.
modprobe the module
P.S.
Which module should I use for modprobe?
Check your kernel
I am working on is the 32-bit version of Devuan.
It has 3 files in the /boot directory as follows:
config-6.1.0-10-686-pae
config-6.1.0-27-686-pae
config-6.1.0-28-686-pae
All 3 report the same results as follows:
CONFIG_TOSHIBA=m
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=m
What does the m value represent?
Can it be changed to y?
Thanks!!
keep us posted
Last night I looked at a package called fnfxd in the search list for brightness in synaptic.
Lo and behold it's an ACPI and hotkey daemon for Toshiba laptops. The description reads as follows:
fnfx enables owners of Toshiba laptops to change the LCD brightness,
control, the internal fan and use the special keys on their keyboard
(Fn-x combinations, hot-keys). The internal functions will give the
possibility to map the Fn-Keys to functions like volume up/down, mute,
suspend to disk, suspend to ram and switch LCD/CRT/TV-out. These
functions heavily depend on the system and/or kernel configuration.
You will need at least a kernel (v2.4.x, v2.5.x, v2.6.x) with ACPI and
Toshiba support (CONFIG_ACPI and CONFIG_ACPI_TOSHIBA).
Can the 6.1.0-28-686-pae kernel be configured for this?
I got the following responses when installing fnfxd and fnfx-client
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.
invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-2) ...
Errors were encountered while processing:
fnfxd
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up fnfxd (0.3-18) ...
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <thoenig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fnfxdfnfx-client
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up fnfxd (0.3-18) ...
Starting Toshiba hotkeys utils: FnFX Daemon v0.3 (c) 2003, 2004 Timo Hoenig <thoenig@nouse.net>fatal error: Could not open /proc/acpi/toshiba/keys.
Please make sure that your kernel has enabled the Toshiba option in the ACPI section.
For more information read the documentation and/or http://fnfx.sf.net/index.php?section=doc#kernel.invoke-rc.d: initscript fnfxd, action "start" failed.
dpkg: error processing package fnfxd (--configure):
installed fnfxd package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of fnfx-client:
fnfx-client depends on fnfxd (>= 0.3-18); however:
Package fnfxd is not configured yet.dpkg: error processing package fnfx-client (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
fnfxd
fnfx-client
If you're using GTK
Thanks! I installed gnome-system-tools as mate-user-admin would have wanted to install the mate desktop too.
Now I need an applet for Screen Brightness that uses xrandr.
Hi Folks,
MX Linux has a User Manager app as part of its MX Tools suite.
Is there something similar I can install for Simpleton Users that aren't au fait with computers like we are?
Thanks!!
Would it be safe it use MX Tweak from MX Linux 23.4?
I tried the following also but to no avail.
I know you can do it with the xfce4 power-manager
There is no slider presented with neither Devuan 5 nor MX Linux 23.4 on the Toshiba Tecra A7 (2006) using xfce4 power-manager.
MX Linux has a Tweak tool that includes a brightness slider using xrandr which works.
I had tried using the arandr app but it didn't have any interface for brightness control.
Using xfce4 power-manager with Devuan 5 on the Dell Latitude E6530 does present a Slider control for adjusting the brightness. Hmmmm.
Hi Folks,
What can be installed so that a User can adjust the Screen Brightness via an applet in the SysTray?
Can gnome-applets be installed for this?
Thanks!!
The command I gave
I used Synaptic and it marked all the required dependencies for installation too.
During the installation process, I was also prompted with a Dialogue Window to select which Display Manager (DM) was to be active. slim was already selected as it was the current one. So, I selected lightdm which was at the top of the list.
I then edited the lightdm.conf file.
I rebooted the Laptop et voila lightdm was the active DM.
Thanks!! again, MTB.
I prefer using Synaptic because it maintains a History of installations which is useful if you need to return to a previous configuration.
I am a long term user of Lightdm
Should I also install lightdm-gtk-greeter as suggested on the website I mentioned?
I just noticed that that website mentions configuring the /etc/lightdm/lightdm.conf file but but without any instructions in how to do so - duh!
Why do we want to Hide the Users? Did you mean [SeatDefaults]?
In MX Linux, greeter-hide-users is commented with a # to disable that setting. When the Login screen appears the User Name is already entered.
Thanks!!
All that matters is the system thought there was a change
What I should have included is where do you look to see the change in 'Label' value from 'Devuan Security' to 'Devuan-Security' for example?
Thanks!!
You have solved the mystery
So, in which of the Base Files should I be looking to see the difference? There was no difference in os-release.
Hi Folks,
I would like to have a more User Friendly Login screen (greeter) so that the User doesn't have to type in their User Name every time they Login as per MX Linux which uses lightdm-gtk-greeter and lightdm-gtk-greeter-settings and lightdm-modified-init.
I found the following page (Item 3).
https://www.baeldung.com/linux/display- … -uninstall
Are those instructions compatible with Devuan 5 - i386?
Does lightdm need to be run as a Service?
Is there anything missing from those instructions?
Thanks!!
It is only or should only be displayed
So far, I have uncovered the following:
Toshiba Tecra A7 after Install and APT updating
~$ cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 5 (daedalus)"
NAME="Devuan GNU/Linux"
VERSION_ID="5"
VERSION="5 (daedalus)"
VERSION_CODENAME="daedalus"
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/"
Created: 2024-12-27 15:06:20
Modified: 2024-09-12 16:16:07
Accessed: 2024-12-27 15:06:19
/var/log/apt/history.log
Last Update occurred starting with the following 2 lines:
Start-Date: 2024-12-27 15:06:19
Commandline: /usr/sbin/synaptic
It contained an entry for:
base-files:i386 (12.4devuan3, 12.4+deb12u7devuan1)
Previous Update occurred as follows:
Start-Date: 2023-07-20 02:57:27
Commandline: apt-get --yes --force-yes install dialog live-boot live-boot-initramfs-tools
Install: dialog:i386 (1.3-20230209-1)
End-Date: 2023-07-20 02:57:30
Live ISO filesystem.squashfs
/etc/os-release
PRETTY_NAME="Devuan GNU/Linux 5 (daedalus)"
NAME="Devuan GNU/Linux"
VERSION_ID="5"
VERSION="5 (daedalus)"
VERSION_CODENAME="daedalus"
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/"
Modified: 2023-05-11 03:09
Accessed: 2023-05-11 03:09
Link Target: ../usr/lib/os-release
It did not have a Created DateTimeStamp.
/var/log/apt/history.log
Last Update occurred as follows:
Start-Date: 2023-07-20 02:57:27
Commandline: apt-get --yes --force-yes install dialog live-boot live-boot-initramfs-tools
Install: dialog:i386 (1.3-20230209-1)
End-Date: 2023-07-20 02:57:30
searched the forum for "changed its 'Suite' value …
So, I used the command
sudo apt-get update --allow-releaseinfo-change
and the Warning Message, regarding the Repository Indexes, is no longer displayed.
However, before I did that, I reloaded the Package Information and this time only the Note about daedalus-security appeared as above in Post #62.
What would have caused the other 2 Notes to no longer be displayed?
How is it that the Suite and Label values were changed and how can you confirm that the changes are legitimate?
I tried searching man pages but couldn't find what effects are established with the use of the "--allow-releaseinfo-change" option. Is this information recorded in a file of the OS too?
change the /etc/adjtime to say LOCAL
This is the option I used and System Date and Time is correctly displayed now.
Previously, I had tried the
hwclock -s
command but it didn't appear to immediately do anything. After what must have been at least 30 mins or so (and maybe a reboot in between) the system date and time was displaying correctly but then I saw the BIOS was different. I prefer the BIOS to match the Operating System whether there is Dual-Booting or not.
So Folks, the Intel Boot Agent message hasn't appeared since installing the 500GB 7200RPM drive and installing Devuan 5 on it.
Boots Fast I guess; gets to the User Name screen in about 1 minute and after the password is entered about another 20 seconds for the Desktop to finish loading. Is that good?
The screen seems to be better quality than the one in the Lenovo L540 and its 16:10 which is much more useful for consuming vertical content.
your reply was confusing
Ah, now I get it. For some reason, I was thinking there was a setting in the 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.
Set the BIOS time to UTC
That must be a feature of newer BIOS/UEFI systems. This Laptop has a BIOS from 2006.
I will try editing the adjtime file.