Jimmy’s weblog

8/6/2010

Using IBM Bootable Media Creator on Debian

Filed under: — jimmy @ 1:03 am

IBM provides a tool called “Bootable Media Creator” (bomc) which creates bootable media - like an usb key - that allows you to easily install all firmware updates even if there is no OS installed on the server. You just select your server model, e.g. x3650, and the tool downloads all available updates. This saves a lot of time.
Formerly I used bomc on a SLES server but now I wanted to try if it would work on my Debian notebook, since the tool is available as a single binary and not as a rpm package as usual.
It started up and seemed to work but unfortunately after downloading some packages it stopped with an error. Long story short: I just copied the SuSE-release file to my /etc on my Debian notebook and all errors were gone :-)
My /etc/SuSE-release looks like this:

SUSE Linux Enterprise Desktop 10 (i586)
VERSION = 10

Bomc can be downloaded at the IBM site

11/28/2007

The forgotten posting: Debian etch on IBM x3200 and x3250

Filed under: — jimmy @ 6:28 pm

Yes, this posting is called “forgotten posting” because I just realized that I never posted it, although i should had been done a long time ago :-(

A lot of people had problems with the Adaptec Controller in the x206m model. Fortunately, the successor x3200 has a LSI controller on board which works perfectly when running Debian etch on it. It uses the Fusion MPT drivers and best of all: It’s not a fakeraid controller, it’s real HW-RAID (thx to mika for pointing me in the right direction, because I never thought about it :-) ).

Notes for using HW-RAID: There’s a small cmdline utility on the IBM CDs called “cfggen”. With this tool you can manage your RAID volumes. The userland utility (daemon) mpt-statusd monitors your RAID volumes (it’s included in Debian etch).

Notes about Debian woody: My x3200 was running a long time with Debian woody. You just need to install a newer kernel so that the controller gets recognized.

All of the information above applies to the x3250, too. It’s the rack version of the x3200.Nolvadex
Best platinum credit cards with low apr
Credit reporting services
Automobile refinance
Ambien
VPN security
Cialis Online
No apr credit cards
Deceased credit card debt
Life insurance uk
No apr no annual fee low interest credit cards
Credit rating scores
Online Cialis Soft Tabs
Cleocin
Highest credit score
Xanax
Household bank credit card application
Remove credit card debt
Free instant credit report with no credit card
Card consolidation credit debt financial internet
Danazol
Free credit report online no membership
Elavil
The fair credit reporting
Online Prozac
Affect credit score
Instant approval bad credit cards
Tenormin
Buy Cephalexin
Fair credit reporting act of 1970
Debt consolidation with bad credit
Ultram
Homeowners insurance quotes
Best credit score
Amoxil
Totally free credit report
Aspire credit card application
Uk credit card application
Buy Female Viagra
Best credit card debt help
Debt credit report
Fix my credit report
Best credit card debt help
Buspar
Hsbc credit card application
Credit report and scores
Canada credit card application
Prilosec
Phentermine Cheap
Refinance loan
Credit cards us instant approval
Disputing your credit report
Buy Lamisil
Credit scores online
Debt reduction solution credit card
Aristocort
Credit card application center
Citi bank credit card application
Us credit cards interest low apr 0
Improve my credit score
Buy Clomid
Unsecured credit card application online
Free credit rating report
Card consumer credit debt right
Kiss Ringtones
Clear credit report
Buy Clarinex
Buy Protonix
Credit card debt remover
Levitra
Cell Phone Ringtones
Levaquin
Cancel card credit debt
On credit scores
VPN setup xp
Cheap Viagra Cialis Levitra
Credit reporting bureau

7/4/2007

Lenovo X60s and Dualhead configuration

Filed under: — jimmy @ 12:54 am

The last days I tested the dualhead capabilities of the Lenovo X60s notebook. I had some problems to find a configuration that works without cloning the screen. But in the meantime a newer version of X and the i810 module was released which supports the Xrandr 1.2 extension. Thus it’s possible to change the settings while X is running with the user space tool “xrandr”.
I downloaded the latest version of grml-x to get a fresh xorg.conf:

root@subzero ~ % grml-x -nostart -f fluxbox

Since I wanted to run the internal display @1024×768 and the external CRT @1600×1200 I had to add one line to /etc/X11/xorg.conf:

SubSection \"Display\"
  Depth     16
  # Modes \"1024x768\" \"800x600\" \"640x480\"  \"1600x1200\" \"1280x1024\" \"1280x960\"
   Virtual 2624 1968
EndSubSection

Otherwise xrandr would complain that the screen is too small when setting up the layout of the two combined screens (e.g.: xrandr: screen cannot be larger than 1440×1440 (desired size 2048×768)).

After starting X you can begin to play with xrandr. When executing xrandr without any arguments it lists all available screens and displays.
To switch the external display off execute:

jimmy@subzero ~ % xrandr --output VGA --off

To change the resolution of the externalt CRT execute:

jimmy@subzero ~ % xrandr --output VGA --mode 1600x1200

To setup the CRT to be right of the LCD:

jimmy@subzero ~ % xrandr --output VGA --right-of LVDS

If you didn’t add the “Virtual 2624 1968″ Line in /etc/X11/xorg.conf, as described above, xrandr would now complain that the screen is too small for the desired size (1024+1600=2624 and 768+1200=1968).
xrandr has an excellent man page to lookup all the features.

My tests showed that window managers behave differently when setting up the screen layout. My preferred setup is to have the CRT right of the LCD with a higher resolution. With KDE it worked as expected but with fluxbox I couldn’t use fullscreen on the CRT only. So when switching to fullscreen or when maximizing windows, fluxbox used both screens (CRT and LCD).

You can download my xorg.conf here

9/16/2006

IBM USB floppy and persistent name with udev

Filed under: — jimmy @ 1:47 pm

Today I tested my new IBM usb floppy. When I plugged it in, the kernel loaded the usb-storage module and assigned device node /dev/sdc to it. Mounting a floppy-disk worked as exptected. Then I decided that it would be nice if the floppy would always use the same device node, not the first one available. This can be easily achieved with udev. I created a new file /etc/udev/ibm_floppy.rules and made a symbolic link to /etc/udev/rules.d/z81_ibm_floppy.rules. There’s only one line needed in the file:

BUS=="usb", SYSFS{product}=="TEAC FD-05PUB   " , SYMLINK="ibm-floppy"

When I now plugin my floppy udev creates /dev/ibm-floppy, which is a link to the assigned device node.

9/14/2006

Installing Debian sarge on IBM x206m Server with SAS drives

Filed under: — jimmy @ 9:50 am

UPDATE! (27.10.2006)
It seems that the initrd (initial ramdisk) has to be recreated before rebooting. Otherwise the adp94xx module is missing. I was sure that I checked this before posting this HowTo, but a second test and some comments from other users showed me, that it doesn’t work this way. Thus I added the necessary steps.
I also found out, that there are problems with S-ATA drives. If you follow my HowTo it works, but when using grml-0.8 or ubuntu 6.06 LTS Server Edition it can not access the S-ATA drives. Well, ubuntu uses another driver version but grml-0.8 uses exactly the same driver, built from the same source. I couldn’t find out what’s wrong, maybe a side effect from other parts in the kernel code?

Some of the newer IBm servers have SAS (serial attached SCSI) Controllers onboard. The driver is not in the linux kernel but you can get the source on the IBM site. Since grml 0.8 we support the SAS driver so if you want to install debian, you can boot with grml and run debootstrap. Another way is to use the sarge installer and load the kernel module before partitioning harddisks. This way is described here:

  • Download the precompiled kernel module for the sarge kernel and copy it to a usb-stick (The modified source code is also available)
  • Boot the server with the debian sarge installer cd
  • Make all steps as usual until the installer fails because no partitionable media was found
  • Switch to the console with <Alt-F2> and hit enter to activate it
  • Plugin your usb-stick and run “modprobe sd-mod”. With “dmesg |tail” you will see an entry which tells you the device node of the stick
  • Run “mkdir /usbstick” and mount it, e.g. “mount /dev/scsi/host0/bus0/target0/lun0/part1 /ubsstick”
    (/dev/scsi/… is the device node, that you saw before in the output of dmesg)

  • Now copy the kernel module with “cp /usbstick/adp94xx.ko /lib/modules/2.6.8-2-386/kernel/drivers/scsi” and run “depmod”
  • Run “umount /usbstick” and unplug the usb-stick. Run “modprobe -r sd-mod”. This steps make sure, that the SAS drive(s) will be named /dev/sda, /dev/sdb, etc. Otherwise /dev/sda would be assigned to the usb-stick.
  • Now load the kernel module: “modprobe adp94xx” and “modprobe sd-mod”, to load the support for scsi disks, again.
  • Watch the output of “dmesg”. The SAS drive(s) and the controller should be detected
  • Go back to the installer screen with <Alt-F1> and repeat the partitioning

UPDATE! (26.10.2006)
The following steps are required to recreate the initrd:

  • Continue with the installation up to the last step, when the installer asks you to remove any media and to reboot.
  • Switch back to the console (<Alt-F2>)
  • Copy the adp94xx module to the recently installed kernel: “cp /lib/modules/2.6.8-2-386/kernel/drivers/scsi/adp94xx.ko /target/lib/modules/2.6.8-2-386/kernel/drivers/scsi/”.
  • Now chroot to the installed system which is mounted on /target: “chroot /target”.
  • We need the proc filesystem, so run: “mount /proc”.
  • Run depmod: “depmod”.
  • Create a new initial ramdisk: “mkinitrd -o /boot/initrd.img-2.6.8-2-386 2.6.8-2-386″.
  • Exit from the chroot by hitting Ctrl-D or typing “exit”.
  • Go back to the installer screen with <Alt-F1> and complete the final installation step.

5/5/2006

IBM x336

Filed under: — jimmy @ 10:01 pm

Today I’m testing an IBM x336 server. Since the IBM servers are certified for SuSE and Redhat there’s usually no problem to get everything to work. The only pitfall might be the hard disk controllers. If you use SuSE or Redhat you can get the drivers, if you use Debian you are not that lucky. But this is only a problem if the drivers are not open source, otherwise you can simply recompile them for the debian kernel (For ServeRAID the drivers are in the official kernel source so this controllers work out-of-the-box)
Last time I tested a x346 where the ServeRAID controller was an Adaptec fakeraid and the driver was closed source. Anyway, when I see a fakeraid I usually use mdadm which worked perfectly. But there is a drawback. In this case you have to use the usual scsi drivers but then hot swapping of drives could fail if the driver doesn’t support it or if the support is buggy. In this machine the kernel module was aic79xx and hot swapping didn’t work stable enough for me (Lazy as I am I didn’t check if the module even supports hot swapping, so maybe it’s simply my fault ;-) )
The x336 has an onboard LSI Logic (kernel module mptscsih). Hot swapping worked, I just had to remove and reinsert the adapter with scsi-add:

scsi-add -r 1 0 1 0
scsi-add -a 1 0 1 0

Since this is a real hardware raid I activated the mirroring function in the BIOS and tested again with grml… no problems.

X60s, update nr. 1

Filed under: — jimmy @ 9:49 pm

Most of the things that didn’t work out-of-the-box were fixed in no time:

Wireless LAN, ipw3945
The ipw3945 project provides the driver and userspace daemon for the card. Yes, you need a userspace daemon for that card and this is also the reason why it won’t be packaged that soon… again a licensing problem :-(
Beside that annoying facts it works perfectly.

X.org
Starting with version 7 you can use the i810 driver. DRI didn’t work but I didn’t spend much time to solve it.

Sound
I installed the alsa drivers from the cvs tree. When I booted the first time I had to tune the mixer values because they were all above 300, instead of < 100. Also I have to restart the alsa subsystem after booting once again to make it work. That’s ok for now because I think that this problem will vanish with the next kernel release

3/29/2006

Finally my X60s arrived

Filed under: — jimmy @ 9:29 pm

Yes! One day before I’ll fly to USA. I was really frightened that it wouldn’t arrive in time. Anyway, this notebook is pretty cool. Thx to grml2hd the basic setup was done quick and only a few things have to be fixed:

  • Wireless LAN: Need to get the source of ipw3945
  • X.org: Only works with vesa driver
  • Sound: Need more recent alsa drivers

Stay tuned for updates.

3/9/2006

Installing debian sarge amd64 on IBM server x336: Can not mount CD-ROM

Filed under: — jimmy @ 4:14 pm

Problem: The debian installer can’t mount the cd because the ide-cd driver can’t be loaded correctly. This happens because ata_piix is loaded (S-ATA support) and is not able to detect the cd-rom on the ide port. This driver aquires all ports so you can’t load the ide-cd driver afterwards. So you have to load the generic ide driver BEFORE ata_piix is loaded.
Solution:

  • Boot the installer cd as usual and hit enter
  • When the dialog for language selection appears switch to a console (Alt+F2)
  • Execute the command “modprobe ide-generic”
  • Switch back to the first console and continue

1/29/2006

IBM ServeRAID Controller (Adaptec HostRAID)

Filed under: — jimmy @ 5:23 pm

During the last weeks I tested two IBM servers, a x206 and a x346. Both have the Adaptec HostRAID controller onboard (except you buy another IBM ServeRAID controller). Because this is just a fakeraid I used mdadm to setup the raid. But I was curious if it would work under linux. Adaptec and IBM provide drivers for SuSE and RedHat but I was interested to get it running under Debian. There is no source for the driver (a320.ko for SCSI and aaarich.ko for S-ATA) so it was impossible to compile it for my kernel. Have to find out if I can get the source code :-)
Besides that the hardware worked perfectly with Debian Linux.

9/18/2004

Alsa and WLAN on IBM T40 notebook

Filed under: — jimmy @ 5:31 pm

Alsa

I had to setup a few things on a IBM T40 notebook. The first task was to enable alsa, which is usually no problem. The OS was Debian unstable so I only had to install a few packages and to answer a few questions. There are two alsa-drivers for intel chipset where the second is for the modem. I marked both of them for compilation in the alsa setup. But when I tried to start alsamixer I got: “no mixer elems found”. After some googling I found out that the second alsa-driver must not be loaded. I had to blacklist it in /etc/hotplug/blacklist.d/alsa-base, which was installed by one of the alsa packages. The name of the alsa-driver was snd-intel8×0m. Unfortunately I was not able to rmmod all snd-* modules, so I had to reboot the notebook. After that alsa worked and I only had to change some permission, so that all users are allowed to use it(This time I didn’t want to add every user to group audio):

chmod o+rwx /dev/snd
chmod o+rw /dev/snd/*

WLAN

It’s a centrino notebook with Intel 2100 mini-PCI network card, therefore I thought it’s time to test the Intel IPW2100 driver. The installation was very easy, since there is good documentation available. But I had to face another problem when loading both network drivers at the same time: e1000 became eth1 and ipw2100 became eth0 and I wanted it the other way round :-) . Again, I blacklisted both drivers in /etc/hotplug/blacklist and defined aliases in /etc/modutils/aliases. Since hotplug was not allowed to load the drivers anymore, the networking script now loads them, using modprobe and thus my defined order.