From owner-freebsd-mobile Tue Jun 4 08:16:31 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA20511 for mobile-outgoing; Tue, 4 Jun 1996 08:16:31 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA20506 for ; Tue, 4 Jun 1996 08:16:25 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id BAA07872; Wed, 5 Jun 1996 01:08:42 +0930 From: Michael Smith Message-Id: <199606041538.BAA07872@genesis.atrad.adelaide.edu.au> Subject: Re: Laptop hardware FOUND To: nate@sri.MT.net (Nate Williams) Date: Wed, 5 Jun 1996 01:08:42 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, nate@sri.MT.net, mobile@freebsd.org In-Reply-To: <199606041509.JAA17185@rocky.sri.MT.net> from "Nate Williams" at Jun 4, 96 09:09:01 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams stands accused of saying: > > > > Uhh, no process crash here. I get a trap 12 somewhere in the APM bios if > > I try to use the 'apm' command (though it's worked a couple of times, > > but I don't know why). And the system goes away and never comes back > > if I suspend with the ethernet card in it. > > Did using the APM_DSVALUE_BUG hack fix that? No. I've had 'apm' work a couple of times; I think one of them was running the GENERIC kernel with the dormant 'apm' driver enabled, but I'm not totally sure there. As I said, it's not too critical just yet. > Re: the suspend and never come back. That's a tough one, since the APM > BIOS is in complete control of the system, so it's *extremely* hard to > debug the system coming back. See my other post on this for more juice. The BIOS in the Sharp actually seems to be quite civilised; I can hotkey-suspend, hotkey into the APM setup screen, and even hotkey the speaker volume up and down without it appearing to faze the system at all. (Although while I was tinkering with that I noticed that the kernel build I was doing was taking a _long_ time. I dunno whether it went into some sort of 'crawl' mode or what. 'systat -vmstat' showed the CPU maxed out, but the next build I did (just watching the files flip by) was much quicker. Anyway, if I can resolve restarting the 'ed' card, I'm in business 8) And here I was expecting that I'd have to start by hacking on the 'wdc' support. What an anticlimax 8) And speaking of hackery, is it normal for the pcic to share an interrupt with another port? I was half hoping to use the IR port, but it's on the same interrupt as the pcic, so it never probes... > Nate -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[