Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Natty Narwhal. It would help us greatly if you
could test with it so we can
Please check Bug #706783 - BIOS SETTING for VGA SHARE MEMORY SIZE was
set to 32M. When changed to 64M Ubuntu Desktop Edition booted normally.
Athlon XP on Biostar Mobo M7VIG 400, w/1GB DDR2 RAM. On board video -
no PCI or AGP video card.
--
You received this bug notification because you are a
** Tags added: via-agp
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-savage in ubuntu.
https://bugs.launchpad.net/bugs/584674
Title:
Lucid fresh install doesn't go beyond login. Possible Savage driver
problem.
I'm now convinced that my problem is a different bug, as it is not
related to the SAVAGE driver, so I've created a bugtracker entry for it:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/669002
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
I've just upgraded from 10.04 to 10.10; now I'm experiencing a problem
which is, superficially at least, very similar. I'm using gdm however.
Upon entering the correct password at gdm, the screen blinks and the gdm
login screen is built up again. Another similarity is that this is also
with the
** Changed in: xserver-xorg-video-savage (Ubuntu)
Status: New = Confirmed
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Tormod Volden wrote:
There are troubleshooting documents on the wiki, for example
https://wiki.ubuntu.com/X/NonGraphicalBoot
YAY! A clue! Thank you!
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this
I wish I knew how to be as helpful as Invader Zim. I am having the same
issue. Bug 567029. How do you run anything at all, much less apport-
collect 584674 when the computer is looped at login?
quote//
1. login in console
2. as root, service kdm stop
3. rmmod savage
4. modprobe savagefb
There are troubleshooting documents on the wiki, for example
https://wiki.ubuntu.com/X/NonGraphicalBoot
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this bug notification because you are a member of Ubuntu-X,
Attached the Xorg Log when I use the vesa driver in xorg.conf (computer
freezes in a black screen and stops responding).
** Attachment added: Xorg.0.log.vesa.txt
http://launchpadlibrarian.net/49315460/Xorg.0.log.vesa.txt
--
Lucid fresh install doesn't go beyond login. Possible Savage driver
Thanks for your report. Please reproduce the problem and run apport-
collect 584674.
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: kdebase-workspace
Description:Ubuntu 10.04 LTS
Release:10.04
xorg:
Instalado: 1:7.5+5ubuntu1
kdm:
Instalado: 4:4.4.2-0ubuntu14
After fresh install from
Please attach the Xorg.0.log with the fatal error.
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-savage in
As I said before, the fatal error doesn't show up in the log anymore.
There is no fatal error anymore.
I'm gonna attach the only error that show up in messages. And still,
that error only occurs when, after boot up, I login at the console, and
modprobe savagefb.
So there are 2 modules for
Ok, the Fatal Error showed up again, I'm attaching it.
However, more issues have come up.
First, xdm login doesn't work anymore. It returns to xdm login sometime
after pressing enter.
Then, when I tried to boot in recovery mode to copy the Xorg log before
it was overwritten, the curses dialog
Normally it should not be necessary to use the savagefb module. You have
all the latest updates, right? There were some savage updates that came
after the (CD) release. Can you try removing the plymouth package to see
if it helps?
--
Lucid fresh install doesn't go beyond login. Possible Savage
Well, I didn't know exactly which plymouth package, so I tried removing
the package plymouth, but it breaks everything. mountall depends on it.
So I removed all plymouth that I could, logos, x11, etc.
The console problem did stop, but the kdm/xdm login problem persists.
--
Lucid fresh install
Got xdm login working again, by putting savagefb in /etc/modules, and
blacklisting savage.
KDM still doesn't work.
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this bug notification because you are a member
** Package changed: kdebase-workspace (Ubuntu) = xserver-xorg-video-
savage (Ubuntu)
** Tags added: kubuntu
--
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this bug notification because you are a member of
Update on the issue:
Now startx also works with savage, I don't need to load savagefb
anymore.
So I installed xdm, and changed from kdm to xdm, and it worked.
So it's obviously an issue with KDM.
Also to note is the fact that the fatal error that sometimes appeared in
Xorg.0.log doesn't show
20 matches
Mail list logo
