where is Windows host name file?

Windows host name file at below folder:
Windows 95/98/Me c:\windows\hosts
Windows NT/2000/XP Pro c:\winnt\system32\drivers\etc\hosts
Windows XP Home c:\windows\system32\drivers\etc\hosts
阅读全文！

.小陈不吃饭!

.小陈不吃饭,个人觉得有以下作用:
1. 博得同情;
2. 想说自己无辜;
3. 表现一种自己的风格；
但是，所有这些都不可能起到他期望的作用，淡化自己的错事！

阅读全文！

Nokia E71 手機使用貼士

Nokia E71 手機支援
Nokia E71

手機使用貼士
以下是Nokia E71 一些常用功能的使用介紹。
按照以下步驟操作，即可啟動相應功能：

新功能/新增設定
如何快捷啓動或關閉藍牙
長按"*"鍵作藍牙開/關

如何更改電郵鍵預設的郵箱
功能表> 工具> 設定> 一般> 電郵鍵設定> 選擇您想預設的電郵信箱。

如何設定加密手機記憶體
功能表-工具-加密-手機記憶體

如何設定加密記憶卡
功能表-工具-加密-記憶卡-加密但不儲存金鑰/加密并儲存金鑰/加密并還原金鑰

如何開/關導航鍵的燈光效果
功能表-工具-操作模式-選擇操作模式-選項-個人化選擇-閃爍燈光-開/關

如何設定燈光效果的顯示時間
功能表-工具-設定-一般-個人化-提示燈-閃光時間-5分鐘/15分鐘/30分鐘/1小時/2小時/無限制

如何設定燈光效果的提示項目
功能表-工具-設定-一般-個人化-提示燈-提示項目-未接來電/新短訊/新多媒體訊息/新電郵

如何切換待機模式
功能表-工具-模式-切換模式
功能表-工具-設定-一般-個人化-主螢幕-模式設定-切換模式

訊息設定
如何設定訊息中心號碼
功能表-通訊-訊息-選項-設定-短訊-訊息中心-SIM卡訊息中心-訊息中心號碼

如何設定訊息報告
功能表-通訊-訊息-選項-設定-短訊-接收狀況報告-是/否

如何查看SIM卡訊息
功能表-通訊-訊息-選項-SIM卡訊息

如何設定存儲已發訊息
功能表-通訊-訊息-選項-設定-其他-儲存寄件備份-是/否

如何設定留言信箱號碼
功能表-通訊-通話郵箱-輸入留言信箱號碼

如何選擇儲存訊息的記憶體
功能表-通訊-訊息-選項-設定-其他-使用中的記憶體-手機記憶體/記憶卡

如何設定訊息有效期
功能表-通訊-訊息-選項-設定-短訊-訊息有效期-1小時/6小時/24小時/3天/1星期/最長時限

如何設定接收/不接收服務訊息
功能表-通訊-訊息-選項-設定-服務訊息-服務訊息-開/關

如何設定接收/不接收廣播訊息
功能表-通訊-訊息-選項-設定-訊息廣播-接收廣播-開/關

通訊錄及通話
如何新增通訊錄詳細資料
功能表-通訊-通訊錄-打開一個聯絡人-選項-修改-選項-加入詳細資料

如何建立分組
功能表-通訊-通訊錄-選項-群組-新增群組

如何複製通訊錄
功能表-通訊-通訊錄-選項-複製-至SIM電話簿/至記憶卡/從記憶卡/製作副本
功能表-工具-記憶卡-選項-備份本機記憶體

如何使用篩選來查看通訊記錄
功能表-通訊記錄-按右導航鍵-選項-篩選-所有通訊/發出的通訊/外來的通訊/語音及視像通話/訊息/分組數據連接/數據通話/WLAN連接/選定的號碼

如何查詢之前通話的時間
功能表-通訊記錄-按右導航鍵-選擇需要查詢的通話-選項-檢視詳細資料

如何為通訊錄新增個人鈴聲/圖像
個人鈴聲設定方法：功能表-通訊-通訊錄-選擇需要修改的聯絡人-選項-開啟-選項-鈴聲
聯絡人縮圖設定方法：功能表-通訊-通訊錄-選擇需要修改的聯絡人-選項-修改-選項-加入縮圖

如何查看SIM卡電話簿
功能表-通訊-通訊錄-選項-SIM卡聯絡人-SIM電話簿

如何使用語音指令/聲控撥號
在待機畫面按住語音鍵或右選擇鍵-當聽到聲音或看到顯示時，清晰地說出指令或儲存在手機記憶體上的姓名

如何開/關單鍵撥號
功能表-工具-設定-手機-通話-單鍵撥號-開/關

如何設定來電轉接
功能表-工具-設定-手機-來電轉接-語音通話-所有語音通話/如線路繁忙/如無人接聽/如超出通訊範圍/如無法接通

如何設定顯示/不顯示通話時間
功能表-工具-設定-手機-通話-顯示通話時間-是/否

如何設定通話報告
功能表-工具-設定-手機-通話-通話報告-開/關

如何設定在來電過程中說出來電者姓名
功能表-工具-操作模式-選擇操作模式-選項-個人化選擇-說出來電方姓名-開/關

如何設定來電等待
功能表-工具-設定-手機-通話-來電等候-選項-啟動

如何設定按任意鍵接聽
功能表-工具-設定-手機-通話-任意鍵接聽-開/關

如何設定以短信拒絕來電
功能表-工具-設定-手機-通話-以短信拒絕來電-是/否

如何更改以訊息拒絕來電的訊息內容
功能表-工具-設定-手機-通話-文字訊息-輸入內容

如何啟動3D鈴聲效果
功能表-影音工具-3-D鈴聲-3-D鈴聲效果-開/關

基本設定
如何設定單鍵撥號
功能表-通訊-單鍵撥號-可設定2-9的單鍵撥號

如何設定語音指令
功能表-工具-語音指令-選項-新應用程式

如何更改手機語言
功能表-工具-設定-一般-個人化-語言-手機語言-自動/繁體中文/English/简体中文

如何關閉預想/智慧輸入
功能表-工具-設定-一般-個人化-語言-智慧輸入-開/關

如何更改編寫語言/預設輸入法
功能表-工具-設定-一般-個人化-語言-預設輸入法-拼音/筆劃/英文

如何更改省電螢幕保護內容
功能表-工具-佈景主題-省電螢幕保護-無/正在播放/動畫

如何更改省電螢幕保護逾時/時間
功能表-工具-設定-一般-個人化-顯示-省電螢幕保護逾時(可以選擇5~90秒)

如何設定字體大小
功能表-工具-設定-一般-個人化-顯示-字型大小-大/一般/小

如何啟動/關閉開機鈴聲
功能表-工具-操作模式-選擇操作模式-選項-個人化選擇-警告音-開/關

如何更改左/右選擇鍵/瀏覽鍵的快捷方式
功能表-工具-設定-一般-個人化-主螢幕-鍵盤捷徑-左/右選擇鍵選擇相應的快捷方式

如何更改待機狀態模式/待機佈景主題模式
功能表-工具-設定-一般-個人化-主螢幕-主螢幕-動態/基本

如何設定自動鎖鍵盤
功能表-工具-設定-一般-安全性-手機及SIM卡-鍵盤自動鎖期間-無/用戶自定義(可以選擇5秒~59分59秒)

如何更改保密碼
功能表-工具-設定-一般-安全性-手機及SIM卡-鎖定碼

如何開啟/關閉遠端手機鎖
功能表-工具-設定-一般-安全性-手機及SIM卡-允許遠端鎖定-是/否

如何更改PIN碼
功能表-工具-設定-一般-安全性-手機及SIM卡-PIN碼(要求PIN碼要在開的狀態)

如何開啟/關閉PIN碼
功能表-工具-設定-一般-安全性-手機及SIM卡-要求PIN碼-開/關

其他
如何設定重複鬧鐘
功能表-辦公室-時鐘-按右導航鍵至響鬧-選項-新響鬧-重複-單次/每天/每週/工作日

如何刪除佈景主題
功能表-安裝-程式管理-選擇需要刪除的佈景主題-選項-移除

如何更換功能表檢視
功能表-選項-更換功能表檢視-圖示/清單
功能表-工具-佈景主題-功能表檢視-圖示/清單

如何更改錄音儲存位置
功能表-工具-設定-應用程式-錄音機-使用中的記憶體-手機記憶體/記憶卡
功能表-影音工具-錄音機-選項-設定-使用中的記憶體-手機記憶體/記憶卡

如何查看手機/記憶卡記憶體詳細資料
功能表-選項-記憶體詳細資料-手機記憶體/記憶卡

如何在日曆中顯示農曆
功能表-辦公室-日曆-選項-設定-農曆-開

如何更改星期開始日
功能表-辦公室-日曆-選項-設定-星期開始於-星期一/星期二/星期三/星期四/星期五/星期六/星期日

如何更新/重新整理音樂資料庫
功能表-影音工具-音樂播放-選項-重新整理

如何開/關相機的進階數碼縮放
功能表-影音工具-相機-選項-設定-進階數碼縮放-關/延伸(持續)

如何更改拍攝聲
功能表-影音工具-相機-選項-設定-拍攝聲-相機1/相機2/相機3/相機4

如何開/關閃光燈
功能表-影音工具-相機-於右方功能表內選擇閃光模式-自動/開/紅眼裝置/關
阅读全文！

想换手机号码?

电话和约已经22个月了,新电信说21个就可以重新签和约--当然是因为新的合约可以拿到便宜手机.
另外一个选项时可以和星和签,好处是IDD免费.
看中了E71,还在犹豫和谁签.
阅读全文！

真汉子何须马革裹尸还！

中条山战役的陕西800冷娃

１９３７年７月７日，侵华日军发动了"芦沟桥事变"后，以闪电般的速度攻城略地……１９３８年３月，日军牛岛、川岸师团兵临山西风陵渡。接杨虎城掌管西北军的孙蔚如向国民政府和陕西民众盟誓：余将以血肉之躯报效国家，舍身家性命以拒日寇，誓与日寇血战到底！但闻黄河水长啸，不求马革裹尸还……
　　１９３８年７月，一支由三万多名"陕西冷娃"组成的队伍夜渡黄河，开进了黄河北岸的中条山。中条山，曾被侵华日军称为"盲肠"。在抗战初期，日军倾十余万兵力，苦战三年，竟未能越过中条山一步。这在抗战初期确属罕见。而坚守中条山的，竟是武器装备低劣、受蒋介石排挤的杂牌军西北军。
　　 一群清一色的号称"冷娃"的陕西子弟兵，在中条山坚持抗战近三年，先后粉碎了日军的11次大扫荡，把不可一世妄言三个月占领中国的日本鬼子拒阻于潼关以外，使其进入关中掠占西北的梦想死于胎中。抗战八年，日军占据了东、南、北大片领土，却一直无力西进，这一切都得之于中条山战役的伟大胜利。日本鬼子不仅未能踏进潼关一步，而且付出了惨重代价，仅"6·6"会战一役，日军排长以上军官的骨灰盒层层叠叠垒堆了1700多具。这是八年抗战中取得重大战果的战区之一。在中条山坚持抗战近三年，陕西子弟兵也有２．１万人牺牲在中条山下、黄河岸边。
　　由徐剑铭等三位陕西本土作家创作的长篇纪实作品《立马中条》中，孙蔚如将军率领关中子弟与日本侵略军"6·6" 血战里有一个八百壮士投身黄河的细节：
　　 177师新兵团有一千多名士兵被两倍于己的鬼子包围，经过拼杀后死亡200，余下的800人被逼到黄河岸边的悬崖上，三面都是绝壁。这
800士兵在短暂的一瞬里从悬崖上跳了下去。下面是被称作母亲的黄河。黄河以母亲的慈爱襟怀包裹了这800个殊死搏斗后誓不投降的关中"冷娃"。他们都是
16-18岁的孩子。他们没有一个人活下来。他们800人集体投河的那一幕，被山里的村民看见了。活着的这个村民，尤其清晰地记得最后一名士兵跳河的情景。悬崖上只留下最后一个关中籍中国士兵。这是一位旗手。他的双手紧紧攥着他的部队的军旗。军旗已经被枪弹撕裂被硝烟熏染，他仍然双手高擎着。他在跳河前吼唱了几句秦腔。那位活着的当地村民还记得其中两句戏词，是《金沙滩》杨继业的两句———
　　　　两狼山———战胡儿啊……天摇地动———
　　　　好男儿———为国家———何俱———死———生啊……
　　　　孙蔚如将军率官兵在800壮士跳河的河滩上举行公祭。黑纱缠臂。纸钱飘飘。香蜡被河风吹得明明灭灭。有人突然发现黄河水浪里有一杆军旗，诧异其为何不被河水冲走。士兵下河打捞这杆军旗时，拖出两具尸首来。旗杆从一个人的后背戳进去，穿透前胸，这是一个被称作鬼子的日本兵的尸体。压在鬼子尸体上边还紧紧攥着旗杆的人，是中国士兵，就是那个吼着秦腔最后跳入黄河的旗手。
　　当时，西安的新闻媒体则代表关中百姓发出真诚的感叹："西北整个得以安定，皆赖我第四集团军英勇将士在黄河北岸艰苦支撑所赐……"。
　　第一战区司令长官卫立煌将军亲临平陆慰问第四集团军官兵、热情盛赞陕军为"中条山的铁柱子。"
　　陈忠实曾评论道：
　　"这些关中将士无论性格性情具备什么样儿的地域性特质，在民族生死存亡的血战中体现出来的凛然不可侵侮的大义，正是中华民族辉煌千古存立不灭的主体精神。"
　　在关中一部县志中，满满十余页的抗战烈士名录，他们全部死于中条山战役。那个时候，该县人口不满一万，而在此战役中捐躯者竟有一千多人。
阅读全文！

笑谈:微软黑屏带来的十大“好处”-Linux伊甸园

笑谈:微软黑屏带来的十大"好处"-Linux伊甸园

1、国产软件的装机量迅速提升。比如WPS Ofiice和永中Office的自从微软黑屏计划以来的装机量已经达到几百万、上千万。

2、基础软件受到的支持力度将会前所未有的大。中国工程院院士、互联网实验室首席科学家倪光南指出，"黑屏事件比任何说教都有力，它让我们明白了中国为什么要发展基础软件的原因，因为只有使用自主可控的软件，信息安全才有保障，自己才是电脑的主人。"

3、给全国人民上了一堂生动的信息安全课。黑屏的心理杀伤力对于网民来说绝对是原子弹级别的。微软黑屏计划再次证明了微软对用户客服端拥有绝对的核心控制权，微软可以根据自身需要随时对用户的计算机实施有效的全程跟踪控制。这表明，凡是使用了微软客服端的用户，压根儿就没有稳私权和个人信息的安全可言。

4、给全国人民上了一堂生动的正版课。我们反对微软的做法，但我们也不支持盗版，黑屏事件能为国人上一堂"正版课"，促进养成一种良好的正版意识和习惯。

5、促进计算机教学的改革。目前计算机教育体制下的学生只会使用微软这一家商业公司的软件，对培养linux的开源平台等会起到很大的促进作用。

6、对软件产业和信息安全的专项或课题的地位得到极大提升。

7、促进对于病毒和黑客的重新定义和立法完善。微软黑屏行动不禁让刘兴亮想起1997年轰动一时的江民公司"逻辑锁"事件。当时，江民公司在其最新发行的防病毒软件KV300L++版中加入了"逻辑锁"程序，这一程序的主要作用是识别盗版和正版软件用户。当使用盗版者的密匙盘运行KV300时，该程序立即启动锁死电脑，使电脑硬盘无法使用，但不会造成破坏。后来北京市公安局给予3000元罚款的处罚，江民公司也承认了错误，取消了该程序。这一次微软黑屏事件也很类似，这将进一步促进相关机构对于病毒和黑客的重新定义和立法完善。

8、给各大媒体提供了一个非常好的炒作话题。

9、促进用户保护视力。各种保健书籍、专家、医生都一直再告诉我们，看书、看电脑时最好每小时都起来休息一下，看看远处什么的。以前老忘记，现在好了，因为有了微软黑屏计划。不愧为国际性的大公司，太人性化了。保护视力，请选用微软。

10、黑客新定义：把你的桌面变黑。昨日，一个MM像发现新大陆似的告诉我："我终于明白了什么黑客，原来就是远程控制把你的桌面变黑，是这样的吗？你快告诉我。"我很用力的点了点头，用非常肯定的语气回答："是的"。

阅读全文！

Recompile your kernel for a perfect fit

Recompile your kernel for a perfect fit

After I wrote an article on optimizing disk performance, some readers
commented that tweaking settings was just part of the job. They
pointed out that you can get more speed if you also compile your
kernel, adjusting it optimally for your specific hardware and needs.
Compiling the kernel isn't the challenge it used to be; nowadays the
process is streamlined, and you don't have to do much but pick your
choices and key in some commands.

Most distributions provide a "one-size-fits-all" kernel, compiled with
the most generic options, so everybody can use it. If you have an
Athlon XP CPU instead of an Intel 386 family processor, or lots of
RAM, or a certain graphics card, you can tweak the kernel and compile
it for optimum performance on your specific hardware. In the process,
you can also probably free some memory by getting rid of unneeded
options, shorten boot time, and increase responsiveness.

An almost dry run

Compiling your kernel isn't very hard, but there's a distinct chance
you could hose your machine and transform it into a paperweight (ask
me how I know!), so you will have to take some precautions. Have a
backup kernel available; that way, should you really muck things up,
you can reboot your computer and start again. I use openSUSE, on which
it's easy to install two or more kernels: by using the YAST
administration tool or the Smart package manager, install two
different versions of your kernel. For example, I have both
2.6.18.8-0.3 and 2.6.18.8-0.5, and my boot page shows:

openSUSE 10.2 - 2.6.18.8-0.5
Failsafe -- openSUSE 10.2 - 2.6.18.8-0.5
openSUSE 10.2 - 2.6.18.8-0.3
Failsafe -- openSUSE 10.2 - 2.6.18.8-0.3

By default, my machine is set to boot with the third option; I leave
that version alone (so I can fall back on it if needed) and experiment
with the first one. After building and being satisfied with your new
kernel, you can use the standard tools (such as YAST for openSUSE) to
set it as a default; more adventurous people could resort to editing
GRUB or LILO boot configuration files by hand.

You will also have to install some specific packages: kernel-source
(the source code you compile), gcc (the compiler), bzip2 (needed
internally), and ncurses (for the configuration menus).

If you want to optimize your kernel, you need to know about your
machine's hardware. By using the commands below, you can note what
kind of processor you have, the RAM in your machine, and more details.
I suggest printing this information out and keeping it by your side
while you work.

lspci -v
cat /proc/cpuinfo
cat /proc/meminfo

If you want to be sure you have everything that you can need, you can
rebuild your kernel without touching anything. Working as root, enter
the commands:

cd /usr/src/linux
make clean
make
make modules_install
make install
reboot

The make process will run for a while, and might produce some
warnings, but it shouldn't show any errors. If, after you reboot,
everything is still fine, you are set for your kernel rebuilding
adventure; in fact, you have just done your first such build! (And if
something did go seriously wrong, for example because you were missing
some package, reboot with the backup kernel, fix the problem, and try
a "dry run" again.)

Just say "M"!

Now, let's compile a kernel for true. Once again, su in order to work
as root, and enter:

cd /usr/src/linux
make clean
make menuconfig

You will see a screen showing a menu full of hundreds of options (so
many ways to mess up!) but we will change just a few. Of course, if
you feel adventurous, you can change anything you desire, as long as
you set up an extra kernel just in case. If you want to disable an
option, unmark it and it won't get compiled. To navigate the menus and
see the available options, use the cursor keys; press "H" to see help
at any time.

The Linux kernel is monolithic, which loosely means that it's just one
big piece of software with everything thrown in. However, you can
extend it by using modules, which are loaded on demand and only if
needed. Thus, if you were to compile all possible functions as
modules, the kernel would be as small as possible, and you would only
suffer a small performance hit the first time a module was loaded.
However, you don't want to make everything a module, because some
functions need be available at boot: for instance, you couldn't read
the partition that holds the modules if you didn't already have the
needed code in the kernel. But whenever it's reasonable, set things up
to be modules.

There's another argument in favor of modules. Removing support for
every seemingly unused piece of hardware can cause some strange
problem: for example, I removed the option about LVM AND RAID DEVICES,
and later found out this caused a needed module not to be built, which
then caused lots of other problems. The safest approach is to mark
undesired options with "M" (so they will be compiled as modules) and
not leave out anything unless you are completely sure you won't need
it; cards or disk partition types you do not have, for example, are
usually safe to remove. However, there are no guarantees that removing
any option won't have a secondary, hidden, undocumented effect, which
might end up in some kind of problem. In that case, reboot with the
backup kernel, and just mark the option in question again.

Some options you can study, in order to save some memory:

In Networking, uncheck Amateur Radio Support unless you connect your
PC to amateur radio. The other options are usually marked as "M";
leave them that way.
In File Systems, verify that everything is marked "M." If you are sure
you won't be needing, say, JFS, you could uncheck the corresponding
option, or better yet leave it as a module.
Also in File Systems, see Partition Types and uncheck everything that
doesn't apply to you. In my case, since I have Windows disks in my
machine, I kept the Windows-related partitions.
In Device Drivers, examine each section, and either uncheck or mark as
"M" any device you do not have. SCSI or ISDN are options you are
likely to be able to drop.
In Bus Options, disable EISA and MCA support unless your motherboard
uses these kinds of buses; check the manufacturer specs if you are not
sure.

Full speed ahead!

Depending on whether you use your PC as a server or as a desktop
machine, you can pick several options to enhance responsiveness. I
recommend the following for a desktop machine:

At Code Maturity Level Options, uncheck "Prompt for development and/or
incomplete code/drivers"; you need this option only if you are
developing or testing something in the kernel.
At General Setup, uncheck "Cpuset support" unless you have more than
one processor; dual and quad-core processors count as more than one.
At Block Layer, uncheck everything unless you have disks that are
larger in size than 2TB.
At Processor Type and Features, uncheck "Symmetric multi-processing
support" unless you have more than one processor, or a Duo or Quad
one. Pick the right processor at Processor Family, and the amount of
RAM you have at High Memory Support. At Preemption Model, pick the
"Preemptible Kernel (Low Latency Desktop)" option. Finally, check
"Preempt the Big Kernel Lock," and at "Timer Frequency" pick 1000Hz.
At Kernel Hacking, uncheck everything -- you won't be doing kernel
development, will you?

After you have finished picking options, exit the configuration
program (say "YES" when asked about saving your new kernel
configuration) and then run:

make
make modules_install
make install

Pay particular attention to unexpected error messages that might show
a problem with your new kernel. Be prepared to wait; on my laptop, the
make process takes more than half an hour. If get an error message,
you can either go back to the menu to try and fix whatever was wrong,
or just reboot with your backup kernel. If you cannot figure out what
happened (quite possible: it's not always easy to relate an error to
your menu choices) you can always reinstall your kernel (use YAST or
Smart, as above) and start again.

If there were no error messages, reboot and try your new kernel.

In my case, I shaved about 10 seconds off the boot time, and also
freed a couple of megabytes of RAM. The boot speedup isn't really
noticeable, but the laptop now feels a bit more agile -- though that
could of course be a placebo effect. Anyway, I learned a bit more
about the kernel, optimized it for my own use, and gained a new tool
in my search for speed.

In conclusion

If you want the swiftest possible Linux, don't be afraid to compile
the kernel. You can learn a lot, and in the end you should get better
system performance.

阅读全文！

Acer 4530 wireless configuration openSUSE 11.0

Acer 4530 wireless configuration openSUSE 11.0 - howto solve the
Atheros Communications Inc. AR242x problems ath5k phy0: failed to
wakeup the MAC Chip

Initial condition of my configuration problems:

A complete system upgrade from openSUSE 10.2 to openSUSE11.0 using
DVD. Before update ALL worked perfectly, after update NO wireless HW
recognized.

ath5k with a persistent "failed to wakeup the MAC Chip" vs ath_pci
with full AR242x support

Good news first:

it's working without recompiling, without special patches - just a
little creative thinking
The same solution below may also work for others

Error messages experienced directly after system update from openSUSE
n10.2 to 11.0

lspci shows:

07:00.0 Ethernet controller: Atheros Communications Inc. AR242x
802.11abg Wireless PCI Express Adapter (rev 01)

Error messages have been

kernel: ath5k phy0: failed to wakeup the MAC Chip
kernel: ath5k_pci: probe of 0000:07:00.0 failed with error -5
ath5k_pci 0000:07:00.0: registered as 'phy0'
kernel: wifi%d: unable to attach hardware: 'Hardware didn't respond as
expected' (HAL status 3)

Long search with Google thru various forums, blogs and howtos shows
that many others have exactly same problem using SuSE 11.0 and their
old good working wireless chip after the update. My update was from
openSUSE 10.2 to 11.0. Before with 10.2, I was using the kernel module
ath_pci with zero problems for approximately one full year. By default
the new openSUSE 11.0 always wants to use ath5k which fails to support
the Atheros AR242x chip. Some have found a working solution with
patching or recompiling,, others still are desperate. Here my
contribution of one among many possible solutions.

I have repeatedly tested below method, rebooted this ending night
about half a dozen time to assure the wireless chip works dependable
after every reboot. It appears to me that the new drivers NOW in use
provide a faster connection, better/stronger signal than the earlier
madwifi version I used under openSUSE 10.2!

Original situation after the complete system UPGRADE from suse 10.2 to 11.0

After the update to openSUSE 11.0 using newest kernel Linux
2.6.25.16-0.1-default #1 SMP 2008-08-21 00:34:25 +0200 x86_64 x86_64
x86_64 GNU/Linux, updated just minutes before the final successful
repeated testing, The hardware was NOT connected and a configuration
impossible.

Various solutions offered had little attraction to me, I wanted an out
of the box working wifi connection !

Here a few steps I FIRST went thru - without success:

Repeated times the ath5k always was loaded first in addition to
ath_pci. An often recommended blacklist in /etc/modprobe.d/blacklist
failed to work. repeated times despite the blacklist entry blacklist
ath5k, the kernel module ath5k with all its "sister" modules were all
present !

A removal of:

rmmod ath5k
rmmod mac80211
rmmod cfg80211

still gave NO success.!

Even a complete removal of ALL wireless relevant modules and modeprobe
of ath_pci brought NO success.!

Of course AFTER every major configuration change a REBOOT ..... still
the entire configuration in

Network --- Networksetting --- AR242x 802.11abg Wireless PCI Express
Adapter showed NO hardware information and thus was NOT free for edit
to finalize the wifi setup.

Hence I use ADD in Network --- Networksetting to add a wireless device
and entered ath_pci as the module. Then I rebooted and the wifi was
working ONCE - after the next reboot it all was like before - a.m.-
i.e. failed to wakeup the MAC Chip !

kernel module ath5k still loaded despite blacklist entry!

After the reboot however - using ath_pci in the added 3rd network
device the AR242x 802.11abg Wireless PCI Express Adapter device was
free to edit !! Hence I changed the default module ath5k to ath_pci,
then removed my added 3rd device, blacklisted again - then REBOOT
again. finally the wireless worked!

Hence the important steps for your AR242x 802.11abg Wireless PCI
Express Adapter configuration on Acer Ferrari 5000:

REMOVE any other packages you might have from earlier OLD Linux
version. I had driverloader and ndiswrapper present and uninstalled
any wireless relevant package except the newest madwifi packages !

The madwifi I installed are official openSUSE packages for x86_64
architecture. My laptop runs on dual 64 bit CPUs. The madwifi packages
installed are the newest official packages as of the date of this
writing:

madwifi-0.9.4-1.x86_64.rpm
madwifi-kmp-default-0.9.4_2.6.25.5_2-1.x86_64.rpm

After install of a.m. packages, a few steps below:

rmmod ath5k + rmmod mac80211 + rmmod cfg80211
in Network --- Networksetting ADD NEW device - as wireless, add the
kernel module ath_pci
/etc/modprobe.d/blacklist enter at bottom a new blacklist entry blacklist ath5k,
reboot
after boot delete your earlier added new wireless device, then edit
your NOW editable AR242x 802.11abg Wireless PCI Express Adapter, enter
ath_pci as kernel module!
Your hardware now should become visible - if in range of an AP you
should see the signal. You may however have to restart your network
with rcnetwork restart. For unknown reason the NEW kernel modules do
NOT autoconnect to the wireless network, even after a new system-start
or reboot!

add new wireless device using kernel module ath_PCi

After all above changes - a short prayer and then a reboot. Your
verification in your network configuration should show all still
correct as below picture. In my Ferrari 5000 case I have 2 network
devices, 1 LAN and one wireless. Both properly recognized and working.

Finally only 2 network devices - WIFI and LAN

For an unknown reason the WLAN does NOT auto-connect to the nearest AP
even if configured to load on boot or on cable connect ( for wlan
cable connect = AP availability ). The problem is annoying but a
simple rcnetwork restart always connects properly to the available AP!
There is justified hope that a soon to come kernel / madwifi update
may solve this issue.

A brief verification of:

lspci -v | grep Atheros -A 20 | grep -v Capabilities | sed
's/^$/\n\n\n\n\n\n\n\n\n\n/' | head -n 10 | uniq shows:

07:00.0 Ethernet controller: Atheros Communications Inc. AR242x
802.11abg Wireless PCI Express Adapter (rev 01)
Subsystem: AMBIT Microsystem Corp. Device 0422
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at b0200000 (64-bit, non-prefetchable) [size=64K]
Kernel driver in use: ath_pci
Kernel modules: ath_pci, ath5k

Thus all perfect now. Above success message ALSO exists directly after
reboot / BEFORE rcnetwork restart. So may be the missing connection to
the AP before the rcnetwork restart may be a timing problem. May be
the AP is too slow for built-in timeout limits or the attempt to
access the AP occurs too early during the boot process ... ?
Nevertheless, the problem is a minor and since I reboot my laptop
every many days or weeks except during travel, it's no deal for me.
But all earlier years until now the wifi connection ALWAYS was up and
running right after the boot/reboot ! Hence this issue may be but a
temporary minor bug to be fixed soon.

My first attempts to blacklist ath5k FAILED

Remember that for an unknown reason my first attempts to blacklist
ath5k FAILED during at least 2-3 reboots !!! Now however it appears to
reliably work. NONE of any ath5k relevant modules is present / loaded
in the current running system. It is UNKNOWN to me what exactly caused
the blacklist NOW to work after repeated initial failures!!!

It took me countless hours during the past 2 days and intense googling
on my second laptop ( Ferrari 4000 ) to search and read thru all the
different other solutions and problems others had and many still have.
Hence I am happy to have it working. The advantage of my current
working solution is that ALL is default openSUSE - all packages, all
configuration ( except the blacklist entry ) and thus ALL current
working system can and will be regularly UPDATED using YAST online
update until one day it all works again as it did all the years
before.
阅读全文！