[SOLVED] Arch won't respond after hibernation

I don't normally hibernate but I accidentally hit the button while moving my keyboard. After I waited a minute and turned it back on it slowly started to boot up then went to a black screen. Now when I restart it reaches the gnome login screen then doesn't respond to the mouse or keyboard. The first thing I though I'd try was reformatting the swap partition but that didn't help. I really don't know what could have happened and I definitely don't know how to fix it. Any help would be appreciated.
Last edited by recharge330 (2011-06-15 16:03:34)

Yup, downgraded some packages and now it works fine. Any mods who see this should feel free to delete this topic considering the title and first post have nothing to do with the problem.

Similar Messages

[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)

[SOLVED] Arch won't boot after install - "GRUB" on black screen

I've installed arch on my 1000H from usb stick using zeneee kernel as described in wiki. Right after install everything was fine - wireless and ethernet were working normally, so i've done reboot.
Now it shows me black screen with "GRUB" text (sic! not "grub>", no error messages) on it. keyboard is not working.
I've tried reinstalling completely again - with full repartitioning of HDD and this time without installing eee kernel - just stock kernel26. Everithing went ok, i've checked grub settings and partitions - ok, but after reboot - again "GRUB" and non-working keyboard.
I'm completely out of ideas.
EDIT: turns out i misplaced GRUB or something. reinstalled placing GRUB on /dev/sda. works fine now.
Last edited by glas01 (2008-11-29 12:46:15)

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)

X220i wireless radio and hotkeys won't work after hibernation

I just bought an X220i laptop. I've spent a weekend downloading updates and drivers and searching the forum and support site, but I have two unresolved issues. Once I bring the computer back from hibernation, the wireless radio is off and will not turn back on. I can bring up the dialogue box, click the "turn on" button, and nothing happens. The only way to restor the wireless connection is to reboot the machine.
A related, but less frustrating, problem is that after hibernation, none of the hotkeys work. Again, rebooting is required to use any hotkey functions. Both of these problems occur after hibernation mode only. They do not happen when the laptop recovers from sleep mode. Any help would be greatly appreciated!

ColonelONeill wrote:
Are you using the preloaded Windows 7?
Can you try running System Update (search in the Start menu) and having it update your drivers?
Unfortunately, System Update often fails to offer the latest versions available, a serious problem.
(See BUG: System Update fails to offer latest versions of some components)
So after running System Update, be sure to check Drivers and software - ThinkPad X220, X220 Tablet, X220i, X220i Tablet (MIGR-77280) and manually install whatever was missed by System Update.
Hope that helps,
John
ThinkPad T450s [ i7-5600U | 8GB | 1TB SSD | Full HD IPS | 802.11ac | BT | Webcam | FR | Win8.1Pro64 ]

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 after lockup: "Failed to read file" [SOLVED]

So like many stories, this one begins with a "Sudo pacman -Syu".
Everything was updating fine, but then my system locked up. I let it set for awhile, but when I couldn't even get a console, I finally rebooted (yes, bad, I know).
I was about half-way through the upgrading process.
Now my system will not boot, and I only get a "Failed to read file" error.
I chrooted into my system through the live disk, and managed to finish the upgrade (I had to fix a few files, and reinstall some manually). I tried a "mkinitcpio -p linux," but no luck.
Is there anything else I could post that might be helpful? This error does not tell me a whole lot.
Thanks!
Last edited by thewooster (2014-06-18 16:11:51)

I did a little more looking around, and found a few more problems.
When I run a "mkinitcpio -p linux" now, I get:
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
It also appears I have a number of "empty" directories "pacman -S linux"
resolving dependencies...
looking for inter-conflicts...
Packages (1): linux-3.14.6-1
Total Installed Size: 70.27 MiB
Net Upgrade Size: 0.00 MiB
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
reinstalling linux...
>>> Updating module dependencies. Please wait ...
depmod: ERROR: failed to load symbols from /lib/modules/3.14.6-1-ARCH/extramodules/fglrx.ko.gz: Invalid argument
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: Unable to write to /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: Unable to write to /boot/initramfs-linux-fallback.img
ldconfig: File /usr/lib/libclamunrar_iface.so is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so.2 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so.4 is empty, not checked.
ldconfig: File /usr/lib/libfontforgeexe.so is empty, not checked.
ldconfig: File /usr/lib/libcord.so is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so.5 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so.0.3000.8 is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so.1 is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so.0 is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so.1 is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so.2 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so.6 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so is empty, not checked.
ldconfig: File /usr/lib/libX11.so.6 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so.6 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so.0.0.1 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.1 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so is empty, not checked.
ldconfig: File /usr/lib/libclamunrar_iface.so.6.1.23 is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so.2 is empty, not checked.
ldconfig: File /usr/lib/libcord.so.1 is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so is empty, not checked.
ldconfig: File /usr/lib/libgccpp.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.2 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so is empty, not checked.
ldconfig: File /usr/lib/libX11.so.6.3.0 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so.2 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so is empty, not checked.
ldconfig: File /usr/lib/libclamunrar.so.6.1.23 is empty, not checked.
ldconfig: File /usr/lib/libclamunrar_iface.so.6 is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libtalloc.so.2.1.1 is empty, not checked.
ldconfig: File /usr/lib/libgutils.so.2 is empty, not checked.
ldconfig: File /usr/lib/libfontforge.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libtalloc-compat1-2.1.1.so is empty, not checked.
ldconfig: File /usr/lib/libgc.so.1 is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so is empty, not checked.
ldconfig: File /usr/lib/libcord.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libgunicode.so.4.0.0 is empty, not checked.
ldconfig: File /usr/lib/libX11.so is empty, not checked.
ldconfig: File /usr/lib/libpytalloc-util.so.2.1.1 is empty, not checked.
ldconfig: File /usr/lib/libgc.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgdk_pixbuf_xlib-2.0.so.0.3000.8 is empty, not checked.
ldconfig: File /usr/lib/libgdraw.so.5.0.0 is empty, not checked.
ldconfig: File /usr/lib/libX11-xcb.so.1.0.0 is empty, not checked.
ldconfig: File /usr/lib/libwbclient.so.0.11 is empty, not checked.
ldconfig: File /usr/lib/libgioftp.so.2.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgc.so.1.0.3 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so is empty, not checked.
ldconfig: File /usr/lib/libgnome-menu-3.so.0 is empty, not checked.
ldconfig: File /usr/lib/libclamav.so.6.1.23 is empty, not checked.
Gummiboot will not reinstall "gummiboot -path=$esp install":
Failed to check file system type of : no such file or directory
I have considered doing a reinstall, but I have so many customizations that I would prefer not to lose them. I do have an rsync backup, but it is a little old, and do have separate home/root partitions, but wouldn't I still lose a fair amount of customizations?

[Solved] X won't srart after ugrade to X 1.7.1-1

Hi,
I am on a 32b updated Arch/KDE 4.3.2 system (with an old Nvidia card) which has been working perfectly till yesterday.
After performing (as root from non graphical terminal) a full system upgrade (pacman -Syu) this morning, X/KDE won't start anymore (even after reboot).
The last X log file shows that the problem is failure to load the /usr/lib/xorg/modules/drivers/nvidia_drv.so file.
However, I've verified that such a file exits there (along with nv_drv.so and vesa_drv.so files).
The pacman log of that last upgrade (which consisted of nearly 60 files) did NOT report any problem, and among others included the following upgrades:
a. xorg server 1.6.3.901 --> 1.7.1-1
b. xf86-video-nv 2.1.14-1 ---> 2.1.15-1
c. mesa 7.5.1.2 ---> 7.6-2
Pacman did NOT upgrade any nvidia driver
Please advise !
Best regards,
Michael Badt
Last edited by mibadt (2009-11-01 08:01:44)

semperfiguy wrote:
Here is the output of thy command:
[drm] Initialized drm 1.1.0 20060810
xorg.conf at pastebin.com/f3edfe847
According to that command, KMS is not in use. Do you have nouveau-drm installed and "options nouveau modeset=1" in your /etc/modprobe.d/modprobe.conf? What's the output of "cat /proc/fb"?
Also, that xorg.conf is using some nVidia-blob-specific options. I'd go with:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
EndSection
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "True"
EndSection
Section "Device"
Identifier "Card0"
Driver "nouveau"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
EndSection

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.

Mouse won't respond after downloading 10.2.8 update.

I had to reinstall the older system of 10.2 after I tried to install 9.1 on my system. I couldn't boot up at all except through using apple option o f or from a system disk. I had recently bought this emac through ebay and it had the Tiger system installed but I didn't get the disk with the computer. My cds are the grey cds and therefore I had problems with the display being small. Finally after downloading 10.2.8 and zapping my pram and reset-all in o f, my display is now back to normal, but I can't get the mouse to respond. I have tried switching mouses and unhooking and reconnecting everything but nothing works. What can I do? This is becoming a real headache. Someone please help me.
Elaine

wmanning,
Welcome to the Apple Discussions!
What kind of mouse are you using? What Mac model name is in the grey OS X 10.2 Install discs you were using? Unless the grey-labeled discs are for the exact same Mac model, there's no guarantee that all the necessary hardware drivers are included, as you've already discovered with the video drivers defaulting to the firmware 640x480 pixels. It rather sounds as if your eMac doesn't have mouse drivers (which is odd; if you can use the keyboard, you must have basic USB driver support).
Refer to eMac: How to locate the serial number and identify your model to check what model you have. If that model shipped with OS X 10.3.x or 10.4.x, the eMac won't run from 10.2.8 anyway. I prefer Mactracker for looking up what OS version shipped with what Mac model.
Your best bet would be to use a retail (black label) OS X install disc, with an OS X version that post-dates when the eMac was built. Such a retail disc will have the full set of hardware drivers for the supported Macs built up to when the disc was pressed. If your eMac has a DVD-ROM or DVD-RW drive, you can use the current Tiger 10.4, which is faster and more stable than 10.2.8. If your eMac only has a CD drive, you can call the Apple Store and ask about the Media Exchange Program, or use a DVD-equipped Mac and a Firewire cable to install OS X on the eMac via FireWire target disk mode.
You can also call the Apple Store and ask about ordering a replacement set of the discs that originally shipped with the eMac.
You need OS X 9.2.2 to run Classic on an eMac (or to boot directly into OS 9 on 700 / 800 MHz nVidia graphics models). There would've been either an eMac-labeled OS 9.2.2 install CD or Software Restore disc originally with the eMac. You can use a commercial OS 9.2.1 CD to install OS 9 on an eMac, then go to the Apple Downloads site (linked at the top of the Discussions pages) to download the 9.2.2 updater. There are a confusing number of ways to reinstall OS 9, depending on the eMac model and the OS X version; see e.g., OS X: How to Perform Mac OS 9 Clean Install (there are links in that Knowledge Base article to other options).

[SOLVED] CCSM won't start after updating compiz

I just updated compiz, compil-plugins-main, ccsm etc. and ccsm (Compizconfig settings manager) just dont start.
[broi@broi-Archlinux ~]$ ccsm
Info: No sexy-python package found, don't worry it's optional.
Traceback (most recent call last):
File "/usr/bin/ccsm", line 99, in <module>
import compizconfig
ImportError: /usr/lib/python2.7/site-packages/compizconfig.so: undefined symbol: ccsImportFromFile
[broi@broi-Archlinux ~]$
I tried with "python2" or "python3" before I type a .py command (which worked in some issues) but in this one it dont help.
When I try with python 3 -> "python3 /usr/bin/ccsm" I get:
[broi@broi-Archlinux ~]$ python3 /usr/bin/ccsm
File "/usr/bin/ccsm", line 45
if dbus.version < (0, 80, 0):
^
TabError: inconsistent use of tabs and spaces in indentation
[broi@broi-Archlinux ~]$
Thanks.
Solution: Rebuilt the compizconfig-python
UPDATE: Just run update and you will get fixed compizconfig-python.
Last edited by broi (2012-03-23 16:26:25)

Same problem after pacman -Syu (using XFCE).
Not only compiz won't start, my mouse cursor is gone until I open some windows. The window decorations have disappeared (minimize, maximize, close). This is even after removing the fusion-icon from autostart in XFCE and rebooting (afaict, compiz is not running as a process when I list running processes with ps -ef). Also having difficulty switching focus between open windows.
[2012-03-21 14:27] upgraded bash (4.2.024-1 -> 4.2.024-2)
[2012-03-21 14:27] upgraded libcompizconfig (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compizconfig-python (0.8.4-2 -> 0.8.4-3)
[2012-03-21 14:27] upgraded ccsm (0.8.4-2 -> 0.8.4-3)
[2012-03-21 14:27] upgraded compiz-bcop (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compiz-fusion-plugins-main (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compiz-fusion-plugins-extra (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compizconfig-backend-gconf (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded device-mapper (2.02.90-1 -> 2.02.95-1)
[2012-03-21 14:27] upgraded emerald-themes (0.6.0-3 -> 0.6.0-4)
[2012-03-21 14:27] upgraded ffmpeg (20120127-3 -> 20120317-1)
[2012-03-21 14:27] upgraded fusion-icon (20101021-1 -> 20120321-1)
[2012-03-21 14:27] upgraded libtasn1 (2.9-2 -> 2.12-1)
[2012-03-21 14:27] upgraded gnutls (3.0.15-1 -> 3.0.17-1)
[2012-03-21 14:27] upgraded grub2-common (1:1.99-6 -> 1:2.00beta2-2)
[2012-03-21 14:27] upgraded grub2-bios (1:1.99-6 -> 1:2.00beta2-2)
[2012-03-21 14:27] upgraded iproute2 (3.2.0-2 -> 3.2.0-3)
[2012-03-21 14:27] upgraded libdrm (2.4.31-1 -> 2.4.32-1)
[2012-03-21 14:27] upgraded lib32-libdrm (2.4.31-1 -> 2.4.32-1)
[2012-03-21 14:27] upgraded lib32-libice (1.0.7-2 -> 1.0.8-1)
[2012-03-21 14:27] upgraded lib32-libxdmcp (1.1.0-2 -> 1.1.1-1)
[2012-03-21 14:27] upgraded lib32-libxcb (1.8.1-1 -> 1.8.1-2)
[2012-03-21 14:27] upgraded lib32-libx11 (1.4.99.901-1 -> 1.4.99.901-2)
[2012-03-21 14:27] upgraded lib32-libxcomposite (0.4.3-2 -> 0.4.3-3)
[2012-03-21 14:27] upgraded lib32-libxext (1.3.0-1 -> 1.3.1-1)
[2012-03-21 14:27] upgraded lib32-libxinerama (1.1.1-2 -> 1.1.2-1)
[2012-03-21 14:27] upgraded lib32-libxrandr (1.3.2-1 -> 1.3.2-2)
[2012-03-21 14:27] upgraded lib32-libxtst (1.2.0-2 -> 1.2.1-1)
[2012-03-21 14:27] upgraded lib32-libxxf86vm (1.1.1-2 -> 1.1.2-1)
[2012-03-21 14:27] upgraded lib32-util-linux (2.20.1-1 -> 2.21-1)
[2012-03-21 14:27] upgraded libftdi (0.19-1 -> 0.20-1)
[2012-03-21 14:27] upgraded linux (3.2.11-1 -> 3.2.12-1)
[2012-03-21 14:27] upgraded live-media (2012.02.29-2 -> 2012.03.20-1)
[2012-03-21 14:27] upgraded lvm2 (2.02.90-1 -> 2.02.95-1)
[2012-03-21 14:27] upgraded mpg123 (1.13.4-2 -> 1.13.6-1)
[2012-03-21 14:27] upgraded neon (0.29.6-3 -> 0.29.6-4)
[2012-03-21 14:28] upgraded openssl (1.0.0.h-1 -> 1.0.1-1)
[2012-03-21 14:28] upgraded psmisc (22.15-1 -> 22.16-1)
[2012-03-21 14:28] upgraded systemd-arch-units (20120311-1 -> 20120317-1)
[2012-03-21 14:28] upgraded vlc (2.0.0-8 -> 2.0.1-1)
[2012-03-21 14:28] upgraded xf86-input-evdev (2.7.0-1 -> 2.7.0-2)
Last edited by David Batson (2012-03-21 21:10:35)

[SOLVED] Arch won't start, uefi lenovo B570

Hi, i am trying to install arch on my lenovo B570 laptop. I downloaded the latest iso from the site and used usb universal installer to create usb install media. In the boot options of my laptop i pick the usb as the first boot device and run it. I can see the efi menu and i pick arch_x86_64, but it seems to me that gummiboot is not firing. After this i only see black screen, and the usb stops blinking. After a while (3-4 min) the lap-top restarts. In the options of my bios i can't find anything like secure boot option, i have read on the forum similar issues and someone said that this should be disabled, but i don't see any option like so. My bios is very primitive, there is only boot order to set and nothing else.
Thanks!
Last edited by stefo (2013-01-02 12:08:39)

I prepared the usb inside Lubuntu, i used gpadted to create new msdos partition table (mbr) and removed any partitions.
I created new partition FAT32 with label "ARCH_201212" and formated the drive. I created two folders inside /mnt, one "iso" and one "usb". I mounted the usb and iso like this:
mount /dev/sdb1 /mnt/usb
mount /home/stefo/Downloads/archlinux-2012.12.01-dual.iso /mnt/iso
Then copied everything from the iso to the usb:
cp -r /mnt/iso /mnt/usb
Unmounted and synced:
umount /mnt/{usb,iso}
sync
EDIT: I also tried with fdisk...
When i try to create new partition table with fdisk on my usb i get this:
Building a new DOS disklabel with disk identifier 0x601ad71e.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
EDIT: When i create new partition table and new FAT32 partition with fdisk, and then try to mount like this:
mount /dev/sdb1 -t vfat /mnt/usb
I get this, and the usb is not mounted:
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
dmesg | tail
[ 1678.604687] FAT-fs (sdb1): bogus number of reserved sectors
[ 1678.604696] FAT-fs (sdb1): Can't find a valid FAT filesystem
EDIT: My mistake sorry, i didn't used mkfs.vfat -F32 to format the partition, i forgot to do that
EDIT: When i try this, i get Permission denied:
sudo awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf | xargs mkfs.vfat /dev/sdb1 -n
EDIT: I don't know why the previous command didn't worked but this one worked:
sudo mkfs.vfat -F32 -n `awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf` /dev/sdb1
Just to check i open gparted and i can see my usb /dev/sdb, one partition sdb1 FAT32 label: ARCH_201212. I copied the content from the iso to the usb, unmounted both the iso and usb folders and sycned, and again i get black screen..
Last edited by stefo (2013-01-02 10:53:10)

[Solved] - VirtualBox XP guest Hangs After Hibernating

Pausing before hibernating doesn't help either.
http://forums.virtualbox.org/viewtopic.php?f=7&t=26622
Disabling Vt-x extension solved it.
I'm not sure about the performance impact. But so far, it isn't noticeable.
From what I've read, Vt-x with nested paging can potentially improve performance dramatically. But at this point, reports to the contrary do exist.
Hope this helps anyone facing a similar issue.

Hey this does not work for me. I still get 800x600 on going FS. I installed guest additions and are loaded fine. Anything else to do? I am running Archbang(Arch Linux+Openbox) as guest on Chakra Arch Host. My host resolution is 1360x768 but guest has 800x600
Last edited by chakra-user (2010-04-11 03:03:47)

IMac won't respond after being put to sleep/turned off.

I've been dealing with this problem for a few months now. If I put my hard disk to sleep or turn my computer off, it doesn't respond when I try to wake it back up or turn it back on. It will make a continuous clicking noise (no there's no disc caught in it the CD drive) and the only way for me to actually restart is to run the Archive and Install feature on the install disc. If I try to simply restart it, I get a blue screen with a folder-with-a-question-mark icon where the Apple icon should be during loading. I've had to skip putting the hard disk to sleep at all but I do just put the display asleep, and it wakes up fine after that.
I've noticed a lot of crashes with Safari and other things like games recently too. I'm usually able to just force quit the program and restart it though. I have a Logitech mouse and an Apple USB keyboard that I use with it and I've tried unplugging and replugging those, as well as trying other keyboards/mice with it to see if it's a rare hardware issue. The only thing I haven't checked yet is the RAM that my boyfriend installed for me a couple years ago.
Although, I've noticed the last couple times I've had to do that, I've had to wait to use the install disc. If I do it too soon after it's stopped responding then my hard drive doesn't show up on the selection menu and the Archive and Install option doesn't come up. I have to let it sit a little while before I can do it.
I'm not at home at the moment to see which exact model/generation it is, but I have the one with the flatpanel screen and built-in iSight. I bought it back in June 2006. I'm currently using Leopard on it (not sure which version though).
Could one of my boards be worn out? Or could the additional RAM be causing problems? Any advice or suggestions are welcome. I'd like try checking everything I can myself before having to take it in to an Apple store. Thanks!

I bought it back in June 2006.
If it was purchased new, you are better off posting in another iMac forum. This is for the G4 iMacs with the articulated display arm and the dome-shaped base. It's not your fault--the forum labeling is, at best, non-intuitive and confuses plenty of posters.
Look at "About this Mac" in your Apple menu and note the processor type. If it says "G5" then your forum is here:
http://discussions.apple.com/category.jspa?categoryID=134
If it says your processor is "Intel," then your forum is here:
http://discussions.apple.com/category.jspa?categoryID=189

[SOLVED] Arch won't mount my hard drives correctly, problems at boot.

Sometimes (only sometimes) Arch Linux will have an error during bootup because my Linux drive gets mounted as sdb instead of sda. My NTFS Sata storage drives gets mounted in its place as sda.
When this happens, Arch Linux will stop booting at the "checking filesystems" step:
:: Checking Filesystems [BUSY]
/dev/sda3:
The superblock could not be read or does not describe a corect ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAIL]
**************** FILESYSTEM CHECK FAILED ****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
Give root password for maintenance
(or type Control-D to continue):
And from there i have to remount my drives manually or restart the computer. Everytime I start the computer, I simply have to hope that my Linux drive will mount as sda. It's totally hit and miss.
Now, I know that my superblock is not corrupt. fsck is failing because it is looking for my linux filesystem on sda. It is encountering my NTFS Sata drive on sda instead of the expected Linux ext filesystem.
So how do I know that this is happening?
Well, after giving the root password, it shows the root prompt
[root@(none) ~]#
and i proceed to use the lshw command to see what's up with the drives:
[root@(none) ~]# lshw -short | grep /dev/
/0/6/0.0.0 /dev/sdb disk 120GB WDC WD1200JB-00E
/0/6/0.0.0/1 /dev/sdb1 volume 101MiB Linux filesystem partition
/0/6/0.0.0/2 /dev/sdb2 volume 258MiB Linux swap volume
/0/6/0.0.0/3 /dev/sdb3 volume 7506MiB EXT4 volume
/0/6/0.0.0/4 /dev/sdb4 volume 104GiB EXT4 volume
/0/6/0.1.0 /dev/sdc disk 81GB Maxtor 6Y080P0
/0/6/0.1.0/1 /dev/sdc1 volume 76GiB Windows NTFS volume
/0/8/0.0.0 /dev/sda disk 640GB Hitachi HDT72106
/0/8/0.0.0/1 /dev/sda1 volume 596GiB Windows NTFS volume
So, clearly, this shows that my Linux drive has gotten mounted as sdb and my NTFS Sata drive has gottem mounted as sda. It's totally random: sometimes they mount vice versa and the system boots just fine.
When Arch does happen to mount itself properly as sda and the system starts successfully, then the lshw command shows this:
[root@(none) ~]# lshw -short | grep /dev/
/0/6/0.0.0 /dev/sda disk 120GB WDC WD1200JB-00E
/0/6/0.0.0/1 /dev/sda1 volume 101MiB Linux filesystem partition
/0/6/0.0.0/2 /dev/sda2 volume 258MiB Linux swap volume
/0/6/0.0.0/3 /dev/sda3 volume 7506MiB EXT4 volume
/0/6/0.0.0/4 /dev/sda4 volume 104GiB EXT4 volume
/0/6/0.1.0 /dev/sdb disk 81GB Maxtor 6Y080P0
/0/6/0.1.0/1 /dev/sdb1 volume 76GiB Windows NTFS volume
/0/8/0.0.0 /dev/sdc disk 640GB Hitachi HDT72106
/0/8/0.0.0/1 /dev/sdc1 volume 596GiB Windows NTFS volume
The above correctly mounted format shows the drives in the same order as my Hard Disk boot priority in BIOS as well as in the same order as during the initial drive detection directly following the memory test (don't know if it has anything to do with it though).
So my question is this. How do I ensure that Arch Linux mounts itself as sda ALL of the time, and not randomly?
Or should I remove my sda entries in etc/fstab and let Arch determine where my Linux filesystems are? If so, how?
It's interesting to note that GRUB is set to boot Arch Linux from hd0, which should be sda.
It's also intriguing to note that if I take out my Sata drive, I never encounter this problem.
Last edited by trusktr (2010-06-15 07:49:31)

Thanks kgas, here's what i found out so far:
Alright so after rebooting, this is what i determined:
When Linux mounts the drives incorrectly (take note of the parts in bold, the short numbers are NTFS filesystems, long numbers the Linux filesystems):
[trusktr@rocketship ~]$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Jun 14 21:08 01CA836D8BE82040 -> ../../[b]sdc1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 0ddf0e41-e7e6-4af5-b0e9-bc79a91b12eb -> ../../[b]sdb1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 92b88528-dd0f-4c1b-bcce-54084ef2aceb -> ../../[b]sdb4[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 C838CF5838CF4462 -> ../../[b]sda1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 cdb33de5-0100-4c5f-a9b1-5c1a444e6eac -> ../../[b]sdb3[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 d0a5d49d-169d-43ce-af0f-216dc4a9f604 -> ../../[b]sdb2[/b]
So an NTFS filesystem is mounted in sda instead of the Linux filesystem
When Linux mounts everything properly:
[trusktr@rocketship ~]$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Jun 14 21:08 01CA836D8BE82040 -> ../../[b]sdb1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 0ddf0e41-e7e6-4af5-b0e9-bc79a91b12eb -> ../../[b]sda1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 92b88528-dd0f-4c1b-bcce-54084ef2aceb -> ../../[b]sda4[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 C838CF5838CF4462 -> ../../[b]sdc1[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 cdb33de5-0100-4c5f-a9b1-5c1a444e6eac -> ../../[b]sda3[/b]
lrwxrwxrwx 1 root root 10 Jun 14 21:08 d0a5d49d-169d-43ce-af0f-216dc4a9f604 -> ../../[b]sda2[/b]
This doesn't tell us much except that I indeed do have uuid's for all the drives.
So, i guess as kgas said, i probably need to use the uuid in fstab so that Linux always knows which hard drive is the linux drive! In that case, only the uuid for the Linux drive will be necessary. For the other drives it wouldn't matter so much i guess since they don't contain the operating system.
Alright, i'll be back to determine if this fixes it!
Last edited by trusktr (2010-06-15 06:41:25)

[SOLVED] X won't start after update

I'm running Arch inside a virtual machine, with Virtualbox.
I ran 'sudo pacman -Syu' and let it install everything. It updated a bunch of xorg-* packages, among a few other things, and then I rebooted. Now it seems like X has stopped working. Normally I use SLiM for starting X, but SLiM itself isn't starting up. I tried 'startx' manually but that didn't work either. I can get into a normal CLI-environment just fine though.
Here are pacman.log: http://ix.io/4MK and Xorg.0.log: http://ix.io/4MJ
I notice the errors in Xorg.0.log but I'm not sure what to make of them.
I'm not sure what else to add here, I hope I'm not missing something obvious.
Last edited by CrashLog (2013-03-18 20:34:33)

I had this problem when I similarly made this update. I'm running Arch on a Dell Inspiron 1100, after the update X wouldn't start. I attempted to roll back to previous versions (as stipulated here and seeing as I had them in my cache) to no avail (gave up in frustration). Finally, I was able to get into X in two different ways:
First, I removed xf86-video-intel and installed xf86-video-vesa, when I rebooted I added the i915.modeset=0 parameter to the boot options at runtime in GRUB. For whatever reason X wouldn't load if I allowed the modeset to happen (bigger console area). This enabled me to boot into a slower X which I was still dissatisfied with, but at the very least it allowed me to isolate the problem as the intel driver as everything else is fully up to date.
Second, I created /etc/X11/xorg.conf.d/20-intel.conf with the following contents:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "NoAccel" "True"
EndSection
This also meant switching back to xf86-video-intel (instead of using xf86-video-vesa) for X. I tried both the "uxa" (supposed to be default) and "sna" options for "AccelMethod" and neither worked, only explicitly using the "NoAccel" "True" option allowed me to get X to function anew. In this manner I don't have to disable the modeset option during boot in GRUB and I'm still utilizing the latest intel driver.
The only inference (albeit perhaps misguided or ignorant) I can make is that something changed in UXA that broke how it worked before (I say this because this laptop is too old to support SNA).

[SOLVED] Arch won't respond after hibernation

Similar Messages

Maybe you are looking for