Igor
-
Posts
13648 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
Two things are important here:
1. You need to set edid=0
2. When you save u-boot environment, you need to issue reset to boot u-boot into new setting.
Works for me.
-
2 minutes ago, Hannes Worst said:
HDMI->VGA converters don't work properly with Armbian on H3 boards I noticed. I never managed to use Armbian with these converters, I'm sorry to say.
Months ago, my primary testing tool become old 19" VGA Philips monitor with 1280x1024 and where I (must) use those converters. I have two different (possible the same?) and both working fine on everything I throw at them. So far I haven't found a glitch, while it's possible that exists at certain converters. -
This way it works with 720p or whatever less than 1080p. There kernel logo doesn't want to show.
Good on 1280x1024 or 720pSpoiler[ 3.336551] simple-framebuffer 7fb00000.framebuffer: framebuffer at 0x7fb00000, 0x500000 bytes, mapped to 0xf0900000 [ 3.336562] simple-framebuffer 7fb00000.framebuffer: format=x8r8g8b8, mode=1280x1024x32, linelength=5120 [ 3.363471] Console: switching to colour frame buffer device 160x64 [ 3.365113] simple-framebuffer 7fb00000.framebuffer: fb0: simplefb registered
Broken on 1080p:Spoiler[ 3.337435] simple-framebuffer 7f817000.framebuffer: framebuffer at 0x7f817000, 0x7e9000 bytes, mapped to 0xf0900000 [ 3.337447] simple-framebuffer 7f817000.framebuffer: format=x8r8g8b8, mode=1920x1080x32, linelength=7680 [ 3.379192] fbcon_init: disable boot-logo (boot-logo bigger than screen). [ 3.379203] Console: switching to colour frame buffer device 240x67 [ 3.420003] simple-framebuffer 7f817000.framebuffer: fb0: simplefb registered
Relevant patch (without 320x200 bitmap.):
Spoilerdiff --git a/drivers/video/logo/Kconfig b/drivers/video/logo/Kconfig --- a/drivers/video/logo/Kconfig +++ b/drivers/video/logo/Kconfig @@ -27,6 +27,10 @@ config LOGO_LINUX_CLUT224 bool "Standard 224-color Linux logo" default y +config LOGO_ARMBIAN_CLUT224 + bool "Standard 224-color Armbian logo" + default y + config LOGO_BLACKFIN_VGA16 bool "16-colour Blackfin Processor Linux logo" depends on BLACKFIN diff --git a/drivers/video/logo/Makefile b/drivers/video/logo/Makefile --- a/drivers/video/logo/Makefile +++ b/drivers/video/logo/Makefile @@ -15,6 +15,7 @@ obj-$(CONFIG_LOGO_SUPERH_MONO) += logo_superh_mono.o obj-$(CONFIG_LOGO_SUPERH_VGA16) += logo_superh_vga16.o obj-$(CONFIG_LOGO_SUPERH_CLUT224) += logo_superh_clut224.o obj-$(CONFIG_LOGO_M32R_CLUT224) += logo_m32r_clut224.o +obj-$(CONFIG_LOGO_ARMBIAN_CLUT224) += logo_armbian_clut224.o obj-$(CONFIG_SPU_BASE) += logo_spe_clut224.o diff --git a/drivers/video/logo/logo.c b/drivers/video/logo/logo.c --- a/drivers/video/logo/logo.c +++ b/drivers/video/logo/logo.c @@ -1,4 +1,3 @@ - /* * Linux logo to be displayed on boot * @@ -36,6 +35,8 @@ static int __init fb_logo_late_init(void) late_initcall(fb_logo_late_init); +extern const struct linux_logo logo_armbian_clut224; + /* logo's are marked __initdata. Use __ref to tell * modpost that it is intended that this function uses data * marked __initdata. @@ -111,6 +112,10 @@ const struct linux_logo * __ref fb_find_logo(int depth) /* M32R Linux logo */ logo = &logo_m32r_clut224; #endif +#ifdef CONFIG_LOGO_ARMBIAN_CLUT224 + /* Armadeus Linux logo */ + logo = &logo_armbian_clut224; +#endif } return logo; } diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c --- a/drivers/video/fbdev/core/fbmem.c +++ b/drivers/video/fbdev/core/fbmem.c @@ -487,7 +487,7 @@ static int fb_show_logo_line(struct fb_info *info, int rotate, } if (fb_logo.depth <= 4) { - logo_new = kmalloc(logo->width * logo->height, GFP_KERNEL); + logo_new = kmalloc(info->var.xres * info->var.yres, GFP_KERNEL); if (logo_new == NULL) { kfree(palette); if (saved_pseudo_palette) @@ -498,8 +498,9 @@ static int fb_show_logo_line(struct fb_info *info, int rotate, fb_set_logo(info, logo, logo_new, fb_logo.depth); } - image.dx = 0; - image.dy = y; + image.dx = (info->var.xres - logo->width) / 2; + image.dy = (info->var.yres - logo->height) / 2; + image.width = logo->width; image.height = logo->height; @@ -657,15 +658,14 @@ int fb_prepare_logo(struct fb_info *info, int rotate) } } - return fb_prepare_extra_logos(info, fb_logo.logo->height, yres); + return fb_prepare_extra_logos(info, info->var.yres, yres); } int fb_show_logo(struct fb_info *info, int rotate) { int y; - y = fb_show_logo_line(info, rotate, fb_logo.logo, 0, - num_online_cpus()); + y = fb_show_logo_line(info, rotate, fb_logo.logo, 0, 1); y = fb_show_extra_logos(info, y, rotate); return y;
I can't see what I did wrong.
-
https://github.com/igorpecovnik/lib/commit/0b7676e527350d8cd454eb638869179d80c23c4c
Working at i2ex and v2
Thanks for the hint @zador.blood.stained
Log:This is filling logs on HB2, have to solve once:
Spoiler[ 228.319445] mmc1: Timeout waiting for hardware cmd interrupt. [ 228.323212] sdhci: =========== REGISTER DUMP (mmc1)=========== [ 228.326936] sdhci: Sys addr: 0x00000000 | Version: 0x00000002 [ 228.330707] sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001 [ 228.334468] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000 [ 228.338217] sdhci: Present: 0x007d8009 | Host ctl: 0x00000001 [ 228.341963] sdhci: Power: 0x00000000 | Blk gap: 0x00000080 [ 228.345716] sdhci: Wake-up: 0x00000008 | Clock: 0x000020af [ 228.349467] sdhci: Timeout: 0x00000080 | Int stat: 0x00000000 [ 228.353205] sdhci: Int enab: 0x007f1003 | Sig enab: 0x007f1003 [ 228.356949] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 [ 228.360694] sdhci: Caps: 0x07eb0000 | Caps_1: 0x0000a007 [ 228.364436] sdhci: Cmd: 0x0000371a | Max curr: 0x00ffffff [ 228.368156] sdhci: Host ctl2: 0x00000000 [ 228.371832] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000 [ 228.375543] sdhci: ===========================================
-
BT is USB, Wifi pci, ok.
Can you provide full logs, preferable:armbianmonitor -uThanks.
-
OMG. I think I'll just burn this board
With actual fire. 
-
-
AFAIK HB does not support Message signaled Interrupts.
I'll try to add this the rest to next update.
-
I just (again) wasted two hours to remember that any of those kernels needs a lot of code cleaning and fixing than "just" USB3. When this is done, than it would be possible to start debugging without wasting hours / days.
About year ago I was approached by Allo, when they were trying to design their own board around S500 (Sparky). They were talking about mainlining (wishes) or bringing things at least to kernel 4.4, but I guess they abandon the idea due to whatever reason. There was lots of discussion going on and after my second reminder, that they need to hire and pay for my time, if they want me involved into their activities, I tuned myself out. They didn't listen what I was trying to tell them anyway.
-
If you were editing settings while transmission was running it's normal, than it doesn't work.
-
You said settings are not saved ... one thing is with transmission - you have to disable daemon when you edit config file otherwise changes are not saved. If low level things are working fine, than this is a general issue.
-
I have no idea what can be wrong. You can try to force video mode in u-boot, perhaps some other than detected one. That's about all what I can come up. It's a bit tricky but doable also without serial console:
https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output
-
Did you enable this ttyS2 in board configuration? Which board do you use and which kernel do you use?
-
41 minutes ago, IgorS said:
On mainline image there is not signal on HDMI
It happened to me few times but it worked after soft reboot. -
It looks like one of the most common problems. Bad SD card.
-
55 minutes ago, IgorS said:
Do I miss something?
Yes. Mainline kernel is still in development and come without end user support. Currently there are problems with screen detection / video driver. It used to work fine, but currently it's just broken ... dunno why exactly, but AFAIK @jernej is working on this. "tomorrow" this will be fixed and some other problem might jump out but we are getting close. For certain scenarios is o.k. for some time.Even with fixed video, there are other limitations on new kernel - no video or 3D acceleration.
-
21 minutes ago, cu6apum said:
If there's a dedicated h.264 (or whatever) player capable of using hw acceleration
yes, use our legacy xenial desktop build.
https://forum.armbian.com/index.php?/topic/2218-cubietruck-multimedia-youtube/#comment-16773
-
On quick comparison there are few minor differences - LEDs are wired differently, eMMC section is useless but generally it should work with MiQi dtb. Have you try?
If it works, we only need to create a patch to create this file. Put our tools into "create patches" and when prompted, create a rk3288-miniarm.dts file with adjusted LED gpio and removed eMMC. Than push resulted patch (when tested) to patches/kernel/rockchip-dev
-
-
-
-
18 minutes ago, sirob said:
What can I do now with this RAW image ?
Delete. It was not done properly. I just update two videos of compilation process. Take a look how it should look like. -
1 hour ago, zador.blood.stained said:
Can "status updates" or whatever it is on profile pages be disabled? For some reason people think it's a good idea to use those for technical support.
Disabled. -
This beta repository does not have archive. It's populated only with latest versions / rebuild every night and therefore you need to issue apt update right before upgrading. This will rebuild packages index and you will be able to issue upgrade.
OrangePi plus 2E mainline kernel
in Allwinner sunxi
Posted
Well, we erase environment on install by purpose, since problems might occur when upgrading from some very old version. With hack - add commands to store environment into your boot script, the same as you typo into u-boot console (without reset). This way your settings will be saved to your environment on each boot.