Martin, yeah you're right that it's read-only, but it's trying to update
the initrd file... which lives outside the persistent file. Thus the
bug (I think...)
I've made a bunch of installation attempts, but it always fails. Your
suggestion to just disable installation and mark it unsupported sou
For what it matters, the .29 version of nvidia-current installs
flawlessly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685017
Title:
Jockey should warn on insufficient disk space in LiveCD environ
Hrm, unfortunately even using all the workarounds I still couldn't get
fglrx up. Here's what I tried:
[Workaround]
1. Download an ISO (I tested against the alpha-1 iso image)
2. Generate a USB drive using usb-creator. Do not reserve all the remaining
space. Leave some amount for system updat
** Description changed:
[Problem]
This is a common issue encountered by users trying to install -nvidia on
systems with insufficient space to install the driver. This can happen for
instance if the user is booting from a usb disk.
It is further noticed that in many cases the system may
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
** Changed in: jockey (Ubuntu Natty)
Importance: Critical => High
** Changed in: jockey (Ubuntu Natty)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: nvidia-graphics-drivers (Ubuntu Natty)
Importance: Critical => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685017
Title:
Jockey should warn on insufficient disk space in
I've reproduced this myself on a 4G usb key, setting the reserved space
to max (3.1G), as I've outlined in the description.
Comment #7 on bug #562312 does indeed describe what is happening. I
think there's a whole class of issues that can occur, which produce a
range of different (and confusing)
@Pedro, I believe that casper can only handle a 4G filesystem max (FAT
limitation?) so even though it is 8Gb total the live environment can't
address the upper 5-8G. So since your storage was set so large, there
wasn't space to write the kernel.
Or something like that. Try reducing the size of y
@Andreas, mount the usb disk in a different working linux installation,
and look at how much free disk space there is on the usb drive itself.
My guess is maybe it ran out of space while trying to create
vmlinuz-2.6.37-7-generic. What % of the free space did you allocate to
reserve for documents a
** Description changed:
[Problem]
This is a common issue encountered by users trying to install -nvidia on
systems with insufficient space to install the driver. This can happen for
instance if the user is booting from a usb disk.
It is further noticed that in many cases the system may
By the way, if it helps I was running a live USB session, from a disk I
made by following the Jono Bacon guide
(http://www.jonobacon.org/2010/11/30/testing-natty-and-unity-safely-
with-a-usb-stick/), with 4Gb of storage for documents and stuff - the
drive has 8Gb total.
--
You received this bug n
Sorry for the duplicate bug #688116. It was submitted semi-automatically
by the bug report application. :/
Cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685017
Title:
Jockey should warn on
/vmlinuz is a broken link:
lrwxrwxrwx 1 root root 29 2010-12-03 08:12 vmlinuz ->
boot/vmlinuz-2.6.37-7-generic
r...@ubuntu:~# ll /boot/
total 20569
drwxr-xr-x 4 root root 80 2010-12-08 13:16 ./
drwxr-xr-x 33 root root 320 2010-12-08 13:09 ../
-rw-r--r-- 1 root root 714835 2010-
I get this when trying to install nvidia-current with apt-get:
r...@ubuntu:~# apt-get install nvidia-current
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
dkms fakeroot nvidia-settings patch screen-r
Yeah I can reproduce this by creating a liveusb with the persistent
storage space slider maxed out, it requires space on the fat32 file
system to manipulate the initramfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Comment #7 on bug #562312 sounds quite pertinent. Please review and see
if that describes the procedure you used to do your install?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685017
Title:
Jock
The way we determined it as an out of space issue, is Sarvatt reproduced
your problem on a USB stick by manually installing nvidia, and got the
error message that way:
Setting up initramfs-tools (0.98.1ubuntu7) ...
update-initramfs: deferring update (trigger activated)
lzma: Encoder error: -214
Where exactly should there be sufficient disk space? The df output below shows
the free space right after I got the error:
ubu...@ubuntu:~$ df -h
FilesystemSize Used Avail Use% Mounted on
aufs 1006M 213M 794M 22% /
none 1000M 352K 1000M 1% /dev
/d
Btw, note that while insufficient disk space can cause the "post-
installation script returned error" error, there may well be other
issues that lead to this same error message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I'm adding a Jockey task because I think this needs fixed via better
installation space checking during installation by jockey.
But I'm leaving the -nvidia task open for now, for tracking/duping
purposes. I don't *think* there is anything we can change in -nvidia to
correct the bug, but until it'
This issue has existed for some time, however in natty with Unity now
being the default interface users are shown a warning that they lack 3D.
This motivates them to try installing a binary driver via jockey.
Especially if they're just testing to kick the tires, they may attempt
to do so on media w
** Description changed:
+ [Problem]
+ This is a common issue encountered by users trying to install -nvidia on
systems with insufficient space to install the driver. This can happen for
instance if the user is booting from a usb disk.
+
+ It is further noticed that in many cases the system may
Wait, you mean the slider in startup-disk-creator where you can choose
how much space you want for settings and documents, right? Or something
else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685017
In discussing this with Sarvatt, it sounds like while this has been a
long standing issue, the unity focus for natty makes this issue
especially important now since.
I hope you don't mind that we're going to use this bug report as a
master bug against jockey for adding checks for this particular
w
25 matches
Mail list logo
