Wireless connection died after Airport Basestation upgrade
I've been following the thread on this list earlier this yeah called 'airport wireless problems' where Jamie Wilkinson recieved a lot of these messages: eth1: Unknown information frame received (type f202). which resulted in no wireless connection. I'm having the same problem. After the latest OSX upgrade, which also provided a firmware upgrade, my Linux wouldn't boot. I fixed that by upgrading to kernel 2.4.23-pre7-ben0. With my Powerbook now booting again, I didn't get a wireless connection, but alot of the above messages. Jamie solved his problem by changing som 'open network' options on his base station, however no similar options are available on my Airport Extreme Basestation.. I've ensured that the essid and the key is correct, tried with both a 40bit key and 128bit. On bootup the kernel reports: eth1: Station identity 001f:0001:0008:0046 eth1: Looks like a Lucent/Agere firmware version 8.70 eth1: Ad-hoc demo mode supported eth1: IEEE standard IBSS ad-hoc mode supported eth1: WEP supported, 104-bit key eth1: MAC address 00:30:65:25:B6:CE eth1: Station name "HERMES I" eth1: ready Can anyone give me a hand, you get used to wireless so quickly ;) Regards.. -- Jesper L. Nielsen http://phunkbros.dk
Re: KDE problems
* Jaime Robles ([EMAIL PROTECTED]) [2003-10-28 18:36]: > KMail is crashing when i download, for example, a big mail and also without > any (known for me) reason. > KBabel is also getting all the system's memory when opening some files. > > Have anybody found any problem with Debian/Unstable KDE's packages? Sorry, haven't solved the problem, just wanted to confirm that I'm having the same trouble. Now my kmail wont even start.. version: [EMAIL PROTECTED]:~$ kmail --version Qt: 3.2.1 KDE: 3.1.4 KMail: 1.5.4 backtrace: 0x0e3f2bf0 in waitpid () from /lib/libpthread.so.0 #0 0x0e3f2bf0 in waitpid () from /lib/libpthread.so.0 #1 0x0f177118 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 #2 0x0e3f1710 in __pthread_sighandler () from /lib/libpthread.so.0 #3 #4 0x0df7ca64 in kill () from /lib/libc.so.6 #5 0x0e3ee510 in pthread_kill () from /lib/libpthread.so.0 #6 0x0e3ee98c in raise () from /lib/libpthread.so.0 #7 0x0df7c84c in raise () from /lib/libc.so.6 #8 0x0df7df88 in abort () from /lib/libc.so.6 #9 0x0f113b08 in KApplication::qt_static_property(QObject*, int, int, QVariant*) () from /usr/lib/libkdecore.so.4 #10 0x0f1146d8 in kdbgstream::flush() () from /usr/lib/libkdecore.so.4 #11 0x101c0ac8 in endl(kdbgstream&) () #12 0x0f99c434 in KMime::Codec::decode(QMemArray const&, bool) const () from /usr/lib/libkdenetwork.so.2 #13 0x10139ad8 in ?? () I haven't had time to locate kmail in the KDE CVS, so I'm unable to debug myself.. Yet.. Regards -- Jesper L. Nielsen http://phunkbros.dk
Re: AirportExtreme on albook G4 15"
* Chris Anderson ([EMAIL PROTECTED]) [2004-01-14 18:44]: > If I recall correctly, there is currently no way to use the Airport > Extreme card in linux. However, since you have a powerbook you can get > an original Airport card and use that without any problems. . And if you do choose this setup, please let me know if you experience 'drop outs' between the Airport card and the basestation. I have the above setup and frequently experience these messages in my log: NETDEV WATCHDOG: eth1: transmit timed out eth1: Tx timeout! ALLOCFID=, TXCOMPLFID=, EVSTAT=8000 eth1: Unknown information frame received (type f202). eth1: Unknown information frame received (type f202). eth1: New link status: Connected (0001) Loads of those, network disappears, and comes back. Sometimes many times per minute. Kernel is currently: 2.6.0-test11, but I've experienced since the OSX upgrade that also trashed Yaboot. -- Jesper L. Nielsen http://phunkbros.dk
Re: Airport and WEP
* Kiko Piris ([EMAIL PROTECTED]) [2004-01-20 10:43]: > I'm asking because I found [*] that with 5.0.4 wep works fine (but it > doesn't with current version, 5.1.1). I can confirm, a few months ago MacOSX updated my openfirmware and my Airport Extreme, and WEP stopped working with a long 'key'. -- Jesper L. Nielsen http://phunkbros.dk
Re: Bug#234062 blender crashes xserver
* Georg Koss ([EMAIL PROTECTED]) [2004-02-29 23:52]: > Hello! > > Since upgraded to blender 2.32 my xserver crashes on invoking blender. > > (I reported that as a critical bug#234062 against blender, but was told by > the maintainer that it should'nt be blender's bug because this > behaviour wasn't detected on a lot of other boxes.) Just as a side-node.. I'm experiencing the same thing when starting Java applications, the X server simply crashes, and when logged in again, I can start the Java application just fine.. Guess the XServer enters som odd stage at some point.. -- Jesper L. Nielsen http://phunkbros.dk
