lkml.org 
[lkml]   [2001]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [Acpi] AGP support locks X - was Re: sony vaio, crude workar
From
Date
Ok, my X server starts now. 

When I try to switch to a virtual text console, my screen blanks. I
can still execute a shutdown command blindly. This implies the kernel
hasn't locked up.

There must be some conflict with the VGA controller still? Maybe the
work around to fix the dead console at boot?

- 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.

> 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.
> >>
-
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/

\
 
 \ /
  Last update: 2005-03-22 12:57    [W:0.028 / U:0.276 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site