I had suggested a while back that the problem lies not within the actual
crdkit (or whatever flavor you decide to use) but that the problem lies
in the kernel level interactions. If you think back to when the original
bug was posted it was around time that there was a significant shift in
the handl
I've been using a work around here for a few weeks to test and it seems
to be working. BONUS - no symlinks and you can try it without any
permanent changes.
1. When Grub loads hit the key to edit the commands "e", this should bring up a
series of lines "root", "kernel", and "initrd".
2. You want
Well two things:
1. Has this been tested under Ubuntu 9.4 Jaunty? i.e is it fixed in the
Ubuntu 2.6.28 kernels?
2. I can confirm that in Kernel 2.6.29 from kernel.org (stable 64-bit)
the drive (2116:0320) works. The .deb's from kernel.org are a straight
forward install.
--
USB Hard Drive Not
*** This bug is a duplicate of bug 149076 ***
https://bugs.launchpad.net/bugs/149076
** This bug has been marked a duplicate of bug 149076
I can't write a cd
--
(Gutsy) K3b won't burn - wodim error
https://bugs.launchpad.net/bugs/178808
You received this bug notification because you are a
I hope to see some progress on this issue soon as it seems to be a
fairly common issue. There a lot of duplicate bugs out there describing
basically the same thing "/usr/bin/wodim: Operation not permitted.
Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/scd0'"
perhaps the description sho
** Summary changed:
- I can't write a cd
+ [SOLVED] I can't write a cd
** Description changed:
+ If you see any of the symptoms of the various outputs in the comments
+ the solution is as follows:
+ "You are not using cdrecord but a defective fork called "wodim".
+
+ wodim is a dead fork fro
