Alright, I've sufficiently reproduced the issue and its workarounds now that I'm comfortable closing the -nvidia part of this bug. I'll update the description with steps I used to work around it.
I reckon there's 3 separate bugs at play here:
1. usb-creator allows people to specify too large a proportion of usb drive space to the persistent file, leaving an insufficient amount to do initrd updates (bug #562312).
2. jockey does not detect the limited system space issue (this bug)
3. casper is not creating the /vmlinuz symlink correctly, which leads to kernel updates failing (bug #557023)
These all need fixed, but none are -nvidia or -fglrx issues specifically, so I'm closing out the -nvidia task for this bug.
Alright, I've sufficiently reproduced the issue and its workarounds now that I'm comfortable closing the -nvidia part of this bug. I'll update the description with steps I used to work around it.
I reckon there's 3 separate bugs at play here:
1. usb-creator allows people to specify too large a proportion of usb drive space to the persistent file, leaving an insufficient amount to do initrd updates (bug #562312).
2. jockey does not detect the limited system space issue (this bug)
3. casper is not creating the /vmlinuz symlink correctly, which leads to kernel updates failing (bug #557023)
These all need fixed, but none are -nvidia or -fglrx issues specifically, so I'm closing out the -nvidia task for this bug.