On Monday, 23-09-2024 at 19:48 newbie...@gmx.de wrote:
>
> hello friends,
>
> I tried but found it too confusing to find where to report bugs for debian
> :-( .
What GUI are you using? (e.g. Gnome, KDE, Xfec, etc ?)
Wayland or X11 ?
What is the model number of monitor are you using?
hello friends,
I tried but found it too confusing to find where to report bugs for debian :-(
.
I see an issues in ver. 12.6.0 started from the live image:
Scaling the desktop by Settings - Display - General - Scale works
counter-intuitive, setting it to 2x reduces everything on scree
On Friday 24 February 2023 10:03:31 pm Max Nikulin wrote:
> On 25/02/2023 00:55, Roy J. Tellason, Sr. wrote:
> > On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
> >> On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
> >>> So this got me curious, and I tried it out. In the terminal tha
On 25/02/2023 00:55, Roy J. Tellason, Sr. wrote:
On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
So this got me curious, and I tried it out. In the terminal that's
running inside of the virtualbox instance where I'm doing emails,
On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
>
> On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
> > On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
> >> echo "$DISPLAY"
> >
> > So this got me curious, and I tried it out. In the terminal that's
> > running inside of
On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
echo "$DISPLAY"
So this got me curious, and I tried it out. In the terminal that's
running inside of the virtualbox instance where I'm doing emails, it
comes back with:
:0
Have
My thanks to David Wright and Max Nikulin.
That was a good wake-up call. Most of my VMs are safe, but it was
interesting to learn what was really going on.
ForwardX11 was enabled for the ssh session. Initially I imagined
vncviewer (to the KVM host though ssh) was the one causing the problem,
On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
> echo "$DISPLAY"
So this got me curious, and I tried it out. In the terminal that's running
inside of the virtualbox instance where I'm doing emails, it comes back with:
:0
But in a terminal which is running on the host Debian syst
On 18/02/2023 08:57, Albert S. wrote:
If you think I issued the xrandr command on the wrong machine, that was
not the case: history makes it clear.
Behavior depends on the DISPLAY environment value at the moment when
xrandr was executed. Likely it was pointed not to vnc Xserver, but to
the
On Fri 17 Feb 2023 at 20:57:38 (-0500), Albert S. wrote:
> Running “xrandr --size 800x600” on a virtual machine affected both
> monitors on my workstation. That was completely unexpected and I am
> wondering how to explain that.
>
> Below you will find the detailed description.
[ … ]
> But my re
tely
unexpected. I am asking myself how can a command issued on a VM which is
running on a different machine affect the screen resolution of the
workstation used to access that VM. Just to be clear, I was accessing
that VM both through ssh and through vncviewer (still back and gray
screen image)
On 12/21/22 03:37, to...@tuxteam.de wrote:
On Tue, Dec 20, 2022 at 05:26:06PM +, Kleene, Steven (kleenesj) wrote:
[...]
On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:
get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid
Thanks. get-edid doesn't find any EDIDs
: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2
External Email: Use Caution
On 20/12/2022 09:49, Timothy M Butterworth wrote:
Newer Intel graphics require closed source binary blobs. Try installing
firmware-linux-nonfree.
In the previous thread somebody spotted an issue
On 21/12/2022 00:26, Kleene, Steven (kleenesj) wrote:
On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:
get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid
Thanks. get-edid doesn't find any EDIDs, and there are no edid files under
/sys/devices.
Have you checked "jou
_
From: to...@tuxteam.de
Sent: Wednesday, December 21, 2022 3:37 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2
External Email: Use Caution
On Tue, Dec 20, 2022 at 05:26:06PM +, Kleene, Steven (kleenesj) wrote:
[...]
> On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:
> > get-edid | parse-edid
> > edid-decode /sys/class/drm/card0-HDMI-A-1/edid
> Thanks. get-edid doesn't find any EDIDs, and there are no edid files under
20, 2022 12:26 PM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2
On Monday, December 19, 2022 9:12 PM, I wrote:
>> Today I have my new desktop and did a clean install of Bullseye. I call fvwm
>> with startx, and once again my screen is 1024x768.
On Mon
Thanks. get-edid doesn't find any EDIDs, and there are no edid files under
/sys/devices.
From: Max Nikulin
Sent: Tuesday, December 20, 2022 10:36 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2
External Email: Us
On 20/12/2022 09:49, Timothy M Butterworth wrote:
Newer Intel graphics require closed source binary blobs. Try installing
firmware-linux-nonfree.
In the previous thread somebody spotted an issue with fetching modes
supported by the monitor. Examples of commands to debug such problem:
get-edi
Kleene, Steven (kleenesj) composed on 2022-12-20 02:12 (UTC):
> Today I have my new desktop and did a clean install of Bullseye.
Cardinal rule of PC shopping for use with Linux, unless you are a Linux
developer:
Make sure the major PC components are several months or more older than
On Mon, Dec 19, 2022 at 9:28 PM Kleene, Steven (kleenesj) <
kleen...@ucmail.uc.edu> wrote:
> On Thursday, December 1, 2022 9:41 PM, I started a thread (same title as
> this
> minus "part 2"), with:
> > Out of the blue today, my usual screen resolution (19
On Thursday, December 1, 2022 9:41 PM, I started a thread (same title as this
minus "part 2"), with:
> Out of the blue today, my usual screen resolution (1920x1200) became
> unavailable.
Despite many helpful suggestions, the problem wasn't resolved. Since I
was about to
On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...
On Sunday, December 4, 2022 1:26 AM, Felix Miata
replied:
> Do you have another VGA cable you could try? Do you have any other PCs with
> VGA out
Kleene, Steven (kleenesj) composed on 2022-12-04 18:03 (UTC):
> I do have /usr/lib/xserver-xorg-video-intel. I don't have
> /etc/X11/xorg.conf.d/ but do have /usr/share/X11/xorg.conf.d/ with the
> following:
> 10-amdgpu.conf 10-quirks.conf 10-radeon.conf 40-libinput.conf
> 70-wacom.conf
>
On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...
On December 4, 2022 1:26 AM, Felix Miata replied:
> Your old Xorg.0.logs differ significantly from your current ones ...
> This suggests to me your
Kleene, Steven (kleenesj) composed on 2022-12-02 02:41 (UTC):
...
Your old Xorg.0.logs differ significantly from your current ones, and my
own on a similar Intel GPU. In what follows, the current ones and the old
ones omit everything between the first and last lines:
*
[ 2059.607] (II) modes
Kleene, Steven (kleenesj) composed on 2022-12-02 02:41 (UTC):
See if adding the following file helps:
---
# cat /etc/X11/xorg.conf.d/25-intelExtra.conf
Section "Device"
Identifier "IntelKludges"
Option "ReprobeOutputs" "on" # default off
EndSection
---
"(WW) VGA ar
On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...
On December 3, 2022 1:23 PM, Felix Miata wrote:
> This and http://paste.debian.net/1262700/ are the same log created Sat Jul 3
> 16:37:19 2021 u
Kleene, Steven (kleenesj) composed on 2022-12-03 14:15 (UTC):
> For Xorg.0.log,
> http://paste.debian.net/1262735/
This and http://paste.debian.net/1262700/ are the same log created
Sat Jul 3 16:37:19 2021 using kernel 4.19.0-17-amd64. If these are from
/var/log/
then look in ~/.local/share/xorg
On December 1, 2022 9:41 PM, I wrote:
>>> Out of the blue today, my usual screen resolution (1920x1200) became
>>> unavailable. ...
On December 2, 2022 10:12 AM, Felix Miata wrote:
>> ... run
>> inxi -U
>> to upgrade, and post here output from within
Kleene, Steven (kleenesj) composed on 2022-12-02 02:20 (UTC):
>> Next, give us the whole log to see:
> cat /var/log/Xorg.0.log | pastebinit
> http://paste.debian.net/1262700/
> That's a lot to look at. Thank you.
I don't see anything to suggest that there's anything wrong. Did these re
On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...
On December 2, 2022 10:12 AM, Felix Miata wrote:
> ... run
> inxi -U
> to upgrade, and post here output from within an X terminal:
Kleene, Steven (kleenesj) composed on 2022-12-02 13:11 (UTC):
> I'll add that I did do a weekly apt upgrade shortly before this happened,
Now let's see how all those things Dan asked for work together:
Install/Upgrade inxi. Buster's inxi is a broken antique. Best to install
directly
from upstre
On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...
On December 2, 2022 7:43 AM, Dan Ritter replied:
> I'm going to guess that this is a change in one or both of:
>
> - GPU firmware
> -
Kleene, Steven (kleenesj) wrote:
> Out of the blue today, my usual screen resolution (1920x1200) became
> unavailable. I booted to the console and called startx, which brings up
> fvwm. But my default base window went way off-screen, and the type was huge.
> xrandr said I was at
Out of the blue today, my usual screen resolution (1920x1200) became
unavailable. I booted to the console and called startx, which brings up
fvwm. But my default base window went way off-screen, and the type was huge.
xrandr said I was at 1024x768 and did not list the 1920x1200 option at all
y.com/aqua+vitae) from TheFreeDictionary.com (http://www.thefreedictionary.com)
Sent from Yahoo Mail on Android
"Andrew M.A. Cater" writes:
> On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
>> I am currently running Debian 10.
>>
>> sudo lspci|grep VGA
>> 01:05.0 VGA compatible controller: Advanced Micro Devices,
>> Inc. [AMD/ATI] RS780 [Radeon HD 3200]
>>
>> sudo xrandr
>>
>> Screen 0: minimu
On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
> I am currently running Debian 10.
>
> sudo lspci|grep VGA
> 01:05.0 VGA compatible controller: Advanced Micro Devices,
> Inc. [AMD/ATI] RS780 [Radeon HD 3200]
>
> sudo xrandr
>
> Screen 0: minimum 320 x 200, current 1440 x 900, maximum
I am currently running Debian 10.
sudo lspci|grep VGA
01:05.0 VGA compatible controller: Advanced Micro Devices,
Inc. [AMD/ATI] RS780 [Radeon HD 3200]
sudo xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA-0 connected primary 1440x900+0+0 (normal left inverted right
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)
&g
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.modes
> 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 re
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
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
On Fri, Jun 29, 2018 at 4:34 AM Darac Marjal
wrote:
>
> Is it BIOS (in which case you have grub-pc
> installed) or (U)EFI (in which case you have grub-efi-ia32 or
> grub-efi-amd64 installed)?
>
I have UEFI (which I just learned), but grub-pc is installed. I assume
that's because the UEFI has leg
On Fri, Jun 29, 2018 at 12:49:53AM -0500, Lance Simmons wrote:
I want to change grub screen resolution.
Four facts:
(1) "vbeinfo" and "videoinfo" return no result in grub. The screen blanks
and eventually I restart the computer.
This /probably/ means that grub
Lance Simmons composed on 2018-06-29 00:49 (UTC-0500):
> (1) "vbeinfo" and "videoinfo" return no result in grub. The screen blanks
> and eventually I restart the computer.
Neither work at my current Grub2-efi prompt on Kaby Lake. From videoinfo, I do
get a two line output:
List of suppo
Hi,
On Fri, 29 Jun 2018 00:49:53 -0500
Lance Simmons wrote:
(...)
>
> (4) So far, changing GRUB_GFXMODE (in /etc/default/grub) to several of
> the resolutions I know my monitor supports (and then running "sudo
> update-grub") has no effect.
>
> Any suggestions?
I had a similar problem some ti
I want to change grub screen resolution.
Four facts:
(1) "vbeinfo" and "videoinfo" return no result in grub. The screen blanks
and eventually I restart the computer.
(2) "hwinfo --framebuffer" returns no result. I would append the logfile,
but it's 7500 lin
ou ran gNewSense which is a version of Debian recommended
> by the Free Software Foundation then you would have to use xorg.conf to set
> the screen resolution.
>
> Think gNewSense = orthodox ; Debian = reformed; Ubuntu =
> secular/heterodox..
>
> MF
>
>
>
, and Debian doesn't.
cathy
On 01/12/2017 06:36 AM, Lisi Reisz wrote:
On Monday 09 January 2017 10:34:23 manashpal wrote:
After installing Debian latest Jessie in my system, I am getting a 1024*768
screen resolution, but my monitor can render 1366*768. it is unlikely to
have got such a unexpec
On Monday 09 January 2017 10:34:23 manashpal wrote:
> After installing Debian latest Jessie in my system, I am getting a 1024*768
> screen resolution, but my monitor can render 1366*768. it is unlikely to
> have got such a unexpected screen resolution like 1024*768. on the other
>
em, I
am getting a 1024*768 screen resolution, but my monitor can render
1366*768. it is unlikely to have got such a unexpected screen
resolution like 1024*768. on the other hand ubuntu, fedora, kali
and many more linux distros has never disappoint me such a way.
how can I f
Op Mon, 09 Jan 2017 11:34:23 +0100 schreef manashpal
:
After installing Debian latest Jessie in my system, I am getting a
1024*768 screen resolution, but my monitor can render >1366*768. it is
unlikely to have got such a unexpected screen resolution like 1024*768.
on the other h
After installing Debian latest Jessie in my system, I am getting a 1024*768
screen resolution, but my monitor can render 1366*768. it is unlikely to have
got such a unexpected screen resolution like 1024*768. on the other hand
ubuntu, fedora, kali and many more linux distros has never
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 10
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 asp
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
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 1600
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 cir
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 el
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
Thanks.
On 09/26/2014 01:19 AM, Chris Bannister wrote:
Maybe X isn't getting the correct resolution from the monitor. Check the
xorg log file and see if that helps.
The Xorg log file ( /var/log/Xorg.0.log ) shows no relevant errors and
only a few items that seem to relate to the resolution.
On Thu 25 Sep 2014 at 20:48:59 +0300, Lars Noodén wrote:
> On 09/25/2014 08:28 PM, Steve Litt wrote:
> >First, how confident are you that this is *only* in Xfce, and not in
> >LXDE and Openbox and who knows what other window managers? Perhaps it's
> >an X thing, plain and simple.
>
> There are st
On Thu, Sep 25, 2014 at 08:48:59PM +0300, Lars Noodén wrote:
> On 09/25/2014 08:28 PM, Steve Litt wrote:
> >First, how confident are you that this is *only* in Xfce, and not in
> >LXDE and Openbox and who knows what other window managers? Perhaps it's
> >an X thing, plain and simple.
>
> There are
On 09/25/2014 08:28 PM, Steve Litt wrote:
First, how confident are you that this is *only* in Xfce, and not in
LXDE and Openbox and who knows what other window managers? Perhaps it's
an X thing, plain and simple.
There are still some configuration options I have missed that are needed
to try L
On Thu, 25 Sep 2014 20:08:54 +0300
Lars Noodén wrote:
> In XFCE4, on Jessie, I am getting a display resolution of 1400x1050
> instead of 1680x1050. If I go to the XFCE Menu -> Settings ->
> Display, it gives me only a single choice, that of 1400x1050, not
> higher or lower.
>
> xrandr seems to
In XFCE4, on Jessie, I am getting a display resolution of 1400x1050
instead of 1680x1050. If I go to the XFCE Menu -> Settings -> Display,
it gives me only a single choice, that of 1400x1050, not higher or lower.
xrandr seems to be able to see the maximum resolution:
$ xrandr
xrandr: Failed t
On 02 Oct 2013, Stan Hoeppner wrote:
[snip]
> > No apology needed. You did in fact peg my age correctly; I will be 61 next
> > month. And I too have known people who run less than the native resolution
> > to make the fonts bigger. When I get to that point, though, I will simply
> > increase
>
On 06/04/12 16:17, Bonno Bloksma wrote:
> there is no man page for grub.
!?
grub-bin2h
grub-editenv
grub-emu
grub-install
grub-mkconfig
grub-mkdevicemap
grub-mkfont
grub-mkimage
grub-mkpasswd-pbkdf2
grub-mkrelpath
grub-mkrescue
grub-probe
grub-reboot
grub-script-check
grub-set-default
grub-set
Hi,
>> AHA, an undocumented feature. At least, it is not documented in the
>> /etc/default/grub file itself.
> You need to do:
>
>info grub
>
> Bet you didn't know about that. :)
Well I knew about info but when I want to know about syntax I use mainly
man, but there is no man page for
On Thu 05 Apr 2012 at 11:48:57 +, Bonno Bloksma wrote:
> AHA, an undocumented feature. At least, it is not documented in the
> /etc/default/grub file itself.
You need to do:
info grub
Bet you didn't know about that. :)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
h time by
>> adding the line set gfxpayload=keep at the proper place.
> You should not need to change the 00_header script.
>
> Adding a line into /etc/default/grub, after the GRUB_GFXMODE entry with
>
> GRUB_GFXPAYLOAD_LINUX=keep
>
> should make grub keep the screen reso
Hi,
>> I do not understand the defaults build into Grub2. For instance the
>> default resolution, it is at 640x480. Which machine running Linux
>> cannot at least use 800x600? Or is Grub2 made with hendhelds as a
>> target environment as well?
> Yes - especially those squint-o-vision "widescre
On 04/04/12 11:37, Bonno Bloksma wrote:
> The second thing I don not understand it why Grub2 will not keep the
> screen resolution after the menu has gone. Why does it by default
> ALWAYS go back to 640x480 even when the menu is shown at a higher
> resolution?
Grub is essentially
On 04/04/12 11:37, Bonno Bloksma wrote:
Hi,
When I install a Squeeze machine, or when I update a Lenny machine to Squeeze,
the first thing I do is to change the screen resolution so I can get some more
tekst on the console when I need it. Of course most of the time I use ssh (or
PuTTY) to go
On 04/04/12 20:37, Bonno Bloksma wrote:
> Hi,
>
> When I install a Squeeze machine, or when I update a Lenny machine
> to Squeeze, the first thing I do is to change the screen resolution
> so I can get some more tekst on the console when I need it. Of course
> most of the time I
Hi,
When I install a Squeeze machine, or when I update a Lenny machine to Squeeze,
the first thing I do is to change the screen resolution so I can get some more
tekst on the console when I need it. Of course most of the time I use ssh (or
PuTTY) to go to a server and I can choose the screen
On Sun, 8 Jan 2012 01:11:37 +
Brian wrote:
> On Sat 07 Jan 2012 at 11:49:08 +0200, Andrei Popescu wrote:
>
> > Did you try without the Modeline? As far as I know X should be able
> > to compute it based on HorizSync, VertRefresh and Modes.
>
> X may indeed do this but, after commenting out
On Sat 07 Jan 2012 at 11:49:08 +0200, Andrei Popescu wrote:
> Did you try without the Modeline? As far as I know X should be able to
> compute it based on HorizSync, VertRefresh and Modes.
X may indeed do this but, after commenting out Modeline, the best it
could offer was 1024x768.
> Also, it
On Fri, 06 Jan 2012 18:37:01 +, Andrew Wood wrote:
> On 06/01/12 18:21, Camaleón wrote:
>> Yup, you have to add the unexistant mode before you can use it :-)
>> Steps are detailed at "Adding undetected resolutions" section.
>> Greetings,
>
> OK, in an ideal world though shouldnt the board 'an
On Vi, 06 ian 12, 23:28:07, Brian wrote:
>
> I'll not bore you with why it happens but the EDID data are not passed to
> X on a couple of my machines, My xorg.conf is usually non-existent but
> in this case I have:
>
>Section "Monitor"
>Identifier "1905FP"
>Modeline "1280x1024"
On Fri 06 Jan 2012 at 18:37:01 +, Andrew Wood wrote:
> OK, in an ideal world though shouldnt the board 'announce' that it
> supports that mode when probed?
I think X can only work with what it is given. If the monitor fails for
some reason to impart information X's idea of what is possible
Andrew Wood:
> On 06/01/12 18:21, Camaleón wrote:
>> Yup, you have to add the unexistant mode before you can use it :-)
>> Steps are detailed at "Adding undetected resolutions" section.
>> Greetings,
>
> OK, in an ideal world though shouldnt the board 'announce' that it
> supports that mode when p
On 06/01/12 18:21, Camaleón wrote:
Yup, you have to add the unexistant mode before you can use it :-)
Steps are detailed at "Adding undetected resolutions" section. Greetings,
OK, in an ideal world though shouldnt the board 'announce' that it
supports that mode when probed?
--
To UNSUBSCRI
On Fri, 06 Jan 2012 17:42:37 +, Andrew Wood wrote:
> On 06/01/12 16:59, Camaleón wrote:
>> On Thu, 05 Jan 2012 23:59:45 +, Andrew Wood wrote:
>>
>>> Ive got an LCD screen whose native resolution is 1440x900 yet i can
>>> only get Wheezy to display 1024x768. No higher resolution is listed i
Thanks guys, xrandr gives:
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis)
0mm x 0mm
1024x768 60.0*
800x60060.3 56.2
848x48060.0
640x48059.9
DVI1 disconnected
On Thu, 05 Jan 2012 23:59:45 +, Andrew Wood wrote:
> Ive got an LCD screen whose native resolution is 1440x900 yet i can only
> get Wheezy to display 1024x768. No higher resolution is listed in System
> Settings. How do I enable a higher resolution please?
What's the output of "xrandr"?
You
Andrew Wood wrote:
Hi Kevin
yes the xserver-xorg-video-intel package is installed. how do i check
which driver is actually being used? one strange thing is that the
kernel is printing out the following to the console, not sure what it
means, could it be a fault with the controller board in the
You can tell by looking in /var/log/Xorg.0.log. If after looking at
the log file, the problem isn't readily apparent, post the contents
here, and someone should be able to figure out what's wrong.
-- Kevin
The pertinent contents of the log seem to be as follows. Im not sure how
it works.
On Vi, 06 ian 12, 02:31:17, Andrew Wood wrote:
> Hi Kevin
>
>
> yes the xserver-xorg-video-intel package is installed. how do i
> check which driver is actually being used? one strange thing is that
> the kernel is printing out the following to the console, not sure
> what it means, could it be a
On 01/05/2012 06:31 PM, Andrew Wood wrote:
Hi Kevin
yes the xserver-xorg-video-intel package is installed. how do i check
which driver is actually being used? one strange thing is that the
kernel is printing out the following to the console, not sure what it
means, could it be a fault with t
Hi Kevin
yes the xserver-xorg-video-intel package is installed. how do i check
which driver is actually being used? one strange thing is that the
kernel is printing out the following to the console, not sure what it
means, could it be a fault with the controller board in the LCD?
353.94242
On 01/05/2012 04:30 PM, Andrew Wood wrote:
Hi Bob
lspci gives:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controll
Hi Bob
lspci gives:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
On 06/01/12 00:23, Bob Proul
Hi Bob
lspci gives:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
On 06/01/12 00:23, Bob Proul
Hi Bob
lspci gives:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
On 06/01/12 00:23, Bob Proul
Hi Bob
lspci gives:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME,
943/940GML Express Integrated Graphics Controller (rev 03)
On 06/01/12 00:23, Bob Proul
Sorry. should also have added the graphics chipset is an intel gma 950
integrated onto an atom itx motherboard.
--
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/4f063
1 - 100 of 484 matches
Mail list logo
