Posts by jdev

jdev · Other Issues

Marjorie wrote:

Also
$ sudo service nftables start
$ sudo service nftables status 
don't provide any output.

Add INIT_VERBOSE=yes to the definitions of environment variables in /etc/init.d/nftables.

jdev · Desktop and Multimedia

Actually it is a missed systemd dependency that should be corrected.

Instead of session optional pam_systemd.so there has to be session optional pam_elogind.so.

jdev · Desktop and Multimedia

Adding session optional pam_elogind.so to /etc/pam.d/lightdm-greeter enables the menu items. See Debian Bug #932047 (lightdm: greeter session support for elogind).

jdev · Desktop and Multimedia

rolfie wrote:

policykit

Somewhat more detailed would have been nice.

jdev · Desktop and Multimedia

cooleo wrote:

Installed Mplayer along with its gui:
Is that the problem with its codec?

Run gmplayer with the file to play in a terminal and you will see if there are any problems or errors.

jdev · Desktop and Multimedia

I've installed xorg-driver-video, xorg-driver-input, openbox, lxsession, lxde-common, lxpanel, pcmanfm. The lightdm-gtk-greeter starts and I'm able to log in.

Prior to logging in, there is the greeter menu bar with the power icon and its menu items Suspend/Hibernate/Restart/ShutDown which all are disabled.

I'd like to enable these and to be able to select them without being logged in. What is to do?

jdev · Other Issues

After my experiences here I created an as small as possible minimal-live ISO image with adjustments in grub's menu and a persistence partition for the /home directory.

While doing so I found some bugs in the desktop-live ISO image.

In boot/grub/x86_64-efi/grub.cfg there are both incorrect entries (insmod with *.mod) and non-existent entries (insmod ieee1275_fb, insmod vbe, insmod vga), which generate error messages during boot. Actually, all insmod entries are unnecessary and should be removed (i.e. only source /boot/grub/grub.cfg should remain) once the error in boot/grub/grub.cfg is fixed.

In boot/grub/grub.cfg the first line must read if loadfont /boot/grub/font.pf2 ; then in order for the following statements to be executed!

By the way, the directory efi seems to be unnecessary, because its content is already in boot/grub/efiboot.img. Furthermore, grub/x86_64-efi/{config.h,kernel.img} seem to be unnecessary.

For a UEFI boot only USB stick, a virtually empty directory isolinux is sufficient, containing only an empty isolinux.cfg.

I did all this for my ISO image and after xorriso-ing an edited boot, an "empty" isolinux and a copied live the USB stick boots perfectly.

jdev · Other Issues

Indeed!

You can delete everything in /isolinux but isolinux.cfg (and even everything in isolinux.cfg) in order to get grub's menu.

jdev · Other Issues

fsmithred wrote:

This one boots uefi:

It does. Thank you very much.

fsmithred wrote:

Sounds like you didn't make a grub.cfg.

I actually did.

For test purposes, I just changed the grub.cfg of your image, xorriso-ed it and this new iso image still boots, so it seems that creating the iso wasn't my problem.

I thought that the isolinux directory is only for non-UEFI legacy booting, but when deleting it, grub ends up in its command line. There is one reference to isolinux in grub's boot loader (/isolinux/isolinux.cfg).

jdev · Other Issues

Well, I seem to have almost made it. My new iso image boots ... but instead of the grub menu I immediately end up in a grub command line.

jdev · Other Issues

fsmithred wrote:

The minimal-live is not set up to boot uefi.

That's what I figured by now.

fsmithred wrote:

If you have another linux set up on the machine, you can boot the minimal-live on usb from grub command-line.

Thanks for the hint, but this is a pain in the ass.

Is there a script or documentation on how to create an iso image? I can mount iso9660 on a different machine and could take the boot and efi directory of the desktop-live and the live directory of the minimal-live to create a minimal-live that boots with uefi.

I have to edit boot/grub/grub.cfg, of course. (And I don't know about efiboot.img.)

jdev · Other Issues

I can boot on an old PC with non-UEFI BIOS, so it seems minimal-live isn't prepared for UEFI-BIOS?

jdev · Other Issues

HevyDevy wrote:

How do you clear the usb stick before you dd the iso?

Not at all, dd overwrites all contents.

jdev · Other Issues

I can't boot the minimal-live from USB.

I dd-ed it on a USB stick:

Device     Boot Start    End Sectors  Size Id Type
/dev/sdd1  *       64 940031  939968  459M 17 Hidden HPFS/NTFS

But the stick isn't bootable with my UEFI-BIOS.

No problems with the desktop-live, on the other hand:

Device Boot Start     End Sectors  Size Id Type
/dev/sdd1   *       64 2366367 2366304  1.1G  0 Empty
/dev/sdd2          588    3467    2880  1.4M ef EFI (FAT-12/16/32)

It can be booted, but seems to have a different structure.

How do I get a bootable minimal-live?

jdev · Installation

And now, to finally solve the last part of my problem, a step by step description of what actually to do:

sudo apt autoremove --purge grub-efi-amd64-signed shim-signed
Edit /etc/os-release and /etc/default/grub as mentioned above.
Remove the old (debian) EFI boot menu entry:
sudo efibootmgr -v and look for the line saying Bootxxxx* debian, where xxxx is something like 0001 or 0002 or so.
Delete the entry:
sudo efibootmgr -b xxxx -B, where xxxx is the value from above.
Install a new boot loader:
sudo grub-install
Optionally, delete the old (debian) secure boot loader:
sudo rm -r /boot/efi/EFI/debian
Reboot.
Be happy!

It worked for me after a netinstall, but do it at your own risk.

jdev · Installation

For those of you who, like me, want to understand in more detail why renaming Debian to Devuan affects secure boot, here is what I have found out so far and what I think to understand:

The signed boot loader shimx64.efi, which is necessary for secure boot, was taken unchanged from Debian. The EFI directory, where the files necessary for booting must be located, is in Debian - of course - defined as boot/efi/EFI/debian. Grub on the other hand takes the definition in GRUB_DISTRIBUTOR as the directory where to install grubx64.efi. So in order for shimx64.efi to load grubx64.efi (probably only within the same directory), grub must also select "debian". If you change this in /etc/default/grub, grubx64.efi will end up in a directory without shimx64.efi.

But the shim sources apparently allow the creation of a signed boot loader with a canonical certificate for other distributions. For Ubuntu this is already part of the rules (dpkg-vendor --is ubuntu), so Devuan would only have to add this for itself, compile and provide shim as an own package.

jdev · Installation

fsmithred wrote:

Are you using secure boot?

No.

I disabled "secure boot" prior to the installation, because it stopped the netinstall usb stick from booting (and I don't want secure boot anyway).

Nevertheless, the signed boot loader was installed.

fsmithred wrote:

Are you unable to boot your os?

No.

But I'd like to change the boot menu entry from "Debian" to "Devuan" and because I can't use the signed boot loader then anyway, I wonder what "remove grub-efi-amd64-signed and just use grub-efi-amd64" means, respectively what exactly has to be done (to make sure it still will boot afterwards).

jdev · Installation

jdev wrote:

HevyDevy wrote:
To answer your question better i think lsb_release -i -s reads from the file /etc/os-release.
Nope, it reads from /etc/lsb-release.

HevyDevy, you are right.

The first part of my problem is solved. The Debian/Devuan version of lsb is modified and reads - unlike the genuine lsb_release, which reads from /etc/lsb-release - /etc/os-release instead.

So the release notes should read more precisely: "Edit /etc/os-release to show ID=devuan and edit /etc/default/grub so that GRUB_DISTRIBUTOR ends with 'echo Devuan' instead of 'echo Debian' (in case lsb_release isn't installed)".

I still don't get "If you're booting UEFI mode, you will also need to remove grub-efi-amd64-signed and just use grub-efi-amd64.", though. Any explanation what to do or what is meant appreciated.

jdev · Installation

bitfarmer wrote:

There might be a difference in the files between people who were running Beta then upgraded and those that just installed the Release version. For the record, I upgraded from Beta, I don't have a /etc/lsb-release, and lsb_release -i -s reports 'Debian' unless I change the ID=Debian line in /etc/os-release whereupon the lsb_release -i -s reports 'Devuan' immediately.

I installed a minimal system with netinstall and have neither /etc/lsb-release nor lsb_release.

I can't find any reference to /etc/os-release in the lsb source from https://git.devuan.org/devuan-packages/lsb. So why is your lsb_release reading /etc/os-release?

So probably https://git.devuan.org/devuan-packages/lsb isn't the place that holds the actual Devuan sources?

jdev · Installation

HevyDevy wrote:

GRUB_DISTRIBUTOR=`lsb_release -d -s`
i get below for a grub boot menu
Devuan GNU/Linux 3 (beowulf)

This is not surprising, since grub undoubtedly makes use of GRUB_DISTRIBUTOR and lsb_release -d provides the description.

It is not and was not the question that a change to GRUB_DISTRIBUTOR will have an effect. The question was whether /etc/os-release would have any effect at all.

fsmithred wrote:

Changing the 'ID=' line in /etc/os-release will also change the name of the bootloader created by 'grub-install'.
Correction:
With ID=mydevuan, grub-install creates a bootloader at /boot/efi/EFI/mydevuan
With ID=devuan, it does not. It just went back to using /boot/efi/EFI/debian.
So, like I said before, I probably can't explain it.

This is strange, because there is no reference to /etc/os-release in any grub source (genuine, debian, devuan) I could find. Actually, /etc/os-release seems to come from systemd and grub-install definitively reads the bootloader id from GRUB_DISTRIBUTOR in /etc/default/grub (unless given by option bootloader-id or setting it as environment variable).

jdev · Installation

HevyDevy wrote:

To answer your question better i think lsb_release -i -s reads from the file /etc/os-release.

Nope, it reads from /etc/lsb-release.

jdev · Installation

The Devuan 3 Beowulf Release Notes says: "Edit /etc/os-release to show ID=devuan or edit /etc/default/grub to GRUB_DISTRIBUTOR="Devuan"."

I understand the change in /etc/default/grub, but why editing /etc/os-release? Grub doesn't seem to read that file, does it?

The Release Notes continues: "If you're booting UEFI mode, you will also need to remove grub-efi-amd64-signed and just use grub-efi-amd64."

Could someone please explain what exactly needs to be done? Why not simply run update-grub to generate a new boot menu?

If I am not wrong, the label "debian" in the UEFI boot menu can easily be changed to "Devuan" afterwards with efibootmgr, or am I missing something?

The officially official Devuan Forum!

#1 Re: Other Issues » [Solved] How to load nftables rules at boot? » 2020-11-11 11:14:45

#2 Re: Desktop and Multimedia » lightdm Suspend/Hibernate/Restart/ShutDown disabled in greeter » 2020-10-03 10:03:11

#3 Re: Desktop and Multimedia » lightdm Suspend/Hibernate/Restart/ShutDown disabled in greeter » 2020-10-02 12:21:34

#4 Re: Desktop and Multimedia » lightdm Suspend/Hibernate/Restart/ShutDown disabled in greeter » 2020-10-02 11:38:08

#5 Re: Desktop and Multimedia » MPlayer GUI does not show video » 2020-10-02 11:02:34

#6 Desktop and Multimedia » lightdm Suspend/Hibernate/Restart/ShutDown disabled in greeter » 2020-10-02 10:56:28

#7 Other Issues » Some ISO image insights and bugs » 2020-06-26 12:19:36

#8 Re: Other Issues » How to boot the minimal-live from USB? » 2020-06-25 20:22:13

#9 Re: Other Issues » How to boot the minimal-live from USB? » 2020-06-25 20:00:54

#10 Re: Other Issues » How to boot the minimal-live from USB? » 2020-06-25 18:30:24

#11 Re: Other Issues » How to boot the minimal-live from USB? » 2020-06-25 16:59:16

#12 Re: Other Issues » How to boot the minimal-live from USB? » 2020-06-25 15:23:44

#13 Re: Other Issues » How to boot the minimal-live from USB? » 2020-06-25 15:17:58

#14 Other Issues » How to boot the minimal-live from USB? » 2020-06-25 14:48:58

#15 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-15 13:46:45

#16 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-11 11:25:23

#17 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-10 19:04:12

#18 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 22:38:00

#19 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 18:54:48

#20 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 18:11:02

#21 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 12:44:07

#22 Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 11:54:20

Board footer