Perhaps someone with compiling experience can offer some ideas. We 'rolled our own' module for the Breezecom PCD wireless card from the 2.4 code on the Breezecom site. They don't seem to be actively supporting this card under Linux as this code looks to be the same as when I did this for the Eiger 2.2 kernel a year ago. The 2.4 files are still called 'beta' - not a good sign.
Compiled against the Bering kernel and pcmcia package used in RC2, the module seems to be created without problems. If no AP is within range, the card loads, tries to find an AP, fails and tells the logs of the problem. The box seems to run properly. However, if an AP is in range, the boot process almost completes to the logon prompt before it crashes when the kernel implodes with a screen full of numbers and a lockup. The AP shows that the LEAF box successfully associated itself on the system right before everything went nuclear. The boot process seems to show the association before the screen fills (to fast to read fully). So, it is the act of association, or something resulting from a successful association that causes the kernel to crash. Any suggestions as to where the problem is? I'm leaning toward the module itself, but wonder about card services or something in the 'if up' procedure. I'm not clear enough on how the gears mesh to make any better guesses! Any ideas? -- Brock Nanson Kamloops BC Canada ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
