On Friday 20 April 2001 18:45, Francois Romieu wrote:
> I assume nothing is overclocked or whatever
Nothing is overclocked.
> Could you try this patch (more output during the loop):
Tried it. The (lengthy) log is attached.
The interrupt is triggered when the other side initiates a request.
eth0
Stefan Jaschke <[EMAIL PROTECTED]> écrit :
> On Friday 20 April 2001 16:33, Francois Romieu wrote:
> > Stefan Jaschke <[EMAIL PROTECTED]> ecrit :
> > > I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles
> > > and works without problems.
> > > This gives me a workable solution :
On Friday 20 April 2001 16:33, Francois Romieu wrote:
> Stefan Jaschke <[EMAIL PROTECTED]> ecrit :
> > I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles
> > and works without problems.
> > This gives me a workable solution :-)
>
> Thanks for the info.
> Now, why do you get so
Stefan Jaschke <[EMAIL PROTECTED]> ecrit :
[...]
> I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles and works
>without
> problems.
> This gives me a workable solution :-)
Thanks for the info.
Now, why do you get so much Receive Queue Empty indications...
--
Ueimor
-
To
Em Fri, Apr 20, 2001 at 02:07:11PM +0200, Stefan Jaschke escreveu:
>
> 'A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> [EMAIL PROTECTED]:
> unrouteable mail domain "skyld.com"'
>
s/skyld/scy
On Friday 20 April 2001 12:25, Francois Romieu wrote:
> What happen's if you compile 2.4.2 epic100 driver in a 2.4.3 tree (I) ?
> I would really appreciate if you could give a look at (I).
I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles and works
without
problems.
This g
On Friday 20 April 2001 13:33, Jeff Garzik wrote:
> Here's a suggestion to try: go through epic100.c and write 0x12
> unconditionally to MIICfg register. Right now it is conditional: if
> (dev->if_port...) out(0x12,ioaddr+MIICfg);
I changed all three such lines. Same behavior as before.
You a
Stefan Jaschke wrote:
> I also noted that there are substantial differences between the original epic100.c at
> http://www.scyld.com/network/epic100.html and the version included with 2.4.3.
> Who did these changes?
Francois (PCI DMA) and me (everything else). The scyld version does not
support
On Friday 20 April 2001 12:25, Francois Romieu wrote:
> Summary:
> Arnd Bergmann:
> orig epic100"DMA mapped epic100 (any version)"
> (<=2.4.0-ac9)
> VT8363ok fscked but ok after bios update
>
> Daniel Nofftz:
> 2.4.2
Hi,
it seems the epic100 driver broke between 2.4.2 and 2.4.3.
I reloaded the epic100 module with the parameter "debug=6".
Unfortunately, I cannot make much out of the log:
Apr 20 12:47:01 antares kernel: epic100.c:v1.11 1/7/2001 Written by Donald Becker
<[EMAIL PROTECTED]>
Apr 20 12:47:01 antar
Stefan Jaschke <[EMAIL PROTECTED]> ecrit :
[...]
> I don't believe the motherboard or the BIOS have anything to do with, simply
It may give a clue because the machine I wrote this mail from is a
2.4.3 + 2*EtherPower II it looks rather fine (old asus motherbord, BX,
backuped peaceful prod server
On Wednesday 18 April 2001 20:40, Francois Romieu wrote:
> Hello,
>
> Oliver Teuber <[EMAIL PROTECTED]> écrit :
> [...]
>
> > 00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev
> > 06) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
> > 00:07.0 ISA bridge:
On Tuesday 17 April 2001 18:45, Oliver Teuber wrote:
> my smc epic100 card does not work with the device driver from
> linux-2.4.3-ac7.
> linux-2.2.19 works fine for me.
Same behavior here. Just want to add that the 2.4.0 kernel (SuSE 7.1) also
works fine.
Stefan
-
To unsubscribe from this list:
hi
my smc epic100 card does not work with the device driver from
linux-2.4.3-ac7.
linux-2.2.19 works fine for me.
please take a look at my /var/log/messages ...
Apr 17 09:37:27 olibox kernel: epic100.c:v1.11 1/7/2001 Written by Donald Becker
<[EMAIL PROTECTED]>
Apr 17 09:37:27 olibox kernel:
14 matches
Mail list logo
