Page 1 of 2

Posted: Wed 04 Nov 2009, 19:17
by abushcrafter
Can one have ALL of the drivers installed, with puppy still doing it's auto detect on whatever hardware you are currently using? please

Posted: Fri 06 Nov 2009, 10:38
by Patriot
Hmmm .....
abushcrafter wrote:Can one have ALL of the drivers installed, with puppy still doing it's auto detect on whatever hardware you are currently using? please
Err ... Yes ?


Rgds

Posted: Fri 06 Nov 2009, 15:09
by panzerpuppy
@ Patriot: Is there a way to enable DRI for R600-based Radeon cards (HD2000 and HD3000 series) with the xfree86-video-ati driver / Xorg 7.3?

I installed your xfree86-video-ati driver .PET and the Xorg 7.3-1 DRI .PET package on Puppy 4.2.1, restarted X, but DRI was not enabled. The base driver works fine, but without 2D or 3D acceleration:

Code: Select all

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:03:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -19
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[dri] Disabling DRI.
(II) RADEON(0): using shadow framebuffer

(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM

(WW) RADEON(0): Direct rendering disabled
(EE) RADEON(0): Acceleration initialization failed
glxgears gears move like a slideshow and hardinfo reports that DRI is disabled

Looks like an additional DRI kernel module is needed for these relatively new cards (not included in the Xorg 7.3 DRI .PET)

Posted: Fri 06 Nov 2009, 20:58
by abushcrafter
Patriot wrote:Hmmm .....
abushcrafter wrote:Can one have ALL of the drivers installed, with puppy still doing it's auto detect on whatever hardware you are currently using? please
Err ... Yes ?


Rgds
Yes, Yeeea and :D thank you

Posted: Fri 06 Nov 2009, 21:32
by Patriot
Hmmm .....
panzerpuppy wrote:@ Patriot: Is there a way to enable DRI for R600-based Radeon cards (HD2000 and HD3000 series) with the xfree86-video-ati driver / Xorg 7.3? .....
Frankly, I do not know for sure if it will work on R7.3 ... R6xx/R7xx is currently stated to have experimental 3D according to xorg's wiki here and here... Newer drm (for dri, which you can find here) and mesa (for 3d) is required for it ... (the current R7.3 on puppy is using mesa 6.5.2)

Anyway, I couldn't get past mesa 7.1 on R7.3 previously as I didn't have much time to mess with it then ... Maybe when I have more free time, I'll try mesa 7.2 ... All mesa beginning 7.3 needs xorg server 1.5 ...


Rgds

Posted: Tue 24 Nov 2009, 09:45
by skinnie
guess there is a mistake in the description,usually tdfx drivers are used for voodoo 3,4,5 and voodoo for the voodoo 1 & 2...I didn't test the pets yet so don't know if it is the description that is wrong or the file...
But great effort :)

Posted: Sat 28 Nov 2009, 13:56
by skinnie
Hi guys,installed the pets for tdfx driver,but I can't get xorg working..
I am using Puppy 4.3.0 with pet update for 4.3.1..
here is my xorg.conf

Code: Select all

Section "Monitor"
	#DisplaySize	  310   230	# mm
	Identifier   "Monitor0"
	VendorName   "PHL"
	ModelName    "PHILIPS 107E5"
	### Comment all HorizSync and VertRefresh values to use DDC:
	Option	    "DPMS"
	HorizSync    30.0-71.0
	VertRefresh  50.0-85.0
	#UseModes     "Modes0" #monitor0usemodes
	Option      "PreferredMode" "1024x768"
	EndSection
	
Section "Modes"
	Identifier "Modes0"
	#modes0modeline0
EndSection

Section "Device"
	### Available Driver options are:-
	### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
	### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
	### [arg]: arg optional
	#Option     "NoAccel"            	# [<bool>]
	#Option     "SWcursor"           	# [<bool>]
	#Option     "UsePIO"             	# [<bool>]
	#Option     "ShowCache"          	# [<bool>]
	#Option     "VideoKey"           	# <i>
	#Option     "NoSLI"              	# [<bool>]
	#Option     "TexturedVideo"      	# [<bool>]
	#Option     "DRI"                	# [<bool>]
	Identifier  "Card0"
	Driver      "tdfx" #card0driver
	VendorName  "3Dfx Interactive, Inc."
	BoardName   "Voodoo 3"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
    DefaultDepth 16
    Subsection "Display"
        Depth       16
        Modes       "1024x768"
    EndSubsection
EndSection

#PuppyHardwareProfile=3dfx_Interactive__Inc_PHILIPS107E
don't know what could be wrong...in teenpup 2009 legacy it works out of the box..

Posted: Sun 29 Nov 2009, 18:52
by mikeb
Hmm..cirrus driver gives black screen with no clues...I guess thats why barry removed them so that vesa is used instead...support for these cards has worsened with each xorg release...the last good driver was in xf86.

But thanks for trying :)

mike

Posted: Wed 30 Dec 2009, 14:58
by zigbert
patriot
I have included the xf86-video-ati-6.12.4-i486 driver into Puppy Stardust (for personal reasons). Thanks :) ....... Now, could you advice me to choose from the driver list. Is there more of these drivers you know users need to make Puppy fly.


Sigmund

SiS 671/771 and Intel D201GLY

Posted: Sun 17 Jan 2010, 03:48
by prehistoric
Some time back I started to build a mini-ITX box for a (relatively) low-power Puppy system, using an Intel D201GLY motherboard with built-in Celeron 215 and SiS graphics. When I tried to get the graphics working, nothing was really satisfactory.

Recently, I dusted off that motherboard and tried again. I'm now posting from boxpup 431 on that machine, but the Puppy installation is lucky to reach 1024x768 with 16-bit color. I now have an installation of iMedia Linux 6.0.4 on the same box which I was able to coax into working flawlessly at 1600x1200 on my SGI 21" CRT. Part of the trick was copying the monitor section from the Puppy xorg.conf. Another part was simply adding "1600x1200" to the list of screen sizes (modes). Once X saw that the monitor could handle the high frequencies involved, everything worked. The changes needed were done by Nicu Pavel, and are available on-line.

Now, my big problem here is that this isn't running under Puppy 4.3.1. Their system, released in July 2008, uses a patched kernel 2.6.23 and Xorg 7.2. If I remember correctly, we are currently at kernel 2.6.30.5 and Xorg 7.1. There are good patched drivers now in Mandriva, and possibly some other distributions. Has anyone managed to move these changes into a Puppy 4.3.1 driver?

Posted: Thu 06 May 2010, 16:35
by TheSlider
thanks for the drivers !

edited :

mmh, i tried installing every ati pets for my old rage mobility m1 and restarted x and puppy but it didn't seem to work.
both # glxinfo and # glxgears with xrog dri showed garbage in the console meaning it couldn't find glx extension even though my xorg conf was correct.

Later i found that i had to set the resolution to 16bits video mode to make it work so now i see those damn gears. Too bad it's so slow and choppy (around 800 frames in 5 secs = 150 fps ? Feels more like 2 fps ).

Any idea on how to use glx on 24/32 bits ?

Posted: Tue 17 Aug 2010, 02:55
by chillinfart
Hey patriot, i have a motherboard with via CLE266 chipset. This pet works on puppy 4.3.1 w/ 2.6.30.5 kernel?

xf86-video-openchrome-0.2.904-i486.pet

If not, what dependencies are needed to compile it (i have the devx sfs mounted)?
More info here:
http://murga-linux.com/puppy/viewtopic.php?p=442434

Posted: Tue 17 Aug 2010, 15:37
by Patriot
Hmmm .....
chillinfart wrote:Hey patriot, i have a motherboard with via CLE266 chipset. This pet works on puppy 4.3.1 w/ 2.6.30.5 kernel?

xf86-video-openchrome-0.2.904-i486.pet .....
Yes, it works on all puppy4 series (4.00 - 4.31) that came with Xorg 7.3 ... Depending on the actual vga chipset configuration, you may also want to try openchrome-0.2.903. Some people have better stability with it. In my case, 0.2.904 works better.


Rgds

Posted: Wed 24 Nov 2010, 19:49
by James186282
I've been puzzling over getting an old laptop to work with composite video out.

Its a
M700 Armada Compaq
With a composite video connector and an Rage Mobility P/M AGP 2x chipset.

I've been fiddling with atitvout and it seems that it has video out but its turned off or? Its not available as a second display (or Both) Anyway...

Should I be trying to compile a Rage128 ATI driver and fiddle with my xorg.conf file to try to use it or?! Sorry for the noobishness of this question.

Posted: Sat 30 Apr 2011, 09:35
by Darkgame
cool. Does this drivers have 3d graphcs?

Posted: Sat 07 Jan 2012, 09:03
by PenguinPupLin
Can I install all theses drivers for Puppy 431(Brunopuppy actually), Wary511, Wary 522, Lighthouse 5.0.3, 214X-TOP9 and Slacko 5.3 as I'm using an external LCD monitor in place of my faulty notebook screen? So far even older puppies such as 431,214X-TOP9 and Legacy OS2 cannot get xorg drivers to work despite my Acer travelmate TM630 notebook having the NV11 Geforce 2 Go chipset shared memory 16MB, which xorg probing showed is a supported NVidia cards under "nv". Using Xvesa seems to make my puppies run less stably and I couldn't run Flsynclient to configure my touchpad tapping problem in Lighthouse puppy for example. My external monitor is a Samsung Syncmaster 931C,capable of much higher resoulutions and frequencies than my notebook screen. At the moment,I'm running xvesa in 1024x768x16 mode. Really hope there is a solution for me. Many thanks in advance.

Posted: Wed 11 Jan 2012, 17:52
by James186282
I picked up a T60 (IBM) laptop with a ATI X1400. I just switched to Lucid 5.2.8 and have tried the ATI_fglrx-10.10-Lucid *With Puppy Package Manager. It reports that it can't find a supported card.

I've been searching around and around for fix. Do I go back to an earlier fglrx version and try to compile that or? Is there some "fix" for this version that I have? Thanks to all those willing to answer my noob questions.

Nooestion?

or

Quob

Posted: Fri 13 Jan 2012, 16:19
by James186282
I unconfused myself. The ATI drivers are not being supported and they don't give source or hardware docs??? That (to me) is crazy. Don't you WANT a world of programmers to come up with new tricks and make your hardware look good? We live in really odd times.

Anywho I fumbled around enought to get the Radeon driver going with X.org well enough to run glxgears.

Posted: Thu 29 Mar 2012, 08:07
by greengeek
James186282 wrote:Anywho I fumbled around enought to get the Radeon driver going with X.org well enough to run glxgears.
Hi James, any chance of listing your xorg.conf file, or some tips about what you tried to get the glxgears going? (I'm trying to grasp this "accelerated graphics" thing and trying to patch together anything that works for others) Thx.

Posted: Mon 23 May 2016, 17:55
by James186282
Sorry I never responded to that message. The company I worked at had a corporate meltdown and my Laptop got snatched so I didn't know how I did it. *Which seems to be a common situation.