SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
xap/MPlayer-1.1_20120701-x86_64-2.txz: Rebuilt.
Don't update (create) icon theme caches unless they exist already.
Once created, these icon registries cause problems unless they are
rebuilt every time new icons are added. If you have any
icon-theme.cache files under /usr/share/icons, it would be a good
idea to get rid of them (unless you're planning to handle keeping
them up to date).
I am running Slackare-current properly updated (I hope), updates dated Wed Jul 18 20:21:15 UTC 2012 included, using fluxbox as WM.
I can get a wired connection with "dhcpcd eth0".
But when I try with wicd-client the connection seems to be established ("Done connected"), but less than a second later it says "Not connected".
With "wicd cli -z -c" it says I am connected but "route" says it's wrong.
With "wicd-curses" hitting the "C" key seems to do nothing at all.
I did "rm -rf ~/.wicd", to no avail.
I can't say exactly after which update wicd failed, but not the last one IIRC.
Am I the only one?
EDIT I tried as root, as well as under xfce and KDE : no luck.
Last edited by Didier Spaier; 07-19-2012 at 08:52 AM.
Reason: Text beginning with EDIT added
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,015
Rep:
I'm having the opposite problem, so to speak, since the upgrades. Wicd works, but NetworkManager does not. It reports there is no wired or wireless connection.
I think that was an error. Its also listed above for the hi-color theme. I don't think this has anything to do with MPlayer.
It did have something to do with MPlayer. The package had code in the install script that would rebuild the hicolor icon cache, creating it if it wasn't there before. Essentially, both packages with that description had the same problem.
Anyone having difficulty with a custom built kernel after all these upgrades? More specifically, kernel 3.4.4 or 3.4.5?
Setup: /dev/sda1 = /boot partition (ext2), /dev/sda2 = luks encrypted LVM (groups root, swap, home, var, tmp, all are ext4)
Did a clean install of -current using a dvd created with all updates up through July 17 changelog. I then upgraded everything up to yesterday's packages which included mkinitrd-1.4.7-i486-4.txz.
Compiled and installed the new kernel and its modules, then created the initrd with the following command:
When I try to boot the new kernel, it fails when trying to decrypt the luks encrypted drive, then the 'init' script exits and I get dropped to a shell of some sort. I can see in the '/boot/initrd-tree/init' script where it is failing, I just can't figure out why. The strange part is that during installation, I created the initrd for the generic-smp kernel using the same command as above, and it boots fine.
To recap, since I feel like an incoherent twit: Clean install of -current which had mkinitrd-1.4.7-i486-3, using generic kernel 3.2.23-smp. Made initrd using that version. Then, upgraded to mkinitrd-1.4.7-i486-4, and used that to make initrd for custom kernel 3.4.5 and can't boot it. I see this in the ChangeLog from July 15:
Quote:
a/mkinitrd-1.4.7-i486-2.txz: Rebuilt.
According to rworkman, udev is indeed required now in early boot for any
system using an initrd, so we'll set UDEV=1 in mkinitrd (leaving -u as a
no-op). This should clear up the issues with the /init script that
expected udevadm to be present.
Use ldconfig -l to ensure all shared libraries have the correct symlinks.
Thanks to Olek on LQ.
So, I don't think I have to use any different options in the 'mkinitrd' script (i.e., '-u'). Also, the I built the custom kernel the same way I've been doing for years. No config changes there. I had a clean install of -current a couple of weeks ago (wiped it and tried CentOS for a few days because that's what we use at work) and 3.4.4 worked fine then, but it fails now. Any ideas? Thanks
I've had a sound issue since the last big update ( ~ 13th-17th July ). I have 2 sound interfaces;
a. cmi8738 card
b. realtek al892 ( ati chipset on mainboard )
I use the CMI for general speaker music/vinyl recording and the Realtek for headset/Skype. KDE complains about the previous devices no longer being available and whether or not I want to remove them which I've done; the correct devices show in System Settings -> Multimedia -> Phonon and in the correct order ( I blacklist the Realtek ATI/Intel HDA at startup in /etc/modprobe.d/blacklist.conf and then load it manually in rc.local so that the CMI is the first card ).
blacklist snd_hda_intel
Everything appears to load correctly at startup and alsamixer shows all the correct devs and interfaces at the CLI. It's just KDE that complains. KMix also says "Mixer not found" or "The audio playback device CMedia ... does not work", and shows no devices when you open it up. Instead is shows amarok playback controls - weird!
Phonon backend is currently set to GStreamer. I've tried MPlayer as well but no luck there. The issue appears to have started with updates between the 13th and 18th of July. The possible updates causing this issue could be MPlayer and gst-plugins*.
Any help in solving this issue would be greatly appreciated.
It did have something to do with MPlayer. The package had code in the install script that would rebuild the hicolor icon cache, creating it if it wasn't there before. Essentially, both packages with that description had the same problem.
Ooops, not the first or probably the last time I have spoken rubbish .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.