[gentoo-user] ATI XPress 200m - direct rendering don't work

[gentoo-user] ATI XPress 200m - direct rendering don't work

[Rudson Ribeiro Alves]

Hi list,

I was wanting install ati-drivers with DRI suport on my notebook zv6000
(AMD 64bit Linux  Gentoo system), but the module fglrx don't load

~ # modprobe fglrx
FATAL: Error inserting fglrx
(/lib/modules/2.6.16-gentoo-r9-ati-3/video/fglrx.ko): Unknown symbol in
module, or unknown parameter (see dmesg)

~ # dmesg
...
fglrx: Unknown symbol inter_module_unregister
fglrx: Unknown symbol inter_module_get_request
fglrx: Unknown symbol pm_register
fglrx: Unknown symbol inter_module_put
fglrx: Unknown symbol pm_unregister_all
fglrx: Unknown symbol inter_module_register
fglrx: Unknown symbol inter_module_unregister
fglrx: Unknown symbol inter_module_get_request
fglrx: Unknown symbol pm_register
fglrx: Unknown symbol inter_module_put
fglrx: Unknown symbol pm_unregister_all
fglrx: Unknown symbol inter_module_register

The /var/log/Xorg.0.log show:
...
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(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): ********************************************* *
...

My kernel is 2.6.16-gentoo-r9 with AGP suport seting:
...
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_DRM is not set
...

Ati-drivers is 8.18.8-r2. The emerge of ati-drivers show several warning
messages of undefined symbols.

Thanks, Alves

		
_______________________________________________________ 
Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! 
http://br.mobile.yahoo.com/mailalertas/ 
 


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] ATI XPress 200m - direct rendering don't work

[Bob Sanders]

On Sat, 24 Jun 2006 03:17:36 +0000
Rudson Ribeiro Alves <rudsonalves@yahoo.com.br> wrote:

> Hi list,
> 
> I was wanting install ati-drivers with DRI suport on my notebook zv6000
> (AMD 64bit Linux  Gentoo system), but the module fglrx don't load
> 
> ~ # modprobe fglrx
> FATAL: Error inserting fglrx
> (/lib/modules/2.6.16-gentoo-r9-ati-3/video/fglrx.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
> 
> ~ # dmesg
> ...
> fglrx: Unknown symbol inter_module_unregister
> fglrx: Unknown symbol inter_module_get_request
> fglrx: Unknown symbol pm_register
> fglrx: Unknown symbol inter_module_put
> fglrx: Unknown symbol pm_unregister_all
> fglrx: Unknown symbol inter_module_register
> fglrx: Unknown symbol inter_module_unregister
> fglrx: Unknown symbol inter_module_get_request
> fglrx: Unknown symbol pm_register
> fglrx: Unknown symbol inter_module_put
> fglrx: Unknown symbol pm_unregister_all
> fglrx: Unknown symbol inter_module_register


You need to set the depreciated option in the kernel.

	Power Management --> Legacy Power Management

Bob

> The /var/log/Xorg.0.log show:
> ...
> (II) Loading extension ATIFGLRXDRI
> (II) fglrx(0): doing DRIScreenInit
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is -1, (Unknown error 999)
> drmOpenDevice: open result is -1, (Unknown error 999)
> drmOpenDevice: Open failed
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is -1, (Unknown error 999)
> drmOpenDevice: open result is -1, (Unknown error 999)
> drmOpenDevice: Open failed
> [drm] failed to load kernel module "fglrx"
> (II) fglrx(0): [drm] drmOpen failed
> (EE) fglrx(0): DRIScreenInit failed!
> (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): ********************************************* *
> ...
> 
> My kernel is 2.6.16-gentoo-r9 with AGP suport seting:
> ...
> CONFIG_AGP=y
> CONFIG_AGP_AMD64=y
> # CONFIG_AGP_INTEL is not set
> # CONFIG_DRM is not set
> ...
> 
> Ati-drivers is 8.18.8-r2. The emerge of ati-drivers show several warning
> messages of undefined symbols.
> 
> Thanks, Alves
> 
> 		
> _______________________________________________________ 
> Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! 
> http://br.mobile.yahoo.com/mailalertas/ 
>  
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 


-- 
-  
Are you living in the real world?
-  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] ATI XPress 200m - direct rendering don't work

[Rudson Ribeiro Alves]

Hi again,


I have set

Power Manangement --> Legacy Power Management

and

Device Drivers --> Memory Technology Devices (MTD)  ---> NAND Flash
Device Drivers --> DiskOnChip 2000, Millennium and Millennium Plus

to define inter_module_register, inter_modules...

After this, ati-drivers compiler without warnings.

To activate DRM, I go to BIOS edit:

"So configuring the BIOS to use the 128M video memory plus another 128M
taken from the system seems to work for me... as a workaround at least.
Good thing good be someone to check why lspci always states 256M since
it may be a bug either in the BIOS or in the lspci code...."
(http://gentoo-wiki.com/HARDWARE_Gentoo_Linux_64bit_on_HP_Pavilion_zv6000_series_notebook)

Ok. After restart X, with DRI, the note give the memory error:

Bad page state in process 'X'
page:ffff8100015df438 flags:0x4000000000000414 mapping:0000000000000000
mapcount
:0 count:0
Trying to fix it up, but a reboot is needed
Backtrace:

Call Trace: <ffffffff80157219>{bad_page+89}
<ffffffff801576b3>{free_hot_cold_pag
e+131}
       <ffffffff801602d2>{unmap_vmas+1234}
<ffffffff801649fd>{unmap_region+189}
       <ffffffff80164df5>{do_munmap+565} <ffffffff8016563d>{sys_munmap+77}
       <ffffffff8010abf6>{system_call+126}
[fglrx] free  PCIe = 54804480
[fglrx] max   PCIe = 54804480
[fglrx] free  LFB = 115666944
[fglrx] max   LFB = 115666944
[fglrx] free  Inv = 0
[fglrx] max   Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0
[fglrx] total FB  = 0
[fglrx] total PCIe = 16384
...

The X start with DRI, but gl programs and X halt the system in the exit.

This is the and of this tunnel?

Thanks,
Alves

> On Sat, 24 Jun 2006 03:17:36 +0000
> Rudson Ribeiro Alves <rudsonalves@yahoo.com.br> wrote:
>
>   
>> Hi list,
>>
>> I was wanting install ati-drivers with DRI suport on my notebook zv6000
>> (AMD 64bit Linux  Gentoo system), but the module fglrx don't load
>>
>> ~ # modprobe fglrx
>> FATAL: Error inserting fglrx
>> (/lib/modules/2.6.16-gentoo-r9-ati-3/video/fglrx.ko): Unknown symbol in
>> module, or unknown parameter (see dmesg)
>>
>> ~ # dmesg
>> ...
>> fglrx: Unknown symbol inter_module_unregister
>> fglrx: Unknown symbol inter_module_get_request
>> fglrx: Unknown symbol pm_register
>> fglrx: Unknown symbol inter_module_put
>> fglrx: Unknown symbol pm_unregister_all
>> fglrx: Unknown symbol inter_module_register
>> fglrx: Unknown symbol inter_module_unregister
>> fglrx: Unknown symbol inter_module_get_request
>> fglrx: Unknown symbol pm_register
>> fglrx: Unknown symbol inter_module_put
>> fglrx: Unknown symbol pm_unregister_all
>> fglrx: Unknown symbol inter_module_register
>>     
>
>
> You need to set the depreciated option in the kernel.
>
> 	Power Management --> Legacy Power Management
>
> Bob
>
>   
>> The /var/log/Xorg.0.log show:
>> ...
>> (II) Loading extension ATIFGLRXDRI
>> (II) fglrx(0): doing DRIScreenInit
>> drmOpenDevice: node name is /dev/dri/card0
>> drmOpenDevice: open result is -1, (Unknown error 999)
>> drmOpenDevice: open result is -1, (Unknown error 999)
>> drmOpenDevice: Open failed
>> drmOpenDevice: node name is /dev/dri/card0
>> drmOpenDevice: open result is -1, (Unknown error 999)
>> drmOpenDevice: open result is -1, (Unknown error 999)
>> drmOpenDevice: Open failed
>> [drm] failed to load kernel module "fglrx"
>> (II) fglrx(0): [drm] drmOpen failed
>> (EE) fglrx(0): DRIScreenInit failed!
>> (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): ********************************************* *
>> ...
>>
>> My kernel is 2.6.16-gentoo-r9 with AGP suport seting:
>> ...
>> CONFIG_AGP=y
>> CONFIG_AGP_AMD64=y
>> # CONFIG_AGP_INTEL is not set
>> # CONFIG_DRM is not set
>> ...
>>
>> Ati-drivers is 8.18.8-r2. The emerge of ati-drivers show several warning
>> messages of undefined symbols.
>>
>> Thanks, Alves
>>
>> 		
>> _______________________________________________________ 
>> Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! 
>> http://br.mobile.yahoo.com/mailalertas/ 
>>  
>>
>> -- 
>> gentoo-user@gentoo.org mailing list
>>
>>
>>     
>
>
>   


		
_______________________________________________________ 
Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! 
http://br.mobile.yahoo.com/mailalertas/ 
 


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] ATI XPress 200m - direct rendering don't work

[Bob Sanders]

On Sun, 25 Jun 2006 11:26:48 +0000
Rudson Ribeiro Alves <rudsonalves@yahoo.com.br> wrote:


> The X start with DRI, but gl programs and X halt the system in the exit.
> 
> This is the and of this tunnel?
> 

Not anything I can recommend from here.  If GL is causing a halt and the bad
memory location is present, perhaps a bad memory module.  Or a bad controller
on the cpu.  I did have that happen to me once.  But it only occured when
compiling nvidia drivers.  Replaced the cpu and everything was fine.

As to the ATI drivers, they continue to cause numerous people grief.

Bob
-  
-- 
gentoo-user@gentoo.org mailing list