I feel a bit embarrassed to ask this, because I should know the answer (and I'm sure I've had this problem before, but a long time ago!)

I've just been renovating one of my ancient machines with a fresh install of Slackware-15. Everything has gone fine, until I try and add AlienBob's Libreoffice package using slackpkg.

It fails with a gpg error!

I should add that I keep a local repository of slackware stuff on a NAS drive, which is regularly updated from slackware.uk.

I've reconfigured my mirrors to slackware.uk, and done a "slackpkg gpg update, slackpkg update" and then reverted to my local mirror, but to no avail.

It has to be something I'm doing, as my regular machines don't have a problem. I'm guessing I need to grab Eric's gpg from somewhere, but I can't for the life of me remember where or how!

Can someone jog this senile old duffer's brain?

Cheers!

--
Pete

oops, hadn't read far enough

Did you change the repoplus line as well as uncommenting Eric's mirror? afair the keys aren't updated unless that is done.

Hi, Hazel,

I just remembered the fix a few moments ago! It was something very similar. I temporarily un-commented the [MIRRORPLUS] line in slackpkgplus.conf that pointed to Eric's mirror, then re-ran slackpkg update gpg, and finally re-commented the [MIRRORPLUS] line. I didn't need to touch [REPOPLUS] just to get the gpg key.

I knew there was something I had to do, but 15 has been so long coming, I haven't done a fresh install in ages!

At least, that's my excuse, and I'm sticking to it!

Thanks for the hint, though!

BTW, did you ever get your penguins back? If you are using grub, I might know the fix!

Cheers,

--
Pete

No, sadly! I did get them back briefly in -current with an earlier kernel but all I get now is a couple of acpi errors.

It's not worth my while switching to GRUB just for that as I hate it. But I'd be interested to know your fix. It might work in elilo too.

My experience with elilo is that it either works or doesn't, and if it doesn't, there's not much you can do about it! I had to ditch it on my laptop as initially, Slackware's installer refused to go past the "loading initrd" stage. I had to install grub on the install pendrive to be able to install ( see here: https://www.linuxquestions.org/quest...re-4175671086/ ).

Once I managed to get it installed, I could get elilo to boot, but like you, no penguins! And if you are having problems early in the boot sequence, its handy to be able to see that screen! So I switched to grub, and haven't looked back!

The problem seems to be an incompatibility between elilo and some uefi frame buffers - mainly Intel graphics, from my experience. However, I also had a similar issue with Grub on an older, non-uefi machine that I have in my workshop. The fix there was to add the following line to grub.conf

Its that last line that does the job. I have no idea how that would translate in elilo!

Anyway, that worked for me, for what it's worth!

Best of luck!

--
Pete

3 members found this post helpful.

The elilo equivalent would be passing the numerical form of GFXPAYLOAD as a kernel parameter of the form "vga=".
From the GRUB manual:
The problem would be knowing what mode to use. When I first started using Linux, a mode was just screen width and height in pixels. Now it seems you need to specify the colour depth as well.

In my case, the width and height is the 1920x1080 in the penultimate line and the 32 is the colour depth. You would need to know what resolutions your card / monitor support, but I would have thought any reasonably modern system should work with any of the examples above. The important bit (in grub) is to pass that information on to the next stage, which is what that red line does. It passes the mode on to the video buffer, rather than letting it try and work it out for itself - which some seem incapable of doing.

Not really my field of expertise - I used to be a broadcast video editor before I retired, so I'm very familiar with analogue video, and know just enough about digital video to be dangerous!

I suspect you knew most of what I've just written anyway, so apologies if so, but sometimes hearing someone else's interpretation can help focus on the problem!

Cheers,

--
Pete

2 members found this post helpful.

Yay! I've got my penguins back! I just gave an explicit vga of 1280x1024x32 to the kernel command line.

It seems that modern kernels will not do coloured images unless you give them an explicit colour depth. Why did no one tell me it was that simple?

YEEHA!

Glad you have your penguins back in captivity!



--
Pete