I assume SATA doesn't have this problem.
I also noticed after going over my dmesg god knows how many times that linux can detect a 40 pin cable vs 80 pin, and only does ata33 with a 40 pin cable. So I put a 80 in on there (wasn't sure it would work since the port on the motherboard wasn't blue) but I guess that's just to tell you which is primary, because it worked, now they both run at ata133.
I would think I'd do better than that though. I was thinking closer to twice as fast, but hey, I'll take anything that's free.
For various reasons which are not very interesting right now, my home server is running Ubuntu. Normally I run CentOS on servers, which has a lovely file called /etc/modprobe.conf that specifies (among other things) which SCSI driver you want to use. I don't see that on Ubuntu (which I'm assuming is the same as Debian for this purpose). As far as I can tell, they seem to have made this type of thing completely automatic. Am I correct in guessing that it figures out The Right Thing To To (tm) on *every* boot, so when I move my disks over to a machine with a different SCSI chipset, it'll load the correct driver automatically?
I'm using modconf to configure the modules to be loaded in debian. nice curses frontend.
I need a program to convert some podcasts to WAV format from MP3. I want to burn a standard audio disc as the player in my car can not handle MP3s. Any suggestions? I'm running Fedora 11 if that matters.
mpg123 -w filename.wav filename.mp3
Well..that sounds interesting...for a few minutes. Everyone sounds like Alvin, Theodore, and Simon. I see no options for changing playback speed. I'll keep searching. But thanks anyways.
I'm using modconf to configure the modules to be loaded in debian. nice
Ok, I loaded it up, and it looks useful. So does that mean that if I want to change my boot device to use a different scsi driver, I need to run modconf, put the correct driver in, and then mkinitrd?
ya know, I'm one of those not using vanilla kernels. I don't like initrd's, my kernel has the needed-for-boot stuff inside as I put it inside.
habard, probably k3b will bring something and hide the commandline tools behind the scenes.
k3b kicks ass.
YMMV of course, but I just did the big switchover.
I was able to connect to the office vpn and remote desktop in a vm in my new ubuntu install on my new machine, so it's now my new machine.
I'm impressed how well it did when I plugged everything in like second monitor and bluetooth and stuff.
thunderbird choked the first time I set it up, it downloaded all my mail then deleted it. hmmm...
And the video driver couldn't parse and therefore save my two monitor setup, so I have a feeling I'll have to do that on every boot....
But it's just nauseatingly fast. It's really not sane.
I synaptic install it, and then go add applet and it's not there.
How on earth to I make that go?
I'm backing up my other linux box to this one, running w2k in a vm for work so I can do some work, installing xp in another vm and the machine is practically idle, no swap, and the only thing going is network.
It should be illegal to have this much power on your desk.
People should suffer when using computers, I have been for 20 years, why not everybody else.
But it works, so, good enough. yay wine
Of course it doesn't recognize my camera exactly, and it won't write to my network drive when I finally figure out how to get it to find the camera's pictures. But progress all the same.
I just got my treo to sync with my XP vm, via bluetooth, can't get it to work on the cable yet, but still working on that.
Still fighting with the treo stuff, but I'm making progress.
But I have 2 fun questions for you guys.
linux has a system beep, it actually beeps the computer's speaker a la bootup when I make an error.
I want to turn that off. How? It does it in lots of applications, so it's not just a terminal thing.
And every once in a while something goes "doo doo doo" in descening pitch, then a few seconds later, in the reverse order.
As if something was disconnecting then reconnecting.
It's not in the sound options, so what the hell is it? nothing in syslog either.
Can't find the doo doo doo one though.