LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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-18-2013, 02:19 AM   #61
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269

Quote:
Originally Posted by michaelslack View Post
If -current(64) goes back to 3.4 then will the dreaded samsung-laptop bricking problem be an issue again? Fixes for that (such as they were) were introduced late in the 3.7 series I believe.
Fixes for that must come from Samsung. The bricking issue is present in Window$ too.
 
Old 05-18-2013, 02:56 AM   #62
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 80

Rep: Reputation: 25
Indeed, Samsung is the culprit, the problem was their fault. Nonetheless I believe workarounds of some kind designed to dramatically reduce the chance of the bricking were introduced into the kernel at 3.7.6 apparently:

Quote:
Originally Posted by volkerdi View Post
The fixes went in with version 3.7.6, however the bug in the firmware remains. It's probably safe, but there are no guarantees.
So the possibility remains, but the risk is of a different order of magnitude with the fixes in, as I understand it.
 
Old 05-18-2013, 02:58 AM   #63
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 861

Rep: Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679Reputation: 1679
Quote:
Originally Posted by michaelslack View Post
Indeed, Samsung is the culprit, the problem was their fault. Nonetheless I believe workarounds of some kind designed to dramatically reduce the chance of the bricking were introduced into the kernel at 3.7.6 apparently:
The same fixes also went into the 3.2 and 3.4 series at that time.
 
1 members found this post helpful.
Old 05-18-2013, 03:54 AM   #64
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 80

Rep: Reputation: 25
Thanks Pat that's good to know.

Michael
 
Old 05-18-2013, 09:43 PM   #65
storkus
Member
 
Registered: Jun 2008
Posts: 310

Rep: Reputation: 45
Is it too early to put my vote in for 3.10, assuming it's stable enough to be worth included in /testing by Slackware's release time? (Like probably everyone else, I'm eyeing b/dmcache.)
 
Old 05-19-2013, 05:44 PM   #66
chytraeus
Member
 
Registered: Dec 2008
Distribution: slackware64 openbsd
Posts: 75

Rep: Reputation: 2
Quote:
Originally Posted by willysr View Post
i do agree with Linux Kernel 3.8.x for now
i'm using VMWare here and i think it's broken if we used a combination of Linux Kernel 3.9 and GCC 4.8 to rebuild the modules
it worked with Linux Kernel 3.9 and GCC 4.7 or Linux Kernel 3.8 and GCC 4.8

Could you share how you get VMWare to work on Slackware?
 
Old 05-19-2013, 09:29 PM   #67
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,546

Rep: Reputation: 419Reputation: 419Reputation: 419Reputation: 419Reputation: 419
run the installer using --ignore-errors
if you are using Linux Kernel 3.8.x, then you don't need to patch anything. It should work out-of-the-box
 
Old 05-19-2013, 09:36 PM   #68
chytraeus
Member
 
Registered: Dec 2008
Distribution: slackware64 openbsd
Posts: 75

Rep: Reputation: 2
Quote:
Originally Posted by willysr View Post
run the installer using --ignore-errors
if you are using Linux Kernel 3.8.x, then you don't need to patch anything. It should work out-of-the-box
Nope, I'm running 3.2.45. Will it still work?
 
Old 05-19-2013, 10:52 PM   #69
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,546

Rep: Reputation: 419Reputation: 419Reputation: 419Reputation: 419Reputation: 419
yes, it should work as well
 
Old 05-20-2013, 03:57 AM   #70
hippy jonny
LQ Newbie
 
Registered: May 2011
Distribution: Slackware-13.37 32 bit
Posts: 6

Rep: Reputation: 6
A lot of guides I've seen with regards to installing vmware (particularly vmplayer) on slack have also used the stanza.

Vmware-installer-script --console --ignore-errors

Also you may have to put the lines

/etc/init.d/vmware-USBArbitrator start
/etc/init.d/vmware start

in your /etc/rc.d/rc.local script.
 
Old 05-20-2013, 04:12 AM   #71
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,546

Rep: Reputation: 419Reputation: 419Reputation: 419Reputation: 419Reputation: 419
I never had to put that line on rc.local here and vwmare should works fine
 
Old 05-20-2013, 11:56 AM   #72
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
Quote:
Originally Posted by willysr View Post
I never had to put that line on rc.local here and vwmare should works fine
I've had to use "/etc/init.d/vmware-USBArbitrator" before in order to get USB working. I don't know why under certain situations that has to be done though.
 
Old 05-20-2013, 02:02 PM   #73
cpuobsessed
Member
 
Registered: Jan 2006
Distribution: Fedora, Ubuntu, Slackware
Posts: 53

Rep: Reputation: 15
I haven't been able to use anything past 3.4.x due to kms problems with the RV500 ATI graphics; also 3.4 is a longterm release
 
Old 05-20-2013, 02:41 PM   #74
gracien
LQ Newbie
 
Registered: Jul 2011
Distribution: Slackware
Posts: 9

Rep: Reputation: Disabled
Root exploit CVE-2013-2094

Quote:
Originally Posted by dolphin77 View Post
Looks like kernels prior to 3.8.10 are not the safe choice currently (local root exploit):

http://packetstormsecurity.com/files/121616/semtex.c
Stable kernel is vulnerable to root exploit CVE-2013-2094 (3.2.29, CONFIG_PERF_EVENTS=y).
What should we do ? Upgrade to current ? Wait for Slack patch ?

Thank you
 
Old 05-20-2013, 02:49 PM   #75
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
Quote:
Originally Posted by gracien View Post
Stable kernel is vulnerable to root exploit CVE-2013-2094 (3.2.29, CONFIG_PERF_EVENTS=y).
What should we do ? Upgrade to current ? Wait for Slack patch ?

Thank you
You can probably patch that yourself if you are comfortable in building your own kernel.
 
  


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] Kernel 3.7.1 keyboard's dead RoyBatty100 Slackware 2 03-06-2013 11:41 PM
LXer: Openmoko Gets New Life in Brazil After Being Declared Dead LXer Syndicated Linux News 0 07-14-2009 09:30 AM
Dead kernel link B4lulu Linux - Newbie 4 08-28-2007 10:30 PM
Kernel updated, now Internet dead dmorrell Linux - Networking 1 04-26-2006 03:40 AM
keyboard dead with kernel 2.6.4 matrixfx Linux - Hardware 2 03-26-2004 10:06 PM


All times are GMT -5. The time now is 03:35 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