Date: Tue, 6 Aug 2002 11:53:17 -0500 (CDT) From: John Utz <john@utzweb.net> To: Sean Chittenden <sean@chittenden.org> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: pcm0 not responding on -CURRENT... Message-ID: <Pine.LNX.4.44.0208061134070.1828-100000@jupiter.linuxengine.net> In-Reply-To: <20020806000914.GA89343@ninja1.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi; On Mon, 5 Aug 2002, Sean Chittenden wrote: > > 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. :-/ :-) should be, or already is, a FAQ entry. it is pretty damn hard to beleive the first time somebody tells you that tho...fortunately, the human mind is constructed in such a way that we eventually get desparate enuf to try *anything* once the agony has gone on long enuf :-) > Is there a reset that we're not performing on startup or unsuspend? -sc well... yes and no. it depends. most laptops are never really off, just like most VCR's and TV's and microwave ovens with clocks in them are never really off.... so, while smarter minds may have better information, i will venture that once ACPI is fully supported then FreeBSD will do a better job of managing this problem. but, you may always have a problem if you also boot windows on this laptop. why? because i think that ACPI 'opens the kimono' pretty far and wide, but it does it with the expectation that the operating system promises that it will 'wipe up afterwards'. :-) Windows device driver developers are under a lot of pressure to 'just get the damn thing shipped', so they arent guaranteed to have appropriately reset the various registers in the device when they stop using them. ACPI trusts that the registers are as they are supposed to be, because that was the promise made to it when the OS came into it's bedroom after the lights where out. But Windows is a naughty, rogueish OS that occasionally ravishes ACPI and then sneaks out the window. so, as ACPI's diligent parent, you are occasionally obligated to protect ACPI's modesty by: 1. Never allowing ACPI to be in the company of that nefarious cad named Windows. 2. If ACPI must come into intimate contact with Windows, you must carefully flush out ACPI's most private, delicate parts. so that's why ya gotta yank the power, eh! :-) man, i had fun writeing that! > > 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: <ESS Technology Maestro3> 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 > > -- John L. Utz III john@utzweb.net Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44.0208061134070.1828-100000>