• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / General Linux questions / Re: Network unreachable on: November 14, 2010, 07:04:28 AM
 Shocked

It works!  Grin

Nothing more to do for having automatic DHCP at reboot. I correctly get the connection with above modification of /etc/network/interfaces file.  Smiley

Problem resolved!
2  Linux Stuff / General Linux questions / Re: Network unreachable on: November 13, 2010, 07:10:47 PM
After having modified /etc/network/interfaces manually with:
Code:
auto eth0
iface eth0 inet dhcp
and restarted network using
Code:
/etc.init.d/networking restart
, I got a connection. But how make this automatically working at reboot?
3  Linux Stuff / General Linux questions / [Resolved] Network unreachable on: November 13, 2010, 06:54:59 PM
Hi all,

I just get access to my guru plug using JTAG module because I couldn't log into plug via SSH, related to network which did not work after an update of packages.

It seems there was something bad during update or reboot because now, network does not work. How would I make the GuruPLug access to network? I have correctly connected ethernet, but no way to reach Internet (ie. no ping on google). For information, here is some commands results:

Code:
01:55:03 root@sheevaplug-debian:boot# /etc/init.d/networking restart
Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces ... (warning).
Reconfiguring network interfaces...done.

Code:
01:55:19 root@sheevaplug-debian:boot# more /etc/network/interfaces
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback

For information, dhclient command returns nothing.

Code:
02:07:30 root@sheevaplug-debian:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:43:01:9b:97 
          inet6 addr: fe80::250:43ff:fe01:9b97/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:67 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10874 (10.6 KiB)  TX bytes:892 (892.0 B)
          Interrupt:11

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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:480 (480.0 B)  TX bytes:480 (480.0 B)

Code:
02:20:02 root@sheevaplug-debian:~# cat /etc/udhcpd.conf
start 192.168.1.100
end 192.168.1.200
interface uap0
opt      lease  86400
opt     router  192.168.1.1
opt     subnet  255.255.255.0
opt     dns     192.168.1.1
opt     domain     localdomain
max_leases     101
lease_file     /var/lib/udhcpd.leases
auto_time       5
Here is log when I reboot GuruPlug, network still does work:
Code:
01:58:06 root@sheevaplug-debian:boot# reboot -i

The system is going down for reboot NOW!ebian (ttyS0) (Sun Nov 14 01:58:41 20
INIT: Sending processes the TERM signal
01:Using makefile-style concurrent boot in runlevel 6.
Shutting down ALSA...done (none loaded).
Stopping bluetooth: bluetoothd.
Network Interface Plugging Daemon...stop eth0...done.
Stopping MTA: exim4_listener.
ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken ... failed!
Stopping internet superserver: inetd.
udhcpd: Disabled. Edit /etc/default/udhcpd to enable it.
Stopping web server: apache2apache2: apr_sockaddr_info_get() failed for sheevaplug-debian
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
 ... waiting .
Stopping MySQL database server: mysqld.
Stopping Samba daemons: nmbd smbd.
Asking all remaining processes to terminate...done.
Currently running processes (pstree):
init-+-mount.ntfs
     |-rc---startpar---sendsigs---pstree
     `-rsyslogd---3*[{rsyslogd}]
Killing all remaining processes...failed.
Stopping enhanced syslogd: rsyslogd.
Deconfiguring network interfaces...done.
Cleaning up ifupdown....
Saving the system clock.
Deactivating swap...done.
Will now restart.
Restarting system.


U-Boot 2009.11-rc1-00602-g8e6db3d (Dec 24 2009 - 03:11:17)
Marvell-Plug2

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1121 Initialized on egiga0
Hit any key to stop autoboot:  0
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.32-00007-g56678ec
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2789748 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, b.
Linux version 2.6.32-00007-g56678ec (root@msi-linux-build.marvell.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33.fa1)) #1 PREEMPT Thu Dec 24 03:15:48 PST 2009
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
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.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
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-bit)
Scanning device for bad blocks
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:        4056
UBI: number of bad PEBs:         0
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: 4056
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 6/1
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:9b:97
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
rtc-mv rtc-mv: setting system clock to 2010-11-14 01:59:13 UTC (1289699953)
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:   516225024 bytes (504126 KiB, 492 MiB, 4001 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
INIT: version 2.88 booting
usb 1-1.2: new high speed USB device using orion-ehci and address 3
Using makefile-style concurrent boot in runlevel S.
usb 1-1.2: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
Starting the hotplug events dispatcher: udevdudevd[598]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/3

udevd[598]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/z60_usbmount.rules:4

.
Synthesizing the initial hotplug events...udevd[599]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rul3

udevd[599]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/z60_usbmount.rules:4

done.
Waiting for /dev to be fully populated...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!
done.
Activating swap...done.
Cleaning up ifupdown....
Setting up networking....
Loading kernel modules...done.
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
done.
Mounting local filesystems...done.
Activating swapfile swap...done.
Cleaning up temporary files....
Configuring network interfaces...done.
Cleaning up temporary files....
Setting up ALSA...done (none loaded).
Setting console screen modes and fonts.
cannot (un)set powersave mode
Setting kernel variables ...done.
INIT: Entering runlevel: 2took 4
Using makefile-style concurrent boot in runlevel 2.
scsi 0:0:0:0: Direct-Access     ST316021 2A                    PQ: 0 ANSI: 0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2 < sda5 >
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI disk
Network Interface Plugging Daemon...start eth0...done.
Starting enhanced syslogd: rsyslogd.
Starting Samba daemons: nmbd smbdNET: 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
Starting web server: apache2apache2: apr_sockaddr_info_get() failed for sheevaplug-debian
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting DNS forwarder and DHCP server: dnsmasq.
Starting bluetooth: bluetoothdBluetooth: 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
Bridge firewalling registered
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Starting Hardware abstraction layer: hald.
Starting MySQL database server: mysqldStarting internet superserver: inetd.
 .udhcpd: Disabled. Edit /etc/default/udhcpd to enable it.
Starting OpenBSD Secure Shell server: sshd.
.
Checking for corrupt, not cleanly closed and upgrade needing tables..
Starting MTA: exim4.
ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken ... failed!
mkdir: cannot create directory `/var/cache/apt': File exists
startpar: service(s) returned failure: rc.local ... failed!
Running scripts in rc2.d/ took 13 seconds.

Debian GNU/Linux squeeze/sid sheevaplug-debian ttyS0

sheevaplug-debian login:

Any help would be greatly appreciated.


ps : I've noticed that /boot floder is empty. Is it normal?
4  General Category / General Discussion / Re: Newbie question about getting started on: October 11, 2010, 01:32:34 PM
Hi.

Indeed, I've had to use a WiFi card to access to my GuruPlug.

Now the problem I have is that I deactivate wifi from guruplug, for I can connect via SSH and don't have more waves at home. But after having updated the guru plug, I can't connect anymore via SSH.

I get "no route to host" message. Do I have another alternative than shiping a JTAG module?

If one need some info, lets me know command outputs you need. Wink

Thanks for help.
5  General Category / General Discussion / Re: Newbie question about getting started on: September 02, 2010, 11:45:48 AM

Do you got an DHCP-Server (sometimes build in a DSL-Router)? Then there is a chance that the
Guruplug gets a DHCP-IP-Address from your Router to which yu could try to get an ssh-connect.

Sometimes the DHCP-Server has to be enabled in the Router.

If you didnt got a DHCP-Server or Router and you are using Windows then you could try to setup
a DHCP-Server via the Freeware FTPD32 - tftpd32.jounin.net


Hi guidol, thanks for your help. o/

My router has DHCP activated. Here is information showed within its interface:

Quote
Baux DHCP / DHCP lease   
Adresse IP          Adresse MAC             Date d'expiration                   Nom
192.168.1.180    00:50:43:01:9b:97    Fri Sep 3 20:08:47 2010 11    Host-001

Table ARP
Address                     HWtype HWaddress              Flags Mask         Iface
192.168.1.199            ether   6C:F0:49:13:71:4D   C                     lan1
192.168.1.180            ether   00:50:43:01:9B:97   C                     lan1

Périphériques réseaux connectés / Connected network devices

port no   mac addr               is local?   ageing timer
  1         00:0c:c3:44:ef:2a      yes         0.00
  3         00:30:88:12:12:37      no         9.59
  1         00:50:43:01:9b:97      no        17.97
  1         00:60:4c:96:7a:ca      no         1.79
  3         00:e0:fc:8c:b5:c6      no         0.00
  1         6c:f0:49:13:71:4d      no         0.00


I've tried to connect via shh to 192.168.1.180, but connection timed out:

Code:
$ ssh root@192.168.1.180
ssh: connect to host 192.168.1.180 port 22: Connection timed out


It looks like SSH server is not installed on Guru Plug. Note I received GuruPlug and plug it into my router without doing any other thing. Did I miss something?
6  General Category / General Discussion / Re: Newbie question about getting started on: September 01, 2010, 01:28:12 PM
Hi,

I don't have wifi card installed on my desktop. I used to connect via Ethernet only. 192.168.1.1 does not answer

There is no way to connect via Ethernet and SSH ?  Lips sealed
7  General Category / General Discussion / Newbie question about getting started on: August 31, 2010, 06:30:55 PM
Hello,

I've received my Guru Server Plug Standard, and I wonder on the procedure to get started. I expected to get an SSH access for manipulating the guru server plug, but I can either ping the connected hardware. In my modem interface, I checked the guru plug is correctly connected and an IP is associated with it: 192.168.1.180. But no way to connect it, via web browser, neither SSH. Undecided

I fear that I need JTAG debug module for getting started, module which I didn't purchased because of I didn't understand its role. Roll Eyes

Can one of you explain me  if JTAG debug module is required to get started or how to get started if no (is ssh access available)?

Thanks for all.


NB: here is my try to connect via SSH:
Code:
ssh root@192.168.1.180
ssh: connect to host 192.168.1.180 port 22: Connection timed out
8  General Category / General Discussion / Re: Shipping GuruPlug Server on: August 31, 2010, 02:39:34 PM
I purchased one at the end of july, I received it yesterday after sending a mail at sales@.

I'm currently wondering how connect to it via SSH or something else... Undecided
9  Hardware and U-Boot firmware / Hardware / Re: GuruPlug Server Plus Heat Problems on: July 14, 2010, 04:16:59 PM
For your information, I don't know if the information has already be given here (I don't have read all posts), but the heat problem has been received by the Globascale:
http://www.globalscaletechnologies.com/news.aspx?showarticle=4

Quote
7/5/2010
Guru Plug Server - Plus Technical Announcement
Some of you may have experience “heat problems” when using your Guru Plug Server  “Plus” under certain conditions.  You will be pleased to know we have isolated the problem, and would like to make the following clarifications and the recommended procedure to eliminate this problem.

There have been a number of postings in the Forums stating the problem was caused by the power supply, and, while in the past we had issues due to some bad capacitors, this in reality has been more of a smoke screen.

The problem is directly related to heat generated by the load on the CPU.   Having 2 x 1Gb Ethernets and WI-FI running concurrently with other interfaces, causes the CPU to work harder and a lot hotter. We have found the  GuruPlug ‘s small enclosure , is not efficient as we would like at heat dissipation, therefore we suggest the following as a workaround.   

The GuruPlug Server “Plus” is designed in its current form for maximum usage with one Gb Ethernet port and one 10/100Mb Ethernet port.  Whilst using the unit in accordance to these parameters will solve the majority of “heat problems”, it is highly recommended as an additional precaution you use 10/100MB speed connections for both Ethernet ports as it will further reduce the high temperatures on the enclosure surface.

There may be some advanced users who really need the 1Gb speed connection, and we understand the dilemma you may currently face. Please rest assure we have not forgotten your requirements, and in about 3-4 months  time we will be releasing a simple to install  “Professional Upgrade Kit“  so you can take advantage of the higher speed connections. In the interim the units will work effectively and the slightly slower speed connection.

Thank-you for your support in purchasing and using our product and, we apologize for the anxiety and inconvenience caused!
 
As we continue to improve the use and reliability of our product(s), specifications are subject to change without notice.
Pages: [1]