From: Pierre B <pierr...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: failure to boot after install
Date: Thu, 11 May 2017 05:54:49 -0700 (PDT) [thread overview]
Message-ID: <35d7da1f-9423-4a09-8e69-73e14651d0cb@googlegroups.com> (raw)
In-Reply-To: <12f56cea-a698-488c-8a85-9330d8f6c2c2@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 2622 bytes --]
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:
>
> <https://lh3.googleusercontent.com/-s6nlWys386o/WQrnVQndiVI/AAAAAAAAC18/trGL4VhsLYQvompN7UDEgXgorbc8d8fhQCLcB/s1600/void%2Binstall%2Blog.jpg>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 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:
>
>
> <https://lh3.googleusercontent.com/-T3PNnUgO3fk/WQrn6NszN4I/AAAAAAAAC2I/DIxE5EPQPg4nxtb4P42HTTFlXk0XDUOiQCLcB/s1600/bios%2Bfreeze.jpg>
>
> 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:
>
>
>
> <https://lh3.googleusercontent.com/-YiLKCEHGyGE/WQrowWzE2RI/AAAAAAAAC2Q/4kli-ELlYrsR8r_jocwvW_sqiECDaG5pgCLcB/s1600/grub%2Binstall%2Blog.jpg>Just
> a bit curious about this part
> <https://lh3.googleusercontent.com/-YiLKCEHGyGE/WQrowWzE2RI/AAAAAAAAC2Q/4kli-ELlYrsR8r_jocwvW_sqiECDaG5pgCLcB/s1600/grub%2Binstall%2Blog.jpg> --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:
>
>
> <https://lh3.googleusercontent.com/-N2dPfe5gMb4/WQrp5cEhR0I/AAAAAAAAC2c/IV35RNBY24ocfRrnfHn1XZUzB--hePhlgCLcB/s1600/non%2Bworking%2BMBR.jpg>
>
> 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.
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 7505 bytes --]
next prev parent reply other threads:[~2017-05-11 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 8:52 Pierre B
2017-05-11 12:54 ` Pierre B [this message]
2017-07-22 11:56 ` Pierre B
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35d7da1f-9423-4a09-8e69-73e14651d0cb@googlegroups.com \
--to="pierr..."@gmail.com \
--cc="void..."@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).