User Tools

Site Tools



  • Have used this distro for many years because
    1. YAST works well as an admin tool
    2. It has (usually) all the packages I need
    3. It is very reliable, and installation is very easy
  • We're currently using 13.2 on all computers

Favourite Applications

  • Gnucash (for personal and club finances)
  • Digikam (for managing photographs)
  • GIMP (for improving photos)
  • Hugin (for panorama stitching)
  • Amarok (for playing music)
  • And the usual favourite workhorses thunderbird, firefox, xemacs, libreoffice

Kernel upgrade failure

  • Did an upgrade which included a new kernel (3.4.28-2.20) and the nas box didn't boot!
  • Luckily, having a remote access card made it easier debug and solve this.
  • Turned out it was due to grub2 not being correctly configured:
    • the boot screen showed it failing to find the old kernel
  • So booting from an installation DVD, and then choosing “rescue system” allowed me to mount the /boot partition
    • then cd to grub2/ and edit the grub.cfg, replacing all kernel revision strings with the correct ones
    • but beware! opensuse 12.3 disks do not work in the microserver
      • maybe a video issue - not sure, but neither my 32bit nor 64bit dvd worked, either via the kvm iLo connection or direct with a monitor.
      • after starting udev, screen goes a nice blank grey and stays that way. With kvm and iLo we get a lost network connection, so it seems to be really screwed!
    • use either the opensuse 12.2 disk, or a system rescue cd

Even better, do this…

  1. cd /boot/grub2
  2. cp grub.cfg grub.cfg.bak
  3. run yast2 → bootloader and then simply hit ok. This rebuilds the grub.cfg
  4. Check the changes to grub.cfg - should show the new kernel being used.

And beware if the boot partition is raided (mine is 4 raid 1 disk partitions). RAIDed /boot can get screwed and will result in bizarre errors, perhaps indicating kernel cannot be found. But I've also other wierd ones that stop networking. After the above config do this:

  1. mdadm –detail /dev/md1
    Then for each missing disk…
  2. mdadm /dev/md1 –ad /dev/sda1
  3. mdadm –detail /dev/md1 (until it as been rebuilt)
  4. repeat for each disk

SSH-Agent, Keychain

After a lot of mucking about, have decided keychain is not much for desktop environment

  • I want kwallet to manage my passphrase at log in.
  • This process also enables a good random passphrase for ssh-keygen since kwallet does the remembering
  1. Get environment variables from the word go in all shells at desktop login time as per this gentoo page
    • create /etc/kde/startup/
      if [ -x /usr/bin/ssh-agent ]; then
        eval "$(/usr/bin/ssh-agent -s)"
    • create /etc/kde/shutdown/
      if [ -n "${SSH_AGENT_PID}" ]; then
        eval "$(ssh-agent -k)"
  2. Add key(s) to ssh-agent at desktop log in time as per this opensuse top tip
    • Add ~/.kde4/Autostart/ (or similar)
      #!/usr/bin/env bash
      thepath=`rpm -q -l ksshaskpass | perl -ne 'm/ksshaskpass$/ && print'`
      export SSH_ASKPASS=$thepath

Firefox Crashes

  • Just crashed at start up (v 29 ish)
  • only on 64bit 13.1 opensuse
  • Eventually just started again (i.e. moved .mozilla away and started afresh). This solved it :-(

Install from ISO on local disk

Doesn't yet work.

Here's an example that has the ISO stored in an LVM volume…

Network scanner

  • How to scan from our nice new shiny HP envy 5640?
  • We're now on opensuse 13.2, and yast scan setup, including using the hp setup menu, doesn't work :-( - nothing is found
  • So after some googling, found this, and got it to work!
  • Here's what to do…
    1. Get hplip v 3.14.10 or more as per hplip page
      • this requires getting the hplip packages from the opensuse Printing repo (do it via one-click from opensuse download page)
      • the stock distro ones are 3.14.6
    2. in a shell run hp-makeuri <IP>, and copy the sane URI
    3. then simply run xsane hpaio:/net/ENVY_5640_series?ip=192.168.199 or whatever
    4. make this simpler by editing your kde start menu for the xsane application and modify the xsane run line to the above.
  • The web server to the scanner does work very well but…
    • it requires admin password
    • doesn't seem to allow more than one login
    • seems to get “locked” by the first machine/user
    • is basically not designed for multi user environments which is a bit naff considering it's a network printer/scanner!!
    • this is all shame since the fundamental network interface is great, and I much prefer the idea of scanning through my browser - xsane is a bit of a clunky experience.
public/compute/opensuse.txt · Last modified: 2015/03/05 22:11 by jon