Wary 0.9.8 (098) feedback

[shinobar]

@Zigbert
Can be off-topic but may be relating with the '.utf8' or '.UTF-8' issue.

You are the pioneer of NLS on Puppy. So, i'd like you to know this.
We need to make many symbolic links for the NLS of your applications.

I'd like to recommend you shifting to the gettext system.

[zekebaby]

Every so often (once every 4 or 5 boots) I completely lose sound. Rerunning alsaconf reports "No supported PnP or PCI card found". lsmod shows snd_intel8x0 is still loaded. Reboot clean with no warysave and sound is back. A couple of reboots later, it's gone again!!! This did not happen in 096 or 097.

Any ideas on how to get sound back without deleting my warysave? Thanks in advance!

[NinerSevenTango]

md5sum checked the iso after burning slow, it checks out.

Boot pfix=ram with wary-098.

lspci reports Atheros wireless card, same as in Quirky (in which wireless works).

Doesn't matter which network wizard is used. Tried the simple one and the classic one.

Access points are detected. Attempting to connect to an open, unencrypted access point fails. Rebooting, multiple attempts, can not establish connection.

This is a Toshiba Satellite Pro s300-1511 laptop. This is the first time it's failed to work on wireless. Other OS versions that work: 4, Lucid, Quirky, other Linii, XP, Vista.

Any suggestions?

--97T--
The reason the room turns dark when you read my posts is because I have a black cloud that follows me around whenever I play with Linux!

[rerwin]

Wireless modem users,
I have updated the mode switcher to better coordinate with driver module loading. The script may initially find the device not quite ready to be recognized, so quits. Normally, it indicates its completion so that the modem initialization scripts can work reliably. A second execution of it then finds everything ready and proceeds with switching - but that may occur after the scripts have determined the modem to use.

Pusbmodeswitch already does not indicate completion if two particular error messages appear. The fix merely adds about 6 more messages that will delay the indication of completion, improving the dependability of wireless modem detection.

The update package is here: http://www.murga-linux.com/puppy/viewto ... 639#467639
Richard

[rerwin]

Every so often (once every 4 or 5 boots) I completely lose sound. Rerunning alsaconf reports "No supported PnP or PCI card found". lsmod shows snd_intel8x0 is still loaded. Reboot clean with no warysave and sound is back. A couple of reboots later, it's gone again!!! This did not happen in 096 or 097.

Any ideas on how to get sound back without deleting my warysave? Thanks in advance!

Thanks for your report. It might be related to Barry's and my adjustments to the timing of alsa sound card detection. We are trying to do better than guessing at a fixed delay for the worst case. It is a race between the sound driver getting started and the alsa script trying to use the driver.

We try to avoid an excessive delay due to other activities that slow things down, so the two barks can occur soon after bootup. Now the alsa script runs slightly earlier than before, but waits for the sound driver to get loaded. The update package mentioned in my previous message here, should further speed up the two barks.

However, if the alsa script starts too early, that might be before the driver even gets initiated by an "event". So, we need to do more tuning.

You could help by installing the update package (now -3) and see if it changes the likelihood of getting sound. It might make things worse, due to the speed-up, but we need to know that. After you try that, I can guide you to adjusting a time value to see if we can delay the script just enough to reliably wait for the initiation of module loading.

Thank you any assistance you can provide.
Richard

[Sage]

Yes, I've discovered the strange no-sound features on some boards. Sometimes (rarely) it is accompanied by absence of the help panel and, ipso facto, no barks - even when barks is normally working on other chassis. The muted sound is a real nuisance, too. Everything was just fine up to 098 (except barks switched off in 096). Seems to me that all this juggling to suit one odd report destroys a previously sound and stable OS. Like my weird ATI939 board, I'd recommend folks with one non-standard behaving system to change it! Not as if there aren't boxloads of 1GHz boards available gratis just for the asking - (how many do you need? - ask me!). These are entirely suitable for a compact distro. Unfortunately, there have to be compromises and expedients in a 120Mb .iso. For dissatisfied folks with go-faster systems, I'd recommend Linux Mint.
I guess to a lesser extent, the same comments are true with all this Winmodem business. If you've been unlucky and got a Conexant or whatever, bin it, PM me and I'll send you one that works. Otherwise, a lot of clever guys are wasting their intellectual effort trying to run kit that was intended for the rogue OS.

[Karl Godt]

That is the fix in the LupQ at the script /usr/local/jwmconfig2/taskbar.

booting lupq-511 I found it !

I also found the template :
It is inside gtk2jwm itself !
lines ~ 98 -148; line 105 : <Corner>white</Corner> ; line 111 : <Corner>#aaaaaa</Corner> ;
changed to <!-- <Corner>white</Corner> --> ; <!-- <Corner>#aaaaaa</Corner> -->

With the 'Or, applay current GTK theme' I can think of two solutions :
1.: 'Or, applay default GTK theme'
2.: 'Or, applay last GTK theme from backup' , which would require some "cp FILE FILE.bak" lines:

Code: Select all

--- /mnt/sdc7/usr/local/jwmconfig2/theme_switcher	2009-10-09 15:01:02.000000000 +0800
+++ /mnt/+mnt+sdc7+luma002+lumasave-MAINluma002.3fs/usr/local/jwmconfig2/theme_switcher	2010-11-18 09:43:11.000000000 +0800
@@ -48,8 +48,10 @@
 
 if [ "$NEWTHEME" != "" ];then
  #select chosen theme...
+ cp -f /root/.jwm/jwmrc-theme /root/.jwm/jwmrc-theme.bak
  cp -f /root/.jwm/themes/${NEWTHEME}-jwmrc /root/.jwm/jwmrc-theme
  #set correct backgrounds for applets...
+ cp -f /root/.jwm/jwm_colors /root/.jwm/jwm_colors.bak
  cp -f /root/.jwm/themes/${NEWTHEME}-colors /root/.jwm/jwm_colors
  #...note, /root/.xinitrc reads this file to set background for absvolume.
  #...note, jwm_colors is written to by /usr/local/jwmconfig2/gtk2jwm script

the whole gtk2jwm would look like :

Code: Select all

--- /usr/local/jwmconfig2/gtk2jwm	2008-01-24 06:34:22.000000000 +0800
+++ /mnt/+mnt+sdc7+luma002+lumasave-MAINluma002.3fs/usr/local/jwmconfig2/gtk2jwm	2010-11-18 09:37:51.000000000 +0800
@@ -19,8 +19,8 @@
 
 ##-------------variables---------------->>
 		
-GTKTHEME=`fgrep 'include' /root/.gtkrc-2.0 | fgrep '/usr/share/themes/' | grep -v '^#' | fgrep -m1 'gtkrc' | tr -d "'" | tr -d '"' | sed 's/include //' | tr -d '\t' | tr -d ' '`
-[ ! -e $GTKTHEME ] && exit 1 
+# GTKTHEME=`fgrep 'include' /root/.gtkrc-2.0 | fgrep '/usr/share/themes/' | grep -v '^#' | fgrep -m1 'gtkrc' | tr -d "'" | tr -d '"' | sed 's/include //' | tr -d '\t' | tr -d ' '`
+# [ ! -e $GTKTHEME ] && exit 1 
 
 JWMTHEME=/root/.jwm/jwmrc-theme
 
@@ -32,23 +32,34 @@
 FULL_COLOUR=255
 
 ##------get relevant gtk colours-------->>
-MENU_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[NORMAL\]' | cut -d'"' -f2`
-ACTIVE_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[SELECTED\]' | cut -d'"' -f2`
-FOREGROUND=`grep -v "^#" $GTKTHEME | grep -m1 '\Wfg\[NORMAL\]' | cut -d'"' -f2`
-PAGER_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[ACTIVE\]' | cut -d'"' -f2`
-FG_SELECTED=`grep -v "^#" $GTKTHEME | grep -m1 '\Wfg\[SELECTED\]' | cut -d'"' -f2`
+# MENU_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[NORMAL\]' | cut -d'"' -f2`
+# ACTIVE_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[SELECTED\]' | cut -d'"' -f2`
+# FOREGROUND=`grep -v "^#" $GTKTHEME | grep -m1 '\Wfg\[NORMAL\]' | cut -d'"' -f2`
+# PAGER_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[ACTIVE\]' | cut -d'"' -f2`
+# FG_SELECTED=`grep -v "^#" $GTKTHEME | grep -m1 '\Wfg\[SELECTED\]' | cut -d'"' -f2`
+if test -f /root/.jwm/jwm_colors.bak ; then
+. /root/.jwm/jwm_colors.bak 
+fi
 
 #save them...
+# echo '#This is written to by /usr/local/jwmconfig2/gtk2jwm script' > /root/.jwm/jwm_colors
+# echo "MENU_BG='${MENU_BG}'" >> /root/.jwm/jwm_colors
+# echo "ACTIVE_BG='${ACTIVE_BG}'" >> /root/.jwm/jwm_colors
+# echo "FOREGROUND='${FOREGROUND}'" >> /root/.jwm/jwm_colors
+# echo "PAGER_BG='${PAGER_BG}'" >> /root/.jwm/jwm_colors
+# echo "FG_SELECTED='${FG_SELECTED}'" >> /root/.jwm/jwm_colors
 echo '#This is written to by /usr/local/jwmconfig2/gtk2jwm script' > /root/.jwm/jwm_colors
-echo "MENU_BG='${MENU_BG}'" >> /root/.jwm/jwm_colors
-echo "ACTIVE_BG='${ACTIVE_BG}'" >> /root/.jwm/jwm_colors
-echo "FOREGROUND='${FOREGROUND}'" >> /root/.jwm/jwm_colors
-echo "PAGER_BG='${PAGER_BG}'" >> /root/.jwm/jwm_colors
-echo "FG_SELECTED='${FG_SELECTED}'" >> /root/.jwm/jwm_colors
+echo "$MENU_BG" >> /root/.jwm/jwm_colors
+echo "$ACTIVE_BG" >> /root/.jwm/jwm_colors
+echo "$FOREGROUND" >> /root/.jwm/jwm_colors
+echo "$PAGER_BG" >> /root/.jwm/jwm_colors
+echo "$FG_SELECTED" >> /root/.jwm/jwm_colors
 
+if test -f /root/.tcl-gtk ; then
 rm -f /root/.tcl-gtk 
+fi
 if [ -z "$MENU_BG" ]; then
- echo > "$JWMTHEME"
+ # echo > "$JWMTHEME"
  pidof jwm >/dev/null && jwm -restart
  exit 2
 else 
@@ -102,13 +113,13 @@
 	<Active>
 		<Text>$FG_SELECTED</Text>
 		<Title>$ACT_GRAD</Title>
-		<Corner>white</Corner>
+		<!-- <Corner>white</Corner> -->
        	<Outline>black</Outline>
 	</Active>
 	<Inactive>
 		<Text>$FOREGROUND</Text>
 		<Title>$MEN_GRAD</Title>
-		<Corner>#aaaaaa</Corner>
+		<!-- <Corner>#aaaaaa</Corner> -->
        	<Outline>black</Outline>
 	</Inactive>
 </WindowStyle>
@@ -157,6 +168,7 @@
 TrayFileBak="/root/.jwmrc-tray.bak"
 
 BackgroundColor="$MENU_BG" #"#ffc100"
+echo $MENU_BG
 
 function GetLineIndex
 {
@@ -169,19 +181,23 @@
 
 GetLineIndex "blinkydelayed"
 linenumber=$?
-echo $linenumber
+# echo $linenumber
 
 GetLineIndex "xload -nolabel"
 linenumber2=$?
-echo $linenumber2
+# echo $linenumber2
 
 lineNumber=`expr $linenumber`
 lineNumber2=`expr $linenumber2`
 
 blinkyline="			blinkydelayed -bg \"$BackgroundColor\""
 xloadline="			xload -nolabel -fg red -hl white -bg \"$BackgroundColor\""
-
-sed -e "$lineNumber"i"$blinkyline" -e "$lineNumber"d -e "$lineNumber2"i"$xloadline" -e "$lineNumber2"d $TrayFileBak > $TrayFile
+if test $lineNumber -gt 0 ; then
+sed -e "$lineNumber"i"$blinkyline" -e "$lineNumber"d $TrayFileBak > $TrayFile
+fi
+if test $lineNumber2 -gt 0 ; then
+sed -e "$lineNumber2"i"$xloadline" -e "$lineNumber2"d $TrayFileBak > $TrayFile
+fi
 #end John Doe's code.
 ########

note : not tested much yet !

[zigbert]

I'd like to recommend you shifting to the gettext system.

What is the gettext system?

I didn't know there existed different uft8-formats .

gtkdialog seems to work best with uft8 (or is it UTF-8), so DE should be enough to determine language. I have stated for translators, that language-file should be uft8.

urxvt work with ÆØÅ when LANG=nb_NO.UTF-8 - Thank you


Sigmund

[ravensrest]

Below is a complete listing of Karl Godt's modified /usr/local/jwmconfig2/gtk2jwm file. His listing above appears to have a couple errors in it, and does not include the auto jwm restart. This one does. I have checked it on my system which has a modified jwmrc-tray and it works fine, but that is the extent of the testing. Save it as gtk2jwm, make it executable and try it.

Thanks, Karl

Code: Select all

#!/bin/bash
##########################
#
# gtk2jwm
# this script integrates
# the default jwm theme 
# with the current gtk 
# theme.
#
# author: thoughtjourney
# date: 28/08/2005
#
# Hacked BK Feb 2006 for JWM 1.4
# Abused by Dougal, Dec 2006
#########################
## Latest update: July 14th: add gradient support for JWM
# BK jan 2008: integrated into jwmconfig2.
#modified by Karl Godt 18 Nov 2010

 ##-------------variables---------------->>
       

 GTKTHEME=`fgrep 'include' /root/.gtkrc-2.0 | fgrep '/usr/share/themes/' | grep -v '^#' | fgrep -m1 'gtkrc' | tr -d "'" | tr -d '"' | sed 's/include //' | tr -d '\t' | tr -d ' '`
 [ ! -e $GTKTHEME ] && exit 1
 
 JWMTHEME=/root/.jwm/jwmrc-theme
 
 FULL_COLOUR=255
 
 ##------get relevant gtk colours-------->>
 MENU_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[NORMAL\]' | cut -d'"' -f2`
 ACTIVE_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[SELECTED\]' | cut -d'"' -f2`
 FOREGROUND=`grep -v "^#" $GTKTHEME | grep -m1 '\Wfg\[NORMAL\]' | cut -d'"' -f2`
 PAGER_BG=`grep -v "^#" $GTKTHEME | grep -m1 '\Wbg\[ACTIVE\]' | cut -d'"' -f2`
 FG_SELECTED=`grep -v "^#" $GTKTHEME | grep -m1 '\Wfg\[SELECTED\]' | cut -d'"' -f2`
if test -f /root/.jwm/jwm_colors.bak ; then
. /root/.jwm/jwm_colors.bak
fi
 
 #save them...
 echo '#This is written to by /usr/local/jwmconfig2/gtk2jwm script' > /root/.jwm/jwm_colors
 echo "MENU_BG='${MENU_BG}'" >> /root/.jwm/jwm_colors
 echo "ACTIVE_BG='${ACTIVE_BG}'" >> /root/.jwm/jwm_colors
 echo "FOREGROUND='${FOREGROUND}'" >> /root/.jwm/jwm_colors
 echo "PAGER_BG='${PAGER_BG}'" >> /root/.jwm/jwm_colors
 echo "FG_SELECTED='${FG_SELECTED}'" >> /root/.jwm/jwm_colors
 echo '#This is written to by /usr/local/jwmconfig2/gtk2jwm script' > /root/.jwm/jwm_colors

echo "$MENU_BG" >> /root/.jwm/jwm_colors
echo "$ACTIVE_BG" >> /root/.jwm/jwm_colors
echo "$FOREGROUND" >> /root/.jwm/jwm_colors
echo "$PAGER_BG" >> /root/.jwm/jwm_colors
echo "$FG_SELECTED" >> /root/.jwm/jwm_colors
 
if test -f /root/.tcl-gtk ; then
 rm -f /root/.tcl-gtk
fi
 if [ -z "$MENU_BG" ]; then
  echo > "$JWMTHEME"
  pidof jwm >/dev/null && jwm -restart
  exit 2
 else
  DEFAULT="
  <JWM>
  <WindowStyle>
    <Active>
       <Text>$FG_SELECTED</Text>
       <Title>$ACT_GRAD</Title>
       <!-- <Corner>white</Corner> -->
           <Outline>black</Outline>
    </Active>
    <Inactive>
       <Text>$FOREGROUND</Text>
       <Title>$MEN_GRAD</Title>
       <!-- <Corner>#aaaaaa</Corner> -->
           <Outline>black</Outline>
    </Inactive>
 </WindowStyle>
 </JWM>"
 fi
 TrayFileBak="/root/.jwmrc-tray.bak"
 
BackgroundColor="$MENU_BG" #"#ffc100"
echo $MENU_BG
 
function GetLineIndex
{
	lineVal=`fgrep -in "$1" $TrayFile | awk -F":" '{print $1}'`
	#return `expr $lineVal`
	return $lineVal
}

 GetLineIndex "blinkydelayed"
 linenumber=$?
 echo $linenumber
 
 GetLineIndex "xload -nolabel"
 linenumber2=$?

 echo $linenumber2
 
 lineNumber=`expr $linenumber`
 lineNumber2=`expr $linenumber2`
 
 blinkyline="         blinkydelayed -bg \"$BackgroundColor\""
 xloadline="         xload -nolabel -fg red -hl white -bg \"$BackgroundColor\""
if test $lineNumber -gt 0 ; then
sed -e "$lineNumber"i"$blinkyline" -e "$lineNumber"d $TrayFileBak > $TrayFile
fi
if test $lineNumber2 -gt 0 ; then
sed -e "$lineNumber2"i"$xloadline" -e "$lineNumber2"d $TrayFileBak > $TrayFile
fi
 #end John Doe's code.
 ########
  
sync
pidof jwm >/dev/null && jwm -restart

[DaveS]

Ravenrest... tried the above and it did not bork the tray, but it did not change the theme either

[bigpup]

ATI is not supporting all video cards with the newest drivers.

ATI web site for what they are calling legacy video drivers.
http://support.amd.com/us/gpudownload/l ... ng=English
Really old stuff here
http://support.amd.com/us/gpudownload/l ... linux.aspx

[CatDude]

Hi

Is this the 'ROX focus bug' or something else ??

What i am about to describe, i can reproduce over and over again (without fail).

Step 1.

• Open a ROX window (i clicked on the desktop 'file' icon)
  
  Now Right-click on the desktop to bring up the main Menu,
  followed by either a Left-click or Right-click on the desktop to get rid of the Menu.

Step 2.

• Next, Right-click inside of the open ROX window (anywhere below the titlebar, yes, even on the toolbar),
  and you should get the main Menu appear and not the ROX menu.
  
  Either Left-click or Right-click anywhere (ROX window, Desktop, wherever) to get rid of the menu,
  then go and click on one of the Desktop Icons (it does nothing), the next click does though.
  
  NOTE:
  If after doing Step 1.
  you go and Right-click on the ROX wiindow titlebar, you get the expected menu,
  but if you then continue as in Step 2, the behaviour is still as explained in Step 2.

Whatever it is,
it seems like the fix suggested by upnorth (amongst others) does the trick.
Edit: /usr/local/bin/rox
from this:

Code: Select all

#!/bin/sh
exec /usr/local/apps/ROX-Filer/AppRun "$@"

To this:

Code: Select all

#!/bin/sh
export GDK_NATIVE_WINDOWS=true
exec /usr/local/apps/ROX-Filer/AppRun "$@"

Restart X server, and things behave as one would expect.

I noticed that Sit Heel Speak had a similar experience in Wary-096,
although he said he could not reproduce it after making a fresh install (Frugal).

Well, i get the exact same behaviour in BOTH Wary-096 and 098,
and as i said above, i can reproduce it at will.

CatDude
.

[ravensrest]

Ravenrest... tried the above and it did not bork the tray, but it did not change the theme either

Dave, I just copied it off my post to /usr/local/jwmconfig2/gtk2jwm. Worked perfectly. Did you change it to executable before trying to run it?

If you did, then please run it within rxvt and let me know if you get any errors.

BS

[rjbrewer]

Whatever it is,
it seems like the fix suggested by upnorth (amongst others) does the trick.


CatDude
.

Yes; I was having same problems, plus:

Clicking an icon (with mouse or touchpad) would often not start
the app on the first try.

Right clicking drive icons would open menu unless I mounted
and closed the window first.

[rerwin]

zekebaby,
To try to fix your problem with unreliable detection of the sound card. I have updated my fix package (to "-4"), that should avoid having ALSA initialization "jump the gun" in checking for sound drivers. Please install it and try your multiple re-boots, to see if it makes detection reliable. The fix is here: http://www.murga-linux.com/puppy/viewto ... 639#467639

If you still see the problem, please run pmodemdiag (in a console) soon after completion of the bootup and as soon as you know there is a problem. Then post or PM-me the pmodemdiag...tar.gz file it generates. That would help me understand the nitty-gritty of what is going on. Thanks.
Richard

[shinobar]

I didn't know there existed different uft8-formats.

@zigbert and Barry:
They are not different format or encoding, but the issue of the name of locale.
You found both 'LANG=nb_NO.utf8' and 'LANG=nb_NO.UTF-8' works as for the Gtk applications, but some X applications like urxvt require 'LANG=nb_NO.UTF-8'.
Most of Linux distributions are using '.UTF-8', and some applications assume it.

@zigbert
As for the gettext:
See http://tldp.org/LDP/abs/html/localization.html,
and visit the topic 'Translate LupQ':
http://www.murga-linux.com/puppy/viewtopic.php?t=59142

[rerwin]

Deleted. Posted to wrong thread.

[fluxit]

I've been unable to get GL acceleration working with the radeon driver with an X1300 on Wary(including 0.9.8.) I've attached my Xorg log. Note these sections:

Code: Select all

(==) RADEON(0): Using XAA acceleration architecture
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"

Code: Select all

(II) RADEON(0): Direct rendering enabled
(II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead.
(II) RADEON(0): Render acceleration disabled

Code: Select all

(EE) AIGLX error: Calling driver entry point failed(EE) AIGLX: reverting to software rendering

On quirky 1.3 I have acceleration working, and it is using EXA instead of XAA.

I am booting the live-CD with pfix=ram and installing mesa-6.5.2-w5.pet which is the only mesa that shows up in Puppy Package Manager.

[Sit Heel Speak]

Something I've spotted, maybe interesting. I can't help but wonder whether this explains a whooo-o-le lotta problems that have been reported with both Intel and Radeon cards, when attempting acceleration.

My plan to issue Catalyst .pet's is on hold until a couple of problems are solved, which I've deduced are due to wary-098 carrying a not-good-enough mesa+glut combination. And so I have begun stepping through the mesa+glut versions, to find one to graft-in that works.

The first two dependencies lacking in wary-098 for compiling mesa+glut, according to http://www.mesa3d.org/install.html, are dri2proto (totally absent from wary-098 even with the devx) and libdrm. mesa needs to be compiled under at least libdrm-2.4.15, but wary-098 carries only libdrm-2.3.0.

So, first I compiled dri2proto-2.3 --hehe, amigo's new2dir is the best thing since sliced silicon-- and then started to compile libdrm-2.4.22 (the latest). For libdrm I used this ./configure line:

Code: Select all

./configure --prefix=/usr/X11R7 --build=i486 --host=i486  --enable-static=yes --enable-vmwgfx-experimental-api --enable-nouveau-experimental-api --with-gnu-ld

and got these warnings

configure: WARNING: Disabling libdrm_intel. It depends on atomic operations, which were not found for your compiler/cpu. Try compiling with -march=native, or install the libatomics-op-dev package.
configure: WARNING: Disabling libdrm_radeon. It depends on atomic operations, which were not found for your compiler/cpu. Try compiling with -march=native, or install the libatomics-op-dev package.

and the end result was:

config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

libdrm 2.4.22 will be compiled with:

libkms no
Intel API no
vmwgfx API yes
Radeon API no
Nouveau API yes

Well! I certainly don't want to build mesa under a libdrm which was built without libatomics-op-dev!

Now to look into this "libatomics-op-dev package" thing-y...

[Sage]

Well spotted bigpup. The takeover of ATI was accompanied by a pile of problems, although they were in the mire technically before that and things have not got better since. But what to do? Let's hope BK can handle the plethora of driver requirements without asking punters to load/unload masses of code.