Is the actual content of the state file, I get that from lenny 2.6.26 kernels too. If you see anything other than N/A, the file actually had contents, and what you see is the contents, if you see N/A inxi had no value for that, and simply shows N/A to indicate no content. In other parts, I simply do not show anything when the value is null, but in this case, I definitely want to see when it's null so I can see bugs and get them fixed

So state: unknown is in fact the value given, which is 'unknown'. But it's odd that you have speed and duplex with value, and the state contains 'unknown', I've only seen that be unknown when speed and duplex were null. But there will be huge variance.

But I appreciate the various samples of what the output can be, when working off something as difficult as this, where I cannot just inject user data files to get values, the only way to see what different systems return is to see what different systems return. But yours is working perfectly, all data files contained values.

First, download this file: http://smxi.org/opt/tree-traverse.pysave it to some directory. That's a script that will show us the contents of your /sys directory, so we can find where the actual locations of the usb wifi data is.

After you have created it, upload it somewhere, like pastebin, and then send me a link to the file.

note, zip or gzip the file before uploading it somewhere, can be here.

Any time you see both IF: and mac: blank, it means the logic failed. speed/duplex might be blank, ie, N/A, but not IF or mac.

The cases of failure are what I need, so if I can get that data file I'll see what's going wrong there. We may integrate this into inxi, not sure yet, ie, run a command, like: inxi -@ 12, and it will collect all the data, zip it into a file and then you can upload it somewhere. But one thing at a time.

Also let me know what kernel you are using, this is highly kernel dependent data, so it's good to get a sense of which kernels give what data, and which are missing what.

Sorry for the long quote, but I get a syntax error when running the tree-traverse.py script:

I'm running Mepis 8.5 32bit with the 2.6.32-1-mepis-smp kernel. I compiled the .deb for my DWA140 (and blacklisted the opensource rt2x00 and rt2800 driver modules and 'decommisioned' the rt2870sta staging driver). I cannot use the Mepis 2.6.36 kernel with the DWA140 wireless device as the latest source code that I used from Ralinktech still does not support the 2.6.36 kernel.

tree-traverse.py and xiin.py(newer version) both require python 2.6+ and will work with the python 3.x branch, also.

I'll request that xiin be used instead of tree-traverse (tt). tt was a quick and dirty script for me, after some feature requests by h2, I made it little more user friendly and renamed it xiin. (It's a play on ixni, invert the 'i's and reverse the 'x' and 'n', so you have inxi inside out and backwards). (pronounced 'zen')

All times are UTC - 5 hours [ DST ] | It is currently Tue Mar 03, 2015 4:17 pm

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum