From: Guy Martin <gmsoft@gentoo.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Support for 2.4.x kernels on hppa
Date: Tue, 25 May 2004 12:21:24 +0200 [thread overview]
Message-ID: <20040525122124.7154e4d2.gmsoft@gentoo.org> (raw)
In-Reply-To: <20040524183227.GW7207@tausq.org>
[-- Attachment #1.1: Type: text/plain, Size: 1395 bytes --]
On Mon, 24 May 2004 11:32:27 -0700
Randolph Chung <tausq@debian.org> wrote:
> I'd like to take an informal "survey" of what kernel versions people
> are using....
I use a 2.6 on a A440 and B180l and a C3600.
I remember having trouble with a J5000 but it was some time ago and I
guess my problem was the SMP enabled.
I'd like to use it on my D270 and on a K360 but there are scsi problems
atm. They both suffer of the same problem described by Joel Soete.
Also, a gentoo user wasn't able to boot a 2.6 on a 735/120. Palo (1.5)
display "If it's the last message ..." and nothing more while it works
well with a 2.4. I'll try myself later on my 735/99 which is down atm.
I'd like to add that despite the scsi problem, I can't still produce
livecd (the gentoo installation cd) using 2.6 because of the numerous
default config. If I remember correctly, if I enable some HIL stuff,
the kernel loops or crash at boot on my b180l.
> If you are one of those people who really care about 2.4 support,
> please speak up now!
Personaly, I don't care about 2.4 even if 2.6 doesn't have SMP. With a
2.4, my D270 compiles things slower with SMP than without. I also have
other problems with SMP like packet loss to localhost, making portmap
and other socket daeùon unusable.
hth
--
Guy Martin
Gentoo Linux - HPPA port Lead / IPv6 team
Lug Charleroi (Belgium)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-05-25 10:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040524183227.GW7207@tausq.org>
2004-05-24 19:07 ` [parisc-linux] Re: Support for 2.4.x kernels on hppa Ulrich Teichert
2004-05-24 19:32 ` [parisc-linux] " William Waites
2004-05-25 4:02 ` Grant Grundler
[not found] ` <20040525173610.GA764@parc.styx.org>
2004-05-26 0:19 ` Grant Grundler
2004-05-24 19:37 ` John David Anglin
2004-05-24 20:19 ` Thibaut VARENE
[not found] ` <200405241937.i4OJbX07011585@hiauly1.hia.nrc.ca>
2004-05-24 19:40 ` Randolph Chung
2004-05-24 21:36 ` Ulrich Teichert
2004-05-24 21:53 ` [parisc-linux] " Steve Bromwich
2004-05-25 10:21 ` Guy Martin [this message]
2004-05-25 17:12 ` [parisc-linux] " Michael S. Zick
2004-05-25 17:14 ` Guy Martin
[not found] <200405242136.i4OLaRtN003029@arbas.nms.ulrich-teichert.org>
2004-05-24 21:47 ` John David Anglin
[not found] ` <200405242147.i4OLlVoZ012250@hiauly1.hia.nrc.ca>
2004-05-25 4:09 ` Grant Grundler
[not found] ` <20040525040929.GB1308@colo.lackof.org>
2004-05-25 5:42 ` Randolph Chung
2004-05-25 6:02 ` John David Anglin
[not found] ` <20040525054216.GD7207@tausq.org>
2004-05-25 15:26 ` James Bottomley
2004-05-25 17:54 ` Carlos O'Donell
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=20040525122124.7154e4d2.gmsoft@gentoo.org \
--to=gmsoft@gentoo.org \
--cc=parisc-linux@lists.parisc-linux.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