From je-vv at e.email Sun Jan 15 00:10:59 2023 From: je-vv at e.email (Javier) Date: Sat, 14 Jan 2023 17:10:59 -0600 Subject: [artix-general] linux 6.1.4.artix1-1 crashes with usb MediaTek mt7612u, 6.0.12.artix1-1 works just fine Message-ID: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> Hello ! I use "usb MediaTek mt7612u" to get wireless internet connection in some machines. After upgrading linux from 6.0.12 to 6.1.4 and rebooting, though the boxes reboot, as soon as there's traffic linux just crashes and hangs forever. I don't know where to look for the logs of that hang, since I had to revert linux to 6.0.12, the old dmesg logs are worthless, they just show a binary string, where I suppose the crash happens: > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ But the boxes show core dump log. I guess on systemd boxes one could use coredumpctl, but these are Artix with S6 boxes. I've been looking for such crashes on internet, but hadn't found relevant information. BTW, the driver itself seems to load fine: > 2023-01-14 11:42:56.270718990 kern.info: [ 5.324501] usb 4-2: Manufacturer: MediaTek Inc. > 2023-01-14 11:42:56.270722455 kern.info: [ 5.324505] usb 4-2: SerialNumber: 000000000 It's just when traffic is attempted that I guess linux crashes. At any rate, for those using "usb MediaTek mt7612u" wireless devices to get internet connection, the work around is to revert linux to 6.0.12, and to prevent linux to upgrade with: > % 'grep' '^IgnorePkg' /etc/pacman.conf > IgnorePkg = linux linux-docs linux-header If anyone knows how can I grab logs from prior linux crashes when using Artix with S6, please let me know. -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Jan 15 00:29:08 2023 From: je-vv at e.email (Javier) Date: Sat, 14 Jan 2023 17:29:08 -0600 Subject: [artix-general] linux 6.1.4.artix1-1 crashes with usb MediaTek mt7612u, 6.0.12.artix1-1 works just fine In-Reply-To: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> References: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> Message-ID: On 1/14/23 17:10, Javier wrote: > Hello ! > > I use "usb MediaTek mt7612u" to get wireless internet connection in some machines.? After upgrading linux from 6.0.12 to 6.1.4 and rebooting, though the boxes reboot, as soon as there's traffic linux just crashes and hangs forever. > > I don't know where to look for the logs of that hang, since I had to revert linux to 6.0.12, the old dmesg logs are worthless, they just show a binary string, where I suppose the crash happens: > >> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > > But the boxes show core dump log.? I guess on systemd boxes one could use coredumpctl, but these are Artix with S6 boxes.? I've been looking for such crashes on internet, but hadn't found relevant information. > > BTW, the driver itself seems to load fine: > >> 2023-01-14 11:42:56.270718990? kern.info: [??? 5.324501] usb 4-2: Manufacturer: MediaTek Inc. >> 2023-01-14 11:42:56.270722455? kern.info: [??? 5.324505] usb 4-2: SerialNumber: 000000000 > > It's just when traffic is attempted that I guess linux crashes. > > At any rate, for those using "usb MediaTek mt7612u" wireless devices to get internet connection, the work around is to revert linux to 6.0.12, and to prevent linux to upgrade with: > >> % 'grep' '^IgnorePkg' /etc/pacman.conf IgnorePkg?? = linux linux-docs linux-header > > If anyone knows how can I grab logs from prior linux crashes when using Artix with S6, please let me know. BTW, Arch is using 6.1.5 currently, and it seems this bug [1], which is a duplicate of [2] seems closed, and it seems from its last comment, there's a version 5 of a patch that makes things work on [3]. I can't really tell if the current Arch linux 6.1.5.arch2-1 package works fine. I don't have any Arch box from quite some time now, but perhaps it's a matter of waiting for that package changes to reach Artix? Can someone tell? -- Javier [1] https://bugs.archlinux.org/task/77011?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= [2] https://bugs.archlinux.org/task/76922?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&;cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&;changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= [3] https://patchwork.kernel.org/project/linux-wireless/patch/20221230200747.19040-1-nbd%40nbd.name -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From ruben at mrbrklyn.com Sun Jan 15 05:36:58 2023 From: ruben at mrbrklyn.com (Ruben Safir) Date: Sat, 14 Jan 2023 23:36:58 -0500 Subject: [artix-general] update package page In-Reply-To: <20221221211010.52ad93ef@hyperion.xyzzy.xyz> References: <20221213132411.GA7836@www2.mrbrklyn.com> <20221221211010.52ad93ef@hyperion.xyzzy.xyz> Message-ID: <20230115043658.GA14133@www2.mrbrklyn.com> just FWIW I just heard about Artix and was checking out the site for the first time. Wanted to report a few dead links... On the Downloads page: https://torrents.artixlinux.org/torrents.php leads to a 502 https://iso.artixlinux.org/weekly-isos.php leads to a 502 Right pane on Downloads page: https://iso.artixlinux.org/isos.php leads to a 502 -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 From je-vv at e.email Sat Jan 21 00:45:21 2023 From: je-vv at e.email (Javier) Date: Fri, 20 Jan 2023 17:45:21 -0600 Subject: [artix-general] linux 6.1.4.artix1-1 crashes with usb MediaTek mt7612u, 6.0.12.artix1-1 works just fine In-Reply-To: References: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> Message-ID: <337a6225-3e64-10e3-a5a1-68d3c930059d@e.email> On 1/14/23 17:29, Javier wrote: > On 1/14/23 17:10, Javier wrote: >> Hello ! >> >> I use "usb MediaTek mt7612u" to get wireless internet connection in some machines.? After upgrading linux from 6.0.12 to 6.1.4 and rebooting, though the boxes reboot, as soon as there's traffic linux just crashes and hangs forever. >> >> I don't know where to look for the logs of that hang, since I had to revert linux to 6.0.12, the old dmesg logs are worthless, they just show a binary string, where I suppose the crash happens: >> >>> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ >> >> But the boxes show core dump log.? I guess on systemd boxes one could use coredumpctl, but these are Artix with S6 boxes.? I've been looking for such crashes on internet, but hadn't found relevant information. >> >> BTW, the driver itself seems to load fine: >> >>> 2023-01-14 11:42:56.270718990? kern.info: [??? 5.324501] usb 4-2: Manufacturer: MediaTek Inc. >>> 2023-01-14 11:42:56.270722455? kern.info: [??? 5.324505] usb 4-2: SerialNumber: 000000000 >> >> It's just when traffic is attempted that I guess linux crashes. >> >> At any rate, for those using "usb MediaTek mt7612u" wireless devices to get internet connection, the work around is to revert linux to 6.0.12, and to prevent linux to upgrade with: >> >>> % 'grep' '^IgnorePkg' /etc/pacman.conf IgnorePkg?? = linux linux-docs linux-header >> >> If anyone knows how can I grab logs from prior linux crashes when using Artix with S6, please let me know. > > > BTW, Arch is using 6.1.5 currently, and it seems this bug [1], which is a duplicate of [2] seems closed, and it seems from its last comment, there's a version 5 of a patch that makes things work on [3]. > > I can't really tell if the current Arch linux 6.1.5.arch2-1 package works fine.? I don't have any Arch box from quite some time now, but perhaps it's a matter of waiting for that package changes to reach Artix?? Can someone tell? According to last update on [2], the patch was added to "6.1.7.arch1-1", and the bug was closed as fixed, since current Arch linux version is precisely that one. Not sure if Artix actually ports linux from its Arch counterpart, if so, perhaps "6.1.7-artix1-1" com with this issue fixed when available. BTW, I tried current Artix "6.1.6.artix1-1" version of linux, and it's much worse, the box just hangs forever when loading the initrd generated by mkinitcpio. The fallback initrd doesn't help a bit, it also hangs forever while loading. So "6.1.6.artix1-1" linux actually breaks those boxes (though it seems unrelated to the mediatek issue). I'll start a new thread if I find an HP laptop also hanging while loading the generated initrd. So far it seems 6.1.6 generated initrd is broken. Though I can't tell how or why... -- Javier [1] https://bugs.archlinux.org/task/77011?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= [2] https://bugs.archlinux.org/task/76922?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&;cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&;changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= [3] https://patchwork.kernel.org/project/linux-wireless/patch/20221230200747.19040-1-nbd%40nbd.name -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sat Jan 21 00:56:36 2023 From: je-vv at e.email (Javier) Date: Fri, 20 Jan 2023 17:56:36 -0600 Subject: [artix-general] linux 6.1.4.artix1-1 crashes with usb MediaTek mt7612u, 6.0.12.artix1-1 works just fine In-Reply-To: <337a6225-3e64-10e3-a5a1-68d3c930059d@e.email> References: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> <337a6225-3e64-10e3-a5a1-68d3c930059d@e.email> Message-ID: <59a9d897-2d38-3060-bff9-6eeb1c8b05bd@e.email> On 1/20/23 17:45, Javier wrote: > On 1/14/23 17:29, Javier wrote: >> On 1/14/23 17:10, Javier wrote: >>> Hello ! >>> >>> I use "usb MediaTek mt7612u" to get wireless internet connection in some machines.? After upgrading linux from 6.0.12 to 6.1.4 and rebooting, though the boxes reboot, as soon as there's traffic linux just crashes and hangs forever. >>> >>> I don't know where to look for the logs of that hang, since I had to revert linux to 6.0.12, the old dmesg logs are worthless, they just show a binary string, where I suppose the crash happens: >>> >>>> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ >>> >>> But the boxes show core dump log.? I guess on systemd boxes one could use coredumpctl, but these are Artix with S6 boxes.? I've been looking for such crashes on internet, but hadn't found relevant information. >>> >>> BTW, the driver itself seems to load fine: >>> >>>> 2023-01-14 11:42:56.270718990? kern.info: [??? 5.324501] usb 4-2: Manufacturer: MediaTek Inc. >>>> 2023-01-14 11:42:56.270722455? kern.info: [??? 5.324505] usb 4-2: SerialNumber: 000000000 >>> >>> It's just when traffic is attempted that I guess linux crashes. >>> >>> At any rate, for those using "usb MediaTek mt7612u" wireless devices to get internet connection, the work around is to revert linux to 6.0.12, and to prevent linux to upgrade with: >>> >>>> % 'grep' '^IgnorePkg' /etc/pacman.conf IgnorePkg?? = linux linux-docs linux-header >>> >>> If anyone knows how can I grab logs from prior linux crashes when using Artix with S6, please let me know. >> >> >> BTW, Arch is using 6.1.5 currently, and it seems this bug [1], which is a duplicate of [2] seems closed, and it seems from its last comment, there's a version 5 of a patch that makes things work on [3]. >> >> I can't really tell if the current Arch linux 6.1.5.arch2-1 package works fine.? I don't have any Arch box from quite some time now, but perhaps it's a matter of waiting for that package changes to reach Artix?? Can someone tell? > > > According to last update on [2], the patch was added to "6.1.7.arch1-1", and the bug was closed as fixed, since current Arch linux version is precisely that one.? Not sure if Artix actually ports linux from its Arch counterpart, if so, perhaps "6.1.7-artix1-1" com with this issue fixed when available. > > BTW, I tried current Artix "6.1.6.artix1-1" version of linux, and it's much worse, the box just hangs forever when loading the initrd generated by mkinitcpio.? The fallback initrd doesn't help a bit, it also hangs forever while loading.? So "6.1.6.artix1-1" linux actually breaks those boxes (though it seems unrelated to the mediatek issue).? I'll start a new thread if I find an HP laptop also hanging while loading the generated initrd.? So far it seems 6.1.6 generated initrd is broken.? Though I can't tell how or why... The HP laptop does boot, perhaps the "6.1.6.artix1-1" is just an issue for haswell processors, who knows... In the end, those boxes need to wait for "6.1.7.artix1-1" any ways, so we'll see when that linux package becomes available, hoping the MediaTek mt7612u issue would be solved by the patch used on that version by Arch, and hopefully the initrd issue is also gone by then. Linux 6.1 packages by Artix not working on several boxes so far, :( -- Javier [1] https://bugs.archlinux.org/task/77011?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= [2] https://bugs.archlinux.org/task/76922?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&;cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&;changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= [3] https://patchwork.kernel.org/project/linux-wireless/patch/20221230200747.19040-1-nbd%40nbd.name -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From somenxavier at posteo.net Sun Jan 22 15:02:31 2023 From: somenxavier at posteo.net (Xavier B.) Date: Sun, 22 Jan 2023 14:02:31 +0000 Subject: [artix-general] linux 6.1.4.artix1-1 crashes with usb MediaTek mt7612u, 6.0.12.artix1-1 works just fine In-Reply-To: <59a9d897-2d38-3060-bff9-6eeb1c8b05bd@e.email> References: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> <337a6225-3e64-10e3-a5a1-68d3c930059d@e.email> <59a9d897-2d38-3060-bff9-6eeb1c8b05bd@e.email> Message-ID: <20230122150231.9650c596c457c0fc28ca24df@posteo.net> Perhaps you could install linux-hardened meanwhile (now 6.1.7). Regards, Xavier On Fri, 20 Jan 2023 17:56:36 -0600 Javier ha escrit: > On 1/20/23 17:45, Javier wrote: > > On 1/14/23 17:29, Javier wrote: > >> On 1/14/23 17:10, Javier wrote: > >>> Hello ! > >>> > >>> I use "usb MediaTek mt7612u" to get wireless internet connection in some machines.? After upgrading linux from 6.0.12 to 6.1.4 and rebooting, though the boxes reboot, as soon as there's traffic linux just crashes and hangs forever. > >>> > >>> I don't know where to look for the logs of that hang, since I had to revert linux to 6.0.12, the old dmesg logs are worthless, they just show a binary string, where I suppose the crash happens: > >>> > >>>> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > >>> > >>> But the boxes show core dump log.? I guess on systemd boxes one could use coredumpctl, but these are Artix with S6 boxes.? I've been looking for such crashes on internet, but hadn't found relevant information. > >>> > >>> BTW, the driver itself seems to load fine: > >>> > >>>> 2023-01-14 11:42:56.270718990? kern.info: [??? 5.324501] usb 4-2: Manufacturer: MediaTek Inc. > >>>> 2023-01-14 11:42:56.270722455? kern.info: [??? 5.324505] usb 4-2: SerialNumber: 000000000 > >>> > >>> It's just when traffic is attempted that I guess linux crashes. > >>> > >>> At any rate, for those using "usb MediaTek mt7612u" wireless devices to get internet connection, the work around is to revert linux to 6.0.12, and to prevent linux to upgrade with: > >>> > >>>> % 'grep' '^IgnorePkg' /etc/pacman.conf IgnorePkg?? = linux linux-docs linux-header > >>> > >>> If anyone knows how can I grab logs from prior linux crashes when using Artix with S6, please let me know. > >> > >> > >> BTW, Arch is using 6.1.5 currently, and it seems this bug [1], which is a duplicate of [2] seems closed, and it seems from its last comment, there's a version 5 of a patch that makes things work on [3]. > >> > >> I can't really tell if the current Arch linux 6.1.5.arch2-1 package works fine.? I don't have any Arch box from quite some time now, but perhaps it's a matter of waiting for that package changes to reach Artix?? Can someone tell? > > > > > > According to last update on [2], the patch was added to "6.1.7.arch1-1", and the bug was closed as fixed, since current Arch linux version is precisely that one.? Not sure if Artix actually ports linux from its Arch counterpart, if so, perhaps "6.1.7-artix1-1" com with this issue fixed when available. > > > > BTW, I tried current Artix "6.1.6.artix1-1" version of linux, and it's much worse, the box just hangs forever when loading the initrd generated by mkinitcpio.? The fallback initrd doesn't help a bit, it also hangs forever while loading.? So "6.1.6.artix1-1" linux actually breaks those boxes (though it seems unrelated to the mediatek issue).? I'll start a new thread if I find an HP laptop also hanging while loading the generated initrd.? So far it seems 6.1.6 generated initrd is broken.? Though I can't tell how or why... > > The HP laptop does boot, perhaps the "6.1.6.artix1-1" is just an issue for haswell processors, who knows... In the end, those boxes need to wait for "6.1.7.artix1-1" any ways, so we'll see when that linux package becomes available, hoping the MediaTek mt7612u issue would be solved by the patch used on that version by Arch, and hopefully the initrd issue is also gone by then. Linux 6.1 packages by Artix not working on several boxes so far, :( > > > -- > Javier > > > [1] https://bugs.archlinux.org/task/77011?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= > [2] https://bugs.archlinux.org/task/76922?string=linux&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&;cat%5B0%5D=&status%5B0%5D=&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&;changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= > [3] https://patchwork.kernel.org/project/linux-wireless/patch/20221230200747.19040-1-nbd%40nbd.name > > From je-vv at e.email Mon Jan 23 07:25:51 2023 From: je-vv at e.email (Javier) Date: Mon, 23 Jan 2023 00:25:51 -0600 Subject: [artix-general] FYI: Thunderbird 102.7 not able to authenticate to enterprise 0365 (depends on admin actions) Message-ID: https://blog.thunderbird.net/2023/01/important-message-for-microsoft-office-365-enterprise-users It seems it's better to wait for 102.7.1, and see if it works. As 102.7.0 already reached "world", for people connecting to enterprise O365 with TB, it's better to set pacman to ignore that package, until the fix gets available. -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Mon Jan 23 07:26:46 2023 From: je-vv at e.email (Javier) Date: Mon, 23 Jan 2023 00:26:46 -0600 Subject: [artix-general] Thunderbird (world) 102.7 breaks sequoia-octopus-librnp (universe) 1.4.1-2 Message-ID: Hello ! The new 102.7.0-1 thunderbird in "world" breaks sequoia-octopus-librnp in "universe". Not sure if a rebuild of sequoia-octopus-librnp is required, or even worse, a new version for it is required. BTW, I don't see a new tag on [1], neither a related reported issue on [2]. For now, this requires preventing pacman to upgrade thunderbird. At any rate, on boxes trying to authenticate to enterprise O365, that's currently a must. But this is a different issue... Thanks ! -- Javier [1] https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp/-/tags [2] https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp/-/issues -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From cs at rtx.ksac.uk Mon Jan 23 14:45:40 2023 From: cs at rtx.ksac.uk (Colin S) Date: Mon, 23 Jan 2023 13:45:40 +0000 Subject: [artix-general] Thunderbird (world) 102.7 breaks sequoia-octopus-librnp (universe) 1.4.1-2 In-Reply-To: References: Message-ID: <6a1ee6b9-9299-8bd2-d918-73db62de0bbe@rtx.ksac.uk> I build sequoia-octopus-librnp from the git source rather than using the packaged version in Universe. I'm not sure what exactly in 102.7.0-1 caused this recent breakage, but simply rerunning the Sequoia build now failed to compile, so some crate dependency must also have changed. Pulling in the latest git commits and then rebuilding seems to fix things. I imagine it should be fairly straightforward for the maintainer to correct the Universe package. On 23/01/2023 06:26, Javier wrote: > Hello ! > > The new 102.7.0-1 thunderbird in "world" breaks sequoia-octopus-librnp > in "universe".? Not sure if a rebuild of sequoia-octopus-librnp is > required, or even worse, a new version for it is required.? BTW, I don't > see a new tag on [1], neither a related reported issue on [2].? For now, > this requires preventing pacman to upgrade thunderbird.? At any rate, on > boxes trying to authenticate to enterprise O365, that's currently a > must.? But this is a different issue... > > Thanks ! > > > From artist at artixlinux.org Mon Jan 23 18:13:00 2023 From: artist at artixlinux.org (artist) Date: Mon, 23 Jan 2023 18:13:00 +0100 Subject: [artix-general] Thunderbird (world) 102.7 breaks sequoia-octopus-librnp (universe) 1.4.1-2 In-Reply-To: <6a1ee6b9-9299-8bd2-d918-73db62de0bbe@rtx.ksac.uk> References: <6a1ee6b9-9299-8bd2-d918-73db62de0bbe@rtx.ksac.uk> Message-ID: Package sequoia-octopus-librnp-1.4.1-4-x86_64.pkg.tar.zst is now in universe to be tested; it does not contain newer commits than the previous version. artist On a bended knee, or systemd, you will never live free On 1/23/23 14:45, Colin S wrote: > I build sequoia-octopus-librnp from the git source rather than using > the packaged version in Universe. I'm not sure what exactly in > 102.7.0-1 caused this recent breakage, but simply rerunning the > Sequoia build now failed to compile, so some crate dependency must > also have changed. Pulling in the latest git commits and then > rebuilding seems to fix things. I imagine it should be fairly > straightforward for the maintainer to correct the Universe package. > > On 23/01/2023 06:26, Javier wrote: >> Hello ! >> >> The new 102.7.0-1 thunderbird in "world" breaks >> sequoia-octopus-librnp in "universe".? Not sure if a rebuild of >> sequoia-octopus-librnp is required, or even worse, a new version for >> it is required.? BTW, I don't see a new tag on [1], neither a related >> reported issue on [2].? For now, this requires preventing pacman to >> upgrade thunderbird.? At any rate, on boxes trying to authenticate to >> enterprise O365, that's currently a must.? But this is a different >> issue... >> >> Thanks ! >> >> >> From cs at rtx.ksac.uk Mon Jan 23 19:05:25 2023 From: cs at rtx.ksac.uk (Colin S) Date: Mon, 23 Jan 2023 18:05:25 +0000 Subject: [artix-general] Thunderbird (world) 102.7 breaks sequoia-octopus-librnp (universe) 1.4.1-2 In-Reply-To: References: <6a1ee6b9-9299-8bd2-d918-73db62de0bbe@rtx.ksac.uk> Message-ID: <5bc166fd-4043-b5b8-b25e-bd2b5a2fc40a@rtx.ksac.uk> Having now had a more thorough look through the commit history, it appears to have been this one that I needed to pull in order to get past the compilation error I was hitting. https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp/-/commit/b4fcbf558f8f0f07a3b753b802d15a2803a7db5b On 23/01/2023 17:13, artist wrote: > Package sequoia-octopus-librnp-1.4.1-4-x86_64.pkg.tar.zst is now in > universe to be tested; it does not contain newer commits than the > previous version. > > artist > > On a bended knee, or systemd, you will never live free > > On 1/23/23 14:45, Colin S wrote: >> I build sequoia-octopus-librnp from the git source rather than using >> the packaged version in Universe. I'm not sure what exactly in >> 102.7.0-1 caused this recent breakage, but simply rerunning the >> Sequoia build now failed to compile, so some crate dependency must >> also have changed. Pulling in the latest git commits and then >> rebuilding seems to fix things. I imagine it should be fairly >> straightforward for the maintainer to correct the Universe package. >> >> On 23/01/2023 06:26, Javier wrote: >>> Hello ! >>> >>> The new 102.7.0-1 thunderbird in "world" breaks >>> sequoia-octopus-librnp in "universe".? Not sure if a rebuild of >>> sequoia-octopus-librnp is required, or even worse, a new version for >>> it is required.? BTW, I don't see a new tag on [1], neither a related >>> reported issue on [2].? For now, this requires preventing pacman to >>> upgrade thunderbird.? At any rate, on boxes trying to authenticate to >>> enterprise O365, that's currently a must.? But this is a different >>> issue... >>> >>> Thanks ! >>> >>> >>> > From je-vv at e.email Mon Jan 23 21:01:21 2023 From: je-vv at e.email (Javier) Date: Mon, 23 Jan 2023 14:01:21 -0600 Subject: [artix-general] Thunderbird (world) 102.7 breaks sequoia-octopus-librnp (universe) 1.4.1-2 In-Reply-To: References: <6a1ee6b9-9299-8bd2-d918-73db62de0bbe@rtx.ksac.uk> Message-ID: <5bf3b1be-d1e2-b954-988d-53c56ac0bf4b@e.email> On 1/23/23 11:13, artist wrote: > Package sequoia-octopus-librnp-1.4.1-4-x86_64.pkg.tar.zst is now in universe to be tested; it does not contain newer commits than the previous version. > > artist Hello Artist, I already tested TB 102.7 with octopus 1.4.1-4, and unfortunately, octopus still remains broken with TB 102.7. It's working fine with TB 102.6.1-1. It seems it's upstream then. I'll look if a new issue on gitlab was filed, and otherwise, I'll report a new one... Thanks a lot ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From artist at artixlinux.org Tue Jan 24 22:26:07 2023 From: artist at artixlinux.org (artist) Date: Tue, 24 Jan 2023 22:26:07 +0100 Subject: [artix-general] FYI: Thunderbird 102.7 not able to authenticate to enterprise 0365 (depends on admin actions) In-Reply-To: References: Message-ID: <5b1c9c8c-1331-1a9a-2466-6b633fbe7476@artixlinux.org> Package betterbird-102.7.1-1-x86_64.pkg.tar.zst is now in the omniverse repo, including the MS OAuth2 fix. I'll test the fix myself tomorrow. artist On a bended knee, or systemd, you will never live free On 1/23/23 07:25, Javier wrote: > https://blog.thunderbird.net/2023/01/important-message-for-microsoft-office-365-enterprise-users > > > It seems it's better to wait for 102.7.1, and see if it works.? As > 102.7.0 already reached "world", for people connecting to enterprise > O365 with TB, it's better to set pacman to ignore that package, until > the fix gets available. > > > From je-vv at e.email Wed Jan 25 01:21:29 2023 From: je-vv at e.email (Javier) Date: Tue, 24 Jan 2023 18:21:29 -0600 Subject: [artix-general] FYI: Thunderbird 102.7 not able to authenticate to enterprise 0365 (depends on admin actions) In-Reply-To: <5b1c9c8c-1331-1a9a-2466-6b633fbe7476@artixlinux.org> References: <5b1c9c8c-1331-1a9a-2466-6b633fbe7476@artixlinux.org> Message-ID: <8fb37075-7052-aeca-47e2-44e77e0fc935@e.email> On 1/24/23 15:26, artist wrote: > Package betterbird-102.7.1-1-x86_64.pkg.tar.zst is now in the omniverse repo, including the MS OAuth2 fix. I'll test the fix myself tomorrow. > > artist Hopefully your testing is successful, though these 2 reports: [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1812090 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1810760 Make me believe the issue is still there, even 102.7.1 was supposed to fix the issue. So [2] was reopened, :( The last comment on [1] before being marked as a duplicate of [2], is that beta should have fixed the issue. It seems we have to wait a bit longer, so far [2] is still not under fixed state... -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From artist at artixlinux.org Thu Jan 26 12:17:59 2023 From: artist at artixlinux.org (artist) Date: Thu, 26 Jan 2023 12:17:59 +0100 Subject: [artix-general] FYI: Thunderbird 102.7 not able to authenticate to enterprise 0365 (depends on admin actions) In-Reply-To: <8fb37075-7052-aeca-47e2-44e77e0fc935@e.email> References: <5b1c9c8c-1331-1a9a-2466-6b633fbe7476@artixlinux.org> <8fb37075-7052-aeca-47e2-44e77e0fc935@e.email> Message-ID: <4db21f33-b1a3-17d2-60f5-c58bc0b99b01@artixlinux.org> betterbird-102.7.1-2-x86_64.pkg.tar.zst is now?in omniverse and seems to work - feedback is welcome artist -- On 1/25/23 01:21, Javier wrote: > On 1/24/23 15:26, artist wrote: >> Package betterbird-102.7.1-1-x86_64.pkg.tar.zst is now in the >> omniverse repo, including the MS OAuth2 fix. I'll test the fix myself >> tomorrow. >> >> artist > > Hopefully your testing is successful, though these 2 reports: > > [1]? https://bugzilla.mozilla.org/show_bug.cgi?id=1812090 > [2]? https://bugzilla.mozilla.org/show_bug.cgi?id=1810760 > > Make me believe the issue is still there, even 102.7.1 was supposed to > fix the issue.? So [2] was reopened, :(? The last comment on [1] > before being marked as a duplicate of [2], is that beta should have > fixed the issue.? It seems we have to wait a bit longer, so far [2] is > still not under fixed state... > > From je-vv at e.email Mon Jan 30 01:24:28 2023 From: je-vv at e.email (Javier) Date: Sun, 29 Jan 2023 18:24:28 -0600 Subject: [artix-general] Thunderbird (world) 102.7 breaks sequoia-octopus-librnp (universe) 1.4.1-2 In-Reply-To: <5bf3b1be-d1e2-b954-988d-53c56ac0bf4b@e.email> References: <6a1ee6b9-9299-8bd2-d918-73db62de0bbe@rtx.ksac.uk> <5bf3b1be-d1e2-b954-988d-53c56ac0bf4b@e.email> Message-ID: <89f8cf7c-0da7-418d-2d07-bf83bc039d3a@e.email> On 1/23/23 14:01, Javier wrote: > Hello Artist, I already tested TB 102.7 with octopus 1.4.1-4, and unfortunately, octopus still remains broken with TB 102.7.? It's working fine with TB 102.6.1-1.? It seems it's upstream then.? I'll look if a new issue on gitlab was filed, and otherwise, I'll report a new one... > > Thanks a lot ! FYI: https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp/-/issues/83 -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Tue Jan 31 05:14:24 2023 From: je-vv at e.email (Javier) Date: Mon, 30 Jan 2023 22:14:24 -0600 Subject: [artix-general] linux 6.1.4.artix1-1 crashes with usb MediaTek mt7612u, 6.0.12.artix1-1 works just fine In-Reply-To: <20230122150231.9650c596c457c0fc28ca24df@posteo.net> References: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> <337a6225-3e64-10e3-a5a1-68d3c930059d@e.email> <59a9d897-2d38-3060-bff9-6eeb1c8b05bd@e.email> <20230122150231.9650c596c457c0fc28ca24df@posteo.net> Message-ID: <7a511956-8265-27fb-400b-e9592a1bc0c9@e.email> On 1/22/23 08:02, Xavier B. wrote: > Perhaps you could install linux-hardened meanwhile (now 6.1.7). > > Regards, > Xavier I've never used linux-hardened, it would be interesting to compare linux source package (PKGBUILD, configs, patches) vs. linux-hardened. One interesting difference is that linux is part of "system", while linux-hardened is part of "world". It's like "core" vs. "extra" on arch. That said, linux 6.1.8.artix1-1 is already part of "system", and it came out without the issue. Not sure if that linux version came out already fixed, or if the patch used on 6.1.7 by arch got propagated. The good news is that the artix linux 6.1.8.artix1-1 package works just fine... Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From somenxavier at posteo.net Tue Jan 31 15:50:51 2023 From: somenxavier at posteo.net (Xavier B.) Date: Tue, 31 Jan 2023 14:50:51 +0000 Subject: [artix-general] linux 6.1.4.artix1-1 crashes with usb MediaTek mt7612u, 6.0.12.artix1-1 works just fine In-Reply-To: <7a511956-8265-27fb-400b-e9592a1bc0c9@e.email> References: <7fa85cc8-5ac0-bb2b-5120-a8a007412b7c@e.email> <337a6225-3e64-10e3-a5a1-68d3c930059d@e.email> <59a9d897-2d38-3060-bff9-6eeb1c8b05bd@e.email> <20230122150231.9650c596c457c0fc28ca24df@posteo.net> <7a511956-8265-27fb-400b-e9592a1bc0c9@e.email> Message-ID: <20230131155051.ad611be3a0c2fa2a233c5d9e@posteo.net> Just a suggestion meanwhile. For not having waiting time. In Arch wiki in Security page is a good point to start to see the enhancements. I ignore the source comparison. Just a user here. Regards, Xavier On Mon, 30 Jan 2023 22:14:24 -0600 Javier ha escrit: > On 1/22/23 08:02, Xavier B. wrote: > > Perhaps you could install linux-hardened meanwhile (now 6.1.7). > > > > Regards, > > Xavier > > I've never used linux-hardened, it would be interesting to compare linux source package (PKGBUILD, configs, patches) vs. linux-hardened. One interesting difference is that linux is part of "system", while linux-hardened is part of "world". It's like "core" vs. "extra" on arch. > > That said, linux 6.1.8.artix1-1 is already part of "system", and it came out without the issue. Not sure if that linux version came out already fixed, or if the patch used on 6.1.7 by arch got propagated. The good news is that the artix linux 6.1.8.artix1-1 package works just fine... > > Thanks ! > > -- > Javier >