> Wait a minute, this is a new board. I had a suspicion, and I have a new
> suspect, can we investigate this?
Yep
> I rebooted, and since I left APM out, the system clock is alright since
> 63 mins. Might the APM BIOS CPU IDLE calls be related? I did *not* enable
If the APM bios holds interrupt
On Thu, Dec 28, 2000 at 02:37:19AM +, Alan Cox wrote:
> > I have my system clock drift roughly -1 s/min, though my CMOS clock is
> > fine unless tampered with.
> adjtimex will let you tell Linux the clock on the board is crap too
But may tamper with the CMOS clock
-
To unsubscribe from this
On Thu, 28 Dec 2000, Alan Cox wrote:
> > > o VIA686a timer reset to 18Hz background (Vojtech Pavlik)
> >
> > I patched my 2.2.18-ma2 with that patch to see if that helps me off my
> > sys time slowness, but it does unfortunately not help.
>
> Thats unrelated
Ok, that's what I eventual
> > o VIA686a timer reset to 18Hz background (Vojtech Pavlik)
>
> I patched my 2.2.18-ma2 with that patch to see if that helps me off my
> sys time slowness, but it does unfortunately not help.
Thats unrelated
> I have my system clock drift roughly -1 s/min, though my CMOS clock is
>
Somewhat late, but not too late; Alan Cox wrote:
> 2.2.19pre1
...
> o VIA686a timer reset to 18Hz background (Vojtech Pavlik)
I patched my 2.2.18-ma2 with that patch to see if that helps me off my
sys time slowness, but it does unfortunately not help.
I have my system clock drift r
Hi
That did it, thanks
Kees
On Sat, 23 Dec 2000, J . A . Magallon wrote:
>
> On 2000.12.23 kees wrote:
> > Hi,
> >
> > Trying to build 2.2.18+pe-patch-2.2.19-3 gives:
> >
> >
> > /usr/bin/cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
> > -O2
> > -fomit-frame-pointer -f
On 2000.12.23 kees wrote:
> Hi,
>
> Trying to build 2.2.18+pe-patch-2.2.19-3 gives:
>
>
> /usr/bin/cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
> -O2
> -fomit-frame-pointer -fno-strict-aliasing -D__SMP__ -pipe -fno-strength-reduce
> -m486 -malign-loops=2 -malign-jumps=2
Hello Alan,
did you receive the mails I sent to you on lxorguk last sunday with
the bonding driver updates ? I had mail problems, and received no ack.
If you want a resend, please just let me now.
Regards,
Willy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
On Fri, Dec 22, 2000 at 12:52:32AM +, Alan Cox wrote:
>
> 2.2.19pre3
> o Fix e820 handling (Andrea Arcangeli)
arch/i386/kernel/setup.c:
/* compare results from other methods and take the greater */
if (ALT_MEM_K < EXT_MEM_K)
On 22 Dec 2000, Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>,
> Richard B. Johnson <[EMAIL PROTECTED]> wrote:
> >alias kwhich='type -path' in ~./bashrc should fix.
>
> Hmm? Smells like a stupid bug to me. The script is called as:
>
> CCFOUND :=$(shell $(CONFIG_SHELL) scripts/k
In article <[EMAIL PROTECTED]>,
Richard B. Johnson <[EMAIL PROTECTED]> wrote:
>alias kwhich='type -path' in ~./bashrc should fix.
Hmm? Smells like a stupid bug to me. The script is called as:
CCFOUND :=$(shell $(CONFIG_SHELL) scripts/kwhich kgcc gcc272 cc gcc)
So how can bash ever decide to rep
On Fri, 22 Dec 2000, Alan Cox wrote:
> > > why 'standard' Unix/sell/executable commands keep getting changed
> > > to GNUisms in distributions.
> >
> > I've been asking that question ever since most popular distributions
> > started putting a copy of bash in /bin/sh.
>
> And which of the versio
> And which of the versions of 'which' would you rather people had. Do you want
> csh behaviour, tcsh behaviour, which non builtin BSD behaviour, which as alias
> trick behaviour, which as ksh behaviour..
>
> There is no standard which command.
Exactly why there will be 3 different overall behavi
> > why 'standard' Unix/sell/executable commands keep getting changed
> > to GNUisms in distributions.
>
> I've been asking that question ever since most popular distributions
> started putting a copy of bash in /bin/sh.
And which of the versions of 'which' would you rather people had. Do you wa
> > o Optimise kernel compiler detect, kgcc before(Peter Samuelson)
> > gcc272 also
>
> kwhich doesn't seem to work ok with several arguments if sh is bash-1.14.7:
Yep. I shall just back this out
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Fri, 22 Dec 2000, Petri Kaukasoina wrote:
> On Fri, Dec 22, 2000 at 12:52:32AM +, Alan Cox wrote:
> >
> > o Optimise kernel compiler detect, kgcc before(Peter Samuelson)
> > gcc272 also
>
> kwhich doesn't seem to work ok with several arguments if sh is bash-1.14.7:
>
> $ sh sc
> alias kwhich='type -path' in ~./bashrc should fix. I don't know
> why 'standard' Unix/sell/executable commands keep getting changed
> to GNUisms in distributions.
I've been asking that question ever since most popular distributions
started putting a copy of bash in /bin/sh.
WHY oh WHY would th
On Fri, Dec 22, 2000 at 12:52:32AM +, Alan Cox wrote:
>
> o Optimise kernel compiler detect, kgcc before(Peter Samuelson)
> gcc272 also
kwhich doesn't seem to work ok with several arguments if sh is bash-1.14.7:
$ sh scripts/kwhich kgcc gcc272 cc gcc
kgcc:gcc272:cc:gcc: not fo
> 2.2.19pre3
[snip]
> o Optimise kernel compiler detect, kgcc before(Peter Samuelson)
> gcc272 also
I get an endless stream of this:
kgcc:gcc272:cc:gcc: not found
kgcc:gcc272:cc:gcc: not found
/bin/sh: -D__KERNEL__: command not found
/bin/sh: -D__KERNEL__: command not found
/bin/sh
19 matches
Mail list logo
