to ADSL and I will need to share my
> net. I am at home.
>
> I bought a new PCI card and plug it. But it is not recognized.
>
> In the logs, see below, it appears that it was renamed from eth0 to eth1.
>
> You know if the driver 8139too is really the one for this hard
On Mon, Jun 01, 2009 at 03:43:21PM +, Marcelo Luiz de Laia wrote:
> Here are the outputs of some commands.
What does dmesg show?
Doug.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
not recognized.
In the logs, see below, it appears that it was renamed from eth0 to eth1.
You know if the driver 8139too is really the one for this hardware? What
I could do to configure it?
Here are the outputs of some commands.
:~$ uname -a
Linux maq 2.6.26-2-486 #1 Thu Mar 26 00:13:41 UTC 2009
On 24.04.09 03:24, jida...@jidanni.org wrote:
> At boot with Linux 2.6.26-2-686 I see
> 8139cp :00:0f.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible
> chip
> 8139cp :00:0f.0: Try the "8139too" driver instead.
> 8139too Fast Ethernet driver 0.9.28
>
Michael Biebl writes:
> echo "blacklist 8139cp" >> /etc/modprobe.d/blacklist.conf
Now with the 2.6.29-1-686 kernel none of this is needed! The errors are gone.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
Michael Biebl wrote:
> jida...@jidanni.org wrote:
>> Now in 2.6.29-1-686 it just says
>> 8139cp :00:0f.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible
>> chip, use 8139too
>> I assume "use" here is short for "using" and means "I
jida...@jidanni.org wrote:
> Now in 2.6.29-1-686 it just says
> 8139cp :00:0f.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible
> chip, use 8139too
> I assume "use" here is short for "using" and means "I, the emitter of
> this message, will use
Now in 2.6.29-1-686 it just says
8139cp :00:0f.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible
chip, use 8139too
I assume "use" here is short for "using" and means "I, the emitter of
this message, will use", and not "you, the person reading th
At boot with Linux 2.6.26-2-686 I see
8139cp :00:0f.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp :00:0f.0: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt :00:0f.0[A] -> GSI 18 (level, low) -> IRQ
On 5/14/07, Florian Kulzer <[EMAIL PROTECTED]> wrote:
With 2.6.8 you have:
> ACPI disabled because your bios is from 95 and too old
> You can enable it with acpi=force
> IRQ9: eth0
With 2.6.18, on the other hand:
> ACPI: Core revision 20060707
> ACPI: setting ELCR to 0800 (from 0200)
> ACP
On Sun, May 13, 2007 at 16:17:55 +1000, Adrian Levi wrote:
> After an upgrade from Sarge networking no linger works. I can see no
> reason for it.
>
> I have attached lspci -vvv, dmesg, and ifconfig eth0 and
> /proc/interrupts for both kernels 2.6.8-2-686 works perfectly.
>
> Error message is:
> Ma
shed some light on this problem.
I havn't looked through all your attachments, but do remember on my upgrade
from Woody, through Sarge, and to Etch, having to add 8139too
to /etc/modules.
It's going back a bit now, but may have had something to do with the change
from the 2.4.27 kern
hed some light on this problem.
Actually, no, but this reply is being sent from an etch box with the
same kernel and same 8139too chip/driver that you report (but different
card).
If I can help by posting any output from this box, let me know.
I'm no expert at all, but notice that the kernels a
s
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
8139too Fast Ethernet driver 0.9.27
PCI: Found IRQ 9 for device :00:09.0
eth0: RealTek RTL8139 at 0xde00, 00:11:95:66:17:73, IRQ 9
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link up, 100M
Problem Solved!
I just get a kernel clean, without any change (.tar.bz2), and
recompiled from scratch using my conf file, and the module
8139too.c worked fine, without any problems.
I think the problem is when i changed my old kernel to support
pci, for som
On Fri, Aug 06, 2004 at 05:15:37AM -0300, Leonardo Marques wrote:
> Hi people,
>
> I having problems with the new module 8139too for the Realtek
> 8139 Ethernet card.
>
> I compiled a new kernel (2.4.27-rc4), with support to pci and
> suport for t
On Mon 9 August 2004 23:19, Leonardo Marques wrote:
> On Mon, Aug 09, 2004 at 09:20:38PM -0400, David P James wrote:
> > Try using modconf instead to install the 8139too module. Don't know
> > why it works and insmod and modprobe don't, but I had a similar
> > li
On Mon, Aug 09, 2004 at 09:20:38PM -0400, David P James wrote:
> On Fri 6 August 2004 04:15, Leonardo Marques wrote:
> > Hi people,
> >
> > I having problems with the new module 8139too for the Realtek
> > 8139 Ethernet card.
>
> I know the fe
On Fri 6 August 2004 04:15, Leonardo Marques wrote:
> Hi people,
>
> I having problems with the new module 8139too for the Realtek
> 8139 Ethernet card.
I know the feeling :)
> I compiled a new kernel (2.4.27-rc4), with support to pci and
> suport for th
Hi people,
I having problems with the new module 8139too for the Realtek
8139 Ethernet card.
I compiled a new kernel (2.4.27-rc4), with support to pci and
suport for this realtek card as a module.
When a i give modprobe 8139too, it returns a long error
t;[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] wrote:
> > Hi all,
> >
> >
> > I'm trying to install a DLink DFE-530 TX (Rev-C1) PCI NIC Card on a Woody
> (tried
> > with 2.4.18 kernel), which seems to work with 8139too module (according to
> some
> > post
[EMAIL PROTECTED] wrote:
Hi all,
I'm trying to install a DLink DFE-530 TX (Rev-C1) PCI NIC Card on a Woody (tried
with 2.4.18 kernel), which seems to work with 8139too module (according to some
posts).
I'm wondering if this f module needs other module(s) (or built-in option)
becau
[EMAIL PROTECTED] wrote:
Hi all,
I'm trying to install a DLink DFE-530 TX (Rev-C1) PCI NIC Card on a Woody (tried
with 2.4.18 kernel), which seems to work with 8139too module (according
try via-rhine module.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
On Tue, 20 Apr 2004 16:49:24 +0200
[EMAIL PROTECTED] wrote:
>
> Hi all,
>
>
> I'm trying to install a DLink DFE-530 TX (Rev-C1) PCI NIC Card on a
> Woody (tried with 2.4.18 kernel), which seems to work with 8139too
> module (according to some posts).
> I'm wo
On Tue, 20 Apr 2004 16:49:24 +0200
[EMAIL PROTECTED] wrote:
>
> I'm trying to install a DLink DFE-530 TX (Rev-C1) PCI NIC Card on a
> Woody (tried with 2.4.18 kernel), which seems to work with 8139too
> module (according to some posts).
> I'm wondering if this f mo
Hi all,
I'm trying to install a DLink DFE-530 TX (Rev-C1) PCI NIC Card on a Woody (tried
with 2.4.18 kernel), which seems to work with 8139too module (according to some
posts).
I'm wondering if this f module needs other module(s) (or built-in option)
because I can't get
On Wed, Jan 28, 2004 at 02:24:27AM -, Timothy Paling wrote:
> On Tue, 2004-01-27 at 19:36, Timothy Paling wrote:
> Producing this listing shows that 8139too is not in the list.
>
> modprobe simple reports that it cannot find the module.
>
> How do I proceed further? I
On Wed, 2004-01-28 at 08:28, Timothy Paling wrote:
> The module does not appear in modconf either, however, it does appear in
> menuconf (make menuconf) and there is a .c source file for the module in
> with the kernel source.
>
> How to compile this module therefore is my new question.
>
well,
Hi,
On Wed, 28 Jan 2004, Timothy Paling wrote:
> > to install a kernel module, you must switch to root, then type: modprobe
> >
> >
> > for example: modprobe 8139too
> >
> > you may need to insert the mii module as well.
> >
> The module does n
> On Tue, 2004-01-27 at 19:36, Timothy Paling wrote:
> Producing this listing shows that 8139too is not in the list.
>
> modprobe simple reports that it cannot find the module.
>
> How do I proceed further? I've located the source for the module in the
> Kernel source how
* Timothy Paling <[EMAIL PROTECTED]> [040128 11:29]:
>
> On Tue, 2004-01-27 at 19:36, Timothy Paling wrote:
> Producing this listing shows that 8139too is not in the list.
>
> modprobe simple reports that it cannot find the module.
>
> How do I proceed further?
Rer
rdBus card working. The Cardbus itself is working (I have verified this by
> looking at /var/log/syslog when inserting the card).
>
> I am aware that I need to install the 8139too module, however, I'm
> completely unsure on how to do this.
Two ways kernel modules can be installed (
On Tuesday 27 January 2004 07:24 pm, Timothy Paling wrote:
> On Tue, 2004-01-27 at 19:36, Timothy Paling wrote:
> Producing this listing shows that 8139too is not in the list.
>
> modprobe simple reports that it cannot find the module.
>
> How do I proceed further? I've loc
On Tue, 2004-01-27 at 19:36, Timothy Paling wrote:
Producing this listing shows that 8139too is not in the list.
modprobe simple reports that it cannot find the module.
How do I proceed further? I've located the source for the module in the
Kernel source however, I'm unsure as to
self is working (I have verified this by
> looking at /var/log/syslog when inserting the card).
>
> I am aware that I need to install the 8139too module, however, I'm
> completely unsure on how to do this.
>
If you are using the 2.4.18-bf2.4 kernel, I think that support for tha
inserting the card).
I am aware that I need to install the 8139too module, however, I'm
completely unsure on how to do this.
Anyhelp or advice would be much appreciated.
Tim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Paul William wrote:
> I went through the woody installation. I installed the 2.4.18-bf kernel
> and when I got to the part of the install where you select kernel
> modules the 8139too (realtek 8139 NIC driver) was not there?!?!
The 8139too driver is compiled into the bf24 kernel series
I have a D-Link DFE-530 TX+ ethernet card. On the
D-Link page they offer a linux driver for it, which is
the RTL-8139 driver.
http://support.dlink.com/Products/view.asp?productid=DFE-530TX+
The autoprobe fails. What parameters can I try to make
it work? Please CC to me, as my inbox can't take the
> Hi,
>
> I went through the woody installation. I installed the 2.4.18-bf kernel
> and when I got to the part of the install where you select kernel
> modules the 8139too (realtek 8139 NIC driver) was not there?!?!
>
> I then exited the installation and reinstalled because I n
Hi,
I went through the woody installation. I installed the 2.4.18-bf kernel
and when I got to the part of the install where you select kernel
modules the 8139too (realtek 8139 NIC driver) was not there?!?!
I then exited the installation and reinstalled because I need that
driver. I did my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 12, 2003 at 12:03:02PM -0700, Jeremy Brooks wrote:
> I need to set the eth0 interface to 100MB/Full Duplex. I have added
> append="ether=0,0,0x30,eth0" to lilo.conf and re-run lilo. On reboot,
> it comes up 10MB/Half Duplex.
That particu
On 12 Jun 2003 12:03:02 -0700
Jeremy Brooks <[EMAIL PROTECTED]> wrote:
>
> hi,
> I need to set the eth0 interface to 100MB/Full Duplex. I have added
> append="ether=0,0,0x30,eth0" to lilo.conf and re-run lilo. On reboot,
> it comes up 10MB/Half Duplex.
>
> Is anyone familiar with this driver? A
hi,
I need to set the eth0 interface to 100MB/Full Duplex. I have added
append="ether=0,0,0x30,eth0" to lilo.conf and re-run lilo. On reboot,
it comes up 10MB/Half Duplex.
Is anyone familiar with this driver? Are my options incorrect?
Many thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
On Sun, Mar 09, 2003 at 10:54:53AM +0100, Joan Tur wrote:
> Thanks. Now usb modules and printer module are loaded automatically, but...
> the 8139too module now complains about unresolved symbols 8-?
Hmmm, that's odd. Are you sure that you didn't accidentally install
another c
a 2.4 kernel -- I believe the usb
> support in 2.4 is more complete. (kernel-image-2.4.18-586 for a
> pentium-optimized kernel)
Thanks. Now usb modules and printer module are loaded automatically, but...
the 8139too module now complains about unresolved symbols 8-?
The kernel image loaded
hi
On muy debian/stable P1 home server w/2 realtek NIC, everything works
smoothly with 2.2.20 and rtl8139. But with 2.4.18 and 8139too, the
modprobe dies saying this:
Loading modules: af_packet 8139too 8139too Fast Ethernet driver 0.9.24
PCI: Setting latency timer of device 00:0b.0 to 64
On Tuesday 05 February 2002 12:48 pm, Jason Majors wrote:
[snip]
>
> My friend kelly is having the same problem. We're going to try the 8139too
> for him, because people on the list are suggesting it.
> But I have the same card and never had to use the too on 2.2.
check last mo
On Tue, Feb 05, 2002 at 06:09:48PM -0500, Jason M. Harvey wrote:
> did you happen to ever use two nics in the same pc that used the same
> module?!? i'm wondering if that would work... as long as modules.conf
> has eth0 and eth1 both specified... on the other hand, walking her
> through all this ov
On Tue, Feb 05, 2002 at 04:14:43PM -0500, Stephen Gran wrote:
| > >
| > My friend kelly is having the same problem. We're going to try the 8139too
| > for him, because people on the list are suggesting it.
| > But I have the same card and never had to use the too on 2.2.
| T
s very happy). it defaulted to kernel
> > 2.2.19 (no pre1). her nic was autodetected, and the 8139too module was
> > inserted. now, that's weird- i've never seen (or tried) 8139too on 2.2.x
> > kernels. so, i had her set up her interfaces file, and networking
> > r
she tried
> everything... different irq's, irq settings in bios and PnP. i told her
> how great they worked for me!
> so, i mailed her my woody cd #1 that i downloaded back in november. she
> now has that installed (and is very happy). it defaulted to kernel
> 2.2.19 (no pre1).
everything... different irq's, irq settings in bios and PnP. i told her
how great they worked for me!
so, i mailed her my woody cd #1 that i downloaded back in november. she
now has that installed (and is very happy). it defaulted to kernel
2.2.19 (no pre1). her nic was autodetected, and the 813
e there is a
>reason why 8139too was written (it's newer right?)
The rtl8139 driver has always been experimental. 8139too is the new
driver which is only marked as experimental in the sources and not in
the kernel konfig. 2.4 has 8139too only. See it as
Quoting Emil Pedersen ([EMAIL PROTECTED]):
> While more or less on the subject 8139, could someone please explain the
> differenses between these, and what benefits one might have over the
> other. I've used them both without trouble, but I asume there is a
> reason why 8139too
zwar erkannt, aber nicht korrekt initialisiert wird (kein link
> >beat).
>
> Sorry, didn't mean to post that to the list. I need to wear a paper
> bag for some time.
>
> What I wrote is: 2.2.19 has both rtl8139 and 8139too, and sourceforge
> has a even later 8139too for 2.4.3 w
kein link
>beat).
Sorry, didn't mean to post that to the list. I need to wear a paper
bag for some time.
What I wrote is: 2.2.19 has both rtl8139 and 8139too, and sourceforge
has a even later 8139too for 2.4.3 which fixes an initializing problem
occuring on an older 8139-based card with the 81
On Sun, 1 Apr 2001 10:49:27 +0200, Michael Meskes <[EMAIL PROTECTED]>
wrote:
>On Fri, Mar 30, 2001 at 02:37:23PM -0300, Daniel Toffetti wrote:
>> I have two cheap cards and it worked fine and straightforward for
>
>On my newer machines it worked well too.
>
>> me. The only problem I had was
On Fri, Mar 30, 2001 at 02:37:23PM -0300, Daniel Toffetti wrote:
> I have two cheap cards and it worked fine and straightforward for
On my newer machines it worked well too.
> me. The only problem I had was that I selected a wrong driver the first
> time, then I browsed the drivers disket
I have two cheap cards and it worked fine and straightforward for
me. The only problem I had was that I selected a wrong driver the first
time, then I browsed the drivers diskette and found the right driver, which
is already bundled with the kernel.
Have you compared the sources of
I've been using this driver ever since I got myself soem cheap 100MB cards
and it worked flawlessly so far. But today I tried upgrading an old machine
from 2.2.18 to 2.4.2 and it freezes upon initialization of that driver, no
matter if it is compiled as module or not.
I tried changing the card to
60 matches
Mail list logo
