On 05/08/16 15:14, Ric Moore wrote:
On 08/04/2016 07:12 PM, Alan Chandler wrote:
I have mythtv installed from debian multimedia. I am running testing
Once you introduce Debian Multimedia to your mix, you get to keep all
the broken pieces. "These packages are known to not integrate well
with o
On 08/04/2016 07:12 PM, Alan Chandler wrote:
I have mythtv installed from debian multimedia. I am running testing
Once you introduce Debian Multimedia to your mix, you get to keep all
the broken pieces. "These packages are known to not integrate well with
other software packages in Debian and
I have mythtv installed from debian multimedia. I am running testing
About a week or so ago now, suddenly it has lost all its on screen text
when playing a video (recorded TV programs). The surrounding overlays
are all there, just the text is missing - including on pop up menus. As
soon
On Sun, 2016-06-26 at 03:13 +1200, cbannis...@slingshot.co.nz wrote:
> On Wed, Jun 22, 2016 at 05:06:13PM +0100, Oliver Elphick wrote:
> > I enabled the on-screen keyboard applet in Cinnamon so as to write
> > some
> > text with French accents. But then it kept on coming
On Wed, Jun 22, 2016 at 05:06:13PM +0100, Oliver Elphick wrote:
> I enabled the on-screen keyboard applet in Cinnamon so as to write some
> text with French accents. But then it kept on coming up when I didn't
> want it, every time I went into any text field. I removed the applet
>
I enabled the on-screen keyboard applet in Cinnamon so as to write some
text with French accents. But then it kept on coming up when I didn't
want it, every time I went into any text field. I removed the applet
from my toolbar - no difference. I found the cinnamon on-screen-
keyboard and de
Gene Heskett composed on 2016-06-12 19:54 (UTC-0400):
mc has been around for north of 30
years I believe, actually dateing back to dos-2.0 days or before.
MC is a 22 year old clone of Norton Commander for DOS (which at the time of
NC birth was v3.2, prior to existence of extended HD partition
Wright wrote:
> > > > It seems obvious to me, he's talking about screen corruption.
> > > > Gene, Is this when you close it down?
> > >
> > > He might be, except I've never seen screen corruption when running
> > > aptitude.
> >
>
On Sunday 12 June 2016 22:13:19 Henrique de Moraes Holschuh wrote:
> I can attest that Debian jessie's Konsole doesn't work quite right in
> every situation with the "TERM=xterm" and Debian's terminfo, for
> example.
Gene is in fact using, or not using, Konsole-Trinity, not KDE-Konsole.
Lisi
On Sun, 12 Jun 2016, Gene Heskett wrote:
> On Sunday 12 June 2016 00:09:54 Joe Pfeiffer wrote:
> > cbannis...@slingshot.co.nz writes:
> > > On Sat, Jun 11, 2016 at 10:04:27PM -0500, David Wright wrote:
> > > It seems obvious to me, he's talking about screen corrupti
On 02/04/16 08:50, Sven Joachim wrote:
> On 2016-04-02 06:51 +0300, Adam Wilson wrote:
>
>> On Fri, 01 Apr 2016 19:58:17 +0200
>> Sven Joachim wrote:
>>
>>> On 2016-04-01 13:40 -0400, Felix Miata wrote:
>>>
Peter Hillier-Brook composed on 2016-04-01 15:14 (UTC+0100):
> Following an
ktop.iso as well
>> as debian-live-8.3.0-amd64-gnome-desktop.iso.
>>
>> Instead of the GUI (desktop etc.) only a garbled screen: Sometimes
>> black with only a mouse pointer, sometimes yellow and green horizontal
>> blocks or other weird patterns. The system mostly hangs
doesn't even boot
> correctly.
>
> Besides that, my bug report would be as follows:
>
>
> Package: ???
> Version: 8.3.0-live ?
>
>
> No GUI when booting debian-live-8.3.0-i386-gnome-desktop.iso as well
> as debian-live-8.3.0-amd64-gnome-desktop.iso.
>
> Instea
llows:
Package: ???
Version: 8.3.0-live ?
No GUI when booting debian-live-8.3.0-i386-gnome-desktop.iso as well as
debian-live-8.3.0-amd64-gnome-desktop.iso.
Instead of the GUI (desktop etc.) only a garbled screen: Sometimes black with
only a mouse pointer, sometimes yellow and green horizontal
On 2016-04-02 06:51 +0300, Adam Wilson wrote:
> On Fri, 01 Apr 2016 19:58:17 +0200
> Sven Joachim wrote:
>
>> On 2016-04-01 13:40 -0400, Felix Miata wrote:
>>
>> > Peter Hillier-Brook composed on 2016-04-01 15:14 (UTC+0100):
>> >
>> >> Following an overnight shut down I couldn't reach the deskto
On Fri, 01 Apr 2016 19:58:17 +0200
Sven Joachim wrote:
> On 2016-04-01 13:40 -0400, Felix Miata wrote:
>
> > Peter Hillier-Brook composed on 2016-04-01 15:14 (UTC+0100):
> >
> >> Following an overnight shut down I couldn't reach the desktop manager
> >> the following day. Running a live system I
Himanshu Shekhar composed on 2016-04-01 22:00 (UTC+0530):
I am unable to use virtual console. Tried all combinations of cTRL+alt+f- .
Only X works fine. Rest all screens show an underscore (cursor) which
doesn't blink. I can't even login.
Even if you wait 30 seconds or a minute or more?
Goog
On Fri, 1 Apr 2016 13:34:04 -0400
Felix Miata wrote:
> Himanshu Shekhar composed on 2016-04-01 22:00 (UTC+0530):
>
> > I am unable to use virtual console. Tried all combinations of cTRL+alt+f- .
> > Only X works fine. Rest all screens show an underscore (cursor) which
> > doesn't blink. I can't
On 2016-04-01 13:40 -0400, Felix Miata wrote:
> Peter Hillier-Brook composed on 2016-04-01 15:14 (UTC+0100):
>
>> Following an overnight shut down I couldn't reach the desktop manager
>> the following day. Running a live system I was able to extract the
>> following via 'dmesg'. Does anyone recogn
Peter Hillier-Brook composed on 2016-04-01 15:14 (UTC+0100):
Following an overnight shut down I couldn't reach the desktop manager
the following day. Running a live system I was able to extract the
following via 'dmesg'. Does anyone recognise this, or can offer a
pointer to the problem?
Himanshu Shekhar composed on 2016-04-01 22:00 (UTC+0530):
I am unable to use virtual console. Tried all combinations of cTRL+alt+f- .
Only X works fine. Rest all screens show an underscore (cursor) which
doesn't blink. I can't even login.
Even if you wait 30 seconds or a minute or more?
Goog
I am unable to use virtual console. Tried all combinations of cTRL+alt+f- .
Only X works fine. Rest all screens show an underscore (cursor) which
doesn't blink. I can't even login.
Googling lead to a solution which said to change resolution in grub
configuration and enable grub terminal. It worked
Following an overnight shut down I couldn't reach the desktop manager
the following day. Running a live system I was able to extract the
following via 'dmesg'. Does anyone recognise this, or can offer a
pointer to the problem?
++
0
> Jessie (i686)
> GNOME 3.14.1
>
> I boot normally and log in. When pressing Fn+Home to increase brightness
> or Fn+End to decrease brightness, I observe a very sluggish behaviour of
> the on screen brightness display (i.e. the "indicator icon" with the bar
> beneat
vo T400
> Jessie (i686)
> GNOME 3.14.1
>
> I boot normally and log in. When pressing Fn+Home to increase
> brightness
> or Fn+End to decrease brightness, I observe a very sluggish behaviour
> of
> the on screen brightness display (i.e. the "indicator icon" with the
ss
or Fn+End to decrease brightness, I observe a very sluggish behaviour of
the on screen brightness display (i.e. the "indicator icon" with the bar
beneath, not the brightness itself which changes instantly): It takes
almost one second before the icon comes up and the change in brightne
On Wed, Feb 24, 2016 at 11:50:09AM -0600, Dennis Wicks wrote:
>
> What is the program that will connect to the current session on the remote
> system? I have used it before but I can't remember what it was.
In Gnome, I usually use Vinagre. In other DEs, I use ssvnc.
--
John
Hi,
I think I stumbled upon this before, but it was not that much of a problem for
me, because I never disable my laptops internal screen
- it's probably desktop-environment dependent, which one are you using?
- do you have an sshd running? ssh into you laptop and issue
# xrandr -
On Fri, 2016-02-26 at 22:06 +, Liam O'Toole wrote:
> On 2016-02-26, Albin Ludvig Otterhäll wrote:
> > I've my Thinkpad T430 connected to a docking station, which itself is
> > connected to two external monitors. When I dock my laptop the laptop
> > screen is b
On 2016-02-26, Albin Ludvig Otterhäll wrote:
> I've my Thinkpad T430 connected to a docking station, which itself is
> connected to two external monitors. When I dock my laptop the laptop
> screen is blacked out and the two monitors starts showing the desktop.
> No problems her
I've my Thinkpad T430 connected to a docking station, which itself is
connected to two external monitors. When I dock my laptop the laptop
screen is blacked out and the two monitors starts showing the desktop.
No problems here.
But when I disconnect the laptop from the docking station the de
On Wednesday 24 February 2016 12:12:54 Javier Vasquez wrote:
> > On Wed, Feb 24, 2016 at 11:50 AM, Dennis Wicks
wrote:
> > ...
> > What is the program that will connect to the current session on the
remote
> > system? I have used it before but I can't remember what it was.
>
> Are you looking f
> On Wed, Feb 24, 2016 at 11:50 AM, Dennis Wicks wrote:
> ...
> What is the program that will connect to the current session on the remote
> system? I have used it before but I can't remember what it was.
Are you looking for x11vnc [1][2] on the host you want to see? If so,
tigervnc and others c
I wish I could remember all of this stuff!
What is the program that will connect to the current session
on the remote system? I have used it before but I can't
remember what it was.
Many TIA!
Dennis
Le 21/02/2016 19:49, Sven Arvidsson a écrit :
I also suggest that you document your efforts on getting Debian to run
here: https://wiki.debian.org/InstallingDebianOn/
Both the stuff that works, and the stuff that doesn't.
I will, after having investigated a bit more :-)
I was worried to noti
On Sun, 2016-02-21 at 18:49 +0100, jdd wrote:
> forgot to say I can connect to the tablet with ssh, so I can see the
> logs, but with no clue (for me)
Xorg logs should be in /var/log/Xorg.0.log in jessie. you can post it
here if you need help understanding it.
If KMS doesn't work at all, it migh
jdd composed on 2016-02-21 18:46 (UTC+0100):
>> Can you double check that you're really running the Xorg intel driver
>> and isn't getting fbdev or something similar?
> don't know, because it do not start with the default grub config. I have
> to add nomodeset or i915.modeset=0 to have a display
forgot to say I can connect to the tablet with ssh, so I can see the
logs, but with no clue (for me)
jdd
have a display, including console
with
fbcon=rotate:1
in the grub linux line, I have finally a *terminal only* landscape
oriented screen (with target multi-users in systemd).
BUT
the boot menu is still portrait
if I run startxfce4, it comes with portrait orientation.
jdd
On Sun, 2016-02-21 at 11:00 +0100, jdd wrote:
> Hello,
>
> I try to install debian jessie on a windows 10 It Works TW891 tablet
> (with attached keyboard)
>
> using the hybrid 32/64 bits dvd, I could install jessie with xfce.
>
> But... it's installed in portrai
Hello,
I try to install debian jessie on a windows 10 It Works TW891 tablet
(with attached keyboard)
using the hybrid 32/64 bits dvd, I could install jessie with xfce.
But... it's installed in portrait mode (the screen need to be seen with
the longer size vertical), when the keyboard e
Hi folks,
does anyone know, how I can get full-screen in konqueror with html5?
I am using webkit and phonon-vlc. It looks like this option is disabled in
konqueror (icon is disabled/inactive), because in iceweasel full-screen is
possible (icon is active).
Thanks for any help.
Best
Hans
* On 2016 08 Jan 14:13 -0600, Sven Arvidsson wrote:
> Another option might be the last answer here:
> http://unix.stackexchange.com/questions/201900/run-true-multiple-process-instances-of-gnome-terminal
Kind of a kludge but that did start a terminal session on the :0.1
screen so I can use
On Fri, 2016-01-08 at 11:20 -0600, Nate Bargmann wrote:
> A difference is that I am not using Xephyr and so no extran X server.
> Instead I am using Zaphod heads mode. I will check again when I get
> home with the --display option. I seem to recall that did not make
> any
> difference.
>
> After
* On 2016 08 Jan 10:48 -0600, Sven Arvidsson wrote:
> Not sure what's going on.
>
> I tried by running an extra X server with Xephyr. No problem launching
> gnome-terminal there by using --display (with no other g-t-s running)
> or by launching gnome-terminal from an xterm inside Xephyr.
A diffe
ICT gnome-terminal runs a single process, /usr/lib/gnome-
> > terminal/gnome-terminal-server each call to gnome-terminal just
> > creates
> > a new window. So if you have g-t-s running on the first screen it
> > will
> > most likely use that.
>
> No other instan
each call to gnome-terminal just creates
> a new window. So if you have g-t-s running on the first screen it will
> most likely use that.
No other instances of GT are running. This would be the first and only.
- Nate
--
"The optimist proclaims that we live in the best of all
possibl
On Thu, 2016-01-07 at 20:55 -0600, Nate Bargmann wrote:
> This is puzzling me. My Xorg is set up for dual-head operation with
> each head having its own screen and four Xfce workspaces per screen.
> It's something I've had working well for several years.
>
> For variou
This is puzzling me. My Xorg is set up for dual-head operation with
each head having its own screen and four Xfce workspaces per screen.
It's something I've had working well for several years.
For various reasons I would like to use Gnome Terminal for an terminal
application as it can
On Thu, Nov 12, 2015 at 18:49:00 +1300, martin f krafft wrote:
> Hello,
>
> Can I use systemd to automatically run scripts as the owner of an
> X session when a USB keyboard or a VGA screen are connected to the
> local machine? Or what other mechanism would you use?
>
It sho
ession when a USB keyboard or a VGA screen are connected to the
> local machine? Or what other mechanism would you use?
As far as I'm aware there's no "production ready" solution for this
yet (in Debian).
>
> In the past, doing so automatically would involve some sort of
Hello,
Can I use systemd to automatically run scripts as the owner of an
X session when a USB keyboard or a VGA screen are connected to the
local machine? Or what other mechanism would you use?
In the past, doing so automatically would involve some sort of hook
in /etc (invoked as root), which
d so I can press some key on
the keyboard, and it will be handled before locker turns on -> insecure.
If I launch it without "--no-late-locking", then the following happens:
Computer stand idle for 10 minutes, display turns off, screen locker
turns on, display turns back on automat
Some reasons make me use own splash screens in my debian stretch. My
service starts just /dev/fb0 is set. I found unwanted screen clearing
occurs three times up to my main program starts from
~/.config/openbox/autostart:
1) getty@tty1.service does it (despite autologin, -noclear option in
command
Just sharing: i am no longer using default vino server. i am using
vnc4server and also tightvncserver both shows the same result.
On Sat, Sep 19, 2015 at 10:41 PM, Muhammad Yousuf Khan
wrote:
> All,
>
> I am having gray screen issue no matter what setting i put in my xstartup
> fi
All,
I am having gray screen issue no matter what setting i put in my xstartup
file.
when ever i connect the client it shows me something gray screen i can not
see anything in the log i dont know what is going on. it never happend to
me before.
no xstartup config is working in this.
any
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
t; 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 switchi
pply 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. (Perh
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
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
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 monitor
ms (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
On 27/08/2015 02:24, Jimmy Johnson wrote:
On 08/26/2015 10:30 AM, Hans wrote:
Hello list,
I cannot unlock kde5 screen although the password is correct. This
behaviour appeared in kde4, too. I believe this is not a bug, it looks
for me, that the related file got not the correct rights settings
On 08/26/2015 10:30 AM, Hans wrote:
Hello list,
I cannot unlock kde5 screen although the password is correct. This
behaviour appeared in kde4, too. I believe this is not a bug, it looks
for me, that the related file got not the correct rights settings.
I have this:
ls -la /usr/lib/x86_64
Hello list,
I cannot unlock kde5 screen although the password is correct. This
behaviour appeared in kde4, too. I believe this is not a bug, it looks for me,
that the related file got not the correct rights settings.
I have this:
ls -la /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
On Thu, 16 Jul 2015 14:17:13 -0400 (EDT), Gene Heskett wrote:
>
> My atom boxes are using xfce I think. And I have studied up on xset, and
> tried every combo that even looks suspicious in an effort to kill the
> screen blanker once and for all. But I can't even do it for 1
On Thu 16 Jul 2015 at 17:10:08 -0600, D. R. Evans wrote:
> If the blanking is caused by a screensaver application under the control of
> your desktop environment, that should work (I guess).
>
> But if it's caused by either DPMS being invoked, or X blanking the monitor,
> then you'll need to expl
On Friday 17 July 2015 06:21:48 Petter Adsen wrote:
> On Thu, 16 Jul 2015 14:17:13 -0400
>
> Gene Heskett wrote:
> > My atom boxes are using xfce I think. And I have studied up on
> > xset, and tried every combo that even looks suspicious in an effort
> > to kill
On Thu, 16 Jul 2015 14:17:13 -0400
Gene Heskett wrote:
> My atom boxes are using xfce I think. And I have studied up on xset, and
> tried every combo that even looks suspicious in an effort to kill the
> screen blanker once and for all. But I can't even do it for 10 minut
On Thu, Jul 16, 2015 at 05:10:08PM -0600, D. R. Evans wrote:
> Gene Heskett wrote on 07/16/2015 02:31 PM:
> > On Thursday 16 July 2015 16:25:29 Mike Castle wrote:
> >> For xfce, you might try this:
> >>
> >> Settings Manager > Session and Startup > Application Autostart
> >> Scroll down and uncheck
On Thursday 16 July 2015 19:10:08 D. R. Evans wrote:
> Gene Heskett wrote on 07/16/2015 02:31 PM:
> > On Thursday 16 July 2015 16:25:29 Mike Castle wrote:
> >> For xfce, you might try this:
> >>
> >> Settings Manager > Session and Startup > Application Autostart
> >> Scroll down and uncheck Screens
Gene Heskett wrote on 07/16/2015 02:31 PM:
> On Thursday 16 July 2015 16:25:29 Mike Castle wrote:
>> For xfce, you might try this:
>>
>> Settings Manager > Session and Startup > Application Autostart
>> Scroll down and uncheck Screensaver.
>
> Hadn't thought of that, thanks. I did set it by unchec
every combo that even looks suspicious in an effort
> > > to kill the screen blanker once and for all. But I can't even do it
> > > for 10 minutes in a row.
> > >
> > > So obviously the solution is not an xset command in the startup.
> > >
> > > Doe
On Thursday 16 July 2015 21:25:29 Mike Castle wrote:
> might be useful if the above doesn't work out for you.
for a session, however long it be, though not permanently:
$ xset -dpms
Or you may have to do:
# xset -dpms
That works until you next reboot.
In my experience turning the screensav
On Thursday 16 July 2015 16:25:29 Mike Castle wrote:
> For xfce, you might try this:
>
> Settings Manager > Session and Startup > Application Autostart
> Scroll down and uncheck Screensaver.
Hadn't thought of that, thanks. I did set it by unchecking all the
blankers and setting the times north of
For xfce, you might try this:
Settings Manager > Session and Startup > Application Autostart
Scroll down and uncheck Screensaver.
There may be additional things you need to do to make sure session stuff
isn't loading screensavers through some other mechanism (i.e, squirreled
away in a saved sessi
On Thursday 16 July 2015 14:35:04 Brian wrote:
> On Thu 16 Jul 2015 at 14:17:13 -0400, Gene Heskett wrote:
> > My atom boxes are using xfce I think. And I have studied up on
> > xset, and tried every combo that even looks suspicious in an effort
> > to kill the screen bla
On Thu 16 Jul 2015 at 14:17:13 -0400, Gene Heskett wrote:
> My atom boxes are using xfce I think. And I have studied up on xset, and
> tried every combo that even looks suspicious in an effort to kill the
> screen blanker once and for all. But I can't even do it for 10 minut
My atom boxes are using xfce I think. And I have studied up on xset, and
tried every combo that even looks suspicious in an effort to kill the
screen blanker once and for all. But I can't even do it for 10 minutes
in a row.
So obviously the solution is not an xset command in the st
Robert S gmail.com> writes:
>
> Hi.
>
> I have had a functioning system on wheeze using grub2. I did an
> upgrade to Jessie according to the debian docs.
>
> Now when I boot my system I simply get a black screen after the POST
> screen - there's no GRUB scr
Ingo K. gmx.li> writes:
> Same here, I upgraded an up-to date Debian wheezy 7.8 with a grub2 1.99 on
> an old Poweredge 650 to jessie 8.1. The upgrade brought grub2 2.02beta2-22
> and big problems.
> grub2 [...] displays nothing
> except a black screen (tried different displa
2beta2-22
and big problems.
(Sorry for excavating the week-old thread but perhaps I got some useful info
for other people.)
> Now when I boot my system I simply get a black screen after the POST
> screen - there's no GRUB screen or any hint of it.
Before my booting process looked like thi
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
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 pa
all GNOME. We prefer
"ICEWM" with startx.
2. Debian installation without GNOME:
To prepare our production system, we installed Debian 8 without
GNOME, After installation , Added same "nolapic" in kernel parameters to
start booting process.
But , this time saw all
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 w
ooting 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
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
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
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-re
t;
>> 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
/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
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.
Please help me solve this.
Thanks,
With Regards,
Dwijesh
t disk before, it is
not necessary after. Besides, BIOSes generally print an error message
such as "no bootable device found" instead of just a blank screen.
See also <http://www.rodsbooks.com/gdisk/bios.html> which contains
valuable information about booting in BIOS mode from a GPT
I have managed to make my system bootable by installing LILO. Could
somebody let me know if this is likely to be obsoleted any time? I
haven't received any indication that it will be.
Have you explored the new bios settings? If we can assume it is a real
working update, you might have some op
On 06/12/2015 11:22 PM, Robert S wrote:
Sadly this problem started AFTER I upgraded my BIOS. I have tried
installing debian (AMD64) from scratch and am unable to boot from this
either. I can't find any way to downgrade the BIOS and there is only
one BIOS upgrade file on the Gigabyte website.
I have had a functioning system on wheeze using grub2. I did an
upgrade to Jessie according to the debian docs.
Now when I boot my system I simply get a black screen after the POST
screen - there's no GRUB screen or any hint of it.
I had a similar problem with a laptop. I resolv
I have had a functioning system on wheeze using grub2. I did an
upgrade to Jessie according to the debian docs.
Now when I boot my system I simply get a black screen after the POST
screen - there's no GRUB screen or any hint of it.
I had a similar problem with a laptop. I resolv
On 12/06/15 10:01 AM, Robert S wrote:
Hi.
I have had a functioning system on wheeze using grub2. I did an
upgrade to Jessie according to the debian docs.
Now when I boot my system I simply get a black screen after the POST
screen - there's no GRUB screen or any hint of it.
I've
801 - 900 of 4563 matches
Mail list logo
