lucky62

  • Posts

    80
  • Joined

  • Last visited

2 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

lucky62's Achievements

  1. My box x88 pro 10 is booting from USB 3.0 HDD but only from USB 2.0 port. USB 3.0 is not supported by U-boot, I think...
  2. I understand, I have no problems with connection. Just the messages are repeating after each 6 seconds.. So it is annoying and due to a rotating buffer older important messages are lost... Nobody else has this problem?...
  3. but wifi is working normally... Box is connected to the wifi and it is accessible.(I am connected via SSH). I am wondering if docker or home-assistant changed something... If I remember these messages were not here before docker / HA installation.
  4. Hello, can anyone say what is the cause of these messages and how to get rid of it? Sep 1 08:40:50 hassio kernel: [ 1026.900395] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (72) Sep 1 08:40:56 hassio kernel: [ 1032.846542] ieee80211 phy0: brcmf_fweh_call_event_handler: no interface object Sep 1 08:40:56 hassio kernel: [ 1032.846581] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (72) Sep 1 08:41:02 hassio kernel: [ 1038.785176] ieee80211 phy0: brcmf_fweh_call_event_handler: no interface object Sep 1 08:41:02 hassio kernel: [ 1038.785214] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (72) Sep 1 08:41:02 hassio kernel: [ 1038.786917] ieee80211 phy0: brcmf_fweh_call_event_handler: no interface object Sep 1 08:41:02 hassio kernel: [ 1038.786939] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (72) Sep 1 08:41:08 hassio kernel: [ 1044.726928] ieee80211 phy0: brcmf_fweh_call_event_handler: no interface object Sep 1 08:41:08 hassio kernel: [ 1044.726965] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (72) Sep 1 08:41:08 hassio kernel: [ 1044.729080] ieee80211 phy0: brcmf_fweh_call_event_handler: no interface object Sep 1 08:41:08 hassio kernel: [ 1044.729125] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (72) Sep 1 08:41:14 hassio kernel: [ 1050.654195] ieee80211 phy0: brcmf_fweh_call_event_handler: no interface object Sep 1 08:41:14 hassio kernel: [ 1050.654226] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (72)
  5. hi @jock, thanks for the reply. I will go through the way recommended by you. I think the possibility to HDMI disable/enable depends on driver.
  6. I see this in the syslog when connected via ssh, but after reboot these messages are not in any log file.. It means that reboot was unexpected... :-( Aug 30 18:17:12 hassio NetworkManager[745]: <info> [1630340232.0227] manager: sleep: sleep requested (sleeping: no enabled: yes) Aug 30 18:17:12 hassio NetworkManager[745]: <info> [1630340232.0234] device (eth0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Aug 30 18:17:12 hassio NetworkManager[745]: <info> [1630340232.0394] manager: NetworkManager state is now ASLEEP Aug 30 18:17:12 hassio systemd[1]: Reached target Sleep. Aug 30 18:17:12 hassio systemd[1]: Starting Suspend... Aug 30 18:17:12 hassio kernel: [ 1162.689452] PM: suspend entry (deep) Aug 30 18:17:12 hassio systemd-sleep[6973]: Suspending system... Aug 30 18:17:12 hassio kernel: [ 1162.703472] Filesystems sync: 0.013 seconds
  7. Hello again, I would like to change the behavior of my IR remote POWER button. Currently the system goes down when button pressed. I need to keep the system running, just I would like to switch off the HDMI output and probably some other parts (audio?..) I changed the KEY_POWER to KEY_SUSPEND in the rc keymap, but now the system is rebooting... Aug 30 17:50:17 hassio systemd[1]: Starting Show bootsplash on system halt, power off, reboot, or kexec... Aug 30 17:50:17 hassio systemd[1]: Stopped target Timers. Aug 30 17:50:17 hassio systemd[1]: Stopping Setup zram based device zram2... Aug 30 17:50:17 hassio systemd[1]: Stopping Manage, Install and Generate Color Profiles... Aug 30 17:50:17 hassio systemd[1]: Stopped target Graphical Interface. Aug 30 17:50:17 hassio systemd[1]: Stopping Disk Manager... Aug 30 17:50:17 hassio systemd[1]: man-db.timer: Succeeded. Aug 30 17:50:17 hassio systemd[1]: Stopped Daily man-db regeneration. Aug 30 17:50:17 hassio systemd[1]: Stopping Authorization Manager... Aug 30 17:50:17 hassio systemd[1]: Stopping Setup zram based device zram1... Aug 30 17:50:17 hassio systemd[1]: logrotate.timer: Succeeded. Aug 30 17:50:17 hassio systemd[1]: Stopped Daily rotation of log files. Aug 30 17:50:17 hassio systemd[1]: Stopped target Sound Card. Aug 30 17:50:17 hassio systemd[1]: Stopping Session 85 of user root. Aug 30 17:50:17 hassio systemd[1]: Stopped target Multi-User System. Aug 30 17:50:17 hassio ModemManager[717]: <info> Caught signal, shutting down... Aug 30 17:50:17 hassio systemd[1]: Stopping Modem Manager... Aug 30 17:50:17 hassio lircd[1173]: lircd-0.10.1[1173]: Notice: caught signal Aug 30 17:50:17 hassio chronyd[1064]: chronyd exiting Aug 30 17:50:17 hassio systemd[1]: Stopping LSB: Klipper daemon... Aug 30 17:50:17 hassio chronyd[1064]: Could not open temporary driftfile /var/lib/chrony/chrony.drift.tmp for writing Aug 30 17:50:17 hassio systemd[1]: Stopped target Login Prompts. Aug 30 17:50:17 hassio systemd[1]: Stopping Getty on tty1... Aug 30 17:50:17 hassio sh[12310]: /bin/sh: 1: echo: echo: I/O error Aug 30 17:50:17 hassio lircd-0.10.1[1173]: Notice: caught signal Aug 30 17:50:17 hassio systemd[1]: Stopping Serial Getty on ttyS2... Aug 30 17:50:17 hassio systemd[1]: Stopping chrony, an NTP client/server... Aug 30 17:50:17 hassio systemd[1]: Stopping OpenBSD Secure Shell server... Aug 30 17:50:17 hassio systemd[1]: sysstat.service: Succeeded. Aug 30 17:50:17 hassio systemd[1]: Stopped Resets System Activity Data Collector. Aug 30 17:50:17 hassio systemd[1]: Stopping Flexible IR remote input/output application support... Aug 30 17:50:49 hassio kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] ... boot continues ... Is some sleep mode supported? Or there is other way how to switch off some hardware?
  8. Hi @Huafu, there is not much more to share than what was already published in this thread... I was trying to compile kernel, but in the end I am using the kernel from @jock. Also I did nothing with HW acceleration... WiFi is working, just needs to be enabled by rk3318-config. IR is working also, just you need the toml file (attached) and register it - described here. Regarding the LCD, I compiled the driver from Arthur - without changes. For this you need to install kernel headers into box, download and unpack the driver sources, switch to the driver directory. In the MakeFile you need to change the path to the kernel - in my case it was: KERNELDIR = /lib/modules/5.10.37-rockchip64/build and you need to create the symlinks to the System.map in the driver directory and in the kernel directory: ln -sf /boot/System.map-$(uname -r) System.map # in the driver directory ln -sf /boot/System.map-$(uname -r) /lib/modules/$(uname -r)/build/System.map then compile and install: make make modules_install Finally you need DT overlay file - just make a copy from here and install it by armbian-add-overlay. DTS will be automatically compiled and installed. After reboot driver should be loaded. To work with it you need to start OpenVFDService. I am using the version compiled by @jock. Last point - I was not happy with cooling - box was very hot even when idle... So I ordered fan and regulator from Aliexpress, I did a big hole to the top cover and mounted together. Fan is powered from the adapter. No big current. Temperature sensor is glued to the heatsink: Soldering - thick wires are for fan (red = + positive). On the left side are the wires of serial interface: x88pro10.toml
  9. #define KEY_HP 211 Probably Horse Power?.... EDIT: idea is not to add more and more keys into the kernel, but allow the user-defined keys and clean the kernel code (keep only required and most commonly used keys).
  10. It's about the philosophy... Why these (for example) are in the kernel directly? #define KEY_FINANCE 219 #define KEY_SPORT 220 #define KEY_SHOP 221 For these I also need a userspace program... Why I need to map the physical key YouTube to something unclear/misleading (e.g. KEY_FN_13) when I simply need to start the YouTube?... :-) It will be much better to allow user defined keys...
  11. Thanks for explanation. So I understand that I must map my special keys to some keys defined in input_event_codes.h Looking into the file I see that there is a lot of defined keys which I will never have. But I cannot simply use the names on my remote... Current implementation was good when linux was used only on computers with more or less fixed set of keys on keyboard. But nowadays there is a lot of devices with very different functions (very different input devices) so it will be better to allow user defined keys beside fixed set of standard keys... My opinion...
  12. Hello UU, I followed you guide, I grabbed all the codes and have created the toml file, copied to the /etc/rc_keymaps and registered in /etc_rc_maps.cfg. It is working. But... My remote has the few special keys, like Youtube, Netflix, TV control keys. These are also in my toml file, but names are not recognized by driver. Seems that key names must be only from defined set. What are the allowed names? Second point not clear to me - how are the KEYs mapped to system/program actions? For example - I would like to open YouTube in the browser when I will press the YouTube KEY, how to do? Keys defined in my toml file (keys marked with * are not recognized): 0xdf06 = "KEY_OK" 0xdf1a = "KEY_UP" 0xdf48 = "KEY_DOWN" 0xdf47 = "KEY_LEFT" 0xdf07 = "KEY_RIGHT" 0xdf42 = "KEY_HOME" 0xdf0a = "KEY_BACK" 0xdf18 = "KEY_MENU" 0xdf03 = "KEY_MODE" 0xdf54 = "KEY_1" 0xdf16 = "KEY_2" 0xdf15 = "KEY_3" 0xdf50 = "KEY_4" 0xdf12 = "KEY_5" 0xdf11 = "KEY_6" 0xdf4c = "KEY_7" 0xdf0e = "KEY_8" 0xdf0d = "KEY_9" 0xdf0c = "KEY_0" 0xdf41 = "KEY_FN" 0xdf10 = "KEY_DEL" * 0xdf5d = "KEY_VOLUMEUP" 0xdf5c = "KEY_VOLUMEDOWN" 0xdf4b = "KEY_YOUTUBE" * 0xdf4f = "KEY_NETFLIX" * 0xdf5f = "KEY_HELP" 0xdf01 = "KEY_PLAY" 0xdf1c = "KEY_POWER" 0xdff1 = "KEY_TVPOWER" * 0xdff2 = "KEY_TVOUTPUT" * 0xdff3 = "KEY_TVMUTE" * 0xdff4 = "KEY_TVVOLUMEDOWN" * 0xdff5 = "KEY_TVVOLUMEUP" *
  13. Thanks for directing me to the right way. At first attempt the ir-keytable -t was not working. I was trying to use the different protocols according the LibreElec Infra-Red Remotes page but I was getting the errors: # ir-keytable -p nec -t Protocols for device can not be changed Protocols changed to Testing events. Please, press CTRL-C to abort. Then I read few other web pages and looking into /etc/rc_maps.cfg and found, that my IR device is not the first (rc0): # ir-keytable Found /sys/class/rc/rc1/ (/dev/input/event2) with: Name: gpio_ir_recv Driver: gpio_ir_recv, table: rc-empty LIRC device: /dev/lirc0 Attached BPF protocols: Operation not supported Supported kernel protocols: other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon Enabled kernel protocols: lirc bus: 25, vendor/product: 0001:0001, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 ms Found /sys/class/rc/rc0/ (/dev/input/event1) with: Name: dw_hdmi Driver: cec, table: rc-cec Supported kernel protocols: cec Enabled kernel protocols: cec bus: 30, vendor/product: 0000:0000, version: 0x0001 Repeat delay = 0 ms, repeat period = 125 ms So I must start the ir-keytable with -s rc1 parameter then finally got it working: # ir-keytable -s rc1 -p nec -t Protocols changed to nec Testing events. Please, press CTRL-C to abort. 3009.632067: lirc protocol(necx): scancode = 0xdf0c 3009.632120: event type EV_MSC(0x04): scancode = 0xdf0c 3009.632120: event type EV_SYN(0x00). 3009.684073: lirc protocol(necx): scancode = 0xdf0c repeat 3009.684129: event type EV_MSC(0x04): scancode = 0xdf0c 3009.684129: event type EV_SYN(0x00). 3009.792069: lirc protocol(necx): scancode = 0xdf0c repeat 3009.792121: event type EV_MSC(0x04): scancode = 0xdf0c 3009.792121: event type EV_SYN(0x00). So last point is to find the correct key mapping and make the settings persistent.
  14. Hello again, last thing I would like to solve is the infrared remote... I read this post and I have a question - is the current kernel compiled with this setting: CONFIG_ROCKCHIP_REMOTECTL=y CONFIG_ROCKCHIP_REMOTECTL_PWM=y I cannot find these in the kernel config file even commented-out. Other point - seems I need the dtbo with remotectl-pwm. This was in the Android DTB: pwm@ff1b0030 { #pwm-cells = <0x03>; clock-names = "pwm\0pclk"; clocks = <0x02 0x3c 0x02 0xd6>; compatible = "rockchip,remotectl-pwm"; handle_cpu_id = <0x01>; interrupts = <0x00 0x32 0x04>; phandle = <0xae>; pinctrl-0 = <0x46>; pinctrl-names = "default"; reg = <0x00 0xff1b0030 0x00 0x10>; remote_pwm_id = <0x03>; remote_support_psci = <0x01>; status = "okay"; ir_key1 { rockchip,key_table = <0xf2 0xe8 0xba 0x9e 0xf4 0x67 0xf1 0x6c 0xef 0x69 0xee 0x6a 0xbd 0x66 0xea 0x73 0xe3 0x72 0xe2 0xd9 0xb2 0x74 0x4d 0x74 0xbc 0x71 0xec 0x8b 0xbf 0x190 0xe0 0x191 0xe1 0x192 0xe9 0xb7 0xe6 0xf8 0xe8 0xb9 0xe7 0xba 0xf0 0x184 0xbe 0x175>; rockchip,usercode = <0x4040>; }; ... few more ir_keys ... }; I found also this (but not sure if it is related): pwmir { pwmir-pin { phandle = <0x46>; rockchip,pins = <0x02 0x02 0x01 0x7e>; }; }; and in __symbols__ pwmir_pin = "/pinctrl/pwmir/pwmir-pin";