Re: [ACPI] Re: Call for help: list of machines with working S3
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 2005-02-03 22:28:19.0 +0100 > > > @@ -,6 +,7 @@ > > > ret = -EINTR; > > > } > > > > > > + try_to_freeze(1); > > > return ret; > > > } > > I also encounter a similar issue. syslogd can't be stopped. It's waiting > > for kjournald to flush some works but kjournald is stopped first. Looks > > like the kernel thread should be stopped later than user thread just > > like Nigel's suspend2 patch does. > > Pavel, do you have any kernel/power/process.c changes in? If not, I'll > submit those refrigerator changes. No, process.c was left unchanged for quite a long time. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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... > > Pavel > > > > --- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100 > > +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 > > @@ -,6 +,7 @@ > > ret = -EINTR; > > } > > > > + try_to_freeze(1); > > return ret; > > } > I also encounter a similar issue. syslogd can't be stopped. It's waiting > for kjournald to flush some works but kjournald is stopped first. Looks > like the kernel thread should be stopped later than user thread just > like Nigel's suspend2 patch does. Pavel, do you have any kernel/power/process.c changes in? If not, I'll submit those refrigerator changes. Regards, Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574 Maintainer of Suspend2 Kernel Patches http://suspend2.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 22:27:26.0 +0100 > +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 > @@ -,6 +,7 @@ > ret = -EINTR; > } > > + try_to_freeze(1); > return ret; > } I also encounter a similar issue. syslogd can't be stopped. It's waiting for kjournald to flush some works but kjournald is stopped first. Looks like the kernel thread should be stopped later than user thread just like Nigel's suspend2 patch does. Thanks, Shaohua - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 22:27:26.0 +0100 +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 @@ -,6 +,7 @@ ret = -EINTR; } + try_to_freeze(1); return ret; } I also encounter a similar issue. syslogd can't be stopped. It's waiting for kjournald to flush some works but kjournald is stopped first. Looks like the kernel thread should be stopped later than user thread just like Nigel's suspend2 patch does. Thanks, Shaohua - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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... Pavel --- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100 +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 @@ -,6 +,7 @@ ret = -EINTR; } + try_to_freeze(1); return ret; } I also encounter a similar issue. syslogd can't be stopped. It's waiting for kjournald to flush some works but kjournald is stopped first. Looks like the kernel thread should be stopped later than user thread just like Nigel's suspend2 patch does. Pavel, do you have any kernel/power/process.c changes in? If not, I'll submit those refrigerator changes. Regards, Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574 Maintainer of Suspend2 Kernel Patches http://suspend2.net - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 2005-02-03 22:28:19.0 +0100 @@ -,6 +,7 @@ ret = -EINTR; } + try_to_freeze(1); return ret; } I also encounter a similar issue. syslogd can't be stopped. It's waiting for kjournald to flush some works but kjournald is stopped first. Looks like the kernel thread should be stopped later than user thread just like Nigel's suspend2 patch does. Pavel, do you have any kernel/power/process.c changes in? If not, I'll submit those refrigerator changes. No, process.c was left unchanged for quite a long time. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 there's a bug in the resuming of this module. Might it be another instance of the LPC chip config space messed up on resume? Best regards, -- Karol 'sziwan' Kozimor [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 there's a bug in the resuming of this module. Might it be another instance of the LPC chip config space messed up on resume? Best regards, -- Karol 'sziwan' Kozimor [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 (Debian package) and from lspci. > > > > I don't have acpidmp and I don't know where to get it, but if you think > > > > it's necessary I can download it if you tell me where to find it. > > > > > > Find below a diff of my dmidecode output versus Lorenzo's. Nothing much > > > to call home about. > > > > I've attached a diff against Lorenzo's too. Only difference is that my > > laptop is a nc4010, and looking here it's clear that this model doesn't > > support APM at least. I also have non-working S3. It behaves just like > > the entry in the ubuntu wiki for the nc6000 in all three cases with a > > full system running at least. I'll try init=/bin/sh later to see if that > > helps and if it does experiment with removing modules one by one... > > Got it. Sorry for the radio silence, I've been busy for a few days. > > 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 there's a bug in the resuming of this module. > > In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and > reload them. > > The s3_bios workaround allows video to kind of work, but I can't use anything > other than vga=normal (vesafb results in corruption), and the screen is no > longer artificially resized to fill the LCD, it's native res and centered > (which sure is annoying). > > Kjartan, I hope you isolate the driver causing you problems, as it seems > these > machines can be made, even if it is a bit of a headache. > I tried it again now using init=/bin/sh and acpi_sleep=s3_bios and it still gives a black screen on resume... :-/ Cheers Kjartan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 (Debian package) and from lspci. I don't have acpidmp and I don't know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Find below a diff of my dmidecode output versus Lorenzo's. Nothing much to call home about. I've attached a diff against Lorenzo's too. Only difference is that my laptop is a nc4010, and looking here it's clear that this model doesn't support APM at least. I also have non-working S3. It behaves just like the entry in the ubuntu wiki for the nc6000 in all three cases with a full system running at least. I'll try init=/bin/sh later to see if that helps and if it does experiment with removing modules one by one... Got it. Sorry for the radio silence, I've been busy for a few days. 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 there's a bug in the resuming of this module. In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and reload them. The s3_bios workaround allows video to kind of work, but I can't use anything other than vga=normal (vesafb results in corruption), and the screen is no longer artificially resized to fill the LCD, it's native res and centered (which sure is annoying). Kjartan, I hope you isolate the driver causing you problems, as it seems these machines can be made, even if it is a bit of a headache. I tried it again now using init=/bin/sh and acpi_sleep=s3_bios and it still gives a black screen on resume... :-/ Cheers Kjartan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 works > perfectly! Presumably there's a bug in the resuming of this module. Well, on my IBM ThinkPad T42p (ATI FireGL T2 128MB), I can resume with both I2C modules loaded, so probably the problem is not specific to the I2C subsystem. > In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and > reload them. I just tested two USB devices after S3 resuming without having removed the USB modules (uhci-hcb and ehci-hcd): - Logitech USB Wheel Mouse (046d:c00c, USB 1.x), it works with no problem on console, but not on X (this was caused by the fact that I've two corepointer on my XF86Config-4, in fact after having corrected this error and restarted X, the USB mouse works) - Mitsubishi Chemical 2.5" HD Case (05e3:0702, USB 2.0 [1], with a SAMSUNG MP0804H 80GB), it works with no problem :-D > The s3_bios workaround allows video to kind of work, but I can't use anything > other than vga=normal (vesafb results in corruption), and the screen is no > longer artificially resized to fill the LCD, it's native res and centered > (which sure is annoying). Again, IMHO the problem is specific to your machine: I use the radeonfb (with acpi_sleep=s3_bios) and the resume is ok (both in console and Debian XFree86-4.3.0.dfsg.1-11, radeon driver). Thx, bye, Gismo / Luca [1] http://www.qbik.ch/usb/devices/showdescr.php?id=3039 pgpFAuFgB8Bft.pgp Description: PGP signature
Re: [ACPI] Re: Call for help: list of machines with working S3
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 works perfectly! Presumably there's a bug in the resuming of this module. Well, on my IBM ThinkPad T42p (ATI FireGL T2 128MB), I can resume with both I2C modules loaded, so probably the problem is not specific to the I2C subsystem. In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and reload them. I just tested two USB devices after S3 resuming without having removed the USB modules (uhci-hcb and ehci-hcd): - Logitech USB Wheel Mouse (046d:c00c, USB 1.x), it works with no problem on console, but not on X (this was caused by the fact that I've two corepointer on my XF86Config-4, in fact after having corrected this error and restarted X, the USB mouse works) - Mitsubishi Chemical 2.5 HD Case (05e3:0702, USB 2.0 [1], with a SAMSUNG MP0804H 80GB), it works with no problem :-D The s3_bios workaround allows video to kind of work, but I can't use anything other than vga=normal (vesafb results in corruption), and the screen is no longer artificially resized to fill the LCD, it's native res and centered (which sure is annoying). Again, IMHO the problem is specific to your machine: I use the radeonfb (with acpi_sleep=s3_bios) and the resume is ok (both in console and Debian XFree86-4.3.0.dfsg.1-11, radeon driver). Thx, bye, Gismo / Luca [1] http://www.qbik.ch/usb/devices/showdescr.php?id=3039 pgpFAuFgB8Bft.pgp Description: PGP signature
Re: [ACPI] Re: Call for help: list of machines with working S3
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 know where to get it, but if you think > > > it's necessary I can download it if you tell me where to find it. > > > > Find below a diff of my dmidecode output versus Lorenzo's. Nothing much > > to call home about. > > I've attached a diff against Lorenzo's too. Only difference is that my > laptop is a nc4010, and looking here it's clear that this model doesn't > support APM at least. I also have non-working S3. It behaves just like > the entry in the ubuntu wiki for the nc6000 in all three cases with a > full system running at least. I'll try init=/bin/sh later to see if that > helps and if it does experiment with removing modules one by one... Got it. Sorry for the radio silence, I've been busy for a few days. 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 there's a bug in the resuming of this module. In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and reload them. The s3_bios workaround allows video to kind of work, but I can't use anything other than vga=normal (vesafb results in corruption), and the screen is no longer artificially resized to fill the LCD, it's native res and centered (which sure is annoying). Kjartan, I hope you isolate the driver causing you problems, as it seems these machines can be made, even if it is a bit of a headache. Lorenzo, thanks for your kernel config. It made it a lot easier to debug this problem. -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Find below a diff of my dmidecode output versus Lorenzo's. Nothing much to call home about. I've attached a diff against Lorenzo's too. Only difference is that my laptop is a nc4010, and looking here it's clear that this model doesn't support APM at least. I also have non-working S3. It behaves just like the entry in the ubuntu wiki for the nc6000 in all three cases with a full system running at least. I'll try init=/bin/sh later to see if that helps and if it does experiment with removing modules one by one... Got it. Sorry for the radio silence, I've been busy for a few days. 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 there's a bug in the resuming of this module. In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and reload them. The s3_bios workaround allows video to kind of work, but I can't use anything other than vga=normal (vesafb results in corruption), and the screen is no longer artificially resized to fill the LCD, it's native res and centered (which sure is annoying). Kjartan, I hope you isolate the driver causing you problems, as it seems these machines can be made, even if it is a bit of a headache. Lorenzo, thanks for your kernel config. It made it a lot easier to debug this problem. -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 know where to get it, but if you think > > it's necessary I can download it if you tell me where to find it. > > Find below a diff of my dmidecode output versus Lorenzo's. Nothing much > to call home about. > I've attached a diff against Lorenzo's too. Only difference is that my laptop is a nc4010, and looking here it's clear that this model doesn't support APM at least. I also have non-working S3. It behaves just like the entry in the ubuntu wiki for the nc6000 in all three cases with a full system running at least. I'll try init=/bin/sh later to see if that helps and if it does experiment with removing modules one by one... --- dmidecode 2005-02-16 15:17:02.127419209 +0100 +++ dmi.out 2005-02-16 15:16:43.142505944 +0100 @@ -1,21 +1,20 @@ # dmidecode 2.5 SMBIOS 2.3 present. -31 structures occupying 1354 bytes. -Table at 0x000FF2EB. +31 structures occupying 1342 bytes. +Table at 0x000FC06F. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BAS Ver. F.2F + Release Date: 12/10/2004 Address: 0xE Runtime Size: 128 kB - ROM Size: 1024 kB + ROM Size: 512 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported - APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported @@ -37,27 +36,27 @@ Handle 0x0001 DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard - Product Name: HP Compaq nc6000 (DJ254A#ABB) - Version: F.0F - Serial Number: XX - UUID: ---- + Product Name: HP Compaq nc4010 (DY885AA#ABN) + Version: F.2F + Serial Number: XX + UUID: ---- Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. Base Board Information Manufacturer: Hewlett-Packard - Product Name: 0890 - Version: 8051 Version 1A.19 + Product Name: 0834 + Version: KBC Version 20.37 Serial Number: Not Specified Handle 0x0003 DMI type 3, 13 bytes. Chassis Information - Manufacturer: Hewlett-Packard + Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified - Serial Number: XX - Asset Tag: + Serial Number: CNU442FBGX + Asset Tag: CNU442FBGX Boot-up State: Safe Power Supply State: Safe Thermal State: Safe @@ -69,8 +68,8 @@ Handle 0x0004 Type: Central Processor Family: Pentium M Manufacturer: Intel(R) - ID: XX XX XX XX XX XX XX XX - Signature: Type 0, Family 6, Model 9, Stepping 5 + ID: D6 06 00 00 BF F9 E9 AF + Signature: Type 0, Family 6, Model 13, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) @@ -93,13 +92,14 @@ Handle 0x0004 FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) + SS (Self-snoop) TM (Thermal monitor supported) SBF (Signal break on FERR) - Version: Intel(R) Pentium(R) M processor 1400MHz - Voltage: 1.8 V + Version: Intel(R) Pentium(R) M processor 1.80GHz + Voltage: 1.1 V External Clock: 100 MHz - Max Speed: 1400 MHz - Current Speed: 1400 MHz + Max Speed: 1800 MHz + Current Speed: 1800 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0005 @@ -121,25 +121,25 @@ Handle 0x0005 Burst Installed SRAM Type: Burst Speed: Unknown - Error
Re: [ACPI] Re: Call for help: list of machines with working S3
On Wed, Feb 16, 2005 at 01:47:04PM +1100, Nigel Cunningham wrote: > Hi. > > On Wed, 2005-02-16 at 12:54, Pavel Machek wrote: > > > Also, is USB suspend/resume supposed to work? My brief trials involved > > > modprobing the USB HCD modules, which still allowed me to suspend/resume, > > > but > > > my USB mouse was non-functional on resume. > > > > Yes, it seems to work quite okay. You may need to unplug/replug > > devices after resume, but it should be basically ok. > > We still have plenty of people for whom the best option is to build as > modules, unload prior to suspending and reload afterwards. It seems to > depend on what type your controller is: I do this for uhci_hcd and get > fully functional usb post resume (-rc4). > I have no problem for USB "stateless" devices. The real problem is when you do a suspend/resume cycle with a *mounted* usb stick or disk. Upon resume, the device is found and associated with a diffent block device than before, and the previous mount point is stuck forever (well, almost forever). Sometime umount -f works, sometime no, but it is quite irritating that I need to reboot to have the "good old /dev/sda1" which is in the fstab working. Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Wed, Feb 16, 2005 at 01:47:04PM +1100, Nigel Cunningham wrote: Hi. On Wed, 2005-02-16 at 12:54, Pavel Machek wrote: Also, is USB suspend/resume supposed to work? My brief trials involved modprobing the USB HCD modules, which still allowed me to suspend/resume, but my USB mouse was non-functional on resume. Yes, it seems to work quite okay. You may need to unplug/replug devices after resume, but it should be basically ok. We still have plenty of people for whom the best option is to build as modules, unload prior to suspending and reload afterwards. It seems to depend on what type your controller is: I do this for uhci_hcd and get fully functional usb post resume (-rc4). I have no problem for USB stateless devices. The real problem is when you do a suspend/resume cycle with a *mounted* usb stick or disk. Upon resume, the device is found and associated with a diffent block device than before, and the previous mount point is stuck forever (well, almost forever). Sometime umount -f works, sometime no, but it is quite irritating that I need to reboot to have the good old /dev/sda1 which is in the fstab working. Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Find below a diff of my dmidecode output versus Lorenzo's. Nothing much to call home about. I've attached a diff against Lorenzo's too. Only difference is that my laptop is a nc4010, and looking here it's clear that this model doesn't support APM at least. I also have non-working S3. It behaves just like the entry in the ubuntu wiki for the nc6000 in all three cases with a full system running at least. I'll try init=/bin/sh later to see if that helps and if it does experiment with removing modules one by one... --- dmidecode 2005-02-16 15:17:02.127419209 +0100 +++ dmi.out 2005-02-16 15:16:43.142505944 +0100 @@ -1,21 +1,20 @@ # dmidecode 2.5 SMBIOS 2.3 present. -31 structures occupying 1354 bytes. -Table at 0x000FF2EB. +31 structures occupying 1342 bytes. +Table at 0x000FC06F. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BAS Ver. F.2F + Release Date: 12/10/2004 Address: 0xE Runtime Size: 128 kB - ROM Size: 1024 kB + ROM Size: 512 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported - APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported @@ -37,27 +36,27 @@ Handle 0x0001 DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard - Product Name: HP Compaq nc6000 (DJ254A#ABB) - Version: F.0F - Serial Number: XX - UUID: ---- + Product Name: HP Compaq nc4010 (DY885AA#ABN) + Version: F.2F + Serial Number: XX + UUID: ---- Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. Base Board Information Manufacturer: Hewlett-Packard - Product Name: 0890 - Version: 8051 Version 1A.19 + Product Name: 0834 + Version: KBC Version 20.37 Serial Number: Not Specified Handle 0x0003 DMI type 3, 13 bytes. Chassis Information - Manufacturer: Hewlett-Packard + Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified - Serial Number: XX - Asset Tag: + Serial Number: CNU442FBGX + Asset Tag: CNU442FBGX Boot-up State: Safe Power Supply State: Safe Thermal State: Safe @@ -69,8 +68,8 @@ Handle 0x0004 Type: Central Processor Family: Pentium M Manufacturer: Intel(R) - ID: XX XX XX XX XX XX XX XX - Signature: Type 0, Family 6, Model 9, Stepping 5 + ID: D6 06 00 00 BF F9 E9 AF + Signature: Type 0, Family 6, Model 13, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) @@ -93,13 +92,14 @@ Handle 0x0004 FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) + SS (Self-snoop) TM (Thermal monitor supported) SBF (Signal break on FERR) - Version: Intel(R) Pentium(R) M processor 1400MHz - Voltage: 1.8 V + Version: Intel(R) Pentium(R) M processor 1.80GHz + Voltage: 1.1 V External Clock: 100 MHz - Max Speed: 1400 MHz - Current Speed: 1400 MHz + Max Speed: 1800 MHz + Current Speed: 1800 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0005 @@ -121,25 +121,25 @@ Handle 0x0005 Burst Installed SRAM Type: Burst Speed: Unknown - Error Correction Type:
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi. On Wed, 2005-02-16 at 12:54, Pavel Machek wrote: > > Also, is USB suspend/resume supposed to work? My brief trials involved > > modprobing the USB HCD modules, which still allowed me to suspend/resume, > > but > > my USB mouse was non-functional on resume. > > Yes, it seems to work quite okay. You may need to unplug/replug > devices after resume, but it should be basically ok. We still have plenty of people for whom the best option is to build as modules, unload prior to suspending and reload afterwards. It seems to depend on what type your controller is: I do this for uhci_hcd and get fully functional usb post resume (-rc4). Regards, Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Ph: +61 (2) 6292 8028 Mob: +61 (417) 100 574 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi! > > I would advise trying to compile a custom kernel from scratch with my > > .config first. > > > > I got S3 working first with a very basic kernel config, but I couldn't > > get it to work with my usual kernel. Assuming it was some feature that > > caused the problem, I started disabling features in the hope of getting > > it to work, but I ended up with two different kernels with seemingly > > irrelevant differences, of which one would succesfully resume and one > > wouldn't. So I started added features to the other kernel, and I never > > found out what caused the problem. > > I took your advice and built your kernel with a few modifications (XFS > instead > of ext, etc.). If I boot the kernel with init=/bin/sh, I can actually > suspend! Thanks! > > I will exhaustively enable and disable drivers tomorrow to figure out which > one is causing suspend to fail when I do a complete boot. Whatever we find is > clearly a bug that should be fixed. > > It is not the framebuffer driver (I always ran without vesafb or radeonfb), > and it is not my ipw2200 or USB drivers. > > Also, is USB suspend/resume supposed to work? My brief trials involved > modprobing the USB HCD modules, which still allowed me to suspend/resume, but > my USB mouse was non-functional on resume. Yes, it seems to work quite okay. You may need to unplug/replug devices after resume, but it should be basically ok. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tuesday 15 Feb 2005 21:09, Lorenzo Colitti wrote: [snip] > I would advise trying to compile a custom kernel from scratch with my > .config first. > > I got S3 working first with a very basic kernel config, but I couldn't > get it to work with my usual kernel. Assuming it was some feature that > caused the problem, I started disabling features in the hope of getting > it to work, but I ended up with two different kernels with seemingly > irrelevant differences, of which one would succesfully resume and one > wouldn't. So I started added features to the other kernel, and I never > found out what caused the problem. I took your advice and built your kernel with a few modifications (XFS instead of ext, etc.). If I boot the kernel with init=/bin/sh, I can actually suspend! Thanks! I will exhaustively enable and disable drivers tomorrow to figure out which one is causing suspend to fail when I do a complete boot. Whatever we find is clearly a bug that should be fixed. It is not the framebuffer driver (I always ran without vesafb or radeonfb), and it is not my ipw2200 or USB drivers. Also, is USB suspend/resume supposed to work? My brief trials involved modprobing the USB HCD modules, which still allowed me to suspend/resume, but my USB mouse was non-functional on resume. -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BDD Ver. F.11 + Release Date: 11/22/2004 Ok, so you both have different BIOS versions and different CPUs. S3 works for me with both BIOS F.0F, which I was using before, and F.11, which I flashed today after learning it existed. Everything else looks pretty identical. Could you both stick /proc/acpi/dsdt up somewhere so I can check if there are any relevant looking differences? I would advise trying to compile a custom kernel from scratch with my .config first. I got S3 working first with a very basic kernel config, but I couldn't get it to work with my usual kernel. Assuming it was some feature that caused the problem, I started disabling features in the hope of getting it to work, but I ended up with two different kernels with seemingly irrelevant differences, of which one would succesfully resume and one wouldn't. So I started added features to the other kernel, and I never found out what caused the problem. I'm not saying that this is not deterministic, but I am saying that, at least in my case, it's not obvious what it is that stops S3 from working. :-) Cheers, Lorenzo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tue, 2005-02-15 at 17:42 +, Alistair John Strachan wrote: > Vendor: Hewlett-Packard > - Version: 68BDD Ver. F.0F > - Release Date: 07/23/2004 > + Version: 68BDD Ver. F.11 > + Release Date: 11/22/2004 Ok, so you both have different BIOS versions and different CPUs. Everything else looks pretty identical. Could you both stick /proc/acpi/dsdt up somewhere so I can check if there are any relevant looking differences? Thanks, -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 know where to get it, but if you think > it's necessary I can download it if you tell me where to find it. Find below a diff of my dmidecode output versus Lorenzo's. Nothing much to call home about. [alistair] 17:40 [~/dmidecode-2.5] diff -Nudr -U3 lorenzo dmiout --- lorenzo 2005-02-15 17:37:36.091770768 + +++ dmiout 2005-02-15 17:40:08.801555352 + @@ -1,13 +1,13 @@ # dmidecode 2.5 SMBIOS 2.3 present. 31 structures occupying 1354 bytes. -Table at 0x000FF2EB. +Table at 0x000FA1EE. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BDD Ver. F.11 + Release Date: 11/22/2004 Address: 0xE Runtime Size: 128 kB ROM Size: 1024 kB @@ -37,10 +37,10 @@ DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard - Product Name: HP Compaq nc6000 (DJ254A#ABB) - Version: F.0F - Serial Number: XX - UUID: ---- + Product Name: HP Compaq nc6000 (PK522PS#UUF) + Version: F.11 + Serial Number: + UUID: Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. @@ -52,11 +52,11 @@ Handle 0x0003 DMI type 3, 13 bytes. Chassis Information - Manufacturer: Hewlett-Packard + Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified - Serial Number: XX + Serial Number: Asset Tag: Boot-up State: Safe Power Supply State: Safe @@ -69,8 +69,8 @@ Type: Central Processor Family: Pentium M Manufacturer: Intel(R) - ID: XX XX XX XX XX XX XX XX - Signature: Type 0, Family 6, Model 9, Stepping 5 + ID: D6 06 00 00 BF F9 E9 AF + Signature: Type 0, Family 6, Model 13, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) @@ -93,13 +93,14 @@ FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) + SS (Self-snoop) TM (Thermal monitor supported) SBF (Signal break on FERR) - Version: Intel(R) Pentium(R) M processor 1400MHz + Version: Intel(R) Pentium(R) M processor 1.60GHz Voltage: 1.8 V External Clock: 100 MHz - Max Speed: 1400 MHz - Current Speed: 1400 MHz + Max Speed: 1600 MHz + Current Speed: 1600 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0005 @@ -131,8 +132,8 @@ Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: External - Installed Size: 1024 KB - Maximum Size: 1024 KB + Installed Size: 2048 KB + Maximum Size: 2048 KB Supported SRAM Types: Burst Installed SRAM Type: Burst @@ -194,7 +195,7 @@ Form Factor: SODIMM Set: None Locator: DIMM #1 - Bank Locator: 030B2C25 + Bank Locator: 6605F934 Type: DDR Type Detail: Synchronous Speed: 142 MHz (7.0 ns) @@ -213,12 +214,12 @@ Form Factor: SODIMM Set: None Locator: DIMM #2 - Bank Locator: 051FD180 + Bank Locator: 0322BB20 Type: DDR Type Detail: Synchronous Speed: 142 MHz (7.0 ns) Manufacturer: Not Specified - Serial Number: -X + Serial Number: Asset Tag: Not Specified Part Number: Not Specified Handle 0x000E @@ -294,8 +295,8 @@ Portable Battery Location: Primary Manufacturer: Hewlett-Packard - Manufacture Date: 12/12/2003 - Serial Number: 1 + Manufacture Date: 08/20/2004 + Serial Number: 01726 Name: Not Specified Chemistry: Lithium Ion
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. Ok, here is the output from dmidecode (Debian package) and from lspci. I don't have acpidmp and I don't know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Cheers, Lorenzo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. Ok, here is the output from dmidecode (Debian package) and from lspci. I don't have acpidmp and I don't know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Cheers, Lorenzo # dmidecode 2.5 SMBIOS 2.3 present. 31 structures occupying 1354 bytes. Table at 0x000FF2EB. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard Version: 68BDD Ver. F.0F Release Date: 07/23/2004 Address: 0xE Runtime Size: 128 kB ROM Size: 1024 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5"/720 KB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported AGP is supported LS-120 boot is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Handle 0x0001 DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard Product Name: HP Compaq nc6000 (DJ254A#ABB) Version: F.0F Serial Number: XX UUID: ---- Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. Base Board Information Manufacturer: Hewlett-Packard Product Name: 0890 Version: 8051 Version 1A.19 Serial Number: Not Specified Handle 0x0003 DMI type 3, 13 bytes. Chassis Information Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified Serial Number: XX Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: External Interface Enabled Handle 0x0004 DMI type 4, 35 bytes. Processor Information Socket Designation: U10 Type: Central Processor Family: Pentium M Manufacturer: Intel(R) ID: XX XX XX XX XX XX XX XX Signature: Type 0, Family 6, Model 9, Stepping 5 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) TM (Thermal monitor supported) SBF (Signal break on FERR) Version: Intel(R) Pentium(R) M processor 1400MHz
Re: [ACPI] Re: Call for help: list of machines with working S3
Alistair John Strachan wrote: .config attached. As recommended elsewhere in this thread, I'm not using any sort of framebuffer driver, but vesafb IS compiled in (but no vga= option is present). Does it need to be compiled out completely? I don't remember, maybe you can deduce it from the .config I sent? I have acpi_sleep=s3_bios on cmdline. I am not using swsusp2 (and I can't see how this is at all related to software suspend). It works with or without swsusp2. Perhaps it is the machine BIOS. Which version do you have? I think it's vF.0F from July 2004. Cheers, Lorenzo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tue, 2005-02-15 at 13:12 +0100, Lorenzo Colitti wrote: > I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 > patch). However, I need to use acpi_sleep=s3_bios, and I can't use > radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tuesday 15 Feb 2005 12:12, Lorenzo Colitti wrote: > Alistair John Strachan wrote: > > On Monday 14 Feb 2005 21:11, Pavel Machek wrote: > >>Table of known working systems: > >>Model hack (or "how to do it") > >>[...] > >>HP NC6000 s3_bios (2) > > > > The above report is incorrect. On 2.6.11-rc4, even with the s3_bios > > option, the NC6000 (which I own) still does not wake up from S3 sleep. > > The wiki linked somewhere else in this thread also identifies these > > machines as not working. > > I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 > patch). However, I need to use acpi_sleep=s3_bios, and I can't use > radeonfb or it will lock up on resume. > > .config attached. > As recommended elsewhere in this thread, I'm not using any sort of framebuffer driver, but vesafb IS compiled in (but no vga= option is present). Does it need to be compiled out completely? I have acpi_sleep=s3_bios on cmdline. I am not using swsusp2 (and I can't see how this is at all related to software suspend). Perhaps it is the machine BIOS. Which version do you have? -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Alistair John Strachan wrote: On Monday 14 Feb 2005 21:11, Pavel Machek wrote: Table of known working systems: Model hack (or "how to do it") [...] HP NC6000 s3_bios (2) The above report is incorrect. On 2.6.11-rc4, even with the s3_bios option, the NC6000 (which I own) still does not wake up from S3 sleep. The wiki linked somewhere else in this thread also identifies these machines as not working. I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. .config attached. Cheers, Lorenzo # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc3-vanilla+swsusp # Thu Feb 10 15:44:07 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set CONFIG_MPENTIUMM=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # NeTraverse Win4Lin Support # # CONFIG_MKI is not set # # Power management options (ACPI, APM) # CONFIG_PM=y CONFIG_PM_DEBUG=y # CONFIG_SOFTWARE_SUSPEND is not set # # Software Suspend 2 # CONFIG_SOFTWARE_SUSPEND2=y CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y # # Image Storage (you need at least one writer) # CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y # # Page Transformers # CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y # # User Interface Options # CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y # # General Options # CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda7" # CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set # CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE is not set # # Debugging # CONFIG_SOFTWARE_SUSPEND_DEBUG=y # CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_DEBUG=y CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management)
Re: [ACPI] Re: Call for help: list of machines with working S3
Alistair John Strachan wrote: On Monday 14 Feb 2005 21:11, Pavel Machek wrote: Table of known working systems: Model hack (or how to do it) [...] HP NC6000 s3_bios (2) The above report is incorrect. On 2.6.11-rc4, even with the s3_bios option, the NC6000 (which I own) still does not wake up from S3 sleep. The wiki linked somewhere else in this thread also identifies these machines as not working. I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. .config attached. Cheers, Lorenzo # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc3-vanilla+swsusp # Thu Feb 10 15:44:07 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION= CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set CONFIG_MPENTIUMM=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # NeTraverse Win4Lin Support # # CONFIG_MKI is not set # # Power management options (ACPI, APM) # CONFIG_PM=y CONFIG_PM_DEBUG=y # CONFIG_SOFTWARE_SUSPEND is not set # # Software Suspend 2 # CONFIG_SOFTWARE_SUSPEND2=y CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y # # Image Storage (you need at least one writer) # CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y # # Page Transformers # CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y # # User Interface Options # CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y # # General Options # CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2=/dev/hda7 # CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set # CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE is not set # # Debugging # CONFIG_SOFTWARE_SUSPEND_DEBUG=y # CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_DEBUG=y CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tuesday 15 Feb 2005 12:12, Lorenzo Colitti wrote: Alistair John Strachan wrote: On Monday 14 Feb 2005 21:11, Pavel Machek wrote: Table of known working systems: Model hack (or how to do it) [...] HP NC6000 s3_bios (2) The above report is incorrect. On 2.6.11-rc4, even with the s3_bios option, the NC6000 (which I own) still does not wake up from S3 sleep. The wiki linked somewhere else in this thread also identifies these machines as not working. I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. .config attached. As recommended elsewhere in this thread, I'm not using any sort of framebuffer driver, but vesafb IS compiled in (but no vga= option is present). Does it need to be compiled out completely? I have acpi_sleep=s3_bios on cmdline. I am not using swsusp2 (and I can't see how this is at all related to software suspend). Perhaps it is the machine BIOS. Which version do you have? -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tue, 2005-02-15 at 13:12 +0100, Lorenzo Colitti wrote: I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Alistair John Strachan wrote: .config attached. As recommended elsewhere in this thread, I'm not using any sort of framebuffer driver, but vesafb IS compiled in (but no vga= option is present). Does it need to be compiled out completely? I don't remember, maybe you can deduce it from the .config I sent? I have acpi_sleep=s3_bios on cmdline. I am not using swsusp2 (and I can't see how this is at all related to software suspend). It works with or without swsusp2. Perhaps it is the machine BIOS. Which version do you have? I think it's vF.0F from July 2004. Cheers, Lorenzo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. Ok, here is the output from dmidecode (Debian package) and from lspci. I don't have acpidmp and I don't know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Cheers, Lorenzo # dmidecode 2.5 SMBIOS 2.3 present. 31 structures occupying 1354 bytes. Table at 0x000FF2EB. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard Version: 68BDD Ver. F.0F Release Date: 07/23/2004 Address: 0xE Runtime Size: 128 kB ROM Size: 1024 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5/720 KB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported AGP is supported LS-120 boot is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Handle 0x0001 DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard Product Name: HP Compaq nc6000 (DJ254A#ABB) Version: F.0F Serial Number: XX UUID: ---- Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. Base Board Information Manufacturer: Hewlett-Packard Product Name: 0890 Version: 8051 Version 1A.19 Serial Number: Not Specified Handle 0x0003 DMI type 3, 13 bytes. Chassis Information Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified Serial Number: XX Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: External Interface Enabled Handle 0x0004 DMI type 4, 35 bytes. Processor Information Socket Designation: U10 Type: Central Processor Family: Pentium M Manufacturer: Intel(R) ID: XX XX XX XX XX XX XX XX Signature: Type 0, Family 6, Model 9, Stepping 5 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) TM (Thermal monitor supported) SBF (Signal break on FERR) Version: Intel(R) Pentium(R) M processor 1400MHz
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. Ok, here is the output from dmidecode (Debian package) and from lspci. I don't have acpidmp and I don't know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Cheers, Lorenzo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
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 know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Find below a diff of my dmidecode output versus Lorenzo's. Nothing much to call home about. [alistair] 17:40 [~/dmidecode-2.5] diff -Nudr -U3 lorenzo dmiout --- lorenzo 2005-02-15 17:37:36.091770768 + +++ dmiout 2005-02-15 17:40:08.801555352 + @@ -1,13 +1,13 @@ # dmidecode 2.5 SMBIOS 2.3 present. 31 structures occupying 1354 bytes. -Table at 0x000FF2EB. +Table at 0x000FA1EE. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BDD Ver. F.11 + Release Date: 11/22/2004 Address: 0xE Runtime Size: 128 kB ROM Size: 1024 kB @@ -37,10 +37,10 @@ DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard - Product Name: HP Compaq nc6000 (DJ254A#ABB) - Version: F.0F - Serial Number: XX - UUID: ---- + Product Name: HP Compaq nc6000 (PK522PS#UUF) + Version: F.11 + Serial Number: censored + UUID: censored Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. @@ -52,11 +52,11 @@ Handle 0x0003 DMI type 3, 13 bytes. Chassis Information - Manufacturer: Hewlett-Packard + Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified - Serial Number: XX + Serial Number: censored Asset Tag: Boot-up State: Safe Power Supply State: Safe @@ -69,8 +69,8 @@ Type: Central Processor Family: Pentium M Manufacturer: Intel(R) - ID: XX XX XX XX XX XX XX XX - Signature: Type 0, Family 6, Model 9, Stepping 5 + ID: D6 06 00 00 BF F9 E9 AF + Signature: Type 0, Family 6, Model 13, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) @@ -93,13 +93,14 @@ FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) + SS (Self-snoop) TM (Thermal monitor supported) SBF (Signal break on FERR) - Version: Intel(R) Pentium(R) M processor 1400MHz + Version: Intel(R) Pentium(R) M processor 1.60GHz Voltage: 1.8 V External Clock: 100 MHz - Max Speed: 1400 MHz - Current Speed: 1400 MHz + Max Speed: 1600 MHz + Current Speed: 1600 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0005 @@ -131,8 +132,8 @@ Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: External - Installed Size: 1024 KB - Maximum Size: 1024 KB + Installed Size: 2048 KB + Maximum Size: 2048 KB Supported SRAM Types: Burst Installed SRAM Type: Burst @@ -194,7 +195,7 @@ Form Factor: SODIMM Set: None Locator: DIMM #1 - Bank Locator: 030B2C25 + Bank Locator: 6605F934 Type: DDR Type Detail: Synchronous Speed: 142 MHz (7.0 ns) @@ -213,12 +214,12 @@ Form Factor: SODIMM Set: None Locator: DIMM #2 - Bank Locator: 051FD180 + Bank Locator: 0322BB20 Type: DDR Type Detail: Synchronous Speed: 142 MHz (7.0 ns) Manufacturer: Not Specified - Serial Number: -X + Serial Number: censored Asset Tag: Not Specified Part Number: Not Specified Handle 0x000E @@ -294,8 +295,8 @@ Portable Battery Location: Primary Manufacturer: Hewlett-Packard - Manufacture Date: 12/12/2003 - Serial Number: 1 + Manufacture Date: 08/20/2004 + Serial Number: 01726 Name: Not Specified
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tue, 2005-02-15 at 17:42 +, Alistair John Strachan wrote: Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BDD Ver. F.11 + Release Date: 11/22/2004 Ok, so you both have different BIOS versions and different CPUs. Everything else looks pretty identical. Could you both stick /proc/acpi/dsdt up somewhere so I can check if there are any relevant looking differences? Thanks, -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BDD Ver. F.11 + Release Date: 11/22/2004 Ok, so you both have different BIOS versions and different CPUs. S3 works for me with both BIOS F.0F, which I was using before, and F.11, which I flashed today after learning it existed. Everything else looks pretty identical. Could you both stick /proc/acpi/dsdt up somewhere so I can check if there are any relevant looking differences? I would advise trying to compile a custom kernel from scratch with my .config first. I got S3 working first with a very basic kernel config, but I couldn't get it to work with my usual kernel. Assuming it was some feature that caused the problem, I started disabling features in the hope of getting it to work, but I ended up with two different kernels with seemingly irrelevant differences, of which one would succesfully resume and one wouldn't. So I started added features to the other kernel, and I never found out what caused the problem. I'm not saying that this is not deterministic, but I am saying that, at least in my case, it's not obvious what it is that stops S3 from working. :-) Cheers, Lorenzo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tuesday 15 Feb 2005 21:09, Lorenzo Colitti wrote: [snip] I would advise trying to compile a custom kernel from scratch with my .config first. I got S3 working first with a very basic kernel config, but I couldn't get it to work with my usual kernel. Assuming it was some feature that caused the problem, I started disabling features in the hope of getting it to work, but I ended up with two different kernels with seemingly irrelevant differences, of which one would succesfully resume and one wouldn't. So I started added features to the other kernel, and I never found out what caused the problem. I took your advice and built your kernel with a few modifications (XFS instead of ext, etc.). If I boot the kernel with init=/bin/sh, I can actually suspend! Thanks! I will exhaustively enable and disable drivers tomorrow to figure out which one is causing suspend to fail when I do a complete boot. Whatever we find is clearly a bug that should be fixed. It is not the framebuffer driver (I always ran without vesafb or radeonfb), and it is not my ipw2200 or USB drivers. Also, is USB suspend/resume supposed to work? My brief trials involved modprobing the USB HCD modules, which still allowed me to suspend/resume, but my USB mouse was non-functional on resume. -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi! I would advise trying to compile a custom kernel from scratch with my .config first. I got S3 working first with a very basic kernel config, but I couldn't get it to work with my usual kernel. Assuming it was some feature that caused the problem, I started disabling features in the hope of getting it to work, but I ended up with two different kernels with seemingly irrelevant differences, of which one would succesfully resume and one wouldn't. So I started added features to the other kernel, and I never found out what caused the problem. I took your advice and built your kernel with a few modifications (XFS instead of ext, etc.). If I boot the kernel with init=/bin/sh, I can actually suspend! Thanks! I will exhaustively enable and disable drivers tomorrow to figure out which one is causing suspend to fail when I do a complete boot. Whatever we find is clearly a bug that should be fixed. It is not the framebuffer driver (I always ran without vesafb or radeonfb), and it is not my ipw2200 or USB drivers. Also, is USB suspend/resume supposed to work? My brief trials involved modprobing the USB HCD modules, which still allowed me to suspend/resume, but my USB mouse was non-functional on resume. Yes, it seems to work quite okay. You may need to unplug/replug devices after resume, but it should be basically ok. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi. On Wed, 2005-02-16 at 12:54, Pavel Machek wrote: Also, is USB suspend/resume supposed to work? My brief trials involved modprobing the USB HCD modules, which still allowed me to suspend/resume, but my USB mouse was non-functional on resume. Yes, it seems to work quite okay. You may need to unplug/replug devices after resume, but it should be basically ok. We still have plenty of people for whom the best option is to build as modules, unload prior to suspending and reload afterwards. It seems to depend on what type your controller is: I do this for uhci_hcd and get fully functional usb post resume (-rc4). Regards, Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Ph: +61 (2) 6292 8028 Mob: +61 (417) 100 574 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
