I see the same problem when trying to boot FreeBSD-3.0-RELEASE (or there
abouts) and later cdroms on my TP770.
I can boot FreeBSD-2.2.8 and earlier FreeBSD-3.0-SNAP cdroms just fine. I
think it has something to do with the new boot loader that went in just
before 3.0-RELEASE.
Tom
On Fri, 13
I'd be more than happy to do the pestering if some one could write down
a detailed description of exactly how the TP's BIOS is non-compliant.
I don't know enough about the boot process and BIOS to write such a
description.
Tom
On Fri, 13 Aug 1999, Mike Smith wrote:
I attempt to boot a CD
On Wed, 15 Dec 1999, Donn Miller wrote:
"Jordan K. Hubbard" wrote:
I was under the impression that Polar Bears are native to the
North Pole and penguins are from the South Pole.
Really? What eats penguins then? Maybe walrus?
Arctic Foxes.
- Donn
I doubt it. No
On Thu, 16 Dec 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] Tom Bartol
writes:
: IIRC it does update uptime properly after a suspend in 2.2.8 but does not
: do so in 3.X and -current on my ThinkPad 770.
define correctly. Eg, if I suspend for an hour it adds an hour?
Warner
On Thu, 16 Dec 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] Tom Bartol
writes:
: I tried 3.0-current after this merge, suspend and resume worked fine on my
: 770 with the exception of uptime.
I can confirm that uptime, at least as reported by uptime(1), isn't
increased
On Thu, 6 Jan 2000, Josef Karthauser wrote:
On Fri, Jan 07, 2000 at 08:00:46AM +1100, Darren Reed wrote:
btw, I completely agree with the need to have good pccard/pcmcia support.
For the first time there was a real reason for me to ditch FreeBSD on an
Intel platform box (my laptop)
On Wed, 16 Feb 2000, Mike Smith wrote:
The problem with the Thinkpad BIOS is where it puts the emulated floppy
image's disk number - it's not in the 'normal' place, and I don't exactly
know how to deal with it cleanly. If someone were to lend me a thinkpad
or look at this it
On Wed, 16 Feb 2000, Mike Smith wrote:
This is a problem with the thinkpad BIOS that I have not had the time to be
able to track down. It would *appear* to be that the BIOS does not do
int 13 handling on boot cdroms, and the boot/loader makes much use of that
for loading the kernel
Hi all,
Has anyone yet tried running -current on a Xeon with 4GB RAM installed?
We're about to place an order for a Quad Xeon and would like to have 4GB
of RAM installed if it is feasible and/or possible to make this work with
-current.
Thanks for the help,
Tom
To Unsubscribe: send mail
On Thu, 8 Apr 1999, John Polstra wrote:
I am not saying the dependencies are broken. I'm just lamenting the
general problem that it's difficult to upgrade a port that depends on
a lot of things. It's a general structural problem, and I don't know
how to fix it.
Say you've got a bunch
On Thu, 8 Apr 1999, Jacques Vidrine wrote:
On 8 April 1999 at 12:24, John Polstra j...@polstra.com wrote:
[snip]
Say you've got a bunch of ports that all depend on the same shared
library -- maybe libjpeg or libXpm. You've had them installed for
a few months, and they all work fine.
On Thu, 22 Apr 1999, Peter Wemm wrote:
Matthew Reimer wrote:
Great work guys! It almost seems that -current is more stable than
-stable!
Matt
Funny you should mention it. I've heard this from a number of people over
the last week.. One has even suggested using a particular
12 matches
Mail list logo
