I can also see that Amlogic uploaded new sources to their Openlinux site, I will see if we can use the latest drivers. [emoji56]
Hi,
new kernel source is the same as openwetek one without commits after Jul 1.
regards,
I can also see that Amlogic uploaded new sources to their Openlinux site, I will see if we can use the latest drivers. [emoji56]
Hi,
new kernel source is the same as openwetek one without commits after Jul 1.
regards,
Hi I Tried .005 build in my K2 pro device and did not recognice my ac wifi adepter. How ı can install my wifi driver to libreelec?
Hi I Tried .005 build in my K2 pro device and did not recognice my ac wifi adepter. How ı can install my wifi driver to libreelec?
I have the same problem with same device. We need wait for a new build.
I have the same problem with same device. We need wait for a new build.
How about tvh and vdr 4k channels. Last time dvbs driver was missing. Did you try?
I have already included the patch for the next build, just noticed it at SPMC today morning. Thanks for the heads up.
Hi kszaq,
I have been waiting for ur s905 build for mxq pro with wifi driver 8189 ftv which u said will be done .pls advise..thanks
Sent from my SM-N910G using Tapatalk
I have the same problem with same device. We need wait for a new build.
Without logs I can't promise the driver will be there as I don't know what's the WiFi chip inside device. As I'm finishing work on a next release your WiFi will probably still not work.
I have been waiting for ur s905 build for mxq pro with wifi driver 8189 ftv which u said will be done .pls advise..thanks
I plan to release the build this week.
[hr]
new kernel source is the same as openwetek one without commits after Jul 1.
I meant the drivers. I included WiFi and NAND driver updates.
No rush, better polish this release and add and test as much features you can instead of releasing something crappy. Build 005 is really good except reboot issues in my case. Remove slowely all spotted bugs becsuse there is no rush - next kodi build is far away.
Without logs I can't promise the driver will be there as I don't know what's the WiFi chip inside device. As I'm finishing work on a next release your WiFi will probably still not work.
I understand, I will wait for release after...
How I can test what wifi chip there is inside? And what kind of log you need?
[hr]
If is useful, I found this info about wifi:
dhd; IEEE 802.11 b/g/n; Broadcom 4329/30; AP Mode
How I can test what wifi chip there is inside? And what kind of log you need?
See LibreELEC
How I can test what wifi chip there is inside? And what kind of log you need?
Please give me a result of the following commands:
[hr]
In Libre Elec by SSH
LibreELEC:~ # cat /sys/bus/sdio/devices/*/device; cat /sys/bus/sdio/devices/*/vendor
0x4335
0x4335
0x4335
0x02d0
0x02d0
0x02d0
LibreELEC:~ # lsusb -v
Bus 001 Device 003: ID 0bc2:2320 Seagate RSS LLC USB 3.0 bridge [Portable Expansion Drive]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bc2 Seagate RSS LLC
idProduct 0x2320 USB 3.0 bridge [Portable Expansion Drive]
bcdDevice 1.00
iManufacturer 2 Seagate
iProduct 3 Expansion
iSerial 1 123456789012
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
-sh: Per-port: not found
EndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Command pipe (0x01)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
HIRD Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 2 TT per port
bMaxPacketSize0 64
idVendor 0x05e3 Genesys Logic, Inc.
idProduct 0x0610 4-port hub
bcdDevice 32.98
iManufacturer 0
iProduct 1 USB2.0 Hub
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 1 Single TT
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
Endpoint DescrieProtocol 2 TT per port
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 4
wHubCharacteristic 0x00e0
Ganged power switching
Ganged overcurrent protection
TT think time 32 FS bits
Port indicators
bPwrOn2PwrGood 50 * 2 milli seconds
bHubContrCurrent 100 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Port 3: 0000.0503 highspeed power enable connect
Port 4: 0000.0100 power
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
bNumConfigurations 1
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0001
Self Powered
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.14
iManufacturer 3 Linux 3.14.29 dwc_otg_hcd
iProduct 2 DWC OTG Controller
iSerial 1 dwc2_b
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 1
wHubCharacteristic 0x0008
Ganged power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0503 highspeed power enable connect
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0001
Self Powered
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.14
iManufacturer 3 Linux 3.14.29 dwc_otg_hcd
iProduct 2 DWC OTG Controller
iSerial 1 dwc2_a
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 1
wHubCharacteristic 0x0008
Ganged power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0000
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0001
Self Powered
Display More
I plan to release the build this week.
Here my week is over tomorrow :D, Cant wait to see all the improvements.
Is anyone else having the issue of the refresh rate not changing when playing a 24hz source?
willyfan Thank you for the logs. And sorry to say that your WiFi chip is not supported even in the latest drivers released 2 days ago by Amlogic. I will try to add it manually but not for the next build - a test build soon after I upload the next version?
Hi there,
it seems my box is resetting date/time to 01.01.1970 01:00 am on every cold boot and after some time (betweet 30 secs and a minute) it gets the correct date/time when it has an established network connection. This also happens on Android. Problem with this is that Kodi tries to connect to my Mysql-Server with that incorrect time/date and cannot get through, and so i have no database on Kodi startup. I'll have to wait until the correct time/date are displayed in Kodi and then do a warm reboot to get my Mysql-connection working.
Is there anything i could add to autostart.sh to set/read the correct time/date before Kodi reads my advancedsettings.xml ? Or a pause setting? I want to make sure my wife can use Kodi without rebooting several times
(Wait for network setting doesn't do the trick as the network is available right from the start, it must be the time/date setting and i can reproduce that problem)
I realized the reboot function does not work on
my box, neither while using the remote nor the
app Yatse.
Is that a general bug or just a problem on my side?
willyfan Thank you for the logs. And sorry to say that your WiFi chip is not supported even in the latest drivers released 2 days ago by Amlogic. I will try to add it manually but not for the next build - a test build soon after I upload the next version?
Thanks kszag. We are waiting for your new builds
Hi there,it seems my box is resetting date/time to 01.01.1970 01:00 am on every cold boot and after some time (betweet 30 secs and a minute) it gets the correct date/time when it has an established network connection. This also happens on Android. Problem with this is that Kodi tries to connect to my Mysql-Server with that incorrect time/date and cannot get through, and so i have no database on Kodi startup. I'll have to wait until the correct time/date are displayed in Kodi and then do a warm reboot to get my Mysql-connection working.
Is there anything i could add to autostart.sh to set/read the correct time/date before Kodi reads my advancedsettings.xml ? Or a pause setting? I want to make sure my wife can use Kodi without rebooting several times
(Wait for network setting doesn't do the trick as the network is available right from the start, it must be the time/date setting and i can reproduce that problem)
That is because this device does not have RTC on board and you have to wait until NTP server replies with proper time to your software timer in device software.