nray
April 23rd, 2008, 11:39 AM
So I had been running 32-bit Ubuntu/Mythbuntu 7.10 without any problems, and recently upgraded the memory in my machine to 8GB. First I tried the server kernel with PAE so I could use all the RAM in 32-bit mode, but discovered there are no restricted drivers available for the server kernel, so I decided to try Mythbuntu 7.10 AMD64.
Wired networking is on-board Marvell 88E8056 gigabit ethernet, and wireless is an Abit Airpace (Atheros AR5007EG) 802.11g. Both worked great in 32-bit, though I had to download and compile the source to ndiswrapper to get the AR5007EG working with the WHQL XP driver 5.3.0.56 (the open-source Atheros driver currently has a bug detecting the AR5007EG properly because it re-uses the same PCI identifier the AR5006 series uses, and the ndiswrapper in the gutsy package system is version 1.3, which also has bugs with the AR5007EG, which were fixed in later versions of ndiswrapper).
In many weeks of use, neither wired (Marvell 88E8056) or wireless (Atheros AR5007EG) gave me a moment of trouble in 32-bit.
In 64-bit, it's another story. It first appeared there was a dhcp issue with the Atheros AR5007EG using ndiswrapper (1.52) and the WHQL XP 64-bit 5.3.0.56 drivers, because it had no trouble seeing other wireless networks, it would just timeout during dhcp request. So I manually set all the IP and wireless network information, yet that made no difference (pings to the gateway IP would time out).
Then I tried an ASUS WL-167G USB 802.11g adapter (RaLink RT2500USB), which I'd read should just work out of the box with 7.10, and it was recognized, but nothing I did could get it to connect to my wireless network in 64-bit Mythbuntu 7.10, apparently the same symptoms I saw on the AR5007EG! I removed it and rebooted.
During this 64-bit testing, most of the time the wired connection was fine, however sometimes it would drop and not come back while I was trying different wireless settings in the Network control panel (but if I rebooted it would come back). Annoyed with that, I changed the wired connection from auto-roam to dhcp, and the wired connection just stopped working even across reboots, which I find just bizarre.
Anyone have any idea what is going on? Something seems seriously fubar. I've never had this much trouble with any linux distro.
Wired networking is on-board Marvell 88E8056 gigabit ethernet, and wireless is an Abit Airpace (Atheros AR5007EG) 802.11g. Both worked great in 32-bit, though I had to download and compile the source to ndiswrapper to get the AR5007EG working with the WHQL XP driver 5.3.0.56 (the open-source Atheros driver currently has a bug detecting the AR5007EG properly because it re-uses the same PCI identifier the AR5006 series uses, and the ndiswrapper in the gutsy package system is version 1.3, which also has bugs with the AR5007EG, which were fixed in later versions of ndiswrapper).
In many weeks of use, neither wired (Marvell 88E8056) or wireless (Atheros AR5007EG) gave me a moment of trouble in 32-bit.
In 64-bit, it's another story. It first appeared there was a dhcp issue with the Atheros AR5007EG using ndiswrapper (1.52) and the WHQL XP 64-bit 5.3.0.56 drivers, because it had no trouble seeing other wireless networks, it would just timeout during dhcp request. So I manually set all the IP and wireless network information, yet that made no difference (pings to the gateway IP would time out).
Then I tried an ASUS WL-167G USB 802.11g adapter (RaLink RT2500USB), which I'd read should just work out of the box with 7.10, and it was recognized, but nothing I did could get it to connect to my wireless network in 64-bit Mythbuntu 7.10, apparently the same symptoms I saw on the AR5007EG! I removed it and rebooted.
During this 64-bit testing, most of the time the wired connection was fine, however sometimes it would drop and not come back while I was trying different wireless settings in the Network control panel (but if I rebooted it would come back). Annoyed with that, I changed the wired connection from auto-roam to dhcp, and the wired connection just stopped working even across reboots, which I find just bizarre.
Anyone have any idea what is going on? Something seems seriously fubar. I've never had this much trouble with any linux distro.