Arch Linux

jskier

Member

From: Minnesota, USA

Registered: 2003-07-30

Posts: 383

Website

iwpriv: No private ioctls

This error happens about 85% of the time (otherwise it just works fine). Whenever I use iwpriv to set my mode to anything I get the "No private ioctls" error.
This is a complex problem so I'll start with the basics. My card is integrated into my laptop (HP W500 a/b/g, madwifi drivers support it just fine). I am using the latest madwifi drivers patched with the 2.6.8.1 kernel patch- no errors while compiling.
Basically I need to know what "ioctls" is, where is its domain, and if possible, how to fix it? Thanks in advance.

~JSkier

---

--
JSkier

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: iwpriv: No private ioctls

In general, the message "No private ioctls" means that your driver has not been configured to allow access to the card's "private" functions i.e. hardware-specific settings that are not covered generically by Wireless Extensions. I don't have any experience with the madwifi code, so I can't give you anything more specific.

It's definitely strange that it works sometimes, but not always. Is there anything else happening on your machine when it works, but not when it doesn't work (or vice versa)?

jskier

Member

From: Minnesota, USA

Registered: 2003-07-30

Posts: 383

Website

Re: iwpriv: No private ioctls

I have not noticed anything out of the ordinary yet when it worked or not. About 5 minutes ago I found out that I had improperly set the rate with iwconfig, which actaully works too if set properly, so iwpriv isn't needed. Although it is a strange error that I would like to figure out. Thanks for the response.

JSkier

---

--
JSkier

0sun0ra0

Member

Registered: 2010-02-03

Posts: 9

Re: iwpriv: No private ioctls

i get the same message with iwpriv     i use a eeepc 901 just installed arch too

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: iwpriv: No private ioctls

This thread is nearly six years old, and is unlikely to be relevant today.

Please start a new thread with a more complete description of your issue.

Closed.