Slackware 14.1 - Release candidate 1!

volkerdi · 10-15-2013, 05:57 PM

Quote:

Originally Posted by Drakeo

package pango-1.34.1-i486-1.txz 14.1 rc and the old link libpangox-1.0.so.0 from pkg pango-1.30.1-i486-1.txz 14.0 missing so many media programs webkit etc will crash. so I had to link libpangox-1.0.so.0 to libpangoxft-1.0.so.0.3400.1
all is well. it is also missing in multilib.
also to build the nvidia proprietary driver must use latest driver.

libpangox was marked as deprecated in 2004 and was finally removed upstream. Since making a link isn't the right thing to do, I'm not sure of any solution here for binaries that seem to need it but can't be recompiled.

AlleyTrotter · 10-15-2013, 07:47 PM

When I select slackware from the boot manager page nothing happens ie no boot. The system just goes right back to the boot selector.
The usb UEFI boot stick does work, When I use my elilo.efi and elilo.conf installed on sdb at /boot/efi/ the system boots using linuxB efivar.
Let me add that the efibootmgr does create the boot variable it is listed like this.

Code:

root@linux:~# efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0006,0000,0004,0001,0002,0003
Boot0000* Linux
Boot0001* Hard Drive 
Boot0002* CD/DVD Drive 
Boot0003* USB 
Boot0004* linuxB
Boot0006* Slackware

Let me know what other info I can provide. (PV you have my direct email)
The directory structure can be very tricky when doing efi boot.

1337_powerslacker · 10-15-2013, 08:44 PM

I just downloaded the ISO image of -current as of RC1 stage, and, after wiping my disk, reinstalled. I suspect that this release will be better than the last one. (Not that any of them are bad, per se, but some are better than others).

Go Slackware!

Regards,

Matt

jtsn · 10-15-2013, 09:04 PM

Quote:

Originally Posted by Stuferus

or simply dont use that efi stuff and run with legacy bios option..

You can't multi-boot EFI and legacy OS using the same boot manager.

Drakeo · 10-15-2013, 10:27 PM

Quote:

Originally Posted by volkerdi

libpangox was marked as deprecated in 2004 and was finally removed upstream. Since making a link isn't the right thing to do, I'm not sure of any solution here for binaries that seem to need it but can't be recompiled.

well I guess I will recompile it and work something out. there is always will there will be a way . These huge programs are compiled against prebuilt static lib so I will look at rebuilding the static lib but this means the media plugins in all the latest virtual world viewers will be broken. oh it was a it was a symbolic link. but still not right. but it's working.

this will affect a few slackbuild programs.
I am loving this one it is pretty stable.

Oh yes had to kill nepomuk once it went up to using 3.5 gigs of memory. remember this is an slackpkg upgrade from pristine to another. 14.0 to 14.1 rc
so I cleared out the .kde like it was a fresh new start and that problem went away and was looking at the new default wallpaper nice theme.

DarkVision · 10-15-2013, 11:44 PM

Quote:

Originally Posted by Drakeo

well I guess I will recompile it and work something out. there is always will there will be a way .

Have you tried pangox-compat?

volkerdi · 10-15-2013, 11:53 PM

Quote:

Originally Posted by AlleyTrotter

When I select slackware from the boot manager page nothing happens ie no boot. The system just goes right back to the boot selector.

[...]

Let me know what other info I can provide. (PV you have my direct email)
The directory structure can be very tricky when doing efi boot.

So, it does boot if you select the /EFI/Slackware/elilo.efi using the firmware, right? Due to a lack of native UEFI hardware, that's all I could really test here, besides seeing that efibootmgr had installed *something*.

The line in eliloconfig that installs the menu entry is this one:

efibootmgr -q -c -d $EFI_DEVICE -p $EFI_PARTITION -l /EFI/Slackware/elilo.efi -L "Slackware"

So, for an EFI System Partition of /dev/sda1, that would translate as:

efibootmgr -q -c -d /dev/sda -p 1 -l /EFI/Slackware/elilo.efi -L "Slackware"

Does adding -g help? Otherwise, if you spot a bug in what I'm doing here, any correction is appreciated.

ponce · 10-16-2013, 12:27 AM

Quote:

Originally Posted by DarkVision

Have you tried pangox-compat?

this has been discussed here a little in the last days: my thought is that should not be necessary if the software you want to install is maintained, but in cases where isn't possible can surely be useful...
https://www.linuxquestions.org/quest...nd-4175478070/

as an example, for webkitgtk (that Drakeo named), updating to 1.10.2 will work fine without (see here).

Drakeo · 10-16-2013, 12:42 AM

Quote:

Originally Posted by DarkVision

Have you tried pangox-compat?

well no but I didn't but I will and I sure thank you for pointing me.

update laugh so hard at the readme file

Quote:

Thanks Ponce your right this is not a Slackware problem just mine using Slackware to run my projects qt-webkit is vital.

ponce · 10-16-2013, 02:13 AM

QtWebKit is already included in the stock qt Slackware's package.
try a

Code:

grep -i qtwebkit /var/log/packages/qt-*

Didier Spaier · 10-16-2013, 04:48 AM

Installation went smoothly, made a 100M EFI partition, setup detected it and put a FAT32 fs on it, registered it in /etc/fstab, installed elilo on it, so everything seemed to have worked.

But after that I can't boot the VM.

booting Slackware directly failed, I get:
Attemping to start up from:
-> Slackware... unsuccessful.
then in grub menu from the ISO image I chose "detect/boot any installed operating system" and select Slackware (last line), see os_chooser.png
but this failed as well, with "config file error(s)", see elilo.efi.png
Is there anything wrong in the EFI partition? see elilo.efi.conf.png

So I'm puzzled. Is there a problem with vmplayer and should I try with VirtualBox? What did I do or went wrong?

AlleyTrotter · 10-16-2013, 08:09 AM

Quote:

Originally Posted by volkerdi

So, it does boot if you select the /EFI/Slackware/elilo.efi using the firmware, right? Due to a lack of native UEFI hardware, that's all I could really test here, besides seeing that efibootmgr had installed *something*.
Otherwise, if you spot a bug in what I'm doing here, any correction is appreciated.

Yes by using the firmware it works

Code:

fs1:
cd EFI
cd Slackware
elilo.efi

I am using my B drive for current
So then I made a half dozen entries in the NVRAM using efibootmgr.
To make a long story short entry slack2 worked.
So here ya go

Code:

efibootmgr -q -c -d /dev/sdb -p 1 -l "\EFI\Slackware\elilo.efi" -L slack2

Both the backslashs and quotes were required. Just so were clear /dev/sdb1 is my efi partition
I tried to make a patch file, but I will need to study your script for about a week to do that. LOL
Hope this helps
John

Didier Spaier · 10-16-2013, 09:14 AM

This is what I did:

launch the installer
run setup just to choose the target partition
type the command proposed by AlleyTrotter
restart the VM
Bingo! I can boot into the VM

Thanks AlleyTrotter!

PS about the pic: I didn't try to do that recursively, i.e. launch a VM inside the VM etc. Only 4 G of RAM, sorry

Didier Spaier · 10-16-2013, 09:28 AM

[wrong post]

Didier Spaier · 10-16-2013, 02:16 PM

Quote:

Originally Posted by AlleyTrotter

I tried to make a patch file, but I will need to study your script for about a week to do that

Joking I guess

Code:

diff -u4 /usr/sbin/eliloconfig.old /usr/sbin/eliloconfig > AlleyTrotter.patch.txt

PS Stupid Didier => stupid question: why is eliloconfig installed in /usr/sbin but lilo in /sbin?

PPS on this page I see a commit message:

Quote:

Add support for UNIX-style path names (forward-slash)

but it's in master since 3 months, so not even applied in release 0.6.0 and 0.5.4 is shipped in Slackware-current. I guess we will survive with the backslashes...