networking help with WhiteBox 3

Lleb_KCir · 08-10-2004, 01:03 AM

ok thanks for trying.

Tinkster · 08-10-2004, 01:50 AM

Give's the output of
lspci
ifconfig
lsmod
please.... :)

Cheers,
Tink

J.W. · 08-10-2004, 02:46 AM

Quote:

Originally posted by Lleb_KCir
....im going to be a bit of a pain here, but this thread is over 24hrs old.

That's not really the point. The LQ Rule stating "please don't bump your own threads until 24 hours have passed" is intended to apply to the timestamp of the latest response, not the initial post. In other words, it's not like a blackout period exists for only the first 24 hours, and then it becomes an open season, free-for-all on bumping your own posts whenever you feel like it.

Please keep in mind that the LQ membership is worldwide, and with over 100K members, there are literally tens of thousands of LQ'ers in other time zones who may not have seen your post yet -- give them a chance to respond before bumping again. Additionally, repeated bumps within a thread tends to clutter it up tremendously, and will bury any useful replies amidst an ocean of useless posts, thus making it harder for everyone to find relevant information. For these reasons, members are asked to avoid bumping their own threads in less than 24 hours. Thanks -- J.W.

homey · 08-10-2004, 08:13 AM

I don't think lspci ifconfig or lsmod will show information on his nics at this point because they never showed up at boot time in the output of dmesg.

That's why I suggested using the Knoppix cd. Since Knoppix did find the nics, then running the command lspci would tell what model of nic you have. For example on this box, I get these lines...
00:09.0 Ethernet controller: Winbond Electronics Corp W89C940
00:0a.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]

So for the Intel nic I would google to find an rpm driver for the model 82557 nic.

I did see lots of hits on those kind of drivers and instructions on setting those up including use of insmod / modprobe to get things going.

Tinkster · 08-10-2004, 02:08 PM

Homey,

if his /usr/share/pci.ids is too old to know the
cards lspci will still list them as unknown devices
and you can find them by their numeric ID ...

Alternatively he could just grab a more recent
file from the kernel source and replace the out-
dated one ...

And it's premature to conclude that any of them
won't display anything in the first place.

Cheers,
Tink

Lleb_KCir · 08-11-2004, 03:55 PM

ill post that info tonight when i get home. please bare with some potential misspelling as ill have to retype it all into an other computer to post it.

win32sux · 08-11-2004, 04:54 PM

that's a lot of typing... can't you save the outputs to a text file on a floppy??

=)

Lleb_KCir · 08-11-2004, 04:57 PM

if i knew how i would. i can scroung up a floppy or 2.

win32sux · 08-11-2004, 05:07 PM

become root... then mount the floppy... then redirect the outputs to text files on the floppy...

here's how to do it (for example):

mount /mnt/floppy

lspci > /mnt/floppy/lspci.txt

ifconfig > /mnt/floppy/ifconfig.txt

lsmod > /mnt/floppy/lsmod.txt

good luck...

Lleb_KCir · 08-11-2004, 05:31 PM

ok, so i take it the
'>'

is what will push the responce to those commands to a specific file. very nice. ty.

win32sux · 08-11-2004, 05:35 PM

yeah, it sends the output to a file instead of to your console...

=)

Lleb_KCir · 08-11-2004, 08:13 PM

neet. love to learn things. next question, how do i format a floppy for linux? i have done so for M$ only.

Tinkster · 08-11-2004, 09:54 PM

If you have a fat-formatted floppy that should
do just fine ...

Other than that:
man -k floppy | grep format

Cheers,
Tink

Lleb_KCir · 08-11-2004, 11:24 PM

thanks for all the info on how to do this stuff, here are the 3 txt files from the floppy:

Code:

eth0     
 Link encap:Ethernet  HWaddr 00:60:97:26:6E:02  
  
        inet addr:192.168.2.200  Bcast:192.168.2.255  Mask:255.255.255.0
   
       UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        
  RX packets:1 errors:0 dropped:0 overruns:0 frame:0
         
 TX packets:0 errors:0 dropped:0 overruns:1 carrier:1
      
    collisions:0 txqueuelen:1000 
         
 RX bytes:504 (504.0 b)  TX bytes:0 (0.0 b)
  
        Interrupt:11 Base address:0xdf00 

lo  
      Link encap:Local Loopback  
         
 inet addr:127.0.0.1  Mask:255.0.0.0
      
    UP LOOPBACK RUNNING  MTU:16436  Metric:1
  
        RX packets:269 errors:0 dropped:0 overruns:0 frame:0
    
      TX packets:269 errors:0 dropped:0 overruns:0 carrier:0
   
       collisions:0 txqueuelen:0 
       
   RX bytes:22370 (21.8 Kb)  TX bytes:22370 (21.8 Kb)

Code:

Module                 
 Size  Used by    Not tainted
nls_iso8859-1      
     3516   1  (autoclean)
nls_cp437           
    5148   1  (autoclean)
vfat                
   13004   1  (autoclean)
fat                 
   38872   0  (autoclean) [vfat]
parport_pc   
          19076   1  (autoclean)
lp           
           9028   0  (autoclean)
parport      
          37088   1  (autoclean) [parport_pc lp]
autofs  
               13364   0  (autoclean) (unused)
3c59x   
               30928   1 
floppy               
  58160   2  (autoclean)
sg                   
  36972   0  (autoclean)
sr_mod              
   18136   0  (autoclean)
microcode       
        5848   0  (autoclean)
ide-scsi    
           12592   0 
ide-cd             
    35680   0 
cdrom                 
 33696   0  [sr_mod ide-cd]
keybdev  
               2976   0  (unused)
mousedev   
             5524   1 
hid                 
   22212   0  (unused)
input               
    5920   0  [keybdev mousedev hid]
ehci-hcd    
           20136   0  (unused)
usb-uhci        
       26412   0  (unused)
usbcore             
   79424   1  [hid ehci-hcd usb-uhci]
ext3    
               88104   2 
jbd                 
   52464   2  [ext3]
ata_piix              
  4872   3 
libata              
   35940   0  [ata_piix]
sd_mod  
               13648   6 
scsi_mod  
            110376   5  [sg sr_mod ide-scsi ata_piix libata sd_mod]

Code:

00:00.0 Host bridge: Intel Corp.
 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:01.0 PCI bridge: 
Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: 
Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02)
00:1d.1 USB Controller:
 Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: 
Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: 
Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02)
00:1d.7 USB Controller:
 Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: 
Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev c2)
00:1f.0 ISA bridge: 
Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
00:1f.1 IDE interface: 
Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02)
00:1f.2 IDE interface:
 Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02)
00:1f.3 SMBus:
 Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller:
 Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:00.0 VGA compatible controller:
 ATI Technologies Inc R300 AD [Radeon 9500 Pro]
01:00.1 Display controller: 
ATI Technologies Inc R300 AD [Radeon 9500 Pro] (Secondary)
02:03.0 FireWire (IEEE 1394): 
VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
02:04.0 RAID bus controller:
 VIA Technologies, Inc. VT6410 ATA133 RAID controller (rev 06)
02:05.0 Ethernet controller: 
3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
02:0b.0 Ethernet controller: 
3Com Corporation 3c905 100BaseTX [Boomerang]

again, thank you all for the help and efforts. this is the #1 thing i love about linux. some day i hope to be able to return this level of help to others that will be in the shoes i am in today.

win32sux · 08-11-2004, 11:43 PM

Quote:

Originally posted by Lleb_KCir
inet addr:192.168.2.200 Bcast:192.168.2.255 Mask:255.255.255.0

are you able to ping yourself??

ping 192.168.2.200

(or whatever ip address your card has next time you boot it)

now see if you can ping your router... you can see your routers ip address like this:

route -n

Quote:

3c59x 30928 1

okay, this is the module for your 3c905...

Quote:

02:05.0 Ethernet controller:
3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
02:0b.0 Ethernet controller:
3Com Corporation 3c905 100BaseTX [Boomerang]

you have TWO cards??