>
> I could agree with this if the Sony's behavior was seen on the other 6
> portables on which I've run linux and Slackware. This Sony Vaio is unique
> in
> the persistence with which it refuses to connect to wireless networks. :-)
>
> In the next couple of days, I'll de-activate wicd and instal
On Apr 11, 2012, at 2:46 PM, Rich Shepard wrote:
> My suspicion is that the wireless chip is still new enough that the driver
> does not handle it under all circumstances, even with the 3.2.7 kernel.
Rich,
Just throwing this out there...
Wouldn't this assume it is the responsibility of the wi
On Wed, 11 Apr 2012, Mike Connors wrote:
> Yes, I understand that and that's why I'm suggesting to either delete or
> comment out (#) the eth0 stanza from /etc/rc.d/rc.inet1.conf. Thdn upon
> boot, eth0 will not be brought up and a def route via its interface won't
> be injected into the routing t
>
> > > That's not what I meant. I should have written "have you deleted the
> > > static ip config stanza from /etc/rc.d/rc.inet1.conf file and then
> tested
> > > net connectivity over wifi.?"
> >
> >No. The eth0 interface needs to come down when wlan0 is up, even if
> eth0
> > is not running
On Tue, 10 Apr 2012, Michael Rasmussen wrote:
> As I understand your use cases:
> - at home running on wired (eth0)
> - at a WiFi hotspot running on air (wlan0)
Correct.
> And you never use both at the same time.
> Yes? No?
Yes.
With the wireless issues being a PITA I (with Wes' exper
On Tue, Apr 10, 2012 at 05:22:27PM -0700, Rich Shepard wrote:
> On Tue, 10 Apr 2012, Mike Connors wrote:
>
> > That's not what I meant. I should have written "have you deleted the
> > static ip config stanza from /etc/rc.d/rc.inet1.conf file and then tested
> > net connectivity over wifi.?"
>
>
On Tue, 10 Apr 2012, Mike Connors wrote:
> That's not what I meant. I should have written "have you deleted the
> static ip config stanza from /etc/rc.d/rc.inet1.conf file and then tested
> net connectivity over wifi.?"
No. The eth0 interface needs to come down when wlan0 is up, even if eth0
i
>
>
> D) It's not connectivity to the WAP that's the problem, it's accessing
> the
> 'Net (directly or via a T&C Web page first) that fails because the packets
> apparently insist on forcing themselves on the non-running eth0 and there's
> no cable to move them along. So they die.
>
>
> I use the
On Tue, 10 Apr 2012, Mike Connors wrote:
> ... I suspect there is a problem in the interaction between the NIC driver
> and your chosen net mgmt. software. Is WICD a native app to slackware? If
> not, is there a native net mgmt. app? If there's not a native net mgmt app
> is there another net mgmt
>
> Still don't have the Sony Vaio working with wireless hot spots, but know
> why and would like your ideas on how to remedy the problem.
>
> When I invoke wicd on my Dell Latitude and it connects to the WAP eth0 is
> brought down ('ifconfig eth0 down' in Slackware) so the only network
> inter
Still don't have the Sony Vaio working with wireless hot spots, but know
why and would like your ideas on how to remedy the problem.
When I invoke wicd on my Dell Latitude and it connects to the WAP eth0 is
brought down ('ifconfig eth0 down' in Slackware) so the only network
interface in the
11 matches
Mail list logo
