I've had some luck adding this line to my crontab:
*/1 * * * * ls /mnt/record
It seems by listing the contents of the mount every 60 seconds I stave
off its death, but YMMV. It's definitely a hack, and I look forward to
an actual fix, but in the meantime.
--
You received this bug notification
I wound up using a wireless bridge instead due to the instability of the
adapter.
I still have the hardware though and if you hit a wall I may be able to
assist from the sidelines, I don't remember it being difficult.
--
You received this bug notification because you are a member of Ubuntu
Bug
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/653321/+attachment/1664887/+files/Dependencies.txt
** Attachment added: "Disassembly.txt"
https://bugs.launchpad.net/bugs/653321/+attachment/1664888/+files/Disassembly.txt
** Attachment added: "ProcMaps.txt"
http
Public bug reported:
Binary package hint: synergy
I don't know. I logged in, got a notice that it crashed but it seems to
be working okay at the moment. Sorry I can't be more help.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: synergy 1.3.1-6ubuntu1
ProcVersionSignature: Ubuntu 2.6.3
The driver successfully got me online and at 240-270Mbits for several
hours and then networking completely flaked out and I was getting many
messages like this:
Sep 28 22:40:18 rez kernel: [15159.958213] DeQueueRunning[0]= TRUE!
Sep 28 22:40:19 rez kernel: [15160.574736] DeQueueRunning[0]= TRUE!
S
A copy of my tarball of modified 2.4.0.1 for Maverick 10.10 testers is
attached. There is a kernel module binary included; so if you want to
rebuild, do the following:
1. Extract the archive (it will unpack as ./2010_0709_RT3572_Linux_STA_v2.4.0.1
so extract this where you really want it)
2. `ma
FYI I was able to get the 2.4.0.1 tarball and make my changes to
config.mk and rtusb_dev_id.c and rt_linux.h and it built.
There is something else wrong with 2.4.0.2 from the vendor and the
instructions in this Bug will not get it to build for users. Find the
2.4.0.1 version of the driver and the
I really appreciate the efforts of everyone in this bug, especially Sean
for vigilantly working to support myself and other users of this device.
--
Linksys By Cisco WUSB600N v2 Doesn't Work
https://bugs.launchpad.net/bugs/408165
You received this bug notification because you are a member of Ubun
**’
make[2]: ***
[/home/myusername/Rebuild/2010_0915_RT3572_Linux_STA_v2.4.0.2/os/linux/../../common/cmm_mac_usb.o]
Error 1
make[2]: *** Waiting for unfinished jobs
make[1]: ***
[_module_/home/emory/Rebuild/2010_0915_RT3572_Linux_STA_v2.4.0.2/os/linux]
Error 2
make[1]: Leaving directory
Their clean target in the Makefile doesn't seem to clean up the object
files in os/linux but even after cleaning that up and substituting
usb_buffer_coherent for usb_buffer_alloc_coherent I still get errors.
Last error:
2010_0915_RT3572_Linux_STA_v2.4.0.2/os/linux/../../common/cmm_mac_usb.c:34:
n
Bad news, Maverick 10.10 on 2.6.35-22-generic #33-Ubuntu and the now-
available 2010_0915_RT3572_Linux_STA_v2.4.0.2/ cannot build with the
same instructions.
I could not find 2.4.0.1 anywhere for download.
Here are the errors I get:
/home/myusername/Rebuild/2010_0915_RT3572_Linux_STA_v2.4.0.2/os
I would prefer and recommend that we stop using gender-specific anything
and removing the dependency. Gender isn't a binary "male" "female" for
many people and I think it would be best if localized binaries of IM
clients instead use words that don't have a gender designation or
implication.
"Away
s2disk doesn't work either. having a problem uploading that crash log
however, sorry.
in jaunty i can use s2disk via changing the script in /usr/lib/hal as
discussed in this thread:
http://ubuntuforums.org/showthread.php?t=1215665
these steps in Karmic (or via `sudo s2disk`) results in a hibern
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/31734347/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/31734348/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/31734349/Card0.Amixer.valu
bdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: emory 3354 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf044 irq 22'
Mixer name : 'Rea
sidra ~ % uname -a
Linux sidra 2.6.28-15-generic #50~lp389040oga3 SMP Fri Aug 28 16:56:31 UTC 2009
i686 GNU/Linux
sidra ~ % cat /proc/version_signature
Ubuntu 2.6.28-15.50~lp389040oga3-generic
Audio out now working on a Toshiba NB205 via speaker. I will continue
to test more in the near futur
is not required if you create the kernel headers
>
> --
> Heavy network activity (eg: torrent/nfs file transfers) causes Hard System
> Locks and/or Network Freezes.
> https://bugs.launchpad.net/bugs/147464
> You received this bug notification because you are a direct subscriber
> of
it always
crashes...
On Nov 14, 2007 8:44 AM, hyperair <[EMAIL PROTECTED]> wrote:
> So it's not just NFS transfers eh? At what speeds do your torrent
> transfers usually go, and which torrent client do you use? Also, how
> long before the system locks up?
>
> -emory- wrote
(eg: torrent/nfs file transfers) causes Hard System
> Locks and/or Network Freezes.
> https://bugs.launchpad.net/bugs/147464
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
emory
--
Heavy network activity (eg: torrent/nfs file tran
that is.
On Nov 12, 2007 6:06 PM, effell <[EMAIL PROTECTED]> wrote:
> Since emory asked, I'm experiencing this bug on a system upgraded from
> Feisty.
>
> --
> Heavy network activity (eg: torrent/nfs file transfers) causes Hard System
> Locks and/or Network Freezes.
Just curious, is everyone on a fresh install of gutsy, or are these
problems also happening upgrading from feisty as well? Also, shearn89
and hyperair, to me that sounds like the same issue to me. Did you
downgrade your kernel to get this to work? I'm about five minutes from
installing Feisty back
are we sure it's with the 64 bit version? I'm running 32 bit desktop and
it's doing this... This is the ONLY thing that I've noticed wrong with
this release too... In other news, I just did a fresh install and its'
still messing up. I couldn't test on teh live cd though. Has anyone
tried with the a
ouch...looks like i spoke a bit too soon. All worked well until I loaded
amarok. It could have been a coincidence of course that it started to
crash as soon as that loaded up, I'm not sure. Any luck on anyone else?
I wonder why everyone isnt experiencing this though...
--
Heavy network activity (
AHA! I think I solved the problem. What I think was happening was that gutsy
wasn't using swap correctly. Change swappiness to 10 and it works beautifully
so far!
btw to do so just do
sudo gedit /etc/sysctl.conf
then add the line swappiness=10 to the bottom, if it isn't already there. Can
anyo
24 matches
Mail list logo
