On Wednesday 05 April 2006 18:41, Paul Johnson wrote:
> On Saturday 25 March 2006 12:43, Oliver Jato wrote:
> > i think this could be done with udev rules, though i only used them to
> > always have the same device aliases for my external fw disks.
> >
> > here you'll find out how to write udev rul
On Saturday 25 March 2006 12:43, Oliver Jato wrote:
> i think this could be done with udev rules, though i only used them to
> always have the same device aliases for my external fw disks.
>
> here you'll find out how to write udev rules:
> http://reactivated.net/writing_udev_rules.html
>
> and thi
On 3/25/06, Tyson Varosyan <[EMAIL PROTECTED]> wrote:
Using Debian command mode 2.6 kernel.My NIC keeps jumping around between eth0 and eth1 every so often when Ireboot. It is real annoying! How do I get it to stick to be the same all thetime? It is conflicting with a firewire controller...
I had a
On Sat, 25 Mar 2006 11:09:28 -0800
> My NIC keeps jumping around between eth0 and eth1 every so often when I
> reboot. It is real annoying! How do I get it to stick to be the same all the
> time? It is conflicting with a firewire controller...
My last go around with the network issue w
Tyson Varosyan wrote:
Using Debian command mode 2.6 kernel.
My NIC keeps jumping around between eth0 and eth1 every so often when I
reboot. It is real annoying! How do I get it to stick to be the same all the
time? It is conflicting with a firewire controller...
Try ifrename:
debian
i think this could be done with udev rules, though i only used them to
always have the same device aliases for my external fw disks.
here you'll find out how to write udev rules:
http://reactivated.net/writing_udev_rules.html
and this is a snippet i found on a web site:
# cat /etc/udev/network.r
]
Sent: Saturday, March 25, 2006 11:52 AM
To: Tyson Varosyan
Cc: debian-user@lists.debian.org
Subject: Re: How do I make my NIC pick the same ETH port every time?
> Using Debian command mode 2.6 kernel.
>
> My NIC keeps jumping around between eth0 and eth1 every so often when I
> reboot
> Using Debian command mode 2.6 kernel.
>
> My NIC keeps jumping around between eth0 and eth1 every so often when I
> reboot. It is real annoying! How do I get it to stick to be the same all
> the
> time? It is conflicting with a firewire controller...
>
what i would do if i
Tyson Varosyan wrote:
> Using Debian command mode 2.6 kernel.
>
> My NIC keeps jumping around between eth0 and eth1 every so often when I
> reboot. It is real annoying! How do I get it to stick to be the same all the
> time? It is conflicting with a firewire controller...
>
Th
-Original Message-
From: Paul Johnson [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 25, 2006 11:29 AM
To: debian-user@lists.debian.org
Subject: Re: How do I make my NIC pick the same ETH port every time?
On Saturday 25 March 2006 11:09, Tyson Varosyan wrote:
> Using Debian command mode
On Saturday 25 March 2006 11:09, Tyson Varosyan wrote:
> Using Debian command mode 2.6 kernel.
>
> My NIC keeps jumping around between eth0 and eth1 every so often when I
> reboot. It is real annoying! How do I get it to stick to be the same all
> the time? It is conflicting
Using Debian command mode 2.6 kernel.
My NIC keeps jumping around between eth0 and eth1 every so often when I
reboot. It is real annoying! How do I get it to stick to be the same all the
time? It is conflicting with a firewire controller...
Tyson Varosyan
Technical Manager, Uptime Technical
As I am now reading the changelog for the recent 2.2.20-i386 kernel update
(2.2.20-5woody5) I see:
*This effectively removes all *-scylid.o modules
I know the natsemi.c is available from Scylid computing, therefore, does the new
2.2.20 kernel binary not provide the natsemi LKM?
If my novice h
Running kernel is: kernel-image-2.2.20-5woody5
I believe there was a recent security update (2 March) to the 2.2.20 kernel.
>
> which kernel do you run now ? the version is the same or is it different from
> that you run before and used to
> work. You could post a dpkg -l | grep kernel, too.
which kernel do you run now ? the version is the same or is it different from that you
run before and used to
work. You could post a dpkg -l | grep kernel, too.
Andrea
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I use my Debian system for data backup (rdiff-backup) and to maintain plenty of
external drive space (Samba). Yes, this is the heart of my home office computer
network; unfortunately as a Mechanical Engineer, most of the application software I
need, particular for customer interface, runs on MS.
Trying to do my first kernel compile because my nic isn't supported on
any of the ones on the distribution CD's. Anyway I have an onboard
Broadcom 4401. When I run make menuconfig it isn't listed but a Tigon
9 is.
1) Is the Tigon 9 the name of the boxed-plugin card with the same
> portion mine wasn't listed. I have the source from the manufacturer.
> How do I add that to the mix?
Just compile the manufacturers source as a module after you finish
compiling the kernel and load in at boot up by adding it to
/etc/modules.
>
>
> Mark Healey
> [EMAIL PROTECTED]
>
> Giving
Preamble: I no working networking or X please don't send suggestions
that require those to be working.
I'm going to go through Kents 10 step procedure to compiling the linux
kernel. I ran into trouble at step 7. I was pretty much taking the
default questions I don't understand. Anyway when it
Hello Brian,
Am 02:19 2002-12-01 -0500 hat Brian Kendig geschrieben:
>Ethernet port powered by a 3Com 3C905 Fast Etherlink XL 10/100 chip.
A realy good NIC ;-))
Works every time...
>Problem is, the Debian 3.0 installation disks have no driver for this
>network interface. I want to use floppies
On 01 Dec 2002, 02:19:16, Brian Kendig wrote:
>
>
> I have a Dell Latitude CPi laptop computer with a Dell Latitude C/Port
> dock. The laptop has no network connectivity, but the dock provides an
> Ethernet port powered by a 3Com 3C905 Fast Etherlink XL 10/100 chip.
>
> Problem is, the Debian
On Sun, Dec 01, 2002 at 02:19:16AM -0500, Brian Kendig wrote:
| I have a Dell Latitude CPi laptop computer with a Dell Latitude C/Port
| dock. The laptop has no network connectivity, but the dock provides an
| Ethernet port powered by a 3Com 3C905 Fast Etherlink XL 10/100 chip.
The driver is "3
Brian Kendig said:
> I have a Dell Latitude CPi laptop computer with a Dell Latitude C/Port
> dock. The laptop has no network connectivity, but the dock provides an
> Ethernet port powered by a 3Com 3C905 Fast Etherlink XL 10/100 chip.
>
> Problem is, the Debian 3.0 installation disks have no driv
I have a Dell Latitude CPi laptop computer with a Dell Latitude C/Port
dock. The laptop has no network connectivity, but the dock provides an
Ethernet port powered by a 3Com 3C905 Fast Etherlink XL 10/100 chip.
Problem is, the Debian 3.0 installation disks have no driver for this
network inter
On Sat, Jan 27, 2001 at 10:46:57AM -, Henry Gomersall wrote:
> I have a D-Link DFE-520TX ethernet card connecting me, via a cable modem to
> the internet. I wish to install debian over the internet. I have installed
> the base system fine, and it all works (i assume) as it should. However,
>
On Sat, 27 Jan 2001, Henry Gomersall wrote:
> I have a D-Link DFE-520TX ethernet card connecting me, via a cable modem to
> ..
> This particular card cannot be selected from the list of NICs during
> installation (of the base system from the rescue disk). This then means I
> ..
> (ftp.dlinknet.com/
I do not know the solution but following may help if this is pci card.
# cat /proc/pci|grep -ie ethernet
or # cat /proc/pci|less
This gives actual chip used on the NIC then you can decide which
driver to use. I have Kingston Card and Linksys card but they
use same family of chip.
In my case
I have a D-Link DFE-520TX ethernet card connecting
me, via a cable modem tothe internet. I wish to install debian over the
internet. I have installedthe base system fine, and it all works (i assume)
as it should. However,This particular card cannot be selected from the list
of NICs duringins
I have an old 486SX25 with 16MB of RAM and a SMC 8013WC NIC, which worked
under the 2.0.36 kernel, but when I upgraded to potato, WD.O tells me that
there is no card installed. When I boot back into DOS and run the config
utility, it says that the EEPROM was trashed and rewrites it. I
downloaded
I have a problem with my NIC.
ifconfig reports that HWaddr is 00:00:21:CE:18:CF
http://www.cavebear.com/CaveBear/Ethernet/ says that this 21 is SC&C (PAM
Soft&Hardware also reported).
Can you point me to their home page ?
30 matches
Mail list logo
