Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
12-02-2013, 01:27 PM
|
#16
|
Member
Registered: Apr 2006
Location: SE Texas
Distribution: Slack64-15.0
Posts: 910
Rep:
|
No problems with Slack64-C Multilib here on 4 desktops, 2 media boxes and 2 old Dell D630's.
HP All-in-one D110 works perfect from all systems.
|
|
|
12-02-2013, 03:00 PM
|
#17
|
Member
Registered: Nov 2003
Posts: 528
Rep:
|
I have been having problems with Slackware 14.1, but I am working through them one by one, and nothing has tempted me to go back to 14.0. In fact, the same has been true for past releases. Things break; fix or work-arounds are found for most, some we live with. Progress is ahead, not the othe way.
It helps a lot that I can boot back to Slackware 14.0 to test something. Sometimes, it turns out it worked that way in the older release too. Sometimes a work-around I used in 14.0 is no longer needed (and now breaks things) because the underlying bug was fixed.
|
|
|
12-02-2013, 04:48 PM
|
#18
|
Senior Member
Registered: Nov 2003
Distribution: Slackʍɐɹǝ
Posts: 1,486
Original Poster
|
Lets see, running full install of 14.1 KDE, same as I had in 14.0.
Firefox will stop displaying jpg's after a while (I posted a sep thread) but I've also noticed issues with other apps start at the same time, for example trying to switch Dolphin from windowed to full screen the right pane won't expand. I have to leave X and go back in.
Printer is an HP Photosmart Premium, everything just worked when I installed 14.0, but the install of 14.1 lost several paper sizes and would not print two to a page. I downgraded the the hplip package to the one from 14.0 to get the functions back but sane lists the scanner but won't let me choose it to scan from.
anyway, it gets frustrating to loose functions over time because my phone keeps doing he same thing. My android phone Google removed the zoom buttons from the map and ignores the menu button on the bottom of the phone for a menu button halfway off the left top of the screen Apple style then did the same in the music and store app. I'm right handed so a top left menu covers most of the screen. Microsoft made the same mistake way back with Windows mobile 3.
My old laptop I can't use newer than Slackware 13 because the alternate Intel video driver that works is no longer in /extras.
Last edited by enine; 12-02-2013 at 04:51 PM.
|
|
|
12-02-2013, 04:55 PM
|
#19
|
Senior Member
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 15.0 (multilib)
Posts: 1,356
Rep:
|
Quote:
You might want to look at darktable
|
I have tried darktable and all the other Linux raw processors. I would love to use it if it gave as good results as SilkyPix for my Panasonic G3. I could not get the lens correction to work as well as in SilkyPix.
|
|
|
12-02-2013, 04:59 PM
|
#20
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep:
|
If you mean that firefox displays black boxes instead of jpegs, there is, or was, a fix for that in xorg:
Put:
Option "XAANoOffscreenPixmaps" "true"
in a Device section in a file in /etc/X11/xorg.conf.d/
You may have to fill in the rest of the Device section too. Not sure.
|
|
|
12-02-2013, 05:00 PM
|
#21
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep:
|
Quote:
Originally Posted by arubin
I have tried darktable and all the other Linux raw processors. I would love to use it if it gave as good results as SilkyPix for my Panasonic G3. I could not get the lens correction to work as well as in SilkyPix.
|
You may want to open a bug report or ask on the mailing list about this. It'd be great to have it support as many cameras/lenses as possible.
|
|
|
12-02-2013, 05:56 PM
|
#22
|
Member
Registered: Aug 2013
Distribution: Slackware 14.1
Posts: 128
Rep:
|
Quote:
Originally Posted by Woodsman
There has been a long standing claim that Linux based systems are good for reviving old hardware. I have a PI and a PII. I updated those systems regularly when I updated my primary systems. Both now run Slackware 14.0 and both are horribly sluggish. Through the years I noticed both systems getting slower with each update.
This is not a rap against Slackware, which I have used for 10 years. Only a rebuttable against the claim.
Those two computers seem to have run best around the Slackware 12.1 and 12.2 era. That seems to be the turning point at which the claim turned into a fallacy. I'm half tempted to return those old systems to 12.2 (which I always thought was one of the best Slackware releases ever ). 12.1/12.2 are reaching EOL, but I use the two computers only for hobbyist reasons anyway.
|
Well, I had the same problem many years ago. When I would upgrade Slackware, the system would get slower. Not needing any of the newer stuff, I just went back to the older version. If memory serves me correctly at all, that was Slack 7 or so. I kept it until that machine died. When I got another machine and installed the latest Slack on it, I was surprised that XFree86 was gone!
Coordially,
|
|
|
12-02-2013, 06:59 PM
|
#23
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
|
Quote:
My old laptop I can't use newer than Slackware 13 because the alternate Intel video driver that works is no longer in /extras.
|
Yeah, I know. Somewhere along the way the kernel devs pulled support for 3dfx Glide for my Banshee AGP in my PII. The kernel in Slackware 13.1 I think.
I don't remember for certain, but perhaps the 2.4 kernel ran faster on the PI and PII too.
|
|
|
12-03-2013, 03:03 PM
|
#24
|
Member
Registered: Mar 2010
Location: oregon
Distribution: slackware64-15.0 / slarm64-current
Posts: 790
|
I have a digium tdm400p telephony card that requires "BIG_KERNEL_LOCK", a kernel option that was removed in the 3.xx kernels... Thus my asterisk box has to remain at slackware-13.37 for ever...
|
|
|
12-04-2013, 12:09 AM
|
#25
|
Senior Member
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 1,038
|
I feel bad that you're having trouble, but it's also a bit funny, because I had problems with 14.0 on my Lenovo T510 and had to go back to 13.1! USB events made it kernel-panic, and I could never get its integrated wireless to work. But 14.1's been working like a charm.
Conservative releases are good, and frankly that used to be the very definition of point releases -- minor revision bumps for incremental changes, and major revision bumps for big changes. It's nice when things actually happen like they should!
|
|
|
12-04-2013, 01:49 PM
|
#26
|
LQ Newbie
Registered: Nov 2006
Location: Slovenia
Distribution: Slackware Current
Posts: 25
Rep:
|
Quote:
Originally Posted by flyingv2
Cannot install catalyst 13.1 legacy driver on 14.1 -> Rdesktop is painfully slow with opensource radeon driver.
|
Option "NoAccel" "on"
and rdesktop is fast again...
|
|
|
12-05-2013, 05:05 AM
|
#27
|
Member
Registered: Feb 2004
Location: Valby, Denmark / Citizen of the Web
Distribution: Slackware 14.1
Posts: 879
Rep:
|
Quote:
Originally Posted by arubin
It took me all day yesterday to get wine working with SilkyPix on 14.1 and was on the point of rolling back in frustration.
Much of the problem was of my own making. I could have sworn I had multiib fully installed but didn't. And on the umpteenth try SilkyPix ran. I still don't know what I did that made the difference.
But the combination of wine and SilkyPix is unsupported and I suppose I should count myself lucky that it does work.
|
Maybe you can look into using PlayOnLinux - it allows for pulling in an older version of Wine for a specific application.
It will require some scripting - I checked, there is no install script for your application - but it will definitely be better than a dual-boot or rollback...
Last edited by mjjzf; 12-05-2013 at 05:05 AM.
Reason: Edited for clarity
|
|
|
12-05-2013, 05:12 AM
|
#28
|
Senior Member
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 15.0 (multilib)
Posts: 1,356
Rep:
|
mjjzf
It is working using .wine from my old installation.
|
|
|
12-10-2013, 06:56 PM
|
#29
|
Senior Member
Registered: Nov 2003
Distribution: Slackʍɐɹǝ
Posts: 1,486
Original Poster
|
Quote:
Originally Posted by dive
If you mean that firefox displays black boxes instead of jpegs, there is, or was, a fix for that in xorg:
Put:
Option "XAANoOffscreenPixmaps" "true"
in a Device section in a file in /etc/X11/xorg.conf.d/
You may have to fill in the rest of the Device section too. Not sure.
|
hmm, I waited until the problem occured again to be sure and it started again tonight
so I'm looking in /etc/X11/xorg.conf.d/ and its empty so I assume I would have to create a new file but I don't know the format.
|
|
|
12-11-2013, 02:24 AM
|
#30
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep:
|
You can use /etc/X11/xorg.conf-vesa as a help. You should only need the Device section I think, but make sure that the Driver points to your normal graphics driver - radeon, nouveau etc - rather than vesa, which is meant as fallback, or you may not even need a Driver option, which I've not tested. You should also find some examples on the net of what the section should look like.
It should look something like:
Code:
Section "Device"
Driver "radeon"
Option "XAANoOffscreenPixmaps" "true"
EndSection
You may need more options, but it's been a while since I've had to set one up and I don't know if xorg will detect the rest of the options automagically or not.
Last edited by dive; 12-11-2013 at 02:30 AM.
|
|
|
All times are GMT -5. The time now is 02:40 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|