From: Max Grabert <parisc@gmail.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: J2240 - Almost there....
Date: Sat, 31 Dec 2005 15:43:22 +0100 [thread overview]
Message-ID: <e6eae0290512310643q523877d9x@mail.gmail.com> (raw)
In-Reply-To: <20051230200924.GA3556@tachyon.int.mcmartin.ca>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
On 30/12/05, Kyle McMartin <kyle@mcmartin.ca> wrote:
> On Fri, Dec 30, 2005 at 10:51:22AM -0500, Craig D. Lansing wrote:
> > defxx.c:v1.06 2003/08/04 Lawrence V. Stephani and others
> > fddi%d: DEFPA at I/O addr = 0x100, IRQ = 96, Hardware addr =
> 58-B0-60-00-00-00
>
> I'm going to take a stab and say this is your problem. You're likely going
> to see a HPMC chassis code however this machine displays such a thing (look
> up the LED code, or it should display it right on an LCD if it was one.)
>
> [Thanks for identifying a piece of non-working hardware.]
BTW, this is a DEC FDDI card, those were usually the ones sold by HP/Compaq.
DEFPA is known not to work on 2.6 ... on any platform. Which is kind
of sad since
all the BSDs have a working driver and it is a nice piece of hardware.
I contacted the maintainer a couple of months ago, but he was busy
with other projects,
and he said he wanted to completely rewrite the driver, but it is
rather low priority for him
right now. I also gave it a try to fix the driver, but I soon found
out that it is more effort
to fix the driver than to rewrite it from scratch.
The only supported and working FDDI cards under linux are the ones
from Sysconnect,
however those cards have a GPL-only driver and there exists no driver
for the BSDs.
> To work around this, you have two options:
>
> 1 - Remove the expansion card, if possible.
>
> 2 - Boot single user, (append single to the PALO/IPL command line)
> 2.1 - Edit/create /etc/hotplug/blacklist.d/parisc and
> add the module name (probably defxx) to the file.
>
> If other modules give you grief, repeat the step to blacklist them.
>
> I'll make sure this module doesn't get built into the kernel, the driver
> is probably written non-portably, and thus fails miserably on 'odd'
> hardware like parisc.
No, it's much worse than that :-P
5 years of bit-rot leaves its marks.
Greetings,
Max
[-- 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
prev parent reply other threads:[~2005-12-31 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 15:51 [parisc-linux] J2240 - Almost there Craig D. Lansing
2005-12-30 20:09 ` Kyle McMartin
2005-12-31 3:16 ` Craig D. Lansing
2005-12-31 3:30 ` Kyle McMartin
2005-12-31 16:21 ` Craig D. Lansing
2005-12-31 18:08 ` Grant Grundler
2006-01-01 4:21 ` Craig D. Lansing
2006-01-01 6:32 ` Grant Grundler
2006-01-01 14:15 ` Thibaut VARENE
2006-01-03 1:19 ` Craig D. Lansing
2006-01-03 2:01 ` Matthew Wilcox
2006-01-04 17:43 ` Grant Grundler
2006-01-04 17:49 ` Matthew Wilcox
2006-01-04 18:18 ` Grant Grundler
2006-01-05 4:08 ` Craig D. Lansing
2006-01-03 2:01 ` Craig D. Lansing
2005-12-31 14:43 ` Max Grabert [this message]
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=e6eae0290512310643q523877d9x@mail.gmail.com \
--to=parisc@gmail.com \
--cc=kyle@mcmartin.ca \
--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