You are not logged in.
You could also do lsmod |grep iwlwifi to see if the wireless module is loaded.
I think the card uses the legacy driver so
grep iwl4965 /proc/modulesAnd if it isn't loaded use
# modprobe iwl4965If that fixes things then add the module name to /etc/modules (or to a file under /etc/modules-load.d/) to force load it every boot.
Yes but a chroot is easier and quicker:
mkdir sid
# debootstrap sid sid/ https://deb.debian.org/debian
# chroot sid/Well it would be for a Debian package and they prefer it if you use the reportbug package but some maintainers can be funny if bugs are reported in derivatives. Can you reproduce this in a Debian sid chroot?
maybe libelogind-dev does not provide libsystemd-dev?
No, it does not. I've just unpacked the .deb in my Alpine Linux system and checked ![]()
Perhaps a bug report is called for then.
EDIT: until it's fixed use the equivs package to create "fake" dependencies.
Nice, thanks for sharing.
Apologies if this is an irritating point to raise but your scripts do not use bashisms so they could (should?) have a /bin/sh shebang instead.
EDIT: and did you know that yad already has a calendar?
yad --calendarIt used to ask where to put the bootloader when you installed the deb package, but it no longer asks.
The non-UEFI version (grub-pc) still asks for a target drive but the UEFI version does not because the question is meaningless for a UEFI system.
Why not just grab the source package instead and apply the patch to that?
Add the relevant deb-src lines to /etc/apt/sources.list then use
# apt update
apt source gnome-settings-daemon
cd gnome-settings-daemon-*
patch -p1 < brightness.patch
dpkg-source --commit
# mk-build-deps --install --remove
debuild -us -uc
# dpkg -i ../gnome-settings-daemon*.deb
# aptitude purge gnome-settings-daemon-build-depsThe dpkg-source & mk-build-deps commands are supplied by the dpkg-dev & devscripts packages.
How can I change dependency on libsystemd-dev and libudev-dev to libelogind-dev and libeudev-dev?
You shouldn't have to do that at all, the libelogind0 package has Provides: libsystemd0.
Can we see
apt policy libgnome-desktop-3-devIt might be best to add the beowulf repositories and let the libraw19 package be installed from there, it will then be updated afterwards if there are any vulnerabilities found.
Adding beowulf to a ceres system shouldn't cause any problems — APT will favour the ceres packages because they have a higher version number.
And note that the Mega .deb package adds their Debian buster repositories and APT key to the system when it is installed.
It is the same stanza I used with the previous OB setup.
## This uses the 'oblogout' menu {item => ['lxterminal sudo -e shutdown -r now', 'Reboot', 'applications-system']},and
## This uses the 'oblogout' menu {item => ['lxterminal sudo -e shutdown -h now', 'Shutdown', 'applications-system']},
I think you must be mistaken — the -e switch for sudo invokes it as an editor for the file named afterwards, check ~/.xsession-errors to confirm this. I think you meant to use
{item => ['lxterminal -e sudo shutdown -h now', 'Shutdown', 'applications-system']},But you don't need to open a terminal emulator to run the command ![]()
only those icons are available? ie: the ones with the UUID type names?
Not sure, sorry. I would investigate but the snooker's on TV ![]()
using the stanza in schema.pl won't work
You should show us exactly what you are adding to ~/.config/obmenu-generator/schema.pl.
This works for me:
{item => ['sudo shutdown -r now', 'Reboot']},That entry doesn't have an icon but one can be added with a third item between the square brackets.
FWIW I prefer to use obsession to exit the openbox session.
Check the installation instructions on trizen's github site: https://github.com/trizen/obmenu-genera … INSTALL.md
That has a link to my Debian packages for obmenu-generator, which include a package for the DesktopEntry perl modules (if you add the repository then these will be installed as a dependency of the obmenu-generator package).
If you decide to use my packages then you should try to remove the perl modules that were installed by the cpanm commands listed in Miyo's guide:
# cpanm uninstall Linux::DesktopFiles Data::Dump File::DesktopEntryIf you decide not to use my packages then you should still remove the Linux::DesktopFiles & Data::Dump perl modules because installing them with cpanm means that they will not be updated if any vulnerabilities are found in them.
The Devuan repsositories already have packages for those modules and they will be updated if any vulnerabilities arise:
# apt install libfile-desktopentry-perl libdata-dump-perlAlthough in my tests the libfile-desktopentry-perl package isn't actually needed to generate the menus.
HTH
EDIT: libfile-desktopentry-perl is an optional dependency to provide locale support, I'll add it to my package as a Recommends.
EDIT2: package updated, the current version is now 0.89-2.
No, Korn Shell only offers simple completion and has no command option completion (AFAIK). I've never really missed it though.
If you want a fully featured interactive shell then you should try zsh instead, especially with either fizsh or grml's sublime configuration. The latter's completion system is *much* better than the one offered with bash.
EDIT: but don't bother with oh-my-zsh, that's a buggy pile of shite.
I use this to launch a QEMU/KVM virtual machine along with virt-viewer and a shared directory (with the path to the disk image as the argument):
function vlaunch {
qemu-system-x86_64 -enable-kvm \
-m 4G \
-cpu host \
-smp cores=4 \
-drive file="$1",format=raw,cache=none,if=virtio \
-soundhw hda \
-vga qxl \
-device virtio-serial-pci \
-device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 \
-chardev spicevmc,id=spicechannel0,name=vdagent \
-spice unix,addr=/tmp/vm_spice.socket,disable-ticketing \
-device nec-usb-xhci,id=usb \
-chardev spicevmc,name=usbredir,id=usbredirchardev1 \
-device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 \
-chardev spicevmc,name=usbredir,id=usbredirchardev2 \
-device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 \
-fsdev local,id=qemu_dev,path=/home/empty/Public,security_model=none \
-device virtio-9p-pci,fsdev=qemu_dev,mount_tag=qemu_mount &
remote-viewer "spice+unix:///tmp/vm_spice.socket"
}See http://forums.debian.net/viewtopic.php?f=16&t=144775 for more on this.
But that's in $ENV (~/.kshrc) because I use Korn Shell rather than bloaty old bash :-)
why does my bios menu have a checkmark saying disable uefi / enable legacy bios
The "legacy bios" [sic] is an emulation performed by the UEFI firmware.
Do you have you any historical examples of said rootkits?
See https://www.blackhat.com/docs/asia-17/m … eality.pdf & https://www.welivesecurity.com/wp-conte … -LoJax.pdf (although Secure Boot doesn't actually offer any protection against LoJax).
(shouldn't be a driver problem with the cards)
Unless both cards have the same problem :-)
See https://wiki.archlinux.org/index.php/Ne … less#Intel & https://wiki.archlinux.org/index.php/Ne … ss#Atheros for some troubleshooting ideas.
Otherwise see https://wiki.archlinux.org/index.php/Ne … onnections — cause #4 looks like it might be relevant here.
Looks like this may not be possible: https://git.kernel.org/pub/scm/bluetoot … b0b1ab0818
However it seems that the Raspbian folks have a package for bluez-alsa: https://www.sigmdel.ca/michel/ha/rpi/bl … 01_en.html
You might be able to grab the source and rebuild it for Devuan and amd64. Or package up bluez-alsa directly from the GitHub repository.
Disclaimer: I don't use Bluetooth so I might be talking out of my ass (again).
Ive just disabled uefi altogether
No, you haven't. You've enabled CSM ("Legacy" mode), which emulates non-UEFI booting via your machine's UEFI firmware. This means the machine is still open to the many UEFI firmware vulnerabilities.
my drives are encrypted so good luck to anyone who can get info off them
If you have a rootkit then it can read the contents of the drive once the system is running. Secure Boot would help prevent rootkits from running. It's far from perfect but it is an extra layer of protection.
And before anybody starts bleating about not trusting Microsoft's keys note that it is possible to create your own keys, enrol them in the UEFI firmware and sign the kernel images with them. That's how I have enabled Secure Boot in my Alpine Linux system.
1st. question
As dice says: don't use the block devices as fs_spec identifiers in /etc/fstab, they can change from one boot to the next. You could also use a partition LABEL as an alternative to the UUID, or the PARTUUID or PARTLABEL (for GUID partition tables only).
2nd. question
I use a simple (Korn Shell) script to backup my Debian system to the spare drive in my laptop: https://gist.githubusercontent.com/Head … 2dd/backup
That script hardcodes /dev/sda1 as the backup drive because it's the only SATA device and so never changes, you should probably use the /dev/disk/by-uuid/ identifiers instead.
See also https://wiki.archlinux.org/index.php/Rs … tem_backup
In my case the script is called by a systemd .service (hence all of the print statements, which are recorded in the journal), run once a week by a systemd .timer; for Devuan you could use a(n) (ana)cron job instead.
I am formally withdrawing my assistance in this thread as an act of solidarity with anticapitalista. I fully support their fight to overthrow the capitalist system.
EDIT: and for the record Microsoft charge a nominal fee of $99 for use of their Secure Boot keys.
That is the complete line
I really don't think so. Try xterm instead, that wraps the output. Or run
efibootmgr -v | grep efiWhat do you make of this? Live is correctly signed, full install is not?
Some UEFI implementations will allow live ISO images to run with Secure Boot enabled even if they do not support it.
From your output Devuan has the signed kernel and the shim EFI loader so you probably just need to mark shimx64.efi in the installed system as "trusted" from the firmware ("BIOS") menus.
And please edit your posts to use code tags for any terminal output, it greatly improves readability.
The AX201 should be supported by the firmware-iwlwifi & kernel packages in the beowulf-backports repositories.
The .deb packages can be downloaded from Debian's repositories (which are mirrored in Devuan by amprolla):
http://deb.debian.org/debian/pool/non-f … +1_all.deb
http://deb.debian.org/debian/pool/main/ … _amd64.deb
Download those on another machine then transfer them to your Devuan system and install them. Afterwards you can add the beowulf-backports repositories and install the linux-image-amd64 metapackage from there so that the kernel is kept updated.
You should probably post /etc/fstab and /etc/network/interfaces.
I don't use NFS myself but I would check https://wiki.archlinux.org/index.php/NF … /etc/fstab — the _netdev option looks relevant for this problem.
Unfortunately "efibootmgr -v" does not say which .efi is being booted when you boot from a USB drive. It outputs this on antiX:
Boot0005* UEFI: USB DISK 2.0 PMAP PciRoot(0x0)/Pci(0x14,0x0)/USB(8,0)/HD(1,MBR,0x4f44f,0x800,0x3d4000)..BO
That looks to be cropped, can you scroll the output? Or make the terminal bigger so that you can see it all.
How can this be?
Not sure. Which kernel is it using?
uname -a
aptitude search '?narrow(?installed, linux-image)'
ls -l /vmlinuzSome UEFI implementations require that the user mark the EFI loader as "trusted" in the firmware ("BIOS") menus.
This will show exactly what is being booted:
efibootmgr -vDevuan should be using shimx64.efi.
EDIT: and use this to check if Secure Boot is enabled for the booted system:
mokutil --sb-statehttps://pkginfo.devuan.org/stage/beowul … 50f-1.html
Note that it is possible to boot antiX with Secure Boot enabled if my HowTo guide on the MX Linux forums is followed.