Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11066] New: x11r7 X11 S40xorg leads to a black screen on QEMU x86 but startx works
Date: Tue, 05 Jun 2018 21:42:56 +0000	[thread overview]
Message-ID: <bug-11066-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11066

            Bug ID: 11066
           Summary: x11r7 X11 S40xorg leads to a black screen on QEMU x86
                    but startx works
           Product: buildroot
           Version: 2018.02.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: ciro.santilli at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I was on 2017.08 happily doing starx manually, when I rebased to
77c47c3ff8601da2fdc8f82f84be117dd636b02c (post 2018.05) and noticed that X11
was starting automatically due to S40xorg
d83eacaaa8f17b5d573d540ca6338390fcfa0ba1

Unfortunately, the screen is then black.

However, if I manually remove S40xorg and go back to my startx method, it still
works (except the mouse doesn't move, as before, do you have a clue about that
as well?)

My precise setup is:
https://github.com/cirosantilli/buildroot/tree/77c47c3ff8601da2fdc8f82f84be117dd636b02c
which does for build:

#!/usr/bin/env bash
unset LD_LIBRARY_PATH
defconfig="${1:-qemu_x86_64_defconfig}"
outdir="output/${defconfig}"
make O="$outdir" "$defconfig"
printf "
BR2_CCACHE=y
BR2_PACKAGE_HOST_QEMU=y
BR2_PACKAGE_HOST_QEMU_LINUX_USER_MODE=n
BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE=y
BR2_PACKAGE_HOST_QEMU_VDE2=y

BR2_PACKAGE_XAPP_TWM=y
BR2_PACKAGE_XAPP_XCALC=y
BR2_PACKAGE_XAPP_XCLOCK=y
BR2_PACKAGE_XAPP_XEYES=y
BR2_PACKAGE_XAPP_XINIT=y
BR2_PACKAGE_XDRIVER_XF86_INPUT_KEYBOARD=y
BR2_PACKAGE_XDRIVER_XF86_INPUT_MOUSE=y
BR2_PACKAGE_XDRIVER_XF86_VIDEO_CIRRUS=y
BR2_PACKAGE_XDRIVER_XF86_VIDEO_FBDEV=y
BR2_PACKAGE_XDRIVER_XF86_VIDEO_VESA=y
BR2_PACKAGE_XORG7=y
BR2_PACKAGE_XSERVER_XORG_SERVER=y
BR2_PACKAGE_XTERM=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
${2:-}
" >> "${outdir}/.config"
make O="$outdir" olddefconfig
time make O="$outdir" BR2_JLEVEL="$(nproc)" HOST_QEMU_OPTS='--enable-sdl
--with-sdlabi=2.0'

run:

#!/usr/bin/env bash
outdir="${1:-output/qemu_x86_64_defconfig}"
"${outdir}/host/usr/bin/qemu-system-x86_64" \
  -M pc \
  -append 'root=/dev/vda console=ttyS0' \
  -drive file="${outdir}/images/rootfs.ext2,if=virtio,format=raw" \
  -enable-kvm \
  -kernel "${outdir}/images/bzImage" \
  -m 512 \
  -net nic,model=virtio \
  -net user,hostfwd=tcp::2222-:22 \
  -serial mon:stdio \
;

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2018-06-05 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 21:42 bugzilla at busybox.net [this message]
2018-06-05 21:44 ` [Buildroot] [Bug 11066] x11r7 X11 S40xorg leads to a black screen on QEMU x86 but startx works bugzilla at busybox.net
2018-06-05 21:45 ` bugzilla at busybox.net
2018-06-06 14:49 ` bugzilla at busybox.net
2018-08-29 13:17 ` bugzilla at busybox.net
2019-01-06 21:25 ` bugzilla at busybox.net

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=bug-11066-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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