Re: acpi patch for dell laptop?
doesn't work for several models.. Including Inspiron 7500. WHo knows enough about this to be able to look at debug info I have? My system gives lots of: acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc167ed60), AE_ERROR ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ad0: 24207MB IBM-DARA-225000 [49184/16/63] at ata0-master UDMA33 ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER acd0: DVD-ROM TOSHIBA DVD-ROM SD-C2402 at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s4a ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER [...] On Sun, 22 Jun 2003, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. It seems to work for me. The ACPI warnings about zero length buffers go away at least. I've got a Dell Inspirion 8500, A03 BIOS. Ken -- Kenneth Merry [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: audigy 2
On Tue, Jun 10, 2003 at 09:55:18AM +0400, Yuriy Tsibizov wrote: it?s just another question about audigy 2! does someone have audigy 2 working well in freebsd?? i don?t have sound since november 2002.:( ..snip.. or wait for 2-3 days, I have Audigy 2 support in my drivers (http://chibis.persons.gfk.ru/audigy/) but I forgot to put them on website ;-) Unfortunately your driver isn't very committable -- unfortunately you took it upon himself to totally reformat our emu10k1.c file in addition to embellishing it. So it is impossible to see what changes you really made to the driver. I don't suppose you've got a patch with the minimal number of changes to support audigy and audigy2? Old driver (emu10k1.c) was too big for me to work on it and was difficult to add MIDI support. I know that my driver will never go into the tree - sound@ decided to use Orlando Bassotto's work. His driver is much closer to original emu10k1.c that mine. Yuriy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
On Sun, Jun 22, 2003 at 09:35:32PM -0600, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. It seems to work for me. The ACPI warnings about zero length buffers go away at least. Great. Do you also have working battery status now? I've got a Dell Inspirion 8500, A03 BIOS. I've added this model to the confirmed working model list on the page. I've also added the models from the rest of the reports. Thanks to all the people who submitted their report! Maybe it is time to think about an integrated kernel database of bad ACPI hardware, so that people won't have to search on the mailing lists/web to get their laptop to work? --Stijn -- Tact, n.: The unsaid part of what you're thinking. pgp0.pgp Description: PGP signature
Error in ipfw manpage (EXAMPLES/SETS OF RULES)
Submitter-Id: current-users Originator:Kostyuk Oleg [EMAIL PROTECTED] Organization: Confidential: no Synopsis: Error in ipfw manpage (EXAMPLES/SETS OF RULES) Severity: non-critical Priority: low Category: docs Class: doc-bug Release: FreeBSD 5.1-RELEASE i386 Environment: System: FreeBSD demani.digma 5.1-RELEASE FreeBSD 5.1-RELEASE #3: Mon Jun 9 12:19:59 EEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/CUB i386 Description: The ipfw(8) manpage has an example of using ipfw sets of rules, but the example does not work. How-To-Repeat: Try to execute commands from EXAMPLES/SETS OF RULES manpage section # id uid=0(root) gid=0(wheel) groups=0(wheel), 5(operator) # ipfw disable set 18 ipfw: unrecognize enable/disable keyword: set Fix: Patch for manpage --- /usr/src/sbin/ipfw/ipfw.8 Sat Mar 15 03:13:00 2003 +++ ipfw.8 Mon Jun 23 09:50:59 2003 @@ -2001,9 +2001,9 @@ .Ss SETS OF RULES To add a set of rules atomically, e.g. set 18: .Pp -.Dl ipfw disable set 18 +.Dl ipfw set disable 18 .Dl ipfw add NN set 18 ... # repeat as needed -.Dl ipfw enable set 18 +.Dl ipfw set enable 18 .Pp To delete a set of rules atomically the command is simply: .Pp @@ -2011,9 +2011,9 @@ .Pp To test a ruleset and disable it and regain control if something goes wrong: .Pp -.Dl ipfw disable set 18 +.Dl ipfw set disable 18 .Dl ipfw add NN set 18 ... # repeat as needed -.Dl ipfw enable set 18 ; echo done; sleep 30 ipfw disable set 18 +.Dl ipfw set enable 18 ; echo done; sleep 30 ipfw set disable 18 .Pp Here if everything goes well, you press control-C before the sleep terminates, and your ruleset will be left active. Otherwise, e.g. if ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] usbdevs {-1.5}
[EMAIL PROTECTED] Current, I've gone through the USB hardware that I had laying around and added a series of entries in usbdevs. I submitted a couple of entries a while ago, but I guess the email got lost in the noise. Who should I contact about getting this committed? Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems on Samsung Q10 (AE_AML_NO_RETURN_VALUE /AE_BAD_PARAMETER)
Hi! I recently bought a Samsung Q10 and on both 5.1-RELEASE and -current I get these acpi errors: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sun Jun 22 19:00:44 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DEIMOS Preloaded elf kernel /boot/kernel/kernel at 0xc04ee000. Preloaded elf module /boot/kernel/snd_ich.ko at 0xc04ee2bc. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04ee368. Preloaded elf module /boot/kernel/acpi.ko at 0xc04ee414. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 996682387 Hz CPU: Mobile Intel(R) Pentium(R) III CPU - M 1000MHz (996.68-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b4 Stepping = 4 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 393740288 (375 MB) avail memory = 376864768 (359 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fdf30 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node
Re: ACPI problems on Samsung Q10 (AE_AML_NO_RETURN_VALUE /AE_BAD_PARAMETER)
Hi, I'm seeing similiar things on my setup - both the ACPI Global Lock messages and the wi0 issues. In fact, the wi driver seems to be incredibly unstable - Every half hour or so I need to remove and re-insert the card to regain network connectivity (and ofcourse killall dhclient ; ifconfig wi0 ... ; dhclient wi0 ). I have described my problems in more detail in my thread 'ACPI issues on ThinkPad T21 + Dock'. /Eirik On Mon, 23 Jun 2003 10:40:06 +0200 Hendrik Scholz [EMAIL PROTECTED] wrote: Hi! I recently bought a Samsung Q10 and on both 5.1-RELEASE and -current I get these acpi errors: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sun Jun 22 19:00:44 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DEIMOS Preloaded elf kernel /boot/kernel/kernel at 0xc04ee000. Preloaded elf module /boot/kernel/snd_ich.ko at 0xc04ee2bc. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04ee368. Preloaded elf module /boot/kernel/acpi.ko at 0xc04ee414. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 996682387 Hz CPU: Mobile Intel(R) Pentium(R) III CPU - M 1000MHz (996.68-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b4 Stepping = 4 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 393740288 (375 MB) avail memory = 376864768 (359 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fdf30 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc11ae480), AE_AML_NO_RETURN_VALUE acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-1287: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node 0xc11ae620), AE_AML_NO_RETURN_VALUE ACPI-0175: *** Error: Method execution failed [\\_SB_.ADP1._STA] (Node
Re: nVidia nForce2 AGP chipset drivers
On Sun, 22 Jun 2003, Matthew N. Dodd wrote: On Mon, 23 Jun 2003, Arjan van Leeuwen wrote: Hmm... I don't have the hardware either, but I was thinking about buying a new mainboard based on it (if there is support in FreeBSD, of course :)). Maybe someone who actually has an nForce2 board can help us out here? Can you post the patches to the list so that someone can test them? Lacking the hardware, (and sleep last night when I started), I'm not yet far along enough to have something that is testable. ftp://ftp.jurai.net/users/winter/patches/nforce-agp.diff I suspect using this will result in a panic so load this as a module. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Bits detached from the build (please help tidying this up)
On Mon, Jun 23, 2003 at 12:36:58AM -0700, Tim J. Robbins wrote: tjr 2003/06/23 00:36:58 PDT FreeBSD src repository Removed files: usr.sbin/prefix Makefile prefix.8 prefix.sh Log: Delete prefix: its functionality has been merged into ifconfig. Thanks! Here's the almost complete list of all subdirectories detached from the build (all concerned parties are explicitly CC:ed and quoted in parenthesis): a.out bits that eventually will be made a port: gnu/lib/libgcc_r(peter) libexec/rtld-aout (peter) usr.bin/ar (peter) usr.bin/nm (peter) usr.bin/size(peter) usr.bin/strings (peter) usr.bin/strip (peter) Bluetooth utilities (have never been connected to the build): usr.bin/bluetooth (julian) usr.sbin/bluetooth (julian) HPFS support (have never been connected to the build): sbin/mount_hpfs (semenu) sys/modules/hpfs(semenu) KLD modules: sys/modules/amd (scottl) sys/modules/null(markm) sys/modules/oldcard (imp) sys/modules/pcfclock(obrien)didn't work on Alpha sys/modules/pcic(imp) sys/modules/rndtest (sam) sys/modules/scd (mdodd) sys/modules/sem (alfred) sys/modules/svr4(green) sys/modules/ufs (iedowse) In case where a module is not connected on purpose (like is the case with null and ufs modules), could the respective developers please add a commented out entry to modules/Makefile explaining the reason? And in case of a broken module, can it be left commented out there too and marked as such, please? Miscellaneous: gnu/lib/libiberty (obrien) kerberos5/libexec/hprop (markm) sbin/disklabel (phk) this must die sbin/ffsinfo(mckusick) PR bin/53517 usr.sbin/asf(grog) forgot to attach? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
--- Julian Elischer [EMAIL PROTECTED] wrote: doesn't work for several models.. Including Inspiron 7500. WHo knows enough about this to be able to look at debug info I have? John Baldwin has posted a patch which worked for me on my Thinkpad 600X with the same ACPI-0340 error. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=214877+0+archive/2003/freebsd-current/20030615.freebsd-current My system gives lots of: acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc167ed60), AE_ERROR ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ad0: 24207MB IBM-DARA-225000 [49184/16/63] at ata0-master UDMA33 ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER acd0: DVD-ROM TOSHIBA DVD-ROM SD-C2402 at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s4a ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER [...] On Sun, 22 Jun 2003, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. It seems to work for me. The ACPI warnings about zero length buffers go away at least. I've got a Dell Inspirion 8500, A03 BIOS. Ken -- Kenneth Merry [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI CD mount problems
On Sun, Jun 22, 2003 at 10:24:44PM -0600, Kenneth D. Merry wrote: On Tue, Jun 17, 2003 at 22:01:02 -0400, Guy Middleton wrote: I have a Yamaha CRW4416S CD drive as /dev/cd0. When I try to mount a disk, it says cd9660: /dev/cd0: Invalid argument, and this in the log file: (cd0:ahc0:0:3:0): READ(10). CDB: 28 0 0 0 0 10 0 0 1 0 (cd0:ahc0:0:3:0): CAM Status: SCSI Status Error (cd0:ahc0:0:3:0): SCSI Status: Check Condition (cd0:ahc0:0:3:0): ILLEGAL REQUEST asc:21,0 (cd0:ahc0:0:3:0): Logical block address out of range (cd0:ahc0:0:3:0): Unretryable error (cd0:ahc0:0:3:0): cddone: got error 0x16 back I know the drive works, I can write good disks with it. What's happening here? This is on 5.1-RELEASE. It's complaining that we're trying to access a logical block address that isn't on the CD. Since it is trying to read block 16 (0x10) from the CD, my guess is that it is a blank CD. Does it do that for every CD, or just that one? This was actually a FreeBSD ISO distribution disk. It does this for every disk; the only time I could successfully mount a disk was with one I had just written on that drive. If I then opened and closed the drive, I could not mount the disk. What does dmesg say about the CD capacity if you boot? You can also get that CD's capacity like this: camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 The first number is the last LBA on the CD, the second one is the blocksize. dmesg says this at boot: cd0 at ahc0 bus 0 target 3 lun 0 cd0: YAMAHA CRW4416S 1.0f Removable CD-ROM SCSI-2 device cd0: 8.333MB/s transfers (8.333MHz, offset 31) cd0: cd present [0 x 2048 byte records] Camcontrol says this: # camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 -1 2048 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
Hi, doesn't work for several models.. Including Inspiron 7500. WHo knows enough about this to be able to look at debug info I have? John Baldwin has posted a patch which worked for me on my Thinkpad 600X with the same ACPI-0340 error. I tried this patch, and while it does get rid of that particular error message, I have a feeling it's (ACPI/the patch/or something) causing my system to overheat, making it power down after a while. Funny thing is that this only seems to happen while I'm in a dockingstation (ThinkPad T21 + Dock). And with ACPI disabled, the machine refuses totally to boot, it hangs at 'Mounting root from ...'. If I undock the machine, I can boot with and without ACPI, with the latter option being the only usable (stable) mode. /Eirik My system gives lots of: acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT1._STA] (Node 0xc167ed60), AE_ERROR ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ad0: 24207MB IBM-DARA-225000 [49184/16/63] at ata0-master UDMA33 ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER acd0: DVD-ROM TOSHIBA DVD-ROM SD-C2402 at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s4a ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER [...] On Sun, 22 Jun 2003, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. It seems to work for me. The ACPI warnings about zero length buffers go away at least. I've got a Dell Inspirion 8500, A03 BIOS. Ken -- Kenneth Merry [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: SCSI CD mount problems
On Mon, Jun 23, 2003 at 09:50:39 -0400, Guy Middleton wrote: On Sun, Jun 22, 2003 at 10:24:44PM -0600, Kenneth D. Merry wrote: On Tue, Jun 17, 2003 at 22:01:02 -0400, Guy Middleton wrote: I have a Yamaha CRW4416S CD drive as /dev/cd0. When I try to mount a disk, it says cd9660: /dev/cd0: Invalid argument, and this in the log file: (cd0:ahc0:0:3:0): READ(10). CDB: 28 0 0 0 0 10 0 0 1 0 (cd0:ahc0:0:3:0): CAM Status: SCSI Status Error (cd0:ahc0:0:3:0): SCSI Status: Check Condition (cd0:ahc0:0:3:0): ILLEGAL REQUEST asc:21,0 (cd0:ahc0:0:3:0): Logical block address out of range (cd0:ahc0:0:3:0): Unretryable error (cd0:ahc0:0:3:0): cddone: got error 0x16 back I know the drive works, I can write good disks with it. What's happening here? This is on 5.1-RELEASE. It's complaining that we're trying to access a logical block address that isn't on the CD. Since it is trying to read block 16 (0x10) from the CD, my guess is that it is a blank CD. Does it do that for every CD, or just that one? This was actually a FreeBSD ISO distribution disk. It does this for every disk; the only time I could successfully mount a disk was with one I had just written on that drive. If I then opened and closed the drive, I could not mount the disk. I assume you can put the disks in other drives and they work fine? What does dmesg say about the CD capacity if you boot? You can also get that CD's capacity like this: camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 The first number is the last LBA on the CD, the second one is the blocksize. dmesg says this at boot: cd0 at ahc0 bus 0 target 3 lun 0 cd0: YAMAHA CRW4416S 1.0f Removable CD-ROM SCSI-2 device cd0: 8.333MB/s transfers (8.333MHz, offset 31) cd0: cd present [0 x 2048 byte records] Camcontrol says this: # camcontrol cmd cd0 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 -1 2048 All I can say is that it appears that something is wrong with the drive. We're just reporting what it reports back as far as capacity, and the fact that it complains about a block being out of range just confirms that it has bogus capacity information internally. Ken -- Kenneth Merry [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
interrupt trouble with SIS645DX based notebook
Hello, i have heavy trouble getting _ANY_ *bsd or linux working on my notebook. In fact every installation attempt failed so far but only FreeBSD 5.1 was able to boot on this box (really i tried openbsd 3.3, netbsd 1.6.1, freebsd 4.8, knoppix 3.2, all crash when trying to access the cd-rom drive, only freebsd is smart enuff to get it to work using PIO4). I have installed it and it runs fine so far. Only 2 things are not working: the Cisco MiniPCI 350 wlan card (crashes when activating the interface) and the SIS7012 ac'97 sound (crashes when i load the module and try to play something). After days of experimenting around i found out that no miniPCI wlan card works and just causes a systemcrash when trying to activate it. I found out too that, when no MiniPCI card is installed, the sound works perfectly. In /var/log/messages i often get a message 'stray interrupt 7'. I tryed several kernels, tryed to load the Cisco driver as modules instead on compiling into the kernel, really have hours of messing-around-with-kernel-config, and nothing worked :( Its a Elitegroup G732 based Notebook (sold as Gericom Masterpiece, Vobis M9 ...), featuring the SIS645DX chipset, mobile Radeon 9000 ... Im really trying hard to get rid of windows :/ So if you have any hints for me, please post ... notebook without wlan sound isnt any fun ... thanks in advance. ACPI debug layer 0x0 debug level 0x0 Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Fri Jun 20 17:05:21 GMT 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYONE_NEW_13 Preloaded elf kernel /boot/kernel/kernel at 0xc051b000. Calibrating clock(s) ... i8254 clock: 1193124 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz Calibrating TSC clock ... TSC clock: 2141106812 Hz Timecounter TSC frequency 2141106812 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2141.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 534708224 (509 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00542000 - 0x1f4d2fff, 519639040 bytes (126865 pages) avail memory = 513798144 (489 MB) bios32: Found BIOS32 Service Directory header at 0xc00f69c0 bios32: Entry = 0xfd880 (c00fd880) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd880+0x138 pnpbios: Found PnP BIOS data at 0xc00f6a20 pnpbios: Entry = f:a964 Rev = 1.0 Other BIOS signatures found: wlan: 802.11 Link Layer null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 01 00 00 00 22 00 00 01 00 04 00 01 19 01 00 01 2f 01 00 01 34 01 00 01 82 01 0d 01 0e 01 0f 01 20 01 92 01 93 01 94 01 95 01 96 01 a2 01 a3 01 a4 01 a5 01 a6 01 VESA: 55 mode(s) found VESA: v2.0, 65536k memory, flags:0x1, mode table:0xc0484c22 (122) VESA: ATI MOBILITY RADEON 9000 VESA: ATI Technologies Inc. M9 01.00 acpi0: PTLTDRSDT on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x80010014 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=06461039) pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00fdf40 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs slot 1 05A 0x43 3 4 5 9 10 11 15 slot 1 05B 0x44 3 4 5 9 10 11 15 slot 2 06A 0x44 3 4 5 9 10 11 15 embedded0 10A 0x42 3 4 5 6 7 9 10 11 12 14 15 embedded01A 0x41 3 4 5 6 9 10 11 15 embedded01B 0x42 3 4 5 6 9 10 11 15 embedded02A 0x41 3 4 5 9 10 11 15 embedded02B 0x42 3 4 5 9 10 11 15 embedded02C 0x43 3 4 5 9 10 11 15 embedded02D 0x44 3 4 5 9 10 11 15 embedded03A 0x60 3 4 5 9 10 11 15 embedded03B 0x61 3 4 5 9 10 11 15 embedded03C 0x62 3 4 5 9 10 11 15 embedded03D 0x63 3 4 5 9 10 11 15 embedded04A 0x44 3 4 5 9 10 11 15 AcpiOsDerivePciId: bus 0 dev 2 func 0 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 4, width = 2 Timecounter ACPI-fast frequency
Re: Recent getty(8) changes clobbers w(1)
On Thu, Jun 19, 2003 at 03:20:28PM +0200, Morten Rodal wrote: After the recent getty(8) changes w(1) will now show root logins on the same ttys if you use su(1). However, after logging out the root user is not removed from the w(1) (or who(1) for that matter). Example output from w(1) where tty p0 and p4 have been used to login with root, and currently logged out while p2 is still logged in. [atlantis] ~ w 3:17pm up 5:44, 8 users, load averages: 0,02 0,15 0,31 USER TTY FROM LOGIN@ IDLE WHAT root p0 - 9:40am - vi root p2 - 3:11pm 2 -su (csh) root p4 - 3:14pm - w morten p0 :0.0 3:10pm - vi morten p1 :0.0 9:46am 2 irssi morten p2 :0.0 3:10pm 2 -su (csh) morten p3 :0.0 3:10pm 6 ssh slimy morten p4 :0.0 3:11pm - w As far as I know this started after the getty(8) changes, but it could be some other changes as while. Am I the only one seeing this? Thanks for reporting this, but I've been unable to reproduce the problem. Moreover, getty(8) is neither responsible for updating utmp(5) nor used on pseudo terminals, so my recent changes to getty(8) could hardly introduce the problem you were observing. A possible reason for it might be that your utmp(5) file got broken in some way. -- Yar ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent getty(8) changes clobbers w(1)
On Mon, Jun 23, 2003 at 18:46:00 +0400, Yar Tikhiy wrote: On Thu, Jun 19, 2003 at 03:20:28PM +0200, Morten Rodal wrote: After the recent getty(8) changes w(1) will now show root logins on the same ttys if you use su(1). However, after logging out the root user is not removed from the w(1) (or who(1) for that matter). Example output from w(1) where tty p0 and p4 have been used to login with root, and currently logged out while p2 is still logged in. [atlantis] ~ w 3:17pm up 5:44, 8 users, load averages: 0,02 0,15 0,31 USER TTY FROM LOGIN@ IDLE WHAT root p0 - 9:40am - vi root p2 - 3:11pm 2 -su (csh) root p4 - 3:14pm - w morten p0 :0.0 3:10pm - vi morten p1 :0.0 9:46am 2 irssi morten p2 :0.0 3:10pm 2 -su (csh) morten p3 :0.0 3:10pm 6 ssh slimy morten p4 :0.0 3:11pm - w As far as I know this started after the getty(8) changes, but it could be some other changes as while. Am I the only one seeing this? Thanks for reporting this, but I've been unable to reproduce the problem. Moreover, getty(8) is neither responsible for updating utmp(5) nor used on pseudo terminals, so my recent changes to getty(8) could hardly introduce the problem you were observing. A possible reason for it might be that your utmp(5) file got broken in some way. It can be some su problem too, I saw similar reports. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems on Samsung Q10 (AE_AML_NO_RETURN_VALUE /AE_BAD_PARAMETER)
Hi! I applied the patch from http://docs.freebsd.org/cgi/getmsg.cgi?fetch=214877+0+archive/2003/freebsd-current/20030615.freebsd-current and the AE_BAD_PARAEMTER error disappers. Hendrik -- Hendrik Scholz - [EMAIL PROTECTED] - http://raisdorf.net/ Forcast for tonight: Dark. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
Eirik Oeverby wrote: [...] And with ACPI disabled, the machine refuses totally to boot, it hangs at 'Mounting root from ...'. If I undock the machine, I can boot with and without ACPI, with the latter option being the only usable (stable) mode. Just out of curiosity, have you tried setting hw.pci.allow_unsupported_io_range=1 in your /boot/device.hints file? I've found that this option fixes many unbootable laptops - especially thinkpads. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SCSI CD mount problems
On Mon, Jun 23, 2003 at 08:31:20AM -0600, Kenneth D. Merry wrote: On Mon, Jun 23, 2003 at 09:50:39 -0400, Guy Middleton wrote: This was actually a FreeBSD ISO distribution disk. It does this for every disk; the only time I could successfully mount a disk was with one I had just written on that drive. If I then opened and closed the drive, I could not mount the disk. I assume you can put the disks in other drives and they work fine? Yes, no problem reading them in the IDE drive. -1 2048 All I can say is that it appears that something is wrong with the drive. We're just reporting what it reports back as far as capacity, and the fact that it complains about a block being out of range just confirms that it has bogus capacity information internally. Well, that's annoying. I assumed that the drive was ok, since it could write correctly. I guess I better go shopping for a new one. :-) -Guy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compaq N610c ACPI
Ok i've been a morron... updated the wrong web site with the dmesg and ACPI code... The code is located at: http://www.guldan.cistron.nl/dmesg_output.txt http://www.guldan.cistron.nl/n610c_2.dsl Robert On Thu, Jun 19, 2003 at 09:42:00PM +0200, Robert Blacquière wrote: Hi, I've a ComPaq n610c with FreeBSD 5.1-Current running. With the latest bios/RomPaq i was able to install Current/5.1-Release. Previous RomPaq was completely broken for ACPI. But now is more or less works. I have still some problems with acpi and without acpi. With acpi i got some warnings and short/mid freezes during boot and sysctl -A. I've already did some digging in ACPI asl/aml code but can't do the tricks like removing a simple * from the Name (_HID, *PNPsomething) . Has any one any good leads to help or docs without having to spend 2 years of college? I've made a dmesg and a ACPI dump available at: http://www.guldan.demon.nl/dmesg_output.txt http://www.guldan.demon.nl/n610c_2.dsl Booting 5.1 Current without acpi leaves this machine totally broken devices can't be found and drivers seem to locate the cardbus controller multiple times. Having up to 17 cardbus adaptors reported in my system... mmmhh Sounds cool ;-) Robert PS: Compaq released this week a new RomPaq for this machine F.14 A -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: He guys you left some holes out there! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: He guys you left some holes out there! pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
On Mon, 23 Jun 2003 10:53:32 -0400 Jesse Guardiani [EMAIL PROTECTED] wrote: And with ACPI disabled, the machine refuses totally to boot, it hangs at 'Mounting root from ...'. If I undock the machine, I can boot with and without ACPI, with the latter option being the only usable (stable) mode. Just out of curiosity, have you tried setting hw.pci.allow_unsupported_io_range=1 in your /boot/device.hints file? I've found that this option fixes many unbootable laptops - especially thinkpads. Hmm.. Yes, I think I have. Atleast it's in my device.hints file now - however I don't know if I tried docking it and booting without ACPI after I put that line in.. Perhaps I should try again, but my gut feeling tells me it's not gonna make any difference. Atleast as long as its undocked it had no effect on any of the other problems I'm experiencing. /Eirik pgp0.pgp Description: PGP signature
Re: Problem with wi in CURRENT (and 5.1)
On Tue, Jun 17, 2003 at 11:48:13AM +0100, Robert Hulme wrote: I'm having some problems with wi in 5-CURRENT and 5.1 in general. I'm using a Proxim Skyline 802.11b PC Card (which I believe uses the Prism 2 chipset). The PC Card is using the 0.3.0 primary and 0.8.3 secondary firmware (which I believe is the latest). I have a Dell Inspiron 8200. The card works fine in Windows XP and FreeBSD 5.0, but in 5.1 if I use ifconfig to bring up the card (for example during boot) it locks my laptop up for about a minute while I get loads of error messages appear on screen. Eventually I get a 'init failed' and 'tx buffer allocation failed (error 12)' error, and although ifconfig says the interface is up it doesn't actually work. See if there isn't updated firmware for your card. Rumor has it the MS-Windows driver uploads the latest firmware version into the RAM on the card. For Lucent cards you want any versoin 8 firmware from http://www.expressresponse.com/cgi-bin/proxim02/showFaq.cgi?session_id=1055265419.6837.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with wi in CURRENT (and 5.1)
Hi, this is exactly the problem I have with my wi-driven card aswell. I have a pretty standard Lucent card (Orinoco Silver, 64bit), PCMCIA, in my ThinkPad T21 (see another thread specifically about that machine and its issues with 5.1). It will work for a while, then start spitting out error messages like wi0: bad alloc 55c != 2a2, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 573 != 2a2, cur 0 nxt 0 wi0: device timeout and wi0: timeout in wi_seek to fc02/0 wi0: timeout in wi_seek to fc03/0 and ofcourse the messages you describe. Pulling the card out and re-inserting it, then ifconfig, brings it back to life for a few minutes or as much as half an hour or so. At first I thought it was a signal level problem, but it's not. I also thought it's an encryption problem, but that's not it either. So I'm really confused - it worked perfectly for weeks on end with 4.8, and now in 5.1/CURRENT it screws me over like this. Firmware is at the latest level. Just my two cents to confirm your story ;) /Eirik On Mon, 23 Jun 2003 09:26:11 -0700 David O'Brien [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2003 at 11:48:13AM +0100, Robert Hulme wrote: I'm having some problems with wi in 5-CURRENT and 5.1 in general. I'm using a Proxim Skyline 802.11b PC Card (which I believe uses the Prism 2 chipset). The PC Card is using the 0.3.0 primary and 0.8.3 secondary firmware (which I believe is the latest). I have a Dell Inspiron 8200. The card works fine in Windows XP and FreeBSD 5.0, but in 5.1 if I use ifconfig to bring up the card (for example during boot) it locks my laptop up for about a minute while I get loads of error messages appear on screen. Eventually I get a 'init failed' and 'tx buffer allocation failed (error 12)' error, and although ifconfig says the interface is up it doesn't actually work. See if there isn't updated firmware for your card. Rumor has it the MS-Windows driver uploads the latest firmware version into the RAM on the card. For Lucent cards you want any versoin 8 firmware from http://www.expressresponse.com/cgi-bin/proxim02/showFaq.cgi?session_id=1055265419.6837.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: audigy 2
Yuriy, Yuriy Tsibizov wrote: Unfortunately your driver isn't very committable -- unfortunately you took it upon himself to totally reformat our emu10k1.c file in addition to embellishing it. So it is impossible to see what changes you really made to the driver. I don't suppose you've got a patch with the minimal number of changes to support audigy and audigy2? Old driver (emu10k1.c) was too big for me to work on it and was difficult to add MIDI support. I know that my driver will never go into the tree - sound@ decided to use Orlando Bassotto's work. His driver is much closer to original emu10k1.c that mine. that is a pity, I'd really like to see Audigy support in the tree. People create patches all the time and maintain them separately for some time, but the eventual goal should be inclusion in the main tree. Juggling a number of third-party patches when building a kernel is a pain (even though I understand the Linux folks do this a lot.) You would make many of us happy if your patch could be made committable. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: acpi patch for dell laptop?
On Mon, Jun 23, 2003 at 08:52:20 +0200, Stijn Hoop wrote: On Sun, Jun 22, 2003 at 09:35:32PM -0600, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. It seems to work for me. The ACPI warnings about zero length buffers go away at least. Great. Do you also have working battery status now? How do I figure that out? Via the ACPI sysctls, or some other method? When I unplug the power: - hw.acpi.battery.state goes from 0 - 1 - hw.acpi.battery.time goes from 0 to 152 - hw.acpi.battery.life starts to go down Is there some tool that'll show battery info? Also, what units are the temperature in? Ken -- Kenneth Merry [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
On Mon, Jun 23, 2003 at 11:03:34AM -0600, Kenneth D. Merry wrote: On Mon, Jun 23, 2003 at 08:52:20 +0200, Stijn Hoop wrote: On Sun, Jun 22, 2003 at 09:35:32PM -0600, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: http://sandcat.nl/~stijn/freebsd/dell.php It seems to work for me. The ACPI warnings about zero length buffers go away at least. Great. Do you also have working battery status now? How do I figure that out? Via the ACPI sysctls, or some other method? ACPI sysctls was the method that didn't work without the patch on my Inspiron. When I unplug the power: - hw.acpi.battery.state goes from 0 - 1 - hw.acpi.battery.time goes from 0 to 152 - hw.acpi.battery.life starts to go down That looks like correct behaviour. The battery time can't be determined when on AC power. Is there some tool that'll show battery info? I don't know of one that uses the ACPI sysctls, maybe someone else? Also, what units are the temperature in? 1/10 Kelvin I've been led to believe. HTH, --Stijn -- My server has more fans than Britney. -- Steve Warwick, from a posting at [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
I am modifying and improving a kernel module to work with the dell i8500 so you can have access to the battery, temp, fan info true the sysctl ioctl.. it's now working in 2day i well send info about this. or look at my web page www.x123.info sysctl hw.dell hw.dell.fan_restricted: 0 hw.dell.handle_buttons: 0 hw.dell.repeat_delay: 250 hw.dell.repeat_rate: 10 hw.dell.service_tag: BFT8Q0J hw.dell.power_status: 0 hw.dell.left_fan.status: low hw.dell.left_fan.rpm: 102450 hw.dell.right_fan.status: low hw.dell.right_fan.rpm: 141840 hw.dell.cpu_temp: 47 On Monday 23 June 2003 17:03, Kenneth D. Merry wrote: On Mon, Jun 23, 2003 at 08:52:20 +0200, Stijn Hoop wrote: On Sun, Jun 22, 2003 at 09:35:32PM -0600, Kenneth D. Merry wrote: On Sat, Jun 21, 2003 at 00:13:10 +0200, Stijn Hoop wrote: On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: Where can I find the latest, greatest patch that fixes this? Try this URL: http://sandcat.nl/~stijn/freebsd/dell.php and let me know if it works. It seems to work for me. The ACPI warnings about zero length buffers go away at least. Great. Do you also have working battery status now? How do I figure that out? Via the ACPI sysctls, or some other method? When I unplug the power: - hw.acpi.battery.state goes from 0 - 1 - hw.acpi.battery.time goes from 0 to 152 - hw.acpi.battery.life starts to go down Is there some tool that'll show battery info? Also, what units are the temperature in? Ken -- /* FingerPrint: 5BF1 58B1 DE75 CBE3 6044 7098 1246 1EF6 9E78 041C @@@ @@ @@@ @@! @@@ !@@ @@! @@@ @[EMAIL PROTECTED]@!@ !@@!! @!@ [EMAIL PROTECTED] !!: !!! !:! !!: !!! :: : :: ::.: : :: : : The Power To Kill LinuX */ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem with wi in CURRENT (and 5.1)
I am already running the latest firmware, and it works in 5.0 but not in 5.1 or 5-CURRENT. Is anyone going to take a look at this? It seems that wi is broken for a significant number of people (there have been several emails like mine recently to current and mobile) in 5.1+ -Rob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David O'Brien Sent: 23 June 2003 17:26 To: Robert Hulme Cc: [EMAIL PROTECTED] On Tue, Jun 17, 2003 at 11:48:13AM +0100, Robert Hulme wrote: I'm having some problems with wi in 5-CURRENT and 5.1 in general. I'm using a Proxim Skyline 802.11b PC Card (which I believe uses the Prism 2 chipset). The PC Card is using the 0.3.0 primary and 0.8.3 secondary firmware (which I believe is the latest). I have a Dell Inspiron 8200. The card works fine in Windows XP and FreeBSD 5.0, but in 5.1 if I use ifconfig to bring up the card (for example during boot) it locks my laptop up for about a minute while I get loads of error messages appear on screen. Eventually I get a 'init failed' and 'tx buffer allocation failed (error 12)' error, and although ifconfig says the interface is up it doesn't actually work. See if there isn't updated firmware for your card. Rumor has it the MS-Windows driver uploads the latest firmware version into the RAM on the card. For Lucent cards you want any versoin 8 firmware from http://www.expressresponse.com/cgi-bin/proxim02/showFaq.cgi?se ssion_id=1055265419.6837.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem with wi in CURRENT (and 5.1)
Thanks for the support :-D Pulling the card out, reinserting it and doing ifconfig sadly doesn't help me :( -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eirik Oeverby Sent: 23 June 2003 17:42 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Hi, this is exactly the problem I have with my wi-driven card aswell. I have a pretty standard Lucent card (Orinoco Silver, 64bit), PCMCIA, in my ThinkPad T21 (see another thread specifically about that machine and its issues with 5.1). It will work for a while, then start spitting out error messages like wi0: bad alloc 55c != 2a2, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 573 != 2a2, cur 0 nxt 0 wi0: device timeout and wi0: timeout in wi_seek to fc02/0 wi0: timeout in wi_seek to fc03/0 and ofcourse the messages you describe. Pulling the card out and re-inserting it, then ifconfig, brings it back to life for a few minutes or as much as half an hour or so. At first I thought it was a signal level problem, but it's not. I also thought it's an encryption problem, but that's not it either. So I'm really confused - it worked perfectly for weeks on end with 4.8, and now in 5.1/CURRENT it screws me over like this. Firmware is at the latest level. Just my two cents to confirm your story ;) /Eirik On Mon, 23 Jun 2003 09:26:11 -0700 David O'Brien [EMAIL PROTECTED] wrote: On Tue, Jun 17, 2003 at 11:48:13AM +0100, Robert Hulme wrote: I'm having some problems with wi in 5-CURRENT and 5.1 in general. I'm using a Proxim Skyline 802.11b PC Card (which I believe uses the Prism 2 chipset). The PC Card is using the 0.3.0 primary and 0.8.3 secondary firmware (which I believe is the latest). I have a Dell Inspiron 8200. The card works fine in Windows XP and FreeBSD 5.0, but in 5.1 if I use ifconfig to bring up the card (for example during boot) it locks my laptop up for about a minute while I get loads of error messages appear on screen. Eventually I get a 'init failed' and 'tx buffer allocation failed (error 12)' error, and although ifconfig says the interface is up it doesn't actually work. See if there isn't updated firmware for your card. Rumor has it the MS-Windows driver uploads the latest firmware version into the RAM on the card. For Lucent cards you want any versoin 8 firmware from http://www.expressresponse.com/cgi-bin/proxim02/showFaq.cgi?session_id =1055265419.6837.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
Eirik Oeverby wrote: On Mon, 23 Jun 2003 10:53:32 -0400 Jesse Guardiani [EMAIL PROTECTED] wrote: And with ACPI disabled, the machine refuses totally to boot, it hangs at 'Mounting root from ...'. If I undock the machine, I can boot with and without ACPI, with the latter option being the only usable (stable) mode. Just out of curiosity, have you tried setting hw.pci.allow_unsupported_io_range=1 in your /boot/device.hints file? I've found that this option fixes many unbootable laptops - especially thinkpads. Hmm.. Yes, I think I have. Atleast it's in my device.hints file now - however I don't know if I tried docking it and booting without ACPI after I put that line in.. Perhaps I should try again, but my gut feeling tells me it's not gonna make any difference. Atleast as long as its undocked it had no effect on any of the other problems I'm experiencing. Try again and let me know. /Eirik -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
make.conf and MASTER_SITE_BACKUP
Hi, Had a quick search around mail archives and problem reports. Did spot anything, but it seems MASTER_SITE_BACKUP?= MASTER_SITE_OVERRIDE?= work in make.conf for 5 however make.conf(5) doesn't seem to mention it? Is this a feature? -byron ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf and MASTER_SITE_BACKUP
On 2003.06.23 19:42:25 +0200, Byron Schlemmer wrote: Had a quick search around mail archives and problem reports. Did spot anything, but it seems MASTER_SITE_BACKUP?= MASTER_SITE_OVERRIDE?= work in make.conf for 5 however make.conf(5) doesn't seem to mention it? Is this a feature? Partly. They are described in ports(7), which is referenced from make.conf(5). -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: audigy 2
Yuriy Tsibizov wrote: Old driver (emu10k1.c) was too big for me to work on it and was difficult to add MIDI support. I know that my driver will never go into the tree - sound@ decided to use Orlando Bassotto's work. His driver is much closer to original emu10k1.c that mine. How about making a 'emu10k2' driver for just audigy 2.. and leaving the current 'emu10k1' alone? -- The more we disagree, the more chance there is that at least one of us is right. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cardbus and xircom ethernet problem
M. Warner Losh wrote: I've seen this with a few cards that I have here. I'm not sure what causes it, and haven't had time to look into it deeply. You might try OLDCARD to see if that helps. Warner I have just recompiled it with the OLDCARD parameters and now it shows more promising signs. However it still doesn't work :( I now get on inserting the card: holly kernel: pccard: card inserted, slot0 holly pccardd[172]: Card Xircom(CreditCard Ethernet 10/100 + Modem 56) [CEM56] [1.00] matched Xircom (CreditCard Ethernet 10/100 + Modem 56) [null] [null] holly pccard[172]: driver allocation failed for Xircom(CreditCard Ethernet 10/100 + Modem 56): Device not configured Though this is obviously a lot better looking than using NEWCARD which causes those CIS errors. My kernel config currently has: nodevicecbb nodevicepccard nodevicecardbus device card 2 device pcic device xe The OLDCARD file actually does not have a number after device card, however I found when trying to compile this it errors with Device card requires a count. I am unsure of what the count means so just put a random number in there. Anything else I can try? Regards, Matt. -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cardbus and xircom ethernet problem
-Original Message- From: Matt [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 2:22 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: cardbus and xircom ethernet problem My kernel config currently has: nodevicecbb nodevicepccard nodevicecardbus device card 2 device pcic device xe The OLDCARD file actually does not have a number after device card, however I found when trying to compile this it errors with Device card requires a count. I am unsure of what the count means so just put a random number in there. Anything else I can try? Do try loading if_dc.ko or compiling that in again. -Will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: cardbus and xircom ethernet problem
Will Saxon said: Do try loading if_dc.ko or compiling that in again. -Will Sorry yeah I have already added dc and various other's that I have seen could belong to these xircom cards. It hasn't made a difference. I actually believe it is xe though as when I remove the card it says this: holly pccard[172]: xe-1: Xircom (CreditCard Ethernet 10/100 + Modem 56) removed. The xe-1 part suggests xe driver I guess? Matt. -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI Patch/DSDT .asl for Dell Inspiron 5000
Thanks for your patch submission. I looked into it and found a few
problems. Attached is a patch based on yours that should be equivalent
but fixes a few problems:
* Don't call msleep if event has already occurred
* Don't read CSR twice if not necessary (also fixed in EcEventWait)
* Unused loop variable removed
And same as yours:
* 1 us wait added before first EC_STATUS read
* A single call of msleep with 10 ms timeout is now used
Please try the patch and see if it works for you.
-NateIndex: acpi_ec.c
===
RCS file: /home/ncvs/src/sys/dev/acpica/acpi_ec.c,v
retrieving revision 1.29
diff -u -r1.29 acpi_ec.c
--- acpi_ec.c 27 Nov 2002 18:09:20 - 1.29
+++ acpi_ec.c 23 Jun 2003 18:46:00 -
@@ -616,7 +616,6 @@
EcWaitEventIntr(struct acpi_ec_softc *sc, EC_EVENT Event)
{
EC_STATUS EcStatus;
-inti;
ACPI_FUNCTION_TRACE_U32((char *)(uintptr_t)__func__, (UINT32)Event);
@@ -628,28 +627,33 @@
ACPI_VPRINT(sc-ec_dev, acpi_device_get_parent_softc(sc-ec_dev),
EcWaitEventIntr called without EC lock!\n);
+/*
+ * Stall for 1 microsecond before reading the status register
+ * for the first time. This allows the EC to set the IBF/OBF
+ * bit to its proper state.
+ */
+AcpiOsStall(1);
EcStatus = EC_GET_CSR(sc);
+if ((Event == EC_EVENT_OUTPUT_BUFFER_FULL
+ (EcStatus EC_FLAG_OUTPUT_BUFFER) != 0) ||
+ (Event == EC_EVENT_INPUT_BUFFER_EMPTY
+ (EcStatus EC_FLAG_INPUT_BUFFER) == 0))
+ return(AE_OK);
-/* XXX waiting too long? */
-for(i = 0; i 10; i++){
- /*
-* Check EC status against the desired event.
-*/
- if ((Event == EC_EVENT_OUTPUT_BUFFER_FULL)
- (EcStatus EC_FLAG_OUTPUT_BUFFER))
- return_ACPI_STATUS(AE_OK);
-
- if ((Event == EC_EVENT_INPUT_BUFFER_EMPTY)
- !(EcStatus EC_FLAG_INPUT_BUFFER))
- return_ACPI_STATUS(AE_OK);
-
- sc-ec_csrvalue = 0;
- if (ACPI_MSLEEP(sc-ec_csrvalue, acpi_mutex, PZERO, EcWait, 1) !=
EWOULDBLOCK){
- EcStatus = sc-ec_csrvalue;
- }else{
- EcStatus = EC_GET_CSR(sc);
- }
+/* Wait up to 10ms for the EC status to indicate completion. */
+sc-ec_csrvalue = 0;
+if (ACPI_MSLEEP(sc-ec_csrvalue, acpi_mutex, PZERO, EcWait, hz / 100)
+!= EWOULDBLOCK) {
+ EcStatus = sc-ec_csrvalue;
+} else {
+ EcStatus = EC_GET_CSR(sc);
}
+if ((Event == EC_EVENT_OUTPUT_BUFFER_FULL
+ (EcStatus EC_FLAG_OUTPUT_BUFFER) != 0) ||
+ (Event == EC_EVENT_INPUT_BUFFER_EMPTY
+ (EcStatus EC_FLAG_INPUT_BUFFER) == 0))
+ return(AE_OK);
+
return_ACPI_STATUS(AE_ERROR);
}
@@ -669,11 +673,8 @@
* Stall for 1 microsecond before reading the status register
* for the first time. This allows the EC to set the IBF/OBF
* bit to its proper state.
- *
- * XXX it is not clear why we read the CSR twice.
*/
AcpiOsStall(1);
-EcStatus = EC_GET_CSR(sc);
/*
* Wait For Event:
@@ -684,13 +685,11 @@
for (i = 0; i 1000; i++) {
EcStatus = EC_GET_CSR(sc);
-if ((Event == EC_EVENT_OUTPUT_BUFFER_FULL)
-(EcStatus EC_FLAG_OUTPUT_BUFFER))
- return(AE_OK);
-
- if ((Event == EC_EVENT_INPUT_BUFFER_EMPTY)
-!(EcStatus EC_FLAG_INPUT_BUFFER))
- return(AE_OK);
+ if ((Event == EC_EVENT_OUTPUT_BUFFER_FULL
+ (EcStatus EC_FLAG_OUTPUT_BUFFER) != 0) ||
+ (Event == EC_EVENT_INPUT_BUFFER_EMPTY
+ (EcStatus EC_FLAG_INPUT_BUFFER) == 0))
+ return(AE_OK);
AcpiOsStall(10);
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cardbus and xircom ethernet problem
On Mon, Jun 23, 2003 at 07:31:09PM +0100, Matt wrote: Will Saxon said: Do try loading if_dc.ko or compiling that in again. -Will Sorry yeah I have already added dc and various other's that I have seen could belong to these xircom cards. It hasn't made a difference. I actually believe it is xe though as when I remove the card it says this: holly pccard[172]: xe-1: Xircom (CreditCard Ethernet 10/100 + Modem 56) removed. The xe-1 part suggests xe driver I guess? Matt. Yes, all the 16-bit Xircom Ethernet cards are handled (for some definition of handled) by the xe driver. Their 32-bit (Cardbus) products used very different hardware that is understood by the dc driver. As for your card, it looks like some resource required by the driver isn't being allocated. Try booting in verbose mode (boot -v) again -- I think that turns on the right debug output in the pccard driver. Full 'dmesg' output would also be useful (I realise you have no network on this machine yet - can you maybe put it on a floppy and mail it from another machine?) Scott -- === Scott Mitchell | PGP Key ID | Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines scott at fishballoon.org | 0xAA775B8B | -- Anon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
Speaking about ACPI, has anyone figured out how to close the lid without suspending? I remember before, when the lid was closed, it would suspend even with sysctl set to not suspend and the screen stays on and when you resume, you can type but the screen freezes and doesn't update. This is on a Inspiron 8200. I can't test the new patch for a few days as my original HD running March 8, 2003 -CURRENT died on April 7, 2003 and it seems the drive has problems reading/writing as it timeouts but I can get /etc only so I'm going to rebuild the system. Cheers, Vince - [EMAIL PROTECTED] - Vice President __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] [EMAIL PROTECTED] - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
Hi again, No workie. No difference in behaviour whatsoever. Sorry :( /Eirik On Mon, 23 Jun 2003 13:43:14 -0400 Jesse Guardiani [EMAIL PROTECTED] wrote: Eirik Oeverby wrote: On Mon, 23 Jun 2003 10:53:32 -0400 Jesse Guardiani [EMAIL PROTECTED] wrote: And with ACPI disabled, the machine refuses totally to boot, it hangs at 'Mounting root from ...'. If I undock the machine, I can boot with and without ACPI, with the latter option being the only usable (stable) mode. Just out of curiosity, have you tried setting hw.pci.allow_unsupported_io_range=1 in your /boot/device.hints file? I've found that this option fixes many unbootable laptops - especially thinkpads. Hmm.. Yes, I think I have. Atleast it's in my device.hints file now - however I don't know if I tried docking it and booting without ACPI after I put that line in.. Perhaps I should try again, but my gut feeling tells me it's not gonna make any difference. Atleast as long as its undocked it had no effect on any of the other problems I'm experiencing. Try again and let me know. /Eirik -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
Crap. I just saw that I had no quotes around the '1'. Will it still get that setting, or do I have to change it and try again? (My line says hw.pci.allow_unsupported_io_range=1 while I believe (according to the other examples in the file) it should say hw.pci.allow_unsupported_io_range=1 . Does this make a difference?) /Eirik On Mon, 23 Jun 2003 22:40:40 +0200 Eirik Oeverby [EMAIL PROTECTED] wrote: Hi again, No workie. No difference in behaviour whatsoever. Sorry :( /Eirik On Mon, 23 Jun 2003 13:43:14 -0400 Jesse Guardiani [EMAIL PROTECTED] wrote: Eirik Oeverby wrote: On Mon, 23 Jun 2003 10:53:32 -0400 Jesse Guardiani [EMAIL PROTECTED] wrote: And with ACPI disabled, the machine refuses totally to boot, it hangs at 'Mounting root from ...'. If I undock the machine, I can boot with and without ACPI, with the latter option being the only usable (stable) mode. Just out of curiosity, have you tried setting hw.pci.allow_unsupported_io_range=1 in your /boot/device.hints file? I've found that this option fixes many unbootable laptops - especially thinkpads. Hmm.. Yes, I think I have. Atleast it's in my device.hints file now- however I don't know if I tried docking it and booting without ACPI after I put that line in.. Perhaps I should try again, but my gut feeling tells me it's not gonna make any difference. Atleast as long as its undocked it had no effect on any of the other problems I'm experiencing. Try again and let me know. /Eirik -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem with wi in CURRENT (and 5.1)
Hi. On Mon, Jun 23, 2003 at 06:34:00PM +0100, Robert Hulme wrote: I am already running the latest firmware, and it works in 5.0 but not in 5.1 or 5-CURRENT. Is anyone going to take a look at this? It seems that wi is broken for a significant number of people (there have been several emails like mine recently to current and mobile) in 5.1+ Most messages and all of the problems go away, when I use WITNESS in the Kernel. This seems to be a timing issue. Do you have WITNESS turned on or turned off in the Kernel? If it is not set, could you add options WITNESS to your kernel config and check if the problem is still there? - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-CURRENT hangs on disk i/o? sysctl_old_user() non-sleepablelocks
Don Lewis [EMAIL PROTECTED] writes: Try the very untested patch below ... Well, it seems to be working now, but not necessarily due to this patch. I lost two of the four drives on my ATA RAID card (RAID-5) so lost my entire system :-(. Rebuilt the box from the 5.0-RELEASE floppies/net then cvsupped to 5.1-CURRENT. Reinstalled all the stuff like qmail and apache. I'm no longer seeing the unlocked messages in the logs any longer. Thanks for all your help! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
lock order reversal under recent -CURRENT
Hi, under a recent -CURRENT I get this: --- lock order reversal 1st 0xc2e475c8 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:432 2nd 0xc082f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:328 Stack backtrace: backtrace(c03c9d09,c082f110,c03d8851,c03d8851,c03d86ec) at backtrace+0x17 witness_lock(c082f110,8,c03d86ec,148,0) at witness_lock+0x697 _mtx_lock_flags(c082f110,0,c03d86ec,148,3) at _mtx_lock_flags+0xb1 _vm_map_lock(c082f0b0,c03d86ec,148,d26e3a54,c0247ce4) at _vm_map_lock+0x36 kmem_malloc(c082f0b0,1000,101,d26e3ac0,c03586e0) at kmem_malloc+0x66 page_alloc(c083a240,1000,d26e3ab3,101,c041066c) at page_alloc+0x27 slab_zalloc(c083a240,101,c03da0b0,66e,c26c56e4) at slab_zalloc+0x150 uma_zone_slab(c083a240,101,c03da0b0,66e,0) at uma_zone_slab+0xd8 uma_zalloc_internal(c083a240,0,101,6ee,0) at uma_zalloc_internal+0x55 uma_zfree_arg(c26c56c0,d1db6bdc,0,1,0) at uma_zfree_arg+0x2cb swp_pager_meta_free_all(c2e475c8,c03d8044,c03d7fd8,1b2) at swp_pager_meta_free_all+0x1b0 swap_pager_dealloc(c2e475c8,1,c03d9fb3,10c,0) at swap_pager_dealloc+0x113 vm_pager_deallocate(c2e475c8,0,c03d9189,25f,0) at vm_pager_deallocate+0x3d vm_object_terminate(c2e475c8,0,c03d9189,1b0,c02388e0) at vm_object_terminate+0x1f4 vm_object_deallocate(c2e475c8,c2da999c,c2e475c8,c2da999c,d26e3c64) at vm_object_deallocate+0x377 vm_map_entry_delete(c2dad800,c2da999c,c03d88bf,86d,c03c54da) at vm_map_entry_delete+0x3b vm_map_delete(c2dad800,0,bfc0,c2dad800,c26b7400) at vm_map_delete+0x413 vm_map_remove(c2dad800,0,bfc0,11d,c03c4a8b) at vm_map_remove+0x58 exit1(c2c8c980,0,c03c4a8b,65,d26e3d40) at exit1+0x696 sys_exit(c2c8c980,d26e3d10,c03dd56d,3fd,1) at sys_exit+0x41 syscall(2f,2f,2f,0,e34) at syscall+0x26e Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip = 0x2851d44f, esp = 0xbfbff840, ebp = 0xbfbff86c --- - `uname -a` says: - FreeBSD nemesis.bsd-network.org 5.1-CURRENT FreeBSD 5.1-CURRENT #3: Mon Jun 23 00:30:36 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEMESIS i386 - The LOR happens at normal work under X. A few xterm, mozilla, gimp and gqview. Not very wild things. best regards, Gordon -- There is no place like 127.0.0.1/8! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
transferring data (after losing all non-root logins)
I recently forgot my root password, rebooted single-user and changed it, and immediately afterwards the computer denied the existence of any non-root users (home directories still there for those that had them, they still have login shells, etc.). This was the only change made to the system. This is a -current system from late April that was in storage for a while. I was planning on wiping this system to install 5.1-R anyway, but I need to back up the data first. I can't burn a CD because I didn't have mkisofs installed and can't install it (no man user), I can't run sshd (no ssh user), and I can't figure out how to make telnet allow root logins (I know, a Very Bad Idea(tm) usually, but it's not a security issue when I'm allowing it from one IP for 5 minutes and will be changing passwords anyway). So... I'm think of trying to find another hard drive, to install that and transfer the data. Does anyone have any other ideas? Thanks, -David (please cc:) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: transferring data (after losing all non-root logins)
I recently forgot my root password, rebooted single-user and changed it, and immediately afterwards the computer denied the existence of any non-root users (home directories still there for those that had them, they still have login shells, etc.). This was the only change made to the system. This is a -current system from late April that was in storage for a while. I was planning on wiping this system to install 5.1-R anyway, but I need to back up the data first. I can't burn a CD because I didn't have mkisofs installed and can't install it (no man user), I can't run sshd (no ssh user), and I can't figure out how to make telnet allow root logins (I know, a Very Bad Idea(tm) usually, but it's not a security issue when I'm allowing it from one IP for 5 minutes and will be changing passwords anyway). So... I'm think of trying to find another hard drive, to install that and transfer the data. Does anyone have any other ideas? Well, it really sounds like your password database got got hosed. Does /etc/master.passwd have entries for all of your non-root users? If so, then probably all you need to do is regenerate your password database. The easiest way to do this is run vipw, make some kind of change (and undo the change -- this is just so it thinks the file has been changed) and exit. Your password database will be regenerated. -- Matt Emmerton ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
if_wi patch
hi, this patch adds support for authmode stuff to the if_wi of 5.1-release. regards bruno --- sys/dev/wi/if_wi.c.orig Tue Jun 24 01:35:41 2003 +++ sys/dev/wi/if_wi.c Tue Jun 24 01:43:53 2003 @@ -1117,6 +1117,9 @@ error = copyout(sc-sc_nodename, ireq-i_data, ireq-i_len); break; + case IEEE80211_IOC_AUTHMODE: + ireq-i_val = sc-sc_cnfauthmode; + break; default: error = ieee80211_ioctl(ifp, cmd, data); break; @@ -1146,6 +1149,9 @@ } memcpy(sc-sc_nodename, nodename, IEEE80211_NWID_LEN); sc-sc_nodelen = ireq-i_len; + break; + case IEEE80211_IOC_AUTHMODE: + sc-sc_cnfauthmode = ireq-i_val; break; default: error = ieee80211_ioctl(ifp, cmd, data); ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: transferring data (after losing all non-root logins)
On Mon, 23 Jun 2003, Matthew Emmerton wrote: Well, it really sounds like your password database got got hosed. Does /etc/master.passwd have entries for all of your non-root users? If so, then probably all you need to do is regenerate your password database. The easiest way to do this is run vipw, make some kind of change (and undo the change -- this is just so it thinks the file has been changed) and exit. Your password database will be regenerated. Thanks... better than a workaround, solving the problem is always nice :) All the files, including master.passwd, were fine, which is what puzzled me, but regenerating the password database worked. -David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
LOR in VM (with backtrace)
CURRENT dated June 19;
lock order reversal
1st 0xc45788ac vm object (vm object) @
/a/asami/portbuild/i386/src-client/sys/vm/vm_object.c:1506
2nd 0xc082f110 system map (system map) @
/a/asami/portbuild/i386/src-client/sys/vm/vm_kern.c:328
Debugger(c03f450d,c082f110,c043190e,c043190e,c043178f) at Debugger+0x54
witness_lock(c082f110,8,c043178f,148,d8ca79f8) at witness_lock+0x6ac
_mtx_lock_flags(c082f110,0,c043178f,148,c4496850) at _mtx_lock_flags+0xb1
_vm_map_lock(c082f0b0,c043178f,148,c025dc34,246) at _vm_map_lock+0x36
kmem_malloc(c082f0b0,1000,101,d8ca7a8c,c0390425) at kmem_malloc+0x65
page_alloc(c083a240,1000,d8ca7a7f,101,c0457e2c) at page_alloc+0x27
slab_zalloc(c083a240,101,c04332aa,66e,c414e5c4) at slab_zalloc+0x155
uma_zone_slab(c083a240,101,c04332aa,66e,0) at uma_zone_slab+0xd8
uma_zalloc_internal(c083a240,0,101,6ee,0) at uma_zalloc_internal+0x55
uma_zfree_arg(c414e5a0,d7a86000,0,1,0) at uma_zfree_arg+0x2cc
swp_pager_meta_free(c45788ac,1d,0,1,0) at swp_pager_meta_free+0x1b2
swap_pager_freespace(c45788ac,1d,0,1,0) at swap_pager_freespace+0x57
vm_object_backing_scan(c4bec5c8,4,c0432299,5f7,c0432299) at
vm_object_backing_scan+0x28a
vm_object_collapse(c4bec5c8,0,c0432299,1ef,c45a0ec4) at vm_object_collapse+0x11a
vm_object_deallocate(c4fab940,c5093ce4,c4fab940,c5093ce4,d8ca7c60) at
vm_object_deallocate+0x28e
vm_map_entry_delete(c1506100,c5093ce4,c043197c,86d,c041ada4) at
vm_map_entry_delete+0x3b
vm_map_delete(c1506100,0,bfc0,c1506100,c4123f00) at vm_map_delete+0x413
vm_map_remove(c1506100,0,bfc0,11d,65) at vm_map_remove+0x55
exit1(c4496850,0,c041a26b,65,d8ca7d40) at exit1+0x63d
sys_exit(c4496850,d8ca7d10,c0437c26,3fd,1) at sys_exit+0x41
syscall(2f,2f,2f,0,) at syscall+0x26e
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x2829e9ff, esp = 0xbfbfde3c, ebp =
0xbfbfde58 ---
[...]
#10 0xc037fef6 in _vm_map_lock (map=0x0, file=0x0, line=0)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_map.c:388
#11 0xc037efe5 in kmem_malloc (map=0xc082f0b0, size=4096, flags=257)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_kern.c:328
#12 0xc03906a7 in page_alloc (zone=0xc083a240, bytes=0, pflag=0x0, wait=0)
at /a/asami/portbuild/i386/src-client/sys/vm/uma_core.c:802
#13 0xc0390425 in slab_zalloc (zone=0xc083a240, wait=257)
at /a/asami/portbuild/i386/src-client/sys/vm/uma_core.c:711
#14 0xc03915d8 in uma_zone_slab (zone=0xc083a240, flags=257)
at /a/asami/portbuild/i386/src-client/sys/vm/uma_core.c:1493
#15 0xc0391865 in uma_zalloc_internal (zone=0xc083a240, udata=0x0, flags=257)
at /a/asami/portbuild/i386/src-client/sys/vm/uma_core.c:1648
#16 0xc0391bdc in uma_zfree_arg (zone=0x101, item=0xd7a86000, udata=0x0)
at /a/asami/portbuild/i386/src-client/sys/vm/uma_core.c:1786
#17 0xc037a292 in swp_pager_meta_free (object=0xc45788ac, index=15621429236810645533,
count=1)
at uma.h:257
#18 0xc0378367 in swap_pager_freespace (object=0xc45788ac, start=15621429236810645533,
size=1)
at /a/asami/portbuild/i386/src-client/sys/vm/swap_pager.c:551
#19 0xc0388b3a in vm_object_backing_scan (object=0xc4bec5c8, op=4)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_object.c:1395
#20 0xc038795a in vm_object_collapse (object=0xc4bec5c8)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_object.c:1543
#21 0xc03862de in vm_object_deallocate (object=0xc4bec5c8)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_object.c:502
#22 0xc038255b in vm_map_entry_delete (map=0xc1506100, entry=0xc5093ce4)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_map.c:2034
#23 0xc0382993 in vm_map_delete (map=0xc1506100, start=3305716964, end=3217031168)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_map.c:2166
#24 0xc0382a15 in vm_map_remove (map=0xc1506100, start=0, end=3217031168)
at /a/asami/portbuild/i386/src-client/sys/vm/vm_map.c:2188
#25 0xc0240f2d in exit1 (td=0xc4496850, rv=0) at vm_map.h:191
#26 0xc02408e1 in sys_exit () at
/a/asami/portbuild/i386/src-client/sys/kern/kern_exit.c:102
#27 0xc03d2a8e in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = -1, tf_ebp =
-1077944744, tf_isp = -657818252, tf_ebx = 674341884, tf_edx = 10, tf_ecx = 674341520,
tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = 673835519, tf_cs = 31, tf_eflags =
642, tf_esp = -1077944772, tf_ss = 47})
at /a/asami/portbuild/i386/src-client/sys/i386/i386/trap.c:1023
#28 0xc03c2eed in Xint0x80_syscall () at {standard input}:138
-
pgp0.pgp
Description: PGP signature
[current] Re: ACPI Patch/DSDT .asl for Dell Inspiron 5000
Nate == Nate Lawson [EMAIL PROTECTED] writes: Nate Thanks for your patch submission. I looked into it and found a Nate few problems. Attached is a patch based on yours that should be Nate equivalent but fixes a few problems: Is this working for your laptop's S3 suspend? I'm trying to figure out what is required to make the S3 suspend work on my Dell D800 . Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: where is rogue?
On Wed, Jun 18, 2003 at 07:39:22AM +0100, Mark Murray wrote: Kris Kennaway writes: I installed freebsd-games, and it has most of the games I remember, but n= ot rogue. Well, hrumph, it's supposed to be in that port. Mark, it looks like rogue wasn't added for some reason. Oops. Fix coming later today. Any progress on this? Kris pgp0.pgp Description: PGP signature
Re: acpi patch for dell laptop?
On Mon, Jun 23, 2003 at 10:38:26AM -1000, Vincent Poy wrote: Speaking about ACPI, has anyone figured out how to close the lid without suspending? I remember before, when the lid was closed, it would suspend even with sysctl set to not suspend and the screen stays on and when you resume, you can type but the screen freezes and doesn't update. Setting hw.acpi.lid_switch_state=NONE in /etc/sysctl.conf keeps my Toshiba from suspending on lid close. Is that the sysctl you are referring to as not working? -- Scott LambertKC5MLE Unix SysAdmin [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [current] Re: ACPI Patch/DSDT .asl for Dell Inspiron 5000
The .asl file that I created is only for the Inspiron 5000. However, the S3 suspend itself on my machine works... however on resume I have a problem where the keyboard driver cannot reset the keyboard: atkbd: cannot set the command byte. I have heard that this affects some people only when they are running X Windows, however on my machine it happens on a straight text shell as well. I'm going to spend some time looking into this. Is anyone else having this problem? Isaac On Monday 23 June 2003 09:08 pm, David Gilbert wrote: Nate == Nate Lawson [EMAIL PROTECTED] writes: Nate Thanks for your patch submission. I looked into it and found a Nate few problems. Attached is a patch based on yours that should be Nate equivalent but fixes a few problems: Is this working for your laptop's S3 suspend? I'm trying to figure out what is required to make the S3 suspend work on my Dell D800 . Dave. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acpi patch for dell laptop?
+--- On Monday, June 23, 2003 09:42, | Shizuka Kudo proclaimed: | | --- Julian Elischer [EMAIL PROTECTED] wrote: | doesn't work for several models.. Including Inspiron 7500. | WHo knows enough about this to be able to look at debug info | I have? | | John Baldwin has posted a patch which worked for me on my Thinkpad 600X | with the same ACPI-0340 error. | | http://docs.freebsd.org/cgi/getmsg.cgi?fetch=214877+0+archive/2003/freebs |d-current/20030615.freebsd-current | ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER After patching my DSDT table, I was receiving a flood of these messages as well on my Gateway SOLO-9300, but the above patch also worked for me, and now I see zero messages from ACPI. Whoo-hoo! Is there a central location where we can post DSDT patches, as well as quirks like this, for various laptop models? I would like to share mine (although I think I am the only person who has mentioned a Gateway laptop here). In case there isn't, here is some info about my machine: (if any of this looks strange, please let me know) $ sysctl hw.acpi hw.acpi.supported_sleep_state: S1 S2 S3 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S1 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 1 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 5 hw.acpi.thermal.tz0.temperature: 3291 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3681 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3701 hw.acpi.thermal.tz0._ACx: 3321 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.acline: 1 hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 $ cat /etc/sysctl.conf # # the NONE setting lets the intended BIOS setting of 'lcd off' work hw.acpi.lid_switch_state=NONE # update the temperatures more often hw.acpi.thermal.polling_rate=5 # the S3 setting was causing all sorts of havoc, locking the machine up # so tight that the AC and batteries had to be removed to make it # function again hw.acpi.suspend_state=S1 -- +-+--+ | Michael W. Oliver, CCNP | The tree of liberty must be | | IPv6 FreeBSD mark | refreshed from time to time | | [EMAIL PROTECTED]| with the blood of patriots | | http://michael.gargantuan.com/| and tyrants.| | ASpath-tree, Looking Glass, etc. | - President Thomas Jefferson | | +--+ | gpg key - http://michael.gargantuan.com/gnupg/pubkey.asc | ++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
