subject:"USB"

Thanks for your help. But before I attempt disabling the cdrom, I would like to 
mention that I can already see the following devices (with corresponding .init 
and .lock files) :

cuaU0.0
cuaU0.1
cuaU0.2
cuau0

I am almost certain that cuaU0.0 is the modem. I will try disabling the the 
cdrom and then switch mode.

Thanks again 
Regards

Manish Jain

From: odhia...@gmail.com
Date: Sun, 30 Jun 2013 11:45:11 +0300
Subject: Re: Problems getting my Huawei 0x140b USB modem to speak to internet
To: bourne.ident...@hotmail.com

Hi Manish,

I seem to have missed the name - Huawei, sorry for that.

Anyway, this should be easy to resolve - I suppose.

With the virtual cd-rom (da0) presenting itself, FreeBSD will assume the modem 
is simply a mass storage device and leave it at that. You need to disable the 
virtual cd-rom in order to use the modem.


Use Hyperterminal or putty or minicom (does it still exist?) to disable it.
Here are the AT commands to do that:

1. To disable; AT^U2DIAG=0
2. To re-enable: AT^U2DIAG=1

After disabling, you should be able to see a device node for the modem - 
/dev/cuaU0.0 or something. They may be two devices or three. One of them is the 
modem



And here is a ppp.conf which you can use - just change the APN (safaricom) to 
your provider's APN, change authname/authkey and also change the device to what 
you'll have gotten from /dev/



Hope that helps!


u3g:
 set device /dev/cuaU0.0
 set server /var/run/3g-internet  0177
 set speed 921600
 set timeout 0


 set authname saf
 set authkey data
 set dial ABORT BUSY ABORT NO\\sTIMEOUT 2 \
   \\ \
   AT OK-AT-OK \
   AT+CFUN=1 OK-AT-OK \
   AT+CMEE=2 OK-AT-OK \
   AT+CSQ OK \


   AT+CGDCONT=1,\\\IP\\\,\\\safaricom\\\ OK \
   ATD*99# CONNECT
 set crtscts on
 disable vjcomp
 disable acfcomp
 disable deflate
 disable deflate24
 disable pred1


 disable protocomp
 disable mppe
 disable ipv6cp
 disable lqr
 disable echo
 #nat enable yes
 enable dns
 resolv writable
 set dns 8.8.8.8
 set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0


 add default HISADDR  # See ppp.link*




On 30 June 2013 01:00, Manish Jain bourne.ident...@hotmail.com wrote:


Hi,



I thought the manufacturer name was mentioned in the original message : Huawei 
(0x12d1). Underneath is an extract from /var/log/messages :



Jun 29 23:03:57 bourne kernel: u3g0: Found 3 ports.

Jun 29 23:03:57 bourne kernel: umass0: HUAWEI TECHNOLOGIES HUAWEI Mobile, 
class 0/0, rev 1.10/0.00, addr 2 on usbus1

Jun 29 23:03:57 bourne kernel: umass0:  SCSI over Bulk-Only; quirks = 0x

Jun 29 23:03:57 bourne kernel: umass0:0:0:-1: Attached to scbus0

Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 
0 0 0 0 0 0

Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI 
Status Error

Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check 
Condition

Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): SCSI sense: UNIT 
ATTENTION asc:28,0 (Not ready to ready change, medium may have changed)

Jun 29 23:03:57 bourne kernel: cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0

Jun 29 23:03:57 bourne kernel: cd0: HUAWEI Mass Storage 2.31 Removable CD-ROM 
SCSI-0 device

Jun 29 23:03:57 bourne kernel: cd0: 1.000MB/s transfers

Jun 29 23:03:57 bourne kernel: cd0: cd present [52352 x 2048 byte records]

Jun 29 23:03:57 bourne kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 1

Jun 29 23:03:57 bourne kernel: da0: HUAWEI SD Storage 2.31 Removable Direct 
Access SCSI-2 device

Jun 29 23:03:57 bourne kernel: da0: 1.000MB/s transfers

Jun 29 23:03:57 bourne kernel: da0: 7580MB (15523840 512 byte sectors: 255H 
63S/T 966C)





Regards,



Manish Jain

+91-88064-38388



On 30-Jun-13 00:41, Odhiambo Washington wrote:


What is the manufacturer/model of the modem?



Is it detected by FreeBSD? Please show the /var/log/message entry for it.

I have never heard of usb_modeswitch.conf in FreeBSD!







On 29 June 2013 20:53, Manish Jain bourne.ident...@hotmail.com

mailto:bourne.ident...@hotmail.com wrote:



Hello All,



I have a a Huawei USB modem (product id 0x140b) which is connected

to my PC. I downloaded and installed Draisberghof's usb_modeswitch.



The following are the contents of my /etc/usb_modeswitch.conf :



DisableSwitching=0

EnableLogging=1

DefaultVendor=0x12d1

DefaultProduct=0x140b

TargetVendor=0x12d1

TargetProduct=0x1446

CheckSuccess=20

MessageEndpoint=0x0f


MessageContent=__555342431234567800__1106200100__00



When I run usb_modeswitch -c /etc/usb_modeswitch.conf, I get the

following message :



Looking for target devices ...

  No devices in target mode or class found

Looking for default devices ...

found matching product ID

adding device

  Found device in default mode, class or configuration (1)

Accessing device 010 on bus 000

Re: Problems getting my Huawei 0x140b USB modem to speak to internet

In that case, try disabling the cdrom and see if you make headway.


On 30 June 2013 13:29, Manish Jain bourne.ident...@hotmail.com wrote:

 Thanks for your help. But before I attempt disabling the cdrom, I would
 like to mention that I can already see the following devices (with
 corresponding .init and .lock files) :

 cuaU0.0
 cuaU0.1
 cuaU0.2
 cuau0

 I am almost certain that cuaU0.0 is the modem. I will try disabling the
 the cdrom and then switch mode.

 Thanks again 
 Regards

 Manish Jain

 --
 From: odhia...@gmail.com
 Date: Sun, 30 Jun 2013 11:45:11 +0300
 Subject: Re: Problems getting my Huawei 0x140b USB modem to speak to
 internet
 To: bourne.ident...@hotmail.com


 Hi Manish,

 I seem to have missed the name - Huawei, sorry for that.

 Anyway, this should be easy to resolve - I suppose.

 With the virtual cd-rom (da0) presenting itself, FreeBSD will assume the
 modem is simply a mass storage device and leave it at that. You need to
 disable the virtual cd-rom in order to use the modem.
 Use Hyperterminal or putty or minicom (does it still exist?) to disable it.
 Here are the AT commands to do that:

 1. To disable; AT^U2DIAG=0
 2. To re-enable: AT^U2DIAG=1

 After disabling, you should be able to see a device node for the modem -
 /dev/cuaU0.0 or something. They may be two devices or three. One of them is
 the modem

 And here is a ppp.conf which you can use - just change the APN (safaricom)
 to your provider's APN, change authname/authkey and also change the device
 to what you'll have gotten from /dev/

 Hope that helps!


 u3g:
  set device /dev/cuaU0.0
  set server /var/run/3g-internet  0177
  set speed 921600
  set timeout 0
  set authname saf
  set authkey data
  set dial ABORT BUSY ABORT NO\\sTIMEOUT 2 \
\\ \
AT OK-AT-OK \
AT+CFUN=1 OK-AT-OK \
AT+CMEE=2 OK-AT-OK \
AT+CSQ OK \
AT+CGDCONT=1,\\\IP\\\,\\\*safaricom*\\\ OK \
ATD*99# CONNECT
  set crtscts on
  disable vjcomp
  disable acfcomp
  disable deflate
  disable deflate24
  disable pred1
  disable protocomp
  disable mppe
  disable ipv6cp
  disable lqr
  disable echo
  #nat enable yes
  enable dns
  resolv writable
  set dns 8.8.8.8
  set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0
  add default HISADDR  # See ppp.link*




 On 30 June 2013 01:00, Manish Jain bourne.ident...@hotmail.com wrote:

 Hi,

 I thought the manufacturer name was mentioned in the original message :
 Huawei (0x12d1). Underneath is an extract from /var/log/messages :

 Jun 29 23:03:57 bourne kernel: u3g0: Found 3 ports.
 Jun 29 23:03:57 bourne kernel: umass0: HUAWEI TECHNOLOGIES HUAWEI Mobile,
 class 0/0, rev 1.10/0.00, addr 2 on usbus1
 Jun 29 23:03:57 bourne kernel: umass0:  SCSI over Bulk-Only; quirks =
 0x
 Jun 29 23:03:57 bourne kernel: umass0:0:0:-1: Attached to scbus0
 Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY.
 CDB: 0 0 0 0 0 0
 Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI
 Status Error
 Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): SCSI status:
 Check Condition
 Jun 29 23:03:57 bourne kernel: (probe0:umass-sim0:0:0:0): SCSI sense: UNIT
 ATTENTION asc:28,0 (Not ready to ready change, medium may have changed)
 Jun 29 23:03:57 bourne kernel: cd0 at umass-sim0 bus 0 scbus0 target 0 lun
 0
 Jun 29 23:03:57 bourne kernel: cd0: HUAWEI Mass Storage 2.31 Removable
 CD-ROM SCSI-0 device
 Jun 29 23:03:57 bourne kernel: cd0: 1.000MB/s transfers
 Jun 29 23:03:57 bourne kernel: cd0: cd present [52352 x 2048 byte records]
 Jun 29 23:03:57 bourne kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun
 1
 Jun 29 23:03:57 bourne kernel: da0: HUAWEI SD Storage 2.31 Removable
 Direct Access SCSI-2 device
 Jun 29 23:03:57 bourne kernel: da0: 1.000MB/s transfers
 Jun 29 23:03:57 bourne kernel: da0: 7580MB (15523840 512 byte sectors:
 255H 63S/T 966C)


 Regards,

 Manish Jain
 +91-88064-38388


 On 30-Jun-13 00:41, Odhiambo Washington wrote:

 What is the manufacturer/model of the modem?

 Is it detected by FreeBSD? Please show the /var/log/message entry for it.
 I have never heard of usb_modeswitch.conf in FreeBSD!



 On 29 June 2013 20:53, Manish Jain bourne.ident...@hotmail.com
 mailto:bourne.identity@**hotmail.com bourne.ident...@hotmail.com
 wrote:

 Hello All,

 I have a a Huawei USB modem (product id 0x140b) which is connected
 to my PC. I downloaded and installed Draisberghof's usb_modeswitch.

 The following are the contents of my /etc/usb_modeswitch.conf :

 DisableSwitching=0
 EnableLogging=1
 DefaultVendor=0x12d1
 DefaultProduct=0x140b
 TargetVendor=0x12d1
 TargetProduct=0x1446
 CheckSuccess=20
 MessageEndpoint=0x0f
 MessageContent=__**555342431234567800**__**
 1106200100**__00


 When I run usb_modeswitch -c /etc/usb_modeswitch.conf, I get the
 following message :

 Looking for target devices

Re: Problems getting my Huawei 0x140b USB modem to speak to internet


Hello Odhiambo/All,

I installed and ran minicom. There are 2 devices which are possible 
candidates as the modem : cuaU0.0 and cuaU0.2


I symlinked modem to each of the 2 devices and ran minicom. With both 
devices, the AT command returns OK, but AT^U2DIAG=0 returns COMMAND NOT 
SUPPORT


Any tips on what to do next ?


Thanks 
Regards,

Manish Jain
+91-88064-38388

On 30-Jun-13 17:30, freebsd-questions-requ...@freebsd.org wrote:

Send freebsd-questions mailing list submissions to
freebsd-questions@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to
freebsd-questions-requ...@freebsd.org

You can reach the person managing the list at
freebsd-questions-ow...@freebsd.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of freebsd-questions digest...


Today's Topics:

1. question, following error Shared object libc.so.6 not
   found, required by fortune (Rev Herbert Miller)
2. Re: question, following error Shared object libc.so.6 not
   found, required by fortune (Polytropon)
3. ALT key problem with Virtual Box? (Scott Ballantyne)
4. Re: ALT key problem with Virtual Box? (Polytropon)
5. Problems getting my Huawei 0x140b USB modem to speak to
   internet (Manish Jain)
6. Re: ALT key problem with Virtual Box? (Scott Ballantyne)
7. Baker Invites freebsd-questions@freebsd.org to spend holiday
   in Goa (John Baker)
8.  (Upali Kulasekara)
9. Re: your mail (Daniel Feenberg)
   10. RE: Problems getting my Huawei 0x140b USB modem to speak to
   internet (Manish Jain)
   11. Re: Problems getting my Huawei 0x140b USB modem to speak to
   internet (Odhiambo Washington)


--

Message: 1
Date: Sat, 29 Jun 2013 10:48:38 -0400
From: Rev Herbert Miller herbertmil...@me.com
To: questi...@freebsd.org
Subject: question, following error Shared object libc.so.6 not
found, required by fortune
Message-ID: 650f01ca-f62f-49e7-957f-9bfdc06d6...@me.com
Content-Type: text/plain; charset=us-ascii

I was trying to use the content management system for our website.  I needed to 
restart on terminal but I keep coming up with the following error:  I don't 
know programing at all, so don't know if this is something I can fix.


Shared object libc.so.6 not found, required by fortune

Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variable is needed to run this program
root@psumc:/usr/local/tomcat5.5 # bin/startup.sh
Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variable is needed to run this program
root@psumc:/usr/local/tomcat5.5 # su -c 'killall -9 java'

--

Message: 2
Date: Sat, 29 Jun 2013 17:58:31 +0200
From: Polytropon free...@edvax.de
To: Rev Herbert Miller herbertmil...@me.com
Cc: questi...@freebsd.org
Subject: Re: question, following error Shared object libc.so.6 not
found, required by fortune
Message-ID: 20130629175831.b2bf7fcb.free...@edvax.de
Content-Type: text/plain; charset=US-ASCII

On Sat, 29 Jun 2013 10:48:38 -0400, Rev Herbert Miller wrote:

I was trying to use the content management system for our website.
I needed to restart on terminal but I keep coming up with the
following error:  I don't know programing at all, so don't know
if this is something I can fix.


In worst case, notify your system administrator.




Shared object libc.so.6 not found, required by fortune


This kind of error often indicates an incomplete system update
were libraries are out of date or missing. What way of system
update has been performed?




root@psumc:/usr/local/tomcat5.5 # bin/startup.sh
Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variable is needed to run this program


That can be a side effect, maybe some accidentally overwritten
configuration file or a program that's unable to run due to a
missing dependency?

What happens if you manually define those variables to the proper
valies and try again, e. g.

# setenv JAVA_HOME=/usr/local/where your JAVA stuff is
# setenv JRE_HOME=/usr/local/where your runtime lives
# bin/startup,sh

Does this produce a different result?




root@psumc:/usr/local/tomcat5.5 # su -c 'killall -9 java'


That command doesn't make sense. The prompt indicates that you
are already root. The -c parameter for the su command is missing
an argument, the class. See man su for details, no programming
knowledge required. ;-)



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr

Re: Problems getting my Huawei 0x140b USB modem to speak to internet

Hi Manish,

If you have a Windows PC, use putty.exe and point the config to the COM
port on which the modem is detected to be attached to.
That's how I do it, unfortunately.

On 30 June 2013 16:51, Manish Jain bourne.ident...@hotmail.com wrote:

Hello Odhiambo/All,

I installed and ran minicom. There are 2 devices which are possible
candidates as the modem : cuaU0.0 and cuaU0.2

I symlinked modem to each of the 2 devices and ran minicom. With both
devices, the AT command returns OK, but AT^U2DIAG=0 returns COMMAND NOT
SUPPORT

Any tips on what to do next ?

Thanks
Regards,

Manish Jain
+91-88064-38388

On 30-Jun-13 17:30,
freebsd-questions-request@**freebsd.orgfreebsd-questions-requ...@freebsd.orgwrote:

Send freebsd-questions mailing list submissions to
freebsd-questions@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit

http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to

freebsd-questions-request@**freebsd.orgfreebsd-questions-requ...@freebsd.org

You can reach the person managing the list at

freebsd-questions-owner@**freebsd.orgfreebsd-questions-ow...@freebsd.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of freebsd-questions digest...

Today's Topics:

1. question, following error Shared object libc.so.6 not
found, required by fortune (Rev Herbert Miller)
2. Re: question, following error Shared object libc.so.6 not
found, required by fortune (Polytropon)
3. ALT key problem with Virtual Box? (Scott Ballantyne)
4. Re: ALT key problem with Virtual Box? (Polytropon)
5. Problems getting my Huawei 0x140b USB modem to speak to
internet (Manish Jain)
6. Re: ALT key problem with Virtual Box? (Scott Ballantyne)
7. Baker Invites freebsd-questions@freebsd.org to spend holiday
in Goa (John Baker)
8. (Upali Kulasekara)
9. Re: your mail (Daniel Feenberg)
10. RE: Problems getting my Huawei 0x140b USB modem to speak to
internet (Manish Jain)
11. Re: Problems getting my Huawei 0x140b USB modem to speak to
internet (Odhiambo Washington)

--**--**
--

Message: 1
Date: Sat, 29 Jun 2013 10:48:38 -0400
From: Rev Herbert Miller herbertmil...@me.com
To: questi...@freebsd.org
Subject: question, following error Shared object libc.so.6 not
found, required by fortune
Message-ID:
650F01CA-F62F-49E7-957F-**9bfdc06d6...@me.com650f01ca-f62f-49e7-957f-9bfdc06d6...@me.com

Content-Type: text/plain; charset=us-ascii

I was trying to use the content management system for our website. I
needed to restart on terminal but I keep coming up with the following
error: I don't know programing at all, so don't know if this is something
I can fix.

Shared object libc.so.6 not found, required by fortune

Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variable is needed to run this program
root@psumc:/usr/local/tomcat5.**5 # bin/startup.sh
Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variable is needed to run this program
root@psumc:/usr/local/tomcat5.**5 # su -c 'killall -9 java'

Message: 2
Date: Sat, 29 Jun 2013 17:58:31 +0200
From: Polytropon free...@edvax.de
To: Rev Herbert Miller herbertmil...@me.com
Cc: questi...@freebsd.org
Subject: Re: question, following error Shared object libc.so.6 not
found, required by fortune
Message-ID:
20130629175831.b2bf7fcb.**free...@edvax.de20130629175831.b2bf7fcb.free...@edvax.de

Content-Type: text/plain; charset=US-ASCII

On Sat, 29 Jun 2013 10:48:38 -0400, Rev Herbert Miller wrote:

I was trying to use the content management system for our website.
I needed to restart on terminal but I keep coming up with the
following error: I don't know programing at all, so don't know
if this is something I can fix.

In worst case, notify your system administrator.

Shared object libc.so.6 not found, required by fortune

This kind of error often indicates an incomplete system update
were libraries are out of date or missing. What way of system
update has been performed?

root@psumc:/usr/local/tomcat5.**5 # bin/startup.sh
Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variable is needed to run this program

That can be a side effect, maybe some accidentally overwritten
configuration file or a program that's unable to run due to a
missing dependency?

What happens if you manually define those variables to the proper
valies and try again, e. g.

# setenv JAVA_HOME=/usr/local/where your JAVA stuff

Re: Problems getting my Huawei 0x140b USB modem to speak to internet



Hello Odhiambo/All,

I seem to have made some progress but final success still eludes me. 
With modem symlinked to cuaU0.0, this is what happens is minicom :


AT^GETPORTMODE
^GETPORTMODE:TYPE:EV-DO:Qualcomm,MDM:0,DIAG:1,PCUI:2,CDROM:3

OK
AT^SETPORT=A1;1,2,3
COMMAND NOT SUPPORT

AT^GETPORTMODE succeeds, but with AT^U2DIAG/AT^SETPORT I get COMMAND 
NOT SUPPORT. So how to disable the CD mode and make FreeBSD treat it 
purely as a modem ? Some of the commands the modem supports (as reported 
by Windows' device manager) are as follows :


ATQ0V1E0 - OK
AT+GMM - EC156
AT+FCLASS=? - 0,2.0
AT#CLS=? - COMMAND NOT SUPPORT
   ^HRSSILVL:80
   ^HDRRSSI: 31
   ^HRSSILVL:60
   ^HDRRSSI: 31


Thanks for any help.

Regards,

Manish Jain
+91-88064-38388

On 30-Jun-13 19:41, Odhiambo Washington wrote:

Hi Manish,

If you have a Windows PC, use putty.exe and point the config to the COM
port on which the modem is detected to be attached to.
That's how I do it, unfortunately.



On 30 June 2013 16:51, Manish Jain bourne.ident...@hotmail.com
mailto:bourne.ident...@hotmail.com wrote:

Hello Odhiambo/All,

I installed and ran minicom. There are 2 devices which are possible
candidates as the modem : cuaU0.0 and cuaU0.2

I symlinked modem to each of the 2 devices and ran minicom. With
both devices, the AT command returns OK, but AT^U2DIAG=0 returns
COMMAND NOT SUPPORT

Any tips on what to do next ?


Thanks 
Regards,

Manish Jain
+91-88064-38388

On 30-Jun-13 17:30, freebsd-questions-request@__freebsd.org
mailto:freebsd-questions-requ...@freebsd.org wrote:

Send freebsd-questions mailing list submissions to
freebsd-questions@freebsd.org mailto:freebsd-questions@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to
freebsd-questions-request@__freebsd.org
mailto:freebsd-questions-requ...@freebsd.org

You can reach the person managing the list at
freebsd-questions-owner@__freebsd.org
mailto:freebsd-questions-ow...@freebsd.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of freebsd-questions digest...


Today's Topics:

 1. question, following error Shared object libc.so.6 not
found, required by fortune (Rev Herbert Miller)
 2. Re: question, following error Shared object libc.so.6 not
found, required by fortune (Polytropon)
 3. ALT key problem with Virtual Box? (Scott Ballantyne)
 4. Re: ALT key problem with Virtual Box? (Polytropon)
 5. Problems getting my Huawei 0x140b USB modem to speak to
internet (Manish Jain)
 6. Re: ALT key problem with Virtual Box? (Scott Ballantyne)
 7. Baker Invites freebsd-questions@freebsd.org
mailto:freebsd-questions@freebsd.org to spend holiday
in Goa (John Baker)
 8.  (Upali Kulasekara)
 9. Re: your mail (Daniel Feenberg)
10. RE: Problems getting my Huawei 0x140b USB modem to speak to
internet (Manish Jain)
11. Re: Problems getting my Huawei 0x140b USB modem to speak to
internet (Odhiambo Washington)



--__--__--

Message: 1
Date: Sat, 29 Jun 2013 10:48:38 -0400
From: Rev Herbert Miller herbertmil...@me.com
mailto:herbertmil...@me.com
To: questi...@freebsd.org
Subject: question, following error Shared object libc.so.6 not
 found, required by fortune
Message-ID: 650f01ca-f62f-49e7-957f-__9bfdc06d6...@me.com
mailto:650f01ca-f62f-49e7-957f-9bfdc06d6...@me.com
Content-Type: text/plain; charset=us-ascii

I was trying to use the content management system for our
website.  I needed to restart on terminal but I keep coming up
with the following error:  I don't know programing at all, so
don't know if this is something I can fix.


Shared object libc.so.6 not found, required by fortune

Neither the JAVA_HOME nor the JRE_HOME environment variable is
defined
At least one of these environment variable is needed to run this
program
root@psumc:/usr/local/tomcat5.__5 # bin/startup.sh
Neither the JAVA_HOME nor the JRE_HOME environment variable is
defined
At least one of these environment variable is needed to run this
program
root@psumc:/usr/local/tomcat5.__5 # su -c 'killall -9 java'

--

Message: 2
Date: Sat, 29 Jun 2013 17:58:31 +0200

Re: Problems getting my Huawei 0x140b USB modem to speak to internet

What model of Huawei is the modem? E-what??



On 30 June 2013 19:23, Manish Jain bourne.ident...@hotmail.com wrote:


 Hello Odhiambo/All,

 I seem to have made some progress but final success still eludes me. With
 modem symlinked to cuaU0.0, this is what happens is minicom :

 AT^GETPORTMODE
 ^GETPORTMODE:TYPE:EV-DO:**Qualcomm,MDM:0,DIAG:1,PCUI:2,**CDROM:3

 OK
 AT^SETPORT=A1;1,2,3
 COMMAND NOT SUPPORT

 AT^GETPORTMODE succeeds, but with AT^U2DIAG/AT^SETPORT I get COMMAND NOT
 SUPPORT. So how to disable the CD mode and make FreeBSD treat it purely as
 a modem ? Some of the commands the modem supports (as reported by Windows'
 device manager) are as follows :

 ATQ0V1E0 - OK
 AT+GMM - EC156
 AT+FCLASS=? - 0,2.0
 AT#CLS=? - COMMAND NOT SUPPORT
^HRSSILVL:80
^HDRRSSI: 31
^HRSSILVL:60
^HDRRSSI: 31


 Thanks for any help.

 Regards,

 Manish Jain
 +91-88064-38388


 On 30-Jun-13 19:41, Odhiambo Washington wrote:

 Hi Manish,

 If you have a Windows PC, use putty.exe and point the config to the COM
 port on which the modem is detected to be attached to.
 That's how I do it, unfortunately.



 On 30 June 2013 16:51, Manish Jain bourne.ident...@hotmail.com
 mailto:bourne.identity@**hotmail.com bourne.ident...@hotmail.com
 wrote:

 Hello Odhiambo/All,

 I installed and ran minicom. There are 2 devices which are possible
 candidates as the modem : cuaU0.0 and cuaU0.2

 I symlinked modem to each of the 2 devices and ran minicom. With
 both devices, the AT command returns OK, but AT^U2DIAG=0 returns
 COMMAND NOT SUPPORT

 Any tips on what to do next ?


 Thanks 
 Regards,

 Manish Jain
 +91-88064-38388

 On 30-Jun-13 17:30, 
 freebsd-questions-request@__fr**eebsd.orghttp://freebsd.org

 
 mailto:freebsd-questions-**requ...@freebsd.orgfreebsd-questions-requ...@freebsd.org
 wrote:

 Send freebsd-questions mailing list submissions to
 freebsd-questions@freebsd.org mailto:freebsd-questions@**
 freebsd.org freebsd-questions@freebsd.org


 To subscribe or unsubscribe via the World Wide Web, visit
 http://lists.freebsd.org/__**mailman/listinfo/freebsd-__**
 questionshttp://lists.freebsd.org/__mailman/listinfo/freebsd-__questions

 
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
 
 or, via email, send a message with subject or body 'help' to
 freebsd-questions-request@__fr**eebsd.org http://freebsd.org
 
 mailto:freebsd-questions-**requ...@freebsd.orgfreebsd-questions-requ...@freebsd.org
 


 You can reach the person managing the list at
 freebsd-questions-owner@__free**bsd.org http://freebsd.org
 
 mailto:freebsd-questions-**ow...@freebsd.orgfreebsd-questions-ow...@freebsd.org
 


 When replying, please edit your Subject line so it is more
 specific
 than Re: Contents of freebsd-questions digest...


 Today's Topics:

  1. question, following error Shared object libc.so.6 not
 found, required by fortune (Rev Herbert Miller)
  2. Re: question, following error Shared object libc.so.6
 not
 found, required by fortune (Polytropon)
  3. ALT key problem with Virtual Box? (Scott Ballantyne)
  4. Re: ALT key problem with Virtual Box? (Polytropon)
  5. Problems getting my Huawei 0x140b USB modem to speak to
 internet (Manish Jain)
  6. Re: ALT key problem with Virtual Box? (Scott Ballantyne)
  7. Baker Invites freebsd-questions@freebsd.org
 
 mailto:freebsd-questions@**freebsd.orgfreebsd-questions@freebsd.org
 to spend holiday

 in Goa (John Baker)
  8.  (Upali Kulasekara)
  9. Re: your mail (Daniel Feenberg)
 10. RE: Problems getting my Huawei 0x140b USB modem to speak
 to
 internet (Manish Jain)
 11. Re: Problems getting my Huawei 0x140b USB modem to speak
 to
 internet (Odhiambo Washington)


 --**__**
 --__--


 Message: 1
 Date: Sat, 29 Jun 2013 10:48:38 -0400
 From: Rev Herbert Miller herbertmil...@me.com
 mailto:herbertmil...@me.com

 To: questi...@freebsd.org
 Subject: question, following error Shared object libc.so.6 not
  found, required by fortune
 Message-ID: 
 650F01CA-F62F-49E7-957F-__**9bfdc06d6...@me.com650f01ca-f62f-49e7-957f-__9bfdc06d6...@me.com
 
 mailto:650F01CA-F62F-49E7-**957f-9bfdc06d6...@me.com650f01ca-f62f-49e7-957f-9bfdc06d6...@me.com
 

 Content-Type: text/plain; charset=us-ascii

 I was trying to use the content management system for our
 website.  I needed to restart on terminal but I keep coming up
 with the following

Re: Problems getting my Huawei 0x140b USB modem to speak to internet

EC156 is what the label on the modem says, which is the response given 
by AT+GMM. 0x140b is the chipset.


Regards,

Manish Jain
+91-88064-38388

On 30-Jun-13 22:02, Odhiambo Washington wrote:

What model of Huawei is the modem? E-what??



On 30 June 2013 19:23, Manish Jain bourne.ident...@hotmail.com
mailto:bourne.ident...@hotmail.com wrote:


Hello Odhiambo/All,

I seem to have made some progress but final success still eludes me.
With modem symlinked to cuaU0.0, this is what happens is minicom :

AT^GETPORTMODE
^GETPORTMODE:TYPE:EV-DO:__Qualcomm,MDM:0,DIAG:1,PCUI:2,__CDROM:3

OK
AT^SETPORT=A1;1,2,3
COMMAND NOT SUPPORT

AT^GETPORTMODE succeeds, but with AT^U2DIAG/AT^SETPORT I get
COMMAND NOT SUPPORT. So how to disable the CD mode and make
FreeBSD treat it purely as a modem ? Some of the commands the modem
supports (as reported by Windows' device manager) are as follows :

ATQ0V1E0 - OK
AT+GMM - EC156
AT+FCLASS=? - 0,2.0
AT#CLS=? - COMMAND NOT SUPPORT
^HRSSILVL:80
^HDRRSSI: 31
^HRSSILVL:60
^HDRRSSI: 31


Thanks for any help.

Regards,

Manish Jain
+91-88064-38388


On 30-Jun-13 19:41, Odhiambo Washington wrote:

Hi Manish,

If you have a Windows PC, use putty.exe and point the config to
the COM
port on which the modem is detected to be attached to.
That's how I do it, unfortunately.



On 30 June 2013 16:51, Manish Jain bourne.ident...@hotmail.com
mailto:bourne.ident...@hotmail.com
mailto:bourne.identity@__hotmail.com
mailto:bourne.ident...@hotmail.com wrote:

 Hello Odhiambo/All,

 I installed and ran minicom. There are 2 devices which are
possible
 candidates as the modem : cuaU0.0 and cuaU0.2

 I symlinked modem to each of the 2 devices and ran minicom.
With
 both devices, the AT command returns OK, but AT^U2DIAG=0
returns
 COMMAND NOT SUPPORT

 Any tips on what to do next ?


 Thanks 
 Regards,

 Manish Jain
 +91-88064-38388

 On 30-Jun-13 17:30,
freebsd-questions-request@__fr__eebsd.org http://freebsd.org

 mailto:freebsd-questions-__requ...@freebsd.org
mailto:freebsd-questions-requ...@freebsd.org wrote:

 Send freebsd-questions mailing list submissions to
freebsd-questions@freebsd.org
mailto:freebsd-questions@freebsd.org
mailto:freebsd-questions@__freebsd.org
mailto:freebsd-questions@freebsd.org


 To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions


http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 or, via email, send a message with subject or body
'help' to
 freebsd-questions-request@__fr__eebsd.org
http://freebsd.org
 mailto:freebsd-questions-__requ...@freebsd.org
mailto:freebsd-questions-requ...@freebsd.org


 You can reach the person managing the list at
 freebsd-questions-owner@__free__bsd.org
http://freebsd.org
 mailto:freebsd-questions-__ow...@freebsd.org
mailto:freebsd-questions-ow...@freebsd.org


 When replying, please edit your Subject line so it is
more specific
 than Re: Contents of freebsd-questions digest...


 Today's Topics:

  1. question, following error Shared object
libc.so.6 not
 found, required by fortune (Rev Herbert Miller)
  2. Re: question, following error Shared object
libc.so.6 not
 found, required by fortune (Polytropon)
  3. ALT key problem with Virtual Box? (Scott
Ballantyne)
  4. Re: ALT key problem with Virtual Box? (Polytropon)
  5. Problems getting my Huawei 0x140b USB modem to
speak to
 internet (Manish Jain)
  6. Re: ALT key problem with Virtual Box? (Scott
Ballantyne)
  7. Baker Invites freebsd-questions@freebsd.org
mailto:freebsd-questions@freebsd.org
 mailto:freebsd-questions@__freebsd.org
mailto:freebsd-questions@freebsd.org to spend holiday

 in Goa (John Baker)
  8.  (Upali Kulasekara)
  9. Re: your mail (Daniel Feenberg)
 10. RE: Problems getting my Huawei 0x140b USB modem
to speak

Re: Problems getting my Huawei 0x140b USB modem to speak to internet

, following error Shared object
 libc.so.6 not
  found, required by fortune (Rev Herbert Miller)
   2. Re: question, following error Shared object
 libc.so.6 not
  found, required by fortune (Polytropon)
   3. ALT key problem with Virtual Box? (Scott
 Ballantyne)
   4. Re: ALT key problem with Virtual Box?
 (Polytropon)
   5. Problems getting my Huawei 0x140b USB modem to
 speak to
  internet (Manish Jain)
   6. Re: ALT key problem with Virtual Box? (Scott
 Ballantyne)
   7. Baker Invites freebsd-questions@freebsd.org
 
 mailto:freebsd-questions@**freebsd.orgfreebsd-questions@freebsd.org
 
  
 mailto:freebsd-questions@__fr**eebsd.orghttp://freebsd.org

 
 mailto:freebsd-questions@**freebsd.orgfreebsd-questions@freebsd.org
 to spend holiday

  in Goa (John Baker)
   8.  (Upali Kulasekara)
   9. Re: your mail (Daniel Feenberg)
  10. RE: Problems getting my Huawei 0x140b USB modem
 to speak to
  internet (Manish Jain)
  11. Re: Problems getting my Huawei 0x140b USB modem
 to speak to
  internet (Odhiambo Washington)



 --**--**
 --__--__--



  Message: 1
  Date: Sat, 29 Jun 2013 10:48:38 -0400
  From: Rev Herbert Miller herbertmil...@me.com
 mailto:herbertmil...@me.com
  mailto:herbertmil...@me.com

 mailto:herbertmil...@me.com**

  To: questi...@freebsd.org
  Subject: question, following error Shared object
 libc.so.6 not
   found, required by fortune
  Message-ID:
 
 650F01CA-F62F-49E7-957F-**9bfdc06d6...@me.com650f01ca-f62f-49e7-957f-9bfdc06d6...@me.com
 
 mailto:650F01CA-F62F-49E7-**957f-__9bfdc06d6...@me.com650f01ca-f62f-49e7-957f-__9bfdc06d6...@me.com
 
  
 mailto:650F01CA-F62F-49E7-__**957f-9bfdc06d6...@me.com650f01ca-f62f-49e7-__957f-9bfdc06d6...@me.com

 
 mailto:650F01CA-F62F-49E7-**957f-9bfdc06d6...@me.com650f01ca-f62f-49e7-957f-9bfdc06d6...@me.com
 

  Content-Type: text/plain; charset=us-ascii

  I was trying to use the content management system for our
  website.  I needed to restart on terminal but I keep
 coming up
  with the following error:  I don't know programing at
 all, so
  don't know if this is something I can fix.


  Shared object libc.so.6 not found, required by
 fortune

  Neither the JAVA_HOME nor the JRE_HOME environment
 variable is
  defined
  At least one of these environment variable is needed to
 run this
  program
  root@psumc:/usr/local/tomcat5.**5 # bin/startup.sh


  Neither the JAVA_HOME nor the JRE_HOME environment
 variable is
  defined
  At least one of these environment variable is needed to
 run this
  program
  root@psumc:/usr/local/tomcat5.**5 # su -c 'killall
 -9

 java'


  --

  Message: 2
  Date: Sat, 29 Jun 2013 17:58:31 +0200
  From: Polytropon free...@edvax.de
 mailto:free...@edvax.de mailto:free...@edvax.de

 mailto:free...@edvax.de

  To: Rev Herbert Miller herbertmil...@me.com
 mailto:herbertmil...@me.com
  mailto:herbertmil...@me.com
 mailto:herbertmil...@me.com**
  Cc: questi...@freebsd.org
 mailto:questi...@freebsd.org mailto:questi...@freebsd.org

 mailto:questi...@freebsd.org**

  Subject: Re: question, following error Shared object
 libc.so.6 not
   found, required by fortune
  Message-ID:
 
 20130629175831.b2bf7fcb.**free...@edvax.de20130629175831.b2bf7fcb.free...@edvax.de
 
 mailto:20130629175831.**b2bf7fcb.__free...@edvax.de20130629175831.b2bf7fcb.__free...@edvax.de
 
  
 mailto:20130629175831.__**b2bf7fcb.free...@edvax.de20130629175831.__b2bf7fcb.free...@edvax.de

 
 mailto:20130629175831.**b2bf7fcb.free...@edvax.de20130629175831.b2bf7fcb.free...@edvax.de
 

  Content-Type: text/plain; charset=US-ASCII

  On Sat, 29 Jun 2013 10:48:38 -0400, Rev Herbert Miller
 wrote:

  I was trying

Re: Problems getting my Huawei 0x140b USB modem to speak to internet

Sorry for typo. 0x140b is the product ID under vendor Huawei (vendor id 
0x12d1).


Regards,

Manish Jain
+91-88064-38388


On 30-Jun-13 23:49, Manish Jain wrote:

EC156 is what the label on the modem says, which is the response given
by AT+GMM. 0x140b is the chipset.

Regards,

Manish Jain
+91-88064-38388

On 30-Jun-13 22:02, Odhiambo Washington wrote:

What model of Huawei is the modem? E-what??



On 30 June 2013 19:23, Manish Jain bourne.ident...@hotmail.com
mailto:bourne.ident...@hotmail.com wrote:


Hello Odhiambo/All,

I seem to have made some progress but final success still eludes me.
With modem symlinked to cuaU0.0, this is what happens is minicom :

AT^GETPORTMODE
^GETPORTMODE:TYPE:EV-DO:__Qualcomm,MDM:0,DIAG:1,PCUI:2,__CDROM:3

OK
AT^SETPORT=A1;1,2,3
COMMAND NOT SUPPORT

AT^GETPORTMODE succeeds, but with AT^U2DIAG/AT^SETPORT I get
COMMAND NOT SUPPORT. So how to disable the CD mode and make
FreeBSD treat it purely as a modem ? Some of the commands the modem
supports (as reported by Windows' device manager) are as follows :

ATQ0V1E0 - OK
AT+GMM - EC156
AT+FCLASS=? - 0,2.0
AT#CLS=? - COMMAND NOT SUPPORT
^HRSSILVL:80
^HDRRSSI: 31
^HRSSILVL:60
^HDRRSSI: 31


Thanks for any help.

Regards,

Manish Jain
+91-88064-38388


On 30-Jun-13 19:41, Odhiambo Washington wrote:

Hi Manish,

If you have a Windows PC, use putty.exe and point the config to
the COM
port on which the modem is detected to be attached to.
That's how I do it, unfortunately.



On 30 June 2013 16:51, Manish Jain bourne.ident...@hotmail.com
mailto:bourne.ident...@hotmail.com
mailto:bourne.identity@__hotmail.com
mailto:bourne.ident...@hotmail.com wrote:

 Hello Odhiambo/All,

 I installed and ran minicom. There are 2 devices which are
possible
 candidates as the modem : cuaU0.0 and cuaU0.2

 I symlinked modem to each of the 2 devices and ran minicom.
With
 both devices, the AT command returns OK, but AT^U2DIAG=0
returns
 COMMAND NOT SUPPORT

 Any tips on what to do next ?


 Thanks 
 Regards,

 Manish Jain
 +91-88064-38388

 On 30-Jun-13 17:30,
freebsd-questions-request@__fr__eebsd.org http://freebsd.org

 mailto:freebsd-questions-__requ...@freebsd.org
mailto:freebsd-questions-requ...@freebsd.org wrote:

 Send freebsd-questions mailing list submissions to
freebsd-questions@freebsd.org
mailto:freebsd-questions@freebsd.org
mailto:freebsd-questions@__freebsd.org
mailto:freebsd-questions@freebsd.org


 To subscribe or unsubscribe via the World Wide Web,
visit

http://lists.freebsd.org/mailman/listinfo/freebsd-questions
http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions


http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 or, via email, send a message with subject or body
'help' to
 freebsd-questions-request@__fr__eebsd.org
http://freebsd.org
 mailto:freebsd-questions-__requ...@freebsd.org
mailto:freebsd-questions-requ...@freebsd.org


 You can reach the person managing the list at
 freebsd-questions-owner@__free__bsd.org
http://freebsd.org
 mailto:freebsd-questions-__ow...@freebsd.org
mailto:freebsd-questions-ow...@freebsd.org


 When replying, please edit your Subject line so it is
more specific
 than Re: Contents of freebsd-questions digest...


 Today's Topics:

  1. question, following error Shared object
libc.so.6 not
 found, required by fortune (Rev Herbert
Miller)
  2. Re: question, following error Shared object
libc.so.6 not
 found, required by fortune (Polytropon)
  3. ALT key problem with Virtual Box? (Scott
Ballantyne)
  4. Re: ALT key problem with Virtual Box?
(Polytropon)
  5. Problems getting my Huawei 0x140b USB modem to
speak to
 internet (Manish Jain)
  6. Re: ALT key problem with Virtual Box? (Scott
Ballantyne)
  7. Baker Invites freebsd-questions@freebsd.org
mailto:freebsd-questions@freebsd.org
 mailto:freebsd-questions@__freebsd.org
mailto:freebsd-questions@freebsd.org to spend holiday

 in Goa (John Baker)
  8.  (Upali Kulasekara

Problems getting my Huawei 0x140b USB modem to speak to internet

2013-06-29 Thread Manish Jain


Hello All,

I have a a Huawei USB modem (product id 0x140b) which is connected to my 
PC. I downloaded and installed Draisberghof's usb_modeswitch.


The following are the contents of my /etc/usb_modeswitch.conf :

DisableSwitching=0
EnableLogging=1
DefaultVendor=0x12d1
DefaultProduct=0x140b
TargetVendor=0x12d1
TargetProduct=0x1446
CheckSuccess=20
MessageEndpoint=0x0f
MessageContent=55534243123456780011062001

When I run usb_modeswitch -c /etc/usb_modeswitch.conf, I get the 
following message :


Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
   found matching product ID
   adding device
 Found device in default mode, class or configuration (1)
Accessing device 010 on bus 000 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using interface number 0
Error: can't use storage command in MessageContent with interface 0;
   interface class is 255, should be 8. Aborting.


So my FreeBSD box cannot speak to internet and I have boot MS-DOG for 
this holy purpose. Can someone please suggest a remedy ?


Thanks in advance 
--
Regards,

Manish Jain
+91-88064-38388
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-06 Thread Joseph Mays


If you do a ls /dev/da* What does it show.


root@warehouse:/root # ls -la /dev/da*
crw-r-  1 root  operator0, 123 Jun  4 17:08 /dev/da0
crw-r-  1 root  operator0, 124 Jun  4 17:08 /dev/da0s1
crw-r-  1 root  operator0, 131 Jun  4 17:08 /dev/da1
crw-r-  1 root  operator0, 132 Jun  4 17:08 /dev/da1s1
crw-r-  1 root  operator0, 138 Jun  4 17:08 /dev/da2
crw-r-  1 root  operator0, 108 Jun  5 15:11 /dev/da2s1
crw-r-  1 root  operator0, 154 Jun  4 17:08 /dev/da3
crw-r-  1 root  operator0, 155 Jun  4 17:08 /dev/da3s1
crw-r-  1 root  operator0, 152 Jun  4 12:08 /dev/da3s2

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-06 Thread Lowell Gilbert

Joseph Mays m...@win.net writes:

 If you do a ls /dev/da* What does it show.

 root@warehouse:/root # ls -la /dev/da*
 crw-r-  1 root  operator0, 123 Jun  4 17:08 /dev/da0
 crw-r-  1 root  operator0, 124 Jun  4 17:08 /dev/da0s1
 crw-r-  1 root  operator0, 131 Jun  4 17:08 /dev/da1
 crw-r-  1 root  operator0, 132 Jun  4 17:08 /dev/da1s1
 crw-r-  1 root  operator0, 138 Jun  4 17:08 /dev/da2
 crw-r-  1 root  operator0, 108 Jun  5 15:11 /dev/da2s1
 crw-r-  1 root  operator0, 154 Jun  4 17:08 /dev/da3
 crw-r-  1 root  operator0, 155 Jun  4 17:08 /dev/da3s1
 crw-r-  1 root  operator0, 152 Jun  4 12:08 /dev/da3s2

Just checking the obvious: you're sure this particular disk is showing
up as da2, right?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-06 Thread Joseph Mays


Just checking the obvious: you're sure this particular disk is showing
up as da2, right?


Yes.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

USB can't mount msdosfs drive

Tried several iterations, though it’s clearly a fat32 formatted USB drive. 
Shown  below are the results of fdisk and the mount_msdosfs command.


root@warehouse:/root # fdisk /dev/da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
start 8064, size 30473088 (14879 Meg), flag 80 (active)
beg: cyl 1/ head 0/ sector 1;
end: cyl 706/ head 115/ sector 52
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

root@warehouse:/root # mount_msdosfs /dev/da2s1 /usb2
mount_msdosfs: /dev/da2s1: Invalid argument
root@warehouse:/root #
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

One item of note – I did not notice this before, the but following messages are 
appearing in dmesg whenever I try to mount this device. Note that I have 
another msdosfs usb stick mounted in usb0, that mount worked fine first try.

WARNING: mount of da2s1 denied due to unsupported optional features

From: Joseph Mays 
Sent: Wednesday, June 05, 2013 11:55 AM
To: freebsd-questions@freebsd.org 
Subject: USB can't mount msdosfs drive

Tried several iterations, though it’s clearly a fat32 formatted USB drive. 
Shown  below are the results of fdisk and the mount_msdosfs command.


root@warehouse:/root # fdisk /dev/da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
start 8064, size 30473088 (14879 Meg), flag 80 (active)
beg: cyl 1/ head 0/ sector 1;
end: cyl 706/ head 115/ sector 52
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

root@warehouse:/root # mount_msdosfs /dev/da2s1 /usb2
mount_msdosfs: /dev/da2s1: Invalid argument
root@warehouse:/root #
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-05 Thread Tijl Coosemans

On 2013-06-05 18:33, Joseph Mays wrote:
 Joseph Mays:
 Tried several iterations, though it’s clearly a fat32 formatted USB
 drive. Shown below are the results of fdisk and the mount_msdosfs
 command.
 
 
 root@warehouse:/root # fdisk /dev/da2
 *** Working on device /dev/da2 ***
 parameters extracted from in-core disklabel are:
 cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)
 
 Figures below won't work with BIOS for partitions not in cyl 1
 parameters to be used for BIOS calculations are:
 cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
 start 8064, size 30473088 (14879 Meg), flag 80 (active)
 beg: cyl 1/ head 0/ sector 1;
 end: cyl 706/ head 115/ sector 52
 The data for partition 2 is:
 UNUSED
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED
 
 root@warehouse:/root # mount_msdosfs /dev/da2s1 /usb2
 mount_msdosfs: /dev/da2s1: Invalid argument

 One item of note – I did not notice this before, the but following
 messages are appearing in dmesg whenever I try to mount this device.
 Note that I have another msdosfs usb stick mounted in usb0, that
 mount worked fine first try.
 
 WARNING: mount of da2s1 denied due to unsupported optional features

That's odd, because that warning comes from ext2fs not msdosfs. Do you
use ext2fs anywhere?
What version of FreeBSD is this? And is this just a standard installation
or do you compile your own kernel?



signature.asc
Description: OpenPGP digital signature

Re: USB can't mount msdosfs drive


WARNING: mount of da2s1 denied due to unsupported optional features



That's odd, because that warning comes from ext2fs not msdosfs. Do you
use ext2fs anywhere?
What version of FreeBSD is this? And is this just a standard installation
or do you compile your own kernel?


root@warehouse:/root # uname -a
FreeBSD warehouse 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 UTC 2012 
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64


No, I didn't compile my own kernel. The USB stick in question was stuck into 
the back of a redhat linux box. Okay, I did actually try also mounting it 
with:


mount -t ext2fs /dev/da2s1 /usb2

just to see what would happen. After trying it a couple more times I see 
that was what was adding the that warning to dmesg. So that's explained, but 
I still don't understand why I can't mount it with mount_msdosfs





-Original Message- 
From: Tijl Coosemans

Sent: Wednesday, June 05, 2013 1:36 PM
To: Joseph Mays
Cc: freebsd-questions@freebsd.org
Subject: Re: USB can't mount msdosfs drive

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-05 Thread Warren Block


On Wed, 5 Jun 2013, Joseph Mays wrote:


Tried several iterations, though it?s clearly a fat32 formatted USB drive. 
Shown  below are the results of fdisk and the mount_msdosfs command.


root@warehouse:/root # fdisk /dev/da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
   start 8064, size 30473088 (14879 Meg), flag 80 (active)
   beg: cyl 1/ head 0/ sector 1;
   end: cyl 706/ head 115/ sector 52
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

root@warehouse:/root # mount_msdosfs /dev/da2s1 /usb2
mount_msdosfs: /dev/da2s1: Invalid argument
root@warehouse:/root #


Maybe the large option to mount_msdosfs(8)?

Also, something is odd about the first partition starting at 8064. 
What does 'gpart show da2' say?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive


Maybe the large option to mount_msdosfs(8)?


Also, something is odd about the first partition starting at 8064. 
What does 'gpart show da2' say?


root@warehouse:/backups # gpart show da2
=  63  30481089  da2  MBR  (14G)
   63  8001   - free -  (3.9M)
 8064  304730881  !12  [active]  (14G)

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive


root@warehouse:/backups # mount_msdosfs -o large /dev/da2s1 /usb2
mount_msdosfs: /dev/da2s1: Invalid argument

-Original Message- 
From: Warren Block

Sent: Wednesday, June 05, 2013 2:50 PM
To: Joseph Mays
Cc: freebsd-questions@freebsd.org
Subject: Re: USB can't mount msdosfs drive

On Wed, 5 Jun 2013, Joseph Mays wrote:

Tried several iterations, though it?s clearly a fat32 formatted USB drive. 
Shown  below are the results of fdisk and the mount_msdosfs command.



root@warehouse:/root # fdisk /dev/da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1897 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
   start 8064, size 30473088 (14879 Meg), flag 80 (active)
   beg: cyl 1/ head 0/ sector 1;
   end: cyl 706/ head 115/ sector 52
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

root@warehouse:/root # mount_msdosfs /dev/da2s1 /usb2
mount_msdosfs: /dev/da2s1: Invalid argument
root@warehouse:/root #


Maybe the large option to mount_msdosfs(8)?

Also, something is odd about the first partition starting at 8064.
What does 'gpart show da2' say? 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-05 Thread Polytropon

On Wed, 5 Jun 2013 15:12:19 -0400, Joseph Mays wrote:
 root@warehouse:/backups # mount_msdosfs -o large /dev/da2s1 /usb2
 mount_msdosfs: /dev/da2s1: Invalid argument

Just a wild guess, without having tried any reference test
on my side, but did you already try to access da2 instead
of da2s1? _Sometimes_ (and I can't even tell you at _what_
times) a FAT (msdosfs) formatted media can be mounted in
that specific way (even though I assume that in such a
case, no slice device would be present - but as I said,
just a guess maybe worth a try).

# mount_msdosfs /dev/da2 /usb2

But just to be fully sure: This is a USB stick / thumb
drive, right? It's not some internal card reader (which
would probably require re-tasting)? Just asking to make
sure I haven't missed this fact while reading...



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive


did you already try to access da2 instead of da2s1?


Yeah, tried that early on, got the same result.

root@warehouse:/backups/postgres-02/info # mount_msdosfs /dev/da2 /usb2
mount_msdosfs: /dev/da2: Invalid argument


But just to be fully sure: This is a USB stick / thumb drive, right?


Yes. It's one of several thumb drives that were mounted in the back of some 
linux machines at remote sites we help a customer with. The client is unsure 
what was on them, but needs to know. We asked them to gather them up and 
stick them into usb ports on a freebsd machine we have access to and manage 
at their location (in another state). Most of them I got mounted as either 
msdosfs, or ufs, or ntfs, or extfs2, and was able to get the data off them. 
This thumb drive is one of two holdouts.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-05 Thread Jerry

On Wed, 5 Jun 2013 16:12:59 -0400
Joseph Mays articulated:

 Yes. It's one of several thumb drives that were mounted in the back
 of some linux machines at remote sites we help a customer with. The
 client is unsure what was on them, but needs to know. We asked them
 to gather them up and stick them into usb ports on a freebsd machine
 we have access to and manage at their location (in another state).
 Most of them I got mounted as either msdosfs, or ufs, or ntfs, or
 extfs2, and was able to get the data off them. This thumb drive is
 one of two holdouts.

Is it possible that they are petitioned as exFAT (Extended File
Allocation Table) drives? That is how I partition all of my flash drives.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB can't mount msdosfs drive

2013-06-05 Thread Bernt Hansson


On 2013-06-05 22:12, Joseph Mays wrote:

did you already try to access da2 instead of da2s1?


Yeah, tried that early on, got the same result.

root@warehouse:/backups/postgres-02/info # mount_msdosfs /dev/da2 /usb2
mount_msdosfs: /dev/da2: Invalid argument


But just to be fully sure: This is a USB stick / thumb drive, right?


Yes. It's one of several thumb drives that were mounted in the back of
some linux machines at remote sites we help a customer with. The client
is unsure what was on them, but needs to know. We asked them to gather
them up and stick them into usb ports on a freebsd machine we have
access to and manage at their location (in another state). Most of them
I got mounted as either msdosfs, or ufs, or ntfs, or extfs2, and was
able to get the data off them. This thumb drive is one of two holdouts.


If you do a ls /dev/da* What does it show.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Recommendations for 64GB USB 3.0 Sticks?

2013-05-27 Thread Jens Schweikhardt

hello, world\n

I have a problem with a USB 2.0 64GB Stick, that's not recognized by
FreeBSD 9 (Corsair Survivor). I have also read other people having
problems with large size sticks (=64GB). Has anyone a recommendation
for a 64GB USB 3.0 stick? Preferably with read and write speeds
=100MByte/s, respectively.

Regards,

Jens
-- 
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB Flash Drive in Stock

2013-04-02 Thread notruiruiwa...@163.com

   Hi,


   Glad to hear that you're on the market for usb driver memory, we are
   experienced in this field for about 8 years.


There is much experience in usb driver memory with higher quality.


What’s more, we have our own RD to meet any of your requirements.


   There are usb driver memory in stock and the quotation as follows:

   1GB: EXW US$2.10, 2GB: EXW US$2.42, 4GB: EXW US$2.91, 8GB: EXW US$3.55,
   16GB: EXW US$6.13, 32GB: EXW US$10.49, 64GB: EXW US$ 22.26, 128GB: EXW
   US$ 25.49, 256GB: EXW US$30.33

   M.O.Q: 500PCS


Please contact us without any hesitation if there is anything we can
   do for you.


Look forward to hearing from you and establishing friendly business
   relationship between us.


Best Regards.

   Jane2
attachment: USB_Flash_Drive.jpg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB Flash Drive in Stock

2013-04-02 Thread notruiruiwa...@163.com

   Hi,


   Glad to hear that you're on the market for usb driver memory, we are
   experienced in this field for about 8 years.


There is much experience in usb driver memory with higher quality.


What’s more, we have our own RD to meet any of your requirements.


   There are usb driver memory in stock and the quotation as follows:

   1GB: EXW US$2.10, 2GB: EXW US$2.42, 4GB: EXW US$2.91, 8GB: EXW US$3.55,
   16GB: EXW US$6.13, 32GB: EXW US$10.49, 64GB: EXW US$ 22.26, 128GB: EXW
   US$ 25.49, 256GB: EXW US$30.33

   M.O.Q: 500PCS


Please contact us without any hesitation if there is anything we can
   do for you.


Look forward to hearing from you and establishing friendly business
   relationship between us.


Best Regards.

   Jane2
attachment: USB_Flash_Drive.jpg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Ronald F. Guilmette


In message 5153a2fd.8020...@sneakertech.com, you wrote:


  Why exactly is the bs=10240 is there?  Wouldn't the default of 512
  do just as well?

Modern systems can read and write far more than 512 bytes per operation. 
Sticking with 512 would work perfectly fine, but you'd be imposing an 
unnecessary bottleneck and the copy would be a lot slower overall. 
Whether 10K is optimal or not depends on the exact hardware you're 
messing with (it looks pretty low to me, I'd suggest more like 1M).


I agree.  And 10 kibibytes is probably quite a bit less than optimal.

I have filed the following PR:

http://www.freebsd.org/cgi/query-pr.cgi?pr=177431

Thank you for your reply.


Regards,
rfg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Quartz




I have filed the following PR:

http://www.freebsd.org/cgi/query-pr.cgi?pr=177431


Er, don't take my word for law: I have *no* idea if 1M is a good idea 
for most systems, I'm not even sure if it's optimal for mine. I did a 
single test with three random values at different orders of magnitude 
and picked the fastest. I do think that 10k is probably way under the 
right value, but someone should do proper testing on a variety of 
hardware before changing all the docs.


As for the conv=sync option, I'm not convinced it's necessary either 
way. I've dd'd zillions of images to various media over the years and 
have never specified a conv parameter and I've never had problems. I 
don't think modern systems really care what the end is padded with 
(provided nothing is corrupt of course). Someone with more experience 
would need to chime in on this.


__
it has a certain smooth-brained appeal
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Steve O'Hara-Smith

On Thu, 28 Mar 2013 04:27:43 -0400
Quartz qua...@sneakertech.com wrote:

 
  I have filed the following PR:
 
  http://www.freebsd.org/cgi/query-pr.cgi?pr=177431
 
 Er, don't take my word for law: I have *no* idea if 1M is a good idea 
 for most systems, I'm not even sure if it's optimal for mine. I did a 
 single test with three random values at different orders of magnitude 
 and picked the fastest. I do think that 10k is probably way under the 
 right value, but someone should do proper testing on a variety of 
 hardware before changing all the docs.

The 1M will work fine, it's way bigger than any physical write. In
theory the performance should max out when the block size matches the
maximum physical write size of the controller (often 64K), but that assumes
zero read latency on the data feed so in practice larger block sizes help,
but except for things like tape they don't help much once you pass the
device/controller max write block size.

-- 
Steve O'Hara-Smith st...@sohara.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Ronald F. Guilmette


In message 5153feff.4090...@sneakertech.com, you wrote:


 I have filed the following PR:

 http://www.freebsd.org/cgi/query-pr.cgi?pr=177431

Er, don't take my word for law:

I didn't.  I won't.

I have *no* idea if 1M is a good idea 

Any size which is an exact multiple of the physical block size for
the target device should provide performance which is as good as
it gets.

I googled around and read various comments.  Some of these kinds
of devices have a physical block size of 64KiB.  Some have 128KiB.
Some have 256KiB.  Some have 1MiB.

For all of these devices, seting blocksize to 1MiB will provide optimal
performance with at worst only a _relatively_ tiny waste of space.

As for the conv=sync option, I'm not convinced it's necessary either 
way.

Neither am I, but I would rather have it there, than not and take
chances.

It won't hurt anything, and it appears that it _may_ perhaps help.

I don't think modern systems really care what the end is padded with 

That wasn't my concern.  My concern is that I personally do not know
what the officially defined semantics are in cases where dd is asked
to copy data in a specific input block size _and_ the actual data
available from the input device doesn't perfectly fill up that last
block.

It is possible, I would guess, that dd may notice the EOF occuring
before it has filled up an entire input buffer, and then just quit
at that point, _without_ writing the partial last block to the
output device.

It seems to me that conv=sync is cheap insurance against this
possibility.

I have always been a belt and suspenders kind of guy.


Regards,
rfg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Arthur Chance


On 03/28/13 10:32, Ronald F. Guilmette wrote:


In message 5153feff.4090...@sneakertech.com, you wrote:




I have filed the following PR:

http://www.freebsd.org/cgi/query-pr.cgi?pr=177431


Er, don't take my word for law:


I didn't.  I won't.


I have *no* idea if 1M is a good idea


Any size which is an exact multiple of the physical block size for
the target device should provide performance which is as good as
it gets.

I googled around and read various comments.  Some of these kinds
of devices have a physical block size of 64KiB.  Some have 128KiB.
Some have 256KiB.  Some have 1MiB.

For all of these devices, seting blocksize to 1MiB will provide optimal
performance with at worst only a _relatively_ tiny waste of space.


As for the conv=sync option, I'm not convinced it's necessary either
way.


Neither am I, but I would rather have it there, than not and take
chances.

It won't hurt anything, and it appears that it _may_ perhaps help.


I don't think modern systems really care what the end is padded with


That wasn't my concern.  My concern is that I personally do not know
what the officially defined semantics are in cases where dd is asked
to copy data in a specific input block size _and_ the actual data
available from the input device doesn't perfectly fill up that last
block.

It is possible, I would guess, that dd may notice the EOF occuring
before it has filled up an entire input buffer, and then just quit
at that point, _without_ writing the partial last block to the
output device.


It will attempt to write a short block. E.g.

arthur@fileserver[2] ls -l t.pdf
-rw-rw-r--  1 arthur  arthur  233812 Feb 18 12:26 t.pdf
arthur@fileserver[2] dd if=t.pdf of=/dev/null bs=1k
228+1 records in
228+1 records out
233812 bytes transferred in 0.036731 secs (6365521 bytes/sec)

Those +1 records are the final short block.


It seems to me that conv=sync is cheap insurance against this
possibility.


It's used as an insurance against output devices which have a fixed (or 
in the case of tape, a minimum) block size. If the short block is not an 
exact integer multiple of the device block size then the final write 
will fail. conv=sync and a bs (or obs) that's a strict multiple of block 
size prevents the problem. That's exactly your use case.



I have always been a belt and suspenders kind of guy.


Show me the experienced sysadmin who isn't. Invariably learnt the hard 
way. :-}



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Release 9.1 and 3G usb Modem

2013-03-28 Thread Leonardo Santagostini

Well, after trying so many things with no luck, i will give a try on ubuntu.

I must say all the support that give to me Odhiambo was excellent. Thanks
to all of you, thanks Odhiambo for all your effort.

Lets see what happen.

Saludos / Regards
Leonardo Santagostini

http://ar.linkedin.com/in/santagostini





2013/3/27 Matthias Apitz g...@unixarea.de

 El día Wednesday, March 27, 2013 a las 05:09:22PM -0300, Leonardo
 Santagostini escribió:

  Hello Odhiambo .
 
  The 3G model is Huawei E173 with Movistar Argentina.
 
  Ive tried but i cant see in windows de USB port to have a serial link :(
 
  Saludos / Regards
  Leonardo Santagostini

 Hi,

 Pls check if this E173 card is supported by the /sys/dev/usb/serial/u3g.c
 driver; figure out the vendorID and productID of this card and check if
 it is in the driver to attach to; I own an E220 and an E1750 Huawei card,
 both are just working fine without any tricks.

 matthias
 --
 Sent from my FreeBSD netbook

 Matthias Apitz   |  - No system with backdoors like
 Apple/Android
 E-mail: g...@unixarea.de |  - Never being an iSlave
 WWW: http://www.unixarea.de/ |  - No proprietary attachments, no HTML/RTF
 in E-mail
 phone: +49-170-4527211   |  - Respect for open standards

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-28 Thread Ronald F. Guilmette


In message 51543b7a.4030...@qeng-ho.org, 
Arthur Chance free...@qeng-ho.org wrote:

On 03/28/13 10:32, Ronald F. Guilmette wrote:
 It is possible, I would guess, that dd may notice the EOF occuring
 before it has filled up an entire input buffer, and then just quit
 at that point, _without_ writing the partial last block to the
 output device.

It will attempt to write a short block. E.g.

arthur@fileserver[2] ls -l t.pdf
-rw-rw-r--  1 arthur  arthur  233812 Feb 18 12:26 t.pdf
arthur@fileserver[2] dd if=t.pdf of=/dev/null bs=1k
228+1 records in
228+1 records out
233812 bytes transferred in 0.036731 secs (6365521 bytes/sec)

Those +1 records are the final short block.

OK.  Thanks.  That's definitely good to know.

I wonder if this behavior is documented in the man page.  (It certainly
should be, if it isn't already.)

 It seems to me that conv=sync is cheap insurance against this
 possibility.

It's used as an insurance against output devices which have a fixed (or 
in the case of tape, a minimum) block size. If the short block is not an 
exact integer multiple of the device block size then the final write 
will fail.

Right.  I understand.

conv=sync and a bs (or obs) that's a strict multiple of block 
size prevents the problem. That's exactly your use case.

Right.


Regards,
rfg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Release 9.1 and 3G usb Modem

2013-03-27 Thread Leonardo Santagostini

Hello all.

I have a latitude e6400 with FreeBSD Release 9.1. And i can't get the USB
modem working.

I tried with umodem, u3g but no luck :(

-- Dmesg
root@:/root # dmesg
Copyright (c) 1992-2012 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 9.1-RELEASE #0 r243826: Tue Dec  4 06:55:39 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
CPU: Intel(R) Core(TM)2 Duo CPU P8400  @ 2.26GHz (2261.05-MHz 686-class
CPU)
  Origin = GenuineIntel  Id = 0x1067a  Family = 6  Model = 17  Stepping =
10

Features=0xbfebfbffFPU,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,PBE

Features2=0x408e3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE
  AMD Features=0x2010NX,LM
  AMD Features2=0x1LAHF
  TSC: P-state invariant, performance statistics
real memory  = 2147483648 (2048 MB)
avail memory = 1967104000 (1875 MB)
Event timer LAPIC quality 400
ACPI APIC Table: DELL   M09
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 2
ioapic0 Version 2.0 irqs 0-23 on motherboard
kbd1 at kbdmux0
kqemu version 0x00010400
kqemu: KQEMU installed, max_locked_mem=980872kB.
acpi0: DELL M09 on motherboard
Timecounter HPET frequency 14318180 Hz quality 950
Event timer HPET frequency 14318180 Hz quality 450
Event timer HPET1 frequency 14318180 Hz quality 440
Event timer HPET2 frequency 14318180 Hz quality 440
Event timer HPET3 frequency 14318180 Hz quality 440
acpi0: reservation of 0, 9f000 (3) failed
acpi0: reservation of 10, 78f4d400 (3) failed
cpu0: ACPI CPU on acpi0
cpu1: ACPI CPU on acpi0
atrtc0: AT realtime clock port 0x70-0x71,0x72-0x77 irq 8 on acpi0
Event timer RTC frequency 32768 Hz quality 0
attimer0: AT timer port 0x40-0x43,0x50-0x53 irq 2 on acpi0
Timecounter i8254 frequency 1193182 Hz quality 0
Event timer i8254 frequency 1193182 Hz quality 100
Timecounter ACPI-fast frequency 3579545 Hz quality 900
acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
acpi_ec0: Embedded Controller: GPE 0x11 port 0x930,0x934 on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
vgapci0: VGA-compatible display port 0xef70-0xef77 mem
0xf6c0-0xf6ff,0xe000-0xefff irq 16 at device 2.0 on pci0
agp0: Intel GM45 SVGA controller on vgapci0
agp0: aperture size is 256M, detected 32764k stolen memory
vgapci1: VGA-compatible display mem 0xf6b0-0xf6bf at device 2.1
on pci0
pci0: simple comms at device 3.0 (no driver attached)
atapci0: Intel ATA controller port
0xef78-0xef7f,0xef68-0xef6b,0xef80-0xef87,0xef6c-0xef6f,0xef90-0xef9f irq
18 at device 3.2 on pci0
ata2: ATA channel at channel 0 on atapci0
ata3: ATA channel at channel 1 on atapci0
pci0: simple comms, UART at device 3.3 (no driver attached)
em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xefe0-0xefff mem
0xf6ae-0xf6af,0xf6adb000-0xf6adbfff irq 22 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:1e:c9:25:e8:07
uhci0: Intel 82801I (ICH9) USB controller port 0x6f60-0x6f7f irq 20 at
device 26.0 on pci0
uhci0: LegSup = 0x2f00
usbus0 on uhci0
uhci1: Intel 82801I (ICH9) USB controller port 0x6f80-0x6f9f irq 21 at
device 26.1 on pci0
uhci1: LegSup = 0x2f00
usbus1 on uhci1
uhci2: Intel 82801I (ICH9) USB controller port 0x6fa0-0x6fbf irq 22 at
device 26.2 on pci0
uhci2: LegSup = 0x2f00
usbus2 on uhci2
ehci0: Intel 82801I (ICH9) USB 2.0 controller mem 0xfed1c400-0xfed1c7ff
irq 22 at device 26.7 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci0
hdac0: Intel 82801I HDA Controller mem 0xf6adc000-0xf6ad irq 21 at
device 27.0 on pci0
pcib1: ACPI PCI-PCI bridge at device 28.0 on pci0
pci11: ACPI PCI bus on pcib1
pcib2: ACPI PCI-PCI bridge at device 28.1 on pci0
pci12: ACPI PCI bus on pcib2
iwn0: Intel Ultimate N WiFi Link 5300 mem 0xf69fe000-0xf69f irq 17 at
device 0.0 on pci12
pcib3: ACPI PCI-PCI bridge at device 28.2 on pci0
pci13: ACPI PCI bus on pcib3
uhci3: Intel 82801I (ICH9) USB controller port 0x6f00-0x6f1f irq 20 at
device 29.0 on pci0
uhci3: LegSup = 0x2f00
usbus4 on uhci3
uhci4: Intel 82801I (ICH9) USB controller port 0x6f20-0x6f3f irq 21 at
device 29.1 on pci0
uhci4: LegSup = 0x2f00
usbus5 on uhci4
uhci5: Intel 82801I (ICH9) USB controller port 0x6f40-0x6f5f irq 22 at
device 29.2 on pci0
uhci5: LegSup = 0x2f00
usbus6 on uhci5
ehci1: Intel 82801I (ICH9) USB 2.0 controller mem 0xfed1c000-0xfed1c3ff
irq 20 at device 29.7 on pci0
usbus7: EHCI version 1.0
usbus7 on ehci1
pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0
pci3: ACPI PCI bus on pcib4
cbb0: RF5C476 PCI-CardBus Bridge irq 19 at device 1.0 on pci3
cardbus0: CardBus bus on cbb0
pccard0: 16-bit

Re: Release 9.1 and 3G usb Modem

2013-03-27 Thread Odhiambo Washington

On 27 March 2013 16:29, Leonardo Santagostini lsantagost...@gmail.comwrote:

 Hello all.

 I have a latitude e6400 with FreeBSD Release 9.1. And i can't get the USB
 modem working.

 I tried with umodem, u3g but no luck :(


[snip]


 ugen7.2: HUAWEI at usbus7
 ugen7.2: HUAWEI at usbus7 (disconnected)
 ugen7.2: HUAWEI at usbus7
 umodem0: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on usbus7
 umodem0: data interface 0, has no CM over data, has no break
 umodem1: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on usbus7
 umodem1: data interface 1, has no CM over data, has no break
 umodem2: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on usbus7
 umodem2: data interface 2, has no CM over data, has no break
 umass0: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on usbus7
 umass0:  SCSI over Bulk-Only; quirks = 0x
 umass0:9:0:-1: Attached to scbus9
 cd1 at umass-sim0 bus 0 scbus9 target 0 lun 0
 cd1: HUAWEI Mass Storage 2.31 Removable CD-ROM SCSI-2 device
 cd1: 40.000MB/s transfers
 cd1: Attempt to query device size failed: NOT READY, Medium not present
 umass1: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on usbus7
 umass1:  SCSI over Bulk-Only; quirks = 0x
 umass1:10:1:-1: Attached to scbus10
 da0 at umass-sim1 bus 1 scbus10 target 0 lun 0
 da0: HUAWEI SD Storage 2.31 Removable Direct Access SCSI-2 device
 da0: 40.000MB/s transfers
 da0: Attempt to query device size failed: NOT READY, Medium not present



[snip]

Huawei modem, as I can see. That should be easy.

Connect to the modem through HyperTerminal or Putty on a different machine
Issue the command: AT^U2DIAG=0
That should disable the virtual CD-ROM and FreeBSD will see the modem.

Here are some commands you'll need to know about:
Do you have a Windows PC near you? If you plug the device into it and the
virtualCD pops up, then it means command was not successful. The fact that
fake CD still shows means command did not succeed!

AT^u2diag=0 (all off)
AT^u2diag=1 (CD on, SD off)
AT^u2diag=256 (CD off, SD is on)
AT^u2diag=255 (all on - including SD Card)
AT^u2diag=276 (Factory Reset)
A+CLAC - Display all available commands. However it does not tell you how
to use them



And here is a working ppp.conf - but you need to change the *bolded* values
to match your end of the environment:)

u3g:
 set device */dev/cuaU0.0*
 set server /var/run/3g-internet  0177
 set speed 921600
 set timeout 0
 set authname *saf*
 set authkey *data*
 set dial ABORT BUSY ABORT NO\\sTIMEOUT 2 \
   \\ \
   AT OK-AT-OK \
   AT+CFUN=1 OK-AT-OK \
   AT+CMEE=2 OK-AT-OK \
   AT+CSQ OK \
   AT+CGDCONT=1,\\\IP\\\,\\\*APN*\\\ OK \
   ATD**99#* CONNECT
 set crtscts on
 disable vjcomp
 disable acfcomp
 disable deflate
 disable deflate24
 disable pred1
 disable protocomp
 disable mppe
 disable ipv6cp
 disable lqr
 disable echo
 #nat enable yes
 enable dns
 resolv writable
 set dns 8.8.8.8
 set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0
 add default HISADDR  # See ppp.link*


Lemme know if you get stuck.

Also, always give details about modem - manufacturer, model...


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
I can't hear you -- I'm using the scrambler.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Release 9.1 and 3G usb Modem

2013-03-27 Thread Leonardo Santagostini

Hello Odhiambo .

The 3G model is Huawei E173 with Movistar Argentina.

Ive tried but i cant see in windows de USB port to have a serial link :(

Saludos / Regards
Leonardo Santagostini





2013/3/27 Odhiambo Washington odhia...@gmail.com


 On 27 March 2013 16:29, Leonardo Santagostini lsantagost...@gmail.comwrote:

 Hello all.

 I have a latitude e6400 with FreeBSD Release 9.1. And i can't get the USB
 modem working.

 I tried with umodem, u3g but no luck :(


 [snip]


 ugen7.2: HUAWEI at usbus7
 ugen7.2: HUAWEI at usbus7 (disconnected)
 ugen7.2: HUAWEI at usbus7
 umodem0: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umodem0: data interface 0, has no CM over data, has no break
 umodem1: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umodem1: data interface 1, has no CM over data, has no break
 umodem2: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umodem2: data interface 2, has no CM over data, has no break
 umass0: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on usbus7
 umass0:  SCSI over Bulk-Only; quirks = 0x
 umass0:9:0:-1: Attached to scbus9
 cd1 at umass-sim0 bus 0 scbus9 target 0 lun 0
 cd1: HUAWEI Mass Storage 2.31 Removable CD-ROM SCSI-2 device
 cd1: 40.000MB/s transfers
 cd1: Attempt to query device size failed: NOT READY, Medium not present
 umass1: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on usbus7
 umass1:  SCSI over Bulk-Only; quirks = 0x
 umass1:10:1:-1: Attached to scbus10
 da0 at umass-sim1 bus 1 scbus10 target 0 lun 0
 da0: HUAWEI SD Storage 2.31 Removable Direct Access SCSI-2 device
 da0: 40.000MB/s transfers
 da0: Attempt to query device size failed: NOT READY, Medium not present



 [snip]

 Huawei modem, as I can see. That should be easy.

 Connect to the modem through HyperTerminal or Putty on a different machine
 Issue the command: AT^U2DIAG=0
 That should disable the virtual CD-ROM and FreeBSD will see the modem.

 Here are some commands you'll need to know about:
 Do you have a Windows PC near you? If you plug the device into it and the
 virtualCD pops up, then it means command was not successful. The fact that
 fake CD still shows means command did not succeed!

 AT^u2diag=0 (all off)
 AT^u2diag=1 (CD on, SD off)
 AT^u2diag=256 (CD off, SD is on)
 AT^u2diag=255 (all on - including SD Card)
 AT^u2diag=276 (Factory Reset)
 A+CLAC - Display all available commands. However it does not tell you how
 to use them



 And here is a working ppp.conf - but you need to change the *bolded* values
 to match your end of the environment:)

 u3g:
  set device */dev/cuaU0.0*
  set server /var/run/3g-internet  0177
  set speed 921600
  set timeout 0
  set authname *saf*
  set authkey *data*
  set dial ABORT BUSY ABORT NO\\sTIMEOUT 2 \
\\ \
AT OK-AT-OK \
AT+CFUN=1 OK-AT-OK \
AT+CMEE=2 OK-AT-OK \
AT+CSQ OK \
AT+CGDCONT=1,\\\IP\\\,\\\*APN*\\\ OK \
ATD**99#* CONNECT
  set crtscts on
  disable vjcomp
  disable acfcomp
  disable deflate
  disable deflate24
  disable pred1
  disable protocomp
  disable mppe
  disable ipv6cp
  disable lqr
  disable echo
  #nat enable yes
  enable dns
  resolv writable
  set dns 8.8.8.8
  set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0
  add default HISADDR  # See ppp.link*


 Lemme know if you get stuck.

 Also, always give details about modem - manufacturer, model...


 --
 Best regards,
 Odhiambo WASHINGTON,
 Nairobi,KE
 +254733744121/+254722743223
 I can't hear you -- I'm using the scrambler.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Release 9.1 and 3G usb Modem

2013-03-27 Thread Odhiambo Washington

On Windows, install the modem drivers and make it usable.
Then connect to the port on which it is installed using putty or
HyperTerminal. I am hoping you know how to do that.
Then type the commands:

at^u2diag=0 ENTER
atz ENTER

Disconnect modem and connect to FreeBSD. You will see the modem correctly
identified and connected to a port.

On Windows, when you go to Hardware-Device Manager, look at the Serial
ports available. One of them MUST be the one the modem is using!




On 27 March 2013 23:09, Leonardo Santagostini lsantagost...@gmail.comwrote:

 Hello Odhiambo .

 The 3G model is Huawei E173 with Movistar Argentina.

 Ive tried but i cant see in windows de USB port to have a serial link :(

 Saludos / Regards
  Leonardo Santagostini





 2013/3/27 Odhiambo Washington odhia...@gmail.com


 On 27 March 2013 16:29, Leonardo Santagostini lsantagost...@gmail.comwrote:

 Hello all.

 I have a latitude e6400 with FreeBSD Release 9.1. And i can't get the USB
 modem working.

 I tried with umodem, u3g but no luck :(


 [snip]


 ugen7.2: HUAWEI at usbus7
 ugen7.2: HUAWEI at usbus7 (disconnected)
 ugen7.2: HUAWEI at usbus7
 umodem0: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umodem0: data interface 0, has no CM over data, has no break
 umodem1: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umodem1: data interface 1, has no CM over data, has no break
 umodem2: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umodem2: data interface 2, has no CM over data, has no break
 umass0: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umass0:  SCSI over Bulk-Only; quirks = 0x
 umass0:9:0:-1: Attached to scbus9
 cd1 at umass-sim0 bus 0 scbus9 target 0 lun 0
 cd1: HUAWEI Mass Storage 2.31 Removable CD-ROM SCSI-2 device
 cd1: 40.000MB/s transfers
 cd1: Attempt to query device size failed: NOT READY, Medium not present
 umass1: HUAWEI HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 2 on
 usbus7
 umass1:  SCSI over Bulk-Only; quirks = 0x
 umass1:10:1:-1: Attached to scbus10
 da0 at umass-sim1 bus 1 scbus10 target 0 lun 0
 da0: HUAWEI SD Storage 2.31 Removable Direct Access SCSI-2 device
 da0: 40.000MB/s transfers
 da0: Attempt to query device size failed: NOT READY, Medium not present



 [snip]

 Huawei modem, as I can see. That should be easy.

 Connect to the modem through HyperTerminal or Putty on a different machine
 Issue the command: AT^U2DIAG=0
 That should disable the virtual CD-ROM and FreeBSD will see the modem.

 Here are some commands you'll need to know about:
 Do you have a Windows PC near you? If you plug the device into it and the
 virtualCD pops up, then it means command was not successful. The fact that
 fake CD still shows means command did not succeed!

 AT^u2diag=0 (all off)
 AT^u2diag=1 (CD on, SD off)
 AT^u2diag=256 (CD off, SD is on)
 AT^u2diag=255 (all on - including SD Card)
 AT^u2diag=276 (Factory Reset)
 A+CLAC - Display all available commands. However it does not tell you how
 to use them



 And here is a working ppp.conf - but you need to change the *bolded* values
 to match your end of the environment:)

 u3g:
  set device */dev/cuaU0.0*
  set server /var/run/3g-internet  0177
  set speed 921600
  set timeout 0
  set authname *saf*
  set authkey *data*
  set dial ABORT BUSY ABORT NO\\sTIMEOUT 2 \
\\ \
AT OK-AT-OK \
AT+CFUN=1 OK-AT-OK \
AT+CMEE=2 OK-AT-OK \
AT+CSQ OK \
AT+CGDCONT=1,\\\IP\\\,\\\*APN*\\\ OK \
ATD**99#* CONNECT
  set crtscts on
  disable vjcomp
  disable acfcomp
  disable deflate
  disable deflate24
  disable pred1
  disable protocomp
  disable mppe
  disable ipv6cp
  disable lqr
  disable echo
  #nat enable yes
  enable dns
  resolv writable
  set dns 8.8.8.8
  set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0
  add default HISADDR  # See ppp.link*


 Lemme know if you get stuck.

 Also, always give details about modem - manufacturer, model...


 --
 Best regards,
 Odhiambo WASHINGTON,
 Nairobi,KE
 +254733744121/+254722743223
 I can't hear you -- I'm using the scrambler.





-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
I can't hear you -- I'm using the scrambler.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Release 9.1 and 3G usb Modem

2013-03-27 Thread Matthias Apitz

El día Wednesday, March 27, 2013 a las 05:09:22PM -0300, Leonardo Santagostini 
escribió:

 Hello Odhiambo .
 
 The 3G model is Huawei E173 with Movistar Argentina.
 
 Ive tried but i cant see in windows de USB port to have a serial link :(
 
 Saludos / Regards
 Leonardo Santagostini

Hi,

Pls check if this E173 card is supported by the /sys/dev/usb/serial/u3g.c
driver; figure out the vendorID and productID of this card and check if
it is in the driver to attach to; I own an E220 and an E1750 Huawei card,
both are just working fine without any tricks.

matthias
-- 
Sent from my FreeBSD netbook

Matthias Apitz   |  - No system with backdoors like Apple/Android
E-mail: g...@unixarea.de |  - Never being an iSlave
WWW: http://www.unixarea.de/ |  - No proprietary attachments, no HTML/RTF in 
E-mail
phone: +49-170-4527211   |  - Respect for open standards
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Ronald F. Guilmette


I've never used any FreeBSD memstick image before, but now I have reason
to do so.

I'm reading the instructions for creating a bootable memstick that are
located on this page:

  http://www.freebsd.org/releases/9.1R/announce.html

which include the following example of how to perform the copy:

  # dd if=FreeBSD-9.1-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

Question:

   Why exactly is conv=sync is there?

   Also, in practice what does it actually do?  (I've used dd plenty in my
   lifetime, but never found any reason to use conv= at all.  I always
   thought that it was... mostly... just an archaic leftover from the days
   when some big iron used EBCDIC that needed to get converted to ASCII
   or vise versa.)

   The dd man page describes the sync type of conversion thusly:
   Pad every input block to the input buffer size.  Spaces are used for
   pad bytes if a block oriented conversion value is specified, otherwise
   NUL bytes are used.  Ummm... ok.  WTF is a block oriented conversion
   value?  How would I know if I had specified one?

Question:

Why exactly is the bs=10240 is there?  Wouldn't the default of 512
do just as well?


Regards,
rfg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Release 9.1 and 3G usb Modem

2013-03-27 Thread Leonardo Santagostini

Hello Matthias,

thanks for your response, Odhiambo was helping me with this modem with no
luck. Tomorrow we will continuing trying to get this modem running.

Thanks all, and thanks Odhiambo for all the support he is giving to get
this piece working :)

I really apreciate it !!!

Saludos / Regards
Leonardo Santagostini






2013/3/27 Matthias Apitz g...@unixarea.de

 El día Wednesday, March 27, 2013 a las 05:09:22PM -0300, Leonardo
 Santagostini escribió:

  Hello Odhiambo .
 
  The 3G model is Huawei E173 with Movistar Argentina.
 
  Ive tried but i cant see in windows de USB port to have a serial link :(
 
  Saludos / Regards
  Leonardo Santagostini

 Hi,

 Pls check if this E173 card is supported by the /sys/dev/usb/serial/u3g.c
 driver; figure out the vendorID and productID of this card and check if
 it is in the driver to attach to; I own an E220 and an E1750 Huawei card,
 both are just working fine without any tricks.

 matthias
 --
 Sent from my FreeBSD netbook

 Matthias Apitz   |  - No system with backdoors like
 Apple/Android
 E-mail: g...@unixarea.de |  - Never being an iSlave
 WWW: http://www.unixarea.de/ |  - No proprietary attachments, no HTML/RTF
 in E-mail
 phone: +49-170-4527211   |  - Respect for open standards

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Dan Nelson

In the last episode (Mar 27), Ronald F. Guilmette said:
 I've never used any FreeBSD memstick image before, but now I have reason
 to do so.
 
 I'm reading the instructions for creating a bootable memstick that are
 located on this page:
 
   http://www.freebsd.org/releases/9.1R/announce.html
 
 which include the following example of how to perform the copy:
 
   # dd if=FreeBSD-9.1-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 
 conv=sync
 
 Question:
 
Why exactly is conv=sync is there?

 Question:
 
 Why exactly is the bs=10240 is there?  Wouldn't the default of 512
 do just as well?

It looks like someone just copied a dd commandline from somewhere else,
maybe something to do with tar files (since tar defaults to a 10k blocksize
when writing to tape).  conv=sync isn't needed since the source file is
already a multiple of the target device blocksize (512 bytes), and bs=64k
would be much faster when writing to cheap flash devices like USB sticks
since they don't have a write cache and individual writes are slowish.

-- 
Dan Nelson
dnel...@allantgroup.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Daniel O'Callaghan


On 28/03/2013 8:10 AM, Ronald F. Guilmette wrote:

Question:

Why exactly is conv=sync is there?

I found this on http://www.mkssoftware.com/docs/man1/dd.1.asp

If you specified conv=sync and this input block is smaller than the 
specified input block size, dd pads it to the specified size with null 
bytes. When you also specify a block or unblock conversion, dd uses 
spaces instead of null bytes.


So the last block of output gets padded with 0x00 at the end to fill the 
input block size (from bs=...)



Question:

 Why exactly is the bs=10240 is there?  Wouldn't the default of 512
 do just as well?
It would, but then you would have FILESIZE/512 reads and writes instead 
of FILESIZE/10240 reads and writes - 20 times more.

The end result is the same, but the large bs makes the operation go faster.
I routinely use bs=655360 simply because it is a big number divisible by 
512, which I can easily remember.  512000 would do just as well, though...


Danny

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Copying memstick image to a USB (flash/thumb) drive

2013-03-27 Thread Quartz




 Why exactly is the bs=10240 is there?  Wouldn't the default of 512
 do just as well?


Modern systems can read and write far more than 512 bytes per operation. 
Sticking with 512 would work perfectly fine, but you'd be imposing an 
unnecessary bottleneck and the copy would be a lot slower overall. 
Whether 10K is optimal or not depends on the exact hardware you're 
messing with (it looks pretty low to me, I'd suggest more like 1M).


__
it has a certain smooth-brained appeal
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

USB Flash Drive in Stock

2013-03-20 Thread qq1595544360...@163.com

   Hi,


   Glad to hear that you're on the market for usb driver memory, we are
   experienced in this field for about 8 years.


There is much experience in usb driver memory with higher quality.


What’s more, we have our own RD to meet any of your requirements.


   There are usb driver memory in stock and the quotation as follows:

   1GB: EXW US$2.10, 2GB: EXW US$2.42, 4GB: EXW US$2.91, 8GB: EXW US$3.55,
   16GB: EXW US$6.13, 32GB: EXW US$10.49, 64GB: EXW US$ 22.26, 128GB: EXW
   US$ 25.49, 256GB: EXW US$30.33

   M.O.Q: 500PCS


Please contact us without any hesitation if there is anything we can
   do for you.


Look forward to hearing from you and establishing friendly business
   relationship between us.


Best Regards.

   Jane2
attachment: USB_Flash_Drive.jpg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

USB host controllers on a server that does not use USB devices?

2013-03-20 Thread Anton Shterenlikht

This is on an ia64 server.

Do I need these devices in kernel:

device  ehci# EHCI host controller
device  ohci# OHCI PCI-USB interface
device  uhci# UHCI PCI-USB interface

if I don't ever attach any usb devices to it?

Thanks

Anton

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB host controllers on a server that does not use USB devices?

2013-03-20 Thread ill...@gmail.com

On 20 March 2013 05:10, Anton Shterenlikht me...@bristol.ac.uk wrote:
 This is on an ia64 server.

 Do I need these devices in kernel:

 device  ehci# EHCI host controller
 device  ohci# OHCI PCI-USB interface
 device  uhci# UHCI PCI-USB interface

 if I don't ever attach any usb devices to it?

Probably not on a server, but there are some built-in
devices in some notebooks (webcam  bluetooth)
that are run through a usb bus.

usbconfig(8) may be helpful.

-- 
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB host controllers on a server that does not use USB devices?

2013-03-20 Thread Andrea Venturoli


On 03/20/13 14:59, ill...@gmail.com wrote:


Probably not on a server, but there are some built-in
devices in some notebooks (webcam  bluetooth)
that are run through a usb bus.


It happened to me to see an internal USB tape drive, connected to an USB 
port on the motherboard.


 bye
av.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Identify USB device with devd

2013-03-14 Thread Alberto Mijares

Hi list,

I have 3 USB GSM modems and I want to trigger some actions when they
are plugged to the system. Each modem must trigger a different action,
the problem is how to identify each modem because

1) none of the modems have a serial number
iSerialNumber = 0x  no string

2) two of three modems have same idProduct, so I can't rely on this

3) I don't know how to get the exact USB port where the modem is
plugged. I can get the bus with the variable

port # Hub port number (USB) // man devd.conf

but this is not enough information.

Any suggestion?

Thanks in advance.

Regards,


Alberto Mijares
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: usb hub as kvm switch

2013-02-08 Thread Zoran Kolic

Typo in original post. Should be:

is it possible to use usb hub to handle usb
keyboard and usb mouse for two nodes, of whick
one is freebsd 9.1 amd64 box.

Zoran

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

usb hub as kvm switch

2013-02-08 Thread Zoran Kolic

I have two nodes side by side. There is none of kvm
switches for usb only. I plan to connect usb keyboard
and usb mouse and let monitor with two adapters to do
the rest.
Is it possible to use plain kvm switch for this task.
One of nodes would be freebsd 9.1 amd64.
Best regards

   Zoran

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Crucial SSD firmware upgrade -- usb flash drive issues

2013-02-01 Thread Gary Aitken

I've got a Crucial m4 SSD which needs a firmware upgrade.
From the Crucial website I've downloaded an image which supposedly is an iso
image bootable from either CD or a usb stick.  

Since the fbsd install images are different for booting from cd and usb
flash drives (the flash image is significantly larger), 
I'm wondering if there's anything I need to be aware of when attempting this.

I tried copying the ssd firmware update image to a flash drive using:
  dd if=firmwareupdate.iso of=/dev/da0 bs=64k
which seemed to work.

However, when I attempt to boot the device, BIOS complains about it not
being bootable and says to fix it or select something else which is bootable.

I know the drive can be bootable because I used it for the fbsd 9.1 usb boot
image and it worked fine.

The documentation for the SSD firmware upgrade says Create a Bootable USB 
Drive
with the following steps (summarized here, no real content omitted):

  1.  Start with a newly formatted USB drive
  2.  Open a USB installer program.  If you don't have one, you may download
  a free one such as Universal USB Installer...
  3.  If you are using the Universal USB Installer, then:
  3a. At the Step 1 drop down box, scroll to the bottom and select
  the last option: Try Unlisted Linux ISO
  3b. Go to step 2 (in the pgm) and browse to the firmware ISO that you
  downloaded earlier
  3c. Go to step 3 (in the pgm) and select the flash drive on which you
  want to install the ISO
  3d. Click the Create button and click Format E:\Drive
  3e. A sequence of screens will appear and disappear...

The above is all highly confusing to me, as it's not clear who's doing what.
I'm guessing the Universal Installer Program actually writes a boot block
and then the bootable image someplace beyond that, and the iso image supplied
is not really a complete bootable image for a flash drive -- it's missing the
boot blocks.

Can anyone suggest a way to create a bootable flash drive using this image?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

RE: Crucial SSD firmware upgrade -- usb flash drive issues

2013-02-01 Thread Sean Cavanaugh

 -Original Message-
 From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
 questi...@freebsd.org] On Behalf Of Gary Aitken
 Sent: Friday, February 01, 2013 12:55 PM
 To: FreeBSD Mailing List
 Subject: Crucial SSD firmware upgrade -- usb flash drive issues

 I've got a Crucial m4 SSD which needs a firmware upgrade.
 From the Crucial website I've downloaded an image which supposedly is an
 iso image bootable from either CD or a usb stick.

 Since the fbsd install images are different for booting from cd and usb
flash
 drives (the flash image is significantly larger), I'm wondering if there's
 anything I need to be aware of when attempting this.

 I tried copying the ssd firmware update image to a flash drive using:
   dd if=firmwareupdate.iso of=/dev/da0 bs=64k which seemed to work.

 However, when I attempt to boot the device, BIOS complains about it not
 being bootable and says to fix it or select something else which is
bootable.

 I know the drive can be bootable because I used it for the fbsd 9.1 usb
boot
 image and it worked fine.

 The documentation for the SSD firmware upgrade says Create a Bootable
 USB Drive
 with the following steps (summarized here, no real content omitted):

   1.  Start with a newly formatted USB drive
   2.  Open a USB installer program.  If you don't have one, you may
download
   a free one such as Universal USB Installer...
   3.  If you are using the Universal USB Installer, then:
   3a. At the Step 1 drop down box, scroll to the bottom and select
   the last option: Try Unlisted Linux ISO
   3b. Go to step 2 (in the pgm) and browse to the firmware ISO that you
   downloaded earlier
   3c. Go to step 3 (in the pgm) and select the flash drive on which you
   want to install the ISO
   3d. Click the Create button and click Format E:\Drive
   3e. A sequence of screens will appear and disappear...

 The above is all highly confusing to me, as it's not clear who's doing
what.
 I'm guessing the Universal Installer Program actually writes a boot
block
 and then the bootable image someplace beyond that, and the iso image
 supplied is not really a complete bootable image for a flash drive -- it's
 missing the boot blocks.

 Can anyone suggest a way to create a bootable flash drive using this
image?
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 unsubscr...@freebsd.org

Please see the below site for a script to convert the .ISO into a .IMG that
can be dd written to the thumb drive

http://www.daemonforums.org/showthread.php?t=4361

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Crucial SSD firmware upgrade -- usb flash drive issues

2013-02-01 Thread Gary Aitken

On 02/01/13 11:03, Sean Cavanaugh wrote:
 -Original Message-
 From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
 questi...@freebsd.org] On Behalf Of Gary Aitken
 Sent: Friday, February 01, 2013 12:55 PM
 To: FreeBSD Mailing List
 Subject: Crucial SSD firmware upgrade -- usb flash drive issues

 I've got a Crucial m4 SSD which needs a firmware upgrade.
 From the Crucial website I've downloaded an image which supposedly is an
 iso image bootable from either CD or a usb stick.

 Since the fbsd install images are different for booting from cd and usb
 flash
 drives (the flash image is significantly larger), I'm wondering if there's
 anything I need to be aware of when attempting this.

 I tried copying the ssd firmware update image to a flash drive using:
   dd if=firmwareupdate.iso of=/dev/da0 bs=64k which seemed to work.

 However, when I attempt to boot the device, BIOS complains about it not
 being bootable and says to fix it or select something else which is
 bootable.

 I know the drive can be bootable because I used it for the fbsd 9.1 usb
 boot
 image and it worked fine.

 The documentation for the SSD firmware upgrade says Create a Bootable
 USB Drive
 with the following steps (summarized here, no real content omitted):

   1.  Start with a newly formatted USB drive
   2.  Open a USB installer program.  If you don't have one, you may
 download
   a free one such as Universal USB Installer...
   3.  If you are using the Universal USB Installer, then:
   3a. At the Step 1 drop down box, scroll to the bottom and select
   the last option: Try Unlisted Linux ISO
   3b. Go to step 2 (in the pgm) and browse to the firmware ISO that you
   downloaded earlier
   3c. Go to step 3 (in the pgm) and select the flash drive on which you
   want to install the ISO
   3d. Click the Create button and click Format E:\Drive
   3e. A sequence of screens will appear and disappear...

 The above is all highly confusing to me, as it's not clear who's doing
 what.
 I'm guessing the Universal Installer Program actually writes a boot
 block
 and then the bootable image someplace beyond that, and the iso image
 supplied is not really a complete bootable image for a flash drive -- it's
 missing the boot blocks.

 Can anyone suggest a way to create a bootable flash drive using this
 image?
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 unsubscr...@freebsd.org

 Please see the below site for a script to convert the .ISO into a .IMG that
 can be dd written to the thumb drive

 http://www.daemonforums.org/showthread.php?t=4361

Thanks, that was a help.

However, when it boots, I get the following:

  No /boot/loader
  FreeBSD/x86 boot
  Default: 0:ad(0,a)/boot/kernel/kernel
  boot:

I can mount the thumb drive as a ufs file system, which looks like this:
  /boot/
solinux/
boot.cat
boot2880.img
bootmsg.txt
isolinux.bin
isolinux.cfg
memdisk
splash.lss
  /legal.txt
  /revision.txt

Assuming this is all good as a stand-alone linux image, what do I need to 
enter at the boot: prompt to get it to boot?  It's not clear to me what the
code to be booted is.

The isolinux.cfg file looks like this:
  PROMPT 1
  TIMEOUT 30

  DEFAULT default

  DISPLAY bootMsg.txt

  LABEL default
KERNEL memdisk
append initrd=boot2880.img floppy raw

  LABEL alternate
KERNEL memdisk
append initrd=boot2880.img floppy

Thanks for any hints...

Gary
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Crucial SSD firmware upgrade -- usb flash drive issues

2013-02-01 Thread Warren Block


On Fri, 1 Feb 2013, Gary Aitken wrote:

On 02/01/13 11:03, Sean Cavanaugh wrote:


Please see the below site for a script to convert the .ISO into a .IMG that
can be dd written to the thumb drive

http://www.daemonforums.org/showthread.php?t=4361


That looks to be specific to converting a FreeBSD installer CD to memory 
stick... which of course is not needed any more.


The implications of trying to custom build an SSD firmware update image 
from a CD could be big, and it's really not something to experiment with 
unless you feel lucky.


From a user support standpoint, the first thing to do is send a Why 
aren't you supporting your users with a memory stick firmware update? 
Many people no longer have CD drives.


Practically speaking, that is not likely to result in a quick result, or 
possibly any result.  So use a program they recommend, or use an 
external CD drive to update the firmware.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Crucial SSD firmware upgrade -- usb flash drive issues

2013-02-01 Thread Zoran Kolic

If I understand correctly, it is iso image from ssd manufacturer.
They tend to think everybody uses win and has cd drive. Quick
search might give easy answer, if win/linux box is available. You
could try out unetbootin. Tutorial says it takes an image and
makes bootable usb stick.
Best regards

Zoran


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Crucial SSD firmware upgrade -- usb flash drive issues

2013-02-01 Thread Gary Aitken

On 02/01/13 22:06, Zoran Kolic wrote:
 If I understand correctly, it is iso image from ssd manufacturer.
 They tend to think everybody uses win and has cd drive. Quick
 search might give easy answer, if win/linux box is available. You
 could try out unetbootin. Tutorial says it takes an image and
 makes bootable usb stick.

On 02/01/13 17:05, Warren Block wrote:

 The implications of trying to custom build an SSD firmware update image from 
 a CD could be big, and it's really not something to experiment with unless 
 you feel lucky.
 
 From a user support standpoint, the first thing to do is send a Why 
 aren't you supporting your users with a memory stick firmware update? Many 
 people no longer have CD drives.
 
 Practically speaking, that is not likely to result in a quick result, or 
 possibly any result.  So use a program they recommend, or use an external CD 
 drive to update the firmware.

The mfg claims the iso image is suitable for booting either from CD or a usb
stick; with the caveat that you use some magic software to write the bootable
usb stick.  I guess I'll just find a way to write a CD.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Locking USB Serial Device to Specific Com port

2013-01-27 Thread dweimer


On 2013-01-26 16:40, Shane Ambler wrote:

On 27/01/2013 08:15, dweimer wrote:

I would like to lock down the USB serial port adapter used on the 
UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get 
a

clean shutdown in event of a power failure.

I believe that this requires setting a hint line of some sort in the
/boot/loader.conf file, but I am having trouble tracking down what 
this

should be, or maybe I am on the wrong track.  Here is the current
information from the adpapters, the UPS adapter was connected at 
boot,

is on /dev/cuaU0, the other one was plugged in after boot, and is on
/dev/cuaU1.


start with man devd.conf

You can add your own devd files in /usr/local/etc/devd/
Something along the lines of -

attach 200 {
device-name cuaU[0-9]+;
match vendor 0x067b;
match product 0x2303;
action sleep 2; cd /dev; ln -s ${device-name} upsmonitor;
};

use usbconfig to get info. I am thinking with the similarity of the 
two
you may need to rely on bus and hubaddr or devaddr to keep each 
device

identified by usb port location.


OK, so I was looking in the wrong direction, which might explain why my 
searching wasn't finding anything.


However I might still be out of luck, after doing some checking, and a 
reboot the only difference I can find is below.


dev.uplcom.0.%location: bus=1 hubaddr=1 port=0 devaddr=2 interface=0
dev.uplcom.1.%location: bus=1 hubaddr=3 port=0 devaddr=3 interface=0

The devices have switch at this point, all info from usbconfig, dmesg, 
looks identical, these two lines from the sysctl -a | grep uplcom 
output is all that changed, the hubaddr=1 and hubaddr=3 have switched, 
however the man devd.conf has a variable list, to use, and doesn't seem 
to have an option to match agains that hubaddr variable.


 Variable  Description
 bus   Device name of parent bus.
 cdev  Device node path if one is created by the devfs(5) 
filesys-

   tem.
 cisproductCIS-product.
 cisvendor CIS-vendor.
 class Device class.
 deviceDevice ID.
 devclass  Device Class (USB)
 devsubclass   Device Sub-class (USB)
 device-name   Name of attached/detached device.
 endpoints Endpoint count (USB)
 function  Card functions.
 interface Interface ID (USB)
 intclass  Interface Class (USB)
 intprotocol   Interface Protocol  (USB)
 intsubclass   Interface Sub-class (USB)
 manufacturer  Manufacturer ID (pccard).
 mode  Peripheral mode (USB)
 notifyMatch the value of the ``notify'' variable.
 parentParent device
 port  Hub port number (USB)
 product   Product ID (pccard/USB).
 release   Hardware revision (USB)
 sernumSerial Number (USB).
 slot  Card slot.
 subvendor Sub-vendor ID.
 subdevice Sub-device ID.
 subsystem Matches a subsystem of a system, see below.
 systemMatches a system type, see below.
 type  Type of notification, see below.
 vendorVendor ID.


But the action line above does give me an idea though, I should be able 
to write a script to run at startup to find the line, and create the 
link to the device.  The only one I care about is the UPS monitor, as 
the other is only occasionally used, and I can easily check which com 
port its on before connecting to it.


--
Thanks,
   Dean E. Weimer
   http://www.dweimer.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Locking USB Serial Device to Specific Com port

2013-01-27 Thread Warren Block


On Sun, 27 Jan 2013, dweimer wrote:


On 2013-01-26 16:40, Shane Ambler wrote:

On 27/01/2013 08:15, dweimer wrote:


I would like to lock down the USB serial port adapter used on the UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get a
clean shutdown in event of a power failure.

I believe that this requires setting a hint line of some sort in the
/boot/loader.conf file, but I am having trouble tracking down what this
should be, or maybe I am on the wrong track.  Here is the current
information from the adpapters, the UPS adapter was connected at boot,
is on /dev/cuaU0, the other one was plugged in after boot, and is on
/dev/cuaU1.


start with man devd.conf

You can add your own devd files in /usr/local/etc/devd/
Something along the lines of -

attach 200 {
device-name cuaU[0-9]+;
match vendor 0x067b;
match product 0x2303;
action sleep 2; cd /dev; ln -s ${device-name} upsmonitor;
};

use usbconfig to get info. I am thinking with the similarity of the two
you may need to rely on bus and hubaddr or devaddr to keep each device
identified by usb port location.


OK, so I was looking in the wrong direction, which might explain why my 
searching wasn't finding anything.


However I might still be out of luck, after doing some checking, and a reboot 
the only difference I can find is below.


dev.uplcom.0.%location: bus=1 hubaddr=1 port=0 devaddr=2 interface=0
dev.uplcom.1.%location: bus=1 hubaddr=3 port=0 devaddr=3 interface=0


usbconfig may be able to get the device serial number, although they 
may not be unique.  Jamming useful scripts inside an action can be complicated. 
It may be easier to just trigger an external script.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Locking USB Serial Device to Specific Com port

2013-01-27 Thread dweimer


On 2013-01-27 08:48, dweimer wrote:

On 2013-01-26 16:40, Shane Ambler wrote:

On 27/01/2013 08:15, dweimer wrote:

I would like to lock down the USB serial port adapter used on the 
UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get 
a

clean shutdown in event of a power failure.

I believe that this requires setting a hint line of some sort in 
the
/boot/loader.conf file, but I am having trouble tracking down what 
this

should be, or maybe I am on the wrong track.  Here is the current
information from the adpapters, the UPS adapter was connected at 
boot,
is on /dev/cuaU0, the other one was plugged in after boot, and is 
on

/dev/cuaU1.


start with man devd.conf

You can add your own devd files in /usr/local/etc/devd/
Something along the lines of -

attach 200 {
device-name cuaU[0-9]+;
match vendor 0x067b;
match product 0x2303;
action sleep 2; cd /dev; ln -s ${device-name} upsmonitor;
};

use usbconfig to get info. I am thinking with the similarity of the 
two
you may need to rely on bus and hubaddr or devaddr to keep each 
device

identified by usb port location.


OK, so I was looking in the wrong direction, which might explain why
my searching wasn't finding anything.

However I might still be out of luck, after doing some checking, and
a reboot the only difference I can find is below.

dev.uplcom.0.%location: bus=1 hubaddr=1 port=0 devaddr=2 interface=0
dev.uplcom.1.%location: bus=1 hubaddr=3 port=0 devaddr=3 interface=0

The devices have switch at this point, all info from usbconfig,
dmesg, looks identical, these two lines from the sysctl -a | grep
uplcom output is all that changed, the hubaddr=1 and hubaddr=3 have
switched, however the man devd.conf has a variable list, to use, and
doesn't seem to have an option to match agains that hubaddr variable.

 Variable  Description
 bus   Device name of parent bus.
 cdev  Device node path if one is created by the devfs(5) 
filesys-

   tem.
 cisproductCIS-product.
 cisvendor CIS-vendor.
 class Device class.
 deviceDevice ID.
 devclass  Device Class (USB)
 devsubclass   Device Sub-class (USB)
 device-name   Name of attached/detached device.
 endpoints Endpoint count (USB)
 function  Card functions.
 interface Interface ID (USB)
 intclass  Interface Class (USB)
 intprotocol   Interface Protocol  (USB)
 intsubclass   Interface Sub-class (USB)
 manufacturer  Manufacturer ID (pccard).
 mode  Peripheral mode (USB)
 notifyMatch the value of the ``notify'' variable.
 parentParent device
 port  Hub port number (USB)
 product   Product ID (pccard/USB).
 release   Hardware revision (USB)
 sernumSerial Number (USB).
 slot  Card slot.
 subvendor Sub-vendor ID.
 subdevice Sub-device ID.
 subsystem Matches a subsystem of a system, see below.
 systemMatches a system type, see below.
 type  Type of notification, see below.
 vendorVendor ID.


But the action line above does give me an idea though, I should be
able to write a script to run at startup to find the line, and create
the link to the device.  The only one I care about is the UPS 
monitor,

as the other is only occasionally used, and I can easily check which
com port its on before connecting to it.


This probably wouldn't work for anyone else, but here is my solution in 
case it does help someone else.


Created a new script in /usr/local/etc/rc.d/nutusblink
#!/bin/sh

# PROVIDE: NUTUSBLINK
# REQUIRE: NETWORKING
# BEFORE: nut
# KEYWORD: shutdown

. /etc/rc.subr

name=nutusblink
start_cmd=nutusblink_start
stop_cmd=nutusblink_stop
rcvar=nutusblink_enable


find_comport() {
  grepstring='uplcom.*hubaddr='${nutusblink_hubaddr}
  comnum=`sysctl -a | grep ${grepstring} | awk '{print $1}' | awk -F . 
'{print $3}'`

}

nutusblink_start() {
  find_comport
  echo 
  echo ...Creating USB Serial Adapter Comport Link for NUT UPS 
Monitoring...

  ln -s /dev/cuaU${comnum} /dev/${nutusblink_link}
  echo/dev/${nutusblink_link} Linked to /dev/cuaU${comnum}
  echo 
}

nutusblink_stop() {
  find_comport
  echo 
  echo ...Removing USB Serial Adapter Comport Link for NUT UPS 
Monitoring...

  rm /dev/${nutusblink_link}
  echo/dev/${nutusblink_link} No longer linked to 
/dev/cuaU${comnum}

  echo 
}

load_rc_config $name

: ${nutusblink_enable=NO}
: ${nutusblink_hubaddr=}
: ${nutusblink_link=}

run_rc_command $1


Added these lines to /etc/rc.conf
# Create NUT USB Link
nutusblink_enable=YES
nutusblink_hubaddr=3
nutusblink_link=nutusblink

End Result,
I now have a link /dev/nutusblink pointed at /dev/cuaU#, where # is the 
correct port number.  I have tested on a couple of reboots, and 
configured NUT to use the link instead of the actual com port.  Using 
the BEFORE: nut in the script ensures that it gets ran

Re: Locking USB Serial Device to Specific Com port

2013-01-27 Thread dweimer


On 2013-01-27 09:29, Warren Block wrote:

On Sun, 27 Jan 2013, dweimer wrote:


On 2013-01-26 16:40, Shane Ambler wrote:

On 27/01/2013 08:15, dweimer wrote:

I would like to lock down the USB serial port adapter used on the 
UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will 
get a

clean shutdown in event of a power failure.
I believe that this requires setting a hint line of some sort in 
the
/boot/loader.conf file, but I am having trouble tracking down what 
this

should be, or maybe I am on the wrong track.  Here is the current
information from the adpapters, the UPS adapter was connected at 
boot,
is on /dev/cuaU0, the other one was plugged in after boot, and is 
on

/dev/cuaU1.

start with man devd.conf
You can add your own devd files in /usr/local/etc/devd/
Something along the lines of -
attach 200 {
device-name cuaU[0-9]+;
match vendor 0x067b;
match product 0x2303;
action sleep 2; cd /dev; ln -s ${device-name} upsmonitor;
};
use usbconfig to get info. I am thinking with the similarity of the 
two
you may need to rely on bus and hubaddr or devaddr to keep each 
device

identified by usb port location.


OK, so I was looking in the wrong direction, which might explain why 
my searching wasn't finding anything.


However I might still be out of luck, after doing some checking, and 
a reboot the only difference I can find is below.


dev.uplcom.0.%location: bus=1 hubaddr=1 port=0 devaddr=2 interface=0
dev.uplcom.1.%location: bus=1 hubaddr=3 port=0 devaddr=3 interface=0


usbconfig may be able to get the device serial number, although they
may not be unique.  Jamming useful scripts inside an action can be
complicated. It may be easier to just trigger an external script.


That's just it, can't get usbconfig to give me anything different 
between the two, they don't appear to have a serial number set on them.


# usbconfig -d ugen0.2 dump_device_desc
ugen0.2: USB-Serial Controller Prolific Technology Inc. at usbus0, 
cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON


  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0040
  idVendor = 0x067b
  idProduct = 0x2303
  bcdDevice = 0x0300
  iManufacturer = 0x0001  Prolific Technology Inc.
  iProduct = 0x0002  USB-Serial Controller
  iSerialNumber = 0x  no string
  bNumConfigurations = 0x0001

# usbconfig -d ugen0.3 dump_device_desc
ugen0.3: USB-Serial Controller Prolific Technology Inc. at usbus0, 
cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON


  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0040
  idVendor = 0x067b
  idProduct = 0x2303
  bcdDevice = 0x0300
  iManufacturer = 0x0001  Prolific Technology Inc.
  iProduct = 0x0002  USB-Serial Controller
  iSerialNumber = 0x  no string
  bNumConfigurations = 0x0001


--
Thanks,
   Dean E. Weimer
   http://www.dweimer.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Locking USB Serial Device to Specific Com port

2013-01-26 Thread dweimer

I have two USB Serial adapters I use on my web server, ones always 
connected, to allow NUT to monitor my UPS.  The other I use to view the 
console of my pfSense firewall, however I sometimes disconnect this one 
to use it with my laptop to configure switches.


Because this one is unplugged and plugged back in, sometimes on reboot 
it ends up switching its com port with the UPS, so NUT fails to start 
and the UPS is unmonitored.


I would like to lock down the USB serial port adapter used on the UPS 
to /dev/cuaU0, to make sure the UPS is always monitored and I will get a 
clean shutdown in event of a power failure.


I believe that this requires setting a hint line of some sort in the 
/boot/loader.conf file, but I am having trouble tracking down what this 
should be, or maybe I am on the wrong track.  Here is the current 
information from the adpapters, the UPS adapter was connected at boot, 
is on /dev/cuaU0, the other one was plugged in after boot, and is on 
/dev/cuaU1.



dmesg output:
ugen0.2: Prolific Technology Inc. at usbus0
uplcom0: Prolific Technology Inc. USB-Serial Controller, class 0/0, 
rev 1.10/3.00, addr 2 on usbus0

ugen0.3: Prolific Technology Inc. at usbus0
uplcom1: Prolific Technology Inc. USB-Serial Controller, class 0/0, 
rev 1.10/3.00, addr 3 on usbus0


sysctl -a | grep uplmon:
device  uplcom
hw.usb.uplcom.debug: 0
dev.uplcom.0.%desc: Prolific Technology Inc. USB-Serial Controller, 
class 0/0, rev 1.10/3.00, addr 2

dev.uplcom.0.%driver: uplcom
dev.uplcom.0.%location: bus=1 hubaddr=3 port=0 devaddr=2 interface=0
dev.uplcom.0.%pnpinfo: vendor=0x067b product=0x2303 devclass=0x00 
devsubclass=0x00 sernum= release=0x0300 mode=host intclass=0xff 
intsubclass=0x00 intprotocol=0x00  ttyname=U0 ttyports=1

dev.uplcom.0.%parent: uhub0
dev.uplcom.0.ttyname: U0
dev.uplcom.0.ttyports: 1
dev.uplcom.1.%desc: Prolific Technology Inc. USB-Serial Controller, 
class 0/0, rev 1.10/3.00, addr 3

dev.uplcom.1.%driver: uplcom
dev.uplcom.1.%location: bus=1 hubaddr=1 port=0 devaddr=3 interface=0
dev.uplcom.1.%pnpinfo: vendor=0x067b product=0x2303 devclass=0x00 
devsubclass=0x00 sernum= release=0x0300 mode=host intclass=0xff 
intsubclass=0x00 intprotocol=0x00  ttyname=U1 ttyports=1

dev.uplcom.1.%parent: uhub0
dev.uplcom.1.ttyname: U1
dev.uplcom.1.ttyports: 1

Does anyone have any suggestions on how to do this?

--
Thanks,
   Dean E. Weimer
   http://www.dweimer.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Locking USB Serial Device to Specific Com port

2013-01-26 Thread Shane Ambler


On 27/01/2013 08:15, dweimer wrote:


I would like to lock down the USB serial port adapter used on the UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get a
clean shutdown in event of a power failure.

I believe that this requires setting a hint line of some sort in the
/boot/loader.conf file, but I am having trouble tracking down what this
should be, or maybe I am on the wrong track.  Here is the current
information from the adpapters, the UPS adapter was connected at boot,
is on /dev/cuaU0, the other one was plugged in after boot, and is on
/dev/cuaU1.


start with man devd.conf

You can add your own devd files in /usr/local/etc/devd/
Something along the lines of -

attach 200 {
device-name cuaU[0-9]+;
match vendor 0x067b;
match product 0x2303;
action sleep 2; cd /dev; ln -s ${device-name} upsmonitor;
};

use usbconfig to get info. I am thinking with the similarity of the two
you may need to rely on bus and hubaddr or devaddr to keep each device
identified by usb port location.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: USB in Windows7 guest

2013-01-12 Thread Boris Samorodov

Hi Leslie and All,

09.01.2013 16:38, Leslie Jensen пишет:
 
 Hello.
 
 I posted this on the freebsd-virtualization list but got no answers so 
 now I hope that someone here can shed the light for me.
 
 
 I have a Windows7 guest OS in Virtualbox on a FreeBSD 9.1-RELEASE system.
 
 I've followed the instructions in the handbook for enabling USB-support 
 in Virtualbox.
 
 In the machines settings I've ticked for activation of USB controller 
 but not for USB2 because it needs an extension pack that's not available 
 for freebsd if I've understood it right.
 
 I have an Epson V500 scanner that is recognized as an unknown device by 
 the host OS.
 
 ugen7.2: EPSON at usbus7
 Unknown USB device: vendor 0x04b8 product 0x0130 bus uhub7
 
 
 I cannot get it to appear in the guest OS.
 
 Is it possible and if so what do I need to do in order to make it visible?

Sure it's possible. For me it (FreeBSD-i386 9-STABLE host, WinXP guest)
it just works. I'm not sure if it matters -- I install guest additions.

I'd recommend double check your configuration. Ah, yes one more place to
check that you had not mention: is USB enabled at VirtualboxManager for
this virtual machine?

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

USB in Windows7 guest

2013-01-09 Thread Leslie Jensen



Hello.

I posted this on the freebsd-virtualization list but got no answers so 
now I hope that someone here can shed the light for me.



I have a Windows7 guest OS in Virtualbox on a FreeBSD 9.1-RELEASE system.

I've followed the instructions in the handbook for enabling USB-support 
in Virtualbox.


In the machines settings I've ticked for activation of USB controller 
but not for USB2 because it needs an extension pack that's not available 
for freebsd if I've understood it right.


I have an Epson V500 scanner that is recognized as an unknown device by 
the host OS.


ugen7.2: EPSON at usbus7
Unknown USB device: vendor 0x04b8 product 0x0130 bus uhub7


I cannot get it to appear in the guest OS.

Is it possible and if so what do I need to do in order to make it visible?

Thanks

/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

How to Make Customized Boot-able DVD or USB

2012-12-20 Thread Hooman Oroojeni

Hi People,
I was wondering if I could make a FreeBSD boot-able USB or DVD with
pre-installed software and services such as DHCP Client/Server. I would be
pleased if you could help me.

Thanks
Hooman
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Compatability for various USB 3.0 / PCIe cards ?

2012-11-24 Thread Lucas B. Cohen

On 2012.11.23 22:11, Ronald F. Guilmette wrote:
 
 Well friends, it's that time of year again... yep, it's shop till you drop
 time!
For me it's usually *after* Christmas season, but whatever works :)

 I can't imagine
 that there is really that much different about the pricey ones to make
 them worth the extra money.)
I can imagine it. For a controller, negotiating USB 3.0 / XHCI protocol
with a device is one thing, delivering the expected bandwidth is
another. I've toyed around with enough cheap IDE and SATA adapters to
know it takes more than a logo on the packaging to get decent throughput.

Also, the bus needs to offer enough bandwidth to avoid being a
bottleneck. Theoretical maximum speed for USB3 is 5 Gbits/s, that's a
bit more than 2 PCIe lanes can sustain, so you'll want an adapter than
plugs into a full-sized PCIe connector, unlike the Syba one.

Hope this helps,


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Compatability for various USB 3.0 / PCIe cards ?

2012-11-23 Thread Ronald F. Guilmette


Well friends, it's that time of year again... yep, it's shop till you drop
time!

This year it appears that everybody and his brother is having a sale on
compact (mostly 2.5 inch) external drives, and most of them nowadays have
a USB 3.0 connection.

That's swell, and there are some really good bargains on these things
out there... especially today... but there is a fly in the ointment.
My older motherboards don't have built-in USB 3.0 support, so I'll need
to add that.

So I'd like to know what (if any) USB 3.0 / PCIe adapter cards are known
to work well with FreeBSD at this time.

The cheapest one I found on Newegg was about thirteen bucks, but of course
they don't say anything about what chips are on that exactly.

There's also a Syba branded one on mazon for about fourteen bucks, and
in this case it explicitly says Asmedia Chipset.

So?  What works with FreeBSD?  (Keep in mind that I don't want to spend
much.  Oddly enough, some of these things are priced in the low teens,
as I've said, but others cost as much as fifty bucks.  I can't imagine
that there is really that much different about the pricey ones to make
them worth the extra money.)


Regards,
rfg
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

USB flash diver Introduce for the NEW shared photos with you

2012-11-22 Thread USB flash diver Introduce for the NEW


Dear Manager
Have a nice day

This is Jerry from Shenzhen of China, writing to you to enter into business

relationship with you. We are the professional manufacturer
with nearly 6 years of experience oversea business in supplying USB Flash

Drives, Tablet PC, Keyboard, Mouse, MP3, Digital Photo frame, Laser Pointer,

Sound recording pen. We can supply you the competitive price and best  
quality,


Welcome to visit our website: http://pzz510127.cn.alibaba.com

Meanwhile, we will offer positive cooperation and sincere service, also look

foward to buliding up long cooperation and double-win situation between us,
Do the promise as belows:
1: Samples are arranged only about 2-3 days
2: The goods is at the rate of 100% inspected and tested before delivery
3: Any style of LOGO is no problem for us per as your requirement to  
publicize


your company
4: There is thousand kinds of USB Flash Drive for your choice, also you can

select any type you like or open new mould for you
5: Our factory is located in Shenzhen, so our quotation is FOB shenzhen.

If any interest or need, Please feel free to contact us without hesitating,  
we


will do everything well for you.

Your reply will be highly appreciated

Thank you very much
Jerry
Telephone: 86-0755-83268990-802
Mobilephone : 086 18682315895
MSN:jerry200...@hotmail.com
Skype:jerry200836
Email :jerry200...@yahoo.cn
Company  name : T-Jorda Electronics Co.,Ltd
Website : http://pzz510127.cn.alibaba.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: eGalax USB touch panel on ExoPC Slate vs. FreeBSD and X11

2012-11-20 Thread Bill Paul

 
 I am pleased to see others having success at getting tablet input to work.
 I tried and failed with 8.x on my Fujitsu T-1010.
 
 Question: The button emulation. Did you add that or was it already there? I
 want to use Squeak Smalltalk on a tablet and the three button mouse
 emulation is a big deal, especially without a keyboard.

The button emulation was already there. The BIOS on the ExoPC Slate
uses it itself: when you power up the tablet, there are two areas you can
press to enter the BIOS setup or the boot select menu. You can use the
touch panel to set the BIOS options or choose the boot path and then tap
the screen to select. The simulated button presses via screen taps are the
only thing that work with the ums(4) driver out of the box. If you look
at the HID collection dump from the mouse emulation mode, you can see it
supports an X axis, Y axis and two button inputs. The touch screen
synthesizes the button inputs internally based on tap patterns.

 
 Which leads me to my next question. What are you using for input? Is anyone
 working on handwriting recognition or does Apple still have the patents
 locked up? My goal is to be as much as possible like the Newton.

Initially I was using a USB keyboard. The ExoPC Slate has two USB ports
on the side. I have this old Targus USB I/O expander that also provides
PS/2 keyboard and mouse inputs, along with RS-232 port, printer port and
USB ethernet (Pegasus chipset, aue(4) driver). At minimum, USB keyboard
is required in order to install FreeBSD. I also the USB thumbdrive
installer to load the OS. After that I used the USB ethernet to load
papckages.

Once I had the OS installed, I switched to using a bluetooth keyboard.
It's less clunky without the extra wires.

Note that this was intended to be Intel's developer reference platform
for the Meego OS (which is basically just another flavor of Linux). It
came with Meego installed (it's now dual-booting Meego and FreeBSD). Meego
includes an on-screen keyboard input widget which is something that plain
X11 lacks. So for now, I need a physical keyboard.

In addition to the eGalax touch screen, the Slate has:

Atom N450 1.66Ghz CPU (can run i386 or amd64 versions of FreeBSD)
2GB RAM
64GB SSD storage
Atheros 9285 WiFi
Atheros bluetooth
Intel Pineview graphics (1388x768 resolution)

The bluetooth requires a binary blob firmware image to be loaded and
I had to jigger the Intel xf86 video driver a little but it's all working
now.

-Bill

 
 On Fri, Nov 16, 2012 at 9:04 AM, Bill Paul wp...@freebsd.org wrote:
 
 
  Well... apparently I was able to get this to work on my own. To recap, I
  have an ExoPC Slate running FreeBSD 9.0 and xorg 1.7 with an eGalax
  USB HID touch screen. Out of the box, ums(4) claims it but doesn't
  like it.
 
  After investigating a bit more, I found that the screen has multiple HID
  collections associated with it:
 
  Collection type=Application page=Digitizer usage=Touch_Screen
  Collection type=Physical page=Digitizer usage=Finger
 
  Collection type=Application page=Generic_Desktop usage=Pointer
  Collection type=Physical page=Generic_Desktop usage=Pointer
 
  Collection type=Application page=Microsoft usage=0x0001
 
  Collection type=Application page=Digitizer usage=Touch_Screen
  Collection type=Physical page=Digitizer usage=Stylus
 
  Collection type=Application page=Digitizer usage=Device_Configuration
  Collection type=Physical page=Digitizer usage=Finger
 
  The ums(4) driver is trying to use the 'Pointer' collection, but I think
  it may be getting confused by the X/Y ranges:
 
  Collection type=Application page=Generic_Desktop usage=Pointer
  Collection type=Physical page=Generic_Desktop usage=Pointer
  Input   rid=1 size=1 count=1 page=Button usage=Button_1, logical range
  0..1, physical range 1..2047
  Input   rid=1 size=1 count=1 page=Button usage=Button_2, logical range
  0..1, physical range 1..2047
  Input   rid=1 size=16 count=1 page=Generic_Desktop usage=X, logical range
  0..4095, physical range 0..4095
  Input   rid=1 size=16 count=1 page=Generic_Desktop usage=Y, logical range
  0..4095, physical range 0..4095
  End collection
  End collection
 
  There are two problems. First, the ranges are a little unusual. I think
  other mouse devices only have ranges from -127 to +127. Second, the input
  flags for the X and Y axis entries are 0x2 (HI_VARIABLE) and not
  HI_RELATIVE,
  which is what the usm(4) driver expects. This causes it to ignore the X
  and Y
  axis entries and only handle the button entries. I tried changing the code
  to
  accept just the HI_VARIABLE flag, but that still didn't make the cursor
  move.
  In any case, I was wrong that the problem is that the FreeBSD ums(4) driver
  doesn't handle gestures: it's just not flexible enough to handle this
   oddball pointer design.
 
  Anyway, go get it to work with X as a standard pointer device, I finally
  ended up doing the following:
 
  1) Edited the uhid_probe() function in sys/dev/usb/input/uhid.c

Re: eGalax USB touch panel on ExoPC Slate vs. FreeBSD and X11

2012-11-16 Thread Bill Paul


Well... apparently I was able to get this to work on my own. To recap, I
have an ExoPC Slate running FreeBSD 9.0 and xorg 1.7 with an eGalax
USB HID touch screen. Out of the box, ums(4) claims it but doesn't
like it.

After investigating a bit more, I found that the screen has multiple HID
collections associated with it:

Collection type=Application page=Digitizer usage=Touch_Screen
Collection type=Physical page=Digitizer usage=Finger

Collection type=Application page=Generic_Desktop usage=Pointer
Collection type=Physical page=Generic_Desktop usage=Pointer

Collection type=Application page=Microsoft usage=0x0001

Collection type=Application page=Digitizer usage=Touch_Screen
Collection type=Physical page=Digitizer usage=Stylus

Collection type=Application page=Digitizer usage=Device_Configuration
Collection type=Physical page=Digitizer usage=Finger

The ums(4) driver is trying to use the 'Pointer' collection, but I think
it may be getting confused by the X/Y ranges:

Collection type=Application page=Generic_Desktop usage=Pointer
Collection type=Physical page=Generic_Desktop usage=Pointer
Input   rid=1 size=1 count=1 page=Button usage=Button_1, logical range 0..1, 
physical range 1..2047
Input   rid=1 size=1 count=1 page=Button usage=Button_2, logical range 0..1, 
physical range 1..2047
Input   rid=1 size=16 count=1 page=Generic_Desktop usage=X, logical range 
0..4095, physical range 0..4095
Input   rid=1 size=16 count=1 page=Generic_Desktop usage=Y, logical range 
0..4095, physical range 0..4095
End collection
End collection

There are two problems. First, the ranges are a little unusual. I think
other mouse devices only have ranges from -127 to +127. Second, the input
flags for the X and Y axis entries are 0x2 (HI_VARIABLE) and not HI_RELATIVE,
which is what the usm(4) driver expects. This causes it to ignore the X and Y
axis entries and only handle the button entries. I tried changing the code to
accept just the HI_VARIABLE flag, but that still didn't make the cursor move.
In any case, I was wrong that the problem is that the FreeBSD ums(4) driver
doesn't handle gestures: it's just not flexible enough to handle this
 oddball pointer design.

Anyway, go get it to work with X as a standard pointer device, I finally
ended up doing the following:

1) Edited the uhid_probe() function in sys/dev/usb/input/uhid.c to comment
   out the code that excludes UIPROTO_MOUSE devices:
 
/*
 * Don't attach to mouse and keyboard devices, hence then no
 * nomatch event is generated and then ums and ukbd won't
 * attach properly when loaded.
 */
if ((uaa-info.bInterfaceClass == UICLASS_HID) 
(uaa-info.bInterfaceSubClass == UISUBCLASS_BOOT) 
((uaa-info.bInterfaceProtocol == UIPROTO_BOOT_KEYBOARD)/* ||
 (uaa-info.bInterfaceProtocol == UIPROTO_MOUSE) */)) {
return (ENXIO);
}

   Note: this will make it match all mice. I could have fixed it to
   be more selective, but for now I just wanted things to work.

2) Recompiled the kernel with the ums(4) and uhid(4) drivers removed.
3) Edited /boot/loader.conf to load the uhid(4) module:

uhid_load=YES

4) Renamed /boot/kernel/ums.ko to something else so that the system would
   stop trying to automatically load it all the time. (Grrr...)

5) Installed the ports collection.
6) Downloaded the following file:

http://people.freebsd.org/~mav/patch-zz-input-mouse9

6) Copied it to /usr/ports/x11-drivers/xf86-input-mouse/files
7) Recompiled and re-installed the xf86-input-mouse driver:

# cd /usr/ports/x11-drivers/xf86-input-mouse
# make
# make deinstall
# make install

8) Edited my xorg.conf to include the following:

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Collection 2
Option  Protocol usb
Option  Device /dev/uhid0
Option  Emulate3Timeout 10
EndSection

The touch panel is now detected as uhid0 instead of ums0 and the mouse
input driver now handles it directly instead of going through /dev/sysmouse.

Note that the 'Collection 2' option line is critical here. The driver
defaults to using collection 1, which is the touch screen. However this
doesn't provide a working pointer. Collection 2 is for the mouse emulation
mode, which is not ideal, but at least it allows me to move the cursor with
my finger now.

Button presses are a little tricky. There are 3 possible results:

1) Quick press -- button 1
2) Press and hold for a few seconds - button 2
3) Tap, release for a second, then press and hold -- button 3

I put the complete output of usbuhidctl -r and my xorg.conf file here:

http://people.freebsd.org/~wpaul/expoc

Note that I'm using the VESA driver for now as the Intel driver seems to
lock up when used with the Intel Pineview graphics controller in this
tablet.

Also note that it looks like you can use pretty much any other USB mouse
this way too, just remember to remove

eGalax USB touch panel on ExoPC Slate vs. FreeBSD and X11

2012-11-15 Thread Bill Paul

Okay. I have my doubts that anyone will be able to answer this question
but I'm going to try anyway.

I have an ExoPC Slate tablet with FreeBSD 9.0 freshly installed on it,
and it has the following touch screen device:

ugen0.2: eGalax Inc. at usbus0
ums0: eGalax Inc. USB TouchController, class 0/0, rev 1.10/10.06, addr 2 on 
usbus0

tablet# usbconfig -u 0 -a 2 dump_device_desc
ugen0.2: USB TouchController eGalax Inc. at usbus0, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0110 
  bDeviceClass = 0x 
  bDeviceSubClass = 0x 
  bDeviceProtocol = 0x 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x0eef 
  idProduct = 0x72a1 
  bcdDevice = 0x1006 
  iManufacturer = 0x0001  eGalax Inc.
  iProduct = 0x0002  USB TouchController
  iSerialNumber = 0x  no string
  bNumConfigurations = 0x0001 

I put the complete dmesg.boot from FreeBSD 9.0 on the tablet at:

http://people.freebsd.org/~wpaul/exopc/dmesg.boot

This device is detected by the ums(4) driver as a USB mouse. However, it
doesn't quite work right as the ums(4) driver doesn't support multitouch
gestures. It senses taps on the screen as button presses, but the cursor
doesn't move.

My question is:

Can someone please tell me how to get this device to work with Xorg in
FreeBSD (in this case, FreeBSD 9.0)?

Here are some things I'd prefer you didn't tell me:

- Try the uep(4) driver! Yes, I know about the uep(4) driver. It's for
  a different class of device. It doesn't support this one.

- Try this patch! I'm hoping for an officially supported solution
  rather than an experimental patch. I mean, it's not that I don't
  appreciate someone's hard work and all, but these things have been
  around for a while now; you'd think support for it would already
  be integrated. And besides, it works with Linux. (You don't know
  how long I've been wanting to say that.)

- Go to this web page! This _might_ be an acceptable answer _IF_ the
  said page contains specific instructions which are known to work. I
  already searched through many web pages before I came here.

- Hey Bill, why don't you just write your own driver? Because I don't
  write FreeBSD drivers anymore, and I certainly don't write USB HID
  drivers, and because fuck you, that's why. (Note: I said that last
  part with a smile on my face, just in case it wasn't clear. Sometimes
  people have a hard time grasping my particular brand of humor.)

This particular touch screen is basically a USB HID class device. I
suspect there's some kind of gimmick you can do with libusb to get it
to work with the X server, but I've already spent some time on various
experimenmts and come up empty. As I said, I'm hoping there's official
support for this kind of device, and I just need to know the right
magic incantation to turn it on.

Any help would be appreciated.

-Bill

--
=
-Bill Paul(510) 749-2329 | Member of Technical Staff,
 wp...@windriver.com | Master of Unix-Fu - Wind River Systems
=
   I put a dollar in a change machine. Nothing changed. - George Carlin
=
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

ndis build for syslink AE2500 usb wifi stick failed

2012-09-23 Thread Fbsd8


Followed the instructions from here
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html#CONFIG-NETWORK-NDIS

But when I rebooted got these dmesg messages.

 no match for ZwQueryInformationFile
 no match for ZwReadFile
 no match for ZwCreateFile
 no match for ExfInterlockedRemoveHeadList
 no match for ExfInterlockedInsertTailList

 ugen3.2: Cisco at usbus3
 ndis0: Cisco Linksys AE2500, rev 2.00/0.01, addr 2 on usbus3
 ndis0: NDIS API version: 5.1
 ndis0: init handler failed
 device_attach: ndis0 attach returned 6

How do I get those missing 5 files included into the ndis build?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

How to configure USB wifi stick?


Looking for howto on configuring a
Cisco Linksys AE2500 USB wifi stick.
When I plug it in all I get is the USB msg
ugen3.2: Cisco at usbus3.
FreeBSD handbook does not have section on usb wifi setup.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?


On 22.09.2012 16:26, Fbsd8 wrote:

Looking for howto on configuring a
Cisco Linksys AE2500 USB wifi stick.
When I plug it in all I get is the USB msg
ugen3.2: Cisco at usbus3.
FreeBSD handbook does not have section on usb wifi setup.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org



Is your USB stick or Chip on hardware list?
http://www.freebsd.org/releases/8.2R/hardware.html#WLAN
rum and ural driver are for some wifi usb sticks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?


lokada...@gmx.de wrote:

On 22.09.2012 16:26, Fbsd8 wrote:

Looking for howto on configuring a
Cisco Linksys AE2500 USB wifi stick.
When I plug it in all I get is the USB msg
ugen3.2: Cisco at usbus3.
FreeBSD handbook does not have section on usb wifi setup.




Is your USB stick or Chip on hardware list?
http://www.freebsd.org/releases/8.2R/hardware.html#WLAN
rum and ural driver are for some wifi usb sticks.



NO
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?


On 22.09.2012 19:14, Fbsd8 wrote:

lokada...@gmx.de wrote:

On 22.09.2012 16:26, Fbsd8 wrote:

Looking for howto on configuring a
Cisco Linksys AE2500 USB wifi stick.
When I plug it in all I get is the USB msg
ugen3.2: Cisco at usbus3.
FreeBSD handbook does not have section on usb wifi setup.




Is your USB stick or Chip on hardware list?
http://www.freebsd.org/releases/8.2R/hardware.html#WLAN
rum and ural driver are for some wifi usb sticks.



NO
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org



Have you load bwi driver?
it looks like Linksys AE2500 USB use BMC4323 chipset.
https://www.google.de/search?q=Cisco+Linksys+AE2500+chipset
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?


lokada...@gmx.de wrote:

On 22.09.2012 19:14, Fbsd8 wrote:

lokada...@gmx.de wrote:

On 22.09.2012 16:26, Fbsd8 wrote:

Looking for howto on configuring a
Cisco Linksys AE2500 USB wifi stick.
When I plug it in all I get is the USB msg
ugen3.2: Cisco at usbus3.
FreeBSD handbook does not have section on usb wifi setup.




Is your USB stick or Chip on hardware list?
http://www.freebsd.org/releases/8.2R/hardware.html#WLAN
rum and ural driver are for some wifi usb sticks.



NO


Have you load bwi driver?
it looks like Linksys AE2500 USB use BMC4323 chipset.
https://www.google.de/search?q=Cisco+Linksys+AE2500+chipset


I am running 9.1-RC1 and have no boot loader.conf for any wifi modules.
Is there some usb.conf file where I can add statement for my USB linksys 
AE2500 wifi stick so the kernel modules will get auto loaded at first 
use time?

If not, what are the boot loader statements I need to add?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?


On 22.09.2012 20:59, Fbsd8 wrote:

lokada...@gmx.de wrote:

On 22.09.2012 19:14, Fbsd8 wrote:

lokada...@gmx.de wrote:

On 22.09.2012 16:26, Fbsd8 wrote:

Looking for howto on configuring a
Cisco Linksys AE2500 USB wifi stick.
When I plug it in all I get is the USB msg
ugen3.2: Cisco at usbus3.
FreeBSD handbook does not have section on usb wifi setup.




Is your USB stick or Chip on hardware list?
http://www.freebsd.org/releases/8.2R/hardware.html#WLAN
rum and ural driver are for some wifi usb sticks.



NO


Have you load bwi driver?
it looks like Linksys AE2500 USB use BMC4323 chipset.
https://www.google.de/search?q=Cisco+Linksys+AE2500+chipset


I am running 9.1-RC1 and have no boot loader.conf for any wifi modules.
Is there some usb.conf file where I can add statement for my USB 
linksys AE2500 wifi stick so the kernel modules will get auto loaded 
at first use time?

If not, what are the boot loader statements I need to add?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org



Create loader.conf self.
cd /boot/
edit loader.conf
/autoboot_delay/=3
When you reboot your system and you see, that you only have 3 or 2 
seconds instead 10 your loader.conf will be load.

When i remeber right, put bwi_load=YES in loader.conf

From command line you can make kldload bwi to load and test it 
without reboot.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?


On 22.09.2012 20:59, Fbsd8 wrote:

I am running 9.1-RC1 and have no boot loader.conf for any wifi modules.
Is there some usb.conf file where I can add statement for my USB 
linksys AE2500 wifi stick so the kernel modules will get auto loaded 
at first use time?

If not, what are the boot loader statements I need to add?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org



To load bwi in loader.conf put

if_bwi_load=YES
in it.

http://www.freebsd.org/cgi/man.cgi?query=bwisektion=4manpath=FreeBSD+8.2-RELEASE


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?

2012-09-22 Thread Matthias Apitz

El día Saturday, September 22, 2012 a las 02:59:39PM -0400, Fbsd8 escribió:

  Have you load bwi driver?
  it looks like Linksys AE2500 USB use BMC4323 chipset.
  https://www.google.de/search?q=Cisco+Linksys+AE2500+chipset
  
 I am running 9.1-RC1 and have no boot loader.conf for any wifi modules.
 Is there some usb.conf file where I can add statement for my USB linksys 
 AE2500 wifi stick so the kernel modules will get auto loaded at first 
 use time?
 If not, what are the boot loader statements I need to add?

How about

$ man bwi
$ man loader.conf

HIH

matthias
-- 
Matthias Apitz   |  /\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211   |  / \ - Respect for open standards
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to configure USB wifi stick?