Debian Multimedia :: Wheezy Black Screen After Upgrade

May 4, 2015

i have an installation of wheezy 7.8 i think. i was facing difficulties in read of matroska video. therefore have decided to installer gstreamer1.0 wich should be resolve my problem. i have added the backports repository in apt sources list. after an apt-get update i launch apt-get install gstreamer1.0 . i have noticed it have starting downloading more file than it needs i concluded that it was a upgrade or something like because the kernel was also updated. after the the packet downloading it has started the installation with some errors related to LOCALE LCC. it has stopped and restarted some services wich is normal. i have closed all others apps and restarted. Here start the hell. after the restart i have passed the kde login screen and after BLACK SCREEN with mouse working.

Alt+F2 don't open the krunner

What i have tried? i have rename the /home/jefcolbi/.cache and back it again, rename /home/jefcolbi/.kde and back it again. next i have tried to check the Xorg config file. i created a new one with X -configure, modified it to feet my system configuration this does not resolve the problem but add another the keyboard is not working in graphical mode.

My system configuration:

Toshiba laptop Satellite Pro L300
Dual core
3gb Ram
graphic card:Mobile Intel(R) GMA 4500MHD
sound card: Intel HD Audio
debian whezzy 7.8 with KDE

Note: everything was working fine before trying to install gstreamer1.O from backports repository

View 3 Replies


ADVERTISEMENT

Debian Multimedia :: Gdm3 Black Screen With Cursor After Upgrade

Oct 25, 2015

Yesterday I done an upgrade with apt and since that time whenever I boot up I am presented with only a blank screen and an unresponsive cursor. I cannot switch console using Ctl+Alt+F*. The only thing I can do is Alt+SysRq+(R,E,I,S) which kills gdm3 and gets me back to the console.

* I can get into Xorg fine via the startx command
* As a temporary fix, if I enable automatic login (via /etc/gdm3/daemon.conf) then gdm3 works.

But I can't get the normal authenticated login screen to work.

Output of journalctl for a failed attempt at running gdm3 with verbose debugging enabled:

Code: Select allOct 25 01:24:43 [hostname-removed] systemd[1]: Starting GNOME Display Manager...
Oct 25 01:24:43 [hostname-removed] systemd[1]: Started GNOME Display Manager.
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Enabling debugging
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Changing user:group to Debian-gdm:Debian-gdm
Oct 25 01:24:43 [hostname-removed] gdm3[15863]: Successfully connected to D-Bus

[Code] ....

One other thing worth noting, before upgrading yesterday, I changed mirrors and accidentally pasted in "stable" into /etc/apt/sources.list. So basically I did an initial upgrade, realised my mistake, switched back to testing (which I was on before) and done another upgrade, which is when I noticed this problem.

View 14 Replies View Related

Debian Hardware :: Wheezy - GMA500 Black Screen After Loading Ramdisk

Aug 21, 2013

I have just installed Debian Wheezy on an E6XX Intel platform and after loading ramdisk, the screen goes black and I cannot use the system.

*) In the beginning, I tried to pass "nomodeset" in Grub, but after loading ramdisk, it tries to change screen's resolution and it goes blank.
*) gma500 output in dmesg can be seen in [1] at the bottom of this page.
*) I tried passing "GRUB_GFXMODE=640x480
GRUB_GFXPAYLOAD_LINUX=640x480" + update-grub, but it keeps failing.
*) I examined EDI's monitor output through "sudo get-edid |sudo parse-edid" (see [2] below), it seems that it is not possible to get the EDID information from the screen correctly. However, I am using this screen with xrandr with Debian Squeeze and I have no problems.

>>>>>>>>>>>>>>>>> [1] dmesg about "gma500"
[ 10.164297] gma500 0000:00:02.0: setting latency timer to 64
[ 10.164325] gma500 0000:00:02.0: Enabling MSI failed!
[ 10.164923] [drm] internal display is MIPI display
[ 10.167632] gma500 0000:00:02.0: VBT signature missing
[ 10.167828] Stolen memory information
[ 10.167840] base in RAM: 0x3f800000

[Code] ....

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
parse-edid: IO error reading EDID

View 4 Replies View Related

Debian Multimedia :: Debian Wheezy / Screen Blinking

Mar 30, 2011

I am giving Wheezy a whirl and am having with screen blinking ever 30 seconds.

View 5 Replies View Related

Debian :: Squeeze Black Screen On Boot Since Upgrade?

Aug 11, 2010

After doing a dist-upgrade today, my one year old install of squeeze will no longer boot. It stops with a black screen and has to be hard reset. Cant even get to tty1. The last line in dmesg is: cfg80211: Calling CRDA to update world regulatory domain

mike@vaio ~ $ lspci | grep Network 06:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100.Just wondered if anyone has any ideas before I restore from a backup?

View 3 Replies View Related

Debian Multimedia :: Screen Gets Black After Log Off In Squeeze?

Mar 23, 2011

I installed Debian Squeeze from Debian 6.01 CD 1 on my old Pentium 4 Desktop. Now when I log off, the screen gets black and login window is not appearing. I have tried all old post of linux questions forum and also of ubuntu

View 7 Replies View Related

Debian Multimedia :: Screen Turning To Black After Suspending

Oct 20, 2015

I have a problem with my computer running debian testing with kde. When after a while I'm away form keyboard my screen turn off for power saving, but I cannot in any way turn it on again.

I tried moving mouse, pressing some key, Ctrl + Alt + Del, Ctrl + Alt + BackSpace, Ctrl + Alt + Esc, and also Ctrl+Alt+F1/2/ecc.. No way. I had to reset my computer every time.

View 1 Replies View Related

Debian Multimedia :: Black Screen After Startx Command

Dec 21, 2015

I updated Debian system yesterday. I am getting black screen after I execute startx command. I am using system as server and manually boot into GUI mode whenever required.

View 10 Replies View Related

Debian Multimedia :: Xorg Ended In Black Screen

Jun 9, 2010

I am new to Linux and installed Debian. After the Installation I started Debian and ended in a black screen. I came out there changing to a terminal (ctrl+alt+F1) but I dont know how to get Xorg running. I am using the Mainboard:Gigabyte GA-D510UD without any extras (means just the Mainboard with Ram and an IDE Hdd). here is the Log file from Xorg [URL]... System Information is in the log.

View 7 Replies View Related

Debian Multimedia :: Resuming From Hibernation - Black Screen?

Sep 1, 2011

The problem is black screen after resuming hibernation.After I switch my computer on (after hibernation), I can see some progress bar and (after loading to 100%) black screen appears.I have Debian + GNOME and I DON't have xscreensaver.

View 2 Replies View Related

Debian Multimedia :: Iceweasel Black Screen When Playing Videos

Sep 18, 2015

What I mean by black screen is that whenever I view a video or if there is video content anywhere on the page, my whole monitor goes black for around 3 seconds then plays the video content.

I am running Jessie 8.2 by the way.

View 7 Replies View Related

Debian Multimedia :: Login Screen (GNOME) Stays Black

Apr 7, 2016

After applying upgrades to debian 8.2 on a lenovo yoga3 notebook and a reboot I am not able to login into my GNOME desktop. The login screen stays black. If I press the power button to suspend I can see the login screen with default background for ~1 second before it turns black again. What can I do to fix this issue? Is there a way to login via terminal and do a rollback? Can I use my home folder an personal settings if i reinstall debian and keep the /home partition?

View 14 Replies View Related

Debian Multimedia :: X Broken After Update - Screen Remains Black

Dec 20, 2010

So I'm pretty awful at keeping Debian up to date, I guess. I'm using cron-apt to fetch updates every night, then apply them whenever I get around to it. Well, I neglected that last part for a month or two, and after some routine downtime to clear the case of dust, I decided it was time to upgrade. So I ran the command, everything checked out fine, and I was on my merry way. Until a half-hour ago when I accidentally shutdown the computer (I use the same zsh prompt on each computer, so I got them confused.) I turned it back on, only to be greeted with a black screen after all the services started up.

Everything works: ircd, MPD, etc. EXCEPT, of course, X. At first I thought the update broke SLIM, but after checking htop and doing a killall slim, it doesn't appear to be running (the screen remains black.) I hit Control-Alt-f2 to get to get back to a terminal, then tried doing startx, which freezes the computer entirely. All the network services stop, I can't SSH in, etc. It's dead. If I'm not mistaken, Xorg.0.log should say something, but I'm not a huge expert on it. The last line isn't an error, I can tell you that. So what's the deal here? apt-get remove xorg and start over?

View 1 Replies View Related

Debian Multimedia :: Screen Remains Black After Sleep Mode

Feb 20, 2011

I recently came to Debian. As I have an ati card, I tried the proprietary drivers first, but then came back to radeon (open-source). In the process, I think I may have broke my xorg.conf . Sometimes, when the monitor goes into sleep mode, when I came back, the screen remains black (sometimes I see just the cursor).

Here is my xorg.conf
# NOXORGCONFEXISTED: No X.org configuration file existed when this backup was created.

Also, I have lots of backups in my X11 folder, like xorg.conf.fglrx-3, xorg.conf.original-1, or backup.xorg.conf. Is it safe to remove them? What should I do about the main xorg.conf?

View 7 Replies View Related

Debian Multimedia :: Laptop Screen Stays Black On Resume From Suspend?

Jun 22, 2011

I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread:

Tue Jun 21 23:07:12 AKDT 2011: performing suspend
Tue Jun 21 23:07:28 AKDT 2011: Awake.
Tue Jun 21 23:07:28 AKDT 2011: Running hooks for resume

[code]...

View 8 Replies View Related

Debian :: How To Upgrade To Wheezy

May 20, 2011

I got "stuck" with stable up to now and want to upgrade to Wheezy. But, although I've done this before, I'm having a dependency problem I wanted to ask about before breaking my system somehow. This is the /etc/apt/sources.list, ready for Wheezy:

[URL]

So, I regularly use aptitude as my package manager. After updating the database with aptitude update, trying aptitude full-upgrade gives me a huge of conflicts.

[code]....

But, if I use apt-get dist-upgrade, I get no conflicts. if I dist-upgrade with apt-get, will that affect my daily usage of aptitude (which I prefer)? I know APT is a single database and apt-get and aptitude are just different interfaces, but I guess differences might rise when marking packages as automatically or manually installed.

View 7 Replies View Related

Debian Multimedia :: Connect From Remmina To Jessie On Another System Via Xdmcp - Only Black Screen Happen

Jul 16, 2015

I want connect from remmina to jessie on another system via xdmcp but only black screen happened.

my daemon.conf
Code: Select all[security]
DisallowTCP=false

[xdmcp]
Enable=true

[debug]
Enable = true

And gdm3 listen on udp/177. My syslog :

Code: Select allJul 16 10:17:46 office /usr/bin/dbus-launch[1455]: X Error of failed request:  BadValue (integer parameter out of range for operation)
Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Major opcode of failed request:  140 (RANDR)
Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Minor opcode of failed request:  7 (RRSetScreenSize)
Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Value in failed request:  0x0
Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Serial number of failed request:  150

[Code] ....

View 1 Replies View Related

Debian :: No Internet After Upgrade From Wheezy To Jessie

May 27, 2015

I upgraded my Wheezy 7.8 to make sure all packages were installed Before taking the next step to upgrade to Jessie.I upgraded to Jessie and it seemed to run OK....but after reboot I had no network Connection..I checked ifconfig and the wrong network card mac address is being assigned to the wrong card....?I have a clonezilla server on my server, so this was my network interfaces before and after upgrade

Code: Select all# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback

[code]...

I even checked nano /etc/resolv.conf and sure enough my gateway was the same for my Internet eth0.When I ran ifconfig I could see that the eth0 mac address was set as eth1..I tried to reset my drbl for clonezilla but that only sees the vmware Connection and not my actural cards.. have taken alook at /etc/udev/rules.d/70-persistent-net.rules and the assignment is right but not ifconfig?

View 14 Replies View Related

Debian :: Wheezy To Jessie Upgrade Will Not Boot

May 28, 2015

With "quiet" removed from the grub linux line, I'm getting the following error messages when the boot hangs up early in the boot process (19.768231 seconds into boot).:

input: HDA NVidia HDMI/DP,pcm=3 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6
input: HDA NVidia HDMI/DP,pcm=7 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7
input: HDA NVidia HDMI/DP,pcm=8 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input8

So, is this a NVidia issue or a sound card issue?

View 1 Replies View Related

Debian Installation :: Upgrade To Wheezy Successful But No CLI And No GUI?

Jun 9, 2011

I upgraded one of my Squeeze installations to Wheezy, but after selecting it in grub, nothing is displayed on screen: no CLI and no GUI. I tried Ctrl + Alt + F[1-7] and I got nothing. My laptop is Acer Aspire 7715Z. I am attributing this to module as there seems to be disk activity, but without a screen, I cannot be certain.

View 14 Replies View Related

Debian Hardware :: No Sound After Upgrade (Wheezy)

Jan 17, 2014

Sound is not working perfectly since installation. I fixed it by command: 'alsactl init' every time sound doesn't come out. However, since last week, sound was not working. I suspect it was caused by the 'apt-get upgrade' I did.

Code: Select allroot@debian:~# alsactl init
alsactl: init:1743: No soundcards found...
lspci (only audio)
Code: Select allroot@debian:~# lspci -v
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
   Subsystem: Micro-Star International Co., Ltd. Device b002

[Code] ....

It seems I am missing a module/ kernel driver for the sound card

Note: I have testing in sources list but have stable with higher priority. So I should still be in Wheezy

View 5 Replies View Related

Debian Installation :: Upgrade From Squeeze To Wheezy Or Jessie

Jul 28, 2015

is it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.

View 2 Replies View Related

Debian :: Dedi Server Don't Reboot After Wheezy / Jessie Upgrade

Jul 26, 2015

I have upgraded my debian server on april when Jessie came up, but I *forgot* to reboot at this time. As a new kernel* was released this week as a security update, and since my server installed it (via unattended-upgrade on security packages), I rebooted it last night. It never came back online.

I have access to a rescue boot (Ubuntu 12.04 LTS), and tried to analyse the failure (by mounting /sys /dev /proc and /boot and chrooting), but without luck so far.

As it's a dedicated server, I don't have access to the console. What I know :

No log in var/log since the failed reboot. I don't know how to have/find others logs.Previous kernel was 3.2.0-4-amd64, new is 3.16.0-4-amd64, What I tried without luck) :

Change the booting kernel, via update-grub. Tried 3.2, 3.2 with sysvinit and 3.16 rescue mode I think. I should have done it right, but without console it's hard to tell.apt-get update/apt-get upgrade/apt-get dist-upgradeadding nomodeset to kernel load in grubWhat I haven't tried :

update-initramfs, I don't really know why it would block the boot

*linux-image-3.16.0-4-amd64:amd64 3.16.7-ckt11-1+deb8u2

View 6 Replies View Related

Debian Installation :: Failed Wheezy To Jessie Upgrade (cannot Boot)

Aug 13, 2014

I upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:

Code:
Select allLoading, please wait...
[    6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616
9/52442880 blocks
[    7.480551] Error: Driver 'pcspkr' is already registered, aborting...
[    8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks
[   18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead
_

The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.

In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.

I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.

View 12 Replies View Related

Debian Installation :: Broken Grub After Wheezy To Jessie Upgrade

Jun 2, 2015

I've changed my /etc/apt/sources.lst file to use "jessie" repositories instead of "wheezy". I then ran synaptic and updated everything (there were loads of packages, something like 2000 to update).

After this I rebooted. The grub menu shows as usual with the background image I'd set and the operating systems as usual (including Windows 7) however there is no longer a 5 second countdown and when I select *any* menu option, it asks for a username and password.

I don't know what username and password it's asking for as I never used to have one set!!! I did have a username and password set up so that if you wanted to edit a grub menu option so I tried that but to no avail.

I'm using MBR/BIOS not EFI.

View 3 Replies View Related

Debian Installation :: Multiple SystemD Errors After Upgrade From Wheezy

Mar 3, 2016

Recently I upgraded my machine from wheezy to jessie.

Everything went smooth until the point that I restarted the node.

During startup I'm getting the following message which is flooding the screen:

Code: Select allsystemd-journald[296]: Failed to forward syslog message: Connection refused

After waiting a long time (the message above still continues to flood the screen), I'm being prompted with the following:

Code: Select allGive root password for maintenance (or type Control-D to continue):

If I press Ctrl+D the boot process continues and finally boots normally.

What I can do to avoid pressing Ctrl+D during the boot process?

I'm assuming that it must be a startup service which is failing but I'm unable to trace which exactly is that.

I'm attaching the full log [URL] ....

View 8 Replies View Related

Debian Hardware :: Wheezy - Cannot Upgrade Nvidia Driver To 319.82 Backport

Nov 17, 2014

I'm on Wheezy with version 304.117 of the proprietary nvidia driver installed and working, but an application I have needs a newer version of the driver. I'm trying to install the 319.82 version in backports by following the instructions given here, but when I issue the command to install nvidia-kernel-dkms, I get the following:

Code: Select all> sudo aptitude -t wheezy-backports -r install nvidia-kernel-dkms

The following NEW packages will be installed:
  libgl1-nvidia-glx-i386:i386{a} nvidia-driver{a}

The following packages will be REMOVED:
  libgl1-nvidia-alternatives{u} libglx-nvidia-alternatives{u}
  libxvmcnvidia1{u} nvidia-glx{u}

The following packages will be upgraded:
  glx-alternative-nvidia glx-diversions libgl1-nvidia-glx
  libgl1-nvidia-glx:i386 libnvidia-ml1 nvidia-alternative
  nvidia-installer-cleanup nvidia-kernel-dkms nvidia-settings
  nvidia-smi nvidia-vdpau-driver xserver-xorg-video-nvidia

The following partially installed packages will be configured:
  mint-flashplugin-11:i386
12 packages upgraded, 2 newly installed, 4 to remove and 151 not upgraded.
Need to get 32.3 MB of archives. After unpacking 9,440 kB will be freed.

The following packages have unmet dependencies:
 glx-alternative-mesa : Depends: glx-diversions (= 0.2.2) but 0.5.1~bpo70+1 is to be installed.
Internal error: found 2 (choice -> promotion) mappings for a single choice.
Internal error: found 2 (choice -> promotion) mappings for a single choice.

The following actions will resolve these dependencies:

      Remove the following packages:                                     
1)      glx-alternative-mesa                                             
2)      glx-alternative-nvidia                                           
3)      libgl1-nvidia-glx                                                 
4)      libgl1-nvidia-glx:i386                                           
5)      nvidia-alternative                                               
6)      nvidia-kernel-dkms                                               

[Code] ....

Accept this solution? [Y/n/q/?] q

The mint-flashplugin problem is a separate issue which I've had for a while. I assume that it can be ignored for the purposes of this post.

If I'm reading the aptitude output above correctly, it's telling me that the only way to "resolve" the conflict is by uninstalling all nvidia support, leaving me with no driver at all. Is that right?

View 2 Replies View Related

Debian Installation :: Dist-upgrade From Wheezy (using Systemd) To Jessie Hangs

Nov 19, 2014

I have done on previous releases, but this time it hangs on me. It's "only" a Virtualbox, so I can reproduce it.

The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.

Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade

It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.

Should I disable systemd on wheezy before? This might not have been tested so much.

View 10 Replies View Related

Debian Installation :: Upgrade From Wheezy To Jessie Modify Print Drivers?

Feb 9, 2016

Does upgrade from wheezy to jessie modify print drivers....

View 1 Replies View Related

Debian :: 7.8 Wheezy Amd64 - Screen Blocked Suddenly

Feb 18, 2015

I'm using Debian 7.8 Wheezy amd64, Gnome classic session. Laptop ASUS F551MAV, Intel HD Graphics (Integrated GPU), xserver-xorg-video-intel 2:2.19.0-6, firmware-linux-free 3.2

Sometimes, after inactivity, the screen turns black, not allowing me to see login screen. If I press CTRL+ALT+F1 (or F2,F3,Fn) nothing happens. The computer is still responsive, as I can reboot it through key shortcuts.

I have search in almost all logs in /var/log, without any information about the cause of the error. The time I was away from computer was between +- 18:10-18:22

Here is the log of daemon.log at the time of rebooting: [URL] ....

I can see one line that seems to be an error with (but it is displayed as warning):

Code: Select allFeb 18 18:21:47 debian gnome-session[3714]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Recurso no disponible temporalmente) on X server :0.#012
Recurso no disponible temporalmente is in english something like: Resource not available temporaly.

Log of syslog at the moment of screen blocked
Code: Select allFeb 18 18:17:01 debian /USR/SBIN/CRON[4235]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 18 18:21:36 debian acpid: client 3226[0:0] has disconnected
Feb 18 18:21:44 debian shutdown[4411]: shutting down for system reboot

[Code] ....

It is not the first time that this is happens. It already happened a few times, that when I'm away, the screen is simply blocked.

View 4 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved