Text 13207, 168 rader
Skriven 2009-09-16 16:53:48 av Maurice Kinal (1:261/38)
     Kommentar till en text av Russell Tiedt
Ärende: love to hear the robin go tweet tweet tweet
===================================================
Hey Russell!

> Right, I have a Sandisk 512MB micro SD card, in a Verbatim adapter

I ran into the same problem as you with the onboard sd card reader. I can make
ramdisks work there but because of the limited ram the two neighbours in
question won't be able to get all the crow bait they need in there.  I was
toying with the idea of the initrd method instead but given their overwhelming
neediness I haven't bothered.  Also I lack a proper 32 bit development platform
at the moment and to be honest that isn't hurting my feelings any since the
p3's.

> apparently a BIOS update will fix that

If you decide to pursue that route let me know how it works out and I'll pass
the word down the line.  My best guess at this moment is the 915 chipsets on
there are a tad out of sync usb-wise with later chipsets. The Atom here is 945
and is capable of booting a fully bloated system off usb drives, including
flash and regular hd's.  It also can boot ide and I assume sata based flash
disks without any grief.  Same with the xeon guy.  However neither care to boot
the overbloated systems but they can if they want to.  Haven't tried sd cards
on either as I lack the interface for them at the moment.  Not convinced I need
to but maybe.

Anyhow, as is, you should have no problem booting a ttylinux into ram on your
eeepc as is.  The current kernel lacks the L2 driver for the network chip as
well as the wireless ath5k but we could take care of that quite readily if you
want to go that route.  You definetly have more than enough ram for this idea
and the Sandisk 512MB micro SD card is overkill but then again that will leave
you with much free disk space for whatever else you may wish it for.

> you can run multiple instances of it on different ports ...

Interesting but I am not sure why you need to do that if you're targetting a
player as opposed to a server.

> FTP is after all, a file transfer protocol, but sshfs, allows
> accessing the files as if they where on a local HDD, you can edit,
> save copy, etc, as if they where local

Understood but for a player I don't think any of it will be needed. Also sshfs
requires glib which causes suspicion to rise with me since that is the one
dependency that causes a system to become overbloated once it sinks in as a
needed dependency.  The evilness seems to begin with glib or so I've noticed.

> no need to ftp them to a local directory, edit, and ftp
> back to source

And exactly how or why is any of that is important to a player? Somewhere I
seem to have gotten my wires crossed with the original intent.

I have finally gotten the funds for that M-Audio Audiophile 192 ... , been
playing with it the last couple of days ... ,

> it sounds good, but not as good as I had hoped. (Might be due to the
> crapy wire and plugs, I had to pay ridiculous prices for, so I could
> connect it to my Hi-Fi setup ...

Yeah.  The connectors would probably be the issue.  I know when I connected the
turntable to the revolution I had problems with a couple of different rca <->
minijact adapters until stumbling onto the 'right' one. Also I upgraded the
alsa stuff here which made a HUGE difference once I got the hardware issues
resolved.  However the 182 is different since it has the proper connectors to
start with.  Which kernel version and alsa versions are you using?

> but how much this will improve sound quality is as yet unknown.

Same here but I suspect quite a bit.

> If you have a list of all the packages you used for your multi-media
> ttylinux/minimal-linux setup, it would be appreciated.

I just started a new one that I am testing so if you could wait a couple days I
might have a better answer.  If you're going to *need* things like sox and/or
ecasound then I'll have to add g++ to the development system and that will cost
me around 20-30M of real estate but offhand I am sure it is doable.  Not sure
what it'll end up costing on the target but given the last build which was
sitting around 42M I am guessing it'll take up the elbow room for a 64M ramdisk
so it looks to me like you'll need a 128M one.  I imagine the Sandisk 512MB
micro SD card is looking more attractive to this particular idea eh?  However
then you would need an adapter for ide to pull that off on the p3 target. I
haven't ever seen one of those but have seen sata ones for sd.

> Need a starting place to get this up to speed.

Understood.  Here is a list of my latest attempt at an x86_64 ttylinuxie thingy
still untested but it works in a chrooted enviroment.  I'll let you know if it
could work for your plan later but will have to add g++ into the mix if you
feel it REALLY needs it.  Personally I don't think so but then I am not much
into AV stuff so what would I know eh?

-----------------------------------------------------------
aaa_base-1.0-20090914-x86_64.tbz
attr-2.4.43-20090915-x86_64.tbz
autoconf-2.64-20090913-x86_64.tbz
automake-1.11-20090913-x86_64.tbz
bash-4.0.28-20090913-x86_64.tbz
bin86-0.16.17-20090913-x86_64.tbz
binutils-2.19.51.0.14-20090913-x86_64.tbz
bison-2.4.1-20090913-x86_64.tbz
busybox-1.15.0-20090914-x86_64.tbz
bzip2-1.0.5-20090914-x86_64.tbz
calc-2.12.4.0-20090914-x86_64.tbz
dhcpcd-4.0.13-20090914-x86_64.tbz
dmidecode-2.10-20090914-x86_64.tbz
e2fsprogs-1.41.9-20090913-x86_64.tbz
ethtool-6-20090914-x86_64.tbz
file-5.03-20090913-x86_64.tbz
flex-2.5.35-20090913-x86_64.tbz
gawk-3.1.7-20090913-x86_64.tbz
gcc-4.4.1-20090913-x86_64.tbz
gettext-0.17-20090915-x86_64.tbz
glib-2.18.4-20090915-x86_64.tbz
glibc-2.10.1-20090913-x86_64.tbz
gmp-4.3.1-20090913-x86_64.tbz
gpm-1.20.6-20090914-x86_64.tbz
gzip-1.3.12-20090914-x86_64.tbz
iptables-1.4.3.2-20090914-x86_64.tbz
kernel-2.6.31-20090914-x86_64.tbz
kernel_headers-2.6.31-20090913-x86_64.tbz
libcap-2.16-20090915-x86_64.tbz
libtool-2.2.6-20090913-x86_64.tbz
lilo-22.8-20090913-x86_64.tbz
links-2.2-20090914-x86_64.tbz
m4-1.4.13-20090913-x86_64.tbz
make-3.81-20090913-x86_64.tbz
mc-4.6.2pre1-20090915-x86_64.tbz
module-init-tools-3.10-20090914-x86_64.tbz
mpfr-2.4.1-20090913-x86_64.tbz
ncurses-5.7-20090913-x86_64.tbz
ntp-4.2.4p7-20090914-x86_64.tbz
openssh-5.2p1-20090914-x86_64.tbz
openssl-1.0.0.beta3-20090914-x86_64.tbz
pciutils-3.1.3-20090914-x86_64.tbz
perl-5.10.0-20090913-x86_64.tbz
pkg_config-0.23-20090913-x86_64.tbz
readline-6.0-20090913-x86_64.tbz
tar-1.22-20090914-x86_64.tbz
texinfo-4.13-20090913-x86_64.tbz
util_linux_ng-2.16.1-20090914-x86_64.tbz
wireless_tools-30.pre8-20090914-x86_64.tbz
xz-4.999.8beta-20090914-x86_64.tbz
zlib-1.2.3-20090913-x86_64.tbz
-----------------------------------------------------------

The above sits at around 156M and even with g++ added would still make it
attractive as a 256M ramdisk.  Also would have to add a few AV libs but I think
it might be still doable.  I can't see ditching too much of the above if the
only reason is to gain real estate for other stuff but I can get it in under
128M if I ditch some of the above without any regard to other stuff and it'll
work great for a more pure ttylinux as it sits today.

Let me know for sure what the target is and I'll adapt the above to see what is
what.  If only a media player then all I should need to add is alsa-libs and
alsa-utils and whatever media player, and there I'd strongly suggest mplayer as
it is the most capable.  None of these requires g++ though so that will
simplify everything since I won't have to rebuild the gcc package, possibly gmp
if it's g++ libs are desirable which they probably would be for fft's in the
case of the AV editors and libs that have yet to learn that straight c is the
way to go.  :::sigh:::

Kids these days.

Life is good,
Maurice

--- BBBS/LiI v4.01 Flag
 * Origin: Prism bbs (1:261/38)