sorry , it is config_logo
please add it back. Our logo is not from kernel. Even removing that does not make any difference to the logo.
Please only disable framebuffer console and share the dmesg.
my config file :
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE is not set
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
dmesg:
0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.253-tegra (dpt@18-04) (gcc version 7.5.0 (Linaro GCC 7.5-2019.12) ) #5 SMP PREEMPT Fri Mar 24 17:15:07 CST 2023
[ 0.000000] Boot CPU: AArch64 Processor [411fd071]
[ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 48,
[ 0.000000] OF: fdt: - 80000000 , 3f800000
[ 0.000000] OF: fdt: - bfa00000 , 3fe00000
[ 0.000000] OF: fdt: - ffa00000 , 600000
[ 0.000000] Found tegra_fbmem: 00800000@92ca9000
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options ‘’)
[ 0.000000] bootconsole [uart8250] enabled
[ 0.000000] OF: reserved mem: initialized node iram-carveout, compatible id nvidia,iram-carveout
[ 0.000000] OF: reserved mem: initialized node ramoops_carveout, compatible id nvidia,ramoops
[ 0.000000] cma: Reserved 64 MiB at 0x00000000fb800000
[ 0.000000] On node 0 totalpages: 522752
[ 0.000000] DMA zone: 8192 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 522752 pages, LIFO batch:31
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.0 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] percpu: Embedded 24 pages/cpu s57624 r8192 d32488 u98304
[ 0.000000] pcpu-alloc: s57624 r8192 d32488 u98304 alloc=24*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] CPU features: enabling workaround for ARM erratum 832075
[ 0.000000] Speculative Store Bypass Disable mitigation not required
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 514560
[ 0.000000] Kernel command line: tegraid=21.1.2.0.0 ddr_die=2048M@2048M section=256M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 core_edp_mv=1125 core_edp_ma=4000 gpt tegra_fbmem=0x800000@0x92ca9000 is_hdmi_initialised=1 earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 fbcon=map:0 net.ifnames=0 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 fbcon=map:0 net.ifnames=0
please remove quiet from extlinux.conf and share log again.
Also, attach it as a file… do not copy paste anything unless you want everyone just spending time in scrolling…
sorry. Let’s try another way. Please set the fbcon back. But change the fbcon=map:0 to fbcon=map:1
Incidentally, the text-mode logins are from getty running. You might find this of interest (you can ignore serial getty):
sudo grep -R 'getty' /etc/systemd/*
Although you could disable a getty service, or better yet remove “wanting” that service at certain run levels, consider instead the output of this:
cat /proc/cmdline
Note that there can be more than one “console=...” statement, and you don’t care about the ttyS0 (or other serial device) for the regular boot screen, but if you were to remove the “console=tty0”, then most boot content would no longer show up in the text terminal. It is possible though that a getty definition for either multi-user.target or graphical.target could still enable this later on via a “Wants” definition.
I would be careful about editing or removing anything in “/etc/systemd” unless you first know how it works.
Hi WayneWWW,
Set fbcon back and modify fbcon=map:1 in cmdline, the monitor doesn’t show anything.
But one more thing is that, after the device power up and login to system by ssh, then run the demo DRM appliction,.
During the debug, I found that the CRTC-Encoder-Connector pipeline had been already setup. Which system application(why) setup the pipeline when system is starting up?
Because My DRM application must control the display excludely , How can I stop that system application to setup the pipeline?