Bug#410320: [Suspend-devel] Bug#410320: s2ram: whitelist entry
Hi,
On Mon, Feb 12, 2007 at 09:30:17PM +0100, Tim Dijkstra wrote:
> Hi Guys,
>
> I just got this report
>
> On Fri, 9 Feb 2007 18:19:59 +0100
> Bill Allombert <[EMAIL PROTECTED]> wrote:
>
> > Package: uswsusp
> > Version: 0.3~cvs20060928-6
> > Severity: wishlist
> >
> > Hello Tim,
> >
> > With etch-amd64 on my new laptop, s2ram work fine with that option:
> >
> > #s2ram -f -a 1
> >
> > Here the laptop ID:
> >
> > #This machine can be identified by:
> > sys_vendor = "FUJITSU SIEMENS"
> > sys_product = "Amilo Si 1520"
> > sys_version = "Rev 1"
> > bios_version = " 1.10"
>
> Current CVS already has this entry:
>
> { "FUJITSU SIEMENS","Amilo Si 1520","", "",
> S3_BIOS|S3_MODE },
>
> I'm not really an expert in those video hacks. What would Bill have
> missed without S3_MODE? Higher resolution console maybe?
Yes, vesafb.
With S3_BIOS, you usually end in plain VGA mode (as after VBE_POST), S3_MODE
then sets back the VESA mode (same as VBE_MODE), at least IIUC, which should
be a noop in the case of non-fbdev console.
Bill, if you could try if your machine also wirks with "s2ram -f -a3",
this would confirm the entry which is already in the whitelist.
Thanks,
Stefan
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#410320: [Suspend-devel] Bug#410320: s2ram: whitelist entry
On Mon, Feb 12, 2007 at 09:52:09PM +0100, Stefan Seyfried wrote:
> Hi,
>
> >
> > { "FUJITSU SIEMENS","Amilo Si 1520","", "",
> > S3_BIOS|S3_MODE },
> >
> > I'm not really an expert in those video hacks. What would Bill have
> > missed without S3_MODE? Higher resolution console maybe?
>
> Yes, vesafb.
>
> With S3_BIOS, you usually end in plain VGA mode (as after VBE_POST), S3_MODE
> then sets back the VESA mode (same as VBE_MODE), at least IIUC, which should
> be a noop in the case of non-fbdev console.
... which is my case.
> Bill, if you could try if your machine also wirks with "s2ram -f -a3",
> this would confirm the entry which is already in the whitelist.
I just tested and it works fine.
Cheers,
--
Bill. <[EMAIL PROTECTED]>
Imagine a large blue swirl here.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#410320: [Suspend-devel] Bug#410320: s2ram: whitelist entry
On Mon, Feb 12, 2007 at 11:49:49PM +0100, Bill Allombert wrote:
> On Mon, Feb 12, 2007 at 09:52:09PM +0100, Stefan Seyfried wrote:
> > Hi,
> >
> > >
> > > { "FUJITSU SIEMENS","Amilo Si 1520","", "",
> > > S3_BIOS|S3_MODE },
>
> > Bill, if you could try if your machine also wirks with "s2ram -f -a3",
> > this would confirm the entry which is already in the whitelist.
>
> I just tested and it works fine.
Thanks for testing, this means that the current whitelist entry as in
CVS will work fine for you, and that this bug can probably be closed
as "will be fixed with the next version update" :-)
Have fun,
Stefan
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
