• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2
Author Topic: guruplug - perhaps bricked - now eth0 not starting during boot  (Read 3965 times)
lopgok
Newbie
*

Karma: 0
Posts: 16


View Profile
« on: April 07, 2010, 05:43:22 PM »

I got a guruplug. I was able to ssh into it.

I created a user.
I ran apt-get update
I ran apt-get dist-upgrade
I ran apt-get autoremove
I set the date.
I rebooted with the 'reboot' command.

Though my router thinks the ip address of the guruplug has not changed,
I cannot ping it, nor can I connect via ssh.

I pulled the power cord, and plugged it in again, but no success.
I don't have a mini-usb connector to attach to a serial port.

The blue light on the front blinks quickly,k and the green light is on and not blinking.

Any ideas how I can communicate with the guruplug?

thanks
« Last Edit: April 08, 2010, 04:52:05 PM by lopgok » Logged

SgtPepper
Newbie
*

Karma: 2
Posts: 19


View Profile
« Reply #1 on: April 07, 2010, 07:05:25 PM »

I got a guruplug.
I didn't think they were shipping GuruPlugs until the end of the month.  When did you order yours?

As to your question, I think your best bet will be to find a usb cable and use the serial port.
Logged

lopgok
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #2 on: April 07, 2010, 07:15:15 PM »

There are 2 standard shaped USB ports on the guruplug.
I am not sure if either of them is a console port.
As I said, there is no miniusb port.

I don't think I have any male-male cables (or A-A or whatever they are called).
Logged

SgtPepper
Newbie
*

Karma: 2
Posts: 19


View Profile
« Reply #3 on: April 07, 2010, 07:31:03 PM »

There are 2 standard shaped USB ports on the guruplug.
I am not sure if either of them is a console port.
As I said, there is no miniusb port.

I don't think I have any male-male cables (or A-A or whatever they are called).
Sorry, I thought you meant you didn't have a min-usb cable.  The pictures on Globalscale's site show a mini-usb port for GuruPlug Server, GuruPlug Server Plus, and GuruPlug Display.  Did you get it from somewhere else?

Without a serial port, I don't know what else to tell you.
Logged

lopgok
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #4 on: April 07, 2010, 07:45:57 PM »

There isn't a mini-usb port on the box. I did see a really small reset button (that was not labelled).
There are two white connectors on one side, presumably for the jtag board, and a black connector on the
other side, for the usnap, I believe.

Also 2 standard usb ports, and 1 ethernet port.
I do have the jtag board, so I could wire up some kind of rs232 from that, thought I don't know the pinouts...
Looks like the uart board has a mini-usb. I have wired it up, and I am now trying to talk to the guruplug...
« Last Edit: April 07, 2010, 08:08:52 PM by lopgok » Logged

SgtPepper
Newbie
*

Karma: 2
Posts: 19


View Profile
« Reply #5 on: April 07, 2010, 08:05:10 PM »

There isn't a mini-usb port on the box. I did see a really small reset button (that was not labelled).
There are two white connectors on one side, presumably for the jtag board, and a black connector on the
other side, for the usnap, I believe.

Also 2 standard usb ports, and 1 ethernet port.
I do have the jtag board, so I could wire up some kind of rs232 from that, thought I don't know the pinouts...
There should be a mini-usb plug on the JTAG board.  Try that.
Logged

lopgok
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #6 on: April 07, 2010, 08:27:51 PM »

I hooked it up to a linux box.
After running modprobe usbserial, dmesg says:

usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: New USB device found, idVendor=9e88, idProduct=9e8f
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: SheevaPlug JTAGKey FT2232D B
usb 1-1: Manufacturer: FTDI
usb 1-1: SerialNumber: FTSMF2G2
usb 1-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core

I don't seem to have a /dev/ttyUSB anything to connect to.
My linux box is running mandriva 2009.1

Any thoughts?
Logged

fragfutter
Sr. Member
****

Karma: 12
Posts: 280


View Profile
« Reply #7 on: April 08, 2010, 12:06:22 AM »

the guruplug is shipping? must resist to check mail every five minutes, must resist....


So dmesg finds an usb serial device (great!) but does not create a ttyUSB? I would guess you are missing an udev rule that handles this. Check this http://bifrost.projects.linpro.no/wiki/SheevaPlugConfig
Logged

NewIT
Jr. Member
**

Karma: 10
Posts: 88



View Profile WWW
« Reply #8 on: April 08, 2010, 01:15:31 AM »

I got a guruplug.


Where did you aquire your GuruPlug?
Was it one of the ones Marvell gave away at the CES?
Logged

lopgok
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #9 on: April 08, 2010, 05:04:45 AM »

I got the plug straight from marvell.
Logged

MarkF
Full Member
***

Karma: 7
Posts: 144


View Profile
« Reply #10 on: April 08, 2010, 08:24:57 AM »

The GuruPlugs on GlobalScale's site require a separate board/box to connect to the console (tty0) and JTAG interface.  I don't know about yours.

http://www.globalscaletechnologies.com/p-28-guruplug-jtag.aspx
Logged

Mark

Magus
Newbie
*

Karma: 1
Posts: 25


View Profile
« Reply #11 on: April 08, 2010, 09:55:36 AM »

I got one given to me by Marvell at Linux show. Having real problems- no documentation, no disk.  Is there anywhere I can get info. I called Globalscale but they advise me to post here.
Logged

lopgok
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #12 on: April 08, 2010, 04:50:46 PM »

I was able to log in with the serial console.
The network was not being started at boot.
I was able to start the network with

ethconfig eth0 up

I looked in the /etc/network/interfaces file and there was no 'eth0' in it.
I changed the line that said
auto lo
to
auto lo eth0

When I ran /etc/init.d/networking restart
I got the following:
Reconfiguring network interfaces...Ignoring unknown interface eth0=eth0.
done.

I tried putting 'auto eth0' on a line by itself, but that didn't help.

I think when I ran the updates, that somehow eth0 starting at boot time got removed from
somewhere in the network startup code. I have no idea why I am getting the error about
'Ignoring unknown interface eth0=eth0'.

Any ideas would be greatly appreciated.
Logged

pancho
Newbie
*

Karma: 1
Posts: 20


View Profile
« Reply #13 on: April 08, 2010, 10:32:20 PM »

Hi there.

Try posting here the output of this command
$ dmesg

Maybe the kernel is not recognizing the ethernet card, or udev is renaming it
to another name (eth1?).

Cheers,
Logged

lopgok
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #14 on: April 09, 2010, 04:25:28 AM »


Try posting here the output of this command
$ dmesg

Maybe the kernel is not recognizing the ethernet card, or udev is renaming it
to another name (eth1?).


When I do start the network, it is recognized as eth0.
Looking at ifconfig, it seems to have a ipv6 address, not a ipv4 address:
eth0      Link encap:Ethernet  HWaddr 00:50:43:01:42:39 
          inet6 addr: fe80::250:43ff:fe01:4239/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:91 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5824 (5.6 KiB)  TX bytes:468 (468.0 B)
          Interrupt:11


Here is dmesg output:
Linux version 2.6.32-00007-g56678ec (root@msi-linux-build.marvell.com) (gcc vers
ion 4.1.2 20070925 (Red Hat 4.1.2-33.fa1)) #1 PREEMPT Thu Dec 24 03:15:48 PST 20
09
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell Plug2 Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c05881c8, node_mem_map c065f000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=
ubifs
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513024KB available (5144K code, 1034K data, 148K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
initial MPP regs: 01111111 11113311 33331111 33003333 00002233 00000222 00000000
  final MPP regs: 01111111 11113311 33331111 33003333 00002233 00000222 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
        (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
        (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4010, nTxLock = 32080
msgmni has been set to 1002
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bi
t)
Scanning device for bad blocks
Bad eraseblock 244 at 0x000001e80000
Bad eraseblock 245 at 0x000001ea0000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            507 MiB
UBI: number of good PEBs:        4054
UBI: number of bad PEBs:         2
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4054
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 447
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:42:39
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug2:red:health
Registered led device: plug2:green:health
Registered led device: plug2:red:wmode
Registered led device: plug2:green:wmode
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mmc0: new high speed SDIO card at address 0001
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Gating clock of unused units
before: 0x00dfc3fd
 after: 0x00c701d9
rtc-mv rtc-mv: setting system clock to 2009-08-08 19:46:43 UTC (1249760803)
usb 1-1: new high speed USB device using orion-ehci and address 2
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   515966976 bytes (503874 KiB, 492 MiB, 3999 LEBs)
UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 148K
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas_sdio mmc0:0001:1: firmware: requesting sd8688_helper.bin
libertas: can't load helper firmware
libertas: failed to load helper firmware
libertas_sdio: probe of mmc0:0001:1 failed with error -2
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
btmrvl_sdio mmc0:0001:2: firmware: requesting sd8688_helper.bin
btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2
btmrvl_sdio_download_fw: Failed to download helper!
btmrvl_sdio_probe: Downloading firmware failed!
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: link up, 100 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1
uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin
uap_sdio mmc0:0001:1: firmware: requesting mrvl/sd8688_ap.bin
UAP FW is active
ADDRCONF(NETDEV_UP): uap0: link is not ready
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (8022 buckets, 32088 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
Bridge firewalling registered
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
eth0: no IPv6 routers present
Logged

Pages: [1] 2
Print
Jump to: