You are not logged in.
Pages: 1
I don't know why but when I upgraded last night my system broke. :shock: The update was to the latest kernel, mkinitcpio, udev, nvidia, etc from versions only a release earlier. (i.e my system was already up to date bar those next version upgrades)
It couldn't mount the filesystem to boot up. I had to re-install the base system but luckily I could mount the existing partitions to install to without having to reformat. Then hal, dbus, portmap and fam failed to start so I had to re-install them and gnome.
Was there any major changes to the kernel that might have caused my system to fail? Or was I just struck by sod's law?
Intel i7-920 (stock), ASUS P6TD-Deluxe, AMD R9 270X, RAM: 6GB
Offline
just change your ramdisk,
boot with kernel26.img instead of initrd26.img, then change it permanent in your bootloader after successfull boot.
check wiki for mkinitcpio for more information
Offline
Thanks but I've already been using mkinitcpio and kernel26.img.
Intel i7-920 (stock), ASUS P6TD-Deluxe, AMD R9 270X, RAM: 6GB
Offline
Did you try changing it in grub to kernel26-fallback.img ?
And what exactly was the error ? Was it acpi related or disk related or... ?
Do you have any custom udev rules?
What's the hardware configuration (what kind of disks etc.)?
Offline
I can't remember exactly the error messages but they were something like not being to mount block device (0,0) and kernel panic: not synching with filesystem.
I have a custom rule for VMware in udev. The one it says about in the Wiki.
Intel i7-920 (stock), ASUS P6TD-Deluxe, AMD R9 270X, RAM: 6GB
Offline
Pages: 1