On Sat, Jun 28, 2008 at 12:34 AM, Mike McMullin wrote:

Can you expand that please, 11.0 broke my wireless, and i think it's the atheros driver at primary fault?

There is a new atheros driver from the madwifi project that's fully open source and can now be included in the kernel(it's called ath5k). It's based on a bsd version, but it's still in the alpha stages. It seems to only work with the 5xxx series chipsets. While it worked with my netgear card ok for browsing, I couldn't do any scp transfers because it would drop the packets. I ended up just compiling the old ath_pci module and now it works fine. There is also a madwifi repository, but I never could get it to work before, and it's just as easy for me to compile it anyway. YaST also has an issue with selecting the ath5k driver for unsupported chipsets. My Dlink card uses the 2413 chip, and ath5k doesn't support it. However, YaST selected the ath5k module and said it was configured. I'm guessing they never resolved that issue before 11.0 was fully released.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sat, 2008-06-28 at 09:57 -0400, Larry Stotler wrote:

On Sat, Jun 28, 2008 at 12:34 AM, Mike McMullin wrote:

...

Can you expand that please, 11.0 broke my wireless, and i think it's the atheros driver at primary fault?

There is a new atheros driver from the madwifi project that's fully open source and can now be included in the kernel(it's called ath5k). It's based on a bsd version, but it's still in the alpha stages. It seems to only work with the 5xxx series chipsets. While it worked with my netgear card ok for browsing, I couldn't do any scp transfers because it would drop the packets. I ended up just compiling the old ath_pci module and now it works fine. There is also a madwifi repository, but I never could get it to work before, and it's just as easy for me to compile it anyway.

That the ticket, the wireless worked perfectly under the ath_pci, can i get an URL for the source that you used?

YaST also has an issue with selecting the ath5k driver for unsupported chipsets. My Dlink card uses the 2413 chip, and ath5k doesn't support it. However, YaST selected the ath5k module and said it was configured. I'm guessing they never resolved that issue before 11.0 was fully released....

Yeah, and the mad-wifi update this week didn't help at all. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Mike McMullin wrote:

...

If you are using the new kernel based atheros wireless driver, you will very likely get lots of error messages. I ended up compiling the madwifi driver from source to fix that(they do have a repository for it now). What exactly is in the logs.

Can you expand that please, 11.0 broke my wireless, and i think it's the atheros driver at primary fault?

I finally gave up and upgraded to XP-Pro on my Toshiba laptop (with Atheros wireless card). Works great. I haven't given up on SuSE Linux -- I still have a desktop workstation and a domain controller running on v11.0, with KDE4, no less. But I had to admit that the support just isn't there for this laptop. After fussing and fighting with it for a week or so, I'd finally had enough. What I mostly use are Thunderbird, Firefox, Sunbird, and OpenOffice. They all run just fine on XP-Pro, and my smb server works way better than nfs ever did on this machine. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Sloan wrote:

Just as an FYI there are other linux distros. If suse doesn't work well on a particular machine, if it were me, I'd try ubuntu or something, rather than throw in the towel and retreat to ms windows.

Yeah, I didn't mention it, for the sake of brevity, but I did try kubuntu "Hardy Heron" as well. There were things about it I liked, such as their approach to dealing with Atheros cards, but there were disappointments with it as well. For example, I couldn't get nfs working with it as a client and SuSE as the server, and it's important for me to be able to keep 8 or 9 server shares available to the other computers in the house. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jerry Houston wrote:

Joe Sloan wrote:

...

Just as an FYI there are other linux distros. If suse doesn't work well on a particular machine, if it were me, I'd try ubuntu or something, rather than throw in the towel and retreat to ms windows.

Yeah, I didn't mention it, for the sake of brevity, but I did try kubuntu "Hardy Heron" as well. There were things about it I liked, such as their approach to dealing with Atheros cards, but there were disappointments with it as well. For example, I couldn't get nfs working with it as a client and SuSE as the server, and it's important for me to be able to keep 8 or 9 server shares available to the other computers in the house.

Ah, that's another thing. I've found that while for me ubuntu has been rock solid, kubuntu is not so good. Not only the default app selection - no firefox, no synaptic, but apps would also crash on kubuntu, sort of the inverse of my experience with suse 11.0. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org