Hi,
i want connect my nexus 4 in usb device, so i following these instructions http://www.noobslab.com/2013/06/mount-g ... linux.html
But i have a problem, just when i connect my nexus 4 in USB, i have got one window which spawn full times, so i can't check if my nexus 4 is really mounted or do some others things, my laptop just freeze about a moment..
EDIT: Sorry i forgotten to say what is the message on the window: "Impossible to mount Nexus 4 Impossible to find a udev peripheral corresponding."
my laptop: Aspire ES1-311-C7CZ
i'm on Linux Mint with Cinnemon
Thanks for your answer.
Problem window spam Nexus 4
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Problem window spam Nexus 4
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 4 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Problem window spam Nexus 4
fist thing firs, what is the result of
Code: Select all
inxi -Fxz
Re: Problem window spam Nexus 4
Thanks for answer first
Code: Select all
~ $ inxi -Fxz
System: Host: userPortable Kernel: 3.13.0-24-generic x86_64 (64 bit, gcc: 4.8.2)
Desktop: Gnome Distro: Linux Mint 17 Qiana
Machine: Mobo: Acer model: Aspire ES1-311 version: V1.07 Bios: Insyde version: V1.07 date: 08/13/2014
CPU: Dual core Intel Celeron CPU N2840 (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8666.66
Clock Speeds: 1: 498.00 MHz 2: 498.00 MHz
Graphics: Card: Intel ValleyView Gen7 bus-ID: 00:02.0
X.Org: 1.15.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.0hz
GLX Renderer: Mesa DRI Intel Bay Trail GLX Version: 3.0 Mesa 10.1.0 Direct Rendering: Yes
Audio: Card: Intel ValleyView High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture ver: k3.13.0-24-generic
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 ver: 2.3LK-NAPI port: 1000 bus-ID: 03:00.1
IF: eth0 state: down mac: <filter>
Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k bus-ID: 02:00.0
IF: wlan0 state: up mac: <filter>
Drives: HDD Total Size: 500.1GB (1.3% used) 1: id: /dev/sda model: WDC_WD5000LPVX size: 500.1GB
Partition: ID: / size: 14G used: 5.1G (40%) fs: ext4 ID: /home size: 193G used: 958M (1%) fs: ext4
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: System Temperatures: cpu: 49.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 149 Uptime: 5 min Memory: 724.4/3839.0MB Runlevel: 2 Gcc sys: 4.8.2 Client: Shell inxi: 1.8.4
Re: Problem window spam Nexus 4
I'm afraid you need reinstall your system. that article is old and ubuntu/mint now support mtp mount by default and it will conflicted with the method mentioned in that article.
Re: Problem window spam Nexus 4
Yet, i have installed mint since one week only, and the problem was from the beginning, so i did the article just after, and it is the same problem,
anyway i will try a new installation with Mint "Rebecca".
I keep you updated.
anyway i will try a new installation with Mint "Rebecca".
I keep you updated.
Re: Problem window spam Nexus 4
I have just done the installation, and I tried to link my nexus 4 and i have the same issue..
I did the update too, but there are no changements..
So i will try to do the article, or you have an other solution ?
I did the update too, but there are no changements..
So i will try to do the article, or you have an other solution ?
Re: Problem window spam Nexus 4
You'll probably have to get device IDs info and setup UDEV rules to enable the USB attached NEXUS 4 device to run..
http://wiki.cyanogenmod.org/w/UDEV
--that's something else, but check about udev rules..
http://wiki.cyanogenmod.org/w/UDEV
--that's something else, but check about udev rules..