Puppi Raspberry Pi Hardware

[Dave_G]

@humblesoul

I speak under correction but I think USB sound would also require drivers.

[humblesoul]

That'll teach me to click reply without reading all the preceding posts... one assumed usb sound was as generic and common as mouse, keyboard and web cam support in most distro's these days.

[Dave_G]

The reason I say that USB sound may require a driver is simply that
USB keyboards and mice are all pretty much the same so one generic driver
is suitable whereas the USB sound will be dependent on the codec chip
the manufacturer decided to use and thus would require a dedicated driver
to access the required registers to make it work.

I could be wrong though but the fact that ALSA is not included, I don't hold
out much hope that the Pi will be making any sounds as is.

[humblesoul]

Agreed, but if one is spending less than twenty quid on a computer... usb sound can be had for less than a fiver and is bound to be pretty generic at that price. Even some supposedly pro usb audio gear doesn't require drivers in windoze.

[Dave_G]

True, it all depends if any USB sound support is included in the distros
available for the Pi.
If so then theoretically one might find one (or more) USB sound adaptors
that may just work.

[sickgut]

*puff* *puff* phewww....
just catching my breathe, had a thought and came running down the mountain, i hope they put a road in so i can use a skateboard next time.

Any way, i have messed with a USB sound adaptor, its a budget behringer brand, but the interesting thing is that it works immediately in puppy 4.2, debian lenny/ squeeze and ubuntu and puppeee/ fluppy and others and windows xp with no looking around for drivers, its identified as a Generic USB sound device, aparently the hardware in these devices arent all the same but they use the same driver.... i think much the same way as external usb dvd drives and usb thumb drives all use the same set of generic drivers.

but i think most arm devices have never been made to attach usb sound devices too.... i dunno..... i would be interested if someone tests a cheapo $9 usb sound adator on one of these things.... is alsa installed at all in the software or is it there but not functioning?

[Dave_G]

sickgut wrote:

is alsa installed at all in the software or is it there but not functioning?

Judging from what Lobster wrote, I suspect that you may be heading back to the mountain very soon.
You may well be right that the generic USB Audio class driver
may not be available for ARM.

Lobster, any chance you have one of these USB audio goodies laying about
that you could try out and save sickgut the exhausting trip back up the mountain?
(The poor guy has a backpack full of mouthwash bottles, very heavy).

[prehistoric]

A video I saw via BBC showed the RPi connected to a television via HDMI. Normally, HDMI carries both digital video and digital sound. Could the assumption that people will use a television with HDMI be the key to this audio omission mystery? Generic USB audio should be a cheap alternative, but not particularly neat.

Very glad to hear that the dd problem was due to using /dev/sda1 instead of /dev/sda. You don't want to get into kernel debuggery on a system which does mysterious things with dd. I have an early netbook with a cheap SSD that looks like /dev/sda at boot and /dev/sdb later. Using dd on that is dangerous.

Been there on the powered USB hub mysteries. Another version of the problem shows up on devices like KVM switches which draw power from PS/2 ports.

Very general advice: even though you intend to squeeze your resulting system into a small SD card, use a large size, or an external USB drive, during development. (I also use unreasonably large swap partitions, so I can watch memory leaks develop before they bring a system down. Years ago this allowed me to trace a problem to a proprietary nVidia driver.) This would immediately distinguish between a restriction caused by the size of the card, and an entirely different restriction, as described above.

[Aitch]

The Pi has an HDMI combined digital video and audio o/p, as well as phono analogue video and 3.5mm audio o/p, so it IS designed for audio, and SBMC are interested as it has xbox/1080p video capabilities, apparently...so I suspect a codec issue only....there was talk of AAC licensing costs early on

http://forum.xbmc.org/showthread.php?tid=121499

Best get some skates on or XBMC will steal the glory!

Aitch

[Dave_G]

The drivers are one thing, whether they be USB, HDMI or thru the Pi's audio port.

The fact that Lobster mentioned that there is no ALSA, there is no way to "talk" to the drivers as there is no audio "core".

The way I see the Linux audio system is as follows: (could be wrong)

Code: Select all

{audio file} ----> {music app} ----> {ALSA} ----> {driver} ----> {hardware} ----> {audio out}

Hope I'm mistaken and that one of those USB thingies work.

[Lobster]

Barrys back proving that I am devolving . . .
No surprise there
http://bkhome.org/blog/?viewDetailed=02795

In other sound related news: Sound is not a priority for me. I may try my USB headphones which may have an inbuilt sound card - doubt it. Still wrestling with basic command line mayhem such as setting file permissions. Debian Squeeze for Rpi seems very much a work in progress. It will get you going for sure.

Slowly things are settling and I am making sense of the strengths and limitations of my understanding as well as hardware and software.

For those helping and wandering up and down mountains. I am reading and taking my time.

Here is something to get you riled up.
No Flash support.

OK time to continue . . .

[Aitch]

We are in this list already......

http://elinux.org/RPi_Distributions

....and Arch for Pi is CLI...apparently

http://news.techeye.net/hardware/linux- ... -available

Aitch

[sickgut]

The drivers are one thing, whether they be USB, HDMI or thru the Pi's audio port.

The fact that Lobster mentioned that there is no ALSA, there is no way to "talk" to the drivers as there is no audio "core".

The way I see the Linux audio system is as follows: (could be wrong)

Code: Select all

{audio file} ----> {music app} ----> {ALSA} ----> {driver} ----> {hardware} ----> {audio out}

Hope I'm mistaken and that one of those USB thingies work.

sorry to break from the current sound subject.
I want to ask people about clusters because altho the cpu in the Rasp Pi is lame, the video chip is very good, also 256mb ram is quite good also, altho the ethernet isnt gigabit, a gigabit ethernet adaptor could be used on the usb port. Is the usb port version 2.0? i hope it is.

new supercomputers are just clusters but the new ones also have the mechanizm to access GPUs to add to the processing capability just like a normal CPU, so a typical "blade" has 2x cpus on one motherboard and one high end video chip that adds a huge performance increase over just accessing cpus as processing power.

Is anyone here familiar with setting up clusters, and if so is it a simple affair to use attached gpus for processing power, is that a default option in the OS that lets you do this, or is this something very special and out of the reach of normal people?

The appeal of running alot of Rasp Pi in one huge cluster is no need to spend alot of money on cooling, and space is saved as well as power consumption. If the software is ready to access the gpu of the rasp to add this to the pool of processing power, it could actually be reasonably ok, not realy as a price perforamance thing but more like power consumption and maybe space and the ease of adding more "blades" later on and in the event of a failed "blade" its very simple to replace and inexpensive. The cost of a huge air conditioning system is saved and so is the maintanence on alot of water cooling compared to using high end cpus and or cpu fans. Ofcause with so many rasp pi crammed together the heat problem is more than a single rasp standing by itself, but i suspect just one large air forced fan blowing over 30 of them will be enough to keep the air circulating.

anyway.... if anyone knows about clusters accessing gpus then let me know

[Dave_G]

sickgut

I now nothing about clusters, just thinking out aloud here.
Presumably how clustering works is the processing cycles are distributed
amongst many CPUs/GPUs.

If this is indeed the case, then there must be some kind of high speed interconnecting "channel/s"
between the CPU's/GPU's to distribute and collect the data once it's been "crunched".
Surely even USB 2.0 at 480Mbps would create a bottle neck once a cluster
of a certain size has been exceeded?

Just a thought.

[sickgut]

sickgut

I now nothing about clusters, just thinking out aloud here.
Presumably how clustering works is the processing cycles are distributed
amongst many CPUs/GPUs.

If this is indeed the case, then there must be some kind of high speed interconnecting "channel/s"
between the CPU's/GPU's to distribute and collect the data once it's been "crunched".
Surely even USB 2.0 at 480Mbps would create a bottle neck once a cluster
of a certain size has been exceeded?

Just a thought.

i think the inability of the rasp pi to actually pump out processed data at 480Mbs a second would mean it isnt much of an issue as a bottle neck.. dont quote me tho.. just spitting out loud aswell. but yeah... unless we have good networking, you might as well thow it all in the bin. I need to research how much bandwidth is actually used in a gigabit cluster 480Mbs is almost half that speed... my instincts tell me the bottle neck would still be the rasp pi slow processing power...

i have placed an order for one but depending on what i can prioritize here at home, maybe ill order 10 of them just for giggles and try it all out. If it doesnt work out then i can give most of them away as presents to people who would like to have one.

i really do see the Rasp Pi as the perfect platform to bring linux gaming in a semi console format to the masses, but ofcause its not going to go anywhere without any sound how it is now.

[Dave_G]

I remember seeing a video on the Raspberry site where several (can't recall exact number)
of RPI's connected to each other (via ethernet presumably) and driving
a video wall of equal number of screens displaying HDMI video.
Maybe you want to check it out as a starting point.

[Lobster]

The Rpi 'B' - the one with ethernet has 512MB of ram not 256MB (the early boards had 256)

Lobster edit - WRONG Lobster - see later post

Got JWM installed
went to command line by logging out but it needs a parameter to run something like
jwm -display x (where x is the type of display or res or some sort) . . .

[Dave_G]

Lobster

Perhaps the X is display number (0, 1, etc etc)
That is what I would try, what's the worst that can happen?
Are there no man pages or other help for JWM?

[puppy_apprentice]

The Rpi 'B' - the one with ethernet has 512MB of ram not 256MB (the early boards had 256)

Wikipedia, RPi FAQ and every article i've read mention only about 256MB of RAM - maybe u as a developer got a one with bigger memory or somebody from RPi is lazy to change the data

btw. i will by my RPi only when Puppy will be ready ;p

[Lobster]

Perhaps the X is display number (0, 1, etc etc)

Good plan for later
The TV has been claimed by those wishing to watch 'Telly' - whatever that is . . .

oh my mistake the model A was upgraded from 128MB to 256MB
sorry for the confusion
http://www.raspberrypi.org/faqs

OK that means Puppy will be using his full skill set to get a small ISO image

I am glad people are inspired to buy the hardware.
I am on a steep learning curve.

I have plans about what I can realistically achieve.

meanwhile in the future . . .
A cluster game console? . . . well the Rpi could be combined with an extension board and a cluster of off the shelf GPU cards for some major rendering

One extension board is the Gert
there will be more:
http://elinux.org/RPi_Expansion_Boards#GertBoard