Differences between revisions 14 and 15
Revision 14 as of 2009-01-25 15:46:34
Size: 5125
Editor: FranklinPiat
Comment: dropping pcmcia-compat.sh
Revision 15 as of 2009-03-16 03:32:06
Size: 5129
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
[[TableOfContents(2)]] <<TableOfContents(2)>>
Line 16: Line 16:
-- ["John Talbut"] [[DateTime(2007-12-16T09:32:17Z)]] -- [[John_Talbut]] <<DateTime(2007-12-16T09:32:17Z)>>
Line 22: Line 22:
Yes, it's the natural way of a portal. When it's grow up and become too big, We can create sub portal. At this moment, I think SystemAdministration and ["Network"] are more urgent to fragment. WiFi portal is not enough too big at this moment; Yes, it's the natural way of a portal. When it's grow up and become too big, We can create sub portal. At this moment, I think SystemAdministration and [[Network]] are more urgent to fragment. WiFi portal is not enough too big at this moment;
Line 26: Line 26:
-- SalokineTerata [[DateTime(2007-12-16T14:22:12Z)]] -- SalokineTerata <<DateTime(2007-12-16T14:22:12Z)>>
Line 30: Line 30:
Should I move details from our ["DebianEeePC"] project here (mostly about Atheros 242x which is in Eee models 701, 900 and 900A) or just link to our own wiki? What about ath5k? I understand the version in 2.6.26 works on some systems already (though we will need to wait for a later release for support on these Eee PC models). Should I move details from our [[DebianEeePC]] project here (mostly about Atheros 242x which is in Eee models 701, 900 and 900A) or just link to our own wiki? What about ath5k? I understand the version in 2.6.26 works on some systems already (though we will need to wait for a later release for support on these Eee PC models).
Line 32: Line 32:
We have rt2860-source from Ralink for ["DebianEeePC/Model/901"] hosted at eeepc.debian.net. Some non-Eee owners with this hardware may benefit. We are also looking now at rtl8187se for ["DebianEeePC/Model/701SD"]. Neither of these are yet suitable for inclusion in Debian. In the first case although the driver is open source, it embeds non-free firmware. We're hoping the rt2x00 project wil support this, but work on it is very early. In the second, none of the developers have this system yet and we haven't made packages yet. I don't know if it includes non-free firmware or not. It appears the same hardware is included in the MSI Wind netbook. We have rt2860-source from Ralink for [[DebianEeePC/Model/901]] hosted at eeepc.debian.net. Some non-Eee owners with this hardware may benefit. We are also looking now at rtl8187se for [[DebianEeePC/Model/701SD]]. Neither of these are yet suitable for inclusion in Debian. In the first case although the driver is open source, it embeds non-free firmware. We're hoping the rt2x00 project wil support this, but work on it is very early. In the second, none of the developers have this system yet and we haven't made packages yet. I don't know if it includes non-free firmware or not. It appears the same hardware is included in the MSI Wind netbook.
Line 34: Line 34:
-- BenArmstrong [[DateTime(2008-10-11T16:33:11Z)]] -- BenArmstrong <<DateTime(2008-10-11T16:33:11Z)>>
Line 39: Line 39:
-- FranklinPiat [[DateTime(2008-10-12T07:39:26Z)]] -- FranklinPiat <<DateTime(2008-10-12T07:39:26Z)>>
Line 41: Line 41:
I've created ["rtl-wifi"], which includes driver installation procedures relating to the Realtek RTL8187SE chipset. I've created [[rtl-wifi]], which includes driver installation procedures relating to the Realtek RTL8187SE chipset.
Line 43: Line 43:
A page about ath5k relating to supported chipsets (brief list), missing features (with respect to [:WiFi/ath_pci:madwifi]) and other known issues could potentially be useful to existing ath_pci users. Possibly even a "Switching from madwifi to ath5k" section as done in ["iwlwifi"]. A page about ath5k relating to supported chipsets (brief list), missing features (with respect to [[WiFi/ath_pci|madwifi]]) and other known issues could potentially be useful to existing ath_pci users. Possibly even a "Switching from madwifi to ath5k" section as done in [[iwlwifi]].
Line 45: Line 45:
-- GeoffSimmons [[DateTime(2009-01-04T15:01:54Z)]] -- GeoffSimmons <<DateTime(2009-01-04T15:01:54Z)>>
Line 47: Line 47:
I consider that 1 page/module is the best compromize, to keep pages short. If multiple pages apply for a given [wifi] device, I hesitate to put the explanation on the ["WiFi"] page, or as a header on each of the alternatives pages. -- FranklinPiat [[DateTime(2009-01-04T16:27:44Z)]] I consider that 1 page/module is the best compromize, to keep pages short. If multiple pages apply for a given [wifi] device, I hesitate to put the explanation on the [[WiFi]] page, or as a header on each of the alternatives pages. -- FranklinPiat <<DateTime(2009-01-04T16:27:44Z)>>
Line 49: Line 49:
As per BenArmstrong's suggestion, I have created ["rt2860sta"] and transferred the content of ["DebianEeePC/HowTo/Wifi/Rt2860"] within. Apart from the leading sentence, this content was not specific to the Eee. Comments welcome. -- GeoffSimmons [[DateTime(2009-01-13T13:27:37Z)]] As per BenArmstrong's suggestion, I have created [[rt2860sta]] and transferred the content of [[DebianEeePC/HowTo/Wifi/Rt2860]] within. Apart from the leading sentence, this content was not specific to the Eee. Comments welcome. -- GeoffSimmons <<DateTime(2009-01-13T13:27:37Z)>>
Line 53: Line 53:
I have added more content to ["WiFi/HowToUse"]. Made the assumption that users would want to connect to a WPA-protected network (managed mode), providing common configuration examples (N-M, wpa_supplicant) accordingly. Not covered is monitor and master mode operation, which is either driver-specific (eg. Ralink devices require rt2x00 GIT for BSS master) or unsupported. I have added more content to [[WiFi/HowToUse]]. Made the assumption that users would want to connect to a WPA-protected network (managed mode), providing common configuration examples (N-M, wpa_supplicant) accordingly. Not covered is monitor and master mode operation, which is either driver-specific (eg. Ralink devices require rt2x00 GIT for BSS master) or unsupported.
Line 55: Line 55:
I am loathe to migrate the Ad-Hoc setup content from ["WiFi"] to here, due to its insecure nature. "iwconfig ath0 mode Ad-hoc" will not work for current [:WiFi/ath_pci:MadWifi] drivers anyway. I suggest this either be deleted or moved elsewhere. -- GeoffSimmons [[DateTime(2009-01-21T17:58:32Z)]] I am loathe to migrate the Ad-Hoc setup content from [[WiFi]] to here, due to its insecure nature. "iwconfig ath0 mode Ad-hoc" will not work for current [[WiFi/ath_pci|MadWifi]] drivers anyway. I suggest this either be deleted or moved elsewhere. -- GeoffSimmons <<DateTime(2009-01-21T17:58:32Z)>>
Line 59: Line 59:
  Moved to ["WiFi/AdHoc"] and expanded. -- GeoffSimmons [[DateTime(2009-01-22T08:38:43Z)]]   Moved to [[WiFi/AdHoc]] and expanded. -- GeoffSimmons <<DateTime(2009-01-22T08:38:43Z)>>
Line 63: Line 63:
["WiFi/HowToUse"]: The [http://greenfly.org/fujitsu/#Tips%20and%20Tricks recently added "pcmcia-compat.sh" tip] (moved from ["WiFi"]) is PCMCIA-specific, in contrast to DebPkg:ifscheme and others. The tip also references {{{cardctl}}}, which is no longer in DebPkg:pcmcia-cs (succeeded by {{{pccardctl}}} in DebPkg:pcmciautils, no compatibility symlink is made, {{{pccardctl}}} doesn't have a "scheme" command). This is an obsolete wireless interface configuration example. -- GeoffSimmons [[DateTime(2009-01-25T15:14:47Z)]]
 I have droped that paragraph, Thanks. -- FranklinPiat [[DateTime(2009-01-25T15:46:34Z)]]
[[WiFi/HowToUse]]: The [[http://greenfly.org/fujitsu/#Tips%20and%20Tricks|recently added "pcmcia-compat.sh" tip]] (moved from [[WiFi]]) is PCMCIA-specific, in contrast to DebPkg:ifscheme and others. The tip also references {{{cardctl}}}, which is no longer in DebPkg:pcmcia-cs (succeeded by {{{pccardctl}}} in DebPkg:pcmciautils, no compatibility symlink is made, {{{pccardctl}}} doesn't have a "scheme" command). This is an obsolete wireless interface configuration example. -- GeoffSimmons <<DateTime(2009-01-25T15:14:47Z)>>
 I have droped that paragraph, Thanks. -- FranklinPiat <<DateTime(2009-01-25T15:46:34Z)>>

Place new comments at the bottom

Add new comments, don't edit old ones

Sign your comments using @SIG@

Page structure

I suggest that there could be a separate section for hardware and the Install Driver section being kept for software. At the moment all the information on this page seems to refer to cards using the ?MadWiFi software (including the need for module-assistant). So I would suggest under Install Driver there would be two sections (at present), one for ?MadWiFi and one for BCM43xx. Similarly the hardware section could be divided into devices using the Atheros chipset and devices using the Broadcom chipsets.

I think it would be a good idea if the BCM43xx information was included here rather than being on a separate page.

-- John_Talbut 2007-12-16 09:32:17


Hi,

Yes, it's the natural way of a portal. When it's grow up and become too big, We can create sub portal. At this moment, I think SystemAdministration and Network are more urgent to fragment. WiFi portal is not enough too big at this moment;

Bye

-- SalokineTerata 2007-12-16 14:22:12


Should I move details from our DebianEeePC project here (mostly about Atheros 242x which is in Eee models 701, 900 and 900A) or just link to our own wiki? What about ath5k? I understand the version in 2.6.26 works on some systems already (though we will need to wait for a later release for support on these Eee PC models).

We have rt2860-source from Ralink for DebianEeePC/Model/901 hosted at eeepc.debian.net. Some non-Eee owners with this hardware may benefit. We are also looking now at rtl8187se for DebianEeePC/Model/701SD. Neither of these are yet suitable for inclusion in Debian. In the first case although the driver is open source, it embeds non-free firmware. We're hoping the rt2x00 project wil support this, but work on it is very early. In the second, none of the developers have this system yet and we haven't made packages yet. I don't know if it includes non-free firmware or not. It appears the same hardware is included in the MSI Wind netbook.

-- BenArmstrong 2008-10-11 16:33:11

Moving details about Atheros 242x here looks like a good idea.

-- FranklinPiat 2008-10-12 07:39:26

I've created ?rtl-wifi, which includes driver installation procedures relating to the Realtek RTL8187SE chipset.

A page about ath5k relating to supported chipsets (brief list), missing features (with respect to madwifi) and other known issues could potentially be useful to existing ath_pci users. Possibly even a "Switching from madwifi to ath5k" section as done in iwlwifi.

-- GeoffSimmons 2009-01-04 15:01:54

I consider that 1 page/module is the best compromize, to keep pages short. If multiple pages apply for a given [wifi] device, I hesitate to put the explanation on the WiFi page, or as a header on each of the alternatives pages. -- FranklinPiat 2009-01-04 16:27:44

As per BenArmstrong's suggestion, I have created rt2860sta and transferred the content of DebianEeePC/HowTo/Wifi/Rt2860 within. Apart from the leading sentence, this content was not specific to the Eee. Comments welcome. -- GeoffSimmons 2009-01-13 13:27:37


I have added more content to WiFi/HowToUse. Made the assumption that users would want to connect to a WPA-protected network (managed mode), providing common configuration examples (N-M, wpa_supplicant) accordingly. Not covered is monitor and master mode operation, which is either driver-specific (eg. Ralink devices require rt2x00 GIT for BSS master) or unsupported.

I am loathe to migrate the Ad-Hoc setup content from WiFi to here, due to its insecure nature. "iwconfig ath0 mode Ad-hoc" will not work for current MadWifi drivers anyway. I suggest this either be deleted or moved elsewhere. -- GeoffSimmons 2009-01-21 17:58:32

  • Regarding the second point, I am not quite sure what should be done... since Ad-Hoc can be useful in some situation, it could be moved to another page. BTW, I wonder how much insecure it is, compared to "open" hotspots.


WiFi/HowToUse: The recently added "pcmcia-compat.sh" tip (moved from WiFi) is PCMCIA-specific, in contrast to ifscheme and others. The tip also references cardctl, which is no longer in pcmcia-cs (succeeded by pccardctl in pcmciautils, no compatibility symlink is made, pccardctl doesn't have a "scheme" command). This is an obsolete wireless interface configuration example. -- GeoffSimmons 2009-01-25 15:14:47

  • I have droped that paragraph, Thanks. -- FranklinPiat 2009-01-25 15:46:34