Re: ACPI + Compaq Armada m700
Hello, Last night I cvsupped from 4.6-STABLE to 5.0-CURRENT. I do know the risks of using -CURRENT. Unfortunately I am having a problem with ACPI on boot. I have to issue the following to get the machine to boot boot unset acpi_load boot set boot_verbose=YES boot boot -v then the usual fsck and mount commands. I have read the acpi manpage along with acpiconfig. Unfortunately this didn't shed much light on fixing this problem on a permanent basis. I too have Armada m700 and am seeing the problem. The right solution is to have HP/Compaq fix the BIOS (which isn't likely) or to get someone who has a clue about ACPI look at our acpidump and find what's wrong there and fix the BIOS locally (ACPI configuration can be fetched from disk instead of from BIOS). The reason our computers don't boot is that under newer -current with ACPI it's either full HW configuration via ACPI and m700's ACPI does define our PCI bus (or something) wrong way (or there's a bug in ACPI code in -current). Meanwhile (forever I suppose) you could disable ACPI permanently by adding hint.acpi.0.disabled=1 to /boot/loader.conf[.local]. I also have hint.atkbd.0.flags=0x3 in there which helps with using my m700 with the docking station BTW. -- Michal Mertl [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
Joshua Goodall wrote: On Wed, Dec 04, 2002 at 01:32:58AM +0100, Brad Knowles wrote: At 12:31 PM +0200 2002/12/03, [EMAIL PROTECTED] wrote: The two machines involved are connected by a crossover cable: I've heard of lots of problems with machines using cross-over cables. Can you connect the machines through a switch, and ensure that they are hard-wired to 100Base-TX full duplex at both ends, as opposed to auto-negotiating? Just to add to this a-la-carte selection of possibilities; I recently debugged a NIC throughput problem which was resolved by a flash BIOS upgrade. This was an ASUS A7VL-VM motherboard, which appeared to do unpleasant things to PCI IRQs. Wipes egg off face: it seems that most of the bottleneck was an old drive in the one machine, although systat showed it as only 67% busy. If I fetch a file off the machine with the slow disk twice, the second time it's served from cache and the transfer rate is 60.9 megabits per second (test file is 90984206 bytes). The receiving machine's disk is reported as 10% busy by systat. Much better, but I'd still expect the ethernet to be saturated since transferring data to faster disk using the transaction size from systat yields about 143 megabits per second. [brane] ~ $ dd if=/dev/zero of=t bs=126k count=705 705+0 records in 705+0 records out 90961920 bytes transferred in 5.100551 secs (17833744 bytes/sec) I'll try a long cable tonight and see if I can borrow a switch from work for the evening. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ia64 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- === gnu/usr.bin/binutils/libbfd elf64-ia64.c: In function `elf64_ia64_size_dynamic_sections': elf64-ia64.c:2744: `ELF_DYNAMIC_INTERPRETER' undeclared (first use in this function) elf64-ia64.c:2744: (Each undeclared identifier is reported only once elf64-ia64.c:2744: for each function it appears in.) *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
Brad Knowles wrote: At 12:31 PM +0200 2002/12/03, [EMAIL PROTECTED] wrote: The two machines involved are connected by a crossover cable: I've heard of lots of problems with machines using cross-over cables. Can you connect the machines through a switch, and ensure that they are hard-wired to 100Base-TX full duplex at both ends, as opposed to auto-negotiating? They do this already. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: ata_dmasetup: transfer active on this device!
It seems Ian Dowse wrote: Hi Søren, I get the above panic every few days when resuming, especially if the disk was active while the laptop was suspending - it's easy to reproduce by starting some disk-intensive activity and then hitting the suspend button. I see that IWASAKI-san posted patches for this a few months ago - do you have any plans to incorporate his work? Uhm, its somewhere on my list, but IIRC there was something not quite right with that patch, I'll underline it on my whiteboard :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [acpi-jp 2013] RE: ACPI errors w/ latest ACPI code on GA BX2000 based system
Thanks, Bob.
I think this code is the problem:
Scope(\_TZ_) {
ThermalZone(THRM) {
Name(_AL0, Package(0x1) {
FAN_,
})
The name FAN_ is not defined elsewhere in the namespace.
I guess that BIOS writer forgot to delete _AL0 definition :)
Instead, you can delete these lines and override DSDT, I think.
Name(_AL0, Package(0x1) {
FAN_,
})
Thanks
To my memo:
DefinitionBlock (
acpi_dsdt.aml,//Output filename
DSDT, //Signature
0x1,//DSDT Revision
COMPAQ, //OEMID
AWRDACPI, //TABLE ID
0x1000 //OEM Revision
)
Bob
-Original Message-
From: Thomas Seck [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 30, 2002 4:34 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [acpi-jp 2009] Re: ACPI errors w/ latest ACPI code on GA BX2000
based system
* Mitsuru IWASAKI ([EMAIL PROTECTED]):
Iwasaki-san,
list members,
ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND
ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
I think that this was caused by the following spec changes.
From CHANGES.txt:
22 October 2002. Summary of changes for version 20021022.
1) ACPI CA Core Subsystem:
Implemented a restriction on the Scope operator that the
target must already exist in the namespace at the time the
operator is encountered (during table load or method
execution). In other words, forward references are not
allowed and Scope() cannot create a new object. This changes
the previous behavior where the interpreter would create the
name if not found. This new behavior correctly enables the
search-to-root algorithm during namespace lookup of the target
name. Because of this upsearch, this fixes the known Compaq
_SB_.OKEC problem and makes both the AML interpreter and iASL
compiler compatible with other ACPI implementations.
Could you send your acpidump output to this acpi-jp ML?
Of course. And thank you very much for working on this. Please see the
attached file.
--Thomas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
How can I use my kernel on DP2?
Hi, everybody, I found a very strange thing about kernel on DP2. I do not know why I compiled my kernel, but I can not boot with it? Current# uname -a FreeBSD Current.wtwh.com.cn 5.0-DP2 FreeBSD 5.0-DP2 #1: Sat Nov 16 13:38:33 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 When The box reboot, I explicitly do as follow: ?unload ?load /boot/kernel/kernel ?boot But the result is the same!!! Why? Best Regards Ouyang Kai _ ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
unable to use boot0cfg
Hi I'm using both -current and -stable on the same machine, very common. Boot0cfg has -s [12345] flag to set the slice to boot on and it has been working so far. Beginning from Dec 1, I'm unable to set the slice: root:vallo# boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023: 15:63 63 16382961 2 0x00 1023:255:63 0xa5 1023: 15:63 16383024 16383024 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) root:vallo# boot0cfg -v -s 2 ad0 boot0cfg: /dev/ad0: Operation not permitted root:vallo# disklabel -W ad0 disklabel: /dev/ad0: Operation not permitted This is probably related to recent (re)work to protect disk labels, but I'm not authoritative. This is not a fair way to stick me to -current :-) -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ahc and fd
After recent your changes of the ahc driver, the fd driver can't work on my pc98 box. It never return from the open(2) syscall. I don't know that this problem is only pc98 or not. --- TAKAHASHI Yoshihiro [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc and fd
In message [EMAIL PROTECTED], Takahashi Yoshihiro writes: After recent your changes of the ahc driver, the fd driver can't work on my pc98 box. It never return from the open(2) syscall. I don't know that this problem is only pc98 or not. Please try to comment out the aic driver. The AIC has a very intrusive probe function. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: unable to use boot0cfg
Date: Wed, 4 Dec 2002 15:17:39 +0200 From: Vallo Kallaste [EMAIL PROTECTED] I'm using both -current and -stable on the same machine, very common. Boot0cfg has -s [12345] flag to set the slice to boot on and it has been working so far. Beginning from Dec 1, I'm unable to set the slice: root:vallo# boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023: 15:63 63 16382961 2 0x00 1023:255:63 0xa5 1023: 15:63 16383024 16383024 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) root:vallo# boot0cfg -v -s 2 ad0 boot0cfg: /dev/ad0: Operation not permitted root:vallo# disklabel -W ad0 disklabel: /dev/ad0: Operation not permitted Yes; it is an artifact of GEOM (per phk). This is probably related to recent (re)work to protect disk labels, but I'm not authoritative. This is not a fair way to stick me to -current :-) Right; I have the same problem. By interrupting the boot sequence early enough (by hitting the space bar) -- before loader is, itself, loaded, and the prompt is FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: -- you can override it by typing 0:ad(0,1,a)/boot/loader (to boot from slice 1) -- ref. man boot. The timing can be tricky enough to be a nuisance when one is doing this on a machine with (only) a serial console, especially when the machine is not close enough to hear the disk seeks. :-} Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I have no confidence in results obtained through the use of Microsoft products. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FYI - 4.3-stable to 5.0 upgrade success
On Sat, Nov 30, 2002 at 05:48:21PM -0500, Daniel Eischen wrote: I recently upgraded a Dell Lattitude C600 from some version of -stable after 4.3 to 5.0-current. I first upgraded it to 4.7-stable, then to 5.0-current. I followed the instructions at the end of src/UPDATING pretty much to the letter. I haven't recompiled any applications for 5.0, so they're all running OK under -current (KDE and some other stuff). You could also jump directly from 4.3 to 5.0 -- I'm in charge of supporting this upgrade path, down to 4.0. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg48079/pgp0.pgp Description: PGP signature
RE: How can I use my kernel on DP2?
assuming you read the handbook on updating the kernel http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html , UPDATING in /usr/src ftp://ftp.freebsd.org/pub/FreeBSD/branches/-current/src/UPDATING , and completed a make and make install in your kernel compile directory, you should be able to use it. before you waste time rebooting 1000 times, check the file size of the new kernel and the old kernel to see if it changes. also, look at the make files to see what's happening when you run certain targets. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of kai ouyang Sent: Wednesday, December 04, 2002 12:56 PM To: [EMAIL PROTECTED] Subject: How can I use my kernel on DP2? Hi, everybody, I found a very strange thing about kernel on DP2. I do not know why I compiled my kernel, but I can not boot with it? Current# uname -a FreeBSD Current.wtwh.com.cn 5.0-DP2 FreeBSD 5.0-DP2 #1: Sat Nov 16 13:38:33 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 When The box reboot, I explicitly do as follow: ?unload ?load /boot/kernel/kernel ?boot But the result is the same!!! Why? Best Regards Ouyang Kai _ ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). I see the hanging Speaker problem on an Asus A7V with an Athlon 2000+ and 256 Megs of RAM, so it seems not SMP related, nor Tyan related. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ia64 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- === gnu/usr.bin/binutils/libbfd elf64-ia64.c: In function `elf64_ia64_size_dynamic_sections': elf64-ia64.c:2744: `ELF_DYNAMIC_INTERPRETER' undeclared (first use in this function) elf64-ia64.c:2744: (Each undeclared identifier is reported only once elf64-ia64.c:2744: for each function it appears in.) *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc and fd
In article [EMAIL PROTECTED] Poul-Henning Kamp [EMAIL PROTECTED] writes: In message [EMAIL PROTECTED], Takahashi Yoshihiro writes: After recent your changes of the ahc driver, the fd driver can't work on my pc98 box. It never return from the open(2) syscall. I don't know that this problem is only pc98 or not. Please try to comment out the aic driver. The AIC has a very intrusive probe function. I have tested a new kernel w/o the aic driver, but it has no effect. --- TAKAHASHI Yoshihiro [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc and fd
On Wed, Dec 04, 2002 at 11:53:55PM +0900, Takahashi Yoshihiro wrote: In article [EMAIL PROTECTED] Poul-Henning Kamp [EMAIL PROTECTED] writes: In message [EMAIL PROTECTED], Takahashi Yoshihiro writes: After recent your changes of the ahc driver, the fd driver can't work on my pc98 box. It never return from the open(2) syscall. I don't know that this problem is only pc98 or not. Please try to comment out the aic driver. The AIC has a very intrusive probe function. I have tested a new kernel w/o the aic driver, but it has no effect. Do you have an ahc card in your system? If you don't, then I have no idea what could be going wrong since it shouldn't do anything more than just check PCI Id's and then fail. If you do have an ahc device, try placing the following line in /boot/device.hints: hint.ahc.0.allow_memio=1 If you have more than one ahc device, or your device is dual channel, add more copies of this line to the file and increment the third field of it. If this solves the problem, then your machine probably has an issue with leaking PCI IOPORT cycles onto the ISA bus. Unfortunately, I know little about PC98, nor do I have easy access to a machine. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [acpi-jp 2015] Re: ACPI Poweroff problem
Hi,
* Nate Lawson ([EMAIL PROTECTED]):
Power System off using ACPI
ACPI -1287 *** Error: Method execution failed
AE_AML_UNINITIALIZED_LOCAL
ACPI -1287 *** Error: Method execution failed
AE_AML_UNINITIALIZED_LOCAL
ACPIEnterSleepStatePrep failed AE_AML_UNINITIALIZED_LOCAL
(so, or similar).
PS : I have an VIA KT266 chipset.
Please cc acpi-jp list with acpi problems, as I have on this reply. Check
the current@ archives for the patch 20021122 that iwasaki@ posted. It may
fix your problem.
It seems that some problems were introduced with that patch.
Really? If so, could you describe them? We need to report any
problems to Intel in order to obtain good ACPI support.
BTW, I've seen some AE_AML_UNINITIALIZED_LOCAL problems in DSDT,
especially about one year ago. Typical ASL code is like this:
Method(_PS0) {
Store(Local0, Local0)
Store(0x1, _PSC)
}
As you noticed, uninitialized Local0 is referred in Store operator.
It's easy to fix this kind DSDT errors in most cases.
# or updated BIOS may be already provided.
Please check and fix your acpidump output, or send it to acpi-jp ML.
Thanks
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ahc and fd
In article [EMAIL PROTECTED] Scott Long [EMAIL PROTECTED] writes: Do you have an ahc card in your system? If you don't, then I have no idea what could be going wrong since it shouldn't do anything more than just check PCI Id's and then fail. If you do have an ahc device, try placing the following line in /boot/device.hints: hint.ahc.0.allow_memio=1 I am using the Japanese version of AHA-2940U which supports both IBM-PC and PC-98. I tried enabling the above option, but the fd driver still does not work. I attach the output of dmesg. --- TAKAHASHI Yoshihiro [EMAIL PROTECTED] Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1994-2002 FreeBSD(98) porting team. Copyright (c) 1992 A.Kojima F.Ukai M.Ishii (KMC). Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #11: Wed Dec 4 23:36:53 JST 2002 [EMAIL PROTECTED]:/work/sys/pc98/compile/GENERIC Preloaded elf kernel /boot/kernel.t/kernel at 0xc04f3000. Calibrating clock(s) ... TSC clock: 198947438 Hz, i8254 clock: 2457599 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 2457600 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 198949336 Hz CPU: Pentium Pro (198.95-MHz 686-class CPU) Origin = GenuineIntel Id = 0x616 Stepping = 6 Features=0xf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV real memory = 134217728 (128 MB) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0051a000 - 0x00ef, 10379264 bytes (2534 pages) 0x0100 - 0x07ff7fff, 117407744 bytes (28664 pages) avail memory = 123875328 (118 MB) bios32: Found BIOS32 Service Directory header at 0xc00f4c40 bios32: Entry = 0xf5612 (c00f5612) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xd90b0+0x1c56b pnpbios: Found PnP BIOS data at 0xc00f51b0 pnpbios: Entry = d8000:3a Rev = 1.0 pnpbios: OEM ID 38394350 Other BIOS signatures found: Initializing GEOMetry subsystem random: entropy source mem: memory I/O Pentium Pro MTRR support enabled null: null device, zero device Math emulator present npx0: math processor on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=12378086) pcibios: BIOS_PRESENT call failed pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci0: physical bus=0 found- vendor=0x8086, dev=0x1237, revid=0x02 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x1033, dev=0x002c, revid=0x01 bus=0, slot=6, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0107, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x1033, dev=0x0009, revid=0x02 bus=0, slot=7, func=0 class=03-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base 2000, size 22, enabled map[14]: type 1, range 32, base 2040, size 16, enabled map[18]: type 1, range 32, base 2080, size 22, enabled found- vendor=0x1023, dev=0x9660, revid=0xd3 bus=0, slot=8, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0002, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[10]: type 3, range 32, base 2041, size 12, enabled map[14]: type 4, range 32, base 6000, size 5, enabled map[18]: type 1, range 32, base 2050, size 20, enabled found- vendor=0x8086, dev=0x1229, revid=0x01 bus=0, slot=11, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0147, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x57 (2610 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=3 map[10]: type 4, range 32, base 6100, size 8, enabled map[14]: type 1, range 32, base 20411000, size 12, enabled found- vendor=0x9004, dev=0x8178, revid=0x00 bus=0, slot=16, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0157, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x54 (2520 ns), mingnt=0x08 (2000 ns), maxlat=0x08 (2000 ns) intpin=a, irq=3 PCI-ISA bridge with incorrect subclass 0x80 PCI-ISA bridge with incorrect subclass 0x80 isab0: PCI-ISA bridge at device 6.0 on pci0 isa0: ISA bus on isab0 pci0: display at device 7.0 (no driver attached) pci0: display, VGA at device 8.0 (no driver attached) fxp0: Intel Pro 10/100B/100+
ata device removal panic fix
Hi, I've been hacking on DMA windows on alpha. While I've been getting things wrong, I've been provoking a panic in the ata driver because it cannot do DMA when attaching a disk. The panic is triggered at the end of ad_attach() by the raid probe causing a transfer to fail and the disk to be detached. That's fine and dandy, but ad_print() is called with the (now stale) ad pointer. Here's a patch which fixes the problem. The disk is now correctly detached and the boot proceeds normally (modulo my dma window hacking). The patch is against stable, but should also apply to -current. I think it might appease some people w/marginal hardware who see panics at boot... Drew Index: ata-disk.c === RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.60.2.23 diff -u -r1.60.2.23 ata-disk.c --- ata-disk.c 30 May 2002 11:42:13 - 1.60.2.23 +++ ata-disk.c 4 Dec 2002 16:16:59 - @@ -217,8 +217,9 @@ /* if this disk belongs to an ATA RAID dont print the probe */ if (ata_raiddisk_attach(adp)) adp-flags |= AD_F_RAID_SUBDISK; -else - ad_print(adp); +else if (atadev-driver != NULL) +ad_print(atadev-driver); + } void The panic is as follows: sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 mcclock0: MC146818A real time clock at port 0x70-0x71 on isa0 ad1: READ command timeout tag=0 serv=0 - resetting ata2: resetting devices .. ad1: removed from configuration done fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x0 a1 = 0x1 a2 = 0x0 pc = 0xfc36ddb8 ra = 0xfc36b69c curproc= 0xfc73d458 pid = 0, comm = swapper ddbprinttrap from 0xfc36ddb8 ddbprinttrap(0x0, 0x1, 0x0, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) 0xfc7dda70 ra=0xfc60e9e0,sp=0xfc7dda70 db tr Debugger() at Debugger+0x2c panic() at panic+0x100 trap() at trap+0x600 XentMM() at XentMM+0x2c --- memory management fault (from ipl 4) --- ad_print() at ad_print+0x1f8 ad_attach() at ad_attach+0x5bc ata_boot_attach() at ata_boot_attach+0x1a4 run_interrupt_driven_config_hooks() at run_interrupt_driven_config_hooks+0x30 mi_startup() at mi_startup+0xf4 locorestart() at locorestart+0x68 --- root of call graph --- (gdb) l *ad_attach+0x5bc 0xfc36b69c is in ad_interrupt (../../dev/ata/ata-disk.c:221). 216 217 /* if this disk belongs to an ATA RAID dont print the probe */ 218 if (ata_raiddisk_attach(adp)) 219 adp-flags |= AD_F_RAID_SUBDISK; 220 else 221 ad_print(adp); 222 } 223 224 void 225 ad_detach(struct ata_device *atadev, int flush) /* get rid of flush XXX SOS */ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make buildworld failure
/usr/src/contrib/gcc/cp/except.c:790:18: cfns.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. JY To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sbin/dump dump.8 main.c
On Tue, 2002-12-03 at 13:21, Kirk McKusick wrote: mckusick2002/12/03 10:21:09 PST Modified files: sbin/dumpdump.8 main.c Log: Add the `L' option [...] Aha! I've been waiting for that ever since it was hinted at in the original snapshots readme. I do wonder, however, if there is any way to use the feature without running it as root? I normally run dump as operator (via amanda); when I hacked up amdump to use L, the dumps failed, like so: ?/-- akira.woss /usr/local lev 1 STRANGE sendbackup: start [akira.wossname.net:/usr/local level 1] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end | dump: Cannot create /usr/local/.dump_snapshot: Operation not permitted | ??error [/sbin/dump returned 1]? dumper: strange [missing size line from sendbackup] ? dumper: strange [missing end line from sendbackup] \ I've played with sysctl vfs.usermount and various permissions for the mount points but just haven't gotten it to work for operator. Does anyone have any hints? Is it even possible to create a snapshot without being the super-user? I think I can work around this by configuring amanda to run as root but I did want to point out that this might be an unexpected problem if the silent snapshot semantics are ever adopted (as foreshadowed by the commit message). I can't be the only one running dump as operator, can I? -Ben -- Benjamin Lewis [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld failure
On Thu, Dec 05, 2002 at 02:08:42AM +0800, JY wrote: /usr/src/contrib/gcc/cp/except.c:790:18: cfns.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. Please cvsup again, and reply back if you still have any build problems. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Wed Dec 4 09:35:53 PST 2002 -- Kernel build for GENERIC completed on Wed Dec 4 10:26:52 PST 2002 -- Kernel build for LINT started on Wed Dec 4 10:26:52 PST 2002 -- === vesa Makefile, line 5401: warning: duplicate script for target geom_bsd.o ignored Makefile, line 5404: warning: duplicate script for target geom_mbr.o ignored /local0/scratch/des/src/sys/contrib/dev/acpica/dbdisply.c:131: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/dbexec.c:124: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/dbhistry.c:124: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/dbinput.c:125: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/dbstats.c:125: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/dbxface.c:127: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/hwgpe.c:122: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/hwregs.c: In function `AcpiGetSleepTypeData': /local0/scratch/des/src/sys/contrib/dev/acpica/hwregs.c:242: warning: cast discards qualifiers from pointer target type /local0/scratch/des/src/sys/contrib/dev/acpica/nsxfname.c:125: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/nsxfobj.c:126: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/rsdump.c:124: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/utclib.c:129: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/utdebug.c:122: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/contrib/dev/acpica/utglobal.c: In function `AcpiUtGetRegionName': /local0/scratch/des/src/sys/contrib/dev/acpica/utglobal.c:482: warning: cast discards qualifiers from pointer target type /local0/scratch/des/src/sys/contrib/dev/acpica/utglobal.c: In function `AcpiUtGetEventName': /local0/scratch/des/src/sys/contrib/dev/acpica/utglobal.c:520: warning: cast discards qualifiers from pointer target type /local0/scratch/des/src/sys/contrib/dev/acpica/utglobal.c: In function `AcpiUtGetTypeName': /local0/scratch/des/src/sys/contrib/dev/acpica/utglobal.c:590: warning: cast discards qualifiers from pointer target type /local0/scratch/des/src/sys/contrib/dev/acpica/utglobal.c:593: warning: cast discards qualifiers from pointer target type /local0/scratch/des/src/sys/dev/acpica/acpi_acad.c:50: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/dev/acpica/acpi_cmbat.c:56: warning: `_THIS_MODULE' defined but not used /local0/scratch/des/src/sys/dev/acpica/acpi_powerres.c:272: warning: `acpi_pwr_deregister_consumer' defined but not used /local0/scratch/des/src/sys/dev/acpica/acpi_powerres.c:210: warning: `acpi_pwr_deregister_resource' defined but not used /local0/scratch/des/src/sys/dev/ie/if_ie.c: In function `ieattach': /local0/scratch/des/src/sys/dev/ie/if_ie.c:778: warning: assignment discards qualifiers from pointer target type /local0/scratch/des/src/sys/dev/ie/if_ie.c: In function `ieget': /local0/scratch/des/src/sys/dev/ie/if_ie.c:1147: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type /local0/scratch/des/src/sys/dev/ie/if_ie.c:1237: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type /local0/scratch/des/src/sys/dev/ie/if_ie.c:1237: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type
GEOM + GRUB = ??
Trying to install a new version of GRUB not having much success. I'm wondering if GEOM is interacting with it in some strange way. I am fairly certain grub reads the partitions itself, but this would be through the geom layer would it not? The port might need to be marked broken for 5.0, or someone with geom know-how submit a patch to the grub folks (if that is really the problem). Can anyone else verify this? I'm using grub with a device-map file that used to work just fine. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM + GRUB = ??
Wesley Morgan wrote: Trying to install a new version of GRUB not having much success. I'm wondering if GEOM is interacting with it in some strange way. I am fairly certain grub reads the partitions itself, but this would be through the geom layer would it not? The port might need to be marked broken for 5.0, or someone with geom know-how submit a patch to the grub folks (if that is really the problem). Can anyone else verify this? I'm using grub with a device-map file that used to work just fine. GEOM is merely a byte array layout manager interface layer, of the type I first described BSD needing in about 1995 (according to Google). As such, GEOM is just an abstraction, and just for FreeBSD. The GRUB stuff does not use GEOM, because GEOM is an abstraction that lives in FreeBSD only. GRUB reads the data directly, itself. To do this, it has to have some knowledge of how to at least get at the code in the boot1/boot2 case (try booting one of the files in /boot instead of /kernel), and it needs to understand the FS layout for where the files are stored, and/or use a sector map. It will need to be updated for UFS2, when that becomes an issue. You need to provide a little more information about your failure to PHK or Bruce Evans, who will be able to better tell you how to deal with the FreeBSD boot code. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI + Compaq Armada m700
Apparently the listserver ate my message for breakfast, resending.
Maybe too big? I'm only attaching the patch this time; the other files
are available on request.
-Forwarded Message-
From: Craig Boston [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: ACPI + Compaq Armada m700
Date: 04 Dec 2002 08:55:34 -0600
I've been conversing with Paul off-list about this and it is working on
his m700 now with a fixed AML file. I'm posing my modified AML since
there appear to be a few more people using current on the m700 now than
the last time I checked (when it was 0 :).
Impatient user version:
1. Put the attached acpi_dsdt.aml file in /boot/
2. Add these two lines to /boot/loader.conf:
acpi_dsdt_load=YES
acpi_dsdt_name=/boot/acpi_dsdt.aml
Developer version:
It appears that the AML code in the Compaq BIOS has a few problems with
it that Windows ignores, but a stricter implementation doesn't like.
The problem is that on bootup, no devices are detected. As a result,
the root filesystem can't be mounted and the system panics.
Attached is the ASL output from acpidump (gzipped) and a patch that
corrects some of the bigger problems.
Mostly the changes are along the lines of:
-Name(_HID, *PNP0C0D)
+Name(_HID, PNP0C0D)
For some unknown reason Compaq seems to like the * character in all the
device names. Removing them makes iasl much happier and now the devices
are detected on bootup.
There are also a couple of changes like this:
@@ -625,8 +627,10 @@
Store(Arg0, C082)
Store(Arg1, C081)
Store(Arg2, C082)
+Store(C082, Local0)
^C097()
Release(^C08A)
+Return(Local0)
}
iasl was complaining about a method or two that were called expecting a
return value, but didn't actually return anything. There are many
similar methods that do return a value, and they all seem to just return
whatever was in Arg0. Admittedly, I know next to nothing about ASL/AML,
so maybe one of the ACPI wizards can figure out if this is the right
thing to do or not.
Anyway, it works for Paul and me. Suspend doesn't seem to work
correctly for me, but I don't know if that's an AML issue or something
else. Everything else ACPI works fine on the m700 I'm using.
Craig
--- compaq.asl Tue Oct 29 10:24:52 2002
+++ compaq-fixed.aslWed Dec 4 08:26:58 2002
@@ -63,7 +63,7 @@
Name(C003, 0xfffd)
Mutex(C004, 0)
Device(C005) {
-Name(_HID, *PNP0A03)
+Name(_HID, PNP0A03)
Name(_ADR, 0x0)
OperationRegion(C006, PCI_Config, 0x5a, 0x6)
Field(C006, AnyAcc, NoLock, Preserve) {
@@ -467,7 +467,7 @@
}
Scope(\_SB_) {
Device(C057) {
-Name(_HID, *PNP0C0E)
+Name(_HID, PNP0C0E)
Name(_PRW, Package(0x2) {
0xb,
0x4,
@@ -487,7 +487,7 @@
}
Scope(\_SB_.C005.C013) {
Device(C059) {
-Name(_HID, *PNP0A06)
+Name(_HID, PNP0A06)
OperationRegion(C05A, SystemIO, 0xe0, 0x2)
Field(C05A, ByteAcc, NoLock, Preserve) {
C05B, 8,
@@ -597,9 +597,11 @@
Store(Arg0, C05C)
Store(Arg1, C05B)
Store(Arg2, C05C)
+Store(C05C, Local0)
^C093()
Release(\_GL_)
Release(^C089)
+Return(Local0)
}
Method(C096) {
Store(0x2, C086)
@@ -625,8 +627,10 @@
Store(Arg0, C082)
Store(Arg1, C081)
Store(Arg2, C082)
+Store(C082, Local0)
^C097()
Release(^C08A)
+Return(Local0)
}
Method(C09A, 2) {
If(LEqual(Arg0, 0x0)) {
@@ -994,7 +998,7 @@
}
Scope(\_SB_) {
Device(C0BF) {
-Name(_HID, *PNP0C02)
+Name(_HID, PNP0C02)
Name(_UID, 0x0)
Name(C0C0, Package(0x10) {
})
@@ -1207,7 +1211,7 @@
}
}
Device(C0D8) {
-Name(_HID, *PNP0C01)
+Name(_HID, PNP0C01)
Method(_CRS) {
Name(C0D7, Buffer(0x26) {0x86, 0x9, 0x0, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0,
0x0, 0xa, 0x0, 0x86, 0x9, 0x0, 0x0, 0x0, 0x0, 0xf, 0x0, 0x0, 0x0, 0x1, 0x0, 0x86, 0x9,
0x0, 0x1, 0x0, 0x0, 0x10, 0x0, 0x0, 0x0, 0xf0, 0x0, 0x79, 0x0 })
CreateDWordField(C0D7, 0x20, C00E)
@@ -1218,14 +1222,14 @@
}
Scope(\_SB_.C005) {
Device(C0DA) {
-Name(_HID, *PNP0C02)
+Name(_HID, PNP0C02)
Name(_UID, 0x1)
Name(_CRS, Buffer(0x32) {0x47, 0x1, 0xd0, 0x4, 0xd0, 0x4, 0x1, 0x2, 0x47,
0x1, 0x0, 0x8, 0x0, 0x8, 0x1, 0x80, 0x47, 0x1, 0x0, 0x40, 0x0, 0x40, 0x1, 0x10, 0x47,
0x1, 0x0, 0x50, 0x0, 0x50, 0x1, 0x64, 0x47, 0x1, 0x4, 0x60, 0x4, 0x60, 0x1, 0x2, 0x47,
0x1, 0x0, 0xf0, 0x0, 0xf0, 0x1, 0xd0, 0x79, 0x0 })
}
}
Scope(\_SB_.C005.C013) {
Device(C0DB) {
-Name(_HID, *PNP0C02)
+Name(_HID, PNP0C02)
Name(_UID, 0x2)
Method(_CRS) {
Name(C0D7,
Re: VM related panic during suspend/resume
I've just committed a fix for this assertion failure. Regards, Alan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM + GRUB = ??
On Wed, 4 Dec 2002, Terry Lambert wrote: The GRUB stuff does not use GEOM, because GEOM is an abstraction that lives in FreeBSD only. GRUB reads the data directly, itself. To do this, it has to have some knowledge of how to at least get at the code in the boot1/boot2 case (try booting one of the files in /boot instead of /kernel), and it needs to understand the FS layout for where the files are stored, and/or use a sector map. It will need to be updated for UFS2, when that becomes an issue. It's not the booting that is a problem. That was working fine until I had to wipe out the MBR when my disklabel was chomped last week.. It's the grub command-line shell/installer that won't work now (admittedly I have not updated my grub boot blocks in a while either, so it may be a pre-GEOM issue). Would not accessing /dev/adX with open() or so go through GEOM? -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VM related panic during suspend/resume
On Wed, Dec 04, 2002 at 01:52:33PM -0600, Alan L. Cox wrote: I've just committed a fix for this assertion failure. Regards, Alan Thanks! - Christian -- http://www.unixpages.org[EMAIL PROTECTED] GPG Pub-Key: www.unixpages.org/cbrueffer.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D GPG Key ID : 0xA0ED982D msg48097/pgp0.pgp Description: PGP signature
Re: GEOM + GRUB = ??
On Wed, Dec 04, 2002 at 02:56:10PM -0500, Wesley Morgan wrote: On Wed, 4 Dec 2002, Terry Lambert wrote: The GRUB stuff does not use GEOM, because GEOM is an abstraction that lives in FreeBSD only. GRUB reads the data directly, itself. To do this, it has to have some knowledge of how to at least get at the code in the boot1/boot2 case (try booting one of the files in /boot instead of /kernel), and it needs to understand the FS layout for where the files are stored, and/or use a sector map. It will need to be updated for UFS2, when that becomes an issue. It's not the booting that is a problem. That was working fine until I had to wipe out the MBR when my disklabel was chomped last week.. It's the grub command-line shell/installer that won't work now (admittedly I have not updated my grub boot blocks in a while either, so it may be a pre-GEOM issue). Would not accessing /dev/adX with open() or so go through GEOM? Actually I was having problems with the installer in -STABLE also, so it may also be something with the port itself. - Christian -- http://www.unixpages.org[EMAIL PROTECTED] GPG Pub-Key: www.unixpages.org/cbrueffer.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D GPG Key ID : 0xA0ED982D msg48098/pgp0.pgp Description: PGP signature
ia64 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- === gnu/usr.bin/binutils/libbfd elf64-ia64.c: In function `elf64_ia64_size_dynamic_sections': elf64-ia64.c:2744: `ELF_DYNAMIC_INTERPRETER' undeclared (first use in this function) elf64-ia64.c:2744: (Each undeclared identifier is reported only once elf64-ia64.c:2744: for each function it appears in.) *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
DP-2 and Nvidia Geforce 4
Is there any solution to the above combo other than just waiting? thanks, Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI + Compaq Armada m700
On 4 Dec 2002, Craig Boston wrote: I've been conversing with Paul off-list about this and it is working on his m700 now with a fixed AML file. I'm posing my modified AML since there appear to be a few more people using current on the m700 now than the last time I checked (when it was 0 :). Impatient user version: 1. Put the attached acpi_dsdt.aml file in /boot/ 2. Add these two lines to /boot/loader.conf: acpi_dsdt_load=YES acpi_dsdt_name=/boot/acpi_dsdt.aml Can someone host a db of systems and asl patches? It would be useful to all users, not just freebsd. The problem is that it is impossible to get MB vendors to fix the dsdt when it 'works' on windows. A separate script could take a patch, dump dsdt, compare patch header against asl header (reject if for wrong system), and then compile the new dsdt. This way users wouldn't manually be mucking with acpidump/iasl. Even better, it could be done as an optional part of installkernel. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP-2 and Nvidia Geforce 4
On Wed, 2002-12-04 at 17:04, Rob wrote: Is there any solution to the above combo other than just waiting? I think you've seen my how-to at http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for your card, or are you referring to GeForce 4 with accelerated 3D support? Joe thanks, Rob. -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB mass device not quite there
On Sun, 1 Dec 2002, Pete Carah wrote:
da0 at umass-sim0 bus 0 target 0 lun 0
da0: eUSB Compact Flash 5.07 Removable Direct Access SCSI-2 device
da0: Serial Number 21M82CFC1Y09C11125Z3
da0: 650KB/s transfers
da0: 122MB (250368 512 byte sectors: 64H 32S/T 122C)
...
The other slot is multiple; it handles SmartMedia, MM/SD cards,
and memory-sticks. It is not found by the usb event handler
or camcontrol at all. The directions do say that this device
shows up in windoze as 2 drives (I haven't tried it yet, under any
of 95, 98, or XP). Apparently our usb event handler doesn't expect
to find 2 devices, or pass doesn't expect 2 devices beyond it in
a single scan?
I have 2 different usb umass devices with multiple 'drives' in them --
they both use different luns for this - for whatever reason (perhaps the
get-max-luns call fails?) only lun 0 is ever scanned.
To get them to work all I need do is:
camcontrol rescan X:Y:1
and they will be found. the lowest devices is usually 'automatically'
found as X:Y:0 and so I just need to manually scan the other luns and all
is good.
(JamP3 mp3 player has luns 0 and 1, and my Neodio 6-in-1 flash reader - 4
slots CF/Microdrive SD/MMC Memorystick and smartmedia -
The appropriate quirk for the 6 in 1 device in scsi_da.c is:
{
{T_DIRECT, SIP_MEDIA_REMOVABLE, Generic, USB Storage-*,*},
/*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE
},
and the quirk for the JamP3 is unvailable on a machine that is down right
now... It looks very similar :).
Hope this helps.
Just remember to camcontrol rescan the right lun and you should have no
problems.
Fred
--
Fred Clift - [EMAIL PROTECTED] -- Remember: If brute
force doesn't work, you're just not using enough.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Creating bootsector file for W2k boot menu
I've used Windows NT boot menu for years to boot FreeBSD from the second disk on my machines. I've used bootpart DOS program to do this but now I can't find correct way to do FreeBSD boot block for it. Earlier there was a diskid definition in some Makefile to change. How should I do this now? Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: console problem
This problem and the general 'console freeze' problem, and possibly even the 'floppy doesn't work anymore' problem should be fixed. The problem was with the ahc and ahd drivers corrupting the callout list used to trigger timeouts in the kernel. Scott -Original Message- From: Holm Tiffe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 7:27 AM To: [EMAIL PROTECTED] Subject: Re: console problem Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). I see the hanging Speaker problem on an Asus A7V with an Athlon 2000+ and 256 Megs of RAM, so it seems not SMP related, nor Tyan related. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
USB issues with Apollo KT133A mobo
Hi all. I'm running 5.0-DP2 on a motherboard with the Apollo KT133A chipset. (I believe it's an ASUS, but it doesn't seem to be labelled.) The USB controller (described by dmesg as a VIA 83C572) periodically blows its brains out. More specifically, all USB devices lose power. The device nodes stay in /dev and there are no notices to dmesg about the loss until I unplug and replug them, at which time it says 'port error: restarting port N' where N is generally 0, depending on which controller it is. It then redetects my hardware. This also happened on 4.5 and above, so it might very well be a hardware problem on my end. Since I'm not getting any helpful error messages from my system, my question is this: what debugging switches, if any, should I turn on to see what's going on? Are there any known issues with this controller? Should I just sup to -current? Thanks! -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Lock order reversals in sys_pipe.c and kern_sig.c
Alfred Perlstein wrote: * Kris Kennaway [021118 11:06] wrote: I've just turned witness back on on the bento cluster, and got the following lock order reversals a number of times overnight: Nov 18 07:45:40 gohan11 kernel: 1st 0xc6887200 pipe mutex (pipe mutex) @ /local0/src-client/sys/kern/sys_pipe.c:465 Nov 18 07:45:40 gohan11 kernel: 2nd 0xc0447780 sigio lock (sigio lock) @ /local0/src-client/sys/kern/kern_sig.c:2225 Nov 18 10:28:47 gohan10 kernel: 1st 0xc4941580 pipe mutex (pipe mutex) @ /local0/src-client/sys/kern/sys_pipe.c:1038 [...] Are these known problems? Well now they are, I will investigate as time permits. FYI, just got a similar one yesterday on an up-to-date -current: lock order reversal 1st 0xc784d700 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc0513840 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2225 Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: ACPI Poweroff problem
* Nate Lawson ([EMAIL PROTECTED]): 20021122 has not been imported yet. 20021118 is version in -current. Sorry. Thanks for correcting me on that one. Sorry for the confusion. --Thomas To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sound problems
Lars Eggert wrote: Peter Gade Jensen wrote: I have the same problem. It sounds like the soundbuffer runs empty somehow and needs to fill up before continueing. This results in something that sounds like a really small sample(1ms) looping for 1second or so. If this makes sense? :o) Same here; a good way to produce these symptoms is a portupgrade -a. An even better way turns out to be a sysctl -a while xmms is playing something - I get about a second of garbled audio each time. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Lock order reversals in sys_pipe.c and kern_sig.c
* Lars Eggert [EMAIL PROTECTED] [021204 15:04] wrote: FYI, just got a similar one yesterday on an up-to-date -current: lock order reversal 1st 0xc784d700 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc0513840 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2225 Since no one has given me the traceback based on the patch I posted earlier I have ceased to care about the problem. If someone seriously cares they will run with my patch and post a backtrace. thank you, -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Lock order reversals in sys_pipe.c and kern_sig.c
Alfred Perlstein wrote: * Lars Eggert [021204 15:04] wrote: FYI, just got a similar one yesterday on an up-to-date -current: lock order reversal 1st 0xc784d700 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc0513840 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2225 Since no one has given me the traceback based on the patch I posted earlier I have ceased to care about the problem. If someone seriously cares they will run with my patch and post a backtrace. Applied your patch, will send a traceback when it happens again (I only get one of these every few days). Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: USB issues with Apollo KT133A mobo
Cliff L. Biffle [EMAIL PROTECTED] wrote: More specifically, all USB devices lose power. The device nodes stay in /dev and there are no notices to dmesg about the loss until I unplug and replug them, at which time it says 'port error: restarting port N' where N is generally 0, depending on which controller it is. It then redetects my hardware. 1. IIRC, USB ports on KT133A motherboards were buggy (???). 2. Drawing too much power from the USB ports can cause the ports to shut down. The absolute maximum limit is 500mA, which isn't much (some 2.5 USB hard disks can draw MUCH more, which violates the spec, and sometimes works, and sometimes doesn't). Here's another discussion on this: http://groups.google.com/groups?hl=enlr=lang_enie=UTF-8threadm=ajedc5%24bej%241%40paris.btinternet.comrnum=1 -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[PATCH] net/tac_plus4
Since 5.0 is approaching, and this didnt get any attention on
-ports, I figured I'd forward it here.
- Forwarded message from Jeff Ito [EMAIL PROTECTED] -
Can someone who uses tac_plus/skey please test this to verify it works.
It compiles cleanly. But I am not certain that the apis are quite as
interchangable as it appears.
these deprecate files/patch-aa and files/patch-ab
files/patch-ah
--- skey_fn.c.orig Sun Jun 18 13:26:54 2000
+++ skey_fn.c Sun Nov 3 17:34:25 2002
@@ -27,10 +27,10 @@
#define STATE_AUTHEN_GETUSER 1 /* username has been requested */
#define STATE_AUTHEN_GETPASS 2 /* password has been requested */
-#include skey.h
+#include opie.h
struct private_data {
-struct skey skey;
+struct opie skey;
char password[MAX_PASSWD_LEN + 1];
int state;
};
@@ -44,14 +44,14 @@
struct authen_data *data;
{
struct private_data *p = data-method_data;
-struct skey *skeyp = p-skey;
+struct opie *skeyp = p-skey;
data-status = TAC_PLUS_AUTHEN_STATUS_FAIL;
-if (skeyverify(skeyp, passwd) == 0) {
+if (opieverify(skeyp, passwd) == 0) {
/* S/Key authentication succeeded */
data-status = TAC_PLUS_AUTHEN_STATUS_PASS;
- if (skeyp-n 5) {
+ if (skeyp-opie_n 5) {
data-server_msg = tac_strdup(Password will expire soon);
return (1);
}
@@ -167,10 +167,15 @@
return(1);
}
- if (skeychallenge(p-skey, name, skeyprompt) == 0) {
+ if (opiechallenge(p-skey, name, skeyprompt) == 0) {
char buf[256];
sprintf(buf, %s\nPassword: , skeyprompt);
data-server_msg = tac_strdup(buf);
+
+ /* We try to make it in accordance of standard FreeBSD
+* behaviour in order to avoid surprises for user */
+ data-flags = TAC_PLUS_AUTHEN_FLAG_NOECHO;
+
data-status = TAC_PLUS_AUTHEN_STATUS_GETPASS;
p-state = STATE_AUTHEN_GETPASS;
return (0);
files/patch-ag
--- Makefile.orig Sun Jun 18 13:26:54 2000
+++ MakefileSun Nov 3 17:34:20 2002
@@ -19,7 +19,7 @@
# LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
# FOR A PARTICULAR PURPOSE.
-CC = gcc
+# CC = gcc
# For AIX
# See /usr/lpp/bos/bsdport on your system for details of how to define bsdcc
@@ -33,13 +33,13 @@
# OS=-DMIPS
# For Solaris (SUNOS 5.3, 5.4, 5.5, 5.6) uncomment the following two lines
-OS=-DSOLARIS
-OSLIBS=-lsocket -lnsl
+# OS=-DSOLARIS
+# OSLIBS=-lsocket -lnsl
# For FreeBSD
-# OS=-DFREEBSD
+OS=-DFREEBSD
# You may also need to add:
-# OSLIBS=-lcrypt
+OSLIBS=-lcrypt
# NOTE: If you want your password encryption to be compatible with
# e.g. SunOS, you may need to instead use:
# OSLIBS=-ldescrypt
@@ -64,12 +64,12 @@
# FLAGS = -DTAC_PLUS_USERID=$(USERID) -DTAC_PLUS_GROUPID=$(GROUPID)
# Definitions for SKEY functionality
-# DEFINES = -DSKEY
-# LIBS = ../crimelab/skey/src/libskey.a
+DEFINES = -DSKEY
+LIBS = -lopie -lmd
# INCLUDES = -I../crimelab/skey/src
# Debugging flags
-DEBUG = -g
+# DEBUG = -g
# Enforce a limit on maximum sessions per user. See the user's guide
# for more information.
@@ -85,13 +85,13 @@
# possible), containing its process id. Uncomment and modify the
# following line to change this filename
-# PIDFILE = -DTAC_PLUS_PIDFILE=\/var/run/tac_plus.pid\
+PIDFILE = -DTAC_PLUS_PIDFILE=\/var/run/tac_plus.pid\
#
# End of customisable section of Makefile
#
-CFLAGS = $(DEBUG) $(DEFINES) $(INCLUDES) $(FLAGS) $(OS) $(PIDFILE) $(MAXSESS)
+CFLAGS += $(DEBUG) $(DEFINES) $(INCLUDES) $(FLAGS) $(OS) $(PIDFILE) $(MAXSESS)
HFILES = expire.h parse.h regmagic.h md5.h regexp.h tac_plus.h
@@ -130,8 +130,8 @@
-rm -f *.o *~ *.BAK tac_plus generate_passwd
install:
- cp tac_plus /usr/local/bin
- cp tac_plus.1 /usr/man/manl/tac_plus.1
+ cp tac_plus $(PREFIX)/sbin
+ cp tac_plus.1 $(PREFIX)/man1/tac_plus.1
depend:
makedepend $(CFLAGS) $(SRCS)
...
feedback appreciated
thank you
Jeff
- End forwarded message -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: USB issues with Apollo KT133A mobo
On Wed, Dec 04, 2002 at 04:00:15PM -0700, Cliff L. Biffle wrote: Hi all. I'm running 5.0-DP2 on a motherboard with the Apollo KT133A chipset. (I believe it's an ASUS, but it doesn't seem to be labelled.) The USB controller (described by dmesg as a VIA 83C572) periodically blows its brains out. Is it ohci? If so can you try this patch? Joe -- Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ An eclectic mix of fact and theory. = Index: ohci.c === RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v retrieving revision 1.113 diff -u -r1.113 ohci.c --- ohci.c 30 Sep 2002 17:50:16 - 1.113 +++ ohci.c 1 Dec 2002 21:04:36 - @@ -1810,7 +1810,7 @@ SPLUSBCHECK; /* XXX */ - for (p = head; p == NULL p-next != sed; p = p-next) + for (p = head; p != NULL p-next != sed; p = p-next) ; if (p == NULL) panic(ohci_rem_ed: ED not found\n); msg48114/pgp0.pgp Description: PGP signature
Re: Lock order reversals in sys_pipe.c and kern_sig.c
Alfred Perlstein wrote: * Lars Eggert [021204 15:04] wrote: FYI, just got a similar one yesterday on an up-to-date -current: lock order reversal 1st 0xc784d700 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc0513840 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2225 Since no one has given me the traceback based on the patch I posted earlier I have ceased to care about the problem. If someone seriously cares they will run with my patch and post a backtrace. Here's one: lock order reversal 1st 0xc795ea00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc0515340 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2225 Debugger(witness_lock) Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0 db trace Debugger(c0472495,c0515340,c04a8e51,c04a8e51,c04ab721) at Debugger+0x5a witness_lock(c0515340,8,c04ab721,8b1,eb4d8be8) at witness_lock+0x142 _mtx_lock_flags(c0515340,0,c04ab721,8b1,c02f1531) at _mtx_lock_flags+0x63 pgsigio(c77afae8,17,0,1ad,0) at pgsigio+0x2d pipe_read(c6ff8384,eb4d8c78,c6beb100,0,c6ac9e00) at pipe_read+0x2d4 dofileread(c6ac9e00,c6ff8384,3,bfbfe317,1) at dofileread+0xd7 read(c6ac9e00,eb4d8d10,c04c9811,407,c6bced50) at read+0x7b syscall(2f,2f,bfbf002f,281dca2b,bfbfe330) at syscall+0x3c6 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (3, FreeBSD ELF32, read), eip = 0x280c5ff3, esp = 0xbfbfe2fc, ebp = 0xbfbfe358 --- -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: USB support for new HP printers?
John Nielsen [EMAIL PROTECTED] writes: Hi, John. The LaserJet 1200 advertises several alternate settings for the printer-class interface: 7/1/3 (for IEEE 1284.4 packets, the new and different USB interface you mentioned), 7/1/2 (bidirectional raw print data), and 7/1/1 (unidirectional raw print data). If you can somehow convince the ulpt driver to bind to 7/1/2 or 7/1/1 rather than just blindly binding to the first alternate setting it finds, then that should be all you need. Interesting. I wonder if the same applies to the OfficeJet. I have a d145, and while FreeBSD recognizes it just fine, and attaches it as a ulpt device, it fails to print (the process that tries to write to /dev/ulpt0 just hangs). I'll see if I can figure out a way to force the ulpt driver to bind to 7/1/2. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM + GRUB = ??
Wesley Morgan wrote: It's not the booting that is a problem. That was working fine until I had to wipe out the MBR when my disklabel was chomped last week.. It's the grub command-line shell/installer that won't work now (admittedly I have not updated my grub boot blocks in a while either, so it may be a pre-GEOM issue). Would not accessing /dev/adX with open() or so go through GEOM? OK, I misunderstood; I thought you were saying it's a boot probelm, when it's actually a write the MBR problem. Yes, GEOM breaks a number of things that used to work in that area; you probably need to beat on Poul (there was a seperate report of a port that broke because it could not write the disklabel, that was posted yesterday -- diskcheckd, I believe). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Poweroff problem with IBM ThinkPad T21 (ACPI?)
I just put 5.0-DP2 on my IBM ThinkPad T21 (which I can finaly use, 4.x was pretty bad since only one of the two pcmcia slots worked, and numerous other problems, forcing me to use windows) and have been very very happy with it. ACPI works nicely on the laptop, and everything seems to be pretty happy (I did update it to current once and had to reinstall as the stability was pretty bad, so I took it back to DP2 which is working well). I only have 1 problem that I have been completely unable to solve. If I power off the laptop (shutdown -p now, or halt -p), approximately 60-63 minutes later the laptop will power back on (I live in Los Angeles, and so it powers back on in my laptop bag during my commute home, so when I get home it's about to overheat) all by it's self. This is pretty odd. I have found no way to make it not do this. Does anyone have any ideas? I have verified in the bios that nothing is turned on that would cause this, nor did this happen under Windows XP. Thanks in advance, and great work. I'm really happy that I can finally use FreeBSD on my laptop as well as my desktops/servers. Greg -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
stuck in DDB
Just tonight I pushed Ctl+Alt+Esc and dropped into DDB, only to find I couldn't do anything there. Either the machine hard locked or my keyboard didn't work, I can't think of any way to tell the difference there. I really have pitifully little to go on; I didn't even have DDB compiled in until today for a very long time, so I don't know if it used to work before. I have a USB keyboard, with support for it enabled in the BIOS, if anyone cares. I don't expect anybody can solve this with so little to go on, but maybe somebody else has at least experienced it? (I can't try a non-USB keyboard; this box has a busted PS/2 port.) -- Ray Kohler [EMAIL PROTECTED] Egotist, n.: A person of low taste, more interested in himself than me. -- Ambrose Bierce, The Devil's Dictionary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ia64 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- === gnu/usr.bin/binutils/libbfd elf64-ia64.c: In function `elf64_ia64_size_dynamic_sections': elf64-ia64.c:2744: `ELF_DYNAMIC_INTERPRETER' undeclared (first use in this function) elf64-ia64.c:2744: (Each undeclared identifier is reported only once elf64-ia64.c:2744: for each function it appears in.) *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld failure
On Wed, Dec 04, 2002 at 10:55:24AM -0800, David O'Brien wrote: On Thu, Dec 05, 2002 at 02:08:42AM +0800, JY wrote: /usr/src/contrib/gcc/cp/except.c:790:18: cfns.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. Please cvsup again, and reply back if you still have any build problems. buildworld ok now. But cvsup kept coming up with this -- Running /usr/local/bin/cvsup -- Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Delete src/contrib/gcc/INSTALL Cannot delete /usr/src/contrib/gcc/INSTALL: Directory not empty rm -rf /usr/src rm -rf /usr/sup and re-cvsupping does not help. JY To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld failure
On Thu, Dec 05, 2002 at 10:55:48AM +0800, JY wrote: On Wed, Dec 04, 2002 at 10:55:24AM -0800, David O'Brien wrote: On Thu, Dec 05, 2002 at 02:08:42AM +0800, JY wrote: /usr/src/contrib/gcc/cp/except.c:790:18: cfns.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. Please cvsup again, and reply back if you still have any build problems. buildworld ok now. But cvsup kept coming up with this -- Running /usr/local/bin/cvsup -- Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Delete src/contrib/gcc/INSTALL Cannot delete /usr/src/contrib/gcc/INSTALL: Directory not empty rm -rf /usr/src rm -rf /usr/sup and re-cvsupping does not help. I removed just the problematic directory and re-cvsupped. It downloaded the directory again but after that it didn't complain again. This looks like some kind of repo damage. -- Ray Kohler [EMAIL PROTECTED] You are only young once, but you can stay immature indefinitely. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: console problem
On Wed, 4 Dec 2002, Long, Scott wrote: This problem and the general 'console freeze' problem, and possibly even the 'floppy doesn't work anymore' problem should be fixed. The problem was with the ahc and ahd drivers corrupting the callout list used to trigger timeouts in the kernel. Pardon me for taking this long to answer, but the surest method of proving the fix was a sufficient torture test. It's quite finished now, and this is indeed a fix. I'm curious how you got to looking into the ahc driver for an ostensible syscons bug ... just perusing commit logs? Scott -Original Message- From: Holm Tiffe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 7:27 AM To: [EMAIL PROTECTED] Subject: Re: console problem Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). I see the hanging Speaker problem on an Asus A7V with an Athlon 2000+ and 256 Megs of RAM, so it seems not SMP related, nor Tyan related. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld failure
On Wed, Dec 04, 2002 at 10:09:16PM -0500, Ray Kohler wrote: Cannot delete /usr/src/contrib/gcc/INSTALL: Directory not empty rm -rf /usr/src rm -rf /usr/sup and re-cvsupping does not help. I removed just the problematic directory and re-cvsupped. It downloaded the directory again but after that it didn't complain again. This looks like some kind of repo damage. -- Ray Kohler [EMAIL PROTECTED] I did as you suggested and it's still complaining :( JY To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
Unfortunately, I have no extra hardware available to me, so I can't experiment with switches and whatnot. Also, wouldn't some sort of software experimentation be more appropriate, considering that my existing setup works _perfetcly_ in 4.7? I'm not sure what to do; should I be trying various versions of if_rl.c? Or is there something else that I should be trying? -Craig - Original Message - From: Brad Knowles [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Brad Knowles [EMAIL PROTECTED]; Craig Reyenga [EMAIL PROTECTED]; Terry Lambert [EMAIL PROTECTED]; [EMAIL PROTECTED]; Christopher J Olson [EMAIL PROTECTED] Sent: Tuesday, December 03, 2002 19:32 Subject: Re: Any ideas at all about network problem? At 12:31 PM +0200 2002/12/03, [EMAIL PROTECTED] wrote: The two machines involved are connected by a crossover cable: I've heard of lots of problems with machines using cross-over cables. Can you connect the machines through a switch, and ensure that they are hard-wired to 100Base-TX full duplex at both ends, as opposed to auto-negotiating? I'll try a different cable this evening when I get home. Is there a minimum length? The cable is currently 2m long. I'm prepared to do any other debugging people here can suggest to make it work faster. FWIW my single CPU workstaion at the office running 4.7-STABLE with an fxp0 NIC does not suffer the same throughput reduction. I've also heard of lots of problems with some machines when the cable is too short, at least in certain combinations. Try successively longer lengths of cable, at least up to 20-30m. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP-2 and Nvidia Geforce 4
Joe Marcus Clarke wrote: On Wed, 2002-12-04 at 17:04, Rob wrote: Is there any solution to the above combo other than just waiting? I think you've seen my how-to at http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for your card, or are you referring to GeForce 4 with accelerated 3D support? Joe thanks, Rob. -- PGP Key : http://www.marcuscom.com/pgp.asc Thanks Joe, I will check it out. I think I used your procedure to get the Geforce 2 on my laptop -current working. But I tried a number of things for DP2 on my big machine that didn't work. In that case I've got an Asus V8170 Geforce 4 card that I got on the cheap. I can always go back to a Riva TNT or something thats $20 :) :) Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP-2 and Nvidia Geforce 4
Rob wrote: Joe Marcus Clarke wrote: On Wed, 2002-12-04 at 17:04, Rob wrote: Is there any solution to the above combo other than just waiting? I think you've seen my how-to at http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for your card, or are you referring to GeForce 4 with accelerated 3D support? Joe Hi Joe, I have confirmed that your procedure didn't work with my Asus V8170 Geforce 4 card. But its not a hardware issue. I'm getting undefined symbols in one of the libraries. I will later today boot into DP2 and see if I can put together a more meaningful report. I built the XFree86-4 metaport from a fresh ports directory. First make deinstall then make reinstall. Thanks, Rob. thanks, Rob. -- PGP Key : http://www.marcuscom.com/pgp.asc Thanks Joe, I will check it out. I think I used your procedure to get the Geforce 2 on my laptop -current working. But I tried a number of things for DP2 on my big machine that didn't work. In that case I've got an Asus V8170 Geforce 4 card that I got on the cheap. I can always go back to a Riva TNT or something thats $20 :) :) Rob. -- - The Numeric Python EM Project www.pythonemproject.com -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Poweroff problem with IBM ThinkPad T21 (ACPI?)
This problem was around prior to 5.0-DP2. I have a thinkpad A21 and experienced this at least as far back as early october. I've never had the time to investigate further. You should take this as confirming that this isn't a configuration issue. From Greg Rumple [EMAIL PROTECTED], Wed, Dec 04, 2002 at 11:03:53AM -0800: I just put 5.0-DP2 on my IBM ThinkPad T21 (which I can finaly use, 4.x was pretty bad since only one of the two pcmcia slots worked, and numerous other problems, forcing me to use windows) and have been very very happy with it. ACPI works nicely on the laptop, and everything seems to be pretty happy (I did update it to current once and had to reinstall as the stability was pretty bad, so I took it back to DP2 which is working well). I only have 1 problem that I have been completely unable to solve. If I power off the laptop (shutdown -p now, or halt -p), approximately 60-63 minutes later the laptop will power back on (I live in Los Angeles, and so it powers back on in my laptop bag during my commute home, so when I get home it's about to overheat) all by it's self. This is pretty odd. I have found no way to make it not do this. Does anyone have any ideas? I have verified in the bios that nothing is turned on that would cause this, nor did this happen under Windows XP. Thanks in advance, and great work. I'm really happy that I can finally use FreeBSD on my laptop as well as my desktops/servers. Greg -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Poweroff problem with IBM ThinkPad T21 (ACPI?)
I just put 5.0-DP2 on my IBM ThinkPad T21 (which I can finaly use, 4.x was pretty bad since only one of the two pcmcia slots worked, and numerous other problems, forcing me to use windows) and have been very very happy with it. Really? I ran 4.X on my T21 for over a year with no problems whatsoever. 4.X was usable, unlike 3.X, which was a complete mess. I only have 1 problem that I have been completely unable to solve. If I power off the laptop (shutdown -p now, or halt -p), approximately 60-63 minutes later the laptop will power back on (I live in Los Angeles, and so it powers back on in my laptop bag during my commute home, so when I get home it's about to overheat) all by it's self. This is pretty odd. I have found no way to make it not do this. Hmm, this sounds like a BIOS setting for wakeup on LAN/phone events. You might check the bootup to see if 'Wake-On-Lan' is set or somesuch. Otherwise, I have no idea... Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB issues with Apollo KT133A mobo
On Wednesday 04 December 2002 05:11 pm, Darryl Okahata wrote: 1. IIRC, USB ports on KT133A motherboards were buggy (???). Could be. The ATA controller was also flaking out under 4.7, but is solid as a rock under 5.0-DP2, which is why I'm sticking with it despite other potential bugs. I can burn CDs now! 2. Drawing too much power from the USB ports can cause the ports to shut down. The absolute maximum limit is 500mA, which isn't much (some 2.5 USB hard disks can draw MUCH more, which violates the spec, and sometimes works, and sometimes doesn't). The behavior persists with just an optical USB mouse, which can't possibly be sucking more than a few dozen mills. (I hope.) In the discussion link you sent me, they discuss the controller disabling the port due to excessive current draw...would it re-enable the port when I simply un/replug the mouse? Normally I'd expect that to require a reboot. (The mouse does come back when I remove it and reinsert it, and generally X doesn't even notice.) The KT133 discussion suggests it's a hardware problem, which wouldn't surprise me...this particular mobo is a very early Athlon board, and the chipset may be buggy. -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP-2 and Nvidia Geforce 4
On Wed, 2002-12-04 at 22:46, Rob wrote: Rob wrote: Joe Marcus Clarke wrote: On Wed, 2002-12-04 at 17:04, Rob wrote: Is there any solution to the above combo other than just waiting? I think you've seen my how-to at http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for your card, or are you referring to GeForce 4 with accelerated 3D support? Joe Hi Joe, I have confirmed that your procedure didn't work with my Asus V8170 Geforce 4 card. But its not a hardware issue. I'm getting undefined symbols in one of the libraries. I will later today boot into DP2 and see if I can put together a more meaningful report. I built the XFree86-4 metaport from a fresh ports directory. First make deinstall then make reinstall. I've seen that before. It usually can be fixed by making sure that the correct X server modules are loaded. That is, of course, if you're seeing unresolved symbols in X itself. Joe Thanks, Rob. thanks, Rob. -- PGP Key : http://www.marcuscom.com/pgp.asc Thanks Joe, I will check it out. I think I used your procedure to get the Geforce 2 on my laptop -current working. But I tried a number of things for DP2 on my big machine that didn't work. In that case I've got an Asus V8170 Geforce 4 card that I got on the cheap. I can always go back to a Riva TNT or something thats $20 :) :) Rob. -- - The Numeric Python EM Project www.pythonemproject.com -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB issues with Apollo KT133A mobo
On Wednesday 04 December 2002 05:40 pm, Josef Karthauser wrote: Is it ohci? If so can you try this patch? Joe Hey Joe -- fancy meeting you here. :-) Nope, the KT133 has two UHCI controllers. What I'm going to do next (which I should have done before) is try the following variables: 1. Does the mouse die if it's the only thing plugged in AND is buffered by a powered hub? (iirc, yes, but needs testing) 2. Does the secondary controller work? (The ports stub out in a header on the board, but I've brought them out and will test.) If (1) is true, that (imho) eliminates the current-draw question. If (2) is true, that points to hardware problems with the primary controller. (Forgot I had two. *grin*) -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DP-2 and Nvidia Geforce 4
Joe Marcus Clarke wrote: On Wed, 2002-12-04 at 22:46, Rob wrote: Rob wrote: Joe Marcus Clarke wrote: On Wed, 2002-12-04 at 17:04, Rob wrote: Is there any solution to the above combo other than just waiting? I think you've seen my how-to at http://www.marcuscom.com/g2g-xfree86/article.html. Did it not work for your card, or are you referring to GeForce 4 with accelerated 3D support? Joe Hi Joe, I have confirmed that your procedure didn't work with my Asus V8170 Geforce 4 card. But its not a hardware issue. I'm getting undefined symbols in one of the libraries. I will later today boot into DP2 and see if I can put together a more meaningful report. I built the XFree86-4 metaport from a fresh ports directory. First make deinstall then make reinstall. I've seen that before. It usually can be fixed by making sure that the correct X server modules are loaded. That is, of course, if you're seeing unresolved symbols in X itself. Joe Thanks, Rob. thanks, Rob. -- PGP Key : http://www.marcuscom.com/pgp.asc Thanks Joe, I will check it out. I think I used your procedure to get the Geforce 2 on my laptop -current working. But I tried a number of things for DP2 on my big machine that didn't work. In that case I've got an Asus V8170 Geforce 4 card that I got on the cheap. I can always go back to a Riva TNT or something thats $20 :) :) Rob. -- - The Numeric Python EM Project www.pythonemproject.com -- PGP Key : http://www.marcuscom.com/pgp.asc Ok, here is the error message. The server never even gets past go: Symbol vgaHWUnmapMem from module /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved! Fatal server error: Caught signal 11. Server aborting. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: setfacl requirements?
Hi, everybody, From Robert N M Watson (1) UFS_ACL isn't enabled Yes, I am sure that in my kernel config: options UFS_ACL options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART (2) Extended attributes aren't available on the file system (shouldn't happen for UFS2, but might happen for UFS1 if you don't have UFS_EXTATTR and appropriate configuration of EAs) I do as the README.alcs mkdir -p /usr/.attribute/system cd /.attribute/system extattrctl initattr -p /usr/ 388 posix1e.acl_access extattrctl initattr -p /usr/ 388 posix1e.acl_default (3) The file system isn't mounted with the ACL option: either -o acls (or acls in the fstab file), or more reliably, setting the tunefs -a enable flag in the file system configuration. For better or for worse, POSIX.1e defines that getfacl() will print the current file permissions as an ACL if ACLs aren't available on the file system. As such, you're probably just seeing the results of stat() printed in an ACL form. I use UFS1. In DP1, the ACL works nice. But in DP2, I have never succeeded. in DP1, there is no need to add the 'acls' to 'fstab'. Anyway, I also add the 'acls' flag to 'fstab', but it fails, too. The system always say: Current#cd /usr/ Current#setfacl -m u:oyk:r src setfacl: acl_get_file() failed: Operation not supported Best Regards Ouyang Kai _ ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
