Messages in this thread | | | Subject | AGP support locks X kernel v2.4.9 | From | Nick Papadonis <> | Date | 22 Aug 2001 13:31:05 -0400 |
| |
New information:
I tried compiling agp support and the i810 DRI as modules for kernel v2.4.9. X exits out with:
(II) I810(0): Buffer map : bfb000 (II) I810(0): [drm] added 256 4096 byte DMA buffers I810 Dma Initialization Failed
When recompiling the v2.4.8 kernel with the same configuration, X starts fine.
I wonder what the delta between the two is?
- Nick
bmihulka@hulkster.net writes:
> I did experience this. But when you choose AGP as a module it disables > the drm of the i810. I then added it back as a module and the X server would > not work. Without the i810 drm module it will work. I did not test AGP in the > kernel without the drm module, which may work. > > On a side note the 2.4.5 kernels acpi implimentation will show the correct > battery and ac adaptor status. The stock kernels after that will not without > the new acpi patches. I have also had the problem of a shutdown will lock the > system and I have to pull the plug and battery to turn off. > > Brian > > On 18-Aug-2001 Nick Papadonis wrote: > > This solved the problem. Apparently AGP has to be built as a module > > in kernels v2.4.8 or X will lock up? Anyone else experience this? > > > >> I'm not sure that this is the problem you are having, > >> but I had a problem with X when I was playing with the > >> ACPI stuff and recompiling the kernel on my vaio. Try > >> setting CONFIG_AGP=m (i.e. make AGP support a module, > >> as opposed to being compiled in-kernel.) if it isn't. > >> Once I did that, X started up just fine. Good luck. > >> > >> Dave > > > > > > Dave Morgan <daves_spam_account@yahoo.com> writes: > >> >> I tried this and it doesn't disable the console. > >> The /proc/acpi > >> >> represents the correct power status. When I tried > >> to > >> >> start up X the following error occurs: > >> >> > >> >> I810 Dma Initialization Failed > >> >> XIO: fatal IO error 104 (Connection reset by peer) > >> >on X server > >> >":0.0" > >> >> after 0 requests (0 known processed) with 0 > >> >events remaining. > >> >> > >> >> So the work around must break something else? > >> > >> >Follup: > >> > >> >This isn't because of the ACPI code. It's something > >> >that happens in > >> >my 2.4.8 kernel wo ACPI compiled in. This behavior > >> is >not shown with > >> >the 2.2.16 kernel.
-- Nick - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |