On 2019-01-03 11:02:42 -0800, Leo L. Schwab wrote:
> On Thu, Jan 03, 2019 at 01:46:19PM +0100, Vincent Lefevre wrote:
> > Same problem, with the keyboard not working, so that I couldn't do
> > anything here. I reported the bug against the Linux kernel, because
> > everything is fine with a 4.18
I had the same issues on one of my computers and it behaved exactly as
described above: Nor root device found (USB keyboard unusable)
update-initramfs destroyed any initrd.img it touched with udev 240-2
a downgrade to 239-8 (the last I could get my hands on quickly)
resolved the issue
The system
On Thu, Jan 03, 2019 at 01:46:19PM +0100, Vincent Lefevre wrote:
> Same problem, with the keyboard not working, so that I couldn't do
> anything here. I reported the bug against the Linux kernel, because
> everything is fine with a 4.18 kernel (which I had fortunately kept,
> otherwise I would
On 2018-12-29 16:06:38 -0800, Leo L. Schwab wrote:
> JPGs attached. The messages appear to be coming from initramfs,
> which is trying to locate and mount the rootfs, and failing.
Same problem, with the keyboard not working, so that I couldn't do
anything here. I reported the bug against
On Tue, Jan 01, 2019 at 04:50:51PM +0100, Michael Biebl wrote:
> Am 31.12.18 um 00:04 schrieb Leo L. Schwab:
> > 'lsmod' prints nothing. /proc/modules is empty.
> >
> >> ls -la /dev
> >
> > No block devices appear to be listed. (Screen photos available upon
> > request.)
>
> Hm, this
Am 01.01.19 um 17:13 schrieb Matthias Heinz:
> Hi,
>
> I had the same problem and it took me quite some time to rebuild the
> initramfs
> with the older udev version. But I managed to do this from within the
> initramfs console.
>
> What made me wonder, when I did this, is the fact that the
Hi,
I had the same problem and it took me quite some time to rebuild the initramfs
with the older udev version. But I managed to do this from within the
initramfs console.
What made me wonder, when I did this, is the fact that the root device, which
was set as UUID in grub, was not listed in
Am 31.12.18 um 00:04 schrieb Leo L. Schwab:
> On Sun, Dec 30, 2018 at 10:36:02PM +0100, Michael Biebl wrote:
>> Can you share more details about your storage configuration, like mdadm
>> configs, /etc/fstab etc.
>>
> There is no mdadm config; I deleted the package from the system
> earlier
On Sun, Dec 30, 2018 at 10:36:02PM +0100, Michael Biebl wrote:
> Can you share more details about your storage configuration, like mdadm
> configs, /etc/fstab etc.
>
Oh, sorry, left out partition info.
/etc/fstab by itself won't make much sense, as it's all UUIDs.
Further, the
On Sun, Dec 30, 2018 at 10:36:02PM +0100, Michael Biebl wrote:
> Can you share more details about your storage configuration, like mdadm
> configs, /etc/fstab etc.
>
There is no mdadm config; I deleted the package from the system
earlier when trying to diagnose the issue.
After
Can you share more details about your storage configuration, like mdadm
configs, /etc/fstab etc.
When you are dropped into the initramfs, what's the output of
lsmod or cat /proc/modules
ls -la /dev
ls -la /dev/disk/by-uuid
Is a systemd-udevd process running?
--
Why is it that all of the
Control: tags -1 + moreinfo
On 29.12.18 08:50, Leo L. Schwab wrote:
> Rebuilding the initramfs with 'update-initramfs -u' did not work.
> Thinking I'd invoked 'update-initramfs' incorrectly, I then updated all
> available initramfs images using 'update-initramfs -u -k all'. I then
>
12 matches
Mail list logo
