FC4: IRQ 11 rarely enabled -> no wifi, no ethernet

From: QDaniel_Fr=E8rejacque=22?= (daniel.frerejacque_at_normalesup.org)
Date: 10/24/05

  • Next message: Stephanus Fengler: "Re: how to react on ssh attacks?" 
    Date: Mon, 24 Oct 2005 13:21:08 +0200
To: fedora liste <fedora-list@redhat.com>

    On a recent Toshiba M40, dual boot: windows + FC4,
    Pentium M; networking:
    (a) Syskonnect SK-98xx Gigabit ethernet (compatible with Marvell Yukon)
    (b) Intel Pro Wireless 2200 BG (driver ipw2200 provided)

    During the boot process, after udev and
    before the clock setting, the message
    "Disabling IRQ 11" is displayed.

    This happens randomly, but IRQ 11 is more oftent
    disabled than enabled. In that case neither wifi
    nor etherenet are be activated, nor can be with
    the network tools.
             ------------------
    (1) Examining dmesg, making diff on dmesg with and
    without IRQ 11 ok, there is a message:
    "IRQ 11 nobody care" and roughly twenty lines later
    the "Disabling IRQ 11"

    (2) The advice given in dmesg: in case of harware not
    recognized: try "pci=routeirq" (and post a message if ok)
    don't change anything.

    Note: The driver sk98lin for Gigabit ethernet is not yet
    provided by Fedora, but compiled and installed with
    modprobe for each new version of the kernel.

    If interested, I can forward dmesg with good and bad boots.

    Should I post a bug

    Thanks

    Daniel Frerejacque 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Stephanus Fengler: "Re: how to react on ssh attacks?"

    Relevant Pages

    • Re: soundcard SoundBlaster PCI128 or SoundBlaster live1024 problem
      ... > What messages are you getting from boot log and dmesg? ... ACPI tables contain no PCI IRQ routing entries ... RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize ... USB Universal Host Controller Interface driver v2.2 ...
      (comp.os.linux.hardware)
    • Enabling acpi support renders system unbootable (was: kernel: ad8: FAILURE - READ timed out LBA=
      ... Whenever I try to boot my desktop workstation with FreeBSD, it suddenly just hangs there forever. ... The hard drive is connected to an onboard Promise FastTrak (atapci1: port 0x8000-0x803f,0x7800-0x780f,0x7400-0x747f mem 0xab800000-0xab800fff,0xab000000-0xab01ffff irq 11 at device 14.0 on pci0) controller on my Asus p4s8x motherboard. ... ata1: reiniting channel .. ... So I thought that maybe, just disabling dma and write caching would let me boot my system, otherwise normally, and thereby effectively narrowing down the problem to dma and write caching. ...
      (freebsd-questions)
    • Re: Black screen on booting
      ... Check and recheck your video adapter driver and BIOS. ... Your IRQ sharing seems normal to me. ... >down overnight, but if you wait till it warms up, it will boot as follows: ...
      (microsoft.public.win2000.general)
    • Re: MCP2 on Intel 945 Mobo advice?
      ... You might try setting that and see if you can get a solitary IRQ assigned to the SBLive so that the other devices will go off and find a different IRQ. ... From other OS/2 work before, with the whole thing 'working', but with all the IRQ's the way 'it works', I thought that I would try the option during the boot run to let it examine hardware. ... So I tried Veit Kannegieser's PCIIRQ.ARJ 'force' IRQ suite off his web site both to cross research this with the PCI sniff tests as well as possibly 'fix' the IRQ for at least the SBLive 5.1 PCI add-in card. ...
      (comp.os.os2.setup.misc)
    • 5.2.1 boot-install
      ... I downloaded the 2 meg boot floppy for installing FreeBSD 5.2.1. ... wanted to burn it to a CD (I usually install via ftp, ... pci0: on pcib0 ... 0xffa80000-0xffafffff,0xf0000000-0xf7ffffff irq 11 at device 2.0 on ...
      (freebsd-questions)