how do you configure hardware without kudzu?

thrice · 08-13-2003, 04:50 AM

how do i configure my nic in slackware? i moved from redhat 9.0 to slackware 9.0 today because i've heard so many people swear by slackware, and i wanted to switch before i got too comfortable with redhat's simplicity. in redhat after installing the drivers for my nforce nic, kudzu would recognize it during bootup and configure it for me. now i have no idea how to configure it the hard way. can anyone help? i'd appreciate it a lot

MasterC · 08-13-2003, 04:56 AM

What NIC do you have?

And I really didn't ever care for kudzu personally, always though Mandrake's way of dealing with new hardware was a much better approach

Anyway, post up what you get from typing:
lspci -v

Or at least tell us which module you used in RH.

Cool

MasterC · 08-13-2003, 04:57 AM

Moving to the Slackware Forum

Cool

thrice · 08-13-2003, 11:06 AM

ok when i type lspci -v the nic shows up as nVidia Corporation nForce Ethernet Controller. in redhat after it was installed and configured it would show up as nvnet. i hope this is the information you were asking for. thanks again

MasterC · 08-14-2003, 12:19 AM

Ok, so it looks like you'll just have to grab the NForce drivers from www.nvidia.com and compile/install them.

Follow the directions in the README with it, and if you get stuck, and you can find the answer from a search, feel free to post up!

Cool

thrice · 08-14-2003, 05:29 AM

well yes i've compiled and installed the drivers, but how do i activate them or whatever? i've followed the same steps that i did with redhat but kudzu would take over at this point and my ethernet card would magically work. i don't see my card listed in rc.modules, and when i modprobe nvnet it doesn't find it, so i'm stuck. thanks for stickin with me here. sorry about the newbieness. =)

MasterC · 08-14-2003, 05:35 AM

No problem

Was there any errors during the compiling? If you modprobe nvnet, and you installed the drivers, it should return with a happy blank line (return you to bash prompt, meaning it worked

).

Can you post up your:
/etc/modules.conf
So we can see if any changes were made? Also, did you compile all features in the Nvidia Nforce drivers? I remember taking a peak at the source a while ago, they were seperated into seperate packages.

And when you modprobe nvnet, can you post up the actual error? Along with:
uname -r
ls -l /lib/modules
ls -l /usr/src
And
/etc/lilo.conf
So we can get a good feel for your system?

If you can group them up with the [ CODE ] tags, that'd be cool (it's just to make them all look neat when displayed on the screen here).

Cool

Cool

thrice · 08-14-2003, 07:48 AM

oh i guess modprobe did work then. when i type modprobe nvnet it doesn't give me any errors at all, but when i am shutting down and booting up it says something like 'modprobe: modprobe: Can't locate module nvnet.0~' several times. *sigh*

and yeah after making everything that came with the tar file, a few new folders showed up. one was nvnet, and i ran make install from within nvnet, and it got through with no errors, so i think i did that right

here's all the info you asked for

Code:

uname -r 
 2.4.20

Code:

ls -l /lib/modules 
total 4
drwxr-xr-x    4 root     root         4096 Aug 12 20:30 2.4.20

Code:

ls -l /usr/src 
total 8
drwxr-xr-x    3 root     root         4096 Aug 13 04:04 nvidia
drwxr-xr-x    7 root     root         4096 Dec 12  2002 rpm

this is my lilo.conf past the global section

Code:

# DOS bootable partition config begins
other = /dev/hda1
  label = WinXP
  table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda3
  label = Linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

i tried looking at /etc/modules.conf, but it says its 0 bytes and that nautilus doesn't have anything that can view it. when i type vi /etc/modules.conf it comes up completely blank. what does this mean?
thanks again for helping this poor pathetic newb =)

thrice · 08-14-2003, 07:51 AM

oops...code tags didn't work out quite right sorry =)

MasterC · 08-14-2003, 07:59 AM

Don't worry about the code tags, it wasn't as bad as if this were something like SuSE RedHat or Mandrake

Slim...

Ok, well what does:
lsmod (LSMOD) lowercase show you then (after the boot up)?

It looks like everything is pretty much in order, the only thing I don't see is the kernel source, and it struck me that Slack 9 didn't have that included (and was suprising ). Anyway, let's see lsmod and then we'll pretty much have an idea of how to proceed.

Cool

thrice · 08-14-2003, 01:22 PM

alright here ya go

Code:

root@Home:~# lsmod
Module                  Size  Used by    Tainted: P
keybdev                 1952   0  (unused)
mousedev                4212   1
hid                    18596   0  (unused)
usbmouse                2008   0  (unused)
input                   3200   0  [keybdev mousedev hid usbmouse]
usb-ohci               18856   0  (unused)
ehci-hcd               14632   0  (unused)
usbcore                58144   1  [hid usbmouse usb-ohci ehci-hcd]
nvnet                  26368   0  (unused)
emu10k1                61288   1
ac97_codec              9512   0  [emu10k1]
soundcore               3332   4  [emu10k1]
emu10k1-gp              1352   0  (unused)
gameport                1452   0  [emu10k1-gp]
pcmcia_core            38112   0
ide-scsi                8048   0
ntfs                   51040   1  (autoclean)

i see nvnet in there laughing at me. now what? thanks again

thrice · 08-14-2003, 11:08 PM

what does 'Module Size Used by Tainted: P' mean?
i've read other posts where people show the output of lsmod on their systems and it says 'Not Tainted'. tainted doesn't sound like a good thing. can that have something to do with my problems?

MasterC · 08-15-2003, 12:56 AM

The code tag needs to have the spaces removed

The [ CODE ] has spaces between code and the bracket, in the actual code tag, there are no spaces.

Ok..

Module Size Used by Tainted
Is explaining the different sections of the listings of a module. It's the 'header' that shows each category.

nvnet is loaded, so now we just need to configure your IP and eth0. You can use netconfig to do this, or you can run it by hand. To edit the script by hand, open up:
/etc/rc.d./rc.inet1
In your favorite text editor. If you obtain your IP from DHCP then comment all the lines except:
USE_DHCP=yes

The rest is history. Save and exit, and then, as root type:
/etc/rc.d/rc.inet1
And it should go through and setup your internet for you. When it's done, you should have a working connection, you can check by typing:
ifconfig
If it's not working, post up any errors, and what you see when you type:
ifconfig

Cool

thrice · 08-15-2003, 01:54 AM

yayy! i am now connected to my network although i still can't get online. i'm sure i can figure it out though. i bet i just have the dns ip wrong or something trivial like that. at least i can connect to my router's firmware. i already had eth0 configured, just didn't know to run rc.inet1. still not used to the fact that files other than .exes and .coms can execute =)

i really appreciate your help. didn't think anyone would stick with me for so many posts =) i made a small donation to the forum to keep such a great source for information and help available. definitely gonna donate more in the future. haven't seen one negative post yet and everyone seems to be very helpful and understanding to one another. thanks again!

thrice · 08-15-2003, 02:44 AM

i am now posting from my linux system

one last thing. how do i make /etc/rc.d/rc.inet1 run automatically at bootup? as it is i have to run it every time i get inside linux