
Hello, I have a i7 based HP computer here that until recently was booting Linux and Windows just fine. According to the user, it stopped working after updating the graphics drivers under Windows. Anyway the symptoms are: * Grub loads fine. * Selecting any Linux kernel from grub, results in the computer freezing immediately after loading the kernel (no time to initialize the kernel), with a black screen. * Selecting memtest results in similar problems. * Same thing happens booting from rescue items in grub menu. No extra debugging information. * Keyboard unresponsive after crash. Caps-lock, num-lock, and Ctrl-Alt-Delete don't work. * Booting windows works fine. * Booting Debian live CD image on USB works fine. It has the standard Debian wheezy kernel, 3.2.0-4-amd64, which is the same as one of the options I was attempting to boot from the hard disk. * Power cycling is the only way to un-crash the system. Extra facts: * It is a Nvidia GeForce GT 640 based graphics card * The live CD does not use grub. * Debian/wheezy based system with extra kernels installed from Debian backports. * The dog barking does not make any difference what so ever. * Nvidia closed source drivers not installed (not that I see this making any difference, as the kernel doesn't appear to be started when it crashes) * This is a UEFI boot system, with secure boot turned off. Have tried installing another kernel after booting live CD, and reinstalling grub, however nothing changed. Have run memtest from live CD, no errors reported. Only thing I can think of is that the update of the graphics drivers under Windows has updated the graphics card firmware breaking boots from the version of Grub in Debian stable/wheezy. Does this even make sense? Any other ideas? Thanks -- Brian May <brian@microcomaustralia.com.au>

On 2015-01-25 11:44, Brian May wrote:
I have a i7 based HP computer here that until recently was booting Linux and Windows just fine. According to the user, it stopped working after updating the graphics drivers under Windows.
Do you have access to the PC in person? If not, I'd recommend getting access.
* Selecting any Linux kernel from grub, results in the computer freezing immediately after loading the kernel (no time to initialize the kernel), with a black screen.
Have you tried booting without the 'quiet' option on the kernel command-line? Also have you tried blacklisting the 'nouveau' driver? I forget exactly how to do this in Debian but I'm sure it's straightforward. I have a very similar-sounding HP computer (HP ENVY Phoenix 810-110a) that also came with a GeForce GT 640 which the nouveau driver is _completely_ broken in. Basically I get to the kernel message "fb: switching to nouveaufb from EFI VGA" and nothing proceeds beyond that point. (I also boot in UEFI mode.) My solution was either to use the NVIDIA proprietary driver (most distro packages for the binary driver will blacklist nouveau as a side-effect) or to use the integrated Intel graphics instead.

Hi Brian, Try adding nomodeset at the end of a Linux kernel line in grub assuming you can go into grub edit mode, and see what happens? Also does it boot into console? (Linux 1) Guessing that the Windows graphics driver has nothing to do with that, its probably just a coincidence! Daniel. On Sun, 25 Jan 2015 11:44:23 +1100 Brian May <brian@microcomaustralia.com.au> wrote:
Hello,
I have a i7 based HP computer here that until recently was booting Linux and Windows just fine. According to the user, it stopped working after updating the graphics drivers under Windows.
Anyway the symptoms are:
* Grub loads fine. * Selecting any Linux kernel from grub, results in the computer freezing immediately after loading the kernel (no time to initialize the kernel), with a black screen. * Selecting memtest results in similar problems. * Same thing happens booting from rescue items in grub menu. No extra debugging information. * Keyboard unresponsive after crash. Caps-lock, num-lock, and Ctrl-Alt-Delete don't work. * Booting windows works fine. * Booting Debian live CD image on USB works fine. It has the standard Debian wheezy kernel, 3.2.0-4-amd64, which is the same as one of the options I was attempting to boot from the hard disk. * Power cycling is the only way to un-crash the system.
Extra facts: * It is a Nvidia GeForce GT 640 based graphics card * The live CD does not use grub. * Debian/wheezy based system with extra kernels installed from Debian backports. * The dog barking does not make any difference what so ever. * Nvidia closed source drivers not installed (not that I see this making any difference, as the kernel doesn't appear to be started when it crashes) * This is a UEFI boot system, with secure boot turned off.
Have tried installing another kernel after booting live CD, and reinstalling grub, however nothing changed.
Have run memtest from live CD, no errors reported.
Only thing I can think of is that the update of the graphics drivers under Windows has updated the graphics card firmware breaking boots from the version of Grub in Debian stable/wheezy. Does this even make sense?
Any other ideas?
Thanks -- Brian May <brian@microcomaustralia.com.au>
-- dan062 <dan062@yahoo.com.au>

On 25 Jan 2015 12:14, "Dan062" <dan062@yahoo.com.au> wrote:
Try adding nomodeset at the end of a Linux kernel line in grub assuming you can go into grub edit mode, and see what happens? Also does it boot into console? (Linux 1)
No, can't get any console or any text. nomodeset didn't help, and pretty sure that there is no quiet option being used either.

Hi, On Sun, Jan 25, 2015 at 11:44 AM, Brian May <brian@microcomaustralia.com.au> wrote:
Hello,
........
Extra facts: * It is a Nvidia GeForce GT 640 based graphics card * The live CD does not use grub. * Debian/wheezy based system with extra kernels installed from Debian backports. * The dog barking does not make any difference what so ever.
... humble suggestion that you revisit that influence... Wife and I recently uncovered a hacker plot in our own house. Our seemingly faithful pugalier (codename "chunky munky") and older hairy canine (codename "Kung foo doog") were recently caught redhanded in a hacking attempt designed to plunder our family savings...thankfully our meta-data project caught them before it was too late. ....That goo eyed look you get from your dog when you rub its belly with your foot? Its not love... its evil intent. Suggest: Getting a friend to take the dog for a long walk THEN debug as before. The results may well be very different... ..and if they are... get out of the house...NOW! ;-) BW

Brian May wrote:
Hello,
I have a i7 based HP computer here that until recently was booting Linux and Windows just fine. According to the user, it stopped working after updating the graphics drivers under Windows.
Anyway the symptoms are:
* Grub loads fine. * Selecting any Linux kernel from grub, results in the computer freezing immediately after loading the kernel (no time to initialize the kernel), with a black screen. * Selecting memtest results in similar problems. * Same thing happens booting from rescue items in grub menu. No extra debugging information. * Keyboard unresponsive after crash. Caps-lock, num-lock, and Ctrl-Alt-Delete don't work. * Booting windows works fine. * Booting Debian live CD image on USB works fine. It has the standard Debian wheezy kernel, 3.2.0-4-amd64, which is the same as one of the options I was attempting to boot from the hard disk. * Power cycling is the only way to un-crash the system.
Extra facts: * It is a Nvidia GeForce GT 640 based graphics card * The live CD does not use grub. * Debian/wheezy based system with extra kernels installed from Debian backports. * The dog barking does not make any difference what so ever. * Nvidia closed source drivers not installed (not that I see this making any difference, as the kernel doesn't appear to be started when it crashes) * This is a UEFI boot system, with secure boot turned off.
Have tried installing another kernel after booting live CD, and reinstalling grub, however nothing changed.
Have run memtest from live CD, no errors reported.
Only thing I can think of is that the update of the graphics drivers under Windows has updated the graphics card firmware breaking boots from the version of Grub in Debian stable/wheezy. Does this even make sense?
Any other ideas?
Not clear to me that the above, eliminated possibility that, the Nvidia GeForce GT 640 Windows driver update; some how corrupted the installed Debian/wheezy driver ? regards Rohan McLeod
Thanks -- Brian May <brian@microcomaustralia.com.au <mailto:brian@microcomaustralia.com.au>>
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main

On 25 January 2015 at 15:10, Rohan McLeod <rhn@jeack.com.au> wrote:
Not clear to me that the above, eliminated possibility that, the Nvidia GeForce GT 640 Windows driver update; some how corrupted the installed Debian/wheezy driver ?
The grub boot menu displays fine, and I am rather sceptical that memtest could be corrupted in exactly the same way. -- Brian May <brian@microcomaustralia.com.au>

On 25 January 2015 at 11:44, Brian May <brian@microcomaustralia.com.au> wrote:
I have a i7 based HP computer here that until recently was booting Linux and Windows just fine. According to the user, it stopped working after updating the graphics drivers under Windows.
I finally got it working again. I was forgetting that you can't (re)install grub-efi unless you are booted using EFI first. As my live boot CD was legacy boot not EFI, that rendered my initial attempts to reinstall grub invalid. (sometimes it will tell you, curiously not after booting from this live CD). Anyway, I installed the USB image of rEFInd ( http://www.rodsbooks.com/refind/) onto a USB device, booted from it using EFI. It immediately found a number of boot options, including my existing grub setup. I booted from this, then selected by installed Linux image. Curiously all this worked. Once booted, I run as root: grub-install /dev/sda7 update-grub Now everything works again[1]. I am still a bit puzzled what happened, maybe the windows update did something to stuff up my grub. At least it is working now. Thanks for everyone trying to assist. Notes [1] Actually memtest still is broken, am suspecting that the images provided with Debian wheezy don't work with EFI. -- Brian May <brian@microcomaustralia.com.au>

On Mon, 26 Jan 2015 12:55:28 PM Brian May wrote:
[1] Actually memtest still is broken, am suspecting that the images provided with Debian wheezy don't work with EFI.
I don't believe memtest86+ works with EFI. http://forum.canardpc.com/threads/68001-NEW-!!-Memtest86-5.00-RC1-available-... However, the original memtest does now support EFI: http://www.memtest86.com/download.htm All the best, Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC

Brian May writes:
[computer no work]
AFAICT nobody has asked yet: So the local keyboard/video are borked. But: does it issue a DHCP request? Can you ping, SSH it? If only the local KVM stack is borked, you might be able to poke around in the running system. Also there is netconsole, but that's probably not helpful in this case.
participants (7)
-
Brent Wallis
-
Brian May
-
Chris Samuel
-
Dan062
-
Jeremy Visser
-
Rohan McLeod
-
trentbuck@gmail.com