headers
Stephen Borrill | 5 Aug 2003 11:08
Picon
Favicon

DRI vs Intel 82810-DC100

I've been trying to get X to work on a Dell Optiplex GX100 which has
integrated Intel 82810-DC100 graphics. I've previously had few problems
getting the i810 driver to work (except having to fix the VideoRam size
due to memory allocation problems). Whenever I try and get the i810 driver
to work with the 82810-DC100, the screen just blanks and the console is
locked (can't change back to text console). Dell do provide XF86Config
files on their website and I notice that they include the dri module (not
really any other differences). I also note that NetBSD doesn't currently
support DRI with XFree86. Is my problem likely to be down to the lack of
DRI support? Is there no non-DRI fallback?

--

-- 
Stephen Borrill
Permalink | Reply | 2 comments |
headers
Eric Anholt | 5 Aug 2003 19:03

Re: DRI vs Intel 82810-DC100

On Tue, 2003-08-05 at 02:08, Stephen Borrill wrote:
> I've been trying to get X to work on a Dell Optiplex GX100 which has
> integrated Intel 82810-DC100 graphics. I've previously had few problems
> getting the i810 driver to work (except having to fix the VideoRam size
> due to memory allocation problems). Whenever I try and get the i810 driver
> to work with the 82810-DC100, the screen just blanks and the console is
> locked (can't change back to text console). Dell do provide XF86Config
> files on their website and I notice that they include the dri module (not
> really any other differences). I also note that NetBSD doesn't currently
> support DRI with XFree86. Is my problem likely to be down to the lack of
> DRI support? Is there no non-DRI fallback?

The DRI is basically only for 3d acceleration.  Not having it is just
fine (FreeBSD i810 users still don't have DRI for i810).

--

-- 
Eric Anholt                                eta <at> lclark.edu          
http://people.freebsd.org/~anholt/         anholt <at> FreeBSD.org
Permalink | Reply | 1 comment |
headers
Stephen Borrill | 6 Aug 2003 13:54
Picon
Favicon

Re: DRI vs Intel 82810-DC100

On 5 Aug 2003, Eric Anholt wrote:
> On Tue, 2003-08-05 at 02:08, Stephen Borrill wrote:
> > I've been trying to get X to work on a Dell Optiplex GX100 which has
> > integrated Intel 82810-DC100 graphics. I've previously had few problems
> > getting the i810 driver to work (except having to fix the VideoRam size
> > due to memory allocation problems). Whenever I try and get the i810 driver
> > to work with the 82810-DC100, the screen just blanks and the console is
> > locked (can't change back to text console). Dell do provide XF86Config
> > files on their website and I notice that they include the dri module (not
> > really any other differences). I also note that NetBSD doesn't currently
> > support DRI with XFree86. Is my problem likely to be down to the lack of
> > DRI support? Is there no non-DRI fallback?
> 
> The DRI is basically only for 3d acceleration.  Not having it is just
> fine (FreeBSD i810 users still don't have DRI for i810).

OK.

I've sorted it out after a _lot_ of googling. For the record, the fix is
to add:

	Option "NoDDC" "True"

in the Device section (thanks to the OpenBSD guys for this).

I've also found when dealing with other i810 graphics cards that
specifying the video RAM is a necessity, i.e. add the following to the
Device section too:

	VideoRam	4096
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hubert Feyrer | 14 Aug 2003 11:47
Picon

Can't use 1600x1280 after upgrade to XF4.3.0


After upgrading my -current machine from XFree 4.2.1 to XFree 4.3.0,
display refuses to do 1600x1280, which worked fine before. Does anyone
know how to fix this? (Configu file attached below)

XFree86.0.log says:
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)

I've tried increading
    HorizSync   31.5 - 820.0
    VertRefresh 40-1500
but that still got the same result (this is on a Toshiba Satellite 1410
that definitely can do 1600x1280 on the TFT).

Any clues? :-(

 - Hubert

P.S.: Here's my XF86Config file:

# File generated by xf86config.

Section "Module"
    Load        "dbe"  	# Double buffer extension
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
    Load        "type1"
    Load        "freetype"
    Load       "glx"
(Continue reading)

Permalink | Reply | 10 comments |
headers
MLH | 15 Aug 2003 01:49

XF4.3.0 unstable (was Re: Can't use 1600x1280 after upgrade to XF4.3.0)

On 14 Aug 2003 07:50:00 -0500, Hubert Feyrer wrote:
> 
> After upgrading my -current machine from XFree 4.2.1 to XFree 4.3.0,
> display refuses to do 1600x1280, which worked fine before. Does anyone
> know how to fix this? (Configu file attached below)

Speaking of XFree 4.3.0, something seriously broke between the
build I did on 19 June 2003 and 12 August 2003 :

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: NetBSD/i386 1.6U [ELF] The NetBSD Foundation, Inc.
Build Date: 19 June 2003

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: NetBSD/i386 1.6W [ELF] The NetBSD Foundation, Inc.
Build Date: 12 August 2003

I've installed the 12 August 2003 build on two machines (luckily
no more) and still have the 19 June 2003 build on 5 others. The
latest build is fairly unstable with ati video cards. It's similar
to the problem I had with 4.2.1 and ati cards that the 19 June 2003
build fixed.

Anyone else seen this?
(Continue reading)

Permalink | Reply | 9 comments |
headers
D. E. Evans | 15 Aug 2003 00:07
Favicon

Diamond Viper 330

I've had problems with my Diamond Viper 330 since the
implimentation of XFree86 4.1.  The nv driver does not recognize
my chipset, and errors out (though it worked fine with 4.0).  I
have to use the vesa, which has some display problems, but is
functional.

I am currently using XFree86 4.3 from the XFree86.org.  I also
tried 4.2.1 (?) from the NetBSD 1.6.1 CD, and a compiled version
about a month ago from xsrc.  The XFree86 version broke with 4.2.
Also, recognize that the card is a PCI card, not an AGP card.

I have sent multiple emails to this list for assistance, but so
far, haven't got much help.  I keep getting told, upgrade,
upgrade, upgrade, but to no lasting result.  Plus, I've noted
that I'm not the only one that has complained of the problem,
according to the mailing lists.
--

-- 
D. E. Evans <sinuhe <at> xmission.com>
<http://www.xmission.com/~sinuhe>
Permalink | Reply | 4 comments |
headers
Chuck Cranor | 16 Aug 2003 02:57
Picon

render vs. xclock/4.3.0

hi-

    i upgraded my laptop to the latest xsrc from the netbsd CVS and
it broke my xclock --- the colors in the clock are so dim i can hardly 
see them!

     i run xclock with the following resources:

XClock*analog:  on
XClock*background:      black
XClock*foreground:      cyan
XClock*geometry:        =100x100-1+1
XClock*hands:   green
XClock*highlight:       DarkGreen

    i've found that if i start xclock with "xclock -norender" things
are back to normal (i.e. the clock is easy to read once again, like
it was before my upgrade).

    is the new behavior of xclock really desirable?   i don't really
understand why it was changed, maybe someone can explain?

chuck
Permalink | Reply | 0 comments |
headers
Nicholas Ricketts | 16 Aug 2003 14:41

XCursorGen

I see the xcursorgen is under the xsrc tree. But when I do this:

cd /usr/xrc && make build

it installs pretty much everything. But it doesnt install xcursorgen and I 
need it to help me make some cursors. Any idea on how to make it install this 
program would be appreciated. Thank you.
Permalink | Reply | 4 comments |
headers
Frederick Bruckman | 16 Aug 2003 22:11

Re: XCursorGen

On Sat, 16 Aug 2003, Nicholas Ricketts wrote:

> I see the xcursorgen is under the xsrc tree. But when I do this:
>
> cd /usr/xrc && make build
>
> it installs pretty much everything. But it doesnt install xcursorgen and I
> need it to help me make some cursors. Any idea on how to make it install this
> program would be appreciated. Thank you.

It looks like it's not built by default because it needs libpng.

It would probably be easiest to build the NetBSD package. The package
apparently has the same codebase; the Imakefiles are just patched to
let the package build easily outside of xsrc.

Frederick
Permalink | Reply | 3 comments |
headers
Nicholas Ricketts | 16 Aug 2003 15:36

Re: XCursorGen

I would do that execpt that I always update my x11 using xsrc. So whats going 
to happen if I use the package to install xcursorgen then they fix the xsrc 
so that xcursorgen builds by default. Then I will have a problem. I will have 
2 different verions installed in the same place. I have png-1.2.5nb2 
installed can I use this to compile xcursorgen under xsrc. I really need it 
to compile from xsrc. If the package works why not under work under xsrc. Is 
there a way  to force it to make xcursorgen from xsrc?

On Saturday 16 August 2003 08:11 pm, you wrote:
> On Sat, 16 Aug 2003, Nicholas Ricketts wrote:
> > I see the xcursorgen is under the xsrc tree. But when I do this:
> >
> > cd /usr/xrc && make build
> >
> > it installs pretty much everything. But it doesnt install xcursorgen and
> > I need it to help me make some cursors. Any idea on how to make it
> > install this program would be appreciated. Thank you.
>
> It looks like it's not built by default because it needs libpng.
>
> It would probably be easiest to build the NetBSD package. The package
> apparently has the same codebase; the Imakefiles are just patched to
> let the package build easily outside of xsrc.
>
> Frederick
Permalink | Reply | 2 comments |

Gmane