Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
The latest driver update (urpmi --auto-update => dkms-nvidia-current-295-20-2) fixes the problem, but I had to reboot twice to make it work. JC
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/6 EatDirt : > On 02/03/12 22:44, Wolfgang Bornath wrote: > >>> AFAIK you need to reconfigure your system to use the proprietary >>> modules... >> >> >> Yes, that's to be expected anyway. Thx >> > > Or tweak harddrake to let you in peace with X and video; > > checkout /etc/sysconfig/harddrake2/service.conf > > AUTORECONFIGURE_RIGHT_XORG_DRIVER=no > DETECT_VIDEO=no No, this is no practical solution for the long run. I need the proprietary driver working correctly. So I need to know if something is wrong, so I can start repairing (or reporting). -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
On 02/03/12 22:44, Wolfgang Bornath wrote: AFAIK you need to reconfigure your system to use the proprietary modules... Yes, that's to be expected anyway. Thx Or tweak harddrake to let you in peace with X and video; checkout /etc/sysconfig/harddrake2/service.conf AUTORECONFIGURE_RIGHT_XORG_DRIVER=no DETECT_VIDEO=no cheers, Chris.
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
On 2012.03.06, at 14:08, Colin Guthrie wrote: > 'Twas brillig, and Barry Jackson at 06/03/12 12:26 did gyre and gimble: >> You could try blacklisting the nouveau module - but that won't fix the >> underlying issue - it may however get you working as a temporary fix ;) > > If dkms-nvidia isn't building, then a blacklist likely won't help! :) With this fix I got it bulding, found in google: --- conftest.sh.orig2012-03-06 14:26:04.518194430 +0100 +++ conftest.sh 2012-03-06 14:19:20.684477926 +0100 @@ -126,7 +126,7 @@ CFLAGS="$BASE_CFLAGS $MACH_CFLAGS $OUTPUT_CFLAGS -I$HEADERS $AUTOCONF_CFLAGS" if [ "$ARCH" = "i386" -o "$ARCH" = "x86_64" ]; then -CFLAGS="$CFLAGS -I$SOURCES/arch/x86/include" +CFLAGS="$CFLAGS -I$SOURCES/arch/x86/include -I$SOURCES/arch/x86/include/generated" elif [ "$ARCH" = "ARMv7" ]; then CFLAGS="$CFLAGS -I$SOURCES/arch/arm/include" fi -- J.A. Magallon \ Software is like sex: \ It's better when it's free
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
Yes ! Xavier Le 06/03/2012 14:08, Colin Guthrie a écrit : > 'Twas brillig, and Barry Jackson at 06/03/12 12:26 did gyre and gimble: >> You could try blacklisting the nouveau module - but that won't fix the >> underlying issue - it may however get you working as a temporary fix ;) > If dkms-nvidia isn't building, then a blacklist likely won't help! :) > > Col > >
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
'Twas brillig, and Barry Jackson at 06/03/12 12:26 did gyre and gimble: > You could try blacklisting the nouveau module - but that won't fix the > underlying issue - it may however get you working as a temporary fix ;) If dkms-nvidia isn't building, then a blacklist likely won't help! :) Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
On 06/03/12 09:45, Robert Fox wrote: This was fixed once, but since the latest kernel updates (3.3.0) - the problem has returned: Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. checking in dmesg - I see that the nouveau driver grabs the card before the nvidia driver can - but trying to remove the nouveau driver wants to remove over 800 packages! How can I get the nvidia proprietary driver back?? Thx, R.Fox You could try blacklisting the nouveau module - but that won't fix the underlying issue - it may however get you working as a temporary fix ;) Barry
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
yes and last night after installing the new kernel 3.3.0rc, dkms fails to build dkms-nvidia for this kernel. Cheers Xavier Le 06/03/2012 10:45, Robert Fox a écrit : > This was fixed once, but since the latest kernel updates (3.3.0) - the > problem has returned: > > > Since last Cauldron kernel update, I have two nvidia based system which > now fallback to nouveau when starting X - stating nvidia cannot be > loaded. > > checking in dmesg - I see that the nouveau driver grabs the card before > the nvidia driver can - but trying to remove the nouveau driver wants to > remove over 800 packages! > > How can I get the nvidia proprietary driver back?? > > Thx, > R.Fox > > >
[Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
This was fixed once, but since the latest kernel updates (3.3.0) - the problem has returned: Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. checking in dmesg - I see that the nouveau driver grabs the card before the nvidia driver can - but trying to remove the nouveau driver wants to remove over 800 packages! How can I get the nvidia proprietary driver back?? Thx, R.Fox
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/3 Wolfgang Bornath : > 2012/3/3 Barry Jackson : >> On 02/03/12 16:53, Wolfgang Bornath wrote: >>> >>> 2012/3/2 Wolfgang Bornath: whould be fixed with coming updates. >>> >>> >>> should be fixed >>> Sorry. >>> >> Seems this was not the problem for you, but my FX series card has had no >> nvidia available since x11 was updated before Christmas. >> I think I need a new graphic card :( > > Well, I don't know, but after last update tonight (mirror sync status > 23:01 Paris time) the complete system which was working fine is now > hosed anyway. > > 1. Nouveau driver still there (although I tried with XFdrake to get > the nvidia re-installed), but that did not make my system unusable > before > 2. wifi connection totally lost (not possible to get a connection, > whichever way I tried) > 3. After system start the system now displays a message that it can > not start Gnome 3 because my graphic system is possibly not able to > run in normal Gnome 3, so it starts in a somehow "compatibility mode". > /etc/X11/xorg.conf shows that the nouveau driver is working, which > never had problems with Gnome 3. > 4. I switched to tty2, and was presented with my keyboard now writing > in black! Trying to write 'asdf' does not show any character but > hitting enter returns 'asdf: command not found" > > Points 2, 3, 4 occurred at reboot after the update. > I'll call it a day... After todays updates the issues are resolved: 1. After reconfiguring X and reboot the proprietary driver was accepted and Gnome 3 started without problems 2. After removing all net connections and recreating wlan0 (in MCC without enabling networkmanager) wifi is working again 3. Input on ttys is back to white on black -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/3 Barry Jackson : > On 02/03/12 16:53, Wolfgang Bornath wrote: >> >> 2012/3/2 Wolfgang Bornath: >>> >>> whould be fixed with coming updates. >> >> >> should be fixed >> Sorry. >> > Seems this was not the problem for you, but my FX series card has had no > nvidia available since x11 was updated before Christmas. > I think I need a new graphic card :( Well, I don't know, but after last update tonight (mirror sync status 23:01 Paris time) the complete system which was working fine is now hosed anyway. 1. Nouveau driver still there (although I tried with XFdrake to get the nvidia re-installed), but that did not make my system unusable before 2. wifi connection totally lost (not possible to get a connection, whichever way I tried) 3. After system start the system now displays a message that it can not start Gnome 3 because my graphic system is possibly not able to run in normal Gnome 3, so it starts in a somehow "compatibility mode". /etc/X11/xorg.conf shows that the nouveau driver is working, which never had problems with Gnome 3. 4. I switched to tty2, and was presented with my keyboard now writing in black! Trying to write 'asdf' does not show any character but hitting enter returns 'asdf: command not found" Points 2, 3, 4 occurred at reboot after the update. I'll call it a day... -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
On 02/03/12 16:53, Wolfgang Bornath wrote: 2012/3/2 Wolfgang Bornath: whould be fixed with coming updates. should be fixed Sorry. Seems this was not the problem for you, but my FX series card has had no nvidia available since x11 was updated before Christmas. I think I need a new graphic card :(
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/2 Thomas Backlund : > 02.03.2012 21:06, Wolfgang Bornath skrev: >> 2012/3/2 Anssi Hannula : >>> 02.03.2012 10:38, Robert Fox kirjoitti: Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. >>> >>> Fixed in harddrake-13.89.1. The previous versions do not handle XZ >>> compressed proprietary driver modules properly. >> >> Which means, as soon as we get the new harddrake version in updates >> the issue is (should be) gone? >> > > AFAIK you need to reconfigure your system to use the proprietary modules... Yes, that's to be expected anyway. Thx -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
02.03.2012 21:06, Wolfgang Bornath skrev: > 2012/3/2 Anssi Hannula : >> 02.03.2012 10:38, Robert Fox kirjoitti: >>> Since last Cauldron kernel update, I have two nvidia based system which >>> now fallback to nouveau when starting X - stating nvidia cannot be >>> loaded. >> >> Fixed in harddrake-13.89.1. The previous versions do not handle XZ >> compressed proprietary driver modules properly. > > Which means, as soon as we get the new harddrake version in updates > the issue is (should be) gone? > AFAIK you need to reconfigure your system to use the proprietary modules... -- Thomas
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
02.03.2012 21:06, Wolfgang Bornath kirjoitti: > 2012/3/2 Anssi Hannula : >> 02.03.2012 10:38, Robert Fox kirjoitti: >>> Since last Cauldron kernel update, I have two nvidia based system which >>> now fallback to nouveau when starting X - stating nvidia cannot be >>> loaded. >> >> Fixed in harddrake-13.89.1. The previous versions do not handle XZ >> compressed proprietary driver modules properly. > > Which means, as soon as we get the new harddrake version in updates > the issue is (should be) gone? Yes, except that you have to switch back to the proprietary driver yourself with XFdrake. -- Anssi Hannula
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/2 Anssi Hannula : > 02.03.2012 10:38, Robert Fox kirjoitti: >> Since last Cauldron kernel update, I have two nvidia based system which >> now fallback to nouveau when starting X - stating nvidia cannot be >> loaded. > > Fixed in harddrake-13.89.1. The previous versions do not handle XZ > compressed proprietary driver modules properly. Which means, as soon as we get the new harddrake version in updates the issue is (should be) gone? -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
02.03.2012 10:38, Robert Fox kirjoitti: > Since last Cauldron kernel update, I have two nvidia based system which > now fallback to nouveau when starting X - stating nvidia cannot be > loaded. Fixed in harddrake-13.89.1. The previous versions do not handle XZ compressed proprietary driver modules properly. -- Anssi Hannula
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/2 Wolfgang Bornath : > whould be fixed with coming updates. should be fixed Sorry. -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/2 Barry Jackson : > On 02/03/12 16:31, Bertaux Xavier wrote: >> >> and I think both nvidia and fglrx tickets are the same problem >> >> Xavier >> >> Le 02/03/2012 17:27, Bertaux Xavier a écrit : >>> >>> Le 02/03/2012 16:44, Wolfgang Bornath a écrit : 2012/3/2 EatDirt: > > On 02/03/12 09:38, Robert Fox wrote: >> >> Since last Cauldron kernel update, I have two nvidia based system >> which >> now fallback to nouveau when starting X - stating nvidia cannot be >> loaded. >> > +1 > Recurrent pb for me as well. Did you try to add > > nokmsboot > > in the boot arguments? Same pb here, xorg.conf was changed (display driver changed to "nouveau"). Re-changed the display driver to "nvidia" and added nokmsboot to the boot args, next boot same pb again. >>> >>> +1 >>> >>> Xavier >> >> > IIANM this is now the default behavior when the x11-server version is > updated to a version not supported by the current proprietary nvidia driver. > It avoids a boot failure which would otherwise be the scenario. Reasonable behavior, so to avoid this the x11-server should always match the current proprietary driver. In other words: either one whould be fixed with coming updates. -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
On 02/03/12 16:31, Bertaux Xavier wrote: and I think both nvidia and fglrx tickets are the same problem Xavier Le 02/03/2012 17:27, Bertaux Xavier a écrit : Le 02/03/2012 16:44, Wolfgang Bornath a écrit : 2012/3/2 EatDirt: On 02/03/12 09:38, Robert Fox wrote: Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. +1 Recurrent pb for me as well. Did you try to add nokmsboot in the boot arguments? Same pb here, xorg.conf was changed (display driver changed to "nouveau"). Re-changed the display driver to "nvidia" and added nokmsboot to the boot args, next boot same pb again. +1 Xavier IIANM this is now the default behavior when the x11-server version is updated to a version not supported by the current proprietary nvidia driver. It avoids a boot failure which would otherwise be the scenario. Barry
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
and I think both nvidia and fglrx tickets are the same problem Xavier Le 02/03/2012 17:27, Bertaux Xavier a écrit : > Le 02/03/2012 16:44, Wolfgang Bornath a écrit : >> 2012/3/2 EatDirt : >>> On 02/03/12 09:38, Robert Fox wrote: Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. >>> +1 >>> Recurrent pb for me as well. Did you try to add >>> >>> nokmsboot >>> >>> in the boot arguments? >> Same pb here, xorg.conf was changed (display driver changed to "nouveau"). >> Re-changed the display driver to "nvidia" and added nokmsboot to the >> boot args, next boot same pb again. > +1 > > Xavier
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
Le 02/03/2012 16:44, Wolfgang Bornath a écrit : > 2012/3/2 EatDirt : >> On 02/03/12 09:38, Robert Fox wrote: >>> Since last Cauldron kernel update, I have two nvidia based system which >>> now fallback to nouveau when starting X - stating nvidia cannot be >>> loaded. >>> >> +1 >> Recurrent pb for me as well. Did you try to add >> >> nokmsboot >> >> in the boot arguments? > Same pb here, xorg.conf was changed (display driver changed to "nouveau"). > Re-changed the display driver to "nvidia" and added nokmsboot to the > boot args, next boot same pb again. +1 Xavier >
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
02.03.2012 18:18, Robert Fox skrev: > On Fri, 2012-03-02 at 16:44 +0100, Wolfgang Bornath wrote: >> 2012/3/2 EatDirt : >>> On 02/03/12 09:38, Robert Fox wrote: Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. >>> >>> +1 >>> Recurrent pb for me as well. Did you try to add >>> >>> nokmsboot >>> >>> in the boot arguments? >> >> Same pb here, xorg.conf was changed (display driver changed to "nouveau"). >> Re-changed the display driver to "nvidia" and added nokmsboot to the >> boot args, next boot same pb again. >> > > I will file a bug report . . . > No need, there is already a report... And I'm looking into it... -- Thomas
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
On Fri, 2012-03-02 at 16:44 +0100, Wolfgang Bornath wrote: > 2012/3/2 EatDirt : > > On 02/03/12 09:38, Robert Fox wrote: > >> > >> Since last Cauldron kernel update, I have two nvidia based system which > >> now fallback to nouveau when starting X - stating nvidia cannot be > >> loaded. > >> > > > > +1 > > Recurrent pb for me as well. Did you try to add > > > > nokmsboot > > > > in the boot arguments? > > Same pb here, xorg.conf was changed (display driver changed to "nouveau"). > Re-changed the display driver to "nvidia" and added nokmsboot to the > boot args, next boot same pb again. > I will file a bug report . . .
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
2012/3/2 EatDirt : > On 02/03/12 09:38, Robert Fox wrote: >> >> Since last Cauldron kernel update, I have two nvidia based system which >> now fallback to nouveau when starting X - stating nvidia cannot be >> loaded. >> > > +1 > Recurrent pb for me as well. Did you try to add > > nokmsboot > > in the boot arguments? Same pb here, xorg.conf was changed (display driver changed to "nouveau"). Re-changed the display driver to "nvidia" and added nokmsboot to the boot args, next boot same pb again. -- wobo
Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
On 02/03/12 09:38, Robert Fox wrote: Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. +1 Recurrent pb for me as well. Did you try to add nokmsboot in the boot arguments? chris.
[Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates
Since last Cauldron kernel update, I have two nvidia based system which now fallback to nouveau when starting X - stating nvidia cannot be loaded. checking in dmesg - I see that the nouveau driver grabs the card before the nvidia driver can - but trying to remove the nouveau driver wants to remove over 800 packages! How can I get the nvidia proprietary driver back?? [ 53.253035] [drm] nouveau :04:00.0: Attempting to load BIOS image from PRAMIN [ 53.298983] [drm] nouveau :04:00.0: ... appears to be valid [ 53.298987] [drm] nouveau :04:00.0: BIT BIOS found [ 53.298990] [drm] nouveau :04:00.0: Bios version 62.94.20.00 [ 53.298993] [drm] nouveau :04:00.0: TMDS table version 2.0 [ 53.298996] [drm] nouveau :04:00.0: Found Display Configuration Block version 4.0 [ 53.298998] [drm] nouveau :04:00.0: Raw DCB entry 0: 02000300 0028 [ 53.299013] [drm] nouveau :04:00.0: Raw DCB entry 1: 01000302 00020030 [ 53.299015] [drm] nouveau :04:00.0: Raw DCB entry 2: 04011310 0028 [ 53.299019] [drm] nouveau :04:00.0: Raw DCB entry 3: 02022332 00020010 [ 53.299024] [drm] nouveau :04:00.0: Raw DCB entry 4: 000e [ 53.299029] [drm] nouveau :04:00.0: DCB connector table: VHER 0x40 5 16 4 [ 53.299039] [drm] nouveau :04:00.0: 0: 0x1030: type 0x30 idx 0 tag 0x07 [ 53.299052] [drm] nouveau :04:00.0: 1: 0x0100: type 0x00 idx 1 tag 0xff [ 53.299062] [drm] nouveau :04:00.0: 2: 0x2261: type 0x61 idx 2 tag 0x08 [ 53.299069] [drm] nouveau :04:00.0: Parsing VBIOS init table 0 at offset 0xD21E [ 53.324438] [drm] nouveau :04:00.0: Parsing VBIOS init table 1 at offset 0xD633 [ 53.327051] [drm] nouveau :04:00.0: Parsing VBIOS init table 2 at offset 0xE624 [ 53.327058] [drm] nouveau :04:00.0: Parsing VBIOS init table 3 at offset 0xE76D [ 53.328136] [drm] nouveau :04:00.0: Parsing VBIOS init table 4 at offset 0xE9A9 [ 53.328140] [drm] nouveau :04:00.0: Parsing VBIOS init table at offset 0xEA0E [ 53.348146] [drm] nouveau :04:00.0: 0xEA0E: Condition still not met after 20ms, skipping following opcodes [ 53.366853] [drm] nouveau :04:00.0: 1 available performance level(s) [ 53.366858] [drm] nouveau :04:00.0: 3: core 500MHz shader 1250MHz memory 500MHz voltage 1100mV fanspeed 100% [ 53.366873] [drm] nouveau :04:00.0: c: core 500MHz shader 1250MHz memory 499MHz voltage 1100mV [ 53.368881] [TTM] Zone kernel: Available graphics memory: 1543414 kiB. [ 53.368884] [TTM] Initializing pool allocator. [ 53.368894] [drm] nouveau :04:00.0: Detected 768MiB VRAM [ 53.372117] [drm] nouveau :04:00.0: 512 MiB GART (aperture) [ 53.397649] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 53.397652] [drm] No driver support for vblank timestamp query. [ 53.656361] [drm] nouveau :04:00.0: allocated 1680x1050 fb: 0x31, bo 8800b1df9400 [ 53.656475] fbcon: nouveaufb (fb0) is primary device [ 53.656688] Console: switching to colour frame buffer device 210x65 [ 53.656694] fb0: nouveaufb frame buffer device [ 53.656696] drm: registered panic notifier [ 53.656703] [drm] Initialized nouveau 0.0.16 20090420 for :04:00.0 on minor 0 [ 56.018019] eth0: no IPv6 routers present [ 112.967128] 2:2:1: cannot get freq at ep 0x4 [ 113.975124] 2:3:1: cannot get freq at ep 0x83 [ 115.031128] 2:3:1: cannot get freq at ep 0x83 [ 116.041124] 2:2:1: cannot get freq at ep 0x4 [ 117.054141] 2:3:1: cannot get freq at ep 0x83 [ 123.675318] process `skype' is using obsolete setsockopt SO_BSDCOMPAT [ 243.059920] NVRM: The NVIDIA probe routine was not called for 1 device(s). [ 243.059923] NVRM: This can occur when a driver such as nouveau, rivafb, [ 243.059924] NVRM: nvidiafb, or rivatv was loaded and obtained ownership of [ 243.059925] NVRM: the NVIDIA device(s). [ 243.059927] NVRM: Try unloading the conflicting kernel module (and/or [ 243.059928] NVRM: reconfigure your kernel without the conflicting [ 243.059929] NVRM: driver(s)), then try loading the NVIDIA kernel module [ 243.059929] NVRM: again. [ 243.059931] NVRM: No NVIDIA graphics adapter probed! [ 566.999504] NVRM: The NVIDIA probe routine was not called for 1 device(s). [ 566.999507] NVRM: This can occur when a driver such as nouveau, rivafb, [ 566.999508] NVRM: nvidiafb, or rivatv was loaded and obtained ownership of [ 566.999509] NVRM: the NVIDIA device(s). [ 566.999511] NVRM: Try unloading the conflicting kernel module (and/or [ 566.999512] NVRM: reconfigure your kernel without the conflicting [ 566.999512] NVRM: driver(s)), then try loading the NVIDIA kernel module [ 566.999513] NVRM: again. [ 566.999515] NVRM: No NVIDIA graphics adapter probed! Thx, R.Fox
