public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: john stultz <johnstul@us.ibm.com>,
	Len Brown <len.brown@intel.com>,
	macro@linux-mips.org, linux-kernel@vger.kernel.org,
	dean@arctic.org, zippel@linux-m68k.org
Subject: Re: NTP broken with 2.6.14
Date: Mon, 07 Nov 2005 22:44:44 +0100	[thread overview]
Message-ID: <436FCACC.7060104@eclis.ch> (raw)
In-Reply-To: <200511062349.19257.hpj@urpla.net>

Hans-Peter Jansen a écrit :
> Am Freitag, 4. November 2005 03:50 schrieb Jean-Christian de Rivaz:
> 
>>After trying several time, I am unable to upgrade the BIOS of this
>>machine. The flash utility hang all the system at the very beginning
>>of the real access to programm the flash! This is maybe because I use
>>a freedos image over pxelinux. I will try with a floppy and a MSDOS
>>if I found such olds stuffs somehere.
> 
> 
> Could very well be the netboot stuff. I typically flash BIOS/firmware 
> via DOS network boot images, which provides at least two different ways 
> of disk emulation: a: and c:, but some flash tools just freeze the 
> system on load/image load in both ways. Most prominently is the Promise 
> TX2/100 firmware update, but also a couple of motherboards BIOS' 
> flashers behave that way (cannot remember which ones, though). 

As you can see in my two latest post, I finnaly found that this was not 
the good BIOS for the motherborad. When I understand my mistake, I take 
the good BIOS version and I was able to flash it with FreeDOS over PXE 
network boot. So the netboot stuff was not the problem in my case.

The funny part is that with my motherboard, if you try to flash the 
wrong BIOS version you don't get any clear message agains this 
opearation. But this ended randomly into one of the following posibility:
1) system simply hang.
2) "division by zero error".
3) "failed opcode "<put some hexadecimal bytes here>.
4) immediate reboot.

I think that the BIOS update is an area where the mainboard makers have 
a hug possibility to improve there product...

-- 
Jean-Christian de Rivaz

  reply	other threads:[~2005-11-07 21:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 23:05 NTP broken with 2.6.14 Jean-Christian de Rivaz
2005-11-02 23:21 ` john stultz
2005-11-02 23:37   ` Jean-Christian de Rivaz
2005-11-03  0:15     ` john stultz
2005-11-03  0:45       ` Jean-Christian de Rivaz
2005-11-03  1:07         ` john stultz
2005-11-03  2:26           ` Jean-Christian de Rivaz
2005-11-03 19:32             ` john stultz
2005-11-03 19:51               ` Lennart Sorensen
2005-11-03 20:11                 ` john stultz
2005-11-03 20:48                   ` Lennart Sorensen
2005-11-03 21:00                     ` john stultz
2005-11-03 21:12                       ` Lennart Sorensen
2005-11-03 21:28                   ` Jean-Christian de Rivaz
2005-11-03 21:12               ` Jean-Christian de Rivaz
2005-11-03 21:41                 ` john stultz
2005-11-03 22:10                   ` Jean-Christian de Rivaz
2005-11-03 22:54                     ` john stultz
2005-11-04  0:15                       ` Jean-Christian de Rivaz
2005-11-04  0:40                         ` john stultz
2005-11-04  2:50                           ` Jean-Christian de Rivaz
2005-11-06 22:49                             ` Hans-Peter Jansen
2005-11-07 21:44                               ` Jean-Christian de Rivaz [this message]
2005-11-04 12:40                       ` Maciej W. Rozycki
2005-11-02 23:24 ` john stultz
2005-11-03  0:36 ` Roman Zippel
2005-11-03  1:13   ` Jean-Christian de Rivaz
2005-11-03  9:42     ` Roman Zippel
  -- strict thread matches above, loose matches on Subject: below --
2005-11-04  3:44 Brown, Len
2005-11-04  4:07 ` john stultz
2005-11-04 13:51   ` Lennart Sorensen
2005-11-04 16:39   ` Jean-Christian de Rivaz
2005-11-04 17:41     ` Jean-Christian de Rivaz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=436FCACC.7060104@eclis.ch \
    --to=jc@eclis.ch \
    --cc=dean@arctic.org \
    --cc=hpj@urpla.net \
    --cc=johnstul@us.ibm.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox