Re: screen lock shuts down attached HDDs, they don't start up again

2023-11-22 Thread Zenaan Harkness
On 11/22/23, Zenaan Harkness  wrote:
> On 11/21/23, Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>> On 21 Nov 2023 14:48 +1100, from zen...@gmail.com (Zenaan Harkness):
>>> The desktop displays, but my external HDDs have been put to sleep, and
>>> they do not wake up.
>>>
>>> One of them is zfs. The zfs mounts list shows, but any attempt to
>>> view/ls a zfs mount, just hangs permanently until a reboot.
>>>
>>> The other drive is an ext4 filesystem, and it has been completely
>>> un-mounted and the HDD spun down, and it does not spin up again -
>>> until a reboot.
>>
>> This doesn't sound right.
>>
>> Can you run hdparm -C on the affected devices at the time? What is the
>> result of that?
>
> So it seems I can test this quickly with a manual suspend, then do the
> various checks... it seems that the issue here is the
> auto-sleep/suspend.
>
> For starters, prior to suspend, I've removed the zfs drive, and just
> left the ext4 drive in the USB caddy (it holds up to 2 drives).
>
> Prior to suspend, I get, for the 2.5 inch hdd when it has not been
> accessed for a while and I can feel it is not spinning:
>
> # hdparm -C /dev/sda
> /dev/sda:
>  drive state is:  standby
>
> then, I ls'ed a dir in that drive that had not previously been
> accessed, and could feel it spin up and then give me the output, and
> then I ran hdparm again and interestingly, checking a few times on the
> now spun up drive, I get identical results as with the drive in the
> spun down state:
>
> # hdparm -C /dev/sda
> /dev/sda:
>  drive state is:  standby
>
> 
> Now, after suspend (and wait for hdd to spin down, and wait for
> monitors to blank, and wait another 10s) and finally wake the computer
> up (which is really too slow - 20 or 30 seconds or so, so something
> odd or challenging seems to be happening inside the kernel somewhere):
>
> # ll /dev/sd*
> ls: cannot access '/dev/sd*': No such file or directory
>
> # hdparm -C /dev/sda
> /dev/sda: No such file or directory
>
>
>> Do the drives spin back up if you use hdparm -z?
>
> Prior to suspend and wake, I get this:
>
> # hdparm -z /dev/sda
> /dev/sda:
>  re-reading partition table
>  BLKRRPART failed: Device or resource busy
>
> And again, after suspend and wake there is no more /dev/sda, or any
> /dev/sd*, so I cannot run hdparm on any such device.
>
>
>> What is the exact kernel version you are running? Please provide both
>> the package name and exact package version, and the full output from
>> uname -a.
>
> # uname -a
> Linux zen-L7 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1
> (2023-09-29) x86_64 GNU/Linux
>
> The kernel package is exactly
> linux-image-6.1.0-13-amd64
>
>
>> Assuming that those drives are connected over USB, do they show up in
>> lsusb output while inaccessible?
>
> Prior to suspend and wake, lsusb shows me my hubs, dock, eth adaptors,
> trackball, and possibly the following is the HDD dock ? dunno:
>
> Bus 006 Device 015: ID 152d:0565 JMicron Technology Corp. / JMicron
> USA Technology Corp. JMS56x Series
>
> ... and sure enough after suspend and wake, Bus 006 Device 015 is
> gone, no longer exists, so it somehow has not woken up - but I CAN
> still see the blue light on the hdd caddy, but the hdd remains in a
> spun down/ sleep state, and no /dev/sd* device.


I apologize, the above para was inserted after I did the suspend and
wake cycle, and the following paras were done before that. I apologize
for the confusion, so just be aware the following paras are part of
the "Prior to suspend..." para above.

> I do get these though (alias ll='ls -l'):
>
> # find /dev/disk/|grep usb
> /dev/disk/by-id/usb-WDC_WD20_SPZX-22UA7T0_RANDOM__3F4917AD758C-0:0
> /dev/disk/by-path/pci-:3a:00.0-usb-0:2.3.1:1.0-scsi-0:0:0:0
>
> # ll /dev/disk/by-path/pci-:3a:00.0-usb-0:2.3.1:1.0-scsi-0:0:0:0
> 0 lrwxrwxrwx 1 root root 9 20231122 10:33.10
> /dev/disk/by-path/pci-:3a:00.0-usb-0:2.3.1:1.0-scsi-0:0:0:0 ->
> ../../sda
>
> # ll /dev/sd*
> 0 brw-rw 1 root disk 8, 0 20231122 10:33.10 /dev/sda
>
> ... interestingly, it seems when I formatted this drive with ext4, I
> formatted ext4 on the whole disk (/dev/sda) without using partitions,
> and so it's just /dev/sda and not /dev/sda1, which has the ext4
> filesystem.
>
>
>> Is there anything relevant in dmesg output?
>
> This looks quite suspicious (some error lines, not all of dmesg output):
>
> [42635.638996] usb 6-2.3.1: device not accepting address 15, error -62
> [42668.986050] usb 6-2.3.1: USB disconnect, device number 15
> [42668.986406] device offline error, dev sda, sector 0 op 0x1:(WRITE)
> flags 0x800 phys_seg 0 prio class 2
> [42668.988647] hub 6-2.3.2:1.0: hub_ext_port_status failed (err = -71)
> [42668.990867] hub 6-2.3.2.3:1.0: hub_ext_port_status failed (err = -71)
> [42668.990888] hub 6-2.3.2.1:1.0: hub_ext_port_status failed (err = -71)
> [42669.007554] usb 6-2.3.2.3.1: Failed to suspend device, error -71
> [42669.008775] hub 6-2.3.2:1.0: hub_ext_port_status failed (err = -71)
> 42713.495

Re: screen lock shuts down attached HDDs, they don't start up again

2023-11-22 Thread Zenaan Harkness
On 11/21/23, Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> On 21 Nov 2023 14:48 +1100, from zen...@gmail.com (Zenaan Harkness):
>> The desktop displays, but my external HDDs have been put to sleep, and
>> they do not wake up.
>>
>> One of them is zfs. The zfs mounts list shows, but any attempt to
>> view/ls a zfs mount, just hangs permanently until a reboot.
>>
>> The other drive is an ext4 filesystem, and it has been completely
>> un-mounted and the HDD spun down, and it does not spin up again -
>> until a reboot.
>
> This doesn't sound right.
>
> Can you run hdparm -C on the affected devices at the time? What is the
> result of that?

So it seems I can test this quickly with a manual suspend, then do the
various checks... it seems that the issue here is the
auto-sleep/suspend.

For starters, prior to suspend, I've removed the zfs drive, and just
left the ext4 drive in the USB caddy (it holds up to 2 drives).

Prior to suspend, I get, for the 2.5 inch hdd when it has not been
accessed for a while and I can feel it is not spinning:

# hdparm -C /dev/sda
/dev/sda:
 drive state is:  standby

then, I ls'ed a dir in that drive that had not previously been
accessed, and could feel it spin up and then give me the output, and
then I ran hdparm again and interestingly, checking a few times on the
now spun up drive, I get identical results as with the drive in the
spun down state:

# hdparm -C /dev/sda
/dev/sda:
 drive state is:  standby


Now, after suspend (and wait for hdd to spin down, and wait for
monitors to blank, and wait another 10s) and finally wake the computer
up (which is really too slow - 20 or 30 seconds or so, so something
odd or challenging seems to be happening inside the kernel somewhere):

# ll /dev/sd*
ls: cannot access '/dev/sd*': No such file or directory

# hdparm -C /dev/sda
/dev/sda: No such file or directory


> Do the drives spin back up if you use hdparm -z?

Prior to suspend and wake, I get this:

# hdparm -z /dev/sda
/dev/sda:
 re-reading partition table
 BLKRRPART failed: Device or resource busy

And again, after suspend and wake there is no more /dev/sda, or any
/dev/sd*, so I cannot run hdparm on any such device.


> What is the exact kernel version you are running? Please provide both
> the package name and exact package version, and the full output from
> uname -a.

# uname -a
Linux zen-L7 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1
(2023-09-29) x86_64 GNU/Linux

The kernel package is exactly
linux-image-6.1.0-13-amd64


> Assuming that those drives are connected over USB, do they show up in
> lsusb output while inaccessible?

Prior to suspend and wake, lsusb shows me my hubs, dock, eth adaptors,
trackball, and possibly the following is the HDD dock ? dunno:

Bus 006 Device 015: ID 152d:0565 JMicron Technology Corp. / JMicron
USA Technology Corp. JMS56x Series

... and sure enough after suspend and wake, Bus 006 Device 015 is
gone, no longer exists, so it somehow has not woken up - but I CAN
still see the blue light on the hdd caddy, but the hdd remains in a
spun down/ sleep state, and no /dev/sd* device.

I do get these though (alias ll='ls -l'):

# find /dev/disk/|grep usb
/dev/disk/by-id/usb-WDC_WD20_SPZX-22UA7T0_RANDOM__3F4917AD758C-0:0
/dev/disk/by-path/pci-:3a:00.0-usb-0:2.3.1:1.0-scsi-0:0:0:0

# ll /dev/disk/by-path/pci-:3a:00.0-usb-0:2.3.1:1.0-scsi-0:0:0:0
0 lrwxrwxrwx 1 root root 9 20231122 10:33.10
/dev/disk/by-path/pci-:3a:00.0-usb-0:2.3.1:1.0-scsi-0:0:0:0 ->
../../sda

# ll /dev/sd*
0 brw-rw 1 root disk 8, 0 20231122 10:33.10 /dev/sda

... interestingly, it seems when I formatted this drive with ext4, I
formatted ext4 on the whole disk (/dev/sda) without using partitions,
and so it's just /dev/sda and not /dev/sda1, which has the ext4
filesystem.


> Is there anything relevant in dmesg output?

This looks quite suspicious (some error lines, not all of dmesg output):

[42635.638996] usb 6-2.3.1: device not accepting address 15, error -62
[42668.986050] usb 6-2.3.1: USB disconnect, device number 15
[42668.986406] device offline error, dev sda, sector 0 op 0x1:(WRITE)
flags 0x800 phys_seg 0 prio class 2
[42668.988647] hub 6-2.3.2:1.0: hub_ext_port_status failed (err = -71)
[42668.990867] hub 6-2.3.2.3:1.0: hub_ext_port_status failed (err = -71)
[42668.990888] hub 6-2.3.2.1:1.0: hub_ext_port_status failed (err = -71)
[42669.007554] usb 6-2.3.2.3.1: Failed to suspend device, error -71
[42669.008775] hub 6-2.3.2:1.0: hub_ext_port_status failed (err = -71)
42713.495809] xhci_hcd :3a:00.0: Timeout while waiting for setup
device command
[42713.703761] usb 6-2.3.1: device not accepting address 19, error -62
[42713.704792] usb 6-2.3-port1: unable to enumerate USB device
[42713.708332] usb 6-2.3.2: USB disconnect, device number 5
[42713.708343] usb 6-2.3.2.1: USB disconnect, device number 7


since "2.3.1" appears in the drive links above, and 6 could be "Bus
6". I'm not familiar with dmesg output though...

I also see the following, but tha

Re: screen lock shuts down attached HDDs, they don't start up again

2023-11-21 Thread Michael Kjörling
On 21 Nov 2023 14:48 +1100, from zen...@gmail.com (Zenaan Harkness):
> The desktop displays, but my external HDDs have been put to sleep, and
> they do not wake up.
> 
> One of them is zfs. The zfs mounts list shows, but any attempt to
> view/ls a zfs mount, just hangs permanently until a reboot.
> 
> The other drive is an ext4 filesystem, and it has been completely
> un-mounted and the HDD spun down, and it does not spin up again -
> until a reboot.

This doesn't sound right.

Can you run hdparm -C on the affected devices at the time? What is the
result of that?

Do the drives spin back up if you use hdparm -z?

What is the exact kernel version you are running? Please provide both
the package name and exact package version, and the full output from
uname -a.

Assuming that those drives are connected over USB, do they show up in
lsusb output while inaccessible?

Is there anything relevant in dmesg output?

Are you booting the kernel with any command-line parameters? Please
provide the exact contents of /proc/cmdline.

A spun-down drive can take a brief time to spin back up (typically on
the order of a few seconds), but that SHOULD be handled automatically;
clearly something odd is going on in your case if it doesn't.

-- 
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”



Re: Screen power save in console mode

2022-06-13 Thread David Wright
On Mon 13 Jun 2022 at 10:14:36 (-0400), Felix Miata wrote:
> Jeremy Ardley composed on 2022-06-13 15:49 (UTC+0800):
> 
> > I have a Debain (Armbian) server that does not boot to any form of 
> > window manager, so what is seen on the screen is just the command console.
> 
> > What I would like  to do is have the console screen go into screen power 
> > save mode after some period and recover when keyboard or mouse are used.
> 
> > Is there a simple way to configure that?
> 
> consoleblank= in /etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT=.
> https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

There are also Linux Console Private CSI Sequences
documented in   man 4 console_codes   that include:

   ESC [ 9 ; n ]   Set screen blank timeout to n minutes.
   ESC [ 13 ]  Unblank the screen.
   ESC [ 14 ; n ]  Set the VESA powerdown interval in minutes.

So, for example, I added \e[9;16] to the beginning of /etc/issue
when it became apparent that Linux wasn't blanking the console
any more. I think it was buster, but could have been stretch.
I wouldn't notice if bullseye still doesn't. Don't quote me on
the version.

Cheers,
David.



Re: Screen power save in console mode

2022-06-13 Thread Felix Miata
Jeremy Ardley composed on 2022-06-13 15:49 (UTC+0800):

> I have a Debain (Armbian) server that does not boot to any form of 
> window manager, so what is seen on the screen is just the command console.

> What I would like  to do is have the console screen go into screen power 
> save mode after some period and recover when keyboard or mouse are used.

> Is there a simple way to configure that?

consoleblank= in /etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT=.
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata



Re: Screen power save in console mode

2022-06-13 Thread Bijan Soleymani

On 2022-06-13 03:49, Jeremy Ardley wrote:

I have a Debain (Armbian) server that does not boot to any form of
window manager, so what is seen on the screen is just the command
console.

What I would like  to do is have the console screen go into screen
power save mode after some period and recover when keyboard or mouse
are used.

Is there a simple way to configure that?


It seems this can be done via setterm command. It might require kernel 
or kernel command line parameter changes depending on what you need to 
do.


This link may be of some help:
https://superuser.com/questions/152347/change-linux-console-screen-blanking-behavior

Bijan



Re: Screen goes blank for 1-2 seconds

2022-02-09 Thread hdv@gmail

cat /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input

Should give temperature:
Mine right now is:
29000

which apparently is 29C.

/sys/class/drm/card0/device/hwmon/hwmon0/pwm1

is the power management.


I returned home yesterday.

It seems the temperature here isn't out of the ordinary:

$ cat /sys/class/drm/card0/device/hwmon/hwmon1/temp1_input
37000

(The machine has been on for 4 hours now.)

I read Pankaj's problem disappeared after upgrading his kernel to 5.10. 
I don't think that would help here as I have been on the 5.15 series for 
quite some time now.


I still think it is a firmware problem as I am reasonably sure I've 
eliminated all hardware factors from the equation.


Ah well. It isn't a serious issue. I can live with it. Maybe sometime in 
the future it will be solved.


Grx HdV



Re: Screen goes blank for 1-2 seconds

2022-02-09 Thread Pankaj Jangid
Pankaj Jangid  writes:

> Pankaj Jangid  writes:
>
>> Since I have setup a new hardware - x570 chipset, rx580 GPU - I am
>> facing a very strange problem. The monitor goes blank for a brief time,
>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>> cable.
>>
>> During that 1-2s, the machine response is fine. Whatever I type during
>> that time goes there as input, and visible when the monitor comes back.
>
> Further diagnosing the problem, I could find out these messages in the
> log immediately after the screen goes blank:
>
> [31915.382609] [drm] PCIE GART of 256M enabled (table at 0x00F4).
> [31915.475968] [drm] UVD and UVD ENC initialized successfully.
> [31915.575975] [drm] VCE initialized successfully.
> [31915.583044] amdgpu :2d:00.0: [drm] Cannot find any crtc or sizes
>
> ...
>
> [32051.104088] [drm] PCIE GART of 256M enabled (table at 0x00F4).
> [32051.197629] [drm] UVD and UVD ENC initialized successfully.
> [32051.297636] [drm] VCE initialized successfully.
> [32051.304703] amdgpu :2d:00.0: [drm] Cannot find any crtc or sizes
>
> This looks like a driver issue. Where should I report this problem?

I have upgraded kernel to latest stable from upstream (cp
/boot/config-5.10.0-11-amd64 .config && make oldconfig && make deb-pkg),
and the problem is gone.

The above messages are still coming but there is no frequent blank
screen.




Re: Screen goes blank for 1-2 seconds

2022-02-06 Thread Pankaj Jangid
Pankaj Jangid  writes:

> Since I have setup a new hardware - x570 chipset, rx580 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
>
> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.

Further diagnosing the problem, I could find out these messages in the
log immediately after the screen goes blank:

[31915.382609] [drm] PCIE GART of 256M enabled (table at 0x00F4).
[31915.475968] [drm] UVD and UVD ENC initialized successfully.
[31915.575975] [drm] VCE initialized successfully.
[31915.583044] amdgpu :2d:00.0: [drm] Cannot find any crtc or sizes

...

[32051.104088] [drm] PCIE GART of 256M enabled (table at 0x00F4).
[32051.197629] [drm] UVD and UVD ENC initialized successfully.
[32051.297636] [drm] VCE initialized successfully.
[32051.304703] amdgpu :2d:00.0: [drm] Cannot find any crtc or sizes

This looks like a driver issue. Where should I report this problem?




Re: Screen not blanking

2022-02-06 Thread Cindy Sue Causey
On 2/5/22, Nicholas Geovanis  wrote:
> On Sat, Feb 5, 2022, 3:15 PM c. marlow  wrote:
>>
>> Subject: Screen not blanking
>> Date: Saturday 05 February 2022, 03:13:19 pm
>> From: "c. marlow" 
>> To: us...@trinitydesktop.org
>>
>> Fresh install of Debian 11 ( as of yesterday)
>> Trinity Desktop 14
>>
>> My screen is not going to sleep Sometimes it will and sometimes it
>> won't.
>>
>> For instance:
>>
>> I took a nap earlier... The password box said the session was locked at
>> 2:01
>> PM CST. At 3:00 the screen was still on!!
>>
>
> Just a thought. Make sure the time zone and  localization settings are
> _really_ the same as you use on other Debian installations. And same as you
> are expecting.
>
> Also when the screen does turn off, it takes WAY over the time that
>> I have it set for to blank off and turn off the screen. I have it set for:
>>
>> 25 for screensaver
>>
>> 26 for display standby
>>
>> 26 for display suspend
>>
>> 26 min to power off the screen.
>>
>> Sometimes its almost or right at an hour before the screen blanks off.
>>
>> I didn't have this problem with Gnome DE on Debian.


I'm not using any screensavers these days (for no particular reason),
but when I did have them installed, I've also experienced similar
conflicts. I can't remember if I actually fixed it, seems like it at
least became more bearable, when I went into Settings and played
around there:

Applications (desktop menu) > Settings > Power Manager

Multiple tabs there seem to allow for potential conflict.

That's under XFCE4, by the way. Other desktop environments like
Trinity will hopefully have their own similar user-friendly features.

Afterthought based on the power management potential for conflict: Are
there any possibly related warning or error messages showing up via
e.g. dmesg?

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *



Re: Screen not blanking

2022-02-05 Thread Nicholas Geovanis
On Sat, Feb 5, 2022, 3:15 PM c. marlow  wrote:

> Sending this message to both groups:
>
> --  Forwarded Message  --
>
> Subject: Screen not blanking
> Date: Saturday 05 February 2022, 03:13:19 pm
> From: "c. marlow" 
> To: us...@trinitydesktop.org
>
> Fresh install of Debian 11 ( as of yesterday)
> Trinity Desktop 14
>
> My screen is not going to sleep Sometimes it will and sometimes it
> won't.
>
> For instance:
>
> I took a nap earlier... The password box said the session was locked at
> 2:01
> PM CST. At 3:00 the screen was still on!!
>

Just a thought. Make sure the time zone and  localization settings are
_really_ the same as you use on other Debian installations. And same as you
are expecting.

Also when the screen does turn off, it takes WAY over the time that
> I
> have it set for to blank off and turn off the screen. I have it set for:
>
> 25 for screensaver
>
> 26 for display standby
>
> 26 for display suspend
>
> 26 min to power off the screen.
>
>
> Sometimes its almost or right at an hour before the screen blanks off.
>
>
> I didn't have this problem with Gnome DE on Debian.
>
>
> Thanks,
> Chris
>
>
> ---
>
>


Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread Andrew M.A. Cater
On Fri, Jan 28, 2022 at 05:05:56PM +0100, hdv@gmail wrote:
> On 2022-01-28 16:53, Andrew M.A. Cater wrote:
> 
> > Wherever possible, it's easier if you are using Debian stable: more people
> > will hae experience / be running that at any one time.
> > 
> > All the very best, as ever,
> > 
> > Andy Cater
> 
> I know. But testing is more convenient for me. I need to test current
> software for the courseware I write. Stable is perfectly fine, but not if
> you want to trail the leading edge a bit more closely. Sid is to close to
> the edge for me though.
> 
> I've been running testing for close to 25 years now. In the early days
> breakage was a recurring thing, but nowadays that is quite rare. Up to now
> I've always been able to solve any trouble. My time as a sysadmin still
> proves to be useful when I need to do that.  ;-)
> 
> Grx HdV
>

There's definitely something to be said, if you can, for running a "testing/
sid" distribution in a VM - the hardware requirements are usually constrained
/ understood" and, if the worst comes to the worst, you can supply
a VM image to somebody saying "there's the entire thing you need
against which I wrote my courseware"

This is very general advice, of course, and everyone's situation varies.
The formal security support for testing  is not necessarily there and you
can find times when there are informal freezes, long lasting package 
transitions rendering packages uninstallable, or, of course, the
longer freeze before stable release.

A VM also has the ability to constrain the software used and costs little
to rebuild. For myself, I'd always build a full VM rather than a container -
again, people's needs vary and everyone's situation is different.

All the very best, as ever,

Andy Cater



Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread hdv@gmail

On 2022-01-28 16:53, Andrew M.A. Cater wrote:


Wherever possible, it's easier if you are using Debian stable: more people
will hae experience / be running that at any one time.

All the very best, as ever,

Andy Cater


I know. But testing is more convenient for me. I need to test current 
software for the courseware I write. Stable is perfectly fine, but not 
if you want to trail the leading edge a bit more closely. Sid is to 
close to the edge for me though.


I've been running testing for close to 25 years now. In the early days 
breakage was a recurring thing, but nowadays that is quite rare. Up to 
now I've always been able to solve any trouble. My time as a sysadmin 
still proves to be useful when I need to do that.  ;-)


Grx HdV



Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread hdv@gmail

On 2022-01-28 16:48, Bijan Soleymani wrote:

On 2022-01-28 10:16, hdv@gmail wrote:
About the fan: I seem to remember I had to install amdgpu-fan (needed 
to look that up, forgot the name) when I got this setup. Not sure if 
it still is needed or that the driver can control the fan reliably 
nowadays. I need to check that out too when I get home. 


I've had my card since January 2020 and have not needed amdgpu-fan or 
similar software, and it has just worked with default settings from 
kernel drivers.


I would check amdgpu-fan settings to adjust more aggressively or maybe 
uninstall and try settings fan to max and see if that solves the issue.


I'll keep that in mind. Thanks!

P.S. Apologies for the PM. I accidentally used the wrong shortcut.

Grx HdV



Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread Andrew M.A. Cater
On Fri, Jan 28, 2022 at 04:16:19PM +0100, hdv@gmail wrote:
> On 2022-01-28 15:31, Bijan Soleymani wrote:
> > On 2022-01-28 08:40, hdv@gmail wrote:
> > > I am reasonably sure the problem lies in some form or combination of
> > > software. Sadly, my expertise in that area is insufficient to find
> > > out what it is exactly.
> > 
> > What kernel/OS/driver are you using if it is software I can try to
> > reproduce since I have a pretty similar card.
> > 
> > Also you can max out the fan to see if that helps:
> > 
> > echo 0 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable
> > 
> > (If you can pwm1_enable after it will show 1 and not 0, but if you look
> > at pwm1 it will be at max of 255).
> > 
> > Bijan
> > 
> 
> I am (currently) on
> 
> 5.15.0-2-amd64 #1 SMP Debian 5.15.5-2 (2021-12-18) x86_64 GNU/Linux
> 
> and
> 
> xserver-xorg-video-amdgpu
> 
> if I am not mistaken. Sorry, I can't check it from here.
> 

So - Bookworm / Debian testing?

Are you able to reproduce this on Debian stable and kernel 5.10?

> 
> Grx HdV
>

Wherever possible, it's easier if you are using Debian stable: more people
will hae experience / be running that at any one time.

All the very best, as ever,

Andy Cater 



Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread Bijan Soleymani

On 2022-01-28 10:16, hdv@gmail wrote:
About the fan: I seem to remember I had to install amdgpu-fan (needed 
to look that up, forgot the name) when I got this setup. Not sure if 
it still is needed or that the driver can control the fan reliably 
nowadays. I need to check that out too when I get home. 


I've had my card since January 2020 and have not needed amdgpu-fan or 
similar software, and it has just worked with default settings from 
kernel drivers.


I would check amdgpu-fan settings to adjust more aggressively or maybe 
uninstall and try settings fan to max and see if that solves the issue.


Bijan




Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread hdv@gmail

On 2022-01-28 15:31, Bijan Soleymani wrote:

On 2022-01-28 08:40, hdv@gmail wrote:
I am reasonably sure the problem lies in some form or combination of 
software. Sadly, my expertise in that area is insufficient to find out 
what it is exactly.


What kernel/OS/driver are you using if it is software I can try to 
reproduce since I have a pretty similar card.


On the other hand: what goes in my case is not necessarily valid in 
yours.


In case it is is due to overheating this script will log temperature, 
power management and fan settings.


#!/bin/bash
cd /sys/class/drm/card0/device/hwmon/hwmon0
while `true`;
     do date;
     for x in fan1_enable fan1_input fan1_target pwm1 pwm1_enable 
temp1_input;

     do echo -n "$x: "; cat $x;
     done;
     echo; sleep 1;
done

Output will be the following about once a second:

Fri 28 Jan 2022 09:28:12 AM EST
fan1_enable: 0
fan1_input: 1714
fan1_target: 1714
pwm1: 0
pwm1_enable: 2
temp1_input: 36000

Also you can max out the fan to see if that helps:

echo 0 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable

(If you can pwm1_enable after it will show 1 and not 0, but if you look 
at pwm1 it will be at max of 255).


Bijan



I am (currently) on

5.15.0-2-amd64 #1 SMP Debian 5.15.5-2 (2021-12-18) x86_64 GNU/Linux

and

xserver-xorg-video-amdgpu

if I am not mistaken. Sorry, I can't check it from here.

About the fan: I seem to remember I had to install amdgpu-fan (needed to 
look that up, forgot the name) when I got this setup. Not sure if it 
still is needed or that the driver can control the fan reliably 
nowadays. I need to check that out too when I get home.


Grx HdV



Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread Bijan Soleymani

On 2022-01-28 08:40, hdv@gmail wrote:
I am reasonably sure the problem lies in some form or combination of 
software. Sadly, my expertise in that area is insufficient to find out 
what it is exactly.


What kernel/OS/driver are you using if it is software I can try to 
reproduce since I have a pretty similar card.


On the other hand: what goes in my case is not necessarily valid in 
yours.


In case it is is due to overheating this script will log temperature, 
power management and fan settings.


#!/bin/bash
cd /sys/class/drm/card0/device/hwmon/hwmon0
while `true`;
    do date;
    for x in fan1_enable fan1_input fan1_target pwm1 pwm1_enable 
temp1_input;

    do echo -n "$x: "; cat $x;
    done;
    echo; sleep 1;
done

Output will be the following about once a second:

Fri 28 Jan 2022 09:28:12 AM EST
fan1_enable: 0
fan1_input: 1714
fan1_target: 1714
pwm1: 0
pwm1_enable: 2
temp1_input: 36000

Also you can max out the fan to see if that helps:

echo 0 > /sys/class/drm/card0/device/hwmon/hwmon0/pwm1_enable

(If you can pwm1_enable after it will show 1 and not 0, but if you look 
at pwm1 it will be at max of 255).


Bijan



Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread hdv@gmail

On 2022-01-28 14:12, Pankaj Jangid wrote:

Pankaj Jangid  writes:


UPDATE:

I have changed the HDMI cable and since last 6hrs I have not faced that
event again. Will update in the thread if it re-appears.

Another thing happened when I was replacing the cable. I heard the
sparking noise in the power socket of monitor. So I tightened it up a
bit. So the loose power socket could also be the culprit in my case.

I am just waiting for another day and then I’ll try the earlier HDMI
cable again.


Nope. The problem still exists. I’ll change the power-chord now.



Like I wrote before: I exchanged all non-fixed components (mainly cable, 
ports, display, and slot on the mobo). Where that was not possible I 
made double-sure there was no mechanical source to the problems (bad 
cables, bad seating, corrosion, etc.). The only thing I did not change 
was the combination of the mobo and the graphics card. Maybe/probably I 
did not exclude the power component as a source. I can't remember 
whether I did or not.


I am reasonably sure the problem lies in some form or combination of 
software. Sadly, my expertise in that area is insufficient to find out 
what it is exactly.


On the other hand: what goes in my case is not necessarily valid in yours.

Grx HdV



Re: Screen goes blank for 1-2 seconds

2022-01-28 Thread Pankaj Jangid
Pankaj Jangid  writes:

> UPDATE:
>
> I have changed the HDMI cable and since last 6hrs I have not faced that
> event again. Will update in the thread if it re-appears.
>
> Another thing happened when I was replacing the cable. I heard the
> sparking noise in the power socket of monitor. So I tightened it up a
> bit. So the loose power socket could also be the culprit in my case.
>
> I am just waiting for another day and then I’ll try the earlier HDMI
> cable again.

Nope. The problem still exists. I’ll change the power-chord now.



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Pankaj Jangid
Pankaj Jangid  writes:

> Dan Ritter  writes:
>
>> Pankaj Jangid wrote: 
>>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>>> facing a very strange problem. The monitor goes blank for a brief time,
>>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>>> cable.
>>
>> I have seen this happen with loose or worn-out video cables. 
>
> Sure. Let me try another cable for a day. I’ll update here.

UPDATE:

I have changed the HDMI cable and since last 6hrs I have not faced that
event again. Will update in the thread if it re-appears.

Another thing happened when I was replacing the cable. I heard the
sparking noise in the power socket of monitor. So I tightened it up a
bit. So the loose power socket could also be the culprit in my case.

I am just waiting for another day and then I’ll try the earlier HDMI
cable again.




Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Bijan Soleymani

On 2022-01-27 5:30 a.m., hdv@gmail wrote:


Sadly I do not have access to this machine remotely. I do have my own 
VPN server, but that does not help when the machine in question is 
turned off. ;-)


I'll check the temperature when I am back, and when it happens again.


I played around a tiny bit.

My GPU temperature when logged in remotely via VNC was 29C.

Logging in on local system GPU went up to high 30s just on the desktop.

I ran a game and initially the temperature went.

pwm1 (the power management state) was 0 (off) until 53C when it got set 
to 43.


Temperature went up to 62C, and then dropped to 45C, and then pwm1 went 
back to 0.


Temp went back to 53C before the power management kicked in again.

I did:
echo 0 > pwm1_enable

Which apparently maxes the power management as:
pwm1 was now 255

Then I did:
echo 1 > pwm1_enable

This seemed more aggressive than the default setting of 2 on my system.

Looking at the kernel docs:
https://www.kernel.org/doc/Documentation/hwmon/g762

It seems 1 setting is open mode and 2 is closed mode.

In closed mode it seems there is some feedback mechanism involving the 
fan speed.


Undocumented but it seems setting pwm1_enable to 0, just maxes the power 
management out.


Turns out it is documented in the kernel source comments:
 *  0 : no fan speed control (i.e. fan at full speed)
 *  1 : manual fan speed control enabled (use pwm[1-*]) (open-loop)
 *  2+: automatic fan speed control enabled (use fan[1-*]_target) 
(closed-loop)


Anyways with all this playing around I got my temp down to 21C, when 
logged in locally but not running the game.


tl;dr

If anyone has this happen quickly enough you could try setting fan speed 
to max (echo 0 > pwm1_enable and check that pwm1 goes to 255) and see if 
it fixes it.


Bijan



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Pankaj Jangid
Tim Woodall  writes:

> For a while I was using a mac (running macOS) plugged into a dock with
> two HDMI screens connected and I was having this problem occasionally.
> The mac was clearly thinking the screens had "gone away" because it
> would move windows around. I've now switched to a windows laptop, same
> dock, same cables, same monitors and the problem has gone away.

So this may be a driver issue in macOS and Linux kernel.




Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Pankaj Jangid
Vincent Lefevre  writes:

> So it could be a hardware problem, with this monitor or something
> else, possibly specific to HDMI.
>
> I suggest that you try with another machine, another cable, etc. if
> possible. Or the same machine with another monitor.

I have multiple cables and an extra laptop. Let me try as many
combinations as possible. And report here.

>
> You might get messages in the /var/log/Xorg.0.log file if you're using X.
>

Where are the Wayland logs? I have a freshly installed Debian 11 and
default is Wayland.

> And I had noted that plugging out then in again the HDMI cable on the
> monitor side was generally making the problem disappear for some time.

The problem timing is very random so I am not sure if I can diagnose
anything by changing ports.



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Pankaj Jangid
"hdv@gmail"  writes:

> You are not the only one. I see the exact same here. The system this
> happens on has an RX560 graphics card. I have been seeing these
> blackouts from the start on this configuration (more than 2 years
> now).
>
> I can confirm it is not a mechanical issue (not of cable's
> connections, cable defects, or of the seating of the card in the
> motherboard). It is not the display either (I have tried multiple
> displays). I am almost sure it is a software issue.
>
> I can also confirm the system does not hang. I've tested this with a
> software timer and a request/response loop querying a daemon both
> locally and over a wired network.

Thanks for confirming.

Slight variation though. I have x570 chipset and RX580 GPU. I wrongly
typed RX570 GPU in the original email. But I guess the driver is same
for the family.




Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Pankaj Jangid
Dan Ritter  writes:

> Pankaj Jangid wrote: 
>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>> facing a very strange problem. The monitor goes blank for a brief time,
>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>> cable.
>> 
>> During that 1-2s, the machine response is fine. Whatever I type during
>> that time goes there as input, and visible when the monitor comes back.
>
> I have seen this happen with loose or worn-out video cables. 

Sure. Let me try another cable for a day. I’ll update here.



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Pankaj Jangid
Bijan Soleymani  writes:

> On 2022-01-26 11:35 p.m., Pankaj Jangid wrote> I don’t want to file
> any bug report till I have some concrete data. So
>> my question is - how do I diagnose such an issue and produce some data
>> for debugging. So that I can hand it over to maintainers.
>
> This one line script will sleep for 0.01 seconds at a time and then
> print the current time in milliseconds to a file.
>
> 

Thanks. I’ll use the script.




Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Pankaj Jangid
David Wright  writes:

> On Thu 27 Jan 2022 at 10:05:16 (+0530), Pankaj Jangid wrote:
>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>> facing a very strange problem. The monitor goes blank for a brief time,
>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>> cable.
>
> Can you provoke the same symptom by wiggling the HDMI plug in the
> socket (at either end, but more likely at the computer end)?
> These connectors can be unreliable.

No. This is not happening. In fact I have two GPUs and in total 4 HDMI
ports. In all of them, same symptoms. It happens twice or thrice a day
but sometimes more frequently.

This could be cable problem as pointed out by Dan Ritter. Trying a
different cable for a day.




Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Dan Ritter
Pankaj Jangid wrote: 
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
> 
> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.

I have seen this happen with loose or worn-out video cables. 

-dsr-



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Tim Woodall

On Thu, 27 Jan 2022, Vincent Lefevre wrote:


On 2022-01-27 11:41:44 +0100, Vincent Lefevre wrote:

On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:

Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
facing a very strange problem. The monitor goes blank for a brief time,
like 1-2s and then comes back. It is connected with the GPU using HDMI
cable.


I had a similar problem in 2009 with a monitor connected via HDMI to
a Power Mac (not under Linux). This first happened from time to time,
then much more often, i.e. every day. IIRC, there was no issue when
later, this monitor was connected to a Debian laptop via VGA. I sold
the monitor to someone else (and told him about this problem), and he
confirmed the problem with his machine.


And I had noted that plugging out then in again the HDMI cable on the
monitor side was generally making the problem disappear for some time.



For a while I was using a mac (running macOS) plugged into a dock with
two HDMI screens connected and I was having this problem occasionally.
The mac was clearly thinking the screens had "gone away" because it
would move windows around. I've now switched to a windows laptop, same
dock, same cables, same monitors and the problem has gone away.



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Vincent Lefevre
On 2022-01-27 11:41:44 +0100, Vincent Lefevre wrote:
> On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
> > Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> > facing a very strange problem. The monitor goes blank for a brief time,
> > like 1-2s and then comes back. It is connected with the GPU using HDMI
> > cable.
> 
> I had a similar problem in 2009 with a monitor connected via HDMI to
> a Power Mac (not under Linux). This first happened from time to time,
> then much more often, i.e. every day. IIRC, there was no issue when
> later, this monitor was connected to a Debian laptop via VGA. I sold
> the monitor to someone else (and told him about this problem), and he
> confirmed the problem with his machine.

And I had noted that plugging out then in again the HDMI cable on the
monitor side was generally making the problem disappear for some time.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Vincent Lefevre
On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.

I had a similar problem in 2009 with a monitor connected via HDMI to
a Power Mac (not under Linux). This first happened from time to time,
then much more often, i.e. every day. IIRC, there was no issue when
later, this monitor was connected to a Debian laptop via VGA. I sold
the monitor to someone else (and told him about this problem), and he
confirmed the problem with his machine.

So it could be a hardware problem, with this monitor or something
else, possibly specific to HDMI.

I suggest that you try with another machine, another cable, etc. if
possible. Or the same machine with another monitor.

> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.
> 
> I don’t want to file any bug report till I have some concrete data. So
> my question is - how do I diagnose such an issue and produce some data
> for debugging. So that I can hand it over to maintainers.

You might get messages in the /var/log/Xorg.0.log file if you're using X.

BTW, with my setup, I regularly get disconnected/connected messages
with 1-2 seconds delay, such as:

[166285.233] (--) NVIDIA(GPU-0): DFP-4: disconnected
[166285.233] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[166285.233] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[166285.233] (--) NVIDIA(GPU-0): 
[166286.614] (--) NVIDIA(GPU-0): Samsung U32J59x (DFP-4): connected
[166286.614] (--) NVIDIA(GPU-0): Samsung U32J59x (DFP-4): Internal DisplayPort
[166286.614] (--) NVIDIA(GPU-0): Samsung U32J59x (DFP-4): 960.0 MHz maximum 
pixel clock
[166286.614] (--) NVIDIA(GPU-0): 

I have 2 external monitors, this one connected via HDMI and another
one connected via DisplayPort (no messages in Xorg.0.log for this
other monitor). But I have never noticed any blank time with either
monitor. That's strange.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread hdv@gmail

On 2022-01-27 11:16, Bijan Soleymani wrote:

On 2022-01-27 5:00 a.m., hdv@gmail wrote:
My guess is about once every week. The display is on for roughly 16 
hours each day. There seems to be no discernable relation to "load". 
At least not that I could confirm. I haven't found a link to a 
specific application either. This system is a general purpose 
workstation and it is exposed to most common types of use. I design 
and create courseware, which involves running virtual machines with 
libvirt, coding in several languages, video editing, graphics editing, 
sound editing, editing all kinds of documents, and the standard 
internet stuff. I haven't seen this happening more often with any of 
these uses.


Thanks for the reply!

This blog post seems to indicate it might be due to the fan not turning 
on enough at moderate load by default (it pulses off and on which is not 
enough):

https://zarino.co.uk/post/amp-gpu-fan-curve-pop-os-ubuntu/

cat /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input

Should give temperature:
Mine right now is:
29000

which apparently is 29C.

/sys/class/drm/card0/device/hwmon/hwmon0/pwm1

is the power management.

I'll play around tomorrow.

Bijan


Sadly I do not have access to this machine remotely. I do have my own 
VPN server, but that does not help when the machine in question is 
turned off.  ;-)


I'll check the temperature when I am back, and when it happens again.

Grx HdV




Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Bijan Soleymani

On 2022-01-27 5:00 a.m., hdv@gmail wrote:
My guess is about once every week. The display is on for roughly 16 
hours each day. There seems to be no discernable relation to "load". At 
least not that I could confirm. I haven't found a link to a specific 
application either. This system is a general purpose workstation and it 
is exposed to most common types of use. I design and create courseware, 
which involves running virtual machines with libvirt, coding in several 
languages, video editing, graphics editing, sound editing, editing all 
kinds of documents, and the standard internet stuff. I haven't seen this 
happening more often with any of these uses.


Thanks for the reply!

This blog post seems to indicate it might be due to the fan not turning 
on enough at moderate load by default (it pulses off and on which is not 
enough):

https://zarino.co.uk/post/amp-gpu-fan-curve-pop-os-ubuntu/

cat /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input

Should give temperature:
Mine right now is:
29000

which apparently is 29C.

/sys/class/drm/card0/device/hwmon/hwmon0/pwm1

is the power management.

I'll play around tomorrow.

Bijan



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread hdv@gmail

On 2022-01-27 10:40, Bijan Soleymani wrote:


On 2022-01-27 4:23 a.m., Bijan Soleymani wrote:
Are you also connected via HDMI? I think I am using DVI to mini 
display port.


I will have to check when I return home from this assignment in 2 weeks 
time, but I am almost certain I am using DP. I seem to remember I didn't 
have the appropriate HDMI cable at hand for the resolution I am using 
(3840x2160@60Hz).



Seems the issues happens on windows and on HDMI but not DP:
https://www.reddit.com/r/AMDHelp/comments/ez2c4i/rx_570_screen_randomly_goes_black_during/ 


I will check if my wet memory is corrupt as soon as I can. Who knows? 
Maybe I am using HDMI after all.



Two other cases:
https://www.reddit.com/r/AMDHelp/comments/o1r0y9/screen_goes_to_black_randomly_while_gaming_rx_570/ 



That one says upgrading the power supply fixed it.

https://forums.tomshardware.com/threads/screen-goes-black-for-3-5-seconds-then-goes-back.3397019/ 



This one said they had the card replaced.

Anyways I will test with HDMI tomorrow.

Let me know how often it happens, or if there is anything that can be 
done to trigger it.


My guess is about once every week. The display is on for roughly 16 
hours each day. There seems to be no discernable relation to "load". At 
least not that I could confirm. I haven't found a link to a specific 
application either. This system is a general purpose workstation and it 
is exposed to most common types of use. I design and create courseware, 
which involves running virtual machines with libvirt, coding in several 
languages, video editing, graphics editing, sound editing, editing all 
kinds of documents, and the standard internet stuff. I haven't seen this 
happening more often with any of these uses.


Grx HdV



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Bijan Soleymani



On 2022-01-27 4:23 a.m., Bijan Soleymani wrote:
Are you also connected via HDMI? I think I am using DVI to mini display 
port.


Seems the issues happens on windows and on HDMI but not DP:
https://www.reddit.com/r/AMDHelp/comments/ez2c4i/rx_570_screen_randomly_goes_black_during/

Two other cases:
https://www.reddit.com/r/AMDHelp/comments/o1r0y9/screen_goes_to_black_randomly_while_gaming_rx_570/

That one says upgrading the power supply fixed it.

https://forums.tomshardware.com/threads/screen-goes-black-for-3-5-seconds-then-goes-back.3397019/

This one said they had the card replaced.

Anyways I will test with HDMI tomorrow.

Let me know how often it happens, or if there is anything that can be 
done to trigger it.


Bijan



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread Bijan Soleymani

On 2022-01-27 4:06 a.m., hdv@gmail wrote:
You are not the only one. I see the exact same here. The system this 
happens on has an RX560 graphics card. I have been seeing these 
blackouts from the start on this configuration (more than 2 years now).


Interesting, I just checked and it turns out I have a:
Sapphire Technology Limited Radeon RX 570 Pulse 4GB

But I don't think I've seen the issue.

Let me know what kernel/drivers (plus exact OS version) you guys are 
using and I can try to see if I can reproduce it.


Also let me know how often this happens.

I can confirm it is not a mechanical issue (not of cable's connections, 
cable defects, or of the seating of the card in the motherboard). It is 
not the display either (I have tried multiple displays). I am almost 
sure it is a software issue.


Are you also connected via HDMI? I think I am using DVI to mini display 
port.


I can also confirm the system does not hang. I've tested this with a 
software timer and a request/response loop querying a daemon both 
locally and over a wired network.


Good to know!

Bijan



Re: Screen goes blank for 1-2 seconds

2022-01-27 Thread hdv@gmail

On 2022-01-27 05:35, Pankaj Jangid wrote:

Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
facing a very strange problem. The monitor goes blank for a brief time,
like 1-2s and then comes back. It is connected with the GPU using HDMI
cable.

During that 1-2s, the machine response is fine. Whatever I type during
that time goes there as input, and visible when the monitor comes back.

I don’t want to file any bug report till I have some concrete data. So
my question is - how do I diagnose such an issue and produce some data
for debugging. So that I can hand it over to maintainers.

Regards
Pankaj


You are not the only one. I see the exact same here. The system this 
happens on has an RX560 graphics card. I have been seeing these 
blackouts from the start on this configuration (more than 2 years now).


I can confirm it is not a mechanical issue (not of cable's connections, 
cable defects, or of the seating of the card in the motherboard). It is 
not the display either (I have tried multiple displays). I am almost 
sure it is a software issue.


I can also confirm the system does not hang. I've tested this with a 
software timer and a request/response loop querying a daemon both 
locally and over a wired network.


Grx HdV



Re: Screen goes blank for 1-2 seconds

2022-01-26 Thread Bijan Soleymani
On 2022-01-26 11:35 p.m., Pankaj Jangid wrote> I don’t want to file any 
bug report till I have some concrete data. So

my question is - how do I diagnose such an issue and produce some data
for debugging. So that I can hand it over to maintainers.


This one line script will sleep for 0.01 seconds at a time and then 
print the current time in milliseconds to a file.


while `true`; do sleep 0.01; date +"%T.%3N" ; done > time.txt

Run that and look at the output in time.txt afterwards to make sure the 
system didn't actually stop. (even if it stopped it might still be a 
graphics issue, but at least it's another data point).


Output will look like:
23:41:20.670
23:41:20.686
23:41:20.701
23:41:20.715
23:41:20.732
23:41:20.749
23:41:20.766
23:41:20.785
23:41:20.803
23:41:20.821

(due to the overhead of running sleep and date there's more than 0.01 
seconds per iteration)


This script will give you the biggest time differences:
perl -e 'while(<>){chomp; $old_time = $time; $time = $_; $old_ms = 
$cur_ms ; $_ =~ s/.*[.]//; $cur_ms = $_; $delta = $cur_ms - $old_ms; 
$delta = $delta % 1000; if (defined($old_ms)){print "$delta: $old_time 
$time\n";}}' < time.txt  | sort -n | tail


The output is:
20: 23:50:50.384 23:50:50.404
20: 23:50:51.036 23:50:51.056
20: 23:51:06.262 23:51:06.282
20: 23:51:46.577 23:51:46.597
21: 23:50:42.553 23:50:42.574
21: 23:50:43.999 23:50:44.020
24: 23:50:59.126 23:50:59.150
25: 23:50:41.680 23:50:41.705
25: 23:50:50.192 23:50:50.217
25: 23:50:53.255 23:50:53.280

So in my case the biggest delay was 25ms (at time 23:50:53). If you see 
anything longer than 100ms you'll know the system has gotten stuck 
during the blank interval.


Bijan



Re: Screen goes blank for 1-2 seconds

2022-01-26 Thread David Wright
On Thu 27 Jan 2022 at 10:05:16 (+0530), Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
> 
> During that 1-2s, the machine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.
> 
> I don’t want to file any bug report till I have some concrete data. So
> my question is - how do I diagnose such an issue and produce some data
> for debugging. So that I can hand it over to maintainers.

Can you provoke the same symptom by wiggling the HDMI plug in the
socket (at either end, but more likely at the computer end)?
These connectors can be unreliable.

Cheers,
David.



Re: Screen scaling and 4k support in libvirt with qemu/kvm

2021-01-28 Thread Rainer Dorsch
Am Mittwoch, 27. Januar 2021, 10:55:53 CET schrieb Linux-Fan:
> Linux-Fan writes:
> > Rainer Dorsch writes:
> >> Hi,
> >> 
> >> with virtualbox, it is possible that the guest system rescales its screen
> >> if I change the window for the guest (and virtualbox guest tools are
> >> installed at
> >> least). Does anybody know if that is possible with
> >> virt-manager/libvirt/qemu/ kvm?
> > 
> > It is certainly possible to set the guest resolution to exactly match the
> > window size. I am not sure if it can be configured to _automatically_
> > adjust the guest resolution upon window size change though.
> > 
> > The protocol must support it, because I know that for Windows guest
> > systems, the Windows resolution adjusts to the window size. Unlike with
> > Linux guests, it does this in fixed steps of "common" monitor resolutions
> > and thus does not usually match the exact window size but something
> > smaller.
> > 
> > If you find out how to apply the sizes automatically on Linux, I'd be
> > interested to learn how that works :) If no „solution” exists yet, it
> > might
> > be easy to script (although I have not bothered to do that so far).
> 
> Update: I found out how to enable automatic resizing:
> 
>  * Install `qemu-guest-agent` in the VM in addition to running
>`spice-vdagent`
>  * Set Video model to VGA
> 
> This enables automatic resizing here although from "feeling" the graphics
> performance is worse than with QXL or virtio.

Many thanks for the quick response again.

I did not have spice-vdagent installed in the guest system. Installing spice-
vdagent and switching from QXL to virtio was sufficient here.

Interesting side effect:

On the host system, I get

rd@h370:~$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192
HDMI-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y 
axis) 609mm x 349mm
   3840x2160 30.00*   25.0024.0029.9723.98  
   2560x1440 59.95  
   2048x1280 59.99  
   2048x1080 24.00  
   1920x1080 60.0060.0050.0059.9430.0025.0024.00
29.9723.98  
   1920x1080i60.0050.0059.9450.00  
   1600x1200 60.00  
   1600x900  60.00  
   1280x1024 75.0260.02  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   720x480i  60.0059.94  
   640x480   75.0060.0059.94  
   720x400   70.08  
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
rd@h370:~$ 

After installing spice-vdagent on the guest, I get there

rd@debianVM:~$ xrandr 
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
Virtual-0 connected primary 1920x1080+0+0 0mm x 0mm
   3840x2160 60.00 +
   1920x1200 59.95  
   1920x1080 60.00* 
   1600x1200 59.95  
   1680x1050 60.00  
   1400x1050 60.00  
   1280x1024 59.95  
   1440x900  59.99  
   1280x960  59.99  
   1280x854  59.95  
   1280x800  59.96  
   1280x720  59.97  
   1152x768  59.95  
   1024x768  59.95  
   800x600   59.96  
   848x480   59.94  
   720x480   59.94  
   640x480   59.94  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected
rd@debianVM:~$


Note, the repetition rate (at least virtually) doubles in the guest at 4K.

Pretty cool!

Thanks again
Rainer


-- 
Rainer Dorsch
http://bokomoko.de/




Re: Screen scaling and 4k support in libvirt with qemu/kvm

2021-01-27 Thread Linux-Fan

Linux-Fan writes:


Rainer Dorsch writes:


Hi,

with virtualbox, it is possible that the guest system rescales its screen if  
I change the window for the guest (and virtualbox guest tools are installed  
at

least). Does anybody know if that is possible with virt-manager/libvirt/qemu/
kvm?


It is certainly possible to set the guest resolution to exactly match the  
window size. I am not sure if it can be configured to _automatically_ adjust  
the guest resolution upon window size change though.


The protocol must support it, because I know that for Windows guest systems,  
the Windows resolution adjusts to the window size. Unlike with Linux guests,  
it does this in fixed steps of "common" monitor resolutions and thus does  
not usually match the exact window size but something smaller.


If you find out how to apply the sizes automatically on Linux, I'd be  
interested to learn how that works :) If no „solution” exists yet, it might  
be easy to script (although I have not bothered to do that so far).


Update: I found out how to enable automatic resizing:

* Install `qemu-guest-agent` in the VM in addition to running
  `spice-vdagent`
* Set Video model to VGA

This enables automatic resizing here although from "feeling" the graphics  
performance is worse than with QXL or virtio.


HTH
Linux-Fan

öö


pgpxa2xrz2c0D.pgp
Description: PGP signature


Re: Screen scaling and 4k support in libvirt with qemu/kvm

2021-01-27 Thread Linux-Fan

Rainer Dorsch writes:


Hi,

with virtualbox, it is possible that the guest system rescales its screen if  
I change the window for the guest (and virtualbox guest tools are installed at

least). Does anybody know if that is possible with virt-manager/libvirt/qemu/
kvm?


It is certainly possible to set the guest resolution to exactly match the  
window size. I am not sure if it can be configured to _automatically_ adjust  
the guest resolution upon window size change though.


The protocol must support it, because I know that for Windows guest systems,  
the Windows resolution adjusts to the window size. Unlike with Linux guests,  
it does this in fixed steps of "common" monitor resolutions and thus does  
not usually match the exact window size but something smaller.


If you find out how to apply the sizes automatically on Linux, I'd be  
interested to learn how that works :) If no „solution” exists yet, it might  
be easy to script (although I have not bothered to do that so far).


My usual approach to bypass guest system screen resolution issues is to use  
ssh -X from the host to the guest and then run the program under the host's  
X11 session.



Also I noticed that I cannot scale my guest higher than 1920x1200. Is the max
resolution configured somewhere or is this a fundamental limitation?


This very much sounds like you are either using the VGA video adapter or do  
not have `spice-vdagent` running in the guest system?


Set Video "Model" to either QXL or virtio in virt-manager and then in the  
guest system install and run `spice-vdagent`. This will not apply the  
resolution immediately, but invoking `xrandr` in the guest it should be  
possible to see a lot larger list of virtual screen resolutions including  
one to match the host window size and including sizes above 1920x1200.


HTH
Linux-Fan

öö

[...]


pgpHH0VkHwaRq.pgp
Description: PGP signature


Re: screen doesn't lock anymore when lid closed

2020-04-16 Thread scar

I also tried adding HandleLidSwitchExternalPower=lock and now i have commented 
both out and made a new file /etc/systemd/logind.d/lidswitch.conf with:
HandleLidSwitch=lock
HandleLidSwitchExternalPower=lock

rebooted and it still is ignored.



Re: screen color distortion after xrandr

2020-01-08 Thread Felmon Davis

On Wed, 8 Jan 2020, David Wright wrote:


It sounds to me more like a Desktop problem: I don't know how to make
the effects of xrandr stick like that.

I would investigate where the settings are being kept by:

1) check you have a bash prompt available somewhere, eg a VC.
2) make some change with xrandr (any change).
3) save the configuration.
4) run the line:  find ~ -type f -mmin -3


sounds good! (I overlooked this email, sorry.)

will try the experiment tomorrow.

f.


where 3 is the number of minutes within which you saved the configuration.
It will print the names of any files under your home directory that
have been modified within the last three minutes.

Not running a DE, I can't be more specific than that.

Cheers,
David.





--
Felmon Davis

Verbum sat sapienti.



Re: screen color distortion after xrandr

2020-01-08 Thread David Wright
On Wed 08 Jan 2020 at 22:03:37 (-0500), Dan Ritter wrote:
> David Wright wrote: 
> > For some reason, debian-user rejected this post (and will inform me in
> > due course), so I'm posting it again.
> > 
> > > It sounds to me more like a Desktop problem: I don't know how to make
> > > the effects of xrandr stick like that.
> > > 
> > > I would investigate where the settings are being kept by:
> > > 
> > > 1) check you have a bash prompt available somewhere, eg a VC.
> > > 2) make some change with xrandr (any change).
> > > 3) save the configuration.
> > > 4) run the line:  find ~ -type f -mmin -3
> > > 
> > > where 3 is the number of minutes within which you saved the configuration.
> > > It will print the names of any files under your home directory that
> > > have been modified within the last three minutes.
> > > 
> > > Not running a DE, I can't be more specific than that.
> 
> 
> Yeah, the thing is that xrandr doesn't have a step 3. It acts
> immediately. The usual save mechanism is to call a script from
> .xinitrc or such that invokes the parameters you want.

No, it doesn't, but I thought the DE was doing the saving when
Felmon pressed the 'save this configuration' key.

> Once I pointed this out, the original poster realized that he
> wasn't actually running xrandr.

I know so little about DEs; I hadn't even realised that
that was the implication of Felmon's using Q4os.

Cheers,
David.



Re: screen color distortion after xrandr

2020-01-08 Thread Dan Ritter
David Wright wrote: 
> For some reason, debian-user rejected this post (and will inform me in
> due course), so I'm posting it again.
> 
> > It sounds to me more like a Desktop problem: I don't know how to make
> > the effects of xrandr stick like that.
> > 
> > I would investigate where the settings are being kept by:
> > 
> > 1) check you have a bash prompt available somewhere, eg a VC.
> > 2) make some change with xrandr (any change).
> > 3) save the configuration.
> > 4) run the line:  find ~ -type f -mmin -3
> > 
> > where 3 is the number of minutes within which you saved the configuration.
> > It will print the names of any files under your home directory that
> > have been modified within the last three minutes.
> > 
> > Not running a DE, I can't be more specific than that.


Yeah, the thing is that xrandr doesn't have a step 3. It acts
immediately. The usual save mechanism is to call a script from
.xinitrc or such that invokes the parameters you want.

Once I pointed this out, the original poster realized that he
wasn't actually running xrandr.

-dsr-



Re: screen color distortion after xrandr

2020-01-08 Thread David Wright
For some reason, debian-user rejected this post (and will inform me in
due course), so I'm posting it again.

On Wed 08 Jan 2020 at 08:28:35 (-0600), David Wright wrote:
> On Wed 08 Jan 2020 at 14:24:12 (+0100), Felmon Davis wrote:
> > I was trying to get a second monitor (a tv) to work using xrandr. I
> > noticed that the screen on the laptop would suffer severe, almost
> > 'psychedelic', effects if I hit a certain setting.
> > 
> > unfortunately I don't recall the setting but the ill effect was
> > consistent and rendered the display nearly unreadable. and the only
> > solution was to end the session.
> > 
> > then by accident I hit the 'save this configuration' key and now the
> > setting is permanent.
> > 
> > btw I created a second user and it doesn't suffer from the problem.
> > 
> > I cannot find a way to restore the proper display setting. there's no
> > configuration file I can find for xrandr.
> > 
> > it's an Asus Zenbook with Intel HD graphics.
> > 
> > I am considering shifting to the second user and grappling with the
> > UID and GID changes. I ultimately want to get back to using the
> > original username.
> > 
> > surely there is a simpler solution. perhaps purge xrandr?
> 
> It sounds to me more like a Desktop problem: I don't know how to make
> the effects of xrandr stick like that.
> 
> I would investigate where the settings are being kept by:
> 
> 1) check you have a bash prompt available somewhere, eg a VC.
> 2) make some change with xrandr (any change).
> 3) save the configuration.
> 4) run the line:  find ~ -type f -mmin -3
> 
> where 3 is the number of minutes within which you saved the configuration.
> It will print the names of any files under your home directory that
> have been modified within the last three minutes.
> 
> Not running a DE, I can't be more specific than that.
> 
> Cheers,
> David.



Re: screen color distortion after xrandr

2020-01-08 Thread Charles Curley
On Wed, 8 Jan 2020 10:09:44 -0500
Dan Ritter  wrote:

> What *randr program were you using?
> 
> arandr

If arandr, look in ~/.screenlayout/

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/



Re: screen color distortion after xrandr

2020-01-08 Thread Felmon Davis

ryOn Wed, 8 Jan 2020, Dan Ritter wrote:


Felmon Davis wrote:

greets!

I was trying to get a second monitor (a tv) to work using xrandr. I noticed
that the screen on the laptop would suffer severe, almost 'psychedelic',
effects if I hit a certain setting.

unfortunately I don't recall the setting but the ill effect was consistent
and rendered the display nearly unreadable. and the only solution was to end
the session.

then by accident I hit the 'save this configuration' key and now the setting
is permanent.

btw I created a second user and it doesn't suffer from the problem.

I cannot find a way to restore the proper display setting. there's no
configuration file I can find for xrandr.

it's an Asus Zenbook with Intel HD graphics.

I am considering shifting to the second user and grappling with the UID and
GID changes. I ultimately want to get back to using the original username.

surely there is a simpler solution. perhaps purge xrandr?


xrandr doesn't have a "save this configuration" key; it is
command-line only.

What *randr program were you using?

arandr

lxrandr

something built in to a desktop environment?


ok, that's a very good tip! I'm using on this laptop an environment 
called Q4os (which is based on Trinity Desktop, a debian branch).


I'll ask on the Trinity list.

f.

--
Felmon Davis

Verbum sat sapienti.



Re: screen color distortion after xrandr

2020-01-08 Thread Dan Ritter
Felmon Davis wrote: 
> greets!
> 
> I was trying to get a second monitor (a tv) to work using xrandr. I noticed
> that the screen on the laptop would suffer severe, almost 'psychedelic',
> effects if I hit a certain setting.
> 
> unfortunately I don't recall the setting but the ill effect was consistent
> and rendered the display nearly unreadable. and the only solution was to end
> the session.
> 
> then by accident I hit the 'save this configuration' key and now the setting
> is permanent.
> 
> btw I created a second user and it doesn't suffer from the problem.
> 
> I cannot find a way to restore the proper display setting. there's no
> configuration file I can find for xrandr.
> 
> it's an Asus Zenbook with Intel HD graphics.
> 
> I am considering shifting to the second user and grappling with the UID and
> GID changes. I ultimately want to get back to using the original username.
> 
> surely there is a simpler solution. perhaps purge xrandr?

xrandr doesn't have a "save this configuration" key; it is
command-line only.

What *randr program were you using?

arandr

lxrandr

something built in to a desktop environment?

-dsr-



Re: Screen resolution during Stretch installation

2019-03-01 Thread Étienne Mollier
On 3/1/19 4:20 PM, Fabiano Ferronato wrote:
> I'm installing Debian in my Asus ROG GL552VW laptop (Intel and
> Nvidia video cards) and the resolution (probably 3840x2160)is
> set in a way  that the font size is so small that I have to
> almost  put my face on the monitor so I can read. And the
> windows size is also larger than the monitor area, so I can't
> see the buttons. I can complete the installation either way,
> but I want to know why this is happening and how to solve
> this.
[...]
> Where I can change the screen resolution during (or before)
> install?

Good Day,

In the Grub menu, where you are prompted to choose between
Graphical install, Install, and so on, you can hit 'e' to edit
the Grub entry and prepend the line:

set gfxpayload=keep

Then hit 'F10' to proceed to the installation.

This will conserve the resolution used by this menu, which
should be readable, contrary to the following steps.  Other
values should be possible if you want a better, still readable,
resolution:

set gfxpayload=1280x1024x32

This may answer at least the first question, hopefully.

Kind Regards,
-- 
Étienne Mollier 

All opinions are my own.



Re: Screen resolution during Stretch installation

2019-03-01 Thread Pascal Hambourg

Le 01/03/2019 à 18:30, Felix Miata a écrit :


Including either nomodeset or nouveau.modeset=0 for installation


is pointless, since the installer does not use KMS.


Another key is the i7-6700HQ provides HD 530 Intel video. Intel + NVidia 
usually equates to
"Optimus"


which makes nouveau.modeset=0 even more pointless, since only the Intel 
GPU drives the video outputs and may use KMS.




Re: Screen resolution during Stretch installation

2019-03-01 Thread Felix Miata
Fabiano Ferronato composed on 2019-03-01 16:20 (UTC+0100):

> I don't know if this is the wright place to ask, but I'm searching a lot
> trying to find a way to this problem.
> I'm installing Debian in my Asus ROG GL552VW laptop (Intel and Nvidia video
> cards) and the resolution (probably 3840x2160)is set in a way  that the
> font size is so small that I have to almost  put my face on the monitor so
> I can read. And the windows size is also larger than the monitor area, so I
> can't see the buttons. I can complete the installation either way, but I
> want to know why this is happening and how to solve this.
> After OS install, I try to follow Debian instructions to install Nvidia
> drivers. But I'm following every tutorial and ending up with a broken
> installation.

> So, my questions:
> Where I can change the screen resolution during (or before) install?
> After install, resolution is still wrong. How can I set OS resolution
> during install?

An alternative suggestion to Curt's is to utilize the kernel's KMS. Curt's 
suggestion included
disabling KMS with either the nomodeset or nouveau.modeset=0 string on the 
installer's cmdline.
Including video=2560x1440 or video=1920x1080 should increase the font sizes 
without disabling KMS.

Including either nomodeset or nouveau.modeset=0 for installation generally 
means its included in
/etc/default/grub and /boot/grub/grub.cfg on the installed system, continuing 
KMS blockage, and
making video performance suffer greatly. Both are intended as troubleshooting 
workarounds, though
traditionally, non-FOSS drivers have required disabling KMS full time.

Another key is the i7-6700HQ provides HD 530 Intel video. Intel + NVidia 
usually equates to
"Optimus", which generally means a requirement to follow special instructions 
for installing either
OS or NVidia drivers. These you can find by using Optimus, Prime and Bumblebee 
as search keywords.
Optimus instructions on https://wiki.archlinux.org/index.php/Optimus are 
reputedly very good, in
case any you find for Debian seem inadequate to task.

Note too that there are three potentially competent DDX drivers for NVidia, the 
non-FOSS from
NVidia, plus the two from Xorg, nouveau and modesetting. The newer technology 
modesetting is the
upstream default, included in the server package since 4 years ago, but most 
installations manage
to override it by installing all optional DDX drivers via virtual (meta) 
package, including
xserver-xorg-video-nouveau. BTW, upstream's name for DDX drivers takes the form
xf86-video-, helpful to know in evaluating search results.

Having the nouveau DDX installed blocks the modesetting DDX unless explicitly 
configured not to via
/etc/X11/xorg.conf*. IOW, if you purge xserver-xorg-video-nouveau, or 
explicitly configure its use,
before installing NVidia drivers, you get an opportunity to test whether you 
even need to add the
non-FOSS DDX.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/



Re: Screen resolution during Stretch installation

2019-03-01 Thread Curt
On 2019-03-01, Fabiano Ferronato  wrote:
>
> Hi all!
>
> I don't know if this is the wright place to ask, but I'm searching a lot
> trying to find a way to this problem.
> I'm installing Debian in my Asus ROG GL552VW laptop (Intel and Nvidia video
> cards) and the resolution (probably 3840x2160)is set in a way  that the
> font size is so small that I have to almost  put my face on the monitor so
> I can read. And the windows size is also larger than the monitor area, so I
> can't see the buttons. I can complete the installation either way, but I
> want to know why this is happening and how to solve this.
> After OS install, I try to follow Debian instructions to install Nvidia
> drivers. But I'm following every tutorial and ending up with a broken
> installation.
>

This reddit thread I stumbled on seems pertinent to your case:

https://www.reddit.com/r/linuxquestions/comments/8f9slp/cant_install_any_linux_distro_on_my_asus_rog/

Apparently the key is to set the "nomodeset" boot parameter at the boot
prompt. 


-- 
“Let us again pretend that life is a solid substance, shaped like a globe,
which we turn about in our fingers. Let us pretend that we can make out a plain
and logical story, so that when one matter is despatched--love for instance--
we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves



Re: screen freeze when attaching external screen through the dock.

2018-03-29 Thread BRINER Cédric
The screen does not freeze on X.org.

Where should I report this bug ?

cED



Re: screen freeze when attaching external screen through the dock.

2018-03-29 Thread BRINER Cédric
Hi,

I've looked at the files, and let me show you what I found supicious

in syslog, I've found a lot of:
Mar 29 08:14:20 cedian gvfsd[1697]: Error calling
org.gtk.vfs.MonitorClient.Changed(): Le délai d’attente est dépassé
(g-io-error-quark, 24)

all the logs are in :
https://paste.debian.net/1017405/


-- 
BRINER Cédric, Ing. EPFL & HES
System Administrator, central IT, University of Geneva
+41 22 / 379 71 83



Re: screen freeze when attaching external screen through the dock.

2018-03-28 Thread Abdullah Ramazanoglu
On Tue, 27 Mar 2018 14:45:18 +0200 BRINER Cédric said:

> Which file should I look to to better investigate the topic ?

One of these files might have logged a relevant message just before the
freeze:

/var/log/sylog*
/var/log/messages* 
/var/log/debug*
/var/log/kern.log*

Regards
-- 
Abdullah Ramazanoglu




Re: Screen goes blank after "EDID checksum is invalid" errors

2015-09-06 Thread Johannes Bauer
On 06.09.2015 19:40, Stephen Powell wrote:

> The OP said that what he included in this problem report came from
> another problem report, because it scrolled off the screen too fast
> for him to give actual data.

True, but it was pretty damn close (lots of 0xffs)

>  (Perhaps he doesn't know about
> "dmesg|less".)

Oh I do but of course didn't think to check :-/ At the time I fired off
the posting I had actually just discovered that the system was still
alive (I thought it was ooopsing and unresponsive, the hardware has no
indicators whatsoever, so there's that).

Since I don't need fancy graphics or let alone X on that system, I
figured out that the module gma500_gfx was causing the problems in my
case. I just blacklisted the sucker and the problem's gone.

Just for info, here's what happens when I modprobe it manually
(accompanied with a blanked screen):

[  750.356470] [drm] Initialized drm 1.1.0 20060810
[  750.412907] ACPI: Video Device [GFX0] (multi-head: yes  rom: no
post: no)
[  750.413121] [Firmware Bug]: ACPI: No _BQC method, cannot determine
initial brightness
[  750.416940] acpi device:03: registered as cooling_device2
[  750.425323] acpi device:04: registered as cooling_device3
[  750.425586] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input11
[  750.432866] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[  750.432895] [drm] No driver support for vblank timestamp query.
[  750.552062] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 130
[  750.552096] Raw EDID:
[  750.552109]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  750.552126]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.552142]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.552159]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.552175]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.552192]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.552209]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.552225]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.656185] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 130
[  750.656252] Raw EDID:
[  750.656282]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  750.656319]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.656356]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.656393]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.656430]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.656467]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.656504]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.656541]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.765320] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 130
[  750.765391] Raw EDID:
[  750.765422]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  750.765459]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.765496]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.765533]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.765570]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.765607]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.765644]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.765681]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869209] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 130
[  750.869271] Raw EDID:
[  750.869300]  00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  750.869336]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869373]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869410]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869447]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869484]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869521]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869558]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  750.869601] gma500 :00:02.0: LVDS-1: EDID block 0 invalid.
[  751.338582] gma500 :00:02.0: trying to get vblank count for
disabled pipe 0
[  751.338656] gma500 :00:02.0: trying to get vblank count for
disabled pipe 0
[  751.440308] fbcon: psbdrmfb (fb0) is primary device
[  751.812576] Console: switching to colour frame buffer device 128x48
[  751.823950] gma500 :00:02.0: fb0: psbdrmfb frame buffer device
[  751.824106] gma500 :00:02.0: registered panic notifier
[  751.832812] gma500 :00:02.0: Backlight lvds set brightness 7a127a12
[  751.832988] [drm] Initialized gma500 1.0.0 20140314 for :00:02.0
on minor 0
[  751.841560] gma500 :00:02.0: Backlight lvds set brightness 7a127a12

Also note that the kernel actually oopse

Re: Screen goes blank after "EDID checksum is invalid" errors

2015-09-06 Thread Felix Miata
Johannes Bauer composed on 2015-09-06 11:45 (UTC+0200):

> not sure if this is the right newsgroup, but it's worth a shot.

> I've just installed Jessie i586 on an Intel Atom board. The board has
> has DVI output which is connected to a monitor.

> When booting, I can perfectly see the image during grub2 and also during
> early printk. Then comes the handoff to userspace (/bin/init), it
> executes some stuff (much too fast for me to see) and then I see some of
> these messages (they're copied from another problem report, but look
> exactly like this):

> [2.123456] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
> invalid, remainder is 43...

> This message comes about 3-4 times within 500ms (all guessed values, it
> all runs very fast), then the screen goes dark.

> My guess is that it's trying to do some font switching or frame buffer
> stuff, can't read what the monitor has to offer and switches to a weird
> setting. The system is alive (can ssh into it), but I'd like console
> output as well.

> So I've tried adding "nomodeset", "nofb" and "vga=normal" to my kernel
> cmdline, changed grub to GRUB_TERMINAL=console. The problem remains.

Grub2 complains about deprecation when I use it, but nevertheless, vga= seems
to do what it always did, at least on legacy x86: vga=788, vga=791 or
vga=794. I have no Atoms to try on. OTOH, vga=normal results in no
framebuffer device, so may be counter productive.

If the DVI is connected to a typical LCD, video= on cmdline ought to work:
e.g. video=1024x768@60 or equivalent to match your display's native mode. I
routinely use video= to override native mode on vttys to produce bigger text
than what the default framebuffer size produces using native mode.

> Can anyone's crystal ball reveal some clues on what's going on here and
> how I could fix that?

Is this exclusively a vtty problem, or both vtty and Xorg?

If only vttys, as I mentioned earlier, is plymouth installed? Does noplymouth
added to cmdline help? If it's not installed, does installing plymouth help?

IIRC, WRT Xorg, I've never been unable to work around bad EDID by providing a
simple /etc/X11/xorg.conf from which Xorg will calculate a desirable result.
A template:

http://fm.no-ip.com/Share/Linux/xorg.conf-minimal-EDID-workaround
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/



Re: Screen goes blank after "EDID checksum is invalid" errors

2015-09-06 Thread Stephen Powell
On Sun, 06 Sep 2015 08:07:32 -0400 (EDT), Sven Joachim wrote:
> 
> On 2015-09-06 12:31 +0200, Stephen Powell wrote:
>> Some monitors have invalid EDID checksums.  Blame the manufacturer.
>> Windows is more tolerant of EDID checksum errors than Linux is.
>> If switching monitors solves your problem, then a bona fide EDID checksum
>> error in the hardware is probably to blame.  If you're willing to
>> build a custom kernel, you may be able to circumvent the problem by applying 
>> a
>> patch.  See my kernel-building web page:
>>
>>http://users.wowway.com/~zlinuxman/Kernel.htm
>>
>> In "Step 7: Patch the kernel", there is a specific example of how to apply
>> this patch.  Basically, it allows you to tell the kernel to ignore EDID
>> check sum errors by using the following setting in a file with the extension
>> of ".conf" under /etc/modprobe.d:
>>
>>options drm edid_strict=0
>>
>> This may allow you to use your faulty monitor anyway.  Good luck.
> 
> I don't think this is a very good idea in this case, the EDID of
> Johannes' monitor seems to be very broken (almost all bytes are 0xff).
> Rather than patching the kernel to not complain about that, it is
> probably better to supply valid EDID data via the
> drm_kms_helper.edid_firmware option.
> 
> The downside of this approach is that you have to supply the EDID
> file, there are several under Documentation/EDID/ in the kernel
> source (assembly source and a Makefile).

The OP said that what he included in this problem report came from
another problem report, because it scrolled off the screen too fast
for him to give actual data.  (Perhaps he doesn't know about
"dmesg|less".)  So I wouldn't give too much credence to the content
of the posted EDID data.  Nevertheless, I agree that the approach you
suggested above is a better solution, if the needed firmware file can
be found.

I didn't know about the drm kms_helper.edid option, so I've learned
something new.  Thanks, Sven.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



Re: Screen goes blank after "EDID checksum is invalid" errors

2015-09-06 Thread Sven Joachim
On 2015-09-06 12:31 +0200, Stephen Powell wrote:

> On Sun, 06 Sep 2015 05:45:30 -0400 (EDT), Johannes Bauer wrote:
>> 
>> [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 43
>
> Some monitors have invalid EDID checksums.  Blame the manufacturer.
> Windows is more tolerant of EDID checksum errors than Linux is.
> If switching monitors solves your problem, then a bona fide EDID checksum
> error in the hardware is probably to blame.  If you're willing to
> build a custom kernel, you may be able to circumvent the problem by applying a
> patch.  See my kernel-building web page:
>
>http://users.wowway.com/~zlinuxman/Kernel.htm
>
> In "Step 7: Patch the kernel", there is a specific example of how to apply
> this patch.  Basically, it allows you to tell the kernel to ignore EDID
> check sum errors by using the following setting in a file with the extension
> of ".conf" under /etc/modprobe.d:
>
>options drm edid_strict=0
>
> This may allow you to use your faulty monitor anyway.  Good luck.

I don't think this is a very good idea in this case, the EDID of
Johannes' monitor seems to be very broken (almost all bytes are 0xff).
Rather than patching the kernel to not complain about that, it is
probably better to supply valid EDID data via the
drm_kms_helper.edid_firmware option.

The downside of this approach is that you have to supply the EDID
file, there are several under Documentation/EDID/ in the kernel
source (assembly source and a Makefile).

Cheers,
   Sven



Re: Screen goes blank after "EDID checksum is invalid" errors

2015-09-06 Thread Felix Miata
Johannes Bauer composed on 2015-09-06 11:45 (UTC+0200):

> My guess is that it's trying to do some font switching or frame buffer
> stuff, can't read what the monitor has to offer and switches to a weird
> setting. The system is alive (can ssh into it), but I'd like console
> output as well.

> So I've tried adding "nomodeset", "nofb" and "vga=normal" to my kernel
> cmdline, changed grub to GRUB_TERMINAL=console. The problem remains.

> Can anyone's crystal ball reveal some clues on what's going on here and
> how I could fix that?

Just 3 ideas to try:
1-Try noplymouth on cmdline if plymouth is installed, or uninstall it.
2-replace grub2 with grub legacy if not using UEFI, leave quiet off cmdline,
and set video mode using either vga= and/or video=.
3-ask on intel-...@lists.freedesktop.org mailing list and/or search its archive.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/



Re: Screen goes blank after "EDID checksum is invalid" errors

2015-09-06 Thread Stephen Powell
On Sun, 06 Sep 2015 05:45:30 -0400 (EDT), Johannes Bauer wrote:
> 
> [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 43

Some monitors have invalid EDID checksums.  Blame the manufacturer.
Windows is more tolerant of EDID checksum errors than Linux is.
If switching monitors solves your problem, then a bona fide EDID checksum
error in the hardware is probably to blame.  If you're willing to
build a custom kernel, you may be able to circumvent the problem by applying a
patch.  See my kernel-building web page:

   http://users.wowway.com/~zlinuxman/Kernel.htm

In "Step 7: Patch the kernel", there is a specific example of how to apply
this patch.  Basically, it allows you to tell the kernel to ignore EDID
check sum errors by using the following setting in a file with the extension
of ".conf" under /etc/modprobe.d:

   options drm edid_strict=0

This may allow you to use your faulty monitor anyway.  Good luck.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



Re: Screen goes black after install

2015-06-18 Thread Ric Moore

On 06/17/2015 03:46 PM, Dwijesh Gajadur wrote:

Yes John Hasler..I have already done that..the screen still goes black
after booting :(



Please don't top post.


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/558306eb.5030...@gmail.com



Re: Screen goes black after install

2015-06-18 Thread Patrick Bartek
On Wed, 17 Jun 2015, Dwijesh Gajadur wrote:

> Thanks for your reply Mark Allums..
> 
> I want to use pure command line...I don't want any GUI services to
> load when debian boots..Is there a way to remove all GUI service?.
> Is the video card driver required when we use command line??

The easiest way to remove X and ALL GUI stuff is to reinstall.
Really!  Choose Expert mode or get the NetInstall CD and install only
the Base System, a minimal, command-line only set up that you can
build the system you need off of.

Your black screen problem has happened to me in the past.  I discovered
it was caused (in my case) by the X server being called to run in a
resolution not support by the graphic card.  A bug in the installer?
Setting a supported resolution fixed it.

B


> 
> On Wed, Jun 17, 2015 at 7:25 PM, Mark Allums  wrote:
> 
> > On 06/17/2015 10:12 AM, Dwijesh Gajadur wrote:
> >
> >> Hello everyone.
> >>
> >> I recently bought and installed a PCI ATI Rage 128 Video card on
> >> my pc. I then installed Debian Jessie on the pc.
> >> After booting the following lines appear:
> >>
> >> Loading, Please wait...
> >> fsck from util-linux 2.25.2
> >> /dev/sda5: clean, 48855/7553024 files, 821115/38202368 blocks
> >> _
> >>
> >> And then the screen goes black..nothing appears.
> >> I have tested the video card on windows and it works well.
> >>
> >> I also want to run debian on non-graphical mode..I did not install
> >> any desktop environment.I want to run it on command line as a
> >> server.
> >>
> >
> > Press Ctrl-Alt-F1 and see if a login prompt appears.  If it does,
> > the machine is trying to start X and failing.  I would try to get X
> > running, but if you don't want X, you should probably check and see
> > if a DM (such as lightdm) is installed, then go from there.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150618092641.50eee...@debian7.boseck208.net



Re: Screen goes black after install

2015-06-17 Thread Bob Proulx
Mark Allums wrote:
> Dwijesh Gajadur wrote:
> > I recently bought and installed a PCI ATI Rage 128 Video card on my pc.
> >...
> > And then the screen goes black..nothing appears.
> > I have tested the video card on windows and it works well.
> >
> > I also want to run debian on non-graphical mode..I did not install any
> > desktop environment.I want to run it on command line as a server.
> 
> Press Ctrl-Alt-F1 and see if a login prompt appears.  If it does, the
> machine is trying to start X and failing.  I would try to get X running, but
> if you don't want X, you should probably check and see if a DM (such as
> lightdm) is installed, then go from there.

If no X was installed using Ctrl-Alt-F1 won't exit it.

Since no desktop was installed the going black is probably the
kernel's bitmapped framebuffer at boot.  Try booting with nomodeset on
the kernel command line and see if that improves things.  To do that
interact with the grub boot loader and add that to the boot command
line.

Newer Linux kernels now set the graphics modes very early in the boot
process.  This is something that used to happen with X starting but
now happens by the kernel at boot time even without X.  It enables the
kernel to present boot splash screens and allows switching between X
screens and kernel screens without changing video modes.  And when the
graphics is not supported it tends to break things.  Using nomodeset
instructs the kernel not to do this and to use the BIOS modes
instead.  Using nomodeset now breaks X because X now relies upon the
kernel mode setting.  But it should get your text console working
again.  Hopefully.  Give it a try and see.

Bob


signature.asc
Description: Digital signature


Re: Screen goes black after install

2015-06-17 Thread sp113438
On Wed, 17 Jun 2015 10:25:58 -0500
Mark Allums  wrote:

> On 06/17/2015 10:12 AM, Dwijesh Gajadur wrote:
> > Hello everyone.
> >
> > I recently bought and installed a PCI ATI Rage 128 Video card on my
> > pc. I then installed Debian Jessie on the pc.
> > After booting the following lines appear:
> >
> > Loading, Please wait...
> > fsck from util-linux 2.25.2
> > /dev/sda5: clean, 48855/7553024 files, 821115/38202368 blocks
> > _
> >
> > And then the screen goes black..nothing appears.
> > I have tested the video card on windows and it works well.
> >
> > I also want to run debian on non-graphical mode..I did not install
> > any desktop environment.I want to run it on command line as a
> > server.
> 
> Press Ctrl-Alt-F1 and see if a login prompt appears.  If it does, the 
> machine is trying to start X and failing.  I would try to get X
> running, but if you don't want X, you should probably check and see
> if a DM (such as lightdm) is installed, then go from there.
> 

Press Ctrl-Alt-F2 (since systemd)
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150617223939.18b41d4c@fx4100



Re: Screen goes black after install

2015-06-17 Thread Andrew M.A. Cater
On Wed, Jun 17, 2015 at 10:25:58AM -0500, Mark Allums wrote:
> On 06/17/2015 10:12 AM, Dwijesh Gajadur wrote:
> >Hello everyone.
> >
> >I recently bought and installed a PCI ATI Rage 128 Video card on my pc.
> >I then installed Debian Jessie on the pc.
> >After booting the following lines appear:
> >
> >Loading, Please wait...
> >fsck from util-linux 2.25.2
> >/dev/sda5: clean, 48855/7553024 files, 821115/38202368 blocks
> >_
> >

A really stupid question: does the motherboard also have a video on board -
if so, check which one is the default in BIOS. [I have, in the past, had 
to boot without a video card using the inbuilt VGA, tell it to default to 
PCI on reboot then switch off, insert the card and hope :) ]

> >And then the screen goes black..nothing appears.
> >I have tested the video card on windows and it works well.
> >
> >I also want to run debian on non-graphical mode..I did not install any
> >desktop environment.I want to run it on command line as a server.
> 

Install the absolute bare minimum: use a Debian expert install to allow you
to answer all questions in detail, install only the base system, perhaps
with the SSH server added.

That will install a small text mode system - 280 packages or so - and
should allow you to build on that by adding packages slowly.

Hope this helps a little - logs or more detail will help debug problems

All the best,

AndyC


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150617200255.ga6...@galactic.demon.co.uk



Re: Screen goes black after install

2015-06-17 Thread Dwijesh Gajadur
Yes John Hasler..I have already done that..the screen still goes black
after booting :(

On Wed, Jun 17, 2015 at 11:41 PM, John Hasler  wrote:

> Dwijesh Gajadur writes:
> > I want to use pure command line...I don't want any GUI services to
> > load when debian boots..Is there a way to remove all GUI service?.
>
> Just don't install a display manager.
> --
> John Hasler
> jhas...@newsguy.com
> Elmwood, WI USA
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: https://lists.debian.org/87r3paazrt@thumper.dhh.gt.org
>
>


Re: Screen goes black after install

2015-06-17 Thread John Hasler
Dwijesh Gajadur writes:
> I want to use pure command line...I don't want any GUI services to
> load when debian boots..Is there a way to remove all GUI service?.

Just don't install a display manager.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87r3paazrt@thumper.dhh.gt.org



Re: Screen goes black after install

2015-06-17 Thread Dwijesh Gajadur
Thanks for your reply Mark Allums..

I want to use pure command line...I don't want any GUI services to load
when debian boots..Is there a way to remove all GUI service?.
Is the video card driver required when we use command line??

With Regards,

Dwijesh


On Wed, Jun 17, 2015 at 7:25 PM, Mark Allums  wrote:

> On 06/17/2015 10:12 AM, Dwijesh Gajadur wrote:
>
>> Hello everyone.
>>
>> I recently bought and installed a PCI ATI Rage 128 Video card on my pc.
>> I then installed Debian Jessie on the pc.
>> After booting the following lines appear:
>>
>> Loading, Please wait...
>> fsck from util-linux 2.25.2
>> /dev/sda5: clean, 48855/7553024 files, 821115/38202368 blocks
>> _
>>
>> And then the screen goes black..nothing appears.
>> I have tested the video card on windows and it works well.
>>
>> I also want to run debian on non-graphical mode..I did not install any
>> desktop environment.I want to run it on command line as a server.
>>
>
> Press Ctrl-Alt-F1 and see if a login prompt appears.  If it does, the
> machine is trying to start X and failing.  I would try to get X running,
> but if you don't want X, you should probably check and see if a DM (such as
> lightdm) is installed, then go from there.
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/55819186.8060...@allums.xyz
>
>


Re: Screen goes black after install

2015-06-17 Thread Mark Allums

On 06/17/2015 10:12 AM, Dwijesh Gajadur wrote:

Hello everyone.

I recently bought and installed a PCI ATI Rage 128 Video card on my pc.
I then installed Debian Jessie on the pc.
After booting the following lines appear:

Loading, Please wait...
fsck from util-linux 2.25.2
/dev/sda5: clean, 48855/7553024 files, 821115/38202368 blocks
_

And then the screen goes black..nothing appears.
I have tested the video card on windows and it works well.

I also want to run debian on non-graphical mode..I did not install any
desktop environment.I want to run it on command line as a server.


Press Ctrl-Alt-F1 and see if a login prompt appears.  If it does, the 
machine is trying to start X and failing.  I would try to get X running, 
but if you don't want X, you should probably check and see if a DM (such 
as lightdm) is installed, then go from there.





--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55819186.8060...@allums.xyz



Re: Screen resolution in Jessie (Solved)

2015-04-30 Thread Gary Roach

On 04/30/2015 05:47 AM, Dan Ritter wrote:

On Wed, Apr 29, 2015 at 12:22:43PM -0700, Gary Roach wrote:

On 04/29/2015 09:47 AM, Michael Biebl wrote:

Am 29.04.2015 um 18:28 schrieb Gary Roach:

I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor.
With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
mode. All of my circles are now elipses. Is there a solution to this
problem. Is there a different driver out there. I'm using the on board
video card  on my Intel DP55KG mother board. I am certain that I didn't
have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the "intel" driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?



OK xrandr -v -q gives:

xrandr program version   1.4.2
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
1600x1200  0.00*
1280x1024  0.00
1280x960   0.00
1024x768   0.00
800x6000.00
640x4800.00

No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using
Aptitude. Nothing changed.

[27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)

You have two problems:

1. You are using the VESA driver instead of the intel driver.
Change this by creating /etc/X11/xorg.conf and specifying the
intel driver. Here's a skeleton:

Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

ection "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection

Section "Device"
Identifier  "Card0"
Driver  "intel"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Viewport   0 0
Depth 24
EndSubSection
EndSection



2. (After you solve 1, this may go away) Your monitor's EDID
information is not being picked up or interpreted properly by
the card/driver. You should be able to override it with
something like this:

xrandr --output VGA1 --addmode 1920x1080
xrandr --output VGA1 --mode 1920x1080

-dsr-


Thank you everyone for the help. Dan, you finally tipped me to the real 
problem. There was no xorg.conf file in my system. After further 
reading, I learned that X doesn't use a configuration file any longer 
but generates one on the fly by probing the hardware on boot up. A 
configuration file is only needed if something strange is required. So I 
rebooted  my system and watched the boot messages very carefully ( some 
way to capture these - the real early ones - would be nice). An error 
message showed up saying that a firmware package for radeon 5400 series 
chip set was missing. With more digging around I found that when l did 
an -  apt-get install firmware-linux-nonfree xserver-xorg-video-radeon - 
and reboot the system the correct driver loaded. No more problem.


My wifes computer is the same  but her 4:3 screen doesn't show the 
problem, I may fix it anyway.


I wouldn't be surprised if there a lot of users out there that have the 
same problem but haven't detected it.


Gary R.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5542c075.6080...@verizon.net



Re: Screen resolution in Jessie

2015-04-30 Thread Dan Ritter
On Wed, Apr 29, 2015 at 12:22:43PM -0700, Gary Roach wrote:
> On 04/29/2015 09:47 AM, Michael Biebl wrote:
> >Am 29.04.2015 um 18:28 schrieb Gary Roach:
> >>I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor.
> >>With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
> >>ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
> >>mode. All of my circles are now elipses. Is there a solution to this
> >>problem. Is there a different driver out there. I'm using the on board
> >>video card  on my Intel DP55KG mother board. I am certain that I didn't
> >>have this problem with Wheezy.
> >Does /var/log/Xorg.0.log contain any warnings or errors?
> >I assume you use the "intel" driver? Is xserver-xorg-video-intel
> >correctly installed?
> >
> >What does xrandr -q say?
> >
> >
> OK xrandr -v -q gives:
> 
> xrandr program version   1.4.2
> xrandr: Failed to get size of gamma for output default
> Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
> default connected 1600x1200+0+0 0mm x 0mm
>1600x1200  0.00*
>1280x1024  0.00
>1280x960   0.00
>1024x768   0.00
>800x6000.00
>640x4800.00
> 
> No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using
> Aptitude. Nothing changed.
> 
> [27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)

You have two problems:

1. You are using the VESA driver instead of the intel driver.
Change this by creating /etc/X11/xorg.conf and specifying the
intel driver. Here's a skeleton:

Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

ection "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName"Monitor Model"
EndSection

Section "Device"
Identifier  "Card0"
Driver  "intel"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Viewport   0 0
Depth 24
EndSubSection
EndSection



2. (After you solve 1, this may go away) Your monitor's EDID
information is not being picked up or interpreted properly by
the card/driver. You should be able to override it with
something like this:

xrandr --output VGA1 --addmode 1920x1080
xrandr --output VGA1 --mode 1920x1080

-dsr-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150430124728.gc9...@randomstring.org



Re: Screen resolution in Jessie

2015-04-29 Thread Michael Biebl
Am 29.04.2015 um 21:22 schrieb Gary Roach:
> [27.621] (II) AIGLX: Screen 0 is not DRI2 capable
> [27.638] (EE) AIGLX: reverting to software rendering
> [29.297] (II) AIGLX: Loaded and initialized swrast
> [29.297] (II) GLX: Initialized DRISWRAST GL provider for screen 0

I don't see a message about the intel driver being loaded and used
successfully, only this error message.

Can you provide the full Xorg.0.log somewhere?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Re: Screen resolution in Jessie

2015-04-29 Thread Gary Roach

On 04/29/2015 09:47 AM, Michael Biebl wrote:

Am 29.04.2015 um 18:28 schrieb Gary Roach:

I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor.
With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
mode. All of my circles are now elipses. Is there a solution to this
problem. Is there a different driver out there. I'm using the on board
video card  on my Intel DP55KG mother board. I am certain that I didn't
have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the "intel" driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?



OK xrandr -v -q gives:

xrandr program version   1.4.2
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
   1600x1200  0.00*
   1280x1024  0.00
   1280x960   0.00
   1024x768   0.00
   800x6000.00
   640x4800.00

No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using 
Aptitude. Nothing changed.


There were no warnings or errors in the Xorg.0.log but I did find the 
following:

//(I noticed that it got the screen size right, 520, 320 mm)

[27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)
[27.140] (II) VESA(0): : Using hsync range of 
30.00-83.00 kHz
[27.140] (II) VESA(0): : Using vrefresh range of 
50.00-61.00 Hz
[27.140] (II) VESA(0): : Using maximum pixel clock 
of 175.00 MHz

[27.140] (WW) VESA(0): Unable to estimate virtual size
[27.140] (II) VESA(0): Not using built-in mode "1920x1440" (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode "1856x1392" (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode "1792x1344" (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode "1400x1050" (no mode 
of this name)
[27.141] (II) VESA(0): Not using built-in mode "1152x864" (no mode 
of this name)
[27.141] (II) VESA(0): Not using built-in mode "720x400" (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode "640x350" (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode "512x384" (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode "320x240" (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode "320x200" (no mode of 
this name)

[27.141] (--) VESA(0): Virtual size is 1600x1200 (pitch 1600)
[27.141] (**) VESA(0): *Built-in mode "1600x1200"
[27.141] (**) VESA(0): *Built-in mode "1280x1024"
[27.141] (**) VESA(0): *Built-in mode "1280x960"
[27.141] (**) VESA(0): *Built-in mode "1024x768"
[27.141] (**) VESA(0): *Built-in mode "800x600"
[27.141] (**) VESA(0): *Built-in mode "640x480"
*[27.141] (**) VESA(0): Display dimensions: (520, 320) mm*
[27.141] (**) VESA(0): DPI set to (78, 95)
[27.141] (**) VESA(0): Using "Shadow Framebuffer"
[27.141] (II) Loading sub module "shadow"
[27.141] (II) LoadModule: "shadow"
[27.141] (II) Loading /usr/lib/xorg/modules/libshadow.so
[27.247] (II) Module shadow: vendor="X.Org Foundation"
[27.247]compiled for 1.16.4, module version = 1.1.0
[27.247]ABI class: X.Org ANSI C Emulation, version 0.4
[27.247] (II) Loading sub module "fb"
[27.247] (II) LoadModule: "fb"
[27.247] (II) Loading /usr/lib/xorg/modules/libfb.so
[27.324] (II) Module fb: vendor="X.Org Foundation"
[27.324]compiled for 1.16.4, module version = 1.0.0
[27.324]ABI class: X.Org ANSI C Emulation, version 0.4
[27.324] (==) Depth 24 pixmap format is 32 bpp
[27.324] (II) Loading sub module "int10"
[27.324] (II) LoadModule: "int10"
[27.324] (II) Loading /usr/lib/xorg/modules/libint10.so
[27.324] (II) Module int10: vendor="X.Org Foundation"
[27.324]compiled for 1.16.4, module version = 1.0.0
[27.324]ABI class: X.Org Video Driver, version 18.0
[27.324] (II) VESA(0): initializing int10
[27.324] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[27.324] (II) VESA(0): VESA BIOS detected
[27.324] (II) VESA(0): VESA VBE Version 3.0
[27.324] (II) VESA(0): VESA VBE Total Mem: 16384 kB
[27.324] (II) VESA(0): VESA VBE OEM: ATI ATOMBIOS
[27.324] (II) VESA(0): VESA VBE OEM Software Rev: 12.16
[27.324] (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI 
Technologies Inc.

[27.324] (II) VESA(0): VESA VBE OEM Product: CEDAR
[27.324] (II) VESA(0): VESA VBE OEM Product Rev: 01.00
[27.324] (II) VESA(0): virtual address = 0x7f66a9821000,
physical address = 0xe000, size = 16777216
[27.337] (II) VESA(0): Setting up VESA Mode 0x176 (1600x1200)
[27.337] (II) VESA(0): VBESetVBEMode failed, mode set without 
customized refresh.

[27.451] (==) VESA(0): Default visual is TrueColor
[27.516] (==) VE

Re: Screen resolution in Jessie

2015-04-29 Thread Frank Miles
On Wed, 29 Apr 2015 18:30:03 +0200, Gary Roach wrote:

> I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor. 
> With wheezy, there was a 1920 x 1080? mode that gave the correct aspect 
> ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 
> mode. All of my circles are now elipses. Is there a solution to this 
> problem. Is there a different driver out there. I'm using the on board 
> video card  on my Intel DP55KG mother board. I am certain that I didn't 
> have this problem with Wheezy.
> 
> Gary R.

My 1920 x 1200 is working fine using the on-chip Intel video system and Jessie.
Never tried the x1080.

Can you alter the configuration using xrandr ?

HTH..


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mhr2dg$spg$1...@dont-email.me



Re: Screen resolution in Jessie

2015-04-29 Thread Michael Biebl
Am 29.04.2015 um 18:28 schrieb Gary Roach:
> I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor.
> With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
> ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
> mode. All of my circles are now elipses. Is there a solution to this
> problem. Is there a different driver out there. I'm using the on board
> video card  on my Intel DP55KG mother board. I am certain that I didn't
> have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the "intel" driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Re: Screen rotation question

2014-12-20 Thread Joris Bolsens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Could be there's no difference, but try the --rotate flag and specify
your vga connection

xrandr --output VGA1 --rotate right

On 12/05/2014 02:32 PM, Jacek Dudek wrote:
> X Error of failed request: BadMatch (invalid parameter attributes)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUlhnhAAoJEORnMHMHY2FrWoUQAK5Z01OxG30/yTc/B8jUi4y5
r6lqTXN1NCbP4V8QCLcL0KwnNBPbmZVRe2Ut8yLeg09o1H7BVesEu07VMnIHTeUy
hfy/dKcDt8JpXxDQ5/y3pkOrkvlwt9IRGDy5G2od9k7CWhQ7y69M6pxVY9cxSbzt
4JpydPeJ7S2YwcF4taGfAcJDHfxo16cqGazNiI4nlJRJfGORSw2PMhndGfm0wS/5
QLLxInSHJkvlZ43QYNEyJvof2Zuvq/BR4t39QpH2dj/uup0x/5cIyH6Tg7KwZ+QR
Nel6mWaaGZl5DT4qFxpZm1ZDWCZ0+AuTIeB4iDhpyBugsid+9WVBKpBW7NgDWBje
BA4YQEwVjMgiXKOfwW8464FHABIxQNxtHsQHZDmPeb80o2+UIn9V+CEmWrNLe+gB
26mraGUzNKuUf+yK6higctsnA6cqXSgdtbN6mm2qMU03X0j6fLY/xaNazKDX3c81
1wD9YhJ5MpqmeWaBdwyWjjM/pTWiTWNo5V32vFeQWIpWTKG6Pcde2wLTs8g7JnuF
00z/I3G3OlJ32317YnFSysqJDjBLQUU/NaoAccjOBAiZ/NOfKfIU414k/WRCtQ2c
JTrwvEj1CZKq6y/uyMJWpI91t1NfIaEHAqdRsSjKce1RO6nKa4SyiWlWX7HBe/sR
j9duXnxBpDy6R1NoqYYN
=Ge/E
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/549619ea.20...@gmail.com



Re: Screen doesn't turn off

2014-10-27 Thread Catalin Soare
On Oct 26, 2014 6:08 PM, "Alan Greenberger"  wrote:
>
> On 2014-10-23, Catalin Soare  wrote:
> > --001a11397ac09df76505061dfacf
> > Content-Type: text/plain; charset=UTF-8
> >
> > Hi,
> >
> > I've got 2 computera, both running Debian Wheezy, all updates applied.
One
> > of them seems to ignore the "Brightness and lock" setting which should
make
> > the screen turn off after 30 minutes.
> > It simply remains on all day or night.
> >
> > Anyone have a clue what additional setting I should check?
>
> type "xset q".  If it reports that DPMS is not enabled,
> type "xset +dpms"
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmas...@lists.debian.org
> Archive: https://lists.debian.org/slrnm4q44g.jdu.alanjg@archduke.router
>

I think that did it.

Thank you.

--
Sent from my Brick(TM)


Re: Screen doesn't turn off

2014-10-26 Thread Alan Greenberger
On 2014-10-23, Catalin Soare  wrote:
> --001a11397ac09df76505061dfacf
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
> I've got 2 computera, both running Debian Wheezy, all updates applied. One
> of them seems to ignore the "Brightness and lock" setting which should make
> the screen turn off after 30 minutes.
> It simply remains on all day or night.
>
> Anyone have a clue what additional setting I should check?

type "xset q".  If it reports that DPMS is not enabled,
type "xset +dpms"


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnm4q44g.jdu.alanjg@archduke.router



Re: Screen doesn't turn off

2014-10-23 Thread Ric Moore

On 10/23/2014 05:45 PM, Catalin Soare wrote:

Hi,

I've got 2 computera, both running Debian Wheezy, all updates applied.
One of them seems to ignore the "Brightness and lock" setting which
should make the screen turn off after 30 minutes.
It simply remains on all day or night.

Anyone have a clue what additional setting I should check?

Thank you for your time.


Your screensaver should have settings to enable and set power saving 
modes. Maybe compare the settings of the one that works correctly with 
the one that doesn't? :) Ric




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5449d3fa.7090...@gmail.com



Re: screen 0: in putty title bar

2014-09-18 Thread Aero Maxx


On 18/09/2014 17:38, B wrote:

On Thu, 18 Sep 2014 17:33:18 +0100
Apero Maxx  wrote:


PROMPT_COMMAND='printf "\033k%s@%s:%s\033\\" "${USER}"
"${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'

Check ~/.bashrc for the right string.

I've cracked it thank you! Working just how I like it now.

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/541b438c.9010...@gmail.com



Re: screen 0: in putty title bar

2014-09-18 Thread Bzzzz
On Thu, 18 Sep 2014 17:33:18 +0100
Apero Maxx  wrote:

> PROMPT_COMMAND='printf "\033k%s@%s:%s\033\\" "${USER}"
> "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'

Check ~/.bashrc for the right string.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140918183843.4367af22@msi.defcon1



Re: screen 0: in putty title bar

2014-09-18 Thread Aero Maxx


On 18/09/2014 16:30, Reco wrote:

  Hi.

On Thu, 18 Sep 2014 16:19:59 +0100
Aero Maxx  wrote:


Hi Everyone,

I'm in the process of moving from fedora to debian.

But I have one question about the use of screen when I use it, the title
bar in putty doesn't change like it does in fedora to show/remind me
that I am in a screen, I was wondering how do I change this in debian ?

Try adding this to your /etc/screenrc:

hardstatus on
hardstatus string "[screen %n%?: %t%?] %h"

Reco

Hi Everyone,

This works great, and was a good starting point in the right direction, 
I've done a bit of playing around and checking what the difference is on 
fedora and debian, and can see lots but what I think I need to do now is 
something to do with this from fedora.


PROMPT_COMMAND='printf "\033k%s@%s:%s\033\\" "${USER}" "${HOSTNAME%%.*}" 
"${PWD/#$HOME/~}"'


Id like it to show [screen 0: daniel@hostname:/home/daniel] in the putty 
title bar.


Also would like for it so show [daniel@hostname daniel]# at the command 
prompt part.


Thanks
Daniel


---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/541b094e.8060...@gmail.com



Re: screen 0: in putty title bar

2014-09-18 Thread Aero Maxx

On 18/09/2014 16:30, Reco wrote:

  Hi.

On Thu, 18 Sep 2014 16:19:59 +0100
Aero Maxx  wrote:


Hi Everyone,

I'm in the process of moving from fedora to debian.

But I have one question about the use of screen when I use it, the title
bar in putty doesn't change like it does in fedora to show/remind me
that I am in a screen, I was wondering how do I change this in debian ?

Try adding this to your /etc/screenrc:

hardstatus on
hardstatus string "[screen %n%?: %t%?] %h"

Reco

Thats amazing thank you ever so much! It works a treat.

Daniel.


---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/541afb6f.1060...@gmail.com



Re: screen 0: in putty title bar

2014-09-18 Thread Reco
 Hi.

On Thu, 18 Sep 2014 16:19:59 +0100
Aero Maxx  wrote:

> Hi Everyone,
> 
> I'm in the process of moving from fedora to debian.
> 
> But I have one question about the use of screen when I use it, the title 
> bar in putty doesn't change like it does in fedora to show/remind me 
> that I am in a screen, I was wondering how do I change this in debian ?

Try adding this to your /etc/screenrc:

hardstatus on
hardstatus string "[screen %n%?: %t%?] %h"

Reco


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140918193009.9eb52e96867a75d481eb3...@gmail.com



Re: Screen size trouble with Xorg

2014-07-06 Thread Andrei POPESCU
On Lu, 16 iun 14, 08:03:56, Mike Bailey wrote:
> Hello all,
> Last week I bought myself a new monitor to replace my old 24" monitor. The
> new monitor is a Samsung S27C500, which is connected via hdmi. The monitor
> has two inputs: one hdmi, and one vga. I do not have a VGA input on my video
> card, so I use the hdmi connector. The monitor did not include a vga-to-dvi
> adapter.
> 
> When replacing my old monitor, i used the the aticonfig utility to generate
> a new xorg.conf as I've done in the past, and while the monitor was usable,
> I am stuck with a problem where the screen size is limited to about the size
> of my old 24" monitor, with black space surrounding the entire usable
> screen.

[...]

> Links to my configs:
> 
> xrandr --prop: http://paste2.org/m8gpIbss
> xorg.conf: http://paste2.org/hmIJVWJ0 (monitor block comes from parse-edid)
> xorg.0.log: http://paste2.org/GXNpZpB3

Why use a pastebin if you're not going to include the entire contents. 
Besides, attaching the file would have made your message self-contained.

> lspci block for video card: http://paste2.org/KLNPJnvn
> 
> I notice two things in my xorg.0.log:
> 
> [254760.941] (II) fglrx(0): Using hsync ranges from config file
> [254760.941] (II) fglrx(0): Using vrefresh ranges from config file

I'd try with a minimal xorg.conf:

Section "Device"
Identifier  "WhatEver"
Driver  "fglrx"
EndSection

or even *no* xorg.conf and the radeon driver. Please mind fglrx might be 
blacklisting the necessary radeon kernel module (at least nvidia has to
with nouveau), so it might not work without a few tweaks.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Re: Screen size trouble with Xorg

2014-06-18 Thread Virgo Pärna
On Mon, 16 Jun 2014 09:47:04 -0500, Mike Bailey  wrote:
>
> Sure enough, switching to the Vesa driver makes the entirety of the 
> monitor functional, and performance is pretty fine as well. Thanks a lot 
> for your help.
>

Are you sure, that you are using native resolution of monitor? 

-- 
Virgo Pärna 
virgo.pa...@mail.ee


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnlq51t9.jp8.virgo.pa...@dragon.gaiasoft.ee



Re: Screen size trouble with Xorg

2014-06-16 Thread Steve Litt
On Mon, 16 Jun 2014 08:03:56 -0500
Mike Bailey  wrote:

> Hello all,
> Last week I bought myself a new monitor to replace my old 24"
> monitor. The new monitor is a Samsung S27C500, which is connected via
> hdmi. The monitor has two inputs: one hdmi, and one vga. 

[clip]

> I am stuck with a problem where the screen size
> is limited to about the size of my old 24" monitor, with black space
> surrounding the entire usable screen.
> 
> If I send an ctrl+alt+f2 to switch to tty2, I am able to use the 
> entirety of the monitor, which tells me that this is an issue
> somewhere in X. I dug into 

[clip]

> I appreciate any help any of you are able to toss my way.

I'd handle this as a process. Burn a Ubuntu live DVD, a System Rescue
CD CD, and maybe another live distro or two. Boot into each, and see
whether the symptom does not appear on one of them.

One of the oldest troubleshooting tactics is to find one situation
where the symptom appears, another where it doesn't, and exploit the
differences. What's different about the configs of each? What happens
if you swap out the X config file (whatever it's called these days)
of the one that works over the one that didn't (after backing up the
one that didn't, of course). You can keep changing things til you
find that one factor that causes the symptom.

Somebody recommended switching to VESA as a diagnostic test. That's
certainly a quick test that I'd do early.

HTH,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140616111734.10530ee0@mydesk



Re: Re: Screen size trouble with Xorg

2014-06-16 Thread Mike Bailey

A quick Google returns this interesting link:
http://forums.amd.com/game/messageview.cfm?catid=440&threadid=168568&messid=1324412&parentid=1322139&FTVAR_FORUMVIEWTMP=Branch

indicating even the Windows AMD driver has trouble.

Have you tried the vesa driver as a test?



Wow! I didn't come across that link during my research, but it's
bloody amazing that this is a cross-platform bug facing all
combinations of AMD video cards using the S27C500 monitor. I will give
things a try using the vesa driver, thank you very much for pointing
me in the direction of that link. I believe I'll be going to the store
to buy an Nvidia card later today.

I am happy that this is a real bug on AMD's part, and I am angry they
have turned a blind eye to this problem!


Sure enough, switching to the Vesa driver makes the entirety of the 
monitor functional, and performance is pretty fine as well. Thanks a lot 
for your help.


--
Love,
Mike Bailey


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/c2aa0d89e298c66ff95f5b9170401...@0day4hax.com



Re: Re: Screen size trouble with Xorg

2014-06-16 Thread Ralf Mardorf
On Mon, 2014-06-16 at 09:23 -0500, Mike Bailey wrote:
> > Is it a multisync monitor? You perhaps need to configure the monitor's
> > settings on the monitor.
> > 
> > When using the GUI the frequencies of my monitor are 81.9KHz/89.9Hz, if
> > I switch to tty2 the frequencies are 48.3KHz/59.9Hz on an Arch Linux
> > install using the radeon driver.
> > 
> > My multisync monitor remembers different settings for different
> > frequencies.
> 
> I am not sure how to tell if I have a multisync monitor. My monitor's 
> menu does not offer a way to adjust the size of the screen area. I can 
> tell you that in X, I am seeing a frequency of 67.5khz / 60hz np, and on 
> tty2 I see the same frequency. Pressing the "auto" button results in a 
> popup on the monitor that says "Auto adjustment: Not available".

I now searched the web and noticed that it isn't a CRT monitor. It's a
LED monitor, so my assumption is wrong. Reflecting on the post, I guess
HDMI already was a hint.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1402930221.8460.108.camel@archlinux



Re: Re: Screen size trouble with Xorg

2014-06-16 Thread Mike Bailey

A quick Google returns this interesting link:
http://forums.amd.com/game/messageview.cfm?catid=440&threadid=168568&messid=1324412&parentid=1322139&FTVAR_FORUMVIEWTMP=Branch

indicating even the Windows AMD driver has trouble.

Have you tried the vesa driver as a test?



Wow! I didn't come across that link during my research, but it's bloody 
amazing that this is a cross-platform bug facing all combinations of AMD 
video cards using the S27C500 monitor. I will give things a try using 
the vesa driver, thank you very much for pointing me in the direction of 
that link. I believe I'll be going to the store to buy an Nvidia card 
later today.


I am happy that this is a real bug on AMD's part, and I am angry they 
have turned a blind eye to this problem!



--
Love,
Mike Bailey


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/ff058e7c8e8e1c24bef7158a44ca5...@0day4hax.com



Re: Re: Screen size trouble with Xorg

2014-06-16 Thread Mike Bailey

Is it a multisync monitor? You perhaps need to configure the monitor's
settings on the monitor.

When using the GUI the frequencies of my monitor are 81.9KHz/89.9Hz, if
I switch to tty2 the frequencies are 48.3KHz/59.9Hz on an Arch Linux
install using the radeon driver.

My multisync monitor remembers different settings for different
frequencies.


I am not sure how to tell if I have a multisync monitor. My monitor's 
menu does not offer a way to adjust the size of the screen area. I can 
tell you that in X, I am seeing a frequency of 67.5khz / 60hz np, and on 
tty2 I see the same frequency. Pressing the "auto" button results in a 
popup on the monitor that says "Auto adjustment: Not available".


--
Love,
Mike Bailey


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/b0294fa55d31f94804c5300f4d4ba...@0day4hax.com



Re: Screen size trouble with Xorg

2014-06-16 Thread Chris Bannister
On Mon, Jun 16, 2014 at 08:03:56AM -0500, Mike Bailey wrote:
> Hello all,
> Last week I bought myself a new monitor to replace my old 24" monitor. The
> new monitor is a Samsung S27C500, which is connected via hdmi. The monitor
> has two inputs: one hdmi, and one vga. I do not have a VGA input on my video
> card, so I use the hdmi connector. The monitor did not include a vga-to-dvi
> adapter.

A quick Google returns this interesting link:
http://forums.amd.com/game/messageview.cfm?catid=440&threadid=168568&messid=1324412&parentid=1322139&FTVAR_FORUMVIEWTMP=Branch

indicating even the Windows AMD driver has trouble.

Have you tried the vesa driver as a test?

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140616141202.GA2867@tal



Re: Screen size trouble with Xorg

2014-06-16 Thread Ralf Mardorf
On Mon, 2014-06-16 at 08:03 -0500, Mike Bailey wrote:
> If I send an ctrl+alt+f2 to switch to tty2, I am able to use the 
> entirety of the monitor, which tells me that this is an issue somewhere 
> in X.

Is it a multisync monitor? You perhaps need to configure the monitor's
settings on the monitor.

When using the GUI the frequencies of my monitor are 81.9KHz/89.9Hz, if
I switch to tty2 the frequencies are 48.3KHz/59.9Hz on an Arch Linux
install using the radeon driver.

My multisync monitor remembers different settings for different
frequencies.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1402926527.8460.103.camel@archlinux



Re: Screen Aspect Ratio

2012-10-07 Thread Gary Dale

On 07/10/12 12:13 PM, Stephen P. Molnar wrote:

On 10/07/2012 11:58 AM, Stephen P. Molnar wrote:

On 10/07/2012 11:20 AM, Gary Dale wrote:

On 04/10/12 06:17 AM, Sthu Deus wrote:

Good time of the day, Stephen.


You wrote:


As a result of my stupidity in attempting to modify the screen
drivers I have managed to change my display into something really
ugly.

The aspect ratio is off and the number of available fonts is really
limited. (I also have OpenSUSE 12.2 on another HD and the screen is
normal, leading me to conclude that the problem lies in Debian)

I have switched to Debian and am wondering what display utilities are
available? Google hasn't been on any help

If You did some config. modifications by a normal user, then You can
simply move all the user's home dir. content to another place and then
relogin.

If did that under root user, then You have to reconfigure those
services, for example by simple removal of the config.s to safe place
and restart the service, OR using debian package reconfigurator, or
download from Internet its options OR reinstall the package having
purged it previously.


Sthu.
The main X configuration file is /etc/X11/xorg.conf. If you rename 
this,

Debian/X will try to detect your display and adapter.

You can also boot to a root prompt and try X -configure to produce an
xorg.conf file to experiment with.

If you are using proprietary drivers, they each have a configuration
utility that should help.

Sthu's suggestion of using the purge option with apt-get/aptitude is
also worth trying.

And there's the kernel mode setting driver to consider. If it's not set
properly, you can get into all kinds of problems.

You will also find a /etc/X11/fonts directory that may have been 
screwed

up. If so, you could try renaming it then re-installing X.



Thank you for your reply, I really appreciate it. There is no xorg.conf
filer on the system.

I opened a cosole as root and got:

computation@debian:~$ su
Password:
root@debian:/home/computation# X -configure

Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.


Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.

Please advise.

Again, thanks in advance.


I wrote the above as little too fast.

I just logged on to Debian as root and ran X -configure.  Hereis the 
result:


Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath   "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "built-ins"
EndSection

Section "Module"
Load  "extmod"
Load  "dri2"
Load  "dbe"
Load  "glx"
Load  "dri"
Load  "record"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option"Protocol" "auto"
Option"Device" "/dev/input/mice"
Option"ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
#DisplaySize  470   300# mm
Identifier   "Monitor0"
VendorName   "CMO"
ModelName"CMC 22 W"
HorizSync30.0 - 82.0
VertRefresh  56.0 - 76.0
Option"DPMS"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor"   # []
#Option "HWcursor"   # []
#Option "NoAccel"# []
#Option "ShadowFB"   # []
#Option "UseFBDev"   # []
#Option "Rotate" # []
#Option "VideoKey"   # 
#Option "FlatPanel"  # []
#Option "FPDither"   # []
#Option "CrtcNumber" # 
#Option "FPScale"# []
#Option "FPTweak"# 
#Option "DualHead"   # []
Identifier  "Card0"
Driver  "nv"
VendorName  "nVidia Corporation"
BoardName   "NV44 [GeForce 6200 TurboCache(TM)]"
BusID   "PCI:6:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport   0 0

Re: Screen Aspect Ratio

2012-10-07 Thread Sthu Deus
Good time of the day, Stephen.


You wrote:

> I think that I have located the problem.  The monitor resolution is
> set at 1280x1024 by Debian.  Also there are only four solutions
> listed in System Settings/Size and Orientation.
> 
> I have an OpenSUSE 12.2 installatopn on another hadr drive in the
> systen and it's resolution is 1680x1050 with eleven additional
> different resolutions.

If You want to play w/ resolutions, then try 

xrandr --output VGA-0 --mode 1680x1050

Here You can change VGA w/ LVDS - if it be a laptop.

or using xorg.conf (first generate one for Your system, then adjust
line Modes in something similar):

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Depth 24
Modes "1680x1050"
EndSubSection
EndSection



Sthu.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5071c647.e257700a.1027.0...@mx.google.com



Re: Screen Aspect Ratio

2012-10-07 Thread Stephen P. Molnar

On 10/07/2012 11:58 AM, Stephen P. Molnar wrote:

On 10/07/2012 11:20 AM, Gary Dale wrote:

On 04/10/12 06:17 AM, Sthu Deus wrote:

Good time of the day, Stephen.


You wrote:


As a result of my stupidity in attempting to modify the screen
drivers I have managed to change my display into something really
ugly.

The aspect ratio is off and the number of available fonts is really
limited. (I also have OpenSUSE 12.2 on another HD and the screen is
normal, leading me to conclude that the problem lies in Debian)

I have switched to Debian and am wondering what display utilities are
available? Google hasn't been on any help

If You did some config. modifications by a normal user, then You can
simply move all the user's home dir. content to another place and then
relogin.

If did that under root user, then You have to reconfigure those
services, for example by simple removal of the config.s to safe place
and restart the service, OR using debian package reconfigurator, or
download from Internet its options OR reinstall the package having
purged it previously.


Sthu.

The main X configuration file is /etc/X11/xorg.conf. If you rename this,
Debian/X will try to detect your display and adapter.

You can also boot to a root prompt and try X -configure to produce an
xorg.conf file to experiment with.

If you are using proprietary drivers, they each have a configuration
utility that should help.

Sthu's suggestion of using the purge option with apt-get/aptitude is
also worth trying.

And there's the kernel mode setting driver to consider. If it's not set
properly, you can get into all kinds of problems.

You will also find a /etc/X11/fonts directory that may have been screwed
up. If so, you could try renaming it then re-installing X.



Thank you for your reply, I really appreciate it. There is no xorg.conf
filer on the system.

I opened a cosole as root and got:

computation@debian:~$ su
Password:
root@debian:/home/computation# X -configure

Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.


Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.

Please advise.

Again, thanks in advance.


I wrote the above as little too fast.

I just logged on to Debian as root and ran X -configure.  Hereis the result:

Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath   "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "built-ins"
EndSection

Section "Module"
Load  "extmod"
Load  "dri2"
Load  "dbe"
Load  "glx"
Load  "dri"
Load  "record"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
#DisplaySize  470   300 # mm
Identifier   "Monitor0"
VendorName   "CMO"
ModelName"CMC 22 W"
HorizSync30.0 - 82.0
VertRefresh  56.0 - 76.0
Option  "DPMS"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor"# []
#Option "HWcursor"# []
#Option "NoAccel" # []
#Option "ShadowFB"# []
#Option "UseFBDev"# []
#Option "Rotate"  # []
#Option "VideoKey"# 
#Option "FlatPanel"   # []
#Option "FPDither"# []
#Option "CrtcNumber"  # 
#Option "FPScale" # []
#Option "FPTweak" # 
#Option "DualHead"# []
Identifier  "Card0"
Driver  "nv"
VendorName  "nVidia Corporation"
BoardName   "NV44 [GeForce 6200 TurboCache(TM)]"
BusID   "PCI:6:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "D

  1   2   3   4   5   6   >