<div dir="ltr"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gustin Johnson wrote:<br>
What are the hardware specs of your desktop and what soundcard/midi<br>
controller are you using?</blockquote><div><br>AMD 64 2800+, 1GB, M-Audio Ozone Academic (USB keyboard/MIDI/audio interface, originally bundled with Pro Tools M-Powered Academic bundle. Kernel support added for this device in the main kernel tree, late 2007, then integrated into the Hardy kernel)<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Do you have any extra boot options in your<br>
menu.lst (eg. noacpi or some such)?</blockquote><div><br>I don't see any. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
You mentioned that you had 64Studio installed, does it fare any better<br>
with your hardware? I have 64Studio on my Desktop and Ubuntu for my<br>
laptop and am familiar (and happy) with both distros.</blockquote><div><br>I have never been able to get 64 Studio to recognize my audio/midi hardware, even though I updated it fairly recently. I haven't checked to see what kernel they're currently using. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
-On Wed, 16 Jul 2008, Cory K. wrote:<br>
<br>
I'm going to suggest a clean reinstall of Ubuntu Studio-Hardy on the box<br>
in question *if* you really wanna see if it's the HW or your<br>
configuration. Feisty->Gutsy->Hardy. Many things could have happened<br>
over this time frame.<br>
<br>
-Cory K.</blockquote><div><br>I've been leaning towards this, moving files and directories I want to save to external drives in preparation for it. Three things are hindering this effort:<br><br>1). I still have to learn how to clone my old /home directory into a new installation. I could leave it in the containing file and just copy it into the new /home, but I would rather have it just become the new /home. I'm not sure I'm being clear--<br>
<br>I don't think I want to end up with /home/pad/old_pad, with old_pad being the home folder I saved from the old installation. (My user name is pad.) Rather, I want /home/pad to just be the original /home/pad, with the addition of whatever Ubuntu puts in your home folder by default, such as examples and whatnot. I don't know how to accomplish this other than moving files one at a time into the new /home/pad. Surely there's an easier and more elegant way? Also, not sure if I need the entire /home directory, or just my user (pad) directory to come over.<br>
<br>2) With the availability of the new 64-bit version, I'd rather install that. (Recall that I have an AMD 64-based system). I'm not sure if some things get stored in the home folder that will not be compatible between 32-bit and 64-bit systems. There are all kinds of hidden files that I take to be configuration files, and who knows what else. I don't know if I will break a whole bunch of stuff by attempting to use my old user folder in a new, 64-bit system.<br>
<br>Maybe I should compromise, by moving my /home into its own partition, then installing the 64-bit with its own /home. I can then mount the other /home partition to access files as needed, keeping the /home within the new installation as the default /home. The disadvantage is I won't be able to have the default /home on its own partition--or maybe I can? Just have two different /home partitions with different names, and point to one as the default?<br>
<br>This is way more complicated than I'd like. Much simpler and more elegant to integrate the old into the new. But I'm now sure about the procedure, and what to do about any files that might mess up a 64-bit system.<br>
<br>3) I've noticed I have all the sound (but not MIDI) funtioning on the 2.6.22-xx kernels, but NOT the 2.6.24-xx kernels. That M-Audio thing is not detected--even though the 2.6.24-xx kernels work fine with it on the MacBook, including the new-to-Hardy MIDI functionality. On the desktop, with the ~.24 kernels I can't even listen to .mp3s, no system sounds, nothing. Who knows if I will have no sound at all with a clean reinstall, and if I will be able to fix it if it doesn't work? So I'm a little stuck right now.<br>
<br>Thanks for working with me, I don't know what I'd do otherwise.<br><br>--PD<br></div></div><br></div>