Re-assigning to kernel - this is teh way to clarify whether it's a bug
or just documented behaviour.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/359356
Title:
USB device attached
Now, suspend-resume is about the kernel, the extra modules secion. But
which iof them? Just don't know.
** Package changed: lirc (Ubuntu) => linux-lts-xenial (Ubuntu)
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
Although not a fix by no means I have used a workaround by modifying
/etc/lirc/hardware.conf and changing the line from
REMOTE_LIRCD_ARGS=-d /dev/ttyUSB0
to
REMOTE_LIRCD_ARGS=-d /dev/ttyUSB*
If you have more than one ttyUSB device this will not work but I have
not had this issue.
--
You
As for BIOS, I have updated it long time ago, and I suppose it is still latest
version.
$ lshal | grep firmware
system.firmware.release_date = '09/08/2009' (string)
system.firmware.vendor = 'Phoenix Technologies Ltd.' (string)
system.firmware.version = '11CA.M015.20090908.RHU' (string)
And the computer is NC10. But that is not the only computer that this
bug occurs in.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/359356
Title:
USB device attached to different
As for resume taking so long time, it seems it is an issue with the dvb
device.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/359356
Title:
USB device attached to different ttyUSB
Okay, if its multiple machines, I put the blame squarely on the ftdi_sio
and dib0700 drivers for apparently not implementing any suspend/resume
support. I've actually dug out my usb-uirt hardware, which has some usb-
serial ftdi driver as well, iirc., and will see if I can reproduce the
issue and
Here's the data. Probably not relevant, but resume took more than a
minute.
** Attachment added: dmesg after fresh boot, suspend and resume
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+attachment/2181690/+files/dmesg2
--
You received this bug notification because you are a
Choice excerpts from dmesg:
[0.00] Atom PSE erratum detected, BIOS microcode update
recommended
[0.00] ACPI: BIOS bug: multiple APIC/MADT found, using 0
[0.00] ACPI: If acpi_apic_instance=2 works better, notify
linux-a...@vger.kernel.org
[0.180781] [Firmware Bug]:
99% certain this is not an lirc bug, it is a kernel bug. Devices
disconnecting and reconnecting on suspend/resume is indicative of buggy
support for the usb chipset on the system(s) in question. The isn't
anything in lirc that assigns ttyUSB devices, that is purely the kernel.
--
You received
Tested this in ubuntu 11.04. The device name is not changed, and lirc
works after resume, if neither irexec nor irxevent is running. If either
one is running, device is changed in resume. A workaround is to unplug
and re-plug the USB device. Then /dev/ttyUSB0 exists again and lirc
works. The
Still sounds like a kernel-level issue underneath. Can you provide dmesg
output from after a fresh boot, suspend and resume?
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/359356
Title:
To be more specific, also irxevent and irexec worked after resume in
9.04, when applying comment #7.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
You received this bug notification because you are a member of Mythbuntu
Bug
And the workaround does not work in 10.04 so I don't know how to make
10.04 work as well as 9.04.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
You received this bug notification because you are a member of Mythbuntu
Bug Team,
OK, thanks. Changing back to New so that the lirc guys will look at it.
** Changed in: lirc (Ubuntu)
Status: Incomplete = New
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
You received this bug notification because you
I can not reproduce this in 10.04.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in ubuntu.
Status in “lirc”
Oh, I can reproduce it: I just have to have irxevent running.
Note: If I have irexec running, but no irxevent, the device is not changed in
resume, but lirc does not work anyway.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
18 matches
Mail list logo
