Following my post related to NetworkManager. I have found out about the workaround. If you have x86_64 system with 4GB support enabled, you should disable it in order to make NetworkManager work. I am not sure if that bug affects other distributions so, possibly the bug may be related to the x86_64 kernel. Let see if my theory can be verified.
Busy weekend. I just took a break for making a presentation of Fedora Core 6 and Fedora Project for Vancouver Linux Users Group which will debut on November 20, 2006. A local computer store was kind enough to give me a laptop for the demonstration of Fedora Core 6 (Zod) live spin and Sugar interface from OLPC Project. Should you be interested to view that event and live near Vancouver, here is the address .
Comments
Currently using x86_64 with 4gb + networkmanager. No such issues.
Its a Thinkpad T61 with Intel 3945ABG wireless
Turns out it is something specific to the Marvell network card. I have two NICs on my motherboard and I tried the other one (Nvidia) and network seems to work perfectly! So maybe your problem could be fixed/worked around by trying a different network card.
When I upgraded from 2GB to 4GB, I went into the BIOS, Ctrl-F1 to get to the advanced chipset features, then enabled 4G RAM support. After that, when I booted I couldn't access the network. Interestingly, there was a boot-time message from the kernel
skge eth1: enabling interface, so I didn't look there for the problem.
After reading the posts here I went back, disabled 4G support and got my network back - at the cost of a few hundred MB of RAM. The kernel now only sees 3584MB instead of the 4096MB it saw before.
Pete
桃園房屋買賣 關鍵字行銷關鍵字seo 關鍵字行銷關鍵字seo
導光板 衝孔網 菱型網 不鏽鋼 壯陽 成人用品春藥 壯陽藥品 持久 手工水餃 中華湯包 mini usb 催情 增大 模具廠 104法拍網 信義房屋 房屋買賣 台北法拍屋 塑膠射出成型 模具 Odm 塑膠射出模具 Oem代工廠化妝品盒 藥盒