[Ubuntu-x-swat] [Bug 623732] [NEW] xset dpms force on, not working properly with fglrx

2010-08-24 Thread jamey0824
Public bug reported:

Binary package hint: fglrx

Note I originally report this here
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/528636
but they closed it before i could get lucid running on my machine, due to 
another fglrx bug.  Anyways here's the bug

sleep 1; xset dpms force off ; sleep 10; xset dpms force on

expected behavior:
turn off screen , wait 10 secs , turn back on

fglrx behavior;
turn off screen , wait 10 secs , then goes into standbyi think

have confirmed this behavior with others, and also have verified it works using 
other drivers.  
UPDATE:  Still the same behavior in LUCID, with all versions of fglrx up to 
current.

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
xset dpms force on, not working properly with fglrx
https://bugs.launchpad.net/bugs/623732
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 528636] Re: xset dpms force on not working properly

2010-07-27 Thread jamey0824
Well, sorry i haven't forgoten about this bug but, i have not been able
to upgrade due to another bug which prevented me from upgrading.
Anyways Lucid has the exact same behavior, so this bug still exists

-- 
xset dpms force on not working properly
https://bugs.launchpad.net/bugs/528636
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 550644] Re: multiple display adapters lockup

2010-04-29 Thread jamey0824
Did a reinstall with lynx final, still can't get 2 adapters working at
same time.  Both individually work.

aticonfig  --adapter=all --initial   and computer still crashes

i also disabled kms in grub thats not it.

-- 
multiple display adapters lockup
https://bugs.launchpad.net/bugs/550644
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 550644] [NEW] multiple display adapters lockup

2010-03-28 Thread jamey0824
Public bug reported:

system 2 ati 5450's, lucid
if i enable the second adapter by
aticonfig --adapter=all --initial
system locks up on reboot

i can individually enable either display but both together=crash,

Note a multiseat setup using same system doesn't work either only one
display works at a time.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.721-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sun Mar 28 22:18:35 2010
DkmsStatus:
 fglrx, 8.721, 2.6.32-17-generic, x86_64: installed 
 fglrx, 8.721, 2.6.32-16-generic, x86_64: installed
GdmLog:
 
InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
MachineType: BIOSTAR Group TA790GX A2+
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic 
root=UUID=96d41c48-3a65-4fcf-9c9c-b731eb42588d ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fglrx-installer
XorgLogOld:
 
dmi.bios.date: 08/04/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: TA790GX A2+
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd08/04/2009:svnBIOSTARGroup:pnTA790GXA2+:pvr:rvnBIOSTARGroup:rnTA790GXA2+:rvr:cvnBIOSTARGroup:ct3:cvr6.0:
dmi.product.name: TA790GX A2+
dmi.sys.vendor: BIOSTAR Group
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename:   lucid
 architecture:   x86_64
 kernel: 2.6.32-17-generic

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lucid

-- 
multiple display adapters lockup
https://bugs.launchpad.net/bugs/550644
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 550644] Re: multiple display adapters lockup

2010-03-28 Thread jamey0824

** Attachment added: BootDmesg.txt
   http://launchpadlibrarian.net/42337756/BootDmesg.txt

** Attachment added: CurrentDmesg.txt
   http://launchpadlibrarian.net/42337757/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/42337758/Dependencies.txt

** Attachment added: GdmLog1.txt
   http://launchpadlibrarian.net/42337759/GdmLog1.txt

** Attachment added: GdmLog2.txt
   http://launchpadlibrarian.net/42337760/GdmLog2.txt

** Attachment added: Lspci.txt
   http://launchpadlibrarian.net/42337761/Lspci.txt

** Attachment added: Lsusb.txt
   http://launchpadlibrarian.net/42337762/Lsusb.txt

** Attachment added: PciDisplay.txt
   http://launchpadlibrarian.net/42337763/PciDisplay.txt

** Attachment added: ProcCpuinfo.txt
   http://launchpadlibrarian.net/42337764/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   http://launchpadlibrarian.net/42337765/ProcInterrupts.txt

** Attachment added: ProcModules.txt
   http://launchpadlibrarian.net/42337766/ProcModules.txt

** Attachment added: RelatedPackageVersions.txt
   http://launchpadlibrarian.net/42337767/RelatedPackageVersions.txt

** Attachment added: UdevDb.txt
   http://launchpadlibrarian.net/42337768/UdevDb.txt

** Attachment added: UdevLog.txt
   http://launchpadlibrarian.net/42337769/UdevLog.txt

** Attachment added: XorgConf.txt
   http://launchpadlibrarian.net/42337770/XorgConf.txt

** Attachment added: XorgLog.txt
   http://launchpadlibrarian.net/42337771/XorgLog.txt

** Attachment added: Xrandr.txt
   http://launchpadlibrarian.net/42337772/Xrandr.txt

** Attachment added: setxkbmap.txt
   http://launchpadlibrarian.net/42337773/setxkbmap.txt

** Attachment added: xdpyinfo.txt
   http://launchpadlibrarian.net/42337774/xdpyinfo.txt

** Attachment added: xkbcomp.txt
   http://launchpadlibrarian.net/42337775/xkbcomp.txt

-- 
multiple display adapters lockup
https://bugs.launchpad.net/bugs/550644
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 528636] [NEW] xset dpms force on not working properly

2010-02-26 Thread jamey0824
Public bug reported:

sleep 1; xset dpms force off ; sleep 10; xset dpms force on

expected behavior:
turn off screen , wait 10 secs , turn back on

fglrx behavior;
turn off screen , wait 10 secs , then goes into standbyi think

have confirmed this behavior with others, and also have verified it
works using other drivers.

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
xset dpms force on not working properly
https://bugs.launchpad.net/bugs/528636
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 441653] Re: xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

2009-10-04 Thread jamey0824
Looking into this matter further i've manged to get the additional info
Fatal server error:
xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call


Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
Please also check the log file at /var/log/Xorg.3.log for additional 
information.

 ddxSigGiveUp: Closing log
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
Warning:  Could not generate /etc/X11/xorg.conf.failsafe for vesa driver

-- 
xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call
https://bugs.launchpad.net/bugs/441653
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 441653] Re: xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

2009-10-04 Thread jamey0824
I am using a multiseat setup which has been working fairly well under
karmic, although it seems the order you start your xorg servers seem to
be an issure perhaps with the latest round of updates, causes some sort
of race condition to occur.  Because now when I change the order of the
seats i am able to get them all up for a few seconds then it terminates
with the seat with the console session with the above error.  Note that
strangely this behavior only is exibited on the main console( by that i
mean the terminal that is showing the boot sequence.)  When i change
back with a factory original kdmrc, it still exibits this behavoir.
Which i never had any problems with before.

-- 
xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call
https://bugs.launchpad.net/bugs/441653
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 441653] Re: xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

2009-10-03 Thread jamey0824
I installed kdm and have been using that for some time, sometimes i have
to uninstall kdm and reinstall it to get system to boot, that hasen't
worked in this case.  Although i have just discovered if i manuelly
launch kdm once i get to the prompt the system comes up.  I have no idea
what script , or launch directory normally calls kdm, but i am looking
into it.

-- 
xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call
https://bugs.launchpad.net/bugs/441653
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp