Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    13656

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor
    It's done for kernel 3.4.x(legacy) and 4.4 (development) ... if you build from sources, it will be working in those cases. https://github.com/igorpecovnik/lib/blob/master/scripts/update-motd.d/30-sysinfo In 3.4 it works without anything, for 4.4 you need to patch kernel.
  2. Igor
    I never try PWM on vanilla but i guess it must work. It's disabled in device tree so you need to add it manually: &pwm { pinctrl-names = "default"; pinctrl-0 = <&pwm0_pins_a>, <&pwm1_pins_a>; status = "okay"; };
  3. Igor
    I tried once, a while ago, but as I remember there were some problems or it was even not booting at all. This one is ok: https://github.com/linux4kix/linux-linaro-stable-mx6
  4. Igor
    Yes, rather roll back to 4.2.3 until this is resolved. SATA booting is working fine on all kernels.
  5. Igor
    It refuses to stay on Y ... I think it's something related to recent changes in USB area with OTG intro ... I try few combinations but no luck.
  6. Igor
    Thanks! I'll check this ASAP. Please tell me which kernel have you used, legacy 3.4.110 or vanilla? You probably used latest images (v4.5) ?
  7. Igor
    OK Leave as is, it's working good enough. I'll put patch inside and we can get back later if there will be some other / more serious issues.
  8. Igor
    One small issue. Charging / not charging seems not working ... When I unplug the power on fully charged battery, percentage drops to 98% which is somehow o.k. ... and when I do some stress tests it is going slowly down to 9x%. OK. When I put power back, there is no indication for charging ... but I can read out that AC is plugged.
  9. Igor
    I have no idea what else but I did a recompile from sources and my Hummingboard normally boots (with a fresh SD card).
  10. Igor
    @zador I would say the file system is corrupted due too many hard resets. There are zero reports that this particular u-boot had troubles reading ext FS. @Insider Second problem here is, that you are not using the same kernel source, not same configuration, not same after patches. I know it should be possible to boot but this raises new questions.
  11. Igor
    Oh, true ... quotes. I completely overlooked that problem ttymxc0 yes, lower case.
  12. Igor
    CPU: Freescale i.MX6SOLO rev1.1 at 792 MHz If you have a single core Hummingboard than this could be a problem. Those builds are designed and tested for dual and quad ... Ask Solidrun what to do in such case. The kernel which we use is more or less stock. I never study differences between single and dual/quad.
  13. Igor
    If this parameter is not defined than it's usually not on the lowest number ... try to boot without or just add it after console parameter ... console=ttymxc0,115200 loglevel=7
  14. Igor
    In theory yes But we have some problem here which we need to guess out if we don't have serial console. Check if your boot.cmd is pointing to /dev/sda1 or wherever your system is. Remember to recompile boot.cmd to boot.scr before booting if you change something.
  15. Igor
    I am aware of Odroid boot weirdness but if legacy kernel boots than this part should be o.k. ... I promise to play with it but this week I am very tiny with the time Subforum in development regarding "framework / script / building" is done. I am just no sure what to do with R1. It's a lot of topics, yes, even in Free sections are some ..
  16. Igor
    Doing this blindly is a recipe that it won't work I don't do such way even I have done it so many times. I think at least you forgot to rsync /lib/modules and /lib/firmware from boot image.
  17. Igor
    By default not possible. I am not that familiar with it to do it manually. Let's just close this topic and move to another.
  18. Igor
    Just grab latest (4.81) and you will be fine. There are at most three different versions anyway. If you are on the board, booted from SD, just install the deb package and the boot loader is auto written, if you are not than you need to extract the file and DD-it to the SD card (mmcblk0) and not to the partition (mmcblk0p1) The u-boot loader which you found is just for booting from NAND.
  19. Igor
    I need very detail information, since I don't have Banana PRO ... based on theory / quick checking it should work I have a very similar board (Cubietruck), which is working fine. Support for this chip is build into all kernels.
  20. Igor
    I don't see any problems ... there is no output to serial console, unless specified ... first boot takes little longer, so you need to wait 1-2min to get login prompt. One reboot is in the middle ... not any more in newer Jessie and Trusty builds. Next edit and change console=ttymxc0,115200 and change loglevel to 7 in boot.cmd, convert to boot.scr ... Than you should see much more. If you did not compile on X86 Ubuntu I can't say what went wrong
  21. Igor
    @zador I'll try to give some feedback on those changes later today. In one case I am using one such battery and it's working just fine. The other which I use is salvaged from some tablet. No official batteries here
  22. Igor
    Which modules are you trying and what the iwconfig tells?
  23. Igor
    @wildcat_paris OK, I'll take a look when possible. You can also try to install kernel 4.4 and DTB on the top of the working legacy build. You will only need to manually set DTB and that's all I think.
  24. Igor
    Thanks! This is part is unchanged - it's default Debian / Ubuntu way. I also need to Google for this info since I never try to change that. http://superuser.com/questions/443986/how-can-i-remove-the-ssh-last-login-info
  25. Igor
    Those are needed to boot u-boot and they are *must be* present in u-boot package.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept