ASRock ION 330HT (2nd gen) - built-in IR, which lirc driver? - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: ASRock ION 330HT (2nd gen) - built-in IR, which lirc driver? (/showthread.php?tid=61840) |
- scoopy2scoops - 2009-11-19 won't get chance to do this tonight, will run these commands tomorrow. - marsjall - 2009-11-19 no need to run those commands... it's just the output to see if we can find out how to get this sh*t working - scoopy2scoops - 2009-11-19 ok cool - BlueC - 2009-11-19 marsjall Wrote:the bottom of my dmesg now says This looks pretty promising! Shame I don't have the machine anymore else I'd be all over this, so pls bear with me while I try to work this out from memory and with you as a proxy! Was there any other messages in dmesg related to this? What about /var/log/messages? It *looks* here as if it has registered the serial IR receiver device, but I would have expected it to say where it registered it to in /dev/. Is there now any device on /dev/lirc* ? What does "ls -al /dev/input/by-path" (as root) give? Good News - therealdude - 2009-11-20 Good news! A part of it at least... I received a reply from Asrock today, here's what they say: Quote:Dear Sir, Seems that they are working on it, but in what timeframe it will be ready... - scoopy2scoops - 2009-11-20 I shutdown my Asrock last night from ubuntu and this morning when I switched on the TV it was on really loud, so I turned my Samsung TV down. Strangly my Asrock turned itself on! I've checked it again and it definately isn't a fluke - BlueC - 2009-11-20 More (same) news from ASRock: Quote:Hello, Hmmmm. I'm still thinking that this IR controller can be run using one of the default kernel modules supplier in lirc. I think the lirc_serial module is the best bet. Has anyone else tried "modprobe lirc_serial" and then checked dmesg and /var/log/messages for any hopeful signs? - minifo - 2009-11-20 BlueC Wrote:More (same) news from ASRock: /var/log/messages: Code: Nov 20 17:50:53 XBMCLive kernel: [ 130.884060] lirc_serial: auto-detected active low receiver No new entry After running the "modprobe lirc_serial" you get "/dev/lirc0" but still the remote doesnt work. - BlueC - 2009-11-20 minifo Wrote:After running the "modprobe lirc_serial" you get "/dev/lirc0" but still the remote doesnt work. Hmmm, but it creates the device in /dev so that makes me think the driver *does* work. After the modprobe, can you try running "mode2" then button mashing the remote? Any joy? Or maybe you need "mode2 --device=/dev/lirc0" Any luck with that? - cyberbird - 2009-11-20 marsjall Wrote:WLAN works fine under 9.10 I have send Nuvoton a mail asking about driver suppport. Also in the Linux kernel source I found support for W83667HG, tough targeted as hardware monitor support. I sent an author (from Nuvoton) a mail I will also sent ASRock a mail. I will post updates when I receive replies. - prae5 - 2009-11-20 BlueC Wrote:Hmmm, but it creates the device in /dev so that makes me think the driver *does* work. No that is not necessary the case. It will load if it finds any serial device - standard comm ports, etc... - marathont - 2009-11-20 BlueC Wrote:Hmmm, but it creates the device in /dev so that makes me think the driver *does* work. I ran mode2 --device=/dev/lirc0 Code: mode2: could not open /dev/lirc0 - BlueC - 2009-11-20 marathont Wrote:I ran mode2 --device=/dev/lirc0 Did you do that as root? Or with sudo? Oh, and did you make sure lircd isn't running too? - oysteinr - 2009-11-21 Hi! I am having the same problem with my asrock 330ht. After reading through this thread, i tried "dmesg" and "ls /dev/lirc*", but the output seems a bit different. Any ideas? 11 last lines from dmesg output: Code: [ 20.582273] lirc_dev: IR Remote Control driver registered, major 61 ls /dev/lirc*: Code: xbmc@xbmc-htpc:~$ ls /dev/lirc* I'm running ubuntu 9.04 desktop if that makes any difference CIR is the NCT6775F not the W836x7HG - Maximus.CC64 - 2009-11-21 I scanned the "nuviocirxp.inf" which states that the device is a W836x7HG, after searching the nuvoton website it seems that this is a hardware monitoring chip. But the "x" seems to represent different models: W836x7HG W83637HG-AW LPC Super I/O for Desktop & Server W83667HG LPC Super I/O for Desktop & Server W83697HG LPC Super I/O for Desktop & Server So which one is it ? Time to take a look inside. As i opened up my ION-330-HT-B-BB the chip states to be a: Nuvoton NCT6775F http://www.isd.com/hq/enu/ProductAndSales/ProductLines/ComputerIC/SuperIO/LPCSuperIOforDesktopAndServer/NCT6775F.htm As is clearly seen in the productspecification: http://www.isd.com/hq/enu/ProductAndSales/ProductLines/ComputerIC/SuperIO/LPCSuperIOforDesktopAndServer/ The NCT6775F is the only one with a Consumer-IR. Therefore i can conclude that, if the device is recognized as being a W83667HG stated by cyberbird and BlueC (which has no IR functionality), this cannot possibly work. Gr. Maximus.CC64 |