On Thu, 2002-09-05 at 15:57, Arvin C. Burgos wrote: > based on my experience, try to remove your lancard then boot your >linux box without that hardware. > remove it during kudzu detection, then turn it off. insert again that lancard then >add it again to your system. > hope this will help > > Arvin > Network Administrator > Menusystem, Inc. > (032)2535827
The logic behind your suggestion actually work for me once. But what i did was i opened the /etc/sysconfig/hwconf and looked for the config for the network. You will see the section separated by a single dash on a line. The network config is specified by the string "class: NETWORK". Sample class: NETWORK bus: PCI detached: 0 device: eth driver: 3c59x desc: "3Com Corporation|3c905 100BaseTX [Boomerang]" vendorId: 10b7 deviceId: 9050 subVendorId: 0000 subDeviceId: 0000 pciType: 1 I deleted this section, and the extra dash, then I run kudzu (as root) on the command line. I've only done this on a RH box HTH -- -- .--. Mariano A. Sobida Jr. ( () ) Q Linux Solutions, Inc. `--\\ A Philippine Open Source Solutions Co. office: (632) 894-3592 http://www.q-linux.com ------------------------------------------------------- "If a packet hits a pocket on a socket on a port And the bus is interrupted as a very last resort And the address of the memory makes the data link abort Then the socket packet pocket has an error to report." - RaveN ------------------------------------------------------- _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
