Open bekker opened 6 years ago
ARM doesn't work yet as I do not currently have an ARM-based device with which to test.
Thanks.
To clarify, ARM is a large share of the chromebook market, and is intended to be supported. Not certain when I will be able to do that.
I'm afraid I'm crouton newb and archlinux newb, but I maybe try to look into it. Any tips where to start? I heard about arm specific hacks or something, but I have no idea. Maybe porting those xorg hwe video drivers for debian to arch?
In the mean time, assuming you haven't already done so, you may try alternatively installing xiwi and xorg into your arm release and seeing if either of those potentially resolve your x11 snag:
sudo sh -e installer/main.sh -p /var/sd -r arch -t xiwi -u
or
sudo sh -e installer/main.sh -p /var/sd -r arch -t xorg -u
xorg
didn't work, same result.
xiwi
has same issue as https://github.com/dnschneid/crouton/issues/1940.
It fails to connect to the extension.
This doesn't appear to be arm specific. I have a pixelbook wich is x86-64 and when I run startlxde I get the same "cannot open /dev/tty0" error:
Entering /mnt/stateful_partition/crouton/chroots/arch...
chown: invalid user: ‘messagebus:messagebus’
dbus[25919]: Unknown username "colord" in message bus configuration file
dbus[25919]: Unknown username "rtkit" in message bus configuration file
dbus[25919]: Unknown username "polkitd" in message bus configuration file
dbus[25919]: Unknown username "polkitd" in message bus configuration file
dbus[25919]: Unknown username "avahi" in message bus configuration file
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.71-1-lts x86_64
Current Operating System: Linux localhost 4.4.86-11976-gc4c6234ae4f3 #1 SMP PREEMPT Mon Dec 18 20:29:05 PST 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 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 4710400 verity payload=PARTUUID=a8667891-8209-8648-9d5e-63dc9b8d0cb3/PARTNROFF=1 hashtree=PARTUUID=a8667891-8209-8648-9d5e-63dc9b8d0cb3/PARTNROFF=1 hashstart=4710400 alg=sha1 root_hexdigest=f63107d7629b111ad968b23f1eacca7ee9f2ac86 salt=5a80634bd336e313197cdb37df15e09116debcdb703c5bb7676f863c9e4fa72c" noinitrd vt.global_cursor_default=0 kern_guid=a8667891-8209-8648-9d5e-63dc9b8d0cb3 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 25 December 2017 02:02:38PM
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Thu Jan 4 16:21:34 2018
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/arch...```
This appears to be a separate (new) error that is a result of an upstream (arch) problem.
On my Pixelbook, I was having this problem as well. Just now I came to this issue page to see if anything had changed. On a whim, I did a "sudo sh -e installer/main.sh -t xiwi -u" on my Arch chroot and suddenly... it's working... Yay?
I can enter the chroot, do a "xiwi -T
Oh my god youre right, it works! yihooo. Had to update my chromeOS first though, old chromeOS was no bueno. Havent tried xorg, only xiwi, first time using xiwi might stay with it, any way of using both?
This is correct. I have yet to determine how to address startxfce4 (for example) not working, but launching programs within the chroot using the xiwi -T method has always worked.
Please describe your issue:
I installed this repo on seperate sd card using command below.
enter-chroot
into it works fine, butstartxfce4
doesn't work.Obviously no
/dev/tty0
.Does this repo work on armhf devices currently? Or something I've done wrong?
FYI Ubuntu with dnschneid/crouton works perfectly.