Anybody got xbmc(or full HD playback) working with pi?

I tried Raspbmc and it played 720p files very well.
Haven't tried standard 1080p files yet, but tried a heavy video file with 38 Mbps (Samsung The Beauty of Nature) and it only showed black screen.

Wait, is Raspbmc a software or an OS itself?

EDIT: It looks like a distro to me . I really wish to get full HD playback working with Slackware. I tried compiling xbmc but it failed. ffmpeg worked though.

hi drmozes, if you are checking this "forum", are there any chances of updating your http://www.daves-collective.co.uk/ra...01Aug12.img.xz with it's included raspi kernel packages to a slackware 14.0 version? It would be great to use the same kernel version as armedslack 14.0 uses, and would make compiling kernel modules easier. ps. appreciate the work you've done on it already.

timsoft, that is maintained by David Spencer (55020), not Stuart Winter (drmozes) http://www.daves-collective.co.uk/raspi/

and just to report good news, from now on raspberrypi model B are shipped with 512Mb of RAM
http://www.raspberrypi.org/archives/2180

thanks ponce, and that is good news. I'll just have to get another one with the extra ram :-) , and I'll send an email direct to david. his current install image has an earlier raspberrypi kernel version than the rest of armedslack. I can copy the updated binary blobs onto the boot partition, but creating armedslack raspberrypi kernel install packages myself is getting beyond what I have currently attempted and would probably be duplicating dave's work anyway. hopefully he'll have time to update his install image .

if your problem is the kernel version, you'll have to wait for updates from the raspberrypi's people: that's the modified kernel version they offered for the device until a few days ago, you can't use slackwarearm kernels on it.

they updated recently to 3.2.27, but I haven't tried it yet and I don't know how stable it is.

https://github.com/raspberrypi/linux

yes, my problem is I want to build a rtc kernel module, however the kernel src framework (from armedslack) (/usr/src/linux) is for kernel 3.4.11 and the actual kernel (courtesy of dave) (uname -r) is 3.1.9-20120801

It might might be a bit off-topic I'm not sure, but any pointers would be greatly appreciated. I don't want to screw up my nice new slack14 install on the pi, but I would like to get the rtc modules going in the kernel. In my earlier attempts, the kernel complained about version numbers, (and i think that until the 3.2.x kernel, the kernel did not have the basic rtc kernel stuff at all)

I have an mcp79410 rtc attached to the i2c bus, which according to my information, should work just fine with the ds1307 rtc kernel module - when I can compile it :-)
i have tried Register the (mcp79410) DS1307 RTC chip with the I2C address of 0x6F:
(obtained from i2cdetect 0 and from the mcp79410 data sheet)

echo ds1307 0x6F > /sys/class/i2c-adapter/i2c-0/new_device
(See http://www.element14.com/community/g...rry-pi-via-i2c )
but the 3.1.9 kernel knows nothing about this method of adding devices and complains
i'm using the i2c-tools slackbuild (thanks ponce)

If you need the RTC module your best bet is to recompile the kernel yourself. Use one of the branches from the Raspberry Pi git repository (https://github.com/raspberrypi). I've been running 3.2.27 since early September and it has been very stable and reliable. They've added a branch for the 3.6 kernel, but I haven't tried it yet.

Building the kernel is quite easy - particularly if you use David Spencer's great SlackBuild scripts. He has the scripts and instructions on his site (mentioned above) along with the older compiled kernel and supporting packages. You'll want to build the firmware to match the kernel version.

Before running the SlackBuild scripts, copy David's kernel configuration file (config-raspi) into the kernel source directory as .config, and run "make menuconfig" to generate compatible a version of the config file. Within menuconfig you can also configure what drivers should be compiled into the kernel or compiled as modules. The RTC drivers are in the "Device Drivers" category under "Real Time Clock". You may also need to adjust the configuration to compile modules for SPI or I2C support, depending on what RTC you are using.

Once you have the configuration file, the slackbuild scripts should do the rest and you can upgrade to the new kernel and firmware using upgradepkg.

The best tip I can give you is to back up the SD card with the Pi's OS before trying anything like a kernel upgrade. When everything goes wrong, it is easy to just pull the card, plug it into a desktop or laptop, copy back all the working files, and start over. With the Pi and similar device, I'll usually make a duplicate of the SD card and keep the original as the backup until I know that everything is working properly.

thanks, i'll try that. I may look at the boot image as well, and extract the kernel packages to check them out. If dave doesn't get round to updating his installer image I would like to create my own. that way i'll be able to start from scratch (but with an updated kernel) if necessary.

Here I have updated to the kernel-3.6.y branch of raspberrypi's linux sources, forking dave's slackbuilds

https://github.com/Ponce/raspi-slackbuild
http://ponce.cc/slackware/slackwarearm-14.0/

the raspi-extras folder contains prebuilt packages of kernel, firmware and stuff and a new installer image (untested yet) that uses kernel 3.6.1 (I added ck and bfq patches to my kernel build), but I'm preparing new version of this thingies at the moment, the will be ready soon.

if you want to customize it, you can clone the repository, download the kernel using the scripts included, copying inside the untarred folder the included config as .config, modify it with make menuconfig and then save it in place of the old, so that when you run the build script for all the stuff it will use your new config.

The installer hangs on boot for me. 3 flashes of LED activity and that's about it.

thanks ponce. I got those downloaded, and got the kernel and kernel source installed. I've built a kernel with rtc support, and built the ds1307 module. (it takes half a day or so)
(the ds1307 has an alias for the mcp79410 rtc which I have)
i can install the module with and it shows as rtc_ds1307 in lsmod
however I can't work out how to pass the i2c address to the module so that it works. the port is 6f
as shown by i have tried the method as per http://www.element14.com/community/g...rry-pi-via-i2c
ie but all I get is "no such directory" as i have a /sys/class/i2c-dev directory, but not a /sys/class/i2c-adapter directory. I don't know whether that is a difference between debian and slackware, or if there are some kernel options that I need to select to get these virtual configuration directories. do you have any ideas?

well, a happy update. I found that once the module is loaded (modprobe i2c:mcp7941x ) then it can be configured with
now I have a /dev/rtc0 and and all work as expected (tested after a cold reboot after 5 minutes off, with the ntp entry commented out in /etc/rc.d/rc.local

for those wanting more details with a "howto" at the end, see http://www.element14.com/community/message/63602#63602

I've built a new one, if you want to try it

http://ponce.cc/slackware/slackwarea...extras-3.2.27/

@timsoft: the 3.2.27 kernel that you'll find in the folder above should have the module for your rtc device already built (if you want to test it)