Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: GoinEasy9 on 2021/11/07, 15:37:13
-
Hello folks
Today after the DU, my install brings me through grub and then gives mdadm:no arrays found in config file or automatically, then drops me to a initramfs shell.
Booting to the previous kernel allows for a normal boot.
new kernel 5.15.1-1
working kernel 5.14.15-2
I'm attaching a screen pic of the error screen.
Edit: No errors occurred after updating my lxqt install, new kernel boots fine.
TIA
Tom
-
That looks like, the kernel is not installed propper.
dpkg -l | egrep -i "x-image|x-head"
df -h
-
Thanks towo
root@siduction-kde:/home/goineasy9# dpkg -l | egrep -i "x-image|x-head"
ii linux-headers-5.14.15-2-siduction-amd64 5.14-15.1 amd64 Header files for Linux 5.14.15-2-siduction-amd64
ii linux-headers-5.15.1-1-siduction-amd64 5.15-1 amd64 Header files for Linux 5.15.1-1-siduction-amd64
ii linux-headers-siduction-amd64 5.15-1 amd64 Linux headers for siduction on 64-bit PCs
rc linux-image-5.14.10-1-siduction-amd64 5.14-10 amd64 Linux 5.14 for 64-bit PCs
rc linux-image-5.14.13-1-siduction-amd64 5.14-13 amd64 Linux 5.14 for 64-bit PCs
rc linux-image-5.14.14-1-siduction-amd64 5.14-14 amd64 Linux 5.14 for 64-bit PCs
ii linux-image-5.14.15-2-siduction-amd64 5.14-15.1 amd64 Linux 5.14 for 64-bit PCs
rc linux-image-5.14.5-3-siduction-amd64 5.14-5.2 amd64 Linux 5.14 for 64-bit PCs
rc linux-image-5.14.6-1-siduction-amd64 5.14-7 amd64 Linux 5.14 for 64-bit PCs
rc linux-image-5.14.7-1-siduction-amd64 5.14-7.1 amd64 Linux 5.14 for 64-bit PCs
rc linux-image-5.14.9-1-siduction-amd64 5.14-9 amd64 Linux 5.14 for 64-bit PCs
ii linux-image-5.15.1-1-siduction-amd64 5.15-1 amd64 Linux 5.15 for 64-bit PCs
ii linux-image-siduction-amd64 5.15-1 amd64 Linux image for siduction on 64-bit PCs
root@siduction-kde:/home/goineasy9# df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 387M 1.5M 386M 1% /run
/dev/sda1 49G 9.3G 38G 20% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.9G 4.0K 1.9G 1% /tmp
/dev/sda3 401G 327M 380G 1% /home
tmpfs 387M 72K 387M 1% /run/user/1000
Appreciate your help.
-
There i can't find any issue.
ls -al /boot
-
Thanks again
root@siduction-kde:/home/goineasy9# ls -al /boot
total 98556
drwxr-xr-x 3 root root 4096 Nov 7 08:45 .
drwxr-xr-x 20 root root 4096 Nov 7 08:42 ..
-rw-r--r-- 1 root root 222293 Oct 28 12:57 config-5.14.15-2-siduction-amd64
-rw-r--r-- 1 root root 223480 Nov 6 09:57 config-5.15.1-1-siduction-amd64
drwxr-xr-x 5 root root 4096 Nov 7 08:45 grub
-rw-r--r-- 1 root root 37115107 Oct 31 10:11 initrd.img-5.14.15-2-siduction-amd64
-rw-r--r-- 1 root root 37237059 Nov 7 08:43 initrd.img-5.15.1-1-siduction-amd64
-rw-r--r-- 1 root root 182704 Aug 15 2019 memtest86+.bin
-rw-r--r-- 1 root root 184884 Aug 15 2019 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 5317883 Oct 28 12:57 System.map-5.14.15-2-siduction-amd64
-rw-r--r-- 1 root root 5339427 Nov 6 09:57 System.map-5.15.1-1-siduction-amd64
-rw-r--r-- 1 root root 7514912 Oct 28 12:57 vmlinuz-5.14.15-2-siduction-amd64
-rw-r--r-- 1 root root 7548416 Nov 6 09:57 vmlinuz-5.15.1-1-siduction-amd64
-
Looks all good, i don't see any reason, why that kernel should not boot.
-
Thanks towo
I think I'll try removing, then, reinstalling it and see what happens.
I'll post again afterwards.
-
Hello again
Removing the kernel, then, reinstalling it led to the same error as before. So, I'll wait till a new kernel is ready, and, see if the same thing happens, Very strange, but it is the first of the 5.15 kernels.
Thanks for your help towo
-
Here's a thread that describes the issue and some possible fixes (if a new kernel doesn't resolve it):
https://unix.stackexchange.com/questions/559140/debian-buster-uuid-does-not-exist-dropping-to-shell-problem
-
Thanks dibl
I played with the advice from the forum post. I couldn't fix or even have a different result come up. So, hopefully the next kernel will fix the problem, since it seems I'm the only one experiencing it.
Thanks again, obviously your Google Fu is a lot letter than mine.
-
Hello again.
It seems that 5.15.1-3 is giving me the same "can't find root" error. I'm waiting to see what happens when Tumbleweed releases a 5.15 kernel. Maybe I can do some comparisons. at least my 5.14 kernel still works.
Tom
-
Your error message where the UUID is not recognized makes me suspect something is not quite right on your system. Have you recently added any drives, or changed partition layout, or anything like that? If you are using the UUIDs in /etc/fstab, which I highly recommend, then you might want to compare the UUIDs in fstab with the UUID in the grub config file and make sure that it matches the boot partition. Do you have a swap partition -- your grub couldn't seem to recognize the UUID for resume, which would be the swap partition.
-
Hi dibl
Thanks for the ideas.
The machine has been running siduction for many years, hasn't changed a bit. It has a rack mount for the HDD. I have 4 disks that I can easily slip in, one with windows 10, one with siduction, one with Leap and one with Tumbleweed. anyway ...
The UUID in fstab, for root, is the same as the one showing in the error. Works with 5.14, errors out with 5.15. I have all the normal partitions /root, /home & swap.
I'm going to see if I can find something in the logs, Eventually the answer will turn up.
Tom
-
Hi GoinEasy9,
just to stand by you, my little server has the same problem with kernel 5.15, you're not alone :-)
It's an old installation, maybe 8 years, but dist-upgraded up to date and running fine with Kernel 5.14.16-2. Siduction is installed on the SanDisk SSD /dev/sda. There is no firmware update available. The three HDD are newer.
root@turing:~# inxi -D
Drives: Local Storage: total: 5.52 TiB used: 1 TiB (18.2%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 59.63 GiB
ID-2: /dev/sdb vendor: Seagate model: ST2000VN004-2E4164 size: 1.82 TiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB
ID-4: /dev/sdd vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB
I hope it is an error in the Kernel and will be fixed in a new version. But I have the vague suspicion that something was dropped and will never come back :'(
Roland
-
Have you more than one distro installed on your PC?
-
no, siduction is the one and only.
The SSD is for system, the HDDs are first for multimedia of another linux TV box (nfs share), second for web content (four apache virtual hosts) and nfs shares and third for backup of the second one.
-
can you please give us some information about your system
inxi -F
-
root@turing:/var/log/apt# inxi -F
System: Host: turing Kernel: 5.14.16-2-siduction-amd64 x86_64 bits: 64 Console: pty pts/0
Distro: siduction 12.2.0 Riders on the Storm - kde - (201212092131)
Machine: Type: Desktop Mobo: ASUSTeK model: AT3IONT-I v: Rev X.0x serial: MF70A5G05800167 BIOS: American Megatrends v: 0306
date: 02/01/2010
CPU: Info: Dual Core model: Intel Atom 330 bits: 64 type: MT MCP cache: L2: 512 KiB
Speed: 1600 MHz min/max: N/A Core speeds (MHz): 1: 1600 2: 1600 3: 1600 4: 1600
Graphics: Device-1: Conexant Systems CX23885 PCI Video and Audio Decoder driver: cx23885 v: 0.0.4
Device-2: NVIDIA C79 [ION] driver: N/A
Display: server: X.org 1.20.11 driver: loaded: vesa tty: 325x37
Message: Advanced graphics data unavailable in console for root.
Audio: Device-1: NVIDIA MCP79 High Definition Audio driver: snd_hda_intel
Device-2: Conexant Systems CX23885 PCI Video and Audio Decoder driver: cx23885
Sound Server-1: ALSA v: k5.14.16-2-siduction-amd64 running: yes
Sound Server-2: PipeWire v: 0.3.40 running: yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 48:5b:39:b5:b3:1f
Drives: Local Storage: total: 5.52 TiB used: 1 TiB (18.2%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 59.63 GiB
ID-2: /dev/sdb vendor: Seagate model: ST2000VN004-2E4164 size: 1.82 TiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB
ID-4: /dev/sdd vendor: Western Digital model: WD20EFRX-68EUZN0 size: 1.82 TiB
Partition: ID-1: / size: 56.59 GiB used: 15.54 GiB (27.5%) fs: ext4 dev: /dev/sda2
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 52.0 C mobo: 38.0 C
Fan Speeds (RPM): cpu: 0 psu: 0 case-1: 1323
Info: Processes: 179 Uptime: 6h 15m Memory: 3.16 GiB used: 899.4 MiB (27.8%) Init: systemd runlevel: 5 Shell: Bash
inxi: 3.3.07
-
Just for comparison sake.
$ inxi -F
System: Host: siduction-kde Kernel: 5.14.15-2-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.23.3
Distro: siduction 21.2.0 Farewell - kde - (202109171658)
Machine: Type: Desktop Mobo: ASUSTeK model: M4N82 DELUXE v: Rev 2.00 serial: <superuser required>
BIOS: American Megatrends v: 0703 date: 05/27/2009
CPU: Info: Quad Core model: AMD Phenom II X4 955 bits: 64 type: MCP cache: L2: 2 MiB
Speed: 3200 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 3200 2: 800 3: 2100 4: 3200
Graphics: Device-1: NVIDIA G92 [GeForce 9800 GT] driver: nouveau v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa
resolution: 1680x1050~60Hz
OpenGL: renderer: NV92 v: 3.3 Mesa 21.2.5
Audio: Device-1: NVIDIA MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio driver: snd_hda_intel
Device-2: JMTek LLC. USB PnP Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
Device-3: JMTek LLC. USB PnP Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
Sound Server-1: ALSA v: k5.14.15-2-siduction-amd64 running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Sound Server-3: PipeWire v: 0.3.40 running: yes
Network: Device-1: NVIDIA MCP77 Ethernet driver: forcedeth
IF: enp0s10 state: up speed: 100 Mbps duplex: full mac: 00:26:18:32:33:d9
Drives: Local Storage: total: 465.76 GiB used: 10.35 GiB (2.2%)
ID-1: /dev/sda vendor: Seagate model: ST3500320AS size: 465.76 GiB
Partition: ID-1: / size: 48.91 GiB used: 10.01 GiB (20.5%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 400.29 GiB used: 339.8 MiB (0.1%) fs: ext4 dev: /dev/sda3
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 49.0 C mobo: 28.0 C gpu: nouveau temp: 51.0 C
Fan Speeds (RPM): cpu: 3013 case-1: 2115 case-2: 878
Info: Processes: 201 Uptime: 11m Memory: 3.78 GiB used: 1.13 GiB (30.0%) Shell: Bash inxi: 3.3.07
-
and why seems the new kernel broken for your system ?
no problems here
inxi -SCG
System: Host: siductionbox Kernel: 5.15.2-1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.23.3
Distro: Debian GNU/Linux bookworm/sid
CPU: Info: Quad Core model: Intel Core i5-3570 bits: 64 type: MCP cache: L2: 6 MiB
Speed: 1730 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1730 2: 1612 3: 1714 4: 1719
Graphics: Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics driver: i915 v: kernel
Device-2: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 495.44
Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia resolution: 1920x1200~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 495.44
-
have look at the photograph of GoinEasy9's first post. UUID doesn't come up and we are dropped into busybox. On my desktop PC the new kernel is running w/o issues but not on my old server
-
Greetings from an old Siduction user, since a few years
a Gentoo compiling nerd.
My guess is that the new linux-5.15.x has lost compatibility with old hardware. I tried extensibly to boot with the new kernel. My method to put the old .config into the new directory /usr/src/linux-5.15 and create a new one with:
make oldconfig
didn't work. I tried four times to figure out a new .config. Until I had the idea to grab the Towo Siduction kernel:
---
ral@maci:/boot$ vdir vmlinuz-5.15*
-rw-r--r-- 1 root root 7555296 Nov 12 16:01 vmlinuz-5.15.2-1-siduction-amd64
-rw-r--r-- 1 root root 7133824 Nov 13 13:57 vmlinuz-5.15.2-1.11.144
-rw-r--r-- 1 root root 7267776 Nov 13 20:46 vmlinuz-5.15.2-2.129.453
-rw-r--r-- 1 root root 7249344 Nov 14 16:59 vmlinuz-5.15.2-3.145.491
-rw-r--r-- 1 root root 7317856 Nov 15 14:41 vmlinuz-5.15.2-4.860.2435
---
It isn't a wrongly configured kernel source. Towos kernel boots with all the same error, something with:
ata1 error
I could make a photo from the boot screen before the computer reboots - if you are interested. I do have a Debian-Testing installation for the rescue (having Gentoo this might be necessary sometimes). There the Towo Siduction kernel also plays the same error. Something with the new kernel-5.15 and NVIDIA-MCP7x ???
# inxi -F
System: Host: maci Kernel: 5.14.18-1.162.5494 x86_64 bits: 64 Desktop: MATE 1.24.3 Distro: Gentoo Base System release 2.7
Machine: Type: Laptop System: Apple product: Macmini3,1 v: 1.0 serial: YM9340659G6
Mobo: Apple model: Mac-F22C86C8 serial: N/A UEFI: Apple v: MM31.88Z.00AD.B00.0907171535 date: 07/17/09
CPU: Info: Dual Core model: Intel Core2 Duo P8700 bits: 64 type: MCP cache: L2: 3 MiB
Speed: 1596 MHz min/max: 1596/1862 MHz Core speeds (MHz): 1: 1596 2: 1795
Graphics: Device-1: NVIDIA C79 [GeForce 9400] driver: nouveau v: kernel
Display: server: X.Org 1.20.13 driver: loaded: nouveau resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A
Audio: Device-1: NVIDIA MCP79 High Definition Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.14.18-1.162.5494 running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Network: Device-1: NVIDIA MCP79 Ethernet driver: forcedeth
IF: enp0s10 state: down mac: 00:26:b0:d8:53:d4
Device-2: Broadcom BCM4321 802.11a/b/g/n driver: b43-pci-bridge
IF-ID-1: wlan0 state: up mac: 00:26:08:ed:96:26
Bluetooth: Device-1: Apple Bluetooth USB Host Controller type: USB driver: N/A
Report: This feature requires one of these tools: hciconfig/bt-adapter
Drives: Local Storage: total: 465.76 GiB used: 137.89 GiB (29.6%)
ID-1: /dev/sda vendor: Toshiba model: MQ01ABF050 size: 465.76 GiB
Partition: ID-1: / size: 27.44 GiB used: 21.12 GiB (77.0%) fs: ext4 dev: /dev/sda3
ID-2: /home size: 93.99 GiB used: 90.54 GiB (96.3%) fs: ext4 dev: /dev/dm-0
Swap: ID-1: swap-1 type: partition size: 1024 MiB used: 302.5 MiB (29.5%) dev: /dev/sda5
ID-2: swap-2 type: partition size: 2 GiB used: 0 KiB (0.0%) dev: /dev/sda9
Sensors: Missing: Required tool sensors not installed. Check --recommends
Info: Processes: 154 Uptime: 5h 38m Memory: 3.59 GiB used: 1.69 GiB (46.9%) Shell: Bash inxi: 3.3.08 I do have some higher CPU speed available, but I don't want my 12y old system to heat.
-
My oldest available system is:
System: Host: Thinkpad Kernel: 5.16.0-rc1-siduction-amd64 x86_64 bits: 64 Desktop: N/A
Distro: siduction 21.2.0 Farewell - kde - (202109161307)
Machine: Type: Laptop System: LENOVO product: 4238AC6 v: ThinkPad T420 serial: <superuser required>
Mobo: LENOVO model: 4238AC6 serial: <superuser required> UEFI: LENOVO v: 83ET82WW (1.52 ) date: 06/04/2018
CPU: Info: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP cache: L2: 3 MiB
Speed: 878 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 878 2: 2148 3: 862 4: 881
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
Display: server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 21.2.5
Info: Processes: 197 Uptime: 46m Memory: 7.65 Gi that B used: 1.09 GiB (14.2%) Shell: Bash inxi: 3.3.07So on all my systems, i can't confirm that issue.
Maybe you all with that problem can boot with "quiet" removed from kernel command, maybe we see, what's going wrong.
-
I just came up with a solution for my vmlinuz-5.15.2 by adding:
irqpoll
rootdelay=7
like this boot options:
# cat /proc/cmdline
initrd=\icoreduo.img irqpoll tsx=on noacpi random.trust_cpu=1 ipv6.disable=1 root=/dev/sda3 systemd.unit=default.target hibernate=no rootdelay=7 init=/sbin/systemd rootfstype=ext4 systemd.show_status=1 systemd.log_level=7 acpi_backlight=vendor modeset.nouveau=1 vt.handoff=1 (running without a regular initrd but with only a core2 firmware update image)
This I found out, because I wanted to make a photo of the ata1 error. Since Linux-4.4 sometimes I get an irq 20 error with the hint to use irqpoll as option. For this error never had consequences I never used irqpoll. But to not disturb the error analyzis in this forum I introduced the "irqpoll" option now. This helped. It seems to me that the linux-5.15 kernel is somewhat more sensible and just needs an extra care in options.
The Towo siduction kernel could start my debian-testing partition and my self compiled kernel boots the Gentoo partition just perfectly by adding these two options.
-
hopefully I catched the first error. After that he reduces the speed to 1.5Gbps followed by the same error and finally got the errors from the first posting.
ralul's solution didn't work here
[ This attachment cannot be displayed inline in 'Print Page' view ]
-
@vindeliker,
weird it is, that my two additional options don't work for you, because my error seemed to be the same as yours! If you are unsure the changed boot options take effect, then test them inserting into a previous boot entry and try to see them in: cat /proc/cmdline
... and I would wait some days, there are a record of 940 error corrections in the stableque on the way to 5.15.3
-
Hi
I tried rootdelay=10 without success when error first appeared. Here's the pic with quiet removed.
-
Can you purge the package mdadm? Maybe it lowering the noise in your messages.
-
Here is an ancient dinosaur, which seems to have no problem with the new kernel, just FYI:
System: Kernel: 5.15.2-2-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.23.3
Distro: siduction 13.2.1 December - kde - (201401272125)
Machine: Type: Portable System: 6 product: E v: 6 serial: <filter>
Mobo: N/A model: �g@+�� G serial: <filter> BIOS: Intel
v: CF94510J.15A.0028.2006.1213.1629 date: 12/13/2006
CPU: Info: Dual Core model: Intel Pentium D bits: 64 type: MCP cache: L2: 1024 KiB
Speed: 2795 MHz min/max: N/A Core speeds (MHz): 1: 2795 2: 2795
Graphics: Device-1: Intel 82945G/GZ Integrated Graphics driver: i915 v: kernel
Device-2: Internext Compression iTVC16 Video Decoder driver: ivtv v: 1.4.3
Display: x11 server: X.Org 1.20.11 driver: loaded: intel
resolution: 1360x768~60Hz
OpenGL: renderer: Mesa DRI Intel 945G v: 1.4 Mesa 21.2.5
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel
Device-2: Internext Compression iTVC16 Video Decoder driver: ivtv
Sound Server-1: ALSA v: k5.15.2-2-siduction-amd64 running: yes
Sound Server-2: PipeWire v: 0.3.40 running: yes
Network: Device-1: Intel PRO/100 VE Network driver: e100
IF: eth1 state: down mac: <filter>
Device-2: Belkin F7D2102 802.11n N300 Micro Wireless Adapter v3000 [Realtek
RTL8192CU]
type: USB driver: rtl8192cu
IF: wlan1 state: up mac: <filter>
RAID: Hardware-1: Intel 82801GR/GDH (ICH7R/ICH7DH) SATA Controller [RAID mode]
driver: ahci
Drives: Local Storage: total: 232.89 GiB used: 13.8 GiB (5.9%)
ID-1: /dev/sda vendor: Hitachi model: HDT725025VLA380 size: 232.89 GiB
Partition: ID-1: / size: 21.07 GiB used: 13.74 GiB (65.2%) fs: ext4 dev: /dev/sda1
Swap: ID-1: swap-1 type: partition size: 2 GiB used: 1.8 MiB (0.1%) dev: /dev/sda2
Sensors: Message: No sensor data found. Is lm-sensors configured?
Info: Processes: 171 Uptime: 9m Memory: 1.93 GiB used: 1.18 GiB (61.1%) Shell: Bash
inxi: 3.3.07
-
The failing systems are
- older systems
- have nvidia mcp7xxx chips
- not having the same distro (me having Gentoo stable)
- not having the same hard disks
I guess some kernel fixes are coming, like perhaps:
rtc-mcp795-add-spi-id-table.patch
--- a/drivers/rtc/rtc-mcp795.c
+++ b/drivers/rtc/rtc-mcp795.c
@@ -430,12 +430,19 @@ static const struct of_device_id mcp795_of_match[] = {
MODULE_DEVICE_TABLE(of, mcp795_of_match);
#endif
+static const struct spi_device_id mcp795_spi_ids[] = {
+ { .name = "mcp795" },
+ { }
+};
+MODULE_DEVICE_TABLE(spi, mcp795_spi_ids);
+
static struct spi_driver mcp795_driver = {
.driver = {
.name = "rtc-mcp795",
.of_match_table = of_match_ptr(mcp795_of_match),
},
.probe = mcp795_probe,
+ .id_table = mcp795_spi_ids,
};
module_spi_driver(mcp795_driver);
-- in the stableque for 5.15.3
But with this real time clock patch, I am not expert enough to know if it has to do with the NVIDIA MCP7xxx chips. But the timeout errors point direction timings ....
-
Hi
I purged mdadm removed quiet and this is what came up.
-
Hello
OK, just did an update, got a new kernel, 5.15.2-2, boot worked without error. I guess we received some towo magic.
I'm curious, do we know what caused it?
I'm leaving mdadm purged, I have no raid devices that need monitoring.
Thanks
-
If the new kernel is working, the problem was upstream, since the new kernel has only patch-5.15.3-rc2 added.
-
Off topic but I posting it here due to tthe latest posting:
@ towo purely out of couriosity:
I assumed the siduction kernels are based on the latest stable kernel, which currently is 5.15.
Now seeing in the above posting that the newest kernel has the 5.15-rc2 patch it looks like the current siduction kernel is 5.14 plus selected 5.15 patches? So at which point do you switch to the next kernel number? Or what does it mean?
So is the general idea to use the pre-stabel kernel as the basis for siduction kernels and then add step by step the RC patches of the latest released kernel and see how it works out for siduction users? And then the numbering does not refere to the released kernel but only to the use of some RC-patches of said kernel?
This is for my (and maybe other's) couriosity only ...
All working well here and thanks again.
-
You should open your eyes.
I sayed the kernel has patch 5.15.3-rc2 in, not 5.15-rc2.
-
Ok, thanks, right you are. Now understood.
-
Auf Kernel.org jetzt gerade eingestellt:
stable: 5.15.3 2021-11-18
Bestimmt identisch mit Towos _rc2 Linux kernel.
-
Hi
Strangest thing, on this same computer ... during this mornings full-upgrade I got a kernel panic. I had to do a cold boot to recover, and, during dpkg --reconfigure -a, I got another kernel panic. I'm not sure, but I think it was trying to rebuild intramfs when it happened. dpkg --reconfigure -a after the second panic came up with nothing. Upon reboot, the new 5.15.4 kernel booted just fine and there doesn't seem to be any residual problems from the kernel panic.
DU's on the new machine and the old lxqt laptop went without incident.
BTW - Thunderbird just released it's 5.15 kernel, and, it blew up on this machine also. Instead of just dropping me to busybox, it just left me with some colored artifacts.