Ask a Question related to Debian, Design and Development.
-
Robert Tilley #1
RealTek 8139 Problems
When I installed my system with the Debian 3.0 CD, kernel 2.2.0 was installed.
I selected to install the RealTek 8139 drivers and my NIC has been
functioning perfectly.
I've attempted to install 2.4.19, 2.4.21, and 2.6.0-test2. During a
menuconfig, I specify the RealTek 8139 drivers to be installed as part of the
kernel. However, when I reboot into the fresh kernel my NIC is undetected
and I have no internet access. I must reboot into 2.2.0 if my NIC is to be
used. I've even gone so far as to install _all_ RealTek drivers and no luck.
Any ideas?
Bob
--
Comments are most appreciated,
Robert Tilley
--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
Robert Tilley Guest
-
Mac IE DIV problems
i am working on a site (www.skybridgegroup.com) which has an image in a layer positioned over another layer, which reveals the lower image on... -
problems with preLoadNetThing and fileName (was problems with preLoadNetThing and importFileInto)
You don't want to leave the QT member in your cast when you publish your movie - it's not really there, it's linked. When you run the movie it will... -
RealTex 8139 Problem -- Dmesg output
On Sun, 2003-08-03 at 15:54, Andreas Janssen wrote: What's /etc/interfaces? Do you mean /etc/network/interfaces? A copy of that file, plus... -
Realtek RTL8139 PCI Fast Ethernet Adapter
Hi All, I'm a new Debian user. I got a problem on istallation. My network device, Realtek RTL8139 PCI Fast Ethernet Adapter, was not detected.... -
Sound in Linux Debian 3.0 (WOODY) + Realtek ALC650 + problem with ALSA driver
Hello Has anyone tried to setup soundcard AC97 (integrated on motherboard), chipset Realtek ALC650 on Linux Debian 3.0 (WOODY)? There is... -
Donald Spoon #2
Re: RealTek 8139 Problems
Robert Tilley wrote:
On my machine the older rtl8139.o "realtek driver" module worked just> When I installed my system with the Debian 3.0 CD, kernel 2.2.0 was installed.
> I selected to install the RealTek 8139 drivers and my NIC has been
> functioning perfectly.
>
> I've attempted to install 2.4.19, 2.4.21, and 2.6.0-test2. During a
> menuconfig, I specify the RealTek 8139 drivers to be installed as part of the
> kernel. However, when I reboot into the fresh kernel my NIC is undetected
> and I have no internet access. I must reboot into 2.2.0 if my NIC is to be
> used. I've even gone so far as to install _all_ RealTek drivers and no luck.
>
> Any ideas?
>
> Bob
> --
> Comments are most appreciated,
>
> Robert Tilley
>
>
fine with the 2.2.XX series, and the more recent 8139too.o "realtek
driver" module also worked. I normally used the older driver because I
was used to it & it worked. When the 2.4.XX kernels came out the older
driver module (rtl8139.o) didn't seem to be available and I had to
switch to the 8139too.o module. The need for this switch was not
immediately apparent, except I couldn't get my network going with the
new kernel... a sympto similar to yours.
You might check which module you are trying to load in the 2.4.XX kernel
series mentioned and make sure it is the more recent 8139too.o module.
The places to check are in your /etc/modules file and in modconf.
Cheers,
-Don Spoon-
--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
Donald Spoon Guest
-
Ron Johnson #3
Re: RealTek 8139 Problems
On Sun, 2003-08-03 at 17:02, Robert Tilley wrote:
I certainly hope you mean 2.2.20, instead of 2.2.0!!!> When I installed my system with the Debian 3.0 CD, kernel 2.2.0 was installed.
> I selected to install the RealTek 8139 drivers and my NIC has been
> functioning perfectly.
>
> I've attempted to install 2.4.19, 2.4.21, and 2.6.0-test2. During a
> menuconfig, I specify the RealTek 8139 drivers to be installed as part of the
> kernel. However, when I reboot into the fresh kernel my NIC is undetected
> and I have no internet access. I must reboot into 2.2.0 if my NIC is to be
> used. I've even gone so far as to install _all_ RealTek drivers and no luck.
What problems did you have installing 2.4.19 and .21? They are
what you should be running. I have an 8139 working just fine
with 2.4.20.
Besides, how can we help you without specific data, like snippets
from /var/log/syslog and dmesg.
Also, if you are a Linux newbie, or a Linux vet who is more comfortable
with the auto-detection and GUI niceties that other distros offer,
you might want Libranet, instead. It's fully Debian compatible.
[url]http://www.libranet.com/download.html[/url]
--
+-----------------------------------------------------------------+
| Ron Johnson, Jr. Home: [email]ron.l.johnson@cox.net[/email] |
| Jefferson, LA USA |
| |
| "I'm not a vegetarian because I love animals, I'm a vegetarian |
| because I hate vegetables!" |
| unknown |
+-----------------------------------------------------------------+
--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
Ron Johnson Guest
-
Antony Gelberg #4
Re: RealTek 8139 Problems
On Sun, Aug 03, 2003 at 06:02:58PM -0400, Robert Tilley wrote:
Are you sure you are comiling the driver into the kernel, rather than as> When I installed my system with the Debian 3.0 CD, kernel 2.2.0 was installed.
> I selected to install the RealTek 8139 drivers and my NIC has been
> functioning perfectly.
>
> I've attempted to install 2.4.19, 2.4.21, and 2.6.0-test2. During a
> menuconfig, I specify the RealTek 8139 drivers to be installed as part of the
> kernel. However, when I reboot into the fresh kernel my NIC is undetected
> and I have no internet access. I must reboot into 2.2.0 if my NIC is to be
> used. I've even gone so far as to install _all_ RealTek drivers and no luck.
>
> Any ideas?
>
> Bob
> --
> Comments are most appreciated,
>
> Robert Tilley
a module? The 8139 driver changed between 2.2 and 2.4, and is now
called 8139too. You could try a "modprobe 8139too" as root.
Antony
--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
Antony Gelberg Guest



Reply With Quote

