Posts by nickrob84

    Is there a standard safe oveclock for an RPI3 running LE for general use? Or is it even worth it in the first place? Sorry for hijacking your thead.

    How flexible are the RP's in terms of overclocking. Obvoiusly in the PC world their are components that are literally made to be clocked but is there any evidence to suiggest that overclocking (sensibly) will damage a Pi?

    Well after some extensive testing over both boxes, neither have skipped a beat. I mean I haven't exactly stressed tested them but they have both played several hours of 1080p footage (including live) with no buffering or any issues at all over the 5G network. Not even one. Even afer 12 hours idle they were instantly ready to go. I am a man of my word. There will be a £25 donation in reference to Irusak's help on this subject at some point over the weekend when the wife feels like returning my cards!! Thanks again.

    It accepted the firet command but after the reboot its coming up with:

    LibreELEC-U:~ # cat /sys/bus/usb/drivers/rtl8812au/module/parameters/rtw_power_m
    cat: can't open '/sys/bus/usb/drivers/rtl8812au/module/parameters/rtw_power_mgnt': No such file or directory

    It would be too easy to show up as simple as your setup wouldn't it!

    LibreELEC-U:~ # lsmod
    Module Size Used by
    hci_uart 14478 1
    btbcm 5379 1 hci_uart
    bluetooth 282086 3 btbcm,hci_uart
    brcmfmac 172683 0
    brcmutil 4893 1 brcmfmac
    bcm2835_gpiomem 2652 0
    bcm2835_wdt 2777 0
    8812au 1500982 0
    cfg80211 229385 2 brcmfmac,8812au

    which part am I taking from here?

    I can honestly say I have never had an issue like this for years. I must of put at least 50 hours into solving how to turn the damn power management off wlan1 permenantly and still nothing. I have learnt the inside and outside of SSH/putty/commands as a bonus though. Please somebody must know?

    wlan1 Link encap:Ethernet HWaddr 74:DA:38:73:41:B3
    inet addr: Bcast: Mask:
    RX packets:80274 errors:0 dropped:58 overruns:0 frame:0
    TX packets:692 errors:0 dropped:18 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2319460 (2.2 MiB) TX bytes:145074 (141.6 KiB)

    LibreELEC-U:~ # lsusb -t
    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
    |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc980M
    |__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=rtl88480M

    this make sense to anyone? In particular to the 5G instability?

    Although when it works it works very well, it doesn't seem very reliable interms of holding the connection. I.e 30 mins idle time, go back into Kodi and there is no connection but is fine after a reboot. Anything I can do about the general instabilities? Driver updates etc?