Re: [Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock

2002-10-11 Thread José Fonseca 

Sorry for the delay, but it has been a busy day today.

The libxaa.a module build from today's CVS using gcc-2.95.3/glibc-2.2.5 is 
available at
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/libxaa.a.bz2
This expands to some fat 6MB due to the debug info, but first try it as
is before attempt to strip anything out of it.

I hope this helps to discover the Sig11 problem.

José Fonseca


On Fri, Oct 11, 2002 at 01:22:13AM +0200, Michel Dänzer wrote:
On Fre, 2002-10-11 at 00:24, José Fonseca wrote:
[...]
 Michel, what does exactly this mean?

We don't have a way to find out the version of an XFree86 module
directly yet (I understand the XFree86 CVS trunk has that now). So the
radeon driver tries to load version 1.1 of libxaa. If that succeeds, it
knows it can use the new facilities for line acceleration. If it fails,
the driver knows it's version 1.0.0 and switches to backwards
compatibility mode.

 Would this problem (the signal 11) go away if libxaa.a was included in
 the binary snapshots?

Maybe, maybe not.



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

[spyro@f2s.com: Re: [Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock]

2002-10-11 Thread José Fonseca 

- Forwarded message from Ian Molton [EMAIL PROTECTED] -

Date: Fri, 11 Oct 2002 22:11:50 +0100
From: Ian Molton [EMAIL PROTECTED]
Subject: Re: [Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock
To: José Fonseca [EMAIL PROTECTED]

On Fri, 11 Oct 2002 20:31:53 +0100
José Fonseca [EMAIL PROTECTED] wrote:



The libxaa.a module build from today's CVS using
gcc-2.95.3/glibc-2.2.5 is available at
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/libxaa.a.bz2
This expands to some fat 6MB due to the debug info, but first try it
as is before attempt to strip anything out of it.

I hope this helps to discover the Sig11 problem.


Works great here.

I must say the new radeon driver is nice - such low CPU usage this box
hasnt seen in a while on Q3 and xmms ;)

props, all.

- End forwarded message -


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock

2002-10-11 Thread Pawel Salek 
On 2002.10.11 21:31 José Fonseca wrote:

Sorry for the delay, but it has been a busy day today.

The libxaa.a module build from today's CVS using 
gcc-2.95.3/glibc-2.2.5 is available at
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/libxaa.a.bz2
This expands to some fat 6MB due to the debug info, but first try it 
as
is before attempt to strip anything out of it.

I hope this helps to discover the Sig11 problem.

This fixes the problem for me (on RH8.0, radeon snapshot). And I nearly 
lost the hope.

I think it would be nice to have the snapshots working smoothly again, 
they are really useful for people like me, who would like to follow the 
development but the due to notorius lack of spare time cannot afford 
tracking CVS changes.

Thanks!

-pawel


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock

2002-10-10 Thread Pawel Salek 

On 2002.10.10 18:09 Michel Dänzer wrote:
 Do you also see the signal 11 in the X server log? [snip]
 
 That won't help the signal 11 though, which is probably still due to
 some kind of incompatibility in the binary snapshots.

Yes, I see signal 11 in the log (attached). Strangely, since the 
snapshots are supposedly compiled on RH8.0 (i.e. the same as mine), I 
thought it would not be a problem! Another strange for me thing is that 
the screen is not reset to text mode - but the keyboard works as it 
still was attached to the console.

Pawel



XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 23 January 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.18-11smp i686 [ELF] 
Build Host: daffy.perf.redhat.com
 
Module Loader present
OS Kernel: Linux version 2.4.18-14 ([EMAIL PROTECTED]) (gcc version 
3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 13:35:50 EDT 2002 
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 10 23:51:24 2002
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout Anaconda Configured
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device ATI Radeon Mobility M6
(**) |--Input Device Mouse0
(**) |--Input Device Mouse1
(**) |--Input Device Keyboard0
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc102
(**) XKB: model: pc102
(**) Option XkbLayout se
(**) XKB: layout: se
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to unix/:7100
(**) 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.5
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.0, 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.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x8090, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,3575 card 8086,1969 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,3576 card , rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,2482 card , rev 01 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,2484 card , rev 01 class 0c,03,00 hdr 00
(II) PCI: 00:1e:0: chip 8086,2448 card , rev 41 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,248c card , rev 01 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,248a card , rev 01 class 01,01,8a hdr 00
(II) PCI: 00:1f:3: chip 8086,2483 card , rev 01 class 0c,05,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,2485 card 1558,0420 rev 01 class 04,01,00 hdr 00
(II) PCI: 00:1f:6: chip 8086,2486 card 1558,1800 rev 01 class 07,03,00 hdr 00
(II) PCI: 01:00:0: chip 1002,4c59 card 1558,0420 rev 00 class 03,00,00 hdr 00
(II) PCI: 02:02:0: chip 104c,8023 card 1558,0420 rev 00 class 0c,00,10 hdr 00
(II) PCI: 02:04:0: chip 10ec,8139 card 1558,8586 rev 10 class 02,00,00 hdr 00
(II) PCI: 02:07:0: chip 1180,0476 card , rev 88 class 06,07,00 hdr 82
(II) PCI: 02:07:1: chip 1180,0476 card , rev 88 class 06,07,00 hdr 82
(II) PCI: 02:07:2: chip 1180,0576 card , rev 00 class 08,80,00 hdr 80
(II) PCI: End of PCI scan
(II) LoadModule: scanpci
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor=The XFree86 Project
compiled for 4.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) UnloadModule: scanpci
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(II) Host-to-PCI bridge:
(II) PCI-to-ISA bridge:
(II) PCI-to-PCI bridge:
(II) PCI-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1  0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0x -

Re: [Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock

2002-10-10 Thread José Fonseca 

On Thu, Oct 10, 2002 at 11:58:23PM +0200, Pawel Salek wrote:
On 2002.10.10 18:09 Michel Dänzer wrote:
Do you also see the signal 11 in the X server log? [snip]

That won't help the signal 11 though, which is probably still due to
some kind of incompatibility in the binary snapshots.

Yes, I see signal 11 in the log (attached). Strangely, since the 
snapshots are supposedly compiled on RH8.0 (i.e. the same as mine), I 

Not quite: the snapshots are now being built on chroot'd environment with
gcc-2.95.3 and glibc-2.2.5, which should suite everyone.

thought it would not be a problem! Another strange for me thing is that 
the screen is not reset to text mode - but the keyboard works as it 
still was attached to the console.


XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72) / X Window System
[...]
(II) Loading sub module xaa
(II) LoadModule: xaa
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor=The XFree86 Project
   compiled for 4.2.0, module version = 1.0.0
   ABI class: XFree86 Video Driver, version 0.5
(WW) module minor version (0) is less than the required minor version (1)
[...]

Michel, what does exactly this mean? Would this problem (the signal 11) go 
away if libxaa.a was included in the binary snapshots?

José Fonseca



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Dri-devel] snapshot radeon-20021009 problem report: radeon_unlock

2002-10-09 Thread Pawel Salek 

Hi,

I have got a following messages on boot with current snapshot 
radeon-20021009, running with ATI Radeon Mobility M6 LY rev 0, stock 
RH8.0 kernel (2.4.18-14 with a whole lot of patches).

modprobe: modprobe: Can't locate module char-major-226
last message repeated 3 times

kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
kernel: agpgart: Maximum main memory to use for agp memory: 439M
kernel: agpgart: Detected Intel i830M chipset
kernel: agpgart: AGP aperture is 32M @ 0xea00
kernel: [drm] AGP 0.99 on Unknown @ 0xea00 32MB
kernel: [drm] Initialized radeon 1.6.0 20020828 on minor 0
kernel: [drm:radeon_unlock] *ERROR* Process 665 using kernel context 0
gm[664]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
kernel: [drm:radeon_unlock] *ERROR* Process 672 using kernel context 0
gdm[671]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
kernel: [drm:radeon_unlock] *ERROR* Process 674 using kernel context 0
gdm[673]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
kernel: [drm:radeon_unlock] *ERROR* Process 676 using kernel context 0

My impression is that it is more of a kernel module problem than the 
driver's but that a wild guess only.

(just ask if more information is needed).

-pawel


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel