Can't enter desktop #9
Comments
|
Thank you for opening this issue and trying the project. Can you post the output of |
|
Thank for reply. I following your step:
|
|
After installing 8.1 Linux kernel can not mount the disk. Requires the config_quota. Adding this config does not seem to solve the problem. |
|
@kendling @vartom @kendling Are you using @vartom I'll take a look into it! Thanks for the report! |
|
So added it to the config |
|
@denysvitali Still not working. I was try to redownload FS and extract by new Show this screen after noise screen. |
|
So not only I have such a problem with the launch. |
|
The thing you guys can try (just to test if the kernel is working) is to use the NVIDIA's rootfs (Ubuntu) I have to find a better way to create a customized rootfs of Arch Linux w/ lightdm and some other customizations: after my exams (after February 8) I'll dedicate all of my free time to this project. I'm using this as a base right now to build my rootfs. The previously shared rootfs were a simple My goal is to set up a CI (probably on Travis or Jenkins) to build the rootfs w/ the Pixel C customizations (lightbar that turns light blue after boot, lightdm + nouveau drivers, onboard, wifi scripts and so on). |
|
I tried using NVIDIA's rootfs (Ubuntu) 24.x and 28.1. I tried to use Nvidia with a driver package for tegra and without this package. The result is the same. Instead of the terminal which I see using a 3.18 kernel, I look the same strips. |
|
As it turned out, these problems are interrelated. If in august you like get a picture and # 1 for you a bug, then for me this is a primary problem since I do not get a normal picture at all. |
|
Can you guys please try with this boot image (also available here) and this rootfs? Follow this procedure, the rootfs must be placed in the SHA256 sumsRootfs: bc5299089602f61e0c2c0046dbdf563905c6e5451b1c23a3a7293ffd8ffe52e5 |
|
The system from 160218 does not load onto the desktop. |
|
@vartom that rootfs is marked as a pre-release because it has some bad permissions. In the next build (2018-02-18) everything should work normally. I'm building it right now w/ Travis CI: you can check its status here |
|
@vartom About the |
|
@denysvitali Android 8.1. sdcardfs not necessary. Most likely you have data partition encryption. |
|
Probably. Even though I can mount the |
|
@denysvitali This is not an indicator. check the section is not dm-0? |
|
When Android is booted, I can't access the |
|
block/dm-2 this is encryption. |
|
untagged-828d52 booted to the desktop, no DRI2 capable, softwares rendering ((( |
|
I'll provide a (signed) boot image in a few minutes |
|
You can try this image. |
|
Swears at the Quota. I started the kernel with my ramdisk. I do not want to delete and reflash the system. |
|
You can build my initramfs and set the "in_data" value to true |
|
@denysvitali Your screen photos look different than the ones I run from your image(untagged-828d52). I do not have the WiFi settings. What's the Difference? Do you start the system with a usb flash drive? |
|
@vartom I manually installed |
|
Since I do not know Archlinux, it will be a problem manually installed . |
I'll provide a GNOME rootfs if you want :) |
|
I'll try it tomorrow. this is slightly different from Ubuntu to which I am still getting used to. |
|
Don't worry. As long as you have a shell (SSH) you can easily switch the session an / or the Display Manager with the commands provided above. Check out the GDM page on Arch Linux Wiki for more info |
|
@vartom Here is a freshly created rootfs that boots into GNOME and enables the NetworkManager and bluetooth daemon on boot: |
|
@denysvitali Thank you |
|
@denysvitali Could you give instructions on how to correctly write rootfs on a flash drive? I tried to unzip the archive from rootfs via tar. Unzipped just to the root, not to the folder. As a result, the system starts to boot and hangs. Later I'll try another flash drive, but I do not think this is a problem. |
|
You can install a system on flash drive with this : To summarise use the rsync command to extract your rootfs in a /system directory of the a drive. Then using fastboot your can do : fastboot boot Image.fit newinitrd_usb.tar.gz |
|
@denysvitali @vartom I like this way of booting because you don't need to modify your Pixel C at ALL to work on the project. |
|
I wouldn't recommend running the system from USB. Whilst it is the most convenient solution (there is no need to touch any of the Pixel C partitions) it seems to be pretty unstable. |
|
For system tests, starting with USB is fine. I use a little modified initrams from denysvitali. |
I extract the arch-xfce-lightdm.tar.gz to /data.
And then I run
fastboot boot boot-4.13-rc4_20170816_114501.img.unsignedorfastboot boot boot-4.13-rc4_20170809_223257.img.It can see the noise screen both.
But I can't enter the desktop after waiting 30 minutes.
The text was updated successfully, but these errors were encountered: