Re: MSI N210 graphics card causes boot failure
Sven: On Sun, Jan 01, 2012 at 11:29:51AM +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote: ---snip--- It is essential to find out why it does not work. You might want to try my suggestion to to log in via ssh and then run dmesg after re-loading the nouveau module. Boot with drm.debug=0x04 to obtain additional information. Also, try a 3.2.0-rc7 kernel from experimental. As I haven't heard back, I presume that the dmesg with debug enabled was insufficient to diagnose the problem. I did try to load up the experimental kernel, but there were two libraries (as I recall, my notes are unavailable just now) that were dependencies, and they weren't available. I've been to kernel.org to get the suggested kernel, but haven't managed to build it yet. I'll try today and let you know. Thanks for the assistance so far. Dean -- Dean Provins, P. Geoph. dprov...@alumni.ucalgary.ca http://www.telusplanet.net/~provinsd KeyID at at pgpkeys.mit.edu:11371: 0x9643AE65 Fingerprint: 9B79 75FB 5C2B 22D0 6C8C 5A87 D579 9BE5 9643 AE65 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120105153241.GA2459@ve6wvc
Re: MSI N210 graphics card causes boot failure
On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote: That should work around the problem. If possible, use a second machine to log in via ssh and run rmmod nouveau; modprobe nouveau modeset=1 then. Apending nouveau.modeset=0 at boot time allowed the boot to proceed normally. gdm popped up a graphical screen as expected, BUT, the resolution was 800X600. As root, I then executed rmmod nouveau; modprobe nouveau modeset=1 which caused a loss of X (screen went black) and a loss of the mouse. The keyboard continued to function allowing me to halt the system. I was unable to bring up one of the 6 text screens, and had to work blindly. That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I examined the /var/log/Xorg.0.log.old (new MSI card) and compared it to the /var/log/Xorg.0.log (old 6600 card). It appears that the nouveau module may not have been used. The VESA module seems to be the module of choice and all the higher resolutions were disabled. This is expected, the nouveau X driver needs kernel modesetting to work. It seems that the nouveau modeset=1 does not function as expected. It is essential to find out why it does not work. You might want to try my suggestion to to log in via ssh and then run dmesg after re-loading the nouveau module. Boot with drm.debug=0x04 to obtain additional information. Also, try a 3.2.0-rc7 kernel from experimental. To your knowledge, are there alternative settings that one might use; or do you recommend the binary nVidia driver? The only available alternative in wheezy/sid is the vesa driver which is probably not going to suite you. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r4zjiulc@turtle.gmx.de
Re: MSI N210 graphics card causes boot failure
On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote: That should work around the problem. If possible, use a second machine to log in via ssh and run rmmod nouveau; modprobe nouveau modeset=1 then. Apending nouveau.modeset=0 at boot time allowed the boot to proceed normally. gdm popped up a graphical screen as expected, BUT, the resolution was 800X600. As root, I then executed rmmod nouveau; modprobe nouveau modeset=1 which caused a loss of X (screen went black) and a loss of the mouse. The keyboard continued to function allowing me to halt the system. I was unable to bring up one of the 6 text screens, and had to work blindly. That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I guess blacklisting nouveau module should have be done from init 1 with no running X session at all. I examined the /var/log/Xorg.0.log.old (new MSI card) and compared it to the /var/log/Xorg.0.log (old 6600 card). It appears that the nouveau module may not have been used. The VESA module seems to be the module of choice and all the higher resolutions were disabled. (...) That's why you were able to boot, because the system loaded the VESA driver :-) To your knowledge, are there alternative settings that one might use; or do you recommend the binary nVidia driver? Before ditching nuvó I would try to find out if the card/chipset (geforce 210) is supported within the open source driver. If the card is unsupported, I would try installing Debian's stock nvidia closed source driver. If neither works, your last chance is compiling the nvidia driver from their site. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2012.01.01.14.33...@gmail.com
Re: MSI N210 graphics card causes boot failure
On 2012-01-01 15:33 +0100, Camaleón wrote: On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I guess blacklisting nouveau module should have be done from init 1 with no running X session at all. Booting with init 1 does not prevent the module from being loaded. Before ditching nuvó I would try to find out if the card/chipset (geforce 210) is supported within the open source driver. It is supposed to work. Nouveau supports all NVidia cards from the ancient Riva TNT/TNT2 up to the current GeForce 400/500 models, although not all of them work equally well. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d3b3ied2@turtle.gmx.de
Re: MSI N210 graphics card causes boot failure
On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote: On 2012-01-01 15:33 +0100, Camaleón wrote: On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I guess blacklisting nouveau module should have be done from init 1 with no running X session at all. Booting with init 1 does not prevent the module from being loaded. (...) I haven't expressed myself right. I didn't want to say booting at init 1 to prevent the nuvó module from being loaded but once the system has booted (with KMS disabled) jump to init 1 and blacklist the module from there. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2012.01.01.16.46...@gmail.com
Re: MSI N210 graphics card causes boot failure
On 2012-01-01 17:46 +0100, Camaleón wrote: On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote: On 2012-01-01 15:33 +0100, Camaleón wrote: On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I guess blacklisting nouveau module should have be done from init 1 with no running X session at all. Booting with init 1 does not prevent the module from being loaded. (...) I haven't expressed myself right. I didn't want to say booting at init 1 to prevent the nuvó module from being loaded but once the system has booted (with KMS disabled) jump to init 1 and blacklist the module from there. There is no reason why you would need to switch to runlevel 1 for that. Besides, changing the bootloader configuration to permanently add the nomodeset kernel parameter might be better than blacklisting the module. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874nwficnu@turtle.gmx.de
Re: MSI N210 graphics card causes boot failure
On Sun, 01 Jan 2012 17:57:09 +0100, Sven Joachim wrote: On 2012-01-01 17:46 +0100, Camaleón wrote: On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote: On 2012-01-01 15:33 +0100, Camaleón wrote: On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I guess blacklisting nouveau module should have be done from init 1 with no running X session at all. Booting with init 1 does not prevent the module from being loaded. (...) I haven't expressed myself right. I didn't want to say booting at init 1 to prevent the nuvó module from being loaded but once the system has booted (with KMS disabled) jump to init 1 and blacklist the module from there. There is no reason why you would need to switch to runlevel 1 for that. Neither to avoid losing X and preventing Xorg from going nuts? :-) Besides, changing the bootloader configuration to permanently add the nomodeset kernel parameter might be better than blacklisting the module. Why do you think nvidia nor nuvó are not going to work? Because working with VESA does not look like a sane option nowadays :-( Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2012.01.01.17.11...@gmail.com
Re: MSI N210 graphics card causes boot failure
On 2012-01-01 18:11 +0100, Camaleón wrote: On Sun, 01 Jan 2012 17:57:09 +0100, Sven Joachim wrote: On 2012-01-01 17:46 +0100, Camaleón wrote: On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote: On 2012-01-01 15:33 +0100, Camaleón wrote: On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I guess blacklisting nouveau module should have be done from init 1 with no running X session at all. Booting with init 1 does not prevent the module from being loaded. (...) I haven't expressed myself right. I didn't want to say booting at init 1 to prevent the nuvó module from being loaded but once the system has booted (with KMS disabled) jump to init 1 and blacklist the module from there. There is no reason why you would need to switch to runlevel 1 for that. Neither to avoid losing X and preventing Xorg from going nuts? :-) No, since booting with nomodeset already renders the nouveau module non-functional. Besides, changing the bootloader configuration to permanently add the nomodeset kernel parameter might be better than blacklisting the module. Why do you think nvidia nor nuvó are not going to work? For nvidia, booting with nomodeset is fine, and I did not mean to imply that nouveau will not work for the OP. But *if* you want to be sure that it does not harm you, the kernel parameter is better since blacklisting a module does not prevent it from being loaded in all situations. For instance the X server, unlike udev, invokes modprobe without the -b option when a driver needs a kernel module. Because working with VESA does not look like a sane option nowadays :-( Few people will be happy with vesa, that's true. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ipkvgwp2@turtle.gmx.de
Re: MSI N210 graphics card causes boot failure
Sven: I have executed the recommended procedure. I didn't appreciate the need for the remote login until you explained the purpose - sorry for the delay. On Sun, Jan 01, 2012 at 11:29:51AM +0100, Sven Joachim wrote: On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote: That should work around the problem. If possible, use a second machine to log in via ssh and run rmmod nouveau; modprobe nouveau modeset=1 then. Apending nouveau.modeset=0 at boot time allowed the boot to proceed normally. gdm popped up a graphical screen as expected, BUT, the resolution was 800X600. As root, I then executed rmmod nouveau; modprobe nouveau modeset=1 which caused a loss of X (screen went black) and a loss of the mouse. The keyboard continued to function allowing me to halt the system. I was unable to bring up one of the 6 text screens, and had to work blindly. That's why I suggested to log in from a second computer via ssh. It's hard to do anything with a blank screen. I examined the /var/log/Xorg.0.log.old (new MSI card) and compared it to the /var/log/Xorg.0.log (old 6600 card). It appears that the nouveau module may not have been used. The VESA module seems to be the module of choice and all the higher resolutions were disabled. This is expected, the nouveau X driver needs kernel modesetting to work. It seems that the nouveau modeset=1 does not function as expected. It is essential to find out why it does not work. You might want to try my suggestion to to log in via ssh and then run dmesg after re-loading the nouveau module. Boot with drm.debug=0x04 to obtain additional information. Also, try a 3.2.0-rc7 kernel from experimental. I have performed the following to create the attached file: booted with nouveau.modeset=0 and drm.debug=0x04 logged in remotely executed rmmod nouveau; modprobe nouveau modeset=1 executed dmesg dmesg.drm.modeset_1 gzipped the latter file I noted where the rmmod etc. was executed in the file (near line 643) Attached the file to this note... I'll try the 3.2.0-rc7 kernel you mentioned after this note goes. To your knowledge, are there alternative settings that one might use; or do you recommend the binary nVidia driver? The only available alternative in wheezy/sid is the vesa driver which is probably not going to suite you. Sven Regards, Dean -- Dean Provins, P. Geoph. dprov...@alumni.ucalgary.ca http://www.telusplanet.net/~provinsd KeyID at at pgpkeys.mit.edu:11371: 0x9643AE65 Fingerprint: 9B79 75FB 5C2B 22D0 6C8C 5A87 D579 9BE5 9643 AE65 dmesg.drm.modeset_1.gz Description: Binary data
Re: MSI N210 graphics card causes boot failure
On Sat, 31 Dec 2011 07:30:30 -0700, Dean Allen Provins, P. Geoph. wrote: My nVidia GeForce 6600 GT card started to act up, so I purchased an inexpensive MSI N210 card (which uses the 210 nVidia chipset). The salesman said I'd be happier with it! Sadly, after the the initial boot sequence lines of text (in regular VGA font) appear, the screen goes blank, and the disc stops working. It appears that the fine print boot messages are lost at that time. Is it possible the card does not support alternative VGA text formats? (...) Does anyone know why this happens, or what if any incompatibilities there are between the current Debian release and this card? Any suggestions for an alternative card would also be welcome (high gaming performance is not needed). Before anything, I would try these steps: 1/ Rename any current /etc/X11/xorg.conf file (if any) and let Xorg to auto-configure the card. 2/ Boot with KMS disabled (append nouveau.modeset=0 at boot's kernel line). There is also the closed source nvidia driver which usually works quite well but the first to do is making the system boots :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.12.31.15.31...@gmail.com
Re: MSI N210 graphics card causes boot failure
On 2011-12-31 16:31 +0100, Camaleón wrote: On Sat, 31 Dec 2011 07:30:30 -0700, Dean Allen Provins, P. Geoph. wrote: My nVidia GeForce 6600 GT card started to act up, so I purchased an inexpensive MSI N210 card (which uses the 210 nVidia chipset). The salesman said I'd be happier with it! Sadly, after the the initial boot sequence lines of text (in regular VGA font) appear, the screen goes blank, and the disc stops working. It appears that the fine print boot messages are lost at that time. Is it possible the card does not support alternative VGA text formats? Hardly, I dare say. Does anyone know why this happens, or what if any incompatibilities there are between the current Debian release and this card? Any suggestions for an alternative card would also be welcome (high gaming performance is not needed). Before anything, I would try these steps: 1/ Rename any current /etc/X11/xorg.conf file (if any) and let Xorg to auto-configure the card. This will not help, since there is a problem with the kernel module. 2/ Boot with KMS disabled (append nouveau.modeset=0 at boot's kernel line). That should work around the problem. If possible, use a second machine to log in via ssh and run rmmod nouveau; modprobe nouveau modeset=1 then. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d3b4n3zc@turtle.gmx.de
Re: MSI N210 graphics card causes boot failure
Sven and Camaleón: Thankyou for the replies and suggestions. I have made some progress. See below. On Sat, Dec 31, 2011 at 04:41:11PM +0100, Sven Joachim wrote: On 2011-12-31 16:31 +0100, Camaleón wrote: On Sat, 31 Dec 2011 07:30:30 -0700, Dean Allen Provins, P. Geoph. wrote: My nVidia GeForce 6600 GT card started to act up, so I purchased an inexpensive MSI N210 card (which uses the 210 nVidia chipset). The salesman said I'd be happier with it! Sadly, after the the initial boot sequence lines of text (in regular VGA font) appear, the screen goes blank, and the disc stops working. It appears that the fine print boot messages are lost at that time. Is it possible the card does not support alternative VGA text formats? Hardly, I dare say. Does anyone know why this happens, or what if any incompatibilities there are between the current Debian release and this card? Any suggestions for an alternative card would also be welcome (high gaming performance is not needed). Before anything, I would try these steps: 1/ Rename any current /etc/X11/xorg.conf file (if any) and let Xorg to auto-configure the card. This will not help, since there is a problem with the kernel module. 2/ Boot with KMS disabled (append nouveau.modeset=0 at boot's kernel line). That should work around the problem. If possible, use a second machine to log in via ssh and run rmmod nouveau; modprobe nouveau modeset=1 then. Apending nouveau.modeset=0 at boot time allowed the boot to proceed normally. gdm popped up a graphical screen as expected, BUT, the resolution was 800X600. As root, I then executed rmmod nouveau; modprobe nouveau modeset=1 which caused a loss of X (screen went black) and a loss of the mouse. The keyboard continued to function allowing me to halt the system. I was unable to bring up one of the 6 text screens, and had to work blindly. I examined the /var/log/Xorg.0.log.old (new MSI card) and compared it to the /var/log/Xorg.0.log (old 6600 card). It appears that the nouveau module may not have been used. The VESA module seems to be the module of choice and all the higher resolutions were disabled. Sven It seems that the nouveau modeset=1 does not function as expected. To your knowledge, are there alternative settings that one might use; or do you recommend the binary nVidia driver? Thanks, Dean -- Dean Provins, P. Geoph. dprov...@alumni.ucalgary.ca http://www.telusplanet.net/~provinsd KeyID at at pgpkeys.mit.edu:11371: 0x9643AE65 Fingerprint: 9B79 75FB 5C2B 22D0 6C8C 5A87 D579 9BE5 9643 AE65 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111231204112.GA2875@ve6wvc
