1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

X86/64 Hyperion Server On Windows 10 With Ubuntu Bash (WSL)

Discussion in 'Software Support' started by zapoc, 28 April 2017.

Tags:
  1. penfold42

    penfold42 Moderator Developer

    Messages:
    741
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    I build from source - I’ve never used the installer
     
  2. drc85

    drc85 New Member

    Messages:
    21
    i managed to get the hyperion service + multipliple instances of it, running on WSL :D
    i just had to get better linux knowledge first lol
    the errors in the installation was about the autostart (init is autostart stuff i think ??)
    i still couldnt find a beginner friendly solution / skript for the autostart...
    i always have to start the bash and have to enter the commands manually to start...

    i dont have a usb grabber yet -.-..
    i will get one on the first..
    i hope it works on wsl, this would be awesome!
    i got kodi setup really nice on windows, would be a shame to switch to linux just because of the ambilight :D

    i know there are windows programms like hyperion also but from what i heard hyperion is the best :D
     
  3. penfold42

    penfold42 Moderator Developer

    Messages:
    741
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    Good work!

    USB grabbers probably won’t work with WSL.

    You could try the kodi addon for Hyperion to send the led data from kodi and/or the DirectX grabber
     
  4. drc85

    drc85 New Member

    Messages:
    21
    thx, i think kodi add on would work for kodi but what about a grabber? :D
    im not sure about the driect x grabber? how does it works?
     
  5. drc85

    drc85 New Member

    Messages:
    21
  6. penfold42

    penfold42 Moderator Developer

    Messages:
    741
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    What do you want to be capturing ?

    1) Kodi on Windows ? Try the kodi addon
    2) All windows apps ? Try the direct X grabber
    3) An external signal like a blue ray player or cable tv box ? This isn’t so simple. Right now you can’t use a USB grabber with Hyperion on WSL. If you can use a USB grabber and have kodi play that video then options 1 or 2 above might work.

    Note; I’ve not tried any capture stuff with windows - I’ve just tested the LED and effect side with WSL
     
    • Like Like x 1
  7. drc85

    drc85 New Member

    Messages:
    21
    i want to get the ambilight from a extern hdmi signal ( basically one signal my receiver has two hdmi out)

    i looked at the windows grabber software... im not exactly sure it says monitor and adapter?
    what is meant exactly with adapter? a usb grabber or a gpu?

    i could let the usb grabber display the input video signal fullscreen to a "second monitor"...
    if the second method can grab the the whole second screen i could use this signal to run hyperion ..
    it maybe be possible this way.
     
  8. iiidefconiii

    iiidefconiii Member

    Messages:
    100
    Hardware:
    32/64bit, +Arduino
    did you manage to get hyperion-ng to work?
     
  9. iiidefconiii

    iiidefconiii Member

    Messages:
    100
    Hardware:
    32/64bit, +Arduino
    when i try hyperion-ng on wsl:

    [hyperiond LedDevice] <ERROR> The requested device operation is not supported or prohibited by the running operating system. Device disabled.
     
  10. TimoEr

    TimoEr New Member

    Messages:
    5
    Hardware:
    RPi3, 32/64bit, +Arduino

    I have the same ERROR :/ I installed Hyperion-ng on the Ubuntu WSL but it won't work with my serial connected Arduino.
    With CU the connection works properly and i get the correct Output "ADA"

    I have "straced" the following output:
    Code:
    open("/dev/ttyS3", O_RDWR|O_NOCTTY|O_NONBLOCK|O_CLOEXEC) = 6
    fcntl(6, F_SETFD, FD_CLOEXEC)           = 0
    ioctl(6, TIOCEXCL)                      = -1 ENOTTY (Inappropriate ioctl for device)
    time([1530103952])                      = 1530103952
    fstat(1, {st_mode=S_IFCHR|0660, st_rdev=makedev(4, 1), ...}) = 0
    ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
    write(1, "[hyperiond LedDevice] <ERROR> Th"..., 142) = 142
    time([1530103952])                      = 1530103952
    open("/etc/localtime", O_RDONLY|O_CLOEXEC) = 7
    fstat(7, {st_mode=S_IFREG|0644, st_size=1073, ...}) = 0
    fstat(7, {st_mode=S_IFREG|0644, st_size=1073, ...}) = 0
    read(7, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\2\0\0\0\0"..., 4096) = 1073
    lseek(7, -685, SEEK_CUR)                = 388
    read(7, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\2\0\0\0\0"..., 4096) = 685
    close(7)                                = 0
    socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 7
    connect(7, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = -1 ENOENT (No such file or directory)
    close(7)                                = 0
    open("/dev/console", O_WRONLY|O_NOCTTY) = -1 ENOENT (No such file or directory)
    ioctl(6, TCGETS, {B115200 -opost -isig -icanon echo ...}) = 0
    ioctl(6, TCGETS, {B115200 -opost -isig -icanon echo ...}) = 0
    ioctl(6, SNDCTL_TMR_START or TCSETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
    ioctl(6, TIOCGSERIAL, 0x7fffc9fb1cf0)   = -1 ENOTTY (Inappropriate ioctl for device)
    ioctl(6, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, SNDCTL_TMR_START or TCSETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, SNDCTL_TMR_START or TCSETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, SNDCTL_TMR_START or TCSETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, SNDCTL_TMR_START or TCSETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, SNDCTL_TMR_START or TCSETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TIOCGSERIAL, 0x7fffc9fb1d30)   = -1 ENOTTY (Inappropriate ioctl for device)
    ioctl(6, TCGETS, {B9600 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, SNDCTL_TMR_START or TCSETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    ioctl(6, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    
    
    ioctl(-1, FBIOGET_VSCREENINFO, 0x7fffc9fb2460) = -1 EBADF (Bad file descriptor)
    Maybe this will help to find the bug...

    Greetings Timo
     
  11. iiidefconiii

    iiidefconiii Member

    Messages:
    100
    Hardware:
    32/64bit, +Arduino
    I compiled and installed hyperion again, so i cant try but you could, can you

    sudo passwd root
    su
    and then try again hyperiond? I have read somewere that only root worked with his device. Please report back so i can also give a try
     
  12. TimoEr

    TimoEr New Member

    Messages:
    5
    Hardware:
    RPi3, 32/64bit, +Arduino
    Hey, i have tried it as you suggested. But this doesn't work either.

    it seems that TIOCSTI is not supported in the actual Windows build... https://github.com/Microsoft/WSL/issues/1863

    So does the old hyperion software work for you in WSL with serial Hardware?
     
  13. iiidefconiii

    iiidefconiii Member

    Messages:
    100
    Hardware:
    32/64bit, +Arduino
  14. TimoEr

    TimoEr New Member

    Messages:
    5
    Hardware:
    RPi3, 32/64bit, +Arduino
    Maybe it is possible to add the old serial connection for wsl to Hyperion.ng