[ISSUE] ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[ISSUE] ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[pudiva]

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]

New issue by pudiva on void-packages repository

https://github.com/void-linux/void-packages/issues/53144

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.57_1 x86_64 GenuineIntel notuptodate rrFFF

### Package(s) Affected

linux6.6-6.6.59_1 linux6.6-6.6.61_1 

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

System boots normally.

### Actual behaviour

System freezes forever showing Lenovo logo after selecting kernel on grub. I got no error messages or any other useful output. System boots fine with the older 6.6.57_1 kernel I still have installed, but not with 6.6.59_1 or 6.6.61_1.

### Steps to reproduce

On a ThinkPad P14s Gen 2i:

1. update linux from 6.6.57_1 to 6.6.59_1 or 6.6.61_1
2. reboot
3. see the system freeze after grub

Re: ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 199 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/53144#issuecomment-2485771095

Comment:
do you have a separate boot partition? is it full?

Re: ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[pudiva]

[-- Attachment #1: Type: text/plain, Size: 280 bytes --]

New comment by pudiva on void-packages repository

https://github.com/void-linux/void-packages/issues/53144#issuecomment-2486193373

Comment:
@classabbyamp wow... maybe it is? what do you think?

```
$ df -h
...
/dev/nvme0n1p2                  448M  364M   56M  87% /boot
...
```

Re: ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[pudiva]

[-- Attachment #1: Type: text/plain, Size: 246 bytes --]

New comment by pudiva on void-packages repository

https://github.com/void-linux/void-packages/issues/53144#issuecomment-2486196489

Comment:
@classabbyamp I just realised that there's no `initramfs-6.6.*.img` for the versions I just reported...

Re: ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 244 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/53144#issuecomment-2486198338

Comment:
ok try running [vkpurge](https://man.voidlinux.org/vkpurge) then `xbps-reconfigure -f linux6.6`

Re: [ISSUE] [CLOSED] ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[pudiva]

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

Closed issue by pudiva on void-packages repository

https://github.com/void-linux/void-packages/issues/53144

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.57_1 x86_64 GenuineIntel notuptodate rrFFF

### Package(s) Affected

linux6.6-6.6.59_1 linux6.6-6.6.61_1 

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

System boots normally.

### Actual behaviour

System freezes forever showing Lenovo logo after selecting kernel on grub. I got no error messages or any other useful output. System boots fine with the older 6.6.57_1 kernel I still have installed, but not with 6.6.59_1 or 6.6.61_1.

### Steps to reproduce

On a ThinkPad P14s Gen 2i:

1. update linux from 6.6.57_1 to 6.6.59_1 or 6.6.61_1
2. reboot
3. see the system freeze after grub

Re: ThinkPad P14s Gen 2i doesn't boot after updating linux from 6.6.57_1 to 6.6.59_1

[pudiva]

[-- Attachment #1: Type: text/plain, Size: 337 bytes --]

New comment by pudiva on void-packages repository

https://github.com/void-linux/void-packages/issues/53144#issuecomment-2486229975

Comment:
@classabbyamp yes it was disk space and removing old stuff resolved the issue. it'd be nice if the update hard failed in that case, instead of reporting success... anyway thank you so much! 💖