No eth0 . pleeze help!
Lukas
A while ago, I installed woody from the 3 intallation CDs on a 97/98
Compaq Deskpro 4000.
Then I bought a bigger harddisk and went through the intallation
again.
Only this time, it seems to me no ethernet driver was installed. I'm
not really well informed about drivers.
What I can see from KDE's system info for example, is, that the
ethernet controller was identified (a Compaq 10/100 something
something), but when i say (as root)
ifconfig
it shows me sl0 and lo , but no eth0.
when I try something like
ifconfig eth0 10.0.0.150 netmask 255.255.255.0 broadcast 10.0.0.255 up
it tells me there is no such device.
And indeed in /dev/ there is nothing that looks like eth ..
I thought, maybe on the first installation I had chosen Vanilla
instead of IDE PCI , so I did the whole install again on a different
partition, same result.
(On the original installation(with the small harddisk), it had worked,
and I was able to get on the internet with DSL)
Is my interpretation correct that the driver was not installed? .. It
seems a contradiction, since the ethernet controller was detected. Or
is the driver just hidden away somewhere and I need to bind it into
the kernel?
(I haven't done anything like that yet...)
If the driver is somewhere on one of the intallation CDs, can I just
get it from there (copy) without running the intall stuff from the CD?
scared, tired, and fed up,
Lukas
Werner Steinbrenner
> A while ago, I installed woody from the 3 intallation CDs on a 97/98
> Compaq Deskpro 4000.
> Then I bought a bigger harddisk and went through the intallation
> again.
Bad idea. Next time make a backup with Mondo. This is much more easier
than installing the system again. (See Mondo Documentation --> Google
is your Friend :) )
> Only this time, it seems to me no ethernet driver was installed. I'm
> not really well informed about drivers.
> What I can see from KDE's system info for example, is, that the
> ethernet controller was identified (a Compaq 10/100 something
> something)
Big error. As far as I know Kde only does something like a scanpci and
shows what chipsets or Vendor Information that had been found. That
doesn't mean that the Hardware is correctly installed. I am sorry if I
am talking bullshit now (pleas correct me if I am wrong), but as I
said as far as I know KDE does nothing else than a scanpci or
something like that.
> ifconfig
> it shows me sl0 and lo , but no eth0.
> when I try something like
> ifconfig eth0 10.0.0.150 netmask 255.255.255.0 broadcast 10.0.0.255 up
> it tells me there is no such device.
> And indeed in /dev/ there is nothing that looks like eth ..
Hm, if the driver for your eth card is correctly installed then you
should go to /dev/ and then make a MAKEDEV eth. But test for the
driver before you do that.
> I thought, maybe on the first installation I had chosen Vanilla
> instead of IDE PCI , so I did the whole install again on a different
> partition, same result.
Never do this agaein, this is Linux and not Windows. ;)
> Is my interpretation correct that the driver was not installed? .. It
> seems a contradiction, since the ethernet controller was detected. Or
> is the driver just hidden away somewhere and I need to bind it into
> the kernel?
We don't call that installation. We actually hang driver-modules into
the Kernel. Hmm if your eth controler is standard hardware there
should be a standard module for it. Start as root modconf (better you
don't do that under X do it on a real shell, just type
modconf). Inside modconf you can comfortably activate driver
modules. Go to the eth section and look for your card. If you dont
find the correct chipset take a look on google.
> (I haven't done anything like that yet...)
Bad idea. ;)
> If the driver is somewhere on one of the intallation CDs, can I just
> get it from there (copy) without running the intall stuff from the CD?
As I said before, this is not windows!! Whether the module is
supported by the Kernel or not, but as you said the eth controller had
worked correctly it should be standard hardware.
Be careful whether your old version was an older kernel. So you have
to recompile the kernel so that the hardware is supported but I dont
think that you have to do that.
> scared, tired, and fed up,
Drink a cup of coffe, smoke a cigarett, take a breath, sleep with your
girlfriend and take a look to google. ;) I wan't to tell you that you
don't have to be scared. The Debian Users will help you and if I was
too stupid to do that there will be others who can give you a better
support. You are using DSL right? So I suppose you come from
Germany. If I am right there is an excelent Debian doku free for
reading in the Internet. www.openoffice.de/linux/buch. But a really
good investigation is the book from Peter Ganten "Debian GNU/Linux
Installation und Administration". Take a look to amazon.
I wish you the best for your peoblem. Stay tuned to Debian it is a
really good Linux.
Cheers
Werner
--
Werner Steinbrenner ( wstein-...@sbox.tugraz.at )
Graz - University of Technology
ICQ: 107499048 / west
Werner Steinbrenner
> A while ago, I installed woody from the 3 intallation CDs on a 97/98
> Compaq Deskpro 4000.
> Then I bought a bigger harddisk and went through the intallation
> again.
Bad idea. Next time make a backup with Mondo. This is much more easier
than installing the system again. (See Mondo Documentation --> Google
is your Friend :) )
> Only this time, it seems to me no ethernet driver was installed. I'm
> not really well informed about drivers.
> What I can see from KDE's system info for example, is, that the
> ethernet controller was identified (a Compaq 10/100 something
> something)
Big error. As far as I know Kde only does something like a scanpci and
shows what chipsets or Vendor Information that had been found. That
doesn't mean that the Hardware is correctly installed. I am sorry if I
am talking bullshit now (pleas correct me if I am wrong), but as I
said as far as I know KDE does nothing else than a scanpci or
something like that.
> ifconfig
> it shows me sl0 and lo , but no eth0.
> when I try something like
> ifconfig eth0 10.0.0.150 netmask 255.255.255.0 broadcast 10.0.0.255 up
> it tells me there is no such device.
> And indeed in /dev/ there is nothing that looks like eth ..
Hm, if the driver for your eth card is correctly installed then you
should go to /dev/ and then make a MAKEDEV eth. But test for the
driver before you do that.
> I thought, maybe on the first installation I had chosen Vanilla
> instead of IDE PCI , so I did the whole install again on a different
> partition, same result.
Never do this agaein, this is Linux and not Windows. ;)
> Is my interpretation correct that the driver was not installed? .. It
> seems a contradiction, since the ethernet controller was detected. Or
> is the driver just hidden away somewhere and I need to bind it into
> the kernel?
We don't call that installation. We actually hang driver-modules into
the Kernel. Hmm if your eth controler is standard hardware there
should be a standard module for it. Start as root modconf (better you
don't do that under X do it on a real shell, just type
modconf). Inside modconf you can comfortably activate driver
modules. Go to the eth section and look for your card. If you dont
find the correct chipset take a look on google.
> (I haven't done anything like that yet...)
Bad idea. ;)
> If the driver is somewhere on one of the intallation CDs, can I just
> get it from there (copy) without running the intall stuff from the CD?
As I said before, this is not windows!! Whether the module is
supported by the Kernel or not, but as you said the eth controller had
worked correctly it should be standard hardware.
Be careful whether your old version was an older kernel. So you have
to recompile the kernel so that the hardware is supported but I dont
think that you have to do that.
> scared, tired, and fed up,
Drink a cup of coffe, smoke a cigarett, take a breath, sleep with your
Werner Steinbrenner
> A while ago, I installed woody from the 3 intallation CDs on a 97/98
> Compaq Deskpro 4000.
> Then I bought a bigger harddisk and went through the intallation
> again.
Bad idea. Next time make a backup with Mondo. This is much more easier
than installing the system again. (See Mondo Documentation --> Google
is your Friend :) )
> Only this time, it seems to me no ethernet driver was installed. I'm
> not really well informed about drivers.
> What I can see from KDE's system info for example, is, that the
> ethernet controller was identified (a Compaq 10/100 something
> something)
Big error. As far as I know Kde only does something like a scanpci and
shows what chipsets or Vendor Information that had been found. That
doesn't mean that the Hardware is correctly installed. I am sorry if I
am talking bullshit now (pleas correct me if I am wrong), but as I
said as far as I know KDE does nothing else than a scanpci or
something like that.
> ifconfig
> it shows me sl0 and lo , but no eth0.
> when I try something like
> ifconfig eth0 10.0.0.150 netmask 255.255.255.0 broadcast 10.0.0.255 up
> it tells me there is no such device.
> And indeed in /dev/ there is nothing that looks like eth ..
Hm, if the driver for your eth card is correctly installed then you
should go to /dev/ and then make a MAKEDEV eth. But test for the
driver before you do that.
> I thought, maybe on the first installation I had chosen Vanilla
> instead of IDE PCI , so I did the whole install again on a different
> partition, same result.
Never do this agaein, this is Linux and not Windows. ;)
> Is my interpretation correct that the driver was not installed? .. It
> seems a contradiction, since the ethernet controller was detected. Or
> is the driver just hidden away somewhere and I need to bind it into
> the kernel?
We don't call that installation. We actually hang driver-modules into
the Kernel. Hmm if your eth controler is standard hardware there
should be a standard module for it. Start as root modconf (better you
don't do that under X do it on a real shell, just type
modconf). Inside modconf you can comfortably activate driver
modules. Go to the eth section and look for your card. If you dont
find the correct chipset take a look on google.
> (I haven't done anything like that yet...)
Bad idea. ;)
> If the driver is somewhere on one of the intallation CDs, can I just
> get it from there (copy) without running the intall stuff from the CD?
As I said before, this is not windows!! Whether the module is
supported by the Kernel or not, but as you said the eth controller had
worked correctly it should be standard hardware.
Be careful whether your old version was an older kernel. So you have
to recompile the kernel so that the hardware is supported but I dont
think that you have to do that.
> scared, tired, and fed up,
Drink a cup of coffe, smoke a cigarett, take a breath, sleep with your
Lukas
Meanwhile, I did a lot of reading up on the whole driver arch. in
Linux.
Naively, I had assumed that the install process would actually find
out by itself what the machine's ethernet controller is ... there's a
Linux Newbie for you.
After some searching on the the net it became clear that the Compaq
Netelligent .. is actually a TI Thunderlan chipset.
Now I understand that all the drivers from the CDs are actually on the
HD in /etc/lib/modules and all I had to do was insmod tlan.
When I actually did it, I didn't understand about insmod yet, so I
went back to the installation CDs and did the whole thing again with
the 2.4... kernel, which I guess is a good idea anyways. Picked the
tlan from the list and tada! : Ethernet.
So, ethernet works now, it's back to dealing with apt and the like..
Thanks for all the info, and the pointer to the online book!
Lukas
Werner Steinbrenner <wstein-...@sbox.tugraz.at> wrote in message news:<87smxoo...@sbox.tugraz.at>...
Werner Steinbrenner
> Thanks for all the info, and the pointer to the online book!
I am happy that I was able to give you a little help. It's good that
you told me that you read my posting an waht you have done with it, so
I see that postings are not for nothing. Was I right that you are
German or German speaking? OK thats all for now. Stay tuned. :)
King regards
Werner Steinbrenner
--
Werner Steinbrenner ( wst...@sbox.tugraz.at )