Re: Kernel panic on PCI video card with 2.6.x on Dell Dimension 2300
On Fri, Feb 09, 2007 at 02:38:58PM -0500, John Stoffel wrote:
> >>>>> "Tarek" == Tarek Soliman <tsoliman@zeusmail.bounceme.net> writes:
>
> Tarek> I have done this and even dist-upgraded to etch. Every time I
> Tarek> put the PCI card back, it becomes the source of monitor output
> Tarek> during boot but then the booting fails. I am looking for a way
> Tarek> to figure out at which part the booting fails but I don't know
> Tarek> where kernel panic logs get stored (if at all).
>
> If you have a second computer, then what you can do is setup a serial
> console and capture the bootup messages on the second computer. A
> real godsend. You can even setup things so that you'll see messages
> on both screens, though after a point, the console messages will only
> goto the second screen.
>
After an ACPI/AIPC problem was disabled by boot params I got one line
further; it is not a hard lockup anymore, but an "oops I'm going to panic
soon type" error.
I found that the problem is that the onboard video card (i845g) is
"stealing" memory and right after it get detected by AGPART the kernel
trips over trying to access the address FFFFD0B0.
After some research I'm guessing it is a video memory vs main memory.
I tried different values for mem=xx as a kernel boot parameter. This
only results in different numbers in the AGPART deciding "max memory
allocated to the video card" I wish I could try forcing this to
something.
Can I skip this whole AGPART detection part? I am going to be using a
PCI video card. The onboard card needs to be ignored or something.
>
> Hmmm... have you tried pinging the box after bootup? Is it on the
> network? Is it just that the screen is disabled or non-responsive,
> not that the system hasn't booted up?
>
> Try booting without starting X (or GDM/XDM) and seeing what happens
> then.
>
There is no X yet. This is an install of sarge with nothing selected
from tasksel. It either boots fine with 2.4 or panics during
hardware detection with 2.6.x
--
Tarek
Reply to: