On Ma, 08 iun 21, 12:05:21, Thom Castermans wrote:
>
> - Installed non-free firmware (used the unofficial image [1]) during
> installation and installed the intel-microcode package after installation
> in an attempt to fix the error displayed in [4] ("[Firmware Bug]:
> TSC_DEADLINE d
[Wanderer wrote:]
> It really does sound like he's been doing multiple reinstalls, and even
> probably reinstalled buster after the latest failed install of testing (snip)
This is correct: I reinstalled Bullseye a few times and am currently using a
fresh Buster install (with non-free firmware).
Hi.
On Tue, Jun 08, 2021 at 04:44:35PM +0500, Alexander V. Makartsev wrote:
> > How can I debug this problem? My suspicion is that this has to do with the
> > kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>
> The way I would approach this problem is by making
On Tue, Jun 08, 2021 at 04:44:35PM +0500, Alexander V. Makartsev wrote:
> There was an intention from a systemd developers to make persistent logs the
> default, but I'm unsure if that change made it into Debian already.
Unless something changed that I'm unaware of, new installs of bullseye
should
On Tue, Jun 08, 2021 at 07:43:30AM -0400, The Wanderer wrote:
> On 2021-06-08 at 07:27, Greg Wooledge wrote:
> > The first and most obvious thing you should try is booting the buster
> > kernel, and seeing whether the problem still occurs. This will let
> > you know whether the problem is in the k
On 08.06.2021 15:05, Thom Castermans wrote:
Dear Debian users,
Recently I installed Debian on an ASUS UX501J laptop. Debian stable (Buster)
works flawlessly (I'm using that now), but when I tried to upgrade to testing,
things started going wrong. I would get random kernel panics and other errors
On 2021-06-08 at 07:27, Greg Wooledge wrote:
> On Tue, Jun 08, 2021 at 12:05:21PM +0200, Thom Castermans wrote:
>
>> How can I debug this problem? My suspicion is that this has to do with the
>> kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>>
>> Things I have tried
On Tue, Jun 08, 2021 at 12:05:21PM +0200, Thom Castermans wrote:
> How can I debug this problem? My suspicion is that this has to do with the
> kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>
> Things I have tried so far:
> - Ran smartctl test on the SSD: no issues
On 06/23/2017 08:00 AM, Ron Benincasa wrote:
Colleagues,
I can't figure out what I've done wrong. I did a fresh install of
Stretch, with backports enabled, and Gnome desktop, using the
default kernel as highlighted. When I reboot, I get a kernel panic.
I can SOMETIMES boot in by entering reco
On Sun, Feb 02, 2014 at 02:23:38PM -0700, Rick Macdonald wrote:
> read-only without rebooting. I was seeing journal errors (ext3
> filesystem). Then I saw a BIOS message saying a hard drive failure
> was imminent.
>
Had a hard drive with many bad blocks on it, and run debian(Woody IIRC)
on it as
Marty wrote:
> It's a udev quirl. You need the device file console in /dev. I usually
copy
> the device manually after cloning a disk.
=BEGIN SNIPPET=
# ls -l /dev/console
crw--- 1 root tty 5, 1 Aug 18 09:32 /dev/console
# echo 'testing write' >/dev/console
testing write
# cat -
Joel Barker wrote:
I have been using two hard drives, an old IDE mounted at / and a brand new
SCSI mounted on /home. A few days ago the IDE drive died. Fortunately, I had
just copied all the data over to the SCSI drive (/dev/sda1). But when I try
to boot off the SCSI drive, I get the following
A long time ago, in a galaxy far, far way, someone said...
> On Wed, Jan 26, 2000 at 10:55:22PM -0600, Phil Brutsche wrote:
> > 1) Upgrade from hamm to potato (you might need to go to slink first). The
> >bug fixes along are worth it.
>
> Could I use apt to do this? Is there somewhere a howt
I had some odd behavior after installing a 2.2.x kernel on my slink machine.
I investigated installing the potato packages that were recommended for the
new kernel version, but decided that a the benefits of the 2.2.x kernels over
2.0.x kernels were not worth the trouble. As to upgrading that
On Thu, 27 Jan 2000, Werner Reisberger wrote:
> [...]
>
> I tried to compile 2.2.14 but it failed with many error messages in
> console.c. Isn't it possible to run hamm with newer kernels. Last time
> I read on this list Debian is kernel independent (someone asked why his
> potato uses a 2.0.39 k
On Wed, Jan 26, 2000 at 10:55:22PM -0600, Phil Brutsche wrote:
> 1) Upgrade from hamm to potato (you might need to go to slink first). The
>bug fixes along are worth it.
Could I use apt to do this? Is there somewhere a howto for doing this?
> 2) Use a newer kernel. 2.2.9 is about 6 months o
A long time ago, in a galaxy far, far way, someone said...
> My system crashes from time to time but I cannot reproduce the crashes.
> It may run 2 month without any problems and suddenly a daily cronjob or a
> simple shell command seems to cause the crash. Here is what I could write
> today from
On Thu, 23 Dec 1999, aphro wrote:
> Does it always happen when you run iptraf? it could be a network driver
> problem or a network card hardware problem.
Nope... The machine can just be sitting there lying "idle" (as idle as a
linux box should get that is...)
> a good way to test the board/cpu/
Does it always happen when you run iptraf? it could be a network driver
problem or a network card hardware problem.
a good way to test the board/cpu/hdd and i/o subsystems that i have found
is running 10x copies of [EMAIL PROTECTED] at the same time for 24-48 hours, if
the machine lasts 24 hours
> Saturday night, while I was testing my tape backup procedure, I did a full
> restore into an unused partition. I tried an rm -r on that partition, and
> got a kernel panic, locking my system. Happened again later that night.
>
> Earlier today, while demonstrating the slowness and cpu usage of
20 matches
Mail list logo
