Hi!
> On Sat, 2007-02-24 at 18:13 +0100, `matte wrote:
> > # s2ram -i
> > This machine can be identified by:
> > sys_vendor = " "
> > sys_product = " "
> > sys_version = " "
> > bios_version = "6.00 PG"
> > See http://en.opensuse.org/S2ram for details.
> >
> > If you report
Hi!
So it is a desktop
> Test results:
> Without vga=0
> -f - hangs on resume
> -f -a 1 - beeps and hangs when resuming
> -f -a 2 - hangs on resume
> -f -a 3 - beeps and hangs when resuming
~
and a broken one.
> -f -p -m - hangs on resume
>
> With vg
Hi, I'd like to help contribute to the whitelist. I'm a first-time
conributer though, so if I missed something please feel free to ask.
On my machine:
sys_vendor = "LENOVO"
sys_product = "94553KU"
sys_version = "Thinkpad R60"
bios_version = "7CETC1WW (2.11 )"
s2ram works with
Hello,
On Tue, 2007-02-27 at 10:52 +0100, Pavel Machek wrote:
> Now.. how do we fix this? Whitelist on both bios version and
> northbridge/videocard PCI IDs?
This seems reasonable if the sys_* fields are empty/weak.
> Anyone going to write a patch?
This is the second time you've mentioned patch
On Tue, 2007-02-27 at 10:50 +0100, Pavel Machek wrote:
> Hi!
> > On Sat, 2007-02-24 at 18:13 +0100, `matte wrote:
> > > # s2ram -i
> > > This machine can be identified by:
> > > sys_vendor = " "
> > > sys_product = " "
> > > sys_version = " "
> > > bios_version = "6.00 PG"
>
Machine is unknown.
This machine can be identified by:
sys_vendor = "Hewlett-Packard "
sys_product = "Presario R3000 (PB885EA#ABU) "
sys_version = "F.12"
bios_version = "F.12"
See http://en.opensuse.org/S2ram for details.
If you report a problem, please include the complete ou
On Mon, 2007-02-26 at 22:01 +, Sitsofe Wheeler wrote:
> lspci output to come.
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub
Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
00:03.0 PCI bridge: Intel Corporation 8
On Tue, Feb 27, 2007 at 08:19:43PM +, Sitsofe Wheeler wrote:
> > Are those desktop systems?
>
> The Shuttle was a desktop system and I don't really know of laptops with
> PCI-E...
Almost all new laptops are PCI-E (i think from i915 onward, but at least
from i945, probably all those new unsu
On Tue, Feb 27, 2007 at 10:50:06AM +0100, Pavel Machek wrote:
> > (Looks like this is some sort of default that returned when system
> > integrators are too lazy. Perhaps mainboard and BIOS release date also
> > need to be used in these circumstances?)
>
> Patch would be welcome ;-).
No. It prove
Hi,
I've already sent a similar post to the linux-acpi list some time ago, but
since I didn't get a response yet maybe this is the more appropriate place to
post. (Suggestions on where else to post are very welcome...).
Here's a summary of my problem:
After doing a s2ram cycle my Novatel Merl
On Tue, Feb 27, 2007 at 10:52:17AM +0100, Pavel Machek wrote:
> Now.. how do we fix this? Whitelist on both bios version and
> northbridge/videocard PCI IDs?
If we go that way, the DMI stuff may become irrelevant, since the subvendor
ids are basically as accurate as the DMI entries anyway. For ex
Hi,
I've never had problems suspending my Acer Extensa 4100 but only resuming from
suspend (I've sent a detailed report to Stefan Seyfried in July 2006 using a
2.6.17.4 kernel).
Now that I've tried again running a 2.6.18.1 kernel I'm quite surprised that
_suspending _ via s2ram doesn't work an
On Tue, 2007-02-27 at 21:39 +0100, Stefan Seyfried wrote:
> All just my humble opinion, of course. If somebody wants to implement
> PCI-ID matching and maintain the whitelist for that, i will welcome this,
> too. I for myself am just allergic to duplicated work :-)
If that's the case what should f
Hi!
> > > (Looks like this is some sort of default that returned when system
> > > integrators are too lazy. Perhaps mainboard and BIOS release date also
> > > need to be used in these circumstances?)
> >
> > Patch would be welcome ;-).
>
> No. It proves more and more that DMI data is just not a
Hi,
On Tuesday, 27 February 2007 22:53, Pavel Machek wrote:
> Hi!
>
> > > > (Looks like this is some sort of default that returned when system
> > > > integrators are too lazy. Perhaps mainboard and BIOS release date also
> > > > need to be used in these circumstances?)
> > >
> > > Patch would b
On Tue, Feb 27, 2007 at 10:53:09PM +0100, Pavel Machek wrote:
> I'd actually prefer to do it in s2ram... so that it works inside
> init=/bin/bash.
It will still work with init=/bin/bash, you just need to give the apropriate
parameters to s2ram.
> But feel free to steal^Wborrow hal's whitelist ;
On Tuesday, 27 February 2007 23:17, Stefan Seyfried wrote:
> On Tue, Feb 27, 2007 at 10:53:09PM +0100, Pavel Machek wrote:
>
> > I'd actually prefer to do it in s2ram... so that it works inside
> > init=/bin/bash.
>
> It will still work with init=/bin/bash, you just need to give the apropriate
>
Hi!
> > > > > (Looks like this is some sort of default that returned when system
> > > > > integrators are too lazy. Perhaps mainboard and BIOS release date also
> > > > > need to be used in these circumstances?)
> > > >
> > > > Patch would be welcome ;-).
> > >
> > > No. It proves more and more
Hi!
> > I'd actually prefer to do it in s2ram... so that it works inside
> > init=/bin/bash.
>
> It will still work with init=/bin/bash, you just need to give the apropriate
> parameters to s2ram.
>
> > But feel free to steal^Wborrow hal's whitelist ;-).
>
> You basically cannot do the advanced
Hi,
On Tuesday, 27 February 2007 23:29, Pavel Machek wrote:
> Hi!
>
> > > > > > (Looks like this is some sort of default that returned when system
> > > > > > integrators are too lazy. Perhaps mainboard and BIOS release date
> > > > > > also
> > > > > > need to be used in these circumstances?)
>
On Tue, Feb 27, 2007 at 11:30:23PM +0100, Pavel Machek wrote:
> I do not think we want to go into that trap. We do not want "any
> arbitrary matcher". That's no better than matching in C code.
>
> If PCI IDs/subids are good at telling machines apart, lets use that.
Ok. HAL can already match them
Hi List :-)
I have a Lenovo X60T Tablet.
S2ram works fine but i loose the wacom stylus.
Usually i have to run " setserial /dev/ttyS0 port 0x0200 irq 5
autoconfig" before i start X to make the stylus work, but it does not
work when X is already up.
Is there a way to tell s2ram to run this early en
On Wed, Feb 28, 2007 at 02:35:27AM +0100, Sascha Heid wrote:
> Hi List :-)
>
> I have a Lenovo X60T Tablet.
> S2ram works fine but i loose the wacom stylus.
> Usually i have to run " setserial /dev/ttyS0 port 0x0200 irq 5
> autoconfig" before i start X to make the stylus work, but it does not
> wo
23 matches
Mail list logo
