Re: [Flightgear-users] help with ATI fglrx
On Thursday 03 March 2005 04:45, Stefan Lucian Palade wrote: Hello everyone !! Josh your problem is coming from the module owner as you can see in the lsmod listing the owner of the module ( to be read the father of process in linux ) has the owner id : 7 ... what you have to do is edit the startup config. file so the module is inserted at start-up with the owner id 0(root) ... Also if this is not working it will be usefull if I can see the .config file from kernel menuconfig. It could be the DRI suport from the kernel. Send us the file ( it should have around 50Kb). Good Luck !!! = Stefan Palade My fglrx module is used by 8. If this is a UID, on my system it corresponds to the user 'mail'. Incidentally, so is the soundcore module. But both seem to work ok. LeeE ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
Taken from this page, paragraph 31.1, the part about lsmod output: http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/ch-kernel-modules.html For each line, the first column is the name of the module, the second column is the size of the module, and the third column is the use count. Not a user id. -- Jorge Van Hemelryck ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
On Tuesday 01 March 2005 22:33, Josh Babcock wrote: [snip...] I wonder if it's being loaded by the startup scripts or the kernel before X even starts. I guess I will have to turn off X and restart to check. Josh Hmm... I just had another look at your lsmod o/p to check if if the agpgart module was being used and it looks like it is - by via_agp. I'm using an via chipset mobo too but I compile the via chipset support into the kernel as opposed to agpgart support, which I compile as a module. I dunno if this gets you anywhere but it might be worth trying. Do you have POSIX shared memory support enabled? This comes under Virtual memory filesystem support (former shm fs). I believe this is required for the ATI drivers. LeeE ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
Lee Elliott wrote: On Tuesday 01 March 2005 22:33, Josh Babcock wrote: [snip...] I wonder if it's being loaded by the startup scripts or the kernel before X even starts. I guess I will have to turn off X and restart to check. Josh Hmm... I just had another look at your lsmod o/p to check if if the agpgart module was being used and it looks like it is - by via_agp. I'm using an via chipset mobo too but I compile the via chipset support into the kernel as opposed to agpgart support, which I compile as a module. I dunno if this gets you anywhere but it might be worth trying. Do you have POSIX shared memory support enabled? This comes under Virtual memory filesystem support (former shm fs). I believe this is required for the ATI drivers. LeeE ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d Yeah, I have shared memory support. I'll try putting the via drivers in the kernel. Josh ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
Hello everyone !! Josh your problem is coming from the module owner as you can see in the lsmod listing the owner of the module ( to be read the father of process in linux ) has the owner id : 7 ... what you have to do is edit the startup config. file so the module is inserted at start-up with the owner id 0(root) ... Also if this is not working it will be usefull if I can see the .config file from kernel menuconfig. It could be the DRI suport from the kernel. Send us the file ( it should have around 50Kb). Good Luck !!! = Stefan Palade __ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/ ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
On Monday 28 February 2005 22:23, Josh Babcock wrote: OK, this is making me feel kind of stupid. I never really had any problem with the fglrx driver before, but now I'm a bit stumped. I just completely rebuilt my system to take advantage of LVM and the deb package system as well as to upgrade to 2.6.10. Now, I seem to have fglrx working, but alas, 1 FPS in FG. dmesg reports *lots* of these: [fglrx:firegl_agp_lock_pages] *ERROR* agp_allocate_memory_phys_list failed Has anyone else seen this problem? Oh, to avoid confusion, the kernel and fglrx module did not come from a deb repository, I built them by hand. I just don't find the debian build process sane. I also held the Xfree packages so libGL.so wouldn't get clobbered. Josh Gory details below... [snipped...] Are you using the internal ATI agpgart or the 2.6.10 kernel module? I have the line Option UseInternalAGPGART yes in my XF86Config-4 and the kernel agpgart module is not loaded on my system (2.4.27) so I'm guessing that you're using the 2.6.10 kernel module. Afaik, the ATI drivers aren't claimed to be 2.6.x compatible yet - but then I haven't checked them recently. LeeE ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
On Mon, 28 Feb 2005 17:23:23 -0500, Josh wrote in message [EMAIL PROTECTED]: tower:jbabcock$ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 8500 DDR Generic OpenGL version string: 1.3.4893 (X4.3.0-8.10.19) ..tried this card with the open source DRI driver radeon ? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
Arnt Karlsen wrote: On Mon, 28 Feb 2005 17:23:23 -0500, Josh wrote in message [EMAIL PROTECTED]: tower:jbabcock$ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 8500 DDR Generic OpenGL version string: 1.3.4893 (X4.3.0-8.10.19) ..tried this card with the open source DRI driver radeon ? Yes, a long time ago. It was fairly disappointing. I'll have to check and see if it is working now. Josh ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
Lee Elliott wrote: On Monday 28 February 2005 22:23, Josh Babcock wrote: OK, this is making me feel kind of stupid. I never really had any problem with the fglrx driver before, but now I'm a bit stumped. I just completely rebuilt my system to take advantage of LVM and the deb package system as well as to upgrade to 2.6.10. Now, I seem to have fglrx working, but alas, 1 FPS in FG. dmesg reports *lots* of these: [fglrx:firegl_agp_lock_pages] *ERROR* agp_allocate_memory_phys_list failed Has anyone else seen this problem? Oh, to avoid confusion, the kernel and fglrx module did not come from a deb repository, I built them by hand. I just don't find the debian build process sane. I also held the Xfree packages so libGL.so wouldn't get clobbered. Josh Gory details below... [snipped...] Are you using the internal ATI agpgart or the 2.6.10 kernel module? I have the line Option UseInternalAGPGART yes [snip] Nope, I've got it set to yes. If I recall, using the kernel module led to fglrx spewing all sorts of errors in the X log and X falling back to Mesa. I also think I should note that even though I have FB support in my kernel config, using the line: Option UseFBDev true in XF86Config-4 results in X failing to load, with complaints from fglrx about not being able to access the frame buffer. This is really the same X config that I had working before. I think I either did something stupin in my kernel config or there is some change in the code causing a new problem. Thanks, Josh ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
On Tuesday 01 March 2005 21:41, Josh Babcock wrote: Lee Elliott wrote: On Monday 28 February 2005 22:23, Josh Babcock wrote: OK, this is making me feel kind of stupid. I never really had any problem with the fglrx driver before, but now I'm a bit stumped. I just completely rebuilt my system to take advantage of LVM and the deb package system as well as to upgrade to 2.6.10. Now, I seem to have fglrx working, but alas, 1 FPS in FG. dmesg reports *lots* of these: [fglrx:firegl_agp_lock_pages] *ERROR* agp_allocate_memory_phys_list failed Has anyone else seen this problem? Oh, to avoid confusion, the kernel and fglrx module did not come from a deb repository, I built them by hand. I just don't find the debian build process sane. I also held the Xfree packages so libGL.so wouldn't get clobbered. Josh Gory details below... [snipped...] Are you using the internal ATI agpgart or the 2.6.10 kernel module? I have the line Option UseInternalAGPGART yes [snip] Nope, I've got it set to yes. If I recall, using the kernel module led to fglrx spewing all sorts of errors in the X log and X falling back to Mesa. I also think I should note that even though I have FB support in my kernel config, using the line: Option UseFBDev true in XF86Config-4 results in X failing to load, with complaints from fglrx about not being able to access the frame buffer. This is really the same X config that I had working before. I think I either did something stupin in my kernel config or there is some change in the code causing a new problem. Thanks, Josh Hmm... the fact that the agpgart module is loaded on your system seems to imply that the ATI internal agpgart isn't being used. Dunno why though. LeeE ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] help with ATI fglrx
Lee Elliott wrote: On Tuesday 01 March 2005 21:41, Josh Babcock wrote: Lee Elliott wrote: On Monday 28 February 2005 22:23, Josh Babcock wrote: OK, this is making me feel kind of stupid. I never really had any problem with the fglrx driver before, but now I'm a bit stumped. I just completely rebuilt my system to take advantage of LVM and the deb package system as well as to upgrade to 2.6.10. Now, I seem to have fglrx working, but alas, 1 FPS in FG. dmesg reports *lots* of these: [fglrx:firegl_agp_lock_pages] *ERROR* agp_allocate_memory_phys_list failed Has anyone else seen this problem? Oh, to avoid confusion, the kernel and fglrx module did not come from a deb repository, I built them by hand. I just don't find the debian build process sane. I also held the Xfree packages so libGL.so wouldn't get clobbered. Josh Gory details below... [snipped...] Are you using the internal ATI agpgart or the 2.6.10 kernel module? I have the line Option UseInternalAGPGART yes [snip] Nope, I've got it set to yes. If I recall, using the kernel module led to fglrx spewing all sorts of errors in the X log and X falling back to Mesa. I also think I should note that even though I have FB support in my kernel config, using the line: Option UseFBDev true in XF86Config-4 results in X failing to load, with complaints from fglrx about not being able to access the frame buffer. This is really the same X config that I had working before. I think I either did something stupin in my kernel config or there is some change in the code causing a new problem. Thanks, Josh Hmm... the fact that the agpgart module is loaded on your system seems to imply that the ATI internal agpgart isn't being used. Dunno why though. LeeE ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d I wonder if it's being loaded by the startup scripts or the kernel before X even starts. I guess I will have to turn off X and restart to check. Josh ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] help with ATI fglrx
OK, this is making me feel kind of stupid. I never really had any problem with the fglrx driver before, but now I'm a bit stumped. I just completely rebuilt my system to take advantage of LVM and the deb package system as well as to upgrade to 2.6.10. Now, I seem to have fglrx working, but alas, 1 FPS in FG. dmesg reports *lots* of these: [fglrx:firegl_agp_lock_pages] *ERROR* agp_allocate_memory_phys_list failed Has anyone else seen this problem? Oh, to avoid confusion, the kernel and fglrx module did not come from a deb repository, I built them by hand. I just don't find the debian build process sane. I also held the Xfree packages so libGL.so wouldn't get clobbered. Josh Gory details below, also see these files for even more gory details: For less gory details, take a look at my vacation pics in the home directory. http://home.comcast.net/~jrbabcock/temp/XF86Config-4 http://home.comcast.net/~jrbabcock/temp/XFree86.0.log http://home.comcast.net/~jrbabcock/temp/config-2.6.10 Driver version is: fglrx_4_3_0-8.10.19-1.i386 tower:jbabcock$ fgl_glxgears 892 frames in 5.0 seconds = 178.400 FPS 1119 frames in 5.0 seconds = 223.800 FPS 1119 frames in 5.0 seconds = 223.800 FPS 1120 frames in 5.0 seconds = 224.000 FPS tower:jbabcock$ glxgears 4752 frames in 5.0 seconds = 950.400 FPS 5456 frames in 5.0 seconds = 1091.200 FPS 5439 frames in 5.0 seconds = 1087.800 FPS 5441 frames in 5.0 seconds = 1088.200 FPS tower:jbabcock$ lsmod Module Size Used by fglrx 237500 7 lp 7912 0 8250_pnp7936 0 parport_pc 22404 1 parport20608 2 lp,parport_pc floppy 53648 0 i2c_viapro 6220 0 8250_pci 16704 0 8250 20996 2 8250_pnp,8250_pci serial_core19136 1 8250 via_agp 7424 1 agpgart28136 2 via_agp joydev 7872 0 evdev 7360 0 usbhid 23232 0 uhci_hcd 30160 0 usbcore 105464 3 usbhid,uhci_hcd 8139too20544 0 mii 3968 1 8139too snd_cmipci 29472 0 snd_pcm_oss48420 0 snd_mixer_oss 17536 1 snd_pcm_oss snd_pcm84232 2 snd_cmipci,snd_pcm_oss snd_page_alloc 7492 1 snd_pcm snd_opl3_lib9152 1 snd_cmipci snd_timer 21188 2 snd_pcm,snd_opl3_lib snd_hwdep 7236 1 snd_opl3_lib gameport3520 1 snd_cmipci snd_mpu401_uart 6144 1 snd_cmipci snd_rawmidi20064 1 snd_mpu401_uart snd_seq_device 6924 2 snd_opl3_lib,snd_rawmidi snd46116 10 snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore 7392 1 snd ext2 57480 1 mbcache 6660 1 ext2 tulip 46944 0 cpuid 2436 0 tower:jbabcock$ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 8500 DDR Generic OpenGL version string: 1.3.4893 (X4.3.0-8.10.19) tower:jbabcock$ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context client glx vendor string: ATI client glx version string: 1.3 client glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float, GLX_ATI_render_texture GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 8500 DDR Generic OpenGL version string: 1.3.4893 (X4.3.0-8.10.19) OpenGL extensions: GL_ARB_multitexture, GL_EXT_texture_env_add, GL_EXT_compiled_vertex_array, GL_S3_s3tc, GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_transpose_matrix, GL_ARB_vertex_blend, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_window_pos, GL_ATI_element_array, GL_ATI_envmap_bumpmap, GL_ATI_fragment_shader, GL_ATI_map_object_buffer, GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once, GL_ATI_vertex_array_object, GL_ATI_vertex_attrib_array_object, GL_ATI_vertex_streams, GL_ATIX_texture_env_combine3, GL_ATIX_texture_env_route, GL_ATIX_vertex_shader_output_point_size, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
