Argh, after a period of perfect w-lan connectivity with SuSE 9.3, 10.0
causes agony again.
After the system update, wireless didn't work. I then installed the
ipw-firmware package; after configuring the w-lan interface it worked
fore a few hours until I rebooted. Since then, the wireless connection
has gone. I tried to install the latest ipw2200 and ieee80211 versions,
but neither compiled.
I then reinstalled the original SuSE 10.0 kernel modules (via system
repair), rebuilt ipw-firmware from the src-package (as I picked up in a
SuSE mailing-list), but still, no connectivity. At this stage, I just
don't know what's wrong: kernel modules, firmware, or network setup. And
it all worked so nicely with 9.3!
Any help would be greatly appreciated.
Here's the output from dmesg:
Linux version 2.6.13-15-default (geeko@buildhost) (gcc version 4.0.2
20050901 (prerelease) (SUSE Linux)) #1 Tue Sep 13 14:56:15 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001f740000 (usable)
BIOS-e820: 000000001f740000 - 000000001f750000 (ACPI data)
BIOS-e820: 000000001f750000 - 000000001f800000 (ACPI NVS)
0MB HIGHMEM available.
503MB LOWMEM available.
On node 0 totalpages: 128832
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 124736 pages, LIFO batch:31
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 ACPIAM ) @ 0x000f4fd0
ACPI: RSDT (v001 A M I OEMRSDT 0x07000422 MSFT 0x00000097) @ 0x1f740000
ACPI: FADT (v002 A M I OEMFACP 0x07000422 MSFT 0x00000097) @ 0x1f740200
ACPI: MADT (v001 A M I OEMAPIC 0x07000422 MSFT 0x00000097) @ 0x1f740300
ACPI: OEMB (v001 A M I OEMBIOS 0x07000422 MSFT 0x00000097) @ 0x1f750040
ACPI: DSDT (v001 0ABBD 0ABBD001 0x00000001 MSFT 0x02000001) @ 0x00000000
ACPI: PM-Timer IO Port: 0xe408
ACPI: local apic disabled
Allocating PCI resources starting at 1f800000 (gap: 1f800000:e0800000)
Built 1 zonelists
Kernel command line: root=/dev/hda3 vga=788 selinux=0 resume=/dev/hda4
splash=silent
bootsplash: silent mode.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 1500.329 MHz processor.
Using pmtmr for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 505296k/515328k available (2028k kernel code, 9516k reserved,
700k data, 204k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3002.75 BogoMIPS
(lpj=6005518)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 512
CPU: After generic identify, caps: afe9fbbf 00000000 00000000 00000000
00000180 00000000 00000000
CPU: After vendor identify, caps: afe9fbbf 00000000 00000000 00000000
00000180 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: After all inits, caps: afe9fbbf 00000000 00000000 00000040 00000180
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: Intel(R) Pentium(R) M processor 1.50GHz stepping 06
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
checking if image is initramfs... it is
Freeing initrd memory: 1701k freed
ACPI: Looking for DSDT in initrd... not found!
not found!
ACPI: setting ELCR to 0200 (from 00b8)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: Subsystem revision 20050408
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
Boot video device is 0000:00:02.0
PCI: Enabled i801 SMBus device
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: Embedded Controller [EC0] (gpe 28)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 *4 5 6 7 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 12)
ACPI: Power Resource [GFAN] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bus 2, cardbus bridge: 0000:01:03.0
IO window: 00001000-00001fff
IO window: 00002000-00002fff
PREFETCH window: 20000000-21ffffff
MEM window: 22000000-23ffffff
PCI: Bus 6, cardbus bridge: 0000:01:03.1
IO window: 00003000-00003fff
IO window: 00004000-00004fff
PREFETCH window: 24000000-25ffffff
MEM window: 26000000-27ffffff
PCI: Bridge: 0000:00:1e.0
IO window: c000-cfff
MEM window: fe700000-fe8fffff
PREFETCH window: de500000-de6fffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI-0212: *** Warning: Device is not power manageable
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKB] -> GSI 7 (level, low)
-> IRQ 7
ACPI-0212: *** Warning: Device is not power manageable
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 7
ACPI: PCI Interrupt 0000:01:03.1[B] -> Link [LNKC] -> GSI 7 (level, low)
-> IRQ 7
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1133463198.780:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
vesafb: framebuffer at 0xf0000000, mapped to 0xe0080000, using 3750k,
total 8000k
vesafb: mode is 800x600x16, linelength=1600, pages=7
vesafb: protected mode interface info at 00ff:44f0
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size
51518 bytes,<6>...found (800x600, 8809 bytes, v3).
Console: switching to colour frame buffer device 99x34
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
ACPI-0212: *** Warning: Device is not power manageable
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 7 (level, low)
-> IRQ 7
ACPI: PCI interrupt for device 0000:00:1f.6 disabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
mice: PS/2 mouse device common for all mice
input: PC Speaker
md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 3.38
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
Using IPI Shortcut mode
ACPI wakeup devices:
P0P1 LAN0 CBS0 CBS1 P394 MPCI MODM USB1 USB2 USB3 EHCI SLPB
ACPI: (supports S0 S1 S3 S4 S5)
Freeing unused kernel memory: 204k freed
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
input: AT Translated Set 2 keyboard on isa0060/serio0
ICH4: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 7 (level, low)
-> IRQ 7
ICH4: chipset revision 3
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: IC25N040ATMR04-0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: 78140160 sectors (40007 MB) w/1740KiB Cache, CHS=16383/255/63,
UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4
Probing IDE interface ide1...
hdc: UJDA755 DVD/CDRW, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU1] (supports 8 throttling states)
ACPI: Thermal Zone [THRM] (63 C)
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x116eb1, caps: 0xa04713/0x0
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ACPI: Fan [FN00] (on)
Attempting manual resume
swsusp: Suspend partition has wrong signature?
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Adding 915696k swap on /dev/hda4. Priority:42 extents:1
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
FAT: utf8 is not a recommended IO charset for FAT filesystems,
filesystem will be case sensitive!
FAT: utf8 is not a recommended IO charset for FAT filesystems,
filesystem will be case sensitive!
PCI: Enabling device 0000:00:1f.5 (0005 -> 0007)
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 7 (level, low)
-> IRQ 7
PCI: Setting latency timer of device 0000:00:1f.5 to 64
ieee80211_crypt: module not supported by Novell, setting U taint flag.
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: module not supported by Novell, setting U taint flag.
ieee80211: 802.11 data/management/control stack, 1.0.3
ieee80211: Copyright (C) 2004-2005 Intel Corporation
In <438F5EE0.6050909@univie.ac.at>, on 12/01/05
at 09:36 PM, Birgit Kellner
Argh, after a period of perfect w-lan connectivity with SuSE 9.3, 10.0 causes agony again.
After the system update, wireless didn't work. I then installed the ipw-firmware package; after configuring the w-lan interface it worked fore a few hours until I rebooted. Since then, the wireless connection has gone. I tried to install the latest ipw2200 and ieee80211 versions, but neither compiled.
I then reinstalled the original SuSE 10.0 kernel modules (via system repair), rebuilt ipw-firmware from the src-package (as I picked up in a SuSE mailing-list), but still, no connectivity. At this stage, I just don't know what's wrong: kernel modules, firmware, or network setup. And it all worked so nicely with 9.3!
Any help would be greatly appreciated.
Here's the output from dmesg:
...snip...
ipw2200: module not supported by Novell, setting U taint flag. ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6 ipw2200: Copyright(c) 2003-2004 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: ipw-2.3-boot.fw load failed: Reason -2 ipw2200: Unable to load firmware: 0xFFFFFFFE ipw2200: failed to register network device
Known issue:
https://bugzilla.novell.com/show_bug.cgi?id=113446
HTH.
--
-----------------------------------------------------------
"Michael E. Jaggers"
Michael E. Jaggers wrote:
ipw2200: module not supported by Novell, setting U taint flag. ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6 ipw2200: Copyright(c) 2003-2004 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: ipw-2.3-boot.fw load failed: Reason -2 ipw2200: Unable to load firmware: 0xFFFFFFFE ipw2200: failed to register network device
Known issue: https://bugzilla.novell.com/show_bug.cgi?id=113446
HTH.
Thank you. Let me just see whether I get this straight: Bug 113446 is marked as a duplicate of 112915, and 112915 is said to be resolvable through making sure that in line 236 of /etc/udev/rules.d/50-udev.rules, the name of the firmware loader script must be corrected to /sbin/udev.firmware.sh. Both bugs are marked as resolved. However, the name of the firmware loader *is* already set to /sbin/udev.firmware.sh in my system, so this can't be the culprit. I followed pertinent advice on the ipw2200 sourceforge site and increased the timeout value in /sys/class/firmware/timeout to 100, but this didn't help either. Firmware just doesn't get loaded. Any further suggestions? Thanks, Birgit
In <43908144.9050803@univie.ac.at>, on 12/02/05
at 06:15 PM, Birgit Kellner
Thank you. Let me just see whether I get this straight: Bug 113446 is marked as a duplicate of 112915, and 112915 is said to be resolvable through making sure that in line 236 of /etc/udev/rules.d/50-udev.rules, the name of the firmware loader script must be corrected to /sbin/udev.firmware.sh. Both bugs are marked as resolved.
However, the name of the firmware loader *is* already set to /sbin/udev.firmware.sh in my system, so this can't be the culprit.
That's correct. The problems mentioned were taken care of in the beta tests, and resolved before GM.
I followed pertinent advice on the ipw2200 sourceforge site and increased the timeout value in /sys/class/firmware/timeout to 100, but this didn't help either. Firmware just doesn't get loaded.
Any further suggestions?
Not really. I don't have any machines here with that configuration, so I can't test. I was hoping that the change in timeout would solve your problem.
Thanks,
Birgit
Mike
--
-----------------------------------------------------------
"Michael E. Jaggers"
participants (2)
-
Birgit Kellner
-
Michael E. Jaggers