Friday the 13th Massive Upgrade

willysr · 07-14-2012, 08:18 PM

yup, too much verbose i guess

escaflown · 07-14-2012, 08:20 PM

Quote:

Originally Posted by wildwizard

Well mount certainly got verbose.

Yep and I like the additional info it shows during boot time

schmatzler · 07-14-2012, 09:24 PM

Everything went fine now, but my slapt-get broke due to the libcrypto-update.

Fixed it with downloading the source and doing a

Code:

export CFLAGS="-Wno-error" && make pkg

in that directory. Reinstalled the package afterwards.

willysr · 07-14-2012, 10:23 PM

The fix for wget problem has been resolved now with the latest update

Code:

Sun Jul 15 01:40:08 UTC 2012
Juggle a few things around so that slackpkg won't fall over while upgrading
from 13.37 or an earlier -current:
a/aaa_elflibs-14.0-i486-2.txz:  Rebuilt.
  Don't include libcrypto.so.0 and libssl.so.0 in here.
  The openssl-solibs package is a better place for them.
a/openssl-solibs-1.0.1c-i486-2.txz:  Rebuilt.
  Moved the old 0.9.8x libraries here.
n/openssl-1.0.1c-i486-2.txz:  Rebuilt.
n/wget-1.13.4-i486-2.txz:  Rebuilt.
  Prefer linking with OpenSSL, since the license allows it.
  This is less of a moving target than GnuTLS.

chytraeus · 07-14-2012, 11:16 PM

Quote:

Originally Posted by Speek

Thanks for the updates!
There seems to be a problem with the new mkinitrd. The /init script reports "/sbin/udevadm not found" in lines 303, 307 and 308 during boot.

Yeah, I see the same thing and now my slackware -current won't boot. I'm using lvm and I get some error like could not mount myvg to /mnt. Had to use systemrescue to boot slackware. I still don't have a fix for this. Anyone?

TobiSGD · 07-14-2012, 11:26 PM

I have a similar problem, I can't boot with the generic kernel. I created the initrd with

Code:

mkinitrd -c -u -k 3.2.23-smp -m ext4

That normally works, I just added the -u since I thought the missing udevadm is causing the issue, but that didn't help. It throws out an error-message that it couldn't mount /dev on /mnt because it isn't a block-device.
The huge kernel works without issues.

cwizardone · 07-14-2012, 11:31 PM

Anyone having trouble with the new version of NetworkManager? It is telling me my wireless card doesn't exist. I then installed wicd and the card does work, and it works in Xp.

escaflown · 07-14-2012, 11:40 PM

Quote:

Originally Posted by cwizardone

Anyone having trouble with the new version of NetworkManager? It is telling me my wireless card doesn't exist. I then installed wicd and the card does work, and it works in Xp.

I had the same issue when I first upgraded too. I fount out it was because I was somehow missing libnl3. Everything's working fine now.

chrisretusn · 07-14-2012, 11:45 PM

Well it's done. All is working well.

willysr · 07-15-2012, 12:06 AM

also check /etc/udev/rules.d/70-persistent-net.rules as WLAN card name might get changed there just like in my case from wlan0 to wlan1

glorsplitz · 07-15-2012, 12:16 AM

All is working well here too, current 32/64, new kernel, did mkinitrd_command_generator.sh.

Thank you everyone for help with gnutls, nettle, p11-kit and wget

zakame · 07-15-2012, 01:48 AM

Quote:

Originally Posted by TobiSGD

I have a similar problem, I can't boot with the generic kernel. I created the initrd with

Code:

mkinitrd -c -u -k 3.2.23-smp -m ext4

That normally works, I just added the -u since I thought the missing udevadm is causing the issue, but that didn't help. It throws out an error-message that it couldn't mount /dev on /mnt because it isn't a block-device.
The huge kernel works without issues.

Just upgraded, getting this one too when trying to boot with 3.2.23.

I can boot with my own 3.4.4 kernel, but I notice udevadm trigger trying to import the 'blkid' builtin and failing. Doesn't hamper with anything else though...

wildwizard · 07-15-2012, 02:25 AM

Just noticed this minor glitch with KDE

Code:

kded(6033) PowerDevilUPowerBackend::isAvailable: Could not request activatable names to DBus!
kded(6033): KDE Power Management System init failed!

The end result is the loss of the power off and reboot buttons in the K Menu

zakame · 07-15-2012, 02:28 AM

Quote:

Originally Posted by wildwizard

Just noticed this minor glitch with KDE

Code:

kded(6033) PowerDevilUPowerBackend::isAvailable: Could not request activatable names to DBus!
kded(6033): KDE Power Management System init failed!

The end result is the loss of the power off and reboot buttons in the K Menu

I could not replicate that. I was able to reboot/poweroff with the K Menu buttons fine.

wildwizard · 07-15-2012, 05:23 AM

Quote:

Originally Posted by zakame

I could not replicate that. I was able to reboot/poweroff with the K Menu buttons fine.

Cancel the panic it was a local modification that got undone when dbus was upgraded.