irda-utils error when starting the initscript

Bug #121371 reported by idokibovito
12
Affects Status Importance Assigned to Milestone
irda-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

First of all, this worked in edgy, so that can be a starting point to devs.

I noticed my IRDA doesn't work on the freshly installed feisty.
I load the needed module, then "/etc/init.d/irda-utils restart" and dmesg shows this:

---start of dmesg---
Jun 20 18:10:34 domination irattach: executing: '/sbin/modprobe irda0'
Jun 20 18:10:34 domination irattach: + FATAL: Module irda0 not found.
Jun 20 18:10:34 domination irattach: Trying to load module irda0 exited with status 1
Jun 20 18:10:34 domination irattach: executing: 'echo domination > /proc/sys/net/irda/devname'
Jun 20 18:10:34 domination irattach: executing: 'echo 1 > /proc/sys/net/irda/discovery'
Jun 20 18:10:34 domination irattach: Starting device irda0
Jun 20 18:10:34 domination kernel: [67269.464000] [setup_irq+302/480] setup_irq+0x12e/0x1e0
Jun 20 18:10:34 domination kernel: [67269.464000] [<f8e982c0>] smsc_ircc_interrupt+0x0/0x7d0 [smsc_ircc2]
Jun 20 18:10:34 domination kernel: [67269.464000] [request_irq+163/192] request_irq+0xa3/0xc0
Jun 20 18:10:34 domination kernel: [67269.464000] [<f8e97bef>] smsc_ircc_net_open+0x4f/0x1c0 [smsc_ircc2]
Jun 20 18:10:34 domination kernel: [67269.464000] [find_get_page+32/96] find_get_page+0x20/0x60
Jun 20 18:10:34 domination kernel: [67269.464000] [filemap_nopage+753/928] filemap_nopage+0x2f1/0x3a0
Jun 20 18:10:34 domination kernel: [67269.464000] [dev_open+49/112] dev_open+0x31/0x70
Jun 20 18:10:34 domination kernel: [67269.464000] [dev_change_flags+252/304] dev_change_flags+0xfc/0x130
Jun 20 18:10:34 domination kernel: [67269.464000] [sock_ioctl+0/528] sock_ioctl+0x0/0x210
Jun 20 18:10:34 domination kernel: [67269.464000] [dev_ioctl+611/896] dev_ioctl+0x263/0x380
Jun 20 18:10:34 domination kernel: [67269.464000] [sock_attach_fd+112/208] sock_attach_fd+0x70/0xd0
Jun 20 18:10:34 domination kernel: [67269.464000] [sock_ioctl+191/528] sock_ioctl+0xbf/0x210
Jun 20 18:10:34 domination kernel: [67269.464000] [sock_ioctl+0/528] sock_ioctl+0x0/0x210
Jun 20 18:10:34 domination kernel: [67269.464000] [do_ioctl+43/144] do_ioctl+0x2b/0x90
Jun 20 18:10:34 domination kernel: [67269.464000] [vfs_ioctl+92/672] vfs_ioctl+0x5c/0x2a0
Jun 20 18:10:34 domination kernel: [67269.464000] [sys_ioctl+114/144] sys_ioctl+0x72/0x90
Jun 20 18:10:34 domination kernel: [67269.464000] [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9
Jun 20 18:10:34 domination kernel: [67269.464000] =======================
Jun 20 18:10:34 domination irattach: ioctl(SIOCSIFFLAGS): Resource temporarily unavailable
Jun 20 18:10:34 domination irattach: Stopping device irda0
Jun 20 18:10:34 domination irattach: exiting ...
---end of dmesg---

The strange thing is that it tries to load the module irda0 which doesn't exist, that would be the network interface if this whole thing worked.

I think this is the reason why irdadump doesn't show anything when my phone is there and sending data.
Since it worked in edgy, it must be a relatively small bug somewhere.
Any idea?

Revision history for this message
Alex Midgley (alex-tapdancinggoats) wrote :

This same thing happens for me too. I'm using an HP Pavilion ZT 3000 laptop. Feisty is the first version I've tried on this laptop, so I don't know if this would have worked in Edgy.

Revision history for this message
idokibovito (idokibovito) wrote :

I can assure you that it does work in dapper and even works better in edgy. Need little tricks here and there, but it does work.

I even mailed to the mailing list to offer my help for it to work out of the box but once the mail got deleted and the other time I guess no one answered from the core team (even created packages, thought I invest a little time to help out as a MOTU or so). It's a shame nobody cares about this, even with the offered help. Now the next release is coming, and still nothing from the ubuntu guys. I was thinking about closing this bug and not care about these kind of things anymore, but if you found it Alex, it might come in handy for others too.

Let me know if you need help on this Alex (on < feisty), will try to help you.

Revision history for this message
Alex Midgley (alex-tapdancinggoats) wrote :

I got this working in Feisty for my laptop. There is a problem with the driver for my irda chip (bug 133169).

Check your syslog to see if an SMSC irda chip is detected when you boot. If it is, putting these two lines at the bottom of /etc/modprobe.d/irda-utils might solve the problem:

options smsc-ircc2 ircc_irq=4
alias irda0 smsc-ircc2

Revision history for this message
NoIdea (messerli) wrote :

I got this working in Gutsy for my laptop. There is still a problem with the driver.
I needed additionaly :
options smsc-ircc2 ircc_irq=4 ircc_sir=0x03e8
alias irda0 smsc-ircc2

Revision history for this message
xteejx (xteejx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in irda-utils (Ubuntu):
status: New → Incomplete
Revision history for this message
idokibovito (idokibovito) wrote :

Thanks for your comment Teej!
I'm sorry to see that I reported this bug 2 years ago :( Thus I have no interest on this bug anymore, nor can I help giving any more feedback since I do not own the laptop anymore.

I'm closing this bugreport
(is setting it to invalid the best thing to do?)

Changed in irda-utils (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
xteejx (xteejx) wrote :

Yes, but Alex also had the same problem. So I will re-mark this as Incomplete and see if he can provide that information. Note Dapper, and Hardy onwards are the only supported Ubuntu versions now. We would prefer you to try and reproduce this in Jaunty if possible. Thank you.

Changed in irda-utils (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Alex Midgley (alex-tapdancinggoats) wrote :

I can't help either. The last laptop I had with an IR transceiver broke last year.

Revision history for this message
xteejx (xteejx) wrote :

No worries. I shall close this bug. If you do run into this problem again, you can reopen it by changing the status back to New. Thank you.

Changed in irda-utils (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.