• Content Count

  • Joined

  • Last visited

  1. Don't think so, the connectors are snug on both power supplies, and the boards do start uboot but stall when the kernel kicks in. Maybe there's a momentary power demand increase that the smaller PS can't cope with and it stalls the kernel.
  2. I'm not using any USB cables for power. I use dedicated power supplies with barrel connectors. With a 2.5A power supply, the boards don't run. With a 5A supply, they do. But I agree they're running cool. So maybe my 2.5A power supply is faulty.
  3. Huh, I became suspicious that it may be a power problem when the kernel wouldn't load correctly with the serial monitor attached, so I changed the power supply from a 2.5A one to a 5A one, and now all boards boot correctly. Please ignore the above. I didn't realize that these boards were quite so power hungry. It's funny because the CPU doesn't get even slightly warm while doing an update. I wonder where all that power is going.
  4. I have several Orange Pi One and Orange Pi PC boards (the original ones, H3-based). I have downloaded the latest Armbian release for them Armbian_5.91_Orangepipc_Debian_buster_next_4.19.59 and imaged several SD cards in Linux with dd. The cards are all class 10, some are Sandisk and some are Samsung. I am using a 2.5A power supply for the boards. For all the boards and all the SD cards I get the same result. U-boot starts, gets to the point of loading the kernel, clears the screen then displays "Loading, please wait" then "Starting version 241" and stalls there. Nothing else happen
  5. Yes, that is exactly what I tried using, and why I said that the documentation doesn't apply to the current state of ALSA. For instance,anything I put in /etc/asound.conf is thoroughly ignored and doesn't have any effect; same for /usr/share/alsa/alsa.conf; /proc/asound/modules doesn't exist anymore, etc.
  6. From the CLI that is. I plan on using the OPi as a headless MIDI processor, and I'd like to be able to switch remotely the audio output of ALSA between the default audio-out, the HDMI out and a USB sound card (CM108-based, tested working with the current kernel). ALSA documentation isn't well maintained, most of it is old and doesn't correspond with the current state of the software (config files locations and names, contents etc). I tried various examples I found on several bulletin boards, but none really worked since Armbian seems to do things a bit differently. So I'm asking here:
  7. Also, after compiling the kernel again, when I try to install the packages it gives me sudo dpkg -i linux-dtb-odroidc2_5.06_arm64.deb (Reading database ... 48160 files and directories currently installed.) Preparing to unpack linux-dtb-odroidc2_5.06_arm64.deb ... Unpacking linux-dtb-odroidc2 (5.06) over (5.06) ... dpkg: error processing archive linux-dtb-odroidc2_5.06_arm64.deb (--install): unable to make backup link of `./boot/dtb/meson64_odroidc2.dtb' before installing new version: Operation not permitted Errors were encountered while processing: linux-dtb-odroidc2_5.06_arm64.deb
  8. BTW my problem yesterday with not being able to connect to the C2 with my self-built image - it was a power supply problem. With a good PS it boots just fine. However apt-get update fails with W: Failed to fetch Unable to find expected entry 'main/binary-arm64/Packages' in Release file (Wrong sources.list entry or malformed file)
  9. 64bit. Having a pure 32bit image is only feasible for a headless server-type install, since some drivers (notably the mali-fbdev) are 64bit only AFAIK.
  10. Well I managed to build the image after the change. I did notice some errors during the build (unfortunately I can't copy/paste as I did the building in a real console not a xterm) 1. unsupported ioctl, cmd=0x5331 after update-initramfs 2 missing cp destination file operand after installing RT8192 external driver I wrote the image to a card, plugged it in and connected the odroid to my router via cable, the blue LED blinks meaning it's alive, but it makes no DHCP request to the router. I don't have a display available right now to plug it into, I'll try that tomorrow.
  11. I had cloned your repository in an empty directory about 10 minutes prior to posting. Here's gcc (it's the latest available in Xubuntu 14.04) $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.4-2ubuntu1~14.04.1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-g
  12. I tried to compile a Jessie desktop image for the C2 on my Xubuntu 14.04 laptop. The compile script fails at the u-boot image. The only changes I made to were setting both KERNEL_CONFIGURE and KERNEL_KEEP_CONFIG to "yes" because I wanted to add some modules to the default config. But of course the point where it fails is before it even gets to that part. Displaying message: Preparing host info Config: linux-odroidc2-default Kernel source: Branch: odroidc2-3.14.y linuxsource: linux-odroidc2 Offset: 1 bootsize: 32 bootloader:
  13. Well, so far it seems stable. I have checked the barrel connector and solder joints seem good, no play and very little resistance across. I have found a dual USB charger (one of the ports is high-current, 2A). I'm feeding the current from the 2A plug through the barrel connector, and the other port (1A) through the GPIO. Works well so far, but for some reason if I use just one or the other it doesn't boot correctly. It definitely doesn't use nowhere near as much current as the charger is rated for, and it does heavy tasks (compiling a whole game) without crashing.
  14. I stand corrected; I hadn't actually looked close at how he makes the backup in the first place. But it still wouldn't work if there is more than 16GB of data, simply because there isn't enough space on the 16GB card to hold it all.
  15. That assumes, of course, that you don't already have more than 16GB of data on the 32GB card. Because if you do it won't work. It also has a chance of losing data even if you have less that 16GB on the card, because of the way ext2/ext4 work. There's no guarantee that some files haven't already been written beyond the first 16GB point.