Also, doing /etc/init.d/start/ gdm3 says Starting GNOME display manager: gdm3 but it doesn't do anything. I tried pressing ctrl+f1 all the way to ctrl+f12 and nothing. What does work however is sudo gdm3 (with the "ati"/"radeon" driver --- nothing works at all with fglrx).
I am trying to get fglrx working because I want to fix this compiz issue I've been having here which could be related to the shortcomings of the "ati"/"radeon" driver: viewtopic.php?f=10&t=40991&p=312577#p312577
A few days ago I ditched the user friendly world of Ubuntu and installed Debian Squeeze amd64 (testing) over it. I did not install the suggested Gnome 'X desktop' in favour of booting to the terminal and starting X once logged in as a user.
Everything was fine except for the fact Xvesa was used instead of Xorg as the system did not have the required Fglrx driver. I'm using an Acer ASPIRE 5536 with an ATI Radeon HD 3200 Graphics stuffed in it, which certainly beats intel GMA.
Unfortunately the drivers for it are proprietary.
On Ubuntu this was automatically detected and I was asked if I wanted to sell my soul and enable the restricted drivers. On debian however I have to download a shell-script of the ATI website to install the fglrx module.
Following this guide I downloaded the correct file (Under motherboard/something) and ran it as root.
I couldn't run it with any --buildpky Debian/XXX option, they all failed.
Code: ================================================== ATI Technologies Linux Driver Installer/Packager ================================================== Generating package: Debian/testing cp: cannot stat `/root/fglrx-install.tCX8nC/x710_64a/*': No such file or directory Package build failed!
I recently upgrade from Lenny to Squeeze. My graphic card is nVidia Corporation G86 [GeForce 8400M GT] (rev a1). Using lenny latest drivers from nvidia worked fine. I installed nvidia drivers using Debian packages 195.36.31-6 and latest driver from nvidia site (260.19.36) and also other nvidia drivers. The problem is when I start gdm3 I saw nvidia logo but then when it loads gdm3 it shows gdm3 screen with lot of black pixels and other random pixels and then the screen freezes. And the only thing I can do is restart using [alt]+[sysrq]+b.
I installed jessie from a beta/rc shortly before release on my MacBook Pro 13 Retina and have kept it up to-date with apt-get dist-upgrade. Rcently gdm3/gnome-session have stopped working together. When I log in the screen goes black for a couple of seconds then goes back to the login screen. This happens with "System Default", "GNOME Classic" and "GNOME", but not with "GNOME on Wayland". However, Wayland seems to have some other issues. I haven't tried an alternative dm yet, eg lightdm, but the GNOME desktop does work when started with startx.
I've just used journalctl to get logs of what gdm3 and gnome-session were doing at the time. After booting I waited until the clock reached the next minute (19:55) so I'd know at which point in the logs I'd hit enter on my password. I'll post the gdm log separately in two chunks because the forum server doesn't seem to like text attachments and they're too long for one post.
Log from gnome-session: Code: Select all-- Logs begin at Thu 2015-05-07 19:54:06 CEST, end at Thu 2015-05-07 19:56:41 CEST. -- May 07 19:54:08 jeanette gnome-session[885]: gnome-session[885]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
From the wiki page I know the ATI Mobility Radeon X1400 card is no longer supported by the new fglrx driver in squeeze. Is there a way to use the older driver from lenny? I'm on the radeon driver and the glxgrears performance is pretty low.
I recently installed Debian Squeeze on Acer Aspire 5542 , it has a Ati Radeon HD 4200 graphics card
I want to install the fglrx drivers , I apt-get install fglrx-driver, fglrx-glx & fglrx-control , The packages & dependencies download fine but when apt tries to install them the fglrx-modules-dkms fails .
Some days ago (2015-09-28) I installed Debian testing amd64. Log in as a user failed and instead of the Gnome UI there was a sad face with the text: „Oh no! Something has gone wrong. A problem occurred and the system can't recover.
All extensions have been disabled as a precaution. Log out“.
The relevant output of journalctl (run as root) said:
etc/gdm3/Xsession[5379]: cannot connect to brltty at :0 - /etc/gdm3/Xsession[5379]: Service 'org.kde.kaccessibleapp' does not exist. - gnome-session[5379]: x-session-manager[5379]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 - gnome-session[5379]: x-session-manager[5379]: WARNING: App 'gnome-shell.desktop' respawning too quickly - x-session-manager[5379]: Unrecoverable failure in required component gnome-shell.desktop
[Code] ...
After some investigating, I found three work-arounds.
(1) Use gdm3-autologin: In /etc/gdm3/daemon.conf, remove the double crosses and insert own user name AutomaticLoginEnable = true AutomaticLogin = <own user name> Disadvantage: Only one user can have access to the Gnome ui. If you log out, you enter the gdm3 greeter and … see above.
(2) Turn off gdm3 by running 'systemctl stop gdm3' as root, log in into a terminal as a user and run startx.
(3) Install package lightdm and make it to the standard display manager with 'dpkg-reconfigure lightdm'. Disadvantage: Energy manager and screensaver settings of the Gnome control center are ignored.
The easiest way, however, especially if there are several users, is logging in via the gdm3 greeter.
I am trying to build the ATI fglrx 10.12 driver using the ATI installer on debian Squeeze 64bit.
Todo this I run the following command: ./ati-driver-installer-10-12-x86.x86_64.run --buildpkg Debian/testing
Which produces this output: Created directory fglrx-install.oFbosX Verifying archive integrity... All good. Uncompressing ATI Catalyst(TM) Proprietary Driver-8.801 Generating package: Debian/testing cp: cannot stat `/home/nojan/Downloads/fglrx-install.oFbosX/x710_64a/*': No such file or directory Package build failed! Package build utility output: ..... dh_install: Compatibility levels before 5 are deprecated. cp: cannot stat `./usr/X11R6/lib64/modules/linux': No such file or directory dh_install: cp -a ./usr/X11R6/lib64/modules/linux debian/fglrx-driver/usr/lib/xorg/modules/ returned exit code 1 make: *** [binary] Error 2 dpkg-buildpackage: error: debian/rules binary gave error exit status 2 Removing temporary directory: fglrx-install.oFbosX
I recently decided to replace Lenny on my laptop with Squeeze. All went fine, but now with both GDM and GDM3, the Caps and Num locks come on when GDM starts, and behave erratically. I have to hit the caps/num lock key several times to disable the lock, and sometimes it will come on again after a random time. This behavior persists into my GNOME session. I'll be working on code and *&%#! -- on comes the caps/num locks.
Initially I thought this was an X issue. I uninstalled GDM3 (which is the version installed by squeeze) and logged in at the console then started X via startx. The caps and num locks remained off and behaved in the normal manner. I then tried SLiM, and again the keys behaved normally. Then I tried GDM (2.20 in the squeeze repos), and it behaved the same as GDM3. Even though I purged GDM3 and GDM, I'm wondering if there's some residual configuration data in my home directory, but I can't seem to find anything related. Using SLiM isn't so bad, but once I log in I get asked to unlock the keyring, so typing my password twice to log gets annoying.
For quite a long time now, I haven't even needed to re-install video drivers most of the time. However, ever since version 2.6.36-0.dmz.4, they haven't been. I booted my system after installing that kernel, re-installed the video drivers, and when that didn't work, completely removed them and re-installed them, and it still didn't work. Well, I was told that the installation was successful but even after restarting it appeared that they weren't working. I installed 2.6.36-0.dmz.5 today and the same problem persists. I tried an older kernel version (2.6.36-4 something) and they worked fine.
I installed the latest Debian on a computer to make a backup appliance. No GUI.When the computer starts, everything is okay. The DHCP client is running, the network interface have an address, fine.If I do a /etc/init.d/network restart (or stop + start), no more DHCP client. t is stopped when the interface is down. When the interface is up, I have to start it manually.1 - is it normal ?2 - isn't ifup's job to launch the dhcp client ?3 - can /etc/network/if-up.d be the right place to resolve this ?
I just upgraded one of my non-mission-critical servers to squeeze just to see how it would go. Since the upgrade NFS is broken. When I try to start it I get:
Starting NFS kernel daemon: nfsdrpc.nfsd: unable to resolve ANYADDR:nfs to inet address: Servname not supported for ai_socktype rpc.nfsd: unable to set any sockets for nfsd failed!
I've tried searching on those errors, but all I've found is that this has happened to others when no network interfaces are started; this is clearly not the case with this server, since other services are running and working on both interfaces.
After upgrading to squeeze I have now X Server 1.7.7 installed and it won't start. When I try to run startx script, monitor gets blank for few seconds and then I get back to command prompt and no errors is displayed.
When I try the same as root, system locks up with blank screen and no functioning keyboard.
Initially I had kernel 2.6.28 which worked fine with earlier Lenny's X Server and Matrox P650 AGP video card. After upgrade I found, that Matrox P650 is not longer supported in new xorg and I swapped it to Matrox G550 AGP card.
Tried mga driver's many options, upgraded to kernel 2.6.37.2, tried with Matrox G200 PCI and Savage 4 Pro AGP card but without a success.
With kernel AGP support turned on I got both with Matrox G550 and Savage card an MTRR error: "error setting MTRR, Invalid argument (22)". Without AGP support in kernel, Matrox G550 gets initialised as PCI card and no errors and X still not working. Same with Matrox G200 PCI card.
With vesa driver the behavior is also the same and output at the end of Xorg.log file is almost the same.
So I understand, that this is some X server problem?
Nothing special in xorg.conf file and tried without it also.
End of the Xorg.0.log file:
>> (II) MGA(0): YDstOrg is set to 0 (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules/libfb.so
I just upgraded to Debian 6.0 squeeze 32 bit XFCE from Ubuntu on my old Dell PC. Installation went well, however, i can't get into X windows after reboot, the screen just displays garbage Specs: Dell dimension 600Mhz/384M RAM/10G HDD ATI RAGE pro 128 Any pointers on what should I do?
I just installed squeeze on a raid 1 set of partitions via netinst. gde works fine. I have installed kdm and all of its dependencies (I believe), but when I select it and log in, I see the kde startup screen for a moment, then it goes blank, and goes back to the login screen. My /var/log/kdm.log is:
If I recall correctly, my Squeeze desktop is working whereas my Squeeze laptop isn't.
Here are the errors: Failed to open a session for the virtual machine Ubuntu 10.04.2. The virtual machine 'Ubuntu 10.04.2' has terminated unexpectedly during startup with exit code 1.
Result Code: NS_ERROR_FAILURE (0x80004005) Component: Machine
In playing around trying to get Debian/X installed/working on my PowerBook (machine details in signature), I at some point installed gdm. I then decided to try installing Gnome desktop from the list of tasks in aptitude. I didn't install absolutely everything in the list. (I skipped the accessibility stuff for the most part, for example.) But I did try installing gdm3. Since this conflicts with gdm, this meant uninstalling gdm. No problem. The install etc. seemed to go OK and Debian's configuration tool let me choose between gdm3 and xdm as the display manager. I chose gdm3.
Problem: gdm3 will not start on boot (and I'm not sure whether or how to start it later without leaving root logged in). I found that the init scripts for gdm were still installed in /etc/rc2.d/ etc. but nothing for gdm3. There was a script at /usr/sbin/gdm which appears to want to (1) delete itself; and (2) start gdm3. But the init script /etc/init.d/gdm contains a check for gdm being the default display manager. However, it isn't. The file it checks contained /usr/sbin/gdm3. So I tried using the update-rc.d and also insserv commands to disable gdm and to install the scripts for gdm3. I could disable the commands for gdm fine but not install links for /etc/init.d/gdm3. This script seemed to want console-screen which I didn't have but managed to install by some guesswork. I then got the init script for this installed for /etc/rcS.d but still couldn't get anything installed for init for gdm3. I also tried creating the links manually but this made no difference on boot. I also tried purging gdm rather than just uninstalling it and reinstalling gdm3. No go.
Eventually, I gave up and removed and purged gdm3 and reinstalled gdm and now the display manager starts as it should on boot.
I'm not sure what I did wrong and would like to know. I don't know that I'm bothered one way or another about gdm3 vs. gdm but I'd like to understand what is going on in case something similar happens with something I *do* care about. (I don't know what the advantages of gdm3 are so maybe I should care...)
I'm using Squeeze and my sources list includes stable contrib and non-free (added the last two so I can get firmware needed for wireless).
How to get Java applet running on Squeeze, jre-6u26-linux, is needed to be installed, but I counld not do it, is there any alternative way to get Java applet working ? It works on Lenny, but I am moving to Squeeze.
Is not working my microphone in Deban. In Ubuntu or MW7 all works correctly.
Here are some outputs of commands:
root@debian:/home/brok# uname -a Linux debian 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 x86_64 GNU/Linux root@debian:/home/brok# lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch Distributor ID: Debian
I don't print much, but tonight needed to print and found that none of the printers were listed in Okular or Openoffice, then when I tried to open Cups Administration http://localhost:631/ I got the error message Connection to Server Refused
I am moving over to debian from ubuntu, and the latest install is to an acer aspire one netbook, the wireless card seems to be working and I can see available networks and even connect to mine (with WPA encryption) via the gnome network manager, however opening a browser or pinging both local and external machines all fail. its as if the OS does not not know to use the card. The wired works fine.
If memory serves the card is identified by lspci as Atheros AR5007.
There is no reference to wlan0 in etc/network/interfaces.
I do not have that system on now and have to leave for work, but I can post any further info from conf files etc as required when i get home tonight... Just thought I'd post a quick description in case I'm missing something obvious...
My audio is working, but when i put my usb speaker in it, it doesnt redirect sound to the speaker, just continues to play from the laptop.
In gnome, System->Prefernence->Sound shows the following: Device: HDA ATI SB Device: Logitech USB speaker (Alsa Mixer) lsusb shows: Bus 002 Device 003: ID 046d:0a04 Logitech, Inc. V20 portable speakers (USB powered) dmesg shows: [ 1530.060050] usb 2-1: new full speed USB device using ohci_hcd and address 3 [ 1530.229080] usb 2-1: New USB device found, idVendor=046d, idProduct=0a04
[Code]....
my usb speaker has volume control-up/down, mute, that seems to work, just no sound coming out of it. I am running Squeeze 6.01, kernel 2.6.32-5-686 Also I have 2 computers with squeeze 6.01 installed, both doesnt output usb sound, but the speaker works fine with winXp and ubuntu.
After upgrading my Acer extenza 5620z to debian squeeze(kernel 2.6.32-bpo.5-686) left click was not working on my SynPS/2 Synaptics TouchPad,allthought moving the cursor was working !
I went to debian channel on irc and there was someone who told that I should install a patch [URL] to correct this problem but when I restarted the whole touchpad was not working !!
This morning i installed Debian Squeeze and I'm sure it that was a good choice! I got my wireless stick to work (Linksys: Wusb600n v2), installed Chromium, VLC and some other stuff... and ye. I want to get Compiz working on my system! I'm not sure that my current drivers can deal with it, thought. I'm not good at Linux and I don't know what should I install (if there is something) so that I can have get better performance from my video-card. I made HardInfo report of my system. What are my options? How can I make the performance better and, maybe, run Compiz?
My setup is an HP OfficeJet 4315 All-in-one on a Debian box with the clients using XSANE on Windows boxes.
After upgrading to Squeeze, none of the clients could see the scanner.root could see the scanner from the Debian box.non-root users could not see the scanner from the Debian box.
Obviously, something was wrong with the permissions. After a lot of digging, I found that the /dev entry for the 4315 was owned by root.lp with no world write access.
My solution was to add the saned account to the lp group. I figured that was the most security-conscious way to fix it.
The remote clients can now see the scanner, so everyone is happy.
This may not work for every installation, but for all-in-ones, it probably will.
I have a Fujitsu Siemans Amilo A1630 installed with squeeze and am having problems making the headphone jack work with ALSA, there is no sound from this port and jack auto-detect does not work. All drivers are present and correct and necessary modules for my sound device appear to be loading properly, the device seems fully functional except for headphones.
I have debian with kde on a laptop with a built in ps/2 keyboard and touch pad mouse which have been working without problem since i bought the computer. However, recently i booted the computer up and all of a sudden the mouse and keyboard are not functioning. I know it is not a hardware problem because i can type in the BIOS password, make the selection between normal and recovery mode in grub, and can type in all of my passwords to unencrypt my hard drive.
Also, it recognizes the keyboard all the way up until the point where kde starts, at which point it loads a login screen with the mouse and cursor on the screen, but no ability to type, not even caps lock or ctrl+alt+f1 to switch to console mode. does anyone know why this is? I have performed not updates and have not changed the configuration of my computer so i am not sure why this would happen.
P.S.1 out 15 times when i load the part where i need to type in the passwords to unencrypt the hard drive the keyboard will stop working then instaed of with kde.