Bad, bad idea. With my cheap hot air rework blower alone (without flux!) I can do a better job than the guy in the tutorial did, and in seven seconds instead of four hours. Getting SMT chips ONTO boards is a whole different story. With hot air, chips just fall off of a board, but very good alignment and pressure are necessary to get smt chips on. It becomes necessary to remove the solder from the board pads after a chip is removed if another chip is to be installed in its place. If this is not done the next chip will be resting its leads on thin solder mounds instead of the flat pad conductors. Look at figure 23 in that tutorial and you'll see what you are usually working with: cheap FR4 boards with copper platings glued-on. It's easy to understand why a soldering iron is not the best tool for rework. When chips start being produced solely in BGA or similar formats and when most conductors start getting placed primary on the inner-layers of boards (many motherboards have about seven layers) rework will become much more difficult if not impossible without very expensive equipment (high temperature, lead-free solder isn't helping). There are machines that remove and replace BGA chips but they are not exactly in reach of experimenter hands (wouldn't you rather add another floor to your house?). For those not familiar with BGA, it means that the chip contacts are in the format of little balls situated on the UNDERSIDE of the chip. Removing such chips often means preheating the board directly followed by mechanical removal. Consider BGA the exact opposite of a socketed chip. _________________ BNP.org.uk
Posted: Mon Oct 01, 2007 18:41 Post subject: Transmission problems
Optware is fabulous, but I'm having tremendous problems at getting transmission to work.
I have Asus WL500GP with 1GB ext3 and 200GB vfat. I first had 128MB swapfile on ext3 but added additional 512MB to be sure. Although haven't never seen transmission using any swap jet. I'm running slightly customized DD-WRT 24 RC3.
So I created ./torrent/ file to vfat and mounted it with umask=000 to have permissions. Samba2 is also working fine. I use Asus only via wds or lan (so no wan connected). I don't know has this anyting to do with my problems.
So when I fetch or put *.torrent directly to source dir, it gives errors and doesn't show any seeds or peers. Also I got guite often segmentation faults when for examle doing list on torrents like:
I have tryed almost everything but didn't found out whats wrong.
Is there problems with cron, vfat, swap, .state .info files, wrong libraries, wrong configs (transmission or thttpd), wrong unset libraries or what?
Do you get an core files in torrent/.transmission dir? I confess that previous versions (last year) worked better than 0.82 but if you prepared to analyze or wait you could do this by compiling on router with libefence and debug turned on and use gdb to spot the problem. Then post a ticket to http://transmission.m0k.org/trac
There is transmission-cli that works from command line. If you have troubles with it then it shoul be shown also from that utility. I am no aware of all the kernel changes of the dd-wrt from v23 to v24 as i am not using dd-wrt for many optware things, notably transmission. So report what are you doing with transmission-cli and then we could proceed.
For transmission I am using Kamikaze and opwnwrt-brcm24 feed.
vfat is problematic in several ways. This is only FAT with added suport for long names.
It is not needed nor recommended to run unix programs on non-unix filesystems. So basically you want to run unix of DOS filesystem.
Yeah, I knew some restrictions (for example <4GB files) but thought that it would be useful to have posibility to mount also on Win systems.
But ditched it already.
Found out that e2fstools mkfs.ext3 doesn't know how to correctly create journal (bug?) and was forced to use ext2.
But still have problems. Now it correctly downloads some torrents, but especialy bigger ones (I have 1GB opt and 199GB for rest) >1GB (also smaller) it gives errors:
Error: Insufficient free space Start: 03 Oct 21:08 uploaded: 48.5 MB
Error: Generic I/O error Start: 03 Oct 21:08 uploaded: 0.0 MB
Didn't figure this out jet. I first thought that when I used ln -s /xyz/abc/torrent to create /opt/torrent it was calculating space from /opt but it gives same if I mount 199GB to /mnt and change torrent in transmission.conf to point /mnt/torrent.
btw. Still haven't seen any major swapping on 32MB WL500GP. Only on fromatting ext2 it used some swap.
hi there... nice work + good documentation in the wiki!
is there any chance of getting transmission work with fat? the thing is that i just poreted the disk from ext to fat because of some lame osx and windows machines which where to stupid to handle ext (even with installed ext-support). and i have to say that i doesnt understand the problem. the fat drive i only used to store the files or am i wrong?
so where is the problem?
i've seen some webtransmission-mods with fat support, is this possible here to?
so thx again and bye,