LinuxQuestions.org
Page 5 of 6 « First 34 5 6
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   3.8.y kernel declared dead. (https://www.linuxquestions.org/questions/slackware-14/3-8-y-kernel-declared-dead-4175461663/)

H_TeXMeX_H 05-18-2013 02:19 AM
Quote:
Originally Posted by michaelslack (Post 4953489)
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.

michaelslack 05-18-2013 02:56 AM
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 (Post 4911151)
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.

volkerdi 05-18-2013 02:58 AM
Quote:
Originally Posted by michaelslack (Post 4953575)
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.

michaelslack 05-18-2013 03:54 AM
Thanks Pat that's good to know.

Michael

storkus 05-18-2013 09:43 PM
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.)

chytraeus 05-19-2013 05:44 PM
Quote:
Originally Posted by willysr (Post 4949790)
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?

willysr 05-19-2013 09:29 PM
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

chytraeus 05-19-2013 09:36 PM
Quote:
Originally Posted by willysr (Post 4954589)
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?

willysr 05-19-2013 10:52 PM
yes, it should work as well

hippy jonny 05-20-2013 03:57 AM
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.

willysr 05-20-2013 04:12 AM
I never had to put that line on rc.local here and vwmare should works fine

stormtracknole 05-20-2013 11:56 AM
Quote:
Originally Posted by willysr (Post 4954744)
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.

cpuobsessed 05-20-2013 02:02 PM
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

gracien 05-20-2013 02:41 PM
Root exploit CVE-2013-2094
 
Quote:
Originally Posted by dolphin77 (Post 4951444)
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

stormtracknole 05-20-2013 02:49 PM
Quote:
Originally Posted by gracien (Post 4955127)
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.


All times are GMT -5. The time now is 03:30 PM.
Page 5 of 6 « First 34 5 6
Show 50 post(s) from this thread on one page