 |
 |
 |
 |
| Guides & Solutions (No Questions) Post your guides here (No links to Blogs accepted). You can also append your comments/questions to a guide, but don't start a new thread to ask a question. Use another forum for that. |

9th July 2012, 09:00 AM
|
|
Registered User
|
|
Join Date: Jul 2012
Location: watsontown
Posts: 47

|
|
|
Re: F17 Nvidia guide
Cool then I don't really care, and even if I did I doubt nvidia will fix it.
Their prioty is windows, always has been.
I never had a single nvidia driver issue using their software on windows.
But just because they won't provide support to my driver on linux, doesn't mean I don't have the right to use it.
The only wasted computer, is the one thrown away for a newer one.
http://www.greenhome.com/info/articl..._community/56/
---------- Post added at 08:00 AM ---------- Previous post was at 06:10 AM ----------
Final Solution Xfce:
Code:
rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
abrt-addon-kerneloops-2.0.10-3.fc17.i686
akmod-nvidia-173xx-173.14.35-1.fc17.i686
kernel-3.3.4-5.fc17.i686
kernel-3.4.4-5.fc17.i686
kernel-devel-3.4.4-5.fc17.i686
kernel-headers-3.4.4-5.fc17.i686
kmod-nvidia-173xx-3.4.4-5.fc17.i686-173.14.35-1.fc17.i686
libreport-plugin-kerneloops-2.0.10-3.fc17.i686
nvidia-settings-1.0-18.fc17.i686
nvidia-xconfig-1.0-16.fc17.i686
xorg-x11-drv-nvidia-173xx-173.14.35-1.fc17.i686
xorg-x11-drv-nvidia-173xx-libs-173.14.35-1.fc17.i686
3.4.4-5.fc17.i686
nvidia 7103834 24
i2c_core 28180 2 i2c_viapro,nvidia
# RPM Fusion - nvidia-173xx-xorg.conf
#
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "true"
EndSection
Code:
lspci |grep VGA
00:09.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1)
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] (rev 01)
Code:
glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGI_swap_control, GLX_NV_float_buffer, GLX_ARB_fbconfig_float,
GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap,
GLX_EXT_framebuffer_sRGB, GLX_NV_present_video
GLX version: 1.3
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer,
GLX_ARB_get_proc_address
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce FX 5500/PCI/SSE2/3DNOW!
OpenGL version string: 2.1.2 NVIDIA 173.14.35
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_fragment_program,
GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader,
GL_ARB_half_float_pixel, GL_ARB_imaging, GL_ARB_multisample,
GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_pixel_buffer_object,
GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow,
GL_ARB_shader_objects, GL_ARB_shading_language_100,
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_dot3,
GL_ARB_texture_mirrored_repeat, GL_ARB_texture_rectangle,
GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object,
GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos,
GL_S3_s3tc, GL_EXT_texture_env_add, 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_compiled_vertex_array, GL_EXT_Cg_shader,
GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit,
GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_object,
GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays,
GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels,
GL_EXT_paletted_texture, GL_EXT_pixel_buffer_object,
GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_shadow_funcs,
GL_EXT_shared_texture_palette, GL_EXT_stencil_two_side,
GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_compression_s3tc,
GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod,
GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_sRGB,
GL_EXT_timer_query, GL_EXT_vertex_array, GL_IBM_rasterpos_clip,
GL_IBM_texture_mirrored_repeat, GL_KTX_buffer_region, GL_NV_blend_square,
GL_NV_copy_depth_to_color, GL_NV_depth_clamp, GL_NV_fence,
GL_NV_float_buffer, GL_NV_fog_distance, GL_NV_fragment_program,
GL_NV_fragment_program_option, GL_NV_framebuffer_multisample_coverage,
GL_NV_half_float, GL_NV_light_max_exponent, GL_NV_multisample_filter_hint,
GL_NV_occlusion_query, GL_NV_packed_depth_stencil, GL_NV_pixel_data_range,
GL_NV_point_sprite, GL_NV_primitive_restart, GL_NV_register_combiners,
GL_NV_register_combiners2, GL_NV_texgen_reflection,
GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4,
GL_NV_texture_expand_normal, GL_NV_texture_rectangle,
GL_NV_texture_shader, GL_NV_texture_shader2, GL_NV_texture_shader3,
GL_NV_vertex_array_range, GL_NV_vertex_array_range2, GL_NV_vertex_program,
GL_NV_vertex_program1_1, GL_NV_vertex_program2,
GL_NV_vertex_program2_option, GL_SGIS_generate_mipmap,
GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow,
GL_SUN_slice_accum
120 GLX Visuals
 Side note, if and when the gnome shel/NVIDIAl bug might be fixed where might I find out about?
|

18th July 2012, 07:41 AM
|
 |
Registered User
|
|
Join Date: Jun 2007
Location: Aubagne France
Age: 58
Posts: 398

|
|
|
Re: F17 Nvidia guide
Hi all.
I test F18 rawhide, can I install akmod-nvidia with this rawhide ?
|

18th July 2012, 07:45 AM
|
|
Guest
|
|
Posts: n/a

|
|
|
Re: F17 Nvidia guide
Quote:
Originally Posted by chepioq
Hi all.
I test F18 rawhide, can I install akmod-nvidia with this rawhide ?
|
Yes but you will need to ensure it's a non-debug kernel.
|

18th July 2012, 01:50 PM
|
 |
Registered User
|
|
Join Date: Jun 2007
Location: Aubagne France
Age: 58
Posts: 398

|
|
|
Re: F17 Nvidia guide
Quote:
|
Yes but you will need to ensure it's a non-debug kernel.
|
How can see if kernel is a debug one ?
The latest is kernel-3.5.0-0.rc7.git0.1.fc18, I think it's a debug ...
|

18th July 2012, 02:29 PM
|
|
Guest
|
|
Posts: n/a

|
|
|
Re: F17 Nvidia guide
Quote:
Originally Posted by chepioq
How can see if kernel is a debug one ?
The latest is kernel-3.5.0-0.rc7.git0.1.fc18, I think it's a debug ...
|
Read the changelog
Code:
rpm -q --changelog kernel-3.5.0-0.rc7.git0.1.fc18
|

18th July 2012, 04:04 PM
|
 |
Registered User
|
|
Join Date: Jun 2007
Location: Aubagne France
Age: 58
Posts: 398

|
|
|
Re: F17 Nvidia guide
Thank
Code:
[dominique@dominique Documents]$ rpm -q --changelog kernel-3.5.0-0.rc7.git0.1.fc18 | more
* lun. juil. 16 2012 Justin M. Forbes <jforbes@redhat.com> - 3.5.0-0.rc7.git0.1
- Linux v3.5-rc7
- Disable debugging options.
I install akmod-nvidia and see if that work.
==EDIT==
OK, that's good, I am with drivers nvidia 304.22
Thank
==EDIT 2==
But I can see on koji, the next kernel (kernel-3.5.0-0.rc7.git1.2.fc18) become debug
Quote:
|
* Tue Jul 17 2012 Justin M. Forbes <jforbes@redhat.com> - 3.5.0-0.rc7.git1.2 - Reenable debugging options.
|
Last edited by chepioq; 18th July 2012 at 04:30 PM.
|

20th July 2012, 12:11 AM
|
|
Registered User
|
|
Join Date: Jan 2005
Posts: 26

|
|
|
Re: F17 Nvidia guide
I have a problem with the driver....
On a 64bit install The installation of mesa-libGL.i686 (32bit package) causes issues (i.e missing graphics, etc) with 32 bit games.
If I remove the package its fine - however one major issue - that is a dependency of wine...
How can I avoid this conflict between mesa i686 and nvidia i686 ?
|

31st July 2012, 04:07 AM
|
|
Registered User
|
|
Join Date: Jul 2012
Location: Toronto
Posts: 1

|
|
|
Re: F17 Nvidia Won't Boot to GUI
I have two video cards. The second is an Nvidia. I installed the new drivers and rebooted. The boot screen gets to the end but the GUI does not stay loaded and I don't get a command prompt.
Attached are the outputs for the requested commands.
Any help is appreciated.
|

1st August 2012, 03:54 PM
|
|
Registered User
|
|
Join Date: Jul 2009
Posts: 45

|
|
|
Re: F17 Nvidia guide
Thanks for the guide. Any chance to add some undo steps?
I.e. what to do, if you want to return to nouveau?
/Kenneth
|

1st August 2012, 03:57 PM
|
|
Guest
|
|
Posts: n/a

|
|
|
Re: F17 Nvidia guide
Quote:
Originally Posted by mrbrown79
Thanks for the guide. Any chance to add some undo steps?
I.e. what to do, if you want to return to nouveau?
/Kenneth
|
step
1.
Code:
su
yum erase *\nvidia\*
reboot
done!
|

4th August 2012, 07:49 AM
|
|
Registered User
|
|
Join Date: May 2007
Posts: 76

|
|
|
XBMC has me blue with 3.5.0-2 and 304.30-1
Having a very bizarre problem today. Yum update last night brought me up both to kernel 3.5.0-2 and to nvidia 304.30-1. Everything else I do works fine--except xbmc. Whenever I start xbmc up I get only blues on my screen (not as in a bluescreen, it's as if you were using an rgb monitor and had forgotten to plug in the r and g cables). This persists even when xbmc is in windowed mode, but everything goes back to normal when I exit xbmc.
My install of xbmc is from rpmfusion, xbmc-11.0-1.fc17.x86_64, and it worked perfectly well yesterday before the kernel and nvidia driver updated. As you can see below, previous to the update I was on kernel 3.4.6-2 and nvidia 295.59-1.
I *did* try booting into 3.4.6-2 (which is why you see akmod having created a kmod for nvidia 304.30-1 for that kernel), and the blue did occur there as well, which tends to have me blaming the nvidia update.
Is there any known issues such as this, can anyone reproduce, and more importantly, am I missing a simple fix?
Requested information is below:
#rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
abrt-addon-kerneloops-2.0.10-4.fc17.x86_64
akmod-nvidia-304.30-1.fc17.x86_64
kernel-3.4.5-2.fc17.x86_64
kernel-3.4.6-2.fc17.x86_64
kernel-3.5.0-2.fc17.x86_64
kernel-devel-3.4.5-2.fc17.x86_64
kernel-devel-3.4.6-2.fc17.x86_64
kernel-devel-3.5.0-2.fc17.x86_64
kernel-headers-3.5.0-2.fc17.x86_64
kmod-nvidia-3.4.5-2.fc17.x86_64-295.59-1.fc17.5.x86_64
kmod-nvidia-3.4.6-2.fc17.x86_64-304.30-1.fc17.x86_64
kmod-nvidia-3.5.0-2.fc17.x86_64-304.30-1.fc17.x86_64
libreport-plugin-kerneloops-2.0.10-3.fc17.x86_64
nvidia-settings-1.0-19.fc17.x86_64
nvidia-xconfig-1.0-17.fc17.x86_64
xorg-x11-drv-nvidia-304.30-1.fc17.x86_64
xorg-x11-drv-nvidia-libs-304.30-1.fc17.i686
xorg-x11-drv-nvidia-libs-304.30-1.fc17.x86_64
3.5.0-2.fc17.x86_64
nvidia 11236004 43
i2c_core 38177 3 i2c_i801,nvidia,videodev
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 304.30 (mockbuild@builder1.ovh.rpmfusion.lan) Thu Aug 2 00:54:52 CEST 2012
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from data in "/etc/sysconfig/keyboard"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Seiko/Epson"
HorizSync 31.6 - 47.4
VertRefresh 40.0 - 60.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro 2000M"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "metamodes" "1366x768_60 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
#lspci |grep VGA
01:00.0 VGA compatible controller: nVidia Corporation GF106 [Quadro 2000M] (rev a1)
|

4th August 2012, 08:02 AM
|
 |
Registered User
|
|
Join Date: Jun 2007
Location: Aubagne France
Age: 58
Posts: 398

|
|
|
Re: F17 Nvidia guide
See this bug report on rpmfusion bugzilla : https://bugzilla.rpmfusion.org/show_bug.cgi?id=2434
Driver 304.30 is broken.
You downgrade this driver with those commands :
Code:
su
yum erase *\nvidia\*
yum install akmod-nvidia-295.53-1.fc17.1 xorg-x11-drv-nvidia-libs-295.53-\*.{x86_64,i686} xorg-x11-drv-nvidia-295.53-1.fc17 nvidia-settings-1.0-18.fc17 nvidia-xconfig-1.0-16.fc17
|

4th August 2012, 08:07 AM
|
|
Registered User
|
|
Join Date: May 2007
Posts: 76

|
|
|
Re: F17 Nvidia guide
 After an entire day of searching I finally used the right search terms and discovered that Second Life users are having the same issue literally five minutes after posting my question--for reference that thread is here: http://forums.fedoraforum.org/showthread.php?t=282841
I used those commands and they worked perfectly. I'm surprised that rpmfusion has not yet pulled 304 until there is a fix, but it is still there.
Thank you for the link to the bug report so I can keep an eye on it and know when it is safe not to exclude *\nvidia\* from updates again!
|

4th August 2012, 01:36 PM
|
 |
Registered User
|
|
Join Date: Sep 2008
Location: Thailand
Age: 36
Posts: 355

|
|
|
Re: F17 Nvidia guide
Interesting that many people get it. I'm dual-booted, so I might ride it out. Is there any guessing how long a wait it is till a fix comes in?
OpenTTD has the same problem.
__________________
Greetz (and thanks for all the help!)
BenTrein
The internet isn't a highway, it's a swamp. The more you surf the more it draws you in!
Great authors suffer from Writer's Block. I cherrish my Writer's Blog!
|

5th August 2012, 12:56 AM
|
|
Guest
|
|
Posts: n/a

|
|
|
Re: F17 Nvidia guide
Quote:
Originally Posted by BenTrein
Interesting that many people get it. I'm dual-booted, so I might ride it out. Is there any guessing how long a wait it is till a fix comes in?
OpenTTD has the same problem.
|
Ask nvidia!
---------- Post added 5th August 2012 at 12:56 AM ---------- Previous post was 4th August 2012 at 01:44 PM ----------
Fix released
http://download1.rpmfusion.org/nonfr...rv-nvidia.html
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 16:54 (Thursday, 23-05-2013)
|
|
 |
 |
 |
 |
|
|