Re: no login screen after f25 to f26 upgrade.

2017-10-21 Thread Ed Greshko
> Question: If I were to submit an enhancement request bugzilla on this, would > it likely get > done (preferably in time for Fedora 28)? > > If yes, then > Question: Which bugzilla (or other tracking system) should I use (please > provide url)? There would be no action taken on any fedora bug

Re: Cant boot latest kernel 4.13.5-100 - kernel panic - can't mount root

2017-10-21 Thread Ed Greshko
On 10/21/17 23:10, Andy Paterson wrote: > > FC25 kernel update that installed 4.13.5-100.fc25.x86_64 > > Cant mount /boot > >   > > System:ELITEGROUP COMPUTER SYSTEM CO.,LTD. P965T-A/P965T-A, BIOS 6.00 PG > 08/30/2007 > > 4 X Intel Core2 Quad CPU Q6700 @ 2.66GHZ > >   > > Kernel panic > >   > > Ca

Re: Cant boot latest kernel 4.13.5-100 - kernel panic - can't mount root

2017-10-21 Thread Samuel Sieb
On 10/21/2017 08:10 AM, Andy Paterson wrote: Hi, after a recent package manager based update, FC25 kernel update that installed 4.13.5-100.fc25.x86_64 Cant mount /boot Can you explain this further? Was that an error during the update or you're saying that you can't mount the /boot partition

Re: no login screen after f25 to f26 upgrade.

2017-10-21 Thread William Mattison
(replying to Ed, Samuel, and Patrick) The upgrade phase (step 7) generated a line of output for each package(?) being upgraded. The clean-up phase (step 7) generated a line of output for each upgraded package(?). The verify phase (step 7) generated a line of output for each upgraded package(?).

Cant boot latest kernel 4.13.5-100 - kernel panic - can't mount root

2017-10-21 Thread Andy Paterson
Hi, after a recent package manager based update, FC25 kernel update that installed 4.13.5-100.fc25.x86_64 *Cant mount /boot* System:ELITEGROUP COMPUTER SYSTEM CO.,LTD. P965T-A/P965T-A, BIOS 6.00 PG 08/30/2007 4 X Intel Core2 Quad CPU Q6700 @ 2.66GHZ *Kernel panic* Can boot previous kernel : 4

Re: no login screen after f25 to f26 upgrade.

2017-10-21 Thread Patrick O'Callaghan
On Fri, 2017-10-20 at 21:01 -0700, Samuel Sieb wrote: > > The above indicated that the rpm was built, but could not be installed. > > Most likely due to the dnf command still having the rpm database locked. > > Right, so the next reboot will be able to do the install. You can also just run 'dnf