RE: ACPI problems with Compaq Evo N610c (fwd)
Hello Doug, > From [EMAIL PROTECTED] Fri Sep 5 05:49:49 2003 > Not sure if you got a copy of this first time or not... Sorry, no I did not. My mail pickup system got screwed several times lately. > -- Forwarded message -- > From: Doug Barton <[EMAIL PROTECTED]> > To: "Cagle, John (ISS-Houston)" <[EMAIL PROTECTED]> > Cc: Tony Maher <[EMAIL PROTECTED]>, > Robert Blacquière <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > [EMAIL PROTECTED] > Date: Sun, 31 Aug 2003 19:50:03 -0700 (PDT) > Organization: http://www.FreeBSD.org/ > Subject: RE: ACPI problems with Compaq Evo N610c > > I got interested in this recently because I inherited one of these > laptops from work. > > On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: > > > Which version of the N610C BIOS are you using? (F.14 is the latest on > > the hp.com website.) I know that the _OSI("Windows 2001") bug will be > > fixed in the F.15 release, but I don't think the _GL_ portion of your > > patch will be included. Did you have to remove the Acquire & Release > > of _GL_ in order to get xbat to work? (This is not a problem we see > > with Linux ACPI in 2.4.21, so I think that FreeBSD's ACPI stack needs > > updating.) > > I just updated to F.15, and it does indeed fix the windows bit in the > output of 'acpidump -d'. However, even with Tony's recommendation of > removing the acquire/release of _GL in methods C12C and C12D, I still > can't get xbatt or wmbattery to run, even with the very latest -current > (which has had at least one acpi stack upgrade since 7/30). When I run > either command, it locks the box tight. If I ever get a cursor back, I > have to Ctrl-Alt-Backspace to get out of X, since I can't actually type > anything. > > I have a feeling that my acpi table didn't actually get overridden > though, due to the following from dmesg: > > ACPI: DSDT was overridden. > -0424: *** Error: UtAllocate: Could not allocate size 6e49202a > ACPI-0428: *** Error: Could not allocate table memory for [/* > ] length 6e49202a > ACPI-0368: *** Error: Could not copy override ACPI table, > AE_NO_MEMORY This certainly seems to be the case. I see ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS > Also, the "before" and "after" acpidump's don't show anything different. > So, I'm curious if wmbatt is still working for Tony and Robert or not > with the latest -current. I am currently running FreeBSD k9.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 30 11:48:23 EST 2003 [EMAIL PROTECTED]:/var/obj/space/usr/src/sys/K9 i386 and xbatt works (to certain extent - it show s being power cable in and out and shos charging state when first booted up but after insertion/removal of power cord it no longer shows charging stae or time left in battery) If I get a cahnce on weekend I'll update to latest and let you know. > The other problem I'm having is that doing 'sysctl -a', or just 'sysctl > hw.acpi' locks the system tight for a couple minutes, and never > completes. The last line that's printed to the screen is: > > hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > > Any ideas on that one? This is becase the DSDT was not overridden. I used to see this as well. -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
acpi - too hot, make world dies with various signals
Hello I attempted to do make buildworld on my N610c laptop but it kept dying with various signals *** Signal 4 *** Signal 11 The fan does go off and on in response to high CPU activity but I am guessing not enough and not soon enough. I rebooted with acpi disabled so that fan runs continuously (when there is AC power). Buildworld is now almost complete. It would be nice if acpiconf had option to switch cooling on (permanently) and off (well until acpi decided it was too hot). (Hmm maybe if I had of used 'acpiconf -d' I wouldn't have had to reboot and I could just disable thermal portion of acpi at boot. Wil that leave fan on when no ac power??? hmm.) Even better if acpi switched cooling on sooner. I'll try to look at it myself but that wont be till next weekend. But if anyone has patches or wants me to get debug info I'd be happy to try. thanks -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Compaq N610c and external keyboard
Hello fellow Compaq N610c users, when booting my N610c with an external keyboard, I'd see keyboard lights flash and keyboards worked at boot prompt but after booting finished neither the integratd kbd or the external kbd would work, At boot up would see: atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_probe_and_attach: atkbd0 attach returned 6 This can be fixed by changing /boot/device.hints hint.atkbd.0.flags="0x1" to hint.atkbd.0.flags="0x3" Now both keyboards work fine. Slowly getting there! -- tonym ps still waiting for that unexpected email explaining how to get syspension/resumption to work correctly and to eliminate loss of sync when switching from text to graphics mode. ;-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Compaq Evo N610c
On Thu Jul 31 01:04:15 2003 John Cagle wrote: > Which version of the N610C BIOS are you using? > (F.14 is the latest on the hp.com website.) Laptop is currently in use so I cannot get to bios however: from acpi_dsdt file RSDT: Length=44, Revision=1, Checksum=199, OEMID=COMPAQ, OEM Table ID=CPQ00B7, OEM Revision=0x18040320, Creator ID=CPQ, Creator Revision=0x1 > I know that the _OSI("Windows 2001") bug will be fixed in the > F.15 release, but I don't think the _GL_ portion of your patch > will be included. > Did you have to remove the Acquire & Release of _GL_ in order to > get xbat to work? Yes. Originally at boot up there would be complaints about not being able to acquire locks. I attempted to remove some locks but it was non-obvious to me which ones. Then yesterday received email from Simon who provided a diff against the latest bios on the Compaq site. I had to add in the Windows 2001 fix. > (This is not a problem we see with Linux ACPI in 2.4.21, so I think > that FreeBSD's ACPI stack needs updating.) I leave that to the acpi experts. At bootup I do see: ... ... ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 ACPI-0351: *** Error: Could not install PciConfig handler for C045, AE_ALREADY_EXISTS ACPI-0351: *** Error: Could not install PciConfig handler for C045, AE_ALREADY_EXISTS ACPI-0351: *** Error: Could not install PciConfig handler for C045, AE_ALREADY_EXISTS ACPI-0351: *** Error: Could not install PciConfig handler for C045, AE_ALREADY_EXISTS acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ... All this is on 5.1-R. I am currently building to 5-Current as of last nite. thanks -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compaq Evo N610c
Update on Compaq Evo N610c Thanks to an email from Simon in the UK I now have battery support in my N610c. /boot/loader.conf is now hw.pci.allow_unsupported_io_range=1 acpi_dsdt_load="YES" acpi_dsdt_name="/boot/acpi_dsdt.aml A patch for acpi_dsdt is attached. Now xbatt (and apm) works perfectly. Now all I need is another unexpected email that details how to solve the suspending problem (actually the resumption) and the switching between X and vga screen sync problem and I'd be completely set ;-) Thanks again to Simon! cheers -- tonym--- acpi_dsdt.orig Wed Jul 30 20:40:16 2003 +++ acpi_dsdt Wed Jul 30 20:44:50 2003 @@ -142,8 +142,7 @@ } If(LOr(LEqual(C006, 0x0), LEqual(C006, 0x3))) { If(CondRefOf(\_OSI, Local0)) { -If(\_OSI) { -"Windows 2001" +If(\_OSI("Windows 2001")) { Store(0x4, C006) } } @@ -1654,7 +1653,6 @@ } Method(C12C, 2) { Acquire(C11B, 0x) -Acquire(\_GL_, 0x) Add(Arg1, 0x1, Local6) If(LGreater(Local6, 0x11)) { Store(0x11, Local6) @@ -1690,14 +1688,12 @@ Store(Local3, C0FE) Store(Local4, C0FF) Store(Local5, C100) -Release(\_GL_) Release(C11B) Return(Local7) } Method(C12D, 2) { Store(0x0, Local1) Acquire(C11B, 0x) -Acquire(\_GL_, 0x) Store(SizeOf(Arg1), Local7) Store(0x09c4, Local0) While(LAnd(LNot(LEqual(0x0, C0FB)), LGreater(Local0, 0x0))) { @@ -1728,7 +1724,6 @@ Store(Local3, C0FE) Store(Local4, C0FF) Store(Local5, C100) -Release(\_GL_) Release(C11B) Return(Local0) } ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compaq Evo N610c
Robert, >> debug.acpi.disable="cmbat" > > I did this today, mmm seems something is working (work around). But > battery stats an apm like monitoring of the battery is not working any > more. So what happens if the battery is empty? just system shutdown > without saving of the memory and so? This is expected since we are disabling battery acpi subsystem. And yes there is a downside :-( I'll test to see exactly what happens. >> Minor glitches: >> Switching to and from X can result in screen not being properly sync'd. >> Switching back and forth beween X and console or closing lid often fixes it >> but not always. > > Those glitches are "known" it seems older ComPaQ laptops had the same > issues long time ago.=20 Ok. Are they 'unfixable' or no-one with sufficent vga knowledge has one of these? > Under 4.8 all works with my setup. I have to use 4.8 at home because of > wireless access Ok, good to know. I think I'll try to stick with -Current for now. thanks -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Compaq Evo N610c
Hello, I recently installed FreeBSD 5-1-Release onto a Compaq Evo N610c and upgraded to -Current. FreeBSD k9.home 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Wed Jul 16 08:26:32 EST 2003 [EMAIL PROTECTED]:/var/obj/space/usr/src/sys/GENERIC i386 There were problems when booting with ACPI (short term hanging), running sysctl -a (hanging) and getting pcmcia cards to be recognized. These have been described in emails from Robert ??? and Vaidas Damosevicius (who listed the hw.pci.allow_unsupported_io_range="1" fix). With the following in /boot/loader.conf these problem appear to to have been resolved. hw.pci.allow_unsupported_io_range="1" debug.acpi.disable="cmbat" hw.acpi.verbose="1" (Well I dont think verbose helped, I just want to see more messages.) Without debug.acpi.disable="cmbat", the battery was seen but it complained about it being corrupted. How do you disable multiple drivers? Have multiple lines or a single disable with a delimited string? What delimiter? The man page for acpi could do with some examples I think. Testing card insertion/removal: aic1: at port 0x340-0x35f irq 11 function 0 config 9 on pccard0 aic1: AIC6360, dma, disconnection, parity check, fast SCSI aic1: detached I have only done insertion and removal, I havent actually tried to use device yet. Minor glitches: Switching to and from X can result in screen not being properly sync'd. Switching back and forth beween X and console or closing lid often fixes it but not always. >From boot -v vga0: vga: WARNING: video mode switching is not fully supported on this adapter so this is a known problem. Any fixes? Suspending works - resumption does not :-( Any ideas? thanks -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Confusing error messages from shell image activation
> On the other hand, Applixware Office ships a precompiled package for > /usr/local, and doesn't like being installed anywhere else. Which > means I've got a couple of hundred megabytes being backup up for no > good reason :-(. Really?! I have it installed in /opt/applix and I dont think there are any symlinks anywhere in /usr/local for it. It works fine. The install logfile: CopyFile: /cdrom/applix - /opt/applix/applix CopyFile: /cdrom/axart/alphabet/a1.ag - /opt/applix/axart/alphabet/a1.ag ... ... ... CopyFile: /opt/applix/axdata/axlicensedemo - /opt/applix/axlocal/axlicensedat CopyFile: /opt/applix/axdata/eng/ax_prof4.eng - /opt/applix/axdata/ax_prof4 The location was an install question from memory. This is version 4.42. Maybe Version 5 different? -- tonym (who uses /usr/local for ports/packages, /usr/host for handbuilt stuff and /opt for really big packages that have their own internal hierachy - I am so confused ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: move portmap(8) from /usr/sbin to /sbin
> Sick, poor in performance and the wrong tool for the job. > See mount_null(8) for more details on how to do it right. Yes its perfect for the job apart from: man mount_null THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. This code also needs an owner in order to be less dangerous - serious hackers can apply by sending mail to [EMAIL PROTECTED] and announcing their intent to take it over. I actually tried it a few weeks ago and yes it did screw up files :-( (that was on stable - my current box is broken but checking CVS man page it looks like the warning still applies) But I'd be happy to hear it works on current! tonym To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
> I have to say that PHK has become the MASTER at pissing > people off, ensuring that his opponent goes the deep end > and staying calm so the blame obviously does not fall on > him. Got to admit his formula is very very nice 8) I dont think so. Whatever PHK may or may not have done in the past his answers in this latest storm in a tea cup were more than reasonable and informative. > By a long shot the problem is NOT Karl. It takes at least > TWO to engage in a combatitive conflict -- that is if > you are not schizophreniac. Yes it was two - Karl vs reasoned discussion. tonym To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Speaking of moving files
> A person who really knew fsdb could do it /bin/fsdb, infact it's And for everyone else ;-) WARNING Use this tool with extreme caution--you can damage an FFS file system beyond what fsck(8) can repair. tonym To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message