On Fri, Feb 09, 2007 at 02:04:52PM -0600, Tarek Soliman wrote: > 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. some bios' let you pick pci or agp for video. Also, maybe the agp memory allocation is configurable. you could blacklist the agp modules in /etc/modprobe.d/blacklist A
Attachment:
signature.asc
Description: Digital signature