IRDA-Devices are not created by default (ircomm: 161-0

I confirm this.

I've installed
irda-utils 0.9.16-11ubuntu1 IrDA management and handling utilities
to use my Nokia 6100 phone as a GPRS modem.

After rebooting, no /dev/ircomm* devices where present.
I have to do after every reboot:

modprobe ircomm
sudo mknod /dev/ircomm0 c 161 0
sudo chown :dialout /dev/ircomm0
sudo chmod g+w /dev/ircomm0

After that, devices are created and everything works fine.

Please let me know if you need firther information.

ircomm module should create these devices through uevents

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/testing . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

I've just installed Hardy Heron on a Dell Latitude D420.

The /dev/ircomm* devices were indeed not created until I manually loaded ircomm and ircomm-tty.

JP

Hi jpiesing,

Can you clarify just a little more for me. After you load the ircomm and ircomm-tty modules, did you still have to do create the devices using something like 'sudo mknod /dev/ircomm0 c 161 0' or were /dev/ircomm* created for you automatically? From your comment it seems like /dev/ircomm* were created for you automatically which is what should happen.

So it would seem your issue is that you want the ircomm and ircomm-tty modules automatically loaded?

Thanks.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Testing on Intrepid Alpha 6. Originally, there were no /dev/ircomm devices. When I modprobe ircomm and ircomm-tty, I have:

$ ls /dev/ircomm*
/dev/ircomm0 /dev/ircomm15 /dev/ircomm21 /dev/ircomm28 /dev/ircomm6
/dev/ircomm1 /dev/ircomm16 /dev/ircomm22 /dev/ircomm29 /dev/ircomm7
/dev/ircomm10 /dev/ircomm17 /dev/ircomm23 /dev/ircomm3 /dev/ircomm8
/dev/ircomm11 /dev/ircomm18 /dev/ircomm24 /dev/ircomm30 /dev/ircomm9
/dev/ircomm12 /dev/ircomm19 /dev/ircomm25 /dev/ircomm31
/dev/ircomm13 /dev/ircomm2 /dev/ircomm26 /dev/ircomm4
/dev/ircomm14 /dev/ircomm20 /dev/ircomm27 /dev/ircomm5

I don't actually know whether it is doing anything, or why I have so many, as I don't really know how to test. Typing "hexdump -C" and pressing the remote at the IR sensor doesn't give any output.

setting back to new...

On Jaunty the situation is the same:
To make the devices created I should do these steps:
# modprobe ircomm
# modprobe ircomm-tty

marking as confirmed, multiple users have the same issue

flix, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]