New answers tagged

1

On Linux, the following should work without requiring a new driver: sudo modprobe ftdi-sio vendor=0x0001 product=0x0002


0

I had the same issue. I solved it in 3 steps: Get the source code for linux from Tp-link website (source code) Get the right source code of the kernel in use. This very good tutorial was a great help: https://github.com/notro/rpi-source/wiki Look up in the Makefile in the source code from tp-link, to set up the right platform to compile and fix some minor ...


1

you can also try the command $ usb-devices It would give you something like this, T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=03.19 S: Manufacturer=Linux 3.19.0-59-generic xhci-hcd S: Product=xHCI Host Controller S: ...


1

Another way of finding the /dev/sd device that corresponds to a disc that has no LABEL nor UUID is to use its serial id. For example, my SSD says $ sudo hdparm -I /dev/sda Model Number: KINGSTON SH103S3240G Serial Number: 50999B9999926F99 And I can find which /dev/sd device it is by following the link in ...


2

I am almost sure it's not possible to assign the # of sd, but you might work this around with udev rule that would set up links to the actual sdX and sdXY upon disk drive connection: KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{model}=="USB 2.0 Storage Device", SYMLINK+="usbhd%n" would create these links: /dev/usbhd - The fdiskable node /dev/usbhd1 - ...


1

You would need to specify the mounting point based on the device's UUID. You should refer to the official Ubuntu documentation page on the subject for usage details. Here are examples (your output will be different, but similarly formatted). The command: sudo blkid produces an output similar to: /dev/sda1: TYPE="ntfs" UUID="72C0DE8EC0DE57C5" ...


0

You must use the "dd" command, I've tried with Win32Imager and gotten far but mkfs has issues, install guide even says to use "dd". Easiest is to fresh install Arch, download BlackArch; sudo dd bs=512M if=blackarch-linux.iso of=/dev/sda ;


0

Insignia doesn't explicitly support linux. They also don't seem to list the chipset used in the adapter in the downloadable documentation (bummer!). While it may not work, I wouldn't be surprised if they use the same chipset as startech. So try the drivers listed on their page version V1.14.4 for kernel 2.6.25 or newer. Post back how it goes.


1

The origin of the error code can be found in the source code for the hub in question. e.g. grep -A 1 -m 1 22 /usr/src/linux-source-4.3/drivers/usb/host/xhci.h #define PORT_PLC (1 << 22) /* port configure error change - port failed to configure its link partner */ You'll find the meaning of some error codes in ...


2

This information can be retrieved from the iSerial entry of the verbose output of the lsusb. Easiest is to pass the output to the the less viewer and search manually with /, or for example with grep: $ lsusb -v 2>/dev/null | grep '^Bus\|iSerial' Bus 001 Device 029: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard iSerial 0 ...


1

I got the second modem ativated using the steps at http://askubuntu.com/questions/512092/how-to-set-modem-on-huawei-mobile-broadband: create /etc/usb_modeswitch.d/19d2:2000 sudo touch /etc/usb_modeswitch.d/19d2:2000 sudo nano /etc/usb_modeswitch.d/19d2:2000 Put: ######################################################## # ZTE WCDMA Technologies MSM ...


0

There seem to be several answers for this on our sister site askubuntu.com such as this one which asks you to grep enabled /proc/acpi/wakeup You should find entries for your motherboard's usb hubs such as EHC1 S4 *enabled pci:0000:00:1d.0 EHC2 S4 *enabled pci:0000:00:1a.0 For each hub, you can toggle the setting to disabled by ...


1

You would need to add a USB Device/Peripheral controller to the computer, as opposed to the USB Host Controller they tend to come with. Something like this: https://www.maximintegrated.com/en/products/interface/controllers-expanders/MAX3420E.html Unfortunately, you'd have to find a way to wire it onto your motherboard. Technically, it can be done. ...


0

To get information about linux-headers type the following command: apt-cache search linux-headers The output is somthing like: linux-headers-3.16.0-4-common - Common header files for Linux 3.16.0-4 linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64 linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package) ...


1

It looks as though the journal has become corrupt, doing some searches over the past few days, this seems to not be uncommon on devices that use LUKS. You could try running an fsck on the device, acknowledging that any data on the device may not be accessible after - you may like to use dd to make a copy of the drive before this. A common resolution ...


0

My /etc/rc.local was wired. I deleted it. And now everything seems fine. #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script ...


0

I often get errors like this for no apparent reason and often simply unmounting and remounting fixes it. You can do this with the following commands. unmount - I know it never mounted in the first place, and will likely throw an error, but I would run to ensure a clean state for running luksClose sudo umount "/media/userone/New Volume" lukClose sudo ...


2

If we look at the driver source code mon_text.c we can see in function mon_text_add() where this /sys file is created: (loosely) snprintf(name, NAMESZ, "%ds", busnum); debugfs_create_file(name, 0600, mon_dir, mbus, &mon_fops_stat); and if we follow mon_fops_stat we see it defined in mon_stat.c where the open routine is mon_stat_open() which creates ...


0

The 3.4 GB image is not a live image. It's a full-blown installer with lots of desktop environments, packages for printing, ssh, etc. It could be use to install real (aka non-live) Debian on disks (e.g. hard drives, USB flash drives or even SD cards). If Universal USB installer failed to write it to the flash drive, try Rufus or Unetbootin (if you have a ...


0

Solution for all Corsair mechanical keyboards with usbhid quirks. sudo nano /etc/default/grub or any other editor you like to use instead of nano. you will see this line GRUB_CMDLINE_LINUX_DEFAULT="" make sure to put the usbhid.quircks between the quotes and save that. In my case I had to change it to this line ...


3

The installer considers that the USB stick you used for installation is a CD or DVD image; it left a reference to it in /etc/apt/sources.list as a source of packages for later. If you only wish to install packages from the Internet, you can remove the line mentioning cdrom: in /etc/apt/sources.list, then update the package cache with sudo apt-get update ...


1

You need to modify your /etc/apt/sources.list and comment out the line beginning with deb cdrom:. Use the editor of your choice to add a # directly before deb cdrom: save the file and then run sudo apt-get update.



Top 50 recent answers are included