All Activity
This stream auto-updates
- Past hour
-
I have a CoCo 2 and a Model 100 Portable.
- Today
-
No worries, I just wanted to confirm what you asked. I have it working with the tweak so I'm happy at this point. I'm also working on restoring an old TRS-80 Color 1 right now so I understand the distraction
-
The nand-sata-install script does that adjustment for you, that's the issue I think. https://github.com/armbian/build/blob/master/packages/bsp/common/usr/sbin/nand-sata-install#L205 I'm building a model train speed controller to replace the 1970's one that just failed on my son, a bit distracted. :-)
-
Okay, so I reverted boot.cmd to your version, ie put the rootdev back to /dev/mmcblk1p1, then created armbianEnv.txt with the following line: setenv rootdev "/dev/mmcblk0p1" Rebuilt the scr. Rebooted. Fails to boot, this is the captured output: Begin: Running /scripts/local-block ... done. done. Gave up waiting for suspend/resume device done. Begin: Will now check root file system ... fsck from util-linux 2.29.2 [/sbin/fsck.ext4 (1) -- /dev/mmcblk1p1] fsck.ext4 -a -C0 /dev/mmcblk1p1 LPotato_SD: clean, 13/1954064 files, 166731/7814912 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: No such file or directory mount: invalid option -- done. mount: No such file or directory run-init: opening console: No such file or directory Target filesystem doesn't have requested /sbin/init. run-init: opening console: No such file or directory run-init: opening console: No such file or directory run-init: opening console: No such file or directory run-init: opening console: No such file or directory run-init: opening console: No such file or directory No init found. Try passing init= bootarg. (initramfs) So, while on a fresh Armbian image the boot.cmd you posted works completely 100% as is, when using an older image that was updated via apt and etc seems to require me to directly change the cmd and rebuild scr. Unless I'm doing something wrong with the ArmbianEnv.txt, which is entirely possible. I'm not really familiar with that file.
-
OK, so, for you/anyone doing this before it's officially baked in: Download 4.18 image Build newest 4.18 kernel/u-boot update boot script with the one currently in our repo reboot (because of superstition) run nand-sata-install I would recommend being on the moderately advanced side before attempting it, unless you really want to experiment.
-
Yes, sorry that statement is correct, it would still boot from SD which allowed me to go back in and fix it. I don't have the exact logs of that point but I believe that was when it was hanging at trying to remount the rootfs and failing, so it just sat there hung until I inserted the SD card.
-
Wouldn't boot from eMMC or from SD? It should still work from SD with old boot script, just not from eMMC.
-
testers wanted Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party
Igor replied to Igor's topic in Development
Yes I did notice odd numbers but forgot to check. I do have some thermometer around but I am not close to the boards until tomorrow evening. -
Okay, I might have goofed on something here. I'll fire it back up in a bit, revert my boot.cmd modification, and retest. I can confirm, with both an older armbian image that was upgraded via apt, and with a brand new image downloaded from the main site, that nand-sata-install does not work. The only way I got past that was rebuilding a newer 4.18.19 kernel, and uboot. After that, I required the use of Tony's updated boot.cmd in order to boot from it, it would not boot by default at all.
-
I think wait until 4.19, I was working with @sbc_chrisb to get an image with the typical Armbian package support (kernel/etc). The updated boot script and a fresh 4.18 build can identify and install armbian to the eMMC without boot issues. I assume the issue being seen by Chris has to do with the older image being updated, as you mentioned. Just for sanity I booted my Le Potato up with only the eMMC present again to make sure. ;-) Rebuilt images should work, if you would want to test (assuming you have an eMMC...)
-
No - source: had 2G-IoT; threw it in trash
-
testers wanted Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party
5kft replied to Igor's topic in Development
@Igor - in 4.19.y it looks like the CPU temperature now reported by "/sys/class/thermal/thermal_zone0/temp" is ~10C greater than it was in previous kernels for the H5. The "sun4i-gpadc-iio.c" driver in 4.19.y has numerous changes compared to the previous kernels, and I'm not sure if the previous value reported was incorrect and the new value is correct, or vice-versa. This is consistent across all my different H5 boards. Previously my H5 boards would idle around 30C (reported), now they idle at around 40C (reported): root@orangepizeroplus2:/sys/class/thermal/thermal_zone0# cat temp 40341 root@orangepizeroplus2:/sys/class/thermal/thermal_zone0# Unfortunately I don't have a thermometer handy to check the case temperature of the CPU, but by finger test on the boards the CPU appears to physically be at the same temperature as with the previous kernel... All boards are running idle with no activity (e.g., 240MHz/480MHz clock speed). @Icenowy might you have any ideas regarding this? -
Took me over a year to isolate this bug. Randomly, I have found that /boot/armbianEnv.txt had unconsistent content. Examples: .tty1tty1LOGIN.8 ¹[fU7ttyS0tyS0LOGINusbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u network={ ssid="Demaine_40_Grd_Rue_Chambre-BP" #psk="1234567890" psk=693d195a3bf2ab6defbcc0b54604ced4286a067996138db6dc793d8648f67d79 } usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u network={ ssid="fabste" #psk="1234567890" psk=95342031a4b28398045e1761f9c64f8454902e80d37102e5476fa79abd59e144 } 2 } usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u At last, I have found that "fabste" is the SSID of the network of my neighbour. How did this get here ? The bug occurs only on Orange Pi Zero boards ... which need to perform wifi scan. Does not happen on boards that operate as WIFI AP, or use ethernet. The wifi scan is required to connect to the AP. The scan seem to produce a temp file somewhere (maybe in /tmp, not sure). Then, later, /etc/init.d/armhwinfo runs this, which is very suspicious to me: read USBQUIRKS <${TMPFILE} sed -i '/^usbstoragequirks/d' /boot/armbianEnv.txt echo "usbstoragequirks=${USBQUIRKS}" >>/boot/armbianEnv.txt and if this is followed by a power failure, you end up with a corrupted file: https://lists.denx.de/pipermail/u-boot/2018-June/332375.html https://github.com/ConnectBox/connectbox-pi/issues/220 It's a rare issue from Google point of view; but it's known, and it makes most of my opi0 unusable. Sooner or later, it affects 100% of my opi0 that work as wifi clients. It rendends my pis unusable because I need very specific features which are set in /boot/armbianEnv.txt , usually w1-gpio. When the file is corrupted, and after reboot, I loose control over my 1W devices, and the whole project got broken. Here is my fstab, in case it matters: UUID=ebe9dacf-124f-486c-b6c1-08749e209374 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 I am not sure how to fix this at the distribution level: - use something different than sed in armhwinfo to alter /boot/armbianEnv.txt - perform a sync - change ext4 features - change mount options For now, I am trying to write a personnal fix: record a backup copy of /boot/armbianEnv.txt and restaure it if critical words like "overlay_prefix=sun8i-h3" disappear. Note that, when the file is heavily broken, for all 3 examples above, the pi can boot, establish network connexion, and remains reachable, mostly. I only loose the 1W or GPIO feature. There seem to be very good default settings set as fallback somewhere else. Here are unaffected opis: verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=cir usbhost2 usbhost3 w1-gpio param_w1_pin=PA15 rootdev=UUID=ebe9dacf-124f-486c-b6c1-08749e209374 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 w1-gpio param_w1_pin=PA15 rootdev=UUID=ebe9dacf-124f-486c-b6c1-08749e209374 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I am not sure why one has an empty line. But in both case, the usbstoragequirks line is doubled, and identical to my eyes. This means, /etc/init.d/armhwinfo tries to add already existing data. This script lacks checks !!! .
-
Just a quick note here. Nand-sata-install utility works if you don't mess up with a system. On official images and on supported boards. For 3rd party I don't know and on Lepotato AFAIK we didn't get this far yet? (I could easily miss this) @TonyMac32 Shell I rebuild all Lepotato images? Or later when bumped to 4.19.y?
-
I used this as a patch. That enables building of the pcm5102a module. Put it in userpatches/kernel/yourkernel I got the feeling that Kconfig just doesnt show entries without a text in menuconfig. diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig index c367d110..87c6ae4c 100644 --- a/sound/soc/codecs/Kconfig +++ b/sound/soc/codecs/Kconfig @@ -680,7 +680,7 @@ config SND_SOC_PCM3168A_SPI select REGMAP_SPI config SND_SOC_PCM5102A - tristate + tristate "Texas Instruments PCM5102A CODEC - I2S" config SND_SOC_PCM512x tristate
-
which tool do you use for wrinting images to SD-CARD - i am on Manjaro -linux
martinayotte replied to malaga's topic in General chit chat
Since "dd" doesn't any "verify" during or after "writing", there is no guaranty that binary integrity is Ok. -
You can look at this library, but you will need to tweak base register address to meet the one for H6 : https://github.com/Jeremie-C/OrangePi.GPIO You can read what I've answered previously here :
-
which tool do you use for wrinting images to SD-CARD - i am on Manjaro -linux
olivluca replied to malaga's topic in General chit chat
Why "gamble"? dd works just fine. -
Not expected, root dev should be modified in the armbianEnv.txt file. Sent from my Pixel using Tapatalk
-
Follow up post, in case anyone ends up here in searches on this topic. Once i had this working, I then repeated it using my original SD card install with what started out as an older version of Armbian, upgraded via apt. I had a few minor bumps I'm going to explain here. 1. The new kernel is a must. The stock kernel did not work, I had to reuse the 4.18.19 kernel packages I built before. 2. The updated boot script I keep mentioning has to be tweaked. It will try to use mmcblk1p1 for the root device, but on my board the mmc is mmcblk0. The device would not boot from mmc until I modified the boot.cmd to set the rootdev and rebuilt the scr. I'm not sure if this is expected behaviour or not.
-
testers wanted Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party
rusatch replied to Igor's topic in Development
Thank you. I will switch kernel to dev and test it. -
testers wanted Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party
5kft replied to Igor's topic in Development
Hi @Igor, I've tried a top-of-tree H5 build so far on: Neo2 v1.1 512MB Neo2 v1.1 1GB Orange Pi Zero Plus2 H5 Nano Pi Neo Plus2 ...and all works well. Very nice!! (These are all dumb regulator boards BTW) Tests include USB (Wi-Fi and Ethernet dongles), H/W SPI interface (via spidev), multiple GPIOs (via libgpiod). I've switched to 4.19.y for all of these now. (I still have a few more boards that I'll dig up and try it on...) -
Hello I have Opi lite 2 + 28byj-48 driver and step motor, and I want to play around, but can't find RPi.GPIO for OPi lite 2, how can I make it work ? I find pretty good example with raspberry pi http://www.raspberryproject.pl/en/automation/28byj-48-stepper-motor-raspberry-pi/ , I rearranged GPIOs to fit my board but I have error: File "testy.py", line 4, in <module> import RPi.GPIO as GPIO ModuleNotFoundError: No module named 'RPi' Welcome to ARMBIAN 5.67.181116 nightly Ubuntu 18.04.1 LTS 4.19.2-sunxi64
-
Hello i own an old mxii 2gb tv box (i think is k200) and i was looking for ages to find a working dtb.img. I tried all of them from many armbian images and nothing worked. But this worked like a charm. How do you find it? From which one armbian image? The only problem i have now is that all armbian i tried does not recognise wifi neither internal nor usb external
-
testers wanted Next LTS kernel 4.19.y Allwinner A10, A20, A64, H2+, H3, H5, H6 debugging party
5kft replied to Igor's topic in Development
Hi @rusatch, if you are using the 1.3GHz CPU overclock overlay in your "overlays=" line for your H5 then this could be the cause of your problem (overlay "cpu-clock-1.3GHz"). (If this isn't the case for you, then it's odd because USB works fine for me on four different boards I tried with the new 4.19 kernel...) This overlay needed to be updated for 4.19.y, and if you load it by default in the current build then the load will fail and the DT will reset to the board default. I just pushed an update for this for the new kernel (see https://github.com/armbian/build/commit/06451d37a64a4fd2599207722c73c9c160b63100). The new 4.19.y mainline includes a much more complete cpu opp frequency table (nice!), with frequency and voltage definitions all the way to 1.368GHz. For boards that have real DVFS-capable regulators then the higher frequencies will work by default. So I updated the 1.3GHz overclock overlay hack for boards that only provide a fixed 1.3v maximum, and the new name for the overlay is "cpu-clock-1.3GHz-1.3v". (Side note: I removed the previous "cpu-clock-1.4GHz" overlay as given that the maximum clock speed default at 1.4v is now 1.368GHz it's not really worth maintaining one that goes to 1.396GHz.)
