maxlinux2000
-
Posts
50 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by maxlinux2000
-
-
I don't know if I can help to solve this problem, but I can try.
I want compile the kernel 5.07 because it's working on orangePi3, an then compile again the last 5.1.3 comparing with previous, in order to found the problem and share here the possible solution.
I think that it's only a kernel module that create the bug.
-
ok, i'm tring using this topic
-
I am compiling the armbian for orangePi3, using the armbian tools ... and the compilation works fine.
It works both from the kernel_only and from the entire imageBut I have a problem with the current version of the kernel, because it turns out that it does not support the hdmi-vga adapter and I would like to compile the 5.07 kernel instead of the 5.10.
I have found in the doc but I do not find how to indicate to the compile.sh script that it has to compile version 5.07 of the kernel.
Inside the file config-default.conf I do not see where to put the version.The documentation:
https://docs.armbian.com/Developer-Guide_Build-Preparation/
It is insufficient and does not do much to solve this problem.Can someone help?
regards
MaX -
[ error ] ERROR in function prepare_host [ general.sh:516 ]
[ error ] Running this tool on non x86-x64 build host in not supported
.... so I need to use an x86-x64 tu build an arm kernel? Why?
the arm platform is not reliable enough to compile a kernel?
-
The problem is in the kernel!
Today I copied the 5.07 kernel version, from the Armbian 5.82, that I have in the mmc on the 5.87 that I have in the SDcard.
Now Armbian 5.87 works perfectly, so the problem is in the kernel that for some reason leaves the black screen on orangePi3 using the hdmi-VGA adaper.My idea is now, to try to compile the linux kernel directly in orangePi 5.82, then install it on the SDcard, and verify if it works (or not).
One question, I want to compile only the kernel and not the entire distribution. Can I use the old Debian methods, or do I have to use the repository at https://github.com/armbian/build and then use the kernel_only option?
Note for me, to remember in the future:
In order to use an old kernel in a SDcard you have to:
- rename (on the SDcard) the boot folder in boot.original
- copy the boot folder from the functioning installation in the sdcard
- Copy and replace the file armbianEnv.txt from the folder /boot.original to /boot
- copy from the functioning installation to SDcard, the modules in /lib/modules/<KernelVersion>
-
17 hours ago, martinayotte said:
This seems to be the issue !
Most likely due to the SDCard itself, either corrupted or defective ...
I'm using a newly purchased kingston 16GB sdcard.
But I think the micro sdcard do not have the "read only" switch.
So I do not understand this error. Should I change the sd card? -
I tested the build today 18/05/2019 and it continues with the black screen of my vga lcd of 19".
But I searched in the basement for my old 17 "screen (Hyundai lcd) and ... bingo! The screen shows the start of armbian boot.But there is a big problem, everything is shifted to the right (to 1/3) and the text disappears to the right side.
The digital information on the screen tells me that it is running at 1280x960 60hz.
If I try to move the text to the left, using the buttons on the display it tells me that it is already at maximum and there is a small blinking line to the left at bottom.
Everything points to a problem of synchronization of the refresh in the output hdmi. Problem that version 5.82 did not haveNote that I am using the original hdmi -> vga adapter from the orangePi store.
-
ok, finally I boot from the mmc armbian 5.82, and mounted the 5.87 version of 17/05/2019 in the SD card, then chroot, armbianmonitor -u and here you can see the kernel logs
I hope can help
regards
MaX
Note for the future:
$ sudo su
# cd /media... SDcard path
# mount -t proc /proc proc/
# mount -t sysfs /sys sys/
# mount -o bind /dev dev/
# chroot .
# armbianmonitor -u
# exit
-
Hi
in the last build of 17/05/2019,
https://dl.armbian.com/orangepi3/nightly/Armbian_5.87.190517_Orangepi3_Ubuntu_bionic_dev_5.1.0.7z
armbian won't boot and there are a black display
My board is a opi3 2gbram + mmc 8GB
The board is working, because in the mmc, I have installed an old version (5.82) and I can bood from the SD card with android 7 get form here:
I tried to connect via ssh from another computer, and it's works, I login, changed the default passwd, but after 1 or 2 minutes, the opi3 reboot and from this moment, the reboot is every 30-40 seconds so I don't have the time to login again with ssh
I tried again following this doc:
https://docs.armbian.com/User-Guide_Fine-Tuning/
# nano /boot/boot.cmd
disp.screen0_output_mode=1280x720p60
# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
but nothing it doesn't works
Now I will try to use the debian build image version instead ubuntu one....
-
Hi
the last build,
https://dl.armbian.com/orangepi3/nightly/Armbian_5.86.190515_Orangepi3_Ubuntu_bionic_dev_5.1.0.7z
... my in OrangePi3+emmc-2GBram, can't boot correctly.
I'm using the hdmi-> vga adapter that they sell in the orangepi store on aliexpress and their original 3A power supply.
I get black screen and continuous reboot every 30-40 seconds.
I have no way to debug and give more information. I think it's a panic kernel and the system reboot automatically.My display is a lcd - 1440x900_60 from LG
I have also installed in the 8GB internal mmc the version
https://dl.armbian.com/orangepi3/nightly/Armbian_5.82.190423_Orangepi3_Ubuntu_bionic_dev_5.0.7.7z
and it works correctly after some minor tweaks. (no reboot, no black screen)I think we should set the default resolution of the console to 1024x768 and not a higher one, in the case that is what causes the black screen. Not everyone has a 1080p display
-
Mini tutorial
I am putting here some notes for posterity
In the current version of armbian (testing H6) I use X11 / Xorg only reaches 1024x768, but my display reaches 1440x900.
To add this new resolution to the list of Settings/Display you have to give these commands:# xrandr --listmonitors
(this command serves to see what it's called, the hdmi output)
# cvt 1440 900
(output:
# 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz
Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync )# xrandr --newmode "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
# xrandr --addmode HDMI-1 1440x900_60.00
# xrandr --output HDMI-1 --mode 1440x900_60.00
If it works then modify Xorg with:
# sudo mcedit /etc/X11/xorg.conf.d/40-monitor.conf
Section "Monitor"
Identifier "HDMI-1"
Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
Option "PreferredMode" "1440x900"
EndSection# reboot
-
Hi,
I tried to install on my orangepi3 the last image of 05/15/2019https://dl.armbian.com/orangepi3/nightly/Armbian_5.86.190515_Orangepi3_Ubuntu_bionic_dev_5.1.0.7z
But it gives me a panic kernel when it does the boot.
So I've gone back to the old version 5.82.190423https://dl.armbian.com/orangepi3/nightly/Armbian_5.82.190423_Orangepi3_Ubuntu_bionic_dev_5.0.7.7z
and I've updated with apt-get
When it has rebooted there was the black screen
Before starting the update, the resolution of the display was 1024x768 and its maximum resolution is 1440x900.How do you restore the resolution of the console to 1028x768? I can access to console from another computer via ssh...
regards
MaX
-
a question, on the server https://dl.armbian.com/orangepi3/nightly/ almost all the images have disappeared. Only some old ones have remained. What happens?
-
On 4/26/2019 at 4:56 PM, Igor said:
That is normal for things that are in development.There will be once in the future. There are many ways to speed up this process by helping the project: https://www.armbian.com/get-involved https://www.armbian.com/donate
You are right! I just send a little contribution via paypal
-
This build is a ROCK!!
https://dl.armbian.com/orangepi3/nightly/Armbian_5.83.190427_Orangepi3_Ubuntu_bionic_dev_5.0.10.7z
I'm working with her all day.
I've done graphics with gimp and inkscape.
I have written documents with libreoffice,
I have used the browser for the internet with several tabs open and answering a forum like this.
I have compiled the Marlin firmware (for 3D printers) with Arduino IDE (the last one) ... and everything rolling on wheels.
I have copied 1GB circa file size, from an external hard drive to the internal emmc, by usb3 and it is very very fast.
I have downloaded files, installed programs with apt without problems.We have already begun to see the light at the end of the tunnel?
I do not think it is too long to have a distribution stable enough for daily use.There are minor problems, such as the firmware path for wifi, then some launchers in the xfce4 menu that do not work and some warnings.
You have to check if the Bluetooth works ... I have not tried it to install yet.
but, I'm happy with this system. It is not more unstable than a SID in Debian :)
-
No idea, I'm new in this world... my monitor is 1440x900.... (a bit larger of 720p) and both xorg and the console automactly self adapt theys resolutions.
I think that in a 1080p monitor the system is supported from armbian and the H6 boards
-
-
WOW!! the build of today is fantastic!!
https://dl.armbian.com/orangepi3/nightly/Armbian_5.83.190427_Orangepi3_Ubuntu_bionic_dev_5.0.10.7z
chromium, libreoffice, gimp, inkscape... all together on oragenpi3 - 2GB Ram
-
Hi all,
I'm writing from the last nightly build 5.83-190427 on my orangeP3 2GB Ram.... and seem that the spontaneous reboots problem is solved.
Today I installed the complete desktop without problem... only a warning in the characters interface of armbian-config.
I think that it's for debug purpose.
This board is fast enough for simple tasks, like web navigation . I will to try with libreoffice...
regards
MaX
-
1 minute ago, NicoD said:
When your board is +80°C it is throttling to 1.3Ghz. So it's slower than a 1.5Ghz sbc then. So yes a heatsink is adviceable. And if you don't use a big f* heatsink like @greg798, then a fan is welcome too. But even at 3.3V it's sufficient not to throttle.
Sound doesn't work yet. I don't think HDMI sound will work soon. Maybe 3.5mm jack can work. HDMI audio doesn't work on all Hx boards.
The reboot problem isn't normal. If you can, try measuring the voltage at the usb ports. I've had problems with the OPi3 too with unstable voltages. It was better when using microUSB for power. (I know, it's a joke when microUSB is better than barrel jack).
In this moment, the board is a 1800MHz and 72ºc ... I can't measuring the usb port voltage in this moment... I need to buy a tester, next week I 'll try it.
backing again to audio... In the system preferences (Volume Control), appear a "Defaul Sink" card... and the vmeter is playing, but in the Output Devices appear "Dummy Output".
-
Now with the cpu temperature is at 74º the power supply is cold.
Another question... is fundamental an heat sink for the H6?
-
1 hour ago, martinayotte said:
You didn't mentioned which H6 boards you are using ...
If your board is rebooting by itself while at 45º simply by executing an apt-get, your board and/or power supply are defective.
Sorry, I forgot to mention it!
OrangePi3 + emmc + 2GBRamAt this moment I am testing with 2 chromium windows, playing 2 video from youtube at 720p ... perfect! :D
Now I'm missing the audio cardThe power supply? I'm usig the original one from orangePi....
It is possible but this behavior is erratic.
I suppose that with the CPU at 80º + the power consumption is higher than when it is at 45º.
Now is one hour that does not reboot.. -
Hi, I am using the latest available build (5.83-190426) and I have seen many improvements.
They are still there the spontaneous reboots, and the problem with the wifi firmware, I hope it gets fixed soon.Now I would like to know how to activate the audio card. I'm adding a vga monitor with the hdmi adapter (HDMI to VGA CABLE from ORANGEPI).
How is the audio activated?I have played for 2 hours videos from youtube to 720p, then there has been a spontaneous reboot.
The temperature of the CPU was around 82ºc all the time, with an occupation of 82%.I think I will have to put a fan
but the temperature is not fault. Sometimes do the reboot with cpu at 45º, for example installing a package with apt-get.
-
On 4/25/2019 at 2:19 PM, martinayotte said:
They are there : https://dl.armbian.com/orangepi3/
Hi, I'm new to orangepi3 + emmc.
I have checked both images 5.83-19425, but they can not be used. The network does not work at all. Neither the ethernet nor the wifi.Do you know if there is a newer version that can work decently?
Black screen - was: OrangePi3 won't boot
in Allwinner sunxi
Posted
Today, using a converter "ttl-> usb" I can show something of what happens in my OrangePi3
root@orangepi3:/boot# [ 361.132423] reboot: Restarting system U-Boot SPL 2019.04-armbian (May 29 2019 - 04:11:37 +0200) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.1(debug):89a4d26-dirty NOTICE: BL31: Built : 04:11:28, May 29 2019 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc079e78, model: OrangePi 3 INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 NOTICE: PMIC: AXP805 detected INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.04-armbian (May 29 2019 - 04:11:37 +0200) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi 3 DRAM: 2 GiB MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... No controllers found 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 3167 bytes read in 3 ms (1 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 2 ms (80.1 KiB/s) 27608 bytes read in 11 ms (2.4 MiB/s) 4161 bytes read in 8 ms (507.8 KiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 44000000 8796297 bytes read in 893 ms (9.4 MiB/s) 14563336 bytes read in 1475 ms (9.4 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8796233 Bytes = 8.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 4979c000, end 49fff849 ... OK Loading Device Tree to 000000004972c000, end 000000004979bfff ... OK Starting kernel ... Ubuntu 18.04.2 LTS orangepi3 ttyS0 orangepi3 login: rootI have tried to copy the file /boot/armbianEnv.txt in boot / boot.env because I assumed that there is an error in the path of the boot manager, but it does not work, it gives a CRC error.
root@orangepi3:~# reboot [ 114.695833] reboot: Restarting system U-Boot SPL 2019.04-armbian (May 29 2019 - 04:11:37 +0200) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.1(debug):89a4d26-dirty NOTICE: BL31: Built : 04:11:28, May 29 2019 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc079e78, model: OrangePi 3 INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 NOTICE: PMIC: AXP805 detected INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.04-armbian (May 29 2019 - 04:11:37 +0200) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi 3 DRAM: 2 GiB MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from EXT4... *** Warning - bad CRC, using default environmen t In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... No controllers found 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 3296 bytes read in 3 ms (1 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 2 ms (80.1 KiB/s) 27608 bytes read in 12 ms (2.2 MiB/s) 4161 bytes read in 8 ms (507.8 KiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 44000000 8796297 bytes read in 893 ms (9.4 MiB/s) 14563336 bytes read in 1475 ms (9.4 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8796233 Bytes = 8.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 4979c000, end 49fff849 ... OK Loading Device Tree to 000000004972c000, end 000000004979bfff ... OK Starting kernel ... [ 17.749002] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep st ate -110 Ubuntu 18.04.2 LTS orangepi3 ttyS0 orangepi3 login: Ubuntu 18.04.2 LTS orangepi3 ttyS0 orangepi3 login: Ubuntu 18.04.2 LTS orangepi3 ttyS0 orangepi3 login:Results: My screen is on, but in black.
I remember you that I'm using the HDMI-VGA adapter, the max resolution is 1440*900_60 and in version 5.82 of Armbian, it works perfectly.
Now I'm going to increase the verbosity to 7 and I copy below the result
----------
I'm trying to set the console to 1280x768_60 but now there is a kernel panik.
Here my /boot/armbianEnv.txt
verbosity=7
console=both
overlay_prefix=sun50i-h6
rootdev=UUID=5e6d5fb1-968b-4ce0-b6de-cde02149329b
rootfstype=ext4
hdmi.audio=EDID:0
disp.screen0_output_mode=1280x720p60
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
[ 6.089829] ------------[ cut here ]------------ [ 6.101201] kernel BUG at arch/arm64/kernel/traps.c:425! [ 6.113197] Internal error: Oops - BUG: 0 [#1] SMP [ 6.124665] Modules linked in: realtek dwmac_sun8i mdio_mux [ 6.136959] Process btrfs (pid: 359, stack limit = 0x(____ptrval____)) [ 6.150260] CPU: 2 PID: 359 Comm: btrfs Not tainted 5.1.5-sunxi64 #5.88.19052 9 [ 6.164361] Hardware name: OrangePi 3 (DT) [ 6.175247] pstate: 00000005 (nzcv daif -PAN -UAO) [ 6.186767] pc : do_undefinstr+0x2a4/0x2c0 [ 6.197634] lr : do_undefinstr+0x138/0x2c0 [ 6.208447] sp : ffff00001140b6f0 [ 6.218453] x29: ffff00001140b6f0 x28: ffff8000736b1a00 [ 6.230277] x27: 0000000000001600 x26: 0000000000000000 [ 6.241878] x25: ffff00001019e258 x24: 0000000000000000 [ 6.253444] x23: 0000000060000005 x22: ffff00001019e038 [ 6.264994] x21: ffff00001140b890 x20: ffff00001140b750 [ 6.276330] x19: ffff000010dbc000 x18: 0000000000000000 [ 6.287403] x17: 0000000000000000 x16: 0000000000000001 [ 6.298182] x15: 0000000000000000 x14: 0000000000000000 [ 6.308650] x13: 0000000000000000 x12: 0000000000000000 [ 6.318821] x11: 0000000000000000 x10: 0000000000000001 [ 6.328755] x9 : ffff800077bb71c0 x8 : 0000800066e08000 [ 6.338620] x7 : 0000800066e08000 x6 : ffff00001140b748 [ 6.348389] x5 : ffff000010e68148 x4 : 0000000000000000 [ 6.358107] x3 : 00000000d5300000 x2 : ffff000010dc66c8 [ 6.367712] x1 : ffff000010e68148 x0 : 0000000060000005 [ 6.377204] Call trace: [ 6.383724] do_undefinstr+0x2a4/0x2c0 [ 6.391500] el1_undef+0x10/0x84 [ 6.398668] pagevec_lru_move_fn+0x60/0x158 [ 6.406799] __lru_cache_add+0x80/0x98 [ 6.414487] lru_cache_add_active_or_unevictable+0x6c/0x128 [ 6.424072] __handle_mm_fault+0xad0/0xdc0 [ 6.432201] handle_mm_fault+0x108/0x1c8 [ 6.440118] do_page_fault+0x1b8/0x458 [ 6.447621] do_translation_fault+0x64/0x70 [ 6.455323] do_mem_abort+0x3c/0x98 [ 6.462098] el1_da+0x20/0x94 [ 6.468330] __arch_copy_to_user+0x1c0/0x220 [ 6.475823] copy_page_to_iter+0xd0/0x300 [ 6.482990] generic_file_read_iter+0x300/0x8a0 [ 6.490618] blkdev_read_iter+0x38/0x48 [ 6.497514] new_sync_read+0xe0/0x140 [ 6.504193] __vfs_read+0x2c/0x38 [ 6.510469] vfs_read+0x90/0x170 [ 6.516587] ksys_read+0x64/0xe8 [ 6.522614] __arm64_sys_read+0x18/0x20 [ 6.529189] el0_svc_common.constprop.0+0x58/0xf0 [ 6.536643] el0_svc_handler+0x20/0x78 [ 6.543105] el0_svc+0x8/0xc [ 6.548708] Code: 2a154035 17ffffac a9025bb5 f9001bb7 (d4210000) [ 6.557632] ---[ end trace 8beba6d2a83d9491 ]---cutting both lines
hdmi.audio=EDID:0
disp.screen0_output_mode=1280x720p60
the board can boot without problems, with black screen of course...