> > > Try moving it closer to the access point, if possible, and if it > > > still fails from time to time; > > > if it does there might be a driver or hardware problem > > > > > > Catalin > > > > Here's the thing. It can't be a real range issue because it was > > working perfectly before. I won't be able to narrow it down to a > > hardware issue until I've experimented with the software side of > > things right? I have these in package.keywords for this wireless > > connection: > > > > net-wireless/madwifi-driver ~x86 > > net-wireless/madwifi-tools ~x86 > > net-wireless/wireless-tools ~x86 > > sys-apps/baselayout ~x86 > > app-shells/bash ~x86 > > sys-libs/readline ~x86 > > sys-apps/sysvinit ~x86 > > > > Should I try removing them and emerge the stable stuff? > > > > - Grant > > Actually the masked baselayout seems to have fixed this.... > > - Grant
Ok, it's much better but not as steady as it was. Does this narrow it down to a baselayout issue pretty well? - Grant > > > >I have 3 Gentoo systems connected to my wireless network. 2 of them > > > >have Netgear PCMCIA wireless cards and the third has a PCI card that > > > >is a Netgear of the same series (if you know what I mean). That > > > >desktop is the farthest away from the access point, but it has had a > > > >rock-solid connection for a long time. It is now connected only > > > >intermittently. It always seems to connect on boot up, but sometimes > > > >it can reach the network during operation and sometimes it can not. > > > >It is 100% up to date with the portage tree and I have tried > > > >rebooting. Does anyone have any ideas? > > > > > > > >I'm using the madwifi-driver and wpa_supplicant with a WPA network. > > > > > > > >- Grant -- [email protected] mailing list
