From owner-freebsd-hackers Tue Jan 8 19: 0:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (pop-mu-20-1-dialup-366.freesurf.ch [194.230.238.110]) by hub.freebsd.org (Postfix) with ESMTP id 29F5537B416 for ; Tue, 8 Jan 2002 18:59:46 -0800 (PST) Received: from beerswilling.netscum.dyndns.dk (dcf77-zeit.netscum.dyndns.dk [172.27.72.27] (may be forged)) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6) with ESMTP id g092QIF00212 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Wed, 9 Jan 2002 03:26:19 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/8.11.6) id g092QIN00211; Wed, 9 Jan 2002 03:26:18 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Wed, 9 Jan 2002 03:26:18 +0100 (CET) Message-Id: <200201090226.g092QIN00211@beerswilling.netscum.dyndns.dk> Subject: console becomes unusable after screensaver -- who is to blame? From: BOUWSMA Beery To: freebsd-hackers@freebsd.org Organization: Men not wearing any pants that dont shave X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: TDC Suisse AG, Rumlang X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [replies sent directly to me may timeout and bounce, since I'm not online as often as I should be, but I'll check the list archives] Howdy This is something that normally hasn't been a problem -- with a different video card, I've loaded the green saver, done all my work on the sc consoles, the saver's kicked in when I've failed at staying awake, the monitor has powered down, and then when I've rolled over onto the keyboard, the monitor comes back on and I can work, or fall back asleep, or whatever. However, after putting in this newer Eeevil Kyro video card (pci1: at 0.0 irq 11 I haven't been able to wake up the display after the saver has kicked in for a length of time. I'm able to manually invoke (shift-pause) the saver and soon after, return to normal. And I've never had any problems with the other video card I've normally used. I made the mistake of falling asleep while listening to an mp3, and I seem to remember that it didn't sound quite right as I slept. When I half-woke, I couldn't get the display to come back on by the keyboard, but the mp3 sounded a bit better (I think, I was mostly asleep and the `music' wasn't something I'd be able to identify as sounding abnormal without being familiar with it, which I wasn't). I then moved the mouse. Then the `music' sounded like the machine had wedged. The monitor didn't come back on. I didn't get any response from a serial port that I thought might have a getty (later I verified it should). So after a reboot, when I got into saver mode again but without any mp3 playing, again I couldn't get the keyboard to wake the monitor. However, this time, whacking the mouse returned the display to life and indeed the mouse cursor was hopping smoothly around. But still the keyboard, a generic IBM clickety-click PS/2 model, could not be used for anything. But what I did notice is that each time I hit a key, any mouse movement would freeze for a few seconds, before returning to normal. Dis- and reconnecting the keyboard (I'm not admitting to doing so) did no good. Usual numlock and scrolllock keys made no difference. Only the serial port could be used, though I could cut and paste from the mouse into the login prompt. Obviously this particular video card seems to disagree with something. But who really is to blame? I don't know enough to say * the video card is responsible for hosing the keyboard * there's some BIOS video power manglement option that I need to change * there's something in the green_saver module or FreeBSD itself I haven't taken the time to try the several BIOS choices to see if they make a difference. But if anyone has any ideas, I'm open to learning. I haven't tried the apm_saver at all. --- Actually, it seems that what is happening with this particular video card and the green saver, is identical to what happens on a different machine with a completely different card and BIOS, when I boot without a keyboard attached at time of the kernel probe, such as when I boot to log to a serial console, and then attach the keyboard later. I have but a single keyboard I must juggle around. So it doesn't seem that the video card is at fault itself. Weird. thanks, barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message