Re: machine won't start

2012-07-03 Thread Sascha Wildner
On Tue, 03 Jul 2012 23:15:47 +0200, Carsten Mattner  
carstenmatt...@gmail.com wrote:



Hi,

I tried to install dfly 3.0.2 on an old amd64 box.

When setup was in the configuration phase it didn't allow setting
passwords with : or other characters.

At that point I hit hard (cold) reset and since that time the machine
won't leave the BIOS startup phase (POST?).

Took out the CMOS battery for a minute to no avail. Anything else I
should try? Is it possible that the ROM or CPU has been damaged by
the installer? I can't even get into the BIOS via DEL.
I'll take out the CMOS battery overnight and try tomorrow.

Thanks for any help.


It sounds like http://bugs.dragonflybsd.org/issues/989

Sascha


Re: machine won't start

2012-07-03 Thread Raimundo Santos
On 3 July 2012 18:15, Carsten Mattner carstenmatt...@gmail.com wrote:

 Hi,

 I tried to install dfly 3.0.2 on an old amd64 box.

 When setup was in the configuration phase it didn't allow setting
 passwords with : or other characters.


Well, I have this issue too: only alphanumeric chars. Booring :S

My workaround: just let the root pwd be anything simple and do not create
users with the installer.

Another very insane issue: when let the installer handle the time config,
my machine stay in the UTC and only changed when dntpd was activated. 0_o




 At that point I hit hard (cold) reset and since that time the machine
 won't leave the BIOS startup phase (POST?).

 Took out the CMOS battery for a minute to no avail. Anything else I
 should try? Is it possible that the ROM or CPU has been damaged by
 the installer? I can't even get into the BIOS via DEL.
 I'll take out the CMOS battery overnight and try tomorrow.

 Thanks for any help.


Well... you are very lucky! :)

Try to boot without the HDD and see what happens.

cheers!

raitech

-- 

Raimundo A. P. Santos
Bacharelando em Informática
ICMC - USP


Re: machine won't start

2012-07-03 Thread Carsten Mattner
On Tue, Jul 3, 2012 at 11:30 PM, Sascha Wildner s...@online.de wrote:
 On Tue, 03 Jul 2012 23:15:47 +0200, Carsten Mattner
 carstenmatt...@gmail.com wrote:

 Hi,

 I tried to install dfly 3.0.2 on an old amd64 box.

 When setup was in the configuration phase it didn't allow setting
 passwords with : or other characters.

 At that point I hit hard (cold) reset and since that time the machine
 won't leave the BIOS startup phase (POST?).

 Took out the CMOS battery for a minute to no avail. Anything else I
 should try? Is it possible that the ROM or CPU has been damaged by
 the installer? I can't even get into the BIOS via DEL.
 I'll take out the CMOS battery overnight and try tomorrow.

 Thanks for any help.

 It sounds like http://bugs.dragonflybsd.org/issues/989

Pulled out the hdd, put the battery back, started.
First the 4 POST LEDs looked like this
GREEN  RED
GREEN GREEN
After loading default settings in the BIOS and doing some changes
and saving all of it and restarting all LEDs went green.

Thanks Sascha.

Now I only need to find a way get the HDD content repaired.
Suggestions? Can I use the same machine? I suppose
I'll have to buy or find a USB adapter to connext the 3.5 SATA disk?

This is the first time I saw a BIOS hang caused by harddisk content.


Re: machine won't start

2012-07-03 Thread Carsten Mattner
On Tue, Jul 3, 2012 at 11:55 PM, Carsten Mattner
carstenmatt...@gmail.com wrote:
 On Tue, Jul 3, 2012 at 11:30 PM, Sascha Wildner s...@online.de wrote:
 On Tue, 03 Jul 2012 23:15:47 +0200, Carsten Mattner
 carstenmatt...@gmail.com wrote:

 Hi,

 I tried to install dfly 3.0.2 on an old amd64 box.

 When setup was in the configuration phase it didn't allow setting
 passwords with : or other characters.

 At that point I hit hard (cold) reset and since that time the machine
 won't leave the BIOS startup phase (POST?).

 Took out the CMOS battery for a minute to no avail. Anything else I
 should try? Is it possible that the ROM or CPU has been damaged by
 the installer? I can't even get into the BIOS via DEL.
 I'll take out the CMOS battery overnight and try tomorrow.

 Thanks for any help.

 It sounds like http://bugs.dragonflybsd.org/issues/989

 Pulled out the hdd, put the battery back, started.
 First the 4 POST LEDs looked like this
 GREEN  RED
 GREEN GREEN
 After loading default settings in the BIOS and doing some changes
 and saving all of it and restarting all LEDs went green.

 Thanks Sascha.

 Now I only need to find a way get the HDD content repaired.
 Suggestions? Can I use the same machine? I suppose
 I'll have to buy or find a USB adapter to connext the 3.5 SATA disk?

 This is the first time I saw a BIOS hang caused by harddisk content.

The important question is if the disk would have been incompatible
in content even if I hadn't hard-resetted the machine while in the
installer. ?


Re: machine won't start

2012-07-03 Thread Carsten Mattner
On Tue, Jul 3, 2012 at 11:42 PM, Raimundo Santos rait...@gmail.com wrote:

 Well... you are very lucky! :)

Always have identical spare mainboard just in case?

 Try to boot without the HDD and see what happens.

That worked see the other reply.


Re: machine won't start

2012-07-03 Thread Edward M

On 07/03/2012 02:15 PM, Carsten Mattner wrote:

At that point I hit hard (cold) reset and since that time the machine
won't leave the BIOS startup phase (POST?).

Took out the CMOS battery for a minute to no avail. Anything else I
should try? Is it possible that the ROM or CPU has been damaged by
the installer? I can't even get into the BIOS via DEL.
I'll take out the CMOS battery overnight and try tomorrow.

Thanks for any help.
.



Sounds like identical problem i was having with my old intel based 
laptop.
After the first reboot, following an install, it would get stuck on 
the BIOS screen.
 i had to do. turn  off  the system, remove the hd, connect it on 
an another system and install
   another os, erasing dragonfly. reconnect the hd back to the laptop 
then the laptop would boot fine.


   unfortunately, i never found the solution, the hd pins were 
beginning to bend  from removing

   the hd alot  trying  to find a workaround.