On Wed, Jan 29, 2014 at 08:28:29AM +0100, Ralf wrote:
Hello Chris
The global information right after these introduction lines
detailed information within your mail: answer after each question
(console rights, recovery mode xkbcomp)
OK so you have no deb-multimedia packages installed now?
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
Hello Chris,
Thanks for your attention
pls hereafter the answers:
Le lundi 27 janvier 2014 à 11:24 +0100, Ralf Kaiser a écrit :
2014-01-27 Chris Bannister cbannis...@slingshot.co.nz
On Sun, Jan 26, 2014 at 09:09:43PM +0100, Ralf wrote:
Hi,
Three
there's a second issue after correcting tty0 by hand:
If I don’t boot in recovery, but launch standard init2 mode (without X)
change tty0 values (grp to tty, g+rw)
launch X - everything should work, but the keyboard doesn’t (trackpad is
OK):
the console delivers warnings and errors from xkbcomp:
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
Hi,
Three days ago wheezy began to freeze at the login prompt: no keyboard
and often no mouse, it's a i915 laptop from asus.
I looked in newsgroups whether it might be gdm3, but lighted didn't solve
the issue. I also looked for the xkeyboard mapping, and relaunched
dpkg-reconfigure, but that
On Sun, Jan 26, 2014 at 09:09:43PM +0100, Ralf wrote:
Hi,
Three days ago wheezy began to freeze at the login prompt: no keyboard
and often no mouse, it's a i915 laptop from asus.
xorg.log loads the intel sandy bridge driver correctly, also
other stuff like vesa_drv et fbdev_drv. AT the
7 matches
Mail list logo
