Ubuntu
xserver-xorg-video-nv package

[edgy] livecd (amd64) won't boot into graphical interface

Bug #58821 reported by anonym
4
Affects Status Importance Assigned to Milestone
xserver-xorg-video-nv (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: bootcd

I tried the edgy knot2 live cd, but it will not boot. At the point where you should see the graphical interface/gnome, my display just gives green vertical lines. (and its blinking too :-( )

Safe graphics mode gave the same problem.

My specs:
processor: AMD64 x2 3800+
mainboard: ASUS A8N-e
videocard: NVidea Geforce 6800 GS Pci-e
ram: 1GB

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Can you please follow the instructions at https://help.ubuntu.com/community/DebuggingXAutoconfiguration . After getting your display to work, can you please make sure you attach all the information listed in step 5? Thanks in advance.

Changed in xorg-server:
importance: Untriaged → Medium
status: Unconfirmed → Needs Info
Revision history for this message
OrkanSpec (orkanspec) wrote :

I confirm the problem with "safe graphics mode" in 6.10 beta amd64.
 I have an NVidia GF 6600 AGP graphics card, which does not work with "nv" driver. It works well with proprietary "nvidia" driver and "vesa".
 When booting 6.10 beta there is no difference to me between standard boot and "Start Kubuntu in safe graphics mode" - both the ways result in corrupted display (vertical lines). This "safe graphics mode" worked well in 6.06.

PS. after switching to a console I have still vertical lines and I am not able to do anything.

Revision history for this message
Mark Junker (mjscod) wrote :

I had a similar problem. After seeing some kernel messages, the monitor was turned off by the gfx card/driver and I was unable to install Ubuntu. As a "workaround" I used the "Server" version of Ubuntu and installed the X stuff later.

Revision history for this message
DominikBodi (dominik-bodi) wrote :

"safe graphics mode not using vesa" has been reported as #59618.
#59618 happens with other non-nvidia chipsets, as well.
As for the nv driver not working, please try to follow the instructions at
https://help.ubuntu.com/community/DebuggingXAutoconfiguration in order to provide more diagnostic data.

DominikBodi (dominik-bodi)
Changed in xserver-xorg-video-nv:
assignee: nobody → ubuntu-x-swat
Revision history for this message
Shane (duairc) wrote :

Yeah, I'm getting this too with the amd64 Live CD with Feisty aswell.

I have the same motherboard and graphics as the original poster.

Everything's fine when I edit xorg.conf and use the vesa driver.

Revision history for this message
DominikBodi (dominik-bodi) wrote :

Could you re-test this with gutsy-beta please?

Revision history for this message
Bryce Harrington (bryce) wrote :

Does this issue still occur with Hardy? If not, can someone who is experiencing this issue please attach their /var/log/Xorg.0.log, /etc/X11/xorg.conf, and the output of lscpi -vvnn?

Changed in xserver-xorg-video-nv:
assignee: ubuntu-x-swat → nobody
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

No reply from the reporter, closing the bug.

Changed in xserver-xorg-video-nv:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.