Re: wireless trouble (prism3 mini-pci)

2007-07-26 Thread Ben Cornett

Anybody else have a suggestion?

Thanks!

On 7/25/07, Ben Cornett [EMAIL PROTECTED] wrote:

Thanks for the suggestion!  Unfortunately, when I do this the boot
process hangs.  The last few lines shown are

acpi0 at mainbus0: rev0
acpi0: tables DSDT FACP BOOT SSDT SSDT
acpitimer at acpi0 not configured

Regards,

Ben


On 7/24/07, Jonathan Gray [EMAIL PROTECTED] wrote:

 I suspect your problem might be resolved by getting the
 interrupt routing information out of acpi.

 At the boot prompt try:

 boot -c
 enable acpi
 quit

 And see if that helps.




Re: wireless trouble (prism3 mini-pci)

2007-07-25 Thread Ben Cornett

Thanks for the suggestion!  Unfortunately, when I do this the boot
process hangs.  The last few lines shown are

acpi0 at mainbus0: rev0
acpi0: tables DSDT FACP BOOT SSDT SSDT
acpitimer at acpi0 not configured

Regards,

Ben


On 7/24/07, Jonathan Gray [EMAIL PROTECTED] wrote:


I suspect your problem might be resolved by getting the
interrupt routing information out of acpi.

At the boot prompt try:

boot -c
enable acpi
quit

And see if that helps.




Re: wireless trouble (prism3 mini-pci)

2007-07-24 Thread Jonathan Gray
On Tue, Jul 24, 2007 at 06:12:03PM -0500, Ben Cornett wrote:
 Hi,
 
 I'm trying to get my wireless card working under 4.1.  The machine is
 a Sony VAIO PCG-V505BCP.   It has an Intersil PRISM3 PCI card that
 works fine under linux.   According to the wi(4) manpage, this card
 appears to be supported.   Its interface doesn't show up in the output
 of ifconfig, however.
 
 My dmesg follows, but from this excerpt is appears that I'm having
 some irq problems:
 
wi0 at pci2 dev 2 function 0 Intersil PRISM3 rev
 0x01pci_intr_map: no mapping for pin A
: couldn't map interrupt

Sony hardware tends to be rather quirky/broken in my experience.

I suspect your problem might be resolved by getting the
interrupt routing information out of acpi.

At the boot prompt try:

boot -c
enable acpi
quit

And see if that helps.



Wireless trouble

2006-10-09 Thread Rafael Morales
Hi list :)

I have OpenBSD 3.8 on a PowerBook G4, an Avaya
wireless card (wi0) and my AP.
My problem is when I active the WEP in the AP
(WEP-Open), my wireless lost connection. 

This my card configuration:
wicontrol -e 1 -k abcde123456 -t 6 -n MyName -p1  -f 6


my AP Information is:
ap[0]:  netname (SSID): [ MyName ]
BSSID:  [ 00:18:3f:04:85:21 ]
Channel:[ 6 ]
Beacon Interval:[ 100 ]
Quality/Signal/Noise [signal]:[ 57 / 111 / 54 ]
[dBm]:[ 57 / -38 / -95]
Capinfo:[ ESS PRIV ]


And the output of my card after configure it:
NIC serial number:  [ 01UT0540 ]
Station name:   [ WaveLAN/IEEE node ]
SSID for IBSS creation: [ IBSS ]
Current netname (SSID): [ MyName ]
Desired netname (SSID): [ MyName ]
Current BSSID:  [ 00:18:3f:04:85:21 ]
Channel list:   [ 2047 ]
IBSS channel:   [ 6 ]
Current channel:[ 6 ]
Comms quality/signal/noise: [ 61 112 51 ]
Promiscuous mode:   [ Off ]
Process 802.11b Frame:  [ Off ]
Port type (1=BSS, 3=ad-hoc, 6=Host AP): [ 1 ]
MAC address:[ 00:02:2d:3a:25:5e ]
TX rate (selection):[ 6 ]
TX rate (actual speed): [ 2 ]
Maximum data length:[ 2304 ]
RTS/CTS handshake threshold:[ 2347 ]
Create IBSS:[ Off ]
Antenna diversity (0=auto,1=pri,2=aux): [ ]
Microwave oven robustness:  [ Off ]
Roaming mode(1=firm,3=disable): [ ]
Access point density:   [ 1 ]
Power Management:   [ Off ]
Max sleep time: [ 100 ]
Enhanced Security mode: [ ]
Intersil Prism2-based card: [ 0 ]
Card info:  [ Lucent WaveLAN/IEEE, Firmware 7.28
variant 1 ]
Encryption: [ On ]
Encryption algorithm:   [ Firmware WEP ]
Authentication type 
(1=OpenSys, 2=Shared Key):  [ ]
TX encryption key:  [ 1 ]
Encryption keys:[  ][  ][  ][ ]


And I don't know how active the Authentication type,
because the -A option from wicontrol does not work for
my card.

Someone help me please to active my card using WEP
Thanks and Regards !!!



Re: Wireless trouble

2006-10-09 Thread Andreas Maus

Hi Rafael.

On 10/9/06, Rafael Morales [EMAIL PROTECTED] wrote:


I have OpenBSD 3.8 on a PowerBook G4, an Avaya
wireless card (wi0) and my AP.
My problem is when I active the WEP in the AP
(WEP-Open), my wireless lost connection.

This my card configuration:
wicontrol -e 1 -k abcde123456 -t 6 -n MyName -p1  -f 6

[... snip ...]
Never used wicontrol ... but you can do the same thing using
ifconfig. In this case it would be:

/sbin/ifconfig wi0 chan 6 media autoselect mode 11b nwid MyName \
nwkey persist:abcde123456

You can even put this in your /etc/hostname.wi0 file (writing ! before
ifconfig) and replace wi0 with $if. E.g.

inet 172.16.211.1 255.255.255.0 NONE
!ifconfig $if chan 6 media autoselect mode 11b nwid MyName nwkey
persist:abcde123456

Then it should be set on boot time.

Hope that helps,

Andreas.

P.S.: See man ifconfig and get the list of supported modes running
ifconfig -m wi0

--
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?



Re: Wireless trouble

2006-10-09 Thread Andreas Maus

Hi Stuart.

On 10/9/06, Stuart Henderson [EMAIL PROTECTED] wrote:

 ifconfig. In this case it would be:

this is wi(4) on 3.8, ifconfig didn't know how to configure
wireless settings on prism/wavelan cards back then

Doh! I assumed a current 3.9.
I guess (because I don't have any wi cards - just ath and ra)
it would work with 3.9.

Anyway upgrading to 3.9 is not a bad idea ;)

Andreas.

--
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?



Re: Wireless trouble

2006-10-09 Thread Fred Crowson

Andreas Maus wrote:
snip


inet 172.16.211.1 255.255.255.0 NONE
!ifconfig $if chan 6 media autoselect mode 11b nwid MyName nwkey
persist:abcde123456


/snip

hostname.if does not need the !ifconfig command, the netstart(8)
script calls ifconfig.

Hence hostname.wi0 would be:
inet 172.16.211.1 255.255.255.0 NONE \
chan 6 media autoselect mode 11b \
nwid MyName nwkey persist:abcde123456

HTH

Fred
--
OpenBSD on the Zaurus C3200
http://www.crowsons.net/puters/zaurus.php



Re: Wireless trouble

2006-10-09 Thread Andreas Maus

On 10/9/06, Fred Crowson [EMAIL PROTECTED] wrote:

hostname.if does not need the !ifconfig command, the netstart(8)
script calls ifconfig.

Hence hostname.wi0 would be:
inet 172.16.211.1 255.255.255.0 NONE \
chan 6 media autoselect mode 11b \
nwid MyName nwkey persist:abcde123456

Amazing! ;)
Never thought about that.

Thank you for this tip,

Andreas.

--
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?



Re: Wireless trouble

2006-10-09 Thread Fred Crowson

Andreas Maus wrote:

Hi Stuart.

On 10/9/06, Stuart Henderson [EMAIL PROTECTED] wrote:

 ifconfig. In this case it would be:

this is wi(4) on 3.8, ifconfig didn't know how to configure
wireless settings on prism/wavelan cards back then

Doh! I assumed a current 3.9.
I guess (because I don't have any wi cards - just ath and ra)
it would work with 3.9.

Anyway upgrading to 3.9 is not a bad idea ;)

Andreas.


its true that chan and mode generate the following errors:

ifconfig: SIOCS80211CHANNEL: Invalid argument
ifconfig: SIOCSIFMEDIA: Invalid argument

in 3.8 but a hostname.wi0 with out the media like:

inet 172.16.211.1 255.255.255.0 NONE \
nwid MyName nwkey abcde123456

should just work with a /bin/sh -x /etc/netstart unless the AP isn't 
playing ballcan you get a tcpdump from the AP that might give some 
clues as to why it's failing...


HTH

Fred
--
OpenBSD on the Libretto 70CT
http://www.crowsons.net/puters/fcm.php



ral0 wireless trouble

2005-08-26 Thread Brandon Mercer
Hello Group,
I've seen a lot of emails about wireless... and now I'm adding to it
:-).  I've got a WAP running OpenBSD 3.7 configured as follows:

# cat
/etc/hostname.wi0   
 

!/sbin/wicontrol \$if -f 11 -x 1 -E 3
inet 192.168.10.1 255.255.255.0 NONE nwid mywap \
nwkey secretpass mediaopt hostap


I've already got my linux laptop working with this AP, and tonight I
went out and got a card for my OpenBSD laptop :-).  I'm able to see the
WAP when I wicontrol -L.  Am I correct to assume that this means the
card (Belkin F5D7010) is properly supported?  I've tried the following
to configure the card and I am still not able to ping the WAP:

ifconfig ral0 192.168.10.23 netmask 255.255.255.0 nwid mywap chan 11
nwkey secretpass

Then on the WAP I check the associated stations wicontrol -l :

# wicontrol -l  
2 stations:
00:11:50:15:4e:29  asid=01b0, flags=3AUTH,ASSOC, caps=11ESS,PRIVACY,
rates=f1M,2M,5.5M,11M
00:0e:35:eb:c8:8f  asid=00d0, flags=3AUTH,ASSOC, caps=11ESS,PRIVACY,
rates=f1M,2M,5.5M,11M, sig=33/7


The top one 00:11:50:15:4e:29 is the OpenBSD laptop... it looks
connected to me, but I noticed it doesn't have the sig=33/7 message. 
Can anyone offer me some advice?  Thanks again,
Brandon



Re: ral0 wireless trouble

2005-08-26 Thread Brandon Mercer
Brandon Mercer wrote:

Hello Group,
I've seen a lot of emails about wireless... and now I'm adding to it
:-).  I've got a WAP running OpenBSD 3.7 configured as follows:

Please disregard transposed the key!
Brandon

P.S.  I love an OS that you can plug in the supported hardware and it
just works.  You can't do that on anything but OpenBSD.  Linux and their
modules I feel like I've got to be some kernel guru every time I
change a network card or what not.  Windows... well, I stopped using it
but I think I remember it requiring a CD or floppy or something every
time I added hardware and then I had to reboot and maybe get some
crashes and stuff.  The OpenBSD team is doing a GREAT job!  I'm hooked
:-).