Re: geom<->ata forever cycle
heh. IBM? It's bad. All of the ones that I had (also running -current from within 24 hours) that were spitting that were bad (All were POS IBMs too!). Just my guess, however. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: "Valentin Nechayev" <[EMAIL PROTECTED]> To: "Nick H. -- Network Operations" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, November 22, 2003 8:21 AM Subject: Re: geom<->ata forever cycle > Sat, Nov 22, 2003 at 05:45:09, nickh wrote about "Re: geom<->ata forever cycle": > > > Personally I dont think this is GEOM related. I had a drive start doing > > Yes, it is ATAng related, AFAIS, but triggers GEOM forever cycle. > > > this to me (happens often as I work in a large datacenter) and the drive is > > about to die. What brand drive is it and how old is it? You may waanna > > look into replacing the drive if you have that option. I had one tonight > > that did that to me, swap the drive, fixed. > > System has IBM DJNA-351520 and IBM IC35L040AVER07. They are alive and good. > All other systems, including Win98, RedHat 8.0, FreeBSD 4.9 and > FreeBSD-5.1 of May 2003, works well with these drivers. > Hence, only fresh -current is broken. > > Full dmesg.boot of oldest -current follows. > > 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-20030523 #2: Sun May 25 00:28:30 EEST 2003 > root@:/var/obj/var/HEAD/src/sys/nn15 > Preloaded elf kernel "/boot/kernel/kernel" at 0xc044c000. > Preloaded elf module "/boot/modules/if_rl.ko" at 0xc044c1f4. > Preloaded elf module "/boot/modules/miibus.ko" at 0xc044c2a0. > Calibrating clock(s) ... i8254 clock: 1193010 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > Calibrating TSC clock ... TSC clock: 799435869 Hz > Timecounter "TSC" frequency 799435869 Hz > CPU: Intel Celeron (799.44-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x686 Stepping = 6 > Features=0x383f9ff > real memory = 268369920 (255 MB) > Physical memory chunk(s): > 0x1000 - 0x0009efff, 647168 bytes (158 pages) > 0x00473000 - 0x0fb31fff, 258732032 bytes (63167 pages) > avail memory = 255709184 (243 MB) > bios32: Found BIOS32 Service Directory header at 0xc00fad00 > bios32: Entry = 0xfb190 (c00fb190) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0xf+0xb1c0 > pnpbios: Found PnP BIOS data at 0xc00fbbb0 > pnpbios: Entry = f:bbe0 Rev = 1.0 > Other BIOS signatures found: > null: > random: > mem: > Pentium Pro MTRR support enabled > VESA: information block > 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 > 00 01 80 00 05 02 07 01 00 01 1a 01 00 01 23 01 > 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 > 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 > VESA: 33 mode(s) found > VESA: v3.0, 8192k memory, flags:0x1, mode table:0xc03ac7c2 (122) > VESA: NVidia > VESA: NVidia Corporation Riva TNT Chip Rev B1 > npx0: on motherboard > npx0: INT 16 interface > pci_open(1): mode 1 addr port (0x0cf8) is 0x8058 > pci_open(1a): mode1res=0x8000 (0x8000) > pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=11308086) > pcibios: BIOS version 2.10 > Using $PIR table, 10 entries at 0xc00fded0 > PCI-Only Interrupts: 5 9 11 > Location Bus Device Pin Link IRQs > slot 1 02A 0x60 3 4 5 7 9 10 11 14 15 > slot 1 02B 0x61 3 4 5 7 9 10 11 14 15 > slot 1 02C 0x62 3 4 5 7 9 10 11 14 15 > slot 1 02D 0x63 3 4 5 7 9 10 11 14 15 > slot 2 28A 0x68 3 4 5 7 9 10 11 14 15 > slot 2 28B 0x69 3 4 5 7 9 10 11 14 15 &g
Re: geom<->ata forever cycle
Here's a snippet of dmesg that was before the drive was swapped: Nov 22 09:58:04 juan kernel: ad3: UDMA ICRC error cmd=read fsbn 0 of 0-15 retrying Nov 22 09:58:04 juan last message repeated 2 times Nov 22 09:58:04 juan kernel: ad3: UDMA ICRC error cmd=read fsbn 0 of 0-15 falling back to PIO mode Nov 22 09:58:40 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 1756413 of 1756413-1756497 retrying Nov 22 09:58:40 juan last message repeated 2 times Nov 22 09:58:41 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 34624421 of 34624421-34624548 retrying Nov 22 09:58:42 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 41273248 of 41273248-41273374 retrying Nov 22 09:58:42 juan last message repeated 2 times Nov 22 09:58:42 juan kernel: ad2: UDMA ICRC error cmd=write fsbn 41273248 of 41273248-41273374 falling back to PIO mode After replacing the drive, error gone. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: "Nick H. -- Network Operations" <[EMAIL PROTECTED]> To: "Valentin Nechayev" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, November 22, 2003 5:45 AM Subject: Re: geom<->ata forever cycle > Personally I dont think this is GEOM related. I had a drive start doing > this to me (happens often as I work in a large datacenter) and the drive is > about to die. What brand drive is it and how old is it? You may waanna > look into replacing the drive if you have that option. I had one tonight > that did that to me, swap the drive, fixed. > > > > Regards, > Nick H. > Network Operations Center > [EMAIL PROTECTED] > > Please rate my performance! http://www.supportteam.net/rate.php3 > Please submit all new support requests to > http://ticketmonster.hostingsupport.com/ > --- > Privileged/Confidential Information may be contained in this message. If > you are not the addressee indicated in this message (or responsible for > delivery of the message to such person), you may not copy or deliver this > message to anyone. In such case, you should destroy this message and kindly > notify the sender by reply email. Please advise immediately if you or your > employer do not consent to Internet email for messages of this kind. > Opinions, conclusions and other information in this message that do not > relate to the official business of my firm shall be understood as neither > given nor endorsed by it. > > - Original Message - > From: "Valentin Nechayev" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, November 22, 2003 5:08 AM > Subject: geom<->ata forever cycle > > > > 5.1-current of 2003-11-20 hangs during kernel initialization with forever > > cycle around geom partitioning detection and ATA read failure. > > Message rate is too fast to record, no stopping is available, no serial > > console. > > > > Previous 5-current on this machine was of 2003-05-23. > > How to diagnose? > > dmesg of May's current says: > > > > start_init: trying /sbin/init > > ad0: UDMA ICRC error cmd=read fsbn 4397730 of 4397730-4397857 retrying > > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying > > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying > > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying > > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569ad0: success > settin > > g PIO4 on Intel ICH2 chip > > falling back to PIO mode > > > > Main FreeBSD here is 4.9-release which doesn't complaint to crc errors. > > > > Kernel config wasn't changed: > > > > machine i386 > > cpu I486_CPU > > cpu I586_CPU > > cpu I686_CPU > > ident nn15 > > maxusers 0 > > > > #To statically compile in device wiring instead of /boot/device.hints > > hints "GENERIC.hints" #Default
Re: geom<->ata forever cycle
Personally I dont think this is GEOM related. I had a drive start doing this to me (happens often as I work in a large datacenter) and the drive is about to die. What brand drive is it and how old is it? You may waanna look into replacing the drive if you have that option. I had one tonight that did that to me, swap the drive, fixed. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: "Valentin Nechayev" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 22, 2003 5:08 AM Subject: geom<->ata forever cycle > 5.1-current of 2003-11-20 hangs during kernel initialization with forever > cycle around geom partitioning detection and ATA read failure. > Message rate is too fast to record, no stopping is available, no serial > console. > > Previous 5-current on this machine was of 2003-05-23. > How to diagnose? > dmesg of May's current says: > > start_init: trying /sbin/init > ad0: UDMA ICRC error cmd=read fsbn 4397730 of 4397730-4397857 retrying > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569 retrying > ad0: UDMA ICRC error cmd=read fsbn 4398442 of 4398442-4398569ad0: success settin > g PIO4 on Intel ICH2 chip > falling back to PIO mode > > Main FreeBSD here is 4.9-release which doesn't complaint to crc errors. > > Kernel config wasn't changed: > > machine i386 > cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > ident nn15 > maxusers 0 > > #To statically compile in device wiring instead of /boot/device.hints > hints "GENERIC.hints" #Default places to look for devices. > > makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols > > options SCHED_4BSD > options INET #InterNETworking > options INET6 #IPv6 communications protocols > options FFS #Berkeley Fast Filesystem > options SOFTUPDATES #Enable FFS soft updates support > #options UFS_ACL #Support for access control lists > options UFS_DIRHASH #Improve performance on big directories > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > options PROCFS #Process filesystem (requires PSEUDOFS) > options PSEUDOFS #Pseudo-filesystem framework > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 #Compatible with FreeBSD4 > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > > # Debugging for use in -current > options DDB #Enable the kernel debugger > options INVARIANTS #Enable calls of extra sanity checking > options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS > options WITNESS #Enable checks to detect deadlocks and cycles > options WITNESS_SKIPSPIN #Don't run witness on spinlocks for speed > > device isa > device pci > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > options ATA_STATIC_ID #Static device numbering > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Add suspend/resume support for the i8254. > device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Pseudo devices - the numb
lock order reversal on 5.1
Got this earlier tonight on a box of mine... was testing a possible upgrade from 4.8 to 5.1 on a box to act as my router... dc0: promiscuous mode enabled Oct 26 20:32:37 router kernel: dc0: promiscuous mode enabled lock order reversal 1st 0xc05a4600 bpf global lock (bpf global lock) @ /usr/src/sys/net/bpf.c:375 2nd 0xc1f427bc dc0 (network driver) @ /usr/src/sys/pci/if_dc.c:3543 dc0: promiscuous mode disabled Oct 26 20:32:45 router kernel: dc0: promiscuous mode disabled I'll cvsup again here in a bit and rebuild yet again. I am seeing a version difference on this box and a box I have that builds rather frequently. Im thinking that it's fixed, but figured a heads up wouldn't hurt. I was attempting to go into tcpdump (with nnxXv set as flags). If the new sources dont fix it, I'll email an update, else just assume that it's all fixed. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lockorder reversal on vm_object.c vm_kern.c (with backtrace)
Got this error today when I dropped out of X/KDE. First time I've seen it pop up when dropping out of X/KDE. Machne got real sluggish when I did exit out and took a couple of minutes for console to re-appear and the first thing that jumped across when console did come back up was the following: lock order reversal 1st 0xc8a18534 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:512 2nd 0xc082f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:325 Stack backtrace: backtrace(c0517ac1,c082f110,c05292c2,c05292c2,c052915d) at backtrace+0x17 witness_lock(c082f110,8,c052915d,145,0) at witness_lock+0x697 _mtx_lock_flags(c082f110,0,c052915d,145,3) at _mtx_lock_flags+0xb1 _vm_map_lock(c082f0b0,c052915d,145,e847ea58,c03334d4) at _vm_map_lock+0x36 kmem_malloc(c082f0b0,1000,101,e847eac4,c0478510) at kmem_malloc+0x66 page_alloc(c083a240,1000,e847eab7,101,c058294c) at page_alloc+0x27 slab_zalloc(c083a240,101,c052ab26,66f,c5c6a4a4) at slab_zalloc+0x150 uma_zone_slab(c083a240,101,c052ab26,66f,0) at uma_zone_slab+0xd8 uma_zalloc_internal(c083a240,0,101,6ef,0) at uma_zalloc_internal+0x55 uma_zfree_arg(c5c6a480,e69739b4,0,1,0) at uma_zfree_arg+0x2cb swp_pager_meta_free_all(c8a18534,c0528b64,c0528af8,1af) at swp_pager_meta_free_all+0x1b0 swap_pager_dealloc(c8a18534,1,c052aa29,10b,0) at swap_pager_dealloc+0x113 vm_pager_deallocate(c8a18534,0,c0529bff,25e,c05cd328) at vm_pager_deallocate+0x3d vm_object_terminate(c8a18534,0,c0529bff,200,c8a4603c) at vm_object_terminate+0x1f4 vm_object_deallocate(c8a18534,c8a4603c,c8a18534,c8a4603c,e847ec64) at vm_object_deallocate+0x20f vm_map_entry_delete(c60a7600,c8a4603c,c0529330,86e,c0513401) at vm_map_entry_delete+0x3b vm_map_delete(c60a7600,0,bfc0,c60a7600,c5c54e80) at vm_map_delete+0x453 vm_map_remove(c60a7600,0,bfc0,111,c0512a23) at vm_map_remove+0x58 exit1(c5fb7260,100,c0512a23,63,e847ed40) at exit1+0x626 sys_exit(c5fb7260,e847ed10,c052ebcf,3fb,1) at sys_exit+0x41 syscall(2f,2f,2f,0,2ae4) at syscall+0x26e Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip = 0x2902b71f, esp = 0xbfbff08c, ebp = 0xbfbff0b8 --- *shrug* Figured someone here would know what's going on. >From uname -a: 5.1-RELEASE #7: Wed Jun 18 Sources are from around Jun 9-18. Any suggestions are more than welcome. Thanks! Regards, Nick H. [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: inetd unknown rpc/udp or rpc/tcp
And it did. Thanks! Regards, Nick H. [EMAIL PROTECTED] - Original Message - From: "Vitali Djatsuk" <[EMAIL PROTECTED]> To: "Martin Blapp" <[EMAIL PROTECTED]>; "Nick H. - Network Operations" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 03, 2003 12:40 AM Subject: RE: inetd unknown rpc/udp or rpc/tcp : : : : I had the same problem recently. Mergemastering again, will solve it. : : DvG. : >Sep 2 23:09:18 iso inetd[703]: unknown rpc/udp or rpc/tcp : : Looks like /etc/netconfig is missing or rpcbind is not running at : all. Inetd has rpc support and I guess when rpc is turned all of : you'll get this message. But it's harmless. : : Martin : : Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> : -- : ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH : Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 : PGP: : PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E : -- : ___ : [EMAIL PROTECTED] mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-current : To unsubscribe, send any mail to : "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
inetd unknown rpc/udp or rpc/tcp
Recently I have been trying to get inetd to start on a server of mine and it prints the following error in dmesg: Sep 2 23:09:18 iso inetd[703]: unknown rpc/udp or rpc/tcp There is nothing but ftp turned on in the inetd.conf (turn ftp off, same error). I have tried google, yet it's not returning anything worthwhile. (groups, /bsd and /linux) If anyone has had this issue and knows of a workaround, I'd love to hear about it. It's running a recent RELENG_5_1 world/kernel and there's nothing really out of place anywhere else. Im going to try to build/install world one more time on this box and see what happens, but Im not expecting any changes. Regards, Nick H. [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nge (Dlink 500-T [Gigabit Driver]) Failure on 5.1
Seems as though if it's compiled into the kernel, it works just fine. ## ifconfig begin## nge0: flags=8802 mtu 1500 options=13 ether 00:50:ba:39:19:c3 media: Ethernet autoselect (none) status: no carrier ## ifconfig end ## ## dmesg begin ## nge0: port 0xec00-0xecff mem 0xe2001000-0xe2001fff irq 17 at device 11.0 on pci0 nge0: Ethernet address: 00:50:ba:39:19:c3 miibus2: on nge0 nsgphy0: on miibus2 nsgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ## dmesg end ## Im not quite sure at this point what caused it, but I will attempt to look into it and find out why it wont load as a module. It's built in now and everything is just fine, again, but it still worries me that it's doing that. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] - Original Message ----- From: "Nick H. - Network Operations" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, August 25, 2003 11:59 AM Subject: nge (Dlink 500-T [Gigabit Driver]) Failure on 5.1 : nge0: port 0xec00-0xecff mem : 0xe2001000-0xe2001fff irq 17 at device 11.0 on pci0 : nge0: Ethernet address: 00:50:ba:39:19:c3 : nge0: no memory for jumbo buffers! : nge0: jumbo buffer allocation failed : device_probe_and_attach: nge0 attach returned 6 : : That occurs when I do a kldload if_nge.ko : It has previously worked on the machine, but is now failing. Is there : something special that needs to be done with this device or is it just the : card that is having problems? Im willing to provide anyone with more : information if needed, just shoot me an email. Im going to attempt to build : nge into the kernel and see what happens when it tries loading it up that : way. : : : : Regards, : Nick H. : Network Operations Center : [EMAIL PROTECTED] : : : ___ : [EMAIL PROTECTED] mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-current : To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nge (Dlink 500-T [Gigabit Driver]) Failure on 5.1
nge0: port 0xec00-0xecff mem 0xe2001000-0xe2001fff irq 17 at device 11.0 on pci0 nge0: Ethernet address: 00:50:ba:39:19:c3 nge0: no memory for jumbo buffers! nge0: jumbo buffer allocation failed device_probe_and_attach: nge0 attach returned 6 That occurs when I do a kldload if_nge.ko It has previously worked on the machine, but is now failing. Is there something special that needs to be done with this device or is it just the card that is having problems? Im willing to provide anyone with more information if needed, just shoot me an email. Im going to attempt to build nge into the kernel and see what happens when it tries loading it up that way. Regards, Nick H. Network Operations Center [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
D-Link DGE-500T support
I attempted to use a D-Link DGE-500T card this weekend on 5.1-RELEASE (and -CURRENT) with no success. It is unable to probe the device and find a proper driver for it. My question is: are there any plans currently to provide support for this card? If there is already support for it (which may be the case) then which driver is it using? I tried a GENERIC kernel with all the default drivers, but it diddnt work with them. I can eventually get dmesg output again, but I'd need to bring the server down to put the card back in. Any help is more than welcome. Thank you! Regards, Nick H. [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[RESOLVED] Belkin F5D5020 PCMCIA Card/Notebook Network Card
I auctually got it working under FreeBSD 4.8. Eventually (read: after next
weekend) I plan on attempting to get it working under 5.X. Unfortunately I
need the laptop for an event that is happening this week. Anyways, it's
working and here's the relevant file settings used:
## FOR FREEBSD 4.X ##
/etc/rc.conf:
pccard_enable="YES"
pccard_mem="DEFAULT"
pccardd_flags=" -i 10"
the -i 10 sets the IRQ on the device to 10 (dont ask how I found it... Ive
already closed Opera ;D)
and it's using the following in the /etc/defaults/pccard.conf:
# Belkin F5D5020
card "Belkin" "F5D5020-PCMCIA-Network-Card"
config auto "ed" ? 0x10
insert /etc/pccard_ether $device start
remove /etc/pccard_ether $device stop
The thing is up and running fine. dmesg output:
pcic0: Polling mode
pccard0: on pcic0
pccard1: on pcic0
...
pccard: card inserted, slot 0
...
Setup PC-CARD:
memory
beep
pccardd
...
Jul 28 03:55:30 pccardd[47]: Card "Belkin"("F5D5020-PCMCIA-Network-Card")
[V1]
[0] matched "Belkin" ("F5D5020-PCMCIA-Network-Card") [(null)] [(null)]
...
Jul 28 03:55:35 pccardd[47]: ed1: Belkin (F5D5020-PCMCIA-Network-Card)
inserted.
...
Jul 28 03:56:45 pccardd[47]: pccardd started
The device is running just fine. Hopefully, this is of some help to you, as
if I understand you correctly, you're having issues with the IRQ setting.
Try the pccardd_flags=" -i ##" where ## is the IRQ you want it to use.
Anyways, all is working well now.
Regards,
Nick H.
[EMAIL PROTECTED]
- Original Message -
From: "Brad Knowles" <[EMAIL PROTECTED]>
To: "Nick H. - Network Operations" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "M. Warner Losh" <[EMAIL PROTECTED]>
Sent: Monday, July 28, 2003 3:23 AM
Subject: Re: Belkin F5D5020 PCMCIA Card/Notebook Network Card
: At 2:38 AM -0500 2003/07/28, Nick H. - Network Operations wrote:
:
: > Does support for the Belkin F5D5020 PCMCIA Card/Notebook Network Card
exist
: > in FreeBSD 5.0-RELEASE? According to Belkin, it does, but I have been
: > unable to find any support for this card. Any suggestions on the right
: > place to look are more than welcome.
:
: Back in October of last year, I cooked up a pccard.conf entry for
: it that seemed to mostly work:
:
: # Belkin F5D5020 NE2000-compatible card (FCC ID: LXLC1LANTB)
: card "Belkin" "F5D5020-PCMCIA-Network-Card"
: config auto "ed" ?
: logstr "Belkin F5D5020 10/100 Base-TX Ethernet 16-bit PCMCIA
: card (NE2000-compatible)"
: insert /etc/pccard_ether $device start
: remove /etc/pccard_ether $device stop
:
:
: I submitted this to Warner Losh, but IIRC, I got an indication
: back that this wasn't right. However, I don't recall that I ever got
: any correct pccard.conf setting for this device, and while I could
: get FreeBSD to see the card and use this entry to mostly recognize
: it, I could not actually get any positive network results this way.
:
: Any additional information you can find would be appreciated.
: Right now, I'm using a Linksys (EtherFast 10/100 Integrated PC Card
: (PCM100) on the machine where I was trying to use the Belkin, but it
: sticks out from the machine and blocks the second PC Card slot, so
: I'd prefer to use the Belkin (which is flush with the edge and comes
: with a dongle), if possible.
:
: If I could get them both working, or get one of them working with
: one of my various 802.11b WiFi cards, then I would have two NICs and
: could do some much more interesting things with this machine.
: Unfortunately, everything seems to want IRQ3, so even if I could get
: the individual cards working by themselves, I don't know if I could
: ever get them working together.
:
:
: I did find an interesting entry at
: <http://www.freebsdforums.org/forums/showthread.php?threadid=8315>,
: at the bottom (dated April 2002) that shows the pccard.conf entry of:
:
: # Belkin F5D5020
: card "Belkin" "F5D5020-PCMCIA-Network-Card"
: config auto "ed" ? 0x10
: insert /etc/pccard_ether $device start
: remove /etc/pccard_ether $device stop
:
: Which the author claims (claimed) works (worked) for him.
:
:
: You can see my posts from October of last year at
:
<http://docs.freebsd.org/cgi/getmsg.cgi?fetch=753513+0+archive/2002/freebsd-
questions/20021013.freebsd-questions>,
:
<http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2755078+0+archive/2002/freebsd
-questions/20021013.freebsd-questions>,
: and
:
<http://docs.freebsd.org/cgi/getmsg.cgi?fetch=750581+0+archive/2002/freebsd-
questions/20021013.freebsd-questions>.
: And then there's the post at
:
<http://lists.freebsd.org/pipermail/freebsd-questions/2003-April/001987.html
>
: from April, which als
Belkin F5D5020 PCMCIA Card/Notebook Network Card
Does support for the Belkin F5D5020 PCMCIA Card/Notebook Network Card exist in FreeBSD 5.0-RELEASE? According to Belkin, it does, but I have been unable to find any support for this card. Any suggestions on the right place to look are more than welcome. Here's the mfg's site: http://catalog.belkin.com/IWCatProductPage.process?Merchant_Id=1&Product_Id= 104984# and the page that shows FreeBSD support: http://www.belkin.com/network/F5D5020.html Thanks! Regards, Nick H. [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
