View unanswered posts    View active topics

Board index KnoppMyth Hardware

All times are UTC - 6 hours





Post new topic Reply to topic  Page 1 of 1
  [ 4 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
saruman
PostPosted: Tue Jan 17, 2006 5:50 am 
Offline
Joined: Mon Feb 23, 2004 1:08 am
Posts: 91
Location: Switzerland
Summary:
- I have performed an upgrade to R5A30.1
- The old wireless card does not associate anymore
- A new wireless card compatible with madwifi has trouble associating, and when it does, traffic doesn't seem to go anywhere
- The same hardware setup works flawlessly under a stock Knoppix 4.02 live CD

Log:

- Machine has been running under R4V4 for a while. Figured it was time for an upgrade
- Did an upgrade to preserve /myth partition, but config files from backup caused many-o messes. So I renamed the backup file so that the upgrade wouldn't find it. Re-installed (with upgrade option).

- Can't get the wireless card to work. It worked for months under R4V4, after cutomization to get it going (ndiswrapper, etc...)


- Tried getting it to work for a while (ndiswrapper, acx100), then figured it was maybe caused by the switch to 2.6 kernel.
- Changed the card to a Netgeat WG311T, said to be supported by Madwifi (atheros chipset)
- Downloaded, installed, configured latest madwifi drivers

Current situation:
- The card will "sometimes" associate properly (with an AP that is about 3 feet away). When it does, reported connection speed is lousy.
- I have noticed that bringing up eth0 will trigger ath0 to associate about 5 seconds later. I don't understand at all why that is.
- I then bring eth0 down and try to ping the gateway with ath0, but it can't connect.
- Everything *seems* to be working fine. Logs look ok, config looks ok, etc.
- The same hardware setup in the same spot works flawlessly under a stock Knoppix 4.02 live CD. The card associates right away, connection speed is 54M, connectivity is here.
- I just can't figure it out. It annoys me. I need help.

My questions:
- Is this a kernel problem? Is the kernel somehow misconfigured (explaining the weird behaviour). I have tried rebuilding it from the sources included, but no luck. Are there some secret config options that need to be enabled?
- Is someone actually running a WLAN with Atheros chipset under R5A30.1?
- What should I do next, short of starting from scratch with a Sarge netinstall CD?

Log file and such:
Code:
iwconfig:
=========
ath0      IEEE 802.11g  ESSID:"baybridge" 
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:C0:49:53:00:CC   
          Bit Rate:54 Mb/s   Tx-Power:18 dBm   Sensitivity=0/3 
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=61/94  Signal level=-34 dBm  Noise level=-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
ifconfig:
=========
ath0      Link encap:Ethernet  HWaddr 00:0F:B5:86:E1:82 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:b5ff:fe86:e182/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:46 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:200
          RX bytes:13563 (13.2 KiB)  TX bytes:1204 (1.1 KiB)
          Interrupt:11 Memory:d4e60000-d4e70000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2915 (2.8 KiB)  TX bytes:2915 (2.8 KiB)

route -n:
=========

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 ath0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 ath0

ping gateway:
=============

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
From 192.168.1.2 icmp_seq=2 Destination Host Unreachable
From 192.168.1.2 icmp_seq=3 Destination Host Unreachable
From 192.168.1.2 icmp_seq=5 Destination Host Unreachable
From 192.168.1.2 icmp_seq=6 Destination Host Unreachable
From 192.168.1.2 icmp_seq=7 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7022ms

lsmod | grep ath:
=================

ath_pci                70300  0
ath_rate_sample        15624  1 ath_pci
wlan                  129052  3 ath_pci,ath_rate_sample
ath_hal               148688  3 ath_pci,ath_rate_sample

cat /var/log/messages | grep ath (removed duplicates):
======================================================
Jan 13 17:18:12 mythtv kernel: ath_hal: module license 'Proprietary' taints kernel.
Jan 13 17:18:12 mythtv kernel: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)
Jan 13 17:18:12 mythtv kernel: ath_rate_sample: 1.2
Jan 13 17:18:12 mythtv kernel: ath_pci: 0.9.6.0 (EXPERIMENTAL)
Jan 13 17:18:13 mythtv kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 13 17:18:13 mythtv kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
Jan 13 17:18:13 mythtv kernel: ath0: turboG rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
Jan 13 17:18:13 mythtv kernel: ath0: H/W encryption support: WEP AES AES_CCM TKIP
Jan 13 17:18:13 mythtv kernel: ath0: mac 7.9 phy 4.5 radio 5.6
Jan 13 17:18:13 mythtv kernel: ath0: Use hw queue 1 for WME_AC_BE traffic
Jan 13 17:18:13 mythtv kernel: ath0: Use hw queue 0 for WME_AC_BK traffic
Jan 13 17:18:13 mythtv kernel: ath0: Use hw queue 2 for WME_AC_VI traffic
Jan 13 17:18:13 mythtv kernel: ath0: Use hw queue 3 for WME_AC_VO traffic
Jan 13 17:18:13 mythtv kernel: ath0: Use hw queue 8 for CAB traffic
Jan 13 17:18:13 mythtv kernel: ath0: Use hw queue 9 for beacons
Jan 13 17:18:13 mythtv kernel: ath0: Atheros 5212: mem=0x42000000, irq=11
Top
 Profile  
 
saruman
 Post subject:
PostPosted: Fri Jan 20, 2006 5:46 am 
Offline
Joined: Mon Feb 23, 2004 1:08 am
Posts: 91
Location: Switzerland
Following up on my own thread...

Someone managed to get an atheros-based card working, so it's probably not a kernel issue (http://mysettopbox.tv/phpBB2/viewtopic.php?t=7935)

but

I reinstalled from scratch with a Debian 3.1 CD, and everything works well, so it doesn't seem to be my hardware.

Bottom line: I have no clue.
Top
 Profile  
 
tophee
 Post subject:
PostPosted: Wed Jan 25, 2006 2:43 pm 
Offline
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location: London, UK
Hi Saruman,
Have you made any progress? I've just bought a netgear router (WGT624) and network card also netgear (WG311T) and the router side looks good and is set up ok. My mobo in my Mythboxen is NF7 v2 and I've disabled the onboard LAN in the BIOS. I was under the impression it should just detect the card.
But not so far.
Any more info would be good.

btw, thanks for the thread link. That's useful.

I had already googled Netgear WG311T and Linux and I got lots of hits. haven't had time to investigate fully, but this looks interesting http://www.packetpro.com/~peterson/linux-netgear_wg311t_pci.html
In my initial glance I noticed they refer to "ath0" which I assume is atheros chipset, which means the drivers are there if the thread you listed is correct.
Anyway, I'll be trying to get this sorted over the next couple of days.

Regards Chris
Top
 Profile  
 
saruman
 Post subject:
PostPosted: Thu Jan 26, 2006 1:23 am 
Offline
Joined: Mon Feb 23, 2004 1:08 am
Posts: 91
Location: Switzerland
Well, as I mentioned, everything works now, using the madwifi drivers.
The thing that really stomped me was the fact that I didn't get any errors, problems, etc... but the network connectivity just wasn't happening, or intermittently with very strange patterns.

So, again, I don't know what it was. I just couldn't figure out where to start to fix it, so I just reinstalled from scratch (I had wanted to do it anyway someday).

A few comments
1) I installed a 2.4.27 kernel, not a 2.6. Maybe that's the difference.

2) Installing from scratch took a long time, and quite some skill. Good thing I had prior experience with MythTV and Linux...: so stick with KnoppMyth, it's the best solution!

3) I will test with a later release when I get a chance (but it requires taking apart my box so it might not happen right away)
Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 4 posts ] 


Board index KnoppMyth Hardware

All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 9 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu