From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible
Date: Wed, 15 Jan 2020 14:41:19 +0100 [thread overview]
Message-ID: <20200115134119.GP1314@mail-itl> (raw)
In-Reply-To: <20200115100821.qcdraolkoki6e5tz@sirius.home.kraxel.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1988 bytes --]
On Wed, Jan 15, 2020 at 11:08:21AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > No clue why, also doesn't reproduce here (standard fedora 31 5.4.7
> > > kernel). I don't have an encrypted disk, so no passphrase prompt,
> > > maybe that makes a difference.
> >
> > Extra data point: it worked on 4.19.89.
> >
> > > How does /proc/iomem look after boot, specifically the 0000:00:02.0 pci
> > > bars?
> >
> > grep 0000:00:02.0 /proc/iomem
> > c0000000-c0ffffff : 0000:00:02.0
> > c1087000-c1087fff : 0000:00:02.0
>
> And "grep -A1 0000:00:02.0 /proc/iomem" ?
c0000000-c0ffffff : 0000:00:02.0
c1000000-c103ffff : 0000:00:04.0
--
c1087000-c1087fff : 0000:00:02.0
fec00000-fec00fff : Reserved
Full iomem attached.
> Also: what happens if you "rmmod bochs-drm; modprobe bochs-drm"?
Looks promising, but I didn't get my console back:
[46921.550669] bochs-drm 0000:00:02.0: remove_conflicting_pci_framebuffers: bar 0: 0xc0000000 -> 0xc0ffffff
[46921.550673] bochs-drm 0000:00:02.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1087000 -> 0xc1087fff
[46921.550675] bochs-drm 0000:00:02.0: vgaarb: deactivate vga console
[46921.553577] [drm] Found bochs VGA, ID 0xb0c5.
[46921.553579] [drm] Framebuffer size 16384 kB @ 0xc0000000, mmio @ 0xc1087000.
[46921.554733] [TTM] Zone kernel: Available graphics memory: 1997204 KiB
[46921.554735] [TTM] Initializing pool allocator
[46921.554741] [TTM] Initializing DMA pool allocator
[46921.556460] [drm] Found EDID data blob.
[46921.557129] [drm] Initialized bochs-drm 1.0.0 20130925 for 0000:00:02.0 on minor 0
[46921.562805] fbcon: bochs-drmdrmfb (fb0) is primary device
[46921.562808] fbcon: Deferring console take-over
[46921.562813] bochs-drm 0000:00:02.0: fb0: bochs-drmdrmfb frame buffer device
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.1.2: iomem.txt --]
[-- Type: text/plain, Size: 1691 bytes --]
00000000-00000fff : Reserved
00001000-0009ffff : System RAM
000a0000-000fffff : Reserved
000a0000-000bffff : PCI Bus 0000:00
000f0000-000fffff : System ROM
00100000-007fffff : System RAM
00800000-00807fff : ACPI Non-volatile Storage
00808000-0080ffff : System RAM
00810000-008fffff : ACPI Non-volatile Storage
00900000-be762fff : System RAM
01000000-01c00e30 : Kernel code
01c00e31-0263093f : Kernel data
02c93000-031fffff : Kernel bss
be763000-be774fff : ACPI Non-volatile Storage
be775000-be793fff : Reserved
be794000-be9d5fff : System RAM
be9d6000-beb1afff : Reserved
beb1b000-bfb9afff : System RAM
bfb9b000-bfbf2fff : Reserved
bfbf3000-bfbfafff : ACPI Tables
bfbfb000-bfbfefff : ACPI Non-volatile Storage
bfbff000-bff4ffff : System RAM
bff50000-bff6ffff : Reserved
bff70000-bfffffff : ACPI Non-volatile Storage
c0000000-febfffff : PCI Bus 0000:00
c0000000-c0ffffff : 0000:00:02.0
c1000000-c103ffff : 0000:00:04.0
c1040000-c105ffff : 0000:00:04.0
c1060000-c107ffff : 0000:00:04.0
c1080000-c1083fff : 0000:00:04.0
c1084000-c1084fff : 0000:00:07.0
c1085000-c1085fff : 0000:00:06.0
c1086000-c1086fff : 0000:00:05.0
c1086000-c1086fff : ehci_hcd
c1087000-c1087fff : 0000:00:02.0
fec00000-fec00fff : Reserved
fec00000-fec003ff : IOAPIC 0
fed00000-fed003ff : HPET 0
fed00000-fed003ff : PNP0103:00
fee00000-feefffff : Reserved
fee00000-fee00fff : Local APIC
100000000-1403e1fff : System RAM
1403e2000-143ffffff : RAM buffer
800000000-87fffffff : PCI Bus 0000:00
800000000-800003fff : 0000:00:06.0
800000000-800003fff : virtio-pci-modern
800004000-800007fff : 0000:00:07.0
800004000-800007fff : virtio-pci-modern
fd00000000-ffffffffff : Reserved
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2020-01-15 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 16:32 bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible Marek Marczykowski-Górecki
2020-01-13 7:19 ` Gerd Hoffmann
2020-01-15 0:33 ` Marek Marczykowski-Górecki
[not found] ` <20200115100821.qcdraolkoki6e5tz@sirius.home.kraxel.org>
2020-01-15 13:41 ` Marek Marczykowski-Górecki [this message]
2020-01-15 14:13 ` Gerd Hoffmann
2020-01-15 14:27 ` Marek Marczykowski-Górecki
2020-01-15 16:16 ` Gerd Hoffmann
2020-01-16 2:52 ` Marek Marczykowski-Górecki
2020-01-17 12:58 ` Gerd Hoffmann
2020-01-17 15:22 ` Marek Marczykowski-Górecki
2020-01-20 9:58 ` Gerd Hoffmann
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=20200115134119.GP1314@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=kraxel@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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).