Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "B. Douglas Hilton" <bdhilton@charter.net>
To: Andreas Seltenreich <s_selten@informatik.uni-karlsruhe.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PCI Intel EtherExpressPro100 strangeness on C200 machine.
Date: Sat, 17 Aug 2002 23:33:14 -0400	[thread overview]
Message-ID: <3D5F157A.7070207@charter.net> (raw)
In-Reply-To: 20020818031227.GA32603@gate450.dyndns.org

Yes I made a monolithic kernel, so it rebuilt eepro100.c

Prior, I was using a stock Debian vmlinux-2.4.18-32 kernel
so there is a good chance that the Debian packager had made
the same modification to the source.



Andreas Seltenreich wrote:
> * B. Douglas Hilton <bdhilton@charter.net> [2002-08-18 04:01]:
> 
>>I tried your suggestions and built a new kernel, but
>>it still behaves as it did prior to the modification.
> 
> 
> Just to be sure, you did rebuild the eepro100 module too?
> 
> I'm using the nic for hours now and it is working perfectly.
> 

Hmmm....

> 
>>To summarize (with eepro100 in PCI slot ):
>>
>> - can ping using a dotted quad
>> - cannot ping using dns
>> - can ftp login to another machine on my LAN
>> - when I try to list files or download it locks up.
> 
> 
> With the original module (2.4.19-pa2) I wasn't able to receive ip packets
> larger than approx 150 bytes. For example a ping -s 100  went through
> while ping -s 200 didn't. 
> 
> 
>>This is a major headache. I don't believe that the Debian 3.0
>>cdrom will boot on the C200, and without network I can't
>>upgrade the 0.9.3 cdrom. Its a catch-22!
> 
> 
> Btw. the diff was from 2.4.19-pa2. Maybe there have been other changes
> if you are using an older kernel.
> 

I guess I will try that one then. Thanks.

> The address of the maintainer Andrey V. Savochkin <saw@saw.sw.com.sg>
> seems to be broken. So no help from there.
> 
> regards
> andreas
> 

  reply	other threads:[~2002-08-18  3:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-17 20:32 [parisc-linux] PCI Intel EtherExpressPro100 strangeness on C200 machine B. Douglas Hilton
2002-08-17 22:37 ` Andreas Seltenreich
2002-08-18  2:01   ` B. Douglas Hilton
2002-08-18  3:12     ` Andreas Seltenreich
2002-08-18  3:33       ` B. Douglas Hilton [this message]
2002-08-18  5:16   ` Grant Grundler
2002-08-18 15:55     ` B. Douglas Hilton
2002-08-19 23:00       ` B. Douglas Hilton
2002-08-19 23:58         ` Grant Grundler
2002-08-20  0:04           ` Michael S.Zick
2002-08-20  0:18             ` Matt Taggart
2002-08-20  1:51               ` B. Douglas Hilton
2002-08-20  2:28                 ` B. Douglas Hilton
2002-08-20  0:18   ` Grant Grundler
2002-08-20  8:23     ` Harri Haataja
2002-08-20 12:58       ` Andreas Seltenreich
2002-08-26 18:14   ` Grant Grundler
2002-08-30  6:37   ` Grant Grundler
2002-09-07  0:58     ` [parisc-linux] Opinions on desktop environments Derek Engelhaupt
2002-09-07  1:43       ` Alan Cox
2002-09-07  2:29         ` alaskan
2002-09-07  4:33       ` B. Douglas Hilton
2002-09-07  4:33       ` B. Douglas Hilton
2002-09-07  5:22         ` Derek Engelhaupt

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=3D5F157A.7070207@charter.net \
    --to=bdhilton@charter.net \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=s_selten@informatik.uni-karlsruhe.de \
    /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