crouton
crouton copied to clipboard
working with ChromeOS, X11 Xiwi fails
Discussed in https://github.com/dnschneid/crouton/discussions/4750
Originally posted by TomTravis May 26, 2022
I now a ChromeOS Dev have it running now
reading the x11 code and review the crosh shell and crostini
SUSE and maybe others will be added to the install list RPM file being converted to DEB now
back to write a vscode issue and see what happens. the webserver maybe best to run on a amd64 linux the new x11 on arm64 run the xorg just fine no xorg.config file freon is running
xiwi will not find the display new display. Xorg finds the display just fine. Xiwi has the x86 dummy device hard coded and fails 3017.444] X.Org X Server 1.21.1.99 X Protocol Version 11, Revision 0 [ 3017.445] Current Operating System: Linux localhost 5.10.106-15290-g6e9d70c8a9b4 #1 SMP PREEMPT Wed May 18 19:34:18 PDT 2022 aarch64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 5324800 verity Using a default monitor configuration. [ 3017.458] (==) Automatically adding devices [ 3017.458] (==) Automatically enabling devices [ 3017.458] (==) Automatically adding GPU devices [ 3017.458] (==) Automatically binding GPU devices [ 3017.461] (==) Max clients allowed: 256, resource mask: 0x1fffff
3044.513] (II) modeset(0): ShadowFB: preferred NO, enabled NO [ 3044.513] (II) modeset(0): Output eDP-1 has no monitor section [ 3044.513] (II) modeset(0): Output DP-1 has no monitor section [ 3044.514] (II) modeset(0): EDID for output eDP-1 [ 3044.514] (II) modeset(0): Manufacturer: CMN Model: 14e5 Serial#: 0 [ 3044.514] (II) modeset(0): Year: 2018 Week: 4 [ 3044.514] (II) modeset(0): EDID Version: 1.4 [ 3044.514] (II) modeset(0): Digital Display Input [ 3044.514] (II) modeset(0): 8 bits per channel [ 3044.514] (II) modeset(0): Digital interface is DisplayPort [ 3044.514] (II) modeset(0): Max Image Size [cm]: horiz.: 31 vert.: 17
are you running the latest official crouton release on an official build of ChromeOS?
my forked Crouton repo yes it not changed the src at all yet, the chromebookOS was just updated monday
the main branch not changed since 2016 amd64 work in both Xiwi and Xorg , arm64 Xiwi cannot find the display Xorg finds the GPU and IDs it
Xiwi uses the older X org via the backward compat , Xorg uses the current release amd64
[coco@localhost:~] $Xorg -h
Unrecognized option: -h
use: X [:
Device Dependent Usage
-modulepath paths specify the module search path
-logfile file specify a log file name
-configure probe for devices and write an xorg.conf
-showopts print available options for all installed drivers
-config file specify a configuration file, relative to the
xorg.conf search path, only root can use absolute
-configdir dir specify a configuration directory, relative to the
xorg.conf.d search path, only root can use absolute
-verbose [n] verbose startup messages
-logverbose [n] verbose log messages
-quiet minimal startup messages
-fbbpp n set bpp for the framebuffer. Default: 8
-depth n set colour depth. Default: 8
-gamma f set gamma value (0.1 < f < 10.0) Default: 1.0
-rgamma f set gamma value for red phase
-ggamma f set gamma value for green phase
-bgamma f set gamma value for blue phase
-weight nnn set RGB weighting at 16 bpp. Default: 565
-layout name specify the ServerLayout section name
-screen name specify the Screen section name
-keyboard name specify the core keyboard InputDevice name
-pointer name specify the core pointer InputDevice name
-nosilk disable Silken Mouse
-disableVidMode disable mode adjustments with xvidtune
-allowNonLocalXvidtune allow xvidtune to be run as a non-local client
-allowMouseOpenFail start server even if the mouse can't be initialized
-ignoreABI make module ABI mismatches non-fatal
-isolateDevice bus_id restrict device resets to bus_id (PCI only)
-version show the server version
-showDefaultModulePath show the server default module path
-showDefaultLibPath show the server default library path
-novtswitch don't automatically switch VT at reset & exit
-sharevts share VTs with another X server
vtXX use the specified VT number
-keeptty don't detach controlling tty (for debugging only)
-masterfd
(EE) Fatal server error: (EE) Unrecognized option: -h (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help.
Sorry, I'm having a hard time following what you're saying. Did you compile the latest Xorg yourself? If so, you might be missing some of the patches that crouton applies to the dummy device.
well so here it is, xserver is offical release from Xorg yes is was complied on both amd64 and arm64 Debian run amd64 both Xiwi and Xorg stable. the crouton -r -t use the latest X86 free driver and complies it for the install. i then use the X11 update to Xorg libs the Debootstrap script you wrote compiles to the latest Xorg Libs and Xorg run the older server for Xiwi automatic amd64 jammy fails both Xorg and Xiwi arm64 bullseye and bookworm run the same Xorg works Xiwi fails kali-rolling the debootstrap install missing dbus-x11 you have to apt install dbus-x11 for Xiwi to work Xorg fails have not tried the latest Xserver
you apply the latest update on install the crouton src need work it seems so yes the dummy driver is not used for amd64, both Xiwi and Xorg run. arm64 find the correct GPU and uses it Xiwi want the freedriver it fails arm64 xiwi
hello
Sorry, I'm having a hard time following what you're saying. Did you compile the latest Xorg yourself? If so, you might be missing some of the patches that crouton applies to the dummy device.
hello good to have your thoughts back excellent i spent some time with Git today to update the branches and update my repo I really do not think the X86free drive is used anymore it is still supports on VM boxes with no display, The Xserver code is in full Dev still, it knows chomebook is not a VM device with dummy driver, you admit this is a hack LOL