Ubuntu 7.10 is Gutsy, not Hardy and Gutsy isn't supported anymore for as
far as I know.
It is also not the fault of the graphics card but a combination of all
sorts of issues on quite a few sides, I did some kind of workaround to
fix this but I don't remember it (I'm on hardy now and planning
On Fri, Mar 28, 2008 at 10:00:11PM -, Valeryan_24 wrote:
I still have the same problem at boot, but the exact message is :
Undefined video mode number: 312
Please open a new bug report for the problem you're seeing. The
original libx86 missing-opcodes bug (this one) is already fixed.
On Sat, Mar 22, 2008 at 07:05:33PM -, Jeremy LaCroix wrote:
I also verified that I do have the package that you mentioned installed.
You may need to run sudo update-initramfs -u to see the changes happen
during boot-time.
As for Gutsy, this may not be valid for a Stable Release Update.
I ran sudo update-initramfs -u and it's fixed now. :)
Kees Cook wrote:
On Sat, Mar 22, 2008 at 07:05:33PM -, Jeremy LaCroix wrote:
I also verified that I do have the package that you mentioned installed.
You may need to run sudo update-initramfs -u to see the changes happen
On my side nothing has changed yet.
On Wed, Mar 19, 2008 at 5:27 AM, Steve Langasek
[EMAIL PROTECTED] wrote:
There was a regression introduced in the initramfs-tools package
regarding vesafb introduced some time in the past week, this should be
fixed in initramfs-tools 0.85eubuntu34. You
Just want to change my statement earlier about the vesafb workaround, as of
the latest kernel my ttys are all blank except for the blinking cursor.
--
[amd64 + nvidia 8xxx] usplash shows nothing
https://bugs.launchpad.net/bugs/147623
You received this bug notification because you are a member of
No problems here, i can switch between xorg running nvidia binary driver,
and my terminals without problem. Never had any problemswith usplash booting
up/shutting down either. The only thing that i havent tried would be
suspend, as this is on a big honking workstation rather than a laptop.
--
This problem still needs fixing in Gutsy also.
Pat_Primate wrote:
I confirmed Roger's observation, this bug is still present in Hardy
Alpha 5. With the number of 64bit nvidia 8xxx users out there we really
should fix this before the full release of Hardy, because although there
are
I completely agree, this is a massive bug, due to not knowing what's going
on when the system boots. When the machine needs to fsck, people are just
going to assume nothing is happening and cut off the power to the PC in the
middle of the check. That can be dangerous.
On Feb 6, 2008 12:37 PM,
Even worse, in some cases like mine X doesnt even come up due this problem
(which i assume is a clash between the dodgy fb driver and the nv driver),
the only reason i ever got around it was that i knew enough to try a
nosplash boot.
--
[amd64 + nvidia 8xxx] usplash shows nothing
10 matches
Mail list logo
