Date: Tue, 4 Jun 1996 09:23:54 -0600 From: Nate Williams <nate@sri.MT.net> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: nate@sri.MT.net (Nate Williams), mobile@freebsd.org Subject: Re: Laptop hardware FOUND Message-ID: <199606041523.JAA17249@rocky.sri.MT.net> In-Reply-To: <199606041538.BAA07872@genesis.atrad.adelaide.edu.au> References: <199606041509.JAA17185@rocky.sri.MT.net> <199606041538.BAA07872@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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. Are you using the version of apm.c from the SNAP, or from the Nomad's? I'm a bit biased, but I think my version might work better. > > 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. All of this *while* FreeBSD is running? > (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) Cool. I'll bet you're not the only one who has a problem with this, but I'm not sure why yet. Again, I hope to get some time to look at it, but no promises as to when my life gets back to normal. Hopefully before the rivers and streams slow down enough to go fishing. :) > And here I was expecting that I'd have to start by hacking on the 'wdc' > support. What an anticlimax 8) It still might be something like that, but it's not as likely. > 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... You need to remove the interrupt that the IR port uses from /etc/pccard.conf. It steals one of the interrupts from the list, so if it's not a free interrupt remove it. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606041523.JAA17249>