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.
When I rebooted my -current system today after upgrading to the latest mkinitrd-package and created a new initrd I get a kernel panic:
/bin/ash: error while loading shared libraries: /lib64/libc.so.6 unexpected PLT reloc type 0x25
+1 for me
I believe the problem is a symlink in the /boot/initrd-tree/lib64. I see
I was having this same error: "udevd[1346]: failed to create queue file: No such file or directory"
Think it was solved by adding "devtmpfs /dev devtmpfs mode=0755,nosuid 0 0" to /etc/fstab, based on LFS instructions. No more errors about failed queue file.
I have this error too:
Jul 16 15:28:42 m1 udevd[1328]: '/sbin/modprobe -bv acpi:PNP0B00:' [1362] terminated by signal 6 (Aborted)
Jul 16 15:28:42 m1 udevd[1308]: '/sbin/modprobe -bv acpi:PNP0B00:' [1384] terminated by signal 6 (Aborted)
Seems to be related to rtc_cmos [/sys/bus/acpi/devices/PNP0B00:00/physical_node/uevent]. I'm trying to figure this out and appreciate any help.
The e100 firmware issue is a kernel bug, and there's nothing we can do about that. It's one of the last drivers to call request_firmware() or some such incorrectly, best I recall. This is from memory, so I may have some details wrong, but you get the idea (or at least some usable search terms to double-check me) :-)
Has anyone gotten the Broadcom 4331 wireless working since this update? I've recompiled the kernel with BCMA turned on, and it worked! Yesterday. Now it doesn't work today. The b43 driver loads, but when I try to bring up the wlan0 interface, here's what dmesg says:
Code:
[ 3699.166869] firmware bcma0:0: firmware_loading_store: unexpected value (0)
[ 3699.170621] b43-phy0 ERROR: Firmware file "b43/ucode29_mimo.fw" not found
[ 3699.170631] b43-phy0 ERROR: Firmware file "b43-open/ucode29_mimo.fw" not found
[ 3699.170640] b43-phy0 ERROR: You must go to hxxp://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
The b43 firmware files are installed under /lib/firmware/b43. It's really perplexing since it worked last night, and doesn't work today. The only changes since the last working boot is that I installed a few programs like Skype.
Does anyone else have a working Broadcom 4331 since Friday the 13th?
UPDATE: inph's trick of repeatedly running "ifconfig wlan0 up" does bring the interface up eventually.
Last edited by QuasarDonkey; 07-16-2012 at 03:02 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,015
Rep:
Friday the 13th Massive Nightmare Upgrade Strikes VirtualBox
Looks like VirtualBox has been hit by the Friday the 13th Upgrade, and, yes, I have already re-installed VirutalBox after the upgrade. I've fired it up and it gets to the main windows, but this was the first time I actually tried to run a "machine" therein.
It reports this error,
Quote:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
As previously stated, VB has already been re-installed and on boot up the module loads without an error message.
Just tried it, Vector Linux runs fine on Virtualbox 4.1.18 on my 32 bit -current system and on 4.1.10 (have to update that) on 64 bit (no multilib) -current. Both systems have the latest updates (July 16), Virtualbox is installed using Oracle's installer.
UPDATE: Upgraded to 4.1.18 on the 64 bit machine, still working fine.
This update has brought me nothing but major breakage.
Now truecrypt won't mount any containers. Here's the syslog from the same time I tried mounting:
Code:
Jul 17 04:44:48 slackbook udevd[1377]: failed to create queue file: No such file or directory
Jul 17 04:44:48 slackbook udevd[1377]: failed to create queue file: No such file or directory
And also my system goes idle when enabling swap (encrypted) during boot, so I have to Ctrl-C to cancel swapon.
Since the big update, I get a lot of udevd errors during boot, including the ones that inph and BrZ mentioned.
Note I wiped the whole system yesterday, installed fresh with 13.37, updated to current, and recompiled the kernel (for hardware support). But I'm still having a lot of trouble.
I think it might be time to finally migrate to Arch...
on the contrary, i just wiped my ArchLinux and installed Slackware-Current on my old laptop and it worked perfectly out of the box. Everything just perfect.
One of the reason is the switch from /lib to /usr/lib which broke my system. Slackware made it so easy to upgrade, but unfortunately, not in Arch (at least in my case)
on the contrary, i just wiped my ArchLinux and installed Slackware-Current on my old laptop and it worked perfectly out of the box. Everything just perfect.
I know, Slackware has always worked perfect on my OLD laptop too. It just doesn't like my shiny new MacBook (but neither does any other distro, not that I'd want to use any other; Slackware-current rules) It's just so frustrating that everything worked perfectly a few days ago.
The reason I mentioned Arch is that its wiki indicates that the MacBook is supported (with a little work). Actually the Arch solution for the wireless will probably work with Slack, but there seems to be some udev-related problems in -current, which others are having too.
Last edited by QuasarDonkey; 07-16-2012 at 11:50 PM.
It's just so frustrating that everything worked perfectly a few days ago.
Exactly that is the reason why I always backup the system before upgrading, especially when such major upgrades are coming. When it doesn't work I report my problems here and until they are solved I have the option to revert to the previous state.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.