From info at tecodryer.com Wed Aug 6 21:21:08 2008 From: info at tecodryer.com (TECO DRYER) Date: Wed Aug 6 21:21:24 2008 Subject: Teco Industry is in the business of corn, wheat, paddy, and Message-ID: <20080806212107.CCE718FC1B@mx1.freebsd.org> vegetable dr Sender: "TECO DRYER" Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Date: Thu, 7 Aug 2008 00:12:21 +0300 Message-ID: <20080806211221510.6EB06B0C092D4B53@erkan-e90bf8060> X-Priority: 3 (Normal) Importance: Normal Teco Industry is in the business of corn, wheat, paddy, and vegetable drying machines and the production and marketing of silo & steel construction. Related to the machines that our company produce; Teco Industry has the representatives in Bulgaria, Albania, Ukraine, Tatarstan, Kazakhstan, Russia, Angola and Indonesia. Our partners in these countries are accepted as the leaders in the steel industry. The quality of produced machines is approved by international standards. Teco is guaranteed by CE and ISO 9001-2000 certificates. Teco also contributes to the national economy by creating jobs in designing, project, production, import and export. Teco materializes R&D activities with its professional staff. Quality results are presented to the customers during the production, import and export. Our company takes the leadership of producing and marketing nationally and internationally. For Grain, Oily Seeds, and Pulses: Silos Corn and Soybean Drying Machines Handling Systems like Bucket Elevator, Chain Conveyor and Helix Prop Towers and Catwalks for Handling Systems Unloading Truck Lifts Industrial Foundations, Steel Construction With the expert staff; we take an important target like ‘’Customer Satisfaction and Service Quality’’ and perform service and counseling duties successfully. -------------------------------------------------------------------------------- Contact Us , Teco Dryer Company is ready for a long partnership with you. Sales Engineer Erkan AYMAN eayman@tecodryer.com From misterniceguy0 at gmail.com Wed Aug 13 10:43:43 2008 From: misterniceguy0 at gmail.com (Mister Nice Guy) Date: Wed Aug 13 10:43:50 2008 Subject: Storesonline, Website Design For Ecommerce The Three Things You Must Get Right Message-ID: <3b9f447d0808130329x1d056e6ak5b45da0160d92bb7@mail.gmail.com> *Storesonline, Website Design For Ecommerce The Three Things You Must Get Right* If you're planning to sell goods or services online, you'll need an ecommerce website. As this will be your shop front, your showroom, your salesman and your cashier, you'll appreciate how important it is. Essentially, the success of you ecommerce website depends on getting three factors right - design, usability and search engine optimization.*Storesonline * provides these services for the client. First, let's look at design. Design is important as it influences the impression your visitor gets of you and your business. Your website should be attractive and solidly professional. This assures the first time visitor that you are the right company to do business with.* Storesonline* software offers you point and click design. In addition, your website should reflect your brand and mission statement. Next there's the matter of usability. *Storesonline* software allows for easy navigation for customers. This determines how easily your visitor can navigate your site. The first thing you have to consider is the mechanics of your business model. You have to decide what you want your visitor to do and then give him clear means to do it. One factor that promotes clear navigation is making sure all links are well labeled. For example, "Click here for more details on our refrigerators" is much more useful that just 'click here' or 'more information'. And your visitor should always know his location and how to return to your home page. Remember if your visitor gets lost on your website, he'll just click away, probably never to return. From ws at au.dyndns.ws Thu Aug 28 17:57:52 2008 From: ws at au.dyndns.ws (Wayne Sierke) Date: Thu Aug 28 17:57:59 2008 Subject: Supported devices? vid/pid 0x1131/0x1001 and 0x0a5c/0x2100 Message-ID: <1219945354.2315.21.camel@predator-ii.buffyverse> Hi, I've got a couple of bluetooth USB adapters here and tried them out recently on this i386 7-STABLE GENERIC kernel. I'm sure I had at least one of them working previously, however neither of them seem to work with ng_ubt(4): ubt0: on uhub6 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 Unknown USB device: vendor 0x0a5c product 0x2100 bus uhub6 ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, STALLED (17). No new xfer will be submitted! ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted! and also ubt0: on uhub4 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 2) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=17; nframes=16, buffer size=272 Unknown USB device: vendor 0x1131 product 0x1001 bus uhub4 WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() WARNING: attempt to net_add_domain(netgraph) after domainfinalize() But in the archives it looks as though others have used both of these adapters successfully before. e.g. Mihai Tanasescu reported in Aug 2007: 2. usbdevs -dv (freezes for about 1-2 seconds while displaying the first device): Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 uhub0 port 1 addr 2: full speed, self powered, config 1, ISSCBTA(0x1001), vendor 0x1131(0x1131), rev 3.73 ubt0 and Bruce Cran reported in Sep 2007: ubt0: on uhub1 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 Admittedly that looks like a slightly different revision of the BCM device. Has support for these devices been removed or requires patches, etc? My usbdevs -lv (with the ISSC device attached to hub): # usbdevs -dv Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), SiS(0x0000), rev 1.00 uhub0 port 1 addr 2: full speed, self powered, config 1, product 0x0902(0x0902), vendor 0x03eb(0x03eb), rev 1.00 uhub5 port 1 addr 3: low speed, power 98 mA, config 1, USB-PS/2 Optical Mouse(0xc025), B16_b_02(0x046d), rev 98.02 ums0 port 2 powered port 3 powered port 4 addr 4: low speed, power 100 mA, config 1, Logitech USB Keyboard(0xc315), Logitech(0x046d), rev 28.00 ukbd0 port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), SiS(0x0000), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), SiS(0x0000), rev 1.00 uhub2 port 1 powered port 2 powered Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), SiS(0x0000), rev 1.00 uhub3 port 1 powered port 2 powered port 3 powered port 4 powered port 5 addr 2: high speed, self powered, config 1, USB2.0 Hub(0x0606), vendor 0x05e3(0x05e3), rev 7.02 uhub4 port 1 powered port 2 addr 3: full speed, power 100 mA, config 1, product 0x1001(0x1001), vendor 0x1131(0x1131), rev 1.34 ubt0 port 3 powered port 4 powered port 6 powered In spite of adapters showing as associated with ubt and listed as ubt0, I don't see any /dev/ubt* devices and /etc/rc.d/bluetooth start ubt0 fails: # /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 # kldstat Id Refs Address Size Name 1 29 0xc0400000 979ad0 kernel 2 1 0xc0d7a000 5464 vesa.ko 3 4 0xc0d80000 28678 linux.ko 4 1 0xc0da9000 6f88 snd_ich.ko 5 2 0xc0db0000 4a62c sound.ko 6 1 0xc0dfb000 4e0ef0 nvidia.ko 7 1 0xc12dc000 6a2c4 acpi.ko 8 1 0xc5171000 7000 linprocfs.ko 9 1 0xc5454000 2000 green_saver.ko 10 1 0xc52e8000 2000 rtc.ko 11 1 0xc5f9f000 7000 ng_ubt.ko 12 5 0xc5fa6000 b000 netgraph.ko 13 4 0xc5fd6000 2000 ng_bluetooth.ko 14 1 0xc5fd8000 d000 ng_hci.ko 15 1 0xc5ff2000 f000 ng_l2cap.ko 16 1 0xc6001000 1a000 ng_btsocket.ko 17 1 0xc601b000 4000 ng_socket.ko Thanks for any guidance! Wayne From maksim.yevmenkin at gmail.com Thu Aug 28 20:57:59 2008 From: maksim.yevmenkin at gmail.com (Maksim Yevmenkin) Date: Thu Aug 28 20:58:06 2008 Subject: Supported devices? vid/pid 0x1131/0x1001 and 0x0a5c/0x2100 In-Reply-To: <1219945354.2315.21.camel@predator-ii.buffyverse> References: <1219945354.2315.21.camel@predator-ii.buffyverse> Message-ID: On 8/28/08, Wayne Sierke wrote: > Hi, > > I've got a couple of bluetooth USB adapters here and tried them out > recently on this i386 7-STABLE GENERIC kernel. I'm sure I had at least > one of them working previously, however neither of them seem to work > with ng_ubt(4): > > ubt0: on uhub6 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > Unknown USB device: vendor 0x0a5c product 0x2100 bus uhub6 > ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, STALLED (17). No new xfer will be submitted! > ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted! that looks like some sort of usb problem. > and also > > ubt0: on uhub4 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 2) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=17; nframes=16, buffer size=272 > Unknown USB device: vendor 0x1131 product 0x1001 bus uhub4 > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() that actually looks normal to me. > But in the archives it looks as though others have used both of these > adapters successfully before. > > e.g. Mihai Tanasescu reported in Aug 2007: > 2. usbdevs -dv (freezes for about 1-2 seconds while displaying the first device): > > Controller /dev/usb0: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), > VIA(0x0000), rev 1.00 > uhub0 > port 1 addr 2: full speed, self powered, config 1, ISSCBTA(0x1001), > vendor 0x1131(0x1131), rev 3.73 > ubt0 > > > and Bruce Cran reported in Sep 2007: > ubt0: on uhub1 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; > wMaxPacketSize=49; nframes=6, buffer size=294 > > Admittedly that looks like a slightly different revision of the BCM device. > > Has support for these devices been removed or requires patches, etc? no. those should work (i do not see any reason why they would not) > My usbdevs -lv (with the ISSC device attached to hub): do you mean external usb hub? have you tried to connect your devices directly (i.e. without external hub)? [...] > In spite of adapters showing as associated with ubt and listed as ubt0, > I don't see any /dev/ubt* devices and /etc/rc.d/bluetooth start ubt0 > fails: there will not be any /dev/ubtX device nodes. there will be 'ubtX' netgraph nodes. use 'ngctl li' to see if there are any nodes and how many attached hooks they have. also, '/etc/rc.d/bluetooth start' will be called automatically from by devd(8) when device is plugged. so all you have to do is plug the device and everything should just work. > # /etc/rc.d/bluetooth start ubt0 > /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 yes, if you call 'start' when everything was already started it will fail. the safer thing is to do 'restart' or 'stop' and then 'start'. > # kldstat > Id Refs Address Size Name > 1 29 0xc0400000 979ad0 kernel > 2 1 0xc0d7a000 5464 vesa.ko > 3 4 0xc0d80000 28678 linux.ko > 4 1 0xc0da9000 6f88 snd_ich.ko > 5 2 0xc0db0000 4a62c sound.ko > 6 1 0xc0dfb000 4e0ef0 nvidia.ko > 7 1 0xc12dc000 6a2c4 acpi.ko > 8 1 0xc5171000 7000 linprocfs.ko > 9 1 0xc5454000 2000 green_saver.ko > 10 1 0xc52e8000 2000 rtc.ko > 11 1 0xc5f9f000 7000 ng_ubt.ko > 12 5 0xc5fa6000 b000 netgraph.ko > 13 4 0xc5fd6000 2000 ng_bluetooth.ko > 14 1 0xc5fd8000 d000 ng_hci.ko > 15 1 0xc5ff2000 f000 ng_l2cap.ko > 16 1 0xc6001000 1a000 ng_btsocket.ko > 17 1 0xc601b000 4000 ng_socket.ko this looks normal. thanks, max From ws at au.dyndns.ws Fri Aug 29 05:20:16 2008 From: ws at au.dyndns.ws (Wayne Sierke) Date: Fri Aug 29 05:20:23 2008 Subject: Supported devices? vid/pid 0x1131/0x1001 and 0x0a5c/0x2100 In-Reply-To: References: <1219945354.2315.21.camel@predator-ii.buffyverse> Message-ID: <1219987205.2315.40.camel@predator-ii.buffyverse> On Thu, 2008-08-28 at 13:57 -0700, Maksim Yevmenkin wrote: > On 8/28/08, Wayne Sierke wrote: > > Hi, > > > > I've got a couple of bluetooth USB adapters here and tried them out > > recently on this i386 7-STABLE GENERIC kernel. I'm sure I had at least > > one of them working previously, however neither of them seem to work > > with ng_ubt(4): > > > > ubt0: on uhub6 > > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > > ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > > Unknown USB device: vendor 0x0a5c product 0x2100 bus uhub6 > > ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, STALLED (17). No new xfer will be submitted! > > ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted! > > that looks like some sort of usb problem. > I suspect there's something quirky about the USB on this Gigabyte 8SQ800 board. I have a Logitech MX500 mouse and "New Touch 200" keyboard that I have to connect through an external hub to avoid repeated USB disconnects on those devices. > > and also > > > > ubt0: on uhub4 > > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > > ubt0: Interface 1 (alt.config 2) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=17; nframes=16, buffer size=272 > > Unknown USB device: vendor 0x1131 product 0x1001 bus uhub4 > > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > > that actually looks normal to me. > > > But in the archives it looks as though others have used both of these > > adapters successfully before. > > > > e.g. Mihai Tanasescu reported in Aug 2007: > > 2. usbdevs -dv (freezes for about 1-2 seconds while displaying the first device): > > > > Controller /dev/usb0: > > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), > > VIA(0x0000), rev 1.00 > > uhub0 > > port 1 addr 2: full speed, self powered, config 1, ISSCBTA(0x1001), > > vendor 0x1131(0x1131), rev 3.73 > > ubt0 > > > > > > and Bruce Cran reported in Sep 2007: > > ubt0: on uhub1 > > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; > > wMaxPacketSize=49; nframes=6, buffer size=294 > > > > Admittedly that looks like a slightly different revision of the BCM device. > > > > Has support for these devices been removed or requires patches, etc? > > no. those should work (i do not see any reason why they would not) > > > My usbdevs -lv (with the ISSC device attached to hub): > > do you mean external usb hub? have you tried to connect your devices > directly (i.e. without external hub)? > > [...] > > > In spite of adapters showing as associated with ubt and listed as ubt0, > > I don't see any /dev/ubt* devices and /etc/rc.d/bluetooth start ubt0 > > fails: > > there will not be any /dev/ubtX device nodes. there will be 'ubtX' > netgraph nodes. use 'ngctl li' to see if there are any nodes and how > many attached hooks they have. also, '/etc/rc.d/bluetooth start' will > be called automatically from by devd(8) when device is plugged. so all > you have to do is plug the device and everything should just work. > > > # /etc/rc.d/bluetooth start ubt0 > > /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 > > yes, if you call 'start' when everything was already started it will > fail. the safer thing is to do 'restart' or 'stop' and then 'start'. > > > # kldstat > > Id Refs Address Size Name > > 1 29 0xc0400000 979ad0 kernel > > 2 1 0xc0d7a000 5464 vesa.ko > > 3 4 0xc0d80000 28678 linux.ko > > 4 1 0xc0da9000 6f88 snd_ich.ko > > 5 2 0xc0db0000 4a62c sound.ko > > 6 1 0xc0dfb000 4e0ef0 nvidia.ko > > 7 1 0xc12dc000 6a2c4 acpi.ko > > 8 1 0xc5171000 7000 linprocfs.ko > > 9 1 0xc5454000 2000 green_saver.ko > > 10 1 0xc52e8000 2000 rtc.ko > > 11 1 0xc5f9f000 7000 ng_ubt.ko > > 12 5 0xc5fa6000 b000 netgraph.ko > > 13 4 0xc5fd6000 2000 ng_bluetooth.ko > > 14 1 0xc5fd8000 d000 ng_hci.ko > > 15 1 0xc5ff2000 f000 ng_l2cap.ko > > 16 1 0xc6001000 1a000 ng_btsocket.ko > > 17 1 0xc601b000 4000 ng_socket.ko > > this looks normal. > > thanks, > max Turns out the ISSC adapter is working after all (attached via the external hub). I was thrown by the "Unknown USB device" errors and the lack of entries in /dev - not being familiar with netgraph. And I'm pretty sure it was the BCM device I had working previously, so probably that will be ok, too. ?Thanks very much for your response, max. Wayne