VIA Unichrome for Puppy 3?
Posted: Tue 23 Oct 2007, 09:17
I can't get graphics acceleration to work on my eBox using Puppy 3.01. Does anyone have a solution to this?
READ-ONLY Archive
https://oldforum.puppylinux.com/
Code: Select all
Load "dri"
Load "glx"
Code: Select all
Driver "via"
I got direct rendering according to glxinfo, but glxgears fails with this: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.
Code: Select all
__driCreateNewScreen_20050727 - succeeded
glxgears: Error: Requested window size (300/300) larger than maximum supported by GL engine (0/0).
Code: Select all
VideoRam 32768
Actually, that sounds terrible.Matt wrote:I can only reach close to 18 fps which I take it is maximum for the eBox 3851 I'm using.
Yes, please! I'm sort of stuck at 18 fps since I don't have a full development environment myself.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.
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
Yes, that's the core of your problem. There's no point adding 3D drivers until the "via" Xorg driver is working.nosignal wrote:I think my main problem is that when I include 'Driver "via"' in xorg.conf, xwin fails to start
Code: Select all
i2c_viapro 9236 0
i2c_core 22032 1 i2c_viapro
via_agp 10240 0
agpgart 34128 1 via_agp
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
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.
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.