Re: New ATI fglrx drivers work with AMD64

2005-03-13 Thread Max
Jan,
I did the same things except that I copied fglrx32 libraries from the actual 
debian-i386 installation and used 'apt-get install' within chroot for the rest 
required packages (e.g., xlibs etc.). I also mounted tmpfs from within chroot 
(not from outside like you did) with the command 'mount -t tmpfs tmpfs 
/dev/shm'.
And now DOOM 3 runs under my debian-amd64!!! Speed is not worse than under 
debian-i386.
There are still some problems though that require further investigation. In 
particular, it hang up when I tried to load a saved game. Anyway it's a good 
start ;)
Regards,
Max
Jan Kreuzer wrote:
Hi
here is a qucik description how i got the new fglrx working in 64-bit
and 32-bit chroot:
1)Installed a chroot as stated in
https://alioth.debian.org/docman/vi...o.html#id274243
 2) used alien to convert the driver to a tgz and upacked them to a temp
directory
 3) copied the contents of (driverdir)/usr/X11R6/lib64
to /usr/X11R6/lib64
 4) copied the contents of (driverdir)/usr/X11R6/lib into my chroot
(/var/chroot/sid-ia32/usr/X11R6)
 5) build the kernel module
 6) did a mount -o bind /dev /var/chroot/sid-ia32/dev and a
mount -t tmpfs tmpfs /var/chroot/sid-ia32/dev/shm
to make the 32-bit component of the driver happy
 7) fired up X, tested glxinfo = ok, tested glxinfo32 (fromchroot) = ok
 8) fired up nwn = ok
 9) fired up doom3 = crash :(
Maybe this helps 

P.S.: Please CC me, as i am not on the list (only reading through
archives)
Cheers Jan


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-03-13 Thread Max
Manuel,
These MTRR errors are the reason why direct rendering does not work.
I've just faced a similar problem. Hopefully, in my Tyan Tiger K8W S2875 BIOS setup there is an 
option MTRR Mapping which can be either Continuous or Discrete. The former "explicitly 
describes the PCI hole as non-cacheable" while the latter "leaves the PCI hole below the 
4G boundary undescribed". Continuous is default. All MTRR errors and fglrx direct rendering 
ability had been fixed when I switched MTRR Mapping to Discrete.
You can see the current MTRR state with 'cat /proc/mtrr'.
This is how my MTRR looked with Continuous mapping:
reg00: base=0x (   0MB), size=4096MB: write-back, count=1
reg01: base=0x1 (4096MB), size=1024MB: write-back, count=1
reg02: base=0xc000 (3072MB), size=1024MB: uncachable, count=1   < this 
was problematic
And how they look now:
reg00: base=0x1 (4096MB), size=1024MB: write-back, count=1
reg01: base=0x (   0MB), size=2048MB: write-back, count=1
reg02: base=0x8000 (2048MB), size=1024MB: write-back, count=1
reg03: base=0xe000 (3584MB), size= 128MB: write-combining, count=1
reg04: base=0xf000 (3840MB), size= 128MB: write-combining, count=1
I guess that two 128Mb regions are video card memory and AGP aperture.
Max
Manuel Capinha wrote:
Small add-on:
My problem is somewhere in the kernel module, it seems:
(from dmesg)
[fglrx] module loaded - fglrx 8.8.25 [Jan 14 2005] on minor 0
Fire GL built-in AGP-support
Based on agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 941M
agpgart: Detected AMD 8151 chipset
agpgart: AGP aperture is 32M @ 0x400
Power management callback for AGP chipset installed
[fglrx] AGP detected, AgpState   = 0x1f000b7b (hardware caps of chipset)
mtrr: type mismatch for 400,200 old: write-back new: write-combining
[fglrx:firegl_unlock] *ERROR* Process 25297 using kernel context 0
PID 25297 is my X server.
So, is anyone else seeing this ? I've got no clue about that error message :/
Thanks once again,
Manuel
On Tue, 18 Jan 2005 15:11:32 +, Manuel Capinha <[EMAIL PROTECTED]> wrote:
I got it to install and I can now boot X using ATI's proprietary
drivers, but I got no OpenGL support. Running glxgears gives me around
60 fps, so I know that's being done in software!
Looking in /var/log/XFree86.0.log I found this:
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.8.25
(II) fglrx(0): Date: Jan 14 2005
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE:2.6.9-9-amd64-k8-smp
(II) fglrx(0): Build-Kernel MODVERSIONS:no
(II) fglrx(0): Build-Kernel __SMP__:no
(II) fglrx(0): Build-Kernel PAGE_SIZE:  0x1000
(II) fglrx(0): [drm] register handle = 0xff5f
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_EINVAL"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xff41d000
at 0x2a955da000
(WW) fglrx(0): ***
(WW) fglrx(0): * DRI initialization failed!  *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available*
(WW) fglrx(0): * *
Is anyone else seeing this or does everyone else but my have OpenGL by
hardware ?
TIA,
Manuel
On Tue, 18 Jan 2005 15:10:46 +0100, Filippo Carone
<[EMAIL PROTECTED]> wrote:
* Lorenzo Milesi ([EMAIL PROTECTED]) ha scritto:
Hi, I'd just like to give the list a heads up that the new ATI fglrx
drivers actually work with amd64.  They're only available (as usual) in
rpm's but I hacked together Flavio's debian packages and with a bit of
manual copying around it works.
Can you tell me how did you do it?
I tried just alien-ing the rpm but fails because it tries to overwrite
`/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.
use the --force-overwrite switch of dpkg.
cheers,
fc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-19 Thread Frederik Schueler
Hi,

On Tue, Jan 18, 2005 at 02:04:56PM +, Jean-Luc Coulon (f5ibh) wrote:
> quick and drity :just build the package with alien then install the  
> .deb with --force-overwrite...

Looking into the .rpm, this procedure WILL break your system.

the /usr/lib/libGL.so.1.2 will be replaced by a 32bit one, while the 64bit
one will be stored in /usr/X11R6/lib64/libGL.so.1.2 where no app will
ever look for it.

The correct locations are:

libGL.so (libc6,x86-64) => /usr/lib/libGL.so
libGL.so (libc6) => /emul/ia32-linux/usr/lib/libGL.so

as ldconfig -p | grep libGL.so shows on a sane system.

just --force-overwrite'installing a deb created by alien from the rpm
will break your OpenGL subsystem.


Using --force-overwrite as a magic bullet on every occasion, like more 
and more people on this list seem to think of it, is a very bad
development. 
Please help fixing buggy packages, filing bugs and patches, instead of
beating things into shape with a sledge hammer.


Kind regards
Frederik Schueler

-- 
ENOSIG


pgpr1loSdMiw2.pgp
Description: PGP signature


Re: New ATI fglrx drivers work with AMD64

2005-01-19 Thread Jan Kreuzer
Hi
here is a qucik description how i got the new fglrx working in 64-bit
and 32-bit chroot:

1)Installed a chroot as stated in
https://alioth.debian.org/docman/vi...o.html#id274243
 2) used alien to convert the driver to a tgz and upacked them to a temp
directory
 3) copied the contents of (driverdir)/usr/X11R6/lib64
to /usr/X11R6/lib64
 4) copied the contents of (driverdir)/usr/X11R6/lib into my chroot
(/var/chroot/sid-ia32/usr/X11R6)
 5) build the kernel module
 6) did a mount -o bind /dev /var/chroot/sid-ia32/dev and a
mount -t tmpfs tmpfs /var/chroot/sid-ia32/dev/shm
to make the 32-bit component of the driver happy
 7) fired up X, tested glxinfo = ok, tested glxinfo32 (fromchroot) = ok
 8) fired up nwn = ok
 9) fired up doom3 = crash :(


Maybe this helps 

P.S.: Please CC me, as i am not on the list (only reading through
archives)

Cheers Jan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-19 Thread Lorenzo Milesi
> (WW) fglrx(0): ***
> (WW) fglrx(0): * DRI initialization failed!  *
> (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
> (WW) fglrx(0): * 2D acceleraton available (MMIO) *
> (WW) fglrx(0): * no 3D acceleration available*
> (WW) fglrx(0): * *

I'm getting this error too.
But I have enabled Radeon DRI in kernel, as well as agp for the nvidia
chip (I have the /dev/agpgart)
any idea?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Nick Hemsley
That fixed it. Thanks alot.
Took me a while to get progs loading the right libGL.so though.. rm 
this.. rm that :p

cheers
Peter Nelson wrote:
Nick Hemsley wrote:
OK scrap that, I was using gcc3.3 instead of 3.4. changing the 
symlink worked for me, although I think you can do it in the make.sh.

The module now starts, starting XFree86 however freezes the system 
(not sure if I can ssh), and /var/log/mesages shows:
Jan 19 14:00:02 localhost kernel: Call 
Trace:{:fglrx:firegl_init_aperture+160}
Jan 19 14:00:02 localhost kernel:
{:fglrx:firegl_agp_acquire+0} 
{:fglrx:__ke_agp_available+50} 

well, certainly something agp related.  Try setting
Option "UseInternalAGPGART" "no"
In /etc/X11/XF86Config-4.  I think that's the same crash I got and 
that's how I fixed it.  If not, try various permutations of related 
AGP things.

-Peter


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Peter Nelson
Nick Hemsley wrote:
OK scrap that, I was using gcc3.3 instead of 3.4. changing the symlink 
worked for me, although I think you can do it in the make.sh.

The module now starts, starting XFree86 however freezes the system 
(not sure if I can ssh), and /var/log/mesages shows:
Jan 19 14:00:02 localhost kernel: Call 
Trace:{:fglrx:firegl_init_aperture+160}
Jan 19 14:00:02 localhost kernel:
{:fglrx:firegl_agp_acquire+0} 
{:fglrx:__ke_agp_available+50} 
well, certainly something agp related.  Try setting
Option "UseInternalAGPGART" "no"
In /etc/X11/XF86Config-4.  I think that's the same crash I got and 
that's how I fixed it.  If not, try various permutations of related AGP 
things.

-Peter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Nick Hemsley
OK scrap that, I was using gcc3.3 instead of 3.4. changing the symlink 
worked for me, although I think you can do it in the make.sh.

The module now starts, starting XFree86 however freezes the system (not 
sure if I can ssh), and /var/log/mesages shows:

Jan 19 14:00:02 localhost kernel: fglrx: module license 'Proprietary. 
(C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
Jan 19 14:00:02 localhost kernel: [fglrx] Maximum main memory to use for 
locked dma buffers: 916 MBytes.
Jan 19 14:00:02 localhost kernel: ACPI: PCI interrupt :01:00.0[A] -> 
GSI 16 (level, low) -> IRQ 16
Jan 19 14:00:02 localhost kernel: [fglrx] module loaded - fglrx 8.8.25 
[Jan 14 2005] on minor 0
Jan 19 14:00:02 localhost kernel: Fire GL built-in AGP-support
Jan 19 14:00:02 localhost kernel: Based on agpgart interface v0.99 (c) 
Jeff Hartmann
Jan 19 14:00:02 localhost kernel: agpgart: Maximum main memory to use 
for agp memory: 941M
Jan 19 14:00:02 localhost kernel: PML4 2ab7f067 PGD 3d33b067 PMD 
3d7d3067 PTE 0
Jan 19 14:00:02 localhost kernel: CPU 0
Jan 19 14:00:02 localhost kernel: Modules linked in: fglrx ipv6 
snd_via82xx snd_ac97_codec snd_pcm snd_timer snd_page_alloc gameport 
snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore i2c_viapro 
i2c_core ehci_hcd joydev usbhid uhci_hcd via82cxxx shpchp pci_hotplug 
nls_iso8859_1 nls_cp437 vfat fat ext2 tsdev mousedev evdev psmouse 
sk98lin ide_generic ide_cd ide_core cdrom ext3 jbd mbcache reiserfs 
sd_mod unix fbcon crc32 font bitblit vesafb cfbcopyarea cfbimgblt 
cfbfillrect sata_via libata scsi_mod
Jan 19 14:00:02 localhost kernel: Pid: 5137, comm: XFree86 Tainted: 
P  2.6.10-9-amd64-k8
Jan 19 14:00:02 localhost kernel: RIP: 0010:[_end+535170336/2132725760] 
{:fglrx:__fgl_agp_init+544}
Jan 19 14:00:02 localhost kernel: RSP: 0018:01001c283e38  EFLAGS: 
00210246
Jan 19 14:00:02 localhost kernel: RAX:  RBX: 
0003ad00 RCX: 0030
Jan 19 14:00:02 localhost kernel: RDX: 08c0 RSI: 
801c60d0 RDI: 
Jan 19 14:00:02 localhost kernel: RBP:  R08: 
0036 R09: 0002
Jan 19 14:00:02 localhost kernel: R10:  R11: 
 R12: a028d2b0
Jan 19 14:00:02 localhost kernel: R13:  R14: 
 R15: a02aaec8
Jan 19 14:00:02 localhost kernel: FS:  002a95c496e0() 
GS:803e5a00() knlGS:
Jan 19 14:00:02 localhost kernel: CS:  0010 DS:  ES:  CR0: 
8005003b
Jan 19 14:00:02 localhost kernel: CR2: 0044 CR3: 
00101000 CR4: 06e0
Jan 19 14:00:02 localhost kernel: Process XFree86 (pid: 5137, threadinfo 
01001c282000, task 01003dc83850)
Jan 19 14:00:02 localhost kernel: Stack: 01002892e940 
00014000 a02aae80 a02809a0
Jan 19 14:00:02 localhost kernel:a02ab200 
0001 a028d2b0 40046463
Jan 19 14:00:02 localhost kernel:010029065580 a0277e92
Jan 19 14:00:02 localhost kernel: Call 
Trace:{:fglrx:firegl_init_aperture+160}
Jan 19 14:00:02 localhost kernel:
{:fglrx:firegl_agp_acquire+0} 
{:fglrx:__ke_agp_available+50}
Jan 19 14:00:02 localhost kernel:
{:fglrx:drm_agp_init+82} 
{:fglrx:_firegl_agp_acquire+112}
Jan 19 14:00:02 localhost kernel:
{:fglrx:firegl_agp_acquire+107} 
{:fglrx:firegl_ioctl+334}
Jan 19 14:00:02 localhost kernel:
{sys_ioctl+895} {error_exit+0}
Jan 19 14:00:02 localhost kernel:
{system_call+126}
Jan 19 14:00:02 localhost kernel:
Jan 19 14:00:02 localhost kernel: Code: 0f b7 75 44 66 81 fe 86 80 0f 85 
57 05 00 00 0f b7 45 46 3d

If anyone has any idea what this means, any suggestions would be 
welcome, otherwise I will send a bug report to ATI. *sigh*

Cheers all
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Andrei Mikhailovsky
Many thanks, that solved the issue ))

On Tue, 2005-01-18 at 21:20 -0500, Peter Nelson wrote:
> I had similar issues on i386 when using both the fglrx drivers and the 
> radeonfb console frame buffer.  Try disabling your console frame buffer 
> (or maybe loading vesafb instead of radeonfb?) and it should be fine.  
> Obviously a sub-optimal solution, but I think accelerated X11 is far 
> more important than accelerated console.
> 
> -Peter
> 
> Andrei Mikhailovsky wrote:
> 
> >I've managed to get the 64bit drivers running fine, games and
> >screensavers are now very fast ))
> >
> >However, i am experiencing screen corruption when I switch to the
> >console.
> >
> >Does anyone have similar issues?
> >
> >Thanks
> >
> >On Mon, 2005-01-17 at 23:08 -0500, Peter Nelson wrote:
> >  
> >
> >>Hi, I'd just like to give the list a heads up that the new ATI fglrx 
> >>drivers actually work with amd64.  They're only available (as usual) in 
> >>rpm's but I hacked together Flavio's debian packages and with a bit of 
> >>manual copying around it works.  Hopefully someone with a bit more 
> >>knowledge of how things like /usr/X11R6/lib vs lib64 are supposed to 
> >>work can make a clean package (I just copied stuff around untill it worked).
> >>
> >>Get from http://www.ati.com/support/drivers/linux/radeon-linux64.html
> >>
> >>-Peter
> >>
> >>
> >>
> >>
> 
> 
-- 
Andrei Mikhailovsky
Arhont Ltd - Information Security

Web: http://www.arhont.com
 http://www.wi-foo.com
Tel: +44 (0)870 4431337
Fax: +44 (0)117 9690141
PGP: Key ID - 0xFF67A4F4
PGP: Server - keyserver.pgp.com


signature.asc
Description: This is a digitally signed message part


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Nick Hemsley
Thanks for the heads up, I loooked about 3 days ago
I first tried via flavios site (wierd probs with debhelper) and with the 
alien+ati way. I also tried the patch here: (as per flavio's page) 
http://www.rage3d.org/board/showthread.php?t=33798874.

This is with the ATI+alien method:
After building I try and install and get the following error:
FATAL: Error inserting fglrx 
(/lib/modules/2.6.10-9-amd64-k8/kernel/drivers/char/drm/fglrx.ko): 
Invalid module format
failed.

This is the build process, the warnings at the bottom (about 
init_module...) seem pertinent. any ideas?

[EMAIL PROTECTED]:/lib/modules/fglrx/build_mod# sh make.sh
ATI module generator V 2.0
==
initializing...
cleaning...
patching 'highmem.h'...
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.10-9-amd64-k8/build 
SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/kernel-headers-2.6.10-9-amd64-k8'
 CC [M]  /lib/modules/fglrx/build_mod/2.6.x/agpgart_be.o
 CC [M]  /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 
`firegl_stub_putminor':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:511: warning: 
`inter_module_put' is deprecated (declared at include/linux/module.h:582)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:513: warning: 
`inter_module_unregister' is deprecated (declared at 
include/linux/module.h:578)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 
`firegl_stub_register':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:533: warning: 
`inter_module_register' is deprecated (declared at 
include/linux/module.h:577)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:564: warning: 
`inter_module_put' is deprecated (declared at include/linux/module.h:582)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 
`firegl_get_user_ptr':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1073: warning: 
assignment makes pointer from integer without a cast
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 
`firegl_put_user_ptr':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1105: warning: cast 
from pointer to integer of different size
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1105: warning: cast 
from pointer to integer of different size
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1105: warning: cast 
from pointer to integer of different size
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1105: warning: cast 
from pointer to integer of different size
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: At top level:
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2646: warning: 
initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 
`__ke_vm_map':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2707: warning: 
`remap_page_range' is deprecated (declared at include/linux/mm.h:770)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2774: warning: 
`remap_page_range' is deprecated (declared at include/linux/mm.h:770)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2811: warning: 
`remap_page_range' is deprecated (declared at include/linux/mm.h:770)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 
`__ke_agp_uninit':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:3132: warning: 
`inter_module_put' is deprecated (declared at include/linux/module.h:582)
 LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
 Building modules, stage 2.
 MODPOST
*** Warning: "cleanup_module" 
[/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko] undefined!
*** Warning: "init_module" [/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko] 
undefined!
 CC  /lib/modules/fglrx/build_mod/2.6.x/fglrx.mod.o
 LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
make[1]: Leaving directory `/usr/src/kernel-headers-2.6.10-9-amd64-k8'
build succeeded with return value 0
duplicating results into driver repository...
done.
==
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
==

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Peter Nelson
I had similar issues on i386 when using both the fglrx drivers and the 
radeonfb console frame buffer.  Try disabling your console frame buffer 
(or maybe loading vesafb instead of radeonfb?) and it should be fine.  
Obviously a sub-optimal solution, but I think accelerated X11 is far 
more important than accelerated console.

-Peter
Andrei Mikhailovsky wrote:
I've managed to get the 64bit drivers running fine, games and
screensavers are now very fast ))
However, i am experiencing screen corruption when I switch to the
console.
Does anyone have similar issues?
Thanks
On Mon, 2005-01-17 at 23:08 -0500, Peter Nelson wrote:
 

Hi, I'd just like to give the list a heads up that the new ATI fglrx 
drivers actually work with amd64.  They're only available (as usual) in 
rpm's but I hacked together Flavio's debian packages and with a bit of 
manual copying around it works.  Hopefully someone with a bit more 
knowledge of how things like /usr/X11R6/lib vs lib64 are supposed to 
work can make a clean package (I just copied stuff around untill it worked).

Get from http://www.ati.com/support/drivers/linux/radeon-linux64.html
-Peter
   


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Andrei Mikhailovsky
I've managed to get the 64bit drivers running fine, games and
screensavers are now very fast ))

However, i am experiencing screen corruption when I switch to the
console.

Does anyone have similar issues?

Thanks

On Mon, 2005-01-17 at 23:08 -0500, Peter Nelson wrote:
> Hi, I'd just like to give the list a heads up that the new ATI fglrx 
> drivers actually work with amd64.  They're only available (as usual) in 
> rpm's but I hacked together Flavio's debian packages and with a bit of 
> manual copying around it works.  Hopefully someone with a bit more 
> knowledge of how things like /usr/X11R6/lib vs lib64 are supposed to 
> work can make a clean package (I just copied stuff around untill it worked).
> 
> Get from http://www.ati.com/support/drivers/linux/radeon-linux64.html
> 
> -Peter
> 
> 
-- 
Andrei Mikhailovsky
Arhont Ltd - Information Security

Web: http://www.arhont.com
 http://www.wi-foo.com
Tel: +44 (0)870 4431337
Fax: +44 (0)117 9690141
PGP: Key ID - 0xFF67A4F4
PGP: Server - keyserver.pgp.com


signature.asc
Description: This is a digitally signed message part


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread zeeman
Hi!
use the --force-overwrite switch of dpkg.
OK it worked.
Now I tried building kernel module. All fine. 
ERROR when insmod: undefined symbol pci_find_class in module

so I edited agpgart_be.c replacing pci_find_class with pci_get_class
(from /usr/src/linux/Documentation/pci.txt) and the module loads fine
into the kernel, and I can see it with lsmod.
Same problem and solution here.
But now if I run startx I get an error message saying flgrx module
can't be found! :(
You have to add the following lines in your /etc/X11/XF86Config-4 in 
your Files-Section:

Section "Files"
[...]
ModulePath  "/usr/X11R6/lib64/modules"
ModulePath  "/usr/X11R6/lib/modules"
[...]
EndSection
Greets
Sebastian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Lorenzo Milesi
>  use the --force-overwrite switch of dpkg.

OK it worked.
Now I tried building kernel module. All fine. 
ERROR when insmod: undefined symbol pci_find_class in module

so I edited agpgart_be.c replacing pci_find_class with pci_get_class
(from /usr/src/linux/Documentation/pci.txt) and the module loads fine
into the kernel, and I can see it with lsmod.
But now if I run startx I get an error message saying flgrx module
can't be found! :(

I'm using 2.6.10 custom kernel. I tried 2.6.9 but I get more build
module errors.

Any help?
thanks
maxxer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Lennart Sorensen
On Tue, Jan 18, 2005 at 08:05:47PM +0100, Cyril Chaboisseau wrote:
>  Hi,
> 
> I succeded in building all the fglrx packages with
> apt-get -b source fglrx-installer and by replacing the original
> fglrx-4.3.0-3.14.6.i386.rpm with fglrx_4_3_0-8.8.25-1.i386.rpm + adding
> amd64 to the Architecture -> debian/rules binary
> 
> then I installed fglrx-4.3.0-control-qt3 fglrx-4.3.0-driver
> fglrx-4.3.0-kernel-src with dpkg
> 
> finally I tried to recompile the kernel + modules (make-kpkg) but failed
> towards the end :
> 
> [...]
> /usr/bin/make -C /usr/src/linux SUBDIRS=/usr/src/modules/fglrx-4.3.0-3.14.6 
> modules
> make[2]: Entering directory `/usr/src/linux-2.6.10'
>   LD [M]  /usr/src/modules/fglrx-4.3.0-3.14.6/fglrx.o
> ld: Relocatable linking with relocations from format elf32-i386 
> (/usr/src/modules/fglrx-4.3.0-3.14.6/libfglrx_ip.a.GCC3(vm.o)) to format 
> elf64-x86-64 (/usr/src/modules/fglrx-4.3.0-3.14.6/fglrx.o) is not supported 

Looks like your package makes it try and link a 32bit object into the
64bit kernel module, so most likely the driver package includes both and
you got the wrong one.  The wrong file appears to be libfglrx_ip.a.GCC3

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Cyril Chaboisseau
 Hi,

I succeded in building all the fglrx packages with
apt-get -b source fglrx-installer and by replacing the original
fglrx-4.3.0-3.14.6.i386.rpm with fglrx_4_3_0-8.8.25-1.i386.rpm + adding
amd64 to the Architecture -> debian/rules binary

then I installed fglrx-4.3.0-control-qt3 fglrx-4.3.0-driver
fglrx-4.3.0-kernel-src with dpkg

finally I tried to recompile the kernel + modules (make-kpkg) but failed
towards the end :

[...]
/usr/bin/make -C /usr/src/linux SUBDIRS=/usr/src/modules/fglrx-4.3.0-3.14.6 
modules
make[2]: Entering directory `/usr/src/linux-2.6.10'
  LD [M]  /usr/src/modules/fglrx-4.3.0-3.14.6/fglrx.o
ld: Relocatable linking with relocations from format elf32-i386 
(/usr/src/modules/fglrx-4.3.0-3.14.6/libfglrx_ip.a.GCC3(vm.o)) to format 
elf64-x86-64 (/usr/src/modules/fglrx-4.3.0-3.14.6/fglrx.o) is not supported 


any idea how to correct that ?

I have gcc 3.3 and 3.4 installed and gcc 3.3.5 is used by default

-- 
Cyril Chaboisseau


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Javier Kohen
Lorenzo Milesi wrote:
Hi, I'd just like to give the list a heads up that the new ATI fglrx
drivers actually work with amd64.  They're only available (as usual) in
rpm's but I hacked together Flavio's debian packages and with a bit of
manual copying around it works.  

Can you tell me how did you do it?
I tried just alien-ing the rpm but fails because it tries to overwrite 
`/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.


I added the following diversion manually:
diversion of /usr/X11R6/lib/libGL.so.1.2 to
/usr/X11R6/lib/libGL.so.1.2.xlibmesa by fglrx
$ man dpkg-divert
Then you don't have to worry about --force-overwrite or other options,
it will just work and leave the original file intact (renamed).
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Filippo Carone
* Manuel Capinha ([EMAIL PROTECTED]) ha scritto:
> I got it to install and I can now boot X using ATI's proprietary
> drivers, but I got no OpenGL support. Running glxgears gives me around
> 60 fps, so I know that's being done in software!
> 
> (EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_EINVAL"

 is the agp correctly probed? For example I get:
$ dmesg | grep agp
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: AGP aperture is 128M @ 0xe000
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Found an AGP 3.0 compliant device at :00:00.0.

 and you should have:

$ ls -l /dev/agpgart 
crw-rw  1 root video 10, 175 Jan 18 08:50 /dev/agpgart

 
> Is anyone else seeing this or does everyone else but my have OpenGL by
> hardware ?
> 

 I have a radeon9200 and I used to have the proprietary driver on my
previous i386 architecture. On AMD64 I'm using the opensource drivers
getting ~2000fps with windowed glxgears (~130 fullscreen), so fully
accelerated.

 cheers,
 fc


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Manuel Capinha
Small add-on:

My problem is somewhere in the kernel module, it seems:
(from dmesg)

[fglrx] module loaded - fglrx 8.8.25 [Jan 14 2005] on minor 0
Fire GL built-in AGP-support
Based on agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 941M
agpgart: Detected AMD 8151 chipset
agpgart: AGP aperture is 32M @ 0x400
Power management callback for AGP chipset installed
[fglrx] AGP detected, AgpState   = 0x1f000b7b (hardware caps of chipset)
mtrr: type mismatch for 400,200 old: write-back new: write-combining
[fglrx:firegl_unlock] *ERROR* Process 25297 using kernel context 0


PID 25297 is my X server.

So, is anyone else seeing this ? I've got no clue about that error message :/

Thanks once again,
Manuel

On Tue, 18 Jan 2005 15:11:32 +, Manuel Capinha <[EMAIL PROTECTED]> wrote:
> I got it to install and I can now boot X using ATI's proprietary
> drivers, but I got no OpenGL support. Running glxgears gives me around
> 60 fps, so I know that's being done in software!
> 
> Looking in /var/log/XFree86.0.log I found this:
> 
> (II) fglrx(0): Kernel Module Version Information:
> (II) fglrx(0): Name: fglrx
> (II) fglrx(0): Version: 8.8.25
> (II) fglrx(0): Date: Jan 14 2005
> (II) fglrx(0): Desc: ATI FireGL DRM kernel module
> (II) fglrx(0): Kernel Module version matches driver.
> (II) fglrx(0): Kernel Module Build Time Information:
> (II) fglrx(0): Build-Kernel UTS_RELEASE:2.6.9-9-amd64-k8-smp
> (II) fglrx(0): Build-Kernel MODVERSIONS:no
> (II) fglrx(0): Build-Kernel __SMP__:no
> (II) fglrx(0): Build-Kernel PAGE_SIZE:  0x1000
> (II) fglrx(0): [drm] register handle = 0xff5f
> (EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_EINVAL"
> (EE) fglrx(0): cannot init AGP
> (II) fglrx(0): [drm] removed 1 reserved context for kernel
> (II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xff41d000
> at 0x2a955da000
> (WW) fglrx(0): ***
> (WW) fglrx(0): * DRI initialization failed!  *
> (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
> (WW) fglrx(0): * 2D acceleraton available (MMIO) *
> (WW) fglrx(0): * no 3D acceleration available*
> (WW) fglrx(0): * *
> 
> Is anyone else seeing this or does everyone else but my have OpenGL by
> hardware ?
> 
> TIA,
> Manuel
> 
> 
> On Tue, 18 Jan 2005 15:10:46 +0100, Filippo Carone
> <[EMAIL PROTECTED]> wrote:
> > * Lorenzo Milesi ([EMAIL PROTECTED]) ha scritto:
> > > > Hi, I'd just like to give the list a heads up that the new ATI fglrx
> > > > drivers actually work with amd64.  They're only available (as usual) in
> > > > rpm's but I hacked together Flavio's debian packages and with a bit of
> > > > manual copying around it works.
> > >
> > > Can you tell me how did you do it?
> > > I tried just alien-ing the rpm but fails because it tries to overwrite
> > > `/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.
> >
> >  use the --force-overwrite switch of dpkg.
> >
> >  cheers,
> >  fc
> >
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >
> >
>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Manuel Capinha
I got it to install and I can now boot X using ATI's proprietary
drivers, but I got no OpenGL support. Running glxgears gives me around
60 fps, so I know that's being done in software!

Looking in /var/log/XFree86.0.log I found this:

(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.8.25
(II) fglrx(0): Date: Jan 14 2005
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE:2.6.9-9-amd64-k8-smp
(II) fglrx(0): Build-Kernel MODVERSIONS:no
(II) fglrx(0): Build-Kernel __SMP__:no
(II) fglrx(0): Build-Kernel PAGE_SIZE:  0x1000
(II) fglrx(0): [drm] register handle = 0xff5f
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_EINVAL"
(EE) fglrx(0): cannot init AGP
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0xff41d000
at 0x2a955da000
(WW) fglrx(0): ***
(WW) fglrx(0): * DRI initialization failed!  *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available*
(WW) fglrx(0): * *




Is anyone else seeing this or does everyone else but my have OpenGL by
hardware ?

TIA,
Manuel


On Tue, 18 Jan 2005 15:10:46 +0100, Filippo Carone
<[EMAIL PROTECTED]> wrote:
> * Lorenzo Milesi ([EMAIL PROTECTED]) ha scritto:
> > > Hi, I'd just like to give the list a heads up that the new ATI fglrx
> > > drivers actually work with amd64.  They're only available (as usual) in
> > > rpm's but I hacked together Flavio's debian packages and with a bit of
> > > manual copying around it works.
> >
> > Can you tell me how did you do it?
> > I tried just alien-ing the rpm but fails because it tries to overwrite
> > `/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.
> 
>  use the --force-overwrite switch of dpkg.
> 
>  cheers,
>  fc
> 
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Filippo Carone
* Lorenzo Milesi ([EMAIL PROTECTED]) ha scritto:
> > Hi, I'd just like to give the list a heads up that the new ATI fglrx
> > drivers actually work with amd64.  They're only available (as usual) in
> > rpm's but I hacked together Flavio's debian packages and with a bit of
> > manual copying around it works.  
> 
> Can you tell me how did you do it?
> I tried just alien-ing the rpm but fails because it tries to overwrite 
> `/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.

 use the --force-overwrite switch of dpkg.

 cheers,
 fc
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Jean-Luc Coulon (f5ibh)
Le 18.01.2005 14:57:45, Lorenzo Milesi a écrit :
Hi, I'd just like to give the list a heads up that the new ATI fglrx
drivers actually work with amd64.  They're only available (as usual)
in
rpm's but I hacked together Flavio's debian packages and with a bit
of
manual copying around it works.
Can you tell me how did you do it?
I tried just alien-ing the rpm but fails because it tries to overwrite
`/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.
quick and drity :just build the package with alien then install the  
.deb with --force-overwrite...

Jean-Luc


pgpNNOsUsIePe.pgp
Description: PGP signature


Re: New ATI fglrx drivers work with AMD64

2005-01-18 Thread Lorenzo Milesi
> Hi, I'd just like to give the list a heads up that the new ATI fglrx
> drivers actually work with amd64.  They're only available (as usual) in
> rpm's but I hacked together Flavio's debian packages and with a bit of
> manual copying around it works.  

Can you tell me how did you do it?
I tried just alien-ing the rpm but fails because it tries to overwrite 
`/usr/X11R6/lib/libGL.so.1.2', owned by xlibmesa-gl package.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]