Jump to content

fatugazuhati

  • Posts

    37
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Everything posted by fatugazuhati

  1. Thank you @dbsharpe, I was been able to recompile the kernel on the device with that sources, but I'm not able to crosscompile the kernel with any toolchain, the compilation finish succesfully but I haven't an Image file for the kernel not any ko files for the modules. Do you have some idea of because this occours?
  2. Thanks a lot, yesterday I searched for all the day but I wasn't be able to find this repo. Thank you.
  3. Thanks for answering me but unfortunately that is the binary and can't help me. Anyway are you sure that it has support for vlan 8021q? About the sources for khadas-3.14, this is a big lost, in my opinion the Armbian versions with kernel 3.14 are the better one for s905/s912 devices, with them everything works and it is possible install Armbian in the emmc. The kernel 3.14 is outdated but COREElec too still uses a kernel 3.14 for theese devices. Honestly I don't understand why that branch has been deleted and not only archived.
  4. Does someone have the sources for the old kernel khadas-3.14? It was just few mega. In the past I was able to git it with a simple: git clone -b khadas-3.14 https://github.com/150balbes/Amlogic_s905-kernel.git unfortunately I have never saved it and now it isn't more available in the @balbes150 repo, I never thought it would be removed. I'm using an s905 device with Armbian installed in the emmc and I would stay with this old version because with it everything works, but now I should recompile my kernel to add support for 8021q vlan. If someone has this kernel, please could he upload it somewhere? I really need it. I hope in a hand from you all.
  5. About the wifi you have to lad the correct module, everything is explained in the first post. About the dtb, the best dtb is the one from your manufacturer so if it works you will never use a different dtb.
  6. Try to boot Armbian with kernel 3.14 without any dtb, if it will fail please extract the dtb from your device and post it here.
  7. You can use in armbian the dtb from libreelec.
  8. Simply that it isn't present in your boot img. Yes, you can but it is not so simple and if I'm not in error you should found the answer in the s905/s905x thread.
  9. It is a kernel process and you can check the problem in this way: ps aux | grep " D" root 2534 0.0 0.0 0 0 ? D 14:29 0:03 [vdec-core] root 6948 0.0 0.0 4312 648 pts/0 S+ 15:59 0:00 grep D @balbes150, if can help in dmesg I have this: dmesg | grep vdec [ 5.735325] codec:get gate vdec control ok ffffffc09319c000 [ 5.739991] codec:vdec_request_irq ffffffc00184efa8, vsync [ 5.861875] codec:used fix clk for vdec clk source! Instead using the kernel from Jessie with wich this problem isn't present in dmesg I have this: dmesg | grep vdec [ 5.657064] codec:get gate vdec control ok ffffffc0b3816500 [ 5.661865] codec:used fix clk for vdec clk source!
  10. Did you noticed that also in a clean install at system in idle we always have a system load that never goes under 1 caused by vdec-core in uninterruptible sleep? This is a kernel related problem appeared in last versions and I have reported it here. Do you have some idea about what do to?
  11. After a clean install of debian stretch you can notice a strange load when the system is in idle, also if the cpu is at 0% and we have almost all the ram free we can notice a strange load average. The load should be 0 but it never goes under 1. You can notice this with the commands "top" or "uptime" but I'm sure that you know this :-) With the command "ps -e v" I noticed that there is the process vdec-core that always waits for disk access (D) and in effect you can continuosly see this process in the top and should be for this that the load never goes to 0. After some search I discovered that this should be something kernel related, but I'm not sure what this is. Remembering that in jessie everythings was working correctly and that in the same conditions I had a load of 0, I have simply tried to using the kernel from jessie in stretch to see what happened, I have simply replaced the zimage and in this way the process vdec-core has disappeard and with the cpu at 0% now i have a load of almost 0, how this should be. At the moment to solve this problem I'm using the zimage from jessie in stretch but I'd like to stay with an updated kernel. What should we do to solve the problem? Do you know what vdec-core is?
  12. Has something been changed in the kernel to solve the abnormal load caused by vdec-core?
  13. Same abnormal load caused by vdec-core also in Armbian_5.41_S9xxx_Debian_stretch_3.14.29_server_20180212.img, to avoid the problem I'm using the kernel from jessie but is there any chance to solve this problem in the stretch kernel?
  14. No one noticed a strange load in stretch? Wit a clean install, the cpu at 0% and with almost all the ram free the load never goes under 1. In jessie in the same conditions I have a load of 0. I'm trying to understand why this happens. Ok, the culprit is vdec-core that always waits for disk access and the problem is in the kernel, using the kernel from jessie everything works correctly. I would use an updated kernel, how can this problem been solved?
  15. I'm comparing jessie with stretch from yesterday but without much success. Anyway I have just tried with Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20180205.img and the remote still doesn't work, for example if I press the power-off button nothing happens and in the syslog I have this: Feb 5 20:51:01 localhost kernel: [ 563.265710@0] remote: press ircode = 0x18, Feb 5 20:51:01 localhost kernel: [ 563.265735@0] remote: scancode = 0x0074,maptable = 0,code:0xe718ff00 Feb 5 20:51:01 localhost kernel: [ 563.265777@0] Feb 5 20:51:01 localhost kernel: [ 563.625406@0] remote: release ircode = 0x18, Feb 5 20:51:01 localhost kernel: [ 563.625430@0] remote: scancode = 0x0074, maptable = 0,code:0x00000000 Feb 5 20:51:01 localhost kernel: [ 563.625445@0] Solved :-) I had to write a new rule, thanks for your hard work.
  16. I really don't like ubuntu and I'd like to continue using Debian, do you think that this problem can be solved in some way?
  17. I have been able to boot Stretch with the kernel, the modules and the firmware from Jessie but amremote still doesn't work -.-"
  18. Do you thing that the problem with the remote in Stretch is kernel related? Is there something that can I do? In Jessie the remote works. Can I try to boot stretch with the kernel from Jessie? If I can what files and directories should I replace?
  19. Hi @balbes150, thanks a lot for your work. I have just tried Armbian_5.37_S9xxx_Debian_stretch_4.9.40_server_20180202.img on an s95 meta but I have a black screen and it doesn't boot, I tried using the file gxm_q200_2g.dtb obviously rename as dtb.img, what dtb should I use with my box? About Armbian_5.37_S9xxx_Debian_stretch_3.14.29_server_20180203.img, it works fabulously but I have always to edit the config.txt to make working the wifi and I have to use patchram to make working the bluetooth and I have no way to make working the ir remote, I have the same problems as I described in my previous post. Could you help me in debugging the problem with amremote, I tried everythings and I have no more idea.
  20. Hi @balbes150, a new little problem, on stretch the remote commands doesn't work, I used the same remote.conf that I used in Jessie. I retried in Jessie and everything works. I'm trying to solve this problem, any advice? This time I really don't have any idea on what to check, everything seems ok but amremote doesn't work. I'have correctly installed aml-amremote-905_5.34_arm64, I have placed in /etc/amremote the same remote.conf that I have correctly used in jessie, I have started the service amlogic-remotecfg and it runs without problems but the remote controller doesn't work. Every time that I press a remote controller's button in the syslog I have something similar to this: Feb 2 23:21:40 localhost kernel: [ 682.978463@0] remote: Wrong custom code is 0xe718ff00 Feb 2 23:21:41 localhost kernel: [ 683.887669@0] remote: Wrong custom code is 0xb946ff00 Feb 2 23:21:42 localhost kernel: [ 684.608617@0] remote: Wrong custom code is 0xf906ff00 Feb 2 23:21:42 localhost kernel: [ 685.296251@0] remote: Wrong custom code is 0xbd42ff00 Feb 2 23:21:43 localhost kernel: [ 686.308314@0] remote: Wrong custom code is 0xfb04ff00 Feb 2 23:21:44 localhost kernel: [ 687.122292@0] remote: Wrong custom code is 0xf906ff00 Feb 2 23:21:45 localhost kernel: [ 687.820066@0] remote: Wrong custom code is 0xaa55ff00 but the factory code in /etc/amremote/remote.conf is already set to factory_code= 0xff000001. I have already tried replacing /lib/firmware with the one from jessie where everythings works. What can I do? Could this be a kernel's problem?
  21. I'm trying but without success. I'm not able to understand if the problem is a wrong dtb, a wrong module or a wrong software configuration. These are my steps to install the bluetooth: apt-get install bluetooth blueman bluez bluez-tools rfkill libbluetooth-dev modprobe hci_uart I check that the module is correctly loaded: lsmod | grep hci_uart hci_uart 21653 0 bluetooth 242323 1 hci_uart I check that the firmware is correctly loaded: dmesg | grep firmware [ 15.261423] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt [ 18.800655] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin [ 18.800660] dhd_conf_set_nv_name_by_chip: nvram_path=/lib/firmware/brcm/nvram_ap6330.txt [ 18.800665] dhdsdio_download_firmware: set use_rxchain 0 [ 18.800668] dhdsdio_download_firmware: set txglomsize 16 [ 18.800675] Final fw_path=/lib/firmware/brcm/fw_bcm40183b2.bin [ 18.800678] Final nv_path=/lib/firmware/brcm/nvram_ap6330.txt [ 18.800681] Final conf_path=/lib/firmware/brcm/config.txt I check the bluetooth status and I start it: systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: inactive (dead) Docs: man:bluetoothd(8) systemctl start bluetooth systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Wed 2018-01-31 10:11:40 UTC; 1s ago Docs: man:bluetoothd(8) Main PID: 8845 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─8845 /usr/lib/bluetooth/bluetoothd Jan 31 10:11:40 amlogic systemd[1]: Starting Bluetooth service... Jan 31 10:11:40 amlogic bluetoothd[8845]: Bluetooth daemon 5.43 Jan 31 10:11:40 amlogic bluetoothd[8845]: Starting SDP server Jan 31 10:11:40 amlogic systemd[1]: Started Bluetooth service. Jan 31 10:11:40 amlogic bluetoothd[8845]: Bluetooth management interface 1.4 ini I attach the HCI adapter: sudo hciattach /dev/ttyS1 any I re-check the bluetooth status: service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-01-31 14:58:49 UTC; 7min ago Docs: man:bluetoothd(8) Main PID: 4459 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─4459 /usr/lib/bluetooth/bluetoothd Jan 31 14:58:49 amlogic systemd[1]: Starting Bluetooth service... Jan 31 14:58:49 amlogic bluetoothd[4459]: Bluetooth daemon 5.43 Jan 31 14:58:49 amlogic systemd[1]: Started Bluetooth service. Jan 31 14:58:49 amlogic bluetoothd[4459]: Starting SDP server Jan 31 14:58:49 amlogic bluetoothd[4459]: Bluetooth management interface 1.4 initialized Jan 31 15:06:15 amlogic bluetoothd[4459]: Failed to obtain handles for "Service Changed" characteristic Jan 31 15:06:15 amlogic bluetoothd[4459]: Sap driver initialization failed. Jan 31 15:06:15 amlogic bluetoothd[4459]: sap-server: Operation not permitted (1) Jan 31 15:06:16 amlogic bluetoothd[4459]: hci0 Load Connection Parameters failed: Unknown Command (0x01) and I have 4 erros. The bluetooth seems active: hcitool dev Devices: hci0 8F:CD:8A:1D:F9:D5 rfkill list 0: bt-dev: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmfmac-wifi: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no but I'm not able to see any device or to bee saw from any device: bluetoothctl [NEW] Controller 8F:CD:8A:1D:F9:D5 amlogic [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# discoverable on Changing discoverable on succeeded [CHG] Controller 8F:CD:8A:1D:F9:D5 Discoverable: yes [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller 8F:CD:8A:1D:F9:D5 Discovering: yes [bluetooth]# exit [DEL] Controller 8F:CD:8A:1D:F9:D5 amlogic [default] Any advice? Postedit: I was been able to solve the problem with the bluetooth with patchram, now everythings work on my minibox linux :-) Do you think will be possible install kodi on debian server and have the hardware acceleration working?
  22. At the moment I have enough free time and if you want I can help to test\debug the bluetooth but you should tell me what to do because I haven't any idea. I have an s95 telos and an s95 meta and at the moment I'm using the s95 meta that has an ampak ap6330.
  23. Well, now everything works. With the firmware directory from jessie the wifi works and I have this : root@amlogic:# dmesg | grep firmware [ 77.673467] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt [ 78.559879] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin [ 78.559884] dhd_conf_set_nv_name_by_chip: nvram_path=/lib/firmware/brcm/nvram_ap6330.txt [ 78.559888] dhdsdio_download_firmware: set use_rxchain 0 [ 78.559891] dhdsdio_download_firmware: set txglomsize 16 [ 78.559899] Final fw_path=/lib/firmware/brcm/fw_bcm40183b2.bin [ 78.559902] Final nv_path=/lib/firmware/brcm/nvram_ap6330.txt [ 78.559905] Final conf_path=/lib/firmware/brcm/config.txt With the firmware directory from stretch the wifi doesn't work and I have this : root@amlogic:~# dmesg | grep firmware [ 53.980967] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt [ 54.869114] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin [ 54.869119] dhdsdio_download_firmware: set use_rxchain 0 [ 54.869122] dhdsdio_download_firmware: set txglomsize 16 [ 54.869129] Final fw_path=/lib/firmware/brcm/fw_bcm40183b2.bin [ 54.869132] Final nv_path=/lib/firmware/brcm/ [ 54.869135] Final conf_path=/lib/firmware/brcm/config.txt [ 54.898305] _dhdsdio_download_firmware: dongle nvram file download failed What could be the problem? How can I correctly solve it? Postedit: I solved the problem correctly editing the config.txt
  24. Until some days ago I had installed armbian server based on jessie and everything was working apart the bluetooth. I decided to try the new armbian server based on stretch and I'm not more able to have the wifi working. I'm using the same dtb that I was using with jessie and I also loaded the module dhd that I used in jessie. What can I do? Some advice?
×
×
  • Create New...