On Friday, 6 January 2017 14:38:01 CET Steven Kauffmann wrote:
> When booting I get the following output: give up waiting for root device ...
Looks like the kernel boots but cannot find the disk that contains '/'
> I can still boot into the old kernel (3.2.0-4-amd64).
While in grub menu, check t
On 01/06/2017 08:38 AM, Steven Kauffmann wrote:
> Hi all,
>
> I'm busy with an upgrade from Wheezy to Jessie. I didn't had any issue during
> the upgrade so far, but I cannot boot into the new kernel (3.16.0-4-amd64).
>
> When booting I get the following output: giv
On 01/06/2017 08:38 AM, Steven
Kauffmann wrote:
I'm busy with an upgrade from Wheezy to Jessie. I didn't
had any issue during the upgrade so far, but I cannot boot
into the new kernel (3.16
Hi all,
I'm busy with an upgrade from Wheezy to Jessie. I didn't had any issue
during the upgrade so far, but I cannot boot into the new kernel
(3.16.0-4-amd64).
When booting I get the following output: give up waiting for root device ...
I can still boot into the old kernel (3.2
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 other
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 w
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. Si
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 but
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
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 xorg-v
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 outpu
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 didn'
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: Advanc
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 that
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 driver,
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: AS
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
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 R
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 kn
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
Flags:
> [ 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"
> m
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
Get
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 s
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 text
e" are on the same line; Thundebird
insists on line breaks ...
Kind regards,
Hans
Am 02.10.2016 um 20:31 schrieb Christian Seiler:
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 vagu
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 which
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.
>
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 on
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.
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
>
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 a
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
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
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
Architecture: amd64
Multi-Arch: same
Source: systemd
Versio
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
Hello,
We used during 2 years Gnome and gdm3 on a server with Debian Wheezy to
let users work from their Windows PC via Cygwin and xlaunch (xdmcp). It
worked well till the upgrade to Jessie, for these Windows PC, as for the
system console, a very simple terminal.
The migration has been done
Bill Harris writes:
> Lisi Reisz writes:
>
>> I would do the dist-upgrade first and clear up any mess remaining afterwards.
> I'll report back, assuming that the results of this adventure don't
> brick my machine /and/ my network. :-)
Well, I didn't quite brick it, but it didn't work too great
Lisi Reisz writes:
> I would do the dist-upgrade first and clear up any mess remaining afterwards.
Thanks, Lisi. I was coming to that conclusion, too, but I was looking
for any sort of confirmation that I wasn't guaranteed to brick the
machine.
I'll report back, assuming that the results of t
On Monday 04 July 2016 21:52:49 Bill Harris wrote:
> Gary Dale writes:
> > On 04/07/16 03:23 PM, Bill Harris wrote:
> >>> The simplest solution would be to reinstall the offending
> >>> packages. Apt-get doesn't have that option but aptitude does. I can't
> >>> try this at home but it may resolve
Bill Harris writes:
> - I have yet to do the `apt dist-upgrade` (I downloaded all the packages
> and then quit), so I've got to do that at some time.
>
> - My question was whether I
>
> - reinstall the packages first, and then do the dist-upgrade later, or
>
> - do the dist-upgrade first, a
Gary Dale writes:
> On 04/07/16 03:23 PM, Bill Harris wrote:
>>> The simplest solution would be to reinstall the offending
>>> packages. Apt-get doesn't have that option but aptitude does. I can't
>>> try this at home but it may resolve the conflicts. Install aptitude
>>> and give it a try.
>>
>
On 04/07/16 03:23 PM, Bill Harris wrote:
Gary Dale writes:
On 04/07/16 12:32 PM, Bill Harris wrote:
Summary:
emacs24(1 bug), dbus(1 bug), gnome-settings-daemon(1 bug), libxml2(1 bug),
debhelper(1 bug), openbsd-inetd(1 bug), smartmontools(1 bug), ruby-hpricot(1
bug), cdrdao(1 bug), libglu
Gary Dale writes:
> On 04/07/16 12:32 PM, Bill Harris wrote:
>> Summary:
>> emacs24(1 bug), dbus(1 bug), gnome-settings-daemon(1 bug), libxml2(1 bug),
>> debhelper(1 bug), openbsd-inetd(1 bug), smartmontools(1 bug), ruby-hpricot(1
>> bug), cdrdao(1 bug), libgluegen2-rt-java(1 bug), ndiff(1 b
Cindy-Sue Causey writes:
> I've used "apt-get install --reinstall" successfully a couple times
> during issues. From "man apt-get", this flag's description is:
>
> "Re-install packages that are already installed and at the newest version."
I thought I had seen that apt could do that. Thanks.
On Mon 04 Jul 2016 at 15:09:35 -0400, Cindy-Sue Causey wrote:
> On 7/4/16, Gary Dale wrote:
> >
> > The simplest solution would be to reinstall the offending packages.
> > Apt-get doesn't have that option but aptitude does. I can't try this at
> > home but it may resolve the conflicts. Install ap
On 7/4/16, Gary Dale wrote:
> On 04/07/16 12:32 PM, Bill Harris wrote:
>> I updated one laptop a month or two ago using the process on
>> https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html,
>> and it worked smoothly. Then I tried the same thing yesterday on a
>> secon
On 04/07/16 12:32 PM, Bill Harris wrote:
I updated one laptop a month or two ago using the process on
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html,
and it worked smoothly. Then I tried the same thing yesterday on a
second laptop, except that I forgot to get rid
I updated one laptop a month or two ago using the process on
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html,
and it worked smoothly. Then I tried the same thing yesterday on a
second laptop, except that I forgot to get rid of a wheezy backports
entry; instead, I ju
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.
>
John Conover wrote:
>
> In Wheezy, the index of multiple sound cards is configured in
> /etc/modprobe.d/alsa-base.conf.
>
> In Jessie, the index of multiple sound cards is configured in
> /lib/modprobe.d/aliases.conf.
>
> This is true, isn't it?
>
> Thanks,
>
> John
yes
In Wheezy, the index of multiple sound cards is configured in
/etc/modprobe.d/alsa-base.conf.
In Jessie, the index of multiple sound cards is configured in
/lib/modprobe.d/aliases.conf.
This is true, isn't it?
Thanks,
John
--
John Conover, cono...@rahul.net, http://www.johncon.com/
On Sunday 31 January 2016 17:35:46 Chris Bannister wrote:
> On Thu, Jan 28, 2016 at 10:53:55AM +, Lisi Reisz wrote:
> > Not quite. It still does need the sentence:
> > "Please upgrade your kernel before or while upgrading udev."
> > Perhaps even better:
> > "Please upgrade your kernel before u
On Thu, Jan 28, 2016 at 10:53:55AM +, Lisi Reisz wrote:
>
> Not quite. It still does need the sentence:
> "Please upgrade your kernel before or while upgrading udev."
> Perhaps even better:
> "Please upgrade your kernel before upgrading udev."
> to precede it, since that would obviously be th
On Thursday 28 January 2016 10:28:23 Chris Bannister wrote:
> On Tue, Jan 26, 2016 at 10:38:36PM +0200, Selim T. Erdoğan wrote:
> > On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote:
> > > Am 26.01.2016 um 11:08 schrieb Chris Bannister:
> > > > On Sun, Jan 24, 2016 at 11:58:16AM +0100,
On Tue, Jan 26, 2016 at 11:19:26PM +, Brian wrote:
> This might be an improvement:
>
> You can force the installation of this version of udev, WHICH WILL NOT
> WORK WITH YOUR PRESENT, RUNNING KERNEL AT THE NEXT REBOOT, by creating
> the /etc/udev/kernel-upgrade file.
That sounds confusi
On Tue, Jan 26, 2016 at 10:38:36PM +0200, Selim T. Erdoğan wrote:
> On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote:
> > Am 26.01.2016 um 11:08 schrieb Chris Bannister:
> > > On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
> > >>
> > >> Please upgrade your kernel before
Lisi Reisz wrote:
>
> I think it is you who have had a slight aberration, deloptes. ;-)
>
> Lisi
>
> Sorry for erroneous off-list post.
at least gmail seem to work better than yahoo
ven't got one in my system.
>
> if we read the OPs original post we would note that he's upgrading from
> wheezy to jessie, which is not recommended. he must first upgrade to
> squeeze and then jessie. RTFM :)
7 -> 6 -> 8
I think it is you who have had a slight aberration, deloptes. ;-)
Lisi
Sorry for erroneous off-list post.
On Tue 26 Jan 2016 at 22:38:36 +0200, Selim T. Erdoğan wrote:
> On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote:
>
> > You can force the upgrade of the udev by creating the flag file
> > /etc/udev/kernel-upgrade simply by running something like
> > touch /etc/udev/kernel-upgrade
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 26 Jan 2016 22:34:25 +0100
deloptes wrote:
>Charlie Kravetz wrote:
>
>>
>> If I am reading this list correctly, release sequence was Squeeze,
>> Wheezy, Jessie. That would make the upgrade wheezy to jessie correct
Charlie Kravetz wrote:
>
> If I am reading this list correctly, release sequence was Squeeze,
> Wheezy, Jessie. That would make the upgrade wheezy to jessie correct.
>
Yes apologies - this should be something with the arm related kernel and
udev versions.
regards
m.
>
> if we read the OPs original post we would note that he's upgrading from
> wheezy to jessie, which is not recommended. he must first upgrade to
> squeeze and then jessie. RTFM :)
it was my mistake - jessie follows wheezy - I apologize
regards
On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote:
> Am 26.01.2016 um 11:08 schrieb Chris Bannister:
> > On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
> >>
> >> Please upgrade your kernel before or while upgrading udev.
> >>
> >> AT YOUR OWN RISK, you can force the inst
I'd remove it if
>> the latter, e.g. I haven't got one in my system.
>
>if we read the OPs original post we would note that he's upgrading from
>wheezy to jessie, which is not recommended. he must first upgrade to
>squeeze and then jessie. RTFM :)
>
>regards
&
we would note that he's upgrading from
wheezy to jessie, which is not recommended. he must first upgrade to
squeeze and then jessie. RTFM :)
regards
Am 26.01.2016 um 11:08 schrieb Chris Bannister:
> On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
>>
>> Please upgrade your kernel before or while upgrading udev.
>>
>> AT YOUR OWN RISK, you can force the installation of this version of udev
>> WHICH DOES NOT WORK WITH YOUR RUNNING K
On Tuesday 26 January 2016 10:08:35 Chris Bannister wrote:
> On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
> > Please upgrade your kernel before or while upgrading udev.
> >
> > AT YOUR OWN RISK, you can force the installation of this version of udev
> > WHICH DOES NOT WORK WITH YO
On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
>
> Please upgrade your kernel before or while upgrading udev.
>
> AT YOUR OWN RISK, you can force the installation of this version of udev
> WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
> AT THE NEXT REBOOT
> install both at the same time?
Are you kidding me?!
Wauw, amazing, just freaking amazing!
24.01.2016, 18:56, "Michael Biebl" :
> Am 24.01.2016 um 11:58 schrieb Martin Hanson:
>> I am trying to upgrade a cubox (arm) from Wheezy to Jessie, but I keep
>> running into problems with udev. When I try to install latest
On Sunday 24 January 2016 21:50:35 Martin Hanson wrote:
> > install both at the same time?
>
> Are you kidding me?!
No.
# aptitude install linux-image-whatever udev
Lisi
Am 24.01.2016 um 11:58 schrieb Martin Hanson:
> I am trying to upgrade a cubox (arm) from Wheezy to Jessie, but I keep
> running into problems with udev. When I try to install latest kernel from
> backports:
>
>
> # dpkg -i linux-image-4.3.0-0.bpo.1-armmp_4.3.3-7~bpo8+
Martin Hanson wrote:
> Please upgrade your kernel before or while upgrading udev.
install both at the same time?
I am trying to upgrade a cubox (arm) from Wheezy to Jessie, but I keep running
into problems with udev. When I try to install latest kernel from backports:
# dpkg -i linux-image-4.3.0-0.bpo.1-armmp_4.3.3-7~bpo8+1_armhf.deb
dpkg: regarding .../linux-image-4.3.0-0.bpo.1-armmp_4.3.3-7~bpo8
Quoting Steve McIntyre (st...@einval.com):
> mar...@server1.shellworld.net
> >
> >622 upgraded, 0 newly installed, 0 to remove and 551 not upgraded.
> >Need to get 222 MB of archives.
> >After this operation, 48.4 MB of additional disk space will be used.
> >Do you want to continue [Y/n]?
> >
> >Ne
That should have been a subject of
wheezy to jessie. I goofed
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20150716161308.01b2022...@server1.shellworld.net
On Wed, May 13, 2015 at 05:07:28PM CEST, "Thomas H. George"
said:
> The solution was to remove a duplicate entry from fstab.
>
> dpkg-reconfigure gdm3 exited with a line about the duplicate entry in
> fstab. My fstab is a mess of entries because whenever I connected a usb
> storage device it wou
The solution was to remove a duplicate entry from fstab.
dpkg-reconfigure gdm3 exited with a line about the duplicate entry in
fstab. My fstab is a mess of entries because whenever I connected a usb
storage device it would be reported as a device such as sr, sr0, sr1, sg0,
sdd1, etc. For each I m
On Mon, May 11, 2015 at 11:31:41PM +0200, Michael Biebl wrote:
> Am 11.05.2015 um 23:10 schrieb Thomas H. George:
> > On Mon, May 11, 2015 at 09:10:36PM +0100, Lisi Reisz wrote:
> >> On Monday 11 May 2015 20:52:27 Thomas H. George wrote:
> >>> I ENCOUNTERED THIS SAME PROBLEM WITH THE INSTILLATION O
Quoting Thomas H. George (li...@tomgeorge.info):
> The dist-upgrade with no apparent problems but gdm3 desktop failed to
> open. I ran /etc/init.d/gdm3 restart which failed with messages to
> check systemctl status gdm.service and journalctl -xn. The outputs of
> these commands are given below.
>
Am 11.05.2015 um 23:10 schrieb Thomas H. George:
> On Mon, May 11, 2015 at 09:10:36PM +0100, Lisi Reisz wrote:
>> On Monday 11 May 2015 20:52:27 Thomas H. George wrote:
>>> I ENCOUNTERED THIS SAME PROBLEM WITH THE INSTILLATION OF JESSIE ON A NEW
>>> COMPUTER, POSTED THE DESCRIPTION TO THE DEBIAN US
On Monday 11 May 2015 22:10:50 Thomas H. George wrote:
> On Mon, May 11, 2015 at 09:10:36PM +0100, Lisi Reisz wrote:
> > On Monday 11 May 2015 20:52:27 Thomas H. George wrote:
> > > I ENCOUNTERED THIS SAME PROBLEM WITH THE INSTILLATION OF JESSIE ON A
> > > NEW COMPUTER, POSTED THE DESCRIPTION TO TH
On Mon, May 11, 2015 at 09:10:36PM +0100, Lisi Reisz wrote:
> On Monday 11 May 2015 20:52:27 Thomas H. George wrote:
> > I ENCOUNTERED THIS SAME PROBLEM WITH THE INSTILLATION OF JESSIE ON A NEW
> > COMPUTER, POSTED THE DESCRIPTION TO THE DEBIAN USER LIST AND RECEIVE NO
> > HELP.
>
> Maybe noone kn
On Monday 11 May 2015 20:52:27 Thomas H. George wrote:
> I ENCOUNTERED THIS SAME PROBLEM WITH THE INSTILLATION OF JESSIE ON A NEW
> COMPUTER, POSTED THE DESCRIPTION TO THE DEBIAN USER LIST AND RECEIVE NO
> HELP.
Maybe noone knew the answer. There's no need to shout.
Lisi
--
To UNSUBSCRIBE, em
The dist-upgrade with no apparent problems but gdm3 desktop failed to
open. I ran /etc/init.d/gdm3 restart which failed with messages to
check systemctl status gdm.service and journalctl -xn. The outputs of
these commands are given below.
I ENCOUNTERED THIS SAME PROBLEM WITH THE INSTILLATION OF J
Glad I could help, although I wouldn' call that a solution. I'd rather
have the proprietary drivers working with a mouse cursor that I could
see. Gaming tends to get a little difficult when you can't see the mouse =P
--Francisco
On 05/01/2015 07:02 PM, Rafael Dias da Silva wrote:
Unistalling t
Unistalling the proprietary fglrx driver for Radeon worked. I just
reinstall the xserver-xorg-video-ati and it's working.
The reason why I had the proprietary driver is that the radeon GPU would
increase the heat to 85-90 celsius and drain a lot of battery lfie (seems
to be ok with Jessie).
2015-
Well, that would be another chapter of my long battle to fix my discrete
card.
I have an integrated intel device and a discrete radeon 700 series.
I'll try uninstalling the proprietary drivers to settle with the open
source alternative (if it works I can even turn the radeon off with KMS and
stick
1 - 100 of 141 matches
Mail list logo
