[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Maverick 10.10 live-CD login failure, ttyN screens don't work, on Averatec 3280 running Lucid

I was able to get the 2011-07-20 build of 10.04.3 to boot, using roughly the same tricks that I used for another system described in bug#707755, on a Compaq system. For the live-CD boot line, I hit F6 and selected 'nomode' set. For the rest of the command line, I removed 'quiet' and 'splash' and a

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Maverick 10.10 live-CD login failure, ttyN screens don't work, on Averatec 3280 running Lucid

I'm not sure that the 'nomode' boot line setting was necessary for this Openchrome display - I had used that (see previous comment) for a system with an nVidia display. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Maverick 10.10 live-CD login failure, ttyN screens don't work, on Averatec 3280 running Lucid

At any rate, even if the repaired driver isn't added to the .3 or .4 release of 10.04 LTS, this provides a workaround to allow someone to install this LTS version in a system like this. It's a little beyond what a newbie can be expected to do, though! -- You received this bug notification because

[Ubuntu-x-swat] [Bug 707755] Re: Xorg usually won't start on Compaq system with nVidia Corporation C51 [GeForce 6150 LE] and nVidia chipset

I have just installed 64-bit 11.04 Natty on this system, and will not make any further changes until the next LTS release comes out, assuming that release is acceptable. This is a system I am relying on, so I really can't afford to experiment any more on it. Note that I was unable to run the syste

[Ubuntu-x-swat] [Bug 707755] Re: Xorg usually won't start on Compaq system with nVidia Corporation C51 [GeForce 6150 LE] and nVidia chipset

Also, I don't think I was able to get the system going as far as described in #13 - the system simply could not identify the monitor. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bu

[Ubuntu-x-swat] [Bug 707755] Re: Xorg usually won't start on Compaq system with nVidia Corporation C51 [GeForce 6150 LE] and nVidia chipset

The machine won't boot from a USB stick. It does have a network boot option, but I don't know how to utilize that. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/707755 Title:

[Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

Aeb1barfo - so far the fixes that appear in 11.04 "natty" haven't been backported to 10.04 LTS - I think there is one more point release of the LTS, but don't know if this has enough priority for anyone to actually fix it. For now, post-installation repairs like installing an xorg.conf file may be

[Ubuntu-x-swat] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately

This bug just reappeared in xubuntu 11.10 on the same Averatec laptop, when I select the AntSpotlight screensaver. As suggested in #31, I'll file this as a new bug, with reference to this one. Here's the latest system information. Ubuntu version and kernel version DISTRIB_ID=Ubuntu DISTRIB_RELEAS

[Ubuntu-x-swat] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately

** Description changed: - Note: this bug just reappeared in Xubuntu 11.10. I'll file this as a new - bug. + Note: this bug just reappeared in Xubuntu 11.10. I'll filed this as a + new bug #871471. Binary package hint: xscreensaver Selecting AntSpotlight in either xscreensaver or Gnome Sc

[Ubuntu-x-swat] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately

** Description changed: - Note: this bug just reappeared in Xubuntu 11.10. I'll filed this as a - new bug #871471. + Note: this bug just reappeared in Xubuntu 11.10. I filed this as a new + bug #871471. Binary package hint: xscreensaver Selecting AntSpotlight in either xscreensaver or Gn

[Ubuntu-x-swat] [Bug 871471] Re: AntSpotlight screensaver causes xbuntu 11.10 beta to lock up on Averatec 3280

For comparison, I just booted an 11.04 'natty' live CD and tried the AntSpotlight screensaver on that. The same thing happens - the system locks up a few seconds after the ant rotates around 60 degrees. I then installed apt-show-versions to see what versions of xscreensaver-gl and the openchrome di

[Ubuntu-x-swat] [Bug 747069] Re: [natty beta-1] Screen flashes on and of every few seconds with nouveau driver

This computer is now running 64-bit xubuntu 11.10: Ubuntu version and kernel version DISTRIB_ID=Ubuntu DISTRIB_RELEASE=11.10 DISTRIB_CODENAME=oneiric DISTRIB_DESCRIPTION="Ubuntu 11.10" Linux compaq 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux model na

[Ubuntu-x-swat] [Bug 871471] Re: AntSpotlight screensaver causes xbuntu 11.10 beta to lock up on Averatec 3280

I will recheck this in the next 24 hours. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/871471 Title: AntSpotlight screensaver causes xbuntu 11.10 beta to lock up on

[Ubuntu-x-swat] [Bug 871471] Re: AntSpotlight screensaver causes xbuntu 11.10 beta to lock up on Averatec 3280

This problem is definitely still happening on this Averatec laptop. I reinstalled xscreensaver-gl, version 5.14-1ubuntu1, carefully set the delay for the screensaver to 10 minutes, and selected AntSpotlite. Within a few minutes the system completely locked up. I had to shut the system down with the

[Ubuntu-x-swat] [Bug 946116] Re: lightdm fails to bring up X display automatically after boot

Apparently this problem is already known: http://ubuntuforums.org/showthread.php?t=1613132 Since I'm able to boot to a shell, what I just did was to add nomodeset to /etc/default/grub and run update-grub, as described on the ubuntuforums page above. So now the altered line in /etc/default/grub lo

[Ubuntu-x-swat] [Bug 946116] Re: lightdm fails to bring up X display automatically after boot

#11 is a good workaround, but not really a fix to the nouveau driver bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/946116 Title: lightdm fails to bring up X display a

[Ubuntu-x-swat] [Bug 871471] Re: AntSpotlight screensaver causes xbuntu 11.10 beta to lock up on Averatec 3280

This situation has not changed in the past 60 days - the bug still occurs in the released version. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/871471 Title: AntSpotli

[Ubuntu-x-swat] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately

Here are the modules which are loaded: # lsmod Module Size Used by via45249 2 drm 192194 3 via bnep 17923 2 rfcomm 38408 0 bluetooth 148839 10 bnep,rfcomm parport_pc 32114 0

[Ubuntu-x-swat] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately

I now have Linux Mint 12 installed, and the same problem occurs. Ubuntu version and kernel version DISTRIB_ID=LinuxMint DISTRIB_RELEASE=12 DISTRIB_CODENAME=lisa DISTRIB_DESCRIPTION="Linux Mint 12 Lisa" Linux cupid 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 15:59:53 UTC 2012 i686 athlon i386 GNU/L

[Ubuntu-x-swat] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately

Actully, I meant to attach Xorg.0.log --- here it is ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/455954/+attachment/2712424/+files/xorg.0.log.tgz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa

[Ubuntu-x-swat] [Bug 946116] Re: lightdm fails to bring up X display automatically after boot

Thanks, Robert, for reviewing the lightdm.log output. I´m sure you are right - this is mainly an xorg issue. I´ve filed earlier bug reports on this hardware - see in particular Bug #707755 against development versions of Natty 11.04. :´ Ubuntu version and kernel version DISTRIB_ID=Ubuntu DISTRI

[Ubuntu-x-swat] [Bug 946116] Re: lightdm fails to bring up X display automatically after boot

After filing comment #7, I rebooted the compaq system. As I was awaiting the system to complete booting, after the Grub2 screen closed - I was alternately hitting Alt F1 and Alt F2 and possibly Enter - somethow this time the lightdm login greeter appeared and I was able to log in. I'll attach the l

[Ubuntu-x-swat] [Bug 946116] Re: lightdm fails to bring up X display automatically after boot

I assume there is some sort of race condition in system startup. I am also attaching Xorg.0.log ** Attachment added: "Xorg.0.log after above good startup." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/946116/+attachment/2820143/+files/Xorg.0.log.good -- You received this bug notifica

[Ubuntu-x-swat] [Bug 186103] apport-collect data

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 Architecture: i386 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 ProcVersion:

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/27398494/Dependencies.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/18

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/27398496/LsHal.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/186103 You recei

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/27398497/LsMod.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/186103 You recei

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/27398499/XorgConf.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/186103 You

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/27398498/LsPci.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/186103 You recei

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/27398500/XorgLog.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/186103 You r

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/27398509/XorgLogOld.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/186103

[Ubuntu-x-swat] [Bug 186103]

*** This bug is a duplicate of bug 353208 *** https://bugs.launchpad.net/bugs/353208 ** Attachment added: "system.txt" http://launchpadlibrarian.net/27398510/system.txt -- Gutsy alternate installer fails to recognize display on Averatec 3280 https://bugs.launchpad.net/bugs/186103 You rec

Re: [Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

For the Averatec laptop, it's 1024x768. When fed at a higher resolution, the image is cropped to 1024x768. On Wed, Jun 17, 2009 at 5:12 AM, Bartosz wrote: > What is corect resolution of your monitor? > > -- > [K8M800] Panel on K8M800 is not supported (Averatec 3280) > https://bugs.launchpad.net

Re: [Ubuntu-x-swat] [Bug 271138] Re: mouse and keyboard unresponsive when gdm first runs

I have not, either, so I assume it is no longer a bug. On Fri, Jul 24, 2009 at 1:52 PM, Martin Pool wrote: > I have not seen this on either of my machines for months, so it > probably has been fixed. > > > -- > Martin > > -- > mouse and keyboard unresponsive when gdm f

[Ubuntu-x-swat] [Bug 411164] [NEW] Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

Public bug reported: Binary package hint: xserver-xorg-video-ati I am able to make video work on this system running the 6.06 LTS live/desktop CD, manually selecting the screen resolution. But I am unable to get Xorg to work under later releases. In this case, I installed 8.10 using the alternat

[Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

Result of lspci -vv ** Attachment added: "lspci -vv output" http://launchpadlibrarian.net/30089592/lspci.txt -- Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP https://bugs.launchpad.net/bugs/411164 You received this bug notification because you are a member of Ubuntu-X, whic

[Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

lsmod output ** Attachment added: "lsmod output" http://launchpadlibrarian.net/30089614/lsmod.txt -- Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP https://bugs.launchpad.net/bugs/411164 You received this bug notification because you are a member of Ubuntu-X, which is subscr

[Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

xorg.conf file based on one generated running 6.06 LTS ** Attachment added: "xorg.conf" http://launchpadlibrarian.net/30089711/xorg.conf -- Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP https://bugs.launchpad.net/bugs/411164 You received this bug notification because you a

[Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

Xorg.0.log - from trying to run with vesa driver. ** Attachment added: "Xorg.0.log - running vesa" http://launchpadlibrarian.net/30089776/Xorg.0.log -- Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP https://bugs.launchpad.net/bugs/411164 You received this bug notification be

[Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

xorg.conf.new - generated on FreeBSD 7.1 using command Xorg -configure on the same system. Running the same command on Ubuntu crashed. ** Attachment added: "xorg.conf.new from FreeBSD" http://launchpadlibrarian.net/30089746/xorg.conf.new -- Xorg won't start on PC with ATI Technologies In

[Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

Xorg.0.log - trying to use ati driver ** Attachment added: "Xorg.0.log - running ati driver" http://launchpadlibrarian.net/30092974/Xorg.0.log2 -- Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP https://bugs.launchpad.net/bugs/411164 You received this bug notification because

Re: [Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

I have just installed Ubuntu 7.10 on this system. On starting the installer, I specified the screen resolution as 1024x768x24. The installation went well, though this system is slow by today's standards. Now I am doing an online upgrade to 8.04 LTS. I'm not sure what driver was selected. In the mo

Re: [Ubuntu-x-swat] [Bug 411164] Re: Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP

In my case, the upgrade to 8.04 after the installation of 7.10 went well. The display driver selected in xorg.conf is 'vesa'. On Wed, Aug 12, 2009 at 12:28 AM, Peter Belew wrote: > I have just installed Ubuntu 7.10 on this system. On starting the > installer, I specified the scre

[Ubuntu-x-swat] [Bug 217004] Re: install failure (regression) with ProSavageDDR graphics chipset

I recently did a new installation on the gBox computer mentioned above. It now runs hardy 8.04.3 LTS with a vesa driver - I installed it by installing first 6.06.1 LTS (in safe mode with screen resolution specified explicitly) then upgrading. This system works, but crashes when switching to a text

Re: [Ubuntu-x-swat] [Bug 217004] Re: install failure (regression) with ProSavageDDR graphics chipset

Thanks, Tormod - I just downloaded xserver-xorg-video- savage_2.3.1~git20090813.36ab23a9-0ubuntu0tormod~hardy_i386.deb to my laptop ... is that the right one? I'll install it once I get back to that system. On Fri, Aug 14, 2009 at 11:37 AM, Tormod Volden wrote: > Peter, I updated the Hardy xs

Re: [Ubuntu-x-swat] [Bug 217004] Re: install failure (regression) with ProSavageDDR graphics chipset

and back, reboot, etc properly. I'll submit that as a bug against the vesa driver. (Actually I didn't try the savage driver that comes with 8.04 LTS - I understand the fixes didn't get into a release before Jaunty). On Fri, Aug 14, 2009 at 2:16 PM, Peter Belew wrote: > Thanks, T

Re: [Ubuntu-x-swat] [Bug 217004] Re: install failure (regression) with ProSavageDDR graphics chipset

the system locks up on exiting from Gnome. I haven't tried the savage driver on that system, if it has one. On Fri, Aug 14, 2009 at 6:22 PM, Peter Belew wrote: > Tormod - installing your savage driver solved the problem. After > installing it, I disabled Xorg running at runlevel 2 by renaming

[Ubuntu-x-swat] [Bug 414330] [NEW] When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

Public bug reported: Binary package hint: xserver-xorg-video-vesa System with S3 ProSavage8 running 8.04.3 LTS crashes on logout The 8.04.3 LTS system runs Ok, but crashes when switching to a text console, when logging out (to change users), or when shutting down. (See below) This is the same s

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

** Attachment added: "lspci --vv output" http://launchpadlibrarian.net/30381465/lspci.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/30381466/Dependencies.txt -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving gr

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

** Attachment added: "lsmod output" http://launchpadlibrarian.net/30381507/lsmod.txt -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330 You received this bug notification because you are a m

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

** Attachment added: "/var/log/kern.log" http://launchpadlibrarian.net/30381742/kern.log -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330 You received this bug notification because you are

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

** Attachment added: "xorg.conf - using vesa driver" http://launchpadlibrarian.net/30381801/xorg.conf -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330 You received this bug notification be

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

** Attachment added: "/var/log/messages" http://launchpadlibrarian.net/30381619/messages -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330 You received this bug notification because you are

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

Information about file system usage ** Attachment added: "fdisk and df output" http://launchpadlibrarian.net/30381714/fdisk.txt -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330 You receive

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/30381853/Xorg.0.log -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330 You received this bug notification because you are a me

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

>From comments to bug 217004: >From Tormod Volden: Peter, I updated the Hardy xserver-xorg-video-savage package on https://launchpad.net/~tormodvolden/+archive/ppa to the latest version, so you can try it (I haven't tested it myself). >From me to Tormod Volden: Tormod - installing your savage dri

Re: [Ubuntu-x-swat] [Bug 217004] Re: install failure (regression) with ProSavageDDR graphics chipset

I finally submitted this problem with the vesa driver as bug 414330 half an hour ago, using the ubuntu-bug program. On Sat, Aug 15, 2009 at 10:20 PM, Peter Belew wrote: > I've been unable to report the bug on the vesa driver - Launchpad > won't let me report any new bugs! > &

Re: [Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

I'm downloading the Karmic alpha 4 ISO right now. Also I downloaded and installed the new vesa driver - r...@billy:/home/peter/crash# dpkg -i xserver-xorg-video-vesa_2.2.1-1ubuntu1~hardy_i386.deb (Reading database ... 112177 files and directories currently installed.) Preparing to replace xserver

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

I just booted the Karmic CD with no special settings, and it came up with the Savage driver running at 800x600. I've enclosed the I'll try the safe-mode "text" boot next ... ** Attachment added: "Xorg.0.log - running savage driver" http://launchpadlibrarian.net/30397835/Xorg.0.log -- When u

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

When I put 'text' in the command line (after selecting safe mode with the menu) I eventually get a login prompt. How do I log in at that point? -- When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode https://bugs.launchpad.net/bugs/414330

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

I booted the Karmic alpha 4 CD in safe mode, and X came up eventually in 800x600 resolution, apparently using the savage driver, after trying vesa first. The log is interesting ... a lot of tests resulted in a useable mode selection. I would certainly appreciate the revival of the old boot-time sc

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

Actually, I was able to insert the xorg.conf file while running from the CD. I mounted the disk partition with /etc/X11 on it, and copied xorg.conf into the live CD's /etc/X11, switched to a text console, and restarted X with 'service gdm restart'. The Gnome screen came up with half a dozen possibl

[Ubuntu-x-swat] [Bug 414330] Re: When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266] crashes when leaving graphics mode

Here's xrandr.log In this case, I renamed the xorg.conf file to xorg0.log, to disable it, switched to a text console, shut down X with 'service gdm stop', and ran the command xinit -e 'sh -c "xrandr --verbose > xrandr.log" ' ** Attachment added: "xrandr.log after performing this procedure."

[Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

Karmic Koala 9.10 live CD: I have just tried the 9.10 Karmic alpha 4 live/desktop cd on this Averatec laptop. As before, it boots properly and starts the X server, but with too high a screen resolution. The maximum resolution of the screen is 1024x768. It is necessary to put an xorg.conf file int

[Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

I created a minimal xorg.conf file (attached), and placed it in the livecd's /etc/X11/ directory (in RAM). I then ran 'sudo gdm restart'. When gdm had restarted, and Gnome stuff appeared, the resolution was then 1024x768. You can see the various resolution settings which I could select, in the Xorg

[Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

Xorg.0.log generated starting gdm without the xorg.conf in place. Note the several allowed screen resolutions greater than 1024x768, which this display cannot handle (except by cropping the display to 1024x768. Either: 1) the system has to determine the maximum screen resolution automatically, o

[Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

Here is the Xorg.0.log file generated when restarting gdm with the above xorg.conf file in place. ** Attachment added: "Xorg.0.log after starting with xorg.conf in place" http://launchpadlibrarian.net/30406199/Xorg.0.log -- [K8M800] Panel on K8M800 is not supported (Averatec 3280) https://bug

Re: [Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

Thank you - since I'm away today, I may not get to this until tomorrow. I assume this means I'll have to download the rest of the source and build and install the driver . On Mon, Aug 17, 2009 at 12:00 PM, Bartosz wrote: > If it easier for you please replace the "/src/via_driver.c" file to file

Re: [Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

Actually, I have no idea where to get the rest of the sources (configuration and makefiles etc) to build this. On Mon, Aug 17, 2009 at 12:32 PM, Peter Belew wrote: > Thank you - since I'm away today, I may not get to this until tomorrow. > > I assume this means I'll have to d

Re: [Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

It turns out I had actually built an openchrome driver some time ago (I have to look at my Launchpad email to determine the date) in order to deal with this or a related problem. At any rate, I downloaded the current sources from the OpenChrome server, copied in the patched via_driver.c file, and

[Ubuntu-x-swat] [Bug 186103] Re: [K8M800] Panel on K8M800 is not supported (Averatec 3280)

Please see my comments in bug #296142 regarding my earlier installation of the openchrome driver (in both ubuntu and debian). Also, I tried the live CD for Karmic Koala 9.10, and the only real problem with display is that it also chooses a too-high resolution for the screen, so that only the upper

[Ubuntu-x-swat] [Bug 538893] Re: Console screens unusable on Jetway system with VT8623 [Apollo CLE266], boot problems

The situation is unchanged as of this morning. -- Console screens unusable on Jetway system with VT8623 [Apollo CLE266], boot problems https://bugs.launchpad.net/bugs/538893 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchr

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

The situation is unchanged as of this morning. Spit screen, hazy image while booting, no text consoles, etc. -- [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver https://bugs.launchpad.net/bugs/495553 You receiv

Re: [Ubuntu-x-swat] [Bug 538893] Re: Console screens unusable on Jetway system with VT8623 [Apollo CLE266], boot problems

That seems to have cured the problem on the system with the Jetway motherboard. I did get both my custom boot splash and my custom login-screen splash, though. (Actually I just updated the system with apt-get after blacklisting the viafb, and the initrd happened to be rebuilt in the process) Thank

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

A major part of this bug was solved by disabling the viafb framebuffer driver - this was done by blacklisting viafb in /etc/modprobe.d /blacklist-framebuffer.conf (thanks to a suggestion by Ian Clark for bug #538893 regarding another system with a UniChrome display) - on the next update, the initrd

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

So this problem was largely with the viafb driver, but the console problem is something different. -- [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver https://bugs.launchpad.net/bugs/495553 You received this bu

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

The Beta-2 live cd will not boot properly. First of all, the screen resolution is STILL set wrong initially, so the screen is cropped to the upper-left 1024x768 corner of a larger (1600x1200?) screen. I was able to get around this by changing the screen resolution after logging in. Also, I still

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 boot failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

Incidentally, this system boots properly with the correct screen resolution from the live CD for the Cuban Nova Linux 30012009 V1 (BAIRE-1.1.2-30012009-V1) which I downloaded today. This is a Gentoo- based distro. It appears to use an openchrome driver for this Averatec system. I've attached a tar

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 boot failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

The problem with text consoles is still happening as of 15 Apr 2010. For example, ctrl-alt-F2 results in an unintelligible colored screen. The same for F1 through F6. alt-F7 switches back to Gnome. I'll try the live-cd booting problem on the RC release, unless someone suggests trying a daily build

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 boot failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

I am adding Xorg.0.log before switching to a text console, after switching to a text console, and after switching back to the GUI Gnome screen. Xorg.0.log - before Xorg.0.log.console - after switching to (unusable) console Xorg.0.log.x - after switching back ** Attachment added: "Tar archive cont

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 boot failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

The above Xorg.0.log files were obtained after updating the system around 14:30 UTC on Apr 16. The files were saved while logged in from another machine using ssh. Again, I advocate installation of an ssh server an option on live CDs and during installation (I believe the Sabayon Linux DVD allows

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 boot failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

The booting problem described in #111 is still happening with the 17 April '10 daily build. It's impossible to log in to the X/Gnome display, since as soon as the system logs in, X fails and the GDM login screen reappears after several seconds. After some experimentation, I was able to log on in s

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

** Summary changed: - [K8M800] Beta-2 boot failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid + [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Luc

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

A clarification to #111 and #117 and the problem description - the live CDs for beta-2 and the april 17 build do boot up, but it's impossible to log in once the live CD has booted. However if Lucid has been installed previously, and is updated to date, the principal remaining problem is that it is

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

Hi Bartosz - I'm using the 2.6.32-21-generic #32-Ubuntu SMP kernel, dated Fri Apr 16 08:10:02 UTC - I update with apt-get more or less daily. On the live CD, it's whatever came on the Apr 17 live CD - probably the same, but I didn't check. I looked at Bug #471646, where some similar boot or login

[Ubuntu-x-swat] [Bug 538893] Re: [CLE266] Console screens unusable on Jetway system with VT8623, boot problems

I'm updating this system right now - it hadn't been updated for a few days. I believe blacklisting the viafb solved the problem, and I believe that's the default now - to blacklist viafb. I'll check again when the update is complete. I have another system with the same kind of motherboard. that ha

[Ubuntu-x-swat] [Bug 538893] Re: [CLE266] Console screens unusable on Jetway system with VT8623, boot problems

After today's update, this system is running Linux lightning 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 i686 GNU/Linux viafb is in /etc/modprobe.d/blacklist-framebuffer.conf - this is now the default situation. -- [CLE266] Console screens unusable on Jetway system with VT8623

[Ubuntu-x-swat] [Bug 508456] Re: Lucid frequently crashes while starting gdm on Averatec 3280

Hi Bartosz - I'm not seeing the 'clouded image' problem (#17) any more, but the problems noted in Bug #495553 still remain. This includes the startup problem with the recent daily-build live CDs - where the system tries to auto-login and keeps failing and showing the login dialog. -- Lucid freque

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

I downloaded the 19 April daily build live CD, and it still won't allow logging in. -- [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid https://bugs.launchpad.net/bugs/495553 You received this bug notifi

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

I checked out the driver source specifying "-r 758". I get a fatal error on trying to make the driver - the header file xf86Resources.h is missing, also there are some warnings about formats not matching variables, in via_accel.c, function viaExaUploadToScratch() -- [K8M800] Beta-2 live-CD login

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

The latest Karmic driver for this is xserver-xorg-video-openchrome/karmic 1:0.2.903+svn758-0ubuntu1 How, exactly, can I install that in Lucid? -- [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid http

Re: [Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

The xserver-xorg-video-via driver installed ok, but it doesn't seem to make any difference. Should I change or remove xorg.conf? On Thu, Apr 22, 2010 at 11:53 PM, Bartosz wrote: > Try to install package from that (just double click on that): > https://launchpad.net/ubuntu/+archive/primary/+files/

Re: [Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

I tried to install that; here are the errors that are reported: # dpkg -i xserver-xorg-video-openchrome_0.2.903+svn758-0ubuntu1_i386.deb dpkg: warning: downgrading xserver-xorg-video-openchrome from 1:0.2.904+svn827-1 to 1:0.2.903+svn758-0ubuntu1. dpkg: regarding xserver-xorg-video-openchrome_0.2.

Re: [Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

This still does not work. The make suggests some changes to configure.ac and to Makefile.am - I did the first and the second refers to something that's in Makefile.in (I think) but isn't clear. In any event, the make fails. On Sun, Apr 25, 2010 at 9:22 AM, Bartosz wrote: > try to compile the sour

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

If I boot with Karmic kernel: 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 i686 GNU/Linux Then some Lucid 'features' are suppressed during startup, and I can switch into text consoles with ctrl-alt-F1 through ...F6 properly. The display driver is still xserver-xorg-video-openchr

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid

Early after booting (as in #131) I see the message chroot: cannot execute /etc/apparmor/initramfs This might be relevant or not. -- [K8M800] Beta-2 live-CD login failure, Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid https://bugs.launchp

Re: [Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

Should I apply that to the original via_driver.c file or on top of the previous patch? On Wed, Jan 20, 2010 at 2:40 PM, Bartosz wrote: > Hi > Apply this patch and attach your Xorg.0.log file after that. > > ** Attachment added: "ddc2.patch" >   http://launchpadlibrarian.net/38168035/ddc2.patch >

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

(I applied the patch to the original file) Here's the Xorg.0.log file ... ** Attachment added: "Xorg.0.log after latest patch and reboot" http://launchpadlibrarian.net/38170511/Xorg.0.log -- [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 run

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

I'm not sure the last Xorg.0.log was valid ... I'm going to start with a new source tree later this evening and try again. I ended up with X not starting the last couple of times I tried booting - I had to start in text mode and start daemons manually. -- [K8M800] Screen origin shifted to center

[Ubuntu-x-swat] [Bug 495553] Re: [K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't work, on Averatec 3280 running Lucid with openchrome driver

I was unable to patch: pe...@eros:~/openchrome/src$ patch -p0 < vbeEDID.patch patching file src/via_driver.c Hunk #1 FAILED at 1566. Hunk #2 FAILED at 1620. 2 out of 2 hunks FAILED -- saving rejects to file src/via_driver.c.rej patching file src/via_dri.c Hunk #1 FAILED at 267. 1 out of 1 hunk FAI

  1   2   3   4   >