You are not logged in.

#1 2012-12-08 11:38:38

Never
Member
Registered: 2008-07-01
Posts: 102

linux-lts-3.0.54-1-i686 missing serverworks and ide_disk

I did a pacman -Syu and got linux-lts-3.0.54-1, it did this:

>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 3.0.54-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [pata]
  -> Running build hook: [usbinput]
  -> Running build hook: [fsck]
  -> Running build hook: [filesystems]
  -> Running build hook: [shutdown]
==> ERROR: module not found: `serverworks'
==> ERROR: module not found: `ide_disk'
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 3.0.54-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [pata]
  -> Running build hook: [usbinput]
  -> Running build hook: [fsck]
  -> Running build hook: [filesystems]
  -> Running build hook: [shutdown]
==> ERROR: module not found: `serverworks'
==> ERROR: module not found: `ide_disk'
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly

I went into mkinitcpio.conf and appended serverworks and ide_disk with a question mark, that let it compile without error but when the system started up again it froze at the command prompt. I had to use a rescue disk and then chroot the system and:

$ sudo pacman -U /var/cache/pacman/pkg/linux-lts-3.0.53-1-i686.pkg.tar.xz
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 3.0.53-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [pata]
  -> Running build hook: [usbinput]
  -> Running build hook: [fsck]
  -> Running build hook: [filesystems]
  -> Running build hook: [shutdown]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 3.0.53-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [pata]
  -> Running build hook: [usbinput]
  -> Running build hook: [fsck]
  -> Running build hook: [filesystems]
  -> Running build hook: [shutdown]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful

The system loads without freezing up at the command prompt 10 seconds in, like it did with the latest kernel. Is the removal of serverworks and ide-legacy a permanent thing or merely a mistake? If it is not a mistake what modules should I use in place of serverworks and ide-legacy if I needed those for a stable system? I have made pacman ignore linux-lts for now.

Offline

Board footer

Powered by FluxBB