jantman / puppet-archlinux-macbookretina Goto Github PK

Have you tried the nvidia driver on 11,x (I'm on 11,5). No luck yet. nouveau works fine, but as you might know it's slower. I want to see if I can get the nvidia driver working to see if it's more performant.

I've gotten MATE desktop running under nvidia, just not GOME, which is what I really want.

This has become a bit of a catchall for everything I run on my laptop.

1. split out anything that's specific to me to either https://github.com/jantman/workstation-bootstrap, specific modules that do the "thing" intended (i.e. like profile-sync-daemon), or a workstation-potpurri module
2. Split out anything that's specific to Arch Linux but not MBP into a jantman/archlinux module.
3. Make what's left a real Module, on the forge, well-documented, parameterized classes, etc.

I just did yaourt and pacman full updates for my system built using this module (after not doing them in a LONG time - like 3.9.8-1 to 3.16.4-1).

• initially my touchpad didn't work. I reinstalled xf86-input-mtrack-git and this was fixed after reboot.
• initially wireless didn't work. I tried removing b43-firmware, b43-fwcutter and wireless-bcm43142-dkms and replacing them with broadcom-wl-dkms but this didn't work at all. I them removed broadcom-wl-dkms and re-installed b43-firmware and b43-fwcutter. That got me 2.4GHz working fine, but I couldn't see my 5G (a/n) AP.
• with the upgrade of NetworkManager from 0.9.8.8-1 to 0.9.10.0-4, OpenVPN connections die if they try to override automatic routes with custom manual/local routes. See this. Removing the overriding/local routes fixes the problem.

Error: Evaluation Error: Illegal name. The given name 'puppet-archlinux-macbookretina::firewall_post' does not conform to the naming rule /^((::)?[a-z_]w_)(::[a-z]\w_)*$/ at /etc/puppetlabs/puppet/manifests/site.pp:20:20 on node archlinux.hsd1.pa.comcast.net

Hi Jason!

I follow your instructions and when I try "sudo puppet apply --verbose /etc/puppet/manifests/site.pp" I run into this error: "undefined method `ancestors' for nil:NilClass".

Some output from right above in debug mode:

Debug: /Firewall[101 allow mosh]: [validate]
Debug: /Package[xf86-video-nouveau]: Provider pacman does not support features install_options; not managing attribute install_options
Debug: /Package[nouveau-dri]: Provider pacman does not support features install_options; not managing attribute install_options
Debug: /Package[mesa-libgl]: Provider pacman does not support features install_options; not managing attribute install_options
Debug: /Package[lib32-mesa-libgl]: Provider pacman does not support features install_options; not managing attribute install_options
Debug: /Firewall[100 allow ssh]: [validate]
Debug: Puppet::Type::Sysctl::ProviderParsed: file /etc/sysctl.conf does not exist
Debug: Puppet::Type::Sysctl::ProviderParsed: file /etc/sysctl.conf does not exist
Debug: Puppet::Type::Sysctl::ProviderParsed: file /etc/sysctl.conf does not exist

What's the problem? Could you help?

Thanks a lot
Ivan

When doing a pacman -Syu system upgrade, mkinitcpio builds for the CURRENT kernel, not the NEW one.

Example currently running 3.9.8-1-ARCH and upgrading to 3.10.10-1-ARCH:

upgrading linux...
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/efi/EFI/arch/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/efi/EFI/arch/initramfs-linux.img
==> Starting build: 3.9.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
==> ERROR: module not found: `usbhid'
  -> Running build hook: [fsck]
  -> Running build hook: [resume]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip initcpio image: /boot/efi/EFI/arch/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/efi/EFI/arch/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/efi/EFI/arch/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
==> ERROR: module not found: `usbhid'
  -> Running build hook: [fsck]
  -> Running build hook: [resume]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip initcpio image: /boot/efi/EFI/arch/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
upgrading linux-headers...

When we reboot, we see something like:

Waiting 10 seconds for device /dev/disk/by-partuuid/957fddfa-df23-4501-adf1-5a39f2ea08a0 ...
ERROR: device 'PARTUUID=957fddfa-df23-4501-adf1-5a39f2ea08a0' not found. Skipping fsck.
ERROR: Unable to find root device 'PARTUUID=957fddfa-df23-4501-adf1-5a39f2ea08a0'.
You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#

On second glance, it looks as though the only real problem is that vmlinuz-linux is placed in /boot/ when it should be in /boot/efi/EFI/arch/

I see there's a branch for Arch in Docker support, seems awesome! 👍

I opened a ticket: https://tickets.puppetlabs.com/browse/BKR-1021

But from my understanding, there's no systemd or init command that I can run for the docker_cmd... do you know what I'd need to run to get the box working?

As of this week, because of the many problems trying to get Linux to run on the latest (15,x) MacBook Pro models with the T2 chip, with a very heavy heart, I've turned in my work-issued MBP in exchange for a Dell Precision 5530.

As such, I no longer have any MBP hardware in my possession and will be unable to continue maintaining this module.

If anyone would like to adopt it, please comment here. Otherwise, it will become unsupported.

upgrade to latest nvidia, after reboot get only a black screen. console in (boot with "" kernel option) and Xorg.log.0 shows:

[ 12.441] (EE) NVIDIA(GPU-0): Failed to tear down EVO channel
...
[ 16.440] (EE) NVIDIA(GPU-0): EVO Push buffer channel allocation failed
[ 16.450] (EE) NVIDIA(GPU-0): Failed to allocate EVO core DMA push buffer
[ 16.452] (EE)
Fatal server error:
[ 16.452] (EE) AddScreen/ScreenInit failed for driver 0
...
[ 16.461] (EE) Server terminated with error (1). Closing log file.