ASRock ION 330HT (2nd gen) - built-in IR, which lirc driver?

  Thread Rating:
  • 1 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
scoopy2scoops Offline
Junior Member
Posts: 35
Joined: Nov 2009
Reputation: 0
Post: #31
won't get chance to do this tonight, will run these commands tomorrow.
find quote
marsjall Offline
Junior Member
Posts: 8
Joined: Nov 2009
Reputation: 0
Post: #32
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 Smile
find quote
scoopy2scoops Offline
Junior Member
Posts: 35
Joined: Nov 2009
Reputation: 0
Post: #33
ok cool
find quote
BlueC Offline
Junior Member
Posts: 19
Joined: Nov 2009
Reputation: 0
Post: #34
marsjall Wrote:the bottom of my dmesg now says

Code:
[93191.409817] lirc_dev: IR Remote Control driver registered, major 61
[93192.328025] lirc_serial: auto-detected active low receiver
[93192.328037] lirc_dev: lirc_register_driver: sample_rate: 0
[93192.328190] lirc_serial $Revision: 5.104 $ registered

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?
find quote
therealdude Offline
Junior Member
Posts: 8
Joined: Nov 2009
Reputation: 0
Post: #35
Good news! A part of it at least...

I received a reply from Asrock today, here's what they say:

Quote:Dear Sir,

Thank you for contacting ASRock.

About the issue, we've contacted our device vendor to provide drivers for Linux.
We believed that they are still working on it, please check our website one a while for latest drivers update.

Thank you for your feedback and have a nice day.

Your Sincerely,
ASRock TSD

Seems that they are working on it, but in what timeframe it will be ready...
find quote
scoopy2scoops Offline
Junior Member
Posts: 35
Joined: Nov 2009
Reputation: 0
Post: #36
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
find quote
BlueC Offline
Junior Member
Posts: 19
Joined: Nov 2009
Reputation: 0
Post: #37
More (same) news from ASRock:

Quote:Hello,

I will check this with our headquarters in Taiwan. Hopefully they can get drivers from the manufacturer of the IR controller.

Would people within the Linux community be able to write their own drivers for this? If so, what kind of information would they need?

As you might have read already, the controller is a Nuvoton W836x7HG CIR device. Maybe you and some others with the same request can also contact Nuvoton directly. Maybe it will help to convince them to provide some solution.

As soon as I get some feedback from Taiwan I will let you know.

Best regards,

ASRock Support

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?
find quote
minifo Offline
Junior Member
Posts: 2
Joined: Nov 2009
Reputation: 0
Post: #38
BlueC Wrote:More (same) news from ASRock:
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?

/var/log/messages:
Code:
Nov 20 17:50:53 XBMCLive kernel: [  130.884060] lirc_serial: auto-detected active low receiver
Nov 20 17:50:53 XBMCLive kernel: [  130.884069] lirc_dev: lirc_register_plugin: sample_rate: 0
/var/log/dmesg:
No new entry

After running the "modprobe lirc_serial" you get "/dev/lirc0" but still the remote doesnt work.
(This post was last modified: 2009-11-20 19:59 by minifo.)
find quote
BlueC Offline
Junior Member
Posts: 19
Joined: Nov 2009
Reputation: 0
Post: #39
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?
find quote
cyberbird Offline
Junior Member
Posts: 1
Joined: Nov 2009
Reputation: 0
Post: #40
marsjall Wrote:WLAN works fine under 9.10

I checked inside BIOS and found a CIR enable/disable-switch (it's enabled), so I guess the device is present.

The driver-CD that came with this unit have some windows-drives for the CIR-device.

relnote.txt inside the XP-folder says:

XP CIR driver for Nuvoton's W836x7HG CIR devices.

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.
find quote
prae5 Offline
Team-XBMC Forum Moderator
Posts: 2,072
Joined: Jan 2009
Reputation: 34
Location: Cambridge, UK
Post: #41
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...
find quote
marathont Offline
Junior Member
Posts: 42
Joined: Jan 2006
Reputation: 0
Post: #42
BlueC Wrote: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?

I ran mode2 --device=/dev/lirc0

Code:
mode2: could not open /dev/lirc0
mode2: default_init(): Device or resource busy
find quote
BlueC Offline
Junior Member
Posts: 19
Joined: Nov 2009
Reputation: 0
Post: #43
marathont Wrote:I ran mode2 --device=/dev/lirc0

Code:
mode2: could not open /dev/lirc0
mode2: default_init(): Device or resource busy

Did you do that as root? Or with sudo? Oh, and did you make sure lircd isn't running too?
find quote
oysteinr Offline
Junior Member
Posts: 1
Joined: Nov 2009
Reputation: 0
Post: #44
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
[   20.592116]
[   20.592122] lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $
[   20.592129] lirc_mceusb2: Daniel Melander <lirc@rajidae.se>, Martin Blatter <martin_a_blatter@yahoo.com>
[   20.595399] usbcore: registered new interface driver lirc_mceusb2
[   23.616300] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   23.616311] Bluetooth: BNEP filters: protocol multicast
[   23.643265] Bridge firewalling registered
[   25.170228] ppdev: user-space parallel port driver
[   39.484019] eth0: no IPv6 routers present

ls /dev/lirc*:
Code:
xbmc@xbmc-htpc:~$ ls /dev/lirc*
/dev/lircd

I'm running ubuntu 9.04 desktop if that makes any difference
find quote
Maximus.CC64 Offline
Junior Member
Posts: 3
Joined: Nov 2009
Reputation: 0
Post: #45
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/ProductAndSale...T6775F.htm

As is clearly seen in the productspecification:
http://www.isd.com/hq/enu/ProductAndSale...AndServer/

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
(This post was last modified: 2009-11-21 12:07 by Maximus.CC64.)
find quote
Post Reply