• Content Count

  • Joined

  • Last visited

About CryBaby

  • Rank

Recent Profile Visitors

356 profile views
  1. I tried Focal: I'll have a go with Bullseye. Update: Bullseye 145 boots but it doesn't resize the filesytem. I went through armbian-config and everything else seems OK. Need more space to try out a desktop though.
  2. I just tried this on my Cubietruck. uBoot doesn't like the initrd image: Verifying Checksum ... Bad Data CRC Disk image is corrupt or invalid Then it tries to load from TFTP. The image sha256sum verified OK and the card mounts on my PC OK.
  3. I suppose my battery may be too old. Unfortunately, a new one would take a couple of months to reach me from China. I'll see if I can source one from Europe. I don't suppose there's an easy way to debug it, when the power goes it dies instantly (twice this week so far). If anyone out there can confirm it works for them that would be good to know. Yes, I contributed to the Kickstarter. Since it was mainlined in the 4.20s I kind of hoped it would be working by now. I guess there's more to it than that, I am vague on the details. I know the legacy image is unsupported, I've been running mainline until recently, but I just got my home theatre set up and I really need my media player to play media. If I could also play games with my bluetooth joystick that would be sweet. I haven't checked the bluetooth on mainline. I'll do that. I do appreciate all your efforts supporting so many devices. So many, and yet none can replace a cubietruck for me...
  4. Is anyone still working with cubietruck? I installed the latest mainline image over Christmas expecting it to have the cedrus driver but apparently it does not. I thought that everything except HDMI audio should be working in mainline now. So I installed the latest legacy image. It plays videos well but bluetooth doesnt work. I switched it on in armbian-config and 'rfkill list' shows it as not disabled but the bluetooth manager shows no adapter and search is grayed out. This is a regression as it used to work to some extent. Also, very importantly for me, neither image switch over to battery power when the AC goes out. This also used to work on legacy, unless it was cubian that worked and armbian never did, I should keep notes...
  5. A reboot fixes it for a while, but it seems after a few recordings the tuner stops sending video data. vdr restarts and apparently reloads the kernel modules to no effect, so it restarts again... It's recording now and I'll do more tests. I downloaded the 5.20 Debian image from the archive with a view to extracting the kernel but 7z errors out before unzipping the whole thing. E_FAIL. That's on the cubietruck. I'll try it on my laptop when I get back to work and have the bandwidth to download it.
  6. Not that I can see. There is nothing for it in /lib/firmware. The syslog does say: dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state. but there is no mention of firmware.
  7. I have a rtl2838 based DVB-T dongle which was working beautifully under 3.4.112 on my cubietruck. I upgraded a couple of days ago and now I don't get any video data, although the dongle is still recognised. I see 113 includes a fat patch to the rtl2832 driver. Is there some way I can back that out, or a safe way to go back to 112?
  8. My Cubian nand install is using the same old Allwinner u-boot. Unfortunately I am not able easily to test its network performance with big files. My Cubian sdcard install appears to be using whatever came out of the box with the Cubietruck. Presumably it is the same. The network is slow but it never stops. I have noticed that when I initiate scp on my remote armbian Cubietruck (ie. push the files from remote to local) it does not stop. It only stops when I initiate the scp from my local machine (ie. pull). Pushing files from local to remote also does not stop. I haven't had the time yet to try the new u-boot. Presumably I would do a normal nand install then overwrite the old u-boot with the new. Are there instructions for that anywhere?
  9. OK. I have another cubietruck running cubian, which I don't think has the network problem. I will see what it does differently. And I will try the latest mainline u-boot with armbian legacy.
  10. I am booting from NAND as I want the card slot free. v2015.10 has a NAND SPL driver according to Is that not enough? Or if you build the old u-boot can you include this patch:
  11. I'm getting broken connections when I download big files from my Cubietruck. I've tried reducing CPU freq and setting eth0 to 100 half duplex, as recommended in various places. No joy though. It is said that a GMAC fix for this went into u-boot in mid 2015 but my u-boot appears to be older: $ strings /boot/linux/u-boot.bin | grep 201 U-Boot 2011.09-rc1-00000-gc1cb2f9 (May 30 2014 - 10:19:03) Allwinner Technology arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2010.09-50) 4.5.1 GNU ld (Sourcery G++ Lite 2010.09-50) $ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=cubietruck BOARD_NAME="Cubietruck" VERSION=5.20 LINUXFAMILY=sun7i BRANCH=default ARCH=arm Is it possible/safe to install a newer u-boot? If so where can I get it? Or perhaps someone can suggest an alternative solution?