This is not a kernel issue, this is a by default behaviour:
You can/should use udev to force your kernel assign arbitrary names to devices
as it finds them.
Take a look at my file /etc/udev/rules.d/50-local.rules:
# REGLAS PARA LOS DISPOSITIVOS QUE QUEREMOS CONTROLAR POR NOMBRE
BUS=="usb", SYSFS
Public bug reported:
Binary package hint: linux-source-2.6.20
I'm having a problem with a USB->Serial converter that worked OK under Edgy.
Now it gets added OK (according to syslog) but immediately gets fired out by a
combination of usbfs and NetworkManager trying to take over it...
Looks like
** Attachment added: "udev"
http://librarian.launchpad.net/7382664/udev
--
USB->serialconverter udev endless add/remove
https://bugs.launchpad.net/bugs/108696
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
** Attachment added: "syslog"
http://librarian.launchpad.net/7382665/syslog
--
USB->serialconverter udev endless add/remove
https://bugs.launchpad.net/bugs/108696
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
The failing is the one from FTDI, the other USB->Serial from Prolific
works OK!
** Attachment added: "lsusb"
http://librarian.launchpad.net/7382676/lsusb
--
USB->serialconverter udev endless add/remove
https://bugs.launchpad.net/bugs/108696
You received this bug notification because you are a
OK, stop anyone having this problem, it is NOT a bug or a hardware
support problem!
The problem is initiated by the package brltty, that gets automatically
installed when you upgrade to Feisty.
Just uninstall it and the problem is gone.
Sorry for thinking it could be a bug, I should take more ca
I'm on an AMD64 2.6.31-19-generic #56-Ubuntu SMP and experiencing the
same problem...
Copying speed for some large files (2-12 Gb per file) from SATA to a USB
drive drops to 1,4Mb/s after the first hundreds of Mb are copied. I have
to copy around 1Tb, and I'm expecting it to take 8 days!!! It shou
Public bug reported:
On all recent 3.2 and 3.8 kernels, nfs v3 shares cannot be mounted with
tcp protocol from several nfs clients.
for this test:
nfs-kernel server 1:1.2.5-3ubuntu3.1
kernel 3.2.0-58-generic
Some clients (eg. OUYA console) do mount the shares correctly, but many
others timeout a
** Changed in: nfs-utils (Ubuntu)
Status: New => Invalid
** Description changed:
+ Dismiss this. It was due to a faulty firmware in a Netgear ProSAFE JGS516PE
switch discarding nfs over tcp traffic, while happily switching everything else.
+ No one else being affected pointed me to rethin
