Latest rawhide hal/NetworkManager combo freezes machine or does not work at all

[Kyrre Ness Sjobak]

As taken from the Kismet README:

Q: My distro loads the orinoco drivers for my prism2 card, is this OK?
A: No, not really.  The orinoco and prism chipsets are based off the
same reference design, but there are subtle differences, especially in
the firmware timings.  Using the orinoco drivers may work for a while,
but you're likely going to have problems with lost frames, corrupt
frames, and system hangs.  Plus, if you ever have problems and mention
you're using the orinoco drivers, I'll yell at you.

Think you should get another driver :)

ons, 27.10.2004 kl. 22.42 skrev Dan Williams:
> We've seen machine freezing with kernels since -524 related to IPv6
> code.  #rh135432#.  You actually get panics on the console, but if
> you're in X of course then you can't switch to the console to see the
> panic.  This might be related to your problem, and we've usually seen it
> after picking an ESSID with "other network".
> 
> The other problem is that the orinoco drivers don't support scanning,
> unless you're using upstream drivers.  So you're already hosed there, NM
> attempts to compensate by scanning your approved list, but there's only
> so much it can do with orinoco cards.
> 
> Dan
> 
> On Wed, 2004-10-27 at 16:18 -0400, Amitabha Roy wrote:
> > Latest rawhide update gives hal and NetworkManager version numbers:
> > NetworkManager-0.3.1-1
> > NetworkManager-gnome-0.3.1-1
> > hal-0.4.0-9
> > 
> > First run: made sure NetworkManager started on startup. Opened up gnome console
> > and started NetworkManagerInfo. Applet came up in notification area. Chose
> > "Other Wireless Network" and typed in essid of wireless network (it is
> > non-essid-broadcasting network). This *completely* froze the machine
> > and had to do a hard reboot.
> > 
> > Before freezing, console message was "Forcing device
> > /org/freedesktop/NetworkManager/Devices/eth1"
> > 
> > 
> > Second run: made sure NetworkManager was running. With utmost trepidation,
> > opened up gnome console and typed in NetworkManagerInfo. Machine did not freeze
> > this time, typed in ESSID of network as before. Voila!  System-log
> > shows connected.
> > But also shows network connecting and disconnecting every second or so.
> > Log attached below:
> > Oct 27 16:06:15 localhost kernel: eth1: New link status: Disconnected (0002)
> > Oct 27 16:06:15 localhost kernel: eth1: New link status: Connected (0001)
> > Oct 27 16:06:22 localhost kernel: eth1: New link status: AP Changed (0003)
> > Oct 27 16:06:25 localhost kernel: eth1: New link status: Disconnected (0002)
> > Oct 27 16:06:25 localhost kernel: eth1: New link status: Connected (0001)
> > Oct 27 16:06:28 localhost kernel: eth1: New link status: AP Changed (0003)
> > 
> > As a result, network access is sporadic at best.
> > 
> > 
> >  output of /var/lib/pcmcia/stab is:
> > 
> > Socket 0: Intersil PRISM2 11 Mbps Wireless Adapter
> > 0       network orinoco_cs      0       eth1
> > Socket 1: empty
> > 
> > Anyone else seen this ?
> > 
> > Gone back to stopping NM and using ifup, iwconfig etc (and logging out of X
> > once hostname is set due to xauth *sigh*).
> > 
> > Amitabha
> >