fails on ubuntu 17.10
Created by: computer777
https://pastebin.com/WjZrWJc3 -nexus 7 2012
what is your build environment or the OS you've had success on??
Activity
Created by: ollieparanoid
Welcome to postmarketOS!
pmbootstrap uses qemu user mode emulation to execute arm binaries on an x86_64 computer. That relies on the "binfmt_misc" being set up correctly.
You might have another program installed, which sets up the binfmt_misc stuff in a way that is incompatible with pmbootstrap (e.g. different path to the qemu executable). That might have happened if you have tried to run stuff from a Raspberry Pi SD card for example. It might also be, that Ubuntu 17.10 does this by default.
Could you please try
./pmbootstrap.py shutdown(and./pmbootstrap.py zapto remove the non working chroots it has created), then try it again?pmbootstrap is known to be working on Alpine Linux, Arch Linux, Gentoo, older versions of Ubuntu, ... - so it should really be possible to get it working on 17.10, too.
Note for development: we could check if the system is able to execute armhf binaries with qemu, and if it is not, offer to unload the current binfmt settings and try again.
By * postmarketOS Bot on 2017-10-27T20:50:55
Edited by Ghost User-
Created by: computer777
I have typed those two commands into the terminal and reran ./pmbootstrap.py install and it has not stopped building yet. At linux-asus-grouper...apk now. Your advice seems to have done the trick. What information could i provide you to further assist?
By * postmarketOS Bot on 2017-10-27T21:05:32
-
Created by: ollieparanoid
Glad to hear that! Besides whether the commands worked or not (which you've already answered):
- Do you have just installed Ubuntu (might be the case in a VM)?
- Are you aware of installing anything binfmt/qemu related in Ubuntu at some point?
By * postmarketOS Bot on 2017-10-27T21:09:52
Edited by Ghost User -
Created by: computer777
I figured it is not my job to close issues. Since there really isnt any issue here.... I am still having issues of my own with telnet/ssh. With FDE it takes a few tries with telnet and ssh password does not read back as correct. With FDE I get an orange screen with keyboard. I figured to try without encryption and upon boot I am left with a black screen and my password is still unrecognized.
By * postmarketOS Bot on 2017-10-27T22:28:17
-
Created by: ollieparanoid
I figured it is not my job to close issues.
Well, you can close it if you fell like it is resolved. Someone will open it again if that person think otherwise.
I am not sure I understand what you are saying, you wrote "With FDE" twice. So unlocking does not work, it does not recognize your password?
And with
--no-fdeSSH login does not work?Consider joining the chat!
By * postmarketOS Bot on 2017-10-27T22:35:49
-
Created by: computer777
I left it to build a few times with encryption and was not sure if it actually unlocked. Um, after the successful telnet session using ssh the easiest password I could think of did not work. I left it build without encryption and using ssh , the password again didn't work.
And, with encryption on - I was welcomed by an orange screen and an onscreen keyboard. With encryption off I was welcomed by a black screen. @ollieparanoid
By * postmarketOS Bot on 2017-10-27T22:57:57
Edited by Ghost User -
Created by: ollieparanoid
It sounds like, the video output is not working for some reason. Which user interface did you choose in
pmbootstrap init? For SSH, use the username you have specified inpmbootstrap init(default:user), and the password you assign to that user inpmbootstrap install. That should work, does it not?By * postmarketOS Bot on 2017-10-27T22:59:24
-
Created by: computer777
I chose xfce4. I chose user for the username. The password, for me, does not work.@ollieparanoid
By * postmarketOS Bot on 2017-10-27T23:49:12
Edited by Ghost User -
Created by: ollieparanoid
Okay, xfce4 probably failed (maybe related to #779 (closed)). You could debug this once you have ssh working, and you could use weston in the meantime which should work (if you want to try it out). The password should be working, no one reported that it does not.
- Are you connecting to the right IP?
- Try to rebuild it with a very simple user password just to make sure, then flash it again and finally test it.
By * postmarketOS Bot on 2017-10-27T23:53:44
-
Created by: computer777
Yes, sir. At least as far as I am aware. You're github lists the IP as 17(2).16.42.1. I believe, anyway, the IP is showing up as 17(2).16.42.2. For me anyway. ( Please, don't quote me.) And, yes, the password I typed in was very simple. I will, tomorrow, use Weston as the display. If you would like I will report back.
By * postmarketOS Bot on 2017-10-28T00:25:36
Edited by Ghost User -
Created by: ollieparanoid
That sounds like you have been connecting to
.2? The target device's IP is172.16.42.1, the IP of your PC connected via USB to the device is172.16.42.2. So you would need:ssh user@172.16.42.1. Yes, please report your progress. Thanks!By * postmarketOS Bot on 2017-10-28T00:33:38
-
@computer777 for hildon, try with
apk add mesa-dri-swrast, if you don't have internet on the device you can try with https://wiki.postmarketos.org/wiki/USB_InternetBy Daniele Debernardi on 2017-10-28T15:40:11
-
Created by: computer777
Finally able to see what PostMarketOS is all about with a flash of boot and system with Weston. I'm anxiously waiting for hildon or xfce4 to be usable.(by myself,anyway) Are there any updates you'd be willing to share for the grouper??
By * postmarketOS Bot on 2017-10-30T16:17:26
Edited by Ghost User -
Created by: computer777
Yes, sorry for my poor word and phrase choices. I guess, i just mean progress, like, how far along the maintainer is with pmos stability for the device. Also, idk, i think i cross posted. Sorry. The xfce4 system.img/kernel combination for whatever reason leaves me without ssh access. Could it just be a faulty usb cable?? @ollieparanoid Edit- does the git repository need to be cloned every couple days? There is a way to sync the repo without deleting anything, no?
By * postmarketOS Bot on 2017-10-30T21:45:21
Edited by Ghost User -
Created by: ollieparanoid
how far along the maintainer is with pmos stability for the device.
I think all known progress is on the device's wiki page. It hasn't seen an update since the maintainer @antonok-edm since august though, so maybe he isn't playing much with postmarketOS on that device anymore.
The xfce4 system.img/kernel combination for whatever reason leaves me without ssh access. Could it just be a faulty usb cable?
Uh, maybe. You could try another USB cable and let us know if that doesn't help it, so we can debug further. The UI shouldn't have any influence on whether SSH works or not. The device page says "Can't boot without reflashing boot (!)". I'm not sure what this means, maybe booting only works directly after flashing a kernel to the boot partition, or after flashing the system partition?
If you have some time, I recommend that you play around with various combinations of flashing images and then trying to boot it. And write down what you have done, so you know which combinations work and which ones do not.
Edit- does the git repository need to be cloned every couple days? There is a way to sync the repo without deleting anything, no?
Use
git pullto update the source :)By * postmarketOS Bot on 2017-11-01T16:58:06
-
Created by: antonok-edm
@ollieparanoid @computer777 I'm still around :)
I've been fairly busy recently, but I'd still be happy to help out with the Nexus 7 2012 if I can. I haven't personally seen any SSH problems for a long time, but it's possible something has changed since the last time I tried. I can find some time in the next few days to try a new flash and report back.
Can't boot without reflashing boot
By that, I'm referring to an issue I haven't seen anyone else having, where fully powering off the device and powering it on again would make it hang on the green Android bootloader screen. Reflashing the boot partition allows it to boot one more time. That issue should not be relevant as long as the device is not powered off.
By * postmarketOS Bot on 2017-11-01T20:27:27
-
Created by: computer777
@ollieparanoid it was just occurring for a short time somehow - beyond my comprehension. Yes, after letting pmOS build I used the two flasher commands from within /pmbootstrap. I booted up and the OS would not load - whatever the exact error message was it was something about there being no boot image.
By * postmarketOS Bot on 2017-11-04T16:13:16
-
Created by: ollieparanoid
So it is gone now? That sounds like the "can't find the boot partition" message, which would occur if you didn't flash the system image (which also contains the boot partition, see partition layout) before booting a kernel.
By * postmarketOS Bot on 2017-11-04T16:21:54
-
Created by: antonok-edm
Quick update - I am able to boot successfully and SSH into the device, but I find that it will sometimes hang a seemingly random amount of time shortly after booting -- perhaps this is what you were seeing, @computer777. You have to be quick to get a successful SSH. I haven't seen this problem before.
From the few times I've tested this so far, I have gotten it to not crash a few times (maybe 1 out of 4 or 5 tries). I'm going to see if I can get any more information than this -- so far it seems very random!
By * postmarketOS Bot on 2017-11-07T13:56:08
-
Created by: ollieparanoid
In hindsight, I think it would have been better to open a new issue once the initial problem has been resolved - it's hard to see the actual problem now. But after reading through the thread, the "only problem" (not saying that it's a small issue
@antonok-edm and @computer777: if either of you can reproduce that problem (or other problems that are not in the tracker yet), please open up a new issue and link to this one if it is relevant.
Thanks!
By * postmarketOS Bot on 2017-11-18T14:06:26