It depends what you mean by adding apparmor=0 at the bottom, you need to add it to the line containing the linux kernel command options, it will look something like this
linux /boot/vmlinuz-3.2.0-6-generic root=UUID=b6d5798b-bfb5-4889-9e2d-92395a82bf18 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
you add apparmor=0 to the end of the line, eg.
linux /boot/vmlinuz-3.2.0-6-generic root=UUID=b6d5798b-bfb5-4889-9e2d-92395a82bf18 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 apparmor=0
and then boot.
As for trying Ubuntu on USB, yes this can help track down where the problem is, so it is worth trying. In fact it is worth trying a clean 11.10 too, as the problem may be in some difference caused by upgrading.
It depends what you mean by adding apparmor=0 at the bottom, you need to add it to the line containing the linux kernel command options, it will look something like this
linux /boot/vmlinuz- 3.2.0-6- generic root=UUID= b6d5798b- bfb5-4889- 9e2d-92395a82bf 18 ro crashkernel= 384M-2G: 64M,2G- :128M quiet splash vt.handoff=7
you add apparmor=0 to the end of the line, eg. 3.2.0-6- generic root=UUID= b6d5798b- bfb5-4889- 9e2d-92395a82bf 18 ro crashkernel= 384M-2G: 64M,2G- :128M quiet splash vt.handoff=7 apparmor=0
linux /boot/vmlinuz-
and then boot.
As for trying Ubuntu on USB, yes this can help track down where the problem is, so it is worth trying. In fact it is worth trying a clean 11.10 too, as the problem may be in some difference caused by upgrading.