From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Core126 udevd problem Date: Wed, 02 Jan 2019 17:24:01 +0000 Message-ID: <25C0AEF1-41E8-4DB2-AA39-DE30F09B7BD0@ipfire.org> In-Reply-To: <20190102171335.GA23458@tarvainen.info> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3550174105094356347==" List-Id: --===============3550174105094356347== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I think you might be running into this: https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D4c76d08b2a1ef5a= c9ff8b546c0d887e342adec1c The framebuffer driver is no longer blacklisted and that causes the kernel to= crash on my VIA devices. You can mount the hard drive in a different computer and edit the file manual= ly if that is an option for you. Best, -Michael > On 2 Jan 2019, at 17:13, Tapani Tarvainen wro= te: >=20 > Core126 upgrade killed a machine: boot freezes after udevd start. >=20 > Experimenting with fresh (flash) installation image (and new CF card) > gave same result. >=20 > Up to and including core125 it works like charm (also tested with a > fresh image). >=20 > This is a bit difficult to debug: the last message displayed is >=20 > "Starting udev daemon... [ OK ]" >=20 > After that even keyboard is dead (caps lock doesn't work, nor alt-ctrl-del). >=20 > And as this happens before disks are mounted, there's no log to read. >=20 > This is a rather old machine, VIA C3 CPU, 512MB RAM, booting of CF card, > but there's nothing obviously wrong with the hardware, and as noted it > worked just fine up to and including core125. >=20 > I could leave it running core125, but a firewall that can't be upgraded > is not a workable long-term proposition. >=20 > Any suggestions as to how I could try to track the problem down? >=20 > --=20 > Tapani Tarvainen --===============3550174105094356347==--