You are not logged in.
Pages: 1
Hi, I`m a newbie at linux and definately at CB, but I love what I see. I successfully installed 64-bit waldorf a week ago, and everything has worked just perfect, so I thought I should install 32-bit waldorf on one of my older pc`s. I downloaded the newest image, and the install seems to go just fine until it`s almost finished. Then I get a message of "media change", and "insert disc labeled gnu/linux........". I have downloaded the image several times and burned it numerous times, but every thime I get the same result. Is this something who has appeared in the latest updates of the images, or is this just related to the 32-bit version, or is it a problem with my pc?
Well, I have given up for now, and am currently installing Debian instead. I still have CB-waldorf 64-bit on my main pc, but I would have loved to have it on the old laptop also. But hey, I can play with Debian while I wait for the next update of the waldorf images, or until I can get a hold of the previous ones, or find a solution. I have googled a lot, but cant find any solutions. If anyone can point me in the right direction then I would be grateful, and even perhaps make a "donation";)
Offline
It's not just you. Waldorf is still in the "testing" phase and there are still some kinks left to be worked out. Many of the recent problems are detailed towards the end of this topic: http://crunchbanglinux.org/forums/topic … -20120924/
How did you create the CD or USB stick you are using to install with? Did you check the md5sum of the iso after you downloaded it? The recommended procedure for creating a USB stick is described here: http://crunchbanglinux.org/wiki/statler … stallation and that method usually causes fewer problems than other methods.
Last edited by pidsley (2012-09-28 02:55:12)
Offline
How did you create the CD or USB stick you are using to install with? Did you check the md5sum of the iso after you downloaded it? The recommended procedure for creating a USB stick is described here: http://crunchbanglinux.org/wiki/statler … stallation and that method usually causes fewer problems than other methods.
I burned the dvd with the image- burner integrated in Windows 7. Nope, I didn`t check the md5sum. Instead I downloaded and burned it several times. But now I suspect that somethings off with my cd-rom, so I will try the usb approach instead. I`m just a bit surprised since I had no problem with the 64-bit version a week ago. Everything worked right out of the box, and I still haven`t experienced any problem what so ever. Thanks for the links, I will check it out. I`m also going to check the md5sum on the image I`m downloading now. I`ve never had to do this before, but I guess google will tell me how:)
Offline
Things are changing rather quickly these days, and can be expected to change (sometimes with unpleasant results) from now until Wheezy freezes.
It appears that some of the bugs may be fixed in the newest images. You might want to try a new download.
Offline
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.