DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Packages and Ports

OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD.

Reply
 
Thread Tools Display Modes
Old 17th October 2017
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

https://en.wikipedia.org/wiki/XGI_Technology

If someone sold you this card as "New" and using an "ATI" chipset, they were not truthful with you.

In the interim I looked at the NetBSD kernel configuration. In the default kernel the mga driver is turned off. It may be possible for you to utilize the matrox card in NetBSD. You would have to build a custom kernel which is not an easy undertaking.

Last edited by shep; 17th October 2017 at 09:06 PM.
Reply With Quote
Old 17th October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

No I am not as stupid as that, I chose this card because I can not find a video card for the motherboard of the proliant, I know what is old but it should work because it has good reference under UNIX .
do not take me for what I am not.
your wikipedia link has become paying, and on the other hand the history that this card is interesting but that's not what I want to know, what I want is to operate this card under the three leading BSD.

this the dmesg command :
dmesg :
Code:
vga1 at pci7 dev 4 function 0 "XGI Technology Volari Z7" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
how to configure the xorg.conf ?

i do like this nano /etc/X11/xorg.conf
Quote:
Section "Device"
Identifier "Volari Z7"
Driver "XGI"
Options "AccelMethod" "EXA"
EndSection

nano /var/log/Xorg.0.log
Code:
[    24.931] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
        (Operation not permitted)
        Check that you have set 'machdep.allowaperture=1'
        in /etc/sysctl.conf and reboot your machine
        refer to xf86(4) for details
[    24.931]    linear framebuffer access unavailable
[    24.943] (--) Using wscons driver on /dev/ttyC4
[    24.991]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[    24.991] X Protocol Version 11, Revision 0
[    24.991] Build Operating System: OpenBSD 6.1 i386
[    24.991] Current Operating System: OpenBSD hpc-hapocalipse.my.domain 6.1 GENERIC.M$
[    24.991] Build Date: 01 April 2017  02:13:40PM
[    24.991]
[    24.991] Current version of pixman: 0.34.0
[    24.991]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    24.991] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    24.991] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 18 00:25:29 2017
[    25.045] (==) Using config file: "/etc/X11/xorg.conf"
[    25.045] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
[    25.059] Parse error on line 4 of section Device in file /etc/X11/xorg.conf
        "Options" is not a valid keyword in this section.
[    25.059] (EE) Problem parsing the config file
[    25.059] (EE) Error parsing the config file
[    25.059] (EE)
Fatal server error:
[    25.059] (EE) no screens found(EE)
[    25.059] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    25.059] (EE) Please also check the log file at "/var/log/Xorg.0.log" for addition$
[    25.059] (EE)
[    25.061] (EE) Server terminated with error (1). Closing log file.

Last edited by philo_neo71; 17th October 2017 at 10:33 PM.
Reply With Quote
Old 18th October 2017
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

Sorry, I was confused by your earlier post
Quote:
I change the video card for an ATI radeon card, I ordered I wait to receive it!
This Xenocara page lists the available video drivers in the monolithic xorg that OpenBSD uses.

This Freshports search for xgi does not show any FreeBSD support for xgi video

On my NetBSD 7-1 amd64 there is a man page for xgi video and also an entry for the modular xorg xf86-video-xgi driver

I do have 4 older ATI-rage/Radeon video cards for agp slots. They should all work in FreeBSD/OpenBSD/NetBSD/Linux. If you cover shipping, you can have all 4 of them.
Edit: After some more searching, it appears that the sis driver supports xgi chipsets including yours.
Sis video

In order to use the sis driver you need this in your xorg.conf or xorg.conf.d
Code:
Section "Device"
Identifier "Volari Z7"
Driver "sis"
EndSection

Last edited by shep; 18th October 2017 at 02:02 AM.
Reply With Quote
Old 18th October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

Quote:
I do have 4 older ATI-rage/Radeon video cards for agp slots. They should all work in FreeBSD/OpenBSD/NetBSD/Linux. If you cover shipping, you can have all 4 of them.
Edit: After some more searching, it appears that the sis driver supports xgi chipsets including yours.
Sorry but is not AGP port but PCI 3.3 volts, thanks for your help

after several tests with the video card "XGI Volari Z9s" I abandoned this last for a graphics card "3DFX Voodoo3", it is more recent.
I pity that it will work, because on the web there is interesting information.

dmesg:
Code:
vga1 at pci7 dev 4 function 0 "3DFX Voodoo3" rev 0x01
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
how to configure this card. I think like this:

Code:
"Device" section
Identify "voodoo3"
Driver "3dfx"
EndSection
This configuration does not work!
here is my /var/log/Xorg.0.log:

Code:
[    24.056] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
        (Operation not permitted)
        Check that you have set 'machdep.allowaperture=1'
        in /etc/sysctl.conf and reboot your machine
        refer to xf86(4) for details
[    24.056]    linear framebuffer access unavailable
[    24.069] (--) Using wscons driver on /dev/ttyC4
[    24.117]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[    24.117] X Protocol Version 11, Revision 0
[    24.117] Build Operating System: OpenBSD 6.1 i386
[    24.117] Current Operating System: OpenBSD hpc-hapocalipse.my.domain 6.1 GENERIC.MP#291 i386
[    24.117] Build Date: 01 April 2017  02:13:40PM
[    24.117]
[    24.117] Current version of pixman: 0.34.0
[    24.117]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    24.117] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    24.117] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 18 22:01:10 2017
[    24.171] (==) Using config file: "/etc/X11/xorg.conf"
[    24.171] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
[    24.172] (==) No Layout section.  Using the first Screen section.
[    24.173] (==) No screen section available. Using defaults.
[    24.173] (**) |-->Screen "Default Screen Section" (0)
[    24.173] (**) |   |-->Monitor "<default monitor>"
[    24.174] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    24.174] (==) Disabling SIGIO handlers for input devices
[    24.174] (==) Automatically adding devices
[    24.174] (==) Automatically enabling devices
[    24.174] (==) Not automatically adding GPU devices
[    24.174] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    24.267] (==) FontPath set to:
        /usr/X11R6/lib/X11/fonts/misc/,
        /usr/X11R6/lib/X11/fonts/TTF/,
        /usr/X11R6/lib/X11/fonts/OTF/,
        /usr/X11R6/lib/X11/fonts/Type1/,
                                                                                         2,4-11        Top

[    24.267] (II) The server relies on wscons to provide the list of input devices.
        If no devices become available, reconfigure wscons or disable AutoAddDevices.
[    24.267] (II) Loader magic: 0x3906f020
[    24.267] (II) Module ABI versions:
[    24.267]    X.Org ANSI C Emulation: 0.4
[    24.267]    X.Org Video Driver: 20.0
[    24.267]    X.Org XInput driver : 22.1
[    24.267]    X.Org Server Extension : 9.0
[    24.268] (--) PCI:*(0:1:4:0) 121a:0005:121a:0036 rev 1, Mem @ 0xf8000000/33554432, 0xf4000000/33554432, I/O @ 0x0000c800/256
[    24.268] (--) PCI: (0:3:0:0) 102b:0522:103c:31fa rev 2, Mem @ 0xf6000000/16777216, 0xfbcfc000/16384, 0xfb000000/8388608
[    24.268] (II) LoadModule: "glx"
[    24.287] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[    24.368] (II) Module glx: vendor="X.Org Foundation"
[    24.368]    compiled for 1.18.4, module version = 1.0.0
[    24.368]    ABI class: X.Org Server Extension, version 9.0
[    24.368] (==) AIGLX enabled
[    24.368] (==) Matched tdfx as autoconfigured driver 0
[    24.368] (==) Matched vesa as autoconfigured driver 1
[    24.368] (==) Assigned the driver to the xf86ConfigLayout
[    24.368] (II) LoadModule: "tdfx"
[    24.369] (II) Loading /usr/X11R6/lib/modules/drivers/tdfx_drv.so
[    24.375] (II) Module tdfx: vendor="X.Org Foundation"
[    24.375]    compiled for 1.18.4, module version = 1.4.7
[    24.375]    Module class: X.Org Video Driver
[    24.375]    ABI class: X.Org Video Driver, version 20.0
[    24.375] (II) LoadModule: "vesa"
[    24.375] (II) Loading /usr/X11R6/lib/modules/drivers/vesa_drv.so
[    24.378] (II) Module vesa: vendor="X.Org Foundation"
[    24.378]    compiled for 1.18.4, module version = 2.3.4
[    24.378]    Module class: X.Org Video Driver
[    24.378]    ABI class: X.Org Video Driver, version 20.0
[    24.378] (II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee,
        3dfx Velocity, 3dfx Voodoo3, 3dfx Voodoo4, 3dfx Voodoo5
[    24.378] (II) VESA: driver for VESA chipsets: vesa
[    24.379] (II) TDFX(0): PIO base = 0xc800
[    24.379] (WW) Falling back to old probe method for vesa
[    24.379] (II) Loading sub module "vgahw"
[    24.379] (II) LoadModule: "vgahw"
                                                                                         49,10         55%
[    24.379] (WW) Falling back to old probe method for vesa
[    24.379] (II) Loading sub module "vgahw"
[    24.379] (II) LoadModule: "vgahw"
[    24.390] (II) Loading /usr/X11R6/lib/modules/libvgahw.so
[    24.396] (II) Module vgahw: vendor="X.Org Foundation"
[    24.396]    compiled for 1.18.4, module version = 0.1.0
[    24.396]    ABI class: X.Org Video Driver, version 20.0
[    24.397] (II) Loading sub module "int10"
[    24.397] (II) LoadModule: "int10"
[    24.398] (II) Loading /usr/X11R6/lib/modules/libint10.so
[    24.398] (II) Module int10: vendor="X.Org Foundation"
[    24.398]    compiled for 1.18.4, module version = 1.0.0
[    24.398]    ABI class: X.Org Video Driver, version 20.0
[    24.398] (II) TDFX(0): Softbooting the board (through the int10 interface).
[    24.399] (EE) TDFX(0): Cannot read int vect
[    24.399] (WW) TDFX(0): Softbooting the board failed.
[    24.399] (II) TDFX(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    24.399] (==) TDFX(0): Depth 24, (--) framebuffer bpp 32
[    24.399] (==) TDFX(0): RGB weight 888
[    24.399] (==) TDFX(0): Default visual is TrueColor
[    24.399] (--) TDFX(0): Chipset: "3dfx Voodoo3"
[    24.399] (--) TDFX(0): Linear framebuffer at 0xF4000000
[    24.399] (--) TDFX(0): MMIO registers at addr 0xF8000000
[    24.399] (--) TDFX(0): PIO registers at addr 0xC800
[    24.399] (EE) Segmentation fault at address 0x3b93174
[    24.399] (EE)
Fatal server error:
[    24.399] (EE) Caught signal 11 (Segmentation fault). Server aborting
[    24.399] (EE)
[    24.399] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    24.399] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    24.399] (EE)
[    24.401] (EE) Server terminated with error (1). Closing log file.
~                                                                                                          
~                                                                                                          
~                                                                                                          
                                                                                         88,19         Bot
Reply With Quote
Old 18th October 2017
PapaParrot's Avatar
PapaParrot PapaParrot is offline
parrot
 
Join Date: Jul 2015
Location: Durango, Mx.
Posts: 472
Default

One thing I notice:
Shep shows this:
Code:
Section "Device"
Identifier "Volari Z7"
Driver "sis"
EndSection
The OP shows this:
as does not work,
Code:
"Device" section
Identify "voodoo3"
Driver "3dfx"
EndSection
I don't think that would work, maybe:
Code:
Section "Device"
Identifier "voodoo3"
Driver"sis"
EndSection
I suppose if you try the Driver "3dfx" it might work as well, but is suggesting that the "sis" should be used,
__________________
My best friends are parrots

Last edited by PapaParrot; 18th October 2017 at 09:10 PM.
Reply With Quote
Old 18th October 2017
LeFrettchen's Avatar
LeFrettchen LeFrettchen is offline
Marveled user
 
Join Date: Aug 2012
Location: France
Posts: 405
Default

Quote:
Originally Posted by philo_neo71 View Post

Code:
[    24.398] (II) TDFX(0): Softbooting the board (through the int10 interface).
[    24.399] (EE) TDFX(0): Cannot read int vect
[    24.399] (WW) TDFX(0): Softbooting the board failed.
I may be wrong, but I think this is a known bug from xorg/xserver.

I don't know if a patch exists on OpenBSD.
__________________
ThinkPad W500 P8700 6GB HD3650 - faultry
ThinkStation P700 2x2620v3 32GB 1050ti 3xSSD 1xHDD
Reply With Quote
Old 18th October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

with the xorg.conf like this i have a black screen !

Code:
Section "Device"
Identifier "voodoo3"
Driver"sis"
EndSection
have come close to the solution of the problem

my log :
Quote:
23.913] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[ 23.913] linear framebuffer access unavailable
[ 23.926] (--) Using wscons driver on /dev/ttyC4
[ 23.974]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[ 23.974] X Protocol Version 11, Revision 0
[ 23.974] Build Operating System: OpenBSD 6.1 i386
[ 23.974] Current Operating System: OpenBSD hpc-hapocalipse.my.domain 6.1 G$
[ 23.974] Build Date: 01 April 2017 02:13:40PM
[ 23.974]
[ 23.974] Current version of pixman: 0.34.0
[ 23.974] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 23.974] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 23.974] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 19 00:43:53 2$
[ 24.027] (==) Using config file: "/etc/X11/xorg.conf"
[ 24.027] (==) Using system config directory "/usr/X11R6/share/X11/xorg.con$
[ 24.041] Parse error on line 3 of section Device in file /etc/X11/xorg.conf
"Driver"sis"" is not a valid keyword in this section.
[ 24.041] (EE) Problem parsing the config file
[ 24.041] (EE) Error parsing the config file
[ 24.041] (EE)
Fatal server error:
[ 24.041] (EE) no screens found(EE)
[ 24.041] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 24.041] (EE) Please also check the log file at "/var/log/Xorg.0.log" for $
[ 24.041] (EE)
[ 24.043] (EE) Server terminated with error (1). Closing log file.

Reply With Quote
Old 19th October 2017
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

The Identifier can be any thing you choose - the only constraint is that you use the same exact identification in subsequent sections.

Code:
"Driver"sis"" is not a valid keyword in this section.
If your are using the xgi card, there was a punctuation errror: There needs to be a white space between Device and "sis".
To use the xgi card put the following in /etc/X11/xorg.conf.d/20-xgi.conf
Code:
Section "Device"
Identifier "XGI"
Driver "sis"
EndSection
For the Voodoo3 card you use the tdfx driver. tdfx(4)
Put the following in /etc/X11/xorg.conf.d/20-voodoo3.conf
Code:
Section "Device"
Identifier "voodoo3"
Driver "tdfx"
EndSection
You are going to have problems changing the Identifier if you insist on using a monolithic xorg.conf. For example, if you use voodoo3 in the Device section you also need to use voodoo3 in the screens section.

The advantage of using entries in xorg.conf.d is that you just need to make a device entry and the autogenerated screen section will use the Identification in the device section.

Last edited by shep; 19th October 2017 at 01:44 PM. Reason: correct for the shift from XGI -> Voodoo3
Reply With Quote
Old 19th October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

mister shep,
I sold the card "Volari Z7".
i work with voodoo3 video card, it's more recent.
i don't found the file following in /etc/X11/xorg.conf.d/20-voodoo3.conf
i have put parametrers in /etc/X11/xorg.conf

Code:
Section "Device"
Identifier "voodoo3"
Driver "tdfx"
EndSection
this is my /var/log/Xorg.0.log :

Quote:
24.162] (==) AIGLX enabled
[ 24.163] (II) LoadModule: "tdfx"
[ 24.163] (II) Loading /usr/X11R6/lib/modules/drivers/tdfx_drv.so
[ 24.166] (II) Module tdfx: vendor="X.Org Foundation"
[ 24.166] compiled for 1.18.4, module version = 1.4.7
[ 24.166] Module class: X.Org Video Driver
[ 24.166] ABI class: X.Org Video Driver, version 20.0
[ 24.166] (II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee,
3dfx Velocity, 3dfx Voodoo3, 3dfx Voodoo4, 3dfx Voodoo5
[ 24.167] (II) TDFX(0): PIO base = 0xc800
[ 24.167] (II) Loading sub module "vgahw"
[ 24.167] (II) LoadModule: "vgahw"
[ 24.173] (II) Loading /usr/X11R6/lib/modules/libvgahw.so
[ 24.180] (II) Module vgahw: vendor="X.Org Foundation"
[ 24.180] compiled for 1.18.4, module version = 0.1.0
[ 24.180] ABI class: X.Org Video Driver, version 20.0
[ 24.180] (II) Loading sub module "int10"
[ 24.180] (II) LoadModule: "int10"
[ 24.181] (II) Loading /usr/X11R6/lib/modules/libint10.so
[ 24.182] (II) Module int10: vendor="X.Org Foundation"
[ 24.182] compiled for 1.18.4, module version = 1.0.0
[ 24.182] ABI class: X.Org Video Driver, version 20.0
[ 24.182] (II) TDFX(0): Softbooting the board (through the int10 interface).
[ 24.182] (EE) TDFX(0): Cannot read int vect
[ 24.182] (WW) TDFX(0): Softbooting the board failed.
[ 24.182] (II) TDFX(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 24.182] (==) TDFX(0): Depth 24, (--) framebuffer bpp 32
[ 24.182] (==) TDFX(0): RGB weight 888
[ 24.182] (==) TDFX(0): Default visual is TrueColor
[ 24.182] (--) TDFX(0): Chipset: "3dfx Voodoo3"
[ 24.182] (--) TDFX(0): Linear framebuffer at 0xF4000000
[ 24.182] (--) TDFX(0): MMIO registers at addr 0xF8000000
[ 24.182] (--) TDFX(0): PIO registers at addr 0xC800
[ 24.182] (EE) Segmentation fault at address 0xb926174
[ 24.182] (EE)
Fatal server error:
[ 24.182] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 24.183] (EE)
[ 24.183] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Reply With Quote
Old 19th October 2017
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

Quote:
I don't found the file following in /etc/X11/xorg.conf.d/20-voodoo3.conf
You have to make an /etc/X11/xorg.conf.d directory and then create the 20-voodoo3.conf file in that directory. Remove or rename /etc/X11/xorg.conf (It would compete with the entries in /etc/X11/xorg.conf.d/)

Then you can try various options for tdfx(4) by simply adding the option in the 20-voodoo3.conf file.

You can choose the following options:
Quote:
The following driver Options are supported:
Option "NoAccel" "boolean"
Disable or enable acceleration. Default: acceleration is enabled.
Option "SWCursor" "boolean"
Disable or enable software cursor. Default: software cursor is disable and a hardware cursor is used for configurations where the hardware cursor is available.
Option "DRI" "boolean"
Disable or enable DRI support. By default, DRI is on.
Option "TexturedVideo" "boolean"
This has XvImage support use the texture engine rather than the video overlay.
Option "VideoKey" "integer"
This sets the default pixel value for the YUV video overlay key. Default: undefined.
Option "UsePIO" "boolean"
Force the use of Programmed IO instead of Memory Mapped IO. Default: off.
The following additional Options are supported:
Option "ShowCache" "boolean"

Enable or disable viewing offscreen cache memory. A development debug option. Default: off.
Boolean values are yes/no | true/false | 0/1 | on/off

See this Gentoo Xorg Wiki

For example:
Code:
Section "Device"
Identifier "voodoo3"
Driver "tdfx"
Option "DRI" "false"
EndSection

Last edited by shep; 19th October 2017 at 05:55 PM.
Reply With Quote
Old 19th October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

Mister Shep,
I followed your instructions, I created the directory as well as the file:
/etc/X11/xorg.conf.d/20-voodoo3.conf, I have an error that I do not understand on a vector of type integer: (EE) TDFX (0): Can not read int vect, a problem of reading addressing the processor of the video card.

here is my "/var/log/Xorg.0.log"
Quote:
3dfx Velocity, 3dfx Voodoo3, 3dfx Voodoo4, 3dfx Voodoo5
[ 25.298] (II) TDFX(0): PIO base = 0xc800
[ 25.299] (II) Loading sub module "vgahw"
[ 25.299] (II) LoadModule: "vgahw"
[ 25.301] (II) Loading /usr/X11R6/lib/modules/libvgahw.so
[ 25.311] (II) Module vgahw: vendor="X.Org Foundation"
[ 25.311] compiled for 1.18.4, module version = 0.1.0
[ 25.311] ABI class: X.Org Video Driver, version 20.0
[ 25.312] (II) Loading sub module "int10"
[ 25.312] (II) LoadModule: "int10"
[ 25.313] (II) Loading /usr/X11R6/lib/modules/libint10.so
[ 25.314] (II) Module int10: vendor="X.Org Foundation"
[ 25.314] compiled for 1.18.4, module version = 1.0.0
[ 25.314] ABI class: X.Org Video Driver, version 20.0
[ 25.314] (II) TDFX(0): Softbooting the board (through the int10 interface).
[ 25.315] (EE) TDFX(0): Cannot read int vect
[ 25.315] (WW) TDFX(0): Softbooting the board failed.
[ 25.315] (II) TDFX(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 25.315] (==) TDFX(0): Depth 24, (--) framebuffer bpp 32
[ 25.315] (==) TDFX(0): RGB weight 888
[ 25.315] (==) TDFX(0): Default visual is TrueColor
[ 25.315] (**) TDFX(0): Option "DRI" "false"
[ 25.315] (--) TDFX(0): Chipset: "3dfx Voodoo3"
[ 25.315] (--) TDFX(0): Linear framebuffer at 0xF4000000
[ 25.315] (--) TDFX(0): MMIO registers at addr 0xF8000000
[ 25.315] (--) TDFX(0): PIO registers at addr 0xC800
[ 25.315] (EE) Segmentation fault at address 0xc09d174
[ 25.315] (EE)
Fatal server error:
[ 25.315] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 25.315] (EE)
[ 25.315] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 25.315] (EE) Please also check the log file at "/var/log/Xorg.0.log" for a$
[ 25.315] (EE)
[ 25.317] (EE) Server terminated with error (1). Closing log file.

I let you judge for yourself, I can not do too much reboot because the startup sequence of the proliant is long .... and I'm afraid to damage it!

Kinds regards
Philippe
Reply With Quote
Old 20th October 2017
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

If you tried the various options in tdfx(4) to disable various features:
Code:
 Option "NoAccel" "boolean"
              Disable or enable acceleration.  Default: acceleration is
              enabled.

 Option "DRI" "boolean"
              Disable or enable DRI support. By default, DRI is on.

  Option "SWCursor" "boolean"
              Disable or enable software cursor.  Default: software cursor is
              disable and a hardware cursor is used for configurations where
              the hardware cursor is available.
Then I have only one other thing to try and it is complex:

In the i386 GENERIC kernel there is this line:
Code:
com3    at isa? disable port 0x2e8 irq 9 # (conflicts with some video cards)
You can try using ukc(8) to disable com3. Examples about using ukc are in config(8) under EXAMPLES (kernel modification).
Reply With Quote
Old 21st October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

Hello,

I understand that it is necessary to test several possible configurations, but with the Proliant it is difficult to restart a session I must boot two times to have the multiboot grub, I am afraid to damage my server!

I try this configuration, the server take care of the options that you indicated but I still have an error.

My file /etc/X11/xorg.conf.d/20-voodoo3.conf
Quote:
Section "Device"
Identifier "voodoo3"
Driver "tdfx"
Option "DRI" "true"
Option "NoAccel" "true"
Option "SWCursor" "true"
EndSection
my file /var/log/Xorg.0.log
Quote:
24.299] (II) Module int10: vendor="X.Org Foundation"
[ 24.299] compiled for 1.18.4, module version = 1.0.0
[ 24.299] ABI class: X.Org Video Driver, version 20.0
[ 24.299] (II) TDFX(0): Softbooting the board (through the int10 interface).
[ 24.299] (EE) TDFX(0): Cannot read int vect
[ 24.299] (WW) TDFX(0): Softbooting the board failed.
[ 24.299] (II) TDFX(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 24.299] (==) TDFX(0): Depth 24, (--) framebuffer bpp 32
[ 24.299] (==) TDFX(0): RGB weight 888
[ 24.299] (==) TDFX(0): Default visual is TrueColor
[ 24.299] (**) TDFX(0): Option "NoAccel" "true"
[ 24.299] (**) TDFX(0): Option "SWcursor" "true"
[ 24.299] (**) TDFX(0): Option "DRI" "true"
[ 24.299] (--) TDFX(0): Chipset: "3dfx Voodoo3"
[ 24.299] (--) TDFX(0): Linear framebuffer at 0xF4000000
[ 24.299] (--) TDFX(0): MMIO registers at addr 0xF8000000
[ 24.299] (--) TDFX(0): PIO registers at addr 0xC800
[ 24.299] (EE) Segmentation fault at address 0xd163174
[ 24.299] (EE)
Fatal server error:
[ 24.299] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 24.299] (EE)
[ 24.299] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 24.299] (EE) Please also check the log file at "/var/log/Xorg.0.log" for a$
[ 24.299] (EE)
[ 24.302] (EE) Server terminated with error (1). Closing log file.
Quote:
You can try using ukc(8) to disable com3. Examples about using ukc are in config(8) under EXAMPLES (kernel modification).
I do not know much about BSD and these kernels, that's why I bought this HP Proliant to do kernel compilation, because I have 2 * 4 cores and 16 threads, so when you make this remark with "try using ukc (8) to disable com3", I am a little lost because I start on the kernels on BSD, I do it well under Linux without problems, so I would like to learn skills on BSD .

Regards
Philippe
Reply With Quote
Old 21st October 2017
PapaParrot's Avatar
PapaParrot PapaParrot is offline
parrot
 
Join Date: Jul 2015
Location: Durango, Mx.
Posts: 472
Default

When you boot, before it completely boots:
Quote:
To boot into the User Kernel Config, or UKC, use the -c option at boot-time.

boot> boot hd0a:/bsd -c
From: https://www.openbsd.org/faq/faq5.html
Quote:
Boot-time configuration
Sometimes when booting your system you might notice that the kernel finds your device but maybe at the wrong IRQ. Without rebuilding the kernel, you can use OpenBSD's boot time kernel configuration, boot_config(8).

However, this will only correct your problem for one time. If you reboot, you will have to repeat this procedure. So, this is only a temporary fix, and you should correct the problem using config(8).

To boot into the User Kernel Config, or UKC, use the -c option at boot-time.

boot> boot hd0a:/bsd -c

Doing this will bring up a UKC prompt. Type help for a list of available commands.
Using this :
Code:
man config
Quote:
CONFIG(8) System Manager's Manual CONFIG(8)

NAME
config - build kernel compilation directories or modify a kernel
------ snip -------------
EXAMPLES (kernel building)
Note: The standard OpenBSD kernel configuration (GENERIC or GENERIC.MP)
is suitable for most purposes. Use of an alternative kernel
configuration is not recommended. A custom kernel is built in the
following way.

-------- snip---- note: the examples are way down near the bottom , ---
SEE ALSO
options(4), files.conf(5), boot.conf(8), boot_config(8)
It is a very detailed manual, and there are more details in the "see also" sections.


Quote:
Philippe >> so I would like to learn skills on BSD .
Reading these manuals has helped me a lot, but it does take time. I am still learning more myself and
really don't know that much though.
__________________
My best friends are parrots

Last edited by PapaParrot; 21st October 2017 at 02:56 PM.
Reply With Quote
Old 21st October 2017
shep shep is offline
Real Name: Scott
Arp Constable
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,503
Default

https://dri.freedesktop.org/wiki/DRM/ take a special kernel code that may be failing. You can try removing it.
Code:
Section "Device"
Identifier "voodoo3"
Driver "tdfx"
Option "DRI" "false"
Option "NoAccel" "true"
Option "SWCursor" "true"
EndSection
Reply With Quote
Old 22nd October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

Hi mister GarryR,

I see the command
Quote:
boot> boot hd0a: / bsd -c
, but I am on several hard disks, and addressing hd0a is not going, I run my BSD from a grub of UBUNTU server; and to quote the example here is the statement in the
Quote:
40_custom
of grub:
Code:
menuentry "OpenBSD" {
set root = '(hd1,2)'
chainloader +1
}
I do not know with which command on OpenBSD I will be able to determine the name of my disk space, can be with a command
Quote:
fdisk
.
But I have to know how to do the command
Quote:
boot> boot hdXz: / bsd -c
,
and determine the value of
Quote:
X and z
.

Kinds Regards
Philippe
Reply With Quote
Old 22nd October 2017
PapaParrot's Avatar
PapaParrot PapaParrot is offline
parrot
 
Join Date: Jul 2015
Location: Durango, Mx.
Posts: 472
Default

Ok, understood, any way, that is a very complicated method , and more so on your system,.
Did you try what Shep suggests, changing the Option "DRI" from "true" to false.
Code:
Option "DRI" "false"
?
__________________
My best friends are parrots
Reply With Quote
Old 22nd October 2017
philo_neo71 philo_neo71 is offline
Spam Deminer
 
Join Date: Jul 2009
Posts: 278
Default

i do it but issue
Reply With Quote
Reply

Thread Tools
Display Modes

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 On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
xfce4 issue philo_neo71 NetBSD Package System (pkgsrc) 6 28th May 2018 12:11 PM
xfce4 work fine, but gnome issue philo_neo71 OpenBSD Packages and Ports 10 9th September 2016 01:12 AM
xfce4 issue on sun blade philo_neo71 NetBSD Package System (pkgsrc) 1 30th May 2016 02:56 AM
OpenBSD xfce4 kaschei OpenBSD General 5 28th June 2009 08:45 PM
XFCE4 on 7.0 TMD3 FreeBSD Ports and Packages 3 26th July 2008 03:22 AM


All times are GMT. The time now is 11:35 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick