On my laptop HP 625 (Athlon II P320) x64 installer fails to load (Booting kernel failed: Invalid argument). With mga6.1 it works fine. Do we have some different parameters? Using i586 image works with this laptop. After booting the resuce image, I wanted to mount the partions. The laptop has a lvm volume group. It stays searching volume groups. And never reaches an end. Using mga6.1 (x64) installer, it takes 2 seconds and the devices were mounted.
In the SRPM field is a mga6 version. Please tell which mga7 version you used
CC: (none) => isobuild, mageiatools, marja11Keywords: (none) => NEEDINFO
the ones you can download on current mirrors http://ftp.acc.umu.se/mirror/mageia/distrib/7/x86_64/install/ and use one of the mirrors for the rescue image.
Please, one bug per bug report. The problem with lvm is most likely that udev is not running in the rescue system. lvm2 uses udev. I saw the same hang when building the Live ISOs (which runs the installer in a chroot), and had to bypass the disk probe step in that case to avoid it.
CC: (none) => mageia
I'll check your comment on udev. If so, this needs to be changed. The installer and the rescue system need to work as expected.
Hm, it has worked before without udev... I wonder if we have synced in something from another distro that does not belong there..
Source RPM: drakx-installer-rescue-1.55-10.mga6.src.rpm => drakx-installer-rescue-1.61-2.mga7.x86_64.rpmCC: (none) => tmb
Nope, does not look like that, so I guess its an upstream lvm2 change that bites us now
does it hurt enabling udev during installer/rescue stage?
We already use udev in installer. As for rescue it simply means "someone" needs to adapt/rewrite bits so it works...
@Thomas: do you know why the kernel of 64 bit does not work for an older amd64? Did we drop support for a specific arch?
Nope, it should work... remove splash silent from kernel command line to hopefully see what crashes... maybe even remove any "vga=..."
I believe Marc is using one of the netinstall images, although he hasn't said which one. Marc, try booting using 'text' instead of the default to hopefully see more error messages. Also, a common cause of the error message you are seeing is a bad download/copy. Can you try the same media on another machine to rule that out. I assume you are using the i586 image to boot the rescue system.
sorry. Thought it was clear by the package name. To give you a full overview: Hardware: HP 625 (Athlon II P320) Software: MGA6 x86_64 1. Crashed on update to mga7 (x86_64) during python installation, not booting anymore, rpm gives Seg-Faults 2. tried to recover using http://ftp.acc.umu.se/mirror/mageia/distrib/7/x86_64/install/images/Mageia-7-netinstall-nonfree-x86_64.iso 3. image does not boot - on text-prompt shows the message "Booting kernel failed: Invalid argument" 4. Image http://ftp.acc.umu.se/mirror/mageia/distrib/7/i586/install/images/Mageia-7-netinstall-nonfree-i586.iso boots, but fails to mount partitions on a lvm volume (takes forever) 5. tried to run http://ftp.acc.umu.se/mirror/mageia/distrib/6/x86_64/install/images/Mageia-6.1-netinstall-nonfree-x86_64.iso which boots just fine and is able to mount my partions (takes just 2 seconds) now I try to figure out why rpm produces a segfault.
(In reply to Marc Krämer from comment #12) > 1. Crashed on update to mga7 (x86_64) during python installation, not > booting anymore, rpm gives Seg-Faults > > now I try to figure out why rpm produces a segfault. bug #24767 ?
(In reply to Marja Van Waes from comment #13) > (In reply to Marc Krämer from comment #12) > > > 1. Crashed on update to mga7 (x86_64) during python installation, not > > booting anymore, rpm gives Seg-Faults > > > > > now I try to figure out why rpm produces a segfault. > > bug #24767 ? Probably, so wait for rpm-4.14.2.1-12.mga7 to land on the mirrors to see if it helps
(In reply to Marc Krämer from comment #12) > > 2. tried to recover using > http://ftp.acc.umu.se/mirror/mageia/distrib/7/x86_64/install/images/Mageia-7- > netinstall-nonfree-x86_64.iso > > 3. image does not boot - on text-prompt shows the message "Booting kernel > failed: Invalid argument" This is usually a broken image download or breakage when dumping it to an usb... Have you checked md5 / sha512 ?
@Thomas: redownloaded the file, now it works - not sure what went wrong the first time... since I've overwritten the device and deleted the original files I can't reproduce it for now.... strange. So only lvm2 stays as a problem. Now I try to revive it using the latest rpm package.
Created attachment 11052 [details] start udev You can try this patch
CC: (none) => thierry.vignaud
Created attachment 11053 [details] included udevd wants files Or this one
Keywords: (none) => PATCH
No one tested?
Created attachment 11094 [details] Patch to rescue system to start udevd This one works. I'm not certain we need the udev/hwdb.d files, but better to have something we don't need than miss something we do need.
Attachment 11052 is obsolete: 0 => 1 Attachment 11053 is obsolete: 0 => 1
Released
Resolution: (none) => FIXEDStatus: NEW => RESOLVED