On Fri, 15 Dec 2017, davidson wrote:
On Thu, 14 Dec 2017, josh cha wrote:
How do i fix screen flickering while scrolling and pressing down
buttion? While im on my command-line applications like w3m?
I notice screen flickering while scrolling on down button. its a
problem since stretch
On Thu, 14 Dec 2017, josh cha wrote:
How do i fix screen flickering while scrolling and pressing down
buttion? While im on my command-line applications like w3m?
I notice screen flickering while scrolling on down button. its a
problem since stretch release.
Does this happen all the time, or
Alexandre Rossi composed on 2017-12-14 22:56 (UTC+0100):
> Two other PCs (Linux and Windows) going through the same HDMI cable to
> the same TV and same TV port using the same 1920x1080 resolution work
> perfectly.
How long is the cable? Do you have access to another to
On 15/12/17 10:56, Alexandre Rossi wrote:
I'm experiencing red blinking pixels in dark areas in the displayed
Xorg picture on my TV connected using a HDMI cable.
Alexandre,
can you test with another HDMI cable? Just because the HDMI cable works
under Windows or Linux with a different GPU does
Hi,
I finally got some time to investigate further.
Setup
I'm running Debian Stretch with a backported 4.13 Linux kernel on an
Intel Kaby Lake (chipset H110 and HD graphics 630) machine. I've
installed firmware-misc-nonfree and updated my BIOS to fix the Kavy
Lake HT bug.
Problem
I'm experienc
How do i fix screen flickering while scrolling and pressing down buttion?
While im on my command-line applications like w3m?
I notice screen flickering while scrolling on down button. its a problem
since stretch release.
My laptop
Levono thinkpad T510
Core i5 450m
4gb
240gb ssd
Alexandre Rossi wrote on 12/11/17 10:05:
>> could you show your Xorg.0.log files?
>
> Here it is attached.
>
>> The Kaby Lake GPU needs some firmware. Therefore, what is the print out of
>> grep firmware /var/log/dmesg
>
> $ sudo dmesg | grep firmware
> [9.165601] i915 :00:02.0: firmwa
> could you show your Xorg.0.log files?
Here it is attached.
> The Kaby Lake GPU needs some firmware. Therefore, what is the print out of
> grep firmware /var/log/dmesg
$ sudo dmesg | grep firmware
[9.165601] i915 :00:02.0: firmware: direct-loading firmware
i915/kbl_dmc_ver1_01.bin
[
Hi,
could you show your Xorg.0.log files?
The Kaby Lake GPU needs some firmware. Therefore, what is the print out of
grep firmware /var/log/dmesg
?
Regards,
jvp.
> The image with errors looks as it was manipulated in a photoeditor, eg.
> Gamma/levels curves ... Does the driver have some image adjustment enabled?
I use defaults everywhere, and the behavior is the same with a ubuntu
live image.
$ xgamma
-> Red 1.000, Green 1.000, Blue 1.000
The image with errors looks as it was manipulated in a photoeditor, eg.
Gamma/levels curves ... Does the driver have some image adjustment enabled?
> So the problem only happens with that PC _AND_ Linux/Xorg.
I'm no expert here, but I'd suspect the driver.
I'd also be looking systematically at gradations of known colours
(perhaps start with a colour wheel) to try and tie down where the
errors occur, and whether they're r
> Screenshot [1] looks normal to me, but on screenphoto [2] I clearly see
> red-ish stripes and pink spots in the middle.
>
> Now it looks like your LCD could be faulty not PC hardware\software. Can you
> test it with another LCD monitor, or connect it to TV via HDMI cable if it's
> possible?
The
low (in videos) a single set of colors (dark brownish areas). You
> can look at a screenshot[1] of the root window image as taken by
> imagemagick and the photo[2] of the result on the screen.
>
> [1] https://sml.zincube.net/~niol/tmp/screenshot.jpg
> [2] https://sml.zincube.net/~n
ook at a screenshot[1] of the root window image as taken by
imagemagick and the photo[2] of the result on the screen.
[1] https://sml.zincube.net/~niol/tmp/screenshot.jpg
[2] https://sml.zincube.net/~niol/tmp/screenphoto.jpg
> I'd suggest to check RAM first of all with `memtest86+`
On Thu, Dec 07, 2017 at 05:20:41PM +0500, Alexander V. Makartsev wrote:
>
> There was a microcode bug discovered recently in Kabylake-Skylake CPUs.
> It causes memory corruption if I remember it correctly. It could be
> fixed for certain CPUs by updating firmware for your motherboard or
> installin
On 07.12.2017 16:33, Alexandre Rossi wrote:
> (please CC me as I am not subscribed to the list)
>
> Hi,
>
> I am experiencing on-screen artifacts (red dots) when running at
> 1920x1080 on HDMI out. I've ruled out a hardware (cable, TV or GPU)
> issue by installing win10
(please CC me as I am not subscribed to the list)
Hi,
I am experiencing on-screen artifacts (red dots) when running at
1920x1080 on HDMI out. I've ruled out a hardware (cable, TV or GPU)
issue by installing win10 which does not show those problems.
This is by using stretch, issue occurs
On 24 November 2017 at 17:33, John Cunningham wrote:
> FWIW, I have buster/xfce on a laptop and have the same problem. Backlight is
> fine. I thought about the external monitor trick, too, but I haven't tried
> it yet.
> --John
Well I didn't manage to wake the screen (in
te:
>
>> On 11/24, Jaime T wrote:
>> >Hi all.
>> >
>> >I'm running stable (stretch)/xfce on an hp/compaq nx6110 laptop, and
>> >when the screen blanks, I can't get it to wake up again (nothing
>> >appears on the screen when I press the keys
'm running stable (stretch)/xfce on an hp/compaq nx6110 laptop, and
> >when the screen blanks, I can't get it to wake up again (nothing
> >appears on the screen when I press the keys on the keyboard and move
> >the mouse).
> >
> >The closest debian bug report t
On 11/24, Jaime T wrote:
Hi all.
I'm running stable (stretch)/xfce on an hp/compaq nx6110 laptop, and
when the screen blanks, I can't get it to wake up again (nothing
appears on the screen when I press the keys on the keyboard and move
the mouse).
The closest debian bug report that
Hi all.
I'm running stable (stretch)/xfce on an hp/compaq nx6110 laptop, and
when the screen blanks, I can't get it to wake up again (nothing
appears on the screen when I press the keys on the keyboard and move
the mouse).
The closest debian bug report that I've seen is:
https://
Here is the output of 'lshw':
BTW, ctrl+alt+F1 will get me to the login screen.
latituded505
description: Portable Computer
product: Latitude D505
vendor: Dell Inc.
serial: 10Y2F61
width: 32 bits
capabilities: smbios-2.3 dmi-2.3
configuration: boot=norm
ttings to turn the screen off after some time,
> but I cannot get it back on.
> The touchpad, space bar, enter key does only turn the screen on in a
> sense that it's on but black. I can increase/decrease the blackness
> with the function keys, but I don't get the desktop.
On an older (windows XP era) laptop running Stretch with XFCE desktop I
have set the power settings to turn the screen off after some time, but I
cannot get it back on.
The touchpad, space bar, enter key does only turn the screen on in a sense
that it's on but black. I can increase/decreas
Cheers Greg :)
Pol
On Tue, Nov 07, 2017 at 05:08:45PM +0100, Debian EN wrote:
> with debian9 how disable clear screen after start-up of system?
>
> I remember with debian 8 (maybe) there was /etc/inittab
http://mywiki.wooledge.org/SystemdNoClear
Hi all
with debian9 how disable clear screen after start-up of system?
I remember with debian 8 (maybe) there was /etc/inittab
thanks for help :)
--
Pol
On 10/12/17 01:00, Curt wrote:
On 2017-10-12, David Christensen wrote:
Checking the bugs for 'lightdm-gtk-greeter' -- nope:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=lightdm-gtk-greeter
Not debian, but, yep ...
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/
On 10/12/17 03:56, Darac Marjal wrote:
On Wed, Oct 11, 2017 at 11:13:52PM -0700, David Christensen wrote:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
COMMAND
9957 lightdm 20 0 587348 51196 25444 R 88.2 2.5 2:41.03
lightdm-gtk-gre
...
According to StackOverfl
On Tue 10 Oct 2017 at 21:45:29 (+0200), Tim wrote:
> I experience this bug in jessie as well. However, that bug got fixed in
> stretch. The bug I'm now facing is random (short) periods of a
> black/blank screen. Just as anxiousmac nicely summarized said before:
[…]
> I will t
On Wed, Oct 11, 2017 at 11:13:52PM -0700, David Christensen wrote:
On 10/11/17 21:43, davidson wrote:
On Wed, 11 Oct 2017, David Christensen wrote:
[cut]
If I lock the screen and SSH in from another machine, 'top' says:
...
PID USER PR NI VIRT RES SHR S %CPU %ME
On 2017-10-12, David Christensen wrote:
>
> Checking the bugs for 'lightdm-gtk-greeter' -- nope:
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=lightdm-gtk-greeter
>
Not debian, but, yep ...
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1635125
https://bugs.launch
4.9.51-1 (2017-09-28)
x86_64 GNU/Linux
Recently, I've noticed that if I lock the screen and walk away, when I
return the CPU fan is on high speed. When I unlock the screen, the
CPU Graph indicates that one of my two CPU cores was pegged at 100%,
but dropped off once I logged in.
If I
) x86_64
GNU/Linux
Recently, I've noticed that if I lock the screen and walk away, when I return
the CPU fan is on high speed. When I unlock the screen, the CPU Graph
indicates that one of my two CPU cores was pegged at 100%, but dropped off
once I logged in.
If I lock the screen and S
that if I lock the screen and walk away, when I
return the CPU fan is on high speed. When I unlock the screen, the CPU
Graph indicates that one of my two CPU cores was pegged at 100%, but
dropped off once I logged in.
If I lock the screen and SSH in from another machine, 'top' say
as
> > I recall, was that certain display hardware inverts the sense of the
> > intensity, so that instead of it going from 0 (dark) to max (bright) it
> > goes from 0 (bright) to max (dark). X.org sets the display brightness
> > to what it thinks is max on the log in scre
ntensity, so that instead of it going from 0 (dark) to max (bright) it
> goes from 0 (bright) to max (dark). X.org sets the display brightness
> to what it thinks is max on the log in screen to compensate for the
> possibility that was turned all the way down by a previous user.
>
> Wh
On Sunday, 8 October 2017 11:10:04 UTC+1, Tim wrote:
> First of all, sorry for my late reply: It took me a while before I
> realized this is a mailing list.
[snip]
I have exactly the same problem with the same model of laptop ( HP EliteBook
840)
>From time to time the screen goes bl
screen turn blank after a random time, or at the time of
an event (like starting X, or starting an application, or some
heavy processing etc). After a minute or half an hour?
I want to clarify it happens at random times, not at a certain interval
after boot or during any event. I now also realize
First of all, sorry for my late reply: It took me a while before I
realized this is a mailing list. (I also hope Evolution is smart enough
to figure out to send the right In-Reply-To header.)
On Sat, 23 Sep 2017 20:28:59 -0500, David Wright wrote:
> Does the screen turn blank after a random t
ok 840
notebook. Since then, the laptop's screen sometimes turns blank, i.e.,
as if there is no input to the screen. Strangely enough, whenever I
attach another display, the other display doesn't go blank: It's only
the internal display of the laptop itself that turns completely b
> >> which package I should file the bug against. Moreover, I haven't found
> >> a way to debug the issue either.
> >>
> >> I've recently done a fresh installed of stretch on an HP EliteBook 840
> >> notebook. Since then, the laptop's screen
done a fresh installed of stretch on an HP EliteBook 840
> notebook. Since then, the laptop's screen sometimes turns blank, i.e.,
> as if there is no input to the screen. Strangely enough, whenever I
> attach another display, the other display doesn't go blank: It's only
>
>> sure which package I should file the bug against. Moreover, I
> >> haven't found a way to debug the issue either.
> >>
> >> I've recently done a fresh installed of stretch on an HP EliteBook
> >> 840 notebook. Since then, the laptop's screen som
a way to debug the issue either.
>>
>> I've recently done a fresh installed of stretch on an HP EliteBook 840
>> notebook. Since then, the laptop's screen sometimes turns blank, i.e.,
>> as if there is no input to the screen. Strangely enough, whenever I
>> at
done a fresh installed of stretch on an HP EliteBook 840
> notebook. Since then, the laptop's screen sometimes turns blank, i.e.,
> as if there is no input to the screen. Strangely enough, whenever I
> attach another display, the other display doesn't go blank: It's
ok 840
notebook. Since then, the laptop's screen sometimes turns blank, i.e.,
as if there is no input to the screen. Strangely enough, whenever I
attach another display, the other display doesn't go blank: It's only
the internal display of the laptop itself that turns completely blac
Hi,
I would like to report a bug for Debian stretch, however, I'm not sure
which package I should file the bug against. Moreover, I haven't found
a way to debug the issue either.
I've recently done a fresh installed of stretch on an HP EliteBook 840
notebook. Since then, the
On 09/03/2017 10:32 PM, Jaehong Park wrote:
I just installed Debian 9 yesterday.
And I gave a fatal problem with login screen.
After grub it only showing me black screen, but enter my password it starts
showing me my desktop environment screen correctly.
What�s the cause?
I would add
Setting up VNC, both machines running Debian Stretch with MATE (no VMs
involved). Using tightvncserver, and xtightvncviewer as well as vinagre
as client. In both cases I see some corruption of the upper MATE panel
with red circles containing a number or letter. Anyone have any idea
what this is fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Sep 04, 2017 at 01:32:07PM +0800, Jaehong Park wrote:
> I just installed Debian 9 yesterday.
> And I gave a fatal problem with login screen.
> After grub it only showing me black screen, but enter my password it starts
> showing m
I just installed Debian 9 yesterday.
And I gave a fatal problem with login screen.
After grub it only showing me black screen, but enter my password it starts
showing me my desktop environment screen correctly.
What’s the cause?
Op Fri, 21 Jul 2017 22:26:01 +0200 schreef :
Hello Debian great OS!
I have gtx1060 and monitor resolution 1920x1200
Debian 9.0.1 live cd.
I get black screen "Resolution not support"
I think it's not good.
You are probably using the open source nouveau Nvidia driver,
Hello Debian great OS!
I have gtx1060 and monitor resolution 1920x1200
Debian 9.0.1 live cd.
I get black screen "Resolution not support"
I think it's not good.
On di jul 11, 2017 at 09:31:42, Greg Wooledge wrote:
> On Tue, Jul 11, 2017 at 03:19:05PM +0200, janm wrote:
> > This works well, I just use startx at boot. However, locking the screen and
> > returning from suspend presents me with a blank screen. When I do
> > Ctrl+Alt+F7,
use startx at boot. However, locking the screen and
returning from suspend presents me with a blank screen. When I do Ctrl+Alt+F7,
I get a blank screen with a blinking cursor. Ctrl+Alt+F2 etc. get me other
tty's, but that means losing my session.
Not sure if light-locker is involved still,
On Tue, Jul 11, 2017 at 03:19:05PM +0200, janm wrote:
> This works well, I just use startx at boot. However, locking the screen and
> returning from suspend presents me with a blank screen. When I do
> Ctrl+Alt+F7, I get a blank screen with a blinking cursor. Ctrl+Alt+F2 etc.
>
r.net>> wrote:
>
> Hello Forum,
>
> I have recently migrated from Jessie to Stretch. I have a couple of minor
> issues.
> One of them concern Xfce: some time my fingers seem to do a combination
> of keys
> that magnifies the screen: I got a floating deskt
On 06/28/2017 12:26 PM, Jerome BENOIT wrote:
Hello Forum,
I have recently migrated from Jessie to Stretch. I have a couple of minor
issues.
One of them concern Xfce: some time my fingers seem to do a combination of keys
that magnifies the screen: I got a floating desktop environment that is
Hello Forum,
I have recently migrated from Jessie to Stretch. I have a couple of minor
issues.
One of them concern Xfce: some time my fingers seem to do a combination of keys
that magnifies the screen: I got a floating desktop environment that is lager
than my actual screen. Does any know the
On 06/25/2017 02:34 PM, Darac Marjal wrote:
> On Sun, Jun 25, 2017 at 01:51:01PM -0500, Glenn Holmer wrote:
>> I've got a freeshell.org account, and they're running NetBSD. When I SSH
>> into that account, the terminal looks fine, but when I start irssi, the
>>
On Sun, Jun 25, 2017 at 01:51:01PM -0500, Glenn Holmer wrote:
I've got a freeshell.org account, and they're running NetBSD. When I SSH
into that account, the terminal looks fine, but when I start irssi, the
entire screen blinks on and off about once a second. This is from my
Debian S
I've got a freeshell.org account, and they're running NetBSD. When I SSH
into that account, the terminal looks fine, but when I start irssi, the
entire screen blinks on and off about once a second. This is from my
Debian Stretch box running KDE, with konsole as terminal and bash as sh
Catherine Gramze composed on 2017-03-14 16:47 (UTC):
Note that I am not necessarily looking for a solution. I have a working 4K
system using the integrated graphics card. I most want to understand WHY
Jessie doesn't work with the radeon driver.
For that I have to suggest asking the specialists
or, so it's probably already too late to expect
a report to result in a fix in Debian's "next" release.
Yes, something has regressed. The radeon and fglrx drivers both worked in
Wheezy for my PCI card (but obviously not simultaneously).
I believe that is a different issue than
Le 14/03/2017 à 12:31, Kostiantyn Ponomarenko a écrit :
> I managed to install Debian on z240.
good news :-)
[...]
> Thought, I still wonder why Ubuntu works with "Legacy boot disabled
> and secure boot disabled" out of the box.
may be that has something to do with HP having a commercial agreeme
firmware each option leads to these behavior:
1. Debian installation works, but firmware cannot find bootable file(?).
That means every boot you need to choose "boot from file" and point to
"grubx64.efi".
2. Black screen after "Debian UEFI Installation menu".
With v1.50
David Wright composed on 2017-03-13 23:43 (UTC-0500):
Another oddity is that dmesg always says (both then and now):
[drm] Loading R300 Microcode
radeon :01:00.0: firmware: failed to load radeon/R300_cp.bin (-2)
radeon :01:00.0: Direct firmware load failed with error -2
radeon :01:00.
David Wright composed on 2017-03-13 23:43 (UTC-0500):
When you say get rid of drivers, is that just things like
xserver-xorg-video-foo, or do you also mean things like
kernel modules?
1-In the context of only FOSS in use, I had only Xorg in mind.
2-In the context of proprietary drivers having
On Mon 13 Mar 2017 at 19:30:32 (-0400), Felix Miata wrote:
> Simplest way to use is purge all traces of Intel, proprietary and
> AMD/ATI drivers, install xserver-xorg-video-modesetting, then
> restart.
When you say get rid of drivers, is that just things like
xserver-xorg-video-foo, or do you als
Catherine Gramze composed on 2017-03-14 02:18 (UTC):
As I mentioned in my first post, it is a display issue. The BIOS boot screen
never displays, nor does any of the boot sequence, when using the Radeon R9
270X card. Forcing it into the BIOS setup won't make it display the screen
it
the difficulty is lack of keyboard response at boot, you
can probably work around it by plugging in a PS/2 keyboard.
As I mentioned in my first post, it is a display issue. The BIOS boot screen
never displays, nor does any of the boot sequence, when using the Radeon R9
270X card. Forcing it into
Catherine Gramze composed on 2017-03-13 20:56 (UTC-0400):
Both are not usable simultaneously. My BIOS requires me to disable the
on-board graphics to use the Radeon card. Getting into BIOS is impossible
with the Radeon in use.
Probably not impossible, but difficult I cannot doubt. It ought to
On Mon, Mar 13, 2017 at 7:30 PM, Felix Miata wrote:
> Catherine Gramze composed on 2017-03-13 18:49 (UTC-0400):
>
> Is Plymouth installed?
No, it is not. I checked.
According to that URI it is a refresh of Radeon HD 7870 that apparently
> nobody ever updated Wikipedia to include. The Radeon
y days, to remember when
it goes blank using the Catalyst driver. IIRC it simply never displays
anything at all until I get the graphical login screen at native 4K
resolution. I suspect my Dell doesn't like the low resolution.
http://www1.la.dell.com/vc/en/corp/peripherals/dell-p2415q-monitor/p
Meanwhile, my MSI Z87-43G motherboard boot screen doesn't display unless I
>
>> use the built-in graphics card. When I use my Radeon R9 270X it just goes
>> blank, but still boots through to the default first grub menu item. 4K
>>
>
> Goes blank when exactly? Do
Catherine Gramze composed on 2017-03-13 15:35 (UTC-0400):
Meanwhile, my MSI Z87-43G motherboard boot screen doesn't display unless I
use the built-in graphics card. When I use my Radeon R9 270X it just goes
blank, but still boots through to the default first grub menu item. 4K
Goes blank
Le 13/03/2017 à 18:25, Kent West a écrit :
> Maybe turn off UEFI (assuming your mobo has legacy BIOS support), just
> to see if that gives you any clues?
Yes, tinkering with the UEFI of the machine is a good idea, particularly
switch off secure boot, tpm and the like. Also HP is known for its
non
I tried to boot with variations of these options
"DEBIAN_FRONTEND=text|newt|gtk and vga=normal fb=false", but no luck.
I was also comparing "boot/grub/grub.cfg" from Debian and Ubuntu. I
found that Debian has there all that Ubuntu has and even more
settings.
Don't know what to do.
Any other though
On Mar 13, 2017 08:27, "didier gaumet" wrote:
Le 13/03/2017 à 13:21, Kostiantyn Ponomarenko a écrit :
[...]
> Any other thoughts?
> Thank you,
Maybe turn off UEFI (assuming your mobo has legacy BIOS support), just to
see if that gives you any clues?
--
Kent
Le 13/03/2017 à 13:21, Kostiantyn Ponomarenko a écrit :
[...]
> Any other thoughts?
> Thank you,
> Kostia
look at:
https://www.debian.org/releases/stable/amd64/ch05s03.html.en#installer-args
maybe you could for example try a combination of some parameters like
DEBIAN_FRONTEND=text|newt|gtk and vg
ebian UEFI Installer menu", I see
black screen only.
I suspect that the grub config is missing some options.
Any other thoughts?
Thank you,
Kostia
On Fri, Mar 10, 2017 at 8:32 PM, didier gaumet wrote:
>
> a possible cause of your problem could be a need for a firmware,
> probably fo
a possible cause of your problem could be a need for a firmware,
probably for the graphic card, that is not included (proprietary) in the
installer. so you could either:
- install with the text-mode installer a text-only environment. reboot,
then install needed firmwares, then install a graphic en
Hi folks!
I am trying to install Debian on my new HP z240 box.
I tried Debian 8 and Debian 9 RC2 installers, but neither succeeded.
When I choose to boot from a pen drive I see "Debian UEFI Installer
menu". Then I choose "Install" and get a black screen. Switching to a
virtu
AMD64 Stretch LXDE
In recent weeks when logging in from start or from a screensaver login
or when hitting the shutdown/reboot .. I notice a brief (maybe 1/2 sec)
flickering of the screen. This doesn't appear or happen with anything
else, I don't think it relates to monitor re-adjustmen
swjatoslaw gerus composed on 2017-02-15 00:45 (UTC+0100):
How set screen( not x 11 !) color in Debian to ANSI black or
#00via command line ?
Relevant comment would appreciated
I have
tty=$(tty); [ "$tty" != "${tty#/dev/tty[0-9]}" ] &&am
Gentlemen
How set screen( not x 11 !) color in Debian to ANSI black or
#00via command line ?
Relevant comment would appreciated
--
http://www.fastmail.com - Same, same, but different...
something
to do with my change from Awesome WM to i3 WM. The screen resolution on
my TP is allright in most of the cases. But on my attached 19" display
it's a mess. First with the display manager Lightdm, I have the
wallpaper all over the screen (which is what I want) but within that I
have
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
> to
>> do Alt-F2 (so going to tty2) and Alt-F1 and then I see tty1. In Google I
>> found
>> many similar problems but of no help to me. Any suggestions?
>
> I wonder if this problem's root could be related to this?:
> https://bugs.freedesktop.org/show_bug.cgi?i
The problem remains also with another window manager: icewm, as suggested by
Kamaraju, and also after `aptitude purge xserver-xorg-video-nouveau' as
suggested by Felix. Thanks to both. I have no idea of how to fix it.
Rodolfo
Dan Norton composed on 2016-12-17 20:57 (UTC-0500):
Felix Miata wrote:
> It's probably time to either switch to a newer PC, or try a less
> demanding DE, or even another distro, if the Debian installer is making
> it too hard for you to avoid Gnome...
Thanks for your help, Felix.
Glad
similar problems but of no help to me. Any suggestions?
I wonder if this problem's root could be related to this?:
https://bugs.freedesktop.org/show_bug.cgi?id=90572
startx exits to black screen
> Graphics: Card: NVIDIA NV5 [Riva TNT2 Model 64 / Model 64 Pro]
>Display Server: X
601 - 700 of 4531 matches
Mail list logo
