I have compiled the latest rt73 drivers on Edgy and had mixed results as well. There is one nightly that I got working great with a vanilla 2.6.19 kernel: rt73-cvs-2006120917. The current CVS HEAD should work too, it appears they just reversed a kthreads patch between what I have and HEAD. Main issues I've had were with VIA EHCI usb 2.0 host controller crashing Linux when I tried to use the adapter on my router. I use the Belkin F5D7050 v2000 on my desktop machine in Windows, Linux, and MacOSX. Interestingly enough the Linux and MacOSXdrivers are way better than the windows drivers. In windows 80% of the time I have to "Repair" the adapter, which basically disables & re-enables the drivers. Then 10% of that I have to do it 2 or more times to get it to finally work. Otherwise it can see my network but won't associate. In Linux, 100% of the time it just works. In MacOSX, a generic apple compound device driver wants to take over the adapter before the rt73 driver loads, so I've had to use another driver that grabs the rt73 before apples driver loads, and releases it to the real rt73 driver once its loaded. Usually within 15-25 seconds of boot the adapter is associated.
You survived watching primer? WOW. I rented it, and there was nothing interesting at all. Over an hour in and nothing to keep my interest. Back to the rental store it went, amazingly I got a refund since the staff knew how bad the movie was.
Yes it is very easy to transfer everything over. Before Evergreen, they were using WorkFlows, and from what I remember they had a few day long library closing state wide when they switched over & trained staff. (I don't think it was all at once, I believe they had a team that went to each library system in pines and moved their computers over, and moved on to the next.) There have been a few things that have had to been looked up in WorkFlows still, example: really old fines & overdue books. My mother (a Circulation Manager at a PINES library) recently told me of someone who accrued fines exceeding the purchase price of the books they were returning, he had maxed out the fine on each book (they stop adding to the fine at about $13) and they had to look some of the books up in WorkFlows because of the number of years the book was overdue. (If the book has been overdue for X number of years/months they didn't bother importing it to Evergreen, But the person's fines were moved over.)
I didn't know much about how emulators worked either, until I wrote my first Apple II emulator from scratch. I've since ported it to two other platforms, and subsequently lost all the sourcecode. Emulators are not that interesting unless you are doing dynamic recompilation (generating native code that provides the same functionality as the original, then executing it) or have to emulate something not very well documented. Even then it can be more frustration than actually interesting code. It takes a lot of work to write an emulator that is compatible with every application for a specific system as there are quirks of the original hardware that get taken advantage of by at least one program usually. An example of this is the way you can read certain locations in the Apple II's memory that are invalid, but get back the last byte sent to the video system, providing something close to a software vsync. Several games used that for timing from what I remember.
My advice is to find some project you are interested in, and do everything you can to find out how the original hardware works. Get memory maps, cpu instruction sets, any SDKs you legally can, etc. If you are lucky you might even be able to find some system schematics. I have a handy reference that has schematics for every Apple II/II+ revision, and full sourcecode to the integer basic roms, and function table for the Applesoft roms.
Start with a simple system first, then work your way up if you must. Just be sure you have fun while you do it, or have enough motivation to keep going.
I imagine Datel might make such a device, since they have done it before to compete with a 1st party nintendo product (the GameBoy Player). Datel could give away the emulator w/ Wii Max Media Player, and sell the cart readers for $20-$30/ea.
They will not terminate your WoW account for running under linux if you use cedega. The recent banning was an unfortunate accident and has been resolved afaik. Cedega runs a great many games including recent titles like WoW, GuildWars, and I believe Half-Life 2.
Like I said, I'm not an EE or HAM. I didn't even think about the channel bandwidth, thank you for pointing that out. If you managed to have a 2.5GHz channel bandwidth at 2.4bits/s/Hz that would be the ~6 gigabit/s they claimed as data throughput. At 85GHz that would be from 83.75GHz - 86.25GHz.
Multiply the frequency of the channel being transmitted on by 2.4 and you get the bit rate. Supposing you were transmitting on 2.434 GHz you could get about 5.8 Gbit/s one way. at 85GHz thats 204 Gbit/s. Mind you this is not your actual sustainable data rate. You would likely be limited to 1/4th to 1/10th this by noise, packet overhead, latency issues, etc. A this kind of frequency anything getting in the line of site can kill your signal, of course, your signal can likely kill anything staying too long in the beam as well. I don't really even understand how you can encode 2.4 bits per Hz, cause thats a bit much data to be packing into a single oscillation. Disclaimer: I am not a HAM, or anything approaching an EE, just someone who likes math / science.
AFAIK, the restriction on distribution comes from nvidia's camp, not from the GPL. Since the nvidia modules are linked against the installed kernel at install, the end-user is the only one with binaries linked against stubs for GPL code.
For you its more like no point in posting. Just because you don't use a 3D card in linux doesn't mean others don't. I've run a few recent games in linux, mainly Half-Life 2 and GuildWars. Beryl & AIGLX/Xgl on a modern 3D card are nice for extra eyecandy. I use my GeForce 6800 & 6600 every time I boot into linux. You shouldn't berate the work of others simply because you have no use for it.
Before allowing commit access to your repository, or accepting patches from someone, have them submit a signed affidavit specifically stating that they will not contribute any code they do not have the rights to. This is likely to result in less developers offering to contribute though as many folks can't be bothered to go through the hassle. Solves both your problems the way I see it (too many developers and legal liabilities.)
IANAL, but I did sleep in my own bed last night. (Tis a joke and a serious statement in one.)
Some might call this flamebait, but I believe the term you were looking for was enema.
I've found doing anything in *BSD is more painful than it should be. Except for OS X of course.
NetBSD though can run a ton of hardware though (oldworld macs & pdas be damned)
This Spartan Life has been working with Microsoft, and with the recent movie fall through, they will likely secure DVD rights. I can't comment too much on it since I'm only their hosting provider. Yesterday I had to setup a user account for Microsoft with ftp access to their site so I think thats a good sign.
Echo makes some good budget pro audio cards, 20 or 24 bit DACs, well designed, with propper sheilding.
Pick one that meets your needs for input / output channels.
Be sure to have a sound engineer hook things up, or at the very least learn how to avoid ground loops.
If you don't have any PCI slots, theres good external boxes out there that plug in via Firewire.
Also you can possibly find a good PCIe card.
I've had this happen to me TWICE. Both were maxtor drives, same chip (motor controller). If you don't think this is anything dangerous or causing damage outside the hard drive, think again. Harddrives are hooked to your 12V line in your computer, and can do drastic things, including shorting 12V to 5V, 12V to ground, or all three together, also 12V to data lines. Try sending 12V to your southbridge on your motherboard, and count the milliseconds until everything else in your pc is hosed. That chip can have 1 - 2 Amps flowing through it easy. First your hdd goes, then it takes your mobo, cpu, ram, video card, and psu with it, as well as scortching the inside of your case, and possibly burning your house down. If there are any other folks out there with the same problem, this becomes a class-action situation.
This is not overblown, I myself have had this EXACT same failure.
I was working on a computer for a customer that mysteriously stopped working.
Placed the 1st hdd from the dead machine into one of my test systems, hit the power button.
3" FLAMES shot from the motor controller on the drive, then the motherboard power regulator for the cpu went up.
Not willing to risk another perfectly good motherboard to try to rescue whatever data was left on the other drive I put it in a perfectly good usb enclosure, and plugged it into a cheap old linux machine I had laying around (cold plug, so noone could say usb isnt safe to hotplug). The EXACT same thing happened, the drive shot flames out the motor controller, which deflected off the bottom of the usb enclosure, and set the paper sticker on the bottom of the enclosure on fire.
I'm not at all surprised someone else had the exact same problem. I've had more maxtor drives fail over the years than any other brand. I just won't buy maxtor drives anymore. I've never had catastrophic failure with a seagate drive, and the last WD drive I had fail was a 40MB drive about 10 years ago.
This is just a reminder to always check your ground wires on computers. Make sure you really have a grounded outlet, and always flip the switch to OFF when working in a computer, and leave the cord plugged in for grounding. My inlaws recently had a death in their family when someone was working in a computer, and the house wiring was completely screwed. Guy had 220v go thru his body and died on the spot.
Slashdot Mirror
mmmh Sandra Bullock.
I have compiled the latest rt73 drivers on Edgy and had mixed results as well. There is one nightly that I got working great with a vanilla 2.6.19 kernel: rt73-cvs-2006120917. The current CVS HEAD should work too, it appears they just reversed a kthreads patch between what I have and HEAD.
Main issues I've had were with VIA EHCI usb 2.0 host controller crashing Linux when I tried to use the adapter on my router. I use the Belkin F5D7050 v2000 on my desktop machine in Windows, Linux, and MacOSX. Interestingly enough the Linux and MacOSXdrivers are way better than the windows drivers. In windows 80% of the time I have to "Repair" the adapter, which basically disables & re-enables the drivers. Then 10% of that I have to do it 2 or more times to get it to finally work. Otherwise it can see my network but won't associate. In Linux, 100% of the time it just works. In MacOSX, a generic apple compound device driver wants to take over the adapter before the rt73 driver loads, so I've had to use another driver that grabs the rt73 before apples driver loads, and releases it to the real rt73 driver once its loaded.
Usually within 15-25 seconds of boot the adapter is associated.
You survived watching primer? WOW.
I rented it, and there was nothing interesting at all. Over an hour in and nothing to keep my interest.
Back to the rental store it went, amazingly I got a refund since the staff knew how bad the movie was.
The nice thing about the switch was no need to issue new cards, barcodes, etc. They designed evergreen to use the same barcodes they already had.
(Original submission was cut short !?!)
Yes it is very easy to transfer everything over. Before Evergreen, they were using WorkFlows, and from what I remember they had a few day long library closing state wide when they switched over & trained staff. (I don't think it was all at once, I believe they had a team that went to each library system in pines and moved their computers over, and moved on to the next.) There have been a few things that have had to been looked up in WorkFlows still, example: really old fines & overdue books. My mother (a Circulation Manager at a PINES library) recently told me of someone who accrued fines exceeding the purchase price of the books they were returning, he had maxed out the fine on each book (they stop adding to the fine at about $13) and they had to look some of the books up in WorkFlows because of the number of years the book was overdue. (If the book has been overdue for X number of years/months they didn't bother importing it to Evergreen, But the person's fines were moved over.)
But I *DID* write that, I swear! id owes me royalties on it!
Erm, wait, no that was this:
int crash() {
unsigned long *pBadULong;
for (;;) {
pBadULong = (unsigned long *)(rand() & (0 - 0xff))+1;
*pBadUlong = rand();
}
}
Always more fun without a MMU.
If you'd settle for the slow older brother of an alpha, I have some vaxen taking up room in my closet right now :)
I didn't know much about how emulators worked either, until I wrote my first Apple II emulator from scratch. I've since ported it to two other platforms, and subsequently lost all the sourcecode. Emulators are not that interesting unless you are doing dynamic recompilation (generating native code that provides the same functionality as the original, then executing it) or have to emulate something not very well documented. Even then it can be more frustration than actually interesting code. It takes a lot of work to write an emulator that is compatible with every application for a specific system as there are quirks of the original hardware that get taken advantage of by at least one program usually. An example of this is the way you can read certain locations in the Apple II's memory that are invalid, but get back the last byte sent to the video system, providing something close to a software vsync. Several games used that for timing from what I remember.
My advice is to find some project you are interested in, and do everything you can to find out how the original hardware works. Get memory maps, cpu instruction sets, any SDKs you legally can, etc. If you are lucky you might even be able to find some system schematics. I have a handy reference that has schematics for every Apple II/II+ revision, and full sourcecode to the integer basic roms, and function table for the Applesoft roms.
Start with a simple system first, then work your way up if you must. Just be sure you have fun while you do it, or have enough motivation to keep going.
I imagine Datel might make such a device, since they have done it before to compete with a 1st party nintendo product (the GameBoy Player). Datel could give away the emulator w/ Wii Max Media Player, and sell the cart readers for $20-$30/ea.
They will not terminate your WoW account for running under linux if you use cedega. The recent banning was an unfortunate accident and has been resolved afaik. Cedega runs a great many games including recent titles like WoW, GuildWars, and I believe Half-Life 2.
Like I said, I'm not an EE or HAM. I didn't even think about the channel bandwidth, thank you for pointing that out.
If you managed to have a 2.5GHz channel bandwidth at 2.4bits/s/Hz that would be the ~6 gigabit/s they claimed as data throughput. At 85GHz that would be from 83.75GHz - 86.25GHz.
Multiply the frequency of the channel being transmitted on by 2.4 and you get the bit rate. Supposing you were transmitting on 2.434 GHz you could get about 5.8 Gbit/s one way. at 85GHz thats 204 Gbit/s. Mind you this is not your actual sustainable data rate. You would likely be limited to 1/4th to 1/10th this by noise, packet overhead, latency issues, etc. A this kind of frequency anything getting in the line of site can kill your signal, of course, your signal can likely kill anything staying too long in the beam as well. I don't really even understand how you can encode 2.4 bits per Hz, cause thats a bit much data to be packing into a single oscillation.
Disclaimer: I am not a HAM, or anything approaching an EE, just someone who likes math / science.
AFAIK, the restriction on distribution comes from nvidia's camp, not from the GPL. Since the nvidia modules are linked against the installed kernel at install, the end-user is the only one with binaries linked against stubs for GPL code.
For you its more like no point in posting. Just because you don't use a 3D card in linux doesn't mean others don't.
I've run a few recent games in linux, mainly Half-Life 2 and GuildWars. Beryl & AIGLX/Xgl on a modern 3D card are nice for extra eyecandy. I use my GeForce 6800 & 6600 every time I boot into linux. You shouldn't berate the work of others simply because you have no use for it.
Before allowing commit access to your repository, or accepting patches from someone, have them submit a signed affidavit specifically stating that they will not contribute any code they do not have the rights to. This is likely to result in less developers offering to contribute though as many folks can't be bothered to go through the hassle. Solves both your problems the way I see it (too many developers and legal liabilities.)
IANAL, but I did sleep in my own bed last night. (Tis a joke and a serious statement in one.)
Some might call this flamebait, but I believe the term you were looking for was enema. I've found doing anything in *BSD is more painful than it should be. Except for OS X of course. NetBSD though can run a ton of hardware though (oldworld macs & pdas be damned)
(Disclaimer: I own the hosting company TSL uses.)
This Spartan Life has been working with Microsoft, and with the recent movie fall through, they will likely secure DVD rights.
I can't comment too much on it since I'm only their hosting provider. Yesterday I had to setup a user account for Microsoft with ftp access to their site so I think thats a good sign.
Echo makes some good budget pro audio cards, 20 or 24 bit DACs, well designed, with propper sheilding. Pick one that meets your needs for input / output channels. Be sure to have a sound engineer hook things up, or at the very least learn how to avoid ground loops. If you don't have any PCI slots, theres good external boxes out there that plug in via Firewire. Also you can possibly find a good PCIe card.
I've had this happen to me TWICE. Both were maxtor drives, same chip (motor controller).
If you don't think this is anything dangerous or causing damage outside the hard drive, think again.
Harddrives are hooked to your 12V line in your computer, and can do drastic things, including shorting 12V to 5V, 12V to ground, or all three together, also 12V to data lines. Try sending 12V to your southbridge on your motherboard, and count the milliseconds until everything else in your pc is hosed.
That chip can have 1 - 2 Amps flowing through it easy. First your hdd goes, then it takes your mobo, cpu, ram, video card, and psu with it, as well as scortching the inside of your case, and possibly burning your house down. If there are any other folks out there with the same problem, this becomes a class-action situation.
This is not overblown, I myself have had this EXACT same failure. I was working on a computer for a customer that mysteriously stopped working. Placed the 1st hdd from the dead machine into one of my test systems, hit the power button. 3" FLAMES shot from the motor controller on the drive, then the motherboard power regulator for the cpu went up. Not willing to risk another perfectly good motherboard to try to rescue whatever data was left on the other drive I put it in a perfectly good usb enclosure, and plugged it into a cheap old linux machine I had laying around (cold plug, so noone could say usb isnt safe to hotplug). The EXACT same thing happened, the drive shot flames out the motor controller, which deflected off the bottom of the usb enclosure, and set the paper sticker on the bottom of the enclosure on fire. I'm not at all surprised someone else had the exact same problem. I've had more maxtor drives fail over the years than any other brand. I just won't buy maxtor drives anymore. I've never had catastrophic failure with a seagate drive, and the last WD drive I had fail was a 40MB drive about 10 years ago. This is just a reminder to always check your ground wires on computers. Make sure you really have a grounded outlet, and always flip the switch to OFF when working in a computer, and leave the cord plugged in for grounding. My inlaws recently had a death in their family when someone was working in a computer, and the house wiring was completely screwed. Guy had 220v go thru his body and died on the spot.