From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: Core126 udevd problem
Date: Wed, 02 Jan 2019 19:54:03 +0200
Message-ID: <20190102175403.GC23458@tarvainen.info>
In-Reply-To: <F12D8806-5397-44B2-B3B2-0D3C1AEFD57A@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7868489776966989895=="
List-Id: <development.lists.ipfire.org>

--===============7868489776966989895==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Ah, OK then. Thank you for very quick and helpful response!

Tapani

On Wed, Jan 02, 2019 at 05:46:44PM +0000, Michael Tremer (michael.tremer(a)ip=
fire.org) wrote:
>=20
> Hi,
>=20
> This file will be shipped with the next update. This was an unintended bug.
>=20
> -Michael
>=20
> > On 2 Jan 2019, at 17:39, Tapani Tarvainen <ipfire(a)tapanitarvainen.fi> w=
rote:
> >=20
> > Indeed, restoring /etc/modprobe.d/framebuffer.conf fixed it - thank you!
> >=20
> > (As noted the machine boots off a CF card and I have another machine with
> > card reader so editing it is easy.)
> >=20
> > That leads to a followup question, however: how can I prevent this
> > from happening again with next upgrade, and with other machines that
> > are likely to have the same issue? Guess I could add a custom boot
> > script that runs before udev start and blacklists it again - any
> > better ideas?
> >=20
> > Regards,
> >=20
> > --=20
> > Tapani
> >=20
> > On Wed, Jan 02, 2019 at 05:24:01PM +0000, Michael Tremer (michael.tremer(=
a)ipfire.org) wrote:
> >>=20
> >> Hello,
> >>=20
> >> I think you might be running into this:
> >>=20
> >> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D4c76d08b2a=
1ef5ac9ff8b546c0d887e342adec1c
> >>=20
> >> The framebuffer driver is no longer blacklisted and that causes the kern=
el to crash on my VIA devices.
> >>=20
> >> You can mount the hard drive in a different computer and edit the file m=
anually if that is an option for you.
> >>=20
> >> Best,
> >> -Michael
> >>=20
> >>> On 2 Jan 2019, at 17:13, Tapani Tarvainen <ipfire(a)tapanitarvainen.fi>=
 wrote:
> >>>=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
>=20

--=20
Tapani Tarvainen

--===============7868489776966989895==--