On Fri, Apr 01, 2005 at 11:17:08AM +0200, Romano Giannetti wrote:
> and nothing more. Well, this was done with the double console, so that I
> will try again as soon as I have a bit of time with just the serial console
> on.
Much better now. Configuration, dmesg at boot, etc are at
On Thu, Mar 31, 2005 at 09:54:33PM +0200, Maximilian Engelhardt wrote:
> On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
> >
> > It happens exactly the same on my laptop, sony vaio whose configuration is
> >
> > http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
>
On Thu, Mar 31, 2005 at 09:54:33PM +0200, Maximilian Engelhardt wrote:
On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
It happens exactly the same on my laptop, sony vaio whose configuration is
http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
I was
On Fri, Apr 01, 2005 at 11:17:08AM +0200, Romano Giannetti wrote:
and nothing more. Well, this was done with the double console, so that I
will try again as soon as I have a bit of time with just the serial console
on.
Much better now. Configuration, dmesg at boot, etc are at
On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
>
> It happens exactly the same on my laptop, sony vaio whose configuration is
>
> http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
>
> Next week is Easter holyday here, I will try to connect my Psion casio as
>
On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
It happens exactly the same on my laptop, sony vaio whose configuration is
http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
Next week is Easter holyday here, I will try to connect my Psion casio as
serial
On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
>
> It happens exactly the same on my laptop, sony vaio whose configuration is
>
> http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
>
> Next week is Easter holyday here, I will try to connect my Psion casio as
>
On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
It happens exactly the same on my laptop, sony vaio whose configuration is
http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
Next week is Easter holyday here, I will try to connect my Psion casio as
serial
On Thu, Mar 17, 2005 at 09:05:12PM +0100, Maximilian Engelhardt wrote:
> On Mon, 2005-02-14 at 22:20 +0100, Pavel Machek wrote:
> > Video issues with S3 resume
> > ~~~
> > 2003-2005, Pavel Machek
> >
> Tried all this on my Laptop but
On Thu, Mar 17, 2005 at 09:05:12PM +0100, Maximilian Engelhardt wrote:
On Mon, 2005-02-14 at 22:20 +0100, Pavel Machek wrote:
Video issues with S3 resume
~~~
2003-2005, Pavel Machek
Tried all this on my Laptop but nothing
On Mon, 2005-02-14 at 22:20 +0100, Pavel Machek wrote:
> Hi!
>
> Stefan provided me initial list of machines where S3 works (including
> video). If you have machine that is not on the list, please send me a
> diff. If you have eMachines... I'd like you to try playing with
> vbetool (it worked for
On Mon, 2005-02-14 at 22:20 +0100, Pavel Machek wrote:
Hi!
Stefan provided me initial list of machines where S3 works (including
video). If you have machine that is not on the list, please send me a
diff. If you have eMachines... I'd like you to try playing with
vbetool (it worked for me),
Hi!
> > > > * MySQL (hinders the actual suspension process and kicks the pc
> > > back to
> > > > where it was)
> > >
> > > Try this patch...
> > > Pavel
> > >
> > > --- clean/kernel/signal.c 2005-02-03
Hi.
On Tue, 2005-03-15 at 19:10, Li Shaohua wrote:
> Hi,
> On Mon, 2005-03-14 at 16:00, Pavel Machek wrote:
> > Hi!
> >
> > > * MySQL (hinders the actual suspension process and kicks the pc
> > back to
> > > where it was)
> >
> > Try this patch...
> >
Hi,
On Mon, 2005-03-14 at 16:00, Pavel Machek wrote:
> Hi!
>
> > * MySQL (hinders the actual suspension process and kicks the pc
> back to
> > where it was)
>
> Try this patch...
> Pavel
>
> --- clean/kernel/signal.c
Hi,
On Mon, 2005-03-14 at 16:00, Pavel Machek wrote:
Hi!
* MySQL (hinders the actual suspension process and kicks the pc
back to
where it was)
Try this patch...
Pavel
--- clean/kernel/signal.c 2005-02-03
Hi.
On Tue, 2005-03-15 at 19:10, Li Shaohua wrote:
Hi,
On Mon, 2005-03-14 at 16:00, Pavel Machek wrote:
Hi!
* MySQL (hinders the actual suspension process and kicks the pc
back to
where it was)
Try this patch...
Hi!
* MySQL (hinders the actual suspension process and kicks the pc
back to
where it was)
Try this patch...
Pavel
--- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100
+++
On Monday 14 March 2005 09:00, Pavel Machek wrote:
> Hi!
>
> > * MySQL (hinders the actual suspension process and kicks the pc back to
> > where it was)
>
> Try this patch...
Works nicely. Thanks.
Jan
--
Most people don't need a great deal of love nearly so much as they need
a steady
Hi!
> * MySQL (hinders the actual suspension process and kicks the pc back to
> where it was)
Try this patch...
Pavel
--- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100
+++ linux/kernel/signal.c
Hi!
* MySQL (hinders the actual suspension process and kicks the pc back to
where it was)
Try this patch...
Pavel
--- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100
+++ linux/kernel/signal.c
On Monday 14 March 2005 09:00, Pavel Machek wrote:
Hi!
* MySQL (hinders the actual suspension process and kicks the pc back to
where it was)
Try this patch...
Works nicely. Thanks.
Jan
--
Most people don't need a great deal of love nearly so much as they need
a steady supply.
-
On Monday 14 February 2005 22:11, Pavel Machek wrote:
> Hi!
>
> Stefan provided me initial list of machines where S3 works (including
> video). If you have machine that is not on the list, please send me a
> diff. If you have eMachines... I'd like you to try playing with
> vbetool (it worked for
On Monday 14 February 2005 22:11, Pavel Machek wrote:
Hi!
Stefan provided me initial list of machines where S3 works (including
video). If you have machine that is not on the list, please send me a
diff. If you have eMachines... I'd like you to try playing with
vbetool (it worked for me),
On Mon, 14 Feb 2005 22:11:05 +0100, Pavel Machek <[EMAIL PROTECTED]> wrote:
> Table of known working systems:
>
> Model hack (or "how to do it")
> --
> IBM TP R32 / Type 2658-MMG none (1)
>
Pavel Machek wrote:
> Table of known working systems:
>
> Model hack (or "how to do it")
> --
IBM Thinkpad X40 (Type 2371-7JG) acpi_sleep=s3_bios,s3_mode
--
Stefan Seyfried, QA / R Team Mobile
Pavel Machek wrote:
Table of known working systems:
Model hack (or how to do it)
--
IBM Thinkpad X40 (Type 2371-7JG) acpi_sleep=s3_bios,s3_mode
--
Stefan Seyfried, QA / RD Team Mobile
On Mon, 14 Feb 2005 22:11:05 +0100, Pavel Machek [EMAIL PROTECTED] wrote:
Table of known working systems:
Model hack (or how to do it)
--
IBM TP R32 / Type 2658-MMG none (1)
Athlon HP
Stefan Seyfried wrote:
> Pavel Machek wrote:
>> Hi!
>
>> Table of known working systems:
>>
>> Model hack (or "how to do it")
>> --
>
> IBM Thinkpad T20 (S3 Inc. 86C270-294 Savage/IX-MV), model
Pavel Machek wrote:
> Hi!
> Table of known working systems:
>
> Model hack (or "how to do it")
> --
IBM Thinkpad T20 (S3 Inc. 86C270-294 Savage/IX-MV), model 2647-44G
"Just works" out of the
Pavel Machek wrote:
Hi!
Table of known working systems:
Model hack (or how to do it)
--
IBM Thinkpad T20 (S3 Inc. 86C270-294 Savage/IX-MV), model 2647-44G
Just works out of the box. S1
Stefan Seyfried wrote:
Pavel Machek wrote:
Hi!
Table of known working systems:
Model hack (or how to do it)
--
IBM Thinkpad T20 (S3 Inc. 86C270-294 Savage/IX-MV), model 2647-44G
Just
Pavel Machek wrote:
>> this server crashes when switching to the console or shutting
>> down (crashing is sometimes, not always), very nice screen which
>> slowly turns white
>
> Hmm, it would be nice to be able to trigger "go white" on purpose --
> it looks like screen is burning
Hi!
> > > - DRI must be disabled I guess?! Even with newer X server (x.org)?
> >
> > You still didn't state which X server are you using. In short, XFree86 4.4,
>
> I have stated it several times, but here a sum up:
>
> - XFree86 4.3 (debian/sid)
> no work
> - X.Org 6.8.1.99 (debian
Hi!
- DRI must be disabled I guess?! Even with newer X server (x.org)?
You still didn't state which X server are you using. In short, XFree86 4.4,
I have stated it several times, but here a sum up:
- XFree86 4.3 (debian/sid)
no work
- X.Org 6.8.1.99 (debian -dri-trunk stuff
Pavel Machek wrote:
this server crashes when switching to the console or shutting
down (crashing is sometimes, not always), very nice screen which
slowly turns white
Hmm, it would be nice to be able to trigger go white on purpose --
it looks like screen is burning and could
On Thu, Feb 24, 2005 at 01:37:16PM +0100, Norbert Preining wrote:
> - X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9
> no work
> with 2.6.11-rc4 and 2.6.11-rc3-mm2
> this server crashes when switching to the console or shutting
> down (crashing is sometimes,
On Thu, Feb 24, 2005 at 01:37:16PM +0100, Norbert Preining wrote:
- X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9
no work
with 2.6.11-rc4 and 2.6.11-rc3-mm2
this server crashes when switching to the console or shutting
down (crashing is sometimes, not
Thus wrote Norbert Preining:
> - X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9
> no work
> with 2.6.11-rc4 and 2.6.11-rc3-mm2
> this server crashes when switching to the console or shutting
> down (crashing is sometimes, not always), very nice screen which
>
On Die, 22 Feb 2005, Karol Kozimor wrote:
> Thus wrote Norbert Preining:
> > - DRI must be disabled I guess?! Even with newer X server (x.org)?
>
> You still didn't state which X server are you using. In short, XFree86 4.4,
I have stated it several times, but here a sum up:
- XFree86 4.3
On Die, 22 Feb 2005, Karol Kozimor wrote:
Thus wrote Norbert Preining:
- DRI must be disabled I guess?! Even with newer X server (x.org)?
You still didn't state which X server are you using. In short, XFree86 4.4,
I have stated it several times, but here a sum up:
- XFree86 4.3
Thus wrote Norbert Preining:
- X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9
no work
with 2.6.11-rc4 and 2.6.11-rc3-mm2
this server crashes when switching to the console or shutting
down (crashing is sometimes, not always), very nice screen which
On Mon, 14 Feb 2005 22:11:05 +0100, Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
> Table of known working systems:
>
> Model hack (or "how to do it")
> --
> IBM TP R32 / Type 2658-MMG
On Mon, 14 Feb 2005 22:11:05 +0100, Pavel Machek [EMAIL PROTECTED] wrote:
Hi!
snip
Table of known working systems:
Model hack (or how to do it)
--
IBM TP R32 / Type 2658-MMG none
Thus wrote Norbert Preining:
> - DRI must be disabled I guess?! Even with newer X server (x.org)?
You still didn't state which X server are you using. In short, XFree86 4.4,
X.Org 6.7 and 6.8.2 are fine, anything other (including X.Org 6.8.0 and .1)
is not.
Best regards,
--
Karol 'sziwan'
Thus wrote Alistair John Strachan:
> I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the
> hang
> on resume! If you stop the entire i2c subsystem from being loaded by hotplug
> (note this is the BUS driver, not the sensors driver!), then resume works
> perfectly!
Thus wrote Alistair John Strachan:
I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the
hang
on resume! If you stop the entire i2c subsystem from being loaded by hotplug
(note this is the BUS driver, not the sensors driver!), then resume works
perfectly! Presumably
Thus wrote Norbert Preining:
- DRI must be disabled I guess?! Even with newer X server (x.org)?
You still didn't state which X server are you using. In short, XFree86 4.4,
X.Org 6.7 and 6.8.2 are fine, anything other (including X.Org 6.8.0 and .1)
is not.
Best regards,
--
Karol 'sziwan'
fre, 18,.02.2005 kl. 20.49 +, skrev Alistair John Strachan:
> On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote:
> > tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan:
> > > On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
> > > [snip]
> > >
> > > > Ok, here is the output
fre, 18,.02.2005 kl. 20.49 +, skrev Alistair John Strachan:
On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote:
tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan:
On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
[snip]
Ok, here is the output from dmidecode
Hello!
On Fri 18 Feb 2005 21:49, Alistair John Strachan wrote:
> I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the
> hang
> on resume! If you stop the entire i2c subsystem from being loaded by hotplug
> (note this is the BUS driver, not the sensors driver!), then resume
Hello!
On Fri 18 Feb 2005 21:49, Alistair John Strachan wrote:
I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the
hang
on resume! If you stop the entire i2c subsystem from being loaded by hotplug
(note this is the BUS driver, not the sensors driver!), then resume
On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote:
> tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan:
> > On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
> > [snip]
> >
> > > Ok, here is the output from dmidecode (Debian package) and from lspci.
> > > I don't have acpidmp
Am Freitag, 18. Februar 2005 14:38 schrieb Norbert Preining:
> On Fre, 18 Feb 2005, Norbert Preining wrote:
> > I tried:
> > 2.6.11-rc3-mm2 + Xorg + DRI disabled
> > and this works.
> >
> > I cannot enable dri/drm with the cvs version of the drm modules, because
> > the drm modules do not compile
On Fre, 18 Feb 2005, Norbert Preining wrote:
> I tried:
> 2.6.11-rc3-mm2 + Xorg + DRI disabled
> and this works.
>
> I cannot enable dri/drm with the cvs version of the drm modules, because
> the drm modules do not compile for -mm kernels, since there is the patch
> for multiple agp bridges
On Don, 17 Feb 2005, Stefan Dösinger wrote:
> > Ok, I installed xlibmesa-gl1-dri-trunk, xserver-xfree86-dri-trunk and
> > compiled linux-2.6.11-rc4 and drm modules from drm-trunk-module-src, all
> > from http://www.nixnuts.net/files/
> >
> > But I had no success whatsoever. With this (Xorg server,
On Don, 17 Feb 2005, Stefan Dösinger wrote:
Ok, I installed xlibmesa-gl1-dri-trunk, xserver-xfree86-dri-trunk and
compiled linux-2.6.11-rc4 and drm modules from drm-trunk-module-src, all
from http://www.nixnuts.net/files/
But I had no success whatsoever. With this (Xorg server, current
On Fre, 18 Feb 2005, Norbert Preining wrote:
I tried:
2.6.11-rc3-mm2 + Xorg + DRI disabled
and this works.
I cannot enable dri/drm with the cvs version of the drm modules, because
the drm modules do not compile for -mm kernels, since there is the patch
for multiple agp bridges
Am Freitag, 18. Februar 2005 14:38 schrieb Norbert Preining:
On Fre, 18 Feb 2005, Norbert Preining wrote:
I tried:
2.6.11-rc3-mm2 + Xorg + DRI disabled
and this works.
I cannot enable dri/drm with the cvs version of the drm modules, because
the drm modules do not compile for -mm
On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote:
tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan:
On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
[snip]
Ok, here is the output from dmidecode (Debian package) and from lspci.
I don't have acpidmp and I don't
Pavel Machek schrieb:
>
>>>I'm not sure if you can push the whole industry at once.
>>
>>The goal is to know what to tell the system vendors
>>interested in supporting Linux what they should do
>>with their BIOS on future platforms.
>>
>>I believe our message should be:
>>1. BIOS should
Hi!
Sorry, I was too fast with my mail client. Please cc: Len in your
replies.
To: Len Brown <[EMAIL PROTECTED]>
Subject: Re: [ACPI] Call for help: list of machines with working S3
X-Warning: Reading this can be dangerous to your mental health.
Hi!
> > I'm not sure if you can push the whole
Hello Pavel!
On Mon 14 Feb 2005 22:11, Pavel Machek wrote:
> Stefan provided me initial list of machines where S3 works (including
> video). If you have machine that is not on the list, please send me a
> diff. If you have eMachines... I'd like you to try playing with
Sorry, but a diff of what?
On Thu, 2005-02-17 at 05:15, Vojtech Pavlik wrote:
> I'm not sure if you can push the whole industry at once.
The goal is to know what to tell the system vendors
interested in supporting Linux what they should do
with their BIOS on future platforms.
I believe our message should be:
1. BIOS
Am Donnerstag, 17. Februar 2005 20:08 schrieb Norbert Preining:
> On Die, 15 Feb 2005, Stefan Dösinger wrote:
> > > - DRI must be disabled I guess?! Even with newer X server (x.org)?
> >
> > Do you use the fglrx driver? This doesn't work with any type of suspend
> > so far. If you use the radeon
Hi!
> >>4. Include a mandantory description of video bringup after resume
> >
> > That sounds overcomplicated. Simply add this to the specs:
>
> You have to start to think like a vendor with a long legacy. Then my
> spec draft will make more sense. Basically, you can't tell a vendor
> that his
Pavel Machek schrieb:
>
>>>to reinitialise the graphics hardware, few are going to care about
>>>making life easier for Linux.
>>
> [...]
>>3. Get some shiny certification/label going that can be put on
>>fully conforming products as a sticker. Something like the old
>>"EPA pollution preventer"
Vernon Mauery schrieb:
> Carl-Daniel Hailfinger wrote:
>
>>1. A first step towards better DSDTs would be to make the ASL compiler
>>complain about the same things which are complained about by the
>>in-kernel ACPI interpreter. An example would be the following:
>>
>>acpi_processor-0496 [10]
Hi!
> > to reinitialise the graphics hardware, few are going to care about
> > making life easier for Linux.
>
> 1. A first step towards better DSDTs would be to make the ASL compiler
> complain about the same things which are complained about by the
> in-kernel ACPI interpreter. An example
On Die, 15 Feb 2005, Pavel Machek wrote:
> > - Sometimes I have to make a Sysrq-s (sync) to get some stuff running
> > (eg logging in from the console hangs after input of passwd, calling
> > sysrq-s makes it continue). I had a similar effect when logging in
> > AFTER resuming (for the
On Die, 15 Feb 2005, Stefan Dösinger wrote:
> > - DRI must be disabled I guess?! Even with newer X server (x.org)?
> Do you use the fglrx driver? This doesn't work with any type of suspend so
> far. If you use the radeon driver try a driver update.
Ok, I installed xlibmesa-gl1-dri-trunk,
Carl-Daniel Hailfinger wrote:
> 1. A first step towards better DSDTs would be to make the ASL compiler
> complain about the same things which are complained about by the
> in-kernel ACPI interpreter. An example would be the following:
>
> acpi_processor-0496 [10] acpi_processor_get_inf: Invalid
Matthew Garrett schrieb:
> On Thu, 2005-02-17 at 01:16 -0500, Len Brown wrote:
>
>>I think that it is the BIOS' job on S3-suspend
>>to save the video mode. On S3-resume the BIOS should
>>re-POST and restore the video mode.
>
> I agree, but in the absence of spec requirement and some form of
>
On Die, 15 Feb 2005, Stefan Dösinger wrote:
> > After deactivating DRI in the X config file and saving the states with
> > your script (thanks) and turning off various stuff I get X running
> > again.
> >
> > Questions:
> > - DRI must be disabled I guess?! Even with newer X server (x.org)?
>
> Do
Hi!
> I think that it is the BIOS' job on S3-suspend
> to save the video mode. On S3-resume the BIOS should
> re-POST and restore the video mode.
Can you find it written down somewhere? It would be certainly easier
for me if every BIOS did re-post, but it is not the case on any new
BIOS
>
On Thu, 2005-02-17 at 01:16 -0500, Len Brown wrote:
> Pavel,
> I think that it is the BIOS' job on S3-suspend
> to save the video mode. On S3-resume the BIOS should
> re-POST and restore the video mode.
I agree, but in the absence of spec requirement and some form of
certification process, I
On Thu, Feb 17, 2005 at 01:16:45AM -0500, Len Brown wrote:
> Pavel,
> I think that it is the BIOS' job on S3-suspend
> to save the video mode. On S3-resume the BIOS should
> re-POST and restore the video mode.
Should.
But this definitely is not the case on about 80+% of notebooks.
You can
On Thu, Feb 17, 2005 at 01:16:45AM -0500, Len Brown wrote:
Pavel,
I think that it is the BIOS' job on S3-suspend
to save the video mode. On S3-resume the BIOS should
re-POST and restore the video mode.
Should.
But this definitely is not the case on about 80+% of notebooks.
You can save
On Thu, 2005-02-17 at 01:16 -0500, Len Brown wrote:
Pavel,
I think that it is the BIOS' job on S3-suspend
to save the video mode. On S3-resume the BIOS should
re-POST and restore the video mode.
I agree, but in the absence of spec requirement and some form of
certification process, I don't
Hi!
I think that it is the BIOS' job on S3-suspend
to save the video mode. On S3-resume the BIOS should
re-POST and restore the video mode.
Can you find it written down somewhere? It would be certainly easier
for me if every BIOS did re-post, but it is not the case on any new
BIOS
To
On Die, 15 Feb 2005, Stefan Dösinger wrote:
After deactivating DRI in the X config file and saving the states with
your script (thanks) and turning off various stuff I get X running
again.
Questions:
- DRI must be disabled I guess?! Even with newer X server (x.org)?
Do you use the
Matthew Garrett schrieb:
On Thu, 2005-02-17 at 01:16 -0500, Len Brown wrote:
I think that it is the BIOS' job on S3-suspend
to save the video mode. On S3-resume the BIOS should
re-POST and restore the video mode.
I agree, but in the absence of spec requirement and some form of
Carl-Daniel Hailfinger wrote:
1. A first step towards better DSDTs would be to make the ASL compiler
complain about the same things which are complained about by the
in-kernel ACPI interpreter. An example would be the following:
acpi_processor-0496 [10] acpi_processor_get_inf: Invalid PBLK
On Die, 15 Feb 2005, Stefan Dösinger wrote:
- DRI must be disabled I guess?! Even with newer X server (x.org)?
Do you use the fglrx driver? This doesn't work with any type of suspend so
far. If you use the radeon driver try a driver update.
Ok, I installed xlibmesa-gl1-dri-trunk,
On Die, 15 Feb 2005, Pavel Machek wrote:
- Sometimes I have to make a Sysrq-s (sync) to get some stuff running
(eg logging in from the console hangs after input of passwd, calling
sysrq-s makes it continue). I had a similar effect when logging in
AFTER resuming (for the resume I had
Hi!
to reinitialise the graphics hardware, few are going to care about
making life easier for Linux.
1. A first step towards better DSDTs would be to make the ASL compiler
complain about the same things which are complained about by the
in-kernel ACPI interpreter. An example would be the
Vernon Mauery schrieb:
Carl-Daniel Hailfinger wrote:
1. A first step towards better DSDTs would be to make the ASL compiler
complain about the same things which are complained about by the
in-kernel ACPI interpreter. An example would be the following:
acpi_processor-0496 [10]
Pavel Machek schrieb:
to reinitialise the graphics hardware, few are going to care about
making life easier for Linux.
[...]
3. Get some shiny certification/label going that can be put on
fully conforming products as a sticker. Something like the old
EPA pollution preventer logo, but with a
Hi!
4. Include a mandantory description of video bringup after resume
That sounds overcomplicated. Simply add this to the specs:
You have to start to think like a vendor with a long legacy. Then my
spec draft will make more sense. Basically, you can't tell a vendor
that his hardware is
Am Donnerstag, 17. Februar 2005 20:08 schrieb Norbert Preining:
On Die, 15 Feb 2005, Stefan Dösinger wrote:
- DRI must be disabled I guess?! Even with newer X server (x.org)?
Do you use the fglrx driver? This doesn't work with any type of suspend
so far. If you use the radeon driver try
On Thu, 2005-02-17 at 05:15, Vojtech Pavlik wrote:
I'm not sure if you can push the whole industry at once.
The goal is to know what to tell the system vendors
interested in supporting Linux what they should do
with their BIOS on future platforms.
I believe our message should be:
1. BIOS
Hello Pavel!
On Mon 14 Feb 2005 22:11, Pavel Machek wrote:
Stefan provided me initial list of machines where S3 works (including
video). If you have machine that is not on the list, please send me a
diff. If you have eMachines... I'd like you to try playing with
Sorry, but a diff of what? Of
Hi!
Sorry, I was too fast with my mail client. Please cc: Len in your
replies.
To: Len Brown [EMAIL PROTECTED]
Subject: Re: [ACPI] Call for help: list of machines with working S3
X-Warning: Reading this can be dangerous to your mental health.
Hi!
I'm not sure if you can push the whole
Pavel Machek schrieb:
I'm not sure if you can push the whole industry at once.
The goal is to know what to tell the system vendors
interested in supporting Linux what they should do
with their BIOS on future platforms.
I believe our message should be:
1. BIOS should save/restore video in S3
Pavel,
I think that it is the BIOS' job on S3-suspend
to save the video mode. On S3-resume the BIOS should
re-POST and restore the video mode.
While Linux's X drivers may be able to handle the case
where X is running -- that doesn't help us with the
cases where X is not running (a case that
On Thu, Feb 17, 2005 at 12:22:57AM +0100, Pavel Machek wrote:
> > does anyone have some experiences with intel i855 video card and S3?
> >
> > For me the binary driver from Intel works with S3 but only X server is
> > restored
> > not the text console.
> >
> > With open source driver nothing
Hi!
> does anyone have some experiences with intel i855 video card and S3?
>
> For me the binary driver from Intel works with S3 but only X server is
> restored
> not the text console.
>
> With open source driver nothing is restored. I try to use s3_bios or s3_mode,
> nothing helps. Using
Am Mittwoch, 16. Februar 2005 16:06 schrieb Carl-Daniel Hailfinger:
> Stefan Dösinger schrieb:
> >>The problems with this patch are:
> >>- you need to press a key to come back from the "resume-console" after
> >>resume. - DRI in X does not work (at least for me with intel-agp, others
> >>reportet
On Wed, 16 Feb 2005 16:06:00 +0100, Carl-Daniel Hailfinger
<[EMAIL PROTECTED]> wrote:
> Stefan Dösinger schrieb:
> >>The problems with this patch are:
> >>- you need to press a key to come back from the "resume-console" after
> >>resume. - DRI in X does not work (at least for me with intel-agp,
On Wed, Feb 16, 2005 at 03:54:38PM +0100, Carl-Daniel Hailfinger wrote:
> Romano Giannetti schrieb:
> >
> > I tried with my Sony Vaio FX701. No luck. It goes S3 ok, but it will never
> > come back (blank screen, HDD led fixed on).
> >
> > I am wishing to help, imply tell me what I have to do.
>
1 - 100 of 182 matches
Mail list logo
