Hi Ivar, On Mon, 2003-03-31 at 18:23, Ivar Alm wrote: > At 16:41 2003-03-31, mkamp@gmx.de wrote: > >Hi, > > > > I compiled 2.4.20 with all ACPI questions answered yes, powermgmt yes and > >apm no. > > > > When booting all looks nice until the very ned. Network seems to be up, at > >least the boot process is past dhcp, but I haven't seen any x-stuff yet and > >then the console blanks and nothing happens anymore. It does not respond to > >CTRL+ALT+BS and CTRL+ALT+F1 and CTRL+F7. > > > > When compiling with apm and acpi all off, the machine works fine. > > Check for ACPI messages in syslog. Check for error messages in dmesg as well. dmesg does contain the messages from the last boot, doesn't it? In order to access dmesg I need to reboot with acpi off and don't see anything relevant in dmesg anymore, do I? I attached the syslog from boot until I hit the power off button. I inlined the acpi part below and also a message from the x-server ... It seems to me that acpi killed my screen? On a sidebar I'd like to add that num-lock does still work. I am not able to test if I would be able to access the machine by net, but I would assume so. Apr 1 10:14:44 red kernel: ACPI: Core Subsystem version [20011018] Apr 1 10:14:44 red kernel: evxfevnt-0081 [-19] Acpi_enable : Transition to ACPI mode successful Apr 1 10:14:44 red kernel: Executing device _INI methods:.................evregion-0302 [-1] Ev_address_space_dispa: Region h andler: AE_ERROR [PCIConfig] Apr 1 10:14:44 red kernel: dswexec-0392 [-10] Ds_exec_end_op : [Or]: Could not resolve operands, AE_ERROR Apr 1 10:14:44 red kernel: Ps_execute: method failed - \_SB_.PCI0.PCIB.CDB_._INI (c12c1448) Apr 1 10:14:44 red kernel: nsinit-0351 [-17] Ns_init_one_device : \ /_SB_PCI0PCIBCDB_._INI failed: AE_ERROR Apr 1 10:14:44 red kernel: ....................................... Apr 1 10:14:44 red kernel: 56 Devices found: 56 _STA, 2 _INI Apr 1 10:14:44 red kernel: Completing Region and Field initialization:........... Apr 1 10:14:44 red kernel: 11/18 Regions, 0/0 Fields initialized (587 nodes total) Apr 1 10:14:44 red kernel: ACPI: Subsystem enabled Apr 1 10:14:44 red kernel: evregion-0218 [-1] Ev_address_space_dispa: no handler for region(cf725c88) [Embedded_control] Apr 1 10:14:44 red kernel: exfldio-0219 [-2] Ex_read_field_datum : Region Embedded_control(3) has no handler Apr 1 10:14:44 red kernel: dswexec-0392 [-10] Ds_exec_end_op : [LEqual]: Could not resolve operands, AE_NOT_EXIST Apr 1 10:14:44 red kernel: Ps_execute: method failed - \_SB_.ADP1._STA (c12c5608) Apr 1 10:14:44 red kernel: uteval-0337 [-17] Ut_execute_STA : _STA on ADP1 failed AE_NOT_EXIST Apr 1 10:14:44 red kernel: evregion-0218 [01] Ev_address_space_dispa: no handler for region(cf725c88) [Embedded_control] Apr 1 10:14:44 red kernel: exfldio-0219 [00] Ex_read_field_datum : Region Embedded_control(3) has no handler Apr 1 10:14:44 red kernel: dswexec-0392 [-8] Ds_exec_end_op : [LEqual]: Could not resolve operands, AE_NOT_EXIST Apr 1 10:14:44 red kernel: Ps_execute: method failed - \_SB_.ADP1._STA (c12c5608) Apr 1 10:14:44 red kernel: evregion-0218 [-1] Ev_address_space_dispa: no handler for region(cf725c88) [Embedded_control] Apr 1 10:14:44 red kernel: exfldio-0219 [-2] Ex_read_field_datum : Region Embedded_control(3) has no handler Apr 1 10:14:44 red kernel: dswexec-0392 [-10] Ds_exec_end_op : [LEqual]: Could not resolve operands, AE_NOT_EXIST Apr 1 10:14:44 red kernel: Ps_execute: method failed - \_SB_.BAT1._STA (c12c41c8) Apr 1 10:14:44 red kernel: uteval-0337 [-17] Ut_execute_STA : _STA on BAT1 failed AE_NOT_EXIST Apr 1 10:14:44 red kernel: evregion-0218 [01] Ev_address_space_dispa: no handler for region(cf725c88) [Embedded_control] Apr 1 10:14:44 red kernel: exfldio-0219 [00] Ex_read_field_datum : Region Embedded_control(3) has no handler Apr 1 10:14:44 red kernel: dswexec-0392 [-8] Ds_exec_end_op : [LEqual]: Could not resolve operands, AE_NOT_EXIST Apr 1 10:14:44 red kernel: Ps_execute: method failed - \_SB_.BAT1._STA (c12c41c8) Apr 1 10:14:44 red kernel: Power Resource: found Apr 1 10:14:44 red kernel: EC: found, GPE 24 Apr 1 10:14:44 red kernel: ACPI: System firmware supports S0 S3 S4 S5 Apr 1 10:14:44 red kernel: Processor[0]: C0 C1 C2 C3 Apr 1 10:14:44 red kernel: ACPI: Power Button (FF) found Apr 1 10:14:44 red kernel: ACPI: Multiple power buttons detected, ignoring fixed-feature Apr 1 10:14:44 red kernel: ACPI: Power Button (CM) found Apr 1 10:14:44 red kernel: ACPI: Sleep Button (CM) found Apr 1 10:14:44 red kernel: ACPI: Lid Switch (CM) found Apr 1 10:14:44 red kernel: evregion-0302 [04] Ev_address_space_dispa: Region handler: AE_BAD_PARAMETER [Embedded_control] Apr 1 10:14:44 red kernel: dswexec-0392 [-5] Ds_exec_end_op : [Store]: Could not resolve operands, AE_BAD_PARAMETER Apr 1 10:14:44 red kernel: Ps_execute: method failed - \_TZ_.THRM._TMP (c12c64e8) Apr 1 10:14:44 red kernel: pty: 256 Unix98 ptys configured Apr 1 10:14:44 red kernel: Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enab led later on I found this: Apr 1 10:15:00 red kdm[435]: Server for display :0 terminated unexpectedly Apr 1 10:15:00 red kdm[435]: Display :0 is being disabled (restarting too fast) > > When compiling with acpi off and apm on, the machine works fine and does > >even suspend when closing the lid. So a) Any idea, why acpi does blank my > >screen and b) what are the reasons to switch to acpi? Afaik suspend > >wouldn't work > >with acpi, would it? > > When you mean suspend, I assume you mean suspend to disk, also called > hibernate? Well, I am pretty open in that respect ;-) To be honest I don't have a clue. The opposite would be to suspend to ram, right? I haven't set aside a dedicated partition on my disk for suspending. If it is not doing it implicitly (swap space or something), than I would say I use suspend to ram, right? It doesn't take long to suspend, just 3 to 4 seconds and I've got 256MB ram. That also adds to my assumption that I am suspending to ram. The documentation isn't any help here and as this machine has never seen anything else than debian I don't know what the other os does say. > That works fine with swsusp and the scripts that follows. swsup with acpi? Which script? > My > only problems with the scripts was that I needed to rewrite some parts to > resolve som annoying issues with them. You wrote the script? Could you attach it? Is it part of debian? Thank you for your help. Cheers, Mariano
Attachment:
syslog.bz2
Description: application/bzip