As I posted earlier the Multimedia keys on the Vaio work quite nicely with Gnome apps like Rhythmbox. It's just that I prefer songbird. And while moving a server to a new pair of disks a little music is more than welcome. So let's rock and roll.
Only thing the multimedia keys don't work. Bugger. Songbird seems to ignore the gnome keybindings. The MMKeys add-on only seems to work on Linux. I didn't have the nerve to look into it yet. But there seems no easy way to bind keys to actions in Songbird.
A little annoying.
Tuesday, December 23, 2008
Moving box to S10U6 with ZFS root
So what do you do just before christmas? Well I started updating a T1000 from Solaris 10U4 to U6 with ZFS root. As this box serves a patient administration system in a hospital there is not much room for longer down times. Well except around official holidays.
The T1000 is a nice box to run databases on boot it has one problem - not a real problem more like a hurdle in terms of updating. It came with just a single hard disk when we got it. It has a StorEdge 3510 attached though.
Well sounds quite easy. Setup LiveUpgrade and off you go. In theory yes. Creation of the new boot environment worked nicely. Upgrade went fine too. The damn thing just wouldn't boot off the external disk stack. Bugger.
As there are now double disks in a single bracket available (well for some time now) I ordered a pair of disks to move the installation from one disk to the new pair.
Now the dirty part begins ;-)
As I am too lazy to replicate the installation from scratch (I could do it but it would require more time than I have at hand) I chose the adventurous route ;-)
What's next?
Create a new boot environment on the second disk. As we are still running S10U4 it has to be UFS again. Right now it is still populating the new BE with data from the first disk. (Yes, we are running live at this point.) Luckily the new disks (SATA vs SAS) are much faster, so this is running faster than expected.
Next thing will be the update to S10U6 followed be reboot into the new BE running S10U6. That gives us ZFS root. Once this is done and working I'll delete the first BE and create a new boot environment on a ZFS root pool. And one last reboot will bring us to where we want to be. Mirror root pool with much easier upgrade procedures next time (and just a single reboot needed).
Update
The upgrade to S10U6 took a bit over 2 hours. No problems here. Try to boot the new BE.
With the shutdown running I knew there was something missing.
Exactly.
The luactivate. Things like this happen when you drive home (90min commute) to finish this from home. Oh well!
Anyway, activated and booted the new BE.
Zpool created (remember it has to be a slice in order to be bootable! - Yes I did read the man page on that point ;-))
So now we are copying the S10U6 UFS BE to the final destination on a zpool.
Update 2
Everything made it to the new BE on the zpool. It boots. This was work for today then.
Merry Christmas everyone!
The T1000 is a nice box to run databases on boot it has one problem - not a real problem more like a hurdle in terms of updating. It came with just a single hard disk when we got it. It has a StorEdge 3510 attached though.
Well sounds quite easy. Setup LiveUpgrade and off you go. In theory yes. Creation of the new boot environment worked nicely. Upgrade went fine too. The damn thing just wouldn't boot off the external disk stack. Bugger.
As there are now double disks in a single bracket available (well for some time now) I ordered a pair of disks to move the installation from one disk to the new pair.
Now the dirty part begins ;-)
As I am too lazy to replicate the installation from scratch (I could do it but it would require more time than I have at hand) I chose the adventurous route ;-)
- First of all dump the current installation to the external disk stack.
- Swap the disks.
- Boot off the net (the T1000 doesn't have a DVD drive and I didn't want to try an USB drive)
- Slice one of the new disks as desired
- Restore the dump from the external disks
- Reboot
- Be done.
- Booting fails as I forgot to run installboot on the new disk, so boot net again
- Install the boot block on the new drive with installboot
- Reboot
- Done
What's next?
Create a new boot environment on the second disk. As we are still running S10U4 it has to be UFS again. Right now it is still populating the new BE with data from the first disk. (Yes, we are running live at this point.) Luckily the new disks (SATA vs SAS) are much faster, so this is running faster than expected.
Next thing will be the update to S10U6 followed be reboot into the new BE running S10U6. That gives us ZFS root. Once this is done and working I'll delete the first BE and create a new boot environment on a ZFS root pool. And one last reboot will bring us to where we want to be. Mirror root pool with much easier upgrade procedures next time (and just a single reboot needed).
Update
The upgrade to S10U6 took a bit over 2 hours. No problems here. Try to boot the new BE.
With the shutdown running I knew there was something missing.
Exactly.
The luactivate. Things like this happen when you drive home (90min commute) to finish this from home. Oh well!
Anyway, activated and booted the new BE.
Zpool created (remember it has to be a slice in order to be bootable! - Yes I did read the man page on that point ;-))
So now we are copying the S10U6 UFS BE to the final destination on a zpool.
Update 2
Everything made it to the new BE on the zpool. It boots. This was work for today then.
Merry Christmas everyone!
Wednesday, December 17, 2008
More support fun
Update on the Vaio Support story. 2 days after logging two further calls (both regarding LCD panel brightness) an answer two both of them.
1. How to dim the panel with no OS loaded?
-> We do not support that.
2. Why isn't the panel brightness persistent across reboots (even with vista)?
-> Have you tried the latest update for your graphics card?
When trying to answer via the support web site it hit me twice now that I was typing for too long and got logged out. Of course back in the browser didn't work and I had to type again...
1. How to dim the panel with no OS loaded?
-> We do not support that.
2. Why isn't the panel brightness persistent across reboots (even with vista)?
-> Have you tried the latest update for your graphics card?
When trying to answer via the support web site it hit me twice now that I was typing for too long and got logged out. Of course back in the browser didn't work and I had to type again...
Sony function keys and OpenSolaris
The sound vol up/down/mute buttons on the Vaio nearly worked out of the box, all I had to do was to map them in the Gnome Keyboard Shortcuts preferences.
Running
# dtrace -n '::KeyboardConvertScan:entry {printf("%x", arg1)}'
I found the keycodes for some other keys (Play/Pause, Stop, Next, Prev).
Funny that the Keyboard Shortcuts preferences dialog didn't see the keycodes when I tried to map them directly. So I had a look at acerkb from frkit which I had been using for ages on my Acer Ferrari. Seems like I was lucky that acerkb mapped the keycodes for the sound control already and it therefore just worked. So I replaced the keycodes from the Ferrari with the ones from the Vaio. And voila I was able to map them to the according functions in Gnome.
I wonder how I can find out which keycode sequences the keys generate that I couldn't catch with above dtrace command. There are 4 more Sony keys (S1, S2, AV mode, Eject) that I couldn't grab. Also the keys for LCD brightness, suspend and internal/external display didn't generate a key code. So there is more research needed.
Running
# dtrace -n '::KeyboardConvertScan:entry {printf("%x", arg1)}'
I found the keycodes for some other keys (Play/Pause, Stop, Next, Prev).
Funny that the Keyboard Shortcuts preferences dialog didn't see the keycodes when I tried to map them directly. So I had a look at acerkb from frkit which I had been using for ages on my Acer Ferrari. Seems like I was lucky that acerkb mapped the keycodes for the sound control already and it therefore just worked. So I replaced the keycodes from the Ferrari with the ones from the Vaio. And voila I was able to map them to the according functions in Gnome.
I wonder how I can find out which keycode sequences the keys generate that I couldn't catch with above dtrace command. There are 4 more Sony keys (S1, S2, AV mode, Eject) that I couldn't grab. Also the keys for LCD brightness, suspend and internal/external display didn't generate a key code. So there is more research needed.
How much support to expect
So after playing around with the Vaio and logging a service call about the numlock issue I found that no matter what I did the notebook would only charge the battery to 80%. Since I had ordered a high capacity battery as well I put that one into the notebook to find the exact same behaviour. Charged to 80% and off. Both Vista an Opensolaris reported the notebook was running on mains, battery connected, charged to 80% neither charging or discharging.
Time for another service call.
By now it was day 4 (in words four) after I logged the call about numlock.
And finally some kind soul from Sony's Vaio support answered to the numlock question. Indeed there is no such option in the BIOS (that much I knew already). There also is no way to turn off numlock at bootup using any other tool (Vaio Control Center may be). No BIOS update available. So here I am stuck with a turned on numlock on every boot and it takes Sony's support 4 days to find that out. Great work!
"Only" two days after logging the call on the battery question Vaio Support reacted and asked me a lot of questions. Yes this is the original power supply and batteries that Sony shipped. Yes my power outlet works just fine (why would the notebook run on mains otherwise?). Yes the power supply gets warm after being plugged in for a while. I tried both batteries as well. The guy then suggested a nice list of things to try (I was waiting for "dance around naked" until the end...) No real solution suggested though as I already had all cables removed and reinserted etc.
Funny I had a look around in the "Vaio Control Center" that comes installed with Vista. There is an option to extend battery life by only charging the battery to 80%. This was of course enabled. Switched off I have fully charged batteries.
And of course tech support didn't come up with the thing to check. But it has been only two days on this call.
Let's see how my other calls go. 2 more open for 2 days now.
Time for another service call.
By now it was day 4 (in words four) after I logged the call about numlock.
And finally some kind soul from Sony's Vaio support answered to the numlock question. Indeed there is no such option in the BIOS (that much I knew already). There also is no way to turn off numlock at bootup using any other tool (Vaio Control Center may be). No BIOS update available. So here I am stuck with a turned on numlock on every boot and it takes Sony's support 4 days to find that out. Great work!
"Only" two days after logging the call on the battery question Vaio Support reacted and asked me a lot of questions. Yes this is the original power supply and batteries that Sony shipped. Yes my power outlet works just fine (why would the notebook run on mains otherwise?). Yes the power supply gets warm after being plugged in for a while. I tried both batteries as well. The guy then suggested a nice list of things to try (I was waiting for "dance around naked" until the end...) No real solution suggested though as I already had all cables removed and reinserted etc.
Funny I had a look around in the "Vaio Control Center" that comes installed with Vista. There is an option to extend battery life by only charging the battery to 80%. This was of course enabled. Switched off I have fully charged batteries.
And of course tech support didn't come up with the thing to check. But it has been only two days on this call.
Let's see how my other calls go. 2 more open for 2 days now.
Friday, December 12, 2008
Welcome blog, welcome new toy
Welcome to my blog. I'll mainly post some stuff about (Open)Solaris und a little bit of this and that now and then.
So short before christmas, right in time a new toy arrived. A Sony Vaio AW11Z/B. Quite a nice bit of gear, though a little bit too big. But the AR series models I was going to get wasn't available any more. Since I didn't want anything with less than 1650x1080p display resolution and choise of brand is limited I "had" to go for the AW model.
Unfortunately it comes with Windows Vista preinstalled. That we're about to solve pretty soon :-)
First of all wait a bit until the preloaded Vista is ready to welcome you. Took like 15minutes or so before I was logged in. The notebook comes with a nice collection of software (Adobe Acrobat Distiller, Photoshop Elements etc.). We also might need Vista to watch BluRay discs. So I'm going for a dual boot.
Before we start lets create the recommended recovery dvds (yes there's 3! recovery dvds). Took well over an hour to create these. By the time I was this far I had lunch and my boss was there to take a look at the new toy.
The AW11Z/B comes with two 320GB harddisks. Those will make a nice ZFS mirrored pool. I used Vista's own hard disk and partition manager to shrink the original C: partition down to about 50GB on the first drive. I didn't touch the recovery partition (you never know when you might need it ;-)) That gave me roughly 230GB for the Solaris installation.
So now it's time to boot the Solaris installation dvd (I used SXCE build 103). Choose the text mode install and went for a ZFS root installation. I allocated 30GB to the root pool, the rest will go into homes and stuff.
About 40mins later it's time for the first "real" boot into Solaris.
Everything works just as expected. The first nice surprise is that Wifi works out of the box. (It has a Intel WiFi Link 5100).
For the Marvell Yukon 88E8055 we grab Masayuki Murayama's myk driver and are ready to go on the wired NIC too.
Sound works out of the box as well. Nivida graphics just works too.
Even the built-in webcam just works. All in all a very pleasant and easy thing to do.
Next thing is to create a solaris partition on the second harddisk, create two slices, attach on to the root pool and create a mirrored pool for all the data.
There is also a driver for the SD-Card reader which seems to work (it attached fine). I'll have to test that when I have an SD-Card.
Now everything is ready to put some data on it and install all needed software.
Though a few things remain open at the moment.
Suspend to ram seems to suspend the notebook ok but didn't wake up properly again. I'll have to check that.
The screensaver should switch off the backlight of the display after a while, but didn't.
The key for display brightness don't work so battery runtime is not where I want it to be yet.
The bios is really crippled. All one can change is the time and boot device order. I couldn't even switch off the bootup numlock. That really annoys me and I logged a service request with Sony. So far their support hasn't reacted at all within a day.
When I logged into Opensolaris (I use GDM as display manager) it didn't set the permissions on the sound and webcam device, so I had to fix that manually to have those working as non-root user.
Despite those issues great work from everyone who contributed to (Open)Solaris!
So short before christmas, right in time a new toy arrived. A Sony Vaio AW11Z/B. Quite a nice bit of gear, though a little bit too big. But the AR series models I was going to get wasn't available any more. Since I didn't want anything with less than 1650x1080p display resolution and choise of brand is limited I "had" to go for the AW model.
Unfortunately it comes with Windows Vista preinstalled. That we're about to solve pretty soon :-)
First of all wait a bit until the preloaded Vista is ready to welcome you. Took like 15minutes or so before I was logged in. The notebook comes with a nice collection of software (Adobe Acrobat Distiller, Photoshop Elements etc.). We also might need Vista to watch BluRay discs. So I'm going for a dual boot.
Before we start lets create the recommended recovery dvds (yes there's 3! recovery dvds). Took well over an hour to create these. By the time I was this far I had lunch and my boss was there to take a look at the new toy.
The AW11Z/B comes with two 320GB harddisks. Those will make a nice ZFS mirrored pool. I used Vista's own hard disk and partition manager to shrink the original C: partition down to about 50GB on the first drive. I didn't touch the recovery partition (you never know when you might need it ;-)) That gave me roughly 230GB for the Solaris installation.
So now it's time to boot the Solaris installation dvd (I used SXCE build 103). Choose the text mode install and went for a ZFS root installation. I allocated 30GB to the root pool, the rest will go into homes and stuff.
About 40mins later it's time for the first "real" boot into Solaris.
Everything works just as expected. The first nice surprise is that Wifi works out of the box. (It has a Intel WiFi Link 5100).
For the Marvell Yukon 88E8055 we grab Masayuki Murayama's myk driver and are ready to go on the wired NIC too.
Sound works out of the box as well. Nivida graphics just works too.
Even the built-in webcam just works. All in all a very pleasant and easy thing to do.
Next thing is to create a solaris partition on the second harddisk, create two slices, attach on to the root pool and create a mirrored pool for all the data.
There is also a driver for the SD-Card reader which seems to work (it attached fine). I'll have to test that when I have an SD-Card.
Now everything is ready to put some data on it and install all needed software.
Though a few things remain open at the moment.
Suspend to ram seems to suspend the notebook ok but didn't wake up properly again. I'll have to check that.
The screensaver should switch off the backlight of the display after a while, but didn't.
The key for display brightness don't work so battery runtime is not where I want it to be yet.
The bios is really crippled. All one can change is the time and boot device order. I couldn't even switch off the bootup numlock. That really annoys me and I logged a service request with Sony. So far their support hasn't reacted at all within a day.
When I logged into Opensolaris (I use GDM as display manager) it didn't set the permissions on the sound and webcam device, so I had to fix that manually to have those working as non-root user.
Despite those issues great work from everyone who contributed to (Open)Solaris!
Subscribe to:
Posts (Atom)