64 Studio 3.0 alpha ISO (and from clean 64 Studio 2.1 install)

  • Quentin Harley
Posted: Tue, 12/30/2008 - 19:03

Free has given the users of the free 64 Studio distro a wonderful X-mas present...

64 Studio 3.0 Alpha !

Please Note : This is an Alpha release and is not tested extensively. We need testers!

Edit: There is now an Alpha release ISO set out! Download here:
Please remember to report any and all issues with this early alpha release!

Without further ado, here is a combination of the info that was circulated on the mailing list.

Letter from Free


here's a small Christmas gift for the 64 Studio community  :) 

As you all probably know Debian/lenny has been delayed and it is not
yet clear when it will be released (it was initially scheduled for
September 2008). Practically this means that we can't set any schedule
for a lenny-based 64 Studio 3.0.

So we decided to change a bit the plan and start working on an
Ubuntu/hardy-based 64 Studio 3.0, which is a platform we already
deploy for several projects and known to be stable.

For the braves of you here follows some instructions about how to
upgrade from 64 Studio 2.1 to the developing branch of 64 Studio
3.0. Please keep in mind that all this is still in alpha stage, but
should be already pretty usable.

============= 2.1 -> 3.0alpha upgrade instructions =====================

0) You should have two APT sources files on your 2.1 install:


comment *ALL* entries you have in these two files, and in
the following steps use only the file:


1) Add

deb http://ftp.debian.org/debian etch main contrib non-free
deb http://apt.64studio.com/backports etch-backports main

to your /etc/apt/sources.list and run:

apt-get update
apt-get install dpkg
apt-get remove firefox meterbridge

2) Remove the APT entries of step 1) from your /etc/apt/sources.list
and add these new repositories:

deb http://archive.ubuntu.com/ubuntu hardy main restricted multiverse universe
deb http://archive.ubuntu.com/ubuntu hardy-updates main restricted multiverse universe
deb http://apt.64studio.com/backports hardy-backports main

Then run:

apt-get update
apt-get install ubuntu-keyring
apt-get install sysv-rc=2.86.ds1-14.1ubuntu45.64studio1~hardy1

3) Now run:

apt-get update
apt-get dist-upgrade

and choose the default answer to all questions, except if it asks you if it should install unverified packages - Choose Yes there...

4) Finally issue a:


from the terminal.

5) open a gnome-terminal & run

sudo mkdir /usr/share/backgrounds
sudo cp (your wallpaper) /usr/share/backgrounds

Your screensaver preferences menu will look for this backgrounds folder,
if it can't find it, the screensaver menu will play up.

6) limits.conf for jackd to use realtime settings.

sudo gedit /etc/security/limits.conf

Open limits.conf.dpkg-old from inside gedit and copy the 3 @audio settings into the new limits.conf

@audio - rtprio 99
@audio - memlock unlimited
@audio - nice -10 

You might have to reset your qjackctl settings for Realtime & your card.

This has been tested on i386 and AMD64 versions.

Happy testing!

X-runs followup

  • mick.ca
  • 05/23/07
  • Thu, 01/08/2009 - 17:49
well tried something different here. excluded Jamin altogether. Put a TAP Dynamics on output of master. compressed and tweaked to sound same as jamin output...exciting...HOWEVER...when i exported...two beats in and XRUNS!!! bugger! but hey found a different/new way the "mixdown/master"... ALSO: i have made a GDM login screen for 64Studio. nice grayish blue elegant and simple. language selection etc. where or who do i send to for possible consideration? Also (again): Sorta missed having Abiword in the distro...I have added it myself..basic great and not a huge footprint like open office. cheers MiCK P.S. perhaps we could setup a chat session via the IRC channel so we can discuss in "realtime" some various 64Studio topics? granted we live around the world, i'm sure there could be a suitable time.

kernel installer notes

  • skullnotions
  • 09/29/07
  • Thu, 01/08/2009 - 10:45
Daniel wrote: Hi all, I just gave the amd64 build of 3.0 alpha (3.0~pre4~hardy1) a spin on my HP laptop, Turion CPU. I chose not to configure the network during the install, to see if there were any network dependencies. Here are my notes... The RT kernel caused problems for the installer, but installation was successful after following these steps: a) No kernel found warning - select Continue b) No vmlinuz symbolic link warning - select Create c) initrd kernel image warning, Abort? - select No Apart from that, it was a very smooth install, using manual partitioning. I noticed a few things after logging in that we should fix... See the rest of Daniels mail here: If you are interested in keeping up to date with 64studio development, subscribe to the list here. Cheers! dave.

Mono dependent apps

  • mick.ca
  • 05/23/07
  • Thu, 01/08/2009 - 13:05
I believe that Evolution is mono dependent as well. I do not use either F-Spot or Evolution. i agree with Daniel that Mono apps could be removed. After using this dpkg-query -l | grep mono All it comes back with is fonts and libs...no programs. however apps like Beagle, Tomboy, Muine. Banshee, Cowbell....all depend on mono. none of which are on my system but maybe some to avoid. UPDATE ON TESTING: recorded eight tracks. various with live guitar, acoustic bass, hydrogen drums & keys (using ZYNaddsubfx) NO x-runs...BUT when i interfaced to Jamin via insert in output of master track, I got x-runs two beats into the song! reset tried again..same. i'm running at 256. by the way. when i installed the alpha, i left my home directory intact and patitioned manually. My realtime and settings stayed in place in Jack. Just a thought. Cheers MiCK

Burned with x4 speed still the same result

  • LAUWannabe
  • 01/01/09
  • Wed, 01/07/2009 - 21:13
I burned a new CD with 4x speed but still get the same results after booting after the installation. I don't think it's a problem of the downloaded ISO or the burned CD.

Jack Rack and update

  • mick.ca
  • 05/23/07
  • Wed, 01/07/2009 - 13:37
Recorded a couple of tracks...audio is ok. However, Jack Rack, when i try to open a file i.e. a preset to load; it sorta hangs up in the "open file" dialog. bug? ubuntu? my system? Ardour had a couple a complaints about "playlists" but I ignored those as self stupidity for not saving settings. Lost some icons on my taskbar after a reboot. that is fixed by reloading them, verifying the path in properties and seeing after another reboot if they were still there... they stayed but weird how they disappeared. My Audio convert script in nautilus also took a hike so i ended up loading a program called "Sound Convertor", like it better than the right click script. That's my update. as far as those having load problems. I would suggest, (not knowing exactly your system) but backup ALL your home directory. reload 2.1, make a seperate home partition, than before loading anything else, do the alpha load. Worked for me. My home directory stayed in tack and ubuntu didn't have anything to do but load to the root. cheers, Mike

kernel not found...

  • angelsguitar
  • 12/22/07
  • Tue, 01/06/2009 - 20:39
Hi, LAUWannabe. Don't feel alone, I have the same problem too :( I believe my ISO image is alright; the cheksums match. Maybe I should try to burn it again. My CD/DVD burner is new, so I don't think I have a defective burner. Maybe the burn process corrupted the image during the transfer to the CD. I'll try again later.

mouse right-click menu (desktop)

  • skullnotions
  • 09/29/07
  • Tue, 01/06/2009 - 12:08
Hi Mick, Sorry my post was a bit confusing, Right clicking on the desktop used to bring up a menu with a link to open the gnome-terminal & I use it a lot. The new 3.0 alpha doesn't have this gnome-terminal link in the menu. Installing nautilus-open-terminal puts the menu link back in the right click menu. Editing the xterm file afterwards lets you configure the size of the terminal when it opens. Sure is a great release, all seems fine here. Cheers! dave


  • mick.ca
  • 05/23/07
  • Tue, 01/06/2009 - 12:04
haven't played with the sound apps yet (since the Nvidia driver install) as i have run into a quirky little Flash plugin problem with Opera 9.63. works fine in firefox but not opera (didn't have problem in debian...I'm finding ubuntu may be PART the problem...but i will look into the sound and midi apps today. out of curiosity i checked...my right click in terminal is working fine. regardless this is one amazing alpha release. MiCK P.S. Update: it's only been an hour but the problem is solved. Opera back up and running better than ever! Now that audio question...

Kernel issues on some hardware

  • skullnotions
  • 09/29/07
  • Tue, 01/06/2009 - 04:11
Free wrote: The problem is that the 3.0 alpha release still uses the 2.6.21 kernel from the 2.1 release, which AFAICT is the latest stable one RT-wise (kernels > 2.6.21 all have issues on some hardware). Unfortunately the 2.6.21 lacks support of some recent hardware, most noticeably some ethernet cards and some SATA2 controllers. Kernel 2.6.28 promises to be better RT-wise, but its RT patch hasn't been released yet. As soon as I find a good rt-kernel I will release a 3.0 beta, which will work on newer hardware as well. Cheers! dave

nVidia install

  • skullnotions
  • 09/29/07
  • Tue, 01/06/2009 - 05:36
Hi Mick, Great news about the nVidia install :-) How do you find the audio system compares with/without the driver installed?. Post back any issues you find with the 3.0 alpha release. Good feedback makes for a great version release. Backup your good xorg.conf ready for next time. Just found out how to get back my mouse right-click menu (terminal) sudo apt-get install nautilus-open-terminal If you want change it's default size edit this file: sudo gedit /usr/share/vte/termcap/xterm change this line to alter the size settings. The first is the default, the second setting opens the terminal the full width of my screen. :co#80:it#8:li#24:\ :co#158:it#8:li#24:\ Cheers! dave

It worked!

  • mick.ca
  • 05/23/07
  • Mon, 01/05/2009 - 21:26
LAUwannabe: I did a fresh install/ I also ALWAYS burn my .iso at 4x-16x speed. the slower the better! Skull dave!!: dude it worked! my driver was this NVIDIA-Linux-x86-177.82-pkg1.run. I followed step by step except the xorg backup...did it prior to. All went well as i logged in the menus had special effects, new cursor & i loaded Google earth and now i can go globetrotting again!!! This is turning into a sweet little adventure! cheers MiCK

New ISO dwnld same result

  • LAUWannabe
  • 01/01/09
  • Mon, 01/05/2009 - 21:02
Downloaded the ISO again, checked with md5sum, burned the CD again, now with x20. Same result. @Icemouse: I have made screen pictures per digicam. Need to find a place to upload them. @skullnotions: x4 (CD-speed) would be a bit slow, wouldn't it? AFAIK blank CD's can also be defective from burning to slow (I use blank CD's specified for x52). Did anyone else tried a fresh installation? It seems everyone else is just updating from 2.1.

test xorg.conf

  • skullnotions
  • 09/29/07
  • Mon, 01/05/2009 - 18:00
Hi Mick, You are going the right way about this, I also created an xorg.conf before I started. The graphics part of the xorg.conf I posted is all I use in my graphics section. I don't have the modelines or the BUSID part. Why don't you make two files. Your default and a copy of my graphics part and see which works, also keep your vesa one so you can use it in an emergency. The install messed up the keyboard part of my xorg.config so I had to repair this too. Backup your Backups. Remember to remove the 64studio testing sources from your list once you have the kernel modules and kbuild!. Good luck with your install. Cheers! dave Edit: I don't see the Module section for "glx"

my xorg.conf (practice)

  • mick.ca
  • 05/23/07
  • Mon, 01/05/2009 - 17:07
The website you provided says i have a Geforce 6150SE..so i added this in. Currently It says Device = nividia generic with the vesa driver. But this is my mock up for the new conf. Section "Device" Identifier "Configured Video Device" Boardname "NVIDIA GeForce 6150SE Series" Busid "PCI:0:13:0" Driver "nvidia" Vendorname "NVIDIA" EndSection Section "Monitor" Identifier "Configured Monitor" Vendorname "Samsung" Modelname "Samsung SyncMaster 753DF(X)/703DF(X)/783DF(X)/CD173A(T)" Horizsync 30-71 Vertrefresh 50-160 modeline "640x480@60" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync modeline "640x480@72" 31.5 640 664 704 832 480 489 491 520 -vsync -hsync modeline "640x480@75" 31.5 640 656 720 840 480 481 484 500 -vsync -hsync modeline "640x480@85" 36.0 640 696 752 832 480 481 484 509 -vsync -hsync modeline "800x600@56" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync modeline "800x600@72" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync modeline "800x600@75" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync modeline "800x600@85" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync modeline "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync modeline "832x624@75" 57.284 832 864 928 1152 624 625 628 667 -vsync -hsync modeline "1024x768@85" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync modeline "1024x768@75" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync modeline "1024x768@70" 75.0 1024 1048 1184 1328 768 771 777 806 -vsync -hsync modeline "1024x768@60" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync modeline "1024x768@43" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync interlace +vsync modeline "1152x864@75" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync modeline "1280x960@60" 102.1 1280 1360 1496 1712 960 961 964 994 -hsync +vsync modeline "1280x1024@60" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync modeline "1400x1050@60" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync Gamma 1.0 EndSection Section "Screen" Identifier "Default Screen" Device "Configured Video Device" Monitor "Configured Monitor" Defaultdepth 24 EndSection It not all jumbled up like this post but the values added in monitor allowed me to get 1280x1024 with the vesa driver and not have a shacky screen. other than that.... Do you see anything out of place? or unnesscary?

Debian device check & xorg.conf

  • skullnotions
  • 09/29/07
  • Mon, 01/05/2009 - 16:31
Hi Mick, Debian device check. Might help with card name. paste your result of $ lspci -n Into here xorg.conf graphics part. Format with the [hit tab] for spacing. Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth 24 EndSection Section "Module" Load "glx" EndSection Section "Device" Identifier "Configured Video Device" Driver "nvidia" Option "NoLogo" "True" EndSection Cheers! dave


  • Icemouse
  • 08/04/07
  • Mon, 01/05/2009 - 16:11
For my 64 Studio 2.1 64bit default "dmidecode |more" and "lspci -v" aren't a help and even the manually installed "hwinfo --gfxcard" isn't very helpful. Anyway, you should try those commands, maybe you have better luck.

Nvidia attempt

  • mick.ca
  • 05/23/07
  • Mon, 01/05/2009 - 15:10
I'll give this a go this evening. This hybrid xorg.conf file you speak of: could you show a sample of the monitor and video section. I believe I have that already mapped out but want to be certain. Indeed the Ubuntu way of things is different but it works. Did anyone remember the command for finding what your video card is? I cannot remember mine to save myself. My nividia is onboard so I can't even look at the card! it's in the 96xx area, but to get the right build ...you know the story. cheers MiCK

nVidia binary driver install

  • skullnotions
  • 09/29/07
  • Fri, 01/16/2009 - 09:41
Hi Quentin, No problem, here are my notes. If in the past you have dist-upgraded 2.1 to lenny, you will find this "hardy" nvidia binary install nearly the same, with two differences. First you will have to add the 64studio testing and src to your sources.list (install headers) this will pull dependencies. Then remove the 64studio testing and src from your sources.list. Run apt-get update to refresh back to hardy sources and install build-essential, this will pull dependencies. Once you complete the install you will have to edit your xorg.conf for the nvidia driver, this part is I found the most tricky because the ubuntu xorg.conf is completely different to the 64studio one used in the past. I had to reconfigure the xorg.conf to suit my system. I used a mixture of the hardy xorg.conf and an older 64studio xorg.conf. method: Download the nvidia driver from the download site. Make selection for your version from here Log out of your desktop & log into a console [ctrl] + [alt] + [f1] as root. Change directory to where your nvidia driver downloaded. cp /etc/X11/xorg.conf /etc/X11/xorg.conf2 nano /etc/apt/sources.list (add 64studio/testing & src). apt-get update apt-get install linux-headers-2.6.21-1-multimedia-486 (use your version). nano /etc/apt/sources.list (remove 64studio/testing & src). apt-get update apt-get install build-essential telinit 3 /etc/init.d/gdm stop export CC=gcc-4.1 sh NVIDIA-Linux-x86-173.14.12-pkg1.run (use your version). nano /etc/X11/xorg.conf ReBoot Cheers! dave. PS: $ sudo dpkg -l |grep 2.6.21 ii alsa-modules-2.6.21-1-multimedia-486 1.0.17~hg080328-1+2.6.21-2 ii linux-headers-2.6.21-1-multimedia 2.6.21-2 ii linux-headers-2.6.21-1-multimedia-486 2.6.21-2 ii linux-image-2.6.21-1-multimedia-486 2.6.21-2 ii linux-kbuild-2.6.21 2.6.21-1~bpo.1 Edit: Tidy up a bit.


  • Quentin Harley
  • 05/24/07
  • Mon, 01/05/2009 - 09:28
Hi Dave, Could you drop a breakdown of your method in here as well? Q

No Kernel & nvidia driver install

  • skullnotions
  • 09/29/07
  • Mon, 01/05/2009 - 08:54
Hi, Kernel I have seen this error in the recent past and it was caused by a bad image, I downloaded another image and burned at x4 speed. Not saying this is the same as the error here, but a slower burn might be worth trying. Even consider downloading the iso again. nVidia I have used a method similar to the 2.1 dist-upgrade to lenny one, to install the binary driver on one of my test installs here. Not quite as straightforward as the old method but it seems to have worked. Just checking it out now. Cheers! dave

Graphics drivers

  • Quentin Harley
  • 05/24/07
  • Mon, 01/05/2009 - 08:16
I wanted to get my nvidia card to take over its graphics responsibilities (as it should) and found a simple workaround to the problem: Compiling the 64 Studio kernel in the 8.04 ubuntu environment. After installing I could successfully install the nvidia driver from the site, and tested it by enabling compiz - working fine. I am working on a workaround instruction, and will post it sometime tomorrow if time permits. Cheers, Q


  • Icemouse
  • 08/04/07
  • Mon, 01/05/2009 - 06:49
Hi LAUWannabe :) hi Quentin :) reading http://www.64studio.com/node/879#comment-3614, we can shut out the version as the cause. Using 64bit hardware, both versions are correct. To understand what was going wrong, it would be a help to know in details, what you did LAUWannabe. Maybe you can do a new install and document each step, by quoting word by word your entries and the messages you'll get. Cheers, Ralf

No Kernel...

  • Quentin Harley
  • 05/24/07
  • Sun, 01/04/2009 - 22:33
If the installer cennot find a kernel for your system is may mean that you downloaded the incorrect version for your system, or that the installer ISO is corrupted. Check the md5sum of the ISO you downloaded against the checksums Free recently added to the download location on the web.

Fresh installation failed

  • LAUWannabe
  • 01/01/09
  • Sun, 01/04/2009 - 21:31
I tried to install a fresh 64 Studio 3.0 alpha and after partioning I get a message like 'no Kernel found in apt sources' (don't have the english version as I used german as language). Now I have the option to install without Kernel or cancel installation. I chose "install without Kernel". A bit later I get a message that I'm installing an initrd-Kernel, etc. It seems I have to edit /etc/kernel-img.conf and add "do_initrd = Yes". After the initial reboot I get something like this: L 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99_ No reaction to keyboard input. Installation seems to have failed.

Nv vs nvidia vs vesa

  • mick.ca
  • 05/23/07
  • Sun, 01/04/2009 - 20:02
I roamed through several settings. At boot up the xconf dialog would come up complaining about low graphics mode. i'd pick my monitor. (i had already entered ALL possible resolutions for it in xorg.conf) then i'd play with the nv/nvidia settings for the graphics card. The test button proved useful as the only "non-shakey" combo was with the vesa driver. My screen is clear, not shakey at all and actually other than accelerated stuff it works as good as nvidia did. the ONLY thing i needed accelerated drivers for was google-earth but there's loads of work to do with testing this wonderful alpha. This kicks butt and I won't have time for globetrotting with all the testing to do. Perhaps the beta release will have the 64studio modules for nvidia-glx-legacy-96xx plus kernel...they worked bang on. Till then I will enjoy my holiday present from the guys at 64studio. Keeping in touch MiCK

xorg & nv driver

  • skullnotions
  • 09/29/07
  • Sun, 01/04/2009 - 16:27
Hi Mick, Have you tried using the "nv" driver instead of the vesa? I have changed the "Device" section to this. Section "Device" [hit tab] Identifier "Configured Video Device" [hit tab] Driver "nv" [hit tab] Option "NoLogo" "True" EndSection You can ignore the NoLogo entry thats for when I've installed the nvidia binary driver. Back up your xorg.conf first in case it doesn't work. sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf2 Same feelings here, the new alpha release shows real promise :-) Cheers! dave

nvidia and such

  • mick.ca
  • 05/23/07
  • Sun, 01/04/2009 - 13:20
I'm with skullnotion for now and i'll wait for the later release or tinker later for a solution. Right now i have a regular vesa driver and set my resolutions in my xconfig. no more shaky screen. I don't need acceleration that bad right now. thanks for the fixes skull.. But for now I will concentrate on sound stuff and production. Today i'll play with the midi side and see. So far i'm pleased and excited as to where this is going. Great work guys, thanks Free!


  • Quentin Harley
  • 05/24/07
  • Sun, 01/04/2009 - 08:06
There is a problem with the nvidia drivers from 64 studio. They were created on a different xorg version and will not work on this version. Also it is not possible to install the nvidia driver from the nvidia site at this time because the kernel was not recompiled for the new environment yet... the compilers do not match. I'll ask Free to take a look at this... Cheers, Q

error & sources.list

  • skullnotions
  • 09/29/07
  • Sun, 01/04/2009 - 03:51
Hi Mick, This should generate source list. System>admin>software sources>check all boxes under ubuntu software and updates tab.Reload. Be careful with the proposed & backports. The ones you already have (above howto) cover most things, except security sources. Keep the 64studio hardy-backports entry. Correct the kernel error messages you see in the boot verbose. sudo gedit /etc/sysctl.conf Comment out these entries. kernel.maps_protect =1 vm.mmap_min_addr = 65536 If you run a search for "old" you can checkout which files are changing during upgrades. sudo find / -name '*old' UbuntuGuide This might help with some issues. Not Really sure about the nVidia driver, I haven't set mine up yet, I'm trying to do without it at this time, to see if it gives much improvement to audio performance. I will have a go soon on one of my test installs & post the results. Cheers! dave

error update

  • mick.ca
  • 05/23/07
  • Sun, 01/04/2009 - 00:48
Install went great! installed off of the 64Studio disc. Got the following errors at boot: Setting kernel variables error: "kernel.maps_protect" is an unknown key error: "vm.mmap_min_addr" is an unknown key But it did boot to a non-nvidia driver screen. can't get the nvidia driver from 64studio repos as it wants to REMOVE all xorg components. The headers aren't there and ubuntu drivers aren't working...small problem. the nvidia drivers from the 64studio repos work great but can't install them...workin on the problem now. !!!! does anyone remember the probe command for graphics chips? can't remember what "version" nvidia i have. I used the legacy-96xx module when with 64studio but ubuntu doen't have that..bugger. jack works, ardour etc... for now.. mick

Ubuntu (ish)

  • Quentin Harley
  • 05/24/07
  • Sat, 01/03/2009 - 19:51
The packages will come from Ubuntu, but the kernel will be 64 Studio home brew...


  • sydb
  • 06/05/07
  • Sat, 01/03/2009 - 17:56
Does this mean that 64 Studio is going to based on Ubuntu from now on? -- Michael Pacey

Giving it a try.

  • mick.ca
  • 05/23/07
  • Sat, 01/03/2009 - 16:47
I'm downloading the .iso now. I will try an upgrade as i always do...i.e. keeping home partition in tack and installing to the root partition the upgrade. I realize that each time some 3rd party apps that are used need reinstalling. So i will update as to how that goes from a 3.0 alpha state. I have had problems in the past with locales so i'm crossing my fingers and going for it... someone mentioned a possible need for ubuntu repos after upgrade? if so, which are you using? could you post your "post-upgrade" sources.list? OR will these be there in place already? cheers MiCK

64studio 3.0 alpha

  • skullnotions
  • 09/29/07
  • Fri, 01/02/2009 - 08:29
Hi Ryan, Sorry to see you had a bad time with the dist-upgrade, I hope the iso install works well for you. You have to remember, This is an alpha release, It's for testers to provide information for the future release. The alpha is changing daily, many of yesterdays issues are cleaned up today because people try the tests, and send in their reports. Looking forward to hearing how your install goes. note: The locale error I saw before, The dropping to a shell is a one I have never seen until this thread. Good luck with the new install/test. Cheers! dave

Tried to upgrade - amd64

  • sonictwin
  • 07/18/08
  • Fri, 01/02/2009 - 01:07
Tried to upgrade from a fresh install of 2.1. Install went find, except during the first half perl was crying about setting locale failed. Is this normal? Well after reboot, I'm getting the same error as peterv. Check root = bootarg cat /proc/cmdline or missing modules, devices: cat /proc/modules 1s /dev ALERT! /dev/sda2 does not exist. Dropping to a shell! I booted into a live version of ubuntu and mounted my partition and changed all UUID back to /dev/sda* under /etc/fstab -- thinking this would fix it. That didn't quite do the trick. Now I'm getting IRQ errors, kernel bugs notification,, and sata errors.. Well, I'm downloading the .iso right now, before I install it I'll go back and get the output of those errors. I was frustrated and didnt feel like writing... Cheers! Ryan

64studio_master_i386 install

  • skullnotions
  • 09/29/07
  • Thu, 01/01/2009 - 22:47
Hi, Installed here without problems, The only things I've found to do so far are: sudo mkdir /usr/share/backgrounds sudo cp (your wallpaper) /usr/share/backgrounds I had to re-set qjackctl for realtime. Great work Free, Cheers! dave

New news from Free!!!

  • Quentin Harley
  • 05/24/07
  • Thu, 01/01/2009 - 18:54


as many 64 Studio users are start asking for installable ISOs of the
3.0 alpha release, here we go:


Please keep in mind that all this is ALPHA software and you might hit
bugs, so reports are welcome!

I've tested i386 version, which should be reasonably usable, while the
amd64 is pretty untested.



64studio 3.0 alpha notes

  • skullnotions
  • 09/29/07
  • Thu, 01/01/2009 - 11:02
Notes: Once you complete the fresh 64studio 2.1 install and re set your sources list. apt-get install dpkg will also pull with it the lzma package. Then remove the two other packages, or you will hit errors. Changing over to the ubuntu repositories and running apt-get update will inform you need to import the ubuntu keys, here are the commands you will need. You need to select and drop them into your cosole as root. gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 40976EAF437D05B5 gpg --armor --export 40976EAF437D05B5 | sudo apt-key add - apt-get update apt-get install ubuntu-keyring apt-get install sysv-rc=2.86.ds1-14.1ubuntu45.64studio1~hardy1 The last command here will DOWNGRADE the package, just say yes. Then just continue through the howto. Cheers! dave

Hi Rudl, You need two

  • Pablo
  • 07/11/07
  • Thu, 01/01/2009 - 04:40
Hi Rudl, You need two files, the .iso and the .md5sum (the latter is not compulsory but it's strongly recommended in order to check the integrity of the .iso file before you burn it to a DVD) of the version (choose 2.1, of course) and flavour (amd64 or i386) you want to download. Take a look at your CPU info by typing in the terminal: cat /proc/cpuinfo Search on the internet for your CPU model and learn if it is 64-bit capable or not. The so-called "i386" version works for X86 (32 bit) and, also, for X86_64 and amd64. The "amd64" version only works for X86_64 and amd64 CPU's. Cheers. Pablo.

Want to do it

  • Rudl
  • 12/01/08
  • Wed, 12/31/2008 - 21:04
I want try to update. But first I have a question. Which files do I need from the list in the first download. Rudl

not working?

  • Quentin Harley
  • 05/24/07
  • Wed, 12/31/2008 - 19:49
I know Free is tinkering with the packages at the moment... Could be that you caught it a a vulnerable moment... Check back later.

Not working.

  • petervh
  • 12/31/08
  • Wed, 12/31/2008 - 18:08
So, I've attempted to upgrade to 3.0alpha twice from a fresh 64studio install (once in i386, once in amd64). The same problem has occurred both times. I manage to go through the entire install process, and then when I reboot, I receive these errors: Check root = bootarg cat /proc/cmdline or missing modules, devices: cat /proc/modules 1s /dev ALERT! /dev/hda1 does not exist. Dropping to a shell! Any idea what might have gone wrong, or where I can go from here? Thanks! - Peter

Not working. reboot error.

  • skullnotions
  • 09/29/07
  • Thu, 01/01/2009 - 10:46
Hi Peter, Not really sure here exactly where you are seeing this error? Is it after the install of 2.1 or after the dist-upgrade? I know the dist-upgrade changes the fstab file so if it's happening after the dist-upgrade it could be a conflict between the grub kernel line, and the fstab file. One could be set hda1 and the other could be a UUID reference. I have not seen this error before here. Have you tried again? Cheers! dave

64studio 3.0 alpha i386

  • skullnotions
  • 09/29/07
  • Tue, 01/27/2009 - 00:52
Hi Quentin, Installed fresh 64studio 2.1 i386 this morning and ran dist-upgrade The dist-upgrade saw a clean upgrade path. I am on with the set up and tweaks now. Edit: 27/01/2009. The "people" repository is not needed anymore, you can run the dist-upgrade without it. Cheers! dave