of the computers, look at the
CAS/RAS/clock timing settings like two people suggested (thanks :-) )
and hope to be happy and have a stable machine after that.
Thanks for this half-solution :-)
--
Ronald Bultje
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&qu
settings like two people suggested (thanks :-) )
and hope to be happy and have a stable machine after that.
Thanks for this half-solution :-)
--
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
-8/RH-7.1
installation CDs).
--
Ronald Bultje
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
y I bought... they are all 133 MHz SDRAM sticks, some 64 MB,
some 128 MB MB manual says it can handle all 64/128 MB sticks...
-
Anyway, thanks for any advice until now and thanks for listening again,
hope to hear more solutions.
--
Ronald Bultje
-
To unsubscribe from this list: send the
sticks, some 64 MB,
some 128 MB MB manual says it can handle all 64/128 MB sticks...
- your solution here :-)
Anyway, thanks for any advice until now and thanks for listening again,
hope to hear more solutions.
--
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux
installation CDs).
--
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 04 Jul 2001 17:06:51 -0300, Alessandro Motter Ren wrote:
>
> Which filesystem are you using on this machine?
> []s.
ext2
--
Ronald
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
win2k is running stable and it's scary to see
linux crash while win2k runs stable and smooth.
(ps I'm not subscribed to the list - please CC a copy to me when
replying)
Thanks in advance for any help on this,
--
Ronald Bultje
-
To unsubscribe from this list: send the line "unsubscri
is running stable and it's scary to see
linux crash while win2k runs stable and smooth.
(ps I'm not subscribed to the list - please CC a copy to me when
replying)
Thanks in advance for any help on this,
--
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
On 04 Jul 2001 17:06:51 -0300, Alessandro Motter Ren wrote:
Which filesystem are you using on this machine?
[]s.
ext2
--
Ronald
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
tead of
"linux-2.4.4 mem=256M" at the lilo prompt, it does work. Is this a bug
in the code that handles options given at startup-time? (I only tried
this for 2x128 sticks but I suppose this is the same for 2x64+1x128
sticks - I guess I'm too lazy to try it out).
Regards,
Ronald Bultj
distro = RedHat-7.0 (with updates from redhat.com installed)
Kernel = 2.4.4
gcc = 2.96
glibc = 2.2
system = p-II 400 MHz, 128 MB swap, 440BX (abit p6b) mainboard
memory is (133 MHz) SDRAM memory (running at 100 MHz)
[please CC me, I'm currently not subscribed]
Regards,
Ronald Bultje
-
To unsubs
(with updates from redhat.com installed)
Kernel = 2.4.4
gcc = 2.96
glibc = 2.2
system = p-II 400 MHz, 128 MB swap, 440BX (abit p6b) mainboard
memory is (133 MHz) SDRAM memory (running at 100 MHz)
[please CC me, I'm currently not subscribed]
Regards,
Ronald Bultje
-
To unsubscribe from this list: send
tried
this for 2x128 sticks but I suppose this is the same for 2x64+1x128
sticks - I guess I'm too lazy to try it out).
Regards,
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
>Actually, it broke at 2.4.3. Go look at the first change to buz.c from
>that patch.
None at all. It didn't break at 2.4.3, it just didn't compile at all anymore
in 2.4.3. It was already kind of broken before that.
>PS: I really hate it when people break "functional" things in the >"stable"
Actually, it broke at 2.4.3. Go look at the first change to buz.c from
that patch.
None at all. It didn't break at 2.4.3, it just didn't compile at all anymore
in 2.4.3. It was already kind of broken before that.
PS: I really hate it when people break functional things in the stable
tree.
On 18 May 2001 10:30:40 +0200, reiser.angus wrote:
> TUX does not exist on 2.2 kernel
> They use a RedHat 7.0 with a 2.4 kernel patched by RedHat (with TUX,
> zerocopy, etc..)
I am pretty sure the C'T article mentioned that TUX did use a 2.2.x
kernel - so it does exist. How else could they make
On 18 May 2001 10:12:34 +0200, reiser.angus wrote:
> > However, taking a closer look, it turns out, that the above statement
> > holds true only for 1 and 2 processor machines. Scalability already
> > suffers at 4 processors, and at 8 processors, TUX 2.0 (7500) gets beaten
> > by IIS 5.0 (8001),
On 18 May 2001 10:12:34 +0200, reiser.angus wrote:
However, taking a closer look, it turns out, that the above statement
holds true only for 1 and 2 processor machines. Scalability already
suffers at 4 processors, and at 8 processors, TUX 2.0 (7500) gets beaten
by IIS 5.0 (8001), and
On 18 May 2001 10:30:40 +0200, reiser.angus wrote:
TUX does not exist on 2.2 kernel
They use a RedHat 7.0 with a 2.4 kernel patched by RedHat (with TUX,
zerocopy, etc..)
I am pretty sure the C'T article mentioned that TUX did use a 2.2.x
kernel - so it does exist. How else could they make a
Hello,
I get kernel NULL-pointers when I close my video application ('studio') and
then, X usually locks.
Only way to get back into the machine is ssh'ing and typing 'reboot' (after
examining dmesg, of course) or resetting the box. The
keyboard/mouse/video-card are locked by X, it seems, there's
Hello,
I get kernel NULL-pointers when I close my video application ('studio') and
then, X usually locks.
Only way to get back into the machine is ssh'ing and typing 'reboot' (after
examining dmesg, of course) or resetting the box. The
keyboard/mouse/video-card are locked by X, it seems, there's
On 2001.05.08 01:04:57 +0200 Jesper Juhl wrote:
>
> static inline int sock_rcvlowat(struct sock *sk, int waitall, int len)
> {
> int r = len;
> if (!waitall)
> r = min(sk->rcvlowat, len);
> return max(1,r);
> }
>
return max(1, waitall ? len :
On 2001.05.08 01:04:57 +0200 Jesper Juhl wrote:
static inline int sock_rcvlowat(struct sock *sk, int waitall, int len)
{
int r = len;
if (!waitall)
r = min(sk-rcvlowat, len);
return max(1,r);
}
return max(1, waitall ? len : min(sk-rcvlowat,
On 2001.05.04 03:20:46 +0200 Miles Lane wrote:
> Prepared Text of Remarks by Craig Mundie, Microsoft Senior Vice
> President
> The Commercial Software Model
> The New York University Stern School of Business
> May 3, 2001
For the people who missed it, Alan Cox' response is at:
On 2001.05.04 03:20:46 +0200 Miles Lane wrote:
Prepared Text of Remarks by Craig Mundie, Microsoft Senior Vice
President
The Commercial Software Model
The New York University Stern School of Business
May 3, 2001
For the people who missed it, Alan Cox' response is at:
if they _used_ the old buz-thing, they'd start bugging
you with "how do I fix it?"
A broken driver in the kernel basically means a broken kernel - so it'd be
better to just remove it I guess... What do you think, Alan?
--
Ronald Bultje
-
To unsubscribe from this list: send the l
fix it?
A broken driver in the kernel basically means a broken kernel - so it'd be
better to just remove it I guess... What do you think, Alan?
--
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
ct is optimized for the new
driver (though the old one should still work).
--
Ronald Bultje
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Ple
+ #define KMALLOC_MAXSIZE (128*1024)
#define DEBUG(x) /* Debug driver */
#define IDEBUG(x) /* Debug interrupt handler */
Although this driver will probably be replaced by the new one from Serguei
Miridonov sooner or later, imho it's best to fix this for the time being...
--
Ron
(128*1024)
#define DEBUG(x) /* Debug driver */
#define IDEBUG(x) /* Debug interrupt handler */
Although this driver will probably be replaced by the new one from Serguei
Miridonov sooner or later, imho it's best to fix this for the time being...
--
Ronald Bultje
for the new
driver (though the old one should still work).
--
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
s to do this,
let him use redhat's RPM manager, "enter your password" with a nice
X-window, and press that button "install" - same effect)...
You don't need to patch the kernel for this...
--
Ronald Bultje
-
To unsubscribe from this list: send the line "unsubscrib
that button install - same effect)...
You don't need to patch the kernel for this...
--
Ronald Bultje
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
ns and read the screen. And for pressing the
buttons you really don't need anything else than a touchscreen or some (1?
2?) buttons on the PDA...
And for using linux as a command-line too on a PDA - we'll need something
to make input easier, like Aaron Lehman suggested in another e-mail
(keyboard
a touchscreen or some (1?
2?) buttons on the PDA...
And for using linux as a command-line too on a PDA - we'll need something
to make input easier, like Aaron Lehman suggested in another e-mail
(keyboard, speach recognition).
--
Ronald Bultje
-
To unsubscribe from this list: send the line
a
> drivers have never been loaded and then its interesting. Is the box
> stable
> with 2.2 ?
Yes (i.e. no crashes because of this and never any X-lockup/-crash).
I'll try the non-nvidia boot and send a report to nvidia.
Ronald Bultje
-
To unsubscribe from this list: send the line &q
8ee <__free_pages_ok+be/310>
f: 68 b9 c7 1e c0push $0xc01ec7b9
Is blackbox broken? Or is this a kernel bug? Or a bug in the nvidia
drivers?
I hope you can fix it (if it is a kernel bug)...
Ronald Bultje
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&q
+bc/310
d: 6a 53 push $0x53
Code; c01298ee __free_pages_ok+be/310
f: 68 b9 c7 1e c0push $0xc01ec7b9
Is blackbox broken? Or is this a kernel bug? Or a bug in the nvidia
drivers?
I hope you can fix it (if it is a kernel bug)...
Ronald Bultje
and then its interesting. Is the box
stable
with 2.2 ?
Yes (i.e. no crashes because of this and never any X-lockup/-crash).
I'll try the non-nvidia boot and send a report to nvidia.
Ronald Bultje
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
40 matches
Mail list logo
