a) Can anyone confirm what the Yast Gui that sets Network Manager to use? I mean does it simply define an interface for eth0 e.g.
auto eth0
iface eth0 inet dhcp
or does it do more than that?
b) Also anyone know how to get some password protection on lid-open after s2ram suspension? I have yet to get s2ram to work on the new version 11.3 but it still works ok on 11.2 - without password protection however which is a bit of a nuisance. The same password protection I get screen dimming would be fine.
c) 11.3 seems to have broken suspend via s2ram although it works in /bin/bash with
/sbin/s2ram -f -r -a 2
unfortunately in runlevel3 and beyond it doesn’t turn on the display (although the caps lock key light etc is working).
I read somewhere that my machine supports APM as opposed to acpi and was wondering whether I should try this. Its seems like the newer kernels along with KMS have broken my suspend. (I disable KMS on boot to enable X-Windows GUI but this doesn’t help me resume my display from suspend).
nomodeset added to the kernel options for the bootloader solves the black screen for GUI session
For other stuff relating to suspend:
I have 2 routers and apparently all flavours and current versions of linux find this a problem.
Computer(s) >> Local Safecom 4 Port Cable/DSL Broadband Router (e.g. for WAN sharing) >> ethernet/powerline >> Netgear Broadband Cable Modem Router >> ISP
Both routers have NAT hardware firewall if that is relevant. Until I can figure out how to edit my config somewhere so that both routers and DNS etc are accommodated I have removed the local Safecom router which resolves the problem. Without the extra router I am now using Network Manager (or ifup if I want) and can suspend and hibernate without too much difficulty.
One thing I have done is to add a command to a hook file called 99mylocal I created (and made executable) in /etc/pm/sleep.d to refresh the network. Here is the text of 99mylocal:
#!/bin/bash
case $1 in
hibernate)
echo "Hibernating... suspending to Disk... ;>}"
echo "Unmounting external disks..."
umount -l /dev/sdb1 /dev/sdc1 /dev/sdc2
echo "Taking eth0 down before hibernation..."
/sbin/ifdown eth0
;;
suspend)
echo "Suspending to RAM... ;>}"
echo "Unmounting external disks..."
umount -l /dev/sdb1 /dev/sdc1 /dev/sdc2
echo "Taking down eth0 before suspend ..."
/sbin/ifdown eth0
;;
thaw)
echo "Suspend to disk is over, we are resuming..."
echo "Mounting disks..."
mount -a
echo "Renewing eth0 "
/sbin/rcnetwork restart
echo "network restarted"
;;
resume)
echo "Suspend to RAM seems to be over..."
echo "Mounting disks..."
mount -a
echo "Renewing eth0 "
/sbin/rcnetwork restart
echo "network restarted"
;;
*) echo "somebody is calling me totally wrong."
;;
esac
Without creating the hookfile I could get the same result by opening and then closing the Network Settings control panel in Yast after resuming from suspend or hibernate - since closing the cp runs rcnetwork restart but the hookfile automates it.
