From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 11 May 2017 05:54:49 -0700 (PDT) From: Pierre B To: voidlinux Message-Id: <35d7da1f-9423-4a09-8e69-73e14651d0cb@googlegroups.com> In-Reply-To: <12f56cea-a698-488c-8a85-9330d8f6c2c2@googlegroups.com> References: <12f56cea-a698-488c-8a85-9330d8f6c2c2@googlegroups.com> Subject: Re: failure to boot after install MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3309_680085142.1494507289893" ------=_Part_3309_680085142.1494507289893 Content-Type: multipart/alternative; boundary="----=_Part_3310_155539691.1494507289894" ------=_Part_3310_155539691.1494507289894 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Quick update: I gave Ubuntu 16.04 LTS a spin on that same box and it resulted in exactly the same situation: a non bootable usb key that freeze completely said host. I'm more and more thinking this is linked to more recent versions of Grub. The Linux that currently runs on it is a Ubuntu 14.xx derivate with an older grub version. On Thursday, May 4, 2017 at 10:52:24 AM UTC+2, Pierre B wrote: > > I have strange case of a machine where Voidlinux fails to install > correctly. > > Let me start by saying that I'm using Voidlinux on several computers/VMs > and I'm now getting used to setting it up. > Still there is this one computer where I can't figure out what's going on. > I'm installing the OS to a usb stick and the computer in question is a > Core2Quad running on a X38 motherboard. > Also note that a different flavor of Linux installs and runs fine on it. > > The install procedure itself completes without error: > > > > > > > > > > > > > > > > > > > > > > > > > What happens afterward it that the PC freezes at the bios level. After > processor detection, freeze occurs at memory count, only the letter "M" is > displayed: > > > > > Void-installer boots fine but as soon as the key with newly installed Void > is plugged in during BIOS screen it freezes. > > I tried reinstalling grub manually with verbose output and it doesn't > throw an error: > > > > Just > a bit curious about this part > --prefix > '(,msdos1)/boot/grub' > Shouldn't there be a device before the comma ? > > Digging a bit deeper, I analyzed MBR on that key after dumping it into > nonworking.mbr file: > > > > > What strikes me is that huge part full of zero from offsets 10 to 50. > Comparing to a working installation there is plenty of data in that area. > > > Images were also uploaded here: http://imgur.com/a/deBq0 > > > So I'm turning to your expertise. > > If you have any idea or hint I'm all ears. > > > > ------=_Part_3310_155539691.1494507289894 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Quick update: I gave Ubuntu 16.04 LTS a spin on that same = box and it resulted in exactly the same situation: a non bootable usb key t= hat freeze completely said host.
I'm more and more thinking this is= linked to more recent versions of Grub.=C2=A0

The Linux that currently runs on it is a Ubuntu 14.xx derivate with an old= er grub version.=C2=A0


On Thursday, May 4, 2017 at 10:52:= 24 AM UTC+2, Pierre B wrote:
I have strange case of a machine where Voidlinux fails to in= stall correctly.

Let me start by saying that I'm usi= ng Voidlinux on several computers/VMs and I'm now getting used to setti= ng it up.
Still there is this one computer where I can't figu= re out what's going on. I'm installing the OS to a usb stick and th= e computer in question is a Core2Quad running on a X38 motherboard.
Also note that a different flavor of Linux installs and runs fine on it.=

The install procedure itself completes without er= ror:




=





=





=





=




What happe= ns afterward it that the PC freezes at the bios level. After processor dete= ction, freeze occurs at memory count, only the letter "M" is disp= layed:


Void-installer boots fine but as soon as the = key with newly installed Void is plugged in during BIOS screen it freezes.<= /div>

I tried reinstalling grub manually with verbose ou= tput and it doesn't throw an error:


Just a bit curious about this part= =C2=A0--prefix '(,msdos1)/boot/grub'
Shouldn't there be a device before the comma ?

Digging a bit deeper, I analyzed MBR on that key after dum= ping it into nonworking.mbr file:

=

What strikes me is that huge part full of zero from= offsets 10 to 50. Comparing to a working installation there is plenty of d= ata in that area.


Images were also uploaded here:=C2=A0http://imgur.com/a/deBq0


So I'm turning to your = expertise.

If you have any idea or hint I'm = all ears.



------=_Part_3310_155539691.1494507289894-- ------=_Part_3309_680085142.1494507289893--