Good Idea. Now the debian installer found the hd. Themes the root partition is broken. I will try to delete all partitions and the first 500 Bytes with MBR/RDB and then try to install debian again.

Hi, have you ever seen this:

http://www.littlefe.net/mediawiki/index ... ikaInstall

R&B :)

It didnt helped. I delete all partitions and installed debian again.

If I schwitch the efika on, the hd and all partitons worked well. I could see all directorys with ls hd:3

If I made a reset or start the debian-kernel, the hd is gone. Maybe, because the kernel send a reset-signal to the ata-bus ?

Any solution ?

I try another harddrive from Hitachi. Its a 40GB-drive.

Didnt work :x

It was not found after the Efika switched on nor after a reset.

What is wrong with my Efika ? Or is the firmware buggy ?

Most likely a problem in OF.
And DI_EFIKA too does not find hdd during the work?

As a variant I can only advise to try to connect ide->compactflash adapter. Is version directly under 2.5 ide connector.

It works now.

I sent my Efika to bplan and they install a simple Forth-script in the nvram. Now my hd was found by OF after start and after reboot/reset. Linux works too.

Its a timing-problem with Efika,hd and my pico-PSU. All together wont start fast enough. With a normal PSU, everything worked fine without changes.

I have the same problems on my Efika with pico-psu:

Seagate ST9808210A 80GB does not boot
Western Digital WD800VE-00HDT0 80GB does not boot

but

Seagate ST960821A 60GB does boot

Could I try the nvram setting also? Where can I get it?

Hi Lucas, try adding this to your nvramrc;



This is the script from Germany. The recommended way to use it for now would be to

1) edit it into a text file (efika_atarst.forth) with these contents:



2) boot that from a USB key or TFTP something (boot scsi:0 efika_atarst.forth)

If it works, and doesn't explode your system, then you can put it into nvramrc as the first snippet (no \ FORTH) part. Please be VERY careful.

May I ask why this problem with harddrives have existed
since the first Pegasos-boards and never been fixed?

Why is this so special in SmartFirmware, when there are
absolutely none in x86 BIOS? (If there were, the hard
drive manufacturer would go bankrupt!).

Why is it so hard to implement a pause in each and every
bPlan SmartFirmware release?

Because; it isn't the same problem.



Please direct your complaints to support@efika.de