Sebastien Motala Posted October 29, 2023 Share Posted October 29, 2023 I recently make functionning the I2C-0 port on odroid M1 (thanks to usual user) see topic [odroid m1 i2c not detecting external device]. But I have another problem the tty1 display on the oled screen when I disconnect the HDMI. Where can i disabled this ? 0 Quote Link to comment Share on other sites More sharing options...
usual user Posted October 29, 2023 Share Posted October 29, 2023 I still have an idea for an experiment with your problem: - Blacklist the OLED display driver module so it get not autoloaded at system start I do it e.g. this way: echo blacklist ssd130x-i2c > /etc/modprobe.d/ssd130x-i2c-blacklist.conf But I don't know if it works the same way in an Armbian system. - Boot the system without the HDMI monitor connected - When the boot process is complete, i.e. all automatic graphical console device mappings are complete, modprobe explicit the OLED display driver module - Report if fbcon is no longer binding to the framebuffer device provided by the OLED driver If this works, it might serve as a workaround, because I'm not sure if the Armbian configuration framework can handle two separate graphic cards. But I'm happy to be taught better by an Armbian insider. Oh, by the way, this is not a specific ODROID-M1 problem nor is it special because the display driver uses the i2c interface. It is a general matter to support several grahic cards at the same time, it doesn't matter which interface they use to communicate. The same would happen, for example, if an additional graphics card is used, which is connected via USB adapter. This allows you to find solutions from anywhere and then learn how to configure them in Armbian for its automatisms. 0 Quote Link to comment Share on other sites More sharing options...
Sebastien Motala Posted October 29, 2023 Author Share Posted October 29, 2023 I solve my problem, I change my distribution from debian bookworm to ubuntu jammy. That's all. 0 Quote Link to comment Share on other sites More sharing options...
usual user Posted October 30, 2023 Share Posted October 30, 2023 8 hours ago, Sebastien Motala said: I change my distribution from debian bookworm to ubuntu jammy. This is also a valid way to confirm that the problem is a matter of configuration in the boot process. 8 hours ago, Sebastien Motala said: I solve my problem While this solution does not provide insight into the true cause, it is legitimate. Since Armbian doesn't change the basic structure of the base distribution used, but only improves the device support, the root cause isn't even Armbian's fault. The developed solution for the operation of the OLED, on the other hand, is exactly within the core competence of Armbian and should be integrated into the build system for general out-of-the-box use. This is exactly the contribution you can make to give something back for the contributions that other community members have contributed and that you can use for free. This is the only way the Armbian project can grow, there are already enough users who just take and expect that their special requests will be implemented without their involvement free of charge. In a community driven project, you pay through your own contributions. Contributing nothing is a good prerequisite for being ignored in the future if you ask for support again. 0 Quote Link to comment Share on other sites More sharing options...
Sebastien Motala Posted October 30, 2023 Author Share Posted October 30, 2023 It was a short-lived satisfaction, the problem resurfaced in the same way after the reboot. # find / -name console /sys/class/tty/console /sys/devices/platform/fe5c0000.i2c/i2c-0/0-003c/graphics/fb0/console /sys/devices/platform/serial8250/tty/ttyS6/console /sys/devices/platform/serial8250/tty/ttyS4/console /sys/devices/platform/serial8250/tty/ttyS0/console /sys/devices/platform/serial8250/tty/ttyS7/console /sys/devices/platform/serial8250/tty/ttyS5/console /sys/devices/platform/serial8250/tty/ttyS3/console /sys/devices/platform/serial8250/tty/ttyS1/console /sys/devices/platform/fe660000.serial/tty/ttyS2/console /sys/devices/virtual/tty/console /dev/console How do i remove the line '/sys/devices/platform/fe5c0000.i2c/i2c-0/0-003c/graphics/fb0/console' which is my OLED display device ? For Usual User this is the result of lsmod without HDMI connected, there is unfortunately nothing about i2c in the modules. # lsmod Module Size Used by sunrpc 364544 1 crct10dif_ce 12288 1 polyval_ce 12288 0 snd_soc_simple_card 20480 0 btusb 69632 0 snd_soc_rk817 40960 1 snd_soc_hdmi_codec 20480 1 snd_soc_rockchip_i2s_tdm 32768 4 btrtl 32768 1 btusb 8821cu 1875968 0 snd_soc_simple_card_utils 32768 1 snd_soc_simple_card btintel 53248 1 btusb polyval_generic 12288 1 polyval_ce hantro_vpu 262144 0 snd_soc_core 270336 5 snd_soc_rockchip_i2s_tdm,snd_soc_hdmi_codec,snd_soc_rk817,snd_soc_simple_card_utils,snd_soc_simple_card btbcm 24576 1 btusb rockchip_rga 24576 0 v4l2_vp9 24576 1 hantro_vpu btmtk 12288 1 btusb snd_compress 28672 1 snd_soc_core ssd1307fb 20480 1 gpio_ir_recv 12288 0 rc_core 57344 2 gpio_ir_recv cfg80211 458752 1 8821cu v4l2_h264 16384 1 hantro_vpu ac97_bus 12288 1 snd_soc_core videobuf2_dma_contig 24576 1 hantro_vpu snd_pcm_dmaengine 16384 1 snd_soc_core bluetooth 819200 6 btrtl,btmtk,btintel,btbcm,btusb snd_pcm 143360 5 snd_soc_hdmi_codec,snd_compress,snd_soc_simple_card_utils,snd_soc_core,snd_pcm_dmaengine v4l2_mem2mem 40960 2 hantro_vpu,rockchip_rga videobuf2_dma_sg 16384 1 rockchip_rga snd_timer 40960 1 snd_pcm rfkill 28672 4 bluetooth,cfg80211 videobuf2_memops 16384 2 videobuf2_dma_contig,videobuf2_dma_sg snd 106496 5 snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm joydev 24576 0 videobuf2_v4l2 32768 3 hantro_vpu,rockchip_rga,v4l2_mem2mem soundcore 12288 1 snd rk817_charger 20480 0 videobuf2_common 57344 7 videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_dma_sg,v4l2_mem2mem,videobuf2_memops lz4hc 12288 0 lz4 12288 0 zram 28672 3 binfmt_misc 24576 1 sch_fq_codel 16384 6 ip_tables 32768 0 x_tables 57344 1 ip_tables autofs4 45056 2 dw_hdmi_i2s_audio 12288 0 dw_hdmi_cec 12288 0 rockchipdrm 176128 0 dw_mipi_dsi 16384 1 rockchipdrm dw_hdmi 53248 2 dw_hdmi_i2s_audio,rockchipdrm panfrost 77824 0 analogix_dp 45056 1 rockchipdrm drm_display_helper 172032 3 rockchipdrm,dw_hdmi,analogix_dp gpu_sched 36864 1 panfrost display_connector 16384 0 spi_rockchip_sfc 16384 0 sdhci_of_dwcmshc 16384 0 cec 77824 3 dw_hdmi_cec,drm_display_helper,dw_hdmi drm_shmem_helper 20480 1 panfrost drm_dma_helper 20480 1 rockchipdrm drm_kms_helper 208896 8 dw_mipi_dsi,drm_dma_helper,display_connector,drm_display_helper,rockchipdrm,dw_hdmi,analogix_dp drm 651264 12 gpu_sched,drm_kms_helper,dw_mipi_dsi,drm_dma_helper,display_connector,drm_shmem_helper,drm_display_helper,rockchipdrm,dw_hdmi,panfrost,analogix_dp ahci_dwc 12288 0 0 Quote Link to comment Share on other sites More sharing options...
Sebastien Motala Posted October 30, 2023 Author Share Posted October 30, 2023 I finally solve my problem, there was a module called "ssd1307sd" who use the i2c-0 for displaying tty1 (framebuffer). I blacklist it . echo blacklist ssd1307fb > /etc/modprobe.d/ssd1307fb-blacklist.conf And now all is ok. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.