Problems after instalation - Boot stuck

Ryotenbin · 2014-04-19 00:14:25

Good night everyone.

I'm new here, as well as new using Arch Linux. So, i tried to install, following some of the tutorials i found on the internet, and i kind of think i make it through. However, the first time i tried to boot into arch, i got a problem:

"/dev/sda1: clean, x/y files, z/w blocks"

After this line it kind of freezes. I waited for like 5 minutes but nothing happened. I looked for some guides on this error, and yes i did the command mkinitcpio -p linux, i created the fstab, etc.

I don't know what could have possibly gone wrong. I must say i have a Windows partition also, but i don't think that might be the problem. Should i try to reinstall it with another tutorial? Or is there anything i can do?

Also, i was trying to enter into the arch system using the CD with the comand arch-chroot /mnt, but it didn't work anymore (worked at the first time when i was installing (used this comand before mkinitcpio)). Do i have to mount anything before that?

Thank you!

Slithery · 2014-04-19 10:05:28

The only tutorial you should be follwing is the Beginners Guide on the Arch Wiki.

Anything else is probably out of date.

Ryotenbin · 2014-04-19 13:19:49

I followed the begginers guide, did a fresh installation but didn't help, the problem is still there . I even tried to install the 32 bits version, didn't help.

I saw some people saying they fixed this kind of problem by downgrading the systemd version to 204 or something, but as i'm a newbie here i have no idea how to do it. Does anyone know how to help me?

Thanks a lot!

clfarron4 · 2014-04-19 13:38:53

Ryotenbin wrote:

I saw some people saying they fixed this kind of problem by downgrading the systemd version to 204 or something, but as i'm a newbie here i have no idea how to do it. Does anyone know how to help me?

Before we even discuss downgrading packages, we need to know more about your setup (BIOS/UEFI, GRUB/Gummiboot, partitions, encryption). Could be graphics drivers as well. Based on the little information you've given us, I don't think you're going to get much help ~~(I might as well go and feed the ducks)~~.

Last edited by clfarron4 (2014-04-19 13:39:58)

Ryotenbin · 2014-04-19 14:22:46

Thank you very much for your time!

So, my BIOS supports UEFI, but i've disabled it due to some problems in previous installation attemps (really confusing to install in UEFI devices).

Here follows some usefuk (maybe) configuration files.

Fstab:

PS: This /pen partition was there because i was using my pendrive to gatter the configuration files. The previous installations i didn't use it and yet i couldn't boot.

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sda1
UUID=c1fbc21c-0f1d-47d7-b2e7-99507af0673e	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sda3
UUID=0849290c-ab5c-49c6-8bca-edb3c7b0cfed	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sdc1 LABEL=MULTIBOOT
UUID=FE5A5A9A5A5A4F8F	/pen      	ntfs      	rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096	0 0

# /dev/sda2
UUID=81e8a02f-f84a-41f7-8a14-aeef031e1401	none      	swap      	defaults  	0 0

Grub:

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter 
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" 
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper 
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

#GRUB_SAVEDEFAULT="true"

Hosts (arch is my hostname):

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1	localhost.localdomain	localhost	arch
::1		localhost.localdomain	localhost

# End of file

Mkinitcpio:

# 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.
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 block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block 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 block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard 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="lz4"


# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

Regarding my partitions, i projected them as it follows:

sda1: Root, Primary, 30GB, Beginning, Bootable
sda2: Swap, Primary, 3GB, Beginning, type 82
sda3: Home, Primary, XGB, Beginning

/*Curious that before and after the sda4 there is an unusable allocated space of about 1KB or something. Started to happen after i upgraded my BIOS in order to disable UEFI.*/
sda4: Windows 8.1 partition

The following instructions is what i'm following in order to install Arch:

 loadkeys br-abnt2
setfont Lat2-Terminus16

wifi-menu

mkfs.ext4 /dev/sda1
mkfs.ext4 /dev/sda3

mkswap /dev/sda2
swampon /dev/sda2

mount /dev/sda /mnt
mkdir /mnt/home
mount /dev/sda3 /mnt/home

nano /etc/pacman.d/mirrorlist -> levanta o do Brasil

pacstrap -i /mnt base base-devel
genfstab -U -p /mnt >> /mnt/etc/fstab
nano /mnt/etc/fstab

arch-chroot /mnt /bin/bash

nano /etc/locale.gen -> US e BR
locale-gen
echo LANG=en_US.UTF-8 > /etc/locale.conf
export LANG=en_US.UTF-8

loadkeys br-abnt2
setfont Lat2-Terminus16
nano /etc/vconsole.conf
KEYMAP=de-latin1
FONT=Lat2-Terminus16

ln -s /usr/share/zoneinfo/America/Sao_Paulo /etc/localtime
hwclock --systohc --utc

echo arch > /etc/hostname
nano /etc/hosts
#
# /etc/hosts: static lookup table for host names
#

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1	localhost.localdomain	localhost	arch
::1	localhost.localdomain	localhost

# End of file

mkinitcpio -p linux
passwd

pacman -S grub
grub-install --target=i386-pc --recheck /dev/sda

pacman -S os-prober
grub-mkconfig -o /boot/grub/grub.cfg

exit
umount -R /mnt
reboot

Hope it's helpful! Thanks again, and sorry for my english (i'm brazilian). :-)

Last edited by Ryotenbin (2014-04-19 14:30:35)

clfarron4 · 2014-04-19 14:37:35

Ryotenbin wrote:

Thank you very much for your time!
So, my BIOS supports UEFI, but i've disabled it due to some problems in previous installation attemps (really confusing to install in UEFI devices).
[snip]
Regarding my partitions, i projected them as it follows:
sda1: Root, Primary, 30GB, Beginning, Bootable
sda2: Swap, Primary, 3GB, Beginning, type 82
sda3: Home, Primary, XGB, Beginning
/*Curious that before and after the sda4 there is an unusable allocated space of about 1KB or something. Started to happen after i upgraded my BIOS in order to disable UEFI.*/
sda4: Windows 8.1 partition

Oh dear lord, so you're attempting a BIOS_GPT setup... Well, here's the Wiki page on the matter (I think): https://wiki.archlinux.org/index.php/GU … er_Support

You realise that you'll need to put your UEFI back into UEFI mode to boot Windows 8.

Last edited by clfarron4 (2014-04-19 14:38:27)

Ryotenbin · 2014-04-19 14:43:47

Oh dear lord, so you're attempting a BIOS_GPT setup... Well, here's the Wiki page on the matter (I think): https://wiki.archlinux.org/index.php/GU … er_Support
You realise that you'll need to put your UEFI back into UEFI mode to boot Windows 8.

Oh god, even if i disabled UEFI in the BIOS? I had actually installed Windows 8 when UEFI was already disabled. I'm normally booting into Windows 8, by the way. I thought that if i disabled UEFI i wouldn't need to follow different instructions in order to install Arch. #sad

Lone_Wolf · 2014-04-19 14:46:30

ryotenbin,

if you installed windows in non-uefi mode you should install arch the same way.

if you had sucessfully installed arch in uefi-mode, you'd probably have to switch it off again to boot windows ...

Ryotenbin · 2014-04-19 14:53:10

Lone_Wolf wrote:

ryotenbin,
if you installed windows in non-uefi mode you should install arch the same way.
if you had sucessfully installed arch in uefi-mode, you'd probably have to switch it off again to boot windows ...

Hmm, got it. So, let me explain a few things:

1 - My BIOS is a Insyde model (specialized in UEFI BIOS). Back then it was in version 1.8. At that time i wasn't even able to boot into arch.
2 - Then i contacted my Notebook's manufacturer, and he said that in my Insyde's version UEFI is disabled by default.
3 - Then he sent me a procedure to update my BIOS, so i could manually enable/disable UEFI as i may want.
4 - When i first booted (reboot after BIOS update) i couldn't boot because Windows 8 wasn't installed in UEFI mode.
5 - I went to the bios settings, which now showed me that it was in UEFI mode (also the reason i couldn't boot), but this time i could manually disable it.
6 - I disabled and everything was rainbows
7 - Now i could normally boot inside Windows and i could also boot into Arch setup
8 - I then decided to make a full wipe in my HD, therefore i deleted every partition, installed arch in the first 3 (sda1, 2 and 3) and Windows 8 in sda4 (remaining space)
9 - But here comes the problem, i can't boot because it stays stuck into that /sda1, clean... thing.

Okay that's pretty much the whole story hahaha.

Hope it can clarify some remaining questions.

Last edited by Ryotenbin (2014-04-19 14:55:30)

Ryotenbin · 2014-04-19 15:29:59

I don't know if it's helpful, but i also got these 2 errors when using mkinitcpio -p linux

Warning: Possibly missing firmware for modules: aic94xx and smsmdtv

Steef435 · 2014-04-19 15:59:42

Looks like a classical Windows and Linux dualboot to me, UEFI doesn't seem relevant to me as it is disabled. Did you install Windows after you installed Arch? Then the Windows installation has probably overwritten the bootloader. You could try to chroot into your Arch installation to overwrite the bootloader again. Or, if you want to start from scratch, install Windows before Arch so it doesn't destroy the bootloader.

There should be some information in the wiki on dualbooting, but using the information in the Beginners' Guide should be enough I think. I think there are some other topics on the forums about dualbooting too.

EDIT: See here for the information you need.

Last edited by Steef435 (2014-04-19 16:02:53)

Ryotenbin · 2014-04-19 16:22:53

Steef435 wrote:

Looks like a classical Windows and Linux dualboot to me, UEFI doesn't seem relevant to me as it is disabled. Did you install Windows after you installed Arch? Then the Windows installation has probably overwritten the bootloader. You could try to chroot into your Arch installation to overwrite the bootloader again. Or, if you want to start from scratch, install Windows before Arch so it doesn't destroy the bootloader.
There should be some information in the wiki on dualbooting, but using the information in the Beginners' Guide should be enough I think. I think there are some other topics on the forums about dualbooting too.
EDIT: See here for the information you need.

Yea, that's what i did. Actually i deleted everything, then i set up the 3 first partitions for Arch for future installation. Then i installed windows, went back and installed arch on those 3 initial partitions.

I don't know if it's relevant but, in cfdisk /dev/sda i can see that either Windows and Arch are set to "bootable". The grub still loads first though. Would this be the problem? Would i lose the boot referente to Windows if i disable the bootable option on the Windows partition?

Thanks again.

Steef435 · 2014-04-19 16:58:32

Were you able to boot Windows after you installed it?

What's the output of the following?

# parted /dev/sda print

Last edited by Steef435 (2014-04-19 16:58:47)

Ryotenbin · 2014-04-19 19:35:42

Sorry for my late reply.

Here is the result:

Model: ATA WDC WD7500BPKT-0 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system     Flags
 1      32.3kB  30.0GB  30.0GB  primary  ext4            boot
 2      30.0GB  33.0GB  3002MB  primary  linux-swap(v1)
 3      33.0GB  103GB   70.0GB  primary  ext4
 4      103GB   750GB   647GB   primary  ntfs            boot

Steef435 · 2014-04-19 21:39:07

Hmm. Here ends my knowledge of partition layouts I'm afraid. Perhaps someone else can see something in that output, other than that it's an MBR(msdos) table. I'm not sure about the boot flags, I have only one on what I think is the Windows bootloader. I have a separate /boot partition with no boot flag. Perhaps someone else knows.

Looking back at your installation instructions you posted earlier:

mount /dev/sda /mnt

Should be /dev/sda1, is it just a typo? If it isn't then you'll probably have to check the fstab too.

Also, i was trying to enter into the arch system using the CD with the comand arch-chroot /mnt, but it didn't work anymore (worked at the first time when i was installing (used this comand before mkinitcpio)). Do i have to mount anything before that?

Yeah, you have to mount the partitions of the Arch system again using mount as written in the guide.

I'm not really sure where to look right now. Have you seen a working GRUB before? Just to be sure, does this error come up before or after you choose Archlinux from the menu?

After you installed Windows on the cleaned drive, were you able to successfully boot it? Did you alter the partition layout after that?

Last edited by Steef435 (2014-04-19 21:40:16)

Ryotenbin · 2014-04-19 21:51:32

Steef435 wrote:

Hmm. Here ends my knowledge of partition layouts I'm afraid. Perhaps someone else can see something in that output, other than that it's an MBR(msdos) table. I'm not sure about the boot flags, I have only one on what I think is the Windows bootloader. I have a separate /boot partition with no boot flag. Perhaps someone else knows.
Looking back at your installation instructions you posted earlier:
mount /dev/sda /mnt
Should be /dev/sda1, is it just a typo? If it isn't then you'll probably have to check the fstab too.

Yes i'm pretty sure it's a typo, i copied that from my email (using my phone to guide me while installing haha).

Steef435 wrote:

Also, i was trying to enter into the arch system using the CD with the comand arch-chroot /mnt, but it didn't work anymore (worked at the first time when i was installing (used this comand before mkinitcpio)). Do i have to mount anything before that?
Yeah, you have to mount the partitions of the Arch system again using mount as written in the guide.
I'm not really sure where to look right now. Have you seen a working GRUB before? Just to be sure, does this error come up before or after you choose Archlinux from the menu?

Yes, i've used other distributions before (Crunchbang, Manjaro), and they all were fine. And yes, the grub seems okay, it's just after i choose Arch that the problem happens .

Steef435 wrote:

After you installed Windows on the cleaned drive, were you able to successfully boot it? Did you alter the partition layout after that?

Yes, the Windows boot is completely fine, i didn't alter the partition as i remember.

But thank you very much for your efforts! I'll look up in the forums for any help i can find.

Ryotenbin · 2014-04-19 23:35:39

People, i found this guy that solved the problem: https://bbs.archlinux.org/viewtopic.php?id=171738

Silly7 wrote:

Fixed!
The problem IS infact with systemd, for whatever reason I do not know.
I noticed that my desktop Arch is also running 204-3 of systemd, so i booted up a ArchISO and copied that systemd .tar.xz to a second USB drive, located in /var/cache/pacman/pkg.
After booting up the ArchISO from my first USB stick, mount your / on /mnt, and proceed to chroot in [arch-chroot /mnt /bin/bash]
Then locate your secondary USBs dev name [lsblk] and match the result based on size of your flash drive ( Mine was easy as it was 700mb drive ), then proceed to mount it on /usb. [mount /dev/sdX /usb]
Finally, cd into /usb and execute 'pacman -Ud systemd-204-3-etc.tar.xz' without quotes. Use -U to upgrade to a downgrade (Inception right? ) and add the 'd' to ignore dependancys, else it won't work.

After doing the above im able to get past systemd again. **PLEASE BACK UP YOUR SYSTEM BEFORE DOING THIS, IM NOT RESPONSIBLE IF IT GOES PEAR-SHAPED!**.
Sulice, if your still tuned in, can you tell me how it goes for you? If you need the systemd i can upload for you if you like .

But i can't quite understand how to downgrade this package. Does anyone know how to help me? I want to try this as a last effort

clfarron4 · 2014-04-20 10:51:47

pacman -U </path/to/pkg>

Ryotenbin · 2014-04-20 10:56:57

clfarron4 wrote:

pacman -U </path/to/pkg>

Okay, i was reading something here: https://wiki.archlinux.org/index.php/Do … er_version

And so i went searching for the older package and i found it here: https://www.archlinux.org/packages/core/x86_64/systemd/

However, i have to recompile the package if i understood well. How exactly do i do it? I tried makepkg package-name but it says that PKGBUILD couldn't be found.

Is there any other place i can find it?

Thank you for your time.

Strike0 · 2014-04-20 11:14:35

You can find the older packages here: https://wiki.archlinux.org/index.php/Ar … ck_Machine
The general steps to downgrade are explained here: https://wiki.archlinux.org/index.php/Do … g_packages

edit: I did not read your thread fully, just the last question and now see you actually post above links yourself. In the ARM you find ready packages, so no need to recompile yourself; just install them how cifarron4 showed you above.

Last edited by Strike0 (2014-04-20 11:20:25)

Ryotenbin · 2014-04-20 12:15:26

Strike0 wrote:

You can find the older packages here: https://wiki.archlinux.org/index.php/Ar … ck_Machine
The general steps to downgrade are explained here: https://wiki.archlinux.org/index.php/Do … g_packages
edit: I did not read your thread fully, just the last question and now see you actually post above links yourself. In the ARM you find ready packages, so no need to recompile yourself; just install them how cifarron4 showed you above.

I've just downgraded it, didn't help at all . Guess it's time to give up.

Strike0 · 2014-04-21 10:03:09

Hm, too bad. How do you boot windows now? From the grub-menu or a bios menu? If it is the bios menu, I could assume the two bootable flags are confusing systemd during boot. But that is only guessing and I would not know what happens to your windows boot, if you disable that flag.

I looked at your install notes and don't have any other idea really. However, before trying around in the partition table the culprit seems to be with the install, since you cannot chroot to it from the usb anymore. If you don't want to give up, try that again (and no, you are executing "arch-chroot" just fine; no need to mount anything else than /dev/sda1 to /mnt in your case. <b>Alternatively</b> you can follow https://wiki.archlinux.org/index.php/Ch … artitions). Once you manage to chroot to it, it would be worthwhile to look at the /boot/grub/grub.cfg kernel options. Also post the name of your graphic card, maybe it is a modeset option you need for it in grub and someone knows. While you are at it you can add "nofail" to the fstab options for /pen, if you still want to use it.

Ryotenbin · 2014-04-21 11:22:07

Strike0 wrote:

Hm, too bad. How do you boot windows now? From the grub-menu or a bios menu? If it is the bios menu, I could assume the two bootable flags are confusing systemd during boot. But that is only guessing and I would not know what happens to your windows boot, if you disable that flag.
I looked at your install notes and don't have any other idea really. However, before trying around in the partition table the culprit seems to be with the install, since you cannot chroot to it from the usb anymore. If you don't want to give up, try that again (and no, you are executing "arch-chroot" just fine; no need to mount anything else than /dev/sda1 to /mnt in your case. <b>Alternatively</b> you can follow https://wiki.archlinux.org/index.php/Ch … artitions). Once you manage to chroot to it, it would be worthwhile to look at the /boot/grub/grub.cfg kernel options. Also post the name of your graphic card, maybe it is a modeset option you need for it in grub and someone knows. While you are at it you can add "nofail" to the fstab options for /pen, if you still want to use it.

I'm booting normally from Grub. Yea, i'm going to try that. Actually i tried to install Manjaro, Arch based, and the same problem occures. I was digging arount and found that someone solved this problem by downgrading libcrypt package to an older version. However, i didn't find it anywhere. For the record i'm searched here:

http://seblu.net/a/arm/packages/l/

And answering your question, my graphics card is a Nvidia GeForce 640m.

EDIT: Okay, i found the package. Its name is actually libgcrypt lol. Going to try to downgrade it now.

EDIT2: Yea, didn't help at all. :'(

Last edited by Ryotenbin (2014-04-21 13:55:23)

Ryotenbin · 2014-04-21 18:25:45

Does anyone know why, when i create a partition, it creates 2 more? I was partitioning my HD and when i created a new partition it created 2 more, one before and one after the partition with very small sizes (KB's). It happens both in Windows and Linux installations.

clfarron4 · 2014-04-21 20:56:46

Ryotenbin wrote:

Does anyone know why, when i create a partition, it creates 2 more? I was partitioning my HD and when i created a new partition it created 2 more, one before and one after the partition with very small sizes (KB's). It happens both in Windows and Linux installations.

Are you sure they're actual partitions, or unallocated space before and after?

Arch Linux

#1 2014-04-19 00:14:25

Problems after instalation - Boot stuck

#2 2014-04-19 10:05:28

Re: Problems after instalation - Boot stuck

#3 2014-04-19 13:19:49

Re: Problems after instalation - Boot stuck

#4 2014-04-19 13:38:53

Re: Problems after instalation - Boot stuck

#5 2014-04-19 14:22:46

Re: Problems after instalation - Boot stuck

#6 2014-04-19 14:37:35

Re: Problems after instalation - Boot stuck

#7 2014-04-19 14:43:47

Re: Problems after instalation - Boot stuck

#8 2014-04-19 14:46:30

Re: Problems after instalation - Boot stuck

#9 2014-04-19 14:53:10

Re: Problems after instalation - Boot stuck

#10 2014-04-19 15:29:59

Re: Problems after instalation - Boot stuck

#11 2014-04-19 15:59:42

Re: Problems after instalation - Boot stuck

#12 2014-04-19 16:22:53

Re: Problems after instalation - Boot stuck

#13 2014-04-19 16:58:32

Re: Problems after instalation - Boot stuck

#14 2014-04-19 19:35:42

Re: Problems after instalation - Boot stuck

#15 2014-04-19 21:39:07

Re: Problems after instalation - Boot stuck

#16 2014-04-19 21:51:32

Re: Problems after instalation - Boot stuck

#17 2014-04-19 23:35:39

Re: Problems after instalation - Boot stuck

#18 2014-04-20 10:51:47

Re: Problems after instalation - Boot stuck

#19 2014-04-20 10:56:57

Re: Problems after instalation - Boot stuck

#20 2014-04-20 11:14:35

Re: Problems after instalation - Boot stuck

#21 2014-04-20 12:15:26

Re: Problems after instalation - Boot stuck

#22 2014-04-21 10:03:09

Re: Problems after instalation - Boot stuck

#23 2014-04-21 11:22:07

Re: Problems after instalation - Boot stuck

#24 2014-04-21 18:25:45

Re: Problems after instalation - Boot stuck

#25 2014-04-21 20:56:46

Re: Problems after instalation - Boot stuck

Board footer