On Wednesday, October 9, 2024 11:30:36 AM CEST, Alexis Grigoriou wrote:
root@architect:~# dpkg -l 'linux-image*'
if someone would ask me, i would recommend to type (as root):
get rid of the old/unnecessary files:
# apt-get --purge autoremove
reinstall the current kernel:
# apt-get --reinstall
On 09/10/2024 16:30, Alexis Grigoriou wrote:
root@architect:~# apt-cache policy linux-image-amd64
linux-image-amd64:
Installed: (none)
Install this package and it will pull latest kernel. Perhaps you need to
fix nvidia issues as well.
On Wed, Oct 09, 2024 at 05:55:34 -0400, Timothy M Butterworth wrote:
> What version of Debian are you running? You should not have kernel 5.10.0
> and 6.1.0.
He doesn't. The vast majority of those kernel packages are in the "rc"
state (removed, but configuration files are not purged). Most likel
On Wed, 2024-10-09 at 05:55 -0400, Timothy M Butterworth wrote:
> What version of Debian are you running? You should not have kernel
> 5.10.0 and 6.1.0. Please post the contents of /etc/apt/sources.list.
> It looks like you have repo's from two different Debian releases.
root@architect:~# cat /et
On Wed, Oct 9, 2024 at 5:31 AM Alexis Grigoriou wrote:
> On Wed, 2024-10-09 at 08:59 +, Michael Kjörling wrote:
> > On 9 Oct 2024 11:05 +0300, from ale...@nanoid.net (Alexis Grigoriou):
> > > It seems like one of my Debian Bookworm installations is stuck on
> >
On 9 Oct 2024 12:30 +0300, from ale...@nanoid.net (Alexis Grigoriou):
> This is an excerpt from /etc/syslog:
>
> 2024-10-07T19:33:45.474746+03:00 architect systemd-modules-load[320]:
> Error running install command 'modprobe nvidia-modeset ; modprobe -i
> nvidia-current-drm ' for module nvidia_drm
On Wed, 2024-10-09 at 08:59 +, Michael Kjörling wrote:
> On 9 Oct 2024 11:05 +0300, from ale...@nanoid.net (Alexis Grigoriou):
> > It seems like one of my Debian Bookworm installations is stuck on
> > this kernel. All other Bookworm installations are running 6.1.0.26-
> &g
On 9 Oct 2024 11:05 +0300, from ale...@nanoid.net (Alexis Grigoriou):
> It seems like one of my Debian Bookworm installations is stuck on
> this kernel. All other Bookworm installations are running 6.1.0.26-
> amd64. I installed 6.1.0.26 manually but I got a lot of errors during
> boo
Hello list,
It seems like one of my Debian Bookworm installations is stuck on
this kernel. All other Bookworm installations are running 6.1.0.26-
amd64. I installed 6.1.0.26 manually but I got a lot of errors during
boot and no GUI.
I remember there was an issue regarding a kernel update a few
Hi, Thanks for reading, and I need some help.
Description: About 2024 Mar 14 0:0:0, I use the shortcut 'Ctrl + Alt + L', lock
the screen, after several hours, I want to login the computer. Then, I click
one mouse, and type one enter key, the screen light, and everything stuck and
Hi Sven,
Sven Joachim writes:
> On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
>
>> (Please keep me in CC as I'm not subscribed to the users ML.)
>>
>> Hi,
>>
>> TL;DR I've been experience stuck file system operations on cifs mount on
>> latest
On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
> (Please keep me in CC as I'm not subscribed to the users ML.)
>
> Hi,
>
> TL;DR I've been experience stuck file system operations on cifs mount on
> latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
&
(Please keep me in CC as I'm not subscribed to the users ML.)
Hi,
TL;DR I've been experience stuck file system operations on cifs mount on
latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
like to see if other people are seeing similar issue before actually
fi
I see this sort of message while booting and it continues to show up in
dmesg after booting and after XFCE is up and running:
[ 414.569532] atkbd serio0: Unknown key pressed (translated set 2,
code 0xbe on isa0060/serio0). [ 414.569560] atkbd serio0: Use
'setkeycodes e03e ' to make it known. [
Hello everyone,
I am trying to follow the Debian's wiki about Secure Boot:
https://wiki.debian.org/SecureBoot
I've been able to carry out most of this one, from generating modules to
enrolling in the MOK cert, but it doesn't work the signing of the modules
as per the steps.
The only irregular sc
On Sun, Mar 26, 2023 at 11:33 PM Ram Ramesh wrote:
> Hi Ramesh,
>
> this might help. The bug is fixed with kernel 6.0.2-1
>
> https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1
>
> All the best to you
> Eike
>
> Elke,
>
> Thanks. v6.1 is available on bullseye-backports. I ins
Hi Ramesh,
this might help. The bug is fixed with kernel 6.0.2-1
https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1
All the best to you
Eike
Elke,
Thanks. v6.1 is available on bullseye-backports. I installed it and the
trouble is gone now.
BTW, does non-free firmware t
. It seem to go through all steps and reach
> the end but seem to get stuck in this endless cycle complaining about
> some blkdev issue. Here are the last lines printed on the console
> that shows the cycle
>
> [OK] Reached target Power-off
> [67652.NN] block device a
my RAID disks are working. No issue as long as it runs.
The only trouble I have is that it refuses to reboot/shutdown/poweroff.
It seem to go through all steps and reach the end but seem to get stuck
in this endless cycle complaining about some blkdev issue. Here are the
last lines printed on
On May 29, 2022, at 2:30 PM, Nusrath Moin wrote:
Whenever i login after installing debian on my imac early 2006 it shows
"debian gnu/linux comes with absolutely no warranty, to the extent
permitted by applicable law"
That message is normal when you log in to a terminal. I think OSx showed
On May 29, 2022, at 2:30 PM, Nusrath Moin wrote:
>
>
>Whenever i login after installing debian on my imac early 2006 it shows
>"debian gnu/linux comes with absolutely no warranty, to the extent permitted
>by applicable law" on some command screen and i am stuck what
Nusrath Moin wrote:
> Whenever i login after installing debian on my imac early 2006 it shows
> "debian gnu/linux comes with absolutely no warranty, to the extent
> permitted by applicable law" on some command screen and i am stuck what
> should i do please tell me i am una
Whenever i login after installing debian on my imac early 2006 it shows
"debian gnu/linux comes with absolutely no warranty, to the extent
permitted by applicable law" on some command screen and i am stuck what
should i do please tell me i am unable to use my imac
Le 11/11/2021 à 17:55, Erwan David a écrit :
Le 11/11/2021 à 06:16, David Wright a écrit :
A workaround that might shorten the wait, but only if you're confident
that there aren't processes that need that long to complete, is to edit
the line DefaultTimeoutStopSec=90s in /etc/systemd/system.
Le 11/11/2021 à 06:16, David Wright a écrit :
On Wed 10 Nov 2021 at 22:18:07 (+0100), Erwan David wrote:
Le 10/11/2021 à 20:01, Tixy a écrit :
On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
Since some time, I always have to wait 1 min 30 at shut down because
some service does not stop (
On Wed 10 Nov 2021 at 22:18:07 (+0100), Erwan David wrote:
> Le 10/11/2021 à 20:01, Tixy a écrit :
> > On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
> > > Since some time, I always have to wait 1 min 30 at shut down because
> > > some service does not stop (for user erwan is said).
> > >
>
On Wed, 10 Nov 2021 22:18:07 +0100
Erwan David wrote:
> Thanks, for me the culprint is 'dconf worker' (I see it being killed
> with a 'timeout error') about 90s after preceding message.
>
> I do not know where it comes from, I have dconf-service installed as
> a dependency of many things, thus
Le 10/11/2021 à 20:01, Tixy a écrit :
On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
Since some time, I always have to wait 1 min 30 at shut down because
some service does not stop (for user erwan is said).
How can I debug this, know which service is blocking the shutdown ?
Assuming you
On Wed, 2021-11-10 at 18:33 +0100, Erwan David wrote:
> Since some time, I always have to wait 1 min 30 at shut down because
> some service does not stop (for user erwan is said).
>
> How can I debug this, know which service is blocking the shutdown ?
Assuming you system is using systemd then lo
On Wed, 10 Nov 2021 18:33:10 +0100
Erwan David wrote:
> Since some time, I always have to wait 1 min 30 at shut down because
> some service does not stop (for user erwan is said).
>
> How can I debug this, know which service is blocking the shutdown ?
1) Check your logs, especially /var/log/sy
Since some time, I always have to wait 1 min 30 at shut down because
some service does not stop (for user erwan is said).
How can I debug this, know which service is blocking the shutdown ?
I just dist-upgraded against testing, and after the upgrade, MPlayer
started to report
> Audio device got stuck!
over and over again (about once or twice a second, I think) during
playback of any file with audio, while not actually producing any
audible sound.
The solution to this turns out
On Wed, Jul 21, 2021 at 03:48:08PM -0500, Michael Morgan wrote:
> I need some help here. I worked in a university and have a linux (debian 9)
> machine with DHCP. For some reason I needed a static IP and two weeks ago
> the university sent someone who helped me set up the static IP. From what I
> s
twork/interfaces".
However, I found that now I cannot update/install packages. "apt update"
stuck at "0% [Waiting for headers]" for a long time and then give the
following message:
Ign:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.us.debia
It's current testing.
And other versions are mentioned in the bug repport
https://bugs.kde.org/show_bug.cgi?id=434145
I am sorry I didn't mention this before but the problem appears only with
Dolphin and Krusader.
It has to be something with Kio I think, because there is no problem when
copying
On Sat, Mar 20, 2021, 8:48 PM komodo wrote:
> Hi,
>
> last two months when I copy multiple files from USB or SD to HDD after the
> first
> file copying stucks.
>
> I don't know if this is some known bug but it's really annoying.
>
Just a thought. I've had reliability problems with USB keys in th
On 21-03-2021 11:32, komodo wrote:
> Hi,
>
> last two months when I copy multiple files from USB or SD to HDD after the
> first
> file copying stucks.
>
> I don't know if this is some known bug but it's really annoying.
>
> I have already reported this problem upstream, but no response.
>
> ht
Hi,
last two months when I copy multiple files from USB or SD to HDD after the first
file copying stucks.
I don't know if this is some known bug but it's really annoying.
I have already reported this problem upstream, but no response.
https://bugs.kde.org/show_bug.cgi?id=434145
So please if so
build this same 4.19. and can not boot cause not loading
> initrd. Correct?
>
> If true is strange because I would not expect to overwrite the current
> image. You sure the build/installed new version is different than the one
> you have?
>
> > Any kernel I compile gets stuc
than the one
you have?
> Any kernel I compile gets stuck on the "loading initial ramdisk"
> stage. It tried it multiple different ways and the result is always
> the same. Any advice on what I can do to find out what's going on,
> would be greatly appreciated
>
d
Tony Fischetti wrote:
> Any kernel I compile gets stuck on the "loading initial ramdisk"
> stage. It tried it multiple different ways and the result is always
> the same. Any advice on what I can do to find out what's going on,
> would be greatly appreciated
>
>
Any kernel I compile gets stuck on the "loading initial ramdisk"
stage. It tried it multiple different ways and the result is always
the same. Any advice on what I can do to find out what's going on,
would be greatly appreciated
More info: I'm using stable. The most recent a
On 2/16/19 5:41 AM, rhkra...@gmail.com wrote:
On Friday, February 15, 2019 10:39:58 PM Peter Ehlert wrote:
I don't really know,
What don't you really know? It would be a lot easier to know what you're
talking about if you put your answer under the relevant question (i.e., not
top posting)
Pa
On Friday, February 15, 2019 10:39:58 PM Peter Ehlert wrote:
> I don't really know,
What don't you really know? It would be a lot easier to know what you're
talking about if you put your answer under the relevant question (i.e., not
top posting)
> it is a net install, draws the current packag
I don't really know, it is a net install, draws the current packages
from the repos... so it must have access. no wire was plunged in and my
wifi adapter needed iwiwifi-7260-17.ucode and asked for it.
The installer seems to Only install needed/desired packages.
for example, I did Not want the "d
On 2/15/2019 11:01 AM, Peter Ehlert wrote:
Buster install on 820 Friday, February 15 2019
on USB #1: firmware-buster-DI-alpha5-amd64-netinst.iso
I also have on USB #2: firmware-9.4.0-amd64-DVD-1.iso
booted with #1, ... It did ask for firmware, I put #2 in and pressed
"continue" and install co
Buster install on 820 Friday, February 15 2019
on USB #1: firmware-buster-DI-alpha5-amd64-netinst.iso
I also have on USB #2: firmware-9.4.0-amd64-DVD-1.iso
booted with #1, ... It did ask for firmware, I put #2 in and pressed
"continue" and install continued and I was able to select my wifi
Hop
On 14/02/19 2:30 AM, deb wrote:
> Thank you Alexander.
>
> I kinda like the idea of pulling the Intel wifi and just going with a
> Think Penguin free software wifi.
>
> https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb
>
>
The one that says: "Debian 7,
On 2/12/2019 3:25 PM, Alexander V. Makartsev wrote:
In response to that painful "(still installing 9.7 ...)".
You can also use these official and unofficial at the same time images
to install Debian. [1]
As a last resort you can disassemble laptop and physically remove Intel
WiFi NIC before ins
On 12.02.2019 3:46, deb wrote:
>
> Thanks ~everyone:
>
> Do I gather correctly that Brian is the resident, sarcastic,
> cranky-pants herein?
>
> I stopped reading his replies to folks.
>
>
> anyways:
>
> > A suggestion, especially when installing on unfamiliar hardware, is
> to download the fi
On Mon 11 Feb 2019 at 17:46:19 (-0500), deb wrote:
> [ Peter wrote: ]
> > A suggestion, especially when installing on unfamiliar hardware, is
> to download the firmware archive for your platform and unpack it into
> a directory named firmware
>
> I hear you on this @Peter^
>
> I guess I'm kinda w
On Mon 11 Feb 2019 at 17:46:19 -0500, deb wrote:
> Do I gather correctly that Brian is the resident, sarcastic, cranky-pants
> herein?
Flatterer.
--
Brian.
deb, on 2019-02-11 :
> Do I gather correctly that Brian is the resident, sarcastic,
> cranky-pants herein?
>
> I stopped reading his replies to folks.
Well, I prefer to make no assumptions about people just by
looking on the content of two emails. After all the first
intervention from Brian has m
Thanks ~everyone:
Do I gather correctly that Brian is the resident, sarcastic,
cranky-pants herein?
I stopped reading his replies to folks.
anyways:
> A suggestion, especially when installing on unfamiliar hardware, is
to download the firmware archive for your platform and unpack it i
the last time I had such a problem (Buster net install using wifi) I
bookmarked this
https://wiki.debian.org/Firmware#Firmware_during_the_installation
I believe restarting the installer (from USB) with a second USB inserted
with the firmware solved it... needed packages were found and used.
s
On Mon 11 Feb 2019 at 14:01:06 -0600, David Wright wrote:
> Are you sure about 8625, rather than 8265?
Well-spotted.
https://packages.debian.org/stretch/firmware-iwlwifi
--
Brian.
On Mon 11 Feb 2019 at 20:42:10 +0100, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
I believe you have not.
https://packages.debian.org/sid/all/firmware-misc-nonfree/filelist
--
Brian.
On Mon 11 Feb 2019 at 13:33:39 (-0500), deb wrote:
>
> Hello folks:
>
> When I hit the networking section on a fresh install of 9.6 (full
> install .ISO, not live),
>
> I'm told to insert a USB of these non-free bits.
>
> iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode,
> iwlwifi-8625-24.ucode,
On 2/11/19 8:42 PM, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
>
> $ sudo apt install firmware-misc-nonfree
Whoopsie, one should read "firmware-iwlwifi".
Anyway, the iwlwifi-8625-22.ucode alone should d
Good Day,
Usually this shouldn't be an issue, but due to the nature of
the recent vulnerability in the package installer APT, any
Debian ISO up to 9.6 should be trashed and replaced by 9.7 or
greater.
See https://www.debian.org/security/2019/dsa-4371
and https://www.debian.org/News/2019/20190123
On Mon 11 Feb 2019 at 13:33:39 -0500, deb wrote:
[...]
> * wouldn't it be useful for the installer to Also say what exact hardware it
> is, that is requiring various bits & pieces?
As far as I can see, you haven't given which hardware you are using either.
--
Brian.
Hello folks:
When I hit the networking section on a fresh install of 9.6 (full
install .ISO, not live),
I'm told to insert a USB of these non-free bits.
iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode, iwlwifi-8625-24.ucode,
iwlwifi-8625-23.ucode, iwlwifi-8625-22.ucode
The Problem is -
On 2018-08-17, wrote:
>
> I fear I can't help you with that -- but I "decorated" your mail subject
> a bit for others to find it.
The subject was garnished for me. I saw:
[radeon]] *ERROR* atombios stuck in loop
from Tom Arnall or (or maybe tom arnall, or e.e. cummi
I keep getting the following error when my machine boots:
[radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting
the system finally comes up, after a delay of several minutes.
I'm running Debian Stretch on a Lenovo T400. Previous to the system
upgrade to Stretch, I ran J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Aug 16, 2018 at 08:32:47PM -0700, tom arnall wrote:
Hi, Tom --
> I keep getting the following error when my machine boots:
>
>[radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting
>
> the system finally
On 2018-06-04 12:20 AM, Gary Dale wrote:
I'm running buster on an AMD64 system. I do an apt full-upgrade each
night but tonight it's getting stuck. It seems to be building the
initramfs image but having trouble with memtest86+. These are the last
6 lines that it displays then
On 2018-06-04 12:20 AM, Gary Dale wrote:
I'm running buster on an AMD64 system. I do an apt full-upgrade each
night but tonight it's getting stuck. It seems to be building the
initramfs image but having trouble with memtest86+. These are the last
6 lines that it displays then
I'm running buster on an AMD64 system. I do an apt full-upgrade each
night but tonight it's getting stuck. It seems to be building the
initramfs image but having trouble with memtest86+. These are the last 6
lines that it displays then stops. The terminal window isn't frozen -
On Wed, May 30, 2018 at 5:47 PM, Andy Smith wrote:
> Hello,
>
> On Wed, May 30, 2018 at 05:39:58PM -0500, Charles Zeitler wrote:
>> sudo dpkg --dry-run -r initramfs-tools
>> dpkg: dependency problems prevent removal of initramfs-tools:
>> linux-image-4.9.0-6-amd64 depends on initramfs-tools (>=
>
On Wed 30 May 2018 at 09:24:44 (-0500), Charles Zeitler wrote:
> recently synaptic pulled in initramfs-tools, as a dependency.
>
> it froze before fully configured, and i killed apt.
> now I get the message to do "sudo dpkg --configure -a"
> whenever i use apt/synaptic.
>
> when I try "sudo dpkg
Hello,
On Wed, May 30, 2018 at 05:39:58PM -0500, Charles Zeitler wrote:
> sudo dpkg --dry-run -r initramfs-tools
> dpkg: dependency problems prevent removal of initramfs-tools:
> linux-image-4.9.0-6-amd64 depends on initramfs-tools (>=
> 0.120+deb8u2) | linux-initramfs-tool; however:
To be hones
thanks.
On Wed, May 30, 2018 at 5:26 PM, Andy Smith wrote:
> Hi Charles,
>
> On Wed, May 30, 2018 at 09:24:44AM -0500, Charles Zeitler wrote:
>> it froze before fully configured, and i killed apt.
>> now I get the message to do "sudo dpkg --configure -a"
>> whenever i use apt/synaptic.
>>
>> when
Hi Charles,
On Wed, May 30, 2018 at 09:24:44AM -0500, Charles Zeitler wrote:
> it froze before fully configured, and i killed apt.
> now I get the message to do "sudo dpkg --configure -a"
> whenever i use apt/synaptic.
>
> when I try "sudo dpkg --configure -a", however, it also freezes before
> f
recently synaptic pulled in initramfs-tools, as a dependency.
it froze before fully configured, and i killed apt.
now I get the message to do "sudo dpkg --configure -a"
whenever i use apt/synaptic.
when I try "sudo dpkg --configure -a", however, it also freezes before
finishing configuration.
is
On 4/30/2018 5:00 PM, john doe wrote:
Hi Alan,
On 4/30/2018 2:54 PM, Alan Tu wrote:
John, I do enjoy giving back by documenting and reporting bugs.
:)
Is there some way, at least theoretically, that you know of to get the
text installer to record the output and the responses it think its
r
Hi Alan,
On 4/30/2018 2:54 PM, Alan Tu wrote:
John, I do enjoy giving back by documenting and reporting bugs.
:)
Is there some way, at least theoretically, that you know of to get the
text installer to record the output and the responses it think its
receiving? There's going to be an issue
John, I do enjoy giving back by documenting and reporting bugs.
Is there some way, at least theoretically, that you know of to get the
text installer to record the output and the responses it think its
receiving? There's going to be an issue if the media is read-only and
it can't write files, that
On 4/30/2018 12:01 PM, Alan Tu wrote:
Thanks John for confirming how things are supposed to work, that helps
because it narrows things down and I don't need to wonder what is the
correct way. In MIPS it turns out choices 10 11 is the default.
Problem averted/bypassed.
We're not going to solve it
Thanks John for confirming how things are supposed to work, that helps
because it narrows things down and I don't need to wonder what is the
correct way. In MIPS it turns out choices 10 11 is the default.
Problem averted/bypassed.
We're not going to solve it here, but its still weird. Entering 10
On 4/30/2018 3:00 AM, Alan Tu wrote:
Hi, I'm playing with Debian 9.4 stretch on other architectures via the
QEMU emulator (eventually for security research.) I can't figure out
how to handle the numerical software selection menu in the _text_
installer.
I managed to install Debian x86 inside QEM
Hi, I'm playing with Debian 9.4 stretch on other architectures via the
QEMU emulator (eventually for security research.) I can't figure out
how to handle the numerical software selection menu in the _text_
installer.
I managed to install Debian x86 inside QEMU, using the newt installer.
However, I
Thank you for the advice,
tv.deb...@googlemail.com writes:
> On 28/01/2018 20:25, to...@tuxteam.de wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Sun, Jan 28, 2018 at 02:04:54PM +, Daniel Nemenyi wrote:
>>> Dear all,
>>>
&g
On 28/01/2018 20:25, to...@tuxteam.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jan 28, 2018 at 02:04:54PM +, Daniel Nemenyi wrote:
Dear all,
My laptop has for the second time got stuck on boot, and a seemingly
random number of hard reboots has been necessary to get it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jan 28, 2018 at 02:04:54PM +, Daniel Nemenyi wrote:
> Dear all,
>
> My laptop has for the second time got stuck on boot, and a seemingly
> random number of hard reboots has been necessary to get it running. This
> obvio
Dear all,
My laptop has for the second time got stuck on boot, and a seemingly
random number of hard reboots has been necessary to get it running. This
obviously worries me. I'm running Debian Stretch with full disk
encryption and, after grub, this is what happens:
WARNING: Failed to conne
Stretch eventually.
Best regards
Tomaž
Details from the crash yesterday with linux-image-3.16.0-5-amd64
(3.16.51-3+deb8u1):
Excerpt from /var/log/syslog:
BUG: soft lockup - CPU#3 stuck for 22s! [Xorg:1175]
Modules linked in: usb_storage sha256_ssse3 sha256_generic ecb cbc
algif_skciphe
On Sat, 30 Dec 2017 11:47:23 +0100
Alex ARNAUD wrote:
> Hello all,
>
> I'm helping a user to figure out an issue. On her syslog file I could
> find:
> > BUG: soft lockup - CPU#0 stuck for 22s!
>
>
> - Package version of firmware-amd-graphics: 20161130-3~b
Alex ARNAUD wrote:
> Her configuration is that one:
> - Debian Jessie 8.10
>
> - Kernel : Linux colossus 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3
> (2017-12-13) x86_64 GNU/Linux
> - Kernel package: linux-image-amd64 version "3.16+63"
>
> - Xorg version: 1.16.4
> - Package version of xserver-xorg-c
Hello all,
I'm helping a user to figure out an issue. On her syslog file I could find:
BUG: soft lockup - CPU#0 stuck for 22s!
And the following stack trace:
Stack:
Dec 28 14:34:09 colossus kernel: [946492.108011] a041af86
880429a20728 a04a801d 0001
D
I have a python service which issues the foll. command via a subprocess
call:
RUNLEVEL=1 apt-get install
This package, as part of it's installation, issues a systemctl status smb
command which is getting stuck forever. The reason for giving RUNLEVEL=1 is
to prevent nginx (a dependency o
On 04/04/2017 09:10 PM, Charlie Kravetz wrote:
On my dual video Lenovo thinkpad T520, I had this same issue. I deleted
all the nvidia video stuff, then installed the intel I965 video files.
Rebooting allowed the system to come and set the correct resolution.
Then the backgrounds worked correctly.
>ii xfce4 4.10.1 all Meta-package for the Xfce
>Lightwe
>
>
>Currently, the desktop wallpaper is improperly tiled and stuck:
>
>1. The default Debian 8 wallpaper appears (1024x768) in the upper left
>portion of the my 1920x1080 monitor, and portions
Architecture Description
+++-==---=
ii xfce4 4.10.1 all Meta-package for the Xfce
Lightwe
Currently, the desktop wallpaper is improperly tiled and stuck:
1. The default Debian 8 wallpaper appears
adeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
kernel: [ 22.631947] [drm:atom_execute_table_locked [radeon]]
*ERROR* atombios stuck executing CB32 (len 62, WS 0, PS 0) @ 0xCB4E
kernel: [ 27.636246] [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than
Hi,
Thank you for an answer.
Got my problem solved. It was due to priorities for apt. Had the line
"stable" in the priority file, while wheezy has moved to oldstable.
2015-09-30 1:42 GMT+03:00 Stephen Allen :
> On Tue, Sep 29, 2015 at 05:31:29PM +0300, Roman wrote:
> > Hei guys,
> >
> > Seems l
On Tue, Sep 29, 2015 at 05:31:29PM +0300, Roman wrote:
> Hei guys,
>
> Seems like I need your help.
> Can't go much more further...
>
> Reading package lists... Done
> W: There is no public key available for the following key IDs:
> 7638D0442B90D010
> W: There is no public key available for the f
Hei guys,
Seems like I need your help.
Can't go much more further...
Reading package lists... Done
W: There is no public key available for the following key IDs:
7638D0442B90D010
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available fo
On 7/21/2015 5:04 PM, Michael Bonert wrote:
I solved the problem! I was reading the Network Manager how to -- that
is found here: https://wiki.debian.org/NetworkManager
This is what I did:
**
# vi /etc/NetworkManager/NetworkManager.conf
---
I solved the problem! I was reading the Network Manager how to -- that
is found here: https://wiki.debian.org/NetworkManager
This is what I did:
**
# vi /etc/NetworkManager/NetworkManager.conf
-IT WAS
[ifupdown]
managed=false
-
I had the wireless (AirPort) working on my MacBook Pro 8.1 with a
dual boot MacOS/Debian setup without any difficulty for a couple of years.
A couple of days ago, I decided to try MacOS to configure a new modem,
as the wired connection in Debian would just show "connecting"... and
sit there. I ver
1 - 100 of 674 matches
Mail list logo
