LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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 08-14-2012, 09:34 PM   #106
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.1 64-bit with multilib
Posts: 2,076

Rep: Reputation: 210Reputation: 210Reputation: 210

Quote:
Originally Posted by hitest View Post
You just need to give Slackware some time. Trust me on this. Slackware grows on you. Slackware is very elegant in its logical simplicity.
Couldn't put it better myself...

Also...


 
4 members found this post helpful.
Old 08-14-2012, 09:54 PM   #107
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 527
Blog Entries: 3

Rep: Reputation: 126Reputation: 126
Quote:
Originally Posted by Loslobo View Post
I noticed some alsaconf and xorgsetup hiccups in Slack14-current RC1

On trying both 32 and 64 bit current as fresh installs on the same machine and sound card (Pentium dual core E2220, G41 intel chipset motherboard and Esoniq 1371 PCI sound card); Using alsaconf doesn't seem to detect the older PCI based sound cards like the Esoniq ES1371.

On 32 bit current, alsaconf fails to detect the PCI card, then asks for proceeding to detect ISA legacy, picking yes, alsaconfig picks one, but not the proper card. Yet when I rerun alsaconf for the second time, it properly identifies and detects the Esoniq ES1371 PCI card.

On the 64 bit current, running alsaconfig defaults to asking for ISA legacy and fails to find any sound card when picking yes. Same result when rerunning alsaconf again.

The old xorgsetup script runs and detects my nvidia card, but detects the LCD monitor as three monitors and related screen xorg settings (screen 0, screen 1, screen 2), shown in the generated xorg.conf
I've noticed something similar with alsaconf.. I bought an Asus Xonar DS PCI sound card shortly before upgrading 13.37 to -current. In 13.37 alsaconf found the DS, in -current it doesn't find anything.

The card still works fine, though I did have to spend a few days wrestling /etc/asound.conf into submission...
 
Old 08-14-2012, 10:19 PM   #108
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,205

Rep: Reputation: 554Reputation: 554Reputation: 554Reputation: 554Reputation: 554Reputation: 554
Talking

Quote:
Originally Posted by Jeebizz View Post
Haha
 
Old 08-15-2012, 02:17 AM   #109
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 523

Rep: Reputation: 140Reputation: 140
Angry Slackware14RC1: mesa mach64 dri support dropped upstream

Mesa dropped dri support for older chipsets with mesa-8.0.4, this effectively kills mach64 for older laptops. There is a
Code:
--disable-dri           Disable DRI support [[default=auto]]
configure flag for xf86-video-mach64 but I can't figure out if that is used. If "auto," then it doesn't work since my ATI Rage Mach64, which worked fine with Slackware 13.x, no pitches a fit about missing mach64_dri module - and, lo, it is missing!

This might also effect:
r128
i810
mga
savage
sis
tdfx
unichrome
swrastg

See also
http://www.phoronix.com/scan.php?pag...item&px=OTgzMg
https://aur.archlinux.org/packages.php?ID=17939
(xorg, dri.freedesktop.org, their gits, are down seemingly or I would provide additional source info).

So I will either need to downgrade, see if I can patch a la Arch, or just recycle the old Pentium III laptop (the Horror!).

It may also be time to shift those drivers to /pasture as they are pretty slow to begin with and lack of DRI make them next to useless. A simple fb is just as fast.

Edit: Fixed in Slackware 14.0 RC2 however, mach64_dri is still missing and glxinfo says dri enable. weird.

Last edited by kingbeowulf; 08-16-2012 at 07:11 PM. Reason: New informaton
 
Old 08-15-2012, 07:21 AM   #110
rinias
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 58

Rep: Reputation: 18
Quote:
Originally Posted by bonixavier View Post
The option CONFIG_FB_VESA=y in the RC kernel is causing NVIDIA's blob to spill the following error.
Code:
[   47.491112] NVRM: Your system is not currently configured to drive a VGA console
[   47.491114] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   47.491116] NVRM: requires the use of a text-mode VGA console. Use of other console
[   47.491117] NVRM: drivers including, but not limited to, vesafb, may result in
[   47.491118] NVRM: corruption and stability problems, and is not supported.
For some unknown reason, vesafb stopped working with the newest versions of the blob. Reference is there.
http://www.nvnews.net/vbulletin/show...6&postcount=39

I'm pretty ignorant as to deciphering what all that means and the error message seems harmless to me, just thought I should mention it.
From what I have been able to discover, there have always been stability issues with nvidia and fb's; the change is that they finally put a message in to alert us. If there weren't problems before, it seems they're saying we should chalk that up to luck.

My problems are linked to setting vga to anything other than 'normal' or '0' in my boot loader. If I'm not mistaken, previously, once nvidia was installed, even if the console had been 'pretty' before, it returned to vga=normal mode. Other than making the console ugly, I think there is another change which is worth note:

I only stumbled upon this thread while researching 'vesafb nvidia' to make sure no one had posted this before, but I have been having issues with waking from suspend. There are no issues going into sleep, but when the system wakes up, the system seems to come up but the screen remains blank. Furthermore, I don't think that the keyboard is responsive, as I've tried to export dmesg, pm-suspend and other logs to no avail.

Currently, I am running Slackware64-current with the 302.17 blob. I don't know that it matters, but this particular setup used to have a memory mapping issue which - I believe - was fixed with an io-mem patch in kernel 2.6.30 or 31. I will try to re-enable the vesa console with the 295 blob (hey, they've come out with 304 as the new LTS blob...) and post my results here.

Let me know if you'd like any more information on this issue.
 
Old 08-15-2012, 11:30 AM   #111
aocab
Member
 
Registered: Nov 2009
Location: Heart of Texas
Distribution: Slackware-current
Posts: 138

Rep: Reputation: 30
I also appear to have an odd issue with gmplayer.

Example:

If I open gmplayer like so:
Code:
$ gmplayer
Open a file...play the file...and then stop playback.
If I press play again gmplayer gets stuck with the play button pressed in and I have to kill gmplayer.

Running gmplayer with strace I see these messages repeated when the issue occurs:
Code:
nanosleep({0, 20000000}, NULL)          = 0
select(1, [0], NULL, NULL, {0, 0})      = 0 (Timeout)
nanosleep({0, 20000000}, NULL)          = 0
select(1, [0], NULL, NULL, {0, 0})      = 0 (Timeout)
nanosleep({0, 20000000},  <unfinished ...>
When I kill gmplayer strace spits out:
Code:
MPlayer interrupted by signal 15 in module: unknown
MPlayer interrupted by signal 2 in module: unknown
If I open gmplayer like so:
Code:
$ gmplayer file-to-play
Play the file...stop playback.
If I press play again it works.

It appears that the problem only occurs when I open the file from within gmplayer and play-stop-play.
If I open a file and play-stop and then open another file and play-stop it works.

I also see these messages in konsole when gmplayer's menu opens:
Code:
(gmplayer:2253): Gdk-WARNING **: Attempt to draw a drawable with depth 24 to a drawable with depth 32
Cheers
 
Old 08-15-2012, 11:48 AM   #112
tpreitzel
Member
 
Registered: Aug 2007
Posts: 253

Rep: Reputation: 28
Replace Audacious 3.2.4 With Audacious 3.3.1

Personally, I consider the inclusion of Audacious 3.2.4 a bug. Why? Somewhere along the line recently, the developers omitted the LIRC plug-in. Thankfully, the LIRC plug-in was reinstated in version 3.3.x of Audacious. ALL multimedia runs from a remote control in my house.

According to the developers, one of the main reasons for including the legacy (3.2.x) version of Audacious is due to the requirement of GTK+ version 3 for Audacious 3.3.x which Slackware-Current thankfully provides.

Last edited by tpreitzel; 08-15-2012 at 11:50 AM.
 
Old 08-15-2012, 06:01 PM   #113
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 875

Rep: Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819
Quote:
Originally Posted by tpreitzel View Post
According to the developers, one of the main reasons for including the legacy (3.2.x) version of Audacious is due to the requirement of GTK+ version 3 for Audacious 3.3.x which Slackware-Current thankfully provides.
Audacious 3.2.x already requires GTK+ version 3.

If it drops right in, perhaps I'll take a look. But it's already gotten to be primarily bugfixing time, not upgrade time. Personally, I don't consider a missing feature to be the same thing as a bug.
 
3 members found this post helpful.
Old 08-15-2012, 07:47 PM   #114
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 523

Rep: Reputation: 140Reputation: 140
Quote:
Originally Posted by bonixavier View Post
The option CONFIG_FB_VESA=y in the RC kernel is causing NVIDIA's blob to spill the following error.
Code:
[   47.491112] NVRM: Your system is not currently configured to drive a VGA console
[   47.491114] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   47.491116] NVRM: requires the use of a text-mode VGA console. Use of other console
[   47.491117] NVRM: drivers including, but not limited to, vesafb, may result in
[   47.491118] NVRM: corruption and stability problems, and is not supported.
For some unknown reason, vesafb stopped working with the newest versions of the blob. Reference is there.
http://www.nvnews.net/vbulletin/show...6&postcount=39

I'm pretty ignorant as to deciphering what all that means and the error message seems harmless to me, just thought I should mention it.
I noticed this as well with 30x.y blobs. However, it does not seem to effect performance. I play a lot of 3D games both native and via WINE. Stellarium and Celestia also seem fine.

YMMV. The only box I have with a Nvidia GPU at the moment is a desktop and I run it in "space heater mode" i.e. full power: sleep/suspend == turn of both monitors, hibernation == turn off box.
 
Old 08-15-2012, 07:54 PM   #115
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
There is a bug in the java slackBuild. If your CWD has a space in the path the script will not execute properly. Pretty much where ever that variable is used there is a potential problem.

For instance, this line will fail
Code:
for file in $(ls $CWD/profile.d/${PKGNAM}*) ; do
leaving no profile.d scripts to change permissions on
Code:
chmod 755 $PKG/etc/profile.d/*
This will fail, too.
Code:
cat $CWD/slack-desc.${PKGNAM} > $PKG/install/slack-desc
 
Old 08-15-2012, 08:03 PM   #116
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 728

Rep: Reputation: 168Reputation: 168
Quote:
Originally Posted by shadowsnipes View Post
If your CWD has a space in the path...
I would say this is the bug.

I'm kidding, I'm kidding! :-)
 
2 members found this post helpful.
Old 08-15-2012, 08:27 PM   #117
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,276

Rep: Reputation: 686Reputation: 686Reputation: 686Reputation: 686Reputation: 686Reputation: 686
It could be fixed by quoting but I tend to agree with Alien Bob:
Quote:
Originally Posted by Alien Bob View Post
Using spaces in directory names is not supported by Slackware's scripts. I also do not support it in any of my own scripts. I even have a script (massconvert32.sh) which aborts when it detects a space in the directory name.

Spaces in directory names is an abomination introduced by MS Windows and lazy-ass GUI programs. Real UNIX men avoid space.

Last edited by T3slider; 08-15-2012 at 08:28 PM.
 
4 members found this post helpful.
Old 08-15-2012, 08:30 PM   #118
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 523

Rep: Reputation: 140Reputation: 140
I have loathed spaces in file names since the dawn of time. 8.3 characters is enough for any file name.
 
Old 08-15-2012, 09:27 PM   #119
clifford227
Member
 
Registered: Dec 2009
Distribution: Slackware 14
Posts: 282

Rep: Reputation: 64
I.think.periods.look.cooler.than.spaces.anyway.
 
Old 08-15-2012, 09:38 PM   #120
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 728

Rep: Reputation: 168Reputation: 168
Quote:
Originally Posted by clifford227 View Post
I.think.periods.look.cooler.than.spaces.anyway.
I_prefer_underscores.
 
1 members found this post helpful.
  


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
Bug reports, using them microsoft/linux Debian 1 10-12-2005 07:22 AM
bug reports with apt-get MaTrIx709 Debian 2 07-27-2005 06:05 PM
bug reports on glibc or gcc tvburger Linux From Scratch 1 12-06-2004 12:43 AM
10.1 Beta Cycle Begins, send those bug reports in ! doug_s Mandriva 0 07-24-2004 09:34 AM
How to submit bug reports to Mandrakesoft? registering Mandriva 2 06-04-2004 09:32 AM


All times are GMT -5. The time now is 09:46 PM.

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