Re: WLAN - SMC2632W

From: Christian Weerts (chw@ffis.de)
Date: Thu Nov 28 2002 - 22:31:42 CET

  • Next message: Thomas Kuehling: "Kurzbrief zu der LUGO auf pro-linux.de"

    * Tobias Pielsticker <tpielsticker@web.de> [021128 17:41]:
    >> Ein Auszug aus /etc/network/interfaces und die Ausgabe von ifconfig
    >> könnte uns auch weiterhelfen. Evtl. wäre noch ein dmesg (als root)
    >> interessant.
    >
    > Auszug aus /etc/network/interfaces:
    > auto lo
    > iface lo inet loopback
    > # The first network card - this entry was created during the Debian
    > installation
    > # (network, broadcast and gateway are optional)
    > # automatically added when upgrading
    > auto eth0
    > iface eth0 inet static
    > address 192.168.0.2
    > netmask 255.255.255.0
    > network 192.168.0.0
    > broadcast 192.168.0.255
    > gateway 192.168.0.1
    > auto eth1
    > iface eth1 inet dhcp
    > wireless_mode managed
    > wireless_nick this_one
    > wireless_essid Uni Paderborn
    > wireless_enc on
    > wlan_ng_key0 (meine Karten-Nummer)
    >
    >
    > Auszug aus dmesg:
    > Linux version 2.4.18
    > mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
    > mtrr: detected mtrr type: Intel
    > PCI: PCI BIOS revision 2.10 entry at 0xfbfee, last bus=2
    > PCI: Using configuration type 1
    > PCI: Probing PCI hardware
    > Unknown bridge resource 2: assuming transparent
    > PCI: Discovered primary peer bus 08 [IRQ]
    > PCI: Using IRQ router PIIX [8086/248c] at 00:1f.
    > PCI: Found IRQ 11 for device 00:1f.1
    > PCI: Sharing IRQ 11 with 02:00.0
    > isapnp: Scanning for PnP cards...
    > isapnp: No Plug & Play device found
    > Linux NET4.0 for Linux 2.4
    > Initializing RT netlink socket
    > IA-32 Microcode Update Driver: v1.09 <tigran@veritas.com>
    > parport0: PC-style at 0x378 (0x778) [PCSPP(,...)]
    > parport0: irq 7 detected
    > i2c-core.o: i2c core module
    > i2c-dev.o: i2c /dev entries driver module
    > i2c-core.o: driver i2c-dev dummy driver registered.
    > i2c-proc.o version 2.6.1 (20010825)
    > pty: 256 Unix98 ptys configured
    > PCI: Found IRQ 11 for device 00:1f.6
    > PCI: Sharing IRQ 11 with 00:1f.5
    > lp0: using parport0 (polling).
    > PCI: Enabling device 00:1f.1 (0005 -> 0007)
    > PCI: Found IRQ 11 for device 00:1f.1
    > PCI: Sharing IRQ 11 with 02:00.0
    > PIIX4: chipset revision 1
    > PIIX4: not 100% native mode: will probe irqs later
    > ide0: BM-DMA at 0xbfa0-0xbfa7, BIOS settings: hda:DMA, hdb:pio
    > ide1: BM-DMA at 0xbfa8-0xbfaf, BIOS settings: hdc:DMA, hdd:pio
    > i2o: Checking for PCI I2O controllers...
    > I2O configuration manager v 0.04.
    > PCI: Found IRQ 11 for device 02:00.0
    > PCI: Sharing IRQ 11 with 00:1f.1
    > 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
    > 02:00.0: 3Com PCI 3c905C Tornado at 0xec80. Vers LK1.1.16
    > PPP generic driver version 2.4.1
    > PCI: Sharing IRQ 11 with 02:01.1
    > PCI: Found IRQ 11 for device 02:01.1
    > PCI: Sharing IRQ 11 with 02:01.0
    > Intel PCIC probe: not found.
    > Databook TCIC-2 PCMCIA probe: not found.
    > usb.c: registered new driver hub
    > Yenta IRQ list 06b8, PCI irq11
    > Socket status: 30000006
    > Yenta IRQ list 06b8, PCI irq11
    > Socket status: 30000006
    > PCI: Found IRQ 11 for device 00:1d.0
    > PCI: Sharing IRQ 11 with 01:00.0
    > PCI: Setting latency timer of device 00:1d.0 to 64
    > IP Protocols: ICMP, UDP, TCP, IGMP
    > IP: routing cache hash table of 2048 buckets, 16Kbytes
    > TCP: Hash tables configured (established 16384 bind 16384)
    > PCI: Found IRQ 11 for device 00:1f.5
    > PCI: Sharing IRQ 11 with 00:1f.6
    > PCI: Setting latency timer of device 00:1f.5 to 64
    > cs: IO port probe 0x0c00-0x0cff: clean.
    > cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x817 0x828-0x837
    > 0x840-0x84f 0x860-0x877 0x880-0x88f 0x898-0x89f 0x8a8-0x8cf 0x8e0-0x8ff
    > cs: IO port probe 0x0100-0x04ff: excluding 0x270-0x277 0x4d0-0x4d7
    > cs: IO port probe 0x0a00-0x0aff: clean.
    >
    >
    > Auszug aus ifconfig:
    > eth0 Protokoll:Ethernet Hardware Adresse (meine Adresse)
    > inet Adresse:192.168.0.2 Bcast:192.168.0.255 Maske:255.255.255.0
    > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:84 errors:0 dropped:0 overruns:0 carrier:84
    > Kollisionen:0 Sendewarteschlangenlänge:100
    > RX bytes:0 (0.0 b) TX bytes:5040 (4.9 KiB)
    > Interrupt:11 Basisadresse:0xec80
    >
    > lo Protokoll:Lokale Schleife
    > inet Adresse:127.0.0.1 Maske:255.0.0.0
    > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > RX packets:44 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
    > Kollisionen:0 Sendewarteschlangenlänge:0
    > RX bytes:3854 (3.7 KiB) TX bytes:3854 (3.7 KiB)

    Hmm, der große Kenner in Sachen Netzwerkkonfiguration, speziell WLAN,
    bin ich nicht, aber er wenn bei dmesg und ifconfig nicht einmal eth1
    anzeigt, dann passen m. E. die Kernelmodule nicht. Bist Du dir sicher
    dass es die richtigen Module sind?

    Gruss,
            Christian



    This archive was generated by hypermail 2.1.4 : Thu Nov 28 2002 - 22:31:47 CET