Skip to main content

Posts

Showing posts from May, 2007

Debian 4.0 r0 (Etch) installation on IBM System p5 510 inside LPAR

For some reason, the usual CD/DVD installation does not work in LPAR. I tried both Debian 4.0r0 (netinst and complete cd-1) and OpenSUSE 10.2 (dvd). The errors are known. I reported the OpenSUSE bug here [1], and the Debian bug has been reported here [2]. Update: This workaround should also work in OpenSUSE. Select the logical volume where the installer was disk dumped (dd) as the installer media. This can be done in the Main Menu (4>1>3).

There is a workaround documented by Gottfried Scheckenbach in debian-boot list [3]:

Of interest for users of VIO (via HMC or IVM):
I have found a way around burning a new disc (because I'm not physical near to the machine): I downloded the iso onto the VIO server and putted it via dd into a newly created virtual disc aka LV on the VIO. I attached this virtual disc as secondary hard disc to the LPAR and booted the LPAR using the defictive cdrom. After running into the missing files problem on initializaton of the installer I remounted /cdrom f…

Resetting admin password in IBM System p5 510 Express ASMI

These are the steps in resetting the admin password:

0. Re-route stored static in your body via an ESD wrist strap to a
metallic element.

1. Look for the 2 toggle switches and service processor batt. The batt
should be in front of the Power Supply 1 and Power Supply 2 (codes: E1
and E2, see Rear Location Codes on the cover plate). The "very tiny"
toggle switches should be in the area of P1-C14 slot.

I forgot the exact sequence but it should be a combination of the ff. step (2):

2. Remove the battery, toggle the switches to the opposite direction.
Allows some time for the caps to discharge.

3. Move back the toggle switches and put back the batt in its place.

4. Assign your PC to Class C subnet (i.e. masked 255.255.255.0):
IPaddr: 192.168.2.x for HMC1 or
IPaddr: 192.168.3.x for HMC2

5. Ping HMC1 or HMC2. Access the web interface using the default address:
http://192.168.2.147 (for HMC1) or
http://192.168.3.147 (for HMC2)
Note: Sometimes you have to force the https protocol:
Example: https://192…

ld: unrecognized option '--hash-style=both'

gcc -Wl,-Map=contiki.map,-export-dynamic testv6.co obj_linux-native/socketdev_listener.o \
contiki-linux-native.a -o testv6.linux-native
/usr/local/bin/ld: unrecognized option '--hash-style=both'
/usr/local/bin/ld: use the --help option for usage information
collect2: ld returned 1 exit status


If you look closely, the error is something related to the local gcc not using the host's linker (ld).

$ which gcc
/usr/bin/gcc

$ which ld
/usr/local/bin/ld

For some reason, I messed my compiler path. To synchronized gcc to use the host's dynamic linker (i.e. /usr/bin/ld), set the environment variable COMPILER_PATH to /usr/bin.

$ export COMPILER_PATH=/usr/bin
$ echo $COMPILER_PATH
/usr/bin

$ gcc -print-prog-name=ld
/usr/bin/ld

Upgrade: Ubuntu Edgy (6.10) to Feisty (7.04)

I broke my rule of using the Ubuntu version one step backward from the current development release. My main interest is the stable ntfs driver with write capability. The upgrade went smooth except for a minor issue related to shared-mime-info package and a custom package (freemind). I reported the fix here.

Upgrade woes

I am sharing some of the notes that I've jotted down. This might be helpful to people who are upgrading from the long-term supported (LTS) Ubuntu Linux Dapper Drake (6.06.1) to Edgy Eft (6.10). My own cycle in upgrading is one step backward from the current development release. The current release is Feisty Fawn (Ubuntu 7.04). I use the command update-manager -c -d to dist-upgrade. This must be run as a privileged user.

Error 1:
Could not fetch the package liboobs. This is something related to our Internet filter in the university. So, I have to manually download the liboobs (edgy eft version) and place it in /var/cache/apt/archives/.


Error 2:
Could not install /var/cache/apt/archives/samba_3.0.22-1ubuntu4.1_i386.deb. The error log is: subprocess new pre-removal script returned error exit status 102. At first, I ignored the error but this will come up again later.

Error 3:
The upgrade aborts now. Your system could be in unusable state. A recovery was run (dpkg --configure -a). installAr…