LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
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 05-06-2017, 06:38 PM   #16
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 3,595
Blog Entries: 1

Rep: Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948

Quote:
Originally Posted by ppencho View Post
VirtualBox-5.1.14-112924-Linux_amd64.run and kernel 4.9.26 work fine together...
I usually uninstall VirtualBox before installing a new kernel, but this time forgot all about it. When I rebooted, VirtualBox automatically rebuilt its module for the "new" 4.9.26 kernel and has been running perfectly ever since.

Last edited by cwizardone; 05-06-2017 at 06:48 PM.
 
3 members found this post helpful.
Old 05-06-2017, 08:25 PM   #17
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Debian, Mageia, and whatever VMs I happen to be playing with
Posts: 12,784
Blog Entries: 17

Rep: Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315Reputation: 3315
The update broke my Terminator. Something about Python bindings for libvte.

I'll install anew sometime this week.
 
Old 05-06-2017, 10:01 PM   #18
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,675

Rep: Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978
Here's on my system:
Code:
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
content of dmesg:
Code:
vboxdrv: Unknown symbol __udivmoddi4 (err 0)
 
Old 05-06-2017, 10:20 PM   #19
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 7,628

Rep: Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948
willlysr: that's what I get too
 
Old 05-06-2017, 10:23 PM   #20
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,675

Rep: Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978
i wonder whether this is only happening in x86 as people with x86_64 doesn't have this problem?
 
1 members found this post helpful.
Old 05-06-2017, 10:56 PM   #21
hitest
LQ Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware
Posts: 5,224

Original Poster
Rep: Reputation: 1218Reputation: 1218Reputation: 1218Reputation: 1218Reputation: 1218Reputation: 1218Reputation: 1218Reputation: 1218Reputation: 1218
Quote:
Originally Posted by willysr View Post
i wonder whether this is only happening in x86 as people with x86_64 doesn't have this problem?
Good question. My -current box is 64 bit. Vbox works well here.
 
Old 05-07-2017, 01:13 AM   #22
ppencho
Member
 
Registered: Jan 2004
Location: Bulgaria
Distribution: Slackware64-current
Posts: 94

Rep: Reputation: Disabled
Quote:
Originally Posted by willysr View Post
i wonder whether this is only happening in x86 as people with x86_64 doesn't have this problem?
It seems that __udivmoddi4 is part of libgcc. I have multilib and I still use gcc_5.4_multilib, maybe this makes the difference?

Code:
/usr/lib/libgcc_s.so
/usr/lib/libgcc_s.so.1
/usr/lib64/libgcc_s.so
/usr/lib64/libgcc_s.so.1
/usr/lib64/libgccpp.la
/usr/lib64/libgccpp.so
/usr/lib64/libgccpp.so.1
/usr/lib64/libgccpp.so.1.0.3
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/libgcc.a
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/libgcc_eh.a
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/32/libgcc.a
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/32/libgcc_eh.a
/usr/src/linux-4.9.26/arch/h8300/lib/libgcc.h
/usr/src/linux-4.9.26/arch/m32r/lib/libgcc.h
/usr/src/linux-4.9.26/arch/microblaze/lib/libgcc.h
/usr/src/linux-4.9.26/arch/mips/lib/libgcc.h
/usr/src/linux-4.9.26/arch/score/lib/libgcc.h
/usr/src/linux-4.9.26/arch/sh/lib/libgcc.h
/usr/src/linux-4.9.26/arch/sparc/lib/libgcc.h
 
Old 05-07-2017, 02:09 AM   #23
rdsherman
Member
 
Registered: Aug 2009
Location: Santa Monica CA
Distribution: Slackware64
Posts: 50

Rep: Reputation: 9
I installed the latest -current kernel, glibc, gcc, ... & found a pleasant surprise. For the first time ever, I'm getting USB 3 flash drive write speeds close to what manufacturers claim. My Corsair Voyager II had been hitting no more than 20 MB/s; now it's 50 MB/s, as it should be. Anybody else noticed this radical driver improvement?
 
3 members found this post helpful.
Old 05-07-2017, 03:08 AM   #24
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,675

Rep: Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978
Quote:
Originally Posted by ppencho View Post
It seems that __udivmoddi4 is part of libgcc. I have multilib and I still use gcc_5.4_multilib, maybe this makes the difference?

Code:
/usr/lib/libgcc_s.so
/usr/lib/libgcc_s.so.1
/usr/lib64/libgcc_s.so
/usr/lib64/libgcc_s.so.1
/usr/lib64/libgccpp.la
/usr/lib64/libgccpp.so
/usr/lib64/libgccpp.so.1
/usr/lib64/libgccpp.so.1.0.3
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/libgcc.a
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/libgcc_eh.a
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/32/libgcc.a
/usr/lib64/gcc/x86_64-slackware-linux/5.4.0/32/libgcc_eh.a
/usr/src/linux-4.9.26/arch/h8300/lib/libgcc.h
/usr/src/linux-4.9.26/arch/m32r/lib/libgcc.h
/usr/src/linux-4.9.26/arch/microblaze/lib/libgcc.h
/usr/src/linux-4.9.26/arch/mips/lib/libgcc.h
/usr/src/linux-4.9.26/arch/score/lib/libgcc.h
/usr/src/linux-4.9.26/arch/sh/lib/libgcc.h
/usr/src/linux-4.9.26/arch/sparc/lib/libgcc.h
That could be it, but i'm not really sure
i have GCC 7.1.0 here and i tested with the latest update per May 6 and it still persists
 
1 members found this post helpful.
Old 05-07-2017, 03:09 AM   #25
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,675

Rep: Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978
Quote:
Originally Posted by rdsherman View Post
I installed the latest -current kernel, glibc, gcc, ... & found a pleasant surprise. For the first time ever, I'm getting USB 3 flash drive write speeds close to what manufacturers claim. My Corsair Voyager II had been hitting no more than 20 MB/s; now it's 50 MB/s, as it should be. Anybody else noticed this radical driver improvement?
most likely due to improvements in the kernel side
 
1 members found this post helpful.
Old 05-07-2017, 05:23 AM   #26
arahmadi
LQ Newbie
 
Registered: May 2017
Location: Samarinda, ID
Distribution: Slackware
Posts: 16

Rep: Reputation: Disabled
Hi,

I am new in this community.

I would like to report that perl is not happy with the recent upgrade of Slackware-current, I've got various error with *.c when trying to upgrade via cpan.

i.e.

LibIDN.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xdb80080)
Zlib.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xdb80080)

anyhelp?

I am trying to recompile the Perl now using
https://slackbuilds.org/mirror/slack...source/d/perl/

Last edited by arahmadi; 05-07-2017 at 05:38 AM. Reason: new effort
 
1 members found this post helpful.
Old 05-07-2017, 06:45 AM   #27
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,675

Rep: Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978
Quote:
Originally Posted by arahmadi View Post
Hi,

I am new in this community.

I would like to report that perl is not happy with the recent upgrade of Slackware-current, I've got various error with *.c when trying to upgrade via cpan.

i.e.

LibIDN.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xdb80080)
Zlib.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xdb80080)

anyhelp?

I am trying to recompile the Perl now using
https://slackbuilds.org/mirror/slack...source/d/perl/
Please don't mix between perl packages built via CPAN and SlackBuilds. Just stick with one method and you will be safe.

There are several threads here on LQ (here, here, and here) that discussed about this issue.
 
1 members found this post helpful.
Old 05-07-2017, 07:14 AM   #28
arahmadi
LQ Newbie
 
Registered: May 2017
Location: Samarinda, ID
Distribution: Slackware
Posts: 16

Rep: Reputation: Disabled
Thanks for the clue Willy. I got more clue from here.

Well, I managed to remove old cpan modules (built while in slackware64-14.2).
I've tried to rebuild Zlib, libidn, but the same errors are still there.

Now trying to downgrade the perl from 5.24.0 to 5.22.3, first. Then, summon the cpan console to uninstall things.
It's been a while not playing with -current.
 
Old 05-07-2017, 10:47 AM   #29
arahmadi
LQ Newbie
 
Registered: May 2017
Location: Samarinda, ID
Distribution: Slackware
Posts: 16

Rep: Reputation: Disabled
All good now.
This is my quick and dirty solution:

I move all related modules that was compiled with Perl 5.22.
In this case I back them up in different folders

Something like:

VERSION=_5.22
mv /usr/local/lib64/perl5 /usr/local/lib64/perl5$VERSION
mv /usr/local/shared/perl5 /usr/local/shared/perl5$VERSION
mv /root/.cpan /root/.cpan$VERSION
mv /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/vendor_perl$VERSION
mv /usr/share/perl5/vendor_perl /usr/share/perl5/vendor_perl$VERSION
mv /usr/lib64/perl5 /usr/lib64/perl5$VERSION
mv /usr/share/perl5 /usr/share/perl5$VERSION

Then I recompiled Perl 5.24.1 with the script supplied. cpan console is back.

Everything seems OK for now.

Hence I report successful upgrade to the latest -current on:
Intel DG31PR, Intel Xeon x5450 (mod) @3.0 GHz, DDR2 4GB, Radeon HD6400 1GB, Panasonic (TV) 1920x1080, Microsoft Wireless Mouse (series: 2000) and Keyboard (series: 1000).


Will do more test next weekend.

Good job Pat & Slackware team.
 
1 members found this post helpful.
Old 05-07-2017, 01:18 PM   #30
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 7,628

Rep: Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948Reputation: 2948
willysr: my VM is also 32-bit.
 
  


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
[SOLVED] Slackware Current and Slackware 14.2 default kernel version? LinuxUser42 Slackware 1 02-11-2016 12:39 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:22 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration