drive doesn't boot

[conjuring]

sdb 7 content

Code: Select all

root@hans-Satellite-A100:/media/sdb5# cd /sdb7
root@hans-Satellite-A100:/sdb7# ls -al
totaal 84
drwxr-xr-x 16 root root  4096 nov 19  2011 .
drwxr-xr-x 29 root root  4096 okt 17 19:33 ..
drwxr-xr-x  2 root root  4096 okt 29  2011 bin
drwxr-xr-x  2 root root  4096 okt 31  2011 boot
drwxrwxr-x  4 root root 12288 okt 29  2011 dev
drwxrwxrwx 11 root root  4096 nov 19  2011 etc
drwxr-xr-x  3 root root  4096 nov 19  2011 lib
lrwxrwxrwx  1 root root    11 okt 29  2011 linuxrc -> bin/busybox
drwx------  2 root root 16384 jan  3  2008 lost+found
drwxr-xr-x  2 root root  4096 aug 27  2008 nowhere
drwxr-xr-x 10 root root  4096 nov 18  2011 opt
drwxrwxrwx  2 root root  4096 mrt  5  2011 proc
drwxr-xr-x  2 root root  4096 jan  3  2008 root
drwxr-xr-x  2 root root  4096 nov 19  2011 sbin
drwxrwxrwx  2 root root  4096 mrt  5  2011 share
drwxrwxrwx  2 root root  4096 mrt  5  2011 sys
drwxrwxr-x 20 root root  4096 nov 19  2011 usr


and yes the green led flickers while the other one stays orange

[conjuring]

I gotta go right now

[fvdw]

yes this is the right content and has not tried to boot.

The orange led means it is prbably set to 100 Mb/s or 10 Mb/s speed. That the green flickers means there is communication.

Something must be wrong in the setup

The isp1 and your pc must be in the same sub net mask.

what you can try is start the fvdw-sl-console and fill in as ip address for nas 192.168.0.200 (use another number in case 200 is in use by another device in your lan). Your pc must have an ip in the same range 192.168.0.x
Now try again.
ps it could be that the console has problems to find the nas in time when you use a wireless connection between your router and pc.

As the connection with u-boot is fully independent from the disk this should simple work

[conjuring]

Tried what you said used ethernet cable instead of wireless network and tried with a diffrent nas ip.
Still no progress ...

[conjuring]

I think the isp isnt able to get an ip adress from the servers, since my routers log doesn't log an ip asigning when i connect it.

[fvdw]

lets first concentrate on getting u-boot console working

when connecting with u-boot console it doesn't need an ip address from the dhcp server. the console use the one you have set for the NAS in the fvdw-sl console main window. The only condtion needed is it needs to be reachable in your LAN (so inside the pool of IP addresses that the your router allows (in you case that was 192.168.0.100 to 192.168.0.200. To eliminate all doubts you could try to set it (in your router) the ip pool to 192.168.0.1 - 192.168.0.255
Alos the ip you set for the NAS may not be in use by another device. if you set the pool as suggested then an nas ip of 192.68.0.252 should be ok

And check that the ip of your PC (shown also in the fvdw-sl console window) starts with 192.168.0

[conjuring]

I already tried those thing still, u-boot doesn't seem to work.

[fvdw]

if it doesn't detect u-boot (has nothing to do with firmware or dik partition) then something must be wrong with this network port or mainboard
There are cheap usb-lan dongles, could be an alternative, but it will not be so easy to ge it going if you are not experienced with linux

Still it is funny that it worked, also with my own isp1 it just works fine, so I do not exclude that somewhere you make an error

Otherwise I am out of options :dontknow

[usuario]

I have a similar problem

The unit has fixed blue light, the led ethernet is flashing.

fvdw-sl console does not detect anything

Any ideas?

Thanks,