Looks like it's invoking 'ntfsclone' with the command line options that
work for 'partclone.ntfs' - which don't appear compatible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571537
Title:
FWIW - observing a similar problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571537
Title:
ntfsclone not compatible with Clonezilla
To manage notifications about this bug go to:
The latest in the 2.3.x series I got from the ralink website didn't need
any patching/modifications .. it just compiled straight for me, produced
a working module .. no problem so far, no more connection drops. I am
not using Ubuntu though, I am using Debian, but I don't think the kernel
images
2.3.0.0 version of the driver released in Jan 2010 compiles fine against
the latest 2.6.32 and the problems I had seem to have disappeared.
--
module rt2860sta ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
https://bugs.launchpad.net/bugs/376577
You received this bug notification
Try the attached patch. Comes from
http://ubuntuforums.org/showthread.php?t=1285828 with my own hacking for
2.6.32 since it was originally for 2.6.31 .. seems to work fine so far.
--
module rt2860sta ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
Try the attached patch. Comes from
http://ubuntuforums.org/showthread.php?t=1285828 with my own hacking for
2.6.32 since it was originally for 2.6.31 .. seems to work fine so far.
** Attachment added: RT2860-2.6.32.patch
http://launchpadlibrarian.net/38339796/RT2860-2.6.32.patch
--
module
Unfortunately I get the same connection drops, although I am no longer
seeing the 'RTMPCancelTimer failed' lines in the log anymore
--
module rt2860sta ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
https://bugs.launchpad.net/bugs/376577
You received this bug notification because
This in no way ubuntu specific. It looks P5K specific though. I run
debian with my own 2.6.27 kernels compiled from source and I'm having
those problems too. The link to the kernel bug has been posted here in
the past, but here it is again:
http://bugzilla.kernel.org/show_bug.cgi?id=9143
--
