3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-27 04:01:36 +01:00
Code Issues Releases Wiki Activity

x11: mystery solved, workaround implemented: remove S40xorg

Browse Source
This commit is contained in:
Ciro Santilli
2018-06-05 22:58:06 +01:00
parent b8d8838179
commit 8911f8b505
2 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.adoc
View File

@@ -2258,8 +2258,6 @@ For example, when porting a benchmark to Buildroot, you can first use QEMU's KVM
== X11 == X11
Only tested successfully in `x86_64`. Requires <<graphic-mode>>.
Build and run: Build and run:
.... ....
@@ -2267,10 +2265,6 @@ Build and run:
./run -x ./run -x
.... ....
Before updating Buildroot to 2018.05, this is what happened:
We don't build X11 by default because it takes a considerable amount of time (about 20%), and is not expected to be used by most users: you need to pass the `-x` flag to enable it.
Inside QEMU: Inside QEMU:
.... ....
@@ -2286,10 +2280,20 @@ xeyes
image:x11.png[image] image:x11.png[image]
We don't build X11 by default because it takes a considerable amount of time (about 20%), and is not expected to be used by most users: you need to pass the `-x` flag to enable it.
More details: https://unix.stackexchange.com/questions/70931/how-to-install-x11-on-my-own-linux-buildroot-system/306116#306116 More details: https://unix.stackexchange.com/questions/70931/how-to-install-x11-on-my-own-linux-buildroot-system/306116#306116
Not sure how well that graphics stack represents real systems, but if it does it would be a good way to understand how it works. Not sure how well that graphics stack represents real systems, but if it does it would be a good way to understand how it works.
To x11 packages have an `xserver` prefix as in:
....
./build -b br2/x11 -- xserver_xorg-server-reconfigure
....
the easiest way to find them out is to just list `out/x86_64/buildroot/build/x*`.
TODO as of: c2696c978d6ca88e8b8599c92b1beeda80eb62b2 I noticed that `startx` leads to a <<bug_on>>: TODO as of: c2696c978d6ca88e8b8599c92b1beeda80eb62b2 I noticed that `startx` leads to a <<bug_on>>:
.... ....

5
rootfs_post_build_script
View File

@@ -11,9 +11,14 @@ mkdir -p \
; ;
# Maybe there is a cleaner way to get rid of those files, # Maybe there is a cleaner way to get rid of those files,
# like disabling some Buildroot packages, but no patience. # like disabling some Buildroot packages, but no patience.
#
# As of 2d5f95b1839986ca6d7b568296374a2403d2693d
# xorg must be removed or else we get a black screen:
# https://bugs.busybox.net/show_bug.cgi?id=11066
rm -rf \ rm -rf \
"${target_dir}/etc/init.d/S01logging" \ "${target_dir}/etc/init.d/S01logging" \
"${target_dir}/etc/init.d/S20urandom" \ "${target_dir}/etc/init.d/S20urandom" \
"${target_dir}/etc/init.d/S40network" \ "${target_dir}/etc/init.d/S40network" \
"${target_dir}/etc/init.d/S40xorg" \
"${target_dir}/etc/init.d/S50sshd" \ "${target_dir}/etc/init.d/S50sshd" \
; ;