LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-16-2012, 12:47 PM   #106
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,485

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856

Quote:
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
Quote:
bash-4.1$ ls -l /Slackware64/boot/initrd-tree/lib64/ld-linux-x86-64.so.2
lrwxrwxrwx 1 root root 9 Jul 17 00:37 /Slackware64/boot/initrd-tree/lib64/ld-linux-x86-64.so.2 -> ld-2.9.so*
when the symlink should point to ld-2.15.so
Googling the error brought up this. http://lists.debian.org/debian-glibc.../msg00092.html

For me, this probably is the result of the buildup of cruft from repeated upgrades.
 
1 members found this post helpful.
Old 07-16-2012, 01:27 PM   #107
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware64
Posts: 145

Rep: Reputation: 47
Quote:
Originally Posted by allend View Post
+1 for me

I believe the problem is a symlink in the /boot/initrd-tree/lib64. I see
Code:
bash-4.1$ ls -l /Slackware64/boot/initrd-tree/lib64/ld-linux-x86-64.so.2
lrwxrwxrwx 1 root root 9 Jul 17 00:37 /Slackware64/boot/initrd-tree/lib64/ld-linux-x86-64.so.2 -> ld-2.9.so*
when the symlink should point to ld-2.15.so
Googling the error brought up this. http://lists.debian.org/debian-glibc.../msg00092.html

For me, this probably is the result of the buildup of cruft from repeated upgrades.
Yes, the symlink is the problem. When I changed it to point to ld-2.15.so and re-ran mkinitrd the generic kernel booted fine.

Last edited by mats_b_tegner; 07-16-2012 at 01:29 PM.
 
Old 07-16-2012, 01:40 PM   #108
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,619
Blog Entries: 2

Rep: Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076
I just checked that, in my initrd-tree the link is pointing to the correct file. I wonder why this is the case for me, but not for others?
 
Old 07-16-2012, 02:20 PM   #109
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 131

Rep: Reputation: 52
Now installed fresh -current (as of yesterday) on my ThinkPad T61, mkinitrd seems to behave fine. I was able to just do

Code:
mkinitrd -c -m ext4
in /boot and modify my /etc/lilo.conf as usual, and it just works.

Sounds like the mkinitrd problems are limited to upgraded installs.
 
Old 07-16-2012, 03:00 PM   #110
BrZ
Member
 
Registered: Apr 2009
Distribution: Slackware
Posts: 501

Rep: Reputation: 83
@inph

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.

Thanks.
 
1 members found this post helpful.
Old 07-16-2012, 03:25 PM   #111
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,925

Rep: Reputation: Disabled
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) :-)
 
1 members found this post helpful.
Old 07-16-2012, 03:51 PM   #112
QuasarDonkey
LQ Newbie
 
Registered: Jul 2012
Location: Ireland
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
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 04:02 PM.
 
Old 07-16-2012, 09:52 PM   #113
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,253

Rep: Reputation: 181Reputation: 181
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.
 
Old 07-16-2012, 10:01 PM   #114
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,619
Blog Entries: 2

Rep: Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076
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.

Last edited by TobiSGD; 07-16-2012 at 10:31 PM.
 
Old 07-17-2012, 12:04 AM   #115
QuasarDonkey
LQ Newbie
 
Registered: Jul 2012
Location: Ireland
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
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...
 
Old 07-17-2012, 12:07 AM   #116
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,619
Blog Entries: 2

Rep: Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076
Quote:
Originally Posted by QuasarDonkey View Post
I think it might be time to finally migrate to Arch...
You want to change the distro because you have breakages in a development branch? That sounds rather strange.
 
2 members found this post helpful.
Old 07-17-2012, 12:18 AM   #117
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,599

Original Poster
Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
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)
 
Old 07-17-2012, 12:27 AM   #118
escaflown
Member
 
Registered: May 2009
Location: Canada
Distribution: Slackware
Posts: 237

Rep: Reputation: 30
Quote:
Originally Posted by QuasarDonkey View Post
This update has brought me nothing but major breakage.

...

I think it might be time to finally migrate to Arch...
And as always stated here, -current is for those who know what they're doing ...
 
2 members found this post helpful.
Old 07-17-2012, 12:47 AM   #119
QuasarDonkey
LQ Newbie
 
Registered: Jul 2012
Location: Ireland
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
Quote:
Originally Posted by willysr View Post
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-17-2012 at 12:50 AM.
 
Old 07-17-2012, 12:57 AM   #120
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,619
Blog Entries: 2

Rep: Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076
Quote:
Originally Posted by QuasarDonkey View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Microsoft forms open source subsidiary on Friday the 13th LXer Syndicated Linux News 0 04-13-2012 07:50 PM
LXer: Linux Gets Gooey on Friday the 13th LXer Syndicated Linux News 0 02-13-2009 11:10 PM
LXer: One of those magic times: On Friday the 13th! LXer Syndicated Linux News 1 02-07-2009 10:43 AM
LQ Security Report - February 13th 2005 Capt_Caveman Linux - Security 4 02-13-2005 10:51 PM
LQ security report - Feb 13th 2004 unSpawn Linux - Security 5 02-13-2004 12:36 PM


All times are GMT -5. The time now is 02:03 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration