LinuxQuestions.org - Switching From Wireless to Plugged Problem.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Switching From Wireless to Plugged Problem. (https://www.linuxquestions.org/questions/slackware-14/switching-from-wireless-to-plugged-problem-413284/)

Switching From Wireless to Plugged Problem.

I'm running Slackware 10.1 (2.4.29) on an IBM T21. I usually connect to my home network via a wireless card. I decided to plug in an ethernet cable into the back and I don't know what to do from there.

ifconfig just gives me the loopback network.

Code:

lo      Link encap:Local Network

        innet addr:127.0.0.1 Mask:255.0.0.0

        UP LOOKBACK RUNNING MTU:16436  Metric:1

...

when i connect wirelessly it is on eth0.

Any ideas?

To get linux to show you all interfaces (even the ones that are not configured), run:

Code:

ifconfig -a

Have you ever used your ethernet plug on that laptop? Maybe the drivers aren't loaded for it.

If you have, and the command above revealed your ethernet card is visible, then you just need to assign it an ip address , like this:

Code:

ifconfig eth1 192.168.1.50

(assuming it's detected as eth1)
then 'ifconfig' should show it, along with it's new ip address you gave it.

If that works, just add a default route, and set it to your router:

Code:

route add default gw 192.168.1.1

I used it before but I reinstalled linux since then. When i installed slackware on it (the 2nd time) I had the wireless card plugged in. So maybe the drivers didn't get installed the 2nd time around?

ifconfig -a still only shows up loopback.

If you have activated hotplug, then the network card drivers would have loaded automatically. If not, look at the output of

Code:

lspci -v

and try to determine what type of card you have, then add "modprobe" commands like this

Code:

/sbin/modprobe <your_card_module>

to the end of /etc/rc.d/rc.modules script, so that the drivers for your cards are loaded by Slackware when it boots

Eric

lspci -v gives

Code:

00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)

        Flags: bus master, medium devsel, latency 64

        Memory at f8000000 (32-bit, prefetchable) [size=64M]

        Capabilities: [a0] AGP version 1.0



00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) (prog-if 00 [Normal decode])

        Flags: bus master, 66Mhz, medium devsel, latency 128

        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64

        Memory behind bridge: f0000000-f7ffffff



00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)

        Subsystem: IBM: Unknown device 0130

        Flags: bus master, medium devsel, latency 168, IRQ 11

        Memory at 50000000 (32-bit, non-prefetchable) [size=4K]

        Bus: primary=00, secondary=02, subordinate=04, sec-latency=176

        Memory window 0: 18000000-183ff000 (prefetchable)

        Memory window 1: 18400000-187ff000

        I/O window 0: 00004000-000040ff

        I/O window 1: 00004400-000044ff

        16-bit legacy interface ports at 0001



00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)

        Subsystem: IBM: Unknown device 0130

        Flags: bus master, medium devsel, latency 168, IRQ 11

        Memory at 50100000 (32-bit, non-prefetchable) [size=4K]

        Bus: primary=00, secondary=05, subordinate=07, sec-latency=176

        Memory window 0: 18800000-18bff000 (prefetchable)

        Memory window 1: 18c00000-18fff000

        I/O window 0: 00004800-000048ff

        I/O window 1: 00004c00-00004cff

        16-bit legacy interface ports at 0001



00:03.0 Communication controller: Lucent Microelectronics WinModem 56k (rev 01)

        Subsystem: IBM: Unknown device 018c

        Flags: medium devsel, IRQ 11

        Memory at e8101000 (32-bit, non-prefetchable) [size=256]

        I/O ports at 1c00 [size=8]

        I/O ports at 1800 [size=256]

        Capabilities: [f8] Power Management version 2



00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)

        Subsystem: IBM: Unknown device 0153

        Flags: bus master, slow devsel, latency 64, IRQ 11

        Memory at e8100000 (32-bit, non-prefetchable) [size=4K]

        Memory at e8000000 (32-bit, non-prefetchable) [size=1M]

        Capabilities: [40] Power Management version 2



00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)

        Flags: bus master, medium devsel, latency 0



00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master])

        Flags: bus master, medium devsel, latency 64

        I/O ports at 1c10 [size=16]



00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])

        Flags: bus master, medium devsel, latency 64, IRQ 11

        I/O ports at 1c20 [size=32]



00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)

        Flags: medium devsel, IRQ 9



01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 13) (prog-if 00 [VGA])

        Subsystem: IBM ThinkPad T20

        Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11

        Memory at f0000000 (32-bit, non-prefetchable) [size=128M]

        Expansion ROM at <unassigned> [disabled] [size=64K]

        Capabilities: [dc] Power Management version 1

        Capabilities: [80] AGP version 1.0

i can see the 56k modem. but not the ethernet.

If that is all "lspci -v" gave you, are you certain there actually is a network card in that T20?
I owned a T20 a couple of years back, and I remember that it originally had just a winmodem chip on it's mini-pci card. Even though there is a RJ45 jack on the back, that does not necessarily mean it is connected to anything :-)

I had it swapped for a 3Com network/modem combi card eventually so I could get rid of the cardbus ethernet card I had been using until then.

So - you might want to check what's actually in there by turning the T20 over and remove the small cover plate, after unscrewing the single screw (might be hidden under a wad of rubber). The mini-pci card underneath will either have one cable leading to the phone jack on the back, or two cables - the second running to the adjacent RJ45 network jack.

In case you are using a Cardbus/PCMCIA card - I don't think that would show up in a "lspci" listing.

Eric