Hi
jpff wrote:
> 1) Why will vmlinuz-3.16.0-4-amd64 not load (says loading and the does
> nothing for over 30mins) when vmlinuz-3.2.0-4-amd64 does load?
>
don't know - I had same issue
In my case I found out that initrd was broken. I still have to unpack the
initrd copy /sbin/switch_root and
On 09/20/17 08:32, jpff wrote:
I seem to need to upgrade to Debian stretch to install my printer as
it needs hplip 3.16.11, ad I was running wheezy. ...
While some people succeed at major version upgrades, the few times I
have attempted it resulted in breakage, frustration, and lots of wasted
I seem to need to upgrade to Debian stretch to install my printer as
it needs hplip 3.16.11, ad I was running wheezy. I understand this
needs to be done in two stages, wheezy->jessie->stretch, but I still
need advice as I cannot find out the solution to my problem.
I tried upgrading from Wheezy
On 11/05/2016 08:11 AM, someone wrote wrote:
> On Sun, Oct 02, 2016 at 02:39:50PM -0700, David Christensen wrote:
>> early on, so I pursued the KISS approach
>>
>> I find it helpful to:
>>
>> 1. Have a dedicated hardware firewall/ router appliance.
>>
>> 2. Have more than one computer, each
Hi Hans,
so the radeon driver seems to work but maybe needs some tweaking.
1) Let's have a look at Xorg.0.log.
grep -i chipset /var/log/Xorg.0.log
grep -i render /var/log/Xorg.0.log
(Maybe, append the file to your message)
2) Is there a file /etc/X11/xorg.conf?
3) Take a look at the
Hi,
Am 09.10.2016 um 23:46 schrieb Brian:
On Sat 08 Oct 2016 at 13:50:19 +0200, Hans Kraus wrote:
after following the propositions of Brian:
dpkg -l | grep fglrx
Lines with "ii" indicate installed packages. Purge and see what a reboot
does.
and Jörg-Volker Peetz:
Hi,
I also saw the
On Sat 08 Oct 2016 at 13:50:19 +0200, Hans Kraus wrote:
> after following the propositions of Brian:
> >
> > dpkg -l | grep fglrx
> >
> >Lines with "ii" indicate installed packages. Purge and see what a reboot
> >does.
> and Jörg-Volker Peetz:
> > Hi,
> >
> > I also saw the other e-mail exchange
Hi,
after following the propositions of Brian:
dpkg -l | grep fglrx
Lines with "ii" indicate installed packages. Purge and see what a reboot
does.
and Jörg-Volker Peetz:
> Hi,
>
> I also saw the other e-mail exchange with Brian where you concluded
to purge all
> "fglrx"-related packages.
On Fri 07 Oct 2016 at 19:05:23 +0200, Hans Kraus wrote:
> Hi,
>
> Am 06.10.2016 um 20:43 schrieb Brian:
> >On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote:
> >
> >[...]
> >>>(What does the glxinfo command give?)
> >>>
> >>root@robbe:~# glxinfo
> >>Error: unable to open display
> >
> >That
Hi,
Am 06.10.2016 um 20:43 schrieb Brian:
On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote:
[...]
(What does the glxinfo command give?)
root@robbe:~# glxinfo
Error: unable to open display
That is when you used a terminal. Boot into X with
xinit -- vt$XDG_VTNR
It is not pretty
Hans Kraus composed on 2016-10-02 17:59 (UTC+0200):
I upgraded my Debian server about a week ago from Wheezy to Jessie.
After that the GUI stopped, I see only the grey screen with the sad
computer telling me " Oh no, Something is Wrong" and the only option is
to log out.
I'm using Gnome as
Hi,
I also saw the other e-mail exchange with Brian where you concluded to purge all
"fglrx"-related packages. Similarily, there seem to be "nvidia" packages on your
system. Try
dpkg -l | grep -i nvidia
Purge them also. Then have a look which xorg-video drivers are left:
dpkg -l | grep
Hi,
the requested outputs:
Am 06.10.2016 um 19:56 schrieb Jörg-Volker Peetz:
Hans Kraus wrote on 10/06/16 19:40:
Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz:
[already sent to the list; sent it again to you since you asked for CC]
Hans Kraus wrote on 10/04/16 20:01:
Hi,
The VGA
On Thu 06 Oct 2016 at 19:39:21 +0200, Hans Kraus wrote:
> Hi,
>
> Am 05.10.2016 um 20:58 schrieb Brian:
> >On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:
> >
> >>thanks to all. Brian is right with his opinion that I'm not subscribed
> >>to the list. I sent a 'subscribe' to
> >> but
Hans Kraus wrote on 10/06/16 19:40:
>
>
> Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz:
>> [already sent to the list; sent it again to you since you asked for CC]
>>
>> Hans Kraus wrote on 10/04/16 20:01:
>>> Hi,
>>>
>>> The VGA output:
>>>
Am 05.10.2016 um 22:16 schrieb Jörg-Volker Peetz:
[already sent to the list; sent it again to you since you asked for CC]
Hans Kraus wrote on 10/04/16 20:01:
Hi,
The VGA output:
01:00.0 VGA compatible controller:
Hi,
Am 05.10.2016 um 20:58 schrieb Brian:
On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:
thanks to all. Brian is right with his opinion that I'm not subscribed
to the list. I sent a 'subscribe' to
but didn't get an answer
(or at least I didn't find it).
The reply comes back to the
On Wed 05 Oct 2016 at 19:50:50 +0200, Hans Kraus wrote:
> thanks to all. Brian is right with his opinion that I'm not subscribed
> to the list. I sent a 'subscribe' to
> but didn't get an answer
> (or at least I didn't find it).
The reply comes back to the address you subscribed from. Maybe
Hi,
thanks to all. Brian is right with his opinion that I'm not subscribed
to the list. I sent a 'subscribe' to
but didn't get an answer
(or at least I didn't find it).
How do I switch drivers under Debian, especiallay from the "AMD FGLRX
driver for Radeon adapters" to the "free radeon
Hans Kraus wrote on 10/04/16 20:01:
> Hi,
>
> The VGA output:
>
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Turks
> XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
> Subsystem:
Patrick Bartek wrote:
> Hans Kraus wrote:
>
>> Hi,
>>
>> I upgraded my Debian server about a week ago from Wheezy to Jessie.
>
> What exactly did you do to "upgrade?" Did you read the Jessie Release
> Notes regarding distribution upgrading?
and as a side note, if it is
On Tue 04 Oct 2016 at 20:55:54 +0100, Brian wrote:
> Incidentally, we know X comes up for the OP (gnome-session runs. Without
> X it wouldn't). So this may not be the problem at all.
>
> glxinfo | grep render
>
> is a good command for the OP to run. We would be interested in its output.
The
On Tue 04 Oct 2016 at 14:41:11 -0400, Felix Miata wrote:
> Hans Kraus composed on 2016-10-04 20:01 (UTC+0200):
>
> >The VGA output:
> >
> >01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
> >[AMD/ATI] Turks XT
Hans Kraus composed on 2016-10-04 20:01 (UTC+0200):
The VGA output:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
...
As far as I
Hi,
The VGA output:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 03e0
> [ kernel, dist-upgrade ]
All looks fine, you seem to have an up to date Jessie system and the
only thing that was installed was the security update DSA-3684-1 of
this morning.
On 10/03/2016 08:42 PM, Hans Kraus wrote:
> Oct 02 17:24:37 robbe /etc/gdm3/Xsession[2351]: Xlib: extension "GLX"
>
Hi,
my results:
===
root@robbe:~# uname -a
Linux robbe 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03)
x86_64 GNU/Linux
===
root@robbe:~# apt-get update
On Mon 03 Oct 2016 at 18:50:59 +0200, Hans Kraus wrote:
> Hi, thank's for your sppedy reaction.
>
> With "gui stopped" I mean the following:
> After the boot process, instead of the graphical login screen where
> one can select the user, enter the password and do some selections,
> the following
On Sun 02 Oct 2016 at 20:02:39 +0100, Brian wrote:
> On Sun 02 Oct 2016 at 20:31:50 +0200, Christian Seiler wrote:
>
> > On 10/02/2016 05:59 PM, Hans Kraus wrote:
> > > I upgraded my Debian server about a week ago from Wheezy to Jessie.
> > > After that the GUI stopped,
> >
> > This is a bit
On 10/03/2016 06:50 PM, Hans Kraus wrote:
> With "gui stopped" I mean the following:
> After the boot process, instead of the graphical login screen where
> one can select the user, enter the password and do some selections,
> the following screen appears:
>
> A pic of a sad computer with the
Hi, thank's for your sppedy reaction.
With "gui stopped" I mean the following:
After the boot process, instead of the graphical login screen where
one can select the user, enter the password and do some selections,
the following screen appears:
A pic of a sad computer with the text (the first
On Mon, 3 Oct 2016 00:55:37 -0400, Felix Miata wrote:
>brian composed on 2016-10-02 14:23 (UTC-0400):
>
>> On Sun, 2 Oct 2016 19:29:12 +0200, err...@free.fr wrote:
>
>>>what is your hadware?
>>>graphic card?
>>>and did you have any drivers or firmware for this? like firmware free or
>>>non-free,
brian composed on 2016-10-02 14:23 (UTC-0400):
On Sun, 2 Oct 2016 19:29:12 +0200, err...@free.fr wrote:
what is your hadware?
graphic card?
and did you have any drivers or firmware for this? like firmware free or
non-free, or drivers for nvidia, or amd etc.
It's an eMachines desktop
On Sun, 2 Oct 2016 17:59:48 +0200 Hans Kraus
wrote:
> Hi,
>
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
What exactly did you do to "upgrade?" Did you read the Jessie Release
Notes regarding distribution upgrading?
B
On 10/02/2016 08:59 AM, Hans Kraus wrote:
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped, I see only the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.
>
> I'm using Gnome as my
On Sonntag, 2. Oktober 2016 17:59:48 PYST Hans Kraus wrote:
> Hi,
>
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped, I see only the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.
On Sun 02 Oct 2016 at 20:31:50 +0200, Christian Seiler wrote:
> On 10/02/2016 05:59 PM, Hans Kraus wrote:
> > I upgraded my Debian server about a week ago from Wheezy to Jessie.
> > After that the GUI stopped,
>
> This is a bit vague, so a better explanation would be good. What
> exactly do you
On Sun 02 Oct 2016 at 17:59:48 +0200, Hans Kraus wrote:
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped, I see only the grey screen with the sad
> computer telling me " Oh no, Something is Wrong" and the only option is
> to log out.
>
> I'm
On 10/02/2016 05:59 PM, Hans Kraus wrote:
> I upgraded my Debian server about a week ago from Wheezy to Jessie.
> After that the GUI stopped,
This is a bit vague, so a better explanation would be good. What
exactly do you mean "gui stopped"? Did that happen during the
update? Or at boot? Does the
On Sun, 2 Oct 2016 19:29:12 +0200, you wrote:
>what is your hadware?
>graphic card?
>and did you have any drivers or firmware for this? like firmware free or
>non-free, or drivers for nvidia, or amd etc.
It's an eMachines desktop which was originally supplied with Windows
7. I wiped Windows and
what is your hadware?
graphic card?
and did you have any drivers or firmware for this? like firmware free or
non-free, or drivers for nvidia, or amd etc.
signature.asc
Description: OpenPGP digital signature
On Sun, 2 Oct 2016 17:59:48 +0200, Hans Kraus wrote:
>Hi,
>
>I upgraded my Debian server about a week ago from Wheezy to Jessie.
>After that the GUI stopped, I see only the grey screen with the sad
>computer telling me " Oh no, Something is Wrong" and the only option is
>to log out.
>
>I'm using
Hi,
I upgraded my Debian server about a week ago from Wheezy to Jessie.
After that the GUI stopped, I see only the grey screen with the sad
computer telling me " Oh no, Something is Wrong" and the only option is
to log out.
I'm using Gnome as my desktop. I installed the package again with:
Hello,
It seems that libpam-systemd is correctly installed
dpkg --status libpam-systemd
Package: libpam-systemd
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 304
Maintainer: Debian systemd Maintainers
Jean-Paul Bouchet wrote:
> [...]
> Check that logind is properly installed and pam_systemd is getting
used at login.
> [...]
Could you check if you have libpam-systemd package installed? And also
please check if "loginctl" shows sessions.
Cheers,
Laurent Bigonville
a few days ago after a last upgrade of
Wheezy and a verification that our server was OK, including connection
features. The dist-upgrade has not been perfect: here are the last lines
of the process:
...
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
W: Possible missing firmware
Dnia 2016-06-30, czw o godzinie 12:04 +0100, Lisi Reisz pisze:
> I am in the process of upgrading a desktop form Wheezy to Jessie. So
> far it has gone fine, but it is hung here:
>
> Restarting services possibly affected by the upgrade:
> openbsd-inetd: restarting...done.
> exim4:
El Fri, 18 Mar 2016 00:42:00 -0600, Carlos Carcamo escribió:
> El 6 de marzo de 2016, 09:20, Camaleón escribió:
(...)
>>> 3. El wifi no parece encontrar redes disponibles.
>>
>> Eso te pasa por cambiar a KDE, ahora Network Manager se habrá hecho un
>> lío :-P
>>
>>> Para el
El 6 de marzo de 2016, 09:20, Camaleón <noela...@gmail.com> escribió:
> El Sat, 05 Mar 2016 19:07:27 -0600, Carlos Carcamo escribió:
>
>> Saludos lista,
>>
>> Tengo un pequeño problemita que no se como solucionar, tal vez me
>> puedan asistir un poco.
>
El Sat, 05 Mar 2016 19:07:27 -0600, Carlos Carcamo escribió:
> Saludos lista,
>
> Tengo un pequeño problemita que no se como solucionar, tal vez me
> puedan asistir un poco.
>
> Sucede que hice un dist-upgrade de wheezy a jessie, todo anda bien
> excepto por 3 cosas, 1. el
On Mar 5, 2016 18:08, "Carlos Carcamo" <eazyd...@gmail.com> wrote:
>
> Saludos lista,
>
> Tengo un pequeño problemita que no se como solucionar, tal vez me
> puedan asistir un poco.
>
> Sucede que hice un dist-upgrade de wheezy a jessie, todo anda bien
>
Saludos lista,
Tengo un pequeño problemita que no se como solucionar, tal vez me
puedan asistir un poco.
Sucede que hice un dist-upgrade de wheezy a jessie, todo anda bien
excepto por 3 cosas, 1. el grub no me reconoció una partición con
Fedora, 2. gdm3 no funciona y 3. El wifi no parece
Dan Ritter writes
That sounds very much like rsnapshot.
Thanks very much. I think this is actually a better solution
since it is based on rsync and can use ssh to backup other
systems.
Martin
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe.
The daily system backups had failed for several days so it was
time to investigate and I found that the time of death was after
upgrading squeeze to wheezy.
Pdumpfs is useful because each day's new backup consists
of hard links to all previous files plus any new files that have
been
On Thu, Aug 06, 2015 at 01:13:57PM -0500, martin McCormick wrote:
The daily system backups had failed for several days so it was
time to investigate and I found that the time of death was after
upgrading squeeze to wheezy.
Pdumpfs is useful because each day's new backup consists
of
Le Sat, 27 Jun 2015 07:08:49 + (UTC),
fred f.r...@yahoo.fr a écrit :
Bonsoir Bernard,
je ne comprends pas bien ta réponse, tu veux bien en dire
plus ?Merci !Fred
sudo -s
apt-get install apt aptitude dpkg libc6
slt
bernard
Bonjour Bernard,
tu veux dire qu'il faut
bonjour,
il faut mettre à jour les paquets que je cite avant de faire un
dist-upgrade
mode opératoire :
sudo -s
apt-get update --fix-missing
apt-get install apt aptitude dpkg libc6
apt-get upgrade
apt-get dist-upgrade
slt
bernard
Ok merci pour l'info Bernard.
Parcontre sudo -s pour
Bonsoir Bernard,
je ne comprends pas bien ta réponse, tu veux bien en dire
plus ?Merci !Fred
sudo -s
apt-get install apt aptitude dpkg libc6
slt
bernard
Bonjour Bernard,
tu veux dire qu'il faut mettre à jour les paquets que tu cites avant un
dist-upgrade ?Merci,Fred
Le 26/06/2015 07:13, fred a écrit :
Bonjour à tou-te-s,
j'hésite à mettre à jour avec la commande citée en sujet de ce mel,
quelqu'un ici aurait des retours positifs à partager ?
Bonjour
1) D'un point de vue général, tout changement vers un progrès implique
des risques, même s'ils sont
Bonjour,
Le vendredi 26 juin 2015 à 10:32, maderios a écrit :
Le 26/06/2015 07:13, fred a écrit :
Bonjour à tou-te-s,
j'hésite à mettre à jour avec la commande citée en sujet de ce mel,
quelqu'un ici aurait des retours positifs à partager ?
Bonjour
1) D'un point de vue général, tout
Le 26/06/2015 07:13, fred a écrit :
Bonjour à tou-te-s,
j'hésite à mettre à jour avec la commande citée en sujet de ce mel,
quelqu'un ici aurait des retours positifs à partager ?
Si ton hésitation est relative à Jessie et son ecosystème, sache que tu ne
pourras pas rester éternellement
De : maderios mader...@gmail.com
À : debian-user-french@lists.debian.org
Envoyé le : Vendredi 26 juin 2015 10h32
Objet : Re: apt-get dist-upgrade de Wheezy vers Jessie
Le 26/06/2015 07:13, fred a écrit :
Bonjour à tou-te-s,
j'hésite à mettre à jour avec la commande citée en sujet de
Bonjour à tou-te-s,
j'hésite à mettre à jour avec la commande citée en sujet de ce mel,
quelqu'un ici aurait des retours positifs à partager ?
Merci !Fred
Salut, voici mon fstab:
# that works even if disks are added and removed. See fstab(5).
#
# file system mount point type options dump pass
# / was on /dev/sda1 during installation
UUID=2a235635-d5d2-4373-b6a5-ba38c64f24eb / ext4
errors=remount-ro 0 1
# swap was on
[Même si on ne gueule plus que quand les messages sont en HTML
seul, merci d’éviter de mettre trop de mise en forme. Le mode
texte est le mode préféré.]
Le mardi 31 mars 2015, 21:12:24 le pigeon a écrit :
[…]
*a start job is running for dev-disk ...** […]
Hmm, une rapide recherche sur ce
C'était bien ça! Merci Sylvain.
Cependant il reste un peu long à démarrer, mais je condidère comme résolu.
On 01/04/2015 11:44, le pigeon wrote:
Salut, voici mon fstab:
# that works even if disks are added and removed. See fstab(5).
#
# file system mount point type options dump pass
Forwarded Message
Subject: Re: upgrade de wheezy à testing,démarrage possible seulement
en (sysvinit)
Date: Wed, 1 Apr 2015 11:48:32 +0200
From: Jean-Michel OLTRA jm.ol...@espinasse.net
To: le pigeon le.pigeon.voyageur.dans.le.te...@openmailbox.org
Bonjour
Hello fellow Debian users,
I have been testing upgrading to Jessie given that release is coming
closer. I ran into a problem while upgrading which actually causes the
upgrade to hang and the system to get into a non-bootable state. I
actually managed to track down the problem to an interaction
On Wed, Apr 01, 2015 at 05:23:46PM +0200, Laurens Blankers wrote:
Hello fellow Debian users,
I have been testing upgrading to Jessie given that release is coming
closer. I ran into a problem while upgrading which actually causes the
upgrade to hang and the system to get into a non-bootable
origine du sujet ici :
http://debian-facile.org/viewtopic.php?pid=114572#p114572
Salut,
je viens de faire un
* aptitude safe-upgrade --full-resolver*
en mettant testing dans mes dépots, mais je ne peux pas démarrer en
mode normal. J'obtient ces messages :
*a start job is running for
En installant systemd...,
mais il parait que c'est pas bien :-)
André
On Tuesday 31 March 2015 21:12:24 le pigeon wrote:
origine du sujet ici :
http://debian-facile.org/viewtopic.php?pid=114572#p114572
je viens de faire un
* aptitude safe-upgrade --full-resolver*
en mettant testing dans
systemd est installé :/
On 31/03/2015 21:24, andre_deb...@numericable.fr wrote:
En installant systemd...,
mais il parait que c'est pas bien :-)
André
On Tuesday 31 March 2015 21:12:24 le pigeon wrote:
origine du sujet ici :
http://debian-facile.org/viewtopic.php?pid=114572#p114572
je viens
Hello,
usually when the distribution changes, I update my system rather than
reinstall everything. But for the transition from wheezy to jessie,
I would like to know:
-1- Is it possible to go from wheezy to jessie, keeping sysvinit.
-2- if not, from what I read on the internet, go from
On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:
usually when the distribution changes, I update my system rather than
reinstall everything. But for the transition from wheezy to jessie,
I would like to know:
-1- Is it possible to go from wheezy to jessie, keeping sysvinit.
On 06/01/15 13:12, Brian wrote:
On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:
usually when the distribution changes, I update my system rather than
reinstall everything. But for the transition from wheezy to jessie,
I would like to know:
-1- Is it possible to go from wheezy
On Tue, Jan 06, 2015 at 01:27:35PM +0100, Tony van der Hoff wrote:
Date: Tue, 06 Jan 2015 13:27:35 +0100
From: Tony van der Hoff t...@vanderhoff.org
To: debian-user@lists.debian.org
Subject: Re: upgrade from wheezy to jessie
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
On 06/01/15 13:48, Gerard ROBIN wrote:
On Tue, Jan 06, 2015 at 01:27:35PM +0100, Tony van der Hoff wrote:
Date: Tue, 06 Jan 2015 13:27:35 +0100
From: Tony van der Hoff t...@vanderhoff.org
To: debian-user@lists.debian.org
Subject: Re: upgrade from wheezy to jessie
User-Agent: Mozilla/5.0 (X11
On Ter, 06 Jan 2015, Joe wrote:
The main issue is that anything local mounted in /etc/fstab (even
removable drives) will be treated as essential, and if they are not
there, boot will fail. The answer is either to remove any such drives
from fstab, as the kernel automounting should be good enough
On Tue, 06 Jan 2015 13:42:43 +
Eduardo M KALINOWSKI edua...@kalinowski.com.br wrote:
On Ter, 06 Jan 2015, Joe wrote:
The main issue is that anything local mounted in /etc/fstab (even
removable drives) will be treated as essential, and if they are not
there, boot will fail. The answer
On Tue 06 Jan 2015 at 14:32:00 +0100, Tony van der Hoff wrote:
On 06/01/15 13:48, Gerard ROBIN wrote:
I agree with you regarding jessie, I installed it on a USB drive and
it works fine with systend, but but what concerns me is the transition
from sysvinit to systemd on wheezy. If I
On Tue, 6 Jan 2015 13:48:10 +0100
Gerard ROBIN g.rob...@free.fr wrote:
I agree with you regarding jessie, I installed it on a USB drive and
it works fine with systend, but but what concerns me is the
transition from sysvinit to systemd on wheezy. If I understand what I
read on the web (in
On Tue 06 Jan 2015 at 13:48:10 +0100, Gerard ROBIN wrote:
On Tue, Jan 06, 2015 at 01:27:35PM +0100, Tony van der Hoff wrote:
My advice would be to go with the minimum effort upgrade, as you would
have done in the past. I've been running Jessie in a KVM client for
several months now,
On 1/6/2015 7:27 AM, Tony van der Hoff wrote:
On 06/01/15 13:12, Brian wrote:
On Tue 06 Jan 2015 at 12:11:48 +0100, Gerard ROBIN wrote:
usually when the distribution changes, I update my system rather than
reinstall everything. But for the transition from wheezy to jessie,
I would like to
On 01/06/2015 06:57 AM, Joe wrote:
On Tue, 06 Jan 2015 13:42:43 +
Eduardo M KALINOWSKI edua...@kalinowski.com.br wrote:
On Ter, 06 Jan 2015, Joe wrote:
The main issue is that anything local mounted in /etc/fstab (even
removable drives) will be treated as essential, and if they are not
On Tue, Jan 06, 2015 at 01:35:48PM +, Joe wrote:
Date: Tue, 6 Jan 2015 13:35:48 +
From: Joe j...@jretrading.com
To: debian-user@lists.debian.org
Subject: Re: upgrade from wheezy to jessie
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
On Tue, 6 Jan 2015 13:48:10
On Mi, 03 dec 14, 13:05:11, Kenneth Dombrowski wrote:
Hello debian users,
I am having trouble dist-upgrading from squeeze-lts to wheezy.
I have been following these instructions to upgrade from pre-lts squeeze
(didn't find any specific ones for lts):
On Mi, 03 dec 14, 13:44:31, Kenneth Dombrowski wrote:
Hi again,
I just wanted to follow up with more info.
I think these packages that want to stay with squeeze are pinned, for example:
root@gilgamesh:~/tmp# apt-cache policy perl-base
perl-base:
Installed: 5.10.1-17squeeze6
Hello debian users,
I am having trouble dist-upgrading from squeeze-lts to wheezy.
I have been following these instructions to upgrade from pre-lts squeeze
(didn't find any specific ones for lts):
https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.html
The problem happens
Hi again,
I just wanted to follow up with more info.
I think these packages that want to stay with squeeze are pinned, for example:
root@gilgamesh:~/tmp# apt-cache policy perl-base
perl-base:
Installed: 5.10.1-17squeeze6
Candidate: 5.14.2-21+deb7u2
Version table:
5.14.2-21+deb7u2 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I have a server that was upgraded from squeeze-lts to wheezy.
Since the upgrade, any mail coming from hotmail servers can no longer be
delivered to the server.
I see lots of errors like these in the /var/log/exim4/mainlog
TLS error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
SOLVED ...
Short story:
regenerate exim.crt and exim.key
Turns out that most servers out in the world were happy with the re-use
of the old exim.crt and exim.key files.
These servers had problems until I created new key and cert files:
on your system?
Yours,
Hans
Gesendet:Freitag, 05. September 2014 um 08:57 Uhr
Von:Hans hans.ullr...@loop.de
An:debian-user@lists.debian.org
Betreff:Re: Aw: Re: GUI fails after upgrade from wheezy to jessie
Am Freitag, 5. September 2014, 10:15:36 schrieb Hans Heider:
Hi Hans,
thank you
Am Samstag, 6. September 2014, 17:18:11 schrieb Hans Heider:
Hi Hans,
Hi Hans
I purged whole X, kdm, gdm3, xfdestop4, lxde and finally also twm. After
reinstalling lxde GUI login now works. However, auto-adjusting the
resoltion with an external monitor does not work. Using lxrandr helps,
Hi Hans,
thank you for sharing your ideas.
I used apt-get dist-upgrade for my upgrade from wheezy to jessie. Kernel command line in grub does not have any vga= options.
I removed gdm3 and x11-session from /etc/init.rd/ but somehow Xorg still got started. Cannot image how/why
Am Freitag, 5. September 2014, 10:15:36 schrieb Hans Heider:
Hi Hans,
thank you for sharing your ideas.
I used apt-get dist-upgrade for my upgrade from wheezy to jessie. Kernel
command line in grub does not have any vga= options.
I removed gdm3 and x11-session from /etc/init.rd
Hi all,
I just upgraded from Debian stable (wheezy) to testing (jessie). Unfortunately, I encountered three different problems which are (in decending severity):
1. The GUI became totally unusable. After booting X is started up but in 99% of all tries it just leaves me with a blank screen.
Am Donnerstag, 4. September 2014, 10:57:47 schrieb Hans Heider:
Hi all,
I just upgraded from Debian stable (wheezy) to testing (jessie).
Unfortunately, I encountered three different problems which are (in
decending severity): 1. The GUI became totally unusable. After booting X is
started
I have 2 debian virtual machines running under Windows Hyper-V Server 2012.
I upgraded them from squeeze to wheezy.
They can boot with the squeeze kernel 2.6.32-5-amd64 ok.
But they cannot boot with the wheezy kernel 3.2.0-4-amd64.
Loading, please wait.
Gave up waiting for root device. Common
like there is a bug in initramfs-tools.
Peter
-Original Message-
From: Peter McGill [mailto:petermcg...@goco.net]
Sent: August-13-14 12:21 PM
To: 'debian-user@lists.debian.org'
Subject: Boot failure after upgrade to wheezy
I have 2 debian virtual machines running under Windows Hyper-V
Hi,
I recently upgraded my VPS from squeeze to wheezy using the Debian upgrade
instructions. There were a few issues, most of which I've sorted, but this
one's a killer.
The server runs a postfix mail server with dovecot imap, and sasl
authentication via mysql. After the upgrade I am no longer
1 - 100 of 293 matches
Mail list logo