Never mind, what I'm seeing is Bug #537133.
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
I can confirm this is still broken with portmap 6.0.0-1ubuntu2
installed. My workaround is to turn off statd in /etc/default/nfs-common
and add nolock to the root options in fstab. Portmap still tries to
start and I get error messages but the boot eventually succeeds.
--
mountall issues with NFS
I've just installed lucid on a diskless system. It boots from a usb key,
not pxe, but has an nfs root. It hangs in or just after init-bottom,
apparently because statd and portmap both exit immediately after
starting. My "fix" was to disable them both then add "nolock" to the
root mount options in f
Another suggested fix, from Bug #548917, is to run mountall twice from
mountall.conf. Or I suspect you could put your remount in mountall.conf,
just before the "exec mountall," since it's only the root that needs to
be remounted. I'll try this when I get a chance.
--
mountall issues with NFS root
I had to try a number of different things to get it going. It took
several hours. I don't entirely understand the way the host gets its IP
address. The kernel ipaddr=x.x.x.x option doesn't seem to work, it
always uses dhcp. I ended up using a dhcp server with a static IP for
the host, and also conf
I should also add that I am not using the mountall patch. And I'm doing
this on i386, not amd64.
--
mountall issues with NFS root filesystem
https://bugs.launchpad.net/bugs/537133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Kind of unbelievable that this is still unfixed and still marked low
priority. Can we at least have an explanation of what's broken in
plymouth that makes it impossible to apply the suggested fix? I can look
at fixing plymouth if that's the problem.
--
You received this bug notification because y
The vt.handoff kernel param shouldn't be there in the first place. See
my comment above. And I don't see why this would be an uncommon
installation. It's the only way I know of to install a command line
system that's not a server.
--
You received this bug notification because you are a member of
This bug is fixed in the kernel git. I don't know if the fix made it out to apt
yet. The fix is here:
http://lkml.org/lkml/2010/9/24/108
By the way, when the disk died in my x40, I replaced with a CF card on
an adapter. Faster, cheaper, lower power. And since I'm running Ubuntu,
not XP, I don't n
There used to be a working video driver for the Intel 855GM, but since
it actually worked, it was removed from Xorg. You now have three
choices. You can go with the default, which is fbdev, and suffer crashes
every few days. Or you can use the new intel driver, but it doesn't work
either. I'm using
Maybe I'm missing something here. What you have described is certainly a
bug and should be fixed. But why is the nfs root being mounted read-only
to begin with? An on-disk root is mounted read-only so that if it's
dirty fsck can clean it up. But that makes no sense for an nfs root.
--
mountall is
The fstab hack makes sense. I hadn't thought of that.
I wonder what would happen if you used
"nfsroot=10.10.10.254:/nfsroot,rw" as your kernel option, and "rw" in
fstab. Would the root then be initially mounted rw, and the remount
skipped? The doc says you can put nfs options after the comma, does
That's a bit odd. I would expect if you had rw in your kernel options,
and ro in your fstab, that it would do the remount. But in any case I
think the kernel should mount the nfsroot rw unless you give ro in the
kernel options.
I'm going to bring this up on the nfs mailing list (I'm an nfs
develop
I'm still getting this with the 11.11 beta2. Why is this considered
"low" importance? It makes the system unusable and can take a while to
figure out, even for someone who knows what they're doing. It's
especially pernicious in a VirtualBox VM, where ctl-alt-F1 doesn't do
what you expect. Please ra
The real bug here is not so much that grub is asking the kernel to
switch to vt7 when there is no splash. The real bug is that grub is
requesting a vt switch at all. Grub has no business making this request
because it has no way of knowing whether there is anything on vt7.
The way this should work
I found the perfect fix for this bug. I wiped my disk and installed a
different (not Ubuntu) distro. I am much happier now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830
Title:
grub2 still ha
Are you sure it isn't just hanging because of the disk errors?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759469
Title:
Ubuntu hangs when restoring a session in Firefox
--
ubuntu-bugs mailing l
Any progress on this? I'm running kernel 2.6.32.10+drm33.1 (built from
source), with "nomodeset" option, the last kernel that works for me.
I've got a x40 2386BHU. The x41 has similar problems by the way.
--
lucid xorg regression - thinkpad x40 (855GM) freeze at xorg startup
https://bugs.launchpa
Public bug reported:
Binary package hint: firefox
The maverick firefox package 3.6.11+build3+nobinonly-0ubuntu0.10.10.1
depends on the gnome-icon-theme package for the "forward" and "back"
button icons, but this dependency isn't explicit. So if you just install
firefox without also installing gno
Does anyone know if the fix is in 10.10? Do you still have to disable
statd?
--
mountall issues with NFS root filesystem
https://bugs.launchpad.net/bugs/537133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here's how I did it:
Get the source tarball and apply all patches from:
http://www.foolabs.com/xpdf/download.html
apt-get install libfreetype6-dev lesstif2-dev
./configure --with-t1-library=no
--with-freetype2-includes=/usr/include/freetype2
make xpdf
If you do have libpoppler-dev installed you
This is what fixed it for me:
http://lkml.org/lkml/2010/9/24/108
--
855gm and kernel 2.6.35-22.34 mouse cursor invisible
https://bugs.launchpad.net/bugs/660380
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Me too. Thinkpad x40, Intel 82852/855GM graphics. Dragging the scroll
bar causes the same long pause, where it used to just immediately scroll
the window, so it does look like it's re-rendering for some reason. As a
workaround, grab /usr/bin/xpdf.bin (not /usr/bin/xpdf, which is just a
wrapper) fro
23 matches
Mail list logo
