vnc over ssh with tp-link tl-wn725n causes laptop to freeze
Dear All, Thank you kindly in advance for your help. Please forgive any trivial questions or mistakes by me. I am new to linux (1 month). Hope this is the proper place for such a question. Here goes. I have a number of tp-link tl-wn725n usb adapters that I want to use in laptops. The laptops are running debian wheezy v.7.8 fully updated. I can use the laptops with the tp-link adapters fine for web surfing, downloading a file, etc.. For such things my laptop tp-link combos work great, everything is fine. I installed the tp-link adapters via: http://brilliantlyeasy.com/ubuntu-linux-tl-wn725n-tp-link-version-2-wifi-driver-install/ using the following commands: apt-get update apt-get install linux-headers-$(uname -r) apt-get update apt-get install build-essential apt-get install git git clone https://github.com/lwfinger/rtl8188eu cd rtl8188eu make all make install insmod 8188eu.ko The problem is that when I attempt to vnc over an ssh connection to a debian box running either x11vnc or tightvncserver, I can make the connection, but then the laptop is freezes. This freeze happens withing 2 seconds of making the connection. When the laptop freezes the adapter lights go dark. The laptop becomes unresponsive, from what I can tell, and I have to do a hard reboot. I have tried vnc over ssh with same laptop over the ethernet nic with the tp-link wireless removed from the laptop and I have no problems. I have also tried another laptop, same behavior, vnc over ssh works with wired, freezes laptop with tp-link. laptops are lenovo x120e and z40-70, if this helps. Hopefully I have provided some good information that helps. Please let me know if there is something I've done wrong, such as missed the latest driver, etc. Happy to try to get this working and report back. Thank you kindly, anon ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: vnc over ssh with tp-link tl-wn725n causes laptop to freeze
Dear Mr. Finger, Thank you kindly for your help and patience. I'm sure you explain to write 'uname -r' to many noobs such as myself, your patient instruction is appreciated; thanks for teaching. output of 'uname -r': 3.2.0-v-amd64 I will try the v4.1.8_9499 github and report back. Thank you kindly for this info. >From what I can tell from your email there is an additional in-kernel driver. Somehow I missed this. Before using the install method I described, I did plug the device in, and i didn't see any pop-ups or get any notifications after running ifconfig (no wlan0 posted). Maybe I did something wrong? If v4.1.8_9499 github does not solve my problem, can you kindly guide me to a link showing how to run the in-kernel version or provide some other form of guidance? Your assumptions about my prior OS are spot on. The malware, the need to restart every few days, among many other reasons is why I made the switch to linux, and I am supremely enjoying it. I have found debian to be quite useful and have already switched my primary workstation and a number of other machines. I am definitely seeing better up time and increased productivity for the simple tasks I run. Much of this is thanks to the great community such as yourself and Mr Carpenter, thanks for helping! I built the code in an administrator account in /home/ using sudo. I could not get it to build without sudo. Hopefully this isnt too far off, but I'm sure there is more to learn about users and security permissions. Definitely do not want to boggle my machine. I will report back regarding my v4.1.8_9499 github progress. Kind regards, anon On Wed, 2015-04-22 at 09:52 -0500, Larry Finger wrote: > On 04/22/2015 02:48 AM, Dan Carpenter wrote: > > That's Larry Finger's driver and it might be different from the > > kernel.org driver. I've added him to the CC list. If you look in > > /var/log/messages there may be some useful warning messages from when > > the driver loaded to when it crashed? > > Actually, that driver is Realtek's. I provide the GitHub repo as a service to > users who find faults with the kernel version. As I have no knowledge of the > device's internals, my help is essentially limited to fixing crashes when the > reporter provides the kernel messages as text or a screen photo, and fixing > compilation problems for older kernels. One caveat: Since Ubuntu and RHEL > started backporting wireless API changes to older kernels, their users have > to > fix their own build problems. However, I will ensure that it builds on a > vanilla > 3.X source. > > @Anon: > > I do need to see the kernel messages, either from the log files or a photo of > the logging screen. In subsequent postings, always include your kernel > version, > which is critical. Open a terminal and enter 'uname -r' to find that info. If > your kernel is 3.12 or newer, then you should try the in-kernel version of > the > driver. If it also has the problem, the priority for fixing the bug is > enhanced > a lot. You should also switch to the v4.1.8_9499 branch of the GitHub repo > and > try that version. The master branch, which is what you are likely using, is > v4.1.4. Quite a bit has changed. > > Finally, the person who wrote that web page that you linked gave very bad > advice. Source code should be kept in the user's file area, not in that of > root. > The reason is that make files can sometimes have subtle bugs that generate > harmless messages when run by an unprivileged user, but do serious damage > when > run as root. An example was shown very dramatically a few years ago when > there > was an error in the kernel build system. If you were running as root, it > deleted > /dev/null. After that, the system did very strange things. Of course, > building > 8188eu is not very complicated and is unlikely to have any similar bugs, but > running everything that you can as an unprivileged user is extremely good > practice. I assume that you ran some less secure OS before you changed to > Linux. > That one probably blurred the distinction between an ordinary user and root, > and > that OS was likely plagued by malware! > > Larry > ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Re: vnc over ssh with tp-link tl-wn725n causes laptop to freeze
On Wed, 2015-04-22 at 13:18 -0500, Larry Finger wrote:
> On 04/22/2015 11:45 AM, dborlau...@gmail.com wrote:
> > Dear Mr. Carpenter,
> >
> > Thank you kindly for your help and these nice suggestions. Thank you
> > for CCing Mr. Finger. Actually, I stumbled across his name in my online
> > searches as on of the developers of this driver, and that's why I tried
> > to seek help here.
> >
> > I was able to repeat the problem and then capture /var/log/messages. It
> > is attached to this email. hopefully it went through? It's hard for me
> > to help locate the problem, but I believe I initiated the vnc over ssh
> > action around line 2892-2910 of the attached
> > ("201504220906-0700-messages.txt"), with corresponding messages
> > 2892-2910 being:
> > "
> > Apr 22 08:33:28 x120ea rsyslogd-2177: imuxsock begins to drop messages
> > from pid 3112 due to rate-limiting
> > Apr 22 08:33:30 x120ea rsyslogd-2177: imuxsock lost 49 messages from pid
> > 3112 due to rate-limiting
> > Apr 22 08:35:29 x120ea kernel: [ 153.267088] atkbd serio0: Unknown key
> > pressed (translated set 2, code 0xf1 on isa0060/serio0).
> > Apr 22 08:35:29 x120ea kernel: [ 153.267102] atkbd serio0: Use
> > 'setkeycodes e071 ' to make it known.
> > Apr 22 08:35:29 x120ea kernel: [ 153.277905] atkbd serio0: Unknown key
> > released (translated set 2, code 0xf1 on isa0060/serio0).
> > Apr 22 08:35:29 x120ea kernel: [ 153.277920] atkbd serio0: Use
> > 'setkeycodes e071 ' to make it known.
> > Apr 22 08:35:30 x120ea kernel: [ 153.762396] thinkpad_acpi: unknown
> > possible thermal alarm or keyboard event received
> > Apr 22 08:35:30 x120ea kernel: [ 153.767324] thinkpad_acpi:
> > temperatures (Celsius): 46 0 46 0 0 0 25 0
> > Apr 22 08:35:30 x120ea kernel: [ 153.767352] thinkpad_acpi: unhandled
> > HKEY event 0x6040
> > Apr 22 08:35:30 x120ea kernel: [ 153.767361] thinkpad_acpi: please
> > report the conditions when this event happened to
> > ibm-acpi-de...@lists.sourceforge.net
> > Apr 22 08:35:44 x120ea kernel: [ 167.636259] atkbd serio0: Unknown key
> > pressed (translated set 2, code 0xf1 on isa0060/serio0).
> > Apr 22 08:35:44 x120ea kernel: [ 167.636274] atkbd serio0: Use
> > 'setkeycodes e071 ' to make it known.
> > Apr 22 08:35:44 x120ea kernel: [ 167.646902] atkbd serio0: Unknown key
> > released (translated set 2, code 0xf1 on isa0060/serio0).
> > Apr 22 08:35:44 x120ea kernel: [ 167.646917] atkbd serio0: Use
> > 'setkeycodes e071 ' to make it known.
> > Apr 22 08:35:44 x120ea kernel: [ 168.131693] thinkpad_acpi: unknown
> > possible thermal alarm or keyboard event received
> > Apr 22 08:35:44 x120ea kernel: [ 168.143598] thinkpad_acpi:
> > temperatures (Celsius): 47 0 47 0 0 0 25 0
> > Apr 22 08:35:44 x120ea kernel: [ 168.143627] thinkpad_acpi: unhandled
> > HKEY event 0x6040
> > Apr 22 08:35:44 x120ea kernel: [ 168.143636] thinkpad_acpi: please
> > report the conditions when this event happened to
> > ibm-acpi-de...@lists.sourceforge.net
> > Apr 22 08:40:59 x120ea rsyslogd: [origin software="rsyslogd"
> > swVersion="5.8.11" x-pid="2253" x-info="http://www.rsyslog.com";]
> > rsyslogd was HUPed
> > "
>
> Unfortunately, that log segment does not have help for the problem. In fact,
> the
> logs seldom have any useful information. When a critical error occurs, the
> results are sent to an in-memory buffer and may be sent to the disk, but they
> write is not usually completed. When the system is restarted, the info does
> not
> make it to the logging file.
>
> At the moment, I am running x11vnc server over an ssh link with vnxviewer
> displaying the image. Other than the slowness of the network link, I am
> having
> no problems - the v4.1.8_2499 branch is what is running.
>
> Next, I will try the master branch.
>
> Larry
>
>
Dear Larry,
I am happy to report that I had success with the
("https://github.com/lwfinger/rtl8188eu";) master branch. I no longer
have any problems. Thank you kindly for your help! Very much
appreciated!
Kind regards,
anon
[Solved]
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
