So far I have had no luck. I have installed the GenMU and have everything setup however the network adapter is failing to work. I have tried copying the Athw.sys file from my Windows drive over the one included with GenMU and it still fails. I have tried both different drivers and modified the NIF's with the settings from my windows install as well as the defaults which the driver package would setup. Still nothing. Has anyone been able to get this card working in OS/2? My windows install calls it: 11b/g Wireless LAN Mini PCI Express Adapter III.
Any ideas would be helpful.. On the other hand this machine is flawless. ACPI works, had to force 2 processors but it works well. The only concern I have is that the system runs a bit hot when running OS/2. I am guessing this has to do with the system not throttling the processors. Are there any utilities out there for OS/2 like TPFanControl which would allow me to control the speed of the system fan?
I guess I should add that the log file gives no errors or indications as to why it is not working, the wifi widget says no wireless adapter found.
Hi Robert, you got a PM.
QuoteMy windows install calls it: 11b/g Wireless LAN Mini PCI Express Adapter III.
We need to know the PCI ID of the device. Use the PCI.EXE program to get that information. Also, be aware that there may be a problem with what is supplied with GENMU, where the driver is too new (probably also the case with what you copied from windows), but somebody did report that what you find in GENMU does work, for them. You may have better luck with an older windows driver (win2000 compatible), if you can find one. If you are actually using GENMU_TEST, there are devices that *may* work, but nobody has verified that they actually do work, or not.
QuoteAre there any utilities out there for OS/2 like TPFanControl which would allow me to control the speed of the system fan?
I am working on one, but it is not ready for prime time, yet (and probably never will be, since ACPI is such a mess). It is working good on my ThinkPad T43 (1871-W8M), but only marginally on my Asus M3A78-EM with quad core AMD Phenom processor. The main problem with it, is that it can freeze some processors when it attempts to determine what is, or isn't, supported by ACPI. I am also unable to reboot the Asus, if it is left throttled down when something goes wrong, until I remove AC power (effectively unplug it) for a couple of minutes. I expect that that is really a design problem with the motherboard, since a reset should clear such things, but doesn't.
PCI\VEN_168C&DEV_001C&SUBSYS_0035168C&REV_01
PCI\VEN_168C&DEV_001C&SUBSYS_0035168C
PCI\VEN_168C&DEV_001C&CC_020000
PCI\VEN_168C&DEV_001C&CC_0200
Obviously that is from Windows. The 168cX001C. I've tried several different driver packages. The drivers appear to be working, they are getting assigned interupts and everything in hardware manager. The Link option tells me the status of the device, I just cannot scan or connect to anything and the widget says there are no supported devices installed.
BTW.. if you would like someone with a newer TP to check out your utility I would be glad to try. Anything which can cool this thing down would be appreciated. I am wondering if the older IBM speedstep driver would be of any use since my bios still refers to it as speedstep. An oddity though is if I set the AC profile to anything other then performance the system hangs at the ACPI startup. Even though Battery mode is set to balanced, it boots fine when on battery. lol.
QuoteBTW.. if you would like someone with a newer TP to check out your utility I would be glad to try.
I have sent you an offline note about this. let's keep it offline, for now...
QuoteThe 168cX001C.
That one seems to be causing a few problems, but it does seem to work for a few people. If the GENMAC driver loads (with green text, not red), it should work. One thing to check, is that the HELPERW.EXE line, in CONFIG.SYS, should be near the top of file. Try sorting your CONFIG.SYS with:
http://hobbes.nmsu.edu/download/pub/os2/util/config/LCSS-0-4-0.wpi (http://hobbes.nmsu.edu/download/pub/os2/util/config/LCSS-0-4-0.wpi)
Be sure to READ the instructions, and also get the interim update from:
http://www3.telus.net/public/bissett1/LCSS.dat (http://www3.telus.net/public/bissett1/LCSS.dat)
I assume that you have XWLAN 3.10, which should, at least, detect the device.
Quote from: DougB on 2010.09.06, 05:23:07
That one seems to be causing a few problems, but it does seem to work for a few people. If the GENMAC driver loads (with green text, not red), it should work. One thing to check, is that the HELPERW.EXE line, in CONFIG.SYS, should be near the top of file. Try sorting your CONFIG.SYS with:
http://hobbes.nmsu.edu/download/pub/os2/util/config/LCSS-0-4-0.wpi (http://hobbes.nmsu.edu/download/pub/os2/util/config/LCSS-0-4-0.wpi)
Be sure to READ the instructions, and also get the interim update from:
http://www3.telus.net/public/bissett1/LCSS.dat (http://www3.telus.net/public/bissett1/LCSS.dat)
I assume that you have XWLAN 3.10, which should, at least, detect the device.
Well I guess I should explain what is happening. The driver loads (and the log file looks good); it is in green with the address of the device [168C,001C] in white. XWLAN does not see the device. If I use the default command line tool with genmac after about 30seconds the link status changes to connected. As far as I can tell it is not actually connected to anything, considering I haven't specified an ssid or password at this point. I have tried now 8 different versions of the driver with no avail (actually, some won't even pull the "connected" msg). Some will fail to load. And several will trap the system. The only thing I am wondering is if the trap is actually the working driver and is being caused by ACPI. I haven't tried disabling ACPI because I am scared of what it will do to the system to remove it.
So an update. I updated the .inf file with settings from my windows registry, and added several which were not in it originally. Now the wifi led lights up when the driver loads (just as it does in windows) and apparantly is scanning (blinking on and off at about 10second intervals). If I use the genmac\bin\default.exe the link status changes to Connected and the light stays on solid. Dis.exe will restore the original blinking. XWLAn still does not detect a wifi adapter however. Scan.exe returns nothing. Something is going on here.. I checked all the settings and everything is looking good.. I would say I have a functional driver seeing and I am getting anything from it. Has anyone had any luck getting the b/g Wireless Adapter III working in a T500. (as a side note, I am already far ahead of where I was with OS X :)
It sounds like the driver is actually working. That puts the problem in the XWLAN setup. I would uninstall every trace of XWLAN, and reinstall it. If you have eCenter, or XCenter, use the widget version. otherwise you need to use the EXE version. Don't try to use both or they can interfere with each other, unless you are very careful about how you try to use them (only one at a time).
Gonna give that a try. The option which caused the activity light to start functioning was adding the flags in the .nif to disable power management, and another flag which indicates how the driver sets the led status.
Don't know, well atleast I got this far using the driver which is in the package which is a known working driver (for atleast some versions of the adapter)..
I guess it just isn't going to work. The driver loads fine, and everything looks good, but it cannot scan any access points. The only functions which work are default, dis and link and they actually don't do anything other then make the wifi led come on and blink. Netstat is claiming that data is going through the interface, but since it is impossible to connect to any networks it isn't actually going anywhere. I have now tried every version of the driver since the first which supports this lan adaptor all the way through the most recent (the most recent traps), all the other ones seem to work but don't function (shows up in hardware manager, has resources assigned).
QuoteI guess it just isn't going to work.
Why would you say that? You say
QuoteThe driver loads fine,
That means that the driver it is working.
You seem to have a problem with XWLAN, not the GENMAC driver. The problem with XWLAN is likely some error in the way you have it set up, or you are not using it properly. You say that you can't scan for any access points. Why not? What do you see? How, exactly, do you attempt to do that? Be aware, that if you select network access type "Public networks", and there are no open networks near you, you will not see anything in the list. Be sure that you select "All networks", to see all public, and private, networks in the area. You also won't be able to connect if you haven't made a profile for the access point, and then select it. It is also possible to have a hidden SSID, which will not show up on the Hotspot scan, but you can still connect if you know what is needed to connect to it.
Genmac isn't able to successfully scan for access points (it reports and error). The atheos drivers are a mess.. I was looking at the inf's for it (and the linux sources) and the one driver operated about 14 different hardware revisions. I am guessing that genmac is doing something which is causing it to select the incorrect hardware (I've checked multiple times to see that it was set right, the .inf i am using has the same hw id passed to the driver that windows does). When browsing the Linux source for the specific model which I have if everything isn't set just right the card will just sit there with the radio on and do nothing :)
Linux has nothing, at all, in common with GENMAC. GENMAC uses the windows drivers, when it can. If the driver loads, and you can do anything, at all, with the supplied utilities (which are almost completely useless) the driver is working. XWLAN is where your problem lies, and that is almost guaranteed to be a setup problem.
Quote(it reports and error)
What error?
BTW, it is not GENMAC that scans for access points, or connects to one. It is XWLAN that does that.
Quote from: DougB on 2010.09.08, 18:14:05
Linux has nothing, at all, in common with GENMAC. GENMAC uses the windows drivers, when it can. If the driver loads, and you can do anything, at all, with the supplied utilities (which are almost completely useless) the driver is working. XWLAN is where your problem lies, and that is almost guaranteed to be a setup problem.
Quote(it reports and error)
What error?
BTW, it is not GENMAC that scans for access points, or connects to one. It is XWLAN that does that.
RC=2. scanloop does nothing but error out
The linux driver have something in common with the windows driver, they are both official atheos drivers and let me know what flags need to be set by the driver in order to even make my hardware function. It is clear (I think) that the windows drivers under genmac are not doing this.
Hi all,
I know this is of little help, but in case "Atheos" refers to "Atheros", then let me just tell you that these things are the worst piece of crap under the sun. They should come with stickers "designed for windows only or any available trash can". Prejudice? No - experience. I tried a couple of them and once you tear them out of their target environment (Windows), they become unstable, unpredictable and useless.
I surrendered after two weeks of frustration and bought an Intel 2200BG. Works like a charm right from the start.
In the end, I preferred paying twentysomething Euro including shipping for an Intel MiniPCI instead of waisting my time with that Atheros crap.
Yeah, I know this doesn't help - anyway, good luck. Perhaps it'll work in your case.
Thomas
QuoteRC=2. scanloop does nothing but error out
Where do you see this?
QuoteThe linux driver have something in common with the windows driver, they are both official atheos drivers and let me know what flags need to be set by the driver in order to even make my hardware function. It is clear (I think) that the windows drivers under genmac are not doing this.
Nothing is clear. You do have a better chance of getting it to work with the driver, and INF files copied from the windows that is on your machine, but that is really only true if you have Win2K, or WinXP. Anything later, and the drivers are probably too new for GENMAC to be able to use them.
If the driver loads (and you say that it does), GENMAC is probably working. Playing with the "flags", as you call them, is not likely to accomplish much, since a lot of them are totally ignored. There could be a problem with the way that XWLAN is interpreting some of the driver information, but I suspect that it is more likely that your setup in XWLAN has something wrong.
To pursue this further, we need to know what is in the WRND32.LOG file, and what is in LANTRAN.LOG. One, or both, of them might offer a clue.
RC=2 is from scanloop.cmd
The issue I see is in the comments for the particular chipset which I am using, if a certain flag isn't set it will fail to scan for access points. I've removed xwlan and reinstalled and doesn't work.
The drivers I am using are the W2k/WinXP 32bit ones. They were the oldest ones which supported this card. I have tried every version up to the newest XP driver, the newest release trap when PMSHELL loads. Assuming genmac is passing the flags correctly it should be loading. And as I said, The GENMAC stuff is all in green except the white line which says Unsupported Device!!! [168c:100c]
Lantran.log shows everything being ok, and shows the device's mac as well. It sends with device 0 trying to bind to tcpip 0. I would cut and paste it but I have no way to save anything from my OS/2 drive. Need to make a small fat partition to send stuff back to windows :)
I think you need to ask about this in the XWLAN news group. The server is:
news.gmane.org
Subscribe to gmane.org.netlabs.wlan.general.
QuoteUnsupported Device!!! [168c:100c]
simply means that it is not one of GENMAC's internally supported devices, and it is being supported by using the "UNSUPPORTED" parameter. It is somewhat misleading, but what it is telling you, is that the driver has loaded successfully, and is ready to use. Your problem seems to be something in XWLAN, not GENMAC.
However genmac cannot scan, taking xwlan completely out of the equation. Something is defiantly not right in the driver, however I've completely run out of ideas as to what it could be. I've parsed the default .inf and made sure all parameters are set which the 6013 (lenovo version of the card) requires. Still don't have a working device. There are close to 15 ap's in the area which it should be finding.. but it doesn't find anything. scan.exe shows nothing at all, and scanloop says an error occurred while scanning.
Well atleast the new intel drivers work for my wired connection, but I really would love to get my wifi working.