--- Dr Andrew C Aitchison
<[EMAIL PROTECTED]> wrote:
> Did you add a new disk ?
> I'm wondering if you have some sort of conflict
> (interrupts?)
> between the new disk and the graphics card ?
Hmm, no... just swapped functionality of the disks
already in the system. HD 1 now runs Windows
exclusively. This was the disk with the corrupted
partition table, and is now set up so I don't care if
it dies again... HD 2 is now totally dedicated to
Linux, and contains (will contain) my important
working files. I did, however add a floppy drive
recently. Just tried removing it before replying to
your post, but still have the same problem.
I agree that it does seem to act like an interrupt
conflict. I don't think it is, however... here is my
/proc/interrupts:
CPU0 CPU1
0: 3742 2803 IO-APIC-edge timer
1: 92 75 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 1 0 IO-APIC-edge rtc
11: 2 2 IO-APIC-level eth0
12: 19 14 IO-APIC-edge PS/2 Mouse
14: 44 16 IO-APIC-edge ide0
15: 1388 1736 IO-APIC-edge ide1
NMI: 0 0
LOC: 6467 6466
ERR: 0
MIS: 0
I find it odd that the display controller doesn't show
up here, but in the bios boot screen it says that it
is assigned IRQ 10.
I'm not sure this is the right route... I think maybe
this is a bug in the Linux kernel... I'm going to try
and build a minimized kernel with no frame buffer
support to see if that helps.
Thanks for your time,
--dave
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
