On Wed 28 Jun 2023 at 23:32:56 (-0400), hlyg wrote: > my general impression of bookworm for i386 is slow > > i suppose support for i386 becomes poor as its user base shrink
I'm guessing that new releases use more room as they increase in complexity and functionality. This can result in more swapping, for example. With bullseye, I ceased trying to run Firefox on an i386 with 500MB RAM. > even shutdown is slow, i see it painfully show " Transport endpoint is > not connected" So is it waiting for a timeout to expire? > my usb extension line might cause trouble, it connect to back of pc > case at one end, at the other end is usb hub, it's handy because it > turns one usb socket to four sockets, and it works most of time, but > sometime it can cause trouble, i notice data transfer becomes slow > thru it > > msg in last line is in red, such thing as device name has been edited > for privacy (wlx123), usb wifi adapter is connected to usb hub Do you have other things plugged into the hub with mounted filesystems? If so, what sort of filesystems? > Jun 28 20:10:14 debian ifdown[752]: For info, please visit > https://www.isc.org/software/dhcp/ > Jun 28 20:10:14 debian ifdown[752]: Listening on LPF/wlx123... > Jun 28 20:10:14 debian ifdown[752]: Sending on LPF/wlx123... > Jun 28 20:10:14 debian ifdown[752]: Sending on Socket/fallback > Jun 28 20:10:14 debian ifdown[752]: DHCPRELEASE of 192.168.43.89 on > wlx123 to 192.168.43.208 port 67 > Jun 28 20:10:14 debian systemd-journald[824]: Failed to send READY=1 > notification message: Transport endpoint is not connected Do you only see this message at closedown? Do you have any filesystems mounted via the network? Cheers, David.
