• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by MitchD

  1. Ethernet drivers exist in my image. I tested it before I uploaded it. Your image uses a mainline image, and I provided ethernet patches for that in a post above. Apply the patches and enable them in the defconfig and your own kernel should have them. You set the ethernet driver by doing `make linux-menuconfig`, going to Device Drivers, Network Device Support, Ethernet Driver Support, and selecting "SUNXI Platform Network device drivers", and the three options below that. The only way I know to add drivers to a linux kernel is to build them when you build the kernel. There is no need to download my github and try it, because I gave you the compiled kernel with the drivers in it. If you meant wifi drivers, then you would download mine and patch the kernel to add the drivers, and select those drivers from the `make linux-menuconfig` command, and build the kernel that way. When I put the project together initially, I had a working mainline vanilla boot for the nanopi neo, and I modified armbian's sources to create a legacy buildroot image with realtime capabilities for the nanopi neo. Any use outside of that is up to the end user. I'm not familiar with wireless drivers and I really don't want to spend the time to get them working. The only way I would get them working is if @Igor decided there should be a minimal buildroot image for every board Armbian supports, and I don't think that is likely. If you can't find your device on your subnet, you can try Wake Me On Lan for windows. It will show you every device your computer can ping. If you use linux, nmap and arp should do just fine.
  2. I think you would have to copy directly to the filesystem, but I'm not sure. I've never added drivers after the kernel is compiled. You're going to need to look under /lib/modules and figure out what do there.
  3. It is set up to a dynamic IP right now. If you try `nmap -sP` on your laptop before `arp -a` you might be able to find it. If at all possible, find another ethernet cable, and plug the orange pi directly into the router. Its the easiest method. You should be able to bridge the wireless and ethernet connections, but this is outside the scope of the help I'm able to provide. Its different for every system. The kernel I provided does not have any wifi support, so a cable is going to be the easiest thing to manage.
  4. The kernel you supplied has no drivers, so I'm willing to bet there will be nothing in the TV out. The ethernet doesn't exist in the dtb, so it will not load it in the kernel. I have created a legacy image for you, which has basically everything working but the wifi. It has python and ssh like you wanted. The login is root, password is root. For TV output, you'll want to change the fex file, as described here. Since there is no xserver, I'm not sure what you're going to be displaying on the TV. I hope this helps.
  5. The first link boots for me. How are you copying this to the SD card? I use Etcher. It complains about not having eth0, which leads me to believe something is not correct in the dtb. There is also no wifi driver in this build, so you will not get wifi to work. Looks like ethernet support isn't until 4.13, as you can see on the sunxi mainlining effort page. The output of `uname -a` is: Linux OrangePi_Zero 4.11.9-rt7 #1 SMP Sat Jul 15 20:00:03 CLT 2017 armv7l GNU/Linux This tells me its SMP, not PREEMPT RT. Thats a flag you might want to enable in make linux-menuconfig. Since it does not boot for you, I would recommend trying a better power supply. If that changes nothing, try a different SD card. I imagine you're going to want to have ethernet enabled. I have these patches, which add support for ethernet into a mainline kernel. Add them, and you should be good to go.
  6. I'm using puredata with alsa, and i have a latency of about 8ms. I haven't dug down and messed with drivers yet, but I hope to reduce that. I may add Jack in the future. I'm gonna guess you built it from linux 3.4 sources, right? In your boot partition, there is no script.bin. You'll need that instead of the dtb for the legacy images. I would also suggest getting a USB to serial device and plugging directly into the board via the headers to get boot output. It is extremely useful in cases like these. I will try with my orange pi zero tonight.
  7. I'm not sure that is the way that buildroot's kernel will want to work. Buildroot relies heavily on busybox and its own rootfs. I believe if you copied over the kernel and the /etc/init.d scripts you may have a chance, but its still a pretty challenging endeavor. Do you have your buildroot configuration files somewhere that I can look at? For example, in the kernel config it asks which partition your rootfs is in.
  8. Thanks @gatinho! I'm using the configuration of the older armbian commit for 3.4.112 from November 2, 2016. In this commit the orange pi zero wasn't released yet. I'm not sure it'll work without any modifications. Do you have the H2+ version of the orange pi zero? I have one at home and I can definitely try the rt kernel on it and see what needs tweaking. There shouldn't be all that much to change, assuming the wireless drivers were in november. The main point of contention would be the fex file which sets up everything. I'll look into when the orange pi zero was supported by armbian and fork the branch at that date and see what I can come up with. Are there any programs you'd like installed on the buildroot image? In buildroot, there is no apt-get install, and no gcc compiler. It's meant to basically be a fully cooked system with no unnecessary overhead.
  9. You could try buildroot, which has boot times at around 2-3 seconds. I used armbian's build system to help build a working kernel that has all the stuff you're used to (USB OTG, ethernet, GPIO, etc). It is totally customizable for which packages you need installed, and its got the fastest boot I've seen. Which applications do you want on the device? Do you mind if its mainline or legacy?
  10. I'm not sure if anyone is interested in a very small distro without gcc, but I spent some time the last week using buildroot and armbian's source files to create a 3.4.112-rt image for the nanopi neo. It is going to be part of a realtime audio project (think synth or guitar pedal) that I'm working on and it demands a quick boot, among other things. There is also a mainline version, but it doesn't have all the fixings you folks like, so I don't know if you'd want to use that. You can find the build scripts and config files on my github. I'll be posting the legacy image in a zip file tonight, once I verify everything is reproducible. I would like to thank the Armbian developers for all their time and energy doing what they do. Their code and guides have helped me understand how one would even attempt something like this, and I'm very grateful. If you ever use my image, please donate to the Armbian community. The screenshot is proof that the system works, and how much ram it uses while forwarding a puredata session over X-forwarding. I'm open to any questions. Thanks.