On Wed, Jul 4, 2012 at 2:58 AM, Edward M martinezedward...@gmail.com wrote:
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.
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
On 4 July 2012 06:25, Carsten Mattner carstenmatt...@gmail.com wrote:
The most important questions are
- will the installer always corrupt the hdd in this machine?
Well, I have never seen this issue, but if it happened one time, may happen
again. If you like some challenge, try to install by
On Wed, 04 Jul 2012 12:16:25 +0200, 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
Normally this issue can be fixed by setting the BIOS to access the
disk in LBA or LARGE mode. The problem is due to a bug in the BIOS's
attempt to interpret the slice table in CHS mode instead of logical
block mode. It's a BIOS bug. These old BIOS's make a lot of assumptions
On Wed, Jul 4, 2012 at 7:31 PM, Matthew Dillon
dil...@apollo.backplane.com wrote:
Normally this issue can be fixed by setting the BIOS to access the
disk in LBA or LARGE mode. The problem is due to a bug in the BIOS's
attempt to interpret the slice table in CHS mode instead of
On Wed, Jul 4, 2012 at 7:31 PM, Matthew Dillon
dil...@apollo.backplane.com wrote:
Normally this issue can be fixed by setting the BIOS to access the
disk in LBA or LARGE mode. The problem is due to a bug in the BIOS's
attempt to interpret the slice table in CHS mode instead of
:Thanks Matt for the explanation and tip.
:
:It did of course hang when I tried to DEL into the BIOS.
:What worked is pulling out the sata connector, entering
:the BIOS putting it back and then detecting the disk.
:Interesting the auto detection then worked. I've explicitly
:set it to LARGE and
On Wed, Jul 4, 2012 at 8:07 PM, Matthew Dillon
dil...@apollo.backplane.com wrote:
:Thanks Matt for the explanation and tip.
:
:It did of course hang when I tried to DEL into the BIOS.
:What worked is pulling out the sata connector, entering
:the BIOS putting it back and then detecting the
On Wed, Jul 4, 2012 at 8:11 PM, Carsten Mattner
carstenmatt...@gmail.com wrote:
On Wed, Jul 4, 2012 at 8:07 PM, Matthew Dillon
dil...@apollo.backplane.com wrote:
:Thanks Matt for the explanation and tip.
:
:It did of course hang when I tried to DEL into the BIOS.
:What worked is pulling out
On 4 July 2012 14:31, Matthew Dillon dil...@apollo.backplane.com wrote:
I consider it almost a lost cause.
Don't get it: trying to fix this is a lost cause?
--
Raimundo A. P. Santos
Bacharelando em Informática
ICMC - USP
On Wed, Jul 4, 2012 at 8:16 PM, Carsten Mattner
carstenmatt...@gmail.com wrote:
On Wed, Jul 4, 2012 at 8:11 PM, Carsten Mattner
carstenmatt...@gmail.com wrote:
On Wed, Jul 4, 2012 at 8:07 PM, Matthew Dillon
dil...@apollo.backplane.com wrote:
:Thanks Matt for the explanation and tip.
:
:It
: I consider it almost a lost cause.
:
:
:Don't get it: trying to fix this is a lost cause?
Yah, because if we fix it for one BIOS we break it for another.
Hence, a lost cause. There is no single fix which covers all BIOSs.
-Matt
Been down that path, and almost lost my sanity. The code that probes
for disks via the BIOS (in openbsd's boot loader) is just as sensitive,
causing hangs, etc. Writing that was... interesting. The partition table
entries are just about as sensitive (as you've found out), and the joy is
all the
14 matches
Mail list logo
