RE: Manually bring up NICs not found at install and/or rebuilding Kernel

2001-09-01 Thread Sebastiaan
High,

On Fri, 31 Aug 2001, John Purser wrote:

 Some success!
 
Great!

 The command I used was modprobe eepro100 and both NIC's came up.  I'm
 running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up
 exactly the same way because of formatting differences.
 
 So where should I put the modprobe info to load it at boot and where should
 I configure the ethernet cards?
 
I suggest you do it the right way (though the utilities). Run 'modconf'
before you have insmodded the modeles. Select in modconf the desired
module and it will be loaded at boot. Then edit /etc/network/interfaces to
configure the cards:

iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255

iface eth1 inet static
address 10.0.0.150
netmask 255.255.255.0
network 10.0.0.0

Greetz, 
Sebastiaan


 Thanks,
 
 John Purser
 
 -Original Message-
 From: John Purser [mailto:[EMAIL PROTECTED]
 Sent: Friday, August 31, 2001 06:03
 To: 'Sebastiaan'
 Cc: 'debian users'
 Subject: RE: Manually bring up NICs not found at install and/or
 rebuilding Kernel
 
 
 Okay, so I want to load a module.  I've got about 15 windows open trying to
 find what module I need and all I'm finding is information on drivers.
 
 What module do I need to support Intel Pro/100B PCI cards?
 
 Thanks,
 
 John Purser
 
 -Original Message-
 From: Sebastiaan [mailto:[EMAIL PROTECTED]
 Sent: Friday, August 31, 2001 05:59
 To: John Purser
 Cc: 'debian users'
 Subject: Re: Manually bring up NICs not found at install and/or
 rebuilding Kernel
 
 
 High,
 
  Hello,
 
  I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither
  one recognizes the PCI NICs.  Red Hat and W2K get them first try but I
 don't
  want either one on this box.
 
  During the last attempted install of Woody I tried using the Configure
  Network alternative but was told that there were no NIC's found which
 means
  I have to load different modules in the kernel before I can configure.  So
  either I dynamically load the modules or I have to rebuild my kernel or
  someone gives me another option.
 
  QUESTIONS:
  Is there any way to bring up my NIC's without rebuilding my Kernel?
 
 Which NIC's are you trying to load?
 
 You might want to do it manually. After the installation process has
 installed device drivers on the computer, swap to the second console and
 activate it. There you go to /target/lib/modules/2.4.9 (or something),
 look for your module and insmod it manually. When that works, go back to
 the first console and continue to configure your network. After
 installation you may want to run 'modconf' or edit /etc/modules to make
 the module auto load.
 
 
  
  Would there be any advantage to installing potato and upgrading to Woody?
  Potato doesn't recognize my NIC's either but at least tasksel works.
 
 AFAIK, this has nothing to do with tasksel. You do not have to install
 additional packages if you want to make a NIC work.
 
 Greetz,
 Sebastiaan
 
  Thanks for the help.
 
  John Purser
 
 
 
  --
  To UNSUBSCRIBE, email to [EMAIL PROTECTED]
  with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
 
 
 
 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 



Manually bring up NICs not found at install and/or rebuilding Kernel

2001-08-31 Thread John Purser
Hello,

I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither
one recognizes the PCI NICs.  Red Hat and W2K get them first try but I don't
want either one on this box.

During the last attempted install of Woody I tried using the Configure
Network alternative but was told that there were no NIC's found which means
I have to load different modules in the kernel before I can configure.  So
either I dynamically load the modules or I have to rebuild my kernel or
someone gives me another option.

QUESTIONS:
Is there any way to bring up my NIC's without rebuilding my Kernel?

I've found a .deb file called kernel-source-2.4.6_2.4.6-1_all.deb at
E:\pool\main\k\kernel-source-2.4.6 on the first CD.  Is this my Kernel
Source?  If so how do I install this file.  My Kernel compiling instructions
assume I'm starting with a .bz2 file.

Any tips/suggestions on rebuilding my Kernel?

Would there be any advantage to installing potato and upgrading to Woody?
Potato doesn't recognize my NIC's either but at least tasksel works.

Thanks for the help.

John Purser




Re: Manually bring up NICs not found at install and/or rebuilding Kernel

2001-08-31 Thread Sebastiaan
High,

 Hello,
 
 I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither
 one recognizes the PCI NICs.  Red Hat and W2K get them first try but I don't
 want either one on this box.
 
 During the last attempted install of Woody I tried using the Configure
 Network alternative but was told that there were no NIC's found which means
 I have to load different modules in the kernel before I can configure.  So
 either I dynamically load the modules or I have to rebuild my kernel or
 someone gives me another option.
 
 QUESTIONS:
 Is there any way to bring up my NIC's without rebuilding my Kernel?
 
Which NIC's are you trying to load?

You might want to do it manually. After the installation process has
installed device drivers on the computer, swap to the second console and
activate it. There you go to /target/lib/modules/2.4.9 (or something),
look for your module and insmod it manually. When that works, go back to
the first console and continue to configure your network. After
installation you may want to run 'modconf' or edit /etc/modules to make
the module auto load.


  
 Would there be any advantage to installing potato and upgrading to Woody?
 Potato doesn't recognize my NIC's either but at least tasksel works.
 
AFAIK, this has nothing to do with tasksel. You do not have to install
additional packages if you want to make a NIC work.

Greetz,
Sebastiaan

 Thanks for the help.
 
 John Purser
 
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 



RE: Manually bring up NICs not found at install and/or rebuilding Kernel

2001-08-31 Thread John Purser
Okay, so I want to load a module.  I've got about 15 windows open trying to
find what module I need and all I'm finding is information on drivers.

What module do I need to support Intel Pro/100B PCI cards?

Thanks,

John Purser

-Original Message-
From: Sebastiaan [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2001 05:59
To: John Purser
Cc: 'debian users'
Subject: Re: Manually bring up NICs not found at install and/or
rebuilding Kernel


High,

 Hello,

 I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither
 one recognizes the PCI NICs.  Red Hat and W2K get them first try but I
don't
 want either one on this box.

 During the last attempted install of Woody I tried using the Configure
 Network alternative but was told that there were no NIC's found which
means
 I have to load different modules in the kernel before I can configure.  So
 either I dynamically load the modules or I have to rebuild my kernel or
 someone gives me another option.

 QUESTIONS:
 Is there any way to bring up my NIC's without rebuilding my Kernel?

Which NIC's are you trying to load?

You might want to do it manually. After the installation process has
installed device drivers on the computer, swap to the second console and
activate it. There you go to /target/lib/modules/2.4.9 (or something),
look for your module and insmod it manually. When that works, go back to
the first console and continue to configure your network. After
installation you may want to run 'modconf' or edit /etc/modules to make
the module auto load.


 
 Would there be any advantage to installing potato and upgrading to Woody?
 Potato doesn't recognize my NIC's either but at least tasksel works.

AFAIK, this has nothing to do with tasksel. You do not have to install
additional packages if you want to make a NIC work.

Greetz,
Sebastiaan

 Thanks for the help.

 John Purser



 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]




RE: Manually bring up NICs not found at install and/or rebuilding Kernel

2001-08-31 Thread John Purser
Some success!

The command I used was modprobe eepro100 and both NIC's came up.  I'm
running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up
exactly the same way because of formatting differences.

So where should I put the modprobe info to load it at boot and where should
I configure the ethernet cards?

Thanks,

John Purser

-Original Message-
From: John Purser [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2001 06:03
To: 'Sebastiaan'
Cc: 'debian users'
Subject: RE: Manually bring up NICs not found at install and/or
rebuilding Kernel


Okay, so I want to load a module.  I've got about 15 windows open trying to
find what module I need and all I'm finding is information on drivers.

What module do I need to support Intel Pro/100B PCI cards?

Thanks,

John Purser

-Original Message-
From: Sebastiaan [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2001 05:59
To: John Purser
Cc: 'debian users'
Subject: Re: Manually bring up NICs not found at install and/or
rebuilding Kernel


High,

 Hello,

 I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither
 one recognizes the PCI NICs.  Red Hat and W2K get them first try but I
don't
 want either one on this box.

 During the last attempted install of Woody I tried using the Configure
 Network alternative but was told that there were no NIC's found which
means
 I have to load different modules in the kernel before I can configure.  So
 either I dynamically load the modules or I have to rebuild my kernel or
 someone gives me another option.

 QUESTIONS:
 Is there any way to bring up my NIC's without rebuilding my Kernel?

Which NIC's are you trying to load?

You might want to do it manually. After the installation process has
installed device drivers on the computer, swap to the second console and
activate it. There you go to /target/lib/modules/2.4.9 (or something),
look for your module and insmod it manually. When that works, go back to
the first console and continue to configure your network. After
installation you may want to run 'modconf' or edit /etc/modules to make
the module auto load.


 
 Would there be any advantage to installing potato and upgrading to Woody?
 Potato doesn't recognize my NIC's either but at least tasksel works.

AFAIK, this has nothing to do with tasksel. You do not have to install
additional packages if you want to make a NIC work.

Greetz,
Sebastiaan

 Thanks for the help.

 John Purser



 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]



Re: Manually bring up NICs not found at install and/or rebuilding Kernel

2001-08-31 Thread dman
On Fri, Aug 31, 2001 at 06:23:01AM -0600, John Purser wrote:
| Some success!
| 
| The command I used was modprobe eepro100 and both NIC's came up.  I'm

The driver/module is eepro100 :-).  Driver and kernel module are
basically synonomous.

| running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up
| exactly the same way because of formatting differences.
| 
| So where should I put the modprobe info to load it at boot and where should
| I configure the ethernet cards?

In /etc/modutils/some name you like put
alias eth0 eepro100
alias eth1 eepro100

and run 'update-modules'.  update-modules will grab info from
everything in /etc/modutils and write it to /etc/modules.conf (and
overwrite any changes you may have made to /etc/modules.conf).  

Also you need to configure the interfaces in /etc/network/interfaces.
Include a line that says auto eth0 and auto eth1 to bring up the
interfaces at boot time.  The alias line tells the kernel to use the
'eepro100' module whenever something tries to access either 'eth0' or
'eth1'.

HTH,
-D



Re: Manually bring up NICs not found at install and/or rebuilding Kernel

2001-08-31 Thread Wayne Topa
John Purser([EMAIL PROTECTED]) is reported to have said:
 Hello,
 
 I've repeatedly installed Woody (vanilla) and Potato on my IBM and neither
 one recognizes the PCI NICs.  Red Hat and W2K get them first try but I don't
 want either one on this box.
 
 During the last attempted install of Woody I tried using the Configure
 Network alternative but was told that there were no NIC's found which means
 I have to load different modules in the kernel before I can configure.  So
 either I dynamically load the modules or I have to rebuild my kernel or
 someone gives me another option.
 

I used potato, with Bunk's 2.4.x packages, as a stepping stone to
woody and had minimal problems in the upgrade.  I think that the 2.4.x
packages made that possible.

 QUESTIONS:
 Is there any way to bring up my NIC's without rebuilding my Kernel?

Only if a 'grep /usr/src/linux/.config' or if that isn't there a grep
of the config in /boot shows
CONFIG_EEXPRESS_PRO=y or =m
If not, then the only way is to rebuild the kernel (Usually a smart
move anyway as the stock kernel has much more compiled in then most
users require).  The smaller kernel the better.
 
 I've found a .deb file called kernel-source-2.4.6_2.4.6-1_all.deb at
 E:\pool\main\k\kernel-source-2.4.6 on the first CD.  Is this my Kernel
 Source?  If so how do I install this file.  My Kernel compiling instructions
 assume I'm starting with a .bz2 file.
 
 Any tips/suggestions on rebuilding my Kernel?

I am running kernel-2.4.9 on both potato and woody.  Each of then has
this in /usr/src/linux/Documentation/Configure.help:

EtherExpress PRO/100 support
CONFIG_EEPRO100
  If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
  card, say Y and read the Ethernet-HOWTO, available from
  http://www.linuxdoc.org/docs.html#howto .

  This driver is also available as a module ( = code which can be
  inserted in and removed from the running kernel whenever you want).
  The module will be called eepro100.o. If you want to compile it as a
  module, say M here and read Documentation/modules.txt as well as
  Documentation/networking/net-modules.txt.

Either compile the kernel using the Debian Way, with make kpkg or the 
old fashioned way -make dep ; make clean ; make bzImage

There are many posts on just how to do this in the archives or by
doing a google search.  Running Debian is much different then running
Red Hat or W2k.  You have to be willing to learn things other then
clicking on a button.  You will be much wiser in the long run.
-- 
You have a tendency to feel you are superior to most computers
___



Re: Manually bring up NICs not found at install and/or rebuilding Kernel

2001-08-31 Thread Vineet Kumar
* John Purser ([EMAIL PROTECTED]) [010831 10:34]:
 Some success!
 
 The command I used was modprobe eepro100 and both NIC's came up.  I'm
 running a Red Hat 7.1 box also but I'm hesitant to set the Debian box up
 exactly the same way because of formatting differences.
 
 So where should I put the modprobe info to load it at boot and where should
 I configure the ethernet cards?
 

See dman's reply for what you should do now. For future reference (and
for other readers) you can get your NIC up and running in the initial
installation procedure at the point where it asks you to choose which
kernel modules you want to load. choose eepro100 (in your case, or
whatever your NIC is in other readers' cases) under the 'net' category,
and it will be loaded instantly (so that you can complete the install
via http or ftp) and set up to load at every boot automatically.

-- 
Vineet   http://www.anti-dmca.org
Unauthorized use of this .sig may constitute violation of US law.
echo Qba\'g gernq ba zr\! |tr 'a-zA-Z' 'n-za-mN-ZA-M'


pgpU4zUthM5W5.pgp
Description: PGP signature


Re: Rebuilding Kernel

2000-03-15 Thread Neil L. Roeth
On Mar 13, Andrei Ivanov ([EMAIL PROTECTED]) wrote:
   Hi,
   I need to rebuild the kernel.  My
   system does not have the 
   /usr/src/kernel-source-2.2.14/.config
   file.  How do you create that file
   based on your current kernel?. 
   Thanks for your reply.
   
   -shane
  
  cd /usr/src/linux
  make menuconfig OR
  make xconfig
  

Why isn't the config file corresponding to the kernel that comes with
the distribution provided?  The first time I had to recompile a
kernel, it was rather daunting to have to figure out all of the
various options; it would have been much easier if I could have known
I was just making an incremental change to the current kernel.

-- 
Neil L. Roeth
[EMAIL PROTECTED]


Re: Rebuilding Kernel

2000-03-15 Thread Brad
On Tue, Mar 14, 2000 at 10:36:17PM -0500, Neil L. Roeth wrote:
 
 Why isn't the config file corresponding to the kernel that comes with
 the distribution provided?  The first time I had to recompile a
 kernel, it was rather daunting to have to figure out all of the
 various options; it would have been much easier if I could have known
 I was just making an incremental change to the current kernel.

Have you looked in /boot? Every Debian packaged kernel i've used puts
the configuration there, named config-x.y.z (where x.y.z is the kernel
version number).

Kernels created with kernel-package install their config files into
/boot in the same manner.


-- 
  finger for GPG public key.


pgpVLcsujJrQF.pgp
Description: PGP signature


Rebuilding Kernel

2000-03-14 Thread Shane

Hi,
I need to rebuild the kernel.  My
system does not have the 
/usr/src/kernel-source-2.2.14/.config
file.  How do you create that file
based on your current kernel?. 
Thanks for your reply.

-shane


--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.


Re: Rebuilding Kernel

2000-03-14 Thread Andrei Ivanov
 Hi,
 I need to rebuild the kernel.  My
 system does not have the 
 /usr/src/kernel-source-2.2.14/.config
 file.  How do you create that file
 based on your current kernel?. 
 Thanks for your reply.
 
 -shane

cd /usr/src/linux
make menuconfig OR
make xconfig

RTFM before doing so, about all the options that you can select in kernel
setup.
Andrew
-
 Andrei S. Ivanov  
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
 http://scorpio.dynodns.net -|
 http://scorpio.myip.org-|   --All the pages bundled together.
 http://arshes.dyndns.org   -|  If one does not work, try another :)
 UIN 12402354

 To get my GnuPG public key, go to 
 scorpio.dynodns.net/GnuPG   
 scorpio.myip.org/GnuPG
 arshes.dyndns.org/GnuPG
-


Re: Rebuilding Kernel

2000-03-14 Thread ktb
I'm not entirely sure by your message if you have the kernel source you want
to install.  Take a look at the FAQ,

http://www.debian.org/doc/FAQ/debian-faq-11.html

if your still having trouble.
hth,
kent


- Original Message -
From: Shane [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Monday, March 13, 2000 10:34 PM
Subject: Rebuilding Kernel



 Hi,
 I need to rebuild the kernel.  My
 system does not have the
 /usr/src/kernel-source-2.2.14/.config
 file.  How do you create that file
 based on your current kernel?.
 Thanks for your reply.

 -shane


 --== Sent via Deja.com http://www.deja.com/ ==--
 Share what you know. Learn what you don't.


 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] 
/dev/null



Error while rebuilding kernel

1996-06-03 Thread Paul Barrett

First, I want to thank everyone involved with Debian for doing an
excellent job.  I far prefer my Debian system at home to my current
Sun or previous Ultrix systems at work.  Three cheers for DEBIAN!

Now my question.

While trying to build a custom kernel under 0.93R6, I get an error
about bootsect.o not found.  Looking through the make file, it would
appear that this binary should be compiled when necessary from
bootsect.s, but this doesn't appear to happen.  What's the problem
here?

I've never experience problems build a kernel before, so this seems
awfully strange.

Cheers,
Paul

|~|
| Paul Barrett  -  Astrophysicist  -  Universities Space Research Association |
| Compton Observatory Science Support Center  |
| NASA/Goddard SFC phone: 301-286-1108Guk a 'mzimba, sala 'nhliziyo |
| Code 660.1,  FAX:   301-286-1681(body grow old, but heart   |
| Greenbelt,MD 20771   [EMAIL PROTECTED]   remain behind) |
| http://lheawww.gsfc.nasa.gov/users/barrett/CV.html  |
 ~