From: "McCaffity, Ray" <ray.mccaffity@wcg.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] 2.4.4 stability on Lions
Date: Tue, 22 May 2001 19:25:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005643@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005642@msgid-missing>
I have been running the SuSE 7.2 beta (2.4.4) on a Lion
for about a week now. I don't remember what BIOS I have
but I'll find out.
-----Original Message-----
From: Michael Madore [mailto:mmadore@turbolinux.com]
Sent: Tuesday, May 22, 2001 1:19 PM
To: linux-ia64@linuxia64.org
Subject: [Linux-ia64] 2.4.4 stability on Lions
Hi,
Has anyone seem any instability with the 2.4.4 kernel + David's patch on
Lions? I have been running it successfully on a 2P C0 Big Sur with BIOS
103. On a 4P C0 Lion with BIOS 73, however, I consistantly get lockups
after a short time. Usually I get a totally black screen. I'm going to try
2.4.3 and see if I still see the same problem. 2.4.2 seem to work fine.
--
Mike Madore
Senior Software Engineer
TurboLinux, Inc.
(650)228-5203
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2001-05-22 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 18:18 [Linux-ia64] 2.4.4 stability on Lions Michael Madore
2001-05-22 19:25 ` McCaffity, Ray [this message]
2001-05-22 21:06 ` Matt_Domsch
2001-05-22 21:57 ` Michael Madore
2001-05-22 22:33 ` Wiegrefe, Don J
2001-05-22 22:43 ` Michael Madore
2001-05-23 1:34 ` Matt_Domsch
2001-05-23 16:43 ` Michael Madore
2001-05-23 18:21 ` David Mosberger
2001-05-23 18:23 ` Michael Madore
2001-05-23 20:06 ` Mallick, Asit K
2001-05-23 20:53 ` Michael Madore
2001-05-23 21:54 ` Robboy, David G
2001-05-23 22:26 ` Michael Madore
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=marc-linux-ia64-105590693005643@msgid-missing \
--to=ray.mccaffity@wcg.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.