New IT forum Follow us on Twitter
04 February 2012, 04:17:43 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: EFIKA MX now in stock!
 
   Home   SHOP Help Search Login Register  
Pages: [1]
  Print  
Author Topic: [SOLVED] Guruplug not booting any more  (Read 1843 times)
ciridian
Newbie
*
Posts: 5


« on: 15 June 2010, 02:04:00 pm »

Hi all!
My guruplug won't boot any more... I have used the init_setup.sh attachment from this post: http://www.newit.co.uk/forum/index.php?topic=297.0. Also, I have done some updates and changed the root password. Furthermore I have set the ip address to static with ifconfig.
Only the top LED is burning green, all other LEDs are turned off. I do not have a JTAG board.
Is there anyone who can help me with a suggestion?
Thanks!
« Last Edit: 15 June 2010, 06:29:49 pm by ciridian » Logged
varkey
Newbie
*
Posts: 15


« Reply #1 on: 15 June 2010, 02:10:07 pm »

The init script activates the LEDs. So if you commented that out only the main LED will glow.

The server doesnt respond to ping also?
Logged
ciridian
Newbie
*
Posts: 5


« Reply #2 on: 15 June 2010, 02:38:08 pm »

Thanks for your reply. I believe the LEDs should still be turned on, here is the init_setup.sh:
Code:
#!/bin/sh
# This is called from /etc/rc.local to perform the initial setup.
# We always bootup in AP mode. Delete any stale files
rm -f /etc/wlanclient.mode
SSID=Plug2-uAP-`ifconfig eth0 | awk -F ":" '/HWaddr/ {print $6$7}'`
#insmod /root/uap8xxx.ko
#ifconfig uap0 192.168.1.1 up
/usr/bin/uaputl sys_cfg_ssid $SSID
/usr/bin/uaputl bss_start
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
/etc/init.d/udhcpd start
/etc/init.d/dnsmasq start
iptables -A INPUT -i uap0 -p tcp -m tcp --dport 80 -j ACCEPT
# Re-enable bluetooth. In the earlier case, it didn't find the firmware.
#rmmod libertas_sdio libertas btmrvl_sdio btmrvl bluetooth 2>/dev/null
rmmod btmrvl_sdio btmrvl
/etc/init.d/bluetooth start
#modprobe btmrvl_sdio
#hciconfig hci0 up
#hciconfig hci0 piscan
#/usr/bin/mute-agent &
# Set leds
echo 1 > `eval ls /sys/class/leds/*plug*\:green\:health/brightness`
echo 1 > `eval ls /sys/class/leds/*plug*\:green\:wmode/brightness`
I tried pinging the previous (static) address, but that times out. I also can't find anything in my dhcp table in the router.
Do you have any other suggestions? Thanks!
Logged
fragfutter
Newbie
*
Posts: 24


« Reply #3 on: 15 June 2010, 03:21:00 pm »

if you reconfigured /etc/network/interfaces, did you also disable ifplugd?

You might have moved your plug to a different subnet?

Directly connect the plug to your computer, start tcpdump on your interface and boot the plug. Then see what is coming through. But i would start to look for a serial console. It should be possible to solder something from an USB-ftd serial converter and conenct it to three of the four pins of the serial header.
Logged
ciridian
Newbie
*
Posts: 5


« Reply #4 on: 15 June 2010, 04:14:01 pm »

No, I did not disable ifplugd, I wasn't even aware of any such thing... Tongue
The guruplug was just connected with the ethernet cable to my router the whole time, wifi mode (before I tried to turn it off) was client.
How exactly do I directly connect it to my computer? With the ethernet cable?  Huh
Sorry, I'm not really used to these kind of machines, so I don't really know the debugging procedures.
I did try to connect it via ethernet, this is the tcpdump:
Code:
sudo tcpdump -vv
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
18:10:12.943994 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) :: > ff02::1:ff01:5991: [icmp6 sum ok] ICMP6, neighbor solicitation, length 24, who has fe80::250:43ff:fe01:5991
18:10:13.943866 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::250:43ff:fe01:5991 > ip6-allrouters: [icmp6 sum ok] ICMP6, router solicitation, length 16
  source link-address option (1), length 8 (1): 00:50:43:01:59:91
    0x0000:  0050 4301 5991
18:10:15.593614 IP6 (hlim 1, next-header Options (0) payload length: 36) fe80::250:43ff:fe01:5991 > ff02::16: HBH (rtalert: 0x0000) (padn)[icmp6 sum ok] ICMP6, multicast listener report v2, length 28, 1 group record(s) [gaddr ff02::1:ff01:5991 to_ex { }]
18:10:15.861713 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:43:01:59:91 (oui Unknown), length 300, xid 0xdb63cb50, Flags [none] (0x0000)
  Client-Ethernet-Address 00:50:43:01:59:91 (oui Unknown) [|bootp]
18:10:17.943260 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::250:43ff:fe01:5991 > ip6-allrouters: [icmp6 sum ok] ICMP6, router solicitation, length 16
  source link-address option (1), length 8 (1): 00:50:43:01:59:91
    0x0000:  0050 4301 5991
18:10:21.861785 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:43:01:59:91 (oui Unknown), length 300, xid 0xdb63cb50, secs 6, Flags [none] (0x0000)
  Client-Ethernet-Address 00:50:43:01:59:91 (oui Unknown) [|bootp]
18:10:21.942648 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::250:43ff:fe01:5991 > ip6-allrouters: [icmp6 sum ok] ICMP6, router solicitation, length 16
  source link-address option (1), length 8 (1): 00:50:43:01:59:91
    0x0000:  0050 4301 5991
18:10:36.868899 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:43:01:59:91 (oui Unknown), length 300, xid 0x932f8a4f, Flags [none] (0x0000)
  Client-Ethernet-Address 00:50:43:01:59:91 (oui Unknown) [|bootp]
18:10:41.858161 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:43:01:59:91 (oui Unknown), length 300, xid 0x932f8a4f, secs 5, Flags [none] (0x0000)
  Client-Ethernet-Address 00:50:43:01:59:91 (oui Unknown) [|bootp]
18:10:51.854183 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:43:01:59:91 (oui Unknown), length 300, xid 0x932f8a4f, secs 15, Flags [none] (0x0000)
  Client-Ethernet-Address 00:50:43:01:59:91 (oui Unknown) [|bootp]
^C
10 packets captured
10 packets received by filter
0 packets dropped by kernel
I left it running for +- a minute, the message was repeated. On my pc I am using Ubuntu Maverick Meerkat by the way.
I don't really know how to interpret this dump, it is doing some kind of dhcp request to my pc? Should I set something up so that it can get to the internet via my pc?
Thanks a lot for your help, this is all really new to me!
Logged
fragfutter
Newbie
*
Posts: 24


« Reply #5 on: 15 June 2010, 04:46:47 pm »

yes directly via ethernet cable. The goal was to minimize the traffic you see on the interface.

Here is what will make you happy: BOOTP/DHCP, Request from 00:50:43:01:59:91

If you look at the underside of the plug you will see, that this is the mac address of your plug. It is requesting an IP Address with dhcp. Do you have an dhcp server in
your network (the router most likely). If you connect your plug to the network it will request an address.

If you configured your "static" address with ifconfig it won't survive a reboot. If you edit /etc/network/interfaces you need to disable ifplugd.

You really should look to get a serial console running. Configuring the only connection you have to the plug (ethernet) without knowing what your are doing is prone for disaster.


Logged
ciridian
Newbie
*
Posts: 5


« Reply #6 on: 15 June 2010, 06:29:19 pm »

Thank you very much! It is running like a charm again, although the other LEDs are still switched off. (the one on the left should be green, right?)
What kind of serial console do I need? The JTAG thing that you can buy from New It or will any serial console do? The one that is offered by New It is a bit above my budget, I live in Holland so it needs to be shipped here too. Anyway, thanks for your help and I will look into ifplugd.
Logged
fragfutter
Newbie
*
Posts: 24


« Reply #7 on: 15 June 2010, 08:45:48 pm »

In Theory, if you can handle a soldering iron, any ftdi based serial cable could be used. You need to find a connector for the plug and solder it. But i can't help with that. i have a jtag board, but my plug is basicly unusable (heat, gigabit...)
Logged
varkey
Newbie
*
Posts: 15


« Reply #8 on: 16 June 2010, 04:41:34 am »

Maybe this can be used to get serial access?

http://cgi.ebay.com/USB-RS232-UART-TTL-RS485-Module-FTDI-FT232BM-BL-Chip-/320508487283?cmd=ViewItem&pt=LH_DefaultDomain_0&hash=item4a9fcb6673

Logged
apemberton
Full Member
***
Posts: 100


« Reply #9 on: 16 June 2010, 10:05:32 am »

My tuppence worth....  Smiley

I while ago I needed serial console (not JTAG) access to a non-Sheeva ARM9 device (OK a Buffalo Linkstation with an Orion proc) at 3.3Volts. It was recommended to use a Nokia DKU-5 USB to serial adaptor for their older phones. The web page is at http://buffalo.nas-central.org/wiki/Use_a_Nokia_Serial_Cable_on_an_ARM9_Linkstation. I had difficulty sourcing this cable at the normal mobile phone stores as phones have moved on from serial uart type connections. I had no problems obtaining a cable from a market stall selling Mobile Phones (the type that sells all sorts of tatty mobile phone bits). All I had to do was to cut off the Nokia connector and solder on the correct connector. A disk was supplied but it was not suitable for my 64bit Vista terminal!

   
Logged

Tony Pemberton
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!