Jump to content

Christos

Members
  • Posts

    306
  • Joined

  • Last visited

Everything posted by Christos

  1. I did a build as I always do, selecting from the build tool, did not have an option though to select or not the Thumb2 during the build, so I guess it is there by default, isnt it?
  2. Yes, sorry, forgot to mention Armbian 5.24, jessie legacy 3.4.113, desktop Opi ONE, PCPlus
  3. Talking about this -> https://github.com/igorpecovnik/lib/commit/cdc02f678620d6dba6c9e4ebc60884fc54c6dfc6 Dont know if anyone else noticed it, but after applying this I got about 10% lower CPU temp. (from 75 ro 67) in OPi/H3 under the same heavy workload with same performance! If there has not been any other temperature modificatioin done then this thumb2 change is definitively towards the right direction. Kudos guys!
  4. Ok, Thanks @sanctus , the kernel option specify [1..5] in RT is quite crucial as it seems. In earlier builds, until 27/Oct, Armbian got build ok (but eventually probably was giving issues as later on found out) with option 5 in kernel RT configure. Now, in latest releases (5.24) it reports error even in build phase. Tried the RT option 4, so far with OPi ONE & PCPlus, in both, armbian is building now ok and the timeout errors I got previously now they have gone. At least found out that the RT option plays a significant role in both the armbian build itself and in the filesystem behavior later on. @Igor , from the latest tests, I see stable performance with the current RT patches up to option 4 for OPi ONE & PCPlus.
  5. @Igor could you please let me know this? Also, I think I've stumbled for some time now on something else (which might again be RT-pertinent) but could not clearly identify the cause of it, now it looks more like RT related. There is a bit of weird behaviour on writes/reads. I had quite a few issues in 5.24 on using the nand-sata-install script in OPi PCPlus eMMC, that is the cause why I created this thread here (no one replied though..) -> https://forum.armbian.com/index.php/topic/2890-opi-pcplus-emmc-testing-utility/ I tried using the nand-sata-install but was getting really a lot of memory write timeouts flooding on screen, tried quite a few times (used different and many SDs just in case) and eventually at some point the system completed the operation, yet writes on eMMC filesystem were really non-stable.. That was made with an image having been builded succesfuly with RT patches at the time (actually since a few armbian releases all my images are/where RT..) Now, understanding that might be some RT issue lurking even earlier, I tried the same operation with an armbian build image without RT patches and it works ok! it writes correctly with nand-sata-install script on eMMC! So, it looks to me that there has to be some connection between RT armbian patches and the misbehaviour I saw there. I'm saying this just for your information to have in mind if you go into re-looking at RT patches. /Edit So far all RT images created were with option 5, full preemptive RT, dont know if this makes an issue, someone with more RT experience might give us some insight on RT options selected in kernel configure. Or what could be the most appropriate for these types of boards.
  6. I know, yet the guy there seems he is paying some attention to what is requested, at least he answers in issues, seen way different behaviour in the past from others..
  7. @zador.blood.stained It looks @tkaiser has his words put right indeed, H5 datasheet given.. -> https://github.com/OrangePiLibra/OrangePi_H5SDK/commit/d4a944cf79491223ee4ac990bcbc3510c9a4a6e0#diff-b1fc301dcc585adeb39dcfdc5cdafbdb /Edit Or at least the person there is quite responsive, good sign that he has given even that and said he will give the actual manual as soon as AW releases it.
  8. @Igor, It looks the current RT patches status in relation to what has been newly committed in Armbian gives this problem. Regarding the .img naming did some tests this morning In sequence: Cleaned and reloaded 'lib', deleted 'sources' and they got re-downloaded via compile.sh. After that, tried a build and the .img name is ok, without -rt143 Tried to do a RT build and it fail with the error message mentioned Then tried to do a plain build and it succeeded but the name contains the -rt143.. Deleted the .config file from kernel sources and tried to do a plain build, again it generated a .img with -rt143 It looks that after I try to build even once with the RT, from then on the .img name contains nomatter what the -rt143. Only when I completely delete the 'sources' a new plain build gives proper .img name. Question If I do a build with RT patches enabled, I need to delete the sources after that if I want a new build without RT ? Please add 'with RT patches' in the title, I cannot do that now. Getting Armbian without a specific commit is not so easy (at least for me), so I have to wait until you guys make the Armbian framework able to have RT again. Hopefully that will be done soon..
  9. Well, with new Armbian releases, I use only the inclusion of 8192cu in the modules.conf and nothing else regarding configuration. There is a utility nowadays that takes care of everything and works ok for me, it is the nmtui. So just include the 8192cu in the modules.conf then reboot and then use nmtui. Working with usb wifi dongle/key in NanoPi NEO and OPi ONE.
  10. @Igor Did a complete fresh git clone of armbian, it re-downloaded all its required components sources/toolchains Fifth test, Armbian build OrangePi PCPlus complete image default (legacy) jessie desktop RT patches included (Not my user patch) Armbian build stops with the error mentioned!! So, the RT patches producing this problem. output.log and patching.log
  11. @Igor Could be some recent armbian github commits changed something in the RT area?
  12. Did a fresh git clone of armbian repository, did not delete the sources/toolchains generated folders since no changes were made to them. Fourth test, Armbian build OrangePi PCPlus complete image default (legacy) jessie desktop RT patches included (No my user patch) Armbian build stops with the error mentioned!! So, it looks again like the RT patches producing this problem. After that, the only test remains is additionally the complete erase of all armbian downloaded components (kernel sources, toolchains) but I think that the result might be the same..
  13. Second test, Armbian build OrangePi PCPlus default (legacy) jessie desktop (No RT) My user patch included Builds ok ..but the builded image name again contains the "-rt143" whereas the RT patches are not included, I verified it (again lol) @Igor, that looks like a problem, dont know if its only on my machine though, didnt do a new/fresh complete git clone since I havent modified the armbian's scripts/framework whatsoever, I just started the ./compile.sh and rely on its included update feature. Third test, Armbian build OrangePi PCPlus default (legacy) jessie desktop RT patches included (No my user patch) Armbian build stops with the error mentioned!! So, it looks like the RT patches producing this problem. I will do a new git clone, to verify if there is a problem in my machine, but the build will take considerable more time since it will download all the required build components again.
  14. First test, Armbian build OrangePi PCPlus jessie desktop (No RT) (No my user patch) Builds ok ..but the builded image name contains the "-rt143" whereas the RT patches are not included, I verified it (lol)
  15. And by checking the debug, seen only this problem Processing file /home/christos/armbian/lib/patch/kernel/sun8i-default/ov5640-enhanced-driver-with-vfe-drc-table-fix.patch patch unexpectedly ends in middle of line nothing else
  16. I dont have any altered script of mine! I do have though a (I2S) patch that I use so far since a few armbian releases without problems and from what I see in the compile screen, it reports as 'succeded'. I'm doing another compile right now without RT and without my patch, so far it goes ok. I'll try to incrementally add the RT first and then my patch and see where it stops.
  17. Tried to have a new build today and got this [ error ] ERROR in function compile_kernel [ common.sh:200 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated I was trying to build with options OPi PCPlus, RT patch, jessie, desktop and got this stopping error message Is there any log with details that I can review in order to pinpoint the exact problem?
  18. @rgb Using here the 8192cu with all my boards and 3.4.113 kernel, armbian 5.24, NanoPi NEO & OPi ONE Just put it in modules.conf nano /etc/modules-load.d/modules.conf ===================================== #8189es 8192cu Christos
  19. "Error: unrecognized/unsupported machine ID (r1 = 0x00000000)" @sanctus When I see such message in my board's booting, I know I need a good/new SD and perform a new SD write with etcher..
  20. Hi, Is there any testing utility/exerciser for OPi PCPlus eMMC? I'm geting strange problems when fast and large writes happen in eMMC. /Edit this is what I get by running 'armbianmonitor -c ~/healthtest' WARNING: It seems you're not testing the SD card but instead healthtest () Starting to fill healthtest with test patterns, please be patient this might take a very long time Free space: 3.59 GB Creating file 1.h2w ... OK! Creating file 2.h2w ... OK! Creating file 3.h2w ... OK! Creating file 4.h2w ... OK! Free space: 369.04 MB Average writing speed: 6.95 MB/s Now verifying the written data: SECTORS ok/corrupted/changed/overwritten Validating file 1.h2w ... 2097152/ 0/ 0/ 0 Validating file 2.h2w ... 2097152/ 0/ 0/ 0 Validating file 3.h2w ... 2097152/ 0/ 0/ 0 Validating file 4.h2w ... 489264/ 0/ 0/ 0 Data OK: 3.23 GB (6780720 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average reading speed: 75.48 MB/s Starting iozone tests. Be patient, this can take a very long time to complete: Iozone: Performance Test of File I/O Version $Revision: 3.429 $ Compiled for 32 bit mode. Build: linux Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner, Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone, Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root, Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer, Vangel Bojaxhi, Ben England, Vikentsi Lapa. Run began: Tue Nov 15 19:40:24 2016 Include fsync in write timing O_DIRECT feature enabled Auto Mode File size set to 102400 kB Record Size 4 kB Record Size 512 kB Record Size 16384 kB Command line used: iozone -e -I -a -s 100M -r 4k -r 512k -r 16M -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 3805 6622 15955 15988 13659 3863 102400 512 12115 8113 78890 78923 77726 7646 102400 16384 8527 8468 80074 80280 79733 8426 iozone test complete. touch: cannot touch ‘healthtest/cardtest.ZfDdZ7/.starttime’: No such file or directory Test stopped, read-only filesystem Please be careful using this media since it seems it's already broken. Exiting test. christos@orangepipcplus:~$ appart from the "Average writing speed: 6.95 MB/s" is very low ..that final line is really alarming.. Any hints or relevant info on OPi PCPlus eMMC?
  21. Way to go @tkaiser !! Good !! My board is on route, hopefully you guys will have everything ready just in time !!
  22. Has anyone else noticed that the image file loaded from this baidu link is 77MB whereas the other OrangePi provided link for that same Debian Server for OPiPC2 in GoogleDrive is 280MB ?!?!..
  23. Hmm.. -> https://github.com/OrangePiLibra
  24. @jernej , @Igor I really thank you guys, responded in no time and most of all made me feel that I'm not alone, kudos to both of you. Problem solved!! U-Boot SPL 2016.09.01-armbian (Nov 11 2016 - 16:59:49) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2016.09.01-armbian (Nov 11 2016 - 16:59:49 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi One DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) dotclock: 148500kHz = 148500kHz: (24MHz * 99) / 8 / 2 HDMI PHY divider: 2 pixel_clk: 148500000 pixel_repeat: false x_res: 1920 y_res: 1080 hor_back_porch: 148 hor_front_porch: 88 hor_sync_time: 44 ver_back_porch: 36 ver_front_porch: 4 ver_sync_time: 5 hor_sync_polarity: true ver_sync_polarity: true b_interlace: false hdmi enabled In: serial Out: vga Err: vga Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2092 bytes read in 179 ms (10.7 KiB/s) ## Executing script at 43100000 Booting from SD 144 bytes read in 126 ms (1000 Bytes/s) 3138723 bytes read in 347 ms (8.6 MiB/s) 5080432 bytes read in 502 ms (9.7 MiB/s) ** File not found /boot/.next ** ** File not found .next ** 37448 bytes read in 468 ms (78.1 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3138659 Bytes = 3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Using machid 0x1029 from environment Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.25.2 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 140659/936560 files, 632182/3751668 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Debian GNU/Linux 8 (jessie)! Expecting device dev-ttyS0.device... [ OK ] Reached target Remote File Systems (Pre). [ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point. [ OK ] Reached target Encrypted Volumes. [ OK ] Reached target Paths. [ OK ] Created slice Root Slice. [ OK ] Created slice User and Session Slice. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on Journal Socket. [ OK ] Created slice System Slice. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Created slice system-getty.slice. Starting Increase datagram queue length... Starting Restore / save the current clock... Starting Load Kernel Modules... Starting Create list of required static device nodes...rrent kernel... Starting udev Coldplug all Devices... Mounting Debug File System... Mounting POSIX Message Queue File System... Starting LSB: Set keymap... [ OK ] Reached target Slices. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Started Increase datagram queue length. [ OK ] Started Restore / save the current clock. [ OK ] Started Load Kernel Modules. [ OK ] Started Create list of required static device nodes ...current kernel. [ OK ] Started LSB: Set keymap. [ OK ] Started udev Coldplug all Devices. Starting Create Static Device Nodes in /dev... Mounting FUSE Control File System... Starting Apply Kernel Variables... [ OK ] Listening on Syslog Socket. Starting Journal Service... [ OK ] Started Journal Service. [ OK ] Mounted FUSE Control File System. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Apply Kernel Variables. Starting udev Kernel Device Manager... [ OK ] Started udev Kernel Device Manager. Starting Copy rules generated while the root was ro... Starting LSB: Tune IDE hard disks... Starting LSB: Set preliminary keymap... [ OK ] Started Copy rules generated while the root was ro. [ OK ] Started LSB: Tune IDE hard disks. [ OK ] Reached target Sound Card. [ OK ] Created slice system-ifup.slice. [ OK ] Started LSB: Set preliminary keymap. [ OK ] Found device /dev/ttyS0. Starting Remount Root and Kernel File Systems... [ OK ] Started Remount Root and Kernel File Systems. Activating swap /var/swap... Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... [ OK ] Activated swap /var/swap. [ OK ] Mounted /tmp. [ OK ] Started Load/Save Random Seed. [ OK ] Reached target Local File Systems. Starting Create Volatile Files and Directories... [ OK ] Reached target Remote File Systems. Starting Trigger Flushing of Journal to Persistent Storage... Starting LSB: Prepare console... Starting LSB: Raise network interfaces.... [ OK ] Reached target Swap. [ OK ] Started Create Volatile Files and Directories. [ OK ] Started LSB: Prepare console. [ OK ] Started Trigger Flushing of Journal to Persistent Storage. Starting LSB: Set console font and keymap... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started LSB: Raise network interfaces.. Starting ifup for eth0... [ OK ] Started ifup for eth0. [ OK ] Reached target Network. [ OK ] Reached target Network is Online. [ OK ] Started LSB: Set console font and keymap. [ OK ] Reached target System Initialization. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Timers. Starting Restore Sound Card State... [ OK ] Reached target Basic System. Starting Entropy daemon using the HAVEGE algorithm... [ OK ] Started Entropy daemon using the HAVEGE algorithm. Starting Regular background program processing daemon... [ OK ] Started Regular background program processing daemon. Starting OpenBSD Secure Shell server... [ OK ] Started OpenBSD Secure Shell server. Starting Network Manager... Starting /etc/rc.local Compatibility... Starting Login Service... Starting LSB: Load kernel modules needed to enable cpufreq scaling... Starting LSB: Advanced IEEE 802.11 management daemon... Starting LSB: Start NTP daemon... Starting LSB: Start/stop sysstat's sadc... Starting LSB: Armbian gathering hardware information... Starting LSB: disk temperature monitoring daemon... Starting LSB: No Display Manager... Starting LSB: Starts LIRC daemon.... Starting D-Bus System Message Bus... [ OK ] Started D-Bus System Message Bus. Starting System Logging Service... Starting Permit User Sessions... [ OK ] Started System Logging Service. [ OK ] Started Restore Sound Card State. [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started LSB: Start NTP daemon. [ OK ] Started LSB: Start/stop sysstat's sadc. [ OK ] Started LSB: Armbian gathering hardware information. [ OK ] Started LSB: disk temperature monitoring daemon. [ OK ] Started LSB: No Display Manager. [ OK ] Started LSB: Starts LIRC daemon.. [ OK ] Started Permit User Sessions. [ OK ] Started Login Service. Starting Authenticate and Authorize Users to Run Privileged Tasks... Starting Light Display Manager... Starting LSB: set CPUFreq kernel parameters... Starting Serial Getty on ttyS0... [ OK ] Started Serial Getty on ttyS0. Starting Getty on tty1... [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. Stopping LSB: Starts LIRC daemon.... [ OK ] Stopped LSB: Starts LIRC daemon.. Starting LSB: Starts LIRC daemon.... [ OK ] Started LSB: Starts LIRC daemon.. [ OK ] Started Light Display Manager. [ OK ] Started Authenticate and Authorize Users to Run Privileged Tasks. [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started Network Manager. [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... Starting Network Manager Script Dispatcher Service... [ OK ] Started Update UTMP about System Runlevel Changes. [ OK ] Started Network Manager Script Dispatcher Service. [ OK ] Created slice user-1000.slice. Starting User Manager for UID 1000... [ OK ] Created slice user-108.slice. [ OK ] Started User Manager for UID 1000. Starting User Manager for UID 108... [ OK ] Started User Manager for UID 108. Debian GNU/Linux 8 orangepione ttyS0 orangepione login: It was the cable!!!!!!!!!! Changed it with a new one just now and everything is fine. Even the tty/uart log is different and now it does not mention any dvi, only hdmi. Thank you again for your efforts and please excuse me for the noise, I should have thought of it earlier. At least now, we learned something, not to trust even the out of the bag cables.. thanks Christos
  25. I'll go out to get another HDMI-HDMI cable.. although this first one was right out of the box..
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines