On Sun 02 Jan 2022 at 20:49:12 (-0600), David Wright wrote:
> On Sat 18 Dec 2021 at 11:08:37 (-0500), Greg Wooledge wrote:
> > Today I rebooted my machine for the first time in quite a while, after
> > the kernel update that was released along with Debian 11.2.
>
> Mine's a new installation. I've
On Sat 18 Dec 2021 at 11:08:37 (-0500), Greg Wooledge wrote:
> Today I rebooted my machine for the first time in quite a while, after
> the kernel update that was released along with Debian 11.2.
Mine's a new installation. I've run buster from an external drive
for a while, but have recently
On Sun, 19 Dec 2021, Greg Wooledge wrote:
On Sun, Dec 19, 2021 at 07:19:40AM +, Tim Woodall wrote:
Check if the kernel log jumps from 1/1/70 to today as it boots. That
would point to the RTC being bad when the kernel first starts.
Not sure which log I'd need to look at for this
On 18/12/2021 16:08, Greg Wooledge wrote:
Today I rebooted my machine for the first time in quite a while, after
the kernel update that was released along with Debian 11.2.
When it reached the GRUB screen, I pressed Enter, and nothing happened
as far as I could see. I was initially worried
Looks like the fix is this:
# If you need to disable
# gfxpayload=keep on your system, just add this line (uncommented) to
# /etc/default/grub:
#
# GRUB_GFXPAYLOAD_LINUX=text
So, try just adding the above, then run "update-grub" to activate the change.
The problem seems to be some GPU cards have
On Sun, Dec 19, 2021 at 02:17:17PM -, Curt wrote:
> Did we see /etc/default/grub? Could this resolution bug lead to a
> resolution via a new resolution for the New Year?
>
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/480159
>
> 11 years old, but still extant.
I've used GRUB
On Sun, Dec 19, 2021 at 07:19:40AM +, Tim Woodall wrote:
> Check if the kernel log jumps from 1/1/70 to today as it boots. That
> would point to the RTC being bad when the kernel first starts.
Not sure which log I'd need to look at for this information. dmesg only
reports time in relative
On 2021-12-18, Greg Wooledge wrote:
> On Sat, Dec 18, 2021 at 11:42:23PM +, James Dutton wrote:
>> Disk looks OK to me.
>> Next, check no USB devices are connected while it boots.
>> Disable "quiet" boot mode, so you can see all the boot up messages.
>> This will give you an idea where it is
On Sun, Dec 19, 2021 at 12:54:04PM +, James Dutton wrote:
> One question, does it boot faster if you just press enter at the grub
> menu, and don't wait for the counter?
On Sat, Dec 18, 2021 at 11:08:37AM -0500, Greg Wooledge wrote:
[...]
> When it reached the GRUB screen, I pressed Enter,
On Sat, 18 Dec 2021 at 23:54, Greg Wooledge wrote:
> The symptoms I experienced were BEFORE the kernel was executed. During
> GRUB itself. While sitting at the GRUB menu.
>
> Once the kernel started running, everything was within normal expectations.
>
Sounds like a race condition or infinite
On Sat 18 Dec 2021 at 11:08:37 -0500, Greg Wooledge wrote:
> Today I rebooted my machine for the first time in quite a while, after
> the kernel update that was released along with Debian 11.2.
>
> When it reached the GRUB screen, I pressed Enter, and nothing happened
> as far as I could see. I
On Sat, 18 Dec 2021, Dan Ritter wrote:
Greg Wooledge wrote:
Today I rebooted my machine for the first time in quite a while, after
the kernel update that was released along with Debian 11.2.
...
Eventually, after a minute or two, the system booted. Everything is
working normally now,
Greg Wooledge composed on 2021-12-18 17:39 (UTC-0500):
> === START OF INFORMATION SECTION ===
> Model Family: Toshiba 3.5" DT01ACA... Desktop HDD
> Device Model: TOSHIBA DT01ACA100
I have the same model in a little used SFF Dell GX745 test box:
https://paste.debian.net/1224017/
On Sat, Dec 18, 2021 at 11:42:23PM +, James Dutton wrote:
> Disk looks OK to me.
> Next, check no USB devices are connected while it boots.
> Disable "quiet" boot mode, so you can see all the boot up messages.
> This will give you an idea where it is going slow.
"quiet" is a kernel parameter.
Disk looks OK to me.
Next, check no USB devices are connected while it boots.
Disable "quiet" boot mode, so you can see all the boot up messages.
This will give you an idea where it is going slow.
On Sat, 18 Dec 2021 at 22:39, Greg Wooledge wrote:
>
> On Sat, Dec 18, 2021 at 10:23:54PM +,
Greg Wooledge wrote:
> Today I rebooted my machine for the first time in quite a while, after
> the kernel update that was released along with Debian 11.2.
...
> Eventually, after a minute or two, the system booted. Everything is
> working normally now, post-GRUB.
I upgraded three machines
On Sat, Dec 18, 2021 at 10:23:54PM +, James Dutton wrote:
> Hi,
>
> This is most likely a failing disk.
> Please post the output of:
> smartctl -a /dev/sda
>
> or whatever your disk device name is, if not sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-10-amd64] (local build)
Hi,
This is most likely a failing disk.
Please post the output of:
smartctl -a /dev/sda
or whatever your disk device name is, if not sda
Kind Regards
James
On Sat, 18 Dec 2021 at 16:09, Greg Wooledge wrote:
>
> Today I rebooted my machine for the first time in quite a while, after
> the
Today I rebooted my machine for the first time in quite a while, after
the kernel update that was released along with Debian 11.2.
When it reached the GRUB screen, I pressed Enter, and nothing happened
as far as I could see. I was initially worried that it had stopped
seeing my USB keyboard (a
19 matches
Mail list logo
