linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John & Trudy Phillips <johntrudy@earthlink.net>
To: Josh Huber <huber@alum.wpi.edu>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: orinoco_cs on linuxppc_2_4/linux-2.4-benh
Date: Fri, 18 Jan 2002 20:52:31 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0201182034100.7255-100000@johntrudy.phillips.private> (raw)
In-Reply-To: <87ofjs8ju5.fsf@paradoxical.net>


I have the Orinoco Silver card working with a 550MHz Titanium Powerbook.
I am using the following:
	kernel : linuxppc  2.4.17-rc1
	modules: radeon                 90560   0
		orinoco_cs              5424   1
		orinoco                36016   0 [orinoco_cs]
		hermes                  6288   0 [orinoco_cs orinoco]
		ds                      8720   1 [orinoco_cs]
		yenta_socket           11088   1
		pcmcia_core            43104   0 [orinoco_cs ds yenta_socket]

	pcmcia/config:  ...
		card "Lucent Technologies WaveLAN/IEEE Adapter"
  		  version "Lucent Technologies", "WaveLAN/IEEE"
  		  bind "orinoco_cs"
                        ...
		device "orinoco_cs"
  		class "network" module "hermes", "orinoco", "orinoco_cs"

	pcmcia/config.opts:
		# Ti Powerbook resources
		include port 0x0fff-0x1fff
		include memory 0x80000000-0x80ffffff
		include port 0x100-0xaff
		# Everything else commented out

	pcmcia/wireless.opts
		*,*,*,*)
		    INFO="Wavelan IEEE example (Lucent default settings)"
		    ESSID="xxxxxxxx"
		    MODE="Managed"
		    KEY="xxxxxxx"

Let me know if this is close enough to your setup to help.

On Thu, 17 Jan 2002, Josh Huber wrote:

>
> I've decided to update the kernel on my laptop (Lombard 400),
> currently it's running 2.4.11-pre4-ben0, which seems to work fine,
> except I can't get usbmidi working with it.
>
> usbmidi works (afaict) with the current 2.4.18-pre4(-ben0)? trees from
> either linuxppc_2_4 or Ben's tree.  However, both of them seem to
> break my wireless card.  The link to the base (an airport) appears to
> be good, however no packets are transmitted/received over the link:
>
> with the newer kernels:
>
> iwconfig:
> eth1      IEEE 802.11-DS  ESSID:"huber_net"  Nickname:"mystic"
>           Mode:Managed  Frequency:2.412GHz  Access Point: 00:60:1D:1D:3E:0E
>           Bit Rate:1Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
>           Retry limit:4   RTS thr:off   Fragment thr:off
>           Power Management:off
>           Link Quality:15/92  Signal level:-74 dBm  Noise level:-89 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> dmesg:
> hermes.c: 3 Oct 2001 David Gibson <hermes@gibson.dropbear.id.au>
> orinoco.c 0.09a (David Gibson <hermes@gibson.dropbear.id.au> and others)
> orinoco_cs.c 0.09 (David Gibson <hermes@gibson.dropbear.id.au> and others)
> eth1: Station identity 001f:0001:0004:0034
> eth1: Looks like a Lucent/Agere firmware version 4.52
> eth1: Ad-hoc demo mode supported
> eth1: WEP supported, 104-bit key
> eth1: MAC address 00:60:1D:F1:04:67
> eth1: Station name "HERMES I"
> eth1: ready
> eth1: index 0x01: Vcc 5.0, irq 22, io 0x0100-0x013f
>
>
> Anyone else have this working with current kernels?
>
> with the older kernel:
>
> iwconfig:
> eth1      IEEE 802.11-DS  ESSID:"huber_net"  Nickname:"mystic"
>           Mode:Managed  Frequency:2.412GHz  Access Point: 00:60:1D:1D:3E:0E
>           Bit Rate:11Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
>           Retry limit:4   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
>
> dmesg:
> hermes.c: 3 Oct 2001 David Gibson <hermes@gibson.dropbear.id.au>
> orinoco.c 0.08 (David Gibson <hermes@gibson.dropbear.id.au> and others)
> orinoco_cs.c 0.08 (David Gibson <hermes@gibson.dropbear.id.au> and others)
> eth1: Station identity 001f:0001:0004:0034
> eth1: Looks like a Lucent/Agere firmware version 4.52
> eth1: Ad-hoc demo mode supported.
> eth1: WEP supported, "128"-bit key.
> eth1: MAC address 00:60:1D:F1:04:67
> eth1: Station name "HERMES I"
> eth1: Allowed channels mask: 0x000007ff
> eth1: ready
> eth1: index 0x01: Vcc 5.0, irq 22, io 0x0100-0x013f
>
>
> If you need any more info, just ask,
>
> --
> Josh Huber
>
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-01-19  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18  2:38 orinoco_cs on linuxppc_2_4/linux-2.4-benh Josh Huber
2002-01-19  1:52 ` John & Trudy Phillips [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.33.0201182034100.7255-100000@johntrudy.phillips.private \
    --to=johntrudy@earthlink.net \
    --cc=huber@alum.wpi.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).