The officially official Devuan Forum!

You are not logged in.

#1 Re: Off-topic » The Verdict on Systemd is In » 2020-02-04 12:26:33

golinux wrote:

Did you really have to post that nonsense?

Just trying to brighten up your day!  :-)

#3 Re: Other Issues » Strange grub problem » 2020-01-25 22:38:28

Head_on_a_Stick wrote:
Head_on_a_Stick wrote:

This is starting to ring a bell with me about an old fdn thread that p.H handled and subsequently opened a bug report about. I'll see if I can find it again...

Ha! found it: http://forums.debian.net/viewtopic.php? … 09&start=0

Bug report: https://bugs.debian.org/cgi-bin/bugrepo … bug=925309

So try copying /boot/efi/EFI/devuan to /boot/efi/EFI/debian

EDIT: or perhaps use

# grub-install --target=x86_64-efi --bootloader-id=debian

Thanks for tracking that down! I have just skimmed it for now, but there is a LOT of UEFI/grub lore in there. I will peruse it tomorrow with fresh eyes - my eyes just don't work very well at the end of the day...

#4 Re: Other Issues » Strange grub problem » 2020-01-25 22:04:19

Head_on_a_Stick wrote:
sgage wrote:

If you think it would help, I will post the output of bootinfoscript

No, let's leave it for now. I think it's aimed more at non-UEFI systems anyway.

sgage wrote:

the problem seems to lie with grubx64.efi...

Indeed. This is starting to ring a bell with me about an old fdn thread that p.H handled and subsequently opened a bug report about. I'll see if I can find it again...

Yes, I took bootinfoscript for a spin, and it did seem to be geared for legacy type systems.

I'd be interested in knowing if others have encountered this. I have a workaround for now, but it's something that ought to get fixed...

Thanks for your help - really appreciate it!

#5 Re: Other Issues » Strange grub problem » 2020-01-25 21:38:23

Head_on_a_Stick wrote:
sgage wrote:

what is telling grub where to get its menu from?

I think the information is embedded in grubx64.efi

It may be time to unleash /usr/sbin/bootinfoscript — the output will be lengthy so perhaps use https://paste.debian.net/

Before I release the Kraken, I mean, unleash bootinfoscript, here's an interesting observation:

I saved an image of my beowulf install with dd, then restored an image of ascii to p6. It had been on p5, so I used grub-install to fix up the EFI/devuan directory. It indeed generated a new grubx64.efi, and did not touch grub.cfg. And it booted using the grub.cfg in ascii, at p6. So, I copied that grubx64.efi to a safe place, restored beowulf. It booted using beowulf's grub.cfg! Since, presumably, the /devuan/grubx64.efi points now to p6.

I ran grub-install, rebooted, and sure enough, it booted using the grub.cfg from p5 (a buster installation). I copied the grubx64.efi that I had saved back over to /devuan, and behold, it booted using grub.cfg from p6.

It seems to me that beowulf's grub-install is not generating a proper grubx64.efi. Does no one else have this issue?

If you think it would help, I will post the output of bootinfoscript, but the problem seems to lie with grubx64.efi...

#6 Re: Other Issues » Strange grub problem » 2020-01-25 20:45:06

Head_on_a_Stick wrote:

How very strange hmm

Is the EFI system partition definitely mounted under /boot/efi?

lsblk -f

Try changing /boot/efi/EFI/devuan/grub.cfg to this:

search.fs_uuid 9685be15-8423-402b-b734-f92844748a90 root hd0,gpt6
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

I'm booting via $ESP/EFI/BOOT/bootx64.efi using GRUB but there is no grub.cfg in $ESP/EFI/BOOT/ so I'm not sure if that's actually needed.

Yes, EFI definitely mounted at /boot/efi.

Your grub change didn't change anything. I also tried

configfile (hd0,gpt6)/boot/grub/grub.cfg

that I got from an old script I had kicking around.

I am starting to believe that the grub.cfg in the EFI/(distro) isn't really being used. But then what is telling grub where to get its menu from? Yes, very strange...

#7 Re: Other Issues » Strange grub problem » 2020-01-25 19:54:24

Head_on_a_Stick wrote:
sgage wrote:

It seems that beowulf's grub does not parse the grub.cfg file in /boot/efi/EFI/devuan

Can we see the content of that file please.

sgage wrote:

reinstalled grub to create a new one

How did you do that, exactly?

And can we please see the output of

# parted --list
efibootmgr -v
/sbin/blkid

The boot-info-script package (/usr/sbin/bootinfoscript) will show exactly what's going on but I can't be bothered trawling through the wall-of-output so give me a few posts to work it out for myself first. Thanks.

The grub.cfg generated in the /devuan directory is:

search.fs_uuid 9685be15-8423-402b-b734-f92844748a90 root 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

It is the correct UUID for the beowulf partition.

I created the /devuan directory in EFI/ the way I have been for a couple of years now:

sudo grub-install --recheck --no-floppy --force

parted --list gives:

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  274MB  273MB   fat32        EFI System Partition          boot, esp
 2      274MB   290MB  16.8MB               Microsoft reserved partition  msftres
 3      290MB   275GB  275GB   ntfs                                       msftdata
 4      275GB   344GB  68.7GB  ntfs                                       msftdata
 5      344GB   370GB  25.8GB  ext4
 6      370GB   395GB  25.8GB  ext4

efibootmgr -v gives:

# efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0005,0007,0000,0008,0002,000A,0003,0009,0004,0006,000B,000C
Boot0000* Windows Boot Manager	HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0001* devuan	HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\DEVUAN\SHIMX64.EFI)
Boot0002* USB Floppy/CD	VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)..BO
Boot0003* USB Hard Drive	VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)..BO
Boot0004* ATAPI CD-ROM Drive	VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0300000001)..BO
Boot0005* debian	HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\DEBIAN\SHIMX64.EFI)
Boot0006  UEFI:CD/DVD Drive	BBS(129,,0x0)
Boot0007* ubuntu	HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0008* debian	HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\DEBIAN\GRUBX64.EFI)
Boot0009* UEFI: SanDisk	PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(1,MBR,0x3bf4ec9f,0x390944,0x1f00)..BO
Boot000A* UEFI: SanDisk	PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/CDROM(1,0x390944,0x7c00)..BO
Boot000B  UEFI:Removable Device	BBS(130,,0x0)
Boot000C  UEFI:Network Device	BBS(131,,0x0)

Thanks for having a look...

#8 Other Issues » Strange grub problem » 2020-01-25 18:34:57

sgage
Replies: 10

I am experiencing a strange issue with grub in beowulf. It seems that beowulf's grub does not parse the grub.cfg file in /boot/efi/EFI/devuan, which is supposed to point to the grub.cfg in the /boot/grub partition of the beowulf root partition, and instead uses the /boot/grub/grub.cfg found in the first ext4 partition it encounters.

I have deleted /boot/efi/EFI/devuan and reinstalled grub to create a new one. I am definitely booting from /devuan - I bring up the BIOS boot menu and select 'devuan'.

Update-grub indeed generates the intended grub.cfg in the beowulf /boot/grub - if I copy it to /boot/grub of the first ext4 partition, grub comes up with the beowulf boot menu, in all of its cinnabar glory.

I am booting off of an nvme SSD drive, for what that's worth. nvme0n1p1 is the EFI partition, followed by some ntfs partitions. The first ext4 partition is p5 (currently buster), and beowulf is on p6.

I do a fair amount of experimentation with distros, and this is the first time I've encountered this. It's been going on for some weeks now.

What gives?

#9 Re: News & Announcements » It'll be when It's ready, I know, but an approximation? » 2020-01-15 01:31:12

Still 4 polkit-related packages being held back as of today...

#10 Re: Hardware & System Configuration » Secure Boot » 2020-01-13 17:27:06

Head_on_a_Stick wrote:
aut0exec wrote:

Even saw some Dells the other day where CSM isn't an option within the firmware!

Yeah, Intel are planning to remove it completely: https://www.anandtech.com/show/12068/in … fi-by-2020

Bastards...

Is this still the timeline for eliminating CSM? (The article was written in 2017.)

#11 Re: News & Announcements » It'll be when It's ready, I know, but an approximation? » 2020-01-06 22:21:17

fsmithred wrote:
Head_on_a_Stick wrote:
basati wrote:

The group of developers has to have an idea of where things are going

I can't speak for the developers but fsmithred has just released the first beowulf beta for Refracta so the release is approaching.

Yup. As soon as we get the installer isos right, we'll let you play with them. Meanwhile, I switched my main box to beowulf.  (Bye bye Jessie. I'm sorry it didn't work out as we first expected, but I had nothing to do with that. I kept you as pure as I could.)

My main box would be beowulf if I could install wine32. Other than that. beowulf works beautifully on my machine.

[edit: Ack! I just checked, and I was able to install wine32! So I can run the one program that I need to run in wine. Ironically, wine (64-bit) won't install because of a few held back packages. I'm sure it will get sorted, but I don't need it anyway. My main box is now beowulf!]

#12 Re: Off-topic » This should be fun... » 2019-12-12 01:24:24

aut0exec wrote:
fsmithred wrote:

OK, I read A.6 and if I read it again, I'm sure I'll get a headache.

I think we're screwed. As I see it, there should only be two options on this vote:
1. systemd only
2. some kind of support for other inits.

Then if 2 wins, figure out the details.

Yea... Was wondering this exact thing when reading through the options. Lots of fragmented options for non-systemd.



If Debian goes full systemd, what will this mean for Devuan?

Surely that is the question...

#13 Re: Off-topic » This should be fun... » 2019-12-11 17:43:53

fsmithred wrote:

OK, I read A.6 and if I read it again, I'm sure I'll get a headache.

I think we're screwed. As I see it, there should only be two options on this vote:
1. systemd only
2. some kind of support for other inits.

Then if 2 wins, figure out the details.

Exactly. But this way they can make it come out any way they want :-/

Yes, I think we're screwed.

#14 Re: Off-topic » ladies, gentlemen and whomever else: your fifth freedom... » 2019-12-11 01:33:55

What happened to my comment? It was there a minute ago.

#15 Re: Off-topic » ill just use the mailing list » 2019-12-11 00:31:19

freemedia2018 wrote:

someday maybe theyll fix this forum.

in about two seconds, someones going to tell you that "there is no problem."

theyre right, of course. no problem, at all. ive seen the list-- and ill take it over this. AGAIN.

its about my "hate," of course.

thats what they told me last time. funny, thats what torvalds said, too. look it up, its pretty classic.

Simmer down, man! It's not all about you, y'know. I think you are overreacting just a tad. I agree with most of what you've been saying, but you seem to be seeing enemies where they're not.

#16 Re: Devuan » Debian considering going systemd init only » 2019-12-09 01:14:15

You make a lot of good points. Is there any way for anything good not to get co-opted by the corporate borg? That's what i find myself wondering. ..

#17 Re: Off-topic » This should be fun... » 2019-12-09 00:05:59

freemedia2018 wrote:

do we know the timeframe on this? when does it close?

I believe it's 20 days.

#18 Off-topic » This should be fun... » 2019-12-08 22:26:04

sgage
Replies: 24

Just posted on Slashdot:

Debian Begins Vote on Supporting Non-Systemd Init Options

https://linux.slashdot.org/story/19/12/ … it-options

#19 Re: Devuan » Debian considering going systemd init only » 2019-12-07 22:00:55

little wrote:
ToxicExMachina wrote:

https://lists.debian.org/debian-devel-a … 00002.html
Options for voting are very interesting: according to description every option (except further discussion) is for SystemD.

From mailing listt:

[   ] Choice 1: F: Focus on systemd
[   ] Choice 2: B: Systemd but we support exploring alternatives
[   ] Choice 3: A: Support for multiple init systems is Important
[   ] Choice 4: D: Support non-systemd systems, without blocking progress
[   ] Choice 5: H: Support portability, without blocking progress
[   ] Choice 6: E: Support for multiple init systems is Required
[   ] Choice 7: G: Support portability and multiple implementations
[   ] Choice 8: Further Discussion

Doublespeak at work. Here's what the options really are:

[   ] Choice 1: F: Systemd only
[   ] Choice 2: B: Systemd only
[   ] Choice 3: A: Systemd only
[   ] Choice 4: D: Systemd only
[   ] Choice 5: H: Systemd only
[   ] Choice 6: E: Multiple Init Systems
[   ] Choice 7: G: Something unrelated to dilute votes for 6
[   ] Choice 8: Do nothing

There are essentially two options here: Make systemd default, or support multiple init systems. Anything else is bullshit. How they managed to come up with 7 choices out of 2 is amusing.

It basically seems like what they did for the original systemd vote back in jessie, only 3 times worse. I.e., bullshit. Or if you want to be polite, 'disingenuous'.

#20 Re: Devuan » Debian considering going systemd init only » 2019-12-07 20:13:03

ToxicExMachina wrote:

https://lists.debian.org/debian-devel-a … 00002.html

Options for voting are very interesting: according to description every option (except further discussion) is for SystemD. There is also sjw-related stuff in description for some of options.

Another interesting fact: systemd-homed will be merged with SystemD code very soon. It looks like someone want to turn Debian into SystemD-exclusive for systemd-homed promotion.

This is getting to be very depressing. What is wrong with LP? Does he really have Linus-envy, and want to have his own Lennax? Why can't he just stop? I have a bad feeling about this...

#21 Re: Desktop and Multimedia » SOLVED: MATE: any way to convert Applications-Places-System to single » 2019-12-05 01:45:46

nobodyuknow wrote:

I think it was in Ubuntu MATE that I saw a dialog, probably in MATE Tweak, to choose from a number of different look-and-feels. I much prefer the single menu instead of Applications-Places-System. Does Devuan MATE have an option to do so? I didn't see it in MATE Tweak.

Yes, you can remove all that from the panel, and add the menu of your choice. I'm not in MATE now, but if you right-click on the App/Place/Sys thing, you can delete it. Then right click on the panel and add the menu of your choice. Some people like the Brisk Menu (I don't). There's also a simple menu. Just poke around and see what you like.

No, this is not something you do from MATE Tweak.

#22 Re: Off-topic » your irc client » 2019-11-18 20:44:42

Hexchat is good - relatively full-featured, but easy to use right away.

#23 Re: Installation » ascii 2.1 iso with openrc install doesnt work » 2019-11-07 17:35:38

Just another data point: I installed using the ascii 2.1 iso, selected the openrc option, and it all worked fine.

#24 Re: Desktop and Multimedia » Choosing an email client » 2019-10-24 22:54:33

I use Thunderbird, have been for years. It runs on everything. I typically have several OSes on my system, and all of them share a Thunderbird email database on my data partition, and they all share the Google calendar. I have years and years of old emails that once in a while it's good to be able to search through.

I've tried them all, and nothing beats TB for me. For me it's all about interoperability. No matter what OS I boot up, my mail/calendar presents as identical, and functions identically.

#25 Re: News & Announcements » ASCII 2.1 point release » 2019-10-23 15:40:31

I installed from the new iso (netinst) in order to check out the openrc option. It installed without issue, and openrc is working fine!

Board footer

Forum Software