Re: [Xpert]blank screen when switching from X to console

2001-10-03 Thread Nemanja Miletic

 hi all,

 I have a XFree86 4.1.0 instalation on Savage4 graphic card.
 X server is working fine, but when I try to shut it down with
 CTRL+ALT+backspase or when I try to
 switch to console with CTRL+ALT+Fn it has a great possibility to freeze.
It
 is a black screen freeze with
 no mouse. Only hardware reset button helps. I have Red Hat 6.1 at the
 momment but I had the same problem
 with RH 7.1 . I havo no KDE or GNOME installed just X.

 thank you,
 nemanja

I got the solution for this problem on comp.os.linux.x. I've put these lines
in lilo.conf.

   append=video=vesa:mtrr,ywrap
   vga=0x314

Console is now working in some kind of hi-resolution mode but I have no
problem with X.

regards,
nemanja





___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]glint 1600SW I2C monitor info

2001-10-03 Thread Dr Andrew C Aitchison

On Tue, 2 Oct 2001, Sidik Isani wrote:

 Hello -

   I'd like to get the I2C bus working on the Permedia 3.  One
   use for this would be to do what the Number Nine driver does
   with the monitor information:  If it detects the SGI 1600 SW,
   it automatically enables the FlatPanel option.

   Right now xf86DoEDID_DDC2 is returning NULL with my Permedia 3
   and the glint driver.  Are there some extra DDC2 initialization
   steps missing in the driver perhaps?

Sorry. I did say to Alan that I would look at that, but haven't.
Our Permedia card is now on a Windows machine, so I can't easily
do anything about this any more.

I did find that DDC worked with a monitor connected to the VGA
port, but not to the digital connection. I have some non X tools
which could get DDC information via the digital connection,
so XFree86 is definitely deficient.

It is some months since I looked at this, but if I remember correctly
one of the tools that I tried used the same VBE/Int10 calls as
XFree86 and also failed, while another used different ones which worked.

These tools are ddcprobe and ddcxinfo, which are or were part of RedHat
6.2 anaconda.
I had endian or bitfield problems with the modelines when using these
tools, so do check the results if you use them.

-- 
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED]   http://www.dpmms.cam.ac.uk/~werdna

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]running displays

2001-10-03 Thread Nico Galoppo

--* Owen Taylor (Wed, Oct 03, 2001 at 08:36:24AM -0400) *--

 You can find out what display/server applications are using by
 printing the DISPLAY environment variable:
 
  echo $DISPLAY

Sorry, I think i misexpressed myself. I'd like to know what display the
X server is listening on. Eg. ssh sets $DISPLAY to
myhost.domain.org:10.0, while that doesn't work if the Xserver is
listening on localhost:10.0.

--nico

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]running displays

2001-10-03 Thread Owen Taylor


Nico Galoppo [EMAIL PROTECTED] writes:

 --* Owen Taylor (Wed, Oct 03, 2001 at 08:36:24AM -0400) *--
 
  You can find out what display/server applications are using by
  printing the DISPLAY environment variable:
  
   echo $DISPLAY
 
 Sorry, I think i misexpressed myself. I'd like to know what display the
 X server is listening on. 

A server running on DISPLAY N will typically:

 - listen on the TCP port 6000 + N
 - listen on the Unix domain socket /tmp/.X11-unix/XN

(It could also be listening on DECNET, OS/2 pipes, etc...
IPv6 support is likely to become standard at some point 
in the future.)

So, by using a command such as 'lsof' it's possible to
figure out what displays a server is listening on.

There is (AFAIK) no way to find this out through the X
protocol, because a server may be available by many names. A
display name is a way of contacting a display. A single
display may well be available as:

 :0  - local unix domain socket
 localhost:0 - Over TCP
 :10.0   - forwarded over ssh
 
 Eg. ssh sets $DISPLAY to
 myhost.domain.org:10.0, while that doesn't work if the Xserver is

Note that ssh acts as a proxy server, so
myhost.domain.org:10.0 will typically be forwarded through
to your real display.

Regards,
Owen
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]differences on celeron and PIII

2001-10-03 Thread Peter Pilsl

On Tue, Oct 02, 2001 at 02:50:24PM +0200, Michel Dänzer wrote:
  Thats an interesting point. You mean that a damaged panel can fonts
  make look like AA ? (I always thought that AA looks like an
  hardwareerror and not like a feature ;)
 
 No, my suspicion is that they have different native resolutions, so one
 interpolates, which might look like AA. Just a wild guess...


They *should* have the same resolution ...
 
 
  I'll exchange panels and if at least one laptop is operatable again
  later I'll report again here ...
 
 Exchange panels? Damaged panel? I'm confused, please provide all
 information instead of drawing premature conclusions.


Sorry fot confusing : I just took a look at dell-webpage how to
exchange panels and it looks like one could do several damage to the
panel and the laptop if he is not very careful. Nevertheless I'll try
it, cause I really want to know whats going on.

And the only way to tell if its the panel or the cpu is to exchange
this parts. However the second machine is abroad now, so I can try at
end of november.
 I'm really looking forward and report here ..


thnx for your help.
peter

-- 
mag. peter pilsl

phone: +43 676 3574035
fax  : +43 676 3546512
email: [EMAIL PROTECTED]
sms  : [EMAIL PROTECTED]

pgp-key available
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Mouse Problems with 4.0.3

2001-10-03 Thread Louis Guillaume

Hello,

I just installed the XFree86 4.0.3 binaries on NetBSD 1.5.
In the /etc/X11/XF86Config is...

Section InputDevice
 Identifier  Mouse0
 Driver  mouse
 Option  Protocol wsmouse
 Option  Device /dev/wsmouse0
EndSection


For some reason the mouse is unusable when I startx. I don't have kde 
yet, just twm. The cursor is there and it responds but it doesn't go 
where I tell it!

Does anyone know what may cause this and how it can be fixed?

Louis

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



RE: [Xpert]Trident Chipsets Xv support

2001-10-03 Thread Egbert Eich

Geoffrey Hausheer writes:
  On Mon, Sep 24, 2001 at 09:46:19PM +0100, Alan Hourihane wrote:
   Can I urge people with Trident chips (laptops especially) to get the
   latest CVS code to test Xv support and provide some feedback.
  
  Another update on My Twinhead Powerslim 600 with the Cyber9525DVD:
  I changed the hsync hardcoded adjustment to 0 (it was initally 23)
  I left the vsync at -2.

This will break it for others. We still don't know exactly how to
calculate these values exactly. 

Egbert.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert] Xprint-related problem in StarOffice application

2001-10-03 Thread Malte Cornils

Alan Coopersmith wrote:
 problem you're having is related to XFree86 at all - try asking
on one of the
 StarOffice newsgroups for help.  (The Xprinter  Xprint API's are very close,
 which is why OpenOffice allows using Xprint as a replacement for Xprinter.)

Just to follow up on those interested in the problem, I fixed it
by... guess what... reinstalling StarOffice (I guess I should've
tried that before... After all, I was a Windows user once, I should
know this always helps :-))

Thanks for the answers!

Yours Malte #8-)
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Trident Chipsets Xv support

2001-10-03 Thread Chad Kitching

   Another update on My Twinhead Powerslim 600 with the Cyber9525DVD:
   I changed the hsync hardcoded adjustment to 0 (it was initally 23)
   I left the vsync at -2.

 This will break it for others. We still don't know exactly how to
 calculate these values exactly.

I've done some playing around with my laptop based on a Trident
Cyber9525DVD, and I'm beginning to believe that the CRTC values can't be
correct.  In particular, the CRTC values change from what X sets when I
press Fn-F5 to switch displays, and when I plug these values into the LCD[]
array, the overlay becomes centered properly (without modifying the
h/vsync).  I haven't managed to get 640x480 (unstretched) to work with the
overlay, since I can't get the trident driver to set the proper values
(e.g. the values I set in the LCD array end up being different from what
gets programmed into the VGA CRTC registers).

The CRTC values I'm getting from my card when I switch video outputs is the
same ones that are '#if 0'ed out above the current LCD[] array.


___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Xinerama on 2 out of 3 displays

2001-10-03 Thread Brian J. Murrell

I have a machine running XFree86 Version 4.1.0 with three displays --
a Matrox G400 (dual head card) and an ATI Rage IIC.  I want to bind
the first display of the G400 and the ATI together with Xinerama and
leave the second display of the G400 as a separate screen so that I
can address windows to it with :0.1.

It looks like Xinerama is just on or off, no configurabilty as to what
to bind together as a display.

Am I out of luck?

b.

-- 
Brian J. Murrell
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Xinerama on 2 out of 3 displays

2001-10-03 Thread Mark Vojkovich

On Wed, 3 Oct 2001, Brian J. Murrell wrote:

 I have a machine running XFree86 Version 4.1.0 with three displays --
 a Matrox G400 (dual head card) and an ATI Rage IIC.  I want to bind
 the first display of the G400 and the ATI together with Xinerama and
 leave the second display of the G400 as a separate screen so that I
 can address windows to it with :0.1.
 
 It looks like Xinerama is just on or off, no configurabilty as to what
 to bind together as a display.
 
 Am I out of luck?

   You're out of luck.  The Xinerama specification doesn't allow that.
The new spec being hashed out by X.org will, but I'd expect it to
be a while before anybody implements it due to the scope of the
modifications.


Mark.

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]SGI + Linux + dual (short version)

2001-10-03 Thread bruins

Hi,

I am after a bit of advice on setting up dual headed X and
problems with int10 module.  Any help or advice appreciated.

Error log located at : http://www.montagesystems.com.au/~bruins/XFree86.8.log

What I am hoping to achieve:
Firstly dual headed X11 using any two videocards from below.

Main goal:
Under X11, I would like to have the output of two videocameras
displayed on two monitors. That is camera output A, in a window
on monitor A.  Camera output B, in a window on monitor B.

What hardware I have:
I have a SGI 1450, quad xeon 700, PC, buckets of disk and ram.
2 x PCI, ATI 128 RAGE PAL TV cards 32Meg(capture, video, etc).
1 x PCI, TV Excel (TV tuner with capture card), brooktree BT878 chipset.
1 x AGP, ATI Mach 64 (disabled in BIOS)
1 x PCI, V3800 Riva TNT2, 32 Meg (capture, video, etc) (not in machine)
1 x video source


What software I have:
Linux 2.4.8 kernel
Mandrake 8.0 Traktopel Operating System
Either - XFree86 4.1.0
 XFree86 4.1.99.1  (built from source)
xawtv ver. 3.60


Basically I can't even get the machine to run two headed, either
xinerama or normal, let alone the two video cards displaying from
sources.

My guess is when int10 is probing the *second* video card, it can't read
it's configuration and is failing.

snip
(II) Loading sub module int10
(II) LoadModule: int10
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) R128(1): initializing int10
(EE) R128(1): Cannot read V_BIOS
/snip
 
What I believe I have got to work:
Using the first 128 Rage card, I have got xawtv 
to read /dev/video from the brooktree card.

What I have failed to get to work:

Basically I have failed to get two headed X11 working
  no matter what I have tried.

Using - the first 128 Rage card,
xawtv (no options)
Xfree86 4.1.0 (configured for one monitor only)
Result - Machine lock after moving the mouse 6 cms.

Using - the first 128 Rage card,
xawtv (no options)
Xfree86 4.1.99.1 (configured for one monitor only)
modprobe videodev
ldconfig
Result - Would not use the xvideo extension, even though
 the module was loaded.
 Error mesg -   Xawtv: input image, ports 55-55
 Error mesg -   Xawtv: no usable video port found

If you could please advise me on the setup that is most likely to
work, I would appreciate it.

Thankyou heaps.

 - mike


-- 
Mike Bruinsph  (08) 8331-3022
Information Analystfax (08) 8331-3044
Montage Systems Pty. Ltd.
Adelaide, South Australia. Yes - We do Linux Training !!!
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert