[SOLVED] After update Arch won't boot (possibly because of udev)

After running a update to arch it gives me the following errors on boot:
/lib/udev/udevd: error while loading shared libraries: libkmod.so.2: cannot open shared object file: no object file or directory
then it gives several more errors about libkmod.so.2 and finally drops to a recovery shell. I am using an older version of kmod (version 4.2 I think) because i got a different boot error when I had the latest version installed. Any advice?
Last edited by briff (2012-02-19 03:31:54)

falconindy wrote:
briff wrote:After running a update to arch it gives me the following errors on boot:
After a partial upgrade... This is why -Syu is the only supported upgrade path.
briff wrote:Any advice?
Upgrade the rest of your system. udev is expecting kmod>=5.
Please make sure to regenerate your initramfs images, too.
Thanks, after regenerating the initramfs images it works.

Similar Messages

Computer will not start after update. Won't boot. Security Update. Grey.

This is a fix that worked for me. 2 times in the past Automatic Software update has corrupted my hard drive.
When installing using SOFTWARE UPDATE the installer for the security update fails, says it has been moved to trash and to try again. Well if you restart, you get a system hang and much sadness.
I tried the usual stuff, booting from CD(osx) and selecting the disk utility from the top menu. But that didn't fix it. Then I ran DiskWarrior, which usually fixes anything, but it didn't this time.
Here is what did work. I checked my other mac to see what the last security update was, and it had the 2009-001 update (worked on that mac). So I knew now that the one that screwed up was that update.
I downloaded that update to my laptop.
I started my iMac (the one that crashed after update) in "target disk mode" - this treats the whole computer as an external firewire disk drive (it's totally safe as long as you don't erase anything) - you start into target mode by holding down "T" key while turning on, leave it pressed until you see a symbol on the screen that looks like a "Y".
I hooked up a firewire cable from the iMac to my laptop and waited until the iMacs Hard drive appeared on the laptop desktop.
Now you can browse the corrupt drive just like a regular external drive.
If you have an external drive with room, this is a good time to back up the entire corrupt drive to a folder on the other external just in case...
But what I have found is that when the installer for the security update failed, it corrupted the file that mac osx needs to read during boot, so it is an isolated failure, but it is always better to be safe.
at this point you are ready to attempt the repair..
On my laptop I ran the installer for the security update I had manually downloaded from apples site. When asked for destination for the install I select the HD for the iMac (or whatever unit has the no boot situation that got corrupted). (note that if you have not renamed your main hard drives, you will have a choice of 2 with the same name). Usually the drive on the computer you are using will be first in line. Rename the drive on the computer you are using before running the install if you want to be sure there are no mistakes..)
Select the disk you want to (re)install to, and let it go. It is a long update, so be patient and let it finish. It should say preparing install, installing, finishing, and optimizing system performance...
When it says that the installation completed successfully you can eject the corrupt hard drive by dragging to the trash to dismount it. Then unplug the firewire cable.
Shut down the repaired (hopefully) machine by holding the power button until it turns of.
Count to ten.
Prepare a celebratory or misery soothing beverage (but keep it in the other room).
Some people like to start in safe mode by holding down shift key while turning on, but I couldn't get it to work on mine...
Turn the computer back on and wait. The boot process will take longer than usual the first time.
If and when you get to login or desktop, go in and run apple disk utility and repair the disk, and repair the permissions.
If it worked, breathe a sigh, do a happy dance. And from now on when mac os says there are updates available, write them down, then go to apples site, download them manually, and install them manually, one at a time from now on, to avoid hassles.
Hope this helps!
Enjoy!

Thanks for the post/tips newfocus, hope it helps somebody!

[SOLVED] Enabled AHCI - Arch won't boot

I have switched the SATA preference to AHCI from IDE in the BIOS. Now Arch refuse to boot with following warning:
ERROR: device '/dev/sda2' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda2
[rootfs /]#
I have checked the WIKI and it has a remedy with 'mkinitcpio'; looks outdated. I have also found about adding one moule to initrd with mkinitrd on the www. However, I am not sure and need some guidance regarding this.
By the way, I dual-boot with Ubuntu and it booted just fine after the switch to AHCI.
Thanks.
Last edited by fantab (2013-04-21 22:27:38)

Thanks guys I fixed it from Ubuntu with 'chroot'. I added "ahci" to MODULES in /etc/mkinitcpio.conf and ran mkinitcpio.
I can boot Arch now.
Do I have to re-install the kernel? Do I have to add "ahci" to mkinitcpio.conf at every kernel upgrade and run mkinitcpio? Or am I OK.
Out of curiosity, regarding 'fallback image', how is it "even simpler"? Would love to know, for future reference, any pointers?
Last edited by fantab (2013-04-21 21:39:57)

Arch won't boot on Virtual Box afted updating

I instaled Arch as guest on Vbox, after updating, it won't boot any more. It prints the message "Loading udev...SCSI subsystem initialized" and then the VM crash and the window is inmediately closed.
I searched on the Vbox forum and others have the same problem.
See: http://forums.virtualbox.org/viewtopic. … 890#p83890
Probably is an issue with Arch, because a clean install from core iso does work, but does not after updating.

What do you mean under updating ? pacman -Syu ? And what packages was installed?
Isn't there any virtualbox log or something ?

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

Intel D2700DC + Arch won't boot without display

I've faced really wierd (to me) problem running Arch as mini webserver on the Intel D2700DC mini-ITX board with Atom D2700 integrated and NM10 Express chipset.
I successfully installed the system, configured network and started sshd to continue setting up other services remotely via ssh console. Then I disconnected the keyboard and display from the case and put it under the table. After that I was quiet surprised that the system was not starting up anymore.
After some investigation I've found that the system is not booting if no display is attached to the DVI port of the motherboard. If I start the system with display disconnected, I can hear one beep that notifies about successful BIOS POST, HDD led blinks 2-3 times, and then just nothing happens. System isn't booting up. If I attach the display right after that - nothing is seen on the screen, and display is immediately falling into sleep mode. Keyboard is still active though, and if I press ctrl+alt+del - the system is restarting, and, if display was just connected, it boots ok then. Also it boots fine from the cold state if the display was attached to the DVI port at the time of powering on.
As I can assume from the timings and HDD led blinking, the boot process stops right after GRUB is loaded. There's nothing in system log, cause it seems that boot hangs just before the kernel is loaded by GRUB. I'm really stuck and don't know how to work around this situation, because if the display was disconnected when system was powered on - then there's no way to see anything on the screen until next reboot, and if the display was connected - then the system boots OK.
One more thing to notice:
There was an old CentOS installation on the HDD, to which I installed Arch Linux. I've tried to boot it once or twice before installing Arch, and, as I could remember, it could boot up without display connected, on the very same hardware. So I suppose it's definitely something in Arch that is preventing the system to boot without the display.
I guess that when no display is connected at boot time, NM10 chipset completely disables onboard video, and because of this we can't see anything on the display until the system is restarted. But this somehow affects Arch, so it can't boot without any video hardware present.
Last edited by rand256 (2012-05-10 10:23:28)

I'm afraid there's no such option, but it looks like arch isn't booting just because no graphics card is detected in the system when display it disabled during powering up.
There is a couple of similar topics about some other linux distros can't boot without video card inserted ([1], [2]) with some recommendations on what to do in such a case.
I've followed them - including enabling serial console in /etc/inittab, setting nomodeset in kernel line in grub's menu.lst, checking for enabled splash-screens... but that didn't help.
Does anyone know what options should be tuned in order to boot Arch without any active graphics card present in the system hardware?

After update, firefox won't open

after last update, firefox won't start. maybe because I believed it would restart the first time I started computer. the instructions have always given that option

Try to download the full version and trash the currently installed version to do a clean (re)install of the latest version.
Download a new copy of the Firefox program and save the disk image (dmg) file to the desktop
*Firefox 15.0.x: http://www.mozilla.org/en-US/firefox/all.html
*Trash the current Firefox application (e.g. open the Applications folder in Finder and drag the Firefox application to the Trash) to do a clean (re-)install
*Install the new version that you have downloaded
Your profile data is stored elsewhere in the Firefox Profile Folder, so you won't lose your bookmarks and other personal data if you uninstall and (re)install Firefox.
*http://kb.mozillazine.org/Profile_folder_-_Firefox

Took delivery of imac yesterday with pre-installed Pages, Numbers and Keynote. App store says they need updating but won't let me because I've never owned the major version of the software. I have paid like anyone else, so why can't I update?

Took delivery of imac yesterday with pre-installed Pages, Numbers and Keynote. App store says they need updating but won't let me because I've never owned the major version of the software. I have paid like anyone else, so why can't I update?

You must be signed into the Apple Store with your Apple ID or it won't work.
and
How to deal with a 100 Store Error:
Try here > Mac App Store: "An unknown error occurred (100)" when purchasing
If that doesn't help, open the Finder. From the Finder menu bar click Go > Go to Folder
Type this exactly as you see it here;
~/Library/Caches/com.apple.appstore/Cache.db
Click Go
Move the Cache.db file to the Trash.
Now here:
~/Library/Preferences/
Click Go
Move these files from the Preferences folder to the Trash.
com.apple.appstore.plist
com.apple.storeagent.pllist
Now here:
~/Library/Cookies
Click Go
Move the com.apple.appstore.plist file from the Cookies folder to the Trash.
Empty the Trash, try the App Store.

After updating with ios7, I cannot proceed because I cannot enter my password since it uses Greek letters but the keyboard available is Latin. How can I change the keyboard to Greek?

After updating with ios7, I cannot proceed because I cannot enter my password since it uses Greek letters but the keyboard available is Latin. How can I change the keyboard to Greek?

try tapping holding on the key that would be most similar to the letter you want to enter, that will bring up a menu of other characters similar to that character and maybe the greek letter will be included in that menu

My Macbook won't boot up because there isn't enough free space for my start up disk. It's now stuck on a blue screen. How am I meant to delete files to free up space if I can't access the computer?

My Macbook won't boot up because there sin't enough free space to run the startup disk. My Macbook now won't go past the blue screen so exactly how am I meant to be able to delete files if I can't access the computer?

Do you have a bootable backup?
What operating system are you running? If OS X 10.6 or lower, boot from your original OS X DVD or a retail OS X DVD and then delete files as needed. Your goal should be to get to 10% of your disk capacity free.
If you have OS X 10.7 Lion or 10.8 Mountain Lion, you don't have many choices in recovery mode (boot holding the command and r keys down).
If you have a FireWire or Thunderbolt connection, you can try target disk mode with another mac.
If none of those work, perhaps your local Apple store can help with a bootable external drive.

Arch won't boot after rEFInd update

I've followed https://wiki.archlinux.org/index.php/UEFI_Bootloaders as closely as I can, but still can't get Arch to boot. It doesn't even get to the boot loader.
uname -m
x86_64
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
lsblk
Name Type Mountpoint
sda disk
sda1 part /
sda2 part /boot
sda3 part /boot/efi
sda4 part /var
sda5 part /home
Directory tree:
/boot/
efi/
EFI/
arch/
initramfs-arch-fallback.img
initramfs-arch.img
refind_linux.conf
vmlinux-arch.efi
refind/
icons/
refind.conf
refind_x64.efi
initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda1
efibootmgr -v
BootOrder: 0018, ...
Boot0018* Arch Linux (rEFInd) HD(3,0,0,74930800)File(EFI\refind\refind_x64.efi)
Anything else I'm missing? By the way, I think this is related to the Jan 27. update to refind. Today was the first time I've rebooted my computer since then.
Also - I tried both commenting and uncommenting scan_all_linux_kernels in refind.conf. No dice.
Thank you very much!
EDIT: Some updates...
I was poking around the UEFI shell. The following commands caused my computer to hang (I had to hard-restart):
Shell> fs0:
FS0> ls
I could ls just fine using shell 1.0, but shell 2.0 caused a hang. Then, after the hard restart, more strange behavior:
Shell> bcfg boot add 0 fs0:\EFI\refind\refind_x64.efi "Test"
Error. The file 'fs0:\EFI\refind\refind_x64.efi' did not open.
Also, I can "bcfg boot dump" just fine, but if I want to scroll through the output, I get an error, and it hangs, so I have to hard restart again.
Shell> bcfg boot dump
// bunch of output
Shell> bcfg boot dump -b
// after printing five boot entries...
Press ENTER to continue or 'Q' to break:
ASSERT_EFI_ERROR (Status = Not Ready)
ASSERT c:\dev\edk2top\ShellPkg\Library\UefiShellLib\UefiShellLib.c(3223) : !EFI_ERROR (Status)
Not sure if any of that last but is relevant. Thanks again.
Tried downgrading kernel to 3.6, still won't boot.
Last edited by MitchellSalad (2013-01-30 20:05:10)

MitchellSalad wrote:
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda3
Shouldn't that be sda1? Your root-partition is /dev/sda1.

Arch Won't Boot After Kernel Upgrade

I installed Arch on VirtualBox, but after upgrading the Kernel to 2.6.30 it wouldn't boot. It gets to "Loading udev...." and then VirtualBox crashes.

Hello, I'm having this same problem, except I'm not using VirtualBox or VMWare, I have Arch installed to the hard drive. It worked fine after upgrading to 2.6.30, but after upgrading kernel-headers to 2.6.30.1-1, neither Arch NOR Arch-Fallback will boot! I don't even get to Udev or the part where the two arch logos are on top. It just starts up a little bit, then restarts my computer.
I don't even know if my system has been wiped or something, but I doubt that; I think it's just the booting process. I do have a 2009.2 Live CD, but it's an FTP installation. Is there any way to start up my live CD and do a pacman -U for the old kernel version with the cache on my hard drive? How would I do this?
Last edited by Allamgir (2009-07-07 00:32:12)

Arch won't boot, FS not detected, Kernel Panic.

Ok so here is the situation. I have arch linux installed on sda1, which is a sata drive, samsung. Seems lately I been having problems getting arch to boot because it doesn't know what type filesystem my root device has. It goes on and tells me that I can use the kernel parameter rootfstype= to solve the issue, but yet when I try this, it does nothing. I stop getting the error, about unknown FS type, but arch still won't boot. Init fails...
I have tried everything on these forums to fix the problem and not one thing in general has solved the issue. What seems to be most consistent about this problem, is it takes me at least 20 - 30 times of rebooting before it will finally go through and boot. But, even then this is not foolproof. Last night I tried at least 30+ times of rebooting, powering off and still it would not boot.
So after reading the forums some more I found an article somewhat related to my problem and it was suggested that I add my root FS type as a module and then remove the filesystem hook in mkinitcpio.conf. I tried this approach and at the same time downgraded to 2.6.24.2-1 kernel26 so mkinitcpio would generate the new image. Then I rebooted and arch loaded just fine. So then I rebooted and again, unknown fs type on root device error.
So I retraced my steps and tried the same process again, only this time when I rebooted I got same problem. So as it seems, nothing I did to mkinitcpio.conf did anything to alleviate my problem.
As of right now, I managed to get the fallback image to work(but fallback does not load all the time, just this last time I tried it it worked), but I am scared to death to turn off my machine because I know it's not gonna reboot without a lot of hassle.
So can anyone help me diagnose this problem? What can I do to get the kernel to boot and mount the root device with ext3 and pass init on boot up? I am completely lost when it comes to this...
here is my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="ext3 pata_amd ata_generic sata_nv"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata sata"
here is my fallback.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
# BusLogic is added to support VMWARE arch booting in fallback image
MODULES="BusLogic"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
#BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide filesystems raid encrypt"
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
HOOKS="base udev ide pata scsi sata usbinput raid filesystems"
modules I need
sudo mkinitcpio -M
Password:
Modules autodetected:
ata_generic
libata
pata_acpi
pata_amd
sata_nv
cdrom
ide-core
amd74xx
generic
forcedeth
sd_mod
sr_mod
usbcore
ehci-hcd
ohci-hcd
jbd
ext3
Last edited by jacko (2008-04-15 19:53:35)

I had a similar issue (I think, can you post the exact error the kernel panics with to check?) and it seemed grub or the kernel had difficulties with finding my root device which was specified as a device node in /dev. The solution for me was to change the root parameter in my kernel line in grub's menu.lst to root=/dev/disk/by-label/<label>, I'm sure UUID and such will work fine too. After doing that I haven't encountered a single such kernel panic. More info about persistent device naming can be found here.

After update Arch stays at Welcome Arch - arch live iso the same

Hi, I would ask for your help. I did an update of Arch today morning, after this i can,t boot Arch. I added nomodeset to kernel but it just doesen,t work, won,t boot. I tried to run it from usb media, i downgraded kernel to 3.9, i downgraded intel drivers but still no luck. I have Acer Aspire AOD 270 with GMA3600 driver and Intel Atom procesor. Could somebod help me? It stays at Welcome Arch sign.
Last edited by firekage (2013-11-02 15:05:22)

jasonwryan wrote:
1. Stop bumping this thread: learn to use the edit button.
2. What video card is in your machine?
3. Add the relevant module to your mkinitcpio.conf to start early KMS
4. There is nothing wrong with Arch, except the number of people that want to use it without reading any of the documentation.
1. Intel GMA 3600 with Atom N2600 - Acer AOD 270.
3. My driver is iinstalled, it is something wrong not with it because it stops during boot after checking of root partition in text mode with nomodesert in kernel parameter. Also, the same thing happens on live usb with iso from november, but iso from june works, boots but than upgrades all of it and installation fails to boot,
4. Well, i could debate, i read a lot cause i like it, and in fact there are errors in documentation, for an example: related to installing nvidia driver, xorg.conf and 20-nvidia.conf.
BTW - i know that it is pointed towards me, but belive, or not - i read a lot, i only ask when i can't find a solution over the net, arch wiki or on other media. This problem is very strange - even iso from usb won't boot, on 2 computers (one desktop, one netbook). As a matter of fact, i've been reading since thursday about this problem.
Last edited by firekage (2013-11-02 20:37:18)

System Updates, Now Won't Boot

I did four recommended system updates yesterday, two being Security and ITunes. Now my MacBook won't boot, even in Safe Boot mode or from the disk. Just the blue screen and the circle. I have it connected to another computer so I can see and get into the HD that won't boot but I'm not sure how to bring it back without deleting other files that have nothing to do with it. I'd like to return my system to how it was before I did those updates. It does not have TimeMachine. Is there any way to return to "yesterday" before the updates?
Thanks from Gina

You won't be able to return to the "yesterday" configuration unless you have a backup.
I assume you are using Target Disk mode to connect the MacBook to another Mac. If so, use Disk Utility on the other Mac to run the following: first Repair Disk Permissions. If that doesn't correct the problem, then run First Aid.
 Cheers, Tom

[SOLVED] After update Arch won't boot (possibly because of udev)

Similar Messages

Maybe you are looking for