Am 14.01.19 um 19:45 schrieb Isaac Gelado:
> When I got the initramfs shell I also typed
>
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
>
> and tried to continue the boot process, but it failed. Then I typed
>
> udevadm trigger --type=devices
When I got the initramfs shell I also typed
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add
and tried to continue the boot process, but it failed. Then I typed
udevadm trigger --type=devices --action=add -v
and it booted nicely. Somehow, the `-v` flag
Sorry for the late reply. I could not reboot my machine until today.
I added a sleep 5 and it didn’t work.
On Tue, Jan 8, 2019 at 9:15 AM Michael Biebl wrote:
> Am 08.01.19 um 18:11 schrieb Isaac Gelado:
> > As a side hint that might be helpful. I had two kernels 4.18 and 4.19
> > in my
Am 08.01.19 um 18:11 schrieb Isaac Gelado:
> As a side hint that might be helpful. I had two kernels 4.18 and 4.19
> in my system. This problem started when I first boot 4.19, while I was
> able to boot 4.18 without problems. At some point I decided to do an
> `update-initramfs -k all -u` and the
On Tue, Jan 8, 2019 at 8:38 AM Michael Biebl wrote:
>
> Am 08.01.19 um 16:43 schrieb Isaac Gelado:
> > Adding sleep 1 does not work. I also check that the -v flag is only
> > needed in one of the calls to udevadm.
>
> Urgh, this is getting really weird.
> -v should not affect the behaviour of
Am 08.01.19 um 17:38 schrieb Michael Biebl:
> Am 08.01.19 um 16:43 schrieb Isaac Gelado:
>> Adding sleep 1 does not work. I also check that the -v flag is only
>> needed in one of the calls to udevadm.
>
> Urgh, this is getting really weird.
> -v should not affect the behaviour of udevadm, but
Am 08.01.19 um 16:43 schrieb Isaac Gelado:
> Adding sleep 1 does not work. I also check that the -v flag is only
> needed in one of the calls to udevadm.
Urgh, this is getting really weird.
-v should not affect the behaviour of udevadm, but only generate
additional output which might slow it down
Adding sleep 1 does not work. I also check that the -v flag is only needed
in one of the calls to udevadm.
On Tue, Jan 8, 2019 at 6:35 AM Michael Biebl wrote:
> On Mon, 7 Jan 2019 12:27:10 -0800 Isaac Gelado wrote:
> > I am having this very same issue. If I run
> >
> > udevadm trigger
On Mon, 7 Jan 2019 12:27:10 -0800 Isaac Gelado wrote:
> I am having this very same issue. If I run
>
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
>
> in the initramdfs shell, it does nothing at all. However, if I run
>
> udevadm trigger
Am 08.01.19 um 13:00 schrieb Michael Biebl:
> Am 08.01.19 um 12:53 schrieb Vincent Lefevre:
>> On 2019-01-06 12:30:04 +, Jakub Sokołowski wrote:
>>> On Sun, 6 Jan 2019 08:33:09 +0100 ludszuweit1
>>> wrote:
Is it possible, that dev 240-2 have problems to boot with m2 connected
Am 08.01.19 um 12:53 schrieb Vincent Lefevre:
> On 2019-01-06 12:30:04 +, Jakub Sokołowski wrote:
>> On Sun, 6 Jan 2019 08:33:09 +0100 ludszuweit1
>> wrote:
>>> Is it possible, that dev 240-2 have problems to boot with m2 connected
>>> SSDs?
>>
>> I don't use m2(though I do have it). I'm
On 2019-01-06 12:30:04 +, Jakub Sokołowski wrote:
> On Sun, 6 Jan 2019 08:33:09 +0100 ludszuweit1
> wrote:
> > Is it possible, that dev 240-2 have problems to boot with m2 connected SSDs?
>
> I don't use m2(though I do have it). I'm using regular SATA ports on
> my MSI X99A SLI Plus, which
I can confirm that adding "-v" to the two udevadm trigger commands,i.e.,
udevadm trigger --type=subsystems --action=add -v
udevadm trigger --type=devices --action=add -v
does indeed load the missing modules (on the second command) for me,
too, and boot proceeds normally once I exit the initramfs
I am having this very same issue. If I run
udevadm trigger --type=subsystems --action=add
udevadm trigger --type=devices --action=add
in the initramdfs shell, it does nothing at all. However, if I run
udevadm trigger --type=subsystems --action=add -v
udevadm trigger --type=devices --action=add
Hi Axel
Am 06.01.19 um 13:32 schrieb Axel Ludszuweit:
>
> Hello Michael,
>
> I have try your udev240-3, unfortunately it fails in the same way as
> udev240-2. Due to a lack of PS2 keyboard I can't run your suggested commands
> in the initramfs shell.
> One thing was other than I expected:
>
Hi Laurence!
Am 06.01.19 um 19:29 schrieb Laurence Abbott:
> I'm pretty sure I came across the same issue yesterday: I ran a
> dist-upgrade on an X99-based system (the first for several months) and
> the system was left unbootable. My root system is on raid and booting
> failed with mdadm errors
I'm pretty sure I came across the same issue yesterday: I ran a
dist-upgrade on an X99-based system (the first for several months) and
the system was left unbootable. My root system is on raid and booting
failed with mdadm errors about it not being able to find any of the
raid arrays listed in
On Sun, 6 Jan 2019 13:32:32 +0100 Axel Ludszuweit
wrote:
> With the above mentioned udev packages I can boot into 4.18 but not into 4.19.
Same here. I tried the udev 240-3 that was linked and 4.19.0-1 didn't work for
me either.
On Sun, 6 Jan 2019 08:33:09 +0100 ludszuweit1
wrote:
> Is it possible, that dev 240-2 have problems to boot with m2 connected SSDs?
I don't use m2(though I do have it). I'm using regular SATA ports on my MSI
X99A SLI Plus, which uses the Intel X99 Express chipset. Anyone else using X99
and
On Sat, 5 Jan 2019 22:30:27 +0100 Michael Biebl wrote:
> Am 05.01.19 um 22:09 schrieb Axel Ludszuweit:
> > Hello Michael,
> >
> > yes, I am willing to try your package tomorrow, but I have the following
> > questions:
> > - in the initramfs rescue shell the keyboard doesn‘t work, therefore I
On Sun, 6 Jan 2019 11:53:49 + =?UTF-8?Q?Jakub_Soko=C5=82owski?=
wrote:
> I suspect this might be hardware related since I saw another person having
> the same issue on a forum, and were both using motherboards using Intels X99
> chipset.
I also use a motherboard with X99 chipset,
I suspect this might be hardware related since I saw another person having the
same issue on a forum, and were both using motherboards using Intels X99
chipset.
> Do you have a PS/2 keyboard? This should require any special (USB)
> kernel modules.
No, I don’t have a PS2 keyboard.
The following hint may be useful:
The computer of my wife with nearly the same software and update state as my
one boots without problems with initrd image using udev 240-2.
Am 05.01.19 um 22:30 schrieb Michael Biebl:
> Am 05.01.19 um 22:09 schrieb Axel Ludszuweit:
>> Hello Michael,
>>
>> yes, I am willing to try your package tomorrow, but I have the following
>> questions:
>> - in the initramfs rescue shell the keyboard doesn‘t work, therefore I can
>> run your
Am 05.01.19 um 22:09 schrieb Axel Ludszuweit:
> Hello Michael,
>
> yes, I am willing to try your package tomorrow, but I have the following
> questions:
> - in the initramfs rescue shell the keyboard doesn‘t work, therefore I can
> run your suggested commands
Do you have a PS/2 keyboard? This
On Sat, 5 Jan 2019 21:41:35 +0100 Michael Biebl wrote:
> Hi Axel!
>
> Am 05.01.19 um 21:33 schrieb Axel Ludszuweit:
> > I have read bug
> >
> > #917607: udev240 makes system unbootable; rootfs not found
> >
> > Because my working and failing initrd files contain different udev
> > versions,
Hi Axel!
Am 05.01.19 um 21:33 schrieb Axel Ludszuweit:
> I have read bug
>
> #917607: udev240 makes system unbootable; rootfs not found
>
> Because my working and failing initrd files contain different udev versions,
> the failing one udev240, it may be possible, that this is the cause
I have read bug
#917607: udev240 makes system unbootable; rootfs not found
Because my working and failing initrd files contain different udev versions,
the failing one udev240, it may be possible, that this is the cause of failed
boot.
Bug #917607 description sounds very similar to
I just encountered exactly the same problem. This made my Debian Sid
on workstation unable to boot... oops. I am using regular ext4
filesystems.
It would be great if we could solve it soon since this bug is really
devastating.
(email sent from Ubuntu 18.04)
--
Regards,
Boyuan Yang
29 matches
Mail list logo
