Mailinglist Archive: opensuse (4054 mails)
| < Previous | Next > |
Re: [SLE] wireless problem <SOLVED> again
- From: Paul Cartwright <paul_tbot@xxxxxxxxxxxxxxx>
- Date: Mon, 2 Jan 2006 10:24:58 -0500
- Message-id: <200601021024.58807.paul_tbot@xxxxxxxxxxxxxxx>
On Mon January 2 2006 10:11 am, Dave Howorth wrote:
> > actually I did reboot, a number of times, and I also did
> > if/up/down and network stop/start.
>
> Sorry I obviously phrased that badly! What I meant was - you said
> that you did a reboot, and I'm saying that was what caused you to
> lose the effect of the route command. You made your system work in a
> way that doesn't persist over a reboot. You need to use a different
> technique to fix it permanently - use Yast or edit config files
> directly.
what happened was, I got wireless working. THEN I updated KDE to 3.5
and rebooted. That's when I lost wireless. I had rebooted to get
wireless working, made no changes to it, THEN did the KDE upgrade.
At least that's my story and I'm sticking to it! I'll go back and check
my settings and reboot..
>
> Sadly, I don't think you'll find anybody that will disagree with
> you. Wired networking is inherently simpler and it's also been
> around in a relatively stable form for MUCH longer. So the
> configuration procedures are much better established and simpler for
> the user.
and of course windows makes it work and is supported by most tech
support groups...
>
> But it sounds like you did get your wireless going. So you've found
> all the important factors. Now you just need to make the changes
> permanent. You're almost there.
that's what I'm trying to do !
>
> And IMHO, rebooting after you've made the changes is an excellent
> thing to do because it tests that you have made the right changes.
> If you don't reboot and next month do something else (change a
> printer?) and the month after do something else etc, then when you
> finally do reboot you may find a whole bunch of things stop working
> and you won't have a clue what the reason is. It could be any one,
> or any combination of all the things you've done since the last
> reboot. It's much easier to make sure each set of changes are
> persistent individually, in my experience.
exactly. It is much easier to trouble shoot ONE change.. I do try and
reboot after changing anything important, or adding software.. always
install kernel changes by themselves,etc..
>
> Cheers, Dave
happy new year!!
--
Paul Cartwright
Registered Linux user # 367800
X-Request-PGP: http://home.bellsouth.net/p/PWP-pcartwright/key.asc
> > actually I did reboot, a number of times, and I also did
> > if/up/down and network stop/start.
>
> Sorry I obviously phrased that badly! What I meant was - you said
> that you did a reboot, and I'm saying that was what caused you to
> lose the effect of the route command. You made your system work in a
> way that doesn't persist over a reboot. You need to use a different
> technique to fix it permanently - use Yast or edit config files
> directly.
what happened was, I got wireless working. THEN I updated KDE to 3.5
and rebooted. That's when I lost wireless. I had rebooted to get
wireless working, made no changes to it, THEN did the KDE upgrade.
At least that's my story and I'm sticking to it! I'll go back and check
my settings and reboot..
>
> Sadly, I don't think you'll find anybody that will disagree with
> you. Wired networking is inherently simpler and it's also been
> around in a relatively stable form for MUCH longer. So the
> configuration procedures are much better established and simpler for
> the user.
and of course windows makes it work and is supported by most tech
support groups...
>
> But it sounds like you did get your wireless going. So you've found
> all the important factors. Now you just need to make the changes
> permanent. You're almost there.
that's what I'm trying to do !
>
> And IMHO, rebooting after you've made the changes is an excellent
> thing to do because it tests that you have made the right changes.
> If you don't reboot and next month do something else (change a
> printer?) and the month after do something else etc, then when you
> finally do reboot you may find a whole bunch of things stop working
> and you won't have a clue what the reason is. It could be any one,
> or any combination of all the things you've done since the last
> reboot. It's much easier to make sure each set of changes are
> persistent individually, in my experience.
exactly. It is much easier to trouble shoot ONE change.. I do try and
reboot after changing anything important, or adding software.. always
install kernel changes by themselves,etc..
>
> Cheers, Dave
happy new year!!
--
Paul Cartwright
Registered Linux user # 367800
X-Request-PGP: http://home.bellsouth.net/p/PWP-pcartwright/key.asc
| < Previous | Next > |