This bug is still valid, I'm seeing this exact problem with a fresh
Jaunty install, but the fix is not working. No idea how to get rid of
the wrong /dev/zapctl and get the correct /dev/zap/ctl at thispoint. :(
** Changed in: zaptel (Ubuntu)
Status: Invalid => Confirmed
--
Wrong device-n
The last patch, "autoudev", in that thread fixed the problem correctly. I
would suggest packaging up and including it.
Thanks again for the quick response,
Mark
On Fri, Jun 19, 2009 at 9:42 PM, Stefan Lesicnik
wrote:
> nlinux: Could you try the fix described here and let us kno
Patch works great here, thanks guys. Somebody needs to get on the ball
and get this pushed into the updates, this was killing me on my work
network.
--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notifica
I'm seening this same bug on a fresh install of Jaunty. Has there been
any solution to it?
--
CH produts do not initialize
https://bugs.launchpad.net/bugs/108875
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
The above workaround doesn't work for jaunty:
/sbin/rmmod ehci_hcd
/sbin/modprobe ehci_hcd
apparently ehci_hcd is not compiled as a module but is built directly into the
kernel. The even tried installing later kernel versions from the kernel ppa,
all the way up to 2.6.31rc3 which was just rel
