From owner-freebsd-mobile Mon Aug 5 17:46:38 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4672437B400 for ; Mon, 5 Aug 2002 17:46:34 -0700 (PDT) Received: from mail.tgd.net (mail.tgd.net [209.81.25.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB54A43F1C for ; Mon, 5 Aug 2002 17:38:25 -0700 (PDT) (envelope-from sean@mail.tgd.net) Received: by mail.tgd.net (Postfix, from userid 1001) id ABC6D21023; Mon, 5 Aug 2002 17:09:14 -0700 (PDT) Date: Mon, 5 Aug 2002 17:09:14 -0700 From: Sean Chittenden To: John Utz Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: pcm0 not responding on -CURRENT... Message-ID: <20020806000914.GA89343@ninja1.internal> References: <20020708193250.GB50660@ninja1.internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > when in doubt. > > take all the batteries out. unplug it. > > let it sit for a sec. > > then put the batteries in and plug it in. > > see if that helps At first I thought you were kidding. This solved my problems. :-/ Is there a reset that we're not performing on startup or unsuspend? -sc > if it doesnt. remove all the power again. then enter the bios on the next > reboot prior to entering any operating systems and reset the BIOS to > default. > > then go on from there, etc. > > if that doesnt help. *consider* removing the cmos battery if it has one. > > i say consider because vital things might get permanently frobbed. > > if the cmos battery is soldered on, dont do it. if it's just in a slip > contact. it's probably ok to remove it and then reconfigure everything > from scratch. > > my particular laptop hp 800ct get's it's cardbus slots hosed if i boot > windows. i have to depower to fix it... > > On Mon, 8 Jul 2002, Sean Chittenden wrote: > > > > > Anyone have any ideas why I'd be able to load snd_pcm.ko, then > > > > have it stop responding as soon as I try and play a sound through > > > > it? The dev entry disappears after the 1st time I try and use it. > > > > I haven't recompiled my kernel, the only thing I've done recently > > > > was use bsd-airtools (which I think did something someplace...). > > > > > > > > Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc047b15c. > > > > ... > > > > pcm0: port 0xd800-0xd8ff mem 0xfaffe000-0xfaffffff irq 5 at device 8.0 on pci0 > > > > ... > > > > pcm0:play:0: play interrupt timeout, channel dead > > > > pcm0:play:0: play interrupt timeout, channel dead > > > > pcm0:play:0: play interrupt timeout, channel dead > > > > > > I get this, too from time to time on my DI 8100. However, if I > > > reboot, the problem is usually solved, so it's something > > > intermittent. I have noticed since the latest maestro3 update the > > > other day, I haven't seen the problem. > > > > Hmm... alright. As soon as usr.bin/ps is fixed on -CURRENT, I'll > > rebuild and plunge into KSE III land. <:~) > > > > > > ... > > > > > > > > The only other thing that I can note of any significance for this > > > > laptop is that on shutdown, this laptop will normally freeze hard > > > > after it says "unloading vnlru" or some such. Anyone have any ideas? > > > > > > > > My best/wild/flailing guess is that one of the airtools did something > > > > to my sound card... but I don't know how to reset the hardware config > > > > for the snd card. eh? -sc > > > > > > Could be. While I have a wireless card for this laptop, I do not use > > > bsd-airtools (yet). > > > > The thing that scares me about the bsd-airtools (port is in queue to > > be committed) is that is that it tried to access the audio device when > > I used it... and I haven't had sound since. To me it seems > > implausible or something that would last beyond reboots, but it has so > > I'm stumped. -sc -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message