RE: [Xpert]PowerBook III locks up using the HEAD ati driver(previous HEAD builds were okay)
Whoops. The XFree86.log information I included was from a session using the fbdev driver. It shows a few problems of its own, but not the ones I asked about. The following info from the kernel log may be helpful: radeonfb: ref_clk=2700, ref_div=12, xclk=36675 from OF radeonfb: detected DFP panel size from EDID: 1280x854 Console: switching to colour frame buffer device 160x53 Registered "ati" backlight controller, level: 15/15 radeonfb: pm reg @50, clk_pwrmgt: f17500, pll_pwrmgt: a027e01f, mdll_cko: 980098radeonfb: ATI Radeon M7 LW DDR SGRAM 32 MB radeonfb: DVI port LCD monitor connected radeonfb: CRT port no monitor connected no framebuffer address found for /pci@f000/ATY,CrownParent@10/ATY,Crown_B agpgart: Maximum main memory to use for agp memory: 440M agpgart: Detected Apple UniNorth 1.5 chipset agp: configuring for size idx: 4 agpgart: AGP aperture is 16M @ 0x0 [drm] AGP 0.99 on Unknown @ 0x 16MB [drm] Initialized radeon 1.1.1 20010405 on minor 0 And here is a log from the ati driver session: XFree86 Version 4.2.99.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 26 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.20-pre7-ben0 ppc [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Oct 3 22:07:59 2002 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "macintosh_old" (**) XKB: model: "macintosh_old" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (--) Keyboard: CustomKeycode enabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/tmp/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.99.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.2.99.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:0b:0: chip 106b,002d card , rev 00 class 06,00,00 hdr 00 (II) PCI: 00:10:0: chip 1002,4c57 card 1002,4c57 rev 00 class 03,00,00 hdr 00 (II) PCI: 10:0b:0: chip 106b,002e card , rev 00 class 06,00,00 hdr 00 (II) PCI: 10:17:0: chip 106b,0022 card , rev 03 class ff,00,00 hdr 00 (II) PCI: 10:18:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 10:19:0: chip 106b,0019 card , rev 00 class 0c,03,10 hdr 00 (II) PCI: 10:1a:0: chip 104c,ac50 card 1000, rev 02 class 06,07,00 hdr 02 (II) PCI: 24:0b:0: chip 106b,002f card , rev 00 class 06,00,00 hdr 00 (II) PCI: 24:0e:0: chip 11c1,5811 card 11c1,5811 rev 00 class 0c,00,10 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:11:0), (0,0,36), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus 16: bridge is at (16:11:0), (16,16,36), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 16 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 16 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 16 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-CardBus bridge: (II) Bus 17: bridge
[Xpert]Can't turn dpms off with nv driver
I have been having screen locks since switching to ACPI. In trying to locate the problem, I am trying to disable DPMS when using the nv driver. However, no matter what I try, it always is enabled: ... (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension FontCache (II) Loading extension TOG-CUP ... (==) NV(0): Backing store disabled (==) NV(0): Silken mouse enabled (**) Option "dpms" "no" (**) NV(0): DPMS enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension ... I have set this option in both the Moniter section as well as the Device section for the driver, but neither work. Is this a bug or am I missing something? Jamie Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]PowerBook III locks up using the HEAD ati driver (previous HEADbuilds were okay)
Hi, I am running XFree86 HEAD on a Titanium PowerBook III/800 with a 2.4.20-pre7-ben0 kernel built from Benjamin Herrenschmidt's rsync tree. For the last couple of days, when I build from cvs HEAD, starting X has locked up my display (I cannot switch away from the locked tty7). My kernel is still running, because the CAPSLOCK light still toggles. Anyhow, I have had only minor problems with the ati driver for the last couple of months. I am running radeonfb in the kernel and have the following settings in XF86Config: Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" # Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"pex5" Load"record" Load"speedo" Load"type1" Load"vbe" Load"xie" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbLayout" "us" Option "XkbModel" "macintosh_old" Option "XkbRules" "xfree86" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" Mode "1280x854" # D: 79.815 MHz, H: 51.963 kHz, V: 60.003 Hz DotClock 79.816 HTimings 1280 1296 1408 1536 VTimings 854 855 858 866 Flags"-HSync" "-VSync" EndMode HorizSync 30-68 VertRefresh 50-85 Option "DPMS" EndSection Section "Device" Option "UseFBDev" "true" Identifier "Card0" Driver "fbdev" VendorName "ATI Technologies Inc" BoardName "Radeon Mobility M7 LW [Radeon Mobility 7500]" BusID "PCI:0:16:0" EndSection The problem I have had with the ati driver prior to hitting this display lockup problem was that sometimes when I would switch between a VT window and the X display (or vice versa), the display would show a sequence of three scanlines all starting at different points. So, line 1, 4, 7, 10, ... would start at the right edge of the screen, lines 2, 5, 8, 11, ... would be indented about 1/8 of the screen and lines 3, 6, 12, 13, ... would be indented 1/4 of the screen. Switching back and forth between a VT and the X display would usually clean up the problem. Very occaisionally the machine would lock up and need a cold boot. There was also a scrolling effect, where unsynced lines would seem to be scrolliny up slowly up. The behavior I am seeing now is a little different, the screen blanks out and there is a log delay before one long bright line is shown at the bottom of the screen. The rest of the screen remains black. I am unable to switch to a VT display, unless I am constantly hitting the control-sequence to switch to a VT. If I wait past a few seconds after the X display shows the bright line, the control sequence always fails to switch me to a VT. It is worth noting that the fbdev driver is working pretty well, though it exhibits the same problem that the ati driver used to have. That is, sometimes when switching between a VT and the X display (or vice versa), the display is munged with unsynced scanlines. 00:10.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Radeon Mobility M7 LW Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 26 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.20-pre7-ben0 ppc [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Oct 3 20:40:10 2002 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->
[Xpert]Trident Blade 9750 Tv OUT
Dear all: Im having some trouble finding documentation on how to make a Trident 9750 card to output video to a TV. Yes, yes, I know that video card sucks, but... hey! I have it on my desk. I want to do something useful with it :). I would like if someone could point me some resources to read (if you know a non-trident-related resource that you think it may be useful to me, just send it!). Thanks in advance! Martin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Tinyx Xigs server error
Hi..
i want to run Xigs tinyx server for CyberPro 5350 pci graphic cards.
i have changed the igsstub.c of igs dirs. such as
while (LinuxFindPci(0x10ea, 0x5000, count , &attr) --> while (LinuxFindPci(0x10ea,
0x5300, count, &attr)
But, when i run Xigs server, error occurred.
I think, after kdMapDevice of igs.c, all data of Cop5xxx structure are 0x, and
no changed.
I don't understand which one is wrong. something is missng at igs codes ?
i added to iopl(3) at souce to change permission. but, no works. I think all regster
value of card is not changed...
if you know the answer, please help.
Bye..
Error log messages are follows( I add ErrorF() in code ).
+
InitOutput
kdInitOutput
InitCard
/* /proc/bus/pci/devices read */
line: 80861a300f808
0400
id != ven_dev
line: 000880861a310
id != ven_dev
line: 00f08086244e0
id != ven_dev
line: 00f8808624400
id != ven_dev
line: 00f98086244b0
a801
0010
id != ven_dev
line: 00fa80862442a
a401
0020usb-uhci
id != ven_dev
line: 00fc808624449
a001
0020usb-uhci
id != ven_dev
line: 024810ea53005f400
f7ff0200
0001
count:-1
n: 6
in LinuxFindPci
attr.address[0]: 0xf400, io: 0, naddr: 1
before kdCardInfoLast
before kdScreenInfoAdd
before xalloc
before bzero
before for
before prev
before next
before card
before KdParse
igs card init
size: 1240
defined linux, undefined __arm__, size: 7864320, addr: 0xf400
address: 0x4017c000
defined linux, undefined __arm__, size: 65536, addr: 0xf480
address: 0x40018000
defined linux, undefined __arm__, size: 540, addr: 0xf48bf000
address: 0x408fc000
defined linux, undefined __arm__, size: 65536, addr: 0xf48a
address: 0x408fd000
igs->cop->control: -1, format: -1, fg: 0x, dst_start: 0x,vga:
0x40018000, framebuff: 0x4017c000, copData: 0x408fd000, size: 540, addr: 0xf400
before igsRedInit
igsRegInit
igsScreen InitigsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeUsable
igsInitScreen
igsCursorInit
igsPreserve
igsSave
igs Enable
isgSetBlank
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsModeSupported
igsGetClock
igsInb
igsInb
igsInb
igsInb
h_total: BIOS255 X125
h_display_end: BIOS255 X 99
h_sync_start: BIOS255 X107
h_sync_end: BIOS 31 X 26
h_blank_start: BIOS255 X 99
h_blank_end: BIOS 63 X 0
offset: BIOS 1023 X100
num_fetch: BIOS 1023 X101
v_total: BIOS 2047 X664
v_display_end: BIOS 2047 X599
v_blank_start: BIOS 2047 X599
v_blank_end: BIOS127 X 8
v_retrace_start: BIOS 2047 X637
v_retrace_end: BIOS 15 X 3
vclk_m: BIOS 2047 X 1236
vclk_n: BIOS255 X151
vclk_p: BIOS 7 X 2
vclk: BIOS 14043 X 5
igsInb
igsInb
isgSetBlank
igsCursorEnable
igsUnloadCursor
isgGetColor
igs Put Color
igsDrawEnable
/* igsdraw.h : #define _igsWaitLoop(cop, mask, value) { \
int __loop = 100; \
while (((cop)
Re: [Xpert]XML format for XF86Config
On Thursday 03 October 2002 5:33 pm, Michael Michael wrote: > --- Keith Packard <[EMAIL PROTECTED]> wrote: > > My hope is that the configuration file becomes > > entirely optional. There's > > essentially nothing there which can't be > > autodetected on a reasonable > > system. > > > > At that point, the format of the file is moot. > > Actually long term I was hoping for this sort of thing > there is still need for the file but if it was XML it > should load easily int a personal preference... > > The big picture is I'd like to move towards a XML > format for flat file view and database for ui > managers. Moving to XML helps a lot in moving on to a > system wide config data base. A zillion config file > formats makes it difficult to contemplate. If everyone > would move to and XML format then supporting config > databases becomes possible. > I would like to see happen in the unix world. It does > require each major subsystem developer to look beyond > there needs. > Considering most of the responses so far I'm not sure > thats going to be easy. As an intermediate solution, can you write a tool that would generate XML from a normal config file, and then convert the XML back into the config file? You'd probably have to do something specialy to handle comments so that users don't lose their comments in the process. I realize that this isn't ideal, but it gives you a chance to prove your point (that the ui tools would be simpler, easier to manage, etc.) without requiring anything from the project. If enough people start using the ui tools, then the project would probably switch to XML. Just my $0.02, Tom Panning [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Liberating the Dell Inspiron 2600
[EMAIL PROTECTED] wrote: >>Hi >> >>This is my first ever submission to a mailing list to get help. If I have got the >etiquette wrong, sorry - please advise. >> >>I am failing to get XFree86 to work on a Dell Inspiron 2600 at a screen resolution >of 1024*768. > > > Maybe this will help: > > http://www.pvv.org/~roarl/inspiron4100.txt > > It is the work of a frend and me. Kim, I believe Peter has a Intel 830 graphics chip, not the ATI Radeon mobility. Peter, Try the latest i810 driver from XFree86 CVS. It contains many fixes for memory allocation. Regards, Jens -- /\ Jens Owen/ \/\ _ [EMAIL PROTECTED] /\ \ \ Steamboat Springs, Colorado ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XML format for XF86Config
Around 14 o'clock on Oct 3, Michael Michael wrote: > The big picture is I'd like to move towards a XML format for flat file view > and database for ui managers. Moving to XML helps a lot in moving on to a > system wide config data base. A zillion config file formats makes it > difficult to contemplate. If everyone would move to and XML format then > supporting config databases becomes possible. It doesn't take everyone moving to make this a useful idea; even moving a few systems to a common configuration language would help reduce the problem, and new systems could then see a clear direction in configuration file support. However, you're not going to get any help in this quest until you've generated a concensus among the community that this is a good and useful idea. That can only be done by providing sample implementations that fit neatly into significant existing systems. It's not that each project is lazy or stupid, it's that the work necessary to actually realize any utility is greater than any individual project can support within the framework of the project itself. > I would like to see happen in the unix world. It does require each major > subsystem developer to look beyond there needs. Considering most of the > responses so far I'm not sure thats going to be easy. If it were easy, we'd already be doing it. I'm all for XML-based configuration files (ref fontconfig), but I'm also realistic about the installed base of X configuration files and the existing community expertise in managing them. You can't throw that away lightly, instead you'll have to replace that with a more compelling solution. Keith PackardXFree86 Core TeamHP Cambridge Research Lab ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XML format for XF86Config
--- Keith Packard <[EMAIL PROTECTED]> wrote: > > My hope is that the configuration file becomes > entirely optional. There's > essentially nothing there which can't be > autodetected on a reasonable > system. > > At that point, the format of the file is moot. > Actually long term I was hoping for this sort of thing there is still need for the file but if it was XML it should load easily int a personal preference... The big picture is I'd like to move towards a XML format for flat file view and database for ui managers. Moving to XML helps a lot in moving on to a system wide config data base. A zillion config file formats makes it difficult to contemplate. If everyone would move to and XML format then supporting config databases becomes possible. I would like to see happen in the unix world. It does require each major subsystem developer to look beyond there needs. Considering most of the responses so far I'm not sure thats going to be easy. Mike __ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]xviddetect
Hi,
XFree86 v4 is now a single server, in debian is under /usr/X11R6/bin/XFree86,
which supports all video hardware through different modules
(see Section "Device")..
probably the easiest way to figure out which module to load is do
XFree86 -configure
it will generate a config file (/root/XF86Config.new i believe) for what it
was able to autodetect and you can take it from there.
hope this helps,
ricardo
At some point in the past you ("savanna" <[EMAIL PROTECTED]>) said:
> As part of my job, I install Linux on a lot of different machines. I've
> just moved to Debian Woody, which uses version 4 of XFree86, not version
> 3 (like Debian Potato).
>
> One of the tools I used regularly was xviddetect, to try and work out
> what video hardware was on the machine. This doesn't appear to come in
> the version 4 server - is there something similar?
>
> I know xf86cfg autodetects hardware, but I'd prefer to get the server
> right the first time, rather than selecting the vga server, then
> fixing the server after the install has finished.
>
> --
> Savanna | Free as in 'free speech',
> GnuPG Pub Key E40FAE08 | not 'free beer'.
>
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]nv driver crash on nForce
I don't recall having any problems with 4.2.0 on nForce. I'm not sure that RedHat's "4.2.0" is really the same as a stock XFree86 4.2.0. There have be cases in the past where they have modified theirs. Try an official XFree86 4.2.0. Mark. On 3 Oct 2002, Mikkel Lauritsen wrote: > Hi all, > > this bug report has been posted by me before, but I unfortunately > got sidetracked and never got to follow up on it. My apologies. > > Whenever I try to run the nv driver in 4.2.0 on my nForce-based > PC the X server crashes and locks the PC, requiring a hard reset > to continue, while the closed-source nvidia driver from NVidia > works perfectly. Because of the hard crash I'm not sure whether > the log file is complete, but it does not seem to contain any > irregularities. > > I'm running RedHat Linux 7.3 on an Asus A7N266-VM with an Athlon > XP1800+ and 1 GB ram. The behavior is exactly the same under RedHat > 8.0, where the X package according to the release notes basically > is 4.2.1, even if the version number is still 4.2.0. > > This problem might of course be a RedHat-ism, so I have reported > the problem there as well. Other people seem to have experienced > the same behavior on different nForce-based boards. > > Do you have any suggestions as to how I might try to track this > one down? In case there is a need for it, I'd be more than happy > to provide log files and any other relevant information. > > Thanks, > Mikkel Lauritsen > > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]nv driver crash on nForce
Hi all, this bug report has been posted by me before, but I unfortunately got sidetracked and never got to follow up on it. My apologies. Whenever I try to run the nv driver in 4.2.0 on my nForce-based PC the X server crashes and locks the PC, requiring a hard reset to continue, while the closed-source nvidia driver from NVidia works perfectly. Because of the hard crash I'm not sure whether the log file is complete, but it does not seem to contain any irregularities. I'm running RedHat Linux 7.3 on an Asus A7N266-VM with an Athlon XP1800+ and 1 GB ram. The behavior is exactly the same under RedHat 8.0, where the X package according to the release notes basically is 4.2.1, even if the version number is still 4.2.0. This problem might of course be a RedHat-ism, so I have reported the problem there as well. Other people seem to have experienced the same behavior on different nForce-based boards. Do you have any suggestions as to how I might try to track this one down? In case there is a need for it, I'd be more than happy to provide log files and any other relevant information. Thanks, Mikkel Lauritsen ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Getting the current mouse coordinates in XFree86
I found some code here http://www.gusnet.cx/proj/miscunix/code/xquerypointer.c and modified it to return the coordinates in "+x+y" format. It actually works really well with the windows I like to use - xterms, aterms, etc. I think you are generally right, many GUI applications don't like -geometry so much, but I wasn't really concerned about those - I use terminals 95% of the time. The next step is, of course, to look at modifying the fluxbox code and getting interactive window placement done from inside there. A project for another time :) Cheers, Dave. JohnFlux wrote: > Sounds cool. But, uh, wasn't there problems with -geometry? > There is some problem like gnome programs don't like it. > I remember a discussion a year back about how should a multi-window program > handle -geometry. And what about programs with splash screens, etc.. > > I have a bad memory, hopefully I'll jog someone else's memory enough for th= > em to flame me and tell me to stfu :) ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Sending SIGUSR1 to X-- is it safe?
I use the 'nv' (xfree86 4.2.1) driver and after a screen blank, the bottom half of the screen is on top and vice versa. I use gdm also. I found that if I do: kill -SIGUSR1 `pidof X` after unblanking, X fixes itself and displays properly. Is this what SIGUSR1 is supposed to do (ie reinitialize X) and can I depend on this in future versions of X. I checked the manpage for Xserver, and though it mentioned this signal, the explanation of what it did was vague. I know about using 'chvt 1 && chvt 7', but I wanted to do this from within an apm/acpi script, and this seemed to work well. Jamie Strandboge -- Email:[EMAIL PROTECTED] GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]problem in Pci.c
On Thu, 3 Oct 2002 [EMAIL PROTECTED] wrote: > This is problem in OpenBSD 3.1 stable , Xfree current. > making all in programs/Xserver/hw/xfree86/os-support/bus... > rm -f Pci.o > gcc -c -O2 -ansi -Dasm=__asm -Wall -Wpointer-arith -Wstrict-prototypes >-Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs >-Wundef-I. -I../../../../../../programs/Xserver/hw/xfree86/common >-I../../../../../../programs/Xserver/hw/xfree86/os-support >-I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 >-I../../../../../.. -I../../../../../../exports/include -DCSRG_BASED -DSHAPE >-DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension > -DPIXPRIV -DPANORAMIX -DRENDER -DRANDR -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV >-DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server >-DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension >-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO -O0 Pci.c > In file included from Pci.c:174: > /usr/include/signal.h: In function `sigaddset': > /usr/include/signal.h:69: warning: redundant redeclaration of `errno' in same scope > /usr/include/errno.h:45: warning: previous declaration of `errno' > /usr/include/signal.h: In function `sigdelset': > /usr/include/signal.h:80: warning: redundant redeclaration of `errno' in same scope > /usr/include/errno.h:45: warning: previous declaration of `errno' > /usr/include/signal.h: In function `sigismember': > /usr/include/signal.h:91: warning: redundant redeclaration of `errno' in same scope > /usr/include/errno.h:45: warning: previous declaration of `errno' > Pci.c: In function `pciInit': > Pci.c:245: syntax error before `}' > *** Error code 1 > Stop in /usr/src/XF4/xc/programs/Xserver/hw/xfree86/os-support/bus (line 990 of >Makefile). > *** Error code 1 > any ideas and fixes? Mea culpa. Should be fixed now. Thanks. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]problem in Pci.c
This is problem in OpenBSD 3.1 stable , Xfree current. making all in programs/Xserver/hw/xfree86/os-support/bus... rm -f Pci.o gcc -c -O2 -ansi -Dasm=__asm -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -I. -I../../../../../../programs/Xserver/hw/xfree86/common -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/include -I../../../../../../exports/include/X11 -I../../../../../.. -I../../../../../../exports/include -DCSRG_BASED -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DRENDER -DRANDR -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO -O0 Pci.c In file included from Pci.c:174: /usr/include/signal.h: In function `sigaddset': /usr/include/signal.h:69: warning: redundant redeclaration of `errno' in same scope /usr/include/errno.h:45: warning: previous declaration of `errno' /usr/include/signal.h: In function `sigdelset': /usr/include/signal.h:80: warning: redundant redeclaration of `errno' in same scope /usr/include/errno.h:45: warning: previous declaration of `errno' /usr/include/signal.h: In function `sigismember': /usr/include/signal.h:91: warning: redundant redeclaration of `errno' in same scope /usr/include/errno.h:45: warning: previous declaration of `errno' Pci.c: In function `pciInit': Pci.c:245: syntax error before `}' *** Error code 1 Stop in /usr/src/XF4/xc/programs/Xserver/hw/xfree86/os-support/bus (line 990 of Makefile). *** Error code 1 any ideas and fixes? Regards, Condor ___ http://www.vcable.net ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]mga drivers from Matrox won't do 6 head
> > > Does anything change when you disable do 'Option "NoAccel" "Yes"'? > > Interesting. I have not tried that. > That one rescued me once when I tried to combine an ATI Mach64 with a NVidia TNT2. With acceleration the mouse left trails, actually all kind of movements left some trails on the screen (window moving, cursor moving, dragging, ...). Disabling acceleration helped. Regards, Mikael ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]mga drivers from Matrox won't do 6 head
> Perhaps it is a hardware problem? Can you ensure all cards do really > work? Have you tried using them one by one? Perhaps it'll do to switch > slots on the mainboard? My 6 head machine works fine under WindowsME. > Does anything change when you disable do 'Option "NoAccel" "Yes"'? Interesting. I have not tried that. Kim0 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Liberating the Dell Inspiron 2600
> Hi > > This is my first ever submission to a mailing list to get help. If I have got the >etiquette wrong, sorry - please advise. > > I am failing to get XFree86 to work on a Dell Inspiron 2600 at a screen resolution >of 1024*768. Maybe this will help: http://www.pvv.org/~roarl/inspiron4100.txt It is the work of a frend and me. Kim0 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]mga drivers from Matrox won't do 6 head
> The mga drivers from Matrox works even worse than the mga driver from > XFree86. > It won't accept modelines that work fine under your mga driver, and under > NetBSD ARM32 kernelmodes, and under WindowsME. > > On the 2 first screens however, everything always works fine. It is > always on the last 4 screens that things go wrong, on both mga drivers. > > I tried different window managers, and it seems its not their problem. > After testing more thoroughly, with x11perf, I see that it is quite > random which X draw operations works. > > Do I really have to rewrite the XFree86 mga driver to make this work? > > Kim0 Perhaps it is a hardware problem? Can you ensure all cards do really work? Have you tried using them one by one? Perhaps it'll do to switch slots on the mainboard? Does anything change when you disable do 'Option "NoAccel" "Yes"'? Can the both PCI cards do 'quadrohead' (hihi) when used without the AGP card? Have you tried the combinations AGP-PCI1, AGP-PCI2, only? Perhaps the card is buggy somehow when combining AGP and PCI versions? Just some ideas, don't know if it could by any of them. Regards, Mikael > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Sony FX190 Laptop and External Display
I have a Sony FX190 which employs a Intel 815 graphics chip and provides both an internal LCD display capable of displaying 1400x1050, and an external display connector port. I'd like to be able to switch the external display ON only, all by itself, just like I used to in Windows, so that I can connect an external projector. The projector only accepts 800x600. When I switch 800x600 on the display, the "viewable area" on the LCD shrinks - I believe this is due to the inability of the LCD to "zoom" the display. In windows, with the Fn+F7 key I could cycle through "LCD", "LCD + External", "External". When on "External" the "viewable area" "zooms out" to fill a normal 800x600 area. I'd like to be able to run this portable with the external display only so that the "view area" zooms out and therefore drives the projector properly. I have scoured the web for Anything regarding this specific issue and this specific chip and one of the authors of the driver software has directed me here. Please help ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Liberating the Dell Inspiron 2600
Hi This is my first ever submission to a mailing list to get help. If I have got the etiquette wrong, sorry - please advise. I am failing to get XFree86 to work on a Dell Inspiron 2600 at a screen resolution of 1024*768. I have tried to solve these problems using the advice in Manuel Chakravarty's article "Liberating the Dell Latitude C400" http://www.cse.unsw.edu.au/~chak/linux/c400.html I have noted below the details of my attempts to use the procedure therein. I have also attached corresponding log-file information. Can anyone suggest what I should try next? Peter Howard Notes follow... 1.0 Base Installation I installed Suse Linux 8.0 from distro CDs using Suse's Yast2 tool. This uses a 2.4.18-4GB kernel and XF86 4.2.0. I included the kernel sources from the distro. The automatic installation was successful and everything seems to work. The X server and the desktop enivironment all work "straight out of the box", BUT it comes up at a very low screen resolution. (I'm not sure what - but definitely < 1024 * 768). The attached .tgz file includes the automatically generated XF86Config, XFree86.0.log.asinstalled & messages.asinstalled to capture this state. As a newcomer, it's not clear to me from this log why it is coming up in low resolution. However the following message is distinctly un-encouraging: (WW) I810(0): Bad V_BIOS checksum. 2.0 Patching the X-Server Gambling that these symptons were connected with the same underlying problems cited in Manuel C's article, I then followed his instructions - with the following observations: Installed XFree86-4.2.0 source from an XFree ftp mirror. (Sources not on the Suse distro CD to my surprise) Applied the patch supplied (i830_driver-1mb-stolen-hack.patch) Compiled the X server as per intructions. Copied i810_drv.o into place as recommended. The article says you have to apply two kernel patches before this will work, but I thought it would be instructive to see what happened if rebooted with just this patch in place. The attached .tgz includes the log file from this run: XFree86.0.log.stolenhack. The log still exhibits the checksum problem. It confirms that the "stolenhack" patch is enabled. It gives up when it encounters unresolved symbols: Symbol XAAFillSolidRects from module /usr/X11R6/lib/modules/drivers/i810_drv.o. 3.0 Patching the kernel I hypothesised that the unresolved symbol problem was probably because the matching kernel patches had not been applied, so proceeded with those. Applied the i830-drm.patch to the sources provided in the XFree86 source tree, and copied the resultant i830.o into place as recommended. This required manual intervention to remove an additional argument to do_munmap() introduced by the patch. (The article explains that this may be necessary on non RedHat distros. Applied the agpgart-i830.patch to the kernel sources installed from Suse distro. Manuel's procedure tells you to copy a particular .config file to /usr/src/version/ before 'make'ing. My source tree did not provide a suitable candidate, besides which there was already one there which looked plausible so I left it in-situ. I don't know how to interpret these files properly. I have included the one that was there in the attachment. The procedure was error free until the 'make modules' phase. This produced several errors, BUT it did successfully build the agpgart.o file required. Which I duly copied into place as suggested. I wrapped up with 'depmod -a' as instructed. The server gives up in exactly the same way as above. The log files are identical (apart from the internal date). Log file included XFree86.0.log.final for completeness. XF86logs.tgz Description: application/compressed
Re: [Xpert]Getting the current mouse coordinates in XFree86
On Thu, Oct 03, 2002 at 07:25:31PM +1200, David Antliff wrote: > > Well, I don't know if it's been done before, but I use Fluxbox and as it > stands, it has no ability to place new windows 'interactively' (i.e. > choose to open an xterm, click where you want it to be positioned). I > know it's simple, but if I had a wrapper for XQueryPointer() then I could > use the same technique for any window manager with any window that > supports the -geometry option, by having the menu or keybinding run a > script that gets the current mouse coordinates. > > Simple really eh? :) Sounds cool. But, uh, wasn't there problems with -geometry? There is some problem like gnome programs don't like it. I remember a discussion a year back about how should a multi-window program handle -geometry. And what about programs with splash screens, etc.. I have a bad memory, hopefully I'll jog someone else's memory enough for them to flame me and tell me to stfu :) JohnFlux > > Dave. > > > On Thu, 3 Oct 2002, Brad Hards wrote: > > > XQueryPointer is probably what you want (Xlib Reference Manual, pg 496-7, also > > in man page :) > > > > What is the idea? > > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert -- msg09222/pgp0.pgp Description: PGP signature
Re: [Xpert]Getting the current mouse coordinates in XFree86
Well, I don't know if it's been done before, but I use Fluxbox and as it stands, it has no ability to place new windows 'interactively' (i.e. choose to open an xterm, click where you want it to be positioned). I know it's simple, but if I had a wrapper for XQueryPointer() then I could use the same technique for any window manager with any window that supports the -geometry option, by having the menu or keybinding run a script that gets the current mouse coordinates. Simple really eh? :) Dave. On Thu, 3 Oct 2002, Brad Hards wrote: > XQueryPointer is probably what you want (Xlib Reference Manual, pg 496-7, also > in man page :) > > What is the idea? ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
