Re: Weird things with Xorg on amd54
Just use module assistant to build the nvidia blob driver. Add non-free to your /etc/apt/sources.list apt-get install module-assistant m-a prepare nvidia m-a a-i nvidia apt-get install nvidia-glx nvidia-settings in 2.6.32-5-amd64 nouveau will load during kernel boot. so after you build and install the nvidia blob driver, it will be loaded instead. however as for that boot up session, i couldnt find a way to rmmod nouveau, and modprobe nvidia and go in to X. but reboot was quick and my up time was already lost from the kernel upgrade :) Dean j...@jppozzi.dyndns.org wrote: Le mercredi 19 mai 2010 à 08:57 +0200, Hans-J. Ullrich a écrit : Am Mittwoch, 19. Mai 2010 schrieb Norval Watson: On Mon, May 17, 2010 at 05:01:35PM -0700, Norval Watson wrote: When I dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in I cannot start (or restart) gdm. The 2.6.32-3-amd64 kernel works fine. Are you running the fglrx or nvidia driver by any chance? If so you probably just have to rebuild the module against the new kernel using module-assistant. of course the nvidia driver is moving to dkms and It seems that the "nouveau" driver don't work on amd64, I have tested and revert to the "old" nv driver. Regards JPP -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bf3cedf.7030...@fragfest.com.au
Re: Weird things with Xorg on amd54
Le mercredi 19 mai 2010 à 08:57 +0200, Hans-J. Ullrich a écrit : > Am Mittwoch, 19. Mai 2010 schrieb Norval Watson: > > > On Mon, May 17, 2010 at 05:01:35PM -0700, Norval Watson wrote: > > > When I > > > dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in I > > > cannot start (or restart) gdm. > > > The 2.6.32-3-amd64 kernel works fine. > > > > Are > > > > > you running the fglrx or nvidia driver by any chance? If so > > > you > > > > probably just have to rebuild the module against the new kernel > > > > > using > > > > module-assistant. of course the nvidia driver is moving to dkms > > > > > and > > It seems that the "nouveau" driver don't work on amd64, I have tested and revert to the "old" nv driver. Regards JPP -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1274267316.8396.1.ca...@k2000.jpp.fr
Re: Weird things with Xorg on amd54
Am Mittwoch, 19. Mai 2010 schrieb Norval Watson: > > On Mon, May 17, 2010 at 05:01:35PM -0700, Norval Watson wrote: > > When I > > dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in I > > cannot start (or restart) gdm. > > The 2.6.32-3-amd64 kernel works fine. > > Are > > > you running the fglrx or nvidia driver by any chance? If so > > you > > probably just have to rebuild the module against the new kernel > > > using > > module-assistant. of course the nvidia driver is moving to dkms > > > and > > hence no longer will need manual work it seems. > > > Sorensen > > I am just running nv driver with latest kernel, have not had time to > update nvidia driver yet, thanks Lennart for the heads-up re dkms, I > will check it out! > Norv I solved it for me by blacklisting the "nouveau" kernel module. It seems, this happens with nvidia cards. If you are running nv or the 3d accelerated nvidia-glx driver, you can either delete the nouveau driver or blacklist it. Good luck! Hans -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005190857.43151.hans.ullr...@loop.de
Re: Weird things with Xorg on amd54
> On Mon, May 17, 2010 at 05:01:35PM -0700, Norval Watson wrote: > When I > dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in I > cannot > start (or restart) gdm. > The 2.6.32-3-amd64 kernel works fine. Are > you running the fglrx or nvidia driver by any chance? If so > you probably just have to rebuild the module against the new kernel > using module-assistant. of course the nvidia driver is moving to dkms > and hence no longer will need manual work it seems. -- Len > Sorensen I am just running nv driver with latest kernel, have not had time to update nvidia driver yet, thanks Lennart for the heads-up re dkms, I will check it out! Norv -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/483753.97972...@web111303.mail.gq1.yahoo.com
Re: Weird things with Xorg on amd54
On Mon, May 17, 2010 at 05:01:35PM -0700, Norval Watson wrote: > When I dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in > I cannot start (or restart) gdm. > The 2.6.32-3-amd64 kernel works fine. Are you running the fglrx or nvidia driver by any chance? If so you probably just have to rebuild the module against the new kernel using module-assistant. of course the nvidia driver is moving to dkms and hence no longer will need manual work it seems. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100518141258.gv17...@caffeine.csclub.uwaterloo.ca
Re: Weird things with Xorg on amd54
> ¿nvidia? just blacklist nouveau kernel module On Mon, May 17, 2010 > at 7:01 PM, Norval Watson < > href="mailto:norv2...@yahoo.com.au";>norv2...@yahoo.com.au> wrote: > > When I dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in > I > cannot start (or restart) gdm. > The 2.6.32-3-amd64 kernel works > fine. > HTH Yeah Jaime, you da man, that worked for me :) Now that you mention it, I remember reading somewhere the nouveau driver was still a little buggy perhaps.. Thanks, Norv -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/588893.95278...@web111308.mail.gq1.yahoo.com
Re: Weird things with Xorg on amd54
¿nvidia? just blacklist nouveau kernel module On Mon, May 17, 2010 at 7:01 PM, Norval Watson wrote: > When I dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in > I cannot start (or restart) gdm. > The 2.6.32-3-amd64 kernel works fine. > HTH > Norv > > > > > > -- > To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/344034.82171...@web111310.mail.gq1.yahoo.com > > -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Absolute certainty is a privilege of uneducated minds-and fanatics. It is, for scientific folk, an unattainable ideal. Cassius J. Keyser Jaime Ochoa Malagón Arquitecto de Soluciones Cel: +52 (55) 1021 0774 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikolvy-ccyrohqfa44rymqvw7fpuennv_rb-...@mail.gmail.com
Re: Weird things with Xorg on amd54
When I dist-upgraded recently, debian's 2.6.32-5-amd64 kernel broke x, as in I cannot start (or restart) gdm. The 2.6.32-3-amd64 kernel works fine. HTH Norv -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/344034.82171...@web111310.mail.gq1.yahoo.com
Weird things with Xorg on amd54
Hi all, since the last days there appears a strange thing on my amd64-system. When I boot up, neither kdm, xdm or gdm will start automatically. But when I start them manually by using "/etc/init.d/kdm start", everything works fine. I examined the log files, but the only strange thing I saw in Xorg.log was this: **) Option "xkb_rules" "evdev" (**) Option "xkb_model" "acer_laptop" (**) Option "xkb_layout" "de" (**) Option "xkb_options" "lv3:ralt_switch,terminate:ctrl_alt_bksp" (II) UnloadModule: "synaptics" (II) "Power Button": Close (II) UnloadModule: "evdev" (II) "Video Bus": Close (II) UnloadModule: "evdev" (II) "Power Button": Close (II) UnloadModule: "evdev" (II) "Sleep Button": Close (II) UnloadModule: "evdev" (II) "USB Mouse": Close (II) UnloadModule: "evdev" (II) "Acer Crystal Eye webcam ": Close (II) UnloadModule: "evdev" (II) "AT Translated Set 2 keyboard": Close (II) UnloadModule: "evdev" (II) "Macintosh mouse button emulation": Close (II) UnloadModule: "evdev" (II) "ACPI Virtual Keyboard Device": Close (II) UnloadModule: "evdev" (II) "Acer hotkey driver": Close (II) UnloadModule: "evdev" (WW) xf86CloseConsole: VT_WAITACTIVE failed: Interrupted system call Somehow the evdev-handler is unloading some modules. This is strange, as when starting X manually (as described above) or via "startx", everything works fine and those entries do not appear in Xorg.log. So, what is the difference by starting X manually or via initsript at boot??? This appears only on my amd64-system, my 32-bit system is fine. I would file a bugreport, but I could still not find out, which package is responsible for this. Any ideas? Best regards Hans -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005161236.52642.hans.ullr...@loop.de
