default sound card
Hello I have 2 soundcards on my system, one is on-board and the other is on usb. The system recognise both of them but it uses by default the on-board card. I would like to route the sound to the usb card by default. Any hint appreciated. Thanks. -- Andi Trinculescu +40 722 239747 ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: default sound card
[ISO-8859-1] Andi Tri^nculescu wrote: Hello I have 2 soundcards on my system, one is on-board and the other is on usb. The system recognise both of them but it uses by default the on-board card. I would like to route the sound to the usb card by default. Any hint appreciated. Thanks. -- Andi Trinculescu +40 722 239747 ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]" The device node /dev/dsp is an intelligent link to a current idle device node "/dev/dspX.Y". You may have a try that load sound device driver modules in /etc/rc.local so that you can control the order a sound device uses /dev/dspX.Y. From Beijing, China ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1
Dinesh Nair <[EMAIL PROTECTED]> writes: > i never got re(4) working, and the patch i'm currently using forces > the use of rl(4) instead of using re(4). using rl(4) still shows > media as none, but it works the way it should with packets going in > and out. i've yet to try dag-erling's suggestion of disabling rx and > tx checksums. i'll also try with the patch you sent it to see if > that works. If you can receive but not transmit (as I understood from other posts in the thread, though you never answered my question about tcpdump), disabling tx checksum offloading should be the *first* thing to try, especially as there is a known bug in some RealTek chipsets which will cause tx checksums to be computed incorrectly for short packets (such as ICMP echo replies, or TCP handshake frames). DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
For Sale: Lucent/Ascend BSTDX 8000/9000
59009A BSTDX 9000 chassis Qty 2 59035 110V AC Power Supply Qty 8 59033E Control Processor Qty 5 59050E Control Processor Qty 1 59021D Channelized T1 IOP Qty 7 59011 Universal IOP Qty 6 59021-16 Channelized T1 IOP Qty 3 59107 Control Processor Adpt Module Qty 6 59022D T1 Adpt Module Ext Clock Qty 10 59071A BSTDX 8000 Chassis Qty 2 59022D T1 Adpt Module Ext Clock (NEW) Qty 6 59033D Control Processor Qty 3 59027-16 DSX-1 IOP Qty 3 59028D DSX-1 Adpt. 59094B-16 ATM UNI DS3 IOP Qty 2 59095 ATM UNI DS3 Adpt. Qty 2 59018-16 HSSI IOP Qty 2 59018 HSSI IOP Qty 6 59019 HSSI Adpt. Qty 3 59034 Control processor adpt. Qty 1 59072-64 1 Port Channelized DS3 Processor Qty 1 59122-64 12 Port E1 ATM I/O Processor Qty 1 Regards, Ben Youngblood DCR http://www.networkinghardware.net Tel 310 306 9950 Fax 310 306 5877 [EMAIL PROTECTED] DCR is your one stop solution for Datacom and Networking hardware, new and used at 60% to 90% off list. We buy and sell 3com, ADC/Kentrox, Adtran, Ascend/Lucent, Avaya, Bay Networks, Cabletron, Cisco, Digital Link, Extreme, Juniper, Larscom, Lucent PSAX, Motorola/UDS, N.E.T. Promina And IDNX, Nortel, Racal, Stratacom, Verilink, and more... Over 5,000 items in stock. Please visit out our website @ http://www.networkinghardware.net SOME INVENTORY ON-LINE. PLEASE CALL OR REPLY FOR UPDATED OR INCOMING INVENTORY REMOVAL INSTRUCTIONS: If you have received this message in error or if you would like to be removed from our broadcast for any reason, reply to this email with REMOVE as subject followed by the email address you wish to remove. ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Want to Buy / RFQ : Juniper Networks M7i new or used
Unit 1 Juniper M7iBASE-AC-2FETX (2FE ports; AC power) MEM-FEB-256-S (256M memory) PE-1GE-SFP - 2 units SFP-1GE-SX - 2 units Unit 2 Juniper M7iBASE-AC-1GE (1GE port with SX SFP; AC power) MEM-FEB-256-S (256M memory) PE-1GE-SFP - 1 units SFP-1GE-SX - 1 units Please quote best price, warranty and condition. Thank you. Regards, Ben Youngblood DCR http://www.networkinghardware.net Tel 310 306 9950 Fax 310 306 5877 [EMAIL PROTECTED] DCR is your one stop solution for Datacom and Networking hardware, new and used at 60% to 90% off list. We buy and sell 3com, ADC/Kentrox, Adtran, Ascend/Lucent, Avaya, Bay Networks, Cabletron, Cisco, Digital Link, Extreme, Juniper, Larscom, Lucent PSAX, Motorola/UDS, N.E.T. Promina And IDNX, Nortel, Racal, Stratacom, Verilink, and more... Over 5,000 items in stock. Please visit out our website @ http://www.networkinghardware.net SOME INVENTORY ON-LINE. PLEASE CALL OR REPLY FOR UPDATED OR INCOMING INVENTORY REMOVAL INSTRUCTIONS: If you have received this message in error or if you would like to be removed from our broadcast for any reason, reply to this email with REMOVE as subject followed by the email address you wish to remove. ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nVidia MCP51 NIC
FYI,
I was able to get the onboard NIC on a ECS C51GM-M mATX AM2
GF6100 working with the following patches
am2# diff -u if_nve.c new/if_nve.c
--- if_nve.cSat Jun 17 12:46:04 2006
+++ new/if_nve.cThu Aug 17 12:46:46 2006
@@ -235,6 +235,8 @@
"NVIDIA nForce MCP10 Networking Adapter"},
{NVIDIA_VENDORID, NFORCE_MCPNET11_DEVICEID,
"NVIDIA nForce MCP11 Networking Adapter"},
+ {NVIDIA_VENDORID, NFORCE_MCPNET51_DEVICEID,
+ "NVIDIA nForce MCP51 Networking Adapter"},
{0, 0, NULL}
};
am2# diff -u if_nvereg.h new/if_nvereg.h
--- if_nvereg.h Mon Dec 12 14:40:04 2005
+++ new/if_nvereg.h Thu Aug 17 12:46:46 2006
@@ -40,6 +40,7 @@
#defineNFORCE_MCPNET3_DEVICEID 0x00D6
#defineNFORCE_MCPNET4_DEVICEID 0x0086
#defineNFORCE_MCPNET5_DEVICEID 0x008C
+#defineNFORCE_MCPNET51_DEVICEID 0x0269
#defineNFORCE_MCPNET6_DEVICEID 0x00E6
#defineNFORCE_MCPNET7_DEVICEID 0x00DF
#defineNFORCE_MCPNET8_DEVICEID 0x0056
am2#
Looking through the LINUX version of the driver (forcedeth), they
dont seem to do anything special with this version of the NIC
pciconf shows
[EMAIL PROTECTED]:20:0: class=0x068000 card=0x1b571019 chip=0x026910de
rev=0xa3 hdr=0x00
vendor = 'NVIDIA Corporation'
class= bridge
am2# ifconfig nve0
nve0: flags=8843 mtu 1500
inet 192.168.43.185 netmask 0xff00 broadcast 192.168.43.255
inet6 fe80::216:ecff:fe9b:c397%nve0 prefixlen 64 scopeid 0x3
ether 00:16:ec:9b:c3:97
media: Ethernet autoselect (100baseTX )
status: active
am2#
Here is a dmesg of the working board
Copyright (c) 1992-2006 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 6.1-STABLE #3: Thu Aug 17 12:53:21 EDT 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/am2
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2210.20-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x40fb2 Stepping = 2
Features=0x178bfbff
Features2=0x2001
AMD Features=0xea500800
AMD Features2=0x1f,,CR8>
Cores per package: 2
real memory = 2113863680 (2015 MB)
avail memory = 2063388672 (1967 MB)
ACPI APIC Table:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2
ioapic0 irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: on motherboard
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi0: Power Button (fixed)
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: on acpi0
cpu1: on acpi0
acpi_button0: on acpi0
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
pci0: at device 0.0 (no driver attached)
pci0: at device 0.1 (no driver attached)
pci0: at device 0.2 (no driver attached)
pci0: at device 0.3 (no driver attached)
pci0: at device 0.4 (no driver attached)
pci0: at device 0.5 (no driver attached)
pci0: at device 0.6 (no driver attached)
pci0: at device 0.7 (no driver attached)
pcib1: at device 3.0 on pci0
pci1: on pcib1
pcib2: at device 4.0 on pci0
pci2: on pcib2
pci0: at device 5.0 (no driver attached)
pci0: at device 9.0 (no driver attached)
isab0: at device 10.0 on pci0
isa0: on isab0
pci0: at device 10.1 (no driver attached)
pci0: at device 10.2 (no driver attached)
ohci0: mem 0xfe02f000-0xfe02 irq
21 at device 11.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 8 ports with 8 removable, self powered
ehci0: mem 0xfe02e000-0xfe02e0ff
irq 22 at device 11.1 on pci0
ehci0: [GIANT-LOCKED]
usb1: EHCI version 1.0
usb1: companion controller, 8 ports each: usb0
usb1: on ehci0
usb1: USB revision 2.0
uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub1: 8 ports with 8 removable, self powered
atapci0: port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf400-0xf40f at device 13.0 on pci0
ata0: on atapci0
ata1: on atapci0
atapci1: port
0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f mem
0xfe02d000-0xfe02dfff irq 23 at device 14.0 on pci0
ata2: on atapci1
ata3: on atapci1
pcib3: at device 16.0 on pci0
pci3: on pcib3
rl0: port 0xac00-0xacff mem
0xfddff000-0xfddff0ff irq 17 at device 7.0 on pci3
miibus0: on rl0
rlphy0: on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:50:fc:32:52:a4
pci0: at device 16.3 (no driver attached)
nve0: port 0xd400-0xd407 mem
0xfe02b000-0xfe02bfff irq 21 at device 20.0 on pci0
nve0: Ethernet address 00:16:ec:9b:c
Re: Newbie Question to Device driver writing
Jonathan Herriott wrote: Intron- Unfortunately, I have nothing specific in mind as all my hardware works on FreeBSD. I've almost come to the point where I'm going to go to Fry's and buy a bunch of stuff and make a simple USB device which may turn on or off a light (actually hook it up to a light in my home) just to get some experience with writing drivers. Overall, I'd really love to do an opengl driver for a graphics card, but I figured before I get into something that complex, I might try something simpler. Any suggestion would be great. I'll look into -hackers@ as I would really like to learn the actual internals of FreeBSD. Jon If you want to know how to write a simple USB driver, you may have a look at /usr/src/sys/dev/usb/uscanner.c and /usr/src/sys/dev/usb/ulpt.c. They are both almost as simple as transfering data between hardware device and userland application. To write a graphics card driver that well supports OpenGL is difficult: 1. Current GPUs produced by NVIDIA or ATI (AMD) are complicated. 2. Some vendors wouldn't publicize programming data sheets of GPUs. You may have a look at http://dri.freedesktop.org/. Some days ago, I would create a C++ driver fundamental structure for FreeBSD, but discussants on -hackers@ threw doubts upon me. These days, I think, if FreeBSD can make use of drivers for Microsoft Windows, FreeBSD will become more powerful. Now FreeBSD and Linux both can use network card driver for Windows, with ndis(4) for FreeBSD and NDISWrapper for Linux (http://ndiswrapper.sf.net). But NDIS driver is one of the simplest drivers in WDM. The idea of WDM (Windows Device Model) simulator is quite challenging. But once WDMulator is realized, it will help FreeBSD deeply. From Beijing, China ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
