Posts by chewitt

  • xorg issue x86_64

    ^ the systemd journal clearly shows that udev detects an nVidia card so xorg-configure for nvidia-legacy is invoked according to:

    LibreELEC.tv/96-nvidia.rules at a8b6f4c35dec2a4efb59ba1257f5ec36f4fdcc0d · chewitt/LibreELEC.tv · GitHub

    So create /storage/.config/udev.d/96-nvidia.rules with the content below and then reboot and the updated rule file (which if present overrules the embedded one) should prevent the nvidia card from triggering the xorg-configure process:

    Code
    ACTION!="add|change", GOTO="end_video"
SUBSYSTEM=="pci", ATTR{class}=="0x030000", ATTRS{vendor}=="0x10de", GOTO="subsystem_pci"
GOTO="end_video"

LABEL="subsystem_pci"
GOTO="end_video"

LABEL="end_video"

    The next rule to be evaluated is 97-xorg.rules which should now match against the AMD card:

    LibreELEC.tv/97-xorg.rules at amlogic · chewitt/LibreELEC.tv · GitHub

    In theory..

  • SMB No route to host

    It sounds like the HTPC device is running in a different IP subnet to the NAS and there are no routing rules (or gateway) to handle routing data between the two subnets; hence the "no route to host" message. If you added a WIFI router to an existing network (a hunch) it will be easier to configure it as a wireless bridge so it simply provides a wireless extension to the existing network instead of creating a second (routed) network for wireless devices. If you use it as a router (which will also result in NAT being used) you will need to configure routing rules (either manually on each host or pushed via DHCP) so devices in each subnet know how to route data to each other.

  • Leia ALPHA Video Playback

    LePotato is a nice board (similar, but better designed than C2) but it has core weakness of all S905X devices; only 10/100 Ethernet. The better option would be an S905D device with GB Ethernet, but beware that some also ship with 10/100. Odroid N1 was cancelled. N2 will be along in a bit (but no ideas on it) and the H1 that HK have just announced probably isn't cheap but will have the advantage of being x86_64 and thus less exotic to support compared to ARM hardware. NUC's are good too.

    NB: If it works, don't fix it :)

  • xorg issue x86_64

    It's not clear which device you do want to use, but assuming it's the AMD card the following will blacklist the nVidia driver module and prevent it from being loaded at boot time; at which time only the AMD card should be usable and xorg.conf(s) shouldn't come into play.

    Code
    echo "blacklist nvidia" > /storage/.config/modprobe.d/nvidia.conf
reboot

  • Help with WIFI

    Looks like the device ID exists in both drivers (bcma and wl) so whichever one happens to be loaded by the kernel first (roll dice) tries to claim the device. We should probably patch out the device ID to prevent that.

  • Help with WIFI

    ^ looks like the card is trying to use the in-kernel brcmfmac driver instead of the vendor wl driver, so perhaps blacklist it and reboot:

    Code
    echo "blacklist brcmfmac" > /storage/.config/modprobe.d/brcmfmac.conf
reboot

    sorted?