Jump to content
3 posts in this topic

Recommended Posts

Hey all,

 

I've installed iAtkos v_7 and got it up and running just fine. I've done a few successful x86 installs on my acer aspire one in various versions and distros.

 

At boot, I keep getting the 'EBIOS read error:Device timeout Block 0 sectors 64' which I know is nothing new to these and other forums (yes I read and googled diligently before posting) but the strange thing is, it only happens when I first turn my computer on, then when I manualy power down and restart it's fine. Chameleon boot loader kicks in and everything takes care of itself as normal with no -x -f boot flags etc.

 

The Facts:

 

I've read this is an error with a bad disc burn, but the burn and install went fine, setup is long over and my external dvd drive isn't even on.

 

It's always '0 sectors' never a random number like many others have reported.

 

It always happens immediatly after the acer bios screen and just before the bootloader kicks in, not as a failed darwin boot meaning -v would do nothing to inform me since the problem preempts it.

 

Most confusing (but relieving) of all; it's always temporary. Power down with the button - restart - boots fine. Everywhere else I've read online this error is a deal breaker; you get it, or it boots -not back and fourth.

 

The Questions:

 

I've recently installed switchresx to correct alignment problems on my samsung lcd tv/external monitor. Could this have an effect on boot strings? (doubt it)

 

How do I check my bootloader log/settings to investigate further?

 

Why are the babies of ugly animals still cute? What kind of God would allow that?

 

EFI Strings? I'm new to those, so... maybe something there?

 

MY specs:

Acer Aspire One

120gb HD

1G Ram

Only one partition, formatted hfs+

iAtkos v_7

Voodoo 9.5.0 straight from iAtkos disc (although it says Darwin in 'get info' screen)

Chameleon V2 Bootloader (works fine when it gets there)

 

One last thought before I quits the noobnerd rambling. Could it be something at shutdown that causes the problem at the next start up?

 

Any thoughts appreciated.

 

-JDM

"Life is just a series of one crushing defeat after another until you just wish Flanders was dead."

Have you tried reinstalling the chameleon bootloader?

 

Good idea, just tried it and the install package fails halfway through and reports something like

Install Failed 'postinstall script failure'

 

So maybe I already have a damaged install of cham2. I'll try installing a new bootloader, any suggestions on which one and where to get it?

 

EDIT I did manage to find a few other people with my specific symptoms, but they haven't had much luck either.

 

-JDM

×
×
  • Create New...