 |
 |
| Re: wireless not working |
 |
 |
By mmlr - Posted on June 2, 2008 - 05:36:01 (#22829)
Current version when comment was posted: 1.0.1 |
 |
 |
Have you configured the network using the settings file in "/boot/home/config/settings/kernel/drivers/ipw2100"? As BeOS did not contain any wireless stack or configuration tools, the only way is to configure through that settings file. The file contains comments that explain all relevant settings and should be easy to follow though.
Note that this driver only supports hardware encryption, what limits it to WEP. The hardware does not provide WPA support and there is no software wireless stack to emulate it. So if you are trying to connect to a WPA network this will not work.
Also all laptops containing such a card should have a kill switch that disables wireless. Make sure that wireless is enabled using this switch. If it is a software switch that uses ACPI for example you probably won't be able to change it, as BeOS does not support that either. So if you get a line like "RF kill switch enabled" in the syslog and cannot enable wireless by a hardware switch you are out of luck on that one.
|
|
| wireless not working |
 |
 |
By duda - Posted on June 1, 2008 - 17:15:27 (#22828)
Current version when comment was posted: 1.0.1 |
 |
 |
I have this driver installed but the wireless is not working. This is an intel pro 21003B card. The vendor is 0x8086 and card id is 1043. Syslog contains
KERNEL: driver ipw2100 does not have wake_driver and suspend_driver
ipw2100: will plubish an "Intel(R) PRO/Wireless 2100" as device 0 to /dev/net/ipw2100/0
What can I check to make this work? I am brand new to BeOS.
|
|
| Re: No Interface |
 |
 |
By mmlr - Posted on April 4, 2008 - 07:54:12 (#22675)
Current version when comment was posted: 1.0.1 |
 |
 |
Well, since this is a driver for the ipw2100 it would only make sense if it wasn't compatible :-). It isn't compatible, but there is http://www.bebits.com/app/4031 which you should give a try.
Regards
Michael
|
|
| No interface |
 |
 |
By superhyper - Posted on April 3, 2008 - 21:19:13 (#22674)
Current version when comment was posted: 1.0.1 |
 |
 |
Nothing appears in the network interfaces for me. I have a 2200 model, do you think that's incompatible?
|
|
| Big thanks |
 |
 |
By Double_S - Posted on October 20, 2006 - 09:04:53 (#20800)
Current version when comment was posted: 1.0.0 |
 |
 |
Well I do not use the driver and have not even download it. But I may needed in the future.
Big thanks Michael and the whole crew spending their free time coding Haiku.
|
|
| Neat |
 |
 |
By nutela - Posted on October 20, 2006 - 07:33:35 (#20797)
Current version when comment was posted: 1.0.0 |
 |
 |
So how's the NW stack coming up, great work Michael, and not only you but the entire Haiku team.
Sorry I sounded harsh on your MLnet app a log time ago. Hope to be @ Begeisterd sometimes soon.
|
|
| enable syslog |
 |
 |
By mmlr - Posted on October 20, 2006 - 06:12:54 (#20796)
Current version when comment was posted: 1.0.0 |
 |
 |
Hi rayman
To get the syslog file you need to enable syslog output. Edit the kernel settings file "/boot/home/config/settings/kernel/drivers/kernel" and enable syslog debug output there. Then you should get the syslog file.
If you get the "/dev/net/ipw2100/0" entry you will also get at least the initial debug output where publishing is handled. From there you should see any error output.
Regards
Michael
|
|
| request help |
 |
 |
By rayman - Posted on October 20, 2006 - 05:10:28 (#20795)
Current version when comment was posted: 1.0.0 |
 |
 |
I tested the “driver” on a centrino computer equipped with a IPW2100 card. I obtain the link in the directory /dev/net ==> ipw2100… but not log ( /var/log/syslog ) and not card appear in NetWorking preference ???
Some tests, to isolate the problem from the “switch”, does not give any result !!
how I can test if the driver run or not ?
good work still.
|
|
| horray |
 |
 |
By BeOS Mr X - Posted on October 19, 2006 - 17:29:05 (#20792)
Current version when comment was posted: 1.0.0 |
 |
 |
we need more wireless drivers and this one was a good contribution.
|
|
|
|
|