USB serial adapter not showing as /dev/ttyUSBn
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I have an old system running 14.04 LTS with a USB/RS232 adapter to connect a modem. It was working well until I had to restore the system disk from a backup - only 4 days old, fortunately :-)
Now I connect the USB cable and it shows up on lsusb but /dev/ttyUSB0 is not being created.
lsusb output:
Bus 005 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
syslog when connecting:
Apr 19 17:39:18 tomahawk kernel: [189143.332695] usb 5-1.4: new full-speed USB device number 5 using xhci_hcd
Apr 19 17:39:18 tomahawk kernel: [189143.432551] usb 5-1.4: New USB device found, idVendor=0403, idProduct=6001
Apr 19 17:39:18 tomahawk kernel: [189143.432553] usb 5-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 19 17:39:18 tomahawk kernel: [189143.432554] usb 5-1.4: Product: USB FAST SERIAL ADAPTER
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: Manufacturer: FTDI
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: SerialNumber: FTB9JFF6
Apr 19 17:39:18 tomahawk mtp-probe: checking bus 5, device 5: "/sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/usb5/5-1/5-1.4"
Apr 19 17:39:18 tomahawk mtp-probe: bus: 5, device: 5 was not an MTP device
Any ideas on what might be missing?
TIA
Fernando
usb usb-modem
asked Apr 19 at 17:33
ferdez
104
add a comment |Â
up vote
0
down vote
favorite
I have an old system running 14.04 LTS with a USB/RS232 adapter to connect a modem. It was working well until I had to restore the system disk from a backup - only 4 days old, fortunately :-)
Now I connect the USB cable and it shows up on lsusb but /dev/ttyUSB0 is not being created.
lsusb output:
Bus 005 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
syslog when connecting:
Apr 19 17:39:18 tomahawk kernel: [189143.332695] usb 5-1.4: new full-speed USB device number 5 using xhci_hcd
Apr 19 17:39:18 tomahawk kernel: [189143.432551] usb 5-1.4: New USB device found, idVendor=0403, idProduct=6001
Apr 19 17:39:18 tomahawk kernel: [189143.432553] usb 5-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 19 17:39:18 tomahawk kernel: [189143.432554] usb 5-1.4: Product: USB FAST SERIAL ADAPTER
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: Manufacturer: FTDI
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: SerialNumber: FTB9JFF6
Apr 19 17:39:18 tomahawk mtp-probe: checking bus 5, device 5: "/sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/usb5/5-1/5-1.4"
Apr 19 17:39:18 tomahawk mtp-probe: bus: 5, device: 5 was not an MTP device
Any ideas on what might be missing?
TIA
Fernando
usb usb-modem
asked Apr 19 at 17:33
ferdez
104
You probably need to reinstall the FTDI driver for it. Interminaltypedkms statusand lets see what we get.
– heynnema
Apr 19 at 18:42
"dkms status" comes up empty... :-/
– ferdez
Apr 20 at 7:48
I've come to realize that I probably did a mistake in reinstalling the desktop image instead of the server image. My lsmod output is very small: Module Size Used by hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid psmouse 122880 0 ahci 36864 3 r8169 81920 0 libahci 32768 1 ahci mii 16384 1 r8169 fjes 28672 0
– ferdez
Apr 20 at 8:11
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an old system running 14.04 LTS with a USB/RS232 adapter to connect a modem. It was working well until I had to restore the system disk from a backup - only 4 days old, fortunately :-)
Now I connect the USB cable and it shows up on lsusb but /dev/ttyUSB0 is not being created.
lsusb output:
Bus 005 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
syslog when connecting:
Apr 19 17:39:18 tomahawk kernel: [189143.332695] usb 5-1.4: new full-speed USB device number 5 using xhci_hcd
Apr 19 17:39:18 tomahawk kernel: [189143.432551] usb 5-1.4: New USB device found, idVendor=0403, idProduct=6001
Apr 19 17:39:18 tomahawk kernel: [189143.432553] usb 5-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 19 17:39:18 tomahawk kernel: [189143.432554] usb 5-1.4: Product: USB FAST SERIAL ADAPTER
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: Manufacturer: FTDI
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: SerialNumber: FTB9JFF6
Apr 19 17:39:18 tomahawk mtp-probe: checking bus 5, device 5: "/sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/usb5/5-1/5-1.4"
Apr 19 17:39:18 tomahawk mtp-probe: bus: 5, device: 5 was not an MTP device
Any ideas on what might be missing?
TIA
Fernando
usb usb-modem
asked Apr 19 at 17:33
ferdez
104
I have an old system running 14.04 LTS with a USB/RS232 adapter to connect a modem. It was working well until I had to restore the system disk from a backup - only 4 days old, fortunately :-)
Now I connect the USB cable and it shows up on lsusb but /dev/ttyUSB0 is not being created.
lsusb output:
Bus 005 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
syslog when connecting:
Apr 19 17:39:18 tomahawk kernel: [189143.332695] usb 5-1.4: new full-speed USB device number 5 using xhci_hcd
Apr 19 17:39:18 tomahawk kernel: [189143.432551] usb 5-1.4: New USB device found, idVendor=0403, idProduct=6001
Apr 19 17:39:18 tomahawk kernel: [189143.432553] usb 5-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 19 17:39:18 tomahawk kernel: [189143.432554] usb 5-1.4: Product: USB FAST SERIAL ADAPTER
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: Manufacturer: FTDI
Apr 19 17:39:18 tomahawk kernel: [189143.432555] usb 5-1.4: SerialNumber: FTB9JFF6
Apr 19 17:39:18 tomahawk mtp-probe: checking bus 5, device 5: "/sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0/usb5/5-1/5-1.4"
Apr 19 17:39:18 tomahawk mtp-probe: bus: 5, device: 5 was not an MTP device
Any ideas on what might be missing?
TIA
Fernando
usb usb-modem
asked Apr 19 at 17:33
ferdez
104
asked Apr 19 at 17:33
ferdez
104
asked Apr 19 at 17:33
ferdez
104
asked Apr 19 at 17:33
ferdez
104
104
You probably need to reinstall the FTDI driver for it. Interminaltypedkms statusand lets see what we get.
– heynnema
Apr 19 at 18:42
"dkms status" comes up empty... :-/
– ferdez
Apr 20 at 7:48
I've come to realize that I probably did a mistake in reinstalling the desktop image instead of the server image. My lsmod output is very small: Module Size Used by hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid psmouse 122880 0 ahci 36864 3 r8169 81920 0 libahci 32768 1 ahci mii 16384 1 r8169 fjes 28672 0
– ferdez
Apr 20 at 8:11
add a comment |Â
You probably need to reinstall the FTDI driver for it. Interminaltypedkms statusand lets see what we get.
– heynnema
Apr 19 at 18:42
"dkms status" comes up empty... :-/
– ferdez
Apr 20 at 7:48
I've come to realize that I probably did a mistake in reinstalling the desktop image instead of the server image. My lsmod output is very small: Module Size Used by hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid psmouse 122880 0 ahci 36864 3 r8169 81920 0 libahci 32768 1 ahci mii 16384 1 r8169 fjes 28672 0
– ferdez
Apr 20 at 8:11
You probably need to reinstall the FTDI driver for it. In
terminal type dkms status and lets see what we get.– heynnema
Apr 19 at 18:42
You probably need to reinstall the FTDI driver for it. In
terminal type dkms status and lets see what we get.– heynnema
Apr 19 at 18:42
"dkms status" comes up empty... :-/
– ferdez
Apr 20 at 7:48
"dkms status" comes up empty... :-/
– ferdez
Apr 20 at 7:48
I've come to realize that I probably did a mistake in reinstalling the desktop image instead of the server image. My lsmod output is very small: Module Size Used by hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid psmouse 122880 0 ahci 36864 3 r8169 81920 0 libahci 32768 1 ahci mii 16384 1 r8169 fjes 28672 0
– ferdez
Apr 20 at 8:11
I've come to realize that I probably did a mistake in reinstalling the desktop image instead of the server image. My lsmod output is very small: Module Size Used by hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid psmouse 122880 0 ahci 36864 3 r8169 81920 0 libahci 32768 1 ahci mii 16384 1 r8169 fjes 28672 0
– ferdez
Apr 20 at 8:11
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
Found it.
The process I used to restore the system was:
- install a fresh 14.04 on a new boot disk
- restore everything from backup except /boot
Since I had the system up-to-date, I hoped there would be no problems with this. Almost...
Strangely, the fresh install left me with a 4.40 linux kernel, which is not part of the distribution. So, when I restored /lib, the 4.40 kernel modules where replaced by the 3.13 ones. This meant that the FTDI module was not being loaded anymore.
The solution was to force the reinstall of the 3.13 kernel and manually remove the 4.40 kernel files from /boot. After running update-grub, everything was back to normal.
Thanks for the pointing the right direction @heynnema
edited May 24 at 1:53
Jason Aller
44358
answered Apr 20 at 10:17
ferdez
104
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Found it.
The process I used to restore the system was:
- install a fresh 14.04 on a new boot disk
- restore everything from backup except /boot
Since I had the system up-to-date, I hoped there would be no problems with this. Almost...
Strangely, the fresh install left me with a 4.40 linux kernel, which is not part of the distribution. So, when I restored /lib, the 4.40 kernel modules where replaced by the 3.13 ones. This meant that the FTDI module was not being loaded anymore.
The solution was to force the reinstall of the 3.13 kernel and manually remove the 4.40 kernel files from /boot. After running update-grub, everything was back to normal.
Thanks for the pointing the right direction @heynnema
edited May 24 at 1:53
Jason Aller
44358
answered Apr 20 at 10:17
ferdez
104
add a comment |Â
up vote
0
down vote
Found it.
The process I used to restore the system was:
- install a fresh 14.04 on a new boot disk
- restore everything from backup except /boot
Since I had the system up-to-date, I hoped there would be no problems with this. Almost...
Strangely, the fresh install left me with a 4.40 linux kernel, which is not part of the distribution. So, when I restored /lib, the 4.40 kernel modules where replaced by the 3.13 ones. This meant that the FTDI module was not being loaded anymore.
The solution was to force the reinstall of the 3.13 kernel and manually remove the 4.40 kernel files from /boot. After running update-grub, everything was back to normal.
Thanks for the pointing the right direction @heynnema
edited May 24 at 1:53
Jason Aller
44358
answered Apr 20 at 10:17
ferdez
104
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Found it.
The process I used to restore the system was:
- install a fresh 14.04 on a new boot disk
- restore everything from backup except /boot
Since I had the system up-to-date, I hoped there would be no problems with this. Almost...
Strangely, the fresh install left me with a 4.40 linux kernel, which is not part of the distribution. So, when I restored /lib, the 4.40 kernel modules where replaced by the 3.13 ones. This meant that the FTDI module was not being loaded anymore.
The solution was to force the reinstall of the 3.13 kernel and manually remove the 4.40 kernel files from /boot. After running update-grub, everything was back to normal.
Thanks for the pointing the right direction @heynnema
edited May 24 at 1:53
Jason Aller
44358
answered Apr 20 at 10:17
ferdez
104
Found it.
The process I used to restore the system was:
- install a fresh 14.04 on a new boot disk
- restore everything from backup except /boot
Since I had the system up-to-date, I hoped there would be no problems with this. Almost...
Strangely, the fresh install left me with a 4.40 linux kernel, which is not part of the distribution. So, when I restored /lib, the 4.40 kernel modules where replaced by the 3.13 ones. This meant that the FTDI module was not being loaded anymore.
The solution was to force the reinstall of the 3.13 kernel and manually remove the 4.40 kernel files from /boot. After running update-grub, everything was back to normal.
Thanks for the pointing the right direction @heynnema
edited May 24 at 1:53
Jason Aller
44358
answered Apr 20 at 10:17
ferdez
104
edited May 24 at 1:53
Jason Aller
44358
edited May 24 at 1:53
Jason Aller
44358
edited May 24 at 1:53
Jason Aller
44358
44358
answered Apr 20 at 10:17
ferdez
104
answered Apr 20 at 10:17
ferdez
104
answered Apr 20 at 10:17
ferdez
104
104
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1026471%2fusb-serial-adapter-not-showing-as-dev-ttyusbn%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
You probably need to reinstall the FTDI driver for it. In
terminaltypedkms statusand lets see what we get.– heynnema
Apr 19 at 18:42
"dkms status" comes up empty... :-/
– ferdez
Apr 20 at 7:48
I've come to realize that I probably did a mistake in reinstalling the desktop image instead of the server image. My lsmod output is very small: Module Size Used by hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid psmouse 122880 0 ahci 36864 3 r8169 81920 0 libahci 32768 1 ahci mii 16384 1 r8169 fjes 28672 0
– ferdez
Apr 20 at 8:11