Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ifconfig hangs system?
804 views
Skip to first unread message
Unknown
Jun 13, 2014, 12:19:42 AM6/13/14
to
There's a lot reported on google: linux+ifconfig+hangs
The 4 extracts listed below seem to point to eth0 <-> USB: interation?
===
Its got to be a USB device, OP said he was able to see some
networks but then it wouldn't work anymore.
===
Default Re: Ifconfig up Hang up
The problem is with the drivers for the WUSB600N v1, not that
it's a VMWare install. I have the same issue when booting into a
live CD or my persistent USB install.
Like me, you're going to have to wait for someone to come up with
some proper drivers for the WUSB600N v1
===
I believe that there are problems with the USB drivers that may
manifest themselves differently depending on what combination of
peripherals are plugged into the USB ports. This also may affect the
ethernet, as it's tied in with the USB somehow.
===
Reading some of the developers comments on Github doesn't exactly
inspire me with confidence, the finger seems to point at the (my
paraphrase) unholy botch that is the USB/Ethernet hardware system
============= end of google extracts ================
Previously my X86:MotherBoard:Slackware13 could connect eth0 to the rPi.
Now `ifconfig -a` doesn't return, and
`top` shows kswapd0 going up to 90% CPU, and now I notice a chain of bash
being launched.
Also with eth0 cable unplugged, it hangs, so it's not the rPi.
Besides I can eth0 between: rPi-1 <-> rPi-2; nicely.
Booting to a 9-months-older-than-sla13-slak-derived-version shows:---
-> ifconfig -a ==
eth0 Link encap:Ethernet HWaddr 00:01:2e:25:0b:1c
inet6 addr: fe80::201:2eff:fe25:b1c/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:547 errors:0 dropped:0 overruns:0 frame:0
TX packets:1484 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:187074 (182.6 KiB) TX bytes:457272 (446.5 KiB)
Interrupt:20 Base address:0x6000
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:1380 errors:0 dropped:0 overruns:0 frame:0
TX packets:1380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:105584 (103.1 KiB) TX bytes:105584 (103.1 KiB)
-> nc -l 1234 == waits & eth0:LEDs=off
=> Other e-term -> nc 127.0.0.1 1234 < Go15 ==
(UNKNOWN) [127.0.0.1] 1234 (?) : Connection refused
? eth0:LEDs seems to toggle by a <100sec-crond> ?
=====================
=>Now re-try: boot slak13, with USB header removed & ifconfig -a
== still hangs: `top` = kswapd0 + launches bash-chain!!
...
WDYS ?
The 4 extracts listed below seem to point to eth0 <-> USB: interation?
===
Its got to be a USB device, OP said he was able to see some
networks but then it wouldn't work anymore.
===
Default Re: Ifconfig up Hang up
The problem is with the drivers for the WUSB600N v1, not that
it's a VMWare install. I have the same issue when booting into a
live CD or my persistent USB install.
Like me, you're going to have to wait for someone to come up with
some proper drivers for the WUSB600N v1
===
I believe that there are problems with the USB drivers that may
manifest themselves differently depending on what combination of
peripherals are plugged into the USB ports. This also may affect the
ethernet, as it's tied in with the USB somehow.
===
Reading some of the developers comments on Github doesn't exactly
inspire me with confidence, the finger seems to point at the (my
paraphrase) unholy botch that is the USB/Ethernet hardware system
============= end of google extracts ================
Previously my X86:MotherBoard:Slackware13 could connect eth0 to the rPi.
Now `ifconfig -a` doesn't return, and
`top` shows kswapd0 going up to 90% CPU, and now I notice a chain of bash
being launched.
Also with eth0 cable unplugged, it hangs, so it's not the rPi.
Besides I can eth0 between: rPi-1 <-> rPi-2; nicely.
Booting to a 9-months-older-than-sla13-slak-derived-version shows:---
-> ifconfig -a ==
eth0 Link encap:Ethernet HWaddr 00:01:2e:25:0b:1c
inet6 addr: fe80::201:2eff:fe25:b1c/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:547 errors:0 dropped:0 overruns:0 frame:0
TX packets:1484 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:187074 (182.6 KiB) TX bytes:457272 (446.5 KiB)
Interrupt:20 Base address:0x6000
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:1380 errors:0 dropped:0 overruns:0 frame:0
TX packets:1380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:105584 (103.1 KiB) TX bytes:105584 (103.1 KiB)
-> nc -l 1234 == waits & eth0:LEDs=off
=> Other e-term -> nc 127.0.0.1 1234 < Go15 ==
(UNKNOWN) [127.0.0.1] 1234 (?) : Connection refused
? eth0:LEDs seems to toggle by a <100sec-crond> ?
=====================
=>Now re-try: boot slak13, with USB header removed & ifconfig -a
== still hangs: `top` = kswapd0 + launches bash-chain!!
...
WDYS ?
Unknown
Jun 14, 2014, 12:44:56 AM6/14/14
to
On Fri, 13 Jun 2014 04:19:42 +0000, Unknown wrote:
Sorry !! I made a recursive call.
My script that called ifconfig + ping should have been called IFconfig;
not ifconfig. Apparently I wrote it some time ago and forgot about it.
Sorry !! I made a recursive call.
My script that called ifconfig + ping should have been called IFconfig;
not ifconfig. Apparently I wrote it some time ago and forgot about it.
Unknown
Jun 14, 2014, 12:44:59 AM6/14/14
to
On Fri, 13 Jun 2014 04:19:42 +0000, Unknown wrote:
Sorry !! I made a recursive call.
My script that called ifconfig + ping should have been called IFconfig;
not ifconfig. Apparently I wrote it some time ago and forgot about it.
Sorry !! I made a recursive call.
My script that called ifconfig + ping should have been called IFconfig;
not ifconfig. Apparently I wrote it some time ago and forgot about it.
Chick Tower
Jun 16, 2014, 11:50:49 PM6/16/14
to
On 2014-06-14, Unknown wrote:
> Sorry !! I made a recursive call.
> My script that called ifconfig + ping should have been called IFconfig;
> not ifconfig. Apparently I wrote it some time ago and forgot about it.
So does this mean everything works fine now, or do you still have this
> Sorry !! I made a recursive call.
> My script that called ifconfig + ping should have been called IFconfig;
> not ifconfig. Apparently I wrote it some time ago and forgot about it.
problem? I, myself, can't help you with it, but it's not clear whether
your problem is solved or not.
--
Chick Tower
For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
Keith Keller
Jun 17, 2014, 2:56:57 AM6/17/14
to
On 2014-06-17, Chick Tower <c.t...@deadspam.com> wrote:
> On 2014-06-14, Unknown wrote:
>> Sorry !! I made a recursive call.
>> My script that called ifconfig + ping should have been called IFconfig;
>> not ifconfig. Apparently I wrote it some time ago and forgot about it.
>
> So does this mean everything works fine now, or do you still have this
> problem? I, myself, can't help you with it, but it's not clear whether
> your problem is solved or not.
''Chris Glur's'' problem is PEBKAC. This problem may never be solved.
> On 2014-06-14, Unknown wrote:
>> Sorry !! I made a recursive call.
>> My script that called ifconfig + ping should have been called IFconfig;
>> not ifconfig. Apparently I wrote it some time ago and forgot about it.
>
> So does this mean everything works fine now, or do you still have this
> problem? I, myself, can't help you with it, but it's not clear whether
> your problem is solved or not.
--keith
--
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
0 new messages