ArchiveOrangemail archive

LIRC mailing list


lirc-list.lists.sourceforge.net
(List home) (Recent threads) (68 other SourceForge lists)

Subscription Options

  • RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
  • Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe address with "subscribe" in the subject line, or visit the list's homepage here.
  • Low traffic list: less than 3 messages per day
  • This list contains about 4,239 messages, beginning Aug 2009
  • 0 messages added yesterday
Report the Spam
This button sends a spam report to the moderator. Please use it sparingly. For other removal requests, read this.
Are you sure? yes no

Asrock A330ION mobo (Nuvoton testing)

Ad
Martin Bunyard 1288315632Fri, 29 Oct 2010 01:27:12 +0000 (UTC)
Hi,

I have tried testing the recent Nuvoton driver on an Asrock A330ION mobo
(http://www.asrock.com/mb/overview.asp?Model=A...) with Mythbuntu
10.10 using the instructions in
http://ubuntuforums.org/showthread.php?t=1596...

In overview: I have built a new kernel (based on 2.6.35.22) with the
nuvoton-cir driver patch, configured lirc files and booted into the new
kernel.

kern.log reports:
Oct 29 01:06:37 JamBox kernel: [   19.247230] lirc_dev: IR Remote
Control driver registered, major 250
Oct 29 01:06:38 JamBox kernel: [   19.604228] IR NEC protocol handler
initialized
Oct 29 01:06:38 JamBox kernel: [   19.667421] IR RC5(x) protocol handler
initialized
Oct 29 01:06:38 JamBox kernel: [   19.895208] IR RC6 protocol handler
initialized
Oct 29 01:06:38 JamBox kernel: [   20.004121] IR JVC protocol handler
initialized
Oct 29 01:06:38 JamBox kernel: [   20.046349] IR Sony protocol handler
initialized
Oct 29 01:06:38 JamBox kernel: [   20.243622] IR LIRC bridge handler
initialized

syslog reports:
Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: accepted new client
on /var/run/lirc/lircd
Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: could not get file
information for /dev/lirc0
Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: default_init(): No such
file or directory
Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: Failed to initialize
hardware
Oct 29 01:07:21 JamBox lircd-0.8.7-pre3[1087]: removed client



As can be seen there is no /dev/lirc0

Using modprobe -l I can see the driver loaded but cannot remove it with
modprobe -r.  When attempting to remove the driver there are no errors
on stdout/err nor is there any information in the logs.

I have tried enabling debug output by echoing out to /proc/.../printk
and SIGHUPing rsyslogd but again nothing.

By now you have rightly guessed I am a noob at this sort of thing but I
want to bottom this out.  Can you tell me how I can get more debug
information to find a fix for this?

Martin
Jarod Wilson 1288317093Fri, 29 Oct 2010 01:51:33 +0000 (UTC)
On Thu, Oct 28, 2010 at 9:24 PM, Martin Bunyard
 wrote:
> Hi,
>
> I have tried testing the recent Nuvoton driver on an Asrock A330ION mobo
> (http://www.asrock.com/mb/overview.asp?Model=A...) with Mythbuntu
> 10.10 using the instructions in
> http://ubuntuforums.org/showthread.php?t=1596...
>
> In overview: I have built a new kernel (based on 2.6.35.22) with the
> nuvoton-cir driver patch, configured lirc files and booted into the new
> kernel.
>
> kern.log reports:
> Oct 29 01:06:37 JamBox kernel: [   19.247230] lirc_dev: IR Remote
> Control driver registered, major 250
> Oct 29 01:06:38 JamBox kernel: [   19.604228] IR NEC protocol handler
> initialized
> Oct 29 01:06:38 JamBox kernel: [   19.667421] IR RC5(x) protocol handler
> initialized
> Oct 29 01:06:38 JamBox kernel: [   19.895208] IR RC6 protocol handler
> initialized
> Oct 29 01:06:38 JamBox kernel: [   20.004121] IR JVC protocol handler
> initialized
> Oct 29 01:06:38 JamBox kernel: [   20.046349] IR Sony protocol handler
> initialized
> Oct 29 01:06:38 JamBox kernel: [   20.243622] IR LIRC bridge handler
> initialized
>
> syslog reports:
> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: accepted new client
> on /var/run/lirc/lircd
> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: could not get file
> information for /dev/lirc0
> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: default_init(): No such
> file or directory
> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: Failed to initialize
> hardware
> Oct 29 01:07:21 JamBox lircd-0.8.7-pre3[1087]: removed client
>
>
>
> As can be seen there is no /dev/lirc0There's no evidence there that the nuvoton-cir driver found anything
to bind to, which would certainly explain why you have no /dev/lirc0.
Check through the output of lspnp and/or lshal for pnp ids of either
WEC0530 or NTN0530. If neither are present, that would explain why the
driver isn't binding. If that's indeed the case, you've either got a
different pnp id, that might be added to the driver and it'd magically
Just Work, or perhaps you do have the same pnp id, but its not
exposed, because the IR part is disabled in your bios.-- 
Jarod Wilson
Martin Bunyard 1288742020Tue, 02 Nov 2010 23:53:40 +0000 (UTC)
On Thu, 2010-10-28 at 21:49 -0400, Jarod Wilson wrote:
> On Thu, Oct 28, 2010 at 9:24 PM, Martin Bunyard
>  wrote:
> > Hi,
> >
> > I have tried testing the recent Nuvoton driver on an Asrock A330ION mobo
> > (http://www.asrock.com/mb/overview.asp?Model=A...) with Mythbuntu
> > 10.10 using the instructions in
> > http://ubuntuforums.org/showthread.php?t=1596...
> >
> > In overview: I have built a new kernel (based on 2.6.35.22) with the
> > nuvoton-cir driver patch, configured lirc files and booted into the new
> > kernel.
> >
> > kern.log reports:
> > Oct 29 01:06:37 JamBox kernel: [   19.247230] lirc_dev: IR Remote
> > Control driver registered, major 250
> > Oct 29 01:06:38 JamBox kernel: [   19.604228] IR NEC protocol handler
> > initialized
> > Oct 29 01:06:38 JamBox kernel: [   19.667421] IR RC5(x) protocol handler
> > initialized
> > Oct 29 01:06:38 JamBox kernel: [   19.895208] IR RC6 protocol handler
> > initialized
> > Oct 29 01:06:38 JamBox kernel: [   20.004121] IR JVC protocol handler
> > initialized
> > Oct 29 01:06:38 JamBox kernel: [   20.046349] IR Sony protocol handler
> > initialized
> > Oct 29 01:06:38 JamBox kernel: [   20.243622] IR LIRC bridge handler
> > initialized
> >
> > syslog reports:
> > Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: accepted new client
> > on /var/run/lirc/lircd
> > Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: could not get file
> > information for /dev/lirc0
> > Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: default_init(): No such
> > file or directory
> > Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: Failed to initialize
> > hardware
> > Oct 29 01:07:21 JamBox lircd-0.8.7-pre3[1087]: removed client
> >
> >
> >
> > As can be seen there is no /dev/lirc0
> 
> There's no evidence there that the nuvoton-cir driver found anything
> to bind to, which would certainly explain why you have no /dev/lirc0.
> Check through the output of lspnp and/or lshal for pnp ids of either
> WEC0530 or NTN0530. If neither are present, that would explain why the
> driver isn't binding. If that's indeed the case, you've either got a
> different pnp id, that might be added to the driver and it'd magically
> Just Work, or perhaps you do have the same pnp id, but its not
> exposed, because the IR part is disabled in your bios.
>Well I have found that the pnp id is different for this motherboard.

lshal shows:

udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Generic IRDA-compatible device'  (string)
  info.subsystem = 'pnp'  (string)
  info.udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'pnp'  (string)
  linux.sysfs_path = '/sys/devices/pnp0/00:09'  (string)
  pnp.description = 'Generic IRDA-compatible device'  (string)
  pnp.id = 'PNP0510'  (string)

I added PNP0510 to pnp_device_id (in nuvoton-cir.c) in the same style as
the other pnp ids but am now confronted with another error.

dmesg shows:

[    6.921771] nuvoton-cir 00:09: IR PNP Port not valid!
[    6.922984] nuvoton-cir 00:09: disabled

I took this to mean that the relevant port address had already been
allocated to another device.  The BIOS is configured to allocate
IRQ3/02f8 for the IR device so I checked in dmesg which shows:

[    0.994658] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    0.994829] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[    0.995410] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

Which seems to demonstrate a Before and After setserial configuration
(as per my /etc/serial.conf).  
In other words ttyS1 was allocated to the relevant irq and port but was
then de-allocated as I intended.  I have fiddled around
with /etc/serial.conf even to the point of assigning dummy port
addresses in the hope that this would release 0x02f8 but to no avail.

The BIOS does not help by forcing the IR device to take on the same
irq/port as a typical COM port (COM1 to COM4).

Perhaps I am 'barking up the wrong tree', can you help?

Martin
Jarod Wilson 1288761807Wed, 03 Nov 2010 05:23:27 +0000 (UTC)
On Nov 2, 2010, at 7:51 PM, Martin Bunyard wrote:

> On Thu, 2010-10-28 at 21:49 -0400, Jarod Wilson wrote:
>> On Thu, Oct 28, 2010 at 9:24 PM, Martin Bunyard
>>  wrote:
>>> Hi,
>>> 
>>> I have tried testing the recent Nuvoton driver on an Asrock A330ION mobo
>>> (http://www.asrock.com/mb/overview.asp?Model=A...) with Mythbuntu
>>> 10.10 using the instructions in
>>> http://ubuntuforums.org/showthread.php?t=1596...
>>> 
>>> In overview: I have built a new kernel (based on 2.6.35.22) with the
>>> nuvoton-cir driver patch, configured lirc files and booted into the new
>>> kernel.
>>> 
>>> kern.log reports:
>>> Oct 29 01:06:37 JamBox kernel: [   19.247230] lirc_dev: IR Remote
>>> Control driver registered, major 250
>>> Oct 29 01:06:38 JamBox kernel: [   19.604228] IR NEC protocol handler
>>> initialized
>>> Oct 29 01:06:38 JamBox kernel: [   19.667421] IR RC5(x) protocol handler
>>> initialized
>>> Oct 29 01:06:38 JamBox kernel: [   19.895208] IR RC6 protocol handler
>>> initialized
>>> Oct 29 01:06:38 JamBox kernel: [   20.004121] IR JVC protocol handler
>>> initialized
>>> Oct 29 01:06:38 JamBox kernel: [   20.046349] IR Sony protocol handler
>>> initialized
>>> Oct 29 01:06:38 JamBox kernel: [   20.243622] IR LIRC bridge handler
>>> initialized
>>> 
>>> syslog reports:
>>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: accepted new client
>>> on /var/run/lirc/lircd
>>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: could not get file
>>> information for /dev/lirc0
>>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: default_init(): No such
>>> file or directory
>>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: Failed to initialize
>>> hardware
>>> Oct 29 01:07:21 JamBox lircd-0.8.7-pre3[1087]: removed client
>>> 
>>> 
>>> 
>>> As can be seen there is no /dev/lirc0
>> 
>> There's no evidence there that the nuvoton-cir driver found anything
>> to bind to, which would certainly explain why you have no /dev/lirc0.
>> Check through the output of lspnp and/or lshal for pnp ids of either
>> WEC0530 or NTN0530. If neither are present, that would explain why the
>> driver isn't binding. If that's indeed the case, you've either got a
>> different pnp id, that might be added to the driver and it'd magically
>> Just Work, or perhaps you do have the same pnp id, but its not
>> exposed, because the IR part is disabled in your bios.
>> 
> 
> Well I have found that the pnp id is different for this motherboard.
> 
> lshal shows:
> 
> udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'
>  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
>  info.product = 'Generic IRDA-compatible device'  (string)
>  info.subsystem = 'pnp'  (string)
>  info.udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'  (string)
>  linux.hotplug_type = 2  (0x2)  (int)
>  linux.subsystem = 'pnp'  (string)
>  linux.sysfs_path = '/sys/devices/pnp0/00:09'  (string)
>  pnp.description = 'Generic IRDA-compatible device'  (string)
>  pnp.id = 'PNP0510'  (string)
> 
> I added PNP0510 to pnp_device_id (in nuvoton-cir.c) in the same style as
> the other pnp ids but am now confronted with another error.That's not a Consumer IR device, its an IrDA device, which is something different.> dmesg shows:
> 
> [    6.921771] nuvoton-cir 00:09: IR PNP Port not valid!
> [    6.922984] nuvoton-cir 00:09: disabled
> 
> I took this to mean that the relevant port address had already been
> allocated to another device.  The BIOS is configured to allocate
> IRQ3/02f8 for the IR device so I checked in dmesg which shows:
> 
> [    0.994658] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [    0.994829] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [    0.995410] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 
> Which seems to demonstrate a Before and After setserial configuration
> (as per my /etc/serial.conf).  
> In other words ttyS1 was allocated to the relevant irq and port but was
> then de-allocated as I intended.  I have fiddled around
> with /etc/serial.conf even to the point of assigning dummy port
> addresses in the hope that this would release 0x02f8 but to no avail.
> 
> The BIOS does not help by forcing the IR device to take on the same
> irq/port as a typical COM port (COM1 to COM4).
> 
> Perhaps I am 'barking up the wrong tree', can you help?Unfortunately, it sounds like you're out of luck and you don't actually have the CIR bits available on your board. Or does your bios perhaps give you the ability to specify CIR instead of IrDA?

Also, can you confirm exactly what model of Nuvoton chip you have on your board? Might be able to dig up some further information in the documentation...-- 
Jarod Wilson
Martin Bunyard 1288822887Wed, 03 Nov 2010 22:21:27 +0000 (UTC)
On Wed, 2010-11-03 at 01:20 -0400, Jarod Wilson wrote:
> On Nov 2, 2010, at 7:51 PM, Martin Bunyard wrote:
> 
> > On Thu, 2010-10-28 at 21:49 -0400, Jarod Wilson wrote:
> >> On Thu, Oct 28, 2010 at 9:24 PM, Martin Bunyard
> >>  wrote:
> >>> Hi,
> >>> 
> >>> I have tried testing the recent Nuvoton driver on an Asrock A330ION mobo
> >>> (http://www.asrock.com/mb/overview.asp?Model=A...) with Mythbuntu
> >>> 10.10 using the instructions in
> >>> http://ubuntuforums.org/showthread.php?t=1596...
> >>> 
> >>> In overview: I have built a new kernel (based on 2.6.35.22) with the
> >>> nuvoton-cir driver patch, configured lirc files and booted into the new
> >>> kernel.
> >>> 
> >>> kern.log reports:
> >>> Oct 29 01:06:37 JamBox kernel: [   19.247230] lirc_dev: IR Remote
> >>> Control driver registered, major 250
> >>> Oct 29 01:06:38 JamBox kernel: [   19.604228] IR NEC protocol handler
> >>> initialized
> >>> Oct 29 01:06:38 JamBox kernel: [   19.667421] IR RC5(x) protocol handler
> >>> initialized
> >>> Oct 29 01:06:38 JamBox kernel: [   19.895208] IR RC6 protocol handler
> >>> initialized
> >>> Oct 29 01:06:38 JamBox kernel: [   20.004121] IR JVC protocol handler
> >>> initialized
> >>> Oct 29 01:06:38 JamBox kernel: [   20.046349] IR Sony protocol handler
> >>> initialized
> >>> Oct 29 01:06:38 JamBox kernel: [   20.243622] IR LIRC bridge handler
> >>> initialized
> >>> 
> >>> syslog reports:
> >>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: accepted new client
> >>> on /var/run/lirc/lircd
> >>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: could not get file
> >>> information for /dev/lirc0
> >>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: default_init(): No such
> >>> file or directory
> >>> Oct 29 01:07:12 JamBox lircd-0.8.7-pre3[1087]: Failed to initialize
> >>> hardware
> >>> Oct 29 01:07:21 JamBox lircd-0.8.7-pre3[1087]: removed client
> >>> 
> >>> 
> >>> 
> >>> As can be seen there is no /dev/lirc0
> >> 
> >> There's no evidence there that the nuvoton-cir driver found anything
> >> to bind to, which would certainly explain why you have no /dev/lirc0.
> >> Check through the output of lspnp and/or lshal for pnp ids of either
> >> WEC0530 or NTN0530. If neither are present, that would explain why the
> >> driver isn't binding. If that's indeed the case, you've either got a
> >> different pnp id, that might be added to the driver and it'd magically
> >> Just Work, or perhaps you do have the same pnp id, but its not
> >> exposed, because the IR part is disabled in your bios.
> >> 
> > 
> > Well I have found that the pnp id is different for this motherboard.
> > 
> > lshal shows:
> > 
> > udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'
> >  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
> >  info.product = 'Generic IRDA-compatible device'  (string)
> >  info.subsystem = 'pnp'  (string)
> >  info.udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'  (string)
> >  linux.hotplug_type = 2  (0x2)  (int)
> >  linux.subsystem = 'pnp'  (string)
> >  linux.sysfs_path = '/sys/devices/pnp0/00:09'  (string)
> >  pnp.description = 'Generic IRDA-compatible device'  (string)
> >  pnp.id = 'PNP0510'  (string)
> > 
> > I added PNP0510 to pnp_device_id (in nuvoton-cir.c) in the same style as
> > the other pnp ids but am now confronted with another error.
> 
> That's not a Consumer IR device, its an IrDA device, which is something different.
> 
> 
> > dmesg shows:
> > 
> > [    6.921771] nuvoton-cir 00:09: IR PNP Port not valid!
> > [    6.922984] nuvoton-cir 00:09: disabled
> > 
> > I took this to mean that the relevant port address had already been
> > allocated to another device.  The BIOS is configured to allocate
> > IRQ3/02f8 for the IR device so I checked in dmesg which shows:
> > 
> > [    0.994658] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > [    0.994829] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> > [    0.995410] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > 
> > Which seems to demonstrate a Before and After setserial configuration
> > (as per my /etc/serial.conf).  
> > In other words ttyS1 was allocated to the relevant irq and port but was
> > then de-allocated as I intended.  I have fiddled around
> > with /etc/serial.conf even to the point of assigning dummy port
> > addresses in the hope that this would release 0x02f8 but to no avail.
> > 
> > The BIOS does not help by forcing the IR device to take on the same
> > irq/port as a typical COM port (COM1 to COM4).
> > 
> > Perhaps I am 'barking up the wrong tree', can you help?
> 
> Unfortunately, it sounds like you're out of luck and you don't actually have the CIR bits available on your board. Or does your bios perhaps give you the ability to specify CIR instead of IrDA?
> 
> Also, can you confirm exactly what model of Nuvoton chip you have on your board? Might be able to dig up some further information in the documentation...
>So I have had a look at the board and there quite clearly is:
    Nuvoton
    NCT6775F
    937G9B2936B013-ZXFB

I'd be very interested to hear what you find out.

Thanks for your time,

Martin
Jarod Wilson 1289251596Mon, 08 Nov 2010 21:26:36 +0000 (UTC)
On Nov 3, 2010, at 6:19 PM, Martin Bunyard wrote:

> On Wed, 2010-11-03 at 01:20 -0400, Jarod Wilson wrote:
>> On Nov 2, 2010, at 7:51 PM, Martin Bunyard wrote:
>> 
>>> On Thu, 2010-10-28 at 21:49 -0400, Jarod Wilson wrote:
>>>> On Thu, Oct 28, 2010 at 9:24 PM, Martin Bunyard
>>>>  wrote:>>>> On Thu, Oct 28, 2010 at 9:24 PM, Martin Bunyard
>>>>  wrote:
...
>>>>> As can be seen there is no /dev/lirc0
>>>> 
>>>> There's no evidence there that the nuvoton-cir driver found anything
>>>> to bind to, which would certainly explain why you have no /dev/lirc0.
>>>> Check through the output of lspnp and/or lshal for pnp ids of either
>>>> WEC0530 or NTN0530. If neither are present, that would explain why the
>>>> driver isn't binding. If that's indeed the case, you've either got a
>>>> different pnp id, that might be added to the driver and it'd magically
>>>> Just Work, or perhaps you do have the same pnp id, but its not
>>>> exposed, because the IR part is disabled in your bios.
>>>> 
>>> 
>>> Well I have found that the pnp id is different for this motherboard.
>>> 
>>> lshal shows:
>>> 
>>> udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'
>>> info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
>>> info.product = 'Generic IRDA-compatible device'  (string)
>>> info.subsystem = 'pnp'  (string)
>>> info.udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'  (string)
>>> linux.hotplug_type = 2  (0x2)  (int)
>>> linux.subsystem = 'pnp'  (string)
>>> linux.sysfs_path = '/sys/devices/pnp0/00:09'  (string)
>>> pnp.description = 'Generic IRDA-compatible device'  (string)
>>> pnp.id = 'PNP0510'  (string)
>>> 
>>> I added PNP0510 to pnp_device_id (in nuvoton-cir.c) in the same style as
>>> the other pnp ids but am now confronted with another error.
>> 
>> That's not a Consumer IR device, its an IrDA device, which is something different.
>> 
>> 
>>> dmesg shows:
>>> 
>>> [    6.921771] nuvoton-cir 00:09: IR PNP Port not valid!
>>> [    6.922984] nuvoton-cir 00:09: disabled
>>> 
>>> I took this to mean that the relevant port address had already been
>>> allocated to another device.  The BIOS is configured to allocate
>>> IRQ3/02f8 for the IR device so I checked in dmesg which shows:
>>> 
>>> [    0.994658] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>>> [    0.994829] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>>> [    0.995410] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>>> 
>>> Which seems to demonstrate a Before and After setserial configuration
>>> (as per my /etc/serial.conf).  
>>> In other words ttyS1 was allocated to the relevant irq and port but was
>>> then de-allocated as I intended.  I have fiddled around
>>> with /etc/serial.conf even to the point of assigning dummy port
>>> addresses in the hope that this would release 0x02f8 but to no avail.
>>> 
>>> The BIOS does not help by forcing the IR device to take on the same
>>> irq/port as a typical COM port (COM1 to COM4).
>>> 
>>> Perhaps I am 'barking up the wrong tree', can you help?
>> 
>> Unfortunately, it sounds like you're out of luck and you don't actually have the CIR bits available on your board. Or does your bios perhaps give you the ability to specify CIR instead of IrDA?
>> 
>> Also, can you confirm exactly what model of Nuvoton chip you have on your board? Might be able to dig up some further information in the documentation...
>> 
> 
> So I have had a look at the board and there quite clearly is:
>    Nuvoton
>    NCT6775F
>    937G9B2936B013-ZXFB
> 
> I'd be very interested to hear what you find out.Definitely looks to be the same chip as in the asrock ion330 kit, and I see actual evidence its supposed to have functional cir support. Unless there's an option somewhere in the bios to select between irda and cir though, I'm out of ideas where to look.
Martin Bunyard 1289515961Thu, 11 Nov 2010 22:52:41 +0000 (UTC)
On Mon, 2010-11-08 at 16:22 -0500, Jarod Wilson wrote:
> On Nov 3, 2010, at 6:19 PM, Martin Bunyard wrote:
> 
> > On Wed, 2010-11-03 at 01:20 -0400, Jarod Wilson wrote:
> > > On Nov 2, 2010, at 7:51 PM, Martin Bunyard wrote:
> > > 
> > > > On Thu, 2010-10-28 at 21:49 -0400, Jarod Wilson wrote:
> > > > > On Thu, Oct 28, 2010 at 9:24 PM, Martin Bunyard
> > > > >  wrote:
> ...
> > > > > > As can be seen there is no /dev/lirc0
> > > > > 
> > > > > There's no evidence there that the nuvoton-cir driver found
> > > > > anything
> > > > > to bind to, which would certainly explain why you have
> > > > > no /dev/lirc0.
> > > > > Check through the output of lspnp and/or lshal for pnp ids of
> > > > > either
> > > > > WEC0530 or NTN0530. If neither are present, that would explain
> > > > > why the
> > > > > driver isn't binding. If that's indeed the case, you've either
> > > > > got a
> > > > > different pnp id, that might be added to the driver and it'd
> > > > > magically
> > > > > Just Work, or perhaps you do have the same pnp id, but its not
> > > > > exposed, because the IR part is disabled in your bios.
> > > > > 
> > > > 
> > > > Well I have found that the pnp id is different for this
> > > > motherboard.
> > > > 
> > > > lshal shows:
> > > > 
> > > > udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'
> > > > info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
> > > > info.product = 'Generic IRDA-compatible device'  (string)
> > > > info.subsystem = 'pnp'  (string)
> > > > info.udi = '/org/freedesktop/Hal/devices/pnp_PNP0510'  (string)
> > > > linux.hotplug_type = 2  (0x2)  (int)
> > > > linux.subsystem = 'pnp'  (string)
> > > > linux.sysfs_path = '/sys/devices/pnp0/00:09'  (string)
> > > > pnp.description = 'Generic IRDA-compatible device'  (string)
> > > > pnp.id = 'PNP0510'  (string)
> > > > 
> > > > I added PNP0510 to pnp_device_id (in nuvoton-cir.c) in the same
> > > > style as
> > > > the other pnp ids but am now confronted with another error.
> > > 
> > > That's not a Consumer IR device, its an IrDA device, which is
> > > something different.
> > > 
> > > 
> > > > dmesg shows:
> > > > 
> > > > [    6.921771] nuvoton-cir 00:09: IR PNP Port not valid!
> > > > [    6.922984] nuvoton-cir 00:09: disabled
> > > > 
> > > > I took this to mean that the relevant port address had already
> > > > been
> > > > allocated to another device.  The BIOS is configured to allocate
> > > > IRQ3/02f8 for the IR device so I checked in dmesg which shows:
> > > > 
> > > > [    0.994658] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a
> > > > 16550A
> > > > [    0.994829] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a
> > > > 16550A
> > > > [    0.995410] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > > > 
> > > > Which seems to demonstrate a Before and After setserial
> > > > configuration
> > > > (as per my /etc/serial.conf).  
> > > > In other words ttyS1 was allocated to the relevant irq and port
> > > > but was
> > > > then de-allocated as I intended.  I have fiddled around
> > > > with /etc/serial.conf even to the point of assigning dummy port
> > > > addresses in the hope that this would release 0x02f8 but to no
> > > > avail.
> > > > 
> > > > The BIOS does not help by forcing the IR device to take on the
> > > > same
> > > > irq/port as a typical COM port (COM1 to COM4).
> > > > 
> > > > Perhaps I am 'barking up the wrong tree', can you help?
> > > 
> > > Unfortunately, it sounds like you're out of luck and you don't
> > > actually have the CIR bits available on your board. Or does your
> > > bios perhaps give you the ability to specify CIR instead of IrDA?
> > > 
> > > Also, can you confirm exactly what model of Nuvoton chip you have
> > > on your board? Might be able to dig up some further information in
> > > the documentation...
> > > 
> > 
> > So I have had a look at the board and there quite clearly is:
> >    Nuvoton
> >    NCT6775F
> >    937G9B2936B013-ZXFB
> > 
> > I'd be very interested to hear what you find out.
> 
> 
> Definitely looks to be the same chip as in the asrock ion330 kit, and
> I see actual evidence its supposed to have functional cir support.
> Unless there's an option somewhere in the bios to select between irda
> and cir though, I'm out of ideas where to look.
> 
> -- 
> Jarod Wilson
> 
> 
> 
> 
> 
>I have checked out the BIOS and there is no option to switch between
IRDA and CIR.

As I have mentioned before the IR configuration in the BIOS only allows
for changing of the port/IRQ parameters which correspond to COM1 to
COM4.

I have experimented with cycling through these while looking at the
output of lshal to see if there are any significant changes.

Each time I change the IR parameters lshal shows a serial device that
corresponds to these changes.  So setting the IR device to 02e8/IRQ3
(i.e. COM4) results in:

udi =
'/org/freedesktop/Hal/devices/platform_serial8250_serial_platform_3'
  info.capabilities = {'serial'} (string list)
  info.category = 'serial'  (string)
  info.parent = '/org/freedesktop/Hal/devices/platform_serial8250'
(string)
  info.product = 'Platform Device (serial8250)'  (string)
  info.subsystem = 'tty'  (string)
  info.udi =
'/org/freedesktop/Hal/devices/platform_serial8250_serial_platform_3'
(string)
  linux.device_file = '/dev/ttyS3'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'tty'  (string)
  linux.sysfs_path = '/sys/devices/platform/serial8250/tty/ttyS3'
(string)
  serial.device = '/dev/ttyS3'  (string)
  serial.originating_device =
'/org/freedesktop/Hal/devices/platform_serial8250'  (string)
  serial.port = 3  (0x3)  (int)
  serial.type = 'platform'  (string)

If I were to change the port/IRQ parameters as per COM1, then the lshal
output would be the same but all the 3's would be 0's.

Am I right in thinking that HAL is wrongly identifying the IR device as
a serial device - could this be where the root cause is?

If not the only option left to me is to chase Asrock Support - I dont
hold much hope though.

Martin
Jarod Wilson 1289519679Thu, 11 Nov 2010 23:54:39 +0000 (UTC)
On Thu, Nov 11, 2010 at 5:50 PM, Martin Bunyard
 wrote:
> On Mon, 2010-11-08 at 16:22 -0500, Jarod Wilson wrote:
>> On Nov 3, 2010, at 6:19 PM, Martin Bunyard wrote:> On Mon, 2010-11-08 at 16:22 -0500, Jarod Wilson wrote:
>> On Nov 3, 2010, at 6:19 PM, Martin Bunyard wrote:
...
>> > > Unfortunately, it sounds like you're out of luck and you don't
>> > > actually have the CIR bits available on your board. Or does your
>> > > bios perhaps give you the ability to specify CIR instead of IrDA?
>> > >
>> > > Also, can you confirm exactly what model of Nuvoton chip you have
>> > > on your board? Might be able to dig up some further information in
>> > > the documentation...
>> > >
>> >
>> > So I have had a look at the board and there quite clearly is:
>> >    Nuvoton
>> >    NCT6775F
>> >    937G9B2936B013-ZXFB
>> >
>> > I'd be very interested to hear what you find out.
>>
>>
>> Definitely looks to be the same chip as in the asrock ion330 kit, and
>> I see actual evidence its supposed to have functional cir support.
>> Unless there's an option somewhere in the bios to select between irda
>> and cir though, I'm out of ideas where to look.
>>
>
> I have checked out the BIOS and there is no option to switch between
> IRDA and CIR.
>
> As I have mentioned before the IR configuration in the BIOS only allows
> for changing of the port/IRQ parameters which correspond to COM1 to
> COM4.
>
> I have experimented with cycling through these while looking at the
> output of lshal to see if there are any significant changes.
>
> Each time I change the IR parameters lshal shows a serial device that
> corresponds to these changes.  So setting the IR device to 02e8/IRQ3
> (i.e. COM4) results in:
>
> udi =
> '/org/freedesktop/Hal/devices/platform_serial8250_serial_platform_3'
>  info.capabilities = {'serial'} (string list)
>  info.category = 'serial'  (string)
>  info.parent = '/org/freedesktop/Hal/devices/platform_serial8250'
> (string)
>  info.product = 'Platform Device (serial8250)'  (string)
>  info.subsystem = 'tty'  (string)
>  info.udi =
> '/org/freedesktop/Hal/devices/platform_serial8250_serial_platform_3'
> (string)
>  linux.device_file = '/dev/ttyS3'  (string)
>  linux.hotplug_type = 2  (0x2)  (int)
>  linux.subsystem = 'tty'  (string)
>  linux.sysfs_path = '/sys/devices/platform/serial8250/tty/ttyS3'
> (string)
>  serial.device = '/dev/ttyS3'  (string)
>  serial.originating_device =
> '/org/freedesktop/Hal/devices/platform_serial8250'  (string)
>  serial.port = 3  (0x3)  (int)
>  serial.type = 'platform'  (string)
>
> If I were to change the port/IRQ parameters as per COM1, then the lshal
> output would be the same but all the 3's would be 0's.
>
> Am I right in thinking that HAL is wrongly identifying the IR device as
> a serial device - could this be where the root cause is?Seems unlikely, but maybe. On the board itself... Is there a header
marked CIR or similar, and does it have anything wired up to it? The
most likely thing at this point still seems to be that yes, you have
the same super i/o chip as the asrock ion330 ht boxes, but the CIR
logical device in it isn't enabled.

Now that I think about it... I have an asrock ion330 pro, which comes
w/o any advertised IR support, and its definitely got the same super
i/o chip. I'll have to poke at it some and see if I can see anything
interesting there. I think the board even has a CIR header, but I see
zero evidence of the PNP device on that system as well, and don't
recall anything in the bios that would let me enable it...> If not the only option left to me is to chase Asrock Support - I dont
> hold much hope though.Install Windows, see if it works there?-- 
Jarod Wilson
Martin Bunyard 1289734546Sun, 14 Nov 2010 11:35:46 +0000 (UTC)
On Thu, 2010-11-11 at 18:52 -0500, Jarod Wilson wrote:
> On Thu, Nov 11, 2010 at 5:50 PM, Martin Bunyard
>  wrote:
> > On Mon, 2010-11-08 at 16:22 -0500, Jarod Wilson wrote:
> >> On Nov 3, 2010, at 6:19 PM, Martin Bunyard wrote:
> ...
> >> > > Unfortunately, it sounds like you're out of luck and you don't
> >> > > actually have the CIR bits available on your board. Or does your
> >> > > bios perhaps give you the ability to specify CIR instead of IrDA?
> >> > >
> >> > > Also, can you confirm exactly what model of Nuvoton chip you have
> >> > > on your board? Might be able to dig up some further information in
> >> > > the documentation...
> >> > >
> >> >
> >> > So I have had a look at the board and there quite clearly is:
> >> >    Nuvoton
> >> >    NCT6775F
> >> >    937G9B2936B013-ZXFB
> >> >
> >> > I'd be very interested to hear what you find out.
> >>
> >>
> >> Definitely looks to be the same chip as in the asrock ion330 kit, and
> >> I see actual evidence its supposed to have functional cir support.
> >> Unless there's an option somewhere in the bios to select between irda
> >> and cir though, I'm out of ideas where to look.
> >>
> >
> > I have checked out the BIOS and there is no option to switch between
> > IRDA and CIR.
> >
> > As I have mentioned before the IR configuration in the BIOS only allows
> > for changing of the port/IRQ parameters which correspond to COM1 to
> > COM4.
> >
> > I have experimented with cycling through these while looking at the
> > output of lshal to see if there are any significant changes.
> >
> > Each time I change the IR parameters lshal shows a serial device that
> > corresponds to these changes.  So setting the IR device to 02e8/IRQ3
> > (i.e. COM4) results in:
> >
> > udi =
> > '/org/freedesktop/Hal/devices/platform_serial8250_serial_platform_3'
> >  info.capabilities = {'serial'} (string list)
> >  info.category = 'serial'  (string)
> >  info.parent = '/org/freedesktop/Hal/devices/platform_serial8250'
> > (string)
> >  info.product = 'Platform Device (serial8250)'  (string)
> >  info.subsystem = 'tty'  (string)
> >  info.udi =
> > '/org/freedesktop/Hal/devices/platform_serial8250_serial_platform_3'
> > (string)
> >  linux.device_file = '/dev/ttyS3'  (string)
> >  linux.hotplug_type = 2  (0x2)  (int)
> >  linux.subsystem = 'tty'  (string)
> >  linux.sysfs_path = '/sys/devices/platform/serial8250/tty/ttyS3'
> > (string)
> >  serial.device = '/dev/ttyS3'  (string)
> >  serial.originating_device =
> > '/org/freedesktop/Hal/devices/platform_serial8250'  (string)
> >  serial.port = 3  (0x3)  (int)
> >  serial.type = 'platform'  (string)
> >
> > If I were to change the port/IRQ parameters as per COM1, then the lshal
> > output would be the same but all the 3's would be 0's.
> >
> > Am I right in thinking that HAL is wrongly identifying the IR device as
> > a serial device - could this be where the root cause is?
> 
> Seems unlikely, but maybe. On the board itself... Is there a header
> marked CIR or similar, and does it have anything wired up to it?Yes, there is a header present and marked as IR 1.  The documentation
describes this as a 'Infrared Module Header' and identifies the pins as:
 1 - IRRX
 2 - GND
 3 - <Pin removed>
 4 - IRTX
 5 - +5
 6 - Dummy

I have put a meter on the pins:

Gnd to +5 is: 5.19v
Gnd to IRTX is: 0.00v
Gnd to IRRX is: 0.79v

So I guess we have connectivity of some sort.> The
> most likely thing at this point still seems to be that yes, you have
> the same super i/o chip as the asrock ion330 ht boxes, but the CIR
> logical device in it isn't enabled.
> 
> Now that I think about it... I have an asrock ion330 pro, which comes
> w/o any advertised IR support, and its definitely got the same super
> i/o chip. I'll have to poke at it some and see if I can see anything
> interesting there. I think the board even has a CIR header, but I see
> zero evidence of the PNP device on that system as well, and don't
> recall anything in the bios that would let me enable it...
> 
> > If not the only option left to me is to chase Asrock Support - I dont
> > hold much hope though.
> 
> Install Windows, see if it works there?
>I'll have a rummage for a Windows disk...

Martin
Home | About | Privacy