Ideapad A10 boot on linux

hello a10 users i wonder if somebody has succeeded to boot on linux on this machine .
i will be very happy to do it also
dont hesitate to contact me [email protected] or on this forum
Moderator note; e-mail address removed to stop the spambots getting it

Slackware Linux 13.37 installed on Lenovo Ideapad A10. Contains a big set of standard packages and LibreOffice. https://drive.google.com/file/d/0Byyv_ivdk-JBWU82OGw0MURSOTQ/view?usp=sharing It's a compressed image of bootable Micro-SD card. After decompressing the size is near 8GB, then we need a card with capacity at least 16GB (preferred 32GB C10 class). - download and decompress above file - write the image to Micro-SD - optionally resize the partition (fdisk, resize2fs) - put a card into Lenovo A10 and reboot Enjoy, GaPiK

Similar Messages

Dual boot kali linux with windows 8

i have ideapad y510p and i want to dual boot kali linux with windows 8
i want a full guide to do it please !!help!!!

Hello,
if you got problems with the kernel, you can try backbox-linux. The kernel there is newer. It is based on Ubuntu 12.04 LTS.
Have a nice day
thoschi
LENOVO IDEAPAD Z710 59403383,i7-4700MQ,8 GB DDR3-RAM,1.920 x 1.080 Pixel,NVIDIA® GeForce® GT 740M,Hybrid (1 TB S-ATA + 8GB SSD)

Tutorial - How to triple boot OSX, Linux and Windows 8.1 with a shared Data Partition without any third party Win / OSX softwares

This is not a question, but rather a personal guide that has proved to be running successfully.
I would like to thank numerous sources, including Christopher Murphy's suggestions at:
Re: Repairing Boot Camp after creating new partition
Before proceeding, there are certain concepts needs to know:
Why Boot Camp does NOT allow further partitioning of drives after Windows has installed?
Answer: Because the way Apple configures the Mac to be recognized as non UEFI capable system on Windows.
Quote from Christopher Murphy based on the above line:
However, Windows on Macs right now use CSM-BIOS mode in Mac firmware that presents BIOS to Windows rather than EFI. Windows thinks it's on a BIOS computer, and therefore mandates the use of MBR for boot disks, rather than GPT. So that's why we have this hybrid MBR+GPT approach on Mac with Windows on it. You inherit the limitations of MBR, which is four primary partitions.
So what does it means?
It means that OSX + EFI + Recovery HD + Boot Camp partition = 4 primary partitions and thus any attempt to modify the disk will render booting issues of either system.
For more info on GPT (GUID Partition Table disks VS Master Boot Record or MBR in short, you may visit: http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx)
So, how to overcome it?
The general guideline is to install ALL GPT ready OS first then create a Data partition, before installing Windows (Which is again, NOT supported GPT due to EFI configuration by Apple where end-users are not able to modify it).
Interestingly, since Mac Pro 2013 Late supports only Windows 8 and above, thus it is not known if this CSM-BIOS applies to it or not.
Do take note that GPT disks in Windows can only be booted when the system meets the 2 requirements:
http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx#gpt_faq_win7_boot
1) Windows x64 version (Which is a must for newer Macs. If you cannot go to Boot Camp 5, then you need Windows 7 x86 or 32bit version)
2) UEFI system. However, Windows sees all Macs (With the possibility of Mac Pro 2013 Late is an exception. To be determined) as BIOS, or rather NON-UEFI system.
In short, booting on GPT disks is not possible for Mac in Windows.
Summary,
It is tested that a combination of the following will not work:
- OSX + Windows + Linux
- Windows + OSX + Linux
- Windows + Linux + OSX
Usually it can create the system un-bootable or OSX refused to install due to the system does not recognize such partitions and / or Disk Utility refused to format a free space. An example screen-shot is provided below:
The error message is shown as
Title: "Failed to erase volume" Message: "Failed to wipe volume, as an error occurred: MediaKit has reported that the device does not have enough free space to execute the requested operations."
The second thing is about the preparations we need.
1) 1X Windows 7 or 8 DVD or USB thumbdrive
1A) If you uses a DVD to install, you will need another thumbdrive to load the BootCamp drivers for Windows as well as may requires an external DVD drive for newer Macs
2) 1X Linux DVD of your choice. Personally I choose Fedora 20.
So ready? Let's go.
1. Using Disk Utility, shrink the OSX's partition size to what is needed. For me, I give OSX 150GB. Do NOT create any new partition.
Disk Utility should see something like below whereby only OSX partition is left with desired disk space. The remaining space are to be unused disk space for the moment.
Note: Click on the top most item that should start with the size of your HDD / SSD. Then clicked on "Partition" and specify the desired OSX size. Hit "Apply" after that.
2: Download Boot Camp drivers only via Boot Camp Assistant. The USB thumbdrive shall be used later after Linux's installation.
Boot Camp Assistant should see this:
I have only selected "Download latest Windows Support Files from Apple"
3. Insert Linux DVD, reboot Mac into EFI mode (The left most first "EFI mode").
Note 1: Before rebooting, please plugged in an Ethernet adapter because Wi-Fi drivers is not installed.
Note 2: For Thunderbolt adapters, it must be plugged in before reboot as hot-swapping is not supported under Linux. More on the tips at the end of this article.
Note 3: Press and hold "Option" after the screen turns black. Release Option key after you see the image as below:

For the unfortunate part that did not make it on time to edit the images:
9. Install the Windows Support software from your CD/USB drive to gain full functionality of your computer. Reboot and go to Windows again.
Note 1: You may choose to eject disc at this point of time. For Apple SuperDrive users, you will need to wait until the drivers (i.e. Boot Camp support files) is installed and rebooted before ejecting is reasonably possible (As I failed to figured out how to right click without the drivers)
Note 2: Unlike Windows 7 on KBase article TS4599 Keyboard/trackpad inoperative, black screen, or alert messages when installing Windows 7, USB stick can be plugged in after the Windows installation is done. This is because Windows 7 (And probably Windows 7 with SP1 DVD) does not have a built in USB 3 drivers when it was released back in 2009 where USB3 has not arrived then.
Note 3: Due to TPM, Bitlocker is not supported without the use of thumbdrives.
10. Using Disk Management to determine the given drive letter for the DATA partition (DO NOT DELETE and RECREATE partition or else you can goodbye to booting Linux and OSX). Disk Management will not allow you to format it as exFAT / FAT32 in graphical way.
Note: You may remove or modify some of the disk letters in Disk Management. However, do NOT remove / modfify the drive letter for the partition with 200MB size in HFS. This is because it will disallow booting of Linux and neither could Windows nor OSX can do anything EXCEPT to reinstall Linux only.
11. Open Command Prompt in Administrator Mode (Important!!), and key in the following command:
format F: /FS:exFAT
Give this volume a label after it has successfully formatted before hitting "Enter" again.
Note: Mine Data partition was assigned as F drive. Please make necessary adjustment to "F:" should your Data partition is assigned to other letters.
12. After that, Setup your Data partition structure as you like.
Tip: Minimally create the important folders such as:
- Music
- Documents
- Movie (Videos)
- Downloads
- Pictures
All these folders are commonly used by the 3 OSes. I do NOT recommend changing of /home (OSX and / or Linux) and / or user home directory (Windows) either partially or as a whole.
This is because of compatibility issue.
On a side note, iTunes Media Library used in OSX and Windows are NOT able to be use interchangably due to hard-coded path used.
13. Useful troubleshooting in Fedora / Linux:
With references to these:
http://chaidarun.com/fedora-mbp
http://anderson.the-silvas.com/2014/02/14/fedora-20-on-a-macbook-pro-13-late-201 3-retina-display/
http://unencumberedbyfacts.com/2013/08/16/linux-on-a-macbook-pro-101/
I would like to highlight a few important points:
1) Wi-Fi driver:
http://rpmfusion.org/Configuration
Note 1: The sound driver should be installed at Out of Box Experience. However, the Wi-Fi is not.
Note 2: Install both free and non-free repository. By the way, some other software like VLC can only be found after the Free Repository is installed.
Search for "akmod-wl" in Gnome-Package-Installer in order to install Wi-Fi drivers
Note 3: For those who do not have Ethernet adapters and their Mac does NOT have a built-in Ethernet port, it is recommended to get one. This is because Fedora 20 does not have a good support for iPhone USB tethering. Unsure for Andriod / Blackberry / Windows Phone users.
2) Grub Menu:
It will show several options to boot into OSX, even of the capability to boot into x86 or x64 mode. However, neither of them is bootable except Linux and the rescue.
Hence, it is recommended to remove the items by hand in this file:
/boot/efi/EFI/fedora/grub.cfg
Command to be used:
"sudo gedit /boot/efi/EFI/fedora/grub.cfg"
Parts to be removed:
- For any extra kernels, delete the target entry by locating the line "menuentry" under "/etc/grub.d/10_linux" sector to one line above the next "menuentry".
It is recommended to keep one main kernel, and one recovery at the minimal.
- For other OS, delete all the entry (Since neither it can works) under "/etc/grub.d/30_os-prober" sector without removing the lines starts with ###.
Auto Mount exFAT partition:
- After installing extra packages for exFAT support (Since it is not supported by Fedora 20 from a default installation), you may wish to edit "/etc/fstab" in order to mount the exFAT partition during boot time.
Command to be used:
"sudo gedit /etc/fstab"
Add the following line in gedit:
UUID=702D-912D /run/media/Samuel/DATA exfat defaults 1 2
Note 1: For DATA partition, OSX & Boot Camp partition, Fedora defaults mounts under: "/run/medua/<Username with case sensitive>/<Partition Label Name>"
Note 2: UUID is unique ID. You can find out the UUID by:
Step 1: First determine the DATA partition number:
"sudo gdisk /dev/sda"
Step 2: Determine the UUID of this partition number:
"sudo blkid /dev/sda8"
Reference 1: http://manpages.courier-mta.org/htmlman5/fstab.5.html
Reference 2: http://liquidat.wordpress.com/2007/10/15/short-tip-get-uuid-of-hard-disks/
3) Overheating CPU
Solution is to issue the following command in Linux terminal: su -c "echo -n 1 > /sys/devices/system/cpu/intel_pstate/no_turbo"
4) System resumes immediately after suspend
Solution is to issue the following command in Linux terminal: su -c "echo XHC1 > /proc/acpi/wakeup"
5) What does not works well out of box:
- Both GNOME and KDE's fonts are too small to be readable for out of box experience. Additional configuration is a need. (Some of the info can be found on "More Tips" later)
- Thunderbolt hotplugging is NOT supported under Windows and Linux so far. Neither FaceTime HD camera works as well.
- The red light in Headphone jack is always on. I do not have luck in switching off the light without losing the sound.
Note 1: It is determined that the module "snd_hda_intel" is used by both cards (HDMI and normal output)
Note 2: It is also known that blacklisting it can switch off the redlight at the price of muting the system.
Note: Based on this article, http://support.apple.com/kb/TS1574
A Mac (Except Mac Pro) needs servicing when there is a red light while the system fails to detect internal speakers. However, this article does NOT applies to this issue.
5A) More Tips:
Install gnome-tweak-tool for more customization
Search for: "gnome-package" to install:
Install Gnome Package Installer for advanced package repository
Install Gnome Package Updater for advanced updates to be install (Whereby Fedora's App Store alike might not show the relevant updates)
14. Verify if disk is still GPT:
Use Gdisk to determine if the disk is pure GPT:
http://ubuntuforums.org/showthread.php?t=1742682
Command: sudo gdisk -l /dev/sda (The entire hard drive)
You should see the MBR is "Protective" instead of anything else.
15. Congrats, the system is ready for triple boot. (I forgot to eject my Windows DVD when the photo was taken)
Note 1: You cannot set the default startup disk in Linux due to the lack of Boot Camp Control Panel in Linux.
Neither is changing startup disk recommended in Windows due to the inability to display correctly.
For me, I click "Cancel" whenever I am on this tab (Feel free to make other Boot Camp adjustments in other tabs).
Only OSX I know that can show the startup disk options correctly.
Note 2: For some reason, OSX likes to auto mount the EFI partition everytime it boots up. It is not known to have any issue for ejecting other disks or mounting disks via Disk Utility.
Note 3: It is not determined if any Firmware or System upgrades will cause issues. It is only known that all 3 OS's regular updates should not be an issue.
System Updates excludes Mac OSX 10.9.3 updates to OSX 10.9.4 type as I had done it on a OSX 10.9.4 Mac or Windows 8.1 to Windows 8.1 Update 1 since my Windows DVD comes with Update 1.
System Upgrades refers to OSX Mavericks to Yosemite, Fedora 20 to Fedora 21, Windows 8.1 Update 1 to Windows 8.2 / Windows 9 for that matter.
Note 4: Reset SMC and / or PRAM will NOT affect your ability to boot any of the OS (OSX, Recovery HD, Fedora & Windows 8)
Yup, that is it!

[WORKAROUND] rEFInd doesn't boot new linux 3.8.3-2

Hello!
Today I updated linux to 3.8.3-2 and rEFInd stopped booting. Instead I was stuck with the rEFInd screen (the one saying: booting vmlinux-linux).
Before you ask: Yes, I did copy the new kernel and initramfs to /boot/efi/EFI/arch by doing
sudo cp /boot/vmlinuz-linux /boot/efi/EFI/arch/vmlinuz-arch.efi
sudo cp /boot/initramfs-linux.img /boot/efi/EFI/arch/initramfs-arch.img
sudo cp /boot/initramfs-linux-fallback.img /boot/efi/EFI/arch/initramfs-arch-fallback.img
as I always do.
I solved the problem by starting from a Live-CD and downgrading the kernel. Does anyone know what the issue is?
Any help is much appreciated!
Last edited by mjb (2013-03-29 17:35:36)

cfr wrote:Are you sure this is the same problem? I thought that issue only affected more recent kernels but I can reproduce this failure with the LTS kernel. I have not had the issue at all with 3.7.* kernels - this is the first time it has happened.
The 3.8.3-2 reported by the OP is pretty recent, in my book. The thread to which I linked specifies that the problem began with certain 3.7.x kernels.
With rEFInd, with both the standard and fallback options for the current kernel, it hangs mid line. That is, it prints almost all of the usual loading line up to "initram" and then stops mid-word.
That's new, and suggests that you may be seeing something else -- either your kernel options are being truncated somehow (probably in a rEFInd bug) or there's a firmware bug that's causing the system to hang while rEFInd is displaying text. (rEFInd uses a system call called Print() to do this, so a hang mid-word suggests an EFI bug.) It might be best to start a new thread for this problem if you want to pursue it, if it's new.
With rEFInd and the LTS kernel, with both standard and fallback options, it hangs in the same place but then a message in yellow is overlaid which says "Error: unsupported while loading vmlinuz-linux-ltx".
The "unsupported" message means that the kernel lacks an EFI stub loader.
If it is a kernel bug, it is in the 3.0.69 as well (but it hasn't appeared in any other current or LTS kernel for me).
Unless it's been patched with a back-port of the EFI stub loader, I wouldn't expect 3.0.69 to boot directly via rEFInd or gummiboot.

[SOLVED] Cannot boot with linux-3.5.3

Edit: Solved, as explained here.
Hello,
after upgrading to linux-3.5.3-1 my boot stopped at
:: running early hook [udev]
I tried upgrading to grub-bios-2.00, removing any customization I had in modprobe.conf and /etc/modules-load.d as well as removing the only module (radeon) from /etc/mkinitcpio.conf (obviously followed by mkinitcpio -p linux), which made me go on to
:: waiting for udev uevents to be processed [BUSY]
I'm not sure it's an actual progress.
My /etc/udev/rules.d is empty and /usr/lib/udev/rules.d only contains pacman-tracked stuff.
I enabled some debugging as described here but couldn't get anything useful - is there any way for such messages to be logged somewhere, so they can be pasted here?
I ended up downgrading to linux-3.4.9, which boots fine.
Any idea to troubleshoot this?
cat /etc/rc.conf
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond dbus @networkmanager kdm @cpufreq sshd @cups @supervisor)
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=
# address=
# netmask=
# gateway=
cat /etc/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=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency 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 any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/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
# '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 a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
pacman -Qo /usr/lib/udev/rules.d/*
/usr/lib/udev/rules.d/10-dm.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/10-vboxdrv.rules is owned by virtualbox 4.1.20-2
/usr/lib/udev/rules.d/11-dm-lvm.rules is owned by lvm2 2.02.97-1
/usr/lib/udev/rules.d/13-dm-disk.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/40-gphoto.rules is owned by libgphoto2 2.4.14-1
/usr/lib/udev/rules.d/40-hpet-permissions.rules is owned by jack2 1.9.8-2
/usr/lib/udev/rules.d/40-usb-media-players.rules is owned by media-player-info 17-1
/usr/lib/udev/rules.d/42-usb-hid-pm.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/50-udev-default.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/53-sane.rules is owned by sane 1.0.23-1
/usr/lib/udev/rules.d/60-cdrom_id.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-pcmcia.rules is owned by pcmciautils 018-4
/usr/lib/udev/rules.d/60-persistent-alsa.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-input.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-serial.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage-tape.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-v4l.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-rfkill.rules is owned by rfkill 0.4-5
/usr/lib/udev/rules.d/61-accelerometer.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules is owned by gnome-bluetooth 3.4.2-1
/usr/lib/udev/rules.d/64-md-raid.rules is owned by mdadm 3.2.5-2
/usr/lib/udev/rules.d/65-kvm.rules is owned by qemu 1.1.1-1
/usr/lib/udev/rules.d/69-cd-sensors.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/69-libmtp.rules is owned by libmtp 1.1.4-1
/usr/lib/udev/rules.d/70-infrared.rules is owned by v4l-utils 0.8.8-1
/usr/lib/udev/rules.d/70-power-switch.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-uaccess.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-udev-acl.rules is owned by consolekit 0.4.6-4
/usr/lib/udev/rules.d/71-seat.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/73-seat-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-net-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-probe_mtd.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-tty-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/77-nm-olpc-mesh.rules is owned by networkmanager 0.9.4.0-6
/usr/lib/udev/rules.d/78-sound-card.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-drivers.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-udisks.rules is owned by udisks 1.0.4-5
/usr/lib/udev/rules.d/80-udisks2.rules is owned by udisks2 1.94.0-2
/usr/lib/udev/rules.d/85-usbmuxd.rules is owned by usbmuxd 1.0.8-1
/usr/lib/udev/rules.d/90-alsa-restore.rules is owned by alsa-utils 1.0.25-3
/usr/lib/udev/rules.d/90-libgpod.rules is owned by libgpod 0.8.2-6
/usr/lib/udev/rules.d/90-pulseaudio.rules is owned by pulseaudio 2.1-1
/usr/lib/udev/rules.d/95-cd-devices.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/95-dm-notify.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/95-keyboard-force-release.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-keymap.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-udev-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-csr.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-hid.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-wup.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules is owned by bluez 4.101-1
/usr/lib/udev/rules.d/99-systemd.rules is owned by systemd-tools 188-2
cat /var/log/pacman.log
[2012-08-28 12:27] Running 'pacman -Sy'
[2012-08-28 12:27] synchronizing package lists
[2012-08-28 14:51] Running 'pacman -S -u'
[2012-08-28 14:51] starting full system upgrade
[2012-08-28 14:53] upgraded gc (7.2.c-1 -> 7.2.d-1)
[2012-08-28 14:53] >>> Updating module dependencies. Please wait ...
[2012-08-28 14:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-28 14:53] ==> Building image from preset: 'default'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [autodetect]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] ==> Building image from preset: 'fallback'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] upgraded linux (3.4.9-1 -> 3.5.3-1)
[2012-08-28 14:53] upgraded lirc-utils (1:0.9.0-22 -> 1:0.9.0-26)
[2012-08-28 14:53] In order to use the new version, reload all virtualbox modules manually.
[2012-08-28 14:53] upgraded virtualbox-modules (4.1.20-1 -> 4.1.20-3)
[2012-08-28 14:59] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.3fb/google-chrome-21.0.1180.81-1-x86_64.pkg.tar.xz'
[2012-08-28 14:59] upgraded google-chrome (21.0.1180.57-1 -> 21.0.1180.81-1)
[2012-08-28 15:00] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.MgI/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:00] Running 'pacman -Sy'
[2012-08-28 15:00] synchronizing package lists
[2012-08-28 15:01] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.Vic/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:01] upgraded tunlr (0.1.4-1 -> 0.1.5-1)
[2012-08-28 17:34] Running 'pacman -S extra/kdeedu-kmplot'
[2012-08-28 17:34] installed kdeedu-kmplot (4.9.0-1)
[2012-08-29 10:20] Running 'pacman -Syu'
[2012-08-29 10:20] synchronizing package lists
[2012-08-29 10:20] starting full system upgrade
[2012-08-29 11:07] Running 'pacman -S grub-bios'
[2012-08-29 11:07] removed grub (0.97-21)
[2012-08-29 11:07] Generating grub.cfg.example config file...
[2012-08-29 11:07] This may fail on some machines running a custom kernel.
[2012-08-29 11:08] done.
[2012-08-29 11:08] installed grub-common (2.00-1)
[2012-08-29 11:08] installed grub-bios (2.00-1)
[2012-08-29 11:48] Running 'pacman -Sy'
[2012-08-29 11:48] synchronizing package lists
[2012-08-29 11:48] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -Sy'
[2012-08-29 12:11] synchronizing package lists
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -S -u'
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:15] upgraded firefox (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded firefox-i18n-it (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded gsmartcontrol (0.8.7-1 -> 0.8.7-2)
[2012-08-29 12:15] upgraded libwbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded smbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded samba (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded sane (1.0.22-9 -> 1.0.23-1)
[2012-08-29 12:15] upgraded syslinux (4.05-6 -> 4.05-7)
[2012-08-29 12:15] upgraded thunderbird (14.0-1 -> 15.0-1)
[2012-08-29 12:15] upgraded thunderbird-i18n-it (14.0-1 -> 15.0-1)
[2012-08-29 12:15] -> You can now set custom file descriptor ulimits for Tor in
[2012-08-29 12:15] -> "/etc/conf.d/tor" using the "TOR_MAX_FD" variable.
[2012-08-29 12:15] upgraded tor (0.2.2.37-1 -> 0.2.2.38-1)
[2012-08-29 12:56] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.K10/downgrade-3.0-1-any.pkg.tar.xz'
[2012-08-29 12:56] installed downgrade (3.0-1)
[2012-08-29 12:57] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:04] Running 'pacman -U /var/cache/pacman/pkg/virtualbox-modules-4.1.20-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -R virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rd virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rdd virtualbox-modules'
[2012-08-29 13:06] removed virtualbox-modules (4.1.20-3)
[2012-08-29 13:06] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:06] >>> Updating module dependencies. Please wait ...
[2012-08-29 13:06] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-29 13:06] ==> Building image from preset: 'default'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [autodetect]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:06] -> Running build hook: [sata]
[2012-08-29 13:06] -> Running build hook: [resume]
[2012-08-29 13:06] -> Running build hook: [filesystems]
[2012-08-29 13:06] -> Running build hook: [usbinput]
[2012-08-29 13:06] -> Running build hook: [fsck]
[2012-08-29 13:06] ==> Generating module dependencies
[2012-08-29 13:06] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Image generation successful
[2012-08-29 13:06] ==> Building image from preset: 'fallback'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:07] -> Running build hook: [sata]
[2012-08-29 13:07] -> Running build hook: [resume]
[2012-08-29 13:07] -> Running build hook: [filesystems]
[2012-08-29 13:07] -> Running build hook: [usbinput]
[2012-08-29 13:07] -> Running build hook: [fsck]
[2012-08-29 13:07] ==> Generating module dependencies
[2012-08-29 13:07] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-29 13:07] ==> Image generation successful
[2012-08-29 13:07] upgraded linux (3.5.3-1 -> 3.4.9-1)
[2012-08-29 14:47] Running 'pacman -Sy'
[2012-08-29 14:47] synchronizing package lists
[2012-08-29 14:49] Running 'pacman -S -u'
[2012-08-29 14:49] starting full system upgrade
Last edited by thujone (2012-09-19 12:18:51)

because the report opener said that those freezes fixed with the 'futex' patch (included in 3.14-5).
As he says:
for those who have again problems despite the patch it means probably that there are another bugs further in the source code of kernel 3.14, bugs who are not necessarily related to the "futex problem"
i will try a clean profile, thanks.
Last edited by tritonas00 (2014-04-16 13:22:51)

T400s Linux/Windows dual boot with Linux from Esata Flash Drive

This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
To boot from the esata drive I had to make the following changes in the bios
    I left the esata flash plugged in as I went into the bios
    Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
    Restart and back into the Bios
    Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
    A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
    An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
    A linux Swap partition of 2GB (/dev/sdb5)
    A linux /home partition –the remainder of the drive (/dev/sdb6)
    A linux /root partition of 8GB (/dev/sdb7)
Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
Next step was Linux user configuration which went fine
Next was booting.
In the section management tab
    delete the windows 1 and 2 options (since we are not dual booting directly)
In the boot loader installation tab
    uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
    check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
Open a root terminal
Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
Touch /mnt/sdb6/boot/grub/flag
The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
Start grub and do the following
#grub
            grub> find /boot/grub/flag
                (hd1,5)    -- the result of the find in my example
            grub> root (hd1,5)   -- using the result of the find in my example
            grub> setup (hd1)   -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
                  hopefully grub announces success
            grub> quit
Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.

Hi chrissh
i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the
   Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
any idea?

[SOLVED] linux: /boot/vmlinuz-linux exists in filesystem

I have had this issue for a while now. I ignored it but now I'd like to be able to upgrade. Pacman throws this error:
error: failed to commit transaction (conflicting files)
linux: /boot/vmlinuz-linux exists in filesystem
Errors occurred, no packages were upgraded.
There are now news at archlinux.org, and I'm hesitant to use the --force flag. What do you suggest? Also, I have linux-ck-kernel, if that's relevant to the issue.
Last edited by rubik (2015-01-21 14:19:37)

I don't know how I installed linux-ck-kernel, it's been a while. I probably followed the wiki.
@a821: Here are the commands' outputs:
$ pacman -Qo /boot/vmlinuz-linux
error: No package owns /boot/vmlinuz-linux
$ uname -a
Linux miki-laptop 3.17.5-1-ck #1 SMP PREEMPT Sun Dec 7 07:23:18 EST 2014 x86_64 GNU/Linux
I'm puzzled! Why would pacman care about that file if no package owns it?! The wiki says that in this case I should rename it and update again. I'll try and see what happens.
Last edited by rubik (2015-01-21 13:24:47)

Mac Mini Bios and booting in Linux

Does anyone know if the EFI /Bios issue that prevented the previous generation Mini from booting into Linux without a monitor or KVM switch attached has been remedied in the new Mini's?

If you read the article it says ASUS PB279Q via DisplayPort (the monitor) and the title says in Windows.
It works on any 4k Monitor with a DisplayPort. For OS X guides search google, there are solutions there.
I posted this article for people using Windows who are struggling with 4K out of the mac mini's.
Cheers

PXE-Boot with Linux

I have an IBM Machine (8193-75G) with Intel 10/100/1000 LAN. Is it
possible to do an PXE-Boot with Linux? Do I need a special driver?
Thanx

[email protected]
> I have an IBM Machine (8193-75G) with Intel 10/100/1000 LAN. Is it > possible to do an PXE-Boot with Linux? Do I need a special driver?
> Thanx
You might get an answer in the imaging forum
Jared L Jennings, CNE
Novell Support Forums SysOp.
http://support.novell.com/forums/faq_nntp.html
Posting with XanaNews Reader 1.15.7.4
Geek by Nature, NetWare by Choice.

Strange screen colors while booting Arch Linux (i686)

I'm trying to install Arch on an old computer via usb live,
when I start the first option "Boot Arch Linux i686" at the beginning seems to work then stops and appears:
Arch Linux 3.17.6-1-arch (tty1)
archiso login: root (automatic login)
at this point the pixels begin to change from black to white. until the monitor becomes completely white and black horizontal line appears at the center.
you have any idea what could be the problem?
Thanks for help
Last edited by Enrico87 (2015-01-28 19:06:27)

Enrico87 wrote:actually i have installed Debian
What?? The first post clearly said archlinux, but if this is debian, you are asking in the wrong place. Did you just use debian because the arch iso was unusable? Did these visual distrubances completely prevent login?
can you link me the article?
Not likely. Is your google broken?
EDIT: in hindsight this post was more abrupt than needed for a new-comer to the forums. Please pardon the tone - but the content was exactly as intended. We are happy to help when it is needed, but archlinux users are expected to be able to do some of their own research. If you really need the wiki link provided to you, you most likely would never be happy with archlinux.
Last edited by Trilby (2015-01-28 20:12:45)

GE70 dual booting with linux

Has anyone installed linux as a dual booting OS on their MSI laptop? I've gone through a lot of stuff online to try and install, but the UEFI isn't recognizing anything I have as far as live booting dvd or usb. I've turned off secure boot and fast boot. I can get it to boot off the disk/usb in Legacy mode, but if I install from there it installs as MBR which can cause problems. If anyone's had success, please, let me know.
Thanks!
B

If the laptop came with Win 8 pre installed then bios is set to UEFI, a new measure made by Microsoft to ensure nobody tries to boot other system rather than windows. The only way to boot a linux is to change bios to Legacy and then try to boot, after that, to boot windows you have to change that setting again, so not very efficient really.
My advice is to reinstall windows but in Legacy mode, there is software on the internet to check your windows key and reinstall.
All in all, while you have Windows in UEFI mode forget about dual booting, reinstall windows on Legacy or just erase it and go for linux.

Language change : Lenovo ideapad A10

Hi,
I bought lenovo ideapad A10 serial no. UB02114387 from Oman. There are only three language options given viz, Arabic, French and some other language. How can I change to english. I called technical support in India but could not get a satisfactory reply. Please suggest.

It's a totally your problem. I think you messed up your tab by rooting and by using wrong app from playstore. Make sure permissions to systemui.apk and .odex are rw-r-r.
You can say thank you by pressing the star left to my post IF I HELPED YOU

Booting 'Arch Linux' Error 15: File not found

Booting 'Arch Linux'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz26 root=/dev/sda3 ro vga=792
Error 15: File not found
Press any key to continue...
It's the message that Grub send me choose any option.
Can I solve or I need to format and reinstall?

donniezazen,
Note that you responded to a three year old thread. I cannot tell if you are having a problem, but I doubt this thread has any bearing on it.
Closing. If you are having an issue, please open a new thread. Our policy
Thanks

Arch Linux won't boot (and Linux in general)

Hello everyone,
I've been having this problem for about 3 days now. I finally made an account and post the problem since I can't find a solution (I solved most of my past problems by searching forums and googling so I had never posted before).
So, I was installing Arch linux and Windows 7 on my machine (eee pc 1201t) but had problems booting into linux. First I installed Windows and it worked fine, then I installed Arch linux (this isn't my first time) and rebooted after finishing the installation. But my laptop just won't boot. It just displayed a blinking cursor on the top left of the screen. No error messages whatsoever. It was my first time encountering the problem so I thought reinstalling would do the trick. But it didn't. So I started researching on the same problems on google and discovered that it could be either a HD problem or corrupted MBR or some other problem. My drive works fine, since I can copy data onto it using a live cd (Ubuntu) and Windows works fine with it.
I'm thinking of using "dd" command on my drive and repair the MBR. I would like to know if you guys have encountered the same problem before and what kind of solution you applied.
Note: I also tried installing Ubuntu on my machine but the result was the same.

ngoonee wrote:Live CD, setup grub again, and profit?
I tried this first, had no luck or maybe I wasn't doing it right.
nixpunk wrote:So are you booting into windows using grub or just ntldr?
My laptop boots using ntldr only. Grub does not seem to work. I tried installing Arch and Ubuntu but I had the same result (blinking cursor on the top left of the screen).
schuay wrote:As always with boot problems, you will need to provide some more data about your setup. Output of 'df -h', contents of /boot/grub/menu.lst, install location of grub, etc. Without that, other people can only make guesses about the possible solution
I'll keep that in mind. Sorry for the lack of details regarding my problem. I will try to add as much information as I can the next time I post.
Anyway, I think I solved the problem. I zeroed the MBR on my HD by issuing the command "dd if=/dev/zero of=/dev/sda bs=512 count=1 and grub installed just fine. Thanks for the reply everyone.

Ideapad A10 root / hiding of the navigation bar

Hello,
how can I root the ideapad A10 ? I would like to get a more vertical space on the display by using some of the apps which hide the navigation bar (the area where normally the Home/Back/Running apps are placed).
Solved!
Go to Solution.

Hi karlitos,
No one has yet maybe succeeded to root Ideapad a10, you may try to root using Kingo root App.
You can say thank you by pressing the star left to my post IF I HELPED YOU

Ideapad A10 boot on linux

Similar Messages

Maybe you are looking for