On Mon, Jan 25, 2010 at 3:14 PM, Steve D... wrote:
> On Mon, Jan 25, 2010 at 2:38 PM, Denis Heidtmann
> wrote:
>> On Mon, Jan 25, 2010 at 12:33 PM, Steve D... wrote:
>>
Do you see this as an accurate assessment?
>>>
>>> Pretty much... Your available choices are:
>>>
>>> 1) Deal with it...
On Mon, Jan 25, 2010 at 2:38 PM, Denis Heidtmann
wrote:
> On Mon, Jan 25, 2010 at 12:33 PM, Steve D... wrote:
>
>>> Do you see this as an accurate assessment?
>>
>> Pretty much... Your available choices are:
>>
>> 1) Deal with it... You many have to "ifconfig up" your eth port from
>> time to ti
On Mon, Jan 25, 2010 at 12:33 PM, Steve D... wrote:
> On Sat, Jan 23, 2010 at 7:17 PM, Denis Heidtmann
> wrote:
>>
>> Thanks for all the information. You have saved me from a fruitless
>> bunch of tests. I do not claim to have gotten my head around all the
>> stuff in those links, but I have th
On Sat, Jan 23, 2010 at 7:17 PM, Denis Heidtmann
wrote:
>
> Thanks for all the information. You have saved me from a fruitless
> bunch of tests. I do not claim to have gotten my head around all the
> stuff in those links, but I have the impression that if the NIC is
> misbehaving during the auto
Denis Heidtmann wrote:
> The connection has not had a failure for some days now (many shutdowns
> and reboots, but no interruption of power to the modem or the
> computer), even though renegotiation is likely happening often. Also,
> when failure occurs the only thing which appears to fix it is to
Denis Heidtmann wrote:
> Thanks for all the information. You have saved me from a fruitless
> bunch of tests. I do not claim to have gotten my head around all the
> stuff in those links, but I have the impression that if the NIC is
> misbehaving during the autonegotiation process I have no reason
On Sat, Jan 23, 2010 at 11:27 AM, Steve D... wrote:
> On Thu, Jan 21, 2010 at 7:25 PM, Mike Connors wrote:
>> Denis Heidtmann wrote:
>>> I am glad you have focused on this. Since it is the only thing I have
>>> found which is consistently different between failed and working
>>> modes, it deserv
On Thu, Jan 21, 2010 at 7:25 PM, Mike Connors wrote:
> Denis Heidtmann wrote:
>> I am glad you have focused on this. Since it is the only thing I have
>> found which is consistently different between failed and working
>> modes, it deserves some scrutiny. I think it is interesting that the
>> un
On Thu, Jan 21, 2010 at 7:25 PM, Mike Connors wrote:
> Denis Heidtmann wrote:
>> I am glad you have focused on this. Since it is the only thing I have
>> found which is consistently different between failed and working
>> modes, it deserves some scrutiny. I think it is interesting that the
>> un
Denis Heidtmann wrote:
> I am glad you have focused on this. Since it is the only thing I have
> found which is consistently different between failed and working
> modes, it deserves some scrutiny. I think it is interesting that the
> unused capability (1000baseT) is what is missing when in the f
On Thu, Jan 21, 2010 at 6:33 PM, Mike Connors wrote:
> Denis Heidtmann wrote:
>> Don't jump to conclusions based upon a novice like me reading a
>> script! There could be stuff in there that I missed.
>>
>> It sounds like the consensus here is that to duplicate what happens to
>> the network duri
Denis Heidtmann wrote:
> Don't jump to conclusions based upon a novice like me reading a
> script! There could be stuff in there that I missed.
>
> It sounds like the consensus here is that to duplicate what happens to
> the network during boot I would need to [remove the driver (rmmod),
> restart
Don't jump to conclusions based upon a novice like me reading a
script! There could be stuff in there that I missed.
It sounds like the consensus here is that to duplicate what happens to
the network during boot I would need to [remove the driver (rmmod),
restart the network( ifup?) , ping ], rep
Denis Heidtmann wrote:
> On Thu, Jan 21, 2010 at 12:07 PM, Mike Connors wrote:
>
>>> (BTW, my system has no such command as "network").
>>>
>>> -Denis
>>>
>>>
>> /etc/init.d/networking
>> Usage: /etc/init.d/networking {start|stop}
>>
>
> Mike,
> Looking at the script "networking"
On Thu, Jan 21, 2010 at 12:07 PM, Mike Connors wrote:
>
>> (BTW, my system has no such command as "network").
>>
>> -Denis
>>
> /etc/init.d/networking
> Usage: /etc/init.d/networking {start|stop}
Mike,
Looking at the script "networking" it seems that all it does, after
checking for network mou
On Thu, Jan 21, 2010 at 11:46 AM, Denis Heidtmann
wrote:
> On Thu, Jan 21, 2010 at 10:19 AM, drew wymore wrote:
>> On Thu, Jan 21, 2010 at 10:09 AM, Denis Heidtmann
>> wrote:
>>> On Thu, Jan 21, 2010 at 6:50 AM, Steve D... wrote:
On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann
wrot
> (BTW, my system has no such command as "network").
>
> -Denis
>
/etc/init.d/networking
Usage: /etc/init.d/networking {start|stop}
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On Thu, Jan 21, 2010 at 11:46 AM, Denis Heidtmann
wrote:
> On Thu, Jan 21, 2010 at 10:19 AM, drew wymore wrote:
>> On Thu, Jan 21, 2010 at 10:09 AM, Denis Heidtmann
>> wrote:
>>> On Thu, Jan 21, 2010 at 6:50 AM, Steve D... wrote:
On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann
wrot
On Thu, Jan 21, 2010 at 10:19 AM, drew wymore wrote:
> On Thu, Jan 21, 2010 at 10:09 AM, Denis Heidtmann
> wrote:
>> On Thu, Jan 21, 2010 at 6:50 AM, Steve D... wrote:
>>> On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann
>>> wrote:
I had previously posted this:
00:0a.0 Ethernet
Denis Heidtmann wrote:
> It occurred to me that since the machine supports wake-on-lan, that as
> long as there is power to the box the network "card" must be active.
> This could explain why a change in state only occurs through a
> power-off cycle. Does this help?
My fav part of the output from
On Thu, Jan 21, 2010 at 10:09 AM, Denis Heidtmann
wrote:
> On Thu, Jan 21, 2010 at 6:50 AM, Steve D... wrote:
>> On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann
>> wrote:
>>>
>>> I had previously posted this:
>>> 00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200]
>>> Etherne
On Thu, Jan 21, 2010 at 6:50 AM, Steve D... wrote:
> On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann
> wrote:
>>
>> I had previously posted this:
>> 00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200]
>> Ethernet (rev a2)
>> Subsystem: ASUSTeK Computer Inc. Device 82f2
On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann
wrote:
>
> I had previously posted this:
> 00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200]
> Ethernet (rev a2)
> Subsystem: ASUSTeK Computer Inc. Device 82f2
> Flags: bus master, 66MHz, fast devsel, latency 0, IR
On Wed, Jan 20, 2010 at 10:38 PM, Denis Heidtmann
wrote:
> On Wed, Jan 20, 2010 at 7:57 PM, Larry Brigman
> wrote:
>
>>
>> If you are seeing the list of negotiation rates drop in failed mode
>> then to be able to
>> check this while the system is up will require the network to be down
>> an
On Wed, Jan 20, 2010 at 7:57 PM, Larry Brigman wrote:
>
> If you are seeing the list of negotiation rates drop in failed mode
> then to be able to
> check this while the system is up will require the network to be down
> and at least the associated
> network driver for the card to be rmmod to
On Wed, Jan 20, 2010 at 7:21 PM, Denis Heidtmann
wrote:
> On Wed, Jan 20, 2010 at 5:36 PM, Mike Connors wrote:
>> drew wymore wrote:
>>> I think route -n is what I was thinking of. So disregard what I wrote.
>>> Ok .. so next thing I'm thinking of is that the PK5000 according to
>>> the docs I pu
On Wed, Jan 20, 2010 at 5:36 PM, Mike Connors wrote:
> drew wymore wrote:
>> I think route -n is what I was thinking of. So disregard what I wrote.
>> Ok .. so next thing I'm thinking of is that the PK5000 according to
>> the docs I pulled up is 10/100BaseT and since you have a Gigabit NIC,
>> I'm
On Wed, Jan 20, 2010 at 4:32 PM, drew wymore wrote:
> On Wed, Jan 20, 2010 at 4:20 PM, Denis Heidtmann
> wrote:
>> On Wed, Jan 20, 2010 at 3:43 PM, jen montserrat
>> wrote:
>>> Have you tried using another patch cable, just to rule out the possibility
>>> of it being the network cable? If this
drew wymore wrote:
> I think route -n is what I was thinking of. So disregard what I wrote.
> Ok .. so next thing I'm thinking of is that the PK5000 according to
> the docs I pulled up is 10/100BaseT and since you have a Gigabit NIC,
> I'm starting to lean towards a negotiation error of some sort o
On Wed, Jan 20, 2010 at 4:40 PM, Denis Heidtmann
wrote:
> On Wed, Jan 20, 2010 at 4:32 PM, drew wymore wrote:
>> On Wed, Jan 20, 2010 at 4:20 PM, Denis Heidtmann
>> wrote:
>>> On Wed, Jan 20, 2010 at 3:43 PM, jen montserrat
>>> wrote:
Have you tried using another patch cable, just to rule
On Wed, Jan 20, 2010 at 4:32 PM, drew wymore wrote:
> On Wed, Jan 20, 2010 at 4:20 PM, Denis Heidtmann
> wrote:
>> On Wed, Jan 20, 2010 at 3:43 PM, jen montserrat
>> wrote:
>>> Have you tried using another patch cable, just to rule out the possibility
>>> of it being the network cable? If this
On Wed, Jan 20, 2010 at 4:20 PM, Denis Heidtmann
wrote:
> On Wed, Jan 20, 2010 at 3:43 PM, jen montserrat
> wrote:
>> Have you tried using another patch cable, just to rule out the possibility
>> of it being the network cable? If this is a wireless interface, please
>> ignore this post
>
> I hav
On Wed, Jan 20, 2010 at 3:43 PM, jen montserrat
wrote:
> Have you tried using another patch cable, just to rule out the possibility
> of it being the network cable? If this is a wireless interface, please
> ignore this post
I have tried two different cables. I intend to try a third when the
fai
Have you tried using another patch cable, just to rule out the possibility
of it being the network cable? If this is a wireless interface, please
ignore this post
On Wed, Jan 20, 2010 at 11:23 PM, Denis Heidtmann wrote:
> On Wed, Jan 20, 2010 at 2:32 PM, Mike Connors wrote:
> > drew wymore wro
On Wed, Jan 20, 2010 at 2:32 PM, Mike Connors wrote:
> drew wymore wrote:
>> Would love to try what you suggest, except I do not understand. Is
>> this something that I can do when the network is in the failed state?
> Okay, so let me see if I got this straight? Networking only fails upon
> bootu
On Wed, Jan 20, 2010 at 10:22 AM, drew wymore wrote:
> I'm not home right now to check. But Google mii-tool. Try it when the
> network barfs
>
Nice idea, but:
sudo mii-tool -v
SIOCGMIIPHY on 'eth0' failed: Operation not supported
no MII interfaces found
According to the man page I think this me
drew wymore wrote:
> Would love to try what you suggest, except I do not understand. Is
> this something that I can do when the network is in the failed state?
Okay, so let me see if I got this straight? Networking only fails upon
bootup and when it doesn't work you can't ping the router and you
I'm not home right now to check. But Google mii-tool. Try it when the
network barfs
On Jan 20, 2010 10:15 AM, "Denis Heidtmann"
wrote:
On Wed, Jan 20, 2010 at 10:02 AM, drew wymore wrote:
> On Wed, Jan 20, 2010 ...
Would love to try what you suggest, except I do not understand. Is
this somethi
On Wed, Jan 20, 2010 at 10:03 AM, Larry Williams
wrote:
> Denis Heidtmann wrote:
>> The only observation I can report is
>> that when the network is up ethtool eth0 has an entry "1000baseT/Full"
>> under "Advertised link modes" that is absent when the network is down.
>>
> Have you tried a differe
On Wed, Jan 20, 2010 at 10:02 AM, drew wymore wrote:
> On Wed, Jan 20, 2010 at 9:54 AM, Denis Heidtmann
> wrote:
>> My network problem continues. Here is as concise a description as I can
>> muster:
>>
>> 1) New PK5000 Quest DSL router cabled to my desktop, my only computer.
>> 2) Typically I p
Denis Heidtmann wrote:
> The only observation I can report is
> that when the network is up ethtool eth0 has an entry "1000baseT/Full"
> under "Advertised link modes" that is absent when the network is down.
>
Have you tried a different computer, or at least a different NIC?
On Wed, Jan 20, 2010 at 9:54 AM, Denis Heidtmann
wrote:
> My network problem continues. Here is as concise a description as I can
> muster:
>
> 1) New PK5000 Quest DSL router cabled to my desktop, my only computer.
> 2) Typically I power both the router and the desktop down and up a few
> times
My network problem continues. Here is as concise a description as I can muster:
1) New PK5000 Quest DSL router cabled to my desktop, my only computer.
2) Typically I power both the router and the desktop down and up a few
times a day.
3) Failure means that pings to the router at 192.168.0.1 go un
On Mon, Apr 20, 2009 at 13:29, John Jason Jordan wrote:
> Network Manager has always been a PITA. I went to wicd because the NM
> GUI could never find any of the available networks. Maybe once in a
> while it would drop down a list. Usually I had to go to the command
> line to scan and then conne
On Mon, 20 Apr 2009 09:42:51 -0700
"chris (fool) mccraw" dijo:
> On Sun, Apr 19, 2009 at 23:52, John Jason Jordan wrote:
>
> > The reason I need the GUI is to be able to find wireless networks when
> > I am away from home, select one, and connect to it. It is far faster to
> > do so from the GU
On Sun, Apr 19, 2009 at 23:52, John Jason Jordan wrote:
> The reason I need the GUI is to be able to find wireless networks when
> I am away from home, select one, and connect to it. It is far faster to
> do so from the GUI (assuming I can get it to work) than from the
> command line. Furthermore
On Sun, 19 Apr 2009 22:29:03 -0700
Larry W dijo:
> John Jason Jordan wrote:
> > On Ubuntu, does anyone know a command to launch Network Manager?
> ...
> > I have lost the GUI launcher, but I can't recreate it until I can
> > figure out what the app is called.
>
> I think you're looking for ne
On Sun, Apr 19, 2009 at 11:52 PM, John Jason Jordan wrote:
> On Sun, 19 Apr 2009 23:17:48 -0700
> Bill Barry dijo:
>
> > On Sun, Apr 19, 2009 at 10:53 PM, John Jason Jordan >wrote:
> >
> > > On Sun, 19 Apr 2009 21:05:01 -0700
> > > Bill Barry dijo:
> > >
> > > > > This is not the first time I h
On Sun, 19 Apr 2009 23:17:48 -0700
Bill Barry dijo:
> On Sun, Apr 19, 2009 at 10:53 PM, John Jason Jordan wrote:
>
> > On Sun, 19 Apr 2009 21:05:01 -0700
> > Bill Barry dijo:
> >
> > > > This is not the first time I have tried to figure out how to launch an
> > > > app from the command line. Ma
On Sun, Apr 19, 2009 at 10:53 PM, John Jason Jordan wrote:
> On Sun, 19 Apr 2009 21:05:01 -0700
> Bill Barry dijo:
>
> > > This is not the first time I have tried to figure out how to launch an
> > > app from the command line. Maybe there is a command I can use to find
> > > the launch term for a
On Sun, 19 Apr 2009 21:05:01 -0700
Bill Barry dijo:
> > This is not the first time I have tried to figure out how to launch an
> > app from the command line. Maybe there is a command I can use to find
> > the launch term for all installed packages? Or hopefully can be used
> > with grep or someth
John Jason Jordan wrote:
> On Ubuntu, does anyone know a command to launch Network Manager?
...
> I have lost the GUI launcher, but I can't recreate it until I can
> figure out what the app is called.
I think you're looking for network-admin, part of the
gnome-network-admin package. Assuming
On Sun, Apr 19, 2009 at 8:56 PM, John Jason Jordan wrote:
> On Ubuntu, does anyone know a command to launch Network Manager?
>
> According to Synaptic the package that is installed is
> "network-manager," but that gives a "not found" error message at the
> command line.
>
> I have lost the GUI lau
On Ubuntu, does anyone know a command to launch Network Manager?
According to Synaptic the package that is installed is
"network-manager," but that gives a "not found" error message at the
command line.
I have lost the GUI launcher, but I can't recreate it until I can
figure out what the app is c
54 matches
Mail list logo
