nabled. progress!
Linus wants to "debug this to death" (his words, not mine) but I don't
have access to the suspect hardware for the next five weeks, and it will
probably be serviced some time during those weeks.
Thank you for being patient, Linus. And sorry for not being able to
provide
Linus Torvalds wrote:
>
> On Wed, 11 Oct 2000, Dag B wrote:
> > 2.4.0-test9/10p1
>
> Can you do another test with this (ie in-kernel pcmcia), AND enable
> debugging in both drivers/pci/pci.c and in arch/i386/kernel/pci-i386.h (in
[snip]
> drivers/pcmcia/yenta.c to alloc
irk with this particular laptop model. (CPiA 366XT)
Any takers?
Let me know what debug-switches and knobs I can turn on, and what
information
I can provide.
Regards,
Dag B
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
aptop model. (CPiA 366XT)
Any takers?
Let me know what debug-switches and knobs I can turn on, and what
information
I can provide.
Regards,
Dag B
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Linus Torvalds wrote:
On Wed, 11 Oct 2000, Dag B wrote:
2.4.0-test9/10p1
Can you do another test with this (ie in-kernel pcmcia), AND enable
debugging in both drivers/pci/pci.c and in arch/i386/kernel/pci-i386.h (in
[snip]
drivers/pcmcia/yenta.c to allocate more than 4MB of PCI memory
the driver for `blah' from probing
0x300-0x31f.
The more recent Linux documentation says iomem, while the majority of
other documentation says io port. Given that /proc/ contains both, I'd
like to see a clearification...
Dag B
-
To unsubscribe from this list: send the line "unsubscribe linux-k
agblap:~# cat /proc/interrupts
CPU0
0: 92925 XT-PIC timer
1: 3 XT-PIC keyboard
2: 0 XT-PIC cascade
11:431 XT-PIC Texas Instruments PCI1225, Texas
Instruments PCI1225 (#2), eth0
12: 0 XT-PIC PS/2 Mouse
13: 0 XT-PIC fpu
14:874 XT-PIC ide0
15: 3 XT-PIC ide1
NMI: 0
ERR: 0
Dag B
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
urce collisions
tulip_attach(06:00.0)
PCI: Device 06:00.0 not available because of resource collisions
tulip_attach(06:00.0)
PCI: Device 06:00.0 not available because of resource collisions
Anyone able to tell me what resource collisions we are talking about
here?
Dag B
-
To unsubscribe from this list
(06:00.0)
PCI: Device 06:00.0 not available because of resource collisions
tulip_attach(06:00.0)
PCI: Device 06:00.0 not available because of resource collisions
Anyone able to tell me what resource collisions we are talking about
here?
Dag B
-
To unsubscribe from this list: send the line
removable hardware, but..)
I'd like to note that the hardware is known good.
Any takers?
Dag B
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
like to note that the hardware is known good.
Any takers?
Dag B
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
This is very verbose. Sorry. I much prefer to toss all the pieces on the
table at the same time.
Dag B
[1.] One line summary of the problem:
-test7/8 version of xircom_tulip_cb does not enable my Xircom Realport
(RBEM56G-100)
Nor any of the other kernels I have tried...
[2.] Full
12 matches
Mail list logo
