[ATrpms-users] FC6 kernel update

[Phil Schaffner]

On Tue, 2006-12-19 at 21:45 -0500, Phil Schaffner wrote:
> On Tue, 2006-12-19 at 16:45 -0500, Jeff Guerdat wrote:
> > Philip R. Schaffner wrote:
> > > On Tue, 2006-12-19 at 15:30 -0500, Jeff Guerdat wrote:
> > >> It's b-a-a-a-c-k...
... snip ...
> 
> Seems to be an ATrpms problem rather than a yum bug in this case.  Just
> got the same result with yum - i586 kernel rather than i686 when trying
> an update at home on my laptop - so tried with "smart --gui" and found 
> 
>         kernel-suspend2-2.6.18-1.2868_1.fc6.cubbi_suspend2.i586
> 
> but no 
> 
>         kernel-suspend2-2.6.18-1.2868_1.fc6.cubbi_suspend2.i686
> 
> available.

Seems to be a bit bigger problem, although I can't quite see why.  Since
installing the 2868 kernel my ipw3945 networking is broken.  Even
un-installing everything 2868 and falling back to the 2849 kernel and
kmdls for ieee80211 and ipw3945 it is still failing to get an address
from the router.

Seemingly relevant bits from dmesg:

ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.1.0d
ipw3945: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:03:00.0 to 64
ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
...
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.base_reachable_time; Use net.ipv6.neigh.lo.base_reachable_time_ms instead.
ieee80211_crypt: registered algorithm 'WEP'
ADDRCONF(NETDEV_UP): eth1: link is not ready
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)

There are currently 59 repetitions of the last line interspersed through
dmesg output.  Have fallen back to wired Ethernet.  Any suggestions or
similar reports appreciated.  Anything else I can supply?

Phil