Experimental Physics and Industrial Control System
Hi Mark,
On 2013-04-18 Mark Rivers wrote:
> I then tried to run modprobe for the new device:
> >sudo modprobe ftdi_sio vendor=0x104d product=0x3000
The modprobe command merely tells the Kernel 'please make sure this module
(driver in your case) is loaded'. Once it has been loaded issuing the
modprobe command again won't have any effect (unless it gets unloaded first,
which won't necessarily happen immediately that you unplug the first USB at
which point the driver is no longer needed, although eventually with no
devices connected the kernel might realize this and throw it out
automatically).
> There is still only device ttyUSB0, not a new ttyUSB1.
>
> What am I doing wrong?
I don't know for sure, but there has to be a way to tell the driver that a new
device has been plugged in. I would normally expect the udev mechanism to do
that, so you might find the answer by reading the document that Eric pointed
to.
- Andrew
--
It is difficult to get a man to understand something, when his salary
depends upon his not understanding it. -- Upton Sinclair
- References:
- Linux USB serial questions Mark Rivers
- RE: Linux USB serial questions Mark Rivers
- Navigate by Date:
- Prev:
Re: Linux USB serial questions Dale L. Brewe
- Next:
RE: Linux USB serial questions Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Linux USB serial questions Dale L. Brewe
- Next:
Re: Linux USB serial questions Jeong Han Lee
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024