Jump to content

Murdag

Members
  • Posts

    8
  • Joined

  • Last visited

  1. Yeah I scraped VB cause it was so slow, now have qemu setup and running but did not figure out how to forward a drive (that is not even mounted on the host). Putting it onto a LAN and then configuring the wifi things works sure, it's just a bit more to do. thanks anyway
  2. I guess the main issue is that I'm using a mac and cant see the filesystem, on rasperry pi/ rasbian I could see some part of the fs e.g. /boot and you could do something like touch ssh to enable ssh (which is on in armbian by default which is fine) but something along the lines for wifi would make it easier. I guess rasbian has some part of its system on fat32 and armbian is ext4 all the way or something like that?
  3. so reboot with the latest nightly works for me, great! wifi does not work out of the box but I think 5.1 will bring this in? asa this works it would be really nice if one could write the wifi password onto the sd card somehow without having to build the image by myself, if thats possible a hint would be very welcome [ docker via snap does still not work but as I said if you use the docker install script it will work fine (cause I think someone had the same issue) ]
  4. used ` curl -sSL https://get.docker.com/ | sh` instead of snap and it works now, dont really know why but ... has someone tried wireguard yet/ knows whats blocking?
  5. I got ethernet and wifi working now as well, thanks all! Any chance the wifi patch could be included in the build images? I have some trouble installing docker using snap, `docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.` I had similar issues on other systems and was able to solve them but now I'm currently not, maybe there is a setting in the kernel? I saw wireguard is disabled, maybe something about docker as well?
  6. Thats good to know, did you do anything special? I just put the image on the SD, even used the fancy formatting tool recommended by armbian and plugged the thing in, red lights blinking but its not coming onto the network. I did not do any manual config of the image. Maybe its because my board does not have eMMC but this would be a bit of a surprise if this would make some difference. If someone has a clue I'll try it although I don't have much debugging tooling at hand right now, otherwise wait and see, thanks guys.
  7. I was under the wrong impression this was assumed to be working because wifi seemed more advanced but in reality they're just not related at all I guess.
  8. Hello, thank you all so much for your work, very much looking forward to using it! I tried building the current dev image debian and ubuntu without desktop for my orangepi3 (without eMMC) (instructions worked great!) but when I power it on, it does not show in the network, its connected via LAN. I also tried Nico and Krachlates image with the same result. Using the image from OrangePi, it gets an iP and connects. I sadly cannot check what the output is as I have no HDMI cable around (sad but true), jus wondering if there is something I'd need to do in order to make it connect to the Network? IPs are assigned using DHCP and it works fine for Raspis that I have running. For the raspis I have to put in an `ssh` file to enable ssh, I thought maybe there was something similar regarding network for armbian but I did not find something like this mentioned? thanks in any case, maybe I just need to wait for an official image from you guys.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines