plugout.net

checkt if the files where there and they were.
i dont get an interupt, marvel >>
it just remains waiting for u-boot.
i connected it to a laptop using an ethernet cable i supose this is what you ment?
windows does something when i power it on it says its connecting and gives this as connection info.
Fysiek adres: 00-A0-D1-3B-48-98
IP-adres: 169.254.244.145
Subnetmasker: 255.255.0.0
Standaardgateway:
DNS-server:
WINS-server:

no that is not the right way it must be in a LAN with a dhcp server (router)

So i did what you asked, console stays at waiting for u boot, is it possible that the Sata connector broke ?

no this u-bootr console should even work without a disk installed in your isp1.

It could mean a problem with your network interface on the isp, or a bad cable..
I have an isp1 at home without disk I will test the fvdw-sl console this evening with that, just to be sure that it can talk with the isp1. I never tried it myself on an isp1

Does the nas ip address in the console matter? my dhcp server (router) is set to give out from 198.168.0.100 198.168.0.200

Yes that matters then you should set in the fvdw-sl console 192.168.0.252
and extend the pool of the dhcp server to 192.168.0.254

I just tested it with my isp1 (without a disk) and it is detected just fine by the fvdw-sl console

Now i go for dinner, after that I will do a test with uploading the kernel

I have set the ip settings like you said, still no help, i guess the network interface of the isp broke somehow.
The led work however and so does the activity led on the switch to wich it is connected.

it is not likely that is broken but not impossible

I just uploaded the isp1 2.6.33.1 kernel of the first install package kernel to my isp1 and it worked fine


if the the internet interface is the problem then we can verify tjhis as follow. Take the disk that you have prepared and tried to boot.
If the the boot succeeeded there should be a file "boot.log" present on partition 7

so connect it to your pc running linux
and do this
(assuming the disk you prepared is sdb)

Code: Select all

mkdir /sdb7
sudo mount /dev/sdb7 /sdb7
cat /dev/sdb7/boot.log

and see if it produces output..

it doesn't produce output

well that could be good news, check the content of sdb7

Code: Select all

cd /sdb7
ls -al

conjuring wrote:I have set the ip settings like you said, still no help, i guess the network interface of the isp broke somehow.
The led work however and so does the activity led on the switch to which it is connected.

does the activity led on the backside of the isp1 next to the utp cable also flicker sometimes (it should)