LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Closed Thread
  Search this Thread
Old 01-23-2017, 03:48 AM   #1981
imitheos
Member
 
Registered: May 2005
Location: Greece
Posts: 441

Rep: Reputation: 141Reputation: 141

Quote:
Originally Posted by Darth Vader View Post
Doing "radeon.dpm=0" is Epic Fail!

Sorry, BUT disabling the freaking Power Management in that poor video-card is really a epic bad idea. Better to stay on a lower version kernel.
Does disabling DPM mean you do not have power management at all ? I had the impression that you get the older implementation of dynpm (which sucked majorly compared to dpm of course).

Quote:
Originally Posted by gmgf View Post
yes tested all 4.9 série, 4.9.5 need this command.
I use 4.9 from the beginning and i never had such a problem of not being able to reboot (or any other problem for that matter). My card is 6750 which is also evergreen so if you want me to test something, please tell me. Here is my kernel config if you want to compare options.
 
Old 01-23-2017, 06:11 AM   #1982
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 2,192

Rep: Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987
My card is radeon HD 5750.

Ok thanks, i would watch that tonight.
 
Old 01-23-2017, 07:12 AM   #1983
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
Quote:
Originally Posted by imitheos View Post
Does disabling DPM mean you do not have power management at all ? I had the impression that you get the older implementation of dynpm (which sucked majorly compared to dpm of course).
It does mean that you are back to manual power management, with echoing the powerlevel into a file in sysfs, IIRC.
 
Old 01-23-2017, 09:12 AM   #1984
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,039

Rep: Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218
Firefox-51 has been released, https://ftp.mozilla.org/pub/firefox/....source.tar.xz

The release notes, https://www.mozilla.org/en-US/firefo.../releasenotes/

Last edited by cwizardone; 01-24-2017 at 12:28 PM. Reason: Added a link to the release notes.
 
Old 01-24-2017, 02:15 AM   #1985
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 2,192

Rep: Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987Reputation: 987
Quote:
Originally Posted by imitheos View Post
Does disabling DPM mean you do not have power management at all ? I had the impression that you get the older implementation of dynpm (which sucked majorly compared to dpm of course).



I use 4.9 from the beginning and i never had such a problem of not being able to reboot (or any other problem for that matter). My card is 6750 which is also evergreen so if you want me to test something, please tell me. Here is my kernel config if you want to compare options.
finally i have tested two other distro, one with openrc and one with systemd, same problem, with 4.9.
 
Old 01-24-2017, 03:52 AM   #1986
imitheos
Member
 
Registered: May 2005
Location: Greece
Posts: 441

Rep: Reputation: 141Reputation: 141
Quote:
Originally Posted by gmgf View Post
finally i have tested two other distro, one with openrc and one with systemd, same problem, with 4.9.
Weird. My card is practically the same (the only difference i remember between 6 and 5 series is more powerful uvd for video decoding). Is it possible that there is a change in v4.9 that only triggers on your particular implemention's firmware ? Mine is Sapphire.

If you have the time/patience you could bisect the kernel and find the relevant commit.

Code:
# git bisect start -- drivers/gpu/drm
# git bisect good v4.8
# git bisect bad v4.9
.. compile - install - test kernel ..
# git bisect good/bad depending on outcome.
You compile and test each kernel and if the machine shuts down correctly you mark it "good" otherwise you mark it "bad". The "-- drivers/gpu/drm" part will limit the bisection to commits touching only directories below drivers/gpu/drm so it will be way quicker but it may not find the correct commit if the offending change was on another subsystem.
 
3 members found this post helpful.
Old 01-24-2017, 07:53 PM   #1987
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,308

Rep: Reputation: 922Reputation: 922Reputation: 922Reputation: 922Reputation: 922Reputation: 922Reputation: 922Reputation: 922
linux-4.9.6 ?

https://lkml.org/lkml/2017/1/24/170
 
Old 01-25-2017, 08:35 PM   #1988
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 316

Rep: Reputation: Disabled
Quote:
Originally Posted by alex14641 View Post
Code:
On my system, the Sandisk Cruzer USB Stick has file names in /dev/disk/by-id/, that contain
colons: this causes lilo to fail when using one of these files as a boot disk. This patch
replaces the failure with a warning.

--- ./src/geometry.c.orig       2015-11-21 18:50:18.000000000 -0500
+++ ./src/geometry.c    2016-12-28 18:27:24.322516088 -0500
@@ -1357,16 +1357,12 @@
 
 int geo_open(GEOMETRY *geo,const char *name,int flags)
 {
-    char *here;
-    int user_dev,block_size;
+    int user_dev = -1,block_size;
     struct stat st;
 
-    if ((here = strrchr(name,':')) == NULL) user_dev = -1;
-    else {
-       *here++ = 0;
-        warn("%s:BIOS syntax is no longer supported.\n    Please use a "
-         "DISK section.", name);
-       user_dev = to_number(here);
+    if (strrchr(name,':') != NULL) {
+        warn("%s:BIOS syntax is no longer supported: "
+                        "Treating as a device file.", name);
     }
     if ((geo->fd = open(name,flags)) < 0)
        die("open %s: %s",name,strerror(errno));
What do I have to do to get this patch included in Slackware?
 
Old 01-26-2017, 03:47 AM   #1989
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,039

Rep: Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218Reputation: 7218
Thunderbird-45.7.0.
The release notes, https://www.mozilla.org/en-US/thunde.../releasenotes/
 
1 members found this post helpful.
Old 01-26-2017, 04:01 AM   #1990
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,882

Rep: Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988
Quote:
Originally Posted by alex14641 View Post
What do I have to do to get this patch included in Slackware?
Wouldn't adding a call to realpath(3) to resolve the symbolic link before the check be a safer fix?
 
Old 01-26-2017, 04:08 AM   #1991
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by cwizardone View Post
Thunderbird-45.7.0.
The release notes, https://www.mozilla.org/en-US/thunde.../releasenotes/
Thanks Cwizardone. Actually this could have been posted in the [Slackware Security] thread as this release contains a fix for a tagged Critical vulneribility that "can be used to run attacker code and install software, requiring no user interaction beyond normal browsing.".

Anyway I am sure Pat will upgrade ASAP.
 
1 members found this post helpful.
Old 01-26-2017, 07:47 AM   #1992
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 316

Rep: Reputation: Disabled
Quote:
Originally Posted by GazL View Post
Wouldn't adding a call to realpath(3) to resolve the symbolic link before the check be a safer fix?
The links are auto-generated, to be the same regardless the machine: realpath could potentially be different.
 
Old 01-26-2017, 08:38 AM   #1993
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,882

Rep: Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988Reputation: 4988
Quote:
Originally Posted by alex14641 View Post
The links are auto-generated, to be the same regardless the machine: realpath could potentially be different.
I don't see how, as that's the whole point of the /dev/disk/by-* hierarchy. But it doesn't matter. Was only a suggestion.

If you want your patch included you'll have to argue your case with Pat I guess.
 
Old 01-26-2017, 10:50 PM   #1994
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 316

Rep: Reputation: Disabled
Quote:
Originally Posted by GazL View Post
I don't see how, as that's the whole point of the /dev/disk/by-* hierarchy. But it doesn't matter. Was only a suggestion.

If you want your patch included you'll have to argue your case with Pat I guess.
If you have a machine with one disk, /dev/sda, and you plug in a thumb drive, the real path for the thumb drive will be /dev/sdb; if you have another machine with two disks, /dev/sda and /dev/sdb, and you plug in the thumb drive, the real path will be /dev/sdc. The real paths are different, but the sym link in /dev/disk/by-id will be the same on both machines.
 
Old 01-27-2017, 09:38 AM   #1995
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,198

Rep: Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307
It's not available yet, but please watch for the next version of Flex and update to it as soon as possible. There's an issue in Flex that prevents an unpatched WINE 2.0 from being built:

https://bugs.winehq.org/show_bug.cgi?id=42132
https://github.com/westes/flex/issues/160

It was fixed in the Flex repository just this week:

https://github.com/westes/flex/commi...a2871d6036f253

Last edited by dugan; 01-27-2017 at 09:45 AM.
 
1 members found this post helpful.
  


Closed Thread


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] how to show the current time at the top in the current shell Always ? rohitchauhan Linux - General 5 04-09-2014 03:05 PM
Slackware ARM (current) epic mistake: the current Android kernels are kicked out! Darth Vader Slackware 16 08-25-2013 04:36 PM
[SOLVED] setup fails on most current Slackware-current March 26, 2012 AlleyTrotter Slackware 15 04-09-2012 06:05 AM
Observation of Feb -current vs March -current Hangaber Slackware 14 03-12-2010 08:26 AM
cvs diff the most current and second last current version powah Linux - Software 1 03-30-2006 01:02 PM

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

All times are GMT -5. The time now is 04:26 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
Open Source Consulting | Domain Registration