Viestissä Sunnuntai 2. Helmikuuta 2003 23:23, Gregory K. Meyer kirjoitti: > Viestissä Sunnuntai 2. Helmikuuta 2003 21:43, [Bug 115] kirjoitti: > > https://qa.mandrakesoft.com/show_bug.cgi?id=115 > > > > ------- Additional Comments From [EMAIL PROTECTED] 2003-02-02 20:43 > > ------- After Dominique's report, I went back to do some more testing > > and this is what I have found. I have attached the dmesg output from > > all of the cases, except the one that gave me a kernel panic. > > > > Booting kernel 2.4.21pre4-1mdk without any arguments, I get no network > > functionality, despite the fact that the kernel modules for my nics > > load successfully. This happens withe the onboard VIA Rhine as well > > as a PCI 3c905b. Dmesg output is attached as dmesg.linux > > > > Booting with noapic, the network now works, but the dmesg file is full > > of the APIC errors. The dmesg output is attached as dmesg.noapic > > try to boot with pci=noapic, so it wont shut down the whole apic, only > for the parts that effects the network card...
|pci=noapic or pci=noacpi One of the erros I got referred to boot with |pci=noacpi. I thought the apic was all or nothing. | |WHo came up with these acronyms? | Sorry for the typo... The correct one is of course: pci=noacpi ACPI = Advanced Configuration and Power Interface APIC = Advanced Programmable Interrupt Controller AFAIK acpi uses apic to get the irq-routing (to get around the legacy "only 15 irq"), but when you tell 'pci=noacpi', you gives the control of pci irq to bios (and thereby limits the irq-addressing on the pci bus to the 15 legacy irq, as an "compability mode") -- Thomas ****************************** * If nothing else works, read the manual ... ... ... ******************************
