Messages in this thread | | | From | Alistair John Strachan <> | Subject | Re: debug prism wlan | Date | Sat, 12 Aug 2006 22:06:00 +0100 |
| |
On Saturday 12 August 2006 23:49, Daniel wrote: > *grrrr* it is too late on evening (I'm living in germany ;) )... > > I also fogot to tell following: > > Error for wireless request "Set Frequency" (8B04) : > SET failed on device eth2 ; Input/output error. > > I got this message if I try to start the net device with the init.d script. > If I try to set the channel per hand I got no error but the channel gets > not set (it still is 0). But I am able to set the mode and the essid.
Enabling debug would be good. It seems that the driver has protection around most of the really low level debugging with:
#if VERBOSE > SHOW_ERROR_MESSAGES ...
If this test passes, a silly DEBUG() wrapper is used to determine whether the message should be printed:
islpci_mgt.h:#define DEBUG(f, args...) K_DEBUG(f, pc_debug, args) islpci_mgt.h:#define K_DEBUG(f, m, args...) \ do { \ if(f & m) printk(KERN_DEBUG args); \ } while(0)
Currently the driver has:
islpci_mgt.h:#define VERBOSE 0x01 islpci_mgt.h:#define SHOW_ERROR_MESSAGES 0x01
So I think you'll need to:
a) Hack islpci_mgt.h and change VERBOSE to 0x02 (or any number higher). b) Insert the module with pc_debug=1
Then you should get debugging messages, since (0x01 & 0x01) will trigger the debugging.
-- Cheers, Alistair.
Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |