arp: unknown hardware address format

2003-08-18 Thread Boris Kovalenko
Hello!

   What is the problem if I see arp: unknown hardware address format 
(0x4d6f) messages with bge driver on 5.1R?

Yours truly,
   Boris Kovalenko
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


[current tinderbox] failure on ia64/ia64

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 09:01:29 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-08-18 09:01:29 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 09:04:59 - building world
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
[...]
cc -O -pipe  
-I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure/libexec/sftp-server/../../../crypto/openssh
 -DNO_IDEA  -o sftp-server sftp-common.o sftp-server.o -lssh -lcrypto
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/bin/ld:
 warning: libz.so.2, needed by 
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so,
 not found (try using -rpath or -rpath-link)
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflate'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflate'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateInit_'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateInit_'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateEnd'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateEnd'
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure/libexec/sftp-server.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure/libexec.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src.
TB --- 2003-08-18 10:01:05 - /usr/bin/make returned exit code  1 
TB --- 2003-08-18 10:01:05 - ERROR: failed to build world
TB --- 2003-08-18 10:01:05 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


[current tinderbox] failure on sparc64/sparc64

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 10:01:06 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-08-18 10:01:06 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 10:04:10 - building world
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
[...]
cc -O -pipe  
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure/libexec/sftp-server/../../../crypto/openssh
 -DNO_IDEA  -o sftp-server sftp-common.o sftp-server.o -lssh -lcrypto
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/bin/ld:
 warning: libz.so.2, needed by 
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so,
 not found (try using -rpath or -rpath-link)
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflate'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflate'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateInit_'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateInit_'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateEnd'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateEnd'
*** Error code 1

Stop in 
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure/libexec/sftp-server.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure/libexec.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
TB --- 2003-08-18 10:53:13 - /usr/bin/make returned exit code  1 
TB --- 2003-08-18 10:53:13 - ERROR: failed to build world
TB --- 2003-08-18 10:53:13 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


USB Printer?

2003-08-18 Thread Daniel Nielsen
Hi.

I installed 5.1-RELEASE on a compuiter with a nforce2 mobo, worked
nice... Then I bought a Brother-5050 Laser printer
(Postscript). Installed and configured cups. cups worked fine. Then I
realized, the printer only works if it is turned on before my freebsd
boots. 

When I power it up, it is detected by the freebsd usb-system:

zits root # dmesg | grep ulpt
ulpt0: Brother HL-5050, rev 2.00/1.00, addr 3, iclass 7/1
ulpt0: using bi-directional mode
zits root #

And when I turn it off:
zits root # dmesg | grep ulpt
snip
ulpt0: at uhub0 port 2 (addr 3) disconnected
ulpt0: detached
zits root #

but when I send a job to the printer, the CUPS usb backend just
hangs, locking /dev/ulpt0

I tried cat /root/some-file  /dev/ulpt0 , and it also just hangs. 

If the printer enters standby after boot, then it also doesn't print,
with the same symptoms.

I then tried upgrading to -CURRENT (about a week ago), but it still
doesn't work. It works perfectly from Knoppix 3.2 and winXP, so I'm
pretty sure it is a freeBSD usb problem. I should also mention, that
I'm using a USB mouse, and it works fine even disconnecting and
reconnecting after boot.

Does anyone know what I could do to get it working? Or where to look
for more debugging info? 


/Daniel

-- 
There are no great men, only great challenges that ordinary men are forced
by circumstances to meet.
-- Admiral William Halsey
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: an driver / Cisco Aironet 340 stopped working

2003-08-18 Thread Jack.W.Parks
Don't know if anyone replied yet since I don't subscribe to
freebsd-current, but I had to add the following line to my
/boot/loader.conf file.

hw.pci.allow_unsupported_io_range=1

Jack

-Original Message-
From: Tomi Vainio - Sun Finland [mailto:[EMAIL PROTECTED] 
Sent: Saturday, August 16, 2003 4:27 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: an driver / Cisco Aironet 340 stopped working


I've used my Cisco WLAN with Toshiba Portege 3440 couple years but now
it's broken.  I just upgraded to new Toshiba Tecra M1 and reinstalled
FreeBSD there and now I get an0: record length mismatch -- expected
430, got 440 for Rid ff68 errors.  I already tried with old laptop with
latest kernel and old kernel from Jun 26th but it's also broken there so
I cannot say who long this has been broken.

  Tomppa


fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu
1500
inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 
ether 02:00:39:34:7f:f2
ch 1 dma 0
em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=3RXCSUM,TXCSUM
inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 
inet 212.226.167.247 netmask 0xfff0 broadcast
212.226.167.255
inet6 2001:670:82:babe:208:dff:feda:ec61 prefixlen 64 tentative
autoconf 
ether 00:08:0d:da:ec:61
media: Ethernet autoselect (100baseTX full-duplex)
status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128 
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 
inet 127.0.0.1 netmask 0xff00 
an0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet6 fe80::240:96ff:fe38:56e7%an0 prefixlen 64 scopeid 0x4 
ether 00:40:96:38:56:e7
media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
status: associated
ssid AsOlA 1:AsOlA
stationname phb
channel 6 authmode OPEN powersavemode CAM powersavesleep 200
wepmode ON weptxkey 1
wepkey 1:128-bit

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 #3: Sat Aug 16 20:28:39 EEST 2003
[EMAIL PROTECTED]:/u/F/local/sup/5.0/sys/i386/compile/PHB
acpi_alloc_wakeup_handler: unable to allocate wake memory Preloaded elf
kernel /boot/kernel/kernel at 0xc065. Preloaded elf module
/boot/kernel/splash_bmp.ko at 0xc06502e4. Preloaded elf module
/boot/kernel/vesa.ko at 0xc0650394. Preloaded splash_image_data
/boot/splash.bmp at 0xc0650440. Preloaded elf module
/boot/kernel/usb.ko at 0xc0650490. Preloaded elf module
/boot/kernel/ukbd.ko at 0xc0650538. Preloaded elf module
/boot/kernel/ums.ko at 0xc06505e4. Preloaded elf module
/boot/kernel/umass.ko at 0xc065068c. Preloaded elf module
/boot/kernel/random.ko at 0xc0650738. Calibrating clock(s) ... i8254
clock: 1193183 Hz Timecounter i8254 frequency 1193183 Hz quality 0
Calibrating TSC clock ... TSC clock: 1396507980 Hz
CPU: Intel(R) Pentium(R) M processor 1400MHz (1396.51-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x695  Stepping = 5
 
Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV
,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE
real memory  = 536674304 (511 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x00677000 - 0x1f692fff, 520208384 bytes (127004 pages)
avail memory = 513142784 (489 MB)
bios32: Found BIOS32 Service Directory header at 0xc00f0240
bios32: Entry = 0xfc0e3 (c00fc0e3)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xd641
pnpbios: Found PnP BIOS data at 0xc00f0450
pnpbios: Entry = f:9138  Rev = 1.0
pnpbios: Event flag at 510
pnpbios: OEM ID 8938f351
Other BIOS signatures found:
wlan: 802.11 Link Layer
null: null device, zero device
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 40 00 
00 01 00 02 00 02 13 01 00 01 2d 01 00 01 38 01 
00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
VESA: 31 mode(s) found
VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc053aca0 (140)
VESA: Trident CYBER 2100
VESA: TRIDENT MICROSYSTEMS INC. CYBER 2100 RXT  7.3 (16.28)  
random: entropy source
splash: [EMAIL PROTECTED], size:787506
splash_bmp: beyond screen capacity (1024x768, 255 colors)
splash_bmp: beyond screen capacity (1024x768, 255 colors)
bmp_start(): splash_mode:261
splash: image decoder found: splash_bmp
acpi0: TOSHIB 750  on motherboard
pci_open(1):mode 1 addr port (0x0cf8) is 0x
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=33408086)
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00f01a0
PCI-Only Interrupts: none
Location  Bus Device Pin  Link  IRQs
embedded 

Re: Slow Boot

2003-08-18 Thread Bill Moran
Matthew D. Fuller wrote:
On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
Bill Moran, and lo! it spake thus:
My best guess is that the chipset responds slowly to probes, thus it
takes a while to get the list of devices from it.  However, I've never
looked into it any more than that.
I've always presumed it to be a question of timing out probes to the
drives; it only ever happens on IDE controllers with no devices attached
to 'em.  I habitually just disable the controller channels that are empty
(or, in the case of my SCSI systems, just yank ATA support altogether).
Could be.  This machine is pretty bare-bones.  Single ATA HDD and nothing
on the secondary controller.  I never really considered that, but it makes
sense that probes on the secondary controller would take the full timeout
value if there was nothing to respond.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: USB Printer?

2003-08-18 Thread Bernd Walter
On Mon, Aug 18, 2003 at 01:02:51PM +0200, Daniel Nielsen wrote:
 Hi.
 
 I installed 5.1-RELEASE on a compuiter with a nforce2 mobo, worked
 nice... Then I bought a Brother-5050 Laser printer
 (Postscript). Installed and configured cups. cups worked fine. Then I
 realized, the printer only works if it is turned on before my freebsd
 boots. 
 
 When I power it up, it is detected by the freebsd usb-system:
 
 zits root # dmesg | grep ulpt
 ulpt0: Brother HL-5050, rev 2.00/1.00, addr 3, iclass 7/1
 ulpt0: using bi-directional mode
 zits root #
 
 And when I turn it off:
 zits root # dmesg | grep ulpt
 snip
 ulpt0: at uhub0 port 2 (addr 3) disconnected
 ulpt0: detached
 zits root #
 
 but when I send a job to the printer, the CUPS usb backend just
 hangs, locking /dev/ulpt0
 
 I tried cat /root/some-file  /dev/ulpt0 , and it also just hangs. 

/dev/ulpt0 shouldn't exist after ulpt0 was detached.

 If the printer enters standby after boot, then it also doesn't print,
 with the same symptoms.
 
 I then tried upgrading to -CURRENT (about a week ago), but it still
 doesn't work. It works perfectly from Knoppix 3.2 and winXP, so I'm
 pretty sure it is a freeBSD usb problem. I should also mention, that
 I'm using a USB mouse, and it works fine even disconnecting and
 reconnecting after boot.

That something work with another OS doesn't say anything about that it's
an OS problem.
It could also mean that the other OS has a workaround for a broken
device.

-- 
B.Walter   BWCThttp://www.bwct.de
[EMAIL PROTECTED]  [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: TESTERS WANTED for ATAng preview 2

2003-08-18 Thread Radko Keves
;), Sat, Aug 16, 2003 at 10:06:02PM +0200, Soeren Schmidt said that
 The story continues with Preview 2 - from the README:
 
 Now the functionality is almost equal to that of stock ATA, I'm getting
 close to being ready to expose this on the -current users, so please
 give this a go to shake out the last nasties.
 I've fixed alot of minor issue that testers have reported back (thanks!!),
 plus a few chipset issued found over the last days.
 
 Grap the latest from ftp.deepcore.dk/pub/ATAng and apply the diff files 
 to your src tree, remove the contents of sys/dev/ata and extract the 
 ATAng-*tgz file there, then do the usual drill to get a new kernel...
 
 As usual it might kill your dog, abduct your kids and whatnot :)
 
 Let me know how this works out for you!
 -Søren

hi

sorry if i'm late :)

i attache my dmesg from:
Mon May 19 15:01:33 CEST 2003
(last when kernel found my disks)

current driver from cvs doesn't find any disk -- when try to mount root
:(
and when i use driver from ftp.deepcore.dk/pub/ATAng have found disks ...
but write message:
WARNING: READ_DMA unable to allocate interrupt
every second, and system was booting in the background, bud when try
to start shell i see only this message on the console

if i can help tell me what to do ...

-- 
Archeologists near mount Sinai have discovered what is believed to be a
  missing page from the Bible.  The page is currently being carbon dated
  in Bonn.  If genuine it belongs at the beginning of the Bible and is
  believed to read To my darling Candy.  All characters portrayed
  within  this book are fictitous and any resemblance to persons living 
  or dead is purely coincidental. The page has been universally 
  condemned by church leaders.

RED DWARF Series II Episode 2, Better Than Life
-
R
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-BETA #32: Mon May 19 15:01:33 CEST 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/angel
Preloaded elf kernel /boot.rado/kernel/kernel at 0xc04f8000.
Calibrating clock(s) ... i8254 clock: 1193063 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254  frequency 1193182 Hz
Calibrating TSC clock ... TSC clock: 927110285 Hz
Timecounter TSC  frequency 927110285 Hz
CPU: Intel Pentium III (927.11-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x68a  Stepping = 10
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 268435456 (256 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0051f000 - 0x0fb59fff, 258191360 bytes (63035 pages)
avail memory = 255422464 (243 MB)
bios32: Found BIOS32 Service Directory header at 0xc00fa000
bios32: Entry = 0xeca00 (c00eca00)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xeca00+0x1047
pnpbios: Found PnP BIOS data at 0xc00fe1c0
pnpbios: Entry = f:676c  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
npx0: math processor on motherboard
npx0: INT 16 interface
pci_open(1):mode 1 addr port (0x0cf8) is 0x8070
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=80] is there (id=00091166)
pcibios: BIOS version 2.10
Using $PIR table, 7 entries at 0xc00ede90
PCI-Only Interrupts: none
Location  Bus Device Pin  Link  IRQs
embedded0   15A   0x01  3 4 5 7 10 11 14 15
embedded0   15B   0xff  none
embedded0   15C   0xff  none
embedded0   15D   0xff  none
slot 1  52A   0x13  3 4 5 7 10 11 14 15
slot 1  52B   0x14  3 4 5 7 10 11 14 15
slot 1  52C   0x15  3 4 5 7 10 11 14 15
slot 1  52D   0x15  3 4 5 7 10 11 14 15
slot 2  51A   0x10  3 4 5 7 10 11 14 15
slot 2  51B   0x11  3 4 5 7 10 11 14 15
slot 2  51C   0x12  3 4 5 7 10 11 14 15
slot 2  51D   0x12  3 4 5 7 10 11 14 15
slot 3  01A   0x16  3 4 5 7 10 11 14 15
slot 3  01B   0x17  3 4 5 7 10 11 14 15
slot 3  01C   0x18  3 4 5 7 10 11 14 15
slot 3  01D   0x19  3 4 5 7 10 11 14 15
slot 4  02A   0x1a  3 4 5 7 10 11 14 15
slot 4  02B   0x1b  3 4 5 7 10 11 14 15
slot 4  02C   0x1a  3 4 5 7 10 11 14 15
slot 4  02D   0x1b  3 4 5 7 10 11 14 15
slot 5  03A   0x1c  3 4 5 7 10 11 14 15
slot 5  03B   0x1d  3 4 5 7 10 11 14 15
slot 5  03C   0x1c  3 4 5 7 10 11 14 15
slot 5  03D   0x1d  3 4 5 7 10 11 14 15
slot 6  04A   0x1e  3 4 5 7 10 11 14 15
slot 6  04B   0x1f  3 4 5 7 10 11 14 15
slot 6  04C   0x1e  3 4 5 7 10 11 14 15
slot 6  04D   0x1f  3 4 5 7 10 11 14 15

running config [kernel config file name] returns error

2003-08-18 Thread Kim Culhan

current as of ~1300 UTC 8-18:

running config [kernel config file name] returns:

config: GENERIC:74: devices with zero units are not likely to be correct

-kim

--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


repeatable ufs2 softupdate panic ffs_alloccg: map corrupted

2003-08-18 Thread Aaron Wohl
I got a couple of kernel crashes this morning when amanda tried to
allocate disk space.  I guessed which structure this was writing to,
unounted it and did a fsck -f -y on it.  Remounted it and all is happy
now.  It corrected three block counts that where off.  This was in 5.1
-current less than a week old

Shouldnt it have forced a regular fsck at boot time on its own?  Or how
come the background fsck didnt complain about it?

panic: ffs_alloccg: map corrupted
panic messages:
---
dmesg: kvm_read: 
---

warning: failed to read linker file data at 0xcc02aa00

#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) where
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1  0xc030bd6b in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:372
#2  0xc030c176 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3  0xc0352a71 in bremfreel (bp=0xd82a6628) at
/usr/src/sys/kern/vfs_bio.c:644
#4  0xc0352945 in bremfree (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:626
#5  0xc035c921 in vop_stdfsync (ap=0xe6d867c0) at
/usr/src/sys/kern/vfs_default.c:740
#6  0xc02d1870 in spec_fsync (ap=0xe6d867c0) at
/usr/src/sys/fs/specfs/spec_vnops.c:417
#7  0xc02d0b48 in spec_vnoperate (ap=0x0) at
/usr/src/sys/fs/specfs/spec_vnops.c:122
#8  0xc0428417 in ffs_sync (mp=0xcbda6400, waitfor=2, cred=0xc6752e80,
td=0xc05a3960) at vnode_if.h:627
#9  0xc0368c2b in sync (td=0xc05a3960, uap=0x0) at
/usr/src/sys/kern/vfs_syscalls.c:142
#10 0xc030b8bf in boot (howto=256) at
/usr/src/sys/kern/kern_shutdown.c:281
#11 0xc030c176 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#12 0xc0410e41 in ffs_mapsearch (fs=0xcc013800, cgp=0xdf15,
bpref=8589934592, allocsiz=8)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:2041
#13 0xc040f414 in ffs_alloccgblk (ip=0xcbdb06c0, bp=0xd82a6628,
bpref=120663592) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1405
#14 0xc040f043 in ffs_alloccg (ip=0xcbdb06c0, cg=1283, bpref=120663592,
size=16384) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1302
#15 0xc040e9f7 in ffs_hashalloc (ip=0xcbdb06c0, cg=1283, pref=0,
size=16384, allocator=0xc040eee0 ffs_alloccg)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:1155
#16 0xc040c8d7 in ffs_alloc (ip=0xcbdb06c0, lbn=274445, bpref=120663592,
size=16384, cred=0xcc2e9280, bnp=0xe6d86a58)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:157
#17 0xc04122c0 in ffs_balloc_ufs1 (vp=0xcb93e7fc, startoffset=0,
size=16384, cred=0xcc2e9280, flags=2130706432, bpp=0xe6d86b9c)
at /usr/src/sys/ufs/ffs/ffs_balloc.c:311
#18 0xc0429b67 in ffs_write (ap=0xe6d86be0) at
/usr/src/sys/ufs/ffs/ffs_vnops.c:698
#19 0xc0371183 in vn_write (fp=0xcc42bcc0, uio=0xe6d86c7c,
active_cred=0xcc2e9280, flags=0, td=0xcb907e40) at vnode_if.h:432
#20 0xc0333ce8 in dofilewrite (td=0xcb907e40, fp=0xcc42bcc0, fd=0,
buf=0x50238000, nbyte=0, offset=0, flags=0)
at /usr/src/sys/sys/file.h:249
#21 0xc0333b1e in write (td=0xcb907e40, uap=0xe6d86d10) at
/usr/src/sys/kern/sys_generic.c:330
#22 0xc0492253 in syscall (frame=
  {tf_fs = 47, tf_es = 47, tf_ds = -1078001617, tf_edi = 240, tf_esi
  = 4, tf_ebp = -1077938056, tf_isp = -422023820, tf_ebx =
  1208604828, tf_edx = 240, tf_ecx = 32768, tf_eax = 4, tf_trapno =
  22, tf_err = 2, tf_eip = 1209550783, tf_cs = 31, tf_eflags = 514,
  tf_esp = -1077938116, tf_ss = 47}) at
  /usr/src/sys/i386/i386/trap.c:1008
#23 0xc047988d in Xint0x80_syscall () at {standard input}:145
---Can't read userspace from dump, or kernel process---
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow Boot

2003-08-18 Thread Bill Moran
Andre Guibert de Bruet wrote:
What does pciconf -vl show on the affected machine(s)?
[EMAIL PROTECTED]:0:0:  class=0x06 card=0x chip=0x12378086 
rev=0x02 hdr=0x00
vendor   = 'Intel Corporation'
device   = '82440/1FX 440FX (Natoma) System Controller'
class= bridge
subclass = HOST-PCI
[EMAIL PROTECTED]:1:0:  class=0x060100 card=0x chip=0x70008086 rev=0x01 
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82371SB PIIX3 PCI-to-ISA Bridge (Triton II)'
class= bridge
subclass = PCI-ISA
[EMAIL PROTECTED]:1:1:  class=0x010180 card=0x chip=0x70108086 rev=0x00 
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82371SB PIIX3 IDE Interface (Triton II)'
class= mass storage
subclass = ATA
[EMAIL PROTECTED]:1:2:  class=0x0c0300 card=0x chip=0x70208086 rev=0x01 
hdr=0x00
vendor   = 'Intel Corporation'
device   = '82371SB PIIX3 USB Host Controller (Triton II)'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:10:0: class=0x02 card=0x100010b7 chip=0x920010b7 rev=0x74 
hdr=0x00
vendor   = '3COM Corp, Networking Division'
device   = '3C905C-TX Fast EtherLink for PC Management NIC'
class= network
subclass = ethernet
[EMAIL PROTECTED]:11:0: class=0x02 card=0x813910ec chip=0x813910ec rev=0x10 
hdr=0x00
vendor   = 'Realtek Semiconductor'
device   = 'RT8139 (A/B/C/8130) Fast Ethernet Adapter'
class= network
subclass = ethernet
[EMAIL PROTECTED]:12:0: class=0x03 card=0x47501002 chip=0x47501002 rev=0x5c 
hdr=0x00
vendor   = 'ATI Technologies'
device   = 'Rage 3D Pro PCI Graphics Accelerator'
class= display
subclass = VGA
e fu
Andre Guibert de Bruet | Enterprise Software Consultant 
Silicon Landmark, LLC. | http://siliconlandmark.com/


On Sun, 17 Aug 2003, Bill Moran wrote:


Mike Atamas wrote:

When my system boots it seems to stall when it gets here:

xa807,0xa400-0xa403,0xa000-0xa007 mem 0xe100-0xe10001ff irq 11 at device 11.
0 on pci1
ata2: at 0xe100 on atapci0
ata3: at 0xe100 on atapci0
It stalls for about 20-30 seconds and then continues booting. I can not figure out
what the problem is or how to solve it. Has anyone had similar issues.
I've seen this on various hardware.  I actually have a 200mhz machine sitting here
that has always done this.  I've never seen it cause any problems, and I've never
had any suggestions on how to stop it either.
My best guess is that the chipset responds slowly to probes, thus it takes a while
to get the list of devices from it.  However, I've never looked into it any more
than that.





--
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: USB Printer?

2003-08-18 Thread Daniel Nielsen
On 18/08-03 14.59, Bernd Walter wrote:
 On Mon, Aug 18, 2003 at 01:02:51PM +0200, Daniel Nielsen wrote:
  Hi.
  
  I installed 5.1-RELEASE on a compuiter with a nforce2 mobo, worked
  nice... Then I bought a Brother-5050 Laser printer
  (Postscript). Installed and configured cups. cups worked fine. Then I
  realized, the printer only works if it is turned on before my freebsd
  boots. 
  
  When I power it up, it is detected by the freebsd usb-system:
  
  zits root # dmesg | grep ulpt
  ulpt0: Brother HL-5050, rev 2.00/1.00, addr 3, iclass 7/1
  ulpt0: using bi-directional mode
  zits root #
  
  And when I turn it off:
  zits root # dmesg | grep ulpt
  snip
  ulpt0: at uhub0 port 2 (addr 3) disconnected
  ulpt0: detached
  zits root #
  
  but when I send a job to the printer, the CUPS usb backend just
  hangs, locking /dev/ulpt0
  
  I tried cat /root/some-file  /dev/ulpt0 , and it also just hangs. 
 
 /dev/ulpt0 shouldn't exist after ulpt0 was detached.

It doesn't... I wasn't being clear, I only try the cat thing after the
printer is attached and turned on.
 
  If the printer enters standby after boot, then it also doesn't print,
  with the same symptoms.
  
  I then tried upgrading to -CURRENT (about a week ago), but it still
  doesn't work. It works perfectly from Knoppix 3.2 and winXP, so I'm
  pretty sure it is a freeBSD usb problem. I should also mention, that
  I'm using a USB mouse, and it works fine even disconnecting and
  reconnecting after boot.
 
 That something work with another OS doesn't say anything about that it's
 an OS problem.
 It could also mean that the other OS has a workaround for a broken
 device.

That might be, I'm not an OS expert... Still doesn't change the fact
that it doesn't work in freeBSD though.

/Daniel

-- 
There are no great men, only great challenges that ordinary men are forced
by circumstances to meet.
-- Admiral William Halsey
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow Boot

2003-08-18 Thread Kevin Oberman
 Date: Mon, 18 Aug 2003 08:45:36 -0400
 From: Bill Moran [EMAIL PROTECTED]
 Sender: [EMAIL PROTECTED]
 
 Matthew D. Fuller wrote:
  On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
  Bill Moran, and lo! it spake thus:
  
 My best guess is that the chipset responds slowly to probes, thus it
 takes a while to get the list of devices from it.  However, I've never
 looked into it any more than that.
  
  I've always presumed it to be a question of timing out probes to the
  drives; it only ever happens on IDE controllers with no devices attached
  to 'em.  I habitually just disable the controller channels that are empty
  (or, in the case of my SCSI systems, just yank ATA support altogether).
 
 Could be.  This machine is pretty bare-bones.  Single ATA HDD and nothing
 on the secondary controller.  I never really considered that, but it makes
 sense that probes on the secondary controller would take the full timeout
 value if there was nothing to respond.

Nope. My system has disks on both ATA controllers with hard drives as
the master for each channel. One channel also has the CD drive as
the slave.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow Boot

2003-08-18 Thread Kevin Oberman
Andre Guibert de Bruet wrote:
 What does pciconf -vl show on the affected machine(s)?
[EMAIL PROTECTED]:0:0:  class=0x06 card=0x154110b9 chip=0x154110b9 rev=0x04 
hdr=0x00vendor   = 'Acer Labs Incorporated (ALi)'
device   = 'ALI M1541 Aladdin V/V+ AGP System Controller'
class= bridge
subclass = HOST-PCI
[EMAIL PROTECTED]:1:0: class=0x060400 card=0x00e0 chip=0x524310b9 rev=0x04 
hdr=0x01vendor   = 'Acer Labs Incorporated (ALi)'
device   = 'ALI M1541 PCI to AGP Bridge'
class= bridge
subclass = PCI-PCI
[EMAIL PROTECTED]:3:0: class=0x068000 card=0x710110b9 chip=0x710110b9 rev=0x00 
hdr=0x00vendor   = 'Acer Labs Incorporated (ALi)'
device   = 'ALI M7101 Power Management Controller'
class= bridge
subclass = PCI-unknown
[EMAIL PROTECTED]:7:0: class=0x060100 card=0x chip=0x153310b9 rev=0xc3 
hdr=0x00vendor   = 'Acer Labs Incorporated (ALi)'
device   = 'ALI M1533 Aladdin IV ISA Bridge'
class= bridge
subclass = PCI-ISA
[EMAIL PROTECTED]:9:0:  class=0x040100 card=0x13711274 chip=0x13711274 rev=0x08 
hdr=0x00vendor   = 'Creative (Was: Ensoniq)'
device   = 'ES1371, ES1373 AudioPCI'
class= multimedia
subclass = audio
[EMAIL PROTECTED]:11:0:  class=0x02 card=0x905510b7 chip=0x905510b7 rev=0x30 
hdr=0x00vendor   = '3COM Corp, Networking Division'
device   = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC'
class= network
subclass = ethernet
[EMAIL PROTECTED]:15:0:  class=0x01018a card=0x chip=0x522910b9 rev=0xc1 
hdr=0x00
vendor   = 'Acer Labs Incorporated (ALi)'
device   = 'M1543 Southbridge EIDE Controller'
class= mass storage
subclass = ATA
[EMAIL PROTECTED]:0:0: class=0x03 card=0x0338102b chip=0x0525102b rev=0x04 
hdr=0x00vendor   = 'Matrox Graphics Inc'
device   = 'MGA-G400/450 Chipset'
class= display
subclass = VGA
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


What is the actual status of Audigy2 support in 5.1-CURRENT?

2003-08-18 Thread Tom Parquette
Hi.

I would like to get an Audigy2 Platnum card working on my AMD dual 
processor system.  I'm 5.1-CURRENT but I tend to hang back a little.
I have device pcm and device sbc in the kernel.  When the system 
didn't figure out the card I added device firewire device sbp and 
device fwe to the kernel to see if the probes could figure out the 
firewire interface.

The system appears to locate the firewire components of the card.
It does not seem to understand the sound component.  I get the following 
at boot time:
pci2: multimedia, audio at device 5.0 (no driver attached)

I was following the discussion on the -current list about the Sound 
Blaster Audigy2 support.  I do not know if the discussion continued off 
list but I suspect it might have.

A dogpile search turned up a patch file  emu10k2.txt.  From the 
discussion thread in bsdforums I was unable to determine if this was the 
same patch file also mentioned in the -current mailing list threads. 
The first few lines of the patch file I have read:
diff -u old-emu10k1/emu10k1.c new-emu10k2/emu10k1.c
--- old-emu10k1/emu10k1.c   Mon Feb 10 03:01:34 2003
+++ new-emu10k2/emu10k1.c   Thu Feb 13 05:36:10 2003
@@ -1,4 +1,5 @@
 /*
+ * Copyright (c) 2003 Orlando Bassotto [EMAIL PROTECTED]

Whereis does not tell me the location of emu10k1.c.

Can someone in the know clear this up for me?
Thanks...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow Boot

2003-08-18 Thread Andre Guibert de Bruet

[CC list trimed]

On Mon, 18 Aug 2003, Kevin Oberman wrote:

  From: Bill Moran [EMAIL PROTECTED]
 
  Matthew D. Fuller wrote:
   On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
   Bill Moran, and lo! it spake thus:
  
  My best guess is that the chipset responds slowly to probes, thus it
  takes a while to get the list of devices from it.  However, I've never
  looked into it any more than that.
  
   I've always presumed it to be a question of timing out probes to the
   drives; it only ever happens on IDE controllers with no devices attached
   to 'em.  I habitually just disable the controller channels that are empty
   (or, in the case of my SCSI systems, just yank ATA support altogether).
 
  Could be.  This machine is pretty bare-bones.  Single ATA HDD and nothing
  on the secondary controller.  I never really considered that, but it makes
  sense that probes on the secondary controller would take the full timeout
  value if there was nothing to respond.

 Nope. My system has disks on both ATA controllers with hard drives as
 the master for each channel. One channel also has the CD drive as
 the slave.

Does the hard drive that's on it's own have a Single jumper
configuration option available?

 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]


Re: running config [kernel config file name] returns error

2003-08-18 Thread Kevin Oberman
 Date: Mon, 18 Aug 2003 09:52:03 -0400 (EDT)
 From: Kim Culhan [EMAIL PROTECTED]
 Sender: [EMAIL PROTECTED]
 
 
 current as of ~1300 UTC 8-18:
 
 running config [kernel config file name] returns:
 
 config: GENERIC:74: devices with zero units are not likely to be correct

OK, have you looked at the contents of GENERIC line 74? IT should be:
device   pci

There should be no unit numbers on anything in GENERIC and there are
none in the CVS version. It has not been touched since June 8, so it
looks like something touched your GENERIC.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: What is the actual status of Audigy2 support in 5.1-CURRENT?

2003-08-18 Thread Kevin Oberman
 Date: Mon, 18 Aug 2003 11:08:07 -0400
 From: Tom Parquette [EMAIL PROTECTED]
 Sender: [EMAIL PROTECTED]
 
 Hi.
 
 I would like to get an Audigy2 Platnum card working on my AMD dual 
 processor system.  I'm 5.1-CURRENT but I tend to hang back a little.
 I have device pcm and device sbc in the kernel.  When the system 
 didn't figure out the card I added device firewire device sbp and 
 device fwe to the kernel to see if the probes could figure out the 
 firewire interface.
 
 The system appears to locate the firewire components of the card.
 It does not seem to understand the sound component.  I get the following 
 at boot time:
 pci2: multimedia, audio at device 5.0 (no driver attached)
 
 I was following the discussion on the -current list about the Sound 
 Blaster Audigy2 support.  I do not know if the discussion continued off 
 list but I suspect it might have.
 
 A dogpile search turned up a patch file  emu10k2.txt.  From the 
 discussion thread in bsdforums I was unable to determine if this was the 
 same patch file also mentioned in the -current mailing list threads. 
 The first few lines of the patch file I have read:
 diff -u old-emu10k1/emu10k1.c new-emu10k2/emu10k1.c
 --- old-emu10k1/emu10k1.c   Mon Feb 10 03:01:34 2003
 +++ new-emu10k2/emu10k1.c   Thu Feb 13 05:36:10 2003
 @@ -1,4 +1,5 @@
   /*
 + * Copyright (c) 2003 Orlando Bassotto [EMAIL PROTECTED]
 
 Whereis does not tell me the location of emu10k1.c.
 
 Can someone in the know clear this up for me?

Can't say that I am in the know, but...
% locate emu10k1.c
/usr/src/sys/dev/sound/pci/emu10k1.c

In general, locate(1) is a much better tool for finding random source
files.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow Boot

2003-08-18 Thread Kevin Oberman
 Date: Mon, 18 Aug 2003 11:09:05 -0400 (EDT)
 From: Andre Guibert de Bruet [EMAIL PROTECTED]
 
 
 [CC list trimed]
 
 On Mon, 18 Aug 2003, Kevin Oberman wrote:
 
   From: Bill Moran [EMAIL PROTECTED]
  
   Matthew D. Fuller wrote:
On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
Bill Moran, and lo! it spake thus:
   
   My best guess is that the chipset responds slowly to probes, thus it
   takes a while to get the list of devices from it.  However, I've never
   looked into it any more than that.
   
I've always presumed it to be a question of timing out probes to the
drives; it only ever happens on IDE controllers with no devices attached
to 'em.  I habitually just disable the controller channels that are empty
(or, in the case of my SCSI systems, just yank ATA support altogether).
  
   Could be.  This machine is pretty bare-bones.  Single ATA HDD and nothing
   on the secondary controller.  I never really considered that, but it makes
   sense that probes on the secondary controller would take the full timeout
   value if there was nothing to respond.
 
  Nope. My system has disks on both ATA controllers with hard drives as
  the master for each channel. One channel also has the CD drive as
  the slave.
 
 Does the hard drive that's on it's own have a Single jumper
 configuration option available?

I'm not sure what a Single jumper is, but the drive is jumpered as
master. The only options are master, slave, and Cable Select.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Slow Boot

2003-08-18 Thread Andre Guibert de Bruet

On Mon, 18 Aug 2003, Kevin Oberman wrote:

  Date: Mon, 18 Aug 2003 11:09:05 -0400 (EDT)
  From: Andre Guibert de Bruet [EMAIL PROTECTED]
 
  On Mon, 18 Aug 2003, Kevin Oberman wrote:
 
From: Bill Moran [EMAIL PROTECTED]
   
Matthew D. Fuller wrote:
 On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
 Bill Moran, and lo! it spake thus:

My best guess is that the chipset responds slowly to probes, thus it
takes a while to get the list of devices from it.  However, I've never
looked into it any more than that.

 I've always presumed it to be a question of timing out probes to the
 drives; it only ever happens on IDE controllers with no devices attached
 to 'em.  I habitually just disable the controller channels that are empty
 (or, in the case of my SCSI systems, just yank ATA support altogether).
   
Could be.  This machine is pretty bare-bones.  Single ATA HDD and nothing
on the secondary controller.  I never really considered that, but it makes
sense that probes on the secondary controller would take the full timeout
value if there was nothing to respond.
  
   Nope. My system has disks on both ATA controllers with hard drives as
   the master for each channel. One channel also has the CD drive as
   the slave.
 
  Does the hard drive that's on it's own have a Single jumper
  configuration option available?

 I'm not sure what a Single jumper is, but the drive is jumpered as
 master. The only options are master, slave, and Cable Select.

It's a jumper configuration that's commonly found on Western Digital IDE
drives. It might also be labelled Master w/o slave.

Weirdness occurs (I've seen write errors and timeouts) when these drives
sit on an otherwise empty IDE channel while they are set as 'master'.

 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]


Re: running config [kernel config file name] returns error

2003-08-18 Thread Kim Culhan


On Mon, 18 Aug 2003, Kevin Oberman wrote:

 OK, have you looked at the contents of GENERIC line 74? IT should be:
 device pci

Jeez.. sorry about that. Wrong bits here. Duh.

-kc

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


[current tinderbox] failure on alpha/alpha

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 16:00:11 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-08-18 16:00:11 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 16:02:11 - building world
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
[...]
cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee 
-I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure/libexec/sftp-server/../../../crypto/openssh
 -DNO_IDEA  -o sftp-server sftp-common.o sftp-server.o -lssh -lcrypto
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/bin/ld:
 warning: libz.so.2, needed by 
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so,
 not found (try using -rpath or -rpath-link)
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `deflate'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `inflate'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateInit_'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateInit_'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateEnd'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateEnd'
*** Error code 1

Stop in 
/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure/libexec/sftp-server.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure/libexec.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src.
TB --- 2003-08-18 16:58:35 - /usr/bin/make returned exit code  1 
TB --- 2003-08-18 16:58:35 - ERROR: failed to build world
TB --- 2003-08-18 16:58:35 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


mergemaster b0rked?

2003-08-18 Thread Wilko Bulte
for i in answer  isdntel.sh  record
  tell tell-record unknown_incoming ; do
install -o  -g  -m 700 $i  /var/tmp/temproot/etc/isdn ;  done ;  for i in
holidays.Disdnd.rates.Aisdnd.rates.D   isdnd.rates.F
 isdnd.rates.L   isdnd.rates.UK.BT   isdnd.rc.sample
   isdntel.alias.sample ; do  install -o  -g  -m 600 $i
/var/tmp/temproot/etc/isdn ;  done
install: -g: Invalid argument
*** Error code 67

Stop in /usr/src/etc/isdn.
*** Error code 1

Stop in /usr/src/etc.

  *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
  the temproot environment

#

??

This is on Alpha btw.

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: What is the actual status of Audigy2 support in 5.1-CURRENT?

2003-08-18 Thread David O'Brien
On Mon, Aug 18, 2003 at 11:08:07AM -0400, Tom Parquette wrote:
 I would like to get an Audigy2 Platnum card working on my AMD dual 
 processor system.  I'm 5.1-CURRENT but I tend to hang back a little.
 I have device pcm and device sbc in the kernel.  When the system 
 didn't figure out the card I added device firewire device sbp and 
 device fwe to the kernel to see if the probes could figure out the 
 firewire interface.

I don't think you need device sbc -- I use only modules:

Id Refs AddressSize Name
 1   43 0xc010 31609c   kernel.ko
 51 0xc044 88b4 snd_emu10k1.ko
 62 0xc0449000 1d13csnd_pcm.ko
151 0xc0504000 14934firewire.ko

I use this uncommitted patch (I haven't been able to test it against
older SB Live! 128 cards):

Index: sys/dev/sound/pci/emu10k1.c
===
RCS file: /home/ncvs/src/sys/dev/sound/pci/emu10k1.c,v
retrieving revision 1.37
diff -u -r1.37 emu10k1.c
--- sys/dev/sound/pci/emu10k1.c 20 Apr 2003 09:07:14 -  1.37
+++ sys/dev/sound/pci/emu10k1.c 7 Jun 2003 21:19:50 -
@@ -1,4 +1,5 @@
 /*
+ * Copyright (c) 2003 Orlando Bassotto [EMAIL PROTECTED]
  * Copyright (c) 1999 Cameron Grant [EMAIL PROTECTED]
  * All rights reserved.
  *
@@ -27,6 +28,9 @@
 #include dev/sound/pcm/sound.h
 #include dev/sound/pcm/ac97.h
 #include gnu/dev/sound/pci/emu10k1.h
+#include gnu/dev/sound/pci/emu10k1-ac97.h
+#include gnu/dev/sound/pci/emu10k1-alsa.h
+#include dev/sound/pci/emu10k1.h
 
 #include pci/pcireg.h
 #include pci/pcivar.h
@@ -39,9 +43,25 @@
 #defineEMU10K1_PCI_ID  0x00021102
 #defineEMU10K2_PCI_ID  0x00041102
 #defineEMU_DEFAULT_BUFSZ   4096
-#defineEMU_CHANS   4
+#define EMU_MAX_CHANS  8
 #undef EMUDEBUG
 
+#defineEMUPAGESIZE 4096/* don't change */
+#defineMAXREQVOICES8
+#defineMAXPAGES(32768 * 64 / EMUPAGESIZE)  /* WAVEOUT_MAXBUFSIZE 
* NUM_G / EMUPAGESIZE */
+#defineRESERVED0
+#defineNUM_MIDI16
+#defineNUM_G   64  /* use all channels */
+#defineNUM_FXSENDS 4
+
+#defineTMEMSIZE256*1024
+#defineTMEMSIZEREG 4
+
+#defineENABLE  0x
+#defineDISABLE 0x
+#defineENV_ON  0x80
+#defineENV_OFF 0x00
+
 struct emu_memblk {
SLIST_ENTRY(emu_memblk) link;
void *buf;
@@ -63,6 +83,8 @@
int b16:1, stereo:1, busy:1, running:1, ismaster:1;
int speed;
int start, end, vol;
+   int fxrt1;  /* FX routing */
+   int fxrt2;  /* FX routing (only for audigy) */
u_int32_t buf;
struct emu_voice *slave;
struct pcm_channel *channel;
@@ -91,7 +113,8 @@
 struct sc_info {
device_tdev;
u_int32_t   type, rev;
-   u_int32_t   tos_link:1, APS:1;
+   u_int32_t   tos_link:1, APS:1, audigy:1, audigy2:1;
+   u_int32_t   addrmask;   /* wider if audigy */
 
bus_space_tag_t st;
bus_space_handle_t sh;
@@ -104,9 +127,10 @@
unsigned int bufsz;
int timer, timerinterval;
int pnum, rnum;
+   int nchans;
struct emu_mem mem;
struct emu_voice voice[64];
-   struct sc_pchinfo pch[EMU_CHANS];
+   struct sc_pchinfo pch[EMU_MAX_CHANS];
struct sc_rchinfo rch[3];
 };
 
@@ -166,6 +190,8 @@
 static struct pcmchan_caps emu_playcaps = {4000, 48000, emu_pfmt, 0};
 
 static int adcspeed[8] = {48000, 44100, 32000, 24000, 22050, 16000, 11025, 8000};
+/* audigy supports 12kHz. */
+static int audigy_adcspeed[9] = {48000, 44100, 32000, 24000, 22050, 16000, 12000, 
11025, 8000};
 
 /*  */
 /* Hardware */
@@ -205,7 +231,7 @@
 {
u_int32_t ptr, val, mask, size, offset;
 
-   ptr = ((reg  16)  PTR_ADDRESS_MASK) | (chn  PTR_CHANNELNUM_MASK);
+   ptr = ((reg  16)  sc-addrmask) | (chn  PTR_CHANNELNUM_MASK);
emu_wr(sc, PTR, ptr, 4);
val = emu_rd(sc, DATA, 4);
if (reg  0xff00) {
@@ -223,7 +249,7 @@
 {
u_int32_t ptr, mask, size, offset;
 
-   ptr = ((reg  16)  PTR_ADDRESS_MASK) | (chn  PTR_CHANNELNUM_MASK);
+   ptr = ((reg  16)  sc-addrmask) | (chn  PTR_CHANNELNUM_MASK);
emu_wr(sc, PTR, ptr, 4);
if (reg  0xff00) {
size = (reg  24)  0x3f;
@@ -239,7 +265,8 @@
 static void
 emu_wrefx(struct sc_info *sc, unsigned int pc, unsigned int data)
 {
-   emu_wrptr(sc, 0, MICROCODEBASE + pc, data);
+   pc += sc-audigy ? AUDIGY_CODEBASE : MICROCODEBASE;
+   emu_wrptr(sc, 0, pc, data);
 }
 
 /*  */
@@ -282,7 +309,7 @@
int i, tmp, rate;
 
rate = 0;
-   for (i = 0; i  EMU_CHANS; i++) {
+   for (i = 0; i  sc-nchans; i++) {
   

[current tinderbox] failure on amd64/amd64

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 16:58:35 - starting CURRENT tinderbox run for amd64/amd64
TB --- 2003-08-18 16:58:35 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 17:00:26 - building world
TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
[...]
cc -O -pipe  
-I/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/secure/libexec/sftp-server/../../../crypto/openssh
 -DNO_IDEA  -o sftp-server sftp-common.o sftp-server.o -lssh -lcrypto
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/bin/ld:
 warning: libz.so.2, needed by 
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libssh.so,
 not found (try using -rpath or -rpath-link)
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflate'
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflate'
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateInit_'
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateInit_'
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateEnd'
/home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateEnd'
*** Error code 1

Stop in 
/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/secure/libexec/sftp-server.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/secure/libexec.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/secure.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src.
TB --- 2003-08-18 17:53:08 - /usr/bin/make returned exit code  1 
TB --- 2003-08-18 17:53:08 - ERROR: failed to build world
TB --- 2003-08-18 17:53:08 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: USB Printer?

2003-08-18 Thread Bernd Walter
On Mon, Aug 18, 2003 at 04:53:29PM +0200, Daniel Nielsen wrote:
 On 18/08-03 14.59, Bernd Walter wrote:
  On Mon, Aug 18, 2003 at 01:02:51PM +0200, Daniel Nielsen wrote:
   Hi.
   
   I installed 5.1-RELEASE on a compuiter with a nforce2 mobo, worked
   nice... Then I bought a Brother-5050 Laser printer
   (Postscript). Installed and configured cups. cups worked fine. Then I
   realized, the printer only works if it is turned on before my freebsd
   boots. 
   
   When I power it up, it is detected by the freebsd usb-system:
   
   zits root # dmesg | grep ulpt
   ulpt0: Brother HL-5050, rev 2.00/1.00, addr 3, iclass 7/1
   ulpt0: using bi-directional mode
   zits root #
   
   And when I turn it off:
   zits root # dmesg | grep ulpt
   snip
   ulpt0: at uhub0 port 2 (addr 3) disconnected
   ulpt0: detached
   zits root #
   
   but when I send a job to the printer, the CUPS usb backend just
   hangs, locking /dev/ulpt0
   
   I tried cat /root/some-file  /dev/ulpt0 , and it also just hangs. 
  
  /dev/ulpt0 shouldn't exist after ulpt0 was detached.
 
 It doesn't... I wasn't being clear, I only try the cat thing after the
 printer is attached and turned on.

What does ps -axl say.
What kind of USB controller do you have?
Are other full-speed USB devices working on this usb controller (mices
are often low speed)?

-- 
B.Walter   BWCThttp://www.bwct.de
[EMAIL PROTECTED]  [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


64 bit quantities in statfs ?

2003-08-18 Thread Matthew Dillon
As part of the DragonFly effort we are going to increase the 
mount path limit from 80 chars to 1024.

This will change the statfs structure.  I thought I would adopt the
64 bit changes that 5.x has made to keep things synchronized.

Except... there don't appear to be any 64 bit changes to struct
statfs in 5.x.  Am I missing something here?  Is there an 'nstatfs'
structure that I have not seen?  The following probably need to be 64
bit entries:

f_blocks
f_bfree
f_bavail
f_files
f_ffree
f_syncwrites
f_asyncwrites
f_syncreads
f_asyncreads

-Matt
Matthew Dillon 
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


[current tinderbox] failure on i386/i386

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 17:53:08 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-08-18 17:53:08 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 17:55:19 - building world
TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
TB --- 2003-08-18 18:54:17 - building generic kernel
TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src
TB --- /usr/bin/make buildkernel KERNCONF=GENERIC
 Kernel build for GENERIC started on Mon Aug 18 18:54:17 GMT 2003
[...]
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/fs/procfs/procfs_status.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/fs/procfs/procfs_type.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/fs/pseudofs/pseudofs.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/fs/pseudofs/pseudofs_fileno.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/dev 

[current tinderbox] failure on i386/pc98

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 18:59:05 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-08-18 18:59:05 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 19:01:01 - building world
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
TB --- 2003-08-18 20:00:11 - building generic kernel
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src
TB --- /usr/bin/make buildkernel KERNCONF=GENERIC
 Kernel build for GENERIC started on Mon Aug 18 20:00:11 GMT 2003
[...]
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/fs/procfs/procfs_status.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/fs/procfs/procfs_type.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/fs/pseudofs/pseudofs.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd 
-D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/fs/pseudofs/pseudofs_fileno.c
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys 
-I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev 

Re: What is the actual status of Audigy2 support in 5.1-CURRENT?

2003-08-18 Thread Arjan van Leeuwen
On Monday 18 August 2003 18:37, David O'Brien wrote:
snip
 I use this uncommitted patch (I haven't been able to test it against
 older SB Live! 128 cards):
snip

On http://chibis.persons.gfk.ru/audigy/, Yuriy Tsibizov claims that his 
patches work with both the SB Live! and the Audigy.

If there are so many working patches around, isn't it time that one of them 
gets in the tree? What is the problem here?

Arjan

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: mergemaster b0rked?

2003-08-18 Thread Andre Guibert de Bruet

On Mon, 18 Aug 2003, Wilko Bulte wrote:

 for i in answer  isdntel.sh  record
   tell tell-record unknown_incoming ; do
 install -o  -g  -m 700 $i  /var/tmp/temproot/etc/isdn ;  done ;  for i in
 holidays.Disdnd.rates.Aisdnd.rates.D   isdnd.rates.F
  isdnd.rates.L   isdnd.rates.UK.BT   isdnd.rc.sample
isdntel.alias.sample ; do  install -o  -g  -m 600 $i
 /var/tmp/temproot/etc/isdn ;  done
 install: -g: Invalid argument
 *** Error code 67

 Stop in /usr/src/etc/isdn.
 *** Error code 1

 Stop in /usr/src/etc.

   *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
   the temproot environment

 #

I'm seeing this too. I've cvsup'ed and rebuilt world (making sure that
mergemaster was rebuilt) and it still occurs.

 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]


Re: mergemaster b0rked?

2003-08-18 Thread Craig Rodrigues
On Mon, Aug 18, 2003 at 07:05:54PM +0200, Wilko Bulte wrote:
 for i in answer  isdntel.sh  record
   tell tell-record unknown_incoming ; do
 install -o  -g  -m 700 $i  /var/tmp/temproot/etc/isdn ;  done ;  for i in
  ^^  

Why doesn't the -g flag have a GID as an argument? 

 install: -g: Invalid argument
 *** Error code 67

-- 
Craig Rodrigues
http://crodrigues.org
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: running config [kernel config file name] returns error

2003-08-18 Thread Kris Kennaway
On Mon, Aug 18, 2003 at 09:52:03AM -0400, Kim Culhan wrote:
 
 current as of ~1300 UTC 8-18:
 
 running config [kernel config file name] returns:
 
 config: GENERIC:74: devices with zero units are not likely to be correct

You're probably not using a 5.x GENERIC config.

Kris


pgp0.pgp
Description: PGP signature


Re: mergemaster b0rked?

2003-08-18 Thread Wilko Bulte
On Mon, Aug 18, 2003 at 04:19:22PM -0400, Craig Rodrigues wrote:
 On Mon, Aug 18, 2003 at 07:05:54PM +0200, Wilko Bulte wrote:
  for i in answer  isdntel.sh  record
tell tell-record unknown_incoming ; do
  install -o  -g  -m 700 $i  /var/tmp/temproot/etc/isdn ;  done ;  for i in
   ^^  
 
 Why doesn't the -g flag have a GID as an argument? 

Because it seems that BINGRP and BINOWNER are undefined.

  install: -g: Invalid argument
  *** Error code 67
 
 -- 
 Craig Rodrigues
 http://crodrigues.org
 [EMAIL PROTECTED]
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
---end of quoted text---

-- 
|   / o / /_  _ [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


mksnap_ffs, snapshot issues, again

2003-08-18 Thread Branko F . Granar
I have 900G array on a promise sx6000 controller

This is freshly formatted filesystem (newfs -L export -O 2 -U -g 48000 -i 2048 -m 0 -o 
space /dev/pst0s2d)

# df -i /export
/dev/pst0s2d 778742004 216194 778525810 0%   2 4451592920%   /export

# mount | grep export
/dev/pst0s2d on /export (ufs, local, soft-updates)

let's try to create a snapshot of empty filesystem

# cd /export
# mksnap_ffs /export aaa.snap

... after 30 minutes ... snapshot was not created (!!! On a empty filesystem !!!)... 
Ok, long snapshot creation would be fine if it would not hang all processes, which 
would like to do something on /export (ls /export for example.). Filesystem cannot be 
unmounted. mksnap_ffs process cannot be killed. Reboot and foreground fsck helps.

This is 5.1-RELEASE (without patches, with custom kernel - just picked up generic 
kernel and removed uneeded stuff.)

Any ideas, why is this happening? As i mentioned before, this prevents background fsck 
to make his job done (machine hangs.)


I would really like to solve this issue

Brane
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


[current tinderbox] failure on ia64/ia64

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 20:03:44 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-08-18 20:03:44 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 20:06:22 - building world
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
[...]
cc -O -pipe  
-I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure/libexec/sftp-server/../../../crypto/openssh
 -DNO_IDEA  -o sftp-server sftp-common.o sftp-server.o -lssh -lcrypto
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/bin/ld:
 warning: libz.so.2, needed by 
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so,
 not found (try using -rpath or -rpath-link)
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflate'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflate'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateInit_'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateInit_'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateEnd'
/home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateEnd'
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure/libexec/sftp-server.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure/libexec.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/secure.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src.
TB --- 2003-08-18 21:02:26 - /usr/bin/make returned exit code  1 
TB --- 2003-08-18 21:02:26 - ERROR: failed to build world
TB --- 2003-08-18 21:02:26 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Lot's of SIGILL, SIGSEGV

2003-08-18 Thread Pawel Jakub Dawidek
On Sun, Aug 17, 2003 at 08:00:54PM -0700, David O'Brien wrote:
+  This is a FAQ. In the future, please search the archives before posting.
+  
+  At this moment in time, 'p4' isn't a safe CPUTYPE (It produces broken
+  code). 'p3' or 'i686' are what's recommended for Pentium 4s.
+ 
+ Andre, I think you are out of date -- CPUTYPE=p4 is now safe with GCC
+ 3.3.1.

I think he is right, because when upgrading host where was gcc3.2 to
current -CURRENT (with gcc3.3) 'make world' builds make(1) in first
place and it is builded by gcc3.2 with CPUTYPE=p4, so it will be broken.

So gcc have to be upgraded in first place (with CPUTYPE=p3).

-- 
Pawel Jakub Dawidek   [EMAIL PROTECTED]
UNIX Systems Programmer/Administrator http://garage.freebsd.pl
Am I Evil? Yes, I Am! http://cerber.sourceforge.net


pgp0.pgp
Description: PGP signature


[current tinderbox] failure on sparc64/sparc64

2003-08-18 Thread Tinderbox
TB --- 2003-08-18 21:02:26 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-08-18 21:02:26 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-18 21:05:27 - building world
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
[...]
cc -O -pipe  
-I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure/libexec/sftp-server/../../../crypto/openssh
 -DNO_IDEA  -o sftp-server sftp-common.o sftp-server.o -lssh -lcrypto
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/bin/ld:
 warning: libz.so.2, needed by 
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so,
 not found (try using -rpath or -rpath-link)
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflate'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflate'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateInit_'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateInit_'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateEnd'
/home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateEnd'
*** Error code 1

Stop in 
/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure/libexec/sftp-server.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure/libexec.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/secure.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src.
TB --- 2003-08-18 21:54:31 - /usr/bin/make returned exit code  1 
TB --- 2003-08-18 21:54:31 - ERROR: failed to build world
TB --- 2003-08-18 21:54:31 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: What is the actual status of Audigy2 support in 5.1-CURRENT?

2003-08-18 Thread David O'Brien
On Mon, Aug 18, 2003 at 09:47:00PM +0200, Arjan van Leeuwen wrote:
 On Monday 18 August 2003 18:37, David O'Brien wrote:
 snip
  I use this uncommitted patch (I haven't been able to test it against
  older SB Live! 128 cards):
 snip
 
 On http://chibis.persons.gfk.ru/audigy/, Yuriy Tsibizov claims that his 
 patches work with both the SB Live! and the Audigy.
 
 If there are so many working patches around, isn't it time that one of them 
 gets in the tree? What is the problem here?

I haven't check his in a while, but many of the patches running around
are a complete rewrite of the emu10k driver.  Not being a sound device
driver guy, I personally am not willing to commit a complete rewrite.  I
am willing to champion and commit patches that keep to the existing driver
and only adds Audgy2 support.  Unfortunately those in-the-know that are
writing Audgy2 support aren't keeping to this restriction.  If my posted
patches were known to work on SB Live! 128, I'd commit them as I can
follow them enough to understand the changes.
 
-- 
-- David  ([EMAIL PROTECTED])
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


bluetooth working on 5.1-current

2003-08-18 Thread Kim Culhan

Greetings Max  current-

Thanks muchly for your fine work.. bluetooth is working
very well on -current of ~2100 UTC 8-18.

-kim

--
[EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: an driver / Cisco Aironet 340 stopped working

2003-08-18 Thread Tomi Vainio - Sun Finland
Peter Radcliffe writes:
  
  Have you got recent firmware on the cisco card ? The newer windows
  driver will helpfully upgrade it for you silently. If it has
  upgraded, downgrade it. The freebsd driver doesn't yet work with the
  new firmware.
  
  Cisco have changed the operation of the card with newer firmware and
  havn't released docs on working with the newer firmware.
  
[EMAIL PROTECTED] writes:
  Don't know if anyone replied yet since I don't subscribe to
  freebsd-current, but I had to add the following line to my
  /boot/loader.conf file.
  
  hw.pci.allow_unsupported_io_range=1
  
I've tried multiple old firmwares and this loader.conf tweak but no
luck yet.  Can you say what was the last working firmware?

  Tomppa
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: an driver / Cisco Aironet 340 stopped working

2003-08-18 Thread Peter Radcliffe
Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said:
 Peter Radcliffe writes:
   Cisco have changed the operation of the card with newer firmware and
   havn't released docs on working with the newer firmware.

 I've tried multiple old firmwares and this loader.conf tweak but no
 luck yet.  Can you say what was the last working firmware?

I don't have any 340 cards, just 350 cards, so no.

P.

-- 
pir[EMAIL PROTECTED] [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: an driver / Cisco Aironet 340 stopped working

2003-08-18 Thread Tomi Vainio - Sun Finland
Peter Radcliffe writes:
  Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said:
   Peter Radcliffe writes:
 Cisco have changed the operation of the card with newer firmware and
 havn't released docs on working with the newer firmware.
  
   I've tried multiple old firmwares and this loader.conf tweak but no
   luck yet.  Can you say what was the last working firmware?
  
  I don't have any 340 cards, just 350 cards, so no.
 
Firmware files are the same for both cards or that's my thought from
this filename.

350-340-PCMCIA-LMC-PCI-v52017.exe

  Tomppa
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: an driver / Cisco Aironet 340 stopped working

2003-08-18 Thread Peter Radcliffe
Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said:
 Firmware files are the same for both cards or that's my thought from
 this filename.
 350-340-PCMCIA-LMC-PCI-v52017.exe

The firmware/driver files I have are labelled 350 only.

350 firmware 5.02.19 does not work. 5.00.03 does work.

P.

-- 
pir[EMAIL PROTECTED] [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: mksnap_ffs, snapshot issues, again

2003-08-18 Thread Kris Kennaway
On Mon, Aug 18, 2003 at 10:38:47PM +0200, Branko F. Gra?nar wrote:

 # mksnap_ffs /export aaa.snap
 
 ... after 30 minutes ... snapshot was not created (!!! On a empty
 filesystem !!!)... Ok, long snapshot creation would be fine if it
 would not hang all processes, which would like to do something on
 /export (ls /export for example.). Filesystem cannot be
 unmounted. mksnap_ffs process cannot be killed. Reboot and
 foreground fsck helps.

Please wrap your lines at 70 characters so your emails can be easily read.

The behaviour of filesystem activity stalling during snapshot creation
is intentional, but 30 minutes to snapshot an empty FS is not.  Is
there disk activity during this time?  It's not clear from your mail
whether bg fsck is in operation during this time.  If so, that's
probably the cause, since bg fsck itself uses a snapshot to check the
FS consistency.

Kris


pgp0.pgp
Description: PGP signature


Re: HEADS UP: dynamic root support now in the tree

2003-08-18 Thread Gordon Tetlow
On Sun, Aug 17, 2003 at 06:48:23PM -0700, David O'Brien wrote:
 On Sun, Aug 17, 2003 at 01:54:38AM -0700, Gordon Tetlow wrote:
  I just got through with my commit spree to enable users to build /bin
  and /sbin dynamically linked. To do this required a fair amount of
  tweaking and moving around libraries and such dangerous equipment as
 
 I think this is a more correct way to change the install locations of the
 / needed libs.  Your current way makes the real location a 2nd class
 citizen vs. /usr/lib for any needed compatibility links.
 
 I'd like to commit this:

[snip patch changing SHLIBDIR to LIBDIR]

I think this is a bad idea because all of the .a archives will end up in
/lib. Seeing how those aren't necessary for running binaries in /bin and
/sbin, I'd rather they stay in /usr/lib (which means LIBDIR shouldn't
change if I'm reading the Makefile glue correctly).

-gordon


pgp0.pgp
Description: PGP signature


Re: TESTERS WANTED for ATAng preview 2

2003-08-18 Thread Jason Stone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


  Grap the latest from ftp.deepcore.dk/pub/ATAng and apply the diff files
  to your src tree, remove the contents of sys/dev/ata and extract the
  ATAng-*tgz file there, then do the usual drill to get a new kernel...

Tried to grab this last night, but got 550 conf-patch: Permission denied.
when trying to retrieve conf-patch.


 current driver from cvs doesn't find any disk -- when try to mount root
 :(

I'm also having a problem with the -current ata driver.  I have an smp
system with an offboard promise ide card, and when I build an smp kernel,
the ide drives do not get detected.  If I take smp out of the kernel
though, the drives get detected fine.  Anyone know why this might be?

dmesg's are below as a unified diff between the non-smp kernel and the smp
kernel.


 -Jason

 --
 Freud himself was a bit of a cold fish, and one cannot avoid the suspicion
 that he was insufficiently fondled when he was an infant.
-- Ashley Montagu



- --- dmesg.up  Sat Aug  9 01:38:11 2003
+++ dmesg.smp   Fri Aug  8 05:11:04 2003
@@ -1,99 +1,107 @@
 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 Aug  8 03:06:30 PDT 2003
+FreeBSD 5.1-CURRENT #1: Fri Aug  8 04:15:59 PDT 2003
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/JKERN
- -Preloaded elf kernel /boot/kernel/kernel at 0xc052c000.
+Preloaded elf kernel /boot/kernel/kernel at 0xc0546000.
 Timecounter i8254  frequency 1193182 Hz
 CPU: Pentium II/Pentium II Xeon/Celeron (350.80-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x652  Stepping = 2
   
Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
 real memory  = 268435456 (256 MB)
- -avail memory = 255090688 (243 MB)
+avail memory = 254971904 (243 MB)
+Programming 24 pins in IOAPIC #0
+IOAPIC #0 intpin 2 - irq 0
+IOAPIC #0 intpin 16 - irq 10
+IOAPIC #0 intpin 17 - irq 11
+IOAPIC #0 intpin 19 - irq 9
+FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
+ cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
+ cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
+ io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
 Pentium Pro MTRR support enabled
 npx0: math processor on motherboard
 npx0: INT 16 interface
 pcibios: BIOS version 2.10
 pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard
 pci0: PCI bus on pcib0
 pcib1: PCI-PCI bridge at device 1.0 on pci0
 pci1: PCI bus on pcib1
 pci1: display, VGA at device 0.0 (no driver attached)
 isab0: PCI-ISA bridge at device 7.0 on pci0
 isa0: ISA bus on isab0
 atapci0: Intel PIIX4 UDMA33 controller port 0xffa0-0xffaf at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xef40-0xef5f irq 9 at device 
7.2 on pci0
 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
 usb0: USB revision 1.0
 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 uscanner0: Hewlett-Packard HP ScanJet 5200C, rev 1.00/1.00, addr 2
- -pci0: bridge, PCI-unknown at device 7.3 (no driver attached)
+piix0 port 0x440-0x44f at device 7.3 on pci0
+Timecounter PIIX  frequency 3579545 Hz
 atapci1: Promise PDC20262 UDMA66 controller port 
0xef00-0xef3f,0xefa8-0xefab,0xefa0-0xefa7,0xefac-0xefaf,0xefe0-0xefe7 mem 
0xfebc-0xfebd irq 11 at device 13.0 on pci0
 ata2: at 0xefe0 on atapci1
 ata3: at 0xefa0 on atapci1
 ahc0: Adaptec 2940 Ultra SCSI adapter port 0xe800-0xe8ff mem 0xfebff000-0xfebf 
irq 10 at device 15.0 on pci0
 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
 pcm0: Creative EMU10K1 port 0xef80-0xef9f irq 11 at device 16.0 on pci0
 pcm0: TriTech TR28602 AC97 Codec
 dc0: 82c169 PNIC 10/100BaseTX port 0xe400-0xe4ff mem 0xfebfef00-0xfebfefff irq 11 
at device 18.0 on pci0
 dc0: Ethernet address: 00:a0:cc:40:8e:3e
 miibus0: MII bus on dc0
 bmtphy0: BCM5201 10/100baseTX PHY on miibus0
 bmtphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 pci0: multimedia, video at device 20.0 (no driver attached)
 pci0: multimedia at device 20.1 (no driver attached)
 orm0: Option ROMs at iomem 0xd0800-0xd1fff,0xcc000-0xd07ff,0xc-0xca7ff on isa0
 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
 kbd0 at atkbd0
 psm0: PS/2 Mouse irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: 1440-KB 3.5 drive on fdc0 drive 0
 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO 

Re: TESTERS WANTED for ATAng preview 2

2003-08-18 Thread Steve Ames
On Mon, Aug 18, 2003 at 05:28:48PM -0700, Jason Stone wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
   Grap the latest from ftp.deepcore.dk/pub/ATAng and apply the diff files
   to your src tree, remove the contents of sys/dev/ata and extract the
   ATAng-*tgz file there, then do the usual drill to get a new kernel...
 
 Tried to grab this last night, but got 550 conf-patch: Permission denied.
 when trying to retrieve conf-patch.

I don't think the 8-16 patch requires conf-patch... that was for the
8-7 and 8-8 patches. Looks like it was split into three seperate
diff files for 8-16. I wasn't able to apply diff-sbin-atacontrol
successfully (well the diff applies but there was some devel stuff
in there that keeps it from compiling).

-Steve

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


ACPI on Tyan Motherboard

2003-08-18 Thread Stephen Montgomery-Smith
I have a Tyan S2462 Thunder K7 motherboard.  I was hoping to get power-down to
work.  So I installed FreeBSD current with ACPI enabled.  When I typed shutdown 
-p now the computer halted, and then the video card switched off, and the fans 
kept running.  The computer was frozen - even the power-off power-on button 
wouldn't work.

Actually the power-off button doesn't work at all under FreeBSD-current.  (It is 
a soft power-off button that dmesg shows is detected by the OS.)

I should add that power-down works great with Windows 2000.  Also, the power-off 
button works properly with FreeBSD-stable.

I am thinking that maybe I need to wait a few more months until ACPI is fully 
debugged.  On the other hand, maybe you guys would like to work on this.  I can 
send all info like dmesg, and the kernel configuration (which is basically 
GENERIC with stuff removed, and SMP and pcm added, but actually it didn't work 
with the generic kernel either.)

Is it possible that power is cut to the CPU's, but not to the fans?  Is there 
anyway to tell?

Will I have to program the ACPI (that is take the output of acpidump and edit it)?

It does seem to me that ACPI is working in some form, just not properly.  If I 
boot up with ACPI disabled, then it works just as in FreeBSD-stable, that is, 
the power-off button works well.

--
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


LOR with page queue mutex and vm object

2003-08-18 Thread Kris Kennaway
I got this on alpha just now (kernel updated 2 days ago, filesystems
created with -b 32768 -f 4096 to test reports of panics with these
settings, which may or may not be relevant).  I don't think I've seen
this trace before...apologies if it's another false positive.

Kris

 1st 0xfc6e48d0 vm page queue mutex (vm page queue mutex) @ 
/a/asami/portbuild/alpha/src-client/sys/vm/vm_pageout.c:405
 2nd 0xfc0005102e00 vm object (vm object) @ 
/a/asami/portbuild/alpha/src-client/sys/kern/vfs_bio.c:2280
Stack backtrace:
db_print_backtrace() at db_print_backtrace+0x18
backtrace() at backtrace+0x2c
witness_lock() at witness_lock+0x6fc
_mtx_lock_flags() at _mtx_lock_flags+0xc8
vfs_setdirty() at vfs_setdirty+0x7c
bdwrite() at bdwrite+0x3b8
ffs_update() at ffs_update+0x388
ufs_inactive() at ufs_inactive+0x254
ufs_vnoperate() at ufs_vnoperate+0x2c
vput() at vput+0x170
vm_pageout_scan() at vm_pageout_scan+0x7ac
vm_pageout() at vm_pageout+0x3ac
fork_exit() at fork_exit+0x100
exception_return() at exception_return
-


pgp0.pgp
Description: PGP signature


Re: ACPI on Tyan Motherboard

2003-08-18 Thread David Xu
I have similar problem,  FreeBSD ACPI never work for my Tyan Tiger 230T,
halt -p does not work after I have run the machine for about 10 minutes,
it works if I just power on FreeBSD and then type halt -p immediately,
after power off, NUM LOCK LED on keyboard is still light,  it seems it is not
fully shutdown.

David Xu

- Original Message - 
From: Stephen Montgomery-Smith [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 19, 2003 10:13 AM
Subject: ACPI on Tyan Motherboard


 I have a Tyan S2462 Thunder K7 motherboard.  I was hoping to get power-down to
 work.  So I installed FreeBSD current with ACPI enabled.  When I typed shutdown 
 -p now the computer halted, and then the video card switched off, and the fans 
 kept running.  The computer was frozen - even the power-off power-on button 
 wouldn't work.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: an driver / Cisco Aironet 340 stopped working

2003-08-18 Thread Doug Ambrisko
Tomi Vainio - Sun Finland writes:
| I've used my Cisco WLAN with Toshiba Portege 3440 couple years but now
| it's broken.  I just upgraded to new Toshiba Tecra M1 and reinstalled
| FreeBSD there and now I get an0: record length mismatch -- expected
| 430, got 440 for Rid ff68 errors.  I already tried with old laptop
| with latest kernel and old kernel from Jun 26th but it's also broken
| there so I cannot say who long this has been broken.

I assume you are using a pccard version.

It only a problem newer firmware.  It works ... just noisy!

You can try this patch to -current that should make it quiet.
There is a bug with -current and setting the TX speed that I need
to work on.  Looks like things changed in the wlan module.
I may commit this but there is an issue with the mpi-350 support.
They changed the programing paradigm and after 14 packets the 
TX engine stalls.  I'm still working on tweaks to that.
I had hoped to get that working and commit all of this.

Let me know how this works.  It should just work.

Doug A.

Index: sys/dev/an/if_aironet_ieee.h
===
RCS file: /cvs/src/sys/dev/an/if_aironet_ieee.h,v
retrieving revision 1.11
diff -c -r1.11 if_aironet_ieee.h
*** sys/dev/an/if_aironet_ieee.h29 Dec 2002 19:22:06 -  1.11
--- sys/dev/an/if_aironet_ieee.h19 Aug 2003 02:41:06 -
***
*** 63,69 
   * data, which is 240 words long, so 256 should be a safe
   * value.
   */
! #define AN_MAX_DATALEN512
  
  struct an_req {
u_int16_t   an_len;
--- 63,69 
   * data, which is 240 words long, so 256 should be a safe
   * value.
   */
! #define AN_MAX_DATALEN4096
  
  struct an_req {
u_int16_t   an_len;
***
*** 261,267 
u_int32_t   an_uptime_usecs;/* 0x178 */
u_int32_t   an_uptime_secs; /* 0x17C */
u_int32_t   an_lostsync_better_ap;  /* 0x180 */
!   u_int32_t   an_rsvd[10];
  };
  
  /*
--- 261,267 
u_int32_t   an_uptime_usecs;/* 0x178 */
u_int32_t   an_uptime_secs; /* 0x17C */
u_int32_t   an_lostsync_better_ap;  /* 0x180 */
!   u_int32_t   an_rsvd[15];
  };
  
  /*
***
*** 337,342 
--- 337,343 
u_int8_tan_magic_packet_action; /* 0x98 */
u_int8_tan_magic_packet_ctl;/* 0x99 */
u_int16_t   an_rsvd9;
+   u_int16_t   an_spare[13];
  };
  
  #define AN_OPMODE_IBSS_ADHOC  0x
***
*** 417,422 
--- 418,435 
charan_ssid3[32];
  };
  
+ struct an_ltv_ssid_entry{
+   u_int16_t   an_len;
+   charan_ssid[32];
+ };
+ 
+ #define MAX_SSIDS 25
+ struct an_ltv_ssidlist_new {
+   u_int16_t   an_len;
+   u_int16_t   an_type;
+   struct an_ltv_ssid_entry an_entry[MAX_SSIDS];
+ };
+ 
  /*
   * Valid AP list.
   */
***
*** 501,507 
u_int16_t   an_softcaps;/* 0x7C */
u_int16_t   an_bootblockrev;/* 0x7E */
u_int16_t   an_req_hw_support;  /* 0x80 */
!   u_int16_t   an_unknown; /* 0x82 */
  };
  
  /*
--- 514,520 
u_int16_t   an_softcaps;/* 0x7C */
u_int16_t   an_bootblockrev;/* 0x7E */
u_int16_t   an_req_hw_support;  /* 0x80 */
!   u_int16_t   an_unknown[31]; /* 0x82 */
  };
  
  /*
***
*** 580,586 
u_int8_tan_avg_noise_prev_min_db;   /* 0x7D */
u_int8_tan_max_noise_prev_min_pc;   /* 0x7E */
u_int8_tan_max_noise_prev_min_db;   /* 0x7F */
!   u_int16_t   an_spare[5];
  };
  
  #define AN_STATUS_OPMODE_CONFIGURED   0x0001
--- 593,599 
u_int8_tan_avg_noise_prev_min_db;   /* 0x7D */
u_int8_tan_max_noise_prev_min_pc;   /* 0x7E */
u_int8_tan_max_noise_prev_min_db;   /* 0x7F */
!   u_int16_t   an_spare[8];
  };
  
  #define AN_STATUS_OPMODE_CONFIGURED   0x0001
Index: sys/dev/an/if_an.c
===
RCS file: /cvs/src/sys/dev/an/if_an.c,v
retrieving revision 1.51
diff -c -r1.51 if_an.c
*** sys/dev/an/if_an.c  28 Jun 2003 06:13:27 -  1.51
--- sys/dev/an/if_an.c  19 Aug 2003 02:41:06 -
***
*** 313,319 
device_tdev;
  {
  struct an_softc *sc = device_get_softc(dev);
!   struct an_ltv_ssidlist  ssid;
int error;
  
bzero((char *)ssid, sizeof(ssid));
--- 

Re: ACPI on Tyan Motherboard

2003-08-18 Thread User Takawata
In message [EMAIL PROTECTED], Stephen Montgomery-Smith wrote
:
I have a Tyan S2462 Thunder K7 motherboard.  I was hoping to get power-down to
work.  So I installed FreeBSD current with ACPI enabled.  When I typed shutdo
wn 
-p now the computer halted, and then the video card switched off, and the fan
s 
kept running.  The computer was frozen - even the power-off power-on button 
wouldn't work.

Actually the power-off button doesn't work at all under FreeBSD-current.  (It 
is 
a soft power-off button that dmesg shows is detected by the OS.)

I should add that power-down works great with Windows 2000.  Also, the power-o
ff 
button works properly with FreeBSD-stable.

I am thinking that maybe I need to wait a few more months until ACPI is fully 
debugged.  On the other hand, maybe you guys would like to work on this.  I ca
n 
send all info like dmesg, and the kernel configuration (which is basically 
GENERIC with stuff removed, and SMP and pcm added, but actually it didn't work
 
with the generic kernel either.)

Is it possible that power is cut to the CPU's, but not to the fans?  Is there 
anyway to tell?

Will I have to program the ACPI (that is take the output of acpidump and edi
t it)?

It does seem to me that ACPI is working in some form, just not properly.  If I
 
boot up with ACPI disabled, then it works just as in FreeBSD-stable, that is, 
the power-off button works well.

Try

# sysctl hw.acpi.disable_on_poweroff=0


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADSUP: pca driver being retired.

2003-08-18 Thread Bruce Evans
On Thu, 14 Aug 2003, Poul-Henning Kamp wrote:

 In message [EMAIL PROTECTED], Mark Murray wr
 ites:

 Would it be a useful exercise for the minority(?) of users who use this
 driver to either see if it can be effectively newbussed or turned into
 a port or both?

 The main problem is the code which hi-jacks the i8254 and kicks off
 up to 2 interrupts per second.

What problem is this, except that 2 interrupts per second is too
small for current hardware?

Hmm, use of the interrupts has been broken in -current by incompletely
turning clkintr() into a fast interrupt handler.  pcaintr() is not a
fast interrupt handler, but clkintr() just calls it if pca is active.
pca uses splhigh() for locking, but splhigh is null in -current and
doesn't lock out fast interrupts anyway.  If pca were locked by Giant,
then the large interrupt latency of Giant would show up as large
distortion.

Bruce
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: LOR with page queue mutex and vm object

2003-08-18 Thread Alan L. Cox
Kris Kennaway wrote:
 
 I got this on alpha just now (kernel updated 2 days ago, filesystems
 created with -b 32768 -f 4096 to test reports of panics with these
 settings, which may or may not be relevant).  I don't think I've seen
 this trace before...apologies if it's another false positive.
 

This is real.  I'll look into it.

Thanks,
Alan

 
  1st 0xfc6e48d0 vm page queue mutex (vm page queue mutex) @ 
 /a/asami/portbuild/alpha/src-client/sys/vm/vm_pageout.c:405
  2nd 0xfc0005102e00 vm object (vm object) @ 
 /a/asami/portbuild/alpha/src-client/sys/kern/vfs_bio.c:2280
 Stack backtrace:
 db_print_backtrace() at db_print_backtrace+0x18
 backtrace() at backtrace+0x2c
 witness_lock() at witness_lock+0x6fc
 _mtx_lock_flags() at _mtx_lock_flags+0xc8
 vfs_setdirty() at vfs_setdirty+0x7c
 bdwrite() at bdwrite+0x3b8
 ffs_update() at ffs_update+0x388
 ufs_inactive() at ufs_inactive+0x254
 ufs_vnoperate() at ufs_vnoperate+0x2c
 vput() at vput+0x170
 vm_pageout_scan() at vm_pageout_scan+0x7ac
 vm_pageout() at vm_pageout+0x3ac
 fork_exit() at fork_exit+0x100
 exception_return() at exception_return
 -
 
   
Part 1.2Type: application/pgp-signature
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: an driver / Cisco Aironet 340 stopped working

2003-08-18 Thread Doug Ambrisko
Tomi Vainio - Sun Finland writes:
| Peter Radcliffe writes:
|   Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said:
|Peter Radcliffe writes:
|  Cisco have changed the operation of the card with newer firmware and
|  havn't released docs on working with the newer firmware.
|   
|I've tried multiple old firmwares and this loader.conf tweak but no
|luck yet.  Can you say what was the last working firmware?
|   
|   I don't have any 340 cards, just 350 cards, so no.
|  
| Firmware files are the same for both cards or that's my thought from
| this filename.
| 
| 350-340-PCMCIA-LMC-PCI-v52017.exe

I think he is confusing pccard versus mini-pci cards.  All pccard cards
(4800/340/350) use the same firmware.  I have a mix of them.  The 
mini-pci which is currently only a 350 uses totally different firmware.
It's the newer 350 firmware that I'm having trouble figuring out how
to make it work properly.  The older mini-pci firmware works okay.

Doug A.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: LOR with page queue mutex and vm object

2003-08-18 Thread Alan L. Cox
Kris Kennaway wrote:
 
 On Mon, Aug 18, 2003 at 11:40:09PM -0500, Alan L. Cox wrote:
  Kris Kennaway wrote:
  
   I got this on alpha just now (kernel updated 2 days ago, filesystems
   created with -b 32768 -f 4096 to test reports of panics with these
   settings, which may or may not be relevant).  I don't think I've seen
   this trace before...apologies if it's another false positive.
  
 
  This is real.  I'll look into it.
 
 Great, thanks.  The machine is still in DDB if you need me to do
 anything, otherwise I can dump it and obtain a gdb traceback.
 

The stack trace should suffice.

Thanks,
Alan
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


[current tinderbox] failure on alpha/alpha

2003-08-18 Thread Tinderbox
TB --- 2003-08-19 04:11:42 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-08-19 04:11:42 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-08-19 04:22:37 - building world
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src
TB --- /usr/bin/make -B buildworld
 Rebuilding the temporary build tree
 stage 1: legacy release compatibility shims
 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/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include
 stage 4: building libraries
 stage 4: make dependencies
 stage 4: building everything..
[...]
cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee 
-I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure/libexec/sftp-server/../../../crypto/openssh
 -DNO_IDEA  -o sftp-server sftp-common.o sftp-server.o -lssh -lcrypto
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/bin/ld:
 warning: libz.so.2, needed by 
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so,
 not found (try using -rpath or -rpath-link)
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `deflate'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `inflate'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateInit_'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateInit_'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `inflateEnd'
/home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/lib/libssh.so:
 undefined reference to `deflateEnd'
*** Error code 1

Stop in 
/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure/libexec/sftp-server.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure/libexec.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/secure.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src.
*** Error code 1

Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src.
TB --- 2003-08-19 05:18:54 - /usr/bin/make returned exit code  1 
TB --- 2003-08-19 05:18:54 - ERROR: failed to build world
TB --- 2003-08-19 05:18:54 - tinderbox aborted

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ACPI on Tyan Motherboard

2003-08-18 Thread Stephen Montgomery-Smith
User Takawata wrote:

Try

# sysctl hw.acpi.disable_on_poweroff=0

This didn't make any difference for me.

--
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: LOR with page queue mutex and vm object

2003-08-18 Thread Kris Kennaway
On Mon, Aug 18, 2003 at 11:40:09PM -0500, Alan L. Cox wrote:
 Kris Kennaway wrote:
  
  I got this on alpha just now (kernel updated 2 days ago, filesystems
  created with -b 32768 -f 4096 to test reports of panics with these
  settings, which may or may not be relevant).  I don't think I've seen
  this trace before...apologies if it's another false positive.
  
 
 This is real.  I'll look into it.

Great, thanks.  The machine is still in DDB if you need me to do
anything, otherwise I can dump it and obtain a gdb traceback.

Kris


pgp0.pgp
Description: PGP signature