Re: i915: wheezy / jessie freeze under X
Hello Chris
The global information right after these introduction lines
detailed information within your mail: answer after each question
(console rights, recovery mode & xkbcomp)
regards,
ralf
--
I downgraded to pure Jessie, here the proof, whole command-lines ;-)
ralf@debian:~$ cat /etc/apt/sources.list
deb http://ftp.fr.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
ralf@debian:~$ ls -al /etc/apt/sources.list.d/
total 8
drwxr-xr-x 2 root root 4096 janv. 29 07:48 .
drwxr-xr-x 6 root root 4096 janv. 29 07:49 ..
NB: I was using deb-multimedia 'cause their ffmpeg version
is compiled with apple's codecs, I transcode videos for Mac
ralf@debian:~$ apt-cache policy
Fichiers du paquet :
100 /var/lib/dpkg/status
release a=now
500 http://security.debian.org/ jessie/updates/non-free Translation-en
500 http://security.debian.org/ jessie/updates/main Translation-en
500 http://security.debian.org/ jessie/updates/contrib Translation-en
1010 http://security.debian.org/ jessie/updates/non-free amd64 Packages
release o=Debian,a=testing,n=jessie,l=Debian-Security,c=non-free
origin security.debian.org
1010 http://security.debian.org/ jessie/updates/contrib amd64 Packages
release o=Debian,a=testing,n=jessie,l=Debian-Security,c=contrib
origin security.debian.org
1010 http://security.debian.org/ jessie/updates/main amd64 Packages
release o=Debian,a=testing,n=jessie,l=Debian-Security,c=main
origin security.debian.org
500 http://ftp.fr.debian.org/debian/ jessie/non-free Translation-en
500 http://ftp.fr.debian.org/debian/ jessie/main Translation-fr
500 http://ftp.fr.debian.org/debian/ jessie/main Translation-en
500 http://ftp.fr.debian.org/debian/ jessie/contrib Translation-en
1010 http://ftp.fr.debian.org/debian/ jessie/non-free amd64 Packages
release o=Debian,a=testing,n=jessie,l=Debian,c=non-free
origin ftp.fr.debian.org
1010 http://ftp.fr.debian.org/debian/ jessie/contrib amd64 Packages
release o=Debian,a=testing,n=jessie,l=Debian,c=contrib
origin ftp.fr.debian.org
1010 http://ftp.fr.debian.org/debian/ jessie/main amd64 Packages
release o=Debian,a=testing,n=jessie,l=Debian,c=main
origin ftp.fr.debian.org
Paquets épinglés :
--
Le mardi 28 janvier 2014 à 20:26 +1300, Chris Bannister a écrit :
> On Mon, Jan 27, 2014 at 11:53:28AM +0100, Ralf wrote:
> > > Could you explain this a litte better? Which file did you
> > > chmod, and how
> > > do you launch X in recovery mode?
> >
> > under init2/3 here are the laptop's values:
> >
> > tty [1-6] have group set "tty" in "rw"
> > tty0 remains set on root, without group privilege
> > I aligned this for tty0, which made it
> >
> > (it looks like the system "forgets" to adjust tty0)
>
> Please show *exact* commands and output.
>
> I'm guessing you mean these:
> root@tal:~# ls -al /dev/tty[0-6]
> crw------- 1 root root 4, 0 Jul 15 2013 /dev/tty0
> crw------- 1 root tty 4, 1 Jan 28 2014 /dev/tty1
> crw------- 1 chrisb tty 4, 2 Jan 28 19:18 /dev/tty2
> crw------- 1 chrisb tty 4, 3 Jan 28 19:54 /dev/tty3
> crw------- 1 chrisb tty 4, 4 Jan 28 19:25 /dev/tty4
> crw------- 1 chrisb tty 4, 5 Jan 28 13:09 /dev/tty5
> crw------- 1 chrisb tty 4, 6 Jan 28 19:50 /dev/tty6
>
> If I log out of tty3 then:
> root@tal:~# ls -al /dev/tty[0-6]
> crw------- 1 root root 4, 0 Jul 15 2013 /dev/tty0
> crw------- 1 root tty 4, 1 Jan 28 20:00 /dev/tty1
> crw------- 1 chrisb tty 4, 2 Jan 28 19:59 /dev/tty2
> crw-rw---- 1 root tty 4, 3 Jan 28 20:00 /dev/tty3
> crw------- 1 chrisb tty 4, 4 Jan 28 19:25 /dev/tty4
> crw------- 1 chrisb tty 4, 5 Jan 28 13:09 /dev/tty5
> crw------- 1 chrisb tty 4, 6 Jan 28 20:00 /dev/tty6
root@debian:/home/ralf# ls -al /dev/tty[0-6]
crw------- 1 root root 4, 0 janv. 29 08:09 /dev/tty0
crw-rw---- 1 root tty 4, 1 janv. 29 08:09 /dev/tty1
crw-rw---- 1 root tty 4, 2 janv. 29 08:09 /dev/tty2
crw-rw---- 1 root tty 4, 3 janv. 29 08:09 /dev/tty3
crw-rw---- 1 root tty 4, 4 janv. 29 08:09 /dev/tty4
crw-rw---- 1 root tty 4, 5 janv. 29 08:09 /dev/tty5
crw-rw---- 1 root tty 4, 6 janv. 29 08:09 /dev/tty6
ralf@debian:~$ ls -al /dev/tty[0-6]
crw------- 1 root root 4, 0 janv. 29 08:09 /dev/tty0
crw-rw---- 1 root tty 4, 1 janv. 29 08:09 /dev/tty1
crw-rw---- 1 root tty 4, 2 janv. 29 08:09 /dev/tty2
crw-rw---- 1 root tty 4, 3 janv. 29 08:09 /dev/tty3
crw-rw---- 1 root tty 4, 4 janv. 29 08:09 /dev/tty4
crw-rw---- 1 root tty 4, 5 janv. 29 08:09 /dev/tty5
crw-rw---- 1 root tty 4, 6 janv. 29 08:09 /dev/tty6
>
> Still not sure what you mean by "launch X in recovery mode
>
In order to use the keyboard, I need to start in recovery mode.
If I start through standard init scripts, in default level 2,
I receive mapping warnings & errors from xkbcomp, which end with loosing
the ability to use the keyboard (as soon as X has begun to run), I
explained this
https://lists.debian.org/debian-user/2014/01/msg01311.html
message-id
[🔎] CAJVhHMggg=YGhN5XDUiuw47o35jqPn=YdLhP_ou7aK=X1m9h5g@mail.gmail.com
[it looks like there were two issues: the virtual console tty0 &
xkbcomp]
------------------------------- End of answers - ralf
> > >
> > > > I was using wheezy, plus deb-multimedia & mozilla-esr.
> > > > I upgraded and dist-upgraded to jessie, but the issue
> > > remains.
> > > > Default amd64 kernel config.
> >
> > > What is the output of:
> > > root@tal:~# cat /etc/apt/sources.list
> > deb http://ftp.fr.debian.org/debian/ jessie main contrib non-free
> > deb http://security.debian.org/ jessie/updates main contrib non-free
> > deb http://www.deb-multimedia.org/ jessie main non-free
>
> It's difficult to diagnose where the trouble is if you have 3rd party
> repositories in use. For example, if you think you have found a bug in
> packageA which is from Debian but depends on packageB from a 3rd party
> repository then the bug report for packageA won't even be looked at!
>
> So can you get your system to a state where there are no 3rd party
> packages installed, and see if the problem still exists?
>
> Note: Due to the way deb-multimedia.org versions their packages, it is
> not as simple as just removing the entry from the sources list,
> unfortunately. The package wll have to be purged then installed from the
> Debian repos.
>
> I am curious ... what package(s) are you using from deb-multimedia.org
> which isn't available from ftp.fr.debian.org?
>
> > > root@tal:~# ls -al /etc/apt/sources.list.d/
> > -rw-r--r-- 1 root root 176 déc. 21 00:41 google-chrome.list
>
> If removing the deb-multimedia.org repo doesn't fix it, then you'll have
> to remove that as well. This is only for testing purposes, once you have
> a working system, then you can start adding packages the missing
> packages one by one to see when the problem starts again.
>
>
> > > root@tal:~# apt-cache policy
> > Fichiers du paquet :
> > 100 /var/lib/dpkg/status
> > release a=now
> > 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
> > release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
> > origin dl.google.com
>
> Well, here you have the stable repository, but the rest are for jessie.
> They should all be the same (unless you're using apt-pinning?)
>
> --
> "If you're not careful, the newspapers will have you hating the people
> who are being oppressed, and loving the people who are doing the
> oppressing." --- Malcolm X
>
>
Reply to: