VIA Unichrome for Puppy 3?

Problems and successes with specific brands/models of computer video hardware
Message
Author
Matt
Posts: 9
Joined: Mon 15 Oct 2007, 10:57

VIA Unichrome for Puppy 3?

#1 Post by Matt »

I can't get graphics acceleration to work on my eBox using Puppy 3.01. Does anyone have a solution to this?

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#2 Post by tempestuous »

I'm not sure if MU's 3D Control Centre supports Puppy 3
http://www.murga-linux.com/puppy/viewtopic.php?t=14463

but if not, you can set things up manually. First download and install xorg_OPENGL-7.2.pet from
http://distro.ibiblio.org/pub/linux/dis ... ackages-3/

Now open /etc/X11/xorg.conf in geany
In Section "Module" make sure these lines are included (and not commented out)

Code: Select all

Load "dri"
Load "glx"
In Section "Device" check the the Driver value is "via"

Code: Select all

Driver "via"
In Section "Screen" check that DefaultDepth is 16, because sometimes 3D fails at higher bit depths.
Now reboot, or just restart X. Run "lsmod" and check that these 2 modules are loaded -
via
via_agp

Matt
Posts: 9
Joined: Mon 15 Oct 2007, 10:57

#3 Post by Matt »

I'm pretty sure 3DCC doesn't support Puppy 3, but I use it to try the 3D-demo. X use to crash when trying that, but after installing xorg_OPENGL-7.2.pet at least it doesn't crash. This time the monitor is flickering and I can make out a window there where I guess the 3D demo should be visible. Getting close, but not there yet.

I already had "dri" and "glx" in the module-section. "via" in the device section too.

But like I said: Still not there.

Matt
Posts: 9
Joined: Mon 15 Oct 2007, 10:57

#4 Post by Matt »

Oh... forgot to mention I got both those modules listed in lsmod.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#5 Post by tempestuous »

MU's 3D demo is very complex, and might not work with onboard graphics devices.

I suggest you install glxgears-pup1x.pup as I mentioned in this other thread
http://www.murga-linux.com/puppy/viewto ... 008#145008

then run "glxinfo". If it reports "direct rendering: Yes" then that means success.
Also run "glxgears". When you exit this test (with Esc key, I think) it will report frame rate.

Matt
Posts: 9
Joined: Mon 15 Oct 2007, 10:57

#6 Post by Matt »

tempestuous wrote:MU's 3D demo is very complex, and might not work with onboard graphics devices.

I suggest you install glxgears-pup1x.pup as I mentioned in this other thread
http://www.murga-linux.com/puppy/viewto ... 008#145008

then run "glxinfo". If it reports "direct rendering: Yes" then that means success.
Also run "glxgears". When you exit this test (with Esc key, I think) it will report frame rate.
I got direct rendering according to glxinfo, but glxgears fails with this:

Code: Select all

__driCreateNewScreen_20050727 - succeeded
glxgears: Error: Requested window size (300/300) larger than maximum supported by GL engine (0/0).
[/code]

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#7 Post by tempestuous »

I seem to remember that I compiled glxgears as part of Mesa (OpenGL) under Xorg 6.8.1, so there might be some incompatibilities with OpenGL under Xorg 7.2.

One thing I forgot to mention, certain 3D functions (such as XvMC acceleration) require a certain amount of RAM to be available to the onboard graphics device, and this is set in bios.
Get into bios and allocate at least 32MB to graphics. If you don't know how to get into bios, send pakt a PM, he knows how to do this with an eBox.
It may also be necessary to specify the RAM value in xorg.conf, under Section "Device"

Code: Select all

VideoRam 32768
After restarting X, there may be some critical information contained /var/log/Xorg.0.log
You may see reference to libdrm, which I seem to remember is very important.

Ultimately, your aim is not to run glxgears. See how your system works with everyday tasks.
One of the first things I noticed with accelerated graphics was that text in Geany scrolled really fast when I used the search funtion.

Matt
Posts: 9
Joined: Mon 15 Oct 2007, 10:57

#8 Post by Matt »

Thanks tempestuous :) VideoRam 32768 fixed it, but I can only reach close to 18 fps which I take it is maximum for the eBox 3851 I'm using.

And btw... gxine fails to run on my eBox (Details: serial 369 error_code 11 request_code 139 minor_code 19) Don't know if that's related, but probably is.

Thanks again

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#9 Post by tempestuous »

Matt wrote:I can only reach close to 18 fps which I take it is maximum for the eBox 3851 I'm using.
Actually, that sounds terrible.
With an older version of Puppy on a VIA Epia ML8000A with almost identical specs to your eBox-3851 (800Mhz, CLE266) I got 90fps without DRI, and 500fps with DRI enabled.

Your results are so bad I suspect glxgears is at fault. It's part of the Mesa library, so I suspect there is an incompatibility with my glxgears version and Xorg 7.2.

If someone with Slackware 12 could provide glxgears as a dotpet, that would be useful.
... plus glxinfo and xdriinfo, please.

Matt
Posts: 9
Joined: Mon 15 Oct 2007, 10:57

#10 Post by Matt »

tempestuous wrote:Your results are so bad I suspect glxgears is at fault. It's part of the Mesa library, so I suspect there is an incompatibility with my glxgears version and Xorg 7.2.

If someone with Slackware 12 could provide glxgears as a dotpet, that would be useful.
... plus glxinfo and xdriinfo, please.
Yes, please! I'm sort of stuck at 18 fps since I don't have a full development environment myself.

tony
Posts: 334
Joined: Sat 14 Jan 2006, 10:52
Location: Montreal.ca

Unichrome Plus Flightgear

#11 Post by tony »

Hi tempestuous,

Thanks for all the tips on the Unichrome. I followed them and finally typed Load "dri" into /etc/X11/xorg.conf. Restarted xwindows and glxinfo came back with direct rendering :yes.

However typing into xorg.conf is only a temporary solution as it is overwritten by xwin if you change the screen configuration.

I can actually use Flightgear now with the video breaking up at the edges.

I will have to find out how to increase on board video memory for my Assus A7V/400 computer.

Regards Tony

giac_fab
Posts: 113
Joined: Thu 25 Jan 2007, 23:15

#12 Post by giac_fab »

It works also for me but everytime i use my video-card a little bit ( also with a light mame-game) processor works at 100% .... my fps is about 170
:oops: I know, my english is very bad :oops:
Give a man a fish and he eats for a day, teach a man to fish and he eats for a lifetime.

nosignal
Posts: 8
Joined: Mon 07 Apr 2008, 14:07

VIA Unichrome II in Puppy3 -no acceleration after trying all

#13 Post by nosignal »

The short of it is that I have not had any luck. I think I have tried everything available on the forums, and a bit extra. I hope my log of what I did will make sense.

I would dearly love to get this Norhtec Microclient SR box with VIA CX700 / Unichrome II working propoerly. Fingers crossed:

Code: Select all

Installed:
  - xorg_DRI_MODULES-7.2.pet                      26-Sep-2007 10:20   11M  
    - Actually in a puppy 3 folder, and forums talking of use with puppy 3
  - xorg_OPENGL-7.2.pet                           26-Sep-2007 10:20  972K  
    - the one needed for OpenGL. But only gives Mesa on its own.


Added:
VideoRam 65536
to
/etc/X11/xorg.conf
/etc/X11/xorg.conf.VIA_CX700

Installed geany
- text seems to scroll very fast.
- terminal - geany

Puppy-Software-Installer.pup installed. visible in 
/usr/local/Puppy-Software-Installer
Installed it.
Start->Settings->PSI

MPlayer-1.0rc2-unichrome.pet	  5244617   	15.03.08, 11:13
http://dotpups.de/puppy3/dotpups/Multimedia/
I installed with error:
mplayer has missing these library files:
libfribidi.so.0
PETget does not know what package has these libraries.
Start->Multimedia->MPlayer
>>Doesn't work

Installed 3dcc:
getdir.pup
Gtklist04MU.pup
3DCC-Puppy-2.12-and-2.13.pup
to /usr/local/3DCC
Start->Settings->3DCC
>> 3D Demo: DRI not active - should run <10fps

Unzipped glxtools
Ran glxgears:
- Xlib:  extension "GLX" missing on display ":0.0".

As per http://www.murga-linux.com/puppy/viewtopic.php?search_id=391200353&t=22933
(VIA Unichrome for puppy 3)
Installed xorg_OPENGL-7.2.pet
Added 
# This loads DRI - added by Eric
    Load       "dri"
...
	### Eric added this:
	Driver      "via"
	### Eric removed this BUT xwin then fails:
	Driver      "vesa" #card0driver
to 
/etc/X11/xorg.conf
/etc/X11/xorg.conf.VIA_CX700
>> xwin would not load
- VideoRam not the problem
- Load "dri" not the problem
- Driver "via" - IS a problem if:
  - after existing Driver line
  - if existing Driver line is commented out
>>>> SO, probably can only have one 'Driver' at once, and "via" fails.
>>'lsmod |grep via' produces:
i2c_viapro              9236  0 
i2c_core               22032  1 i2c_viapro
via_agp                10240  0 
agpgart                34128  1 via_agp
NOT
via 
via_agp (it has got this)
as expected
>> /var/log/Xorg.0.log  contains:
libdrm - no reference
XvMC - no reference
drm - no reference
dri:
(near start)
 (II) LoadModule: "dri"
 (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
 (II) Module dri: vendor="X.Org Foundation"
	compiled for 1.3.0, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
 (II) Loading extension XFree86-DRI
... (near end)
 (II) Setting vga for screen 0.
 ...
 (II) Initializing built-in extension XEVIE
 (EE) AIGLX: Screen 0 is not DRI capable
via:
 (II) VESA(0): VESA VBE OEM: VIA CX700
 (II) VESA(0): VESA VBE OEM: VIA CX700
glx:
 (II) LoadModule: "glx"
 (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
 (II) Module glx: vendor="X.Org Foundation"
	compiled for 1.3.0, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
 (==) AIGLX enabled
 (II) Loading extension GLX
...
 (EE) AIGLX: Screen 0 is not DRI capable
 (II) Loading local sub module "GLcore"
 (II) LoadModule: "GLcore"
 (II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
 (II) Module GLcore: vendor="X.Org Foundation"
	compiled for 1.3.0, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
 (II) GLX: Initialized MESA-PROXY GL provider for screen 0
>>>> So DRI not loading? and Mesa loading?
>>>> So no XvMC? and software OpenGL? 

glxgears = 60-70fps
glxinfo has numerous mentions of MESA
>>>> Confirms Software OpenGL

3DCC - 3D Demo: 
- DRI not active - should run <10fps
- runs under 4fps
>>>> confirms DRI has failed.

Uninstalled xorg_OPENGL-7.2.pet
- to do it in 'right' order.
Installed xorg_DRI_MODULES-7.2.pet
Installed xorg_OPENGL-7.2.pet
Installed sdl-1.2.11.pet
- 5 SDL files has a missing library: libvga.so.l
Restarted

Did it work? Do I have via, DRM and OpenGL?

>>'lsmod |grep via' produces:
i2c_viapro              9236  0 
i2c_core               22032  1 i2c_viapro
via_agp                10240  0 
agpgart                34128  1 via_agp
NOT
via 
via_agp (it has got this)
as expected
>>>> No via (though the xorg.conf is not ideal).

glxgears still about 60fps.
>>>> No 3D.

how do find out if opengl its already activated?
You could look and see if these files exist: 
/usr/X11R7/lib/xorg/modules/extensions/libGLcore.so 
/usr/X11R7/lib/xorg/modules/extensions/libglx.so 
If not, you probably don't have OpenGL installed yet.
>> I have both of these.

setup 3D accel in puppy 3.01:
install wNOP, it has it all done already
- its a whole separate iso install

setup 3D accel in puppy 3.01:
in /etc/X11/xorg.conf 
Find the values: 
# Option "DRI" # [<bool>] 
# Option "NoAccel" # [<bool>] 
Change These to (or add): 
Option "DRI" "True" 
Option "NoAccel" "False" 
It should go inside the "Modules" section. 
While you're in there, you might need to enabled GLX if you installed OpenGL.

Manual install of compiz - and getting 3D accelleration.
http://www.murga-linux.com/puppy/viewtopic.php?p=151018
- a very good, detailed instructions.
T test if DRI is working:
After installing glxinfo and typing - Code:
glxinfo | grep dri 
at the command line will tell you whether DRI is active and 
if it is not, typing - Code:
cat /var/log/Xorg.0.log | grep dri
may give you some idea as to why.
>> no mention of dri in glxinfo
>> Xorg.0.log mentions dri module loaded, but vesa driver - yuck?
To Install DRI and 3D properly:
Install
- xorg_DRI_MODULES-7.2.pet 
- xorg_OPENGL-7.2.pet
>> done
Fix glich in /usr/sbin/findhostbridge and find line 97 - replace
shell("ls /lib/modules/2.6/char/agp/*.ko>/tmp/findhostbridge.tmp")
with
shell("ls /lib/modules/2.6/kernel/drivers/char/agp/*.ko>/tmp/findhostbridge.tmp")
>> done
add this line to /etc/rc.d/rc.local: - Code:
modprobe sis_agp
>> my 'via_agp' loads, but 'via' doesn't. So I've tried loading 
modprobe via
>> done
For these fixes to take effect a FULL REBOOT is needed!
>> done
In order to activate 3D accelaration, add to /etc/X11/xorg.conf - Code:
Load "glx" 
Load "dri"
within the section indicated by: - Code:
Section "Module" 
... 
EndSection
>> done
>> no better 3D results.
essential for Compiz are: the addition of: - Code:
Option "AIGLX" "true"
within: - Code:
Section "Server Layout" 
... 
EndSection
>> done
the addition of this code at the end of xorg.conf: - Code:
Section "Extensions" 
    Option "Composite" "Enable" 
EndSection
Still 60fps in glxgears, and glxinfo crashes xwin - dumps me in terminal

nosignal
Posts: 8
Joined: Mon 07 Apr 2008, 14:07

My previous post explained

#14 Post by nosignal »

Apologies about my last post - it was 3am after about 20hours of frustration, so I wasn't thinking the straightest. I think I left out a couple of important sentences.

I got a Norhtec Microclient SR box with VIA CX700 / Unichrome II which was very exciting. I got NOP Puppy 3.01r5 working ok, but without 3D or video acceleration, which I need for the project I am doing (video acceleration is more important).

I have read countless forums about this, and tried a number of things. But the essence of it is I have installed xorg_DRI_MODULES-7.2.pet and xorg_OPENGL-7.2.pet, resulting in no 3D or video acceleration. I tried a few tweaks here and there, as documented above, which made little difference. So I am pretty stuck, and would appreciate some help on this.

I think my main problem is that when I include 'Driver "via"' in xorg.conf, xwin fails to start, and I have to remove that line from the terminal. This could be linked to 'lsmod | grep via' not showing a line just called 'via' (it has other lines with via in them), although I have added 'modprobe via' to rc.local, which has made 'via' appear in lsmod, but has not helped any accelleration.

My other, smaller challenge is knowing when acceleration is enabled. With a combination of 3DCC's 3D demo, glxinfo, glxgears, lsmod and looking at 'Xorg.0.log' I get a rough idea, but its not black and white (especially with XvMC video acceleration).

Any ideas yould be greatly appreciated.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

Re: My previous post explained

#15 Post by tempestuous »

nosignal wrote:I think my main problem is that when I include 'Driver "via"' in xorg.conf, xwin fails to start
Yes, that's the core of your problem. There's no point adding 3D drivers until the "via" Xorg driver is working.
"vesa" is a generic Xorg driver, and is not capable of 3D acceleration.

VIA seems to constantly update their Unichrome graphics chips, and the Xorg/Openchrome developers are always playing catch-up. I suggest you move up to Puppy4, which will take you from Xorg7.2 to Xorg7.3.
Generally, though, your installation process is correct. The steps are -
- get Xorg running with Driver "via"
- install xorg_DRI_MODULES and xorg_OPENGL. For Puppy4 this means Xorg7.3. It would be worth doing a forum search on this, because at one stage kirk contributed updated Xorg and OpenGL libraries for Puppy4.
- modify /etc/X11/xorg.conf to enable 3D
- install 3dcc
Restart X or reboot, then run "glxinfo". Hope that you see "direct rendering: Yes"
- install MPlayer1.0rc2-unichrome, and launch it from the commandline with the correct xvmc parameters. If the video plays, all is well. If it fails, you will see various error messages on the commandline.

If you are hell-bent on sticking with Puppy3, then you are faced with the arduous task of compiling the very latest via Xorg driver from the OpenChrome Project - www.openchrome.org
This is a serious undertaking. It would require
- install Puppy3 developer tools
- install Puppy3 kernel source
- install Xorg7.2 sources
- compile OpenChrome via driver, plus via drm module, plus libdrm, plus OpenGL

nosignal
Posts: 8
Joined: Mon 07 Apr 2008, 14:07

can I manually load the via module earlier

#16 Post by nosignal »

Hi tempestuous, thanks for your help.

I am not hell bent on puppy 3.01, but I do want to try one more thing before giving up on it.

When I do 'lsmod | grep via', I get

Code: Select all

i2c_viapro              9236  0 
i2c_core               22032  1 i2c_viapro 
via_agp                10240  0 
agpgart                34128  1 via_agp 
NOTE: it does not have plain 'via' loaded, just 'via_agp'.

So I tried 'modprobe via', which seemed to work. Then 'lsmod | grep via' showed plain 'via' loaded, and also showed 'drm' loaded, using the 'via' module. I take this as a good sign, as I beleive DRM is related to hardware acceleration.

However, this didn't seem to change my test results. I can only assume that is because 1) I am barking up the wrong tree, or 2) I am not loading the via module early enough. I prefer to think it is 2) :). So I added 'modprobe via' to to rc.local, which has made 'via' appear in lsmod, but has not helped any accelleration.

Should I have the via module loaded somewhere earlier, or is it more likely that the via module just doesn't have what it takes to accelerate my cx700 chipset?

nosignal
Posts: 8
Joined: Mon 07 Apr 2008, 14:07

Puppy 4

#17 Post by nosignal »

Hi again.

I have had a good look for anything to do with Puppy4 and xorg. I can't find a user called kirk. I can't find any useful forum regarding Xorg7.3. I can't find Puppy4 (aka 'puppy-4.00-seamonkey.iso') either, even though it is referenced in a couple of places. The best I can find is Puppy4 beta 1 (aka 'puppy-3.98-seamonkey.iso') at http://distro.ibiblio.org/pub/linux/dis ... -4.00beta/
I did find 'xorg_xvesa-7.3.pet' at ftp://ibiblio.org/pub/linux/distributio ... ackages-4/

So is 'puppy-3.98-seamonkey.iso' and 'xorg_xvesa-7.3.pet' what you had in mind? It sounds like it involves a little more than just installing the pet. Is the process described under 'Puppy4, Alpha3' below, what you recalled?

I thought I'd post my research results below. Quite a few interesting tidbits there.

Everything I could find regarding the latest puppy 4 (up to 10-April-2008):

Code: Select all

Puppy 4.00beta1 - April 5, 2008
beta1 now available. Called  'puppy-3.98-seamonkey.iso'. Available from http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.00beta/
The release notes are here: http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.00beta/release-4.00b.htm
The release notes say: "Version 4.00 is happening ... here it is: the live-CD file is 'puppy-4.00-seamonkey.iso' and is just 83.3MB. Download from http://puppylinux.com/download/."
- BUT I can't find 'puppy-4.00-seamonkey.iso' there ?! But the 'test' folder has the 'puppy-4.00beta' folder, leading to puppy-3.98-seamonkey.iso
Everything I could find regarding Xorg in Puppy 4 in the Development Log (up to 10-April-2008):

Code: Select all

(Development Log by version: http://puppylinux.com/news/index.html)

Puppy 4.00beta1 - April 5, 2008
beta1 now available. Called  'puppy-3.98-seamonkey.iso'. Available from http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.00beta/
The release notes are here: http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.00beta/release-4.00b.htm
The release notes say: "Version 4.00 is happening ... here it is: the live-CD file is 'puppy-4.00-seamonkey.iso' and is just 83.3MB. Download from http://puppylinux.com/download/."
- BUT I can't find 'puppy-4.00-seamonkey.iso' there ?! But the 'test' folder has the 'puppy-4.00beta' folder, leading to puppy-3.98-seamonkey.iso

Puppy4, Alpha5 - January 22nd, 2008 
Xorg Wizard, special case handling
Rerwin has been working with various people, fixing the Xorg Wizard to work with some difficult video hardware. He has now added the Trident video BIOS dated 1997 as a special case. See forum thread, discussion with Barrington:
http://www.murga-linux.com/puppy/viewtopic.php?p=166725#166725
I have added this workaround to the Xorg Wizard.

Puppy4, Alpha4 - January 8th, 2008
Xorg Wizard rerun-at-every-boot bugfix
I found the cause of the problem. Puppy uses hardware profiling for video, so that if Puppy is booted on a different PC or a different monitor, the Xorg Wizard is rerun. A ‘xorg.conf.xxx’ file is created in /etc/X11 for each hardware profile, where ‘xxx’ is a string that represents the video chip and the monitor.
Puppy runs ‘ddcprobe’ to return information about the video chip and the monitor, but it is the latter that is the cause of the bug. One parameter fluctuates. Now fixed.

Puppy4, Alpha3 - December 14th, 2007
has the Xorg drivers as well as Xvesa, however there is only a cutdown selection of Xorg X servers — look in /usr/X11R7/lib/xorg/modules/drivers. Your video hardware will most likely work with the ‘vesa’ server if there is no match, but most likely you will want a server for your specific hardware. In that case, grab the full Xorg 7.3 binary package that I have uploaded to ibiblio (in the Dingo alpha2 folder) and get your required driver out of it. If you have already had the ‘vesa’ server running, you might want to delete the /etc/X11/xorg.conf and xorg.conf.xxxx files before rerunning the ‘xorgwizard’. I would like to know if your specific server works okay and in particular does it need any other files. I will include more servers in the next release of Dingo.

Puppy4, Alpha3 - December 15th, 2007
Well done barry and the puppy team, burned to cd on main pc (athlon 3000, ati9250 graphics,1GB ram), booted up puppy (pfix=ram), extracted the neomagic driver from the full Xorg 7.3 binary package and saved in /usr/X11R7/lib/xorg/modules/drivers. shut down pc saving session to cd.
now the good bit….put cd in toshiba portege 7010 laptop and booted up using wake2pup, Xorg wizard asked to confirm lcd resolution, tested ok,ctrl+alt+backspace, done, puppy running fine. First time without having to mess around altering xwin and manually configuring Xorg.conf. this will be great for all puppy users with older toshiba laptops.
Everything I could find regarding Xorg in Puppy 4 in Forum Discussions

Code: Select all

(up to 10-April-2008):
10 April 2008 - improve Puppy's hardware detection
> xorgwizard doesn't recognize my hardware (onboard graphic and Eizo monitor, connected via DVI) properly. I tested XFdrake (from PCLinuxOS) and my hardware is recognized very well. Perhaps you can have a look at XFdrake and find out why this tool has a better hardware detection than Puppy's xorgwizard.
Any hardware guru reading this (sorry, but it's not me) will want to know some specific details about the graphics "card". Like whether it's Intel, or nVidia, or ATi, what the model and chipset is and so on. 
You could also boot up XFDrake/PCLinuxOS and (in a terminal) type Code:
modprobe -l > filename_of_your_choosing
and compare the result with the same command in Puppy using a diff utility or your very own eyeballs. My guess is that Puppy's will be a shorter list which is why you will need to be specific about your hardware so that the correct module(s) can be identified and added - if suitable.

Apr 07 - "Problem video" fix has confusing user interface - SOLVED
The attachment contains a re-worked implementation of the fix that is triggered by the user's recovery from the hang -- the cancel and invocation of xorgwizard is remembered for later uses of the wizard and xwin. The problem "oem" signatures are kept in a separate file, /etc/xorgoverrides; the file is optional and is created when a hang is detected, but seeding it with the known signatures would avoid most hangs and the need for the recovery.

Puppy4 beta - Sat Apr 05, 2008
Stable enough for daily usage

http://puppylinux.org/wikka/Puppy4
Barry's thoughts about Puppy 3 & Puppy 4:
I have tried to clarify the point on my blog that the puppy3 series will continue. I will differentiate them with different names and on my main page where I state the latest version, I'll put both, so there'll be Slappy (or whatever it gets called) v3.02 and Dingo (or whatever) v4.00.
...
From the point of view of hardware detection, startup/shutdown scripts, all the underlying stuff, they will be equivalent.
- But 3.02 is not available yet. probably not far away.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#18 Post by tempestuous »

Yes, Puppy4 (Dingo) is currently at beta1 release.

Here is kirk's (large) Xorg7.3 DRI package -
http://www.murga-linux.com/puppy/viewto ... 505#164505

and here is the announcement about Barry's revised Xorg7.3
http://puppylinux.com/news/news400a5-400a7.htm
scroll down to "DRI enabled in Dingo"

So in theory DRI should work OK in recent Puppy4 versions, with the addition of xorg_xorg_full_dri-7.3.pet

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#19 Post by Béèm »

tempestuous
If you reference links can you make them clicable?

To do so in the composer window, select the link and push the URL tag.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

User avatar
dinky
Posts: 699
Joined: Sat 19 Jan 2008, 23:39

#20 Post by dinky »

For what it's worth, I think you should compile. I've hunted around abit, and found in the xubuntu forums evidence that this works... on xubuntu at least. Be surprised if you couldn't get it going in Puppy. I'm looking at getting an ebox 4300 in a few months, if it's not solved by then I'll have a go... sorry that won't help you much now. Good luck with it, just remember that you can get it working. This link might help: http://microclient.wordpress.com/2008/0 ... eo-driver/

Post Reply