Our FTDI devices seem to work as well over here, based on short testing
(with 2.6.32-28 on x86-64).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690798
Title:
arduino USB serial device breaks on lu
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655868 might be
very well related to this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690798
Title:
arduino USB serial device breaks on lu
Hi all, we run a Linux-only shop for electronics/hw development. We have
a number of different devices that have FTDI embedded in them. This is
the last thing that keeps us in Hardy. Running custom kernels just
because of this for the next couple of years seems counter-productive so
hopefully this
Currently this stops Altera Quartus II Web Edition from working on Lucid
and also the scanner driver for Canon P-150 (proprietary sane-backend
with open source .so-shim). Lucky me I have and try to use both.
Also, a lot of packages have "Fix committed" in them in this report, but
I can't see the f
Easy fix meanwhile (temporary one) is to comment lines 12 and 13 of
/usr/lib/python2.6/popen2.py
This at least won't confuse the sieve protocol readers so much. And yes,
it's not a real fix.
--
popen2 is deprecated.
https://bugs.launchpad.net/bugs/617872
You received this bug notification becaus
I've done some short testing with a patched kernel and it seems to work
ok (at least better than not working at all :-).
--
Frequently used NIC (Marvell Technology Group Ltd. Device 4381) not supported
https://bugs.launchpad.net/bugs/543314
You received this bug notification because you are a mem
Sony Vaio vpceb1j1e/wi also uses the same marvell chip (different WLAN though):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/532021
--
no connectivity (WLAN or LAN) with HP mini 5102 (netbook)
https://bugs.launchpad.net/bugs/543314
You received this bug notification because you are a memb
Also, as a side note, here are the real names for the chips in question.
A lot of people keep writing about "Marvell 4381" and "Broadcom 4353"
(these are the names that lspci will display when it doesn't have the
device id).
pci-ids hasn't been yet updated to include the proper names, so here they
Bug https://bugs.launchpad.net/ubuntu/+source/plasma-widget-
networkmanagement/+bug/529235 is a duplicate of this one.
There's also a link to forums about this issue:
http://ubuntuforums.org/showthread.php?t=1416385
http://ubuntuforums.org/showthread.php?t=1430781
There is also an upstream bug ag
I added a bugreport against kernel package today about this (not really
plasma-related):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/543314
--
no network connection on HP mini 5102
https://bugs.launchpad.net/bugs/529235
You received this bug notification because you are a member of Kubu
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/41497442/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/41497443/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/41497444/Card0.Amixer.valu
Public bug reported:
When installing, no connectivity is possible because of two reasons:
1) The integrated WLAN uses broadcom restrictred drivers (wl). Installing these
afterwards enables the WLAN (PCI ID: 14e4:4353)
2) The integrated NIC is a new version of Marvell Yukon series, supported by
s
Public bug reported:
Binary package hint: dhcp3-common
The following files are misplaced in dhcp3-common instead of dhcp3-client:
/usr/share/man/ja/man8/dhclient.8.gz
/usr/share/man/ja/man8/dhclient-script.8.gz
/usr/share/man/ja/man5/dhclient.conf.5.gz
/usr/share/man/ja/man5/dhclient.leases.5.gz
Running 2.6.24-19-generic on x86_64 with 82572EI (-17-generic didn't work
either):
e1000 recognizes the PCI ID but does not detect link.
e1000e doesn't even recognize the chip nor register the ethdev (ifconfig -a
doesn't show the device, with link or not).
uname -a:
Linux backup 2.6.24-19-generi
Ah, forgot to mention where the armel thing comes from. Recently, maemo
(the dev environment for Nokia Internet Tablets) moved their ARM
toolchain to a newer EABI and that uses arch 'armel'. Mirroring the repo
for the project caused me to run into the issue. While adding armel
support, noticed a pr
** Attachment added: "Patch to fix mipsel support and add armel support"
http://launchpadlibrarian.net/10596882/armel-and-mips-fix.patch
--
mips/mipsel arch selection problem and armel arch support
https://bugs.launchpad.net/bugs/172454
You received this bug notification because you are a mem
Public bug reported:
Binary package hint: apt-mirror
The script does re matching on the "supported" architectures and with
some archs this causes a problem if the archs are specified in shorted-
prefixed order.
This is a problem for mipsel for example, because matching against mips
will also mat
Had the same problem. Updated from edgy to feisty (was running a custom
built 2.6.18 kernel, but with initramfs generated with stock edgy
process). After update, system stuck on kernel messages.
Using lilo here (x86-64, for some reason had problems with grub
originally and lilo just works), with L
18 matches
Mail list logo
