ImmortanJoe
-
Posts
24 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by ImmortanJoe
-
-
Yesss... Nighties. Going to try the stretch one out today. My only devices are ARM based so I can't build from source.
That was the one good thing about the Sunxi source. With some script tweaking I could build with an ARM host.
Has anyone else found the 8GB eMMC to be a little touchy, especially during boot? Not sure if it's hardware or Sunxi kernel related.
-
I don't know the usual method for rebooting the Allwinner chipsets in Linux. I know the H3 had a register for it, but could also be reset by configuring the mode of the watchdog timer to reset, setting the WDT and letting it trip. Could that work in H6?
-
5 hours ago, lanefu said:
Not for Opi3... defective by design.. http://linux-sunxi.org/H6#Errata
So that's what is wrong with it. Strange implementation coupled with difficulties doing some things with the Linux framework.
Am I reading it correctly that the PCIe controller has either a banked interface or a potentially rolling window? Hm. Besides odd setup, DMA transactions would still function normally, right?
-
Is it within the scope of Armbian to attempt support for the MiniPCIe port with the mainline kernel? I didn't give it much thought until I remembered hat there are MiniPCIe to SATA adapters.
My bandwidth and time are too low to have been much use for the early stages sorry. Someone else had always tried the newest iteration before I'd finished downloading it.
-
Been meaning to say this. The OPi3 seems to deafen nearby wireless devices when running the legacy kernel. It disrupts other WiFi devices, BT and my Logitech keyboard and mouse. Re Logitech dongle, if I put it on a long USB extension cable it works.
My guess is that WiFi is outputting at maximum all the time, but it is just a guess.
-
Krachlatte, I hope you don't mind. I'm putting a link to 0.09 in my post.
https://github.com/krachlatte/armbian-orangepi3/releases/tag/v0.09
-
I had the same result as gnjack.
-
7 hours ago, jamespo said:
How did you get jessie installed on the eMMC?
I'm phone posting so I don't have the info in front of me. Just roughly what I did was:
Download Debian Jessie Desktop for OPi3 from the OPi download section. Use the Google drive link there.
Before closing Drive, find the PDF manual. The website link points to the wrong manual.
IIRC the eMMC flashing script name is in the manual. I couldn't find it anywhere else beforehand.
Run the script and let the magic happen.
There are more steps beforehand but the magic incantation for installation is in the manual.
-
Hm. My earlier reply didn't stick. Which logs, or parts of them would you like to see?
I just started downloading it so it'll be a while.
-
Reimaged the MicroSD again. This time it worked.
-
I haven't reimaged the MicroSD yet. It still has the first attempt on it. My OPi3 has Debian Jessie on the eMMC. There's also a SATA HDD plugged in to one of the USB3.0 ports currently, but results were the same without it.
I did go and grab the UART output for a boot with and without the Armbian SD in.
Here's the early boot results. I'm a little perplexed.
SD card in. Trying to boot Armbian:
Spoiler[176]HELLO! BOOT0 is starting! [179]boot0 commit : 500e56f3b0c9ecec6649770cc5c5fa6d91488d56 [198]PMU: AXP806 [202]set pll start [205]set pll end [206]rtc[0] value = 0x00000000 [209]rtc[1] value = 0x00000000 [212]rtc[2] value = 0x00000000 [215]rtc[3] value = 0x00000000 [219]rtc[4] value = 0x00000000 [222]rtc[5] value = 0x00000000 [225]DRAM VERSION IS V2_5 [227]PMU:Set DDR Vol 1200mV OK. [230]PMU:Set DDR Vol 1200mV OK. [249]DRAM CLK =744 MHZ [252]DRAM Type =7 (3:DDR3,4:DDR4,6:LPDDR2,7:LPDDR3) [257]DRAM zq value: 003b3bfb [264]IPRD=006c006b--PGCR0=00000f5d--PLL=b0003d00 [268]DRAM SIZE =2048 M,para1 = 000030fa,para2 = 08001000 [280]DRAM simple test OK. [282]dram size =2048 [285]card no is 0 [287]sdcard 0 line count 4 [290][mmc]: mmc driver ver 2017-03-14 13:56 [294][mmc]: sdc0 spd mode error, 2 [297][mmc]: mmc 0 bias 00000000 [306][mmc]: Wrong media type 0x00000000 [310][mmc]: ***Try SD card 0*** [329][mmc]: HSSDR52/SDR25 4 bit [332][mmc]: 50000000 Hz [335][mmc]: 30436 MB [337][mmc]: ***SD/MMC 0 init OK!!!*** [481]Loading boot-pkg Succeed(index=0). [485]Entry_name = u-boot [501]Entry_name = parameter [504]Entry_name = monitor [508]Entry_name = scp [517]set arisc reset to de-assert state [521]Entry_name = soc-cfg [525]Entry_name = dtb [528]Entry_name = board-cfg [532]Entry_name = board-fex [535]Entry_name = esm-img [539]Ready to disable icache. [542]Jump to secend Boot. INFO: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):7408d88 NOTICE: BL3-1: Built : 20:42:28, Aug 29 2017 NOTICE: BL3-1 commit: 7408d88f80cb14038350a8f55a280fd0c4caf626 INFO: BL3-1: Initializing runtime services ERROR: Error initializing runtime service tspd_fast INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x4a000000 INFO: BL3-1: Next image spsr = 0x1d3 U-Boot 2014.07-g43c0e2c-dirty (Jan 23 2019 - 16:40:46) Allwinner Technology uboot commit : 43c0e2c9b598bd93aa221e2a5ecec3c55dcfda6e
And with the SD card out, just booting Jessie:
Spoiler[136]HELLO! BOOT0 is starting! [139]boot0 commit : 500e56f3b0c9ecec6649770cc5c5fa6d91488d56 [157]PMU: AXP806 [161]set pll start [164]set pll end [166]rtc[0] value = 0x00000000 [169]rtc[1] value = 0x00000000 [172]rtc[2] value = 0x00000000 [175]rtc[3] value = 0x00000000 [178]rtc[4] value = 0x00000000 [181]rtc[5] value = 0x00000000 [184]DRAM VERSION IS V2_5 [187]PMU:Set DDR Vol 1200mV OK. [190]DRAM CLK =744 MHZ [192]DRAM Type =7 (3:DDR3,4:DDR4,6:LPDDR2,7:LPDDR3) [197]DRAM zq value: 003b3bfb [204]IPRD=006c006b--PGCR0=00000f5d--PLL=b0003d00 [209]DRAM SIZE =2048 M,para1 = 000030fa,para2 = 08001000 [220]DRAM simple test OK. [222]dram size =2048 [225]card no is 2 [227]sdcard 2 line count 8 [230][mmc]: mmc driver ver 2017-03-14 13:56 [234][mmc]: mmc 2 bias 00000004 [243][mmc]: ***Try MMC card 2*** [255][mmc]: MMC 5.1 [257][mmc]: HSDDR52/DDR50 8 bit [260][mmc]: 50000000 Hz [263][mmc]: 7456 MB [265][mmc]: ***SD/MMC 2 init OK!!!*** [354]Loading boot-pkg Succeed(index=0). [357]Entry_name = u-boot [374]Entry_name = parameter [377]Entry_name = monitor [381]Entry_name = scp [390]set arisc reset to de-assert state [394]Entry_name = soc-cfg [398]Entry_name = dtb [401]Entry_name = board-cfg [405]Entry_name = board-fex [408]Entry_name = esm-img [411]Ready to disable icache. [414]0xffffffff 0xffffffff [417]0xff1fffff 0xffffffff [420]0xff0d19ff 0xffffffff [422]0x1a1affff 0xffffff2b [425]0x0e20ffff 0xffffffff [428]0x1c1dffff 0xffffffff [430]Jump to secend Boot. INFO: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):7408d88 NOTICE: BL3-1: Built : 20:42:28, Aug 29 2017 NOTICE: BL3-1 commit: 7408d88f80cb14038350a8f55a280fd0c4caf626 INFO: BL3-1: Initializing runtime services ERROR: Error initializing runtime service tspd_fast INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x4a000000 INFO: BL3-1: Next image spsr = 0x1d3 U-Boot 2014.07-g43c0e2c-dirty (Jan 22 2019 - 17:09:55) Allwinner Technology uboot commit : 43c0e2c9b598bd93aa221e2a5ecec3c55dcfda6e
The Armbian MicroSD is doing something, but I' not totally sure what. Either way, it just boots into Debian Jessie.
-
As always the question is what you want to do with it
I'm typing this on a Pinebook which is fast enough for what I use it for. My Orange Pi Zero is fast enough for file and network services that I use it for. My RPi Zero is fast enough for running RISC OS. It's all down to your use case.
-
14 hours ago, krachlatte said:
could you try windisk imager 32, if you are using windows at all ?
No sorry. I'm 100% ARM based these days. Mostly Armbian and RISC OS on my devices.
I'm sure my usage of dd was correct as I use it regularly. However I am painfully aware of a bug in something which otherwise silently causes a register dump to dmesg which can cause corruption issues. I wrote the image remotely nohup via ssh and didn't think to check for success beyond the nohup output file afterwards.
I will see if I can try again today. I don't have much direct access right now.
7 hours ago, filimonic said:2) "reboot" hangs the device.
Don't concern yourself too much with that right now. I found that the Sunxi OrangePi Jessie Desktop image falls over into some kind of failure register dump mode after reboot. Other Orange Pi devices also seem to have reboot issues so it's hard to say yet whether it's a design failure or a software bug.
Usually wit any Orange Pi device I have, I apply the 10 second power cycle rule.
-
No. I put it on MicroSD. This has highest boot priority. It just went straight through to booting from eMMC. The contents of the MicroSD seemed to be intact. I'll have a better look at the serial output later.
-
This image should just boot from MicroSD once written with dd, right? The OPi3 is just skipping past it to the eMMC. The contents of the partitions appear to be intact.
-
I have an Orange Pi 3. I don't mind trying images if it'll help.
-
18 minutes ago, zador.blood.stained said:
Not on Armbian images since it is currently possible only on legacy kernels.
That's what I thought. Shame the legacy kernel's video is so badly broken it can't display anything on most monitors.
I did see libvdpau-sunxi1 in the apt repository and installed it but it doesn't seem to do anything useful. Thanks for the confirmation. I wasn't sure if my install had broken over time with all the updates or it wasn't supported.
-
is vdpau supposed to work or exist for the PC2? I've seen conflicting reports. My Armbian doesn't seem to have any trace of it.
-
Something broke in USB in the last couple of days. I just updated to the nightly kernel etc. and the hub no longer worked.
23.600145] usb 5-1.1: device descriptor read/64, error -110 [ 23.792099] usb 5-1.1: new full-speed USB device number 4 using ohci-platform [ 28.976623] usb 5-1.1: device descriptor read/64, error -110 [ 41.351812] usb 5-1-port1: cannot reset (err = -62) [ 41.357968] usb 5-1-port1: cannot reset (err = -62) [ 41.363228] usb 5-1: USB disconnect, device number 2 [ 41.363800] usb 5-1-port1: cannot reset (err = -62) [ 45.001488] usb 5-1: new low-speed USB device number 7 using ohci-platform [ 45.185479] usb 5-1: device descriptor read/64, error -62 [ 45.481423] usb 5-1: device descriptor read/64, error -62 [ 45.773439] usb 5-1: new low-speed USB device number 8 using ohci-platform [ 45.957500] usb 5-1: device descriptor read/64, error -62 [ 46.253453] usb 5-1: device descriptor read/64, error -62 [ 46.545463] usb 5-1: new low-speed USB device number 9 using ohci-platform [ 46.961541] usb 5-1: device not accepting address 9, error -62 [ 47.145514] usb 5-1: new low-speed USB device number 10 using ohci-platform [ 47.561536] usb 5-1: device not accepting address 10, error -62 [ 47.567592] usb usb5-port1: unable to enumerate USB device
The mouse and keyboard worked when directly plugged in.
-
14 hours ago, hojnikb said:
PC2 is actually more power hungry than PC.
That's interesting. It seems more stable at least so I'm not complaining.
I know I said it before but the Armbian mainline kernel is advancing so well. Congratulations to the people working on it. It's a great achievement. The improvements are really showing.
I wish I could help but I can't because of reasons involving what I want to do with the OPi PC.
The OPi PC2 works well as a headless build server. However it really needs swap space. I've found when doing big builds using GCC it tends to blow it's RAM budget by 100 - 150MB. I don't know what it swaps out but it doesn't seem to be used, because it stays in swap after the build has finished.
-
The PC2 has its good points. The mainline kernel is improving constantly. There are still some really weird bugs with xorg, terminal display, and something with memory management, but beyond that it's a solid performer. It seems to have less issues with USB device stability than PC mainline kernel, and although I haven't empirically checked it seems to have lower power consumption than the PC. I say this because The PC or peripherals can get upset, however when I have the exact same peripherals and PSU plugged into the PC2 it's fine.
I use my PC2 with Armbian mainline as an aarch64 build server for various projects. Something which my RPi3 was meant to be for when I bought it shortly after release, yet aarch64 is only just starting to appear...
Sometimes I use the PC2 as a desktop but the memory use is problematic. It works well serving X apps remotely via ssh though.
The official Ubuntu legacy image for PC2 is a train wreck and should be avoided. A DIY distribution of Debian based off the source is a headache. I spent ages editing the scripts to make something that would build. A couple of days later the hard drive crashed. I only just re downloaded the source for the most recent fork. So now I have to start again.
-
Hi. I signed up because I saw this thread.
Not sure of the exact model but I've got an Acer monitor with 1920x1080 native resolution. It works with h3disp at lower resolutions but not with 1080p at any refresh rate. This is via a standard passive HDMI to DVI video adaptor. Various Raspberry Pi models can drive the monitor at 1920x1080 without issue.
I tried 1080i. My monitor doesn't seem to understand interlaced and became a digital headache generator.
What I have noticed on both my 1600x1200 LCD and 1920x1080 LCD is that the horizontal frequency is 45kHz at the lower resolutions. The 1600x1200 monitor seemed to make a point of telling me the HSync, which does seem a bit high. I have to wonder what the rate is for 1080p
Good catch on the pll_video. I'll have to see if dropping the value makes it work next chance I get.
e: I just removed a pile of pll_video entries and left 297. 1080p60 works fine now and has an HSync of 68kHz.
What seems to be happening is h3disp is failing to remove old pll_video entries when the mode is changed. This is causing the wrong settings to be used.
Now I can play around with the Orange Pi PC in the native resolution for one of the monitors at least.
I have to ask. It appears the kernel has a heap of mode settings pre-defined in some enums. Why isn't a method available for entering all the values manually via U-Boot or during runtime in Linux? Or is there and I haven't found it.
Orangepi 3 h6 allwiner chip
in Allwinner sunxi
Posted
The Debian Jessie desktop image on the Orange Pi website can be upgraded to Stretch. Wifi partially breaks though. It can see the access points and show signal strength, but nothing happens when trying to connect. Screen resolution seems unchangable. It seems to be a plain Debian. Ie not messed with like some Orange Pi images. So if you really desperately need the legacy kernel that could work. Otherwise, the Armbian release of Stretch is already a nicer option IMHO.
xrdp server seems to have problems. Has anyone got it working properly on the Armbian nightly yet? I wanted to see if there was a noticeable performance difference between the "Legacy" Debian Stretch and Mainline Armbian Stretch through RDP.
Was Wifi meant to be working on the new nightlies? It doesn't seem to be there. It doesn't bother me.
edit: The uptime part of the ssh login script seems to be incorrect. It's grabbing the wrong value.