PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Usb Wlan -> Linksys wusb54g



MATI
24.05.07, 22:30
Hallo,

mein System:

800 Mhz
256 RAM

OpenSuse 10.2

Der Adapter ist per usb angeschlossen.
Ich habe per yast folgendes das prism2.usb Modul geladen und damit auf drahtlos gesetzt.

ifconfig liefert:

eth0 ...
lo ...

er zeigt mir kein wlan0 an.

iwlist scan zeigt:
lo ...
eth0 ...
sit0 ...

Das bedeutet doch dass er die Konfiguration noch nicht ausgeführt hat oder?

Hat jemand Rat? Danke

drcux
24.05.07, 22:36
was sagt dmesg etc.?

MATI
04.06.07, 18:03
dmesg sagt:



Linux version 2.6.18.2-34-xenpae (geeko@buildhost) (gcc version 4.1.2 20061115 (
prerelease) (SUSE Linux)) #1 SMP Mon Nov 27 11:46:27 UTC 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 000000000e8ef000 (usable)
0MB HIGHMEM available.
232MB LOWMEM available.
On node 0 totalpages: 59631
DMA zone: 59631 pages, LIFO batch:15
DMI 2.3 present.
ACPI: RSDP (v000 FUJ ) @ 0x000f6280
ACPI: RSDT (v001 FUJ ACADIA 0x01120000 FUJ 0x00001000) @ 0x0feebb38
ACPI: FADT (v001 FUJ ACADIA 0x01120000 FUJ 0x00001000) @ 0x0feefb8c
ACPI: DSDT (v001 FUJ ACADIA 0x01120000 MSFT 0x01000007) @ 0x00000000
Allocating PCI resources starting at 20000000 (gap: 10000000:eff00000)
Xen reported: 647.849 MHz processor.
Built 1 zonelists. Total pages: 59631
Kernel command line: root=/dev/hda2 vga=0x317 resume=/dev/hda1 splash=silent
bootsplash: silent mode.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Software IO TLB enabled:
Aperture: 2 megabytes
Kernel range: 0x00000000c0b0d000 - 0x00000000c0d0d000
vmalloc area: cf800000-f51fe000, maxmem 2d7fe000
Memory: 214964k/238524k available (1976k kernel code, 15060k reserved, 932k data
, 184k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1622.24 BogoMIPS (lpj=3244491)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383d1f1 00000000 00000000 00000000 00000000
00000000 00000000
CPU: After vendor identify, caps: 0383d1f1 00000000 00000000 00000000 00000000 0
0000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps: 0383d1f1 00000000 00000000 00000040 00000000 0000000
0 00000000
Compat vDSO mapped to f57fd000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
checking if image is initramfs... it is
Freeing initrd memory: 6521k freed
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 0a00)
Brought up 1 CPUs
migration_cost=0
Grant table initialized
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region fc00-fc7f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region fc80-fcbf claimed by ICH4 GPIO
Boot video device is 0000:01:00.0
PCI: Firmware left 0000:02:08.0 e100 interrupts enabled, disabling
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #04 (-#07) is hidden behind transparent bridge #02 (-#04) (try 'pci=ass
ign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: Embedded Controller [EC] (gpe 23) interrupt mode.
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 *9 10)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *9 10)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 *11)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 *9 10)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 *11)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB_._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 13 devices
xen_mem: Initialising balloon driver.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Bridge: 0000:00:01.0
IO window: 2000-2fff
MEM window: f0000000-f00fffff
PREFETCH window: f8000000-fbffffff
PCI: Bus 3, cardbus bridge: 0000:02:0a.0
IO window: 00003400-000034ff
IO window: 00003800-000038ff
PREFETCH window: 20000000-21ffffff
MEM window: 24000000-25ffffff
PCI: Bus 4, cardbus bridge: 0000:02:0a.1
IO window: 00003c00-00003cff
IO window: 00004000-000040ff
PREFETCH window: 22000000-23ffffff
MEM window: 26000000-27ffffff
PCI: Bridge: 0000:00:1e.0
IO window: 3000-3fff
MEM window: f0100000-f01fffff
PREFETCH window: 20000000-23ffffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ
9
PCI: Setting latency timer of device 0000:02:0a.0 to 64
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
ACPI: PCI Interrupt 0000:02:0a.1[B] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ
9
PCI: Setting latency timer of device 0000:02:0a.1 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1181029651.984:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Real Time Clock Driver v1.12ac
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
Xen virtual console successfully installed as ttyS0
Event-channel device installed.
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input0
input: AT Translated Set 2 keyboard as /class/input/input1
input: PS/2 Mouse as /class/input/input2
input: AlpsPS/2 ALPS GlidePoint as /class/input/input3
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
Using IPI No-Shortcut mode
Time: xen clocksource has been installed.
Freeing unused kernel memory: 184k freed
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
ICH2M: IDE controller at PCI slot 0000:00:1f.1
ICH2M: chipset revision 3
ICH2M: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x18c0-0x18c7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x18c8-0x18cf, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: TOSHIBA MK2016GAP, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 39070080 sectors (20003 MB), CHS=38760/16/63, UDMA(66)
hda: cache flushes not supported
hda: hda1 hda2 hda3 < hda5 hda6 >
Probing IDE interface ide1...
hdc: MATSHITADVD-ROM SR-8175, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug
enabled
SGI XFS Quota Management subsystem
Filesystem "hda2": Disabling barriers, not supported by the underlying device
XFS mounting filesystem hda2
Ending clean XFS mount for filesystem: hda2
usbcore: registered new driver usbfs
usbcore: registered new driver hub
prism2usb_init: prism2_usb.o: 0.2.5 Loaded
prism2usb_init: dev_info is: prism2_usb
usbcore: registered new driver prism2_usb
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
lp0: using parport0 (interrupt-driven).
i8xx TCO timer: initialized (0xfc60). heartbeat=30 sec (nowayout=0)
Intel 82802 RNG detected
Linux agpgart interface v0.101 (c) Dave Jones
USB Universal Host Controller Interface driver v3.0
PCI: Enabling device 0000:00:1f.2 (0000 -> 0001)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ
11
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: UHCI Host Controller
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 11, io base 0x000018e0
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.18.2-34-xenpae uhci_hcd
usb usb1: SerialNumber: 0000:00:1f.2
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
hub 1-0:1.0: over-current change on port 2
agpgart: Detected an Intel i815 Chipset.
agpgart: AGP aperture is 64M @ 0xf4000000
PCI: Enabling device 0000:00:1f.4 (0000 -> 0001)
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1f.4[C] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ
11
PCI: Setting latency timer of device 0000:00:1f.4 to 64
uhci_hcd 0000:00:1f.4: UHCI Host Controller
uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1f.4: irq 11, io base 0x00001c00
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.18.2-34-xenpae uhci_hcd
usb usb2: SerialNumber: 0000:00:1f.4
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ
9
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 1-2: new device found, idVendor=5041, idProduct=2234
usb 1-2: new device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-2: configuration #1 chosen from 1 choice
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ
9
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 58770 usecs
intel8x0: clocking to 48000
Yenta: CardBus bridge found at 0000:02:0a.0 [10cf:10e6]
Yenta O2: res at 0x94/0xD4: ea/00
Yenta O2: enabling read prefetch/write burst
Yenta: ISA IRQ mask 0x0438, PCI irq 9
Socket status: 30000006
pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
pcmcia: parent PCI bridge Memory window: 0xf0100000 - 0xf01fffff
pcmcia: parent PCI bridge Memory window: 0x20000000 - 0x23ffffff
Yenta: CardBus bridge found at 0000:02:0a.1 [10cf:10e6]
Yenta: ISA IRQ mask 0x0438, PCI irq 9
Socket status: 30000006
Yenta: Raising subordinate bus# of parent bus (#02) from #04 to #07
pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
pcmcia: parent PCI bridge Memory window: 0xf0100000 - 0xf01fffff
pcmcia: parent PCI bridge Memory window: 0x20000000 - 0x23ffffff
hdc: ATAPI 24X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 9
ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKE] -> GSI 9 (level, low) -> IRQ
9
e100: eth0: e100_probe: addr 0xf0100000, irq 9, MAC addr 00:E0:00:1C:56:35
Adding 514040k swap on /dev/hda1. Priority:-1 extents:1 across:514040k
Filesystem "hda2": Disabling barriers, not supported by the underlying device
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
loop: loaded (max 8 devices)
AppArmor: AppArmor initialized
audit(1181029675.765:2): AppArmor initialized

NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (1863 buckets, 14904 max) - 228 bytes per conntrack
ACPI: AC Adapter [AC] (off-line)
ACPI: Battery Slot [CMB1] (battery present)
ACPI: Battery Slot [CMB2] (battery absent)
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Lid Switch [LID]
audit(1181029698.394:3): audit_pid=2705 old=0 by auid=4294967295
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
ADDRCONF(NETDEV_UP): eth0: link is not ready
NET: Registered protocol family 17

Rain_maker
04.06.07, 18:07
Wozu brauchst Du denn einen xenpae-Kernel?

Nutzt Du XEN überhaupt?

Greetz,

RM

MATI
04.06.07, 18:28
Ja hab halt irgendwelche USB und WLAN Pakete nachinstalliert die mir auch den xenpen kernel angeboten haben. Und daher xenpen - wäre das ein Problem und wenn ja warum?

Rain_maker
04.06.07, 18:32
Genau "irgendwelche" Pakete ist das Problem, wahrscheinlich Kernelmodule für den Xenpae-Kernel und dann hat Yast richtigerweise den Kernel installiert.

Wenn man nämlich kmp-Pakete zu einem nicht installierten Kernel auswählt, dann wird der dazu passende Kernel nachinstalliert.

Man sollte eben auf den Paketnamen schauen, bevor man etwas installiert.

Also, schmeiss den xenpae-Kernel raus und nimm den default und die dazu _passenden_ Module *irgendwas*-kmp-default.

Vielleicht hilft das auch auf Deiner alten Gurke gegen die Performanceprobleme.

Greetz,

RM

MATI
04.06.07, 18:36
und hat das jetzt mit meinem WLAN Problem was zu tun oder nicht?

Rain_maker
04.06.07, 18:37
Kann sein.

Greetz,

RM

MATI
04.06.07, 18:52
danke - hat mir alles sehr geholfen - vor allem die Begründungen.

Rain_maker
04.06.07, 18:56
Bei Deinen Infos kann man auch nur raten.

Du nutzt jedenfalls einen Kernel, der für Dein System Overkill ist und vielleicht weitere Probleme nach sich zieht.

Kernel-default ist mehr als ausreichend für Dein System.

Mit knapp 350 Beiträgen kann man eigentlich etwas mehr an Wissen erwarten.

Greetz,

RM