Re: Patches to dc for testing (both PCI and CardBus versions).
In message: [EMAIL PROTECTED] M. Warner Losh [EMAIL PROTECTED] writes: : This turns the following cards in my collection into working cards: : NetGear FA510 ... : Kingston KE-CB4TX (aka Fast EtheRx CardBus PC Card) : http://people.freebsd.org/~imp/patch-dc.20020926 OK. I lied about these two cards. There is some issue that prevents them from working other than getting the NIC address right. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
xl networking not working any more!
Hello, after the recent changes in if_xl.c (from rev. 1.106 to 1.107) my 3COM 3C905B interface card does not work any more. It is still recognized and the interface comes up, but the media is not detected any more: ifconfig xl0 (with if_xl.c rev. 1.107): xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=3rxcsum,txcsum inet 172.16.81.200 netmask 0xff00 broadcast 172.16.81.255 inet6 fe80::210:5aff:fed7:dd9c%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:d7:dd:9c media: Ethernet 100baseTX hw-loopback status: no carrier ifconfig xl0 (with if_xl.c rev. 1.106): xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=3rxcsum,txcsum inet 172.16.81.200 netmask 0xff00 broadcast 172.16.81.255 inet6 fe80::210:5aff:fed7:dd9c%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:d7:dd:9c media: Ethernet autoselect (100baseTX full-duplex) status: active pciconf -l | fgrep xl0 xl0@pci0:9:0: class=0x02 card=0x905510b7 chip=0x905510b7 rev=0x30 hdr=0x00 Michael -- - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Sat Sep 28 03:14:26 PDT 2002 -- Kernel build for GENERIC completed on Sat Sep 28 03:41:00 PDT 2002 -- Kernel build for LINT started on Sat Sep 28 03:41:00 PDT 2002 -- === vinum cc1: warnings being treated as errors /h/des/src/sys/dev/advansys/adv_pci.c: In function `adv_pci_attach': /h/des/src/sys/dev/advansys/adv_pci.c:197: warning: overflow in implicit constant conversion *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current make depend: 'ar_args' has incomplete type help
On Sep 27 at 22:56, wsk spoke:
folks:
after succeed buildworld ,i custom mykernel and get the error messages
from make depend.
[...]
In file included from ../../../sys/buf.h:271,
from ../../../i386/i386/genassym.c:46:
../../../sys/proc.h:117: field `ar_args' has incomplete type
I had the same. I tried to build and install the kernel first.
Maybe, it's because you have an old compiler installed.
Try installing world first.
Alternatively you might try to patch proc.h.
--- proc.h Fri Sep 27 22:09:29 2002
+++ proc.h.orig Fri Sep 27 21:49:33 2002
@@ -114,7 +114,7 @@
struct pargs {
u_int ar_ref; /* Reference count. */
u_int ar_length; /* Length. */
- u_char *ar_args; /* Arguments. */
+ u_char ar_args[]; /* Arguments. */
};
/*-
-Hanspeter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
kern_sig.c mis-indentation
The indentation and the braces look rather odd in this bit of
kern_sig.c, somebody should straighten it up and check if
there are any bugs in this:
mi_switch();
mtx_unlock_spin(sched_lock);
PICKUP_GIANT();
PROC_LOCK(p);
break;
} else
if (prop SA_IGNORE) {
/*
* Except for SIGCONT, shouldn't get here.
* Default action is to ignore; drop it.
*/
break; /* == ignore */
} else
return (sig);
/*NOTREACHED*/
Poul-Henning
PS: Yes, another score by FlexeLint!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Soundcard drivers
Is there still any development being done on the soundcard drivers in FreeBSD? Especially regarding EMU10K2 support? I'm asking out of curiosity, because listening to radio while being in FreeBSD is suboptimal :) -mg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ATA driver broken?
Hi I can't boot a kernel after my 22nd Sept one. The ATA disk controller does not probe at all, and no bootable disk is found by the kernel. The machine is a Toshiba Libretto 110CT. Here is a dmesg: Copyright (c) 1992-2002 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.0-CURRENT #0: Sat Sep 28 13:31:34 BST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LIBRETTO Preloaded elf kernel /boot/kernel/kernel at 0xc04cd000. Preloaded elf module /boot/kernel/linux.ko at 0xc04cd0a8. Preloaded elf module /boot/kernel/sysvshm.ko at 0xc04cd154. Preloaded elf module /boot/kernel/sysvsem.ko at 0xc04cd200. Preloaded elf module /boot/kernel/sysvmsg.ko at 0xc04cd2ac. Preloaded elf module /boot/kernel/if_dc.ko at 0xc04cd358. Preloaded elf module /boot/kernel/miibus.ko at 0xc04cd404. Preloaded elf module /boot/kernel/if_wi.ko at 0xc04cd4b0. Preloaded elf module /boot/kernel/snd_mss.ko at 0xc04cd55c. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04cd608. Preloaded elf module /boot/kernel/random.ko at 0xc04cd6b4. Preloaded elf module /boot/kernel/atspeaker.ko at 0xc04cd760. Preloaded elf module /boot/kernel/if_ep.ko at 0xc04cd810. Preloaded elf module /boot/kernel/nfsserver.ko at 0xc04cd8bc. Preloaded elf module /boot/kernel/nfsclient.ko at 0xc04cd96c. Preloaded elf module /boot/kernel/acpi.ko at 0xc04cda1c. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 233289368 Hz CPU: Pentium/P55C (quarter-micron) (233.29-MHz 586-class CPU) Origin = GenuineIntel Id = 0x581 Stepping = 1 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 67174400 (65600K bytes) avail memory = 60014592 (58608K bytes) Intel Pentium detected, installing workaround for F00F bug npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 32-bit timer at 3.579545MHz port 0x18a8-0x18ab on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_acad0: AC adapter on acpi0 acpi_cmbat0: Control method Battery on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 atspeaker0 port 0x61 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: Printer on ppbus0 lpt0: Interrupt-driven port Timecounters tick every 10.000 msec Initializing GEOMetry subsystem acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.2% Mounting root from ufs:/dev/ad0s2a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
booting hangs at acpi.ko
Hello, I'm trying to upgrade from 4.6-Stable to Current. I had some difficulties to make buildworld/buildkernel complete. Then I created an empty /boot/device.hints to make. Now when trying to boot it hangs: Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x37174 data=0x1a84+0x6e0 syms=[0x4+0x5540+0x4+0x702d/ ] Is there a way this can be solved? Or should I install 4.6.2 again and upgrade again? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[PATCH] Broadcom BCM5702X Gigabit Ethernet support
# I'm not sure whom to send this patch, but the last person edited
# if_bge.c seems to be you :)
Hi, I got a new machine with Broadcom BCM5702X Gigabit Ethernet.
This NIC isn't supported yet, so I wrote simple patches for it.
It's working now, so far so good :)
Could you review the patches and commit them if acceptable?
# Or may I commit this with confidence?
Thanks
Index: sys/dev/bge/if_bge.c
===
RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v
retrieving revision 1.19
diff -u -r1.19 if_bge.c
--- sys/dev/bge/if_bge.c8 Sep 2002 19:11:58 - 1.19
+++ sys/dev/bge/if_bge.c28 Sep 2002 09:56:11 -
@@ -141,6 +141,8 @@
Broadcom BCM5700 Gigabit Ethernet },
{ BCOM_VENDORID, BCOM_DEVICEID_BCM5701,
Broadcom BCM5701 Gigabit Ethernet },
+ { BCOM_VENDORID, BCOM_DEVICEID_BCM5702X,
+ Broadcom BCM5702X Gigabit Ethernet },
{ BCOM_VENDORID, BCOM_DEVICEID_BCM5703X,
Broadcom BCM5703X Gigabit Ethernet },
{ SK_VENDORID, SK_DEVICEID_ALTIMA,
Index: sys/dev/bge/if_bgereg.h
===
RCS file: /home/ncvs/src/sys/dev/bge/if_bgereg.h,v
retrieving revision 1.7
diff -u -r1.7 if_bgereg.h
--- sys/dev/bge/if_bgereg.h 8 Sep 2002 19:11:58 - 1.7
+++ sys/dev/bge/if_bgereg.h 28 Sep 2002 09:56:15 -
@@ -1784,6 +1784,7 @@
#define BCOM_VENDORID 0x14E4
#define BCOM_DEVICEID_BCM5700 0x1644
#define BCOM_DEVICEID_BCM5701 0x1645
+#define BCOM_DEVICEID_BCM5702X 0x16A6
#define BCOM_DEVICEID_BCM5703X 0x16A7
/*
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ATA driver broken?
On Sat, Sep 28, 2002 at 05:55:02PM +0100, Mark Murray wrote: Hi I can't boot a kernel after my 22nd Sept one. The ATA disk controller does not probe at all, and no bootable disk is found by the kernel. The machine is a Toshiba Libretto 110CT. I'm seeing the same (sortof) on my Dual PIII machine - ATA as well as ISA (PCI-ISA bridge), SCSI (sym) and NIC (fxp) has dissapeared recently. I was suspecting the legacy(4) commits on the 23rd to be causing this. Boot messages (before/after) attached. [...] /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Hey, are any of you guys out there actually *using* RFC 2549? Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS drive F: is disk4 BIOS drive G: is disk5 BIOS 635kB/1047488kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Fri Sep 27 19:22:18 CEST 2002) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x23a018 data=0x310d4+0x3f9cc syms=[0x4+0x2f600+0x4+0x390ba] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 9 seconds... Type '?' for a list of commands, 'help' for more detailed help. OK unload OK boot kernel.old /boot/kernel.old/kernel text=0x236c40 data=0x30df4+0x3f76c syms=[0x4+0x2eb40+0x4+0x38a17] /boot/kernel.old/acpi.ko text=0x37254 data=0x1a84+0x6e0 syms=[0x4+0x5540+0x4+0x702d] Copyright (c) 1992-2002 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.0-CURRENT #0: Mon Sep 16 22:10:00 CEST 2002 [EMAIL PROTECTED]:/data/usr/obj/raid01/usr/src/sys/MONSTER Preloaded elf kernel /boot/kernel.old/kernel at 0xc0458000. Preloaded elf module /boot/kernel.old/acpi.ko at 0xc04580ac. Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (448.88-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1073676288 (1048512K bytes) avail memory = 1037463552 (1013148K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00fdf40 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xc08-0xc0b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_button0: Sleep Button on acpi0 pcib1: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib1 IOAPIC #0 intpin 21 - irq 2 IOAPIC #0 intpin 22 - irq 9 IOAPIC #0 intpin 20 - irq 10 sym0: 875 port 0x1400-0x14ff mem 0xfa10-0xfa100fff,0xfa103000-0xfa1030ff irq 2 at device 13.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: 875 port 0x1800-0x18ff mem 0xfa101000-0xfa101fff,0xfa103400-0xfa1034ff irq 9 at device 13.1 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking fxp0: Intel Pro 10/100B/100+ Ethernet port 0x1060-0x107f mem 0xfa00-0xfa0f,0xfa104000-0xfa104fff irq 10 at device 15.0 on pci0 fxp0: Ethernet address 00:90:27:73:c2:02 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 18.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 18.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at device 18.2 (no driver attached) Timecounter PIIX frequency 3579545 Hz pci0: bridge, PCI-unknown at device 18.3 (no driver attached) pci0: display, VGA at device 20.0 (no driver attached) atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0 port 0x378-0x37f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: Printer on ppbus0 lpt0: Interrupt-driven port sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A, console orm0: Option ROMs at iomem 0xe4000-0xe7fff,0xcc000-0xcc7ff,0xc8000-0xcbfff,0xc-0xc7fff on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 APIC_IO:
Re: [PATCH] Broadcom BCM5702X Gigabit Ethernet support
In article [EMAIL PROTECTED], Mitsuru IWASAKI [EMAIL PROTECTED] wrote: # I'm not sure whom to send this patch, but the last person edited # if_bge.c seems to be you :) Hi, I got a new machine with Broadcom BCM5702X Gigabit Ethernet. This NIC isn't supported yet, so I wrote simple patches for it. It's working now, so far so good :) Could you review the patches and commit them if acceptable? # Or may I commit this with confidence? The patch looks fine to me. Please commit it. Thanks, John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ATA driver broken?
Quoting Niels Chr. Bank-Pedersen [EMAIL PROTECTED]: | On Sat, Sep 28, 2002 at 05:55:02PM +0100, Mark Murray wrote: | Hi | | I can't boot a kernel after my 22nd Sept one. The ATA disk controller | does not probe at all, and no bootable disk is found by the kernel. | | The machine is a Toshiba Libretto 110CT. FWIW, I just booted my Compaq presario off today's build and kernel. I've basically done it everyday for the last 10 days. I may have skipped the reboot a couple of days. ed | | I'm seeing the same (sortof) on my Dual PIII machine - ATA as well as | ISA (PCI-ISA bridge), SCSI (sym) and NIC (fxp) has dissapeared recently. | I was suspecting the legacy(4) commits on the 23rd to be causing this. | Boot messages (before/after) attached. | | [...] | | | /Niels Chr. | | -- | Niels Christian Bank-Pedersen, NCB1-RIPE. | | Hey, are any of you guys out there actually *using* RFC 2549? -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GEOM panic in current kernel
Hi! After the latest geom_* commits I get a panic while booting. The panic occurs before mounting the disks, so I had to hand-write it down.. panic.. mtx_init(e0499ce8, e0396b85, 0, 0, 748f6273) at mtx_init + 0x5f ... g_up_procbody + 0x34 ... Please let me know if/how I could provide more info. Marc msg43545/pgp0.pgp Description: PGP signature
Re: GEOM panic in current kernel
In message [EMAIL PROTECTED], Marc Recht writes: --=.8yCGZQ.c,FaLiI Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi! After the latest geom_* commits I get a panic while booting. The panic occurs before mounting the disks, so I had to hand-write it down.. panic.. mtx_init(e0499ce8, e0396b85, 0, 0, 748f6273) at mtx_init + 0x5f ... g_up_procbody + 0x34 ... Uhm, what was the actual panic message ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Opera 6.1 for FreeBSD!
Does anyone know how to fix this? Arjan On Friday 27 September 2002 14:36, Edwin Culp wrote: Quoting Frode Nordahl [EMAIL PROTECTED]: | Hello, | | As some of you may know, Opera has a native FreeBSD version of Opera in | the works! | | http://web.opera.com/download/unix/untested/intel-freebsd/248-20020923-6 |.1-P1/ | | (Beware: the shared version requires qt-3.0.4, and will not work with | 3.0.5) | | It is of course compiled for FreeBSD 4.x and requires libc_r.so.4. | | The lib/compat/libc_r.so.4 in CVS does not work after recent changes to | threading in CURRENT(?). (Last buildworld September 24., kernel from | today) | | Opera fails with: | Fatal error 'Thread has returned from sigreturn or longjmp' at line ? | in file /usr/src/libc_r/uthread_kern.c (errno = ?) | | Any chance the compat library can be updated to make this work with | recent CURRENT? | | That would _rock_ ! :) I agree that would be fantastic. ed To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
$B"#E9F,HNGd$G$-$J$$$*?M7A$5$s"#(J
ø«µß½Èéæ¤È¨l`³ñðìèܵ½I»êàgåI
Iqbg¤iI
ɧÀª é½ß¨\µÝͨßÉI
¢ÉV»ioê!
¬Ìæ¤ÈêÈ«öl
ÇÜÅ{¨»Áèɧ쵽½ßAXªÌūܹñB
http://211.120.47.186/~cutepower/dattii.co.jp/dollcompany124.jp/
fBJAsAl`H[fUC
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: GEOM panic in current kernel
After the latest geom_* commits I get a panic while booting. The panic occurs before mounting the disks, so I had to hand-write it down.. panic.. mtx_init(e0499ce8, e0396b85, 0, 0, 748f6273) at mtx_init + 0x5f ... g_up_procbody + 0x34 ... Wow! That was a fast reply. :-) Uhm, what was the actual panic message ? mutex g_up 0xe0499cb8 already initialized Marc msg43549/pgp0.pgp Description: PGP signature
Re: Opera 6.1 for FreeBSD!
On Sat, Sep 28, 2002 at 08:23:55PM +0200, Arjan van Leeuwen wrote: Does anyone know how to fix this? Backing out the the kernel ucontext_t changes and mcontext_t commits. If you do that, please post a patch to the list. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM panic in current kernel
In message [EMAIL PROTECTED], Marc Recht writes: --=./s+MTW'WA?QFc= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit After the latest geom_* commits I get a panic while booting. The panic occurs before mounting the disks, so I had to hand-write it down.. panic.. mtx_init(e0499ce8, e0396b85, 0, 0, 748f6273) at mtx_init + 0x5f ... g_up_procbody + 0x34 ... Wow! That was a fast reply. :-) Uhm, what was the actual panic message ? mutex g_up 0xe0499cb8 already initialized Can you try this patch ? Index: geom_kern.c === RCS file: /home/ncvs/src/sys/geom/geom_kern.c,v retrieving revision 1.7 diff -u -r1.7 geom_kern.c --- geom_kern.c 28 Sep 2002 11:57:20 - 1.7 +++ geom_kern.c 28 Sep 2002 18:37:01 - @@ -83,6 +83,7 @@ struct thread *tp = FIRST_THREAD_IN_PROC(p); struct mtx mymutex; + bzero(mymutex, sizeof mymutex); mtx_init(mymutex, g_up, MTX_DEF, 0); mtx_lock(mymutex); tp-td_base_pri = PRIBIO; @@ -107,6 +108,7 @@ struct thread *tp = FIRST_THREAD_IN_PROC(p); struct mtx mymutex; + bzero(mymutex, sizeof mymutex); mtx_init(mymutex, g_down, MTX_DEF, 0); mtx_lock(mymutex); tp-td_base_pri = PRIBIO; -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM panic in current kernel
Uhm, what was the actual panic message ? mutex g_up 0xe0499cb8 already initialized Can you try this patch ? Works great! Thanks! Marc msg43552/pgp0.pgp Description: PGP signature
Re: GEOM panic in current kernel
* De: Terry Lambert [EMAIL PROTECTED] [ Data: 2002-09-28 ] [ Subjecte: Re: GEOM panic in current kernel ] Poul-Henning Kamp wrote: + bzero(mymutex, sizeof mymutex); mtx_init(mymutex, g_up, MTX_DEF, 0); Too bad mtx_init() doesn't really initialize the mutex, or this would not be necessary. 8-(. That would break some witness checks, Terry, which check for something very bad, which shouldn't happen: a mutex actually being initialised twice. -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM panic in current kernel
Poul-Henning Kamp wrote: + bzero(mymutex, sizeof mymutex); mtx_init(mymutex, g_up, MTX_DEF, 0); Too bad mtx_init() doesn't really initialize the mutex, or this would not be necessary. 8-(. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM panic in current kernel
Juli Mallett wrote: * De: Terry Lambert [EMAIL PROTECTED] [ Data: 2002-09-28 ] Poul-Henning Kamp wrote: + bzero(mymutex, sizeof mymutex); mtx_init(mymutex, g_up, MTX_DEF, 0); Too bad mtx_init() doesn't really initialize the mutex, or this would not be necessary. 8-(. That would break some witness checks, Terry, which check for something very bad, which shouldn't happen: a mutex actually being initialised twice. The ones in this case are on the stack, which means that they are not going to persist long enough for that to be a problem. For persistent mutexes, this implies that bzero()'ing is a bad thing to do (from a witness perspective), but a good thing to do otherwise. What this all implies to me is that there needs to be a mutex allocation/deallocation mechanism for keeping witness happy, by verifying that the mutex is no longer used at the point that it is freed, so that it's OK to bzero() it on initial allocation (to differentiate initial allocation from reuse). The point comes down to where do little mutexes come from?. Actually, it seems to me that it should be OK to initialize a mutex multiple times, and only not OK to initialize it if it's in use. In other words, I don't think that the protection you are talking about is protecting against what it;s pretending to. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Journaled filesystem in CURRENT
On Thu, 26 Sep 2002, Claus Assmann wrote: On Thu, Sep 26, 2002, Zhihui Zhang wrote: On Thu, 26 Sep 2002, Claus Assmann wrote: If someone is interested: http://www.sendmail.org/~ca/email/sm-9-rfh.html Just as a small data point: I get message acceptance rates of 400msgs/s on a journalling file system (using a normal PC) that writes the data into the journal too. AFAICT that's due to the fact that fsync() is much fast for this kind of storage. The important part for mailservers here is the rate at which content files can by safely written to disk. From my limited experience journalling file systems are here much better than softupdates. Can you tell me the approximate sizes of these mails and how they are stored? The test for sendmail 9 were made with small sizes (1-4KB). They were stored in flat files using 16 directories. The performance tests for sendmail 8 were done with sizes from 1 to 40 KB, in a single queue directory (AFAIR). Hope I can bother you with two more questions (I know nothing about sendmail beyond its name): (1) Can sendmail be configured to generate automatic messages for the purpose of performance test? (2) Is each mail stored in its own file? Thanks, -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Is phk rewriting the kernel over the weekend?
I need some of whatever it is you're taking. -- Time for my nap... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Soundcard drivers
On Sat, Sep 28, 2002 at 05:55:20PM +0200, Mario Goebbels wrote: Is there still any development being done on the soundcard drivers in FreeBSD? Especially regarding EMU10K2 support? I'm asking out of curiosity, because listening to radio while being in FreeBSD is suboptimal :) The main developers seem not to have been active recently. Kris msg43558/pgp0.pgp Description: PGP signature
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Sat Sep 28 15:19:00 PDT 2002 -- Kernel build for GENERIC completed on Sat Sep 28 15:49:30 PDT 2002 -- Kernel build for LINT started on Sat Sep 28 15:49:30 PDT 2002 -- === vinum cc1: warnings being treated as errors /h/des/src/sys/dev/advansys/adv_pci.c: In function `adv_pci_attach': /h/des/src/sys/dev/advansys/adv_pci.c:197: warning: overflow in implicit constant conversion *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM panic in current kernel
* De: Terry Lambert [EMAIL PROTECTED] [ Data: 2002-09-28 ] [ Subjecte: Re: GEOM panic in current kernel ] Juli Mallett wrote: * De: Terry Lambert [EMAIL PROTECTED] [ Data: 2002-09-28 ] Poul-Henning Kamp wrote: + bzero(mymutex, sizeof mymutex); mtx_init(mymutex, g_up, MTX_DEF, 0); Too bad mtx_init() doesn't really initialize the mutex, or this would not be necessary. 8-(. That would break some witness checks, Terry, which check for something very bad, which shouldn't happen: a mutex actually being initialised twice. The ones in this case are on the stack, which means that they are not going to persist long enough for that to be a problem. For persistent mutexes, this implies that bzero()'ing is a bad thing to do (from a witness perspective), but a good thing to do otherwise. What this all implies to me is that there needs to be a mutex allocation/deallocation mechanism for keeping witness happy, by verifying that the mutex is no longer used at the point that it is freed, so that it's OK to bzero() it on initial allocation (to differentiate initial allocation from reuse). The point comes down to where do little mutexes come from?. Actually, it seems to me that it should be OK to initialize a mutex multiple times, and only not OK to initialize it if it's in use. In other words, I don't think that the protection you are talking about is protecting against what it;s pretending to. A mutex zone or pool, and actual allocation would be interesting. -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Journaled filesystem in CURRENT
On Sat, Sep 28, 2002, Zhihui Zhang wrote: Hope I can bother you with two more questions (I know nothing about sendmail beyond its name): (1) Can sendmail be configured to generate automatic messages for the purpose of performance test? No. sendmail is an MTA, not a performance testing tool... There are different load generators available: Netscape has something (I forgot the name), postal is a test program (which I never got to compile), and smtp-source/smtp-sink from postfix. I have also written some load generators, but they require a specific environment. (2) Is each mail stored in its own file? The format of the sendmail mail queue is documented in doc/op/op.* (should be in /usr/share/doc/smm/08.sendmailop on FreeBSD). In brief: it uses two files: data (message body) and envelope / headers / some other routing data. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
pcm and xl could sleep with xyz locked
Hi, just compiled a custom KERNEL (-current 9/26), and turned on DIAGNOSTIC and WITNESS. I'm seeing a bunch of messages that look like someone'd want to know about them: [larse@nik: ~] cut -d' ' -f6- /var/log/messages | sort | uniq | grep sleep /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0 locked from /usr/src/sys/dev/sound/pcm/sound.c:134 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:fake locked from /usr/src/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:0 locked from /usr/src/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:0 locked from /usr/src/sys/dev/sound/pcm/dsp.c:673 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:0 locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:0 locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:0 locked from /usr/src/sys/dev/sound/pcm/dsp.c:794 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:0 locked from /usr/src/sys/dev/sound/pcm/sound.c:191 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:1 locked from /usr/src/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:2 locked from /usr/src/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:play:3 locked from /usr/src/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:record:0 locked from /usr/src/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with pcm0:record:1 locked from /usr/src/sys/dev/sound/pcm/channel.c:677 /usr/src/sys/vm/uma_core.c:1307: could sleep with xl0 locked from /usr/src/sys/pci/if_xl.c:1264 /usr/src/sys/vm/uma_core.c:1307: could sleep with xl0 locked from /usr/src/sys/pci/if_xl.c:647 Please let me know if there's any other information I can provide. Thanks, Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
[no subject]
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kern_sig.c mis-indentation
On Sat, 28 Sep 2002, Poul-Henning Kamp wrote:
The indentation and the braces look rather odd in this bit of
kern_sig.c, somebody should straighten it up and check if
there are any bugs in this:
mi_switch();
mtx_unlock_spin(sched_lock);
PICKUP_GIANT();
PROC_LOCK(p);
break;
} else
if (prop SA_IGNORE) {
/*
* Except for SIGCONT, shouldn't get here.
* Default action is to ignore; drop it.
*/
break; /* == ignore */
} else
return (sig);
/*NOTREACHED*/
This seemed to be just sloppy editing when it was first committed. IIRC,
this was messed up by putting some ifdefed crud in there, and the smaller
than usual indentation for the 'if' was a hack to avoid re-indenting
properly. The ifdefed crud was soon removed, leaving only the (now
completely bogus) indentation hack. I never merged these bugs and now
use the following patch which just restores to the unmangled version
which is still byte for byte identical with RELENG_4 here:
%%%
Index: kern_sig.c
===
RCS file: /home/ncvs/src/sys/kern/kern_sig.c,v
retrieving revision 1.190
diff -u -2 -r1.190 kern_sig.c
--- kern_sig.c 28 Sep 2002 17:14:53 - 1.190
+++ kern_sig.c 29 Sep 2002 01:27:20 -
@@ -1732,6 +1698,5 @@
PROC_LOCK(p);
break;
- } else
-if (prop SA_IGNORE) {
+ } else if (prop SA_IGNORE) {
/*
* Except for SIGCONT, shouldn't get here.
%%%
PS: Yes, another score by FlexeLint!
Nah. This was painfully obvious to the non-casual observer :). I have
1115 more lines of patches for style bugs in this file.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
kernel panic when booting with USB CF reader
Hi, I'm seeing a kernel panic on -current (9/26) when booting with a SanDisk ImageMate II USB comact flash reader plugged in. The panic occurs after the kernel has loaded when the first rc.d scripts execute (dumpon, vinum, etc). If I boot with the device disconnected, I can plug it in and unplug it without problems later. Attached is a boot trace and a gdb backtrace. (gdb crashed on me, so I couldn't get more information.) Here's the relevant info from the trace: SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a Entropy harvesting: interrupts ethernet point_to_point. kernel dumps on /dev/da1s1b vinum: loaded umass0: BBB reset failed, STALLED da2 at umass-sim0 bus 0 target 0 lun 0 da2: SanDisk ImageMate II 1.30 Removable Direct Access SCSI-2 device da2: 1.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present (da2:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:0): SCSI Status: Check Condition (da2:umass-sim0:0:0:0): NOT READY asc:3a,0 (da2:umass-sim0:0:0:0): Medium not present (da2:umass-sim0:0:0:0): Unretryable error Fatal trap 18: integer divide fault while in kernel mode cpuid = 1; lapic.id = 0200 instruction pointer = 0x8:0xc0437608 stack pointer = 0x10:0xeb484870 frame pointer = 0x10:0xeb4848f8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 67 (vinum) kernel: type 18 trap, code=0 Stopped at __qdivrem+0x38: divl%ecx,%eax Thanks, Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute Copyright (c) 1992-2002 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.0-CURRENT #0: Sat Sep 28 18:54:56 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL-1.4 Preloaded elf kernel /boot/kernel/kernel at 0xc06c. Preloaded elf module /boot/kernel/snd_maestro3.ko at 0xc06c00b4. Preloaded elf module /boot/kernel/firewire.ko at 0xc06c0168. Preloaded elf module /boot/kernel/acpi.ko at 0xc06c0218. Timecounter i8254 frequency 1193119 Hz CPU: Pentium 4 (2372.79-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1073180672 (1048028K bytes) avail memory = 1034698752 (1010448K bytes) Changing APIC ID for IO APIC #0 from 0 to 4 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 2, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 4, version: 0x00178020, at 0xfec0 Pentium Pro MTRR support enabled VESA: v2.0, 65536k memory, flags:0x1, mode table:0xc05aaa62 (122) VESA: ATI RADEON RV250 npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL WS 530 on motherboard Using $PIR table, 12 entries at 0xc00fb9a0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_cpu2: CPU on acpi0 acpi_cpu3: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 IOAPIC #0 intpin 19 - irq 2 IOAPIC #0 intpin 17 - irq 13 IOAPIC #0 intpin 23 - irq 16 agp0: Intel 82860 host to AGP bridge mem 0xe800-0xefff at device 0.0 on pci0 pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 IOAPIC #0 intpin 16 - irq 17 pci1: display, VGA at device 0.0 (no driver attached) pci1: display at device 0.1 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 2.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 31.0 on pci2 pci3: ACPI PCI bus on pcib3 IOAPIC #0 intpin 20 - irq 18 IOAPIC #0 intpin 21 - irq 19 pci3: base peripheral, interrupt controller at device 0.0 (no driver attached) mpt0: LSILogic 1030 Ultra4 Adapter port 0xdc00-0xdcff mem 0xff6a-0xff6b,0xff6c-0xff6d irq 18 at device 12.0 on pci3 mpt1: LSILogic 1030 Ultra4 Adapter port 0xd800-0xd8ff mem 0xff66-0xff67,0xff68-0xff69 irq 19 at device 12.1 on pci3 pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0 pci4: ACPI PCI bus on pcib4 IOAPIC #0 intpin 18 - irq 20 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xcc80-0xccff mem 0xff3ffc00-0xff3ffc7f irq 16 at device 11.0 on pci4 /usr/src/sys/vm/uma_core.c:1307: could sleep with xl0 locked from /usr/src/sys/pci/if_xl.c:1264 /usr/src/sys/vm/uma_core.c:1307: could sleep with xl0 locked
FireWire in 5.0?
I need to plan for some new servers by the end of the year. One of the boxes will require support for FireWire IEEE 1394. While I don't expect 5.0 to ship by November 20, I was wondering what the developers on this list believe the odds are that the FireWire code will make it into a stable 5.0 release by, say, January? I am aware that there is existing FireWire code, I am just wondering by when you think the integration will likely be done. Thanks in advance, --Lucky Green To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: booting hangs at acpi.ko
Hi, I'm trying to upgrade from 4.6-Stable to Current. I had some difficulties to make buildworld/buildkernel complete. Then I created an empty /boot/device.hints to make. Now when trying to boot it hangs: Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x37174 data=0x1a84+0x6e0 syms=[0x4+0x5540+0x4+0x702d/ ] Is there a way this can be solved? Or should I install 4.6.2 again and upgrade again? If you think this is caused by acpi.ko, just disable acpi.ko loading. Please read thru loader(8) and device.hints(5). Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: freeze with the CardBus NIC 3CCFE575BT
In message: [EMAIL PROTECTED] Vincent Poy [EMAIL PROTECTED] writes: : On Tue, 10 Sep 2002, Mikhail Teterin wrote: : : Regardless of whether the xl driver is linked into the kernel or : loaded as a module, the machine freezes shortly after ifconfig-ing : the card. Sunday's -current. Complete freeeze -- can not go into : debugger... : : More information available upon request... : : -mi : : This is interesting. I have the CardBus 3Com NIC 3CXFEM656C which : is the type II card that takes one slot but a combo with 56k modem and the : Megahertz XJack. With Sunday's -current and the 08182002-JP SNAPSHOT, the : card works fine under xl0 driver with the Dell Inspiron 8200 Notebook when : I moved the HDD from the IBM ThinkPad 770Z. On the 770Z however, as soon : as I do the ifconfig, it'll xl0: watchdog timer all over and it will ping : with latencies at 8000ms. So not sure what the problem is. Other cards : which I have tried, the Siemens/Efficient Networks SpeedStream SS1012 and : the SMC Networks SMC8036TX which seems to be identical cards physically as : it has the same design and same label printing information layout seems to : work fine on both machines. The NetGear FA511 and the LinkSys PCM200 both : don't work at all since FreeBSD can't detect the device id or something. I have patches for the 200 v2 problem. The watchdog timer means that you have interrupt problems, almost certainly. My 656C was working with Sept 22's current. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Soundcard drivers
Thus spake Mario Goebbels [EMAIL PROTECTED]: Is there still any development being done on the soundcard drivers in FreeBSD? Especially regarding EMU10K2 support? Go to www.opensound.com/freebsd/. Their drivers should work fine, even with more than two speakers, and they tend to sound better than the stock FreeBSD drivers. The downside is that after the free trial you have to pay for them, but if you really like to listen to music, they're worth it. I'm asking out of curiosity, because listening to radio while being in FreeBSD is suboptimal :) Reading mail with Outlook Express's brain-damaged formatting is suboptimal, too. :-P To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
