Void Linux discussion
 help / color / mirror / Atom feed
From: <0x40@keemail.me>
To: "linux.rog" <linux.rog@gmail.com>
Cc: voidlinux <voidlinux@googlegroups.com>
Subject: Re: Failure during boot / installer / BUG
Date: Tue, 14 May 2019 10:46:58 +0200 (CEST)	[thread overview]
Message-ID: <LepWUbr--3-1@keemail.me> (raw)
In-Reply-To: <65a4e195-58d3-4ea5-9806-680cad9f1ed6@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]

May 14, 2019, 4:35 AM by linux.rog@gmail.com:

> Trying to install Voidlinux lxqt using void-live-i686-20181111-lxqt.iso. I successfully created installer on USB drive.  Boot progresses through
> - decompressing linux
> - booting the kernel
> then hundreds of lines flash by at high speed, saying, e.g.,
>
> [    57.433332] ehci-pci 0000:00:1d.0: dma_direct_map_sg: overlow 0x0000000215bea000+4096 of device mask fffffffff
>
> with the first string of numbers increasing rapidly. (See image attached.)
>
> If switch PCs, the installer runs successfully and is bootable. Going back to original PC and running the newly installed voidlinux, the same failure to boot occurs.
>
> These failure occurs on a PC with an Intel motherboard and I-3 processor.
>
> /linux.rog
>
>
>
> --
>  You received this message because you are subscribed to the Google Groups "voidlinux" group.
>  To unsubscribe from this group and stop receiving emails from it, send an email to > voidlinux+unsubscribe@googlegroups.com <mailto:voidlinux+unsubscribe@googlegroups.com>> .
>  To post to this group, send email to > voidlinux@googlegroups.com <mailto:voidlinux@googlegroups.com>> .
>  To view this discussion on the web visit > https://groups.google.com/d/msgid/voidlinux/65a4e195-58d3-4ea5-9806-680cad9f1ed6%40googlegroups.com <https://groups.google.com/d/msgid/voidlinux/65a4e195-58d3-4ea5-9806-680cad9f1ed6%40googlegroups.com?utm_medium=email&utm_source=footer>> .
>  For more options, visit > https://groups.google.com/d/optout <https://groups.google.com/d/optout>> .
>
Try plugging out any devices that aren't needed for installation. Try another install medium (usb stick, sd card, android phone with the drivedroid app) and other usb ports. If that doesn't work, you can build a new iso with a less ancient kernel using the void-mklive tool. https://github.com/void-linux/void-mklive <https://github.com/void-linux/void-mklive>

-- 
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/LepWUbr--3-1%40keemail.me.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 3743 bytes --]

  reply	other threads:[~2019-05-14  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  2:35 linux.rog
2019-05-14  8:46 ` 0x40 [this message]
2019-05-15  1:25 ` linux.rog

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=LepWUbr--3-1@keemail.me \
    --to=0x40@keemail.me \
    --cc=linux.rog@gmail.com \
    --cc=voidlinux@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).