From gbhembree at comcast.net Wed Aug 6 08:26:53 2008 From: gbhembree at comcast.net (Barry Hembree) Date: Wed, 6 Aug 2008 09:26:53 -0500 Subject: G4 Powerbook Wireless Message-ID: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> Hi All, I recently installed ydl 6.0 on my g4 powerbook. I am having a hard time getting the wireless interface to work. I followed the instructions in the various threads but still no luck. Here are the step I took: 1) bownloaded and compiled the fwcutter program (I have the wired ethernet connection working) 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I don't have Mac OS X on my computer anymore) 3) Tried various combination of editing configuration files by hand and using the network-config app. I do get an error message when I try to activate the device as follows: Error wireless request "Set Mode (8B06)" any help at this point would be gratly appreciated. I have spent far too many hours on this. Thanks Barry From dcenteno at ydl.net Wed Aug 6 20:00:03 2008 From: dcenteno at ydl.net (Derick Centeno) Date: Wed, 06 Aug 2008 22:00:03 -0400 Subject: G4 Powerbook Wireless In-Reply-To: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> Message-ID: <20080806220003.6eb208c9@arakus> Hi Barry! I've got the same type of computer you do. According to the references I found on-line regarding wl-4.80.53.0, for whatever reason, it is buggy and doesn't work. The only way around this is to have OS X running such that fwcutter can extract the firmware from it. I understand your feelings regarding OS X, I commiserate. However, a running version which is used such that a viable version of the firmware becomes extracted from it is the best way to insure the quality of firmware you acquire and import into YDL. I don't envy the work ahead; I can only state that once you pass that stage you may find that the effort was worth it. The instructions on this page still work: http://www.terrasoftsolutions.com/support/solutions/ydl_5.x/airport-extreme.shtml Problems I found: [root at arakus b43-fwcutter-009]# ./b43-fwcutter -w /lib/firmware/ \/mnt/macosx/Sys*/Libr*/Ex*/Ap*/Con*/Ma*/AppleAirPort2 Sorry, the input file is either wrong or not supported by b43-fwcutter. This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. [root at arakus b43-fwcutter-009]# [root at arakus bcm43XX-fwcutter-006]# ./bcm43XX-fwcutter -w /lib/firmware/ \/mnt/macosx/System/Library/Extensions/AppleAirPort2.kext/Contents/MacOS/AppleAirPort2 Sorry, the input file is either wrong or not supported by bcm43XX-fwcutter. This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. The above was resolved by NOT copying over the ifcfg-eth1 file with the ifcfg-eth0 file. Also the HWADDR variable in ifcfg-eth1 != the HWADDR variable in ifcfg-eth0. Anaconda creates both files with different definitions for the hardware location accessed for Ethernet (eth0) and Wireless (eth1). What follows is the ifcfg-eth1 file settings located in /etc/sys*/net*scripts: # Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller DEVICE=eth1 ONBOOT=no BOOTPROTO=dhcp HWADDR=00:11:24:90:c3:d8 NETMASK= DHCP_HOSTNAME=arakus IPADDR= DOMAIN= TYPE=Wireless ESSID=off/any CHANNEL=1 MODE=Managed RATE=Auto USERCTL=yes IPV6INIT=yes PEERDNS=yes After reboot, it is then possible to do the standard manual invocation of eth1 via the terminal. The sequence anywhere else entails looking/scanning for signals and using the essid which are available and/or to those essid's key i've been given to use (in the event of an encrpted network: 1. #ifconfig eth1 up 2. #iwconfig eth1 3. #iwlist eth1 scanning 4. #iwconfig eth1 channel 6 txpower on rate auto essid ???????????? 5. #dhclient eth1 Explanation: ? represent #'s and letters identifying a router or password. In the event a router's signal has a name line 4 should be: #iwconfig eth1 channel 6 txpower on rate auto essid 'xxxxxxxxx' key ????????????????? where x are the char forming the name and the key is the password sequence to that protected router. Of course if you decide to use wpa-supplicant -- a good idea as it is better security, then the sequence of initiating connection between airport extreme and the router will be different. All the best... On Wed, 6 Aug 2008 09:26:53 -0500 Barry Hembree wrote: > Hi All, > > I recently installed ydl 6.0 on my g4 powerbook. I am having a hard > time getting the wireless interface to work. I followed the > instructions in the various threads but still no luck. Here are the > step I took: > > 1) bownloaded and compiled the fwcutter program (I have the wired > ethernet connection working) > 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I don't > have Mac OS X on my computer anymore) > 3) Tried various combination of editing configuration files by hand > and using the network-config app. > > I do get an error message when I try to activate the device as follows: > > Error wireless request "Set Mode (8B06)" > > any help at this point would be gratly appreciated. I have spent far > too many hours on this. > > Thanks > Barry ===== "If I were not a physicist, I would probably be a musician. I often think in music. I live my daydreams in music. I see my life in terms of music. ... I get most joy in life out of music." "What Life Means to Einstein: An Interview by George Sylvester Viereck," for the October 26, 1929 issue of The Saturday Evening Post. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.terrasoftsolutions.com/pipermail/yellowdog-newbie/attachments/20080806/af824605/attachment.bin From ddxxlll at gmail.com Wed Aug 6 22:50:04 2008 From: ddxxlll at gmail.com (Dylan Klebesadel) Date: Wed, 6 Aug 2008 20:50:04 -0800 Subject: G4 Powerbook Wireless In-Reply-To: <20080806220003.6eb208c9@arakus> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> Message-ID: <6104e5d0808062150h3f69a3caj37e034ba4b10029c@mail.gmail.com> Why are you guys emailing my inbox I DON'T EVEN OWN A MAC OR YELLOWDOG. I would however like to know if yellowdog's Gnash supports flash 9 though because I am thinking of dual booting my ps3 so I can watch hulu videos on my 50 inch HDTV in full uncompressed 1080p on my couch On Wed, Aug 6, 2008 at 6:00 PM, Derick Centeno wrote: > Hi Barry! > > I've got the same type of computer you do. According to the references I > found > on-line regarding wl-4.80.53.0, for whatever reason, it is buggy and > doesn't > work. The only way around this is to have OS X running such that fwcutter > can > extract the firmware from it. > > I understand your feelings regarding OS X, I commiserate. However, a > running > version which is used such that a viable version of the firmware becomes > extracted from it is the best way to insure the quality of firmware you > acquire > and import into YDL. I don't envy the work ahead; I can only state that > once > you pass that stage you may find that the effort was worth it. > > The instructions on this page still work: > > http://www.terrasoftsolutions.com/support/solutions/ydl_5.x/airport-extreme.shtml > > Problems I found: > > [root at arakus b43-fwcutter-009]# ./b43-fwcutter -w /lib/firmware/ > \/mnt/macosx/Sys*/Libr*/Ex*/Ap*/Con*/Ma*/AppleAirPort2 Sorry, the input > file is > either wrong or not supported by b43-fwcutter. This file has an unknown > MD5sum > 85c71d658b650fd2ef546d1d81b113a0. > [root at arakus b43-fwcutter-009]# > > > [root at arakus bcm43XX-fwcutter-006]# ./bcm43XX-fwcutter -w /lib/firmware/ > > \/mnt/macosx/System/Library/Extensions/AppleAirPort2.kext/Contents/MacOS/AppleAirPort2 > Sorry, the input file is either wrong or not supported by bcm43XX-fwcutter. > This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. > > The above was resolved by NOT copying over the ifcfg-eth1 file with the > ifcfg-eth0 file. Also the HWADDR variable in ifcfg-eth1 != the HWADDR > variable > in ifcfg-eth0. Anaconda creates both files with different definitions for > the > hardware location accessed for Ethernet (eth0) and Wireless (eth1). > > What follows is the ifcfg-eth1 file settings located in > /etc/sys*/net*scripts: > > # Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller > DEVICE=eth1 > ONBOOT=no > BOOTPROTO=dhcp > HWADDR=00:11:24:90:c3:d8 > NETMASK= > DHCP_HOSTNAME=arakus > IPADDR= > DOMAIN= > TYPE=Wireless > ESSID=off/any > CHANNEL=1 > MODE=Managed > RATE=Auto > USERCTL=yes > IPV6INIT=yes > PEERDNS=yes > > After reboot, it is then possible to do the standard manual invocation of > eth1 > via the terminal. > > The sequence anywhere else entails looking/scanning for signals and using > the > essid which are available and/or to those essid's key i've been given to > use > (in the event of an encrpted network: > > 1. #ifconfig eth1 up > 2. #iwconfig eth1 > 3. #iwlist eth1 scanning > 4. #iwconfig eth1 channel 6 txpower on rate auto essid ???????????? > 5. #dhclient eth1 > > Explanation: ? represent #'s and letters identifying a router or password. > In the event a router's signal has a name line 4 should be: > > #iwconfig eth1 channel 6 txpower on rate auto essid 'xxxxxxxxx' > key ????????????????? > > where x are the char forming the name and the key is the password sequence > to > that protected router. > > Of course if you decide to use wpa-supplicant -- a good idea as it is > better > security, then the sequence of initiating connection between airport > extreme > and the router will be different. > > All the best... > > > On Wed, 6 Aug 2008 09:26:53 -0500 > Barry Hembree wrote: > > > Hi All, > > > > I recently installed ydl 6.0 on my g4 powerbook. I am having a hard > > time getting the wireless interface to work. I followed the > > instructions in the various threads but still no luck. Here are the > > step I took: > > > > 1) bownloaded and compiled the fwcutter program (I have the wired > > ethernet connection working) > > 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I don't > > have Mac OS X on my computer anymore) > > 3) Tried various combination of editing configuration files by hand > > and using the network-config app. > > > > I do get an error message when I try to activate the device as follows: > > > > Error wireless request "Set Mode (8B06)" > > > > any help at this point would be gratly appreciated. I have spent far > > too many hours on this. > > > > Thanks > > Barry > > > ===== > "If I were not a physicist, I would probably be a musician. I often > think in music. I live my daydreams in music. I see my life in terms of > music. ... I get most joy in life out of music." > > "What Life Means to Einstein: An Interview by George Sylvester > Viereck," for the October 26, 1929 issue of The Saturday Evening Post. > > _______________________________________________ > yellowdog-newbie mailing list > yellowdog-newbie at lists.terrasoftsolutions.com > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.terrasoftsolutions.com/pipermail/yellowdog-newbie/attachments/20080806/c709dc5c/attachment.html From dcenteno at ydl.net Thu Aug 7 05:57:30 2008 From: dcenteno at ydl.net (Derick Centeno) Date: Thu, 07 Aug 2008 07:57:30 -0400 Subject: G4 Powerbook Wireless In-Reply-To: <6104e5d0808062150h3f69a3caj37e034ba4b10029c@mail.gmail.com> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> <6104e5d0808062150h3f69a3caj37e034ba4b10029c@mail.gmail.com> Message-ID: <20080807075730.7b60885f@arakus> Dear Dylan: Clarification: I didn't directly email to you any message. I can't speak for anyone else. In general, when you register to participate in these lists there are options available which you choose which determine how you will receive postings individuals sent to the Mail Lists. Different communication media are available here: http://lists.terrasoftsolutions.com/. Briefly, change the options which you chose and what is sent to your mailbox will change. Explanation: The Linux universe, of which YDL is a part, is comprised of the efforts of many, many volunteers producing independent projects. YDL is one of many Linux distributions which share the use of these projects as part of complying with the General Public License (GPL). Gnash, available here, http://www.gnu.org/software/gnash is an independent project which also abides by the GPL. The people to contact regarding requests or features for gnash is the same link, which I'll repeat here: http://www.gnu.org/software/gnash/. Flash is a proprietary product which does not comply with the GPL. There is no claim or surely any reasonable expectation that Flash or Gnash can or do work the same way. There is no way to insure that what one individual finds an acceptable function will be appealing or satisfactory to another. As for the rest, it is great that you have some impressive technology available for you to enjoy. However, as I've clarified for you if there are features you wish to be included either within gnash or any other GPL project/product you need to contact and discuss your request with them. All the best... On Wed, 6 Aug 2008 20:50:04 -0800 "Dylan Klebesadel" wrote: > Why are you guys emailing my inbox I DON'T EVEN OWN A MAC OR YELLOWDOG. I > would however like to know if yellowdog's Gnash supports flash 9 though > because I am thinking of dual booting my ps3 so I can watch hulu videos on > my 50 inch HDTV in full uncompressed 1080p on my couch ===== "If I were not a physicist, I would probably be a musician. I often think in music. I live my daydreams in music. I see my life in terms of music. ... I get most joy in life out of music." "What Life Means to Einstein: An Interview by George Sylvester Viereck," for the October 26, 1929 issue of The Saturday Evening Post. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.terrasoftsolutions.com/pipermail/yellowdog-newbie/attachments/20080807/0011c63a/attachment.bin From gbhembree at comcast.net Thu Aug 7 16:16:53 2008 From: gbhembree at comcast.net (Barry Hembree) Date: Thu, 7 Aug 2008 17:16:53 -0500 Subject: G4 Powerbook Wireless In-Reply-To: <20080806220003.6eb208c9@arakus> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> Message-ID: <701960D8-DCAC-4321-BBBE-1553B57D9C18@comcast.net> Derick, Thanks for your response. I went ahead and installed Mac OS X back on my computer and upgraded it to the latest version. I don't seem to have an AppleAirport2 file. I only have a AppleAirport file. I think the AppleAirport2 file is pre-Leopard. The fwcutter program (I have tried two different versions) does not seem to want to extract the file I have. Any suggestions? Barry On Aug 6, 2008, at 9:00 PM, Derick Centeno wrote: > Hi Barry! > > I've got the same type of computer you do. According to the > references I found > on-line regarding wl-4.80.53.0, for whatever reason, it is buggy and > doesn't > work. The only way around this is to have OS X running such that > fwcutter can > extract the firmware from it. > > I understand your feelings regarding OS X, I commiserate. However, > a running > version which is used such that a viable version of the firmware > becomes > extracted from it is the best way to insure the quality of firmware > you acquire > and import into YDL. I don't envy the work ahead; I can only state > that once > you pass that stage you may find that the effort was worth it. > > The instructions on this page still work: > http://www.terrasoftsolutions.com/support/solutions/ydl_5.x/airport-extreme.shtml > > Problems I found: > > [root at arakus b43-fwcutter-009]# ./b43-fwcutter -w /lib/firmware/ > \/mnt/macosx/Sys*/Libr*/Ex*/Ap*/Con*/Ma*/AppleAirPort2 Sorry, the > input file is > either wrong or not supported by b43-fwcutter. This file has an > unknown MD5sum > 85c71d658b650fd2ef546d1d81b113a0. > [root at arakus b43-fwcutter-009]# > > > [root at arakus bcm43XX-fwcutter-006]# ./bcm43XX-fwcutter -w /lib/ > firmware/ > \/mnt/macosx/System/Library/Extensions/AppleAirPort2.kext/Contents/ > MacOS/AppleAirPort2 > Sorry, the input file is either wrong or not supported by bcm43XX- > fwcutter. > This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. > > The above was resolved by NOT copying over the ifcfg-eth1 file with > the > ifcfg-eth0 file. Also the HWADDR variable in ifcfg-eth1 != the > HWADDR variable > in ifcfg-eth0. Anaconda creates both files with different > definitions for the > hardware location accessed for Ethernet (eth0) and Wireless (eth1). > > What follows is the ifcfg-eth1 file settings located in /etc/sys*/ > net*scripts: > > # Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller > DEVICE=eth1 > ONBOOT=no > BOOTPROTO=dhcp > HWADDR=00:11:24:90:c3:d8 > NETMASK= > DHCP_HOSTNAME=arakus > IPADDR= > DOMAIN= > TYPE=Wireless > ESSID=off/any > CHANNEL=1 > MODE=Managed > RATE=Auto > USERCTL=yes > IPV6INIT=yes > PEERDNS=yes > > After reboot, it is then possible to do the standard manual > invocation of eth1 > via the terminal. > > The sequence anywhere else entails looking/scanning for signals and > using the > essid which are available and/or to those essid's key i've been > given to use > (in the event of an encrpted network: > > 1. #ifconfig eth1 up > 2. #iwconfig eth1 > 3. #iwlist eth1 scanning > 4. #iwconfig eth1 channel 6 txpower on rate auto essid ???????????? > 5. #dhclient eth1 > > Explanation: ? represent #'s and letters identifying a router or > password. > In the event a router's signal has a name line 4 should be: > > #iwconfig eth1 channel 6 txpower on rate auto essid 'xxxxxxxxx' > key ????????????????? > > where x are the char forming the name and the key is the password > sequence to > that protected router. > > Of course if you decide to use wpa-supplicant -- a good idea as it > is better > security, then the sequence of initiating connection between airport > extreme > and the router will be different. > > All the best... > > > On Wed, 6 Aug 2008 09:26:53 -0500 > Barry Hembree wrote: > >> Hi All, >> >> I recently installed ydl 6.0 on my g4 powerbook. I am having a hard >> time getting the wireless interface to work. I followed the >> instructions in the various threads but still no luck. Here are the >> step I took: >> >> 1) bownloaded and compiled the fwcutter program (I have the wired >> ethernet connection working) >> 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I don't >> have Mac OS X on my computer anymore) >> 3) Tried various combination of editing configuration files by hand >> and using the network-config app. >> >> I do get an error message when I try to activate the device as >> follows: >> >> Error wireless request "Set Mode (8B06)" >> >> any help at this point would be gratly appreciated. I have spent far >> too many hours on this. >> >> Thanks >> Barry > > > ===== > "If I were not a physicist, I would probably be a musician. I often > think in music. I live my daydreams in music. I see my life in terms > of > music. ... I get most joy in life out of music." > > "What Life Means to Einstein: An Interview by George Sylvester > Viereck," for the October 26, 1929 issue of The Saturday Evening Post. > _______________________________________________ > yellowdog-newbie mailing list > yellowdog-newbie at lists.terrasoftsolutions.com > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie From dcenteno at ydl.net Thu Aug 7 18:13:31 2008 From: dcenteno at ydl.net (Derick Centeno) Date: Thu, 07 Aug 2008 20:13:31 -0400 Subject: G4 Powerbook Wireless In-Reply-To: <701960D8-DCAC-4321-BBBE-1553B57D9C18@comcast.net> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> <701960D8-DCAC-4321-BBBE-1553B57D9C18@comcast.net> Message-ID: <489B8FAB.40700@ydl.net> Hi Barry: I found that you don't need the latest version of OS X; actually Tiger (10.4.6) is quite good enough. As Apple chose to drop the PPC, I'll be eventually switching to Windows so that I could do decent work and dual boot between Windows and YDL running on a 4 core Cell. So it's just as well that your question comes up now. Read carefully the instructions provided in the link discussing Airport Extreme, it tells you where the file you question is found. Please note that Airport Extreme was a special installation option I chose at the time I bought my G4 - so on my PB it is installed. Keeping that in mind the following can be executed from within the Terminal application found in Utilities within OS X. Here is what a Terminal session looks like revealing a portion of the directory in question; I'm showing a partial listing. Note that ... means sometime precedes and something follows: arakus:/System/Library/Extensions aguila$ ls ... AppleADT746x.kext AppleXsanFilter.kext ImmersionForceFeedback.kext AppleAirPort.kext Apple_iSight.kext KeyLargoATA.kext AppleAirPort2.kext AudioDeviceTreeUpdater.kext L2TP.ppp AppleAltiVecDVDDriver.bundle ... As far as the fwcutter application is concerned I stayed with the version listed in the example, the update or current version didn't work within YDL. So I stayed with what works. All the best... Barry Hembree wrote: > Derick, > > Thanks for your response. I went ahead and installed Mac OS X back on > my computer and upgraded it to the latest version. I don't seem to > have an AppleAirport2 file. I only have a AppleAirport file. I think > the AppleAirport2 file is pre-Leopard. The fwcutter program (I have > tried two different versions) does not seem to want to extract the > file I have. Any suggestions? > > Barry > > On Aug 6, 2008, at 9:00 PM, Derick Centeno wrote: > > >> Hi Barry! >> >> I've got the same type of computer you do. According to the >> references I found >> on-line regarding wl-4.80.53.0, for whatever reason, it is buggy and >> doesn't >> work. The only way around this is to have OS X running such that >> fwcutter can >> extract the firmware from it. >> >> I understand your feelings regarding OS X, I commiserate. However, >> a running >> version which is used such that a viable version of the firmware >> becomes >> extracted from it is the best way to insure the quality of firmware >> you acquire >> and import into YDL. I don't envy the work ahead; I can only state >> that once >> you pass that stage you may find that the effort was worth it. >> >> The instructions on this page still work: >> http://www.terrasoftsolutions.com/support/solutions/ydl_5.x/airport-extreme.shtml >> >> Problems I found: >> >> [root at arakus b43-fwcutter-009]# ./b43-fwcutter -w /lib/firmware/ >> \/mnt/macosx/Sys*/Libr*/Ex*/Ap*/Con*/Ma*/AppleAirPort2 Sorry, the >> input file is >> either wrong or not supported by b43-fwcutter. This file has an >> unknown MD5sum >> 85c71d658b650fd2ef546d1d81b113a0. >> [root at arakus b43-fwcutter-009]# >> >> >> [root at arakus bcm43XX-fwcutter-006]# ./bcm43XX-fwcutter -w /lib/ >> firmware/ >> \/mnt/macosx/System/Library/Extensions/AppleAirPort2.kext/Contents/ >> MacOS/AppleAirPort2 >> Sorry, the input file is either wrong or not supported by bcm43XX- >> fwcutter. >> This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. >> >> The above was resolved by NOT copying over the ifcfg-eth1 file with >> the >> ifcfg-eth0 file. Also the HWADDR variable in ifcfg-eth1 != the >> HWADDR variable >> in ifcfg-eth0. Anaconda creates both files with different >> definitions for the >> hardware location accessed for Ethernet (eth0) and Wireless (eth1). >> >> What follows is the ifcfg-eth1 file settings located in /etc/sys*/ >> net*scripts: >> >> # Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller >> DEVICE=eth1 >> ONBOOT=no >> BOOTPROTO=dhcp >> HWADDR=00:11:24:90:c3:d8 >> NETMASK= >> DHCP_HOSTNAME=arakus >> IPADDR= >> DOMAIN= >> TYPE=Wireless >> ESSID=off/any >> CHANNEL=1 >> MODE=Managed >> RATE=Auto >> USERCTL=yes >> IPV6INIT=yes >> PEERDNS=yes >> >> After reboot, it is then possible to do the standard manual >> invocation of eth1 >> via the terminal. >> >> The sequence anywhere else entails looking/scanning for signals and >> using the >> essid which are available and/or to those essid's key i've been >> given to use >> (in the event of an encrpted network: >> >> 1. #ifconfig eth1 up >> 2. #iwconfig eth1 >> 3. #iwlist eth1 scanning >> 4. #iwconfig eth1 channel 6 txpower on rate auto essid ???????????? >> 5. #dhclient eth1 >> >> Explanation: ? represent #'s and letters identifying a router or >> password. >> In the event a router's signal has a name line 4 should be: >> >> #iwconfig eth1 channel 6 txpower on rate auto essid 'xxxxxxxxx' >> key ????????????????? >> >> where x are the char forming the name and the key is the password >> sequence to >> that protected router. >> >> Of course if you decide to use wpa-supplicant -- a good idea as it >> is better >> security, then the sequence of initiating connection between airport >> extreme >> and the router will be different. >> >> All the best... >> >> >> On Wed, 6 Aug 2008 09:26:53 -0500 >> Barry Hembree wrote: >> >> >>> Hi All, >>> >>> I recently installed ydl 6.0 on my g4 powerbook. I am having a hard >>> time getting the wireless interface to work. I followed the >>> instructions in the various threads but still no luck. Here are the >>> step I took: >>> >>> 1) bownloaded and compiled the fwcutter program (I have the wired >>> ethernet connection working) >>> 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I don't >>> have Mac OS X on my computer anymore) >>> 3) Tried various combination of editing configuration files by hand >>> and using the network-config app. >>> >>> I do get an error message when I try to activate the device as >>> follows: >>> >>> Error wireless request "Set Mode (8B06)" >>> >>> any help at this point would be gratly appreciated. I have spent far >>> too many hours on this. >>> >>> Thanks >>> Barry >>> >> ===== >> "If I were not a physicist, I would probably be a musician. I often >> think in music. I live my daydreams in music. I see my life in terms >> of >> music. ... I get most joy in life out of music." >> >> "What Life Means to Einstein: An Interview by George Sylvester >> Viereck," for the October 26, 1929 issue of The Saturday Evening Post. >> _______________________________________________ >> yellowdog-newbie mailing list >> yellowdog-newbie at lists.terrasoftsolutions.com >> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie >> > > _______________________________________________ > yellowdog-newbie mailing list > yellowdog-newbie at lists.terrasoftsolutions.com > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie > > From dcenteno at ydl.net Thu Aug 7 18:21:54 2008 From: dcenteno at ydl.net (Derick Centeno) Date: Thu, 07 Aug 2008 20:21:54 -0400 Subject: G4 Powerbook Wireless - correction In-Reply-To: <701960D8-DCAC-4321-BBBE-1553B57D9C18@comcast.net> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> <701960D8-DCAC-4321-BBBE-1553B57D9C18@comcast.net> Message-ID: <489B91A2.9090502@ydl.net> Hi Barry: I found that you don't need the latest version of OS X; actually Tiger (10.4.6) is quite good enough. As Apple chose to drop the PPC, I'll be eventually switching to Windows so that I could do decent work and dual boot between Windows and YDL running on a 4 core Cell. So it's just as well that your question comes up now. Read carefully the instructions provided in the link discussing Airport Extreme, it tells you where the file you question is found. Please note that Airport Extreme was a special installation option I chose at the time I bought my G4 - so on my PB it is installed. Keeping that in mind the following can be executed from within the Terminal application found in Utilities within OS X. Here is what a Terminal session looks like revealing a portion of the directory in question; I'm showing a partial listing. Note that ... means something precedes and something follows: arakus:/System/Library/Extensions aguila$ ls ... AppleADT746x.kext AppleAirPort.kext AppleAirPort2.kext AppleAltiVecDVDDriver.bundle ... As far as the fwcutter application is concerned I stayed with the version listed in the example, the update or current version didn't work within YDL. So I stayed with what works. All the best... Barry Hembree wrote: > Derick, > > Thanks for your response. I went ahead and installed Mac OS X back on > my computer and upgraded it to the latest version. I don't seem to > have an AppleAirport2 file. I only have a AppleAirport file. I think > the AppleAirport2 file is pre-Leopard. The fwcutter program (I have > tried two different versions) does not seem to want to extract the > file I have. Any suggestions? > > Barry > > On Aug 6, 2008, at 9:00 PM, Derick Centeno wrote: > > >> Hi Barry! >> >> I've got the same type of computer you do. According to the >> references I found >> on-line regarding wl-4.80.53.0, for whatever reason, it is buggy and >> doesn't >> work. The only way around this is to have OS X running such that >> fwcutter can >> extract the firmware from it. >> >> I understand your feelings regarding OS X, I commiserate. However, >> a running >> version which is used such that a viable version of the firmware >> becomes >> extracted from it is the best way to insure the quality of firmware >> you acquire >> and import into YDL. I don't envy the work ahead; I can only state >> that once >> you pass that stage you may find that the effort was worth it. >> >> The instructions on this page still work: >> http://www.terrasoftsolutions.com/support/solutions/ydl_5.x/airport-extreme.shtml >> >> Problems I found: >> >> [root at arakus b43-fwcutter-009]# ./b43-fwcutter -w /lib/firmware/ >> \/mnt/macosx/Sys*/Libr*/Ex*/Ap*/Con*/Ma*/AppleAirPort2 Sorry, the >> input file is >> either wrong or not supported by b43-fwcutter. This file has an >> unknown MD5sum >> 85c71d658b650fd2ef546d1d81b113a0. >> [root at arakus b43-fwcutter-009]# >> >> >> [root at arakus bcm43XX-fwcutter-006]# ./bcm43XX-fwcutter -w /lib/ >> firmware/ >> \/mnt/macosx/System/Library/Extensions/AppleAirPort2.kext/Contents/ >> MacOS/AppleAirPort2 >> Sorry, the input file is either wrong or not supported by bcm43XX- >> fwcutter. >> This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. >> >> The above was resolved by NOT copying over the ifcfg-eth1 file with >> the >> ifcfg-eth0 file. Also the HWADDR variable in ifcfg-eth1 != the >> HWADDR variable >> in ifcfg-eth0. Anaconda creates both files with different >> definitions for the >> hardware location accessed for Ethernet (eth0) and Wireless (eth1). >> >> What follows is the ifcfg-eth1 file settings located in /etc/sys*/ >> net*scripts: >> >> # Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller >> DEVICE=eth1 >> ONBOOT=no >> BOOTPROTO=dhcp >> HWADDR=00:11:24:90:c3:d8 >> NETMASK= >> DHCP_HOSTNAME=arakus >> IPADDR= >> DOMAIN= >> TYPE=Wireless >> ESSID=off/any >> CHANNEL=1 >> MODE=Managed >> RATE=Auto >> USERCTL=yes >> IPV6INIT=yes >> PEERDNS=yes >> >> After reboot, it is then possible to do the standard manual >> invocation of eth1 >> via the terminal. >> >> The sequence anywhere else entails looking/scanning for signals and >> using the >> essid which are available and/or to those essid's key i've been >> given to use >> (in the event of an encrpted network: >> >> 1. #ifconfig eth1 up >> 2. #iwconfig eth1 >> 3. #iwlist eth1 scanning >> 4. #iwconfig eth1 channel 6 txpower on rate auto essid ???????????? >> 5. #dhclient eth1 >> >> Explanation: ? represent #'s and letters identifying a router or >> password. >> In the event a router's signal has a name line 4 should be: >> >> #iwconfig eth1 channel 6 txpower on rate auto essid 'xxxxxxxxx' >> key ????????????????? >> >> where x are the char forming the name and the key is the password >> sequence to >> that protected router. >> >> Of course if you decide to use wpa-supplicant -- a good idea as it >> is better >> security, then the sequence of initiating connection between airport >> extreme >> and the router will be different. >> >> All the best... >> >> >> On Wed, 6 Aug 2008 09:26:53 -0500 >> Barry Hembree wrote: >> >> >>> Hi All, >>> >>> I recently installed ydl 6.0 on my g4 powerbook. I am having a hard >>> time getting the wireless interface to work. I followed the >>> instructions in the various threads but still no luck. Here are the >>> step I took: >>> >>> 1) bownloaded and compiled the fwcutter program (I have the wired >>> ethernet connection working) >>> 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I don't >>> have Mac OS X on my computer anymore) >>> 3) Tried various combination of editing configuration files by hand >>> and using the network-config app. >>> >>> I do get an error message when I try to activate the device as >>> follows: >>> >>> Error wireless request "Set Mode (8B06)" >>> >>> any help at this point would be gratly appreciated. I have spent far >>> too many hours on this. >>> >>> Thanks >>> Barry >>> >> ===== >> "If I were not a physicist, I would probably be a musician. I often >> think in music. I live my daydreams in music. I see my life in terms >> of >> music. ... I get most joy in life out of music." >> >> "What Life Means to Einstein: An Interview by George Sylvester >> Viereck," for the October 26, 1929 issue of The Saturday Evening Post. >> _______________________________________________ >> yellowdog-newbie mailing list >> yellowdog-newbie at lists.terrasoftsolutions.com >> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie >> > > _______________________________________________ > yellowdog-newbie mailing list > yellowdog-newbie at lists.terrasoftsolutions.com > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie > > From gbhembree at comcast.net Fri Aug 8 07:47:45 2008 From: gbhembree at comcast.net (Barry Hembree) Date: Fri, 8 Aug 2008 08:47:45 -0500 Subject: G4 Powerbook Wireless - correction In-Reply-To: <489B91A2.9090502@ydl.net> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> <701960D8-DCAC-4321-BBBE-1553B57D9C18@comcast.net> <489B91A2.9090502@ydl.net> Message-ID: Derick, Still no good. Here is what I did: 1) I found an old install disk for Airport Extreme. I used Pacifist (a cool utility) to extract the package contents from the cd. 2) I used version 006 of the fwcutter program to extract the drivers from AppleAirport2 into /lib/firmware 3) Made the following ifcfg-eth1 file DEVICE=eth1 ONBOOT=no HWADDR=00:0d:93:7f:4c:c3 NETMASK= DHCP_HOSTNAME= IPADDR= DOMAIN= TYPE=Wireless ESSID='B&MLocal' CHANNEL=6 MODE=Managed RATE=Auto USERCTL=yes IPV6INIT=yes PEERDNS=yes BOOTPROTO=dhcp 4)rebooted 5)/sbin/ifconfig eth1 SIOCSIFFLAGS: No such file or directory 6)dmesg (relevant part) b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed. b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). 7)/sbin/iwconfig eth1 Warning: Driver for device eth1 has been compiled with version 22 of Wireless Extension, while this program supports up to version 20. Some things may be broken... eth1 IEEE 802.11g ESSID:"" Mode:Managed Channel:0 Access Point: Not-Associated Tx-Power=0 dBm Retry min limit:7 RTS thr:off Fragment thr=2346 B Encryption key:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Any ideas? There appears to be some problem with the drivers. Thanks again for all of your help. Barry On Aug 7, 2008, at 7:21 PM, Derick Centeno wrote: > Hi Barry: > > I found that you don't need the latest version of OS X; actually Tiger > (10.4.6) is quite good enough. As Apple chose to drop the PPC, I'll > be > eventually switching to Windows so that I could do decent work and > dual > boot between Windows and YDL running on a 4 core Cell. So it's just > as > well that your question comes up now. > > Read carefully the instructions provided in the link discussing > Airport > Extreme, it tells you where the file you question is found. Please > note > that Airport Extreme was a special installation option I chose at the > time I bought my G4 - so on my PB it is installed. > Keeping that in mind the following can be executed from within the > Terminal application found in Utilities within OS X. > > Here is what a Terminal session looks like revealing a portion of the > directory in question; I'm showing a partial listing. Note that ... > means something precedes and something follows: > > arakus:/System/Library/Extensions aguila$ ls > > ... > AppleADT746x.kext > AppleAirPort.kext > AppleAirPort2.kext > AppleAltiVecDVDDriver.bundle > ... > > As far as the fwcutter application is concerned I stayed with the > version listed in the example, the update or current version didn't > work > within YDL. So I stayed with what works. > > All the best... > > Barry Hembree wrote: >> Derick, >> >> Thanks for your response. I went ahead and installed Mac OS X back on >> my computer and upgraded it to the latest version. I don't seem to >> have an AppleAirport2 file. I only have a AppleAirport file. I think >> the AppleAirport2 file is pre-Leopard. The fwcutter program (I have >> tried two different versions) does not seem to want to extract the >> file I have. Any suggestions? >> >> Barry >> >> On Aug 6, 2008, at 9:00 PM, Derick Centeno wrote: >> >> >>> Hi Barry! >>> >>> I've got the same type of computer you do. According to the >>> references I found >>> on-line regarding wl-4.80.53.0, for whatever reason, it is buggy and >>> doesn't >>> work. The only way around this is to have OS X running such that >>> fwcutter can >>> extract the firmware from it. >>> >>> I understand your feelings regarding OS X, I commiserate. However, >>> a running >>> version which is used such that a viable version of the firmware >>> becomes >>> extracted from it is the best way to insure the quality of firmware >>> you acquire >>> and import into YDL. I don't envy the work ahead; I can only state >>> that once >>> you pass that stage you may find that the effort was worth it. >>> >>> The instructions on this page still work: >>> http://www.terrasoftsolutions.com/support/solutions/ydl_5.x/airport-extreme.shtml >>> >>> Problems I found: >>> >>> [root at arakus b43-fwcutter-009]# ./b43-fwcutter -w /lib/firmware/ >>> \/mnt/macosx/Sys*/Libr*/Ex*/Ap*/Con*/Ma*/AppleAirPort2 Sorry, the >>> input file is >>> either wrong or not supported by b43-fwcutter. This file has an >>> unknown MD5sum >>> 85c71d658b650fd2ef546d1d81b113a0. >>> [root at arakus b43-fwcutter-009]# >>> >>> >>> [root at arakus bcm43XX-fwcutter-006]# ./bcm43XX-fwcutter -w /lib/ >>> firmware/ >>> \/mnt/macosx/System/Library/Extensions/AppleAirPort2.kext/Contents/ >>> MacOS/AppleAirPort2 >>> Sorry, the input file is either wrong or not supported by bcm43XX- >>> fwcutter. >>> This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. >>> >>> The above was resolved by NOT copying over the ifcfg-eth1 file with >>> the >>> ifcfg-eth0 file. Also the HWADDR variable in ifcfg-eth1 != the >>> HWADDR variable >>> in ifcfg-eth0. Anaconda creates both files with different >>> definitions for the >>> hardware location accessed for Ethernet (eth0) and Wireless (eth1). >>> >>> What follows is the ifcfg-eth1 file settings located in /etc/sys*/ >>> net*scripts: >>> >>> # Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller >>> DEVICE=eth1 >>> ONBOOT=no >>> BOOTPROTO=dhcp >>> HWADDR=00:11:24:90:c3:d8 >>> NETMASK= >>> DHCP_HOSTNAME=arakus >>> IPADDR= >>> DOMAIN= >>> TYPE=Wireless >>> ESSID=off/any >>> CHANNEL=1 >>> MODE=Managed >>> RATE=Auto >>> USERCTL=yes >>> IPV6INIT=yes >>> PEERDNS=yes >>> >>> After reboot, it is then possible to do the standard manual >>> invocation of eth1 >>> via the terminal. >>> >>> The sequence anywhere else entails looking/scanning for signals and >>> using the >>> essid which are available and/or to those essid's key i've been >>> given to use >>> (in the event of an encrpted network: >>> >>> 1. #ifconfig eth1 up >>> 2. #iwconfig eth1 >>> 3. #iwlist eth1 scanning >>> 4. #iwconfig eth1 channel 6 txpower on rate auto essid ???????????? >>> 5. #dhclient eth1 >>> >>> Explanation: ? represent #'s and letters identifying a router or >>> password. >>> In the event a router's signal has a name line 4 should be: >>> >>> #iwconfig eth1 channel 6 txpower on rate auto essid 'xxxxxxxxx' >>> key ????????????????? >>> >>> where x are the char forming the name and the key is the password >>> sequence to >>> that protected router. >>> >>> Of course if you decide to use wpa-supplicant -- a good idea as it >>> is better >>> security, then the sequence of initiating connection between airport >>> extreme >>> and the router will be different. >>> >>> All the best... >>> >>> >>> On Wed, 6 Aug 2008 09:26:53 -0500 >>> Barry Hembree wrote: >>> >>> >>>> Hi All, >>>> >>>> I recently installed ydl 6.0 on my g4 powerbook. I am having a hard >>>> time getting the wireless interface to work. I followed the >>>> instructions in the various threads but still no luck. Here are the >>>> step I took: >>>> >>>> 1) bownloaded and compiled the fwcutter program (I have the wired >>>> ethernet connection working) >>>> 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I >>>> don't >>>> have Mac OS X on my computer anymore) >>>> 3) Tried various combination of editing configuration files by hand >>>> and using the network-config app. >>>> >>>> I do get an error message when I try to activate the device as >>>> follows: >>>> >>>> Error wireless request "Set Mode (8B06)" >>>> >>>> any help at this point would be gratly appreciated. I have spent >>>> far >>>> too many hours on this. >>>> >>>> Thanks >>>> Barry >>>> >>> ===== >>> "If I were not a physicist, I would probably be a musician. I often >>> think in music. I live my daydreams in music. I see my life in terms >>> of >>> music. ... I get most joy in life out of music." >>> >>> "What Life Means to Einstein: An Interview by George Sylvester >>> Viereck," for the October 26, 1929 issue of The Saturday Evening >>> Post. >>> _______________________________________________ >>> yellowdog-newbie mailing list >>> yellowdog-newbie at lists.terrasoftsolutions.com >>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog- >>> newbie >>> >> >> _______________________________________________ >> yellowdog-newbie mailing list >> yellowdog-newbie at lists.terrasoftsolutions.com >> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie >> >> > > _______________________________________________ > yellowdog-newbie mailing list > yellowdog-newbie at lists.terrasoftsolutions.com > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie From gbhembree at comcast.net Fri Aug 8 13:53:37 2008 From: gbhembree at comcast.net (Barry Hembree) Date: Fri, 8 Aug 2008 14:53:37 -0500 Subject: G4 Powerbook Wireless I finally gotit!!! In-Reply-To: <20080806220003.6eb208c9@arakus> References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> Message-ID: Derick, Disregard the last message. I have finally got wireless working. Somehow module ssb was getting loaded. I blacklisted it and now everything works. Thanks again for your help you really got me over my first yellowdog hurdle. I'm sure there are more to come. Barry On Aug 6, 2008, at 9:00 PM, Derick Centeno wrote: > Hi Barry! > > I've got the same type of computer you do. According to the > references I found > on-line regarding wl-4.80.53.0, for whatever reason, it is buggy and > doesn't > work. The only way around this is to have OS X running such that > fwcutter can > extract the firmware from it. > > I understand your feelings regarding OS X, I commiserate. However, > a running > version which is used such that a viable version of the firmware > becomes > extracted from it is the best way to insure the quality of firmware > you acquire > and import into YDL. I don't envy the work ahead; I can only state > that once > you pass that stage you may find that the effort was worth it. > > The instructions on this page still work: > http://www.terrasoftsolutions.com/support/solutions/ydl_5.x/airport-extreme.shtml > > Problems I found: > > [root at arakus b43-fwcutter-009]# ./b43-fwcutter -w /lib/firmware/ > \/mnt/macosx/Sys*/Libr*/Ex*/Ap*/Con*/Ma*/AppleAirPort2 Sorry, the > input file is > either wrong or not supported by b43-fwcutter. This file has an > unknown MD5sum > 85c71d658b650fd2ef546d1d81b113a0. > [root at arakus b43-fwcutter-009]# > > > [root at arakus bcm43XX-fwcutter-006]# ./bcm43XX-fwcutter -w /lib/ > firmware/ > \/mnt/macosx/System/Library/Extensions/AppleAirPort2.kext/Contents/ > MacOS/AppleAirPort2 > Sorry, the input file is either wrong or not supported by bcm43XX- > fwcutter. > This file has an unknown MD5sum 85c71d658b650fd2ef546d1d81b113a0. > > The above was resolved by NOT copying over the ifcfg-eth1 file with > the > ifcfg-eth0 file. Also the HWADDR variable in ifcfg-eth1 != the > HWADDR variable > in ifcfg-eth0. Anaconda creates both files with different > definitions for the > hardware location accessed for Ethernet (eth0) and Wireless (eth1). > > What follows is the ifcfg-eth1 file settings located in /etc/sys*/ > net*scripts: > > # Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller > DEVICE=eth1 > ONBOOT=no > BOOTPROTO=dhcp > HWADDR=00:11:24:90:c3:d8 > NETMASK= > DHCP_HOSTNAME=arakus > IPADDR= > DOMAIN= > TYPE=Wireless > ESSID=off/any > CHANNEL=1 > MODE=Managed > RATE=Auto > USERCTL=yes > IPV6INIT=yes > PEERDNS=yes > > After reboot, it is then possible to do the standard manual > invocation of eth1 > via the terminal. > > The sequence anywhere else entails looking/scanning for signals and > using the > essid which are available and/or to those essid's key i've been > given to use > (in the event of an encrpted network: > > 1. #ifconfig eth1 up > 2. #iwconfig eth1 > 3. #iwlist eth1 scanning > 4. #iwconfig eth1 channel 6 txpower on rate auto essid ???????????? > 5. #dhclient eth1 > > Explanation: ? represent #'s and letters identifying a router or > password. > In the event a router's signal has a name line 4 should be: > > #iwconfig eth1 channel 6 txpower on rate auto essid 'xxxxxxxxx' > key ????????????????? > > where x are the char forming the name and the key is the password > sequence to > that protected router. > > Of course if you decide to use wpa-supplicant -- a good idea as it > is better > security, then the sequence of initiating connection between airport > extreme > and the router will be different. > > All the best... > > > On Wed, 6 Aug 2008 09:26:53 -0500 > Barry Hembree wrote: > >> Hi All, >> >> I recently installed ydl 6.0 on my g4 powerbook. I am having a hard >> time getting the wireless interface to work. I followed the >> instructions in the various threads but still no luck. Here are the >> step I took: >> >> 1) bownloaded and compiled the fwcutter program (I have the wired >> ethernet connection working) >> 2) downloaded wl-4.80.53.0 and extracted into /lib/firmware (I don't >> have Mac OS X on my computer anymore) >> 3) Tried various combination of editing configuration files by hand >> and using the network-config app. >> >> I do get an error message when I try to activate the device as >> follows: >> >> Error wireless request "Set Mode (8B06)" >> >> any help at this point would be gratly appreciated. I have spent far >> too many hours on this. >> >> Thanks >> Barry > > > ===== > "If I were not a physicist, I would probably be a musician. I often > think in music. I live my daydreams in music. I see my life in terms > of > music. ... I get most joy in life out of music." > > "What Life Means to Einstein: An Interview by George Sylvester > Viereck," for the October 26, 1929 issue of The Saturday Evening Post. > _______________________________________________ > yellowdog-newbie mailing list > yellowdog-newbie at lists.terrasoftsolutions.com > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie From dcenteno at ydl.net Fri Aug 8 15:09:58 2008 From: dcenteno at ydl.net (Derick Centeno) Date: Fri, 08 Aug 2008 17:09:58 -0400 Subject: G4 Powerbook Wireless I finally gotit!!! In-Reply-To: References: <3A3DE734-C648-4327-B20E-3CE3CE0FD1B8@comcast.net> <20080806220003.6eb208c9@arakus> Message-ID: <20080808170958.46005345@arakus> Glad I could help. It would be a good idea to list or explain how you blacklisted the ssb module as part of this thread. It could be useful as a future reference for someone else. Congratulations on completing this problem successfully. Wishing you all the best... Derick. On Fri, 8 Aug 2008 14:53:37 -0500 Barry Hembree wrote: > Derick, > > Disregard the last message. I have finally got wireless working. > Somehow module ssb was getting loaded. I blacklisted it and now > everything works. Thanks again for your help you really got me over my > first yellowdog hurdle. I'm sure there are more to come. > > Barry ===== "If I were not a physicist, I would probably be a musician. I often think in music. I live my daydreams in music. I see my life in terms of music. ... I get most joy in life out of music." "What Life Means to Einstein: An Interview by George Sylvester Viereck," for the October 26, 1929 issue of The Saturday Evening Post. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.terrasoftsolutions.com/pipermail/yellowdog-newbie/attachments/20080808/b338eeee/attachment.bin