No network after new install: PogoPlug Pro

[Islander]

Connected to new PogoPlug Pro using SSH. Followed installation guide--all went well. At step 12 (/sbin/reboot) SSH connection was broken as expected. But the unit did not make a DHCP request. No SSH and no ping at the prior address.

I think its booted--green light blinks rapidly for about 15 seconds, then goes out and then comes on solid green.

Edited /etc/rc.conf using my linux box--set it for static IP address, set default gateway to my system, etc. All looks okay there.

Install dialogue reported board: PPRO1.

Any ideas how I can bring it up on the network so I can SSH into it?

Tnx for help - Islander

[WarheadsSE]

Odd, because if it's led has switched to solid, then you're running, but the network hasn't come up.

Try doubling the 'network' entry in the DAEMONS= line of rc.conf. This seems to help from what I have heard from others experiencing something similar.

[Islander]

Doubling the "network" entry on the MODULES line didn't help.

Changed rc.conf back to dhcp, as original file.

I measured the time the led was flashing before going solid: 55 seconds.

Increased the UDEV_TIMEOUT setting to 120 seconds (UDEV_TIMEOUT=120), from default 30 in rc.conf.

The led now flashes for 147 seconds before going solid.

Does this mean the udev processing isn't happening so its not finding the network? The installation guide mentions a
patched udev version. Can this be added to the memory stick on my other system? I can't follow step 14 of the guide
because I cannot log in to the plug.

Tnx for the help.

[WarheadsSE]

Not the MODULES, the DAEMONS

But all the same udev is a pain, and a new rootfs needs to be generated. In the past week, I have moved, lost power for 4 days, and had a very busy work schedule so this hasn't happened yet. I'd set the udev timeout back, update the DAEMONS line, and try again.

[Islander]

Actually, it was in DEAMONS all along, not MODULES--my mistake.

Don't worry, this can wait. Meantime, I'll try to hook up a console interface to it.

Tnx for the help!

[WarheadsSE]

I'll get you straightened away one way or another in the end

Heck, I de-bricked one fella week ago.

[WarheadsSE]

I now have a console connected to this PogoPlug Pro. It boots into ARCH Linux and I can log on as root. There is no network, as before. Below is the latter part of the boot dialogue, showing "Starting Network [FAIL}"

What would you suggest to proceed with getting the network functioning, now that I can interact with the system via the console?

Thanks - Islander

Bootup console output follows:
$this->bbcode_second_pass_code('', '
--------------------------------------------------------------------
> Arch Linux ARM

> http://www.archlinuxarm.org

------------------------------
:: Mounting Root Read-Only  [BUSY]  [DONE]
bootlogd: cannot deduce real console device
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
:: Starting UDev Daemon  [BUSY]  [DONE]
:: Triggering UDev uevents  [BUSY]  [DONE]
:: Loading Modules  [BUSY]  [DONE]
:: Waiting for UDev uevents to be processed  [BUSY]  [DONE]
:: Bringing up loopback interface  [BUSY]  [DONE]
:: Checking Filesystems  [BUSY]  [DONE]
:: Mounting Local Filesystems  [BUSY]  [DONE]
 [DONE]
:: Activating Swap  [BUSY]  [DONE]
:: Configuring Time Zone  [BUSY]  [DONE]
:: Removing Leftover Files  [BUSY]  [DONE]
:: Setting Hostname: alarm  [BUSY]  [DONE]
:: Setting Locale: en_US.UTF-8  [BUSY]  [DONE]
:: Setting Consoles to UTF-8 mode  [BUSY]  [DONE]
:: Loading Keyboard Map: us  [BUSY]  [DONE]

INIT: Entering runlevel: 3

:: Setting MAC address  [BUSY] AMBER
GREEN
 [DONE]
:: Starting Syslog-NG  [BUSY]  [DONE]
:: Starting Network  [BUSY]  [FAIL]
:: Starting Network  [BUSY]  [FAIL]
:: Mounting Network Filesystems  [BUSY]  [DONE]
:: Starting crond daemon  [BUSY]  [DONE]
:: Starting Secure Shell Daemon  [BUSY]  [DONE]
:: Starting OpenNTPD  [BUSY]  [DONE]
/bin/cat: /run/bootlogd.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
/bin/rm: cannot remove `/run/bootlogd.pid': No such file or directory


Arch Linux 2.6.31.6_SMP_820 (alarm) (ttyS0)

alarm login: root
Password:
Last login: Wed Dec 31 18:02:25 CST 1969 on ttyS0
[root@alarm ~]#
--------------------------------------------------------------------
')

[coupondeal]

I have a problem that is similar to the original poster's: No network
(the LED blinks then goes solid)

But my problem is even more strange: DHCP works OK, but static IP fails

[WarheadsSE]

Hmm.. double fail on the network?

Check /etc/rc.d/set-oxnas-mac for this to be correct.
`modprobe oxnas-led`