I can confirm this is still an issue and appears to be network load
related and not Compiz-specific.
As I type this I am attempting an iSCSI install of Ubuntu 10.10 using
Ubuntu 10.04 netboot binaries on a Dell Inspiron 600m and the link is
constantly being reset, presumably by the iSCSI traffic.
Chuck,
I don't blame you for changing the status.
If memory serves, squid now "just works" with the
default config.
Marty
--- Chuck Short <[EMAIL PROTECTED]> wrote:
> You should be able to set visible_hostname in the
> configuration file.
>
> chuck
>
> ** Changed in: squid (Ubuntu)
>
I can also confirm. This seems related to the 2.6.22-7 kernel. Loading
under the previous 2.6.20-16 kernel works just fine. Copying
/lib/modules/2.6.20-16-generic/kernel/ubuntu/wireless/acx/acx.ko to
/lib/modules/2.6.22-7-generic/ubuntu/wireless/acx/acx.ko does not help.
Is this possibly relate
Public bug reported:
Binary package hint: squid
Squid uses its own resolver, getting a list of name servers on startup
from /etc/resolv.conf. On a roaming laptop, this information is missing
until a network connection is made, which happens after squid is
launched and has loaded an empty /etc/re
Public bug reported:
Binary package hint: squid
This *might* be considered a dupe of rejected bug 12709, which the
Debian guys decided was a non-issue.
In Ubuntu, I find it most convenient to have squid (or some other
caching proxy server installed), especially for a box which has multiple
users
Putting that line in the options file worked! Hopefully this will
persist across upgrades.
Many thanks.
--
WiFi Detection of and Use of Netgear WG311v2
https://launchpad.net/bugs/21471
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
Well it happened again! Tonight (6-16-6), Ubuntu installed a bunch of
updates which left me with an unbootable machine (after suggesting that
I reboot).
The firmware hack fixed the problem, but why does this happen? When the
module acx gets loaded, it clearly says it isn't compatible.
What give
The firmware solution fixed my problem as well. In fact, when the
default firmware is loaded, the following message is put in
/var/log/messages:
Jun 14 05:26:20 localhost kernel: [4323118.02] acx: firmware 'Rev
2.3.1.31' does not work well with this driver
Ok, the firmware knows its incompat
