You are not logged in.

Pages: 1

Topic closed

#1 2014-10-24 19:36:51

LDI
Member
Registered: 2014-10-24
Posts: 7

[Moved to another thread] Linux 3.17, Samsung, and i915

Hi guys,

Did someone succedeed to get Linux 3.17 (and Intel Microcode stuff) working with the EFIStub ? Below is my day :

Today i updated my Arch laptop (Samsung NP530U4E). I was happy to see Linux kernel 3.17 was there. After reading this, i ran the update. Here is the log :

[2014-10-24 12:12] [PACMAN] Running 'pacman -Syu'
[2014-10-24 12:12] [PACMAN] synchronizing package lists
[2014-10-24 12:12] [PACMAN] starting full system upgrade
[2014-10-24 12:13] [PACMAN] upgraded enca (1.15-1 -> 1.16-1)
[2014-10-24 12:13] [ALPM] warning: /etc/conf.d/fluidsynth installed as /etc/conf.d/fluidsynth.pacnew
[2014-10-24 12:13] [PACMAN] upgraded fluidsynth (1.1.6-3 -> 1.1.6-4)
[2014-10-24 12:13] [PACMAN] upgraded iw (3.14-1 -> 3.17-1)
[2014-10-24 12:13] [PACMAN] installed protobuf-c (1.0.2-1)
[2014-10-24 12:13] [PACMAN] installed libgadu (1.12.0-2)
[2014-10-24 12:14] [PACMAN] upgraded libpurple (2.10.9-2 -> 2.10.10-2)
[2014-10-24 12:14] [PACMAN] upgraded linux-firmware (20140828.13eb208-1 -> 20141009.0e5f637-1)
[2014-10-24 12:14] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-10-24 12:14] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Starting build: 3.17.1-1-ARCH
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Starting build: 3.17.1-1-ARCH
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-10-24 12:14] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2014-10-24 12:14] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-10-24 12:14] [PACMAN] upgraded linux (3.16.4-1 -> 3.17.1-1)
[2014-10-24 12:14] [PACMAN] upgraded lirc-utils (1:0.9.1.a-5 -> 1:0.9.1.a-7)
[2014-10-24 12:14] [PACMAN] upgraded nodejs (0.10.32-9 -> 0.10.33-1)
[2014-10-24 12:14] [PACMAN] upgraded php-composer (1.0.0.alpha8.586-1 -> 1.0.0.alpha8.613-1)
[2014-10-24 12:14] [PACMAN] upgraded unrar (1:5.1.7-1 -> 1:5.2.1-1)
[2014-10-24 12:14] [PACMAN] upgraded webkit2gtk (2.6.1-2 -> 2.6.2-1)

Nothing wrong so. After that, I installed intel-ucode package and copied /boot/intel-ucode.img to /boot/efi/intel-ucode.img (yeah, my EFI partition is mounted at /boot/efi).

Then I updated my boot entry using efibootmgr. As quoted in the wiki, I added an initrd entry BEFORE the "normal" one :

echo 'root=/dev/mapper/vgssd-lvroot rw rootfstype=ext4 add_efi_memmap initrd=\\intel-ucode.img initrd=\\EFI\\arch\\initramfs-arch.img' | iconv -f ascii -t ucs2 | efibootmgr -c -g -d /dev/sda -p 2 -L "Arch Linux" -l '\EFI\arch\vmlinuz-arch.efi' -@ -

When i rebooted, i got a kernel panic. So i plug my Arch Live usb key in and booted on UEFI Shell v1. From there, i was able to boot the kernel using the following line :

\EFI\arch\vmlinux-arch.efi root=/dev/mapper/vgssd-lvroot rw rootfstype=ext4 add_efi_memmap initrd=\EFI\arch\initramfs-arch.img

My issue is the boot is stucked after two lines :

::Running early hooks [udev]
::Running early hooks [lvm2]

My mkinitcpio.conf is very classic, i just get one module and several hooks :

MODULES="i915"
...
HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"

And below are my mounting points :

[...]
/dev/mapper/vgssd-lvroot on / type ext4 (rw,noatime,data=ordered)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/mapper/vghdd-lvboot on /boot type ext2 (rw,relatime,stripe=4)
/dev/mapper/vghdd-lvvar on /var type ext4 (rw,relatime,data=ordered)
/dev/mapper/vghdd-lvhome on /home type ext4 (rw,relatime,data=ordered)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
[...]
root@ultrablackbook #  ls /boot/efi/EFI/arch 
initramfs-arch-fallback.img  initramfs-arch.img  vmlinuz-arch.efi

And my LVM setup :

root@ultrablackbook # vgdisplay 
  --- Volume group ---
  VG Name               vghdd
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               4
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               365,30 GiB
  PE Size               4,00 MiB
  Total PE              93517
  Alloc PE / Size       93517 / 365,30 GiB
  Free  PE / Size       0 / 0   
  VG UUID               reZ7cg-1bkB-sl7x-lwui-C0eM-sewe-YoZwv0
   
  --- Volume group ---
  VG Name               vgssd
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  2
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               19,24 GiB
  PE Size               4,00 MiB
  Total PE              4925
  Alloc PE / Size       4925 / 19,24 GiB
  Free  PE / Size       0 / 0   
  VG UUID               Rwpoay-yKhU-HU8g-kk5N-w942-iFJq-xI3ybf
   
 root@ultrablackbook # lvdisplay 
  --- Logical volume ---
  LV Path                /dev/vghdd/lvswap
  LV Name                lvswap
  VG Name                vghdd
  LV UUID                pXeo0G-5VIJ-xzuL-pZZj-emwP-Eezj-zZvLDt
  LV Write Access        read/write
  LV Creation host, time archiso, 2014-03-02 05:24:57 +0000
  LV Status              available
  # open                 2
  LV Size                4,00 GiB
  Current LE             1024
  Segments               1
  Allocation             contiguous
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1
   
  --- Logical volume ---
  LV Path                /dev/vghdd/lvvar
  LV Name                lvvar
  VG Name                vghdd
  LV UUID                Z5F55K-JMxW-c0rI-jdZB-QWMV-dyUA-Cen65A
  LV Write Access        read/write
  LV Creation host, time archiso, 2014-03-02 05:25:24 +0000
  LV Status              available
  # open                 1
  LV Size                15,00 GiB
  Current LE             3840
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:2
   
  --- Logical volume ---
  LV Path                /dev/vghdd/lvboot
  LV Name                lvboot
  VG Name                vghdd
  LV UUID                jUoBpg-0Jxa-dkMA-asje-XkW9-lURD-dEcJm1
  LV Write Access        read/write
  LV Creation host, time archiso, 2014-03-02 05:26:00 +0000
  LV Status              available
  # open                 1
  LV Size                500,00 MiB
  Current LE             125
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:3
   
  --- Logical volume ---
  LV Path                /dev/vghdd/lvhome
  LV Name                lvhome
  VG Name                vghdd
  LV UUID                ez26Po-LkNR-TQfK-HuzJ-wrsm-2rKI-drlY3l
  LV Write Access        read/write
  LV Creation host, time archiso, 2014-03-02 05:26:21 +0000
  LV Status              available
  # open                 1
  LV Size                345,81 GiB
  Current LE             88528
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:4
   
  --- Logical volume ---
  LV Path                /dev/vgssd/lvroot
  LV Name                lvroot
  VG Name                vgssd
  LV UUID                eoWftR-tFVC-Wzws-GhA0-1xUd-vUwp-50iE5L
  LV Write Access        read/write
  LV Creation host, time archiso, 2014-03-02 05:24:11 +0000
  LV Status              available
  # open                 1
  LV Size                19,24 GiB
  Current LE             4925
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

I was able to boot on the live USB and downgrade kernel, so it's working again. But not really ideal.

Any help would be appreciated. Am i missing something ?

Thanks in advance.

Last edited by LDI (2014-10-25 13:26:39)

Offline

#2 2014-10-24 19:43:59

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,240

Re: [Moved to another thread] Linux 3.17, Samsung, and i915

I noticed that your definitions are

initrd=\\intel-ucode.img initrd=\\EFI\\arch\\initramfs-arch.img

The microcode image file should be in the same directory as the initramfs and kernel files - so presumably you should have:

initrd=\\EFI\\arch\\intel-ucode.img initrd=\\EFI\\arch\\initramfs-arch.img

i.e. the intel-ucode.img file should presumably be in the directory /boot/efi/EFI/arch

Last edited by mcloaked (2014-10-24 19:45:09)

Mike C

Offline

#3 2014-10-24 19:54:44

LDI
Member
Registered: 2014-10-24
Posts: 7

Re: [Moved to another thread] Linux 3.17, Samsung, and i915

Thanks for answering. I just moved the intel-ucode.img to the same directory and tried to boot. This gets rid of the kernel panic.

But the boot is still stucked here sad :

::Running early hooks [udev]
::Running early hooks [lvm2]

Offline

#4 2014-10-24 21:53:16

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

Re: [Moved to another thread] Linux 3.17, Samsung, and i915

Seems to be a problem with lvm rather than with the new firmware handling

I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do.  (Gune | Titan A.E.)

Offline

#5 2014-10-25 11:14:23

LDI
Member
Registered: 2014-10-24
Posts: 7

Re: [Moved to another thread] Linux 3.17, Samsung, and i915

No idea. I tried to add debug and ignore_loglevel options to the kernel line, but didn't give me more useful information.

Is there a way to debug the "early hooks" ?

Edit : Actually this seems to be an issue with Samsung hardware according to this topic.

Last edited by LDI (2014-10-25 11:37:17)

Offline

#6 2014-10-25 12:27:59

teateawhy
Member
From: GER
Registered: 2012-03-05
Posts: 1,138
Website

Re: [Moved to another thread] Linux 3.17, Samsung, and i915

Please change the title to reflect what you have found.

Offline

#7 2014-10-25 13:25:07

LDI
Member
Registered: 2014-10-24
Posts: 7

Re: [Moved to another thread] Linux 3.17, Samsung, and i915

Discussion moved there.

This bug might be involved.

Offline

#8 2014-10-25 18:04:26

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [Moved to another thread] Linux 3.17, Samsung, and i915

LDI wrote:

Discussion moved there.

This bug might be involved.



Please don't do this: report your thread and ask a mod to merge it.



Closing

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

Pages: 1

Topic closed

Board footer

Powered by FluxBB