Menu
▾
▴
wirelessdriver-support — EMail-based online support for the WirelessDriver project
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(38) |
Dec
(37) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(91) |
Feb
(53) |
Mar
(62) |
Apr
(53) |
May
(29) |
Jun
(57) |
Jul
(63) |
Aug
(154) |
Sep
(182) |
Oct
(154) |
Nov
(111) |
Dec
(83) |
| 2003 |
Jan
(77) |
Feb
(110) |
Mar
(66) |
Apr
(34) |
May
(41) |
Jun
(57) |
Jul
(47) |
Aug
(39) |
Sep
(28) |
Oct
(37) |
Nov
(27) |
Dec
(28) |
| 2004 |
Jan
(34) |
Feb
(12) |
Mar
(15) |
Apr
(16) |
May
(6) |
Jun
(17) |
Jul
(12) |
Aug
(14) |
Sep
(18) |
Oct
(5) |
Nov
(14) |
Dec
(19) |
| 2005 |
Jan
(15) |
Feb
(12) |
Mar
(1) |
Apr
(4) |
May
(16) |
Jun
(12) |
Jul
(3) |
Aug
(11) |
Sep
(2) |
Oct
(4) |
Nov
(2) |
Dec
(3) |
| 2006 |
Jan
(11) |
Feb
(6) |
Mar
(3) |
Apr
(3) |
May
(4) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
(1) |
| 2007 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Steven L. <st...@pa...> - 2003-01-26 15:09:15
|
I am having trouble with my AirPort Base Station. It is crashing frequently but "seems" to do this more when I use X than when I use 9.1. I have ventilated the ABS to aid in keeping it cooler as I know heat has been an issue with them. Is anyone else having this problem? Could it be related to the signal from my card fritzing with the ABS? DETAILS: Original ABS WallStreet using an Lucent Orinoco Gold WaveLAN card OS X.II.III (10.2.3) 384 MB.... Steve Lunetta -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "You use a glass mirror to see your face; you use works of art to see your soul." George Bernard Shaw http://www.pagetopage.net |
|
From: Abenstein, J. P., M.D. <abe...@ma...> - 2003-01-25 22:51:55
|
HELP!! I upgraded my G3 powerbook to 10.2 and now when I go to Network in System Preferences there is no option for eithernet adaptor (either en1 or en2). I've tried rebooting, taking the Linksys card in and out and nothing works. The wireless setup is all grayed out. What should I do? This worked great in 10.1!! Thanks John Abenstein abe...@ma... |
|
From: Master M. C. <mag...@co...> - 2003-01-25 16:41:11
|
I installed the new version drivers for os x 10.2 yet the troubleshooting software will not download. I am getting a signal of -79 or so, yet I can not pull an IP. I have tried entering my ip manually but I am having no luck. I can not connect to the internet, I use DHCP with my eithernet and I have the following hardware, I also have encription turned off. Powerbook G3 400 Firewire OS X 10.2.3 Lucent Orinoco WiFi Gold CompUSA 2.4 ghz 11Mbps |
|
From: Shlomo L. <SLe...@at...> - 2003-01-25 14:47:44
|
I have a Linksys - WPC54G card - on TiBook - running 10.2.3. The current driver does not "see" the card. Anything I can do ? Or do you plan future updates to include support for these cards? I would be happy to help with testing of beta versions. With thanks, Shlomo |
|
From: Master M. C. <mag...@co...> - 2003-01-25 08:08:56
|
I have just finished installing your software for OS X 10.2.x and my card; a Lucent Orinoco Gold, now lights up and seems to be receiving signals from my CompUSA Base Station. I however do not know what the network name is or how to really set this up, I have looked through your FAQ and done the following; I have selected en1 I am using DHCP I have Encription turned off I am still not getting any signal in the wireless config menu or able to connect to the internet when right next to the base station. I push apply when I change settings I have tried entering the ip address I get from my standard eithernet connection yet I am having no luck. I can only guess I need to enter a network name yet I have no idea what that is or were to find it, as I said I am new to OS X. Please let me know what I can do. I tried to download the troubleshooter but it says page not found. Thank you for any help. Oh and I am on a Pismo G3 w/G4 500 Powerlogix chip and 384 RAM, if that helps OS X 10.2.3 Thank you again. |
|
From: Matthew T. R. <mru...@sp...> - 2003-01-24 19:28:06
|
On Friday, January 24, 2003, at 11:59 AM, Gerald Clare wrote: > I have the above PCMCIA card for which ASANTE supplies only a PC > driver. I would have liked to use this with my TI PowerBook G4. Is > there any possibility to get a MAC driver for this? The Asante AL1511 is an Atmel-based card, not a Prism/Prism2/Prism2.5. So it won't work with this driver. I have a driver which works with the SMC 2632W V2.0, which is also an Atmel-based card; it might work with your card as well, though I'd need the matching information (the output of ioreg -w0 -c IOPCCard16Device is sufficient, though overkill). And you'd have to be willing to be something of a guinea pig; I've only tested the driver with one system on one card. Also one possible problem problem is that there are three different versions of the AT76C502 chip which this card uses, and my driver is only set up to deal with one of them. |
|
From: Gerald C. <gc...@bt...> - 2003-01-24 17:00:00
|
I have the above PCMCIA card for which ASANTE supplies only a PC driver. I would have liked to use this with my TI PowerBook G4. Is there any possibility to get a MAC driver for this? Gerald Clare |
|
From: MichaelM <mic...@ha...> - 2003-01-24 10:48:39
|
I saw a post from someone saying that their Compact Flash PCMCIA reader
was not working properly after installing the Wireless Driver. I am
experiencing the same problem where my PCMCIA Smart Media reader is not
mounting on the Desktop. I can access it by going to /Volumes/Unlabled but
it does not mount on the desktop. This would be fine except I cannot
unmount it before ejecting the card and the OS always complains about me
removing a drive before unmounting it.
This has only happened after updating my OS to 10.2.3 so there is a
chance that this is either unrelated to the Wireless Driver or it only
happens with the Wireless Driver and 10.2.3. I tried uninstalling the
driver with both the uninstall script and manually. The funny thing is that
even after uninstalling the driver the PC Card menu still shows up in the
menu bar when I insert a card. Is that menu supposed to be there even
without the Wireless Driver installed?
If anyone has any suggestions or if you are experiencing the same
problem please reply to this message.
Thank You,
Michael Maeda
|
|
From: Ron B. <ron...@at...> - 2003-01-23 22:00:46
|
Hi Rob,
Darn, your right! Just checked the Proxim site to confirm that the =20
card is PCMCIA (PC card actually). This brings up two other =20
interesting issues with Apple System Profiler:
The first is that System Profiler states that my built-in ethernet on =20=
my Lombard laptop is the one in use (it includes the MAC and IP =20
addresses of the wireless card). It doesn't event say anything about =20=
the wireless card interface.
The second is that the Cardbus dump states that the card installed is =20=
Cardbus (not pcmcia or pc card), which is why I initially thought it =20
was Cardbus. I have attached the text dump from Apple's System =20
Profiler... it might have significance, or it might be that the =20
profiler is simply buggy.
Network Overview:=09
Built-in:=09
=20
+----------------------------------------------------------------------+
| =
=20
|
| Flags : =20
0x8863<Up,Broadcast,b6,Running,Simplex,Multicast> |
| Ethernet address : xx.xx.xx.xx.xx.xx (edited =20=
out by ron)|
| IP : 192.168.0.2 =
=20
|
| Subnet Mask : 255.255.255.0 =
=20
|
| Broadcast : 192.168.0.255 =
=20
|
| =
=20
|
=20
+----------------------------------------------------------------------+
Devices and Volumes
---------------------------------------------------
PCI:=09
PC Card:=09
=20
+----------------------------------------------------------------------+
| =
=20
|
| Card Type : cardbus =
=20
|
| Card Name : cardbus =
=20
|
| Card Model : TXN,PCI1210-00 =
=20
|
| Vendor ID : 104c =
=20
|
| Device ID : ac1e =
=20
|
| ROM# : Not available =
=20
|
| Revision : 0 =
=20
|
| =
=20
|
=20
+----------------------------------------------------------------------+
Finally, a clarification for those using Orinoco Silver cards. 64 bit =20=
WEP does work!!! However, 128 bit WEP does not (at least with the =20
netgear MR314). Mac OS X 10.2.3.
Thanks a bunch. -Ron
On Thursday, January 23, 2003, at 01:56 PM, Rob McKeever wrote:
> I've got a PowerBook 101-series as well (frequently called Lombard). =20=
> I don't have a CardBus card handy, but it might very well be a problem =
=20
> on Apple's end.
>
> The Intersil and Lucent cards are 16-bit PCMCIA cards and don't use =20=
> the 32-bit CardBus spec and thus work differently in the OS. I'll =20
> make some inquiries and see if I can find anything out.
>
> -Rob
>
>
> On Thursday, January 23, 2003, at 10:03 AM, Ron Benoit wrote:
>
>> Greetings,
>>
>> First, this is not a wireless driver problem or feature request. I =20=
>> have a Orinoco Silver card, and have never had problems with 5.1beta =20=
>> (except that I can't use WEP with my NetGear MR314 router... but =20
>> that's another story). Hats off to the authors and the numerous =20
>> folks on the list who assist others.
>>
>> This question has to do with how the 5.1 beta overcomes a major =20
>> problem with the Lombard laptops and 10.2.3 with respect to Cardbus =20=
>> support. It appears that Cardbus is not fully supported on Lombard =20=
>> in version 10.2.x. I have been reading may such issues on Apple's =20=
>> support forums, and I have officially received the following reply =20=
>> from Asante:
>> -------------
>> Ron,
>>
>> The PowerBook/G3 Series
>> (Bronze Keyboard)
>>
>> Codename: 101, Lombard
>> CPU: PowerPC 750
>> CPU speed: 333/400 Mhz
>>
>> This failure has been verified by Asant=E9 in Apple's Labs. This is =
an =20
>> issue
>> with the Operating System (and Apple un-officially agrees with this
>> assessment by Asant=E9). The CardBus card is not supported in the =20=
>> Lombard
>> series G3 with OS/10.2.3. The issue here is a CardBus issue and not =
a
>> problem with the up-grade card in this laptop.
>> -------------
>>
>> I have been trying to get an Asante 10/100 Friendlynet card working =20=
>> since Jaguar was released. They say it's a cardbus issue (supposedly =
=20
>> confirmed by Apple, but there are no tech notes to support it). I =20=
>> say they are full of crap because my Orinoco Silver card (cardbus) =20=
>> works just fine. However, a lot of folks with Wallstreet and Lombard =
=20
>> laptops are having a lot of cardbus issues.
>>
>> So the question is, is there some sort of fix for these cardbus =20
>> issues in the wireless driver code?
>>
>> Thanks in advance! A very happy yet very frustrated user. -Ron
>>
>>
>> -------------------------------------------------------
>> This SF.NET email is sponsored by:
>> SourceForge Enterprise Edition + IBM + LinuxWorld Something 2 See!
>> http://www.vasoftware.com
>> _______________________________________________
>> Wirelessdriver-support mailing list
>> Wir...@li...
>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support
>>
> --
> "Quidquid latine dictum sit, altum viditur."
>
|
|
From: Rob M. <ro...@ma...> - 2003-01-23 20:56:38
|
I've got a PowerBook 101-series as well (frequently called Lombard). I=20= don't have a CardBus card handy, but it might very well be a problem on=20= Apple's end. The Intersil and Lucent cards are 16-bit PCMCIA cards and don't use the=20= 32-bit CardBus spec and thus work differently in the OS. I'll make=20 some inquiries and see if I can find anything out. -Rob On Thursday, January 23, 2003, at 10:03 AM, Ron Benoit wrote: > Greetings, > > First, this is not a wireless driver problem or feature request. I=20 > have a Orinoco Silver card, and have never had problems with 5.1beta=20= > (except that I can't use WEP with my NetGear MR314 router... but=20 > that's another story). Hats off to the authors and the numerous folks=20= > on the list who assist others. > > This question has to do with how the 5.1 beta overcomes a major=20 > problem with the Lombard laptops and 10.2.3 with respect to Cardbus=20 > support. It appears that Cardbus is not fully supported on Lombard in=20= > version 10.2.x. I have been reading may such issues on Apple's=20 > support forums, and I have officially received the following reply=20 > from Asante: > ------------- > Ron, > > The PowerBook/G3 Series > (Bronze Keyboard) > > Codename: 101, Lombard > CPU: PowerPC 750 > CPU speed: 333/400 Mhz > > This failure has been verified by Asant=E9 in Apple's Labs. This is = an=20 > issue > with the Operating System (and Apple un-officially agrees with this > assessment by Asant=E9). The CardBus card is not supported in the=20 > Lombard > series G3 with OS/10.2.3. The issue here is a CardBus issue and not a > problem with the up-grade card in this laptop. > ------------- > > I have been trying to get an Asante 10/100 Friendlynet card working=20 > since Jaguar was released. They say it's a cardbus issue (supposedly=20= > confirmed by Apple, but there are no tech notes to support it). I say=20= > they are full of crap because my Orinoco Silver card (cardbus) works=20= > just fine. However, a lot of folks with Wallstreet and Lombard=20 > laptops are having a lot of cardbus issues. > > So the question is, is there some sort of fix for these cardbus issues=20= > in the wireless driver code? > > Thanks in advance! A very happy yet very frustrated user. -Ron > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Wirelessdriver-support mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support > -- "Quidquid latine dictum sit, altum viditur." |
|
From: Matthew T. R. <mru...@sp...> - 2003-01-23 19:31:18
|
On Thursday, January 23, 2003, at 01:03 PM, Ron Benoit wrote: > Greetings, > This question has to do with how the 5.1 beta overcomes a major > problem with the Lombard laptops and 10.2.3 with respect to Cardbus > support. It appears that Cardbus is not fully supported on Lombard in > version 10.2.x. I have been reading may such issues on Apple's > support forums, and I have officially received the following reply > from Asante: The wireless 802.11b cards are not Cardbus (32-bit). They are 16-bit PCMCIA. |
|
From: ilvanLord <sil...@ho...> - 2003-01-23 19:24:53
|
I ran the troubleshooting script, and got this:
> ### system info
>=20
> ProductName: Mac OS X
> ProductVersion: 10.2.3
> BuildVersion: 6G30
> Darwin Lyps-nmaito.local. 6.3 Darwin Kernel Version 6.3: Sat Dec 14 03:11=
:25
> PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC Power Macintosh powerpc
> ppc7400
>=20
> ### wireless driver files installed
>=20
> drwxr-xr-x 3 root wheel 102 Jan 20 18:59 WirelessDriver.kext
> drwxr-xr-x 3 root wheel 102 Nov 5 22:04 IOPCCardFamily.kext
> ls: /Library/PreferencePanes: No such file or directory
>=20
> ### wirelesscard info
>=20
> | | | "VersionOneInfo" =3D ("Lucent Technologies","WaveLAN/IEEE=
","V$
> | | | "VersionOneInfo" =3D ("Lucent Technologies","WaveLAN/IE=
EE")
> | | +-o pccard156,2@0,0 <class IOPCCard16Device>
> | | | "IOName" =3D "pccard156,2"
>=20
> ### network info
>=20
> lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> inet6 ::1 prefixlen 128
> inet 127.0.0.1 netmask 0xff000000
> gif0: flags=3D8010<POINTOPOINT,MULTICAST> mtu 1280
> stf0: flags=3D0<> mtu 1280
> en2: flags=3D8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
> tunnel inet -->
> ether 00:02:2d:61:b6:88
> media: <unknown type>
> supported media: none manual autoselect DS1 <half-duplex> DS1
> <full-duplex> DS2 <half-duplex> DS2 <full-duplex> DS5 <half-duplex> DS5
> <full-duplex> DS11 <half-duplex> DS11 <full-duplex>
> en0: flags=3D8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
> tunnel inet -->
> ether 00:03:93:01:08:80
> en1: flags=3D8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet6 fe80::230:65ff:fe1b:71f3%en1 prefixlen 64 scopeid 0x6
> inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255
> ether 00:30:65:1b:71:f3
> media: autoselect status: active
> supported media: autoselect
>=20
> ### wd command line tool status
What should I do now?
--=20
[=A7ilvanLord] 510.272.9728
http://www.silvanlord.com
a virraszt=F3 nyomor=FAs=E1g
piros par=E1zs-szeme nyitva
s v=F6r=F6s var=E1zs-zene sz=EDtja
l=E1ngra t=FCzes tanait.
J'aurais voulu me casser l'=E2me,
j'aurais voulu ne pas mourir.
se joka ei ole n=E4hnyt surua,
ei koskaan n=E4e iloa.
in der K=FCrze
liegt die W=FCrze.
Strc prst skrz krk!
|
|
From: Ron B. <ron...@at...> - 2003-01-23 18:03:54
|
Greetings, First, this is not a wireless driver problem or feature request. I=20 have a Orinoco Silver card, and have never had problems with 5.1beta=20 (except that I can't use WEP with my NetGear MR314 router... but that's=20= another story). Hats off to the authors and the numerous folks on the=20= list who assist others. This question has to do with how the 5.1 beta overcomes a major problem=20= with the Lombard laptops and 10.2.3 with respect to Cardbus support. =20 It appears that Cardbus is not fully supported on Lombard in version=20 10.2.x. I have been reading may such issues on Apple's support forums,=20= and I have officially received the following reply from Asante: ------------- Ron, The PowerBook/G3 Series (Bronze Keyboard) Codename: 101, Lombard CPU: PowerPC 750 CPU speed: 333/400 Mhz This failure has been verified by Asant=E9 in Apple's Labs. This is an=20= issue with the Operating System (and Apple un-officially agrees with this assessment by Asant=E9). The CardBus card is not supported in the = Lombard series G3 with OS/10.2.3. The issue here is a CardBus issue and not a problem with the up-grade card in this laptop. ------------- I have been trying to get an Asante 10/100 Friendlynet card working=20 since Jaguar was released. They say it's a cardbus issue (supposedly=20 confirmed by Apple, but there are no tech notes to support it). I say=20= they are full of crap because my Orinoco Silver card (cardbus) works=20 just fine. However, a lot of folks with Wallstreet and Lombard laptops=20= are having a lot of cardbus issues. So the question is, is there some sort of fix for these cardbus issues=20= in the wireless driver code? Thanks in advance! A very happy yet very frustrated user. -Ron= |
|
From: ilvanLord <sil...@ho...> - 2003-01-23 12:17:47
|
It was recommended that I use the troubleshooting script, but I was unable to download the script: "Not Found - The requested URL /utilities/troubleshooting.sit was not found on this server. Apache/1.3.26 Server at wirelessdriver.sourceforge.net Port 80." Is there a mirror, or another way to get the script? --=20 [=A7ilvanLord] 510.272.9728 http://www.silvanlord.com a virraszt=F3 nyomor=FAs=E1g piros par=E1zs-szeme nyitva s v=F6r=F6s var=E1zs-zene sz=EDtja l=E1ngra t=FCzes tanait. J'aurais voulu me casser l'=E2me, j'aurais voulu ne pas mourir. se joka ei ole n=E4hnyt surua, ei koskaan n=E4e iloa. in der K=FCrze liegt die W=FCrze. Strc prst skrz krk! |
|
From: Nick S. <ns...@qu...> - 2003-01-23 00:31:02
|
Rob McKeever wrote: > Nice assumptions, but... > > 1) Apple isn't using the Intersil PRISM GT chipset. They are using a > Broadcom chip. This info comes from the hardware team involved. My bad. Fortunately, the Linksys WPC54G is also a Broadcom device under the covers > > > 2) There will need to be some work done to support the cardbus > interface. It is more than a little bit different than a 16-bit > PCCard interface as it tries to handle things as if they were > hot-swappable PCI devices, like PCI-X. Ah, but I am suggesting that the Airport Extreme driver is not the same one as the ordinary Airport driver. Since Apple's Airport Extreme card is mini PCI, the more relevant comparison is between Cardbus drivers and PCI drivers. I am hoping that Apple's Airport Extreme card drivers can be trivially configured to talk to a Cardbus card (that is, you can take a driver that normally talks to an IOPCIDevice and make it talk instead to an IOCardBusDevice that implements the same hardware interface). I suspect that they're not going to ship Airport Extreme hardware until 10.2.4 is out, which I suspect will contain an AirportExtreme.kext. > > > 3) You could get the Airport Extreme card to work in a desktop with > some work... namely a PCI adapter board. There will likely be other > issues you'd come across, but you wouldn't know in advance. As soon as the parts (a WMP-11 and Apple's AE module) arrive, I'm going to try it. |
|
From: Jonathan P. <jo...@ma...> - 2003-01-22 21:10:05
|
> un-install orinoco software for os 9, then see if apple airport > recognizes your card, it does for me, I use airport as the driver for > orinoco on my wspbook in os 9, works dandy. For X.2, or 10.2, the wireless driver installer it self was used,(not the combined installer) (check the installers folder)to have the file: WirelessDriver.kext placed in system.library.extensions. Then a restart. This worked for me. Jjjjjjjjjjjjjjj. |
|
From: Rob M. <ro...@ma...> - 2003-01-22 20:30:39
|
Nice assumptions, but... 1) Apple isn't using the Intersil PRISM GT chipset. They are using a Broadcom chip. This info comes from the hardware team involved. 2) There will need to be some work done to support the cardbus interface. It is more than a little bit different than a 16-bit PCCard interface as it tries to handle things as if they were hot-swappable PCI devices, like PCI-X. 3) You could get the Airport Extreme card to work in a desktop with some work... namely a PCI adapter board. There will likely be other issues you'd come across, but you wouldn't know in advance. -Rob On Wednesday, January 22, 2003, at 09:54 AM, Nick Sayer wrote: > This perhaps isn't the absolutely correct place to ask, but I couldn't > really think of a better audience. > > I have a TiBook, so there's no hope of shoehorning the new Airport > Extreme mini PCI device in, but I had a thought and wanted to throw it > up for folks to kick around. > > I bought a Linksys WPC54G. When I stick it in the TiBook, I see it in > ioreg as a IOCardBusDevice.... But it looks a lot like a PCI device. > This is sensible, since so far as I am aware, Cardbus was designed to > look from a driver perspective more like PCI than PCCard. > > Well, Airport Extreme is a miniPCI device, which makes it look > *exactly* like PCI. > > I have already speculated that if you took a Linksys WMP11 and > replaced its 802.11b module with an Apple Airport Extreme module that > you'd be able to use Apple's own drivers to get desktop macs (with PCI > slots) able to use Airport Extreme. > > But I believe we can go further. If we start with a presumption that > everyone's using the Prism GT chipset for 802.11g, I suspect that > merely by editing the Airport Extreme driver's Info.plist file and > adding entries for the stuff that kicks back from ioreg about the > WPC54G that Apple's own driver will be able to deal with this card, at > least in some limited way. > > This immediately tosses up some question marks: Apple's own airport > tab in the network system prefs probably doesn't understand > hot-swappable hardware (meaning you may need to leave the card in from > power-up), and it may not understand having both an Apple Airport > module and an Airport Extreme card in the same machine at the same > time (meaning you may need to disable the Airport module somehow). All > of these questions remain unanswered mainly because no one has Apple's > Airport Extreme driver yet (perhaps coming soon in 10.2.4?). > > What Apple really ought to do is provide an SDK and/or some other > driver specification so that 3rd parties could hook into Apple's > Airport network control panel, but I suspect they would rather folks > buy new powerbooks instead. :-/ > > Any thoughts? > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Scholarships for Techies! > Can't afford IT training? All 2003 ictp students receive scholarships. > Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. > www.ictp.com/training/sourceforge.asp > _______________________________________________ > Wirelessdriver-support mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support > -- "Quidquid latine dictum sit, altum viditur." |
|
From: Nick S. <ns...@qu...> - 2003-01-22 17:54:15
|
This perhaps isn't the absolutely correct place to ask, but I couldn't really think of a better audience. I have a TiBook, so there's no hope of shoehorning the new Airport Extreme mini PCI device in, but I had a thought and wanted to throw it up for folks to kick around. I bought a Linksys WPC54G. When I stick it in the TiBook, I see it in ioreg as a IOCardBusDevice.... But it looks a lot like a PCI device. This is sensible, since so far as I am aware, Cardbus was designed to look from a driver perspective more like PCI than PCCard. Well, Airport Extreme is a miniPCI device, which makes it look *exactly* like PCI. I have already speculated that if you took a Linksys WMP11 and replaced its 802.11b module with an Apple Airport Extreme module that you'd be able to use Apple's own drivers to get desktop macs (with PCI slots) able to use Airport Extreme. But I believe we can go further. If we start with a presumption that everyone's using the Prism GT chipset for 802.11g, I suspect that merely by editing the Airport Extreme driver's Info.plist file and adding entries for the stuff that kicks back from ioreg about the WPC54G that Apple's own driver will be able to deal with this card, at least in some limited way. This immediately tosses up some question marks: Apple's own airport tab in the network system prefs probably doesn't understand hot-swappable hardware (meaning you may need to leave the card in from power-up), and it may not understand having both an Apple Airport module and an Airport Extreme card in the same machine at the same time (meaning you may need to disable the Airport module somehow). All of these questions remain unanswered mainly because no one has Apple's Airport Extreme driver yet (perhaps coming soon in 10.2.4?). What Apple really ought to do is provide an SDK and/or some other driver specification so that 3rd parties could hook into Apple's Airport network control panel, but I suspect they would rather folks buy new powerbooks instead. :-/ Any thoughts? |
|
From: Martin J. <mjo...@ma...> - 2003-01-21 20:12:03
|
On Tuesday, January 21, 2003, at 07:44 Hi!, Nick Harvey wrote: > Had anyone tried the driver successfully with any of the USB adaptors, > or have any clues as to how to enable an imac that cannot take cards > or cables? Hi, You can use ethernet based wireless access points, then you don't need any special software or drivers either. Also you could check the macsense website I think the prime mover behind this driver might have developed USB drivers for them... Marty |
|
From: John L. <je...@ma...> - 2003-01-21 19:28:37
|
The driver does not support USB adapters. I believe there are, or will be, USB drivers available for purchase, but I have no further info. On Tuesday, January 21, 2003, at 09:44 AM, Nick Harvey wrote: > Had anyone tried the driver successfully with any of the USB adaptors, > or have any clues as to how to enable an imac that cannot take cards > or cables? > > Any and all input appreciated > -- > > regards, > > Nick Harvey > Orange Hand Systems, London > > Apple Mac, Networking, Telecoms and Hosting Solutions > > > http://www.orangehand.net > mailto:ni...@or... > > > ------------------------------------------------------- > This SF.net email is sponsored by: Scholarships for Techies! > Can't afford IT training? All 2003 ictp students receive scholarships. > Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. > www.ictp.com/training/sourceforge.asp > _______________________________________________ > Wirelessdriver-support mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-support |
|
From: Nick H. <ni...@or...> - 2003-01-21 15:43:26
|
Had anyone tried the driver successfully with any of the USB adaptors, or have any clues as to how to enable an imac that cannot take cards or cables? Any and all input appreciated -- regards, Nick Harvey Orange Hand Systems, London Apple Mac, Networking, Telecoms and Hosting Solutions http://www.orangehand.net mailto:ni...@or... |
|
From: jim t. <ji...@ma...> - 2003-01-21 11:01:37
|
After further digging I found the solution amongst a couple of posts,
so here it is, consolidated for your pleasure:
Boot into OS9: Delete "Extensions.kextcache" and "Extensions.mkext"
from /System/Library (don't worry, they get created again by your Mac).
Reboot into OS X.2.1
Run the troubleshooting script included with the installer and get the
"IOName" from the "###wirelesscard info" section:
### wirelesscard info
| | "VersionOneInfo" = ("NETGEAR MA401RA Wireless
PC","Card","I$
| | +-o pccardb,7300@0,0 <class IOPCCard16Device>
| | "IOName" = "pccardb,7300"
> Modify info.plist by typing the following command in the terminal
to edit this file with the pico text editor:
sudo pico
/System/Library/Extensions/WirelessDriver.kext/Contents/Info.plist
scroll down to the "everything else" section as seen here:
<key>everything else</key>
<dict>
<key>CFBundleIdentifier</key>
<string>org.noncontiguous.WirelessDriver</string>
<key>IOClass</key>
<string>org_noncontiguous_WirelessDriver</string>
<key>IONameMatch</key>
<array>
<string>pccard156,2</string>
<string>pccard1eb,807</string>
<string>pccard274,1613</string>
<string>pccard274,1612</string>
<string>pccard138,2</string>
</array>
>
> and add your IOName string (pccardb,7300 in the case of the MA401RA)
as found in the troubleshooting script as an entry in this array like
so:
<array>
<string>pccard156,2</string>
<string>pccard1eb,807</string>
<string>pccard274,1613</string>
<string>pccard274,1612</string>
<string>pccard138,2</string>
<string>pccard101,696</string>
<string>pccardb,7300</string>
</array>
to save the file type ctrl-x and accept the changes. View the edited
file in the terminal to be sure your changes are correct:
more /System/Library/Extensions/WirelessDriver.kext/Contents/Info.plist
now remove and re-insert the card, go to network prefs and (hopefully)
see that en1 has appeared. Configure with the WirelessDriver Preference
Pane, everything should work fine.
Thanks to those who provided the pieces,
jimt
On Monday, January 20, 2003, at 01:38 PM,
wir...@li... wrote:
> Hi,
> I've been through months of other 'no en1' postings trying everything
> that I could before posting here, but I can't get anything besides ir,
> modem and built in ethernet to show up in net prefs. My Netgear MA401RA
> shows up in the menubar and in the troubleshooting script, and it works
> on my uncle's thinkpad.
> I have uninstalled, checked the sys/lib/ext and prefpanes and the items
> were gone, then i reinstalled and rebooted, no en1 (but
> WirelessDriver.kext is in System/Library/Extensions and WirelessDriver
> PPane.prefPane is in System/Library/PreferencePanes), reinstalled and
> rebooted again, still no en1. I manually loaded with kextload
> System/Library/Extensions/WirelessDriver.kext in Terminal, and it
> loads, but still no en1 in net prefs. The prefpane is in the system
> prefs, but everything is greyed out.
> This is on a TiBook 500/256
>
> TIA,
> jimt
>
> Here's my tshoot info:
>
> ### system info
>
> ProductName: Mac OS X
> ProductVersion: 10.2.3
> BuildVersion: 6G30
> Darwin jimts-Computer.local. 6.3 Darwin Kernel Version 6.3: Sat Dec 14
> 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC Power
> Macintosh powerpc
> ppc7400
>
> ### wireless driver files installed
>
> drwxr-xr-x 3 root wheel 102 Jan 20 07:36 WirelessDriver.kext
> drwxr-xr-x 3 root wheel 102 Nov 5 23:04 IOPCCardFamily.kext
> ls: /Library/PreferencePanes: No such file or directory
>
> ### wirelesscard info
>
> | | "VersionOneInfo" = ("NETGEAR MA401RA Wireless
> PC","Card","I$
> | | +-o pccardb,7300@0,0 <class IOPCCard16Device>
> | | "IOName" = "pccardb,7300"
>
> ### network info
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> inet 127.0.0.1 netmask 0xff000000
> gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
> stf0: flags=0<> mtu 1280
> en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet6 fe80::203:93ff:fe10:1a7e%en0 prefixlen 64 scopeid 0x4
> ether 00:03:93:10:1a:7e
> media: autoselect (none) status: inactive
> supported media: none autoselect 10baseT/UTP <half-duplex>
> 10baseT/UTP <half-duplex,hw-loopback> 10baseT/UTP <full-duplex>
> 10baseT/UTP <full-duplex,hw-loopback> 100baseTX <half-duplex> 100baseTX
> <half-duplex,hw-loopback> 100baseTX <full-duplex> 100baseTX
> <full-duplex,hw-loopback>
>
> ### wd command line tool status
>
> /Volumes/WirelessDriver beta 5.1/Utilities/Troubleshooting
> Info.command: WirelessConfig: command not found
> logout
> [Process completed]
|
|
From: Geoff C. <geo...@ma...> - 2003-01-21 05:08:42
|
Anybody know of any cost effective solutions for an access point that works with PPoE? Evidently the ORiNOCO AP-200 won't let you use PPoE to access the gateway. |
|
From: Dennis F. <df...@ma...> - 2003-01-21 01:30:41
|
--On Monday, January 20, 2003 12:41 PM -0800 =A7ilvanLord=20 <sil...@ho...> wrote: The faq says "select the EN1 > interface as the active network setting," but there is no EN1 interface, > only AirPort, Infrared, and internal modem. What should I do? Try restarting with your Orinoco card plugged in. When you open up the=20 Network Pref panel and go to the "Network Port Configurations" popup, you=20 should see all your ports. A dialog box should pop on the screen notifying=20 you that you have a new interface. The cat5 ethernet port is en0 If you have an Airport card installed, that will be en1 Then the Orinoco card should be assigned en2 If no Airport, I believe the card should be assigned en1. Change the name if you want by double clicking on it, make sure the "On"=20 checkbox is checked, and then open the WirelessDriver config panel to set=20 it up. -- Dennis Fazio df...@ma... |
|
From: JLM <JL...@ho...> - 2003-01-21 01:29:09
|
On 2003-01-09 Larry Lovig wrote:
> After installing Wireless Driver Beta 5_1 twice, I am still not seeing
> EN1, EN2 or EN anything in my Network Preferences.
> [snip]
> What do you suggest?
I struggled with the same problem, also installing the software twice
without any luck. Upon checking the /System/Library/Extensions/ folder, I
noticed that there was no wireless driver installed. It would seem there is
a permissions problem that is preventing the installer from placing the
driver in the above-mentioned folder.
Using Pseudo to run the installer package may do the trick, but following
are the steps I used to successfully install the driver on my TiBook running
10.2.3.
1. Download and expand the WirelessDriverBeta5_1.tgz archive.
2. Open the folder called "Installers"
3. Right-click "WirelessDriver.pkg" and select "Show Package Contents"
4. Open the "Contents" folder that appears and expand "Archive.pax.gz"
5. "WirelessDriver.kext" is the only file in that archive, and that's the
only file we need. Copy it to your Home directory.
6. Open Terminal. Copy and paste the following commands in succession,
entering in your Administrator password when prompted:
sudo mv ~/WirelessDriver.kext /System/Library/Extensions/WirelessDriver.kext
sudo chown -R root.wheel /System/Library/Extensions/WirelessDriver.kext
7. Reboot.
That's it. Upon reboot, I saw the "EN2" Ethernet interface in the Network
control panel, and I was able to connect wirelessly without any additional
hassles.
I hope this helps those who have encountered this problem. If you have any
questions or comments, please do so off-list as I am not subscribed.
Best regards,
Justin
JLM939 {at} hotmail
--
Shinza.com: Bringing You Japan's Best High-Tech Gadgets
http://shinza.com/
|
5 messages has been excluded from this view by a project administrator.
