From freebsdworld at gmail.com Tue Jan 13 06:09:44 2009 From: freebsdworld at gmail.com (Benjamin Adams) Date: Tue Jan 13 06:09:52 2009 Subject: Fiber Card Message-ID: <6199c3dc0901130548i1e3c09bcl81c038a970d25c13@mail.gmail.com> I have found some fiber cards by emulex, wondering which are supported if any. If none are, can someone recommend a fiber card for me? Thanks Ben From stefan.lambrev at moneybookers.com Tue Jan 13 06:59:23 2009 From: stefan.lambrev at moneybookers.com (Stefan Lambrev) Date: Tue Jan 13 06:59:30 2009 Subject: Fiber Card In-Reply-To: <6199c3dc0901130548i1e3c09bcl81c038a970d25c13@mail.gmail.com> References: <6199c3dc0901130548i1e3c09bcl81c038a970d25c13@mail.gmail.com> Message-ID: <1A98AE78-BECD-418D-926F-19715994C77F@moneybookers.com> Greetings, On Jan 13, 2009, at 3:48 PM, Benjamin Adams wrote: > I have found some fiber cards by emulex, wondering which are > supported if any. Not sure if it is supported. > > If none are, can someone recommend a fiber card for me? > So far I'm happy with http://www.intel.com/Products/Server/Adapters/PRO1000PF/PRO1000PF-overview.htm > Thanks > Ben > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org > " -- Best Wishes, Stefan Lambrev ICQ# 24134177 From freebsdworld at gmail.com Tue Jan 13 07:20:46 2009 From: freebsdworld at gmail.com (Benjamin Adams) Date: Tue Jan 13 07:21:02 2009 Subject: Fiber Card In-Reply-To: <1A98AE78-BECD-418D-926F-19715994C77F@moneybookers.com> References: <6199c3dc0901130548i1e3c09bcl81c038a970d25c13@mail.gmail.com> <1A98AE78-BECD-418D-926F-19715994C77F@moneybookers.com> Message-ID: <6199c3dc0901130720pfabf0d4m5d05e6a0db795b09@mail.gmail.com> Think I called it wrong not Fiber Card but Fiber Channel (direct connect to mount a RAID server) But Thanks On Tue, Jan 13, 2009 at 9:41 AM, Stefan Lambrev wrote: > Greetings, > On Jan 13, 2009, at 3:48 PM, Benjamin Adams wrote: > > I have found some fiber cards by emulex, wondering which are supported if > any. > > Not sure if it is supported. > > If none are, can someone recommend a fiber card for me? > > So far I'm happy > with http://www.intel.com/Products/Server/Adapters/PRO1000PF/PRO1000PF-overview.htm > > Thanks > Ben > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" > > -- > Best Wishes, > Stefan Lambrev > ICQ# 24134177 > > > > > From stefan.lambrev at moneybookers.com Tue Jan 13 07:45:36 2009 From: stefan.lambrev at moneybookers.com (Stefan Lambrev) Date: Tue Jan 13 07:45:42 2009 Subject: Fiber Card In-Reply-To: <6199c3dc0901130720pfabf0d4m5d05e6a0db795b09@mail.gmail.com> References: <6199c3dc0901130548i1e3c09bcl81c038a970d25c13@mail.gmail.com> <1A98AE78-BECD-418D-926F-19715994C77F@moneybookers.com> <6199c3dc0901130720pfabf0d4m5d05e6a0db795b09@mail.gmail.com> Message-ID: <92496F42-CC27-4A8D-BE43-2A60EC7C8009@moneybookers.com> Hi, I think there is no support for Emulex HBAs I have Qlogic QLE2462, Dual-port 4Gbps Fibre Channel PCI Express HBA card which is recognized by isp.ko I never tested stability and performance with this HBA under FreeBSD, but I read somewhere that there is bug in freebsd and make the system unstable under heavy I/O load. http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00266.html On Jan 13, 2009, at 5:20 PM, Benjamin Adams wrote: > Think I called it wrong not Fiber Card but Fiber Channel (direct > connect to mount a RAID server) > But Thanks > > On Tue, Jan 13, 2009 at 9:41 AM, Stefan Lambrev > wrote: >> Greetings, >> On Jan 13, 2009, at 3:48 PM, Benjamin Adams wrote: >> >> I have found some fiber cards by emulex, wondering which are >> supported if >> any. >> >> Not sure if it is supported. >> >> If none are, can someone recommend a fiber card for me? >> >> So far I'm happy >> with http://www.intel.com/Products/Server/Adapters/PRO1000PF/PRO1000PF-overview.htm >> >> Thanks >> Ben >> _______________________________________________ >> freebsd-drivers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers >> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org >> " >> >> -- >> Best Wishes, >> Stefan Lambrev >> ICQ# 24134177 >> >> >> >> >> -- Best Wishes, Stefan Lambrev ICQ# 24134177 From Jeremy at FutureCIS.com Wed Jan 14 21:39:01 2009 From: Jeremy at FutureCIS.com (ThinkDifferently) Date: Wed Jan 14 21:39:09 2009 Subject: How do I use RocketRAID 3120 with FreeBSD 7.1-RELEASE ??? Message-ID: <21471603.post@talk.nabble.com> I bought the HighPoint RocketRAID 3120. I have 2 disks on it in a mirror configuration. Everything seems to go swimmingly through the FreeBSD 7.1-RELEASE build, up until the final reboot. 1) Boot from Disc 1. 2) At the "Welcome to FreeBSD" screen, choose option "6" ok load hptiop ok boot 3) It recognizes my mirror as device "da0" and I proceed with the installation. 4) I install all distros, except X.org & Ports. 5) At the tail end, before rebooting, I enter a shell and vi /boot/loader.conf. I add the line: hptiop_load="YES" 6) REBOOT. The following happens... a) RocketRAID card beeps b) I see the BIOS splash screen c) I see RocketRAID splash screen d) It resets and repeats everything above. I never even get a boot loader menu to try troubleshooting. What did I miss? Why can't this thing boot? Unfortunately, HighPoint's User Manual was last updated in 2007, when FreeBSD 6.1 was the latest. Since then, the hptiop driver was added to 7.x, and that's what I'm trying to use. My /boot/loader.conf file is... hptiop_load="YES" Here's my dmesg, but note the following: -I had to boot from the Live FS CD. -Before booting, I chose option "6" for the ok prompt. -I entered: load hptiop -Upon bootup, I chose the Live FS shell. -Note wayyyy down at the bottom, the 5th & 6th lines from the bottom, the da0 device. Sure, it works great booting from the CD, but how about booting from itself ?! Now, onto the dmesg... Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Phenom(tm) 9600 Quad-Core Processor (2304.92-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f22 Stepping = 2 Features=0x178bfbff Features2=0x802009> AMD Features=0xee500800 AMD Features2=0x7ff,,,Prefetch,,> Cores per package: 4 usable memory = 4007813120 (3822 MB) avail memory = 3846344704 (3668 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bfde0000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xee00-0xeeff mem 0xd0000000-0xdfffffff,0xfdae0000-0xfdaeffff,0xfd900000-0xfd9fffff irq 18 at device 5.0 on pci1 pci1: at device 5.1 (no driver attached) pcib2: irq 18 at device 6.0 on pci0 pci2: on pcib2 hptiop0: adapter at PCI 2:0:0, IRQ 18 hptiop0: mem 0xfd600000-0xfd6fffff,0xfd7f0000-0xfd7fffff,0xfc800000-0xfcffffff irq > 18 at device 0.0 on pci2 hptiop0: 0 RocketRAID 3xxx/4xxx controller driver v1.3 (010208) hptiop0: [GIANT-LOCKED] hptiop0: [ITHREAD] pcib3: irq 18 at device 10.0 on pci0 pci3: on pcib3 re0: port 0xce00-0xceff mem 0xfddff000-0xfddfffff,0xfdde0000-0xfddeffff irq 18 at device 0.0 on pci3 re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1f:d0:9f:04:73 re0: [FILTER] atapci0: port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ohci0: mem 0xfe02e000-0xfe02efff irq 16 at device 18.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfe02d000-0xfe02dfff irq 16 at device 18.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfe02c000-0xfe02c0ff irq 17 at device 18.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 6 ports with 6 removable, self powered ohci2: mem 0xfe02b000-0xfe02bfff irq 18 at device 19.0 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: SMM does not respond, resetting usb3: on ohci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 3 ports with 3 removable, self powered ohci3: mem 0xfe02a000-0xfe02afff irq 18 at device 19.1 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 3 ports with 3 removable, self powered ehci1: mem 0xfe029000-0xfe0290ff irq 19 at device 19.2 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 3 ports each: usb3 usb4 usb5: on ehci1 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 6 ports with 6 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] pci0: at device 20.2 (no driver attached) isab0: at device 20.3 on pci0 isa0: on isab0 pcib4: at device 20.4 on pci0 pci4: on pcib4 re1: port 0xbe00-0xbeff mem 0xfdcff000-0xfdcff0ff irq 20 at device 6.0 on pci4 re1: Chip rev. 0x10000000 re1: MAC rev. 0x00000000 miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:e0:4c:50:2a:cf re1: [FILTER] fwohci0: mem 0xfdcfe000-0xfdcfe7ff,0xfdcf8000-0xfdcfbfff irq 22 at device 14.0 on pci4 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:7c:ed:06:00:00:1f:d0 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x17cc000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:7c:ed:00:1f:d0 fwe0: Ethernet address: 02:7c:ed:00:1f:d0 fwip0: on firewire0 fwip0: Firewire address: 00:7c:ed:06:00:00:1f:d0 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode ohci4: mem 0xfe028000-0xfe028fff irq 18 at device 20.5 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb6: OHCI version 1.0, legacy support usb6: SMM does not respond, resetting usb6: on ohci4 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) md0: Preloaded image 4194304 bytes at 0xffffffff80c4be40 acd0: DVDROM at ata0-master UDMA33 SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! da0 at hptiop0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_LiveFS. acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 Trying to mount root from ufs:/dev/md0 -- View this message in context: http://www.nabble.com/How-do-I-use-RocketRAID-3120-with-FreeBSD-7.1-RELEASE-----tp21471603p21471603.html Sent from the freebsd-drivers mailing list archive at Nabble.com. From freebsddog at hotmail.com Thu Jan 15 02:58:39 2009 From: freebsddog at hotmail.com (Jim Andersson) Date: Thu Jan 15 02:58:45 2009 Subject: 8187SE driver Message-ID: Hi! Is there any chance of getting my wireless card running in CURRENT. Linux says it?s a Realtek 8187SE wireless network card. I have seen some driver for other 8187 cards, is it possible to force such driver to try identify the card? Here is the output of pciconf -lv in my FreeBSD CURRENT:none1@pci0:1:0:0: class=0x028000 card=0x819910ec chip=0x819910ec rev=0x22 hdr=0x00vendor = 'Realtek Semiconductor'class = network Best regards Jim Andersson _________________________________________________________________ Hetaste modetipsen & h?rligaste sk?nhetstesterna! http://salongk.msn.se/ From Jeremy at FutureCIS.com Thu Jan 15 06:30:09 2009 From: Jeremy at FutureCIS.com (ThinkDifferently) Date: Thu Jan 15 06:30:15 2009 Subject: How do I use RocketRAID 3120 with FreeBSD 7.1-RELEASE ??? In-Reply-To: <21471603.post@talk.nabble.com> References: <21471603.post@talk.nabble.com> Message-ID: <21478697.post@talk.nabble.com> ThinkDifferently wrote: > > What did I miss? Why can't this thing boot? Unfortunately, HighPoint's > User Manual was last updated in 2007, when FreeBSD 6.1 was the latest. > Since then, the hptiop driver was added to 7.x, and that's what I'm trying > to use. > I have followed what little there is at... http://www.freebsd.org/cgi/man.cgi?query=hptiop&sektion=4&manpath=FreeBSD+7.1-RELEASE http://www.freebsd.org/cgi/man.cgi?query=hptiop&sektion=4&manpath=FreeBSD+7.1-RELEASE All 3 device statements are in the /usr/src/sys/amd64/conf/GENERIC file, by default. I put the hptiop_load="YES" statement into the /boot/loader.conf file. Their user manual is at... http://www.highpoint-tech.com/PDF/RR3120/RR3120_UM_EN_10_111307_AP.pdf http://www.highpoint-tech.com/PDF/RR3120/RR3120_UM_EN_10_111307_AP.pdf But, it only has instructions up to FreeBSD 6.1, and they don't seem to apply any more to the 7.x version, which has the hptiop(4) driver in the GENERIC kernel. In other words, their instructions for a driver diskette are meaningless. I was led to believe that these cards were compatible with all modern versions of FreeBSD, especially since it's on the hardware compatibility list... http://www.freebsd.org/releases/7.1R/hardware.html http://www.freebsd.org/releases/7.1R/hardware.html -- View this message in context: http://www.nabble.com/How-do-I-use-RocketRAID-3120-with-FreeBSD-7.1-RELEASE-----tp21471603p21478697.html Sent from the freebsd-drivers mailing list archive at Nabble.com. From Jeremy at FutureCIS.com Thu Jan 15 07:36:45 2009 From: Jeremy at FutureCIS.com (ThinkDifferently) Date: Thu Jan 15 07:36:52 2009 Subject: How do I use RocketRAID 3120 with FreeBSD 7.1-RELEASE ??? In-Reply-To: <21471603.post@talk.nabble.com> References: <21471603.post@talk.nabble.com> Message-ID: <21480059.post@talk.nabble.com> I originally posted this thread in freebsd-drivers, thinking it appropriate because I'm trying to figure out how to use the hptiop(4) driver that is included in FreeBSD 7.1-RELEASE. Or, possibly that there are some missing instructions involving the use of this driver, especially as it relates to booting from the da0 device. I tried to move this thread to freebsd-hardware, but it wouldn't let me. -- View this message in context: http://www.nabble.com/How-do-I-use-RocketRAID-3120-with-FreeBSD-7.1-RELEASE-----tp21471603p21480059.html Sent from the freebsd-drivers mailing list archive at Nabble.com. From weongyo.jeong at gmail.com Thu Jan 15 20:35:08 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Thu Jan 15 20:35:16 2009 Subject: 8187SE driver In-Reply-To: References: Message-ID: <20090116040425.GB66457@freebsd.weongyo.org> On Thu, Jan 15, 2009 at 11:48:32AM +0100, Jim Andersson wrote: > > Hi! > > Is there any chance of getting my wireless card running in CURRENT. Linux says itīs a Realtek 8187SE wireless network card. I have seen some driver for other 8187 cards, is it possible to force such driver to try identify the card? > > > Here is the output of pciconf -lv in my FreeBSD CURRENT:none1@pci0:1:0:0: class=0x028000 card=0x819910ec chip=0x819910ec rev=0x22 hdr=0x00vendor = 'Realtek Semiconductor'class = network I think a thing you can try is that, NDISulator using ndis(4). AFAIK there's no support for 8187SE driver until now. regards, Weongyo Jeong From jhb at freebsd.org Fri Jan 16 11:22:41 2009 From: jhb at freebsd.org (John Baldwin) Date: Fri Jan 16 11:22:48 2009 Subject: New NIC driver: sis190 In-Reply-To: <20080429073249.167570@gmx.net> References: <20080429073249.167570@gmx.net> Message-ID: <200901161421.27453.jhb@freebsd.org> On Tuesday 29 April 2008 3:32:49 am Alexander Pohoyda wrote: > I have fixed some minor issues so that it works on FreeBSD 7.0 now (tested with amd64 build) > > http://pohoyda.gmxhome.de/sis190-freebsd-7.tar.gz > > Please have a look and comment if there are obvious problems. Otherwise, I would appreciate if the driver were accepted into the tree. Thank you! Is this the latest version of this driver? -- John Baldwin From freebsddog at hotmail.com Sat Jan 17 07:16:44 2009 From: freebsddog at hotmail.com (Jim Andersson) Date: Sat Jan 17 07:16:52 2009 Subject: 8187SE driver In-Reply-To: <20090116040425.GB66457@freebsd.weongyo.org> References: <20090116040425.GB66457@freebsd.weongyo.org> Message-ID: > From: weongyo.jeong@gmail.com > Date: Fri, 16 Jan 2009 13:04:26 +0900 > To: freebsddog@hotmail.com > CC: freebsd-drivers@freebsd.org > Subject: Re: 8187SE driver > > On Thu, Jan 15, 2009 at 11:48:32AM +0100, Jim Andersson wrote: > > > > Hi! > > > > Is there any chance of getting my wireless card running in CURRENT. Linux says it?s a Realtek 8187SE wireless network card. I have seen some driver for other 8187 cards, is it possible to force such driver to try identify the card? > > > > > > Here is the output of pciconf -lv in my FreeBSD CURRENT:none1@pci0:1:0:0: class=0x028000 card=0x819910ec chip=0x819910ec rev=0x22 hdr=0x00vendor = 'Realtek Semiconductor'class = network > > I think a thing you can try is that, NDISulator using ndis(4). AFAIK > there's no support for 8187SE driver until now. > > regards, > Weongyo Jeong > I tried ndisulator but it didn?t work. I used the INF and the SYS file for Windows Xp. I even tried including a cat file. Although one thing changed, the card is no longer listed when i type pciconf -lv. Dunno if that?s good or bad? _________________________________________________________________ Hetaste modetipsen & h?rligaste sk?nhetstesterna! http://salongk.msn.se/ From weongyo.jeong at gmail.com Mon Jan 19 02:16:54 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Mon Jan 19 02:17:03 2009 Subject: 8187SE driver In-Reply-To: References: <20090116040425.GB66457@freebsd.weongyo.org> Message-ID: <20090119101623.GC81329@freebsd.weongyo.org> On Sat, Jan 17, 2009 at 04:16:43PM +0100, Jim Andersson wrote: > > > From: weongyo.jeong@gmail.com > > Date: Fri, 16 Jan 2009 13:04:26 +0900 > > To: freebsddog@hotmail.com > > CC: freebsd-drivers@freebsd.org > > Subject: Re: 8187SE driver > > > > On Thu, Jan 15, 2009 at 11:48:32AM +0100, Jim Andersson wrote: > > > > > > Hi! > > > > > > Is there any chance of getting my wireless card running in CURRENT. Linux says it?s a Realtek 8187SE wireless network card. I have seen some driver for other 8187 cards, is it possible to force such driver to try identify the card? > > > > > > > > > Here is the output of pciconf -lv in my FreeBSD CURRENT:none1@pci0:1:0:0: class=0x028000 card=0x819910ec chip=0x819910ec rev=0x22 hdr=0x00vendor = 'Realtek Semiconductor'class = network > > > > I think a thing you can try is that, NDISulator using ndis(4). AFAIK > > there's no support for 8187SE driver until now. > > > > regards, > > Weongyo Jeong > > > > I tried ndisulator but it didn?t work. I used the INF and the SYS file for Windows Xp. I even tried including a cat file. > Although one thing changed, the card is no longer listed when i type pciconf -lv. Dunno if that?s good or bad? It looks it's a bad news. Could you please show me dmesg's ouput and steps you followed? regards, Weongyo Jeong From freebsd at sopwith.solgatos.com Fri Jan 23 22:04:31 2009 From: freebsd at sopwith.solgatos.com (Dieter) Date: Fri Jan 23 22:04:36 2009 Subject: Dealing with Seagate's problematic 7200.11 firmware. Message-ID: <200901240523.FAA21539@sopwith.solgatos.com> Most of you have read about the problems with Seagate's 7200.11 disks. For those of you that haven't, the firmware on many of these drives is buggy, and can "brick" the drive when powering up or rebooting the system. Thus far, Seagate's response has been less than wonderful. We need a FLOSS solution. Goals: 1) Ability to read the number of log entries. 2) Ability to change the number of log entries. 3) Ability to install new firmware from Unix. We need for this to work with any flavor of Unix, on any CPU arch, without reboot or power cycle. We need for this to work on one drive without affecting other drives. I don't expect to be able to write FLOSS firmware for the drives, so this isn't listed as a goal. If you think you can, please feel free. The problem: "IF the drive is powered down when there are 320 entries in this journal or log, then when it is powered back up, the drive errors out on init and won't boot properly - to the point that it won't even report it's information to the BIOS." Maxtorman, slashdot discussion [2] If Maxtorman is correct, then once the drive has been operating awhile, we have a 1 in 320 chance that the circular log is at entry 320. We want to be able to find out how many log entries the disk currently has, and we want to be able to change the number of log entries away from 320, while we wait for Seagate to get its act together and release firmware that works properly. Since Seagate's solution will require attaching the drive to an x86 system and booting a FreeDOS ISO from CD, if the log is at 320 that boot will brick the drive. There are other firmware problems with the 7200.11 series, but this is the biggie. Once Seagate releases working firmware, we want to be able to install it from Unix, on any CPU arch. Seagate's release can only install on x86 using FreeDOS. *ATA Commands that may be useful: command name command code in hex page [1] pdf page [1] Read Log Ext 0x2F 27 33 S.M.A.R.T. Read Log Sector 0xB0 / 0xD5 28,34 34,40 S.M.A.R.T. Write Log Sector 0xB0 / 0xD6 28,34 34.40 Write Log Extended 0x3F 28 34 Download Microcode 0x92 27 33 Questions: Is Maxtorman correct about the 320 log entries? Are the commands listed above the ones we need? What is the difference between the "Log Extended" and the S.M.A.R.T. Log Sector? Is "Microcode" the same as "firmware"? (Seagate uses the term firmware elsewhere in the manual, but I don't find any sort of "write firmware" command.) Where can we get more detailed info about these commands and how to use them? References: [1] Seagate Barracuda 7200.11 Serial ATA Product Manual rev C August 2008 http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%207200.11/100507013c.pdf [2] http://it.slashdot.org/article.pl?sid=09/01/21/0052236 From freebsddog at hotmail.com Tue Jan 27 05:23:36 2009 From: freebsddog at hotmail.com (Jim Andersson) Date: Tue Jan 27 05:23:42 2009 Subject: FW: 8187SE driver In-Reply-To: <20090119101623.GC81329@freebsd.weongyo.org> References: <20090116040425.GB66457@freebsd.weongyo.org> <20090119101623.GC81329@freebsd.weongyo.org> Message-ID: From: freebsddog@hotmail.com To: weongyo@freebsd.org Subject: RE: 8187SE driver Date: Tue, 27 Jan 2009 14:22:15 +0100 > From: weongyo.jeong@gmail.com > Date: Mon, 19 Jan 2009 19:16:23 +0900 > To: freebsddog@hotmail.com > CC: freebsd-drivers@freebsd.org > Subject: Re: 8187SE driver > > On Sat, Jan 17, 2009 at 04:16:43PM +0100, Jim Andersson wrote: > > > > > From: weongyo.jeong@gmail.com > > > Date: Fri, 16 Jan 2009 13:04:26 +0900 > > > To: freebsddog@hotmail.com > > > CC: freebsd-drivers@freebsd.org > > > Subject: Re: 8187SE driver > > > > > > On Thu, Jan 15, 2009 at 11:48:32AM +0100, Jim Andersson wrote: > > > > > > > > Hi! > > > > > > > > Is there any chance of getting my wireless card running in CURRENT. Linux says it?s a Realtek 8187SE wireless network card. I have seen some driver for other 8187 cards, is it possible to force such driver to try identify the card? > > > > > > > > > > > > Here is the output of pciconf -lv in my FreeBSD CURRENT:none1@pci0:1:0:0: class=0x028000 card=0x819910ec chip=0x819910ec rev=0x22 hdr=0x00vendor = 'Realtek Semiconductor'class = network > > > > > > I think a thing you can try is that, NDISulator using ndis(4). AFAIK > > > there's no support for 8187SE driver until now. > > > > > > regards, > > > Weongyo Jeong > > > > > > > I tried ndisulator but it didn?t work. I used the INF and the SYS file for Windows Xp. I even tried including a cat file. > > Although one thing changed, the card is no longer listed when i type pciconf -lv. Dunno if that?s good or bad? > > It looks it's a bad news. Could you please show me dmesg's ouput and > steps you followed? > > regards, > Weongyo Jeong > As far as I can see the only thing in dmesg regarding this card is: pci1: on pcib3 pci1: at device 0.0 (no driver attached) What I did was this: I used my windows xp drivers for the card that I recieved with the computer. I used the .sys and the inf file. The driver loads good but no interface is shown. Is the someway to force the driver to attach to pci2 somehow? Or is there some way to use a linux driver? Linux says its a realtek 8187SE. // Jimmie Krama n?gon i vinter! Hitta k?rleken h?r! MSN Dejting _________________________________________________________________ Snygga till dina bilder snabbt, enkelt och gratis med PhotoGallery http://download.live.com/photogallery From weongyo.jeong at gmail.com Wed Jan 28 02:40:05 2009 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Wed Jan 28 02:40:11 2009 Subject: FW: 8187SE driver In-Reply-To: References: <20090116040425.GB66457@freebsd.weongyo.org> <20090119101623.GC81329@freebsd.weongyo.org> Message-ID: <20090128103926.GA82455@freebsd.weongyo.org> On Tue, Jan 27, 2009 at 02:23:33PM +0100, Jim Andersson wrote: > > From: freebsddog@hotmail.com > To: weongyo@freebsd.org > Subject: RE: 8187SE driver > Date: Tue, 27 Jan 2009 14:22:15 +0100 > > > From: weongyo.jeong@gmail.com > > Date: Mon, 19 Jan 2009 19:16:23 +0900 > > To: freebsddog@hotmail.com > > CC: freebsd-drivers@freebsd.org > > Subject: Re: 8187SE driver > > > > On Sat, Jan 17, 2009 at 04:16:43PM +0100, Jim Andersson wrote: > > > > > > > From: weongyo.jeong@gmail.com > > > > Date: Fri, 16 Jan 2009 13:04:26 +0900 > > > > To: freebsddog@hotmail.com > > > > CC: freebsd-drivers@freebsd.org > > > > Subject: Re: 8187SE driver > > > > > > > > On Thu, Jan 15, 2009 at 11:48:32AM +0100, Jim Andersson wrote: > > > > > > > > > > Hi! > > > > > > > > > > Is there any chance of getting my wireless card running in > > > > > CURRENT. Linux says it?s a Realtek 8187SE wireless network > > > > > card. I have seen some driver for other 8187 cards, is it > > > > > possible to force such driver to try identify the card? > > > > > > > > > > > > > > > Here is the output of pciconf -lv in my FreeBSD > > > > > CURRENT:none1@pci0:1:0:0: class=0x028000 card=0x819910ec > > > > > chip=0x819910ec rev=0x22 hdr=0x00vendor = 'Realtek > > > > > Semiconductor'class = network . > > > > > > > > I think a thing you can try is that, NDISulator using ndis(4). AFAIK > > > > there's no support for 8187SE driver until now. > > > > > > > > regards, > > > > Weongyo Jeong > > > > > > > > > > I tried ndisulator but it didn?t work. I used the INF and the SYS > > > file for Windows Xp. I even tried including a cat file. > > > Although one thing changed, the card is no longer listed when i > > > type pciconf -lv. Dunno if that?s good or bad? > > > > It looks it's a bad news. Could you please show me dmesg's ouput and > > steps you followed? > > > > regards, > > Weongyo Jeong > > > > As far as I can see the only thing in dmesg regarding this card is: > > pci1: on pcib3 > pci1: at device 0.0 (no driver attached) > > What I did was this: I used my windows xp drivers for the card that I > recieved with the computer. I used the .sys and the inf file. The > driver loads good but no interface is shown. Is the someway to force > the driver to attach to pci2 somehow? Normally if it works well the device should be detected automatically and should show some messages related with ndis(4). It looks there are another problems in your case. BTW there's no way to force the driver to attach. > Or is there some way to use a linux driver? Linux says its a realtek > 8187SE. No way to use the linux driver. regards, Weongyo Jeong From philip-freebsd1 at soeberg.net Wed Jan 28 05:28:49 2009 From: philip-freebsd1 at soeberg.net (Philip S) Date: Wed Jan 28 05:28:56 2009 Subject: taskqueue(9); taskqueue_thread usage from within interrupt context on BSD6.x Message-ID: <498059A4.7030909@soeberg.net> Hi, I need to defer part of my interrupt handler to a kernel thread and am currently doing this by using my own thread based on taskqueue(9) (via taskqueue_create_fast -> taskqueue_start_threads) My original support target where FreeBSD 6.3 and newer but now I need to support the entire 6 branch and in 6.0 taskqueue_start_threads does not exist. So, in taskqueue(9) for BSD6.0 the following is written: >>> The thread queue can be used, for instance, by interrupt level routines that need to call kernel functions that do things that can only be done from a thread context. (e.g., call malloc with the M_WAITOK flag.) <<< This is excellent. To conserve resources I can use the predefined [taskqueue_thread] symbol and enqueue on that in my interrupt handler, instead of reverting to kthreads. But how? taskqueue_thread is at boot constructed as an MTX_DEF mutex and 6.0 taskqueue_enqueue does not detect the type of mutex for the passed taskqueue pointer, so I must use taskqueue_enqueue_fast, which obviously does not work on taskqueue_thread. (Can't go mtx_lock_spin() on MTX_DEFs, and can't go use mtx_lock() from within an interrupt context) How am I supposed to implement that above snippet from within my interrupt context handler? Thanx, /Phil