[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fglrx and software suspend
- From: "Leo Gürtler" <leo dot c dot g at web dot de>
- Date: Wed, 30 Mar 2005 01:54:46 +0200
Matthew Tippett schrieb:
vbetool is a program that IIRC drops into real mode, and allows INT10
calls to be made. One INT10 call allows you to 'boot the video card'.
From the driver perspective it is very brute force and may not work in
all cases, but is a suitable work-around until we (ATI) have our ACPI
support complete (can't discuss a schedule thought).
Thanks - worked out-of-the-box. Very nice, swsusp2 is soo fast I do not
really need suspend-to-ram anymore.
btw: after building swsusp2 into the kernel, vmware4.5 does not work
anymore and speaks of problems and the computer cannot reboot anymore
(had to shutdown it manually). I do not know if this is due to ati-fglrx
or swsusp2, maybe both. Anyway, here is the output from the log, the
problem occurs when disabling the vmware-bridge. after removing vmware
from /etc/rc2.d the problem went away, so I assume it has rather to do
with swsusp2.
Is there anyone who uses vmware, kernel 2.6.11.x, swsusp2 and the fglrx?
Mar 30 01:26:51 localhost kernel: e0cc4965
Mar 30 01:26:51 localhost kernel: PREEMPT
Mar 30 01:26:51 localhost kernel: Modules linked in: fglrx vmnet pcmcia
usb_storage scsi_mod usbserial usbmouse ohci_hcd yenta_socket
rsrc_nonstatic pcmcia_core snd_intel8x0m snd_intel8x0 snd_ac97_codec
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc
i2c_i801 i2c_core intel_agp agpgart evdev usbhid uhci_hcd ibm_acpi
ehci_hcd usbcore e1000 ide_cd cdrom
Mar 30 01:26:51 localhost kernel: CPU: 0
Mar 30 01:26:51 localhost kernel: EIP:
0060:[pg0+545749349/1069224960] Tainted: P VLI
Mar 30 01:26:51 localhost kernel: EFLAGS: 00010282 (2.6.11.5-thinkpad)
Mar 30 01:26:51 localhost kernel: EIP is at VNetNetifStartXmit+0x15/0x50
[vmnet]
Mar 30 01:26:51 localhost kernel: eax: dd878c64 ebx: dd878c64 ecx:
00000001 edx: dd878c64
Mar 30 01:26:51 localhost kernel: esi: 00000009 edi: 00001042 ebp:
00000000 esp: da187e78
Mar 30 01:26:51 localhost kernel: ds: 007b es: 007b ss: 0068
Mar 30 01:26:51 localhost kernel: Process ifconfig (pid: 5687,
threadinfo=da186000 task=da1a1570)
Mar 30 01:26:51 localhost kernel: Stack: dd878c64 c02c256a dd878c64
00001003 c02b47c1 dd878c64 00000009 dd878c64
Mar 30 01:26:51 localhost kernel: dd878c64 00001003 c02b5d43
dd878c64 c02b45c6 dd878c64 da187ef4 ffffff9d
Mar 30 01:26:51 localhost kernel: ddf968ee ddf968c0 c02f16b7
dd878c64 00001042 00000010 00000000 00000000
Mar 30 01:26:51 localhost kernel: Call Trace:
Mar 30 01:26:51 localhost kernel: [dev_deactivate+90/128]
dev_deactivate+0x5a/0x80
Mar 30 01:26:51 localhost kernel: [dev_close+177/192] dev_close+0xb1/0xc0
Mar 30 01:26:51 localhost kernel: [dev_change_flags+83/304]
dev_change_flags+0x53/0x130
Mar 30 01:26:51 localhost kernel: [dev_load+54/128] dev_load+0x36/0x80
Mar 30 01:26:51 localhost kernel: [devinet_ioctl+599/1488]
devinet_ioctl+0x257/0x5d0
Mar 30 01:26:51 localhost kernel: [inet_ioctl+102/176] inet_ioctl+0x66/0xb0
Mar 30 01:26:51 localhost kernel: [sock_ioctl+201/576]
sock_ioctl+0xc9/0x240
Mar 30 01:26:51 localhost kernel: [do_ioctl+142/160] do_ioctl+0x8e/0xa0
Mar 30 01:26:51 localhost kernel: [old_mmap+253/272] old_mmap+0xfd/0x110
Mar 30 01:26:51 localhost kernel: [vfs_ioctl+101/496] vfs_ioctl+0x65/0x1f0
Mar 30 01:26:51 localhost kernel: [sys_ioctl+69/112] sys_ioctl+0x45/0x70
Mar 30 01:26:51 localhost kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Mar 30 01:26:51 localhost kernel: Code: bc 27 00 00 00 00 31 d2 8b 44 24
04 0f ab 50 24 31 c0 c3 8d 76 00 83 ec 10 8b 44 24 14 89 74 24 0c 8b 74
24 18 85 c0 89 5c 24 08 <8b> 5e 68 74 1a 89 44 24 04 89 1c 24 e8 ca d6
ff ff ff 83 80 02
Mar 30 01:30:56 localhost shutdown[5741]: shutting down for system reboot
Mar 30 01:31:03 localhost kernel: <7>mtrr: no MTRR for e0000000,400000
found
Mar 30 01:31:30 localhost shutdown[5889]: shutting down for system halt
best regards,
Leo
Regards,
Matthew
Leo Gürtler wrote:
Ludovic Noury schrieb:
You have to install the "vbetool" package and use it to save/restore
the
video card state. To do so you just have to uncomment "EnableVbetool
yes"
in /etc/hibernate/hibernate.conf.
Hi,
to understand what is does -> does this work also with normal swsups
(not swsusp2)?
And
how to call vbetool exactly ? I looked into /usr/bin/hibernate but did
not found anything related to the option "EnableVbetool yes" in
/etc/hibernate/hibernate.conf
Thus, if I would call it manually, how does it work?
thanks + greetings,
Leo
I've only tested it with kernel 2.6.10, Flavio's packaged ATI
drivers and
swsusp2 (patch at http://www.suspend2.net/) on a IBM Thinkpad T42p.
Please
note that swsusp2 is MUCH faster than the kernel swsusp.
Best Regards,
--
Ludovic Noury