I suspect you need to install the i386 kernel for thin client booting
(it probably has the i686 variant installed). I ran into a similar issue
in 2006: http://blog.akkaya.de/jpabel/2006/11/17/Ubuntu-Server-6-06-1
-on-my-TU
--
Thin client unable to boot - kernel requires cx8 cmov
https://bugs.laun
I've created a solution that patches the existing bnx2.ko module: it
modifies an existing PCI ID in order to recognize the BCM5716 chip. My
solution is a initramfs hook and takes care of all kernel-updates (and
-upgrades); it's a one-stop solution for using BCM5716's on Hardy. More
info in my blog
Here's my output from NetworkManager --no-daemon (slightly anonymized)
NetworkManager: starting...
NetworkManager: Found radio killswitch
/org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan
NetworkManager: Found radio killswitch
/org/freedesktop/Hal/devices/iwl_wlan_switch
Netwo
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
LANG=de_DE.UTF-8
Uname: Linux 2.6.28-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
--
delay in connecting
I have the same issue on a Lifebook P7230 with an Intel 3945ABG (after a
fresh install).
--
delay in connecting to wireless networks with Broadcom Corporation BCM4328 on
macbook 3,1 on startup and suspend/resume
https://bugs.launchpad.net/bugs/367298
You received this bug notification because yo
I believe that this bug is falsely filed against libpam-keyring: it
should be filed (only) against gdm. The solution should be to add a
trigger for the auto-login checkbox, which tests whether the keyring is
used at all. If so, it informs the user about the security consequences
and changes the key