Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x (also latitude)
hi, sorry to bother you all... i would like to follow up this thread because, i have too this strange effect that with kernel 2.4.2 i'm no more able to use the pcmcia interface (and with 2.2.17 it was ok!). i tried to make some troubleshooting to the best of my knowledge but i lost myself when, last email, Jeff Lessem ended saying that, just using lilo (and not grub) the problem went away.. but is he still speaking of the pcmcia problem? i am using: - a dell latitude cpx h450 (bios a07) - 256 MB of ram - lilo (without any mem append option) - with 2.2.17 pcmcia is working well - with 2.4.2 and external pcmcia-cs 3.1.24 no (i have never been able to load the i82365.o module) you can find in attach my dmesg and the output of "lspci -vvxxx -s03:00" that are my pci entries of the pcmcia adapter (hope not to be a mistake posting a couple of small bin attach) and the relevant message is: Intel PCIC probe: PCI: Enabling device 00:03.0 ( -> 0002) PCI: Found IRQ 11 for device 00:03.0 PCI: The same IRQ used for device 00:03.1 PCI: The same IRQ used for device 00:07.2 Bridge register mapping failed: check cb_mem_base setting not found. i tried to add the cb_mem_base parameter loading pcmcia_core but in the pci_fixup.c source is commented out when you use a >= 2.3.24 kernel, so this line fails: insmod pcmcia_core cb_mem_base=0x1000 could someone kindly shed some light!? sorry, i'm not subscribed to lkml so, please, cc. to me, otherwise, i will check the answers on the ml archive. thank you in advance andrea venturi > In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write: > > > >Careful, you're overwriting ACPI data now (and using it as normal RAM). > > Hmm, I guess that would be bad. > > >Can you try one of a) LILO b) a fixed version of grub c) this patch ? > > I tried LILO and the problem did indeed go away when using that. I > guess I'll stick with LILO until Linux or grub (whichever is broken) > is fixed. There is just something appealing about a proper boot > console on a PC... -- andrea venturi - Nextra spa [EMAIL PROTECTED] - +390516139246 -- "If a man speaks in the forest and there is no woman to hear him, is he still wrong?" ti1225.txt.bz2 dmesg.txt.bz2
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x (also latitude)
hi, sorry to bother you all... i would like to follow up this thread because, i have too this strange effect that with kernel 2.4.2 i'm no more able to use the pcmcia interface (and with 2.2.17 it was ok!). i tried to make some troubleshooting to the best of my knowledge but i lost myself when, last email, Jeff Lessem ended saying that, just using lilo (and not grub) the problem went away.. but is he still speaking of the pcmcia problem? i am using: - a dell latitude cpx h450 (bios a07) - 256 MB of ram - lilo (without any mem append option) - with 2.2.17 pcmcia is working well - with 2.4.2 and external pcmcia-cs 3.1.24 no (i have never been able to load the i82365.o module) you can find in attach my dmesg and the output of "lspci -vvxxx -s03:00" that are my pci entries of the pcmcia adapter (hope not to be a mistake posting a couple of small bin attach) and the relevant message is: Intel PCIC probe: PCI: Enabling device 00:03.0 ( - 0002) PCI: Found IRQ 11 for device 00:03.0 PCI: The same IRQ used for device 00:03.1 PCI: The same IRQ used for device 00:07.2 Bridge register mapping failed: check cb_mem_base setting not found. i tried to add the cb_mem_base parameter loading pcmcia_core but in the pci_fixup.c source is commented out when you use a = 2.3.24 kernel, so this line fails: insmod pcmcia_core cb_mem_base=0x1000 could someone kindly shed some light!? sorry, i'm not subscribed to lkml so, please, cc. to me, otherwise, i will check the answers on the ml archive. thank you in advance andrea venturi In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write: Careful, you're overwriting ACPI data now (and using it as normal RAM). Hmm, I guess that would be bad. Can you try one of a) LILO b) a fixed version of grub c) this patch ? I tried LILO and the problem did indeed go away when using that. I guess I'll stick with LILO until Linux or grub (whichever is broken) is fixed. There is just something appealing about a proper boot console on a PC... -- andrea venturi - Nextra spa [EMAIL PROTECTED] - +390516139246 -- "If a man speaks in the forest and there is no woman to hear him, is he still wrong?" ti1225.txt.bz2 dmesg.txt.bz2
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
> In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write: > > > >Careful, you're overwriting ACPI data now (and using it as normal RAM). > > Hmm, I guess that would be bad. > > >Can you try one of a) LILO b) a fixed version of grub c) this patch ? > > I tried LILO and the problem did indeed go away when using that. I > guess I'll stick with LILO until Linux or grub (whichever is broken) > is fixed. There is just something appealing about a proper boot > console on a PC... Even though I wasn't much help on this, it's nice to know what was different on your config that was causing problems while I wasn't seeing any issues. I sat here for almost an hour last night trying to figure out why your machines memory map would different than mine (I have 320MB of RAM as well, so they should have been the same). The thought that you might be using a different boot loader never even crossed my mind. I've always used LILO so that's why I didn't see any problems. It's nice to know it wasn't just working for me by accident. Later, Tom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write: > >Careful, you're overwriting ACPI data now (and using it as normal RAM). Hmm, I guess that would be bad. >Can you try one of a) LILO b) a fixed version of grub c) this patch ? I tried LILO and the problem did indeed go away when using that. I guess I'll stick with LILO until Linux or grub (whichever is broken) is fixed. There is just something appealing about a proper boot console on a PC... BIOS-provided physical RAM map: BIOS-e820: 0009f800 @ (usable) BIOS-e820: 0800 @ 0009f800 (reserved) BIOS-e820: 00019800 @ 000e6800 (reserved) BIOS-e820: 13ef @ 0010 (usable) BIOS-e820: fc00 @ 13ff (ACPI data) BIOS-e820: 0400 @ 13fffc00 (ACPI NVS) BIOS-e820: 0008 @ fff8 (reserved) On node 0 totalpages: 81904 zone(0): 4096 pages. zone(1): 77808 pages. zone(2): 0 pages. Kernel command line: auto BOOT_IMAGE=Linux ro root=301 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Sat, Feb 24, 2001 at 10:25:42AM -0700, Jeff Lessem wrote:
> In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write:
> >Jeff, are you using the e820 memory map at all ? In particular, are you
> >using grub or some other buggy bootloader that insists on specifying a
> >mem= option on the kernel command line ? There should be a kernel command
> >line message very early on, what does that say ?
>
> Yes, I am using grub, the buggy bootloader. The relevant chunk of
> kernal messages are:
>
> BIOS-provided physical RAM map:
> BIOS-e820: 0009f800 @ (usable)
> BIOS-e820: 0800 @ 0009f800 (reserved)
> BIOS-e820: 00019800 @ 000e6800 (reserved)
> BIOS-e820: 13ef @ 0010 (usable)
> BIOS-e820: fc00 @ 13ff (ACPI data)
> BIOS-e820: 0400 @ 13fffc00 (ACPI NVS)
> BIOS-e820: 0008 @ fff8 (reserved)
> On node 0 totalpages: 81904
> zone(0): 4096 pages.
> zone(1): 77808 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/hda1 mem=327616K
>
> You are dead on, mem= seems a bit small. Forcing mem=320M on the
> command line fixes the problem completely.
Careful, you're overwriting ACPI data now (and using it as normal RAM).
Can you try one of a) LILO b) a fixed version of grub c) this patch ?
diff -ur linux/arch/i386/kernel/setup.c linux-prumpf/arch/i386/kernel/setup.c
--- linux/arch/i386/kernel/setup.c Fri Feb 23 13:37:38 2001
+++ linux-prumpf/arch/i386/kernel/setup.c Sat Feb 24 09:49:50 2001
@@ -555,30 +555,9 @@
e820.nr_map = 0;
usermem = 1;
} else {
- /* If the user specifies memory size, we
-* blow away any automatically generated
-* size
-*/
- unsigned long start_at, mem_size;
-
- if (usermem == 0) {
- /* first time in: zap the whitelist
-* and reinitialize it with the
-* standard low-memory region.
-*/
- e820.nr_map = 0;
- usermem = 1;
- add_memory_region(0, LOWMEMSIZE(), E820_RAM);
- }
- mem_size = memparse(from+4, );
+ memparse(from+4, );
if (*from == '@')
- start_at = memparse(from+1, );
- else {
- start_at = HIGH_MEMORY;
- mem_size -= HIGH_MEMORY;
- usermem=0;
- }
- add_memory_region(start_at, mem_size, E820_RAM);
+ memparse(from+1, );
}
}
c = *(from++);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write: >Jeff, are you using the e820 memory map at all ? In particular, are you >using grub or some other buggy bootloader that insists on specifying a >mem= option on the kernel command line ? There should be a kernel command >line message very early on, what does that say ? Yes, I am using grub, the buggy bootloader. The relevant chunk of kernal messages are: BIOS-provided physical RAM map: BIOS-e820: 0009f800 @ (usable) BIOS-e820: 0800 @ 0009f800 (reserved) BIOS-e820: 00019800 @ 000e6800 (reserved) BIOS-e820: 13ef @ 0010 (usable) BIOS-e820: fc00 @ 13ff (ACPI data) BIOS-e820: 0400 @ 13fffc00 (ACPI NVS) BIOS-e820: 0008 @ fff8 (reserved) On node 0 totalpages: 81904 zone(0): 4096 pages. zone(1): 77808 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda1 mem=327616K You are dead on, mem= seems a bit small. Forcing mem=320M on the command line fixes the problem completely. BIOS-provided physical RAM map: BIOS-e820: 0009f800 @ (usable) BIOS-e820: 0800 @ 0009f800 (reserved) BIOS-e820: 00019800 @ 000e6800 (reserved) BIOS-e820: 13ef @ 0010 (usable) BIOS-e820: fc00 @ 13ff (ACPI data) BIOS-e820: 0400 @ 13fffc00 (ACPI NVS) BIOS-e820: 0008 @ fff8 (reserved) On node 0 totalpages: 81920 zone(0): 4096 pages. zone(1): 77824 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda1 mem=320M - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Sat, Feb 24, 2001 at 05:36:47AM -0800, Linus Torvalds wrote: > On Sat, 24 Feb 2001, Jeff Lessem wrote: > > > > >Also, how much memory does this machine have? That "13ff" does worry > > >me a bit.. > > > > The comptuer has 320MB. At this point I am ready to conclude that the > > computer is broken in some way, because nobody else with an Inspiron > > 5000e that I have heard from has anything like this problem. > I didn't believe that you'd have 320MB just because it's such an odd > number, but the problem is that Linux apparently starts allocating the PCI > address space just _under_ the 320MB mark (you probably have some memory > reserved for ACPI that doesn't show up in the e820 memory map). Jeff, are you using the e820 memory map at all ? In particular, are you using grub or some other buggy bootloader that insists on specifying a mem= option on the kernel command line ? There should be a kernel command line message very early on, what does that say ? Also, can you give us the E820 memory map (kernel messages starting with BIOS-e820) ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Fri, 23 Feb 2001 09:48:04 PST, you write: >The much more likely cause is the "magic registers" for the Texas >Instruments PCI1225, namely > > works broken > > 81: b0 90 > a8: 11 10 > >Although it worries me a bit that your second controller also seems to >have differences in the BridgeCtl thing (16bInt). > >Can you try if a broken setup is fixed by doing a > > setpci -s 00.04.0 81.b=b0 > setpci -s 00.04.0 a8.b=11 > setpci -s 00.04.1 81.b=b0 > setpci -s 00.04.1 81.b=11 I ran setpci -s 00:04.0 81.b=b0, etc., but it didn't make any difference. Checking with lspci -vvxxx after running setpci it appears that register 81 and a8 have stayed at 90 and 10 despite setpci running without an error, using -G and -v setpci claims to be running through /proc/bus/pci and adjusting the appropriate location. Either I am making a fundamental error (yes, I am running it as root) or the changes simply don't matter. >Also, how much memory does this machine have? That "13ff" does worry >me a bit.. The comptuer has 320MB. At this point I am ready to conclude that the computer is broken in some way, because nobody else with an Inspiron 5000e that I have heard from has anything like this problem. I really appreciate the help everybody is providing with what is really only an annoyance, and I wouldn't have even brought it to the attention of linux-kernel, except that something that changed between 2.2.17 and 2.4.x has produced a regression in functionality. If anybody thinks it would be useful, I would be willing to do a binary search between 2.2.17 and 2.4.2 to find out at which release things stopped being setup correctly. -- Jeff Lessem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Fri, 23 Feb 2001 09:48:04 PST, you write: The much more likely cause is the "magic registers" for the Texas Instruments PCI1225, namely works broken 81: b0 90 a8: 11 10 Although it worries me a bit that your second controller also seems to have differences in the BridgeCtl thing (16bInt). Can you try if a broken setup is fixed by doing a setpci -s 00.04.0 81.b=b0 setpci -s 00.04.0 a8.b=11 setpci -s 00.04.1 81.b=b0 setpci -s 00.04.1 81.b=11 I ran setpci -s 00:04.0 81.b=b0, etc., but it didn't make any difference. Checking with lspci -vvxxx after running setpci it appears that register 81 and a8 have stayed at 90 and 10 despite setpci running without an error, using -G and -v setpci claims to be running through /proc/bus/pci and adjusting the appropriate location. Either I am making a fundamental error (yes, I am running it as root) or the changes simply don't matter. Also, how much memory does this machine have? That "13ff" does worry me a bit.. The comptuer has 320MB. At this point I am ready to conclude that the computer is broken in some way, because nobody else with an Inspiron 5000e that I have heard from has anything like this problem. I really appreciate the help everybody is providing with what is really only an annoyance, and I wouldn't have even brought it to the attention of linux-kernel, except that something that changed between 2.2.17 and 2.4.x has produced a regression in functionality. If anybody thinks it would be useful, I would be willing to do a binary search between 2.2.17 and 2.4.2 to find out at which release things stopped being setup correctly. -- Jeff Lessem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Sat, Feb 24, 2001 at 05:36:47AM -0800, Linus Torvalds wrote: On Sat, 24 Feb 2001, Jeff Lessem wrote: Also, how much memory does this machine have? That "13ff" does worry me a bit.. The comptuer has 320MB. At this point I am ready to conclude that the computer is broken in some way, because nobody else with an Inspiron 5000e that I have heard from has anything like this problem. I didn't believe that you'd have 320MB just because it's such an odd number, but the problem is that Linux apparently starts allocating the PCI address space just _under_ the 320MB mark (you probably have some memory reserved for ACPI that doesn't show up in the e820 memory map). Jeff, are you using the e820 memory map at all ? In particular, are you using grub or some other buggy bootloader that insists on specifying a mem= option on the kernel command line ? There should be a kernel command line message very early on, what does that say ? Also, can you give us the E820 memory map (kernel messages starting with BIOS-e820) ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write: Jeff, are you using the e820 memory map at all ? In particular, are you using grub or some other buggy bootloader that insists on specifying a mem= option on the kernel command line ? There should be a kernel command line message very early on, what does that say ? Yes, I am using grub, the buggy bootloader. The relevant chunk of kernal messages are: BIOS-provided physical RAM map: BIOS-e820: 0009f800 @ (usable) BIOS-e820: 0800 @ 0009f800 (reserved) BIOS-e820: 00019800 @ 000e6800 (reserved) BIOS-e820: 13ef @ 0010 (usable) BIOS-e820: fc00 @ 13ff (ACPI data) BIOS-e820: 0400 @ 13fffc00 (ACPI NVS) BIOS-e820: 0008 @ fff8 (reserved) On node 0 totalpages: 81904 zone(0): 4096 pages. zone(1): 77808 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda1 mem=327616K You are dead on, mem= seems a bit small. Forcing mem=320M on the command line fixes the problem completely. BIOS-provided physical RAM map: BIOS-e820: 0009f800 @ (usable) BIOS-e820: 0800 @ 0009f800 (reserved) BIOS-e820: 00019800 @ 000e6800 (reserved) BIOS-e820: 13ef @ 0010 (usable) BIOS-e820: fc00 @ 13ff (ACPI data) BIOS-e820: 0400 @ 13fffc00 (ACPI NVS) BIOS-e820: 0008 @ fff8 (reserved) On node 0 totalpages: 81920 zone(0): 4096 pages. zone(1): 77824 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda1 mem=320M - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Sat, Feb 24, 2001 at 10:25:42AM -0700, Jeff Lessem wrote:
In your message of: Sat, 24 Feb 2001 09:54:47 CST, you write:
Jeff, are you using the e820 memory map at all ? In particular, are you
using grub or some other buggy bootloader that insists on specifying a
mem= option on the kernel command line ? There should be a kernel command
line message very early on, what does that say ?
Yes, I am using grub, the buggy bootloader. The relevant chunk of
kernal messages are:
BIOS-provided physical RAM map:
BIOS-e820: 0009f800 @ (usable)
BIOS-e820: 0800 @ 0009f800 (reserved)
BIOS-e820: 00019800 @ 000e6800 (reserved)
BIOS-e820: 13ef @ 0010 (usable)
BIOS-e820: fc00 @ 13ff (ACPI data)
BIOS-e820: 0400 @ 13fffc00 (ACPI NVS)
BIOS-e820: 0008 @ fff8 (reserved)
On node 0 totalpages: 81904
zone(0): 4096 pages.
zone(1): 77808 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda1 mem=327616K
You are dead on, mem= seems a bit small. Forcing mem=320M on the
command line fixes the problem completely.
Careful, you're overwriting ACPI data now (and using it as normal RAM).
Can you try one of a) LILO b) a fixed version of grub c) this patch ?
diff -ur linux/arch/i386/kernel/setup.c linux-prumpf/arch/i386/kernel/setup.c
--- linux/arch/i386/kernel/setup.c Fri Feb 23 13:37:38 2001
+++ linux-prumpf/arch/i386/kernel/setup.c Sat Feb 24 09:49:50 2001
@@ -555,30 +555,9 @@
e820.nr_map = 0;
usermem = 1;
} else {
- /* If the user specifies memory size, we
-* blow away any automatically generated
-* size
-*/
- unsigned long start_at, mem_size;
-
- if (usermem == 0) {
- /* first time in: zap the whitelist
-* and reinitialize it with the
-* standard low-memory region.
-*/
- e820.nr_map = 0;
- usermem = 1;
- add_memory_region(0, LOWMEMSIZE(), E820_RAM);
- }
- mem_size = memparse(from+4, from);
+ memparse(from+4, from);
if (*from == '@')
- start_at = memparse(from+1, from);
- else {
- start_at = HIGH_MEMORY;
- mem_size -= HIGH_MEMORY;
- usermem=0;
- }
- add_memory_region(start_at, mem_size, E820_RAM);
+ memparse(from+1, from);
}
}
c = *(from++);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write: Careful, you're overwriting ACPI data now (and using it as normal RAM). Hmm, I guess that would be bad. Can you try one of a) LILO b) a fixed version of grub c) this patch ? I tried LILO and the problem did indeed go away when using that. I guess I'll stick with LILO until Linux or grub (whichever is broken) is fixed. There is just something appealing about a proper boot console on a PC... BIOS-provided physical RAM map: BIOS-e820: 0009f800 @ (usable) BIOS-e820: 0800 @ 0009f800 (reserved) BIOS-e820: 00019800 @ 000e6800 (reserved) BIOS-e820: 13ef @ 0010 (usable) BIOS-e820: fc00 @ 13ff (ACPI data) BIOS-e820: 0400 @ 13fffc00 (ACPI NVS) BIOS-e820: 0008 @ fff8 (reserved) On node 0 totalpages: 81904 zone(0): 4096 pages. zone(1): 77808 pages. zone(2): 0 pages. Kernel command line: auto BOOT_IMAGE=Linux ro root=301 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write: Careful, you're overwriting ACPI data now (and using it as normal RAM). Hmm, I guess that would be bad. Can you try one of a) LILO b) a fixed version of grub c) this patch ? I tried LILO and the problem did indeed go away when using that. I guess I'll stick with LILO until Linux or grub (whichever is broken) is fixed. There is just something appealing about a proper boot console on a PC... Even though I wasn't much help on this, it's nice to know what was different on your config that was causing problems while I wasn't seeing any issues. I sat here for almost an hour last night trying to figure out why your machines memory map would different than mine (I have 320MB of RAM as well, so they should have been the same). The thought that you might be using a different boot loader never even crossed my mind. I've always used LILO so that's why I didn't see any problems. It's nice to know it wasn't just working for me by accident. Later, Tom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Thu, 22 Feb 2001, Jeff Lessem wrote: > > In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write: > >Hmm.. You shouldn't be loading any i82365 module at all. You should load > >the "yenta_socket" module. > > I had gone back to my old ways of useing the external PCMCIA stuff. > Here are the relevant lspci --vvxx listings using the yenta driver > builtin to the kernel. The main difference I notice between the > working and broken setup is that the memory locations of the CardBus > controller are different. That should be harmless - they are both unique, and it's just due to different PCI region allocation for the new PCI code (and when soft-booting from an older setup it will remember and honor the old address). The much more likely cause is the "magic registers" for the Texas Instruments PCI1225, namely works broken 81: b0 90 a8: 11 10 Although it worries me a bit that your second controller also seems to have differences in the BridgeCtl thing (16bInt). Can you try if a broken setup is fixed by doing a setpci -s 00.04.0 81.b=b0 setpci -s 00.04.0 a8.b=11 setpci -s 00.04.1 81.b=b0 setpci -s 00.04.1 81.b=11 or similar? Also, how much memory does this machine have? That "13ff" does worry me a bit.. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On 22 Feb 2001 23:01:14 -0800, Barry K. Nathan wrote: > Tom Sightler wrote: > > What's strange is that I have the exact same type of machine and I don't see > > this problem, could you forward me your kernel config as well? I'll compare > > that, and your info from your previous message to mine and see if we can > > find a difference. > > Another variable, perhaps, is the BIOS version. (If you have Quick Boot or > whatever it's called enabled (which is the factory default), you'll have > to hit F2 when the "Dell" screen appears at startup, to try to enter the > BIOS setup (before Setup starts, it will show the BIOS version number and > a bunch of other stuff).) > > I have a working machine, with BIOS A04. (Strangely enough, my Inspiron > 5000e came with BIOS A03, and a floppy disk with A04, along with > instructions with a "do not use this BIOS flasher unless you have [some > werid video-related problem]" type of disclaimer. Since I was having those > APM oopses under Linux, I decided to try upgrading. It didn't fix the > oopses, though.) I have a BIOS that'll fix your APM problems, at a minimum. Anyone who wants it can email me privately, since the site I put it up on no longer exists... Brad Douglas [EMAIL PROTECTED] http://www.linux-fbdev.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Thu, 22 Feb 2001, Jeff Lessem wrote: In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write: Hmm.. You shouldn't be loading any i82365 module at all. You should load the "yenta_socket" module. I had gone back to my old ways of useing the external PCMCIA stuff. Here are the relevant lspci --vvxx listings using the yenta driver builtin to the kernel. The main difference I notice between the working and broken setup is that the memory locations of the CardBus controller are different. That should be harmless - they are both unique, and it's just due to different PCI region allocation for the new PCI code (and when soft-booting from an older setup it will remember and honor the old address). The much more likely cause is the "magic registers" for the Texas Instruments PCI1225, namely works broken 81: b0 90 a8: 11 10 Although it worries me a bit that your second controller also seems to have differences in the BridgeCtl thing (16bInt). Can you try if a broken setup is fixed by doing a setpci -s 00.04.0 81.b=b0 setpci -s 00.04.0 a8.b=11 setpci -s 00.04.1 81.b=b0 setpci -s 00.04.1 81.b=11 or similar? Also, how much memory does this machine have? That "13ff" does worry me a bit.. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On 22 Feb 2001 23:01:14 -0800, Barry K. Nathan wrote: Tom Sightler wrote: What's strange is that I have the exact same type of machine and I don't see this problem, could you forward me your kernel config as well? I'll compare that, and your info from your previous message to mine and see if we can find a difference. Another variable, perhaps, is the BIOS version. (If you have Quick Boot or whatever it's called enabled (which is the factory default), you'll have to hit F2 when the "Dell" screen appears at startup, to try to enter the BIOS setup (before Setup starts, it will show the BIOS version number and a bunch of other stuff).) I have a working machine, with BIOS A04. (Strangely enough, my Inspiron 5000e came with BIOS A03, and a floppy disk with A04, along with instructions with a "do not use this BIOS flasher unless you have [some werid video-related problem]" type of disclaimer. Since I was having those APM oopses under Linux, I decided to try upgrading. It didn't fix the oopses, though.) I have a BIOS that'll fix your APM problems, at a minimum. Anyone who wants it can email me privately, since the site I put it up on no longer exists... Brad Douglas [EMAIL PROTECTED] http://www.linux-fbdev.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write: >Hmm.. You shouldn't be loading any i82365 module at all. You should load >the "yenta_socket" module. I had gone back to my old ways of useing the external PCMCIA stuff. Here are the relevant lspci --vvxx listings using the yenta driver builtin to the kernel. The main difference I notice between the working and broken setup is that the memory locations of the CardBus controller are different. --working with yenta 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00: 86 80 90 71 06 01 10 22 03 00 00 06 00 40 00 00 10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 0c 02 00 ff 00 00 00 09 03 10 11 11 00 10 13 11 60: 00 00 10 20 28 28 28 28 00 00 00 00 00 a0 00 00 70: 20 1f 0a 78 a0 01 07 01 26 1c dc 00 10 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 04 61 00 00 00 05 00 00 00 00 00 00 a0: 02 00 10 00 02 02 00 1f 00 00 00 00 00 00 00 00 b0: 80 20 00 00 30 00 00 00 00 00 74 13 20 10 00 00 c0: 00 00 00 00 00 00 00 00 18 0c 80 01 18 00 00 00 d0: 00 00 00 00 00 00 00 00 0c 00 00 00 00 00 00 00 e0: 4c ad ff bb 8a 3e 00 80 2c d3 f7 cf 9d 3e 00 00 f0: 40 01 00 00 00 f8 00 60 20 0f 00 00 00 00 00 00 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B+ 00: 86 80 91 71 1f 00 20 02 03 00 04 06 00 80 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 40 20 20 a0 22 20: 00 f4 00 f4 00 f8 f0 fb 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: COMPAL Electronics Inc: Unknown device 0011 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 4c 10 1c ac 07 00 10 02 01 00 07 06 08 a8 82 00 10: 00 00 00 68 a0 00 00 02 00 02 02 b0 00 00 00 14 20: 00 f0 3f 14 00 00 40 14 00 f0 7f 14 00 18 00 00 30: fc 18 00 00 00 1c 00 00 fc 1c 00 00 ff 01 c0 05 40: c0 14 11 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 b0 44 20 00 00 00 00 00 00 00 00 02 1c 02 01 90: c0 82 66 60 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 21 7e 00 00 80 00 11 00 00 00 0f 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: COMPAL Electronics Inc: Unknown device 0011 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 4c 10 1c ac 07 00 10 02 01 00 07 06 08 a8 82 00 10: 00 10 00 68 a0 00 00 02 00 06 06 b0 00 00 80 14 20: 00 f0 bf 14 00 00 c0 14 00 f0 ff 14 00 30 00 00 30: fc 30 00 00 00 34 00 00 fc 34 00 00 ff 01 c0 05 40: c0 14 11 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 b0 44 20 00 00 00 00 00 00 00 00 02 1c 02 01 90: c0 82 66 60 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 21 7e 00 00 80 00 11 00 00 00 0f 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
> I took your advice and used the kernel drivers from 2.4.2. I built > the Cardbus and i82365 drivers into the kernel. This shows the exact > same behavior, after a power-on reboot I get: You don't need the i82365 driver, only the Cardbus (yenta) driver. I don't think this would cause your problem, but it's possible, maybe try without it. > and though the cardmgr loads it does not respond to card events, > i.e. inserting a card produces *no* effect, there is not a beep, or > any logged messages. Rebooting with 2.2.17 fixes the problem and > 2.4.2 then works again. It looks to me like something in the PCI bus > isn't setup correctly by the 2.4 kernels, but chasing that down is way > beyond my ability, hence the post to linux-kernel. What's strange is that I have the exact same type of machine and I don't see this problem, could you forward me your kernel config as well? I'll compare that, and your info from your previous message to mine and see if we can find a difference. Later, Tom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Thu, 22 Feb 2001, Jeff Lessem wrote: > > No problem, the listings are below. Both listings were done on a > freshly booted system. The only difference in system states was that > the i82365 modules had loaded. Hmm.. You shouldn't be loading any i82365 module at all. You should load the "yenta_socket" module. One of the major differences between working and non-working is that the non-working thing doesn't have the PCI latency register set. The yenta driver explicitly sets the latency and cache size numbers, so it reall ylook slike you should just use that driver and it should work. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Thu, 22 Feb 2001 19:40:03 PST, you write: >Can you do a full "lspci -vvxxx" (as root) both on a working and a >non-working setup, and send the two files to the kernel list and cc to >me? No problem, the listings are below. Both listings were done on a freshly booted system. The only difference in system states was that the i82365 modules had loaded. The "broken" listing was done after a power-off boot into 2.4.2, and the "working" listing was done after a power-on boot to 2.4.2 from 2.2.17. If any additional information would be helpful, just ask. --Working lspci -vvxxx in 2.4.2 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00: 86 80 90 71 06 01 10 22 03 00 00 06 00 40 00 00 10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 0c 02 00 ff 00 00 00 09 03 10 11 11 00 10 13 11 60: 00 00 10 20 28 28 28 28 00 00 00 00 00 a0 00 00 70: 20 1f 0a 78 a0 01 07 01 26 1c dc 00 10 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 04 61 00 00 00 05 00 00 00 00 00 00 a0: 02 00 10 00 02 02 00 1f 00 00 00 00 00 00 00 00 b0: 80 20 00 00 30 00 00 00 00 00 11 13 20 10 00 00 c0: 00 00 00 00 00 00 00 00 18 0c 80 01 18 00 00 00 d0: 00 00 00 00 00 00 00 00 0c 00 00 00 00 00 00 00 e0: 4c ad ff bb 8a 3e 00 80 2c d3 f7 cf 9d 3e 00 00 f0: 40 01 00 00 00 f8 00 60 20 0f 00 00 00 00 00 00 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B+ 00: 86 80 91 71 1f 00 20 02 03 00 04 06 00 80 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 40 20 20 a0 22 20: 00 f4 00 f4 00 f8 f0 fb 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: COMPAL Electronics Inc: Unknown device 0011 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 4c 10 1c ac 07 00 10 02 01 00 07 06 08 a8 82 00 10: 00 00 00 68 a0 00 00 02 00 02 05 20 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 c0 07 40: c0 14 11 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 b0 44 20 00 00 00 00 00 00 00 00 02 1c 02 01 90: c0 82 66 60 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 21 7e 00 00 80 00 11 00 00 00 0f 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: COMPAL Electronics Inc: Unknown device 0011 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 4c 10 1c ac 07 00 10 02 01 00 07 06 08 a8 82 00 10: 00 10 00 68 a0 00 00 02 00 06 09 20 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 c0 07 40: c0 14 11 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 b0 44 20 00 00 00 00 00 00 00 00 02 1c 02 01 90: c0 82 66 60 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 21 7e 00 00 80 00 11 00 00 00
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Thu, 22 Feb 2001 15:19:15 EST, you write: >I'm a little confused by what you mean when you say PCMCIA modules, are you >referring to the actual PCMCIA socket drivers themselves? If so, perhaps Yes, the i82365 module does not load. >this is why you have problems and I don't. Linux 2.4 includes support for >the Cardbus driver internally, simply make sure you enable Hot Plug support, >and build PCMCIA and Cardbus support right into the kernel. I took your advice and used the kernel drivers from 2.4.2. I built the Cardbus and i82365 drivers into the kernel. This shows the exact same behavior, after a power-on reboot I get: Yenta IRQ list 06d8, PCI irq11 Socket status: 3006 Yenta IRQ list 06d8, PCI irq11 Socket status: 3006 and the wvlan_cs module from the external PCMCIA package loads and works without problems. However, after powering off the status message during boot is: Yenta IRQ list , PCI irq11 Socket status: 35fb54ce Yenta IRQ list , PCI irq11 Socket status: 22b1dcee and though the cardmgr loads it does not respond to card events, i.e. inserting a card produces *no* effect, there is not a beep, or any logged messages. Rebooting with 2.2.17 fixes the problem and 2.4.2 then works again. It looks to me like something in the PCI bus isn't setup correctly by the 2.4 kernels, but chasing that down is way beyond my ability, hence the post to linux-kernel. -- Jeff Lessem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Thu, 22 Feb 2001 15:19:15 EST, you write: I'm a little confused by what you mean when you say PCMCIA modules, are you referring to the actual PCMCIA socket drivers themselves? If so, perhaps Yes, the i82365 module does not load. this is why you have problems and I don't. Linux 2.4 includes support for the Cardbus driver internally, simply make sure you enable Hot Plug support, and build PCMCIA and Cardbus support right into the kernel. I took your advice and used the kernel drivers from 2.4.2. I built the Cardbus and i82365 drivers into the kernel. This shows the exact same behavior, after a power-on reboot I get: Yenta IRQ list 06d8, PCI irq11 Socket status: 3006 Yenta IRQ list 06d8, PCI irq11 Socket status: 3006 and the wvlan_cs module from the external PCMCIA package loads and works without problems. However, after powering off the status message during boot is: Yenta IRQ list , PCI irq11 Socket status: 35fb54ce Yenta IRQ list , PCI irq11 Socket status: 22b1dcee and though the cardmgr loads it does not respond to card events, i.e. inserting a card produces *no* effect, there is not a beep, or any logged messages. Rebooting with 2.2.17 fixes the problem and 2.4.2 then works again. It looks to me like something in the PCI bus isn't setup correctly by the 2.4 kernels, but chasing that down is way beyond my ability, hence the post to linux-kernel. -- Jeff Lessem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Thu, 22 Feb 2001 19:40:03 PST, you write: Can you do a full "lspci -vvxxx" (as root) both on a working and a non-working setup, and send the two files to the kernel list and cc to me? No problem, the listings are below. Both listings were done on a freshly booted system. The only difference in system states was that the i82365 modules had loaded. The "broken" listing was done after a power-off boot into 2.4.2, and the "working" listing was done after a power-on boot to 2.4.2 from 2.2.17. If any additional information would be helpful, just ask. --Working lspci -vvxxx in 2.4.2 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 64 Region 0: Memory at e000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 1.0 Status: RQ=31 SBA+ 64bit- FW- Rate=x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate=none 00: 86 80 90 71 06 01 10 22 03 00 00 06 00 40 00 00 10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 0c 02 00 ff 00 00 00 09 03 10 11 11 00 10 13 11 60: 00 00 10 20 28 28 28 28 00 00 00 00 00 a0 00 00 70: 20 1f 0a 78 a0 01 07 01 26 1c dc 00 10 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 04 61 00 00 00 05 00 00 00 00 00 00 a0: 02 00 10 00 02 02 00 1f 00 00 00 00 00 00 00 00 b0: 80 20 00 00 30 00 00 00 00 00 11 13 20 10 00 00 c0: 00 00 00 00 00 00 00 00 18 0c 80 01 18 00 00 00 d0: 00 00 00 00 00 00 00 00 0c 00 00 00 00 00 00 00 e0: 4c ad ff bb 8a 3e 00 80 2c d3 f7 cf 9d 3e 00 00 f0: 40 01 00 00 00 f8 00 60 20 0f 00 00 00 00 00 00 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 128 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: 2000-2fff Memory behind bridge: f400-f40f Prefetchable memory behind bridge: f800-fbff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B+ 00: 86 80 91 71 1f 00 20 02 03 00 04 06 00 80 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 40 20 20 a0 22 20: 00 f4 00 f4 00 f8 f0 fb 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: COMPAL Electronics Inc: Unknown device 0011 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 168, cache line size 08 Interrupt: pin A routed to IRQ 11 Region 0: Memory at 6800 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=05, sec-latency=32 I/O window 0: -0003 I/O window 1: -0003 BridgeCtl: Parity- SERR- ISA- VGA- MAbort- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 4c 10 1c ac 07 00 10 02 01 00 07 06 08 a8 82 00 10: 00 00 00 68 a0 00 00 02 00 02 05 20 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 c0 07 40: c0 14 11 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 b0 44 20 00 00 00 00 00 00 00 00 02 1c 02 01 90: c0 82 66 60 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 21 7e 00 00 80 00 11 00 00 00 0f 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
On Thu, 22 Feb 2001, Jeff Lessem wrote: No problem, the listings are below. Both listings were done on a freshly booted system. The only difference in system states was that the i82365 modules had loaded. Hmm.. You shouldn't be loading any i82365 module at all. You should load the "yenta_socket" module. One of the major differences between working and non-working is that the non-working thing doesn't have the PCI latency register set. The yenta driver explicitly sets the latency and cache size numbers, so it reall ylook slike you should just use that driver and it should work. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
I took your advice and used the kernel drivers from 2.4.2. I built the Cardbus and i82365 drivers into the kernel. This shows the exact same behavior, after a power-on reboot I get: You don't need the i82365 driver, only the Cardbus (yenta) driver. I don't think this would cause your problem, but it's possible, maybe try without it. and though the cardmgr loads it does not respond to card events, i.e. inserting a card produces *no* effect, there is not a beep, or any logged messages. Rebooting with 2.2.17 fixes the problem and 2.4.2 then works again. It looks to me like something in the PCI bus isn't setup correctly by the 2.4 kernels, but chasing that down is way beyond my ability, hence the post to linux-kernel. What's strange is that I have the exact same type of machine and I don't see this problem, could you forward me your kernel config as well? I'll compare that, and your info from your previous message to mine and see if we can find a difference. Later, Tom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
In your message of: Thu, 22 Feb 2001 20:37:15 PST, you write: Hmm.. You shouldn't be loading any i82365 module at all. You should load the "yenta_socket" module. I had gone back to my old ways of useing the external PCMCIA stuff. Here are the relevant lspci --vvxx listings using the yenta driver builtin to the kernel. The main difference I notice between the working and broken setup is that the memory locations of the CardBus controller are different. --working with yenta 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 64 Region 0: Memory at e000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 1.0 Status: RQ=31 SBA+ 64bit- FW- Rate=x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate=none 00: 86 80 90 71 06 01 10 22 03 00 00 06 00 40 00 00 10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 0c 02 00 ff 00 00 00 09 03 10 11 11 00 10 13 11 60: 00 00 10 20 28 28 28 28 00 00 00 00 00 a0 00 00 70: 20 1f 0a 78 a0 01 07 01 26 1c dc 00 10 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 04 61 00 00 00 05 00 00 00 00 00 00 a0: 02 00 10 00 02 02 00 1f 00 00 00 00 00 00 00 00 b0: 80 20 00 00 30 00 00 00 00 00 74 13 20 10 00 00 c0: 00 00 00 00 00 00 00 00 18 0c 80 01 18 00 00 00 d0: 00 00 00 00 00 00 00 00 0c 00 00 00 00 00 00 00 e0: 4c ad ff bb 8a 3e 00 80 2c d3 f7 cf 9d 3e 00 00 f0: 40 01 00 00 00 f8 00 60 20 0f 00 00 00 00 00 00 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 128 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: 2000-2fff Memory behind bridge: f400-f40f Prefetchable memory behind bridge: f800-fbff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B+ 00: 86 80 91 71 1f 00 20 02 03 00 04 06 00 80 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 40 20 20 a0 22 20: 00 f4 00 f4 00 f8 f0 fb 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:04.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: COMPAL Electronics Inc: Unknown device 0011 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 168, cache line size 08 Interrupt: pin A routed to IRQ 11 Region 0: Memory at 6800 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=02, sec-latency=176 Memory window 0: 1400-143ff000 (prefetchable) Memory window 1: 1440-147ff000 I/O window 0: 1800-18ff I/O window 1: 1c00-1cff BridgeCtl: Parity- SERR- ISA- VGA- MAbort- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 4c 10 1c ac 07 00 10 02 01 00 07 06 08 a8 82 00 10: 00 00 00 68 a0 00 00 02 00 02 02 b0 00 00 00 14 20: 00 f0 3f 14 00 00 40 14 00 f0 7f 14 00 18 00 00 30: fc 18 00 00 00 1c 00 00 fc 1c 00 00 ff 01 c0 05 40: c0 14 11 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 b0 44 20 00 00 00 00 00 00 00 00 02 1c 02 01 90: c0 82 66 60 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 21 7e 00 00 80 00 11 00 00 00 0f 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00
