Posts by Ulysses_

Ulysses_ · Hardware & System Configuration

Who are the developers of devuan in this forum?

Ulysses_ · Hardware & System Configuration

fsmithred wrote:

we don't fork any of the packages necessary for secure boot. Make sure grub-efi-amd64-signed is installed. The bootloader directory in /boot/efi/EFI/ will be named 'debian'.

Does anyone know any virtualization option that supports Secure Boot in the guest, so one can try and understand what is going on in a successful Secure Boot?

Ulysses_ · Hardware & System Configuration

Ive not used antix or mx, i dont see the need for uefi boot or secure boot as mentioned by the limitations Head on a sticker mentions.

It makes no sense that Microsoft would break what little security Secure Boot offers by allowing it to boot absolutely anything plugged into a usb port as long as it bothers to look live and EFI. Do you have any references for this unbelievable limitation?

Ulysses_ · Hardware & System Configuration

seems foxnews like or far right or even extremist fringe of the far right ideology.

I wonder how coked up the op is.

he doesn't know what he's talking about.

These are political remarks and insults to a member who is not allowed by golinux to reply to political remarks and defend their reputation. You are punching an opponent with his hands tied. You have been reported.

Ulysses_ · Hardware & System Configuration

Microsoft charge a nominal fee of $99 for use of their Secure Boot keys.

One more reason to ask the developers of devuan then if they are reading, why not?

Ulysses_ · Hardware & System Configuration

Alright. How do you feel about this?

Instead of answering the question that you know the answer to better than anyone

Ulysses_ · Hardware & System Configuration

"If the .efi's and grub configs you and ubuntu are using are open source it makes sense to have people check them and include them elsewhere if they have to." - and yet you ask Devuan to 'mix some of MX into devuan', the same stuff that antiX uses!

What a mess from such a simple statement. The ".efi and grub configs" are a tiny, tiny percentage of MX that people can check as I said, as in check the source code, and only copy what they need after checking it.

Instead of answering the question that you know the answer to better than anyone, you are just trying to distract and insult.

Some UEFI implementations will allow live ISO images to run with Secure Boot enabled even if they do not support it.

If so, what's to stop devuan from modifying its live ISO image to take advantage of such a feature? Question to the admin if they are reading.

Ulysses_ · Hardware & System Configuration

Who has left and what have they left?

They left the thread because politics is very serious in places like America and Britain where people can lose their jobs for posting the wrong thing online. And because my case against state-supported leftists is valid even if you are not a teacher as the state still protects you as you vandalise property and harass people protesting at anything. No laughs to be had at losing one's job, or worse. Unless one is a genocidal lunatic laughing hysterically at the controlled demolition of America like those crazy villains in James Bond movies. Keep laughing as I recite the number of dead from communism in Cambodia, China, Russia.

Ulysses_ · Hardware & System Configuration

You haven't heard the last of me in that topic. People are not as naive or stupid as you think and that is why they have left. If the .efi's and grub configs you and ubuntu are using are open source it makes sense to have people check them and include them elsewhere if they have to.

Ulysses_ · Hardware & System Configuration

Can't we mix some of MX into devuan?

Ulysses_ · Hardware & System Configuration

Head_on_a_Stick wrote:

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.

The menus here are very rudimentary. They do not have anything like that.

Ulysses_ · Hardware & System Configuration

I did this too to be certain:

efibootmgr -v > temp
featherpad temp

Other lines have parts like ".E.F.I.\.M.I.C.R.O.S.O.F.T.\.B.O.O.T.\.B.O.O.T.M.G.F.W...E.F.I" and ".E.F.I.\.B.O.O.T.\.B.O.O.T.X.6.4...E.F.I" but we should be looking at the line pointed to in "BootCurrent: 0005" shouldn't we.

Ulysses_ · Hardware & System Configuration

Also tried installing MX as a full install to a USB flash drive (not a live boot). It fails to boot and the usual error message shows up:

Invalid signature detected.
Check Secure Boot Policy in Setup

What do you make of this? Live MX is signed, full install is not?

Ulysses_ · Hardware & System Configuration

In devuan, booted from a live CD with EFI but with Secure Boot disabled in a VM because vmware does not seem to support Secure Boot and the laptop does not boot devuan with Secure Boot enabled as I said:

efibootmgr -v
BootCurrent: 0001
BootOrder: 0000,0001,0002,0003
Boot0000* EFI VMware Virtual SATA Hard Drive (0.0)	PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x4,0x0)/Sata(0,0,0)
Boot0001* EFI VMware Virtual IDE CDROM Drive (IDE 1:0)	PciRoot(0x0)/Pci(0x7,0x1)/Ata(1,0,0)

uname -a
Linux devuan 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux

ls -l /vmlinuz 
lrwxrwxrwx 1 root root 27 May 30  2020 /vmlinuz -> boot/vmlinuz-4.19.0-9-amd64

aptitude search '?narrow(?installed, linux-image)'
i A linux-image-4.19.0-9-amd64      - Linux 4.19 for 64-bit PCs (signed)        
i   linux-image-amd64               - Linux for 64-bit PCs (meta-package)       

find / 2> /dev/null | grep -i '\.efi$'
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/gcdia32.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/grubia32.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/grubnetia32-installer.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/grubnetia32.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/gcdx64.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/grubnetx64-installer.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/grubnetx64.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/shim/fbx64.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/shim/mmx64.efi
/lib/live/mount/rootfs/filesystem.squashfs/usr/lib/shim/shimx64.efi
/lib/live/mount/medium/efi/boot/bootia32.efi
/lib/live/mount/medium/efi/boot/bootx64.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/gcdia32.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/grubia32.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/grubnetia32-installer.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/i386-efi/monolithic/grubnetia32.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/gcdx64.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/grubnetx64-installer.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/grubnetx64.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/shim/fbx64.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/shim/mmx64.efi
/run/live/rootfs/filesystem.squashfs/usr/lib/shim/shimx64.efi
/run/live/medium/efi/boot/bootia32.efi
/run/live/medium/efi/boot/bootx64.efi
/usr/lib/grub/i386-efi/monolithic/gcdia32.efi
/usr/lib/grub/i386-efi/monolithic/grubia32.efi
/usr/lib/grub/i386-efi/monolithic/grubnetia32-installer.efi
/usr/lib/grub/i386-efi/monolithic/grubnetia32.efi
/usr/lib/grub/x86_64-efi/monolithic/gcdx64.efi
/usr/lib/grub/x86_64-efi/monolithic/grubnetx64-installer.efi
/usr/lib/grub/x86_64-efi/monolithic/grubnetx64.efi
/usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
/usr/lib/shim/fbx64.efi
/usr/lib/shim/mmx64.efi
/usr/lib/shim/shimx64.efi

Ulysses_ · Hardware & System Configuration

That is the complete line. Similarly in MX booted from a live USB flash drive:

efibootmgr -v
BootCurrent: 0005
[snip...]
Boot0005* UEFI:  USB DISK 2.0 PMAP	PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(1,0)/HD(1,MBR,0x11f75d,0x800,0x3d4000)..BO

uname -a
Linux mx1 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64 GNU/Linux

ls -l /vmlinuz
lrwxrwxrwx 1 root root 28 Oct 29 20:22 /vmlinuz -> boot/vmlinuz-4.19.0-12-amd64

aptitude search '?narrow(?installed, linux-image)'
i   linux-image-4.19.0-12-amd64               - Linux 4.19 for 64-bit PCs (signed)
i   linux-image-amd64                         - Linux for 64-bit PCs (meta-package)

These are all the files ending in .efi:

find / | grep -i '\.efi$'
/usr/lib/grub/i386-efi/monolithic/gcdia32.efi
/usr/lib/grub/i386-efi/monolithic/grubia32.efi
/usr/lib/grub/i386-efi/monolithic/grubnetia32-installer.efi
/usr/lib/grub/i386-efi/monolithic/grubnetia32.efi
/usr/lib/grub/x86_64-efi/monolithic/gcdx64.efi
/usr/lib/grub/x86_64-efi/monolithic/grubnetx64-installer.efi
/usr/lib/grub/x86_64-efi/monolithic/grubnetx64.efi
/usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
/usr/lib/systemd/boot/efi/systemd-bootx64.efi
/live/linux/usr/lib/grub/i386-efi/monolithic/gcdia32.efi
/live/linux/usr/lib/grub/i386-efi/monolithic/grubia32.efi
/live/linux/usr/lib/grub/i386-efi/monolithic/grubnetia32-installer.efi
/live/linux/usr/lib/grub/i386-efi/monolithic/grubnetia32.efi
/live/linux/usr/lib/grub/x86_64-efi/monolithic/gcdx64.efi
/live/linux/usr/lib/grub/x86_64-efi/monolithic/grubnetx64-installer.efi
/live/linux/usr/lib/grub/x86_64-efi/monolithic/grubnetx64.efi
/live/linux/usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
/live/linux/usr/lib/systemd/boot/efi/systemd-bootx64.efi
/live/boot-dev/EFI/BOOT/BOOTia32.efi
/live/boot-dev/EFI/BOOT/BOOTx64.efi
/live/boot-dev/EFI/BOOT/grubx64.efi
/live/boot-dev/boot/uefi-mt/mtest-32.efi
/live/boot-dev/boot/uefi-mt/mtest-64.efi

It is almost certainly EFI/BOOT/BOOTx64.efi or EFI/BOOT/grubx64.efi that is being used, or both.

Ulysses_ · Hardware & System Configuration

Is the live kernel of MX the same as debian's whereas the fully-installed kernel is not so it needs your howto?

Does the LIVE MX boot on your system out of the box, with Secure Boot?

Ulysses_ · Hardware & System Configuration

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

Whereas "mokutil --sb-state" outputs this on antiX:

SecureBoot enabled

That's antiX running with SecureBoot enabled out of the box. Tried MX too, years ago and it booted likewise (EDIT: current MX boots too) but you have a howto for making MX boot with Secure Boot. How can this be?

Ulysses_ · Hardware & System Configuration

Incidentally, xubuntu boots. It has these shim packages:

shim 15+1552672080.a4a1fbe-0ubuntu2
shim-signed 1.45+15+1552672080.a4a1fbe-0ubuntu2

Devuan has these:

shim-helpers-amd64-signed_1+15+1533136590.3beb971+7_amd64.deb
shim-signed_1.33+15+1533136590.3beb971-7_amd64.deb
shim-signed-common_1.33+15+1533136590.3beb971-7_all.deb
shim-unsigned_15+1533136590.3beb971-7_amd64.deb

Remove some packages from Devuan? Mix xubuntu packages into Devuan?

Ulysses_ · Hardware & System Configuration

Devuan does not boot with Secure Boot enabled on my system. Despite the presence of shim packages. But another systemd-free distro, antiX, boots. Without any shim packages at all. How can Devuan be made to boot the same way as antiX when Secure Boot is enabled ?

The plot thickens: the developer of antiX says, word for word, "Secure Boot signing is NOT available on antiX." Then how t.f. does it boot with Secure Boot enabled?

Ulysses_ · Devuan Derivatives

Hello. Need to launch a terminal window at login automatically and run a script in it as root. So far it is in .fluxbox/startup as the following line that prompts for a password to become root. Where is the proper place to put this in fluxuan? So it does not prompt for a password?

sakura -e "bash -c 'trap bash 2; \
   echo Need root permissions.; sudo /home/user/my-script.sh; \
   if [ \\\$? != 0 ]; then echo FAILED, exiting in 10 s; sleep 10; fi' " &

Some of the script follows.

ifconfig $WIFI_DONGLE up $NETWORK_PREFIX.1 netmask 255.255.255.0
route add -net $NETWORK_PREFIX.0 netmask 255.255.255.0 gw $NETWORK_PREFIX.1
echo 1 > /proc/sys/net/ipv4/ip_forward
hostapd hostapd.conf

Ulysses_ · Hardware & System Configuration

Have you looked into running such a nonfree driver sandboxed by any chance? Or know someone who knows how to do it?

Ulysses_ · Hardware & System Configuration

Fair enough. I have written a script to get the wifi working as a hotspot without removing any driver - and be able to unplug and plug in the wifi dongle and get up and running by executing the script again.

Preparation:

apt update
apt -y remove python-wicd
apt -y install network-manager-gnome

# Launch the network manager applet and an output window for it
xfce4-terminal --title=nm-applet -e "sudo -u devuan bash \
-c 'echo This is for the network manager applet; nm-applet' " 2>/dev/null &

Here's the script:

#!/bin/sh

nmcli connection delete my_hotspot 2> /dev/null

nmcli device wifi hotspot con-name my_hotspot ifname wlx0002727ab66a \
ssid my_hotspot password PUT_PASSWORD_HERE

nmcli connection up my_hotspot

Ulysses_ · Hardware & System Configuration

Yes this is the desktop-live iso but not installed yet, simply booting it one can reproduce this apparent bug. Even without this particular hardware being present. Simply apt remove followed by apt install shows this apparent bug.

Another unexpected thing is that package firmware-misc-nonfree (which is needed or the wifi dongle won't work) is installed by default even though contrib and non-free are not enabled in /etc/source.list. Isn't devuan FOSS?

If I do not remove firmware-zd1211, the wifi hotspot appears to be working but when a smartphone try to connect to it, it fails. Removing firmware-zd1211, the wifi still seems to be working as if the kernel module is still loaded, and if you then reconnect the wifi connection, the same smartphone can now connect.

Ulysses_ · Hardware & System Configuration

Here is some output.

Checking that firmware-zd1211 is already installed:

root@devuan:/home/devuan# apt install firmware-zd1211
Reading package lists... Done
Building dependency tree
Reading state information... Done
firmware-zd1211 is already the newest version (1:1.5-4).
0 upgraded, 0 newly installed, 0 to remove and 100 not upgraded.

Now let's remove it.

root@devuan:/home/devuan# apt-get remove firmware-zd1211
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
firmware-zd1211
0 upgraded, 0 newly installed, 1 to remove and 100 not upgraded.
After this operation, 66.6 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 100348 files and directories currently installed.)
Removing firmware-zd1211 (1:1.5-4) ...

Trying to install it again:

root@devuan:/home/devuan# apt-get install firmware-zd1211
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package firmware-zd1211

So no messing with the repos, default settings for everything. This is a live iso boot.

Ulysses_ · Hardware & System Configuration

Trying to set up devuan as a wifi hotspot. For everything to work fine with the given wifi dongle, a little workaround is needed: you must remove package firmware-zd1211 and reconnect the wifi connection.

sudo apt remove firmware-zd1211

But if you then try to install the same package (needed if the wifi dongle is unplugged and plugged back in),

sudo apt install firmware-zd1211

then it says "Unable to locate package firmware-zd1211"

The package has just vanished! An apt update does not help. What is going on?

The same happens on both ascii and beowulf.

The officially official Devuan Forum!

#1 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-03 20:43:21

#2 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-03 20:12:51

#3 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-03 20:01:43

#4 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-03 20:00:37

#5 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-02 21:17:43

#6 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-02 20:55:37

#7 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-02 20:50:15

#8 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-02 20:44:39

#9 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 22:16:59

#10 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 21:13:09

#11 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 21:11:25

#12 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 21:04:28

#13 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 20:45:22

#14 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 20:36:41

#15 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 20:24:04

#16 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 15:55:54

#17 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-12-01 11:33:55

#18 Re: Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-11-30 07:50:33

#19 Hardware & System Configuration » How to make devuan boot with Secure Boot enabled the way antiX does it » 2020-11-30 07:36:56

#20 Re: Devuan Derivatives » [NEW]-FluXuan Linux-[RELEASE] » 2020-06-28 09:31:33

#21 Re: Hardware & System Configuration » SOLVED: Package no longer known to apt after you remove it » 2020-05-09 22:02:28

#22 Re: Hardware & System Configuration » SOLVED: Package no longer known to apt after you remove it » 2020-05-09 15:50:48

#23 Re: Hardware & System Configuration » SOLVED: Package no longer known to apt after you remove it » 2020-05-08 05:17:22

#24 Re: Hardware & System Configuration » SOLVED: Package no longer known to apt after you remove it » 2020-05-07 17:21:53

#25 Hardware & System Configuration » SOLVED: Package no longer known to apt after you remove it » 2020-05-07 17:11:24

Board footer