Bug 6920
| Summary: | prism54 doesn't work at all after upgrade to 2.6.17 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Jordi Mallach (jordi) |
| Component: | network-wireless | Assignee: | Diego Calleja (diegocg) |
| Status: | REJECTED DUPLICATE | ||
| Severity: | normal | CC: | daniel.ritz, diegocg, linville |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.17 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
|
Description
Jordi Mallach
2006-07-29 16:37:17 UTC
Mmmh. This bug may be a dupliate of #6801. If you're compiling your own kernel, could you try this just to check if it works?: "OK, The problem was solved. CardBus works when change CONFIG_PCI_BIOS to CONFIG_PCI_DIRECT in .config. Thanks." Diego, the kernel's config includes both CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y Would that help? Mmh, #6801 says that you should disable CONFIG_PCI_BIOS. You probably selected "PCI Access Mode -> Any", which enables both CONFIG_PCI_* options, you should try to set it to "Direct", that should disable _BIOS. Now, looking at #6801, that trick may not fix the problem in your case, although the symptons look similar the PCI dmesg info looks different, it'd be nice if you could try it though. Hi. Is output of dmesg different with old kernel and new kernel? In my case: - kernel 2.6.16 cs: IO port probe 0x100-0x3af: excluding 0x398-0x39f cs: IO port probe 0xc00-0xcff: clean. - kernel 2.6.17 cs: IO port probe 0x100-0x3af: excluding 0x398-0x39f cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff And, /proc/ioports is different too. - kernel 2.6.16 0cf8-0cff : PCI conf1 - kernel 2.6.16 (nothing) If you have same problems, try change PCI access mode "PCI Access Mode -> Any" to "PCI Access Mode -> Direct". Please show PCI guys dmesg of old kernel, /proc/ioports of both kernels. Some clue should be included in it. yep, exaclty the same issue as bug #6801, #6875. there is a patch in #6875 that fixes the problem ( http://bugzilla.kernel.org/attachment.cgi?id=8798&action=view ). the same patch is also found in 2.6.18-rc4-mm2 After disabling CONFIG_PCI_BIOS, 2.6.17 started working ok. -# CONFIG_PCI_GODIRECT is not set -CONFIG_PCI_GOANY=y -CONFIG_PCI_BIOS=y +CONFIG_PCI_GODIRECT=y +# CONFIG_PCI_GOANY is not set Re: ioports 2.6.16: Aug 14 17:29:35 nubol kernel: cs: IO port probe 0x100-0x4ff: excluding 0x200-0x207 0x220-0x22f 0x388-0x38f 0x4d0-0x4d7 Aug 14 17:29:35 nubol kernel: cs: IO port probe 0x800-0x8ff: clean. Aug 14 17:29:35 nubol kernel: cs: IO port probe 0xc00-0xcff: clean. Aug 14 17:29:35 nubol kernel: cs: IO port probe 0xa00-0xaff: clean. 2.6.17: Aug 21 18:13:38 nubol kernel: cs: IO port probe 0x100-0x4ff: excluding 0x200-0x207 0x220-0x22f 0x388-0x38f 0x4d0-0x4d7 Aug 21 18:13:38 nubol kernel: cs: IO port probe 0x800-0x8ff: clean. Aug 21 18:13:38 nubol kernel: cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff Aug 21 18:13:38 nubol kernel: cs: IO port probe 0xa00-0xaff: clean. So yeah, I guess this is the same bug fixed by the patch in #6875. |