News

All news

Updated Debian, Arch Linux ARM images

Liam has just uploaded new versions of the Debian and Arch Linux ARM distributions to our mirror system. Head on over to the downloads page. The Debian image contains the following updates to the prior 13-04-2012 release:

Dom’s overscan adjustments
Dom’s ALSA driver
re-enable 1600×1200 output (regression in 13-04-2012 release)
boot file tidyup – and remove test cmdline file
vcgencmd provides a version number
fixes for EDID parsing
drive DMT modes in DVI modes by default, even if HDMI is reported as supported
some initial packages that might make setting up Wi-Fi possible
includes the non-free software source (nothing from it though) – useful for Wi-Fi firmware
the latest snapshot of the Qt5 code
a small package that will allow Raspberry Pi to be used as for Qt5 development out of the box
Raspberry Pi wallpaper on white background
LXDE theme for user “pi” is now “mist” (performance improvement)
a new Python IDE “spe” and related tools
- winpdb – python debugger
- wxglade – python dialogue designer
python-pygame
the “scratch” educational programming tool and required squeak-vm
lxtask – runs a task manager when CTRL-ALT-DEL pressed in LXDE
release identification in /etc/issue-rpi and /boot/issue.txt
ssh disabled by default – boot commands taken from /boot/boot.rc if present – candidate to enable ssh included
timezone set to Europe/London
tidied hidden files
package cache is clean

The alpha-quality ALSA driver included in this release is disabled by default. Type

modprobe snd_bcm2835

to enable it.

117 comments

Sounds great, Got utorrent back up so i can try it out soon.

Thanks for the update. Will there also be a GUI-less distro in the near future? And does a headless server have more RAM available due to the disabled GPU?

On my debian image the first thing I did was “apt-get remove lxde && apt-get autoremove” to get rid of X and all that. This left me with a fairly basic install.

I just configure my Linux boxes to not run X by default on boot.

You’ll want to cp /boot/arm224_start.elf to /boot/start.elf so you have 224MB of RAM available to the ARM.

The more superior linux distro available on RPi *is* ‘GUI-less’ in base intall….Arch

Well, you can get a very basic Debian installation if you want by downloading a minimal image of less than 50mb. I just installed Arch on my Pi because the Debian image was giving errors and wouldn’t read my new Sandisk SD card. Arch didn’t have this problem.

I did a quick search on it last night and apparently I would have to patch the image. I just wanted to get it to boot for a quick look. Arch is pretty nice…yet another package manager to learn but that’s not a huge deal. Good job to everyone involved. I have two units and look forward to having lots of fun nights seeing what I can do with them.

Nice :)

Keep up the good work guys!!

Awesome update.
Question for a linux beginner, how do I change the keyboard layout? (from GB to US)

Nevermind — got it with some searching. Was using the wrong dpkg command.

You know, YOU are “THAT GUY”!

“How does XYZ work?” – “nvm figured it out”

If you’re going to come back to the thread just to withdraw your question, why don’t you just post how you solved it?

As far as I remember, it’s something like dpkg-reconfigure console-data, but I’m not sure.

In case any other Yanks were having issues like me:

apt-get install console-common
install-keymap us

also very nice RD avatar

It might be a good idea to start thinking about an upgrade path for the future releases. Folks probably have some stuff set up on their systems and it would be convenient not to have to start from scratch with every new image.

I agree – maybe using a separate /home partition and/or unionfs (like Knoppix’s persistent storage) or something?

Use the package manager for updates.. There’s no need to download and install every new image.

For everyone who doesn’t know how to do that, here is how:

sudo apt-get -y update;sudo apt-get -y upgrade

You can also do it with Synaptic if you prefer a graphical package manager.
Install Syaptic with
sudo apt-get -y install synapic

hit alt+F2 in the LXDE desktop and run:
gksudo synaptic
(assumes that gksudo had been installed)

I’m pretty sure the Raspberry Pi updates aren’t in Debian’s official repository.

Could it be possible for users to help contribute to the various distributions? I’ve suggested bug tracking in the forums and twitter (which have been answered), but is there any way that I can help “Dom” out more directly? This could be a *great* opportunity for anybody who’s been interested in contributing to a Linux distribution but could never get over that first hurdle of “I found a bug, I fixed it, now what?”

Yeah, I’m interested to find out more about that as well. For example, the Debian image does not include staging drivers, one of which I need (wifi r8712u). I had to compile kernel from rpi’s github and build all the modules. I’m considering creating my own image for others to use, but it would be preferable to have official Debian image just include staging.

Well, if you apply to the Broadcom Cambridge position of low level embedded software engineer you may even get to work with him…

Of course you’ll have to work for me!

Gordon

Great news. Where do I apply?

There is a new release out now – I asked for staging drivers to be included, but I do not know if they are. I have a feeling not.

If you’re on the Broadcom network, check out Gray’s list of features for the next version. I think staging drivers are on there.

“low level embedded software engineer”… that would be my dream job :)

i’ll cross my fingers for staging drivers.

thanks,
drew

Yes, we definitely need this. I’m working on opening things up this weekend.

What was the reason behind disabling ssh by default?

Security.

All you need to do is rename boot_enable_ssh.rc to boot.rc on your boot partition if you want sshd starting.

the removal of sshd at boot is really kind of annoying as i have no hdmi input enabled devices and no tv in this room so i have to be able to ssh in to do any configuration such as turning on sshd at boot but of course i can’t because no sshd at boot…. :)

Isn’t this one of those no win things? If it’s there that’s a security hole. If it isn’t people can’t connect until they have enabled it in some other way.

Can’t you just rename the file on the SDcard using a card-reader on your desktop linux box, before plugging it into the Pi?
Assuming you have a desktop linux box (or a LiveCD) …

Replied before reading the rest of the comments – sorry!

Thanks for the release and the ChangeLog much appreciated.

I wish sshd or dropbear would be enabled by default though.

Sorry, it seems it could be enabled with /boot/boot.rc
So no problemo.

big problemo as if you are doing it manually on another system.

removing sshd at boot in the image you start with is not a good idea. as it locks out a percentage of the users and is not “fixable” by the user in some situations. It is always easier to turn things off if you have them than to turn them on if you don’t

found the file in the fat partition, renamed it and it took several reboots and a bit of a wait for it to work. might be better to say the file is in the fat partition if you are writing the image on a windows machine and in /boot if you are workign on a linux machine

Hmm. I think there was some concern about evil black-hat types creating the Raspberry Pi botnet if we have sshd by default and a known passwords. That said, there aren’t going to be many of these devices on the public Internet, so perhaps we should rethink.

Maybe the problem is more we didn’t provide clear instructions on enabling sshd. It literally requires renaming a single file on FAT partition, so it’s not exactly hard to opt-in if you know how.

In fact Eben, perhaps you could update the post to note that sshd is disabled by default, but you can trivially enable it by renaming boot_enable_ssh.rc to boot.rc on the boot partition after writing your SD card.

Scratch that, it is in the changelog. Could be made a little more prominent I suppose

My two problems with the way sshd was turned off by default were 1) that it wasn’t quite clear where the file was. /boot/boot.rc would seem to indicate on the linux side but if you are doing all this manually on another linux system then /boot is empty. Did work it out in the end but putting a note in the docs will fix that. 2) There is a “correct” way to disable sshd using a file in /etc/ssh which is what you’ll find if google/bing to find the answer which then gets confusing when it doesn’t exist when you try to remove it — but all sorted now and i have bits and bobs coming which will solve my lack of hdmi/composite displays so all is good now but i bet your ears were burning last night as you were called every name under the sun :)

How’s this for a possible fix?
The GUI tool that initially images Debian onto the SD card should:
1) Have a checkbox to enable SSH server (which is unchecked by default)
2) Insist that a password be set, as soon as the checkbox is checked. Then the password will be unique!
3) These settings should be entered into image, just before or immediately after the imaging to the SD card occurs.

The result:
1) Botnet averted!
2) A “headless” Raspberry Pi would become easy!
3) The most expensive part of a RPi setup, namely a DVI or HDMI monitor, is now unneeded for those who only want a headless RPi.
Note: This would probably necessitate making a special Live CD (with some kind of minimal linux on it) which has the required mojo to loopback-mount and properly modify the Debian image before it’s imaged to the SD card. I say this because it would probably be too difficult or impractical to implement the necessary loopback-mounting from a Windows-based imaging tool.

Yaba daba do
Thanks guys. I am a happy penguin.

Here is the New Squeeze, after Puppification
http://raspberrypy.tumblr.com/post/21483516950/lobster-here-one-week-of-raspberry-pi

The link fails :(

Successful link now available
http://bit.ly/HUZzLN

Typical! If these were uploaded a little earlier… oh well :)

Great work Liam & the team!

Literally just put the old image on my SD card. Wake up this morning and I’m doing this one now!

Still unclear on how this works exactly but if I upgrade Arch with pacman -Syu will this basically give me the latest changes without the need to start over from this new image?
(Same question re: Debian too.)

Unfortunately we’re not currently packaging the kernel and Broadcom libs as .deb packages with an apt source, so no.

Sorry – does that mean no to just Debian or Arch too?

ASB is just working on Debian.

I realised that *after* I posted it. Oops. Still, if anyone can cover it – is Arch updating via pacman -Syu or do we need to keep going with the new .img file too?

Well, Arch is completely defined by its current version of its packages, so I assume so.

“includes the non-free software source”

There goes your congratulatory e-mail from rms. ;)

I vote for the re-enabling of sshd. I think the reason given for disabling it will not in fact cause a problem in practise.

I agree that an upgrade path is needed. It is a pain to start from scratch each time a new distro appears to add your own features.

can the new *start.elf files be put on github please ?

md5sum of arm192_start.elf on github is currently 67cc4275f5f3ad287d47382ba73cf7fe

while in this new debian image it’s 17e0993a8ed5be368a2ff84e314c97f0

the wrong ones seem to be in the new Arch image as well, I get a 1280×1024 screen there..

As a side question, are the firmware images versioned in any way ? If so, how do we read that version ? md5sum-ing all the files to find out what you have is cumbersome at best.

Also, it would have been hugely useful to have had documented in the changelog how to disable overscan instead of making us all search the forums for a piece of hidden information.
Having the firmware send bcm2708_fb.fbwidth=1504 & bcm2708_fb.fbheight=1104 to a 1600×1200 monitor looks very strange. Do TV’s even exist with a 1600×1200 screen ?

Intersstingly, for me, 1600×1200 worked fine on the 13-04-2012 debian release. This version ‘broke’ it :)

There is a “compile time” timestamp in the start.elf file. I don’t know how to get at it in a proper way.
strings /boot/start.elf | grep -A2 ‘Apr ‘
gives Apr 18, 14:59 for the current image, and Apr 18, 18:16 for the previous one.

It’s definitely not the “official” way to extract this information, but I’ve knocked up a quick python script to extract the build date, time and version from a start.elf file
http://www.andrewscheller.co.uk/read_startelf_version.py

It works for all the versions of start.elf posted on github so far.

Is there a reason the zip file is less than half the size from the previous release? Or was the compression on the previous one just a bit fast-done? My internet appreciates this decrease in size!

is there a way to setup a 1080i 50Hz mode on the video out ?

By default the Rasberry Pi asks the monitor what mode it prefers. That should work in almost all cases. So what is it doing that you need to ask this question?

I got the debian squeeze image this morning from the torrent link.

On qemu, the included start file appears to be working under qemu – I see boot up messages in the vnc client window. But the password given on the download page doesn’t work for me. I just get the “incorrect login” message every time I try to login.
What could I be doing wrong?

Use all lowercase. it’s pi & raspberry .

I’d redefined my capslock as a compose key, so I know capslock can’t be accidentally on. Plus Username comes out in lowercase when I type it. I can’t see the password as I type, but opening any other window and typing in that, I manage to type raspberry correctly more often than not, and I’ve had a dozen failed attempts at logging in. It’s got

try typing it slower, i’ve seen this issue too, think there are little moments where my kb seems to be ignored.

Can anyone show me a screenshot etc. of the wallpaper packaged with it? I’m specific about these things :P

While I fully agree that sshd should be disabled by default, I’ve just upgraded and I don’t have a screen here and want to login over ethernet.

Now the /etc/init.d/ssh script will not start sshd if /etc/ssh/sshd_not_to_be_run exists. But it doesn’t. So.. how do I tell sshd to “just start”?

Thanks ASB for your solution: move the enable ssh script in /boot to boot.rc

Any chance of using 7zip? It would be a *lot* smaller (see http://gyazo.com/e4d105529df3a886b8c46ddaaea1c619 if you don’t believe me – they’re self-extractors but I’d suggest the foundation just used *.7z)

7zip , IIRC, isn’t installed on most Linux distros or windows boxes by default, which makes it difficult for many people. And its not guaranteed the files will be smaller although it is likely.

It may not be installed, but it should be. It’s free, LGPL, and better than it’s competition. Seriously better.
But if going to the 7-zip web site, downloading the installer and running it is ‘difficult for many people’ then how do you expect them to cope with downloading the debian image and dd-ing it to an sd card ?
Give people some credit, not all us are lost causes :)

As for not guaranteed to be smaller, unless you’re trying really hard to find a pathological corner case then 7z will easily beat plain old zip, especially on a filesystem image such as this.

Just to illustrate,
debian6-19-04-2012.zip 444MB
debian6-19-04-2012.7z 279MB

Saving 165MB or just over 37%

Whether it should be on as standard or not is pretty irrelevant, zip IS installed as standard on Linux and Windows. That means even beginners have the easiest possible path to getting their Pi going. Not everyone is an expert – stop assuming that just because you find something easy, everyone else does, and almost no-one is a lost cause. Don’t forget, lots of people will never even have heard of 7z.

JFYI, I use 7z on windows, in case you think I have something against it. Although the GUI is a bit crap.

I use it too – but I’m not advocating we use it as standard for *exactly* the reasons James outlines.

I agree that zip ought to be the default/standard compression format, but would it complicate things too much to *also* add 7z files for those who are comfortable with it? Maybe even if was on an ‘advanced’ download page, so as to not clutter up the normal download page?

Surely you could say, just like people do with PDFs, that the files are compressed with 7zip to make them smaller, and point people to http://www.7-zip.org/download.html (windows at the top, osx and linux ports further down). Please at least add 7z as an option – my internet connection (200k at best) is screaming for it!

Lots of people out there want to try something non-standard, new and interesting called Raspberry Pi.
You’d like them to download and install Win32DiskImager – something they’re even less likely to have heard of, but 7-zip is too much ?

I’m not assuming anyone is an expert, but maybe I’m assuming too much by thinking that if they’re here and are open to trying something new like the Pi, then they might also be willing to learn a few other things along the way.

I guess I’m just having some difficulty reconciling the aims of getting more people into CS, learning programming, etc. with a position that seems to suggest they won’t be willing to learn about 7-zip.

Sorry, got a headache. Really cannot think of anything else to say. Ok, we should use 7z. Sorry, we don’t.

Finding this new Arch image extremely unstable. Installing base-devel will throw up virtual memory errors, and I’ve now had LXDE just freeze up several times on trying to start anything resulting in the entire system img needing rewritten and starting all over again. Anyone else?

virtual memory errors- could this be related to the memory you have allocated to CPU vs. GPU? (just a blind guess, I don’t even have a Pi)

No idea. It worked on the last image, and is set as whatever the default is on the new one when freshly written to sd card.

Seems the default split has changed to 128/128
http://www.raspberrypi.org/forum/distributions/archlinuxarm-on-raspberry-pi/page-6/#p67638

Just tried it with the 192 and even the 224 Elf, same results when it gets to installing gnutls. “Unable to handle kernel paging request at virtual address 90804063”

(It even does it during installing LXDE and related files now.)

I too have gotten kernel panic with this build. I was trying to scp a file to the Pi when it stalled and… Unable to handle kernel paging request at virtual address 973b35dc

Had you sha1 checksum-ed you image after having unzipped the zip file?

If some software is using too much memory you should begin to the see the kernel’s kill feature in action:

What the kill feature is doing is that it kills your program (remove it from RAM and the CPU by brute force), if it dare to use too much memory.

Look for “KILL” messages in in /var/log/dmesg and /var/log/syslog

The SHA-1 appears to match the one in the SHA-1 file in the zip perfectly – sidenote, the one listed on the Downloads page itself is wrong! – and I have still been unable to get anywhere with this new img. With every try either LXDE or base-devel will run into virtual memory errors or on the rare occasions LXDE installs, crash not long after getting into the desktop.

(Ignore – SHA1 for the zip, not the file inside.)

Thanks for the new build.
Is there a bugtracker for the images? I still have problems with the soundcard: The kernel module loads, aplay -l shows a valid card and I get some audio ouput on the speaker. But after some seconds, it crashes:
Apr 21 21:09:29 raspberrypi kernel: snd_bcm2835_playback_open:97 Alsa open (0)
Apr 21 21:09:44 raspberrypi kernel: vcos: [1480]: bcm2835_audio_write:778 bcm2835_audio_write: failed on vchi_bulk_queue_transmit (status=-1)
Apr 21 21:09:44 raspberrypi kernel: snd_bcm2835_playback_close:167 Alsa close

The ALSA driver is still early Alpha quality, so problems are to be expected. Stuff on forum about it.

Also check the firmware issue regarding the alsa driver at github https://github.com/raspberrypi/firmware/issues/2

The bit that please’s me most Default time “London England ”

Small things I suppose :-)

We actually had a great big discussion about whether or not to do that (and the upset emails from Americans who are used to US localisation that we predicted when we had that discussion *have* been coming in). I’m glad we went the way we did. :)

I love the fact that XBMC’s weather is set to Cambridge (it alternates between “Sun cracking the flags” and “Flaccidly fen-moist”)

Wow, really??? Those Americans that are complaining just need to chill. UTC is the *standard* time. What else would make sense for a worldwide product?

(I’m American, BTW. :-))

Actually, UTC is not the same as GMT(London’s time zone). While the two are generally loosely aligned, there can but up to a .9s deviataion, after which a leap second is applied to UTC to bring it back inline. The reason for this is that GMT is defined based on solar observations, while UTC is directly based on atomic observations, and corrections must be made. (why yes, I am the maintainer of my companies timeservers, why do you ask?)

Also worth noting, while during part of they year the time in London happens to be in GMT, they are presently observing BST (daylight savings time), which is UTC+1. This came up on one of the OpenIndiana channels recently, a rather confused gentelman in england was afraid he was late to their meeting when, infact, he was 45mins early.

If I had my druthers, I say just use LOCALE=C TZ=UTC (no daylight savings time)

Well, I wasn’t going to be as pedantic as all that, but I suppose I should’ve known that on a forum as nerdy as this one I would eventually be corrected. :-)

Can’t wait for my tiny board, my little, silicone wafer of goodness…

*twiddle thumbs*

Having some issues while running a USB2SERIAL converter, CDC class device. Got expEYES (http://expeyes.in) working well but the communication gives error when both keyboard and mouse are present with the device. Same stuff works fine on a PC.
It looks like the error is somewhere in the USB driver.
Using debian6-19-04-2012.img, the previous one also gave same error.
INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2

Ajith

The /var/log/messages says the following:
Apr 17 14:44:11 raspberrypi kernel: generic-usb 0003:413C:2107.0015: input: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-bcm2708_usb-1.3.2/input0
Apr 17 14:44:11 raspberrypi kernel: usb 1-1.3.3: new full speed USB device number 33 using dwc_otg
Apr 17 14:44:11 raspberrypi kernel: usb 1-1.3.3: New USB device found, idVendor=04d8, idProduct=00df
Apr 17 14:44:11 raspberrypi kernel: usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 17 14:44:11 raspberrypi kernel: usb 1-1.3.3: Product: MCP2200 USB Serial Port Emulator
Apr 17 14:44:11 raspberrypi kernel: usb 1-1.3.3: Manufacturer: Microchip Technology Inc.
Apr 17 14:44:11 raspberrypi kernel: usb 1-1.3.3: SerialNumber: 0000227788
Apr 17 14:44:11 raspberrypi kernel: cdc_acm 1-1.3.3:1.0: ttyACM0: USB ACM device
Apr 17 14:44:11 raspberrypi kernel: generic-usb 0003:04D8:00DF.0016: hiddev0: USB HID v1.11 Device [Microchip Technology Inc. MCP2200 USB Serial Port Emulator] on usb-bcm2708_usb-1.3.3/input2
Apr 17 14:44:12 raspberrypi kernel: usb 1-1.3.4: reset low speed USB device number 14 using dwc_otg
Apr 17 14:49:56 raspberrypi kernel: usb 1-1.3.4: USB disconnect, device number 14
Apr 17 14:50:24 raspberrypi kernel: usb 1-1.3.2: USB disconnect, device number 32
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.2: new low speed USB device number 34 using dwc_otg
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.2: New USB device found, idVendor=413c, idProduct=2107
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.2: Product: Dell USB Entry Keyboard
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.2: Manufacturer: Dell
Apr 17 14:50:25 raspberrypi kernel: input: Dell Dell USB Entry Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.2/1-1.3.2:1.0/input/input17
Apr 17 14:50:25 raspberrypi kernel: generic-usb 0003:413C:2107.0017: input: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-bcm2708_usb-1.3.2/input0
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.4: new low speed USB device number 35 using dwc_otg
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.4: New USB device found, idVendor=046d, idProduct=c05b
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.4: Product: USB Optical Mouse
Apr 17 14:50:25 raspberrypi kernel: usb 1-1.3.4: Manufacturer: Logitech
Apr 17 14:50:25 raspberrypi kernel: input: Logitech USB Optical Mouse as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/input/input18
Apr 17 14:50:25 raspberrypi kernel: generic-usb 0003:046D:C05B.0018: input: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-bcm2708_usb-1.3.4/input0
Apr 17 14:52:11 raspberrypi kernel: INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2
Apr 17 14:52:11 raspberrypi kernel:
Apr 17 14:52:11 raspberrypi kernel: INFO:: schedule_periodic: No host channel available for periodic transfer.
Apr 17 14:52:11 raspberrypi kernel:
Apr 17 14:52:11 raspberrypi kernel: ERROR::dwc_otg_hcd_urb_enqueue:487: DWC OTG HCD URB Enqueue failed adding QTD. Error status -4008
Apr 17 14:52:11 raspberrypi kernel:
Apr 17 14:52:11 raspberrypi kernel: INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2
Apr 17 14:52:11 raspberrypi kernel:
Apr 17 14:52:11 raspberrypi kernel: INFO:: schedule_periodic: No host channel available for periodic transfer.
Apr 17 14:52:11 raspberrypi kernel:
Apr 17 14:52:11 raspberrypi kernel: ERROR::dwc_otg_hcd_urb_enqueue:487: DWC OTG HCD URB Enqueue failed adding QTD. Error status -4008
Apr 17 14:52:11 raspberrypi kernel:
Apr 17 14:52:11 raspberrypi kernel: INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2
Apr 17 14:52:11 raspberrypi kernel:
Apr 17 14:52:11 raspberrypi kernel: INFO:: schedule_periodic: No host channel available for periodic transfer.

Ajith, can i ask you to use a pastebin the next time for all those log messages?

You can use http://pastebin.com/

Fill out the form, and click the submit button: The web page will now give you a link to your text.

Instead of a long text you can now paste the link in a blog post.

FYI, you should not ask for support here, but use the forum, because there is a better chance for being seen there.

Yes, please post in the troubleshooting section of the forum.

Sorry. I didn’t know. Posting it on the forum.

Liam = Hexxeh? If so: he’s a wizard!

Isn’t there any update-script for old images?

I think Debian and Arch do have something called apt-get and pacman….

Hi, I know that the hardware acceleration on the GPU is optimised for 1920 by 1080P – but is it possible to add other screen modes even if they perform more slowly?

I have a Dell Ultrasharp U3011 for its insane pixel count (2560×1600) and want to know if the Raspberry Pi can drive it for 2d desktop stuff only
Thanks!

Wonderful, but compressing it with 7z nearly halves the size of the download (double the effective bandwidth)

Please confirm if version of Debian is the latest stable version (6.0.4 Squeeze) as I need the Python version to be 2.6 or 2.7 in order to program my Labjack DAQ as the Labjack Python Module is not compatible with Python 3.0 +

Since the update I cant get the pi to output in my monitors native res of 1680×1050 :|

Could it be the same SHA-1 for both distros??

Debian “squeeze”
debian6-19-04-2012.zip
SHA-1 1852df83a11ee7083ca0e5f3fb41f93ecc59b1c8

Arch Linux ARM
archlinuxarm-19-04-2012.zip
SHA-1 1852df83a11ee7083ca0e5f3fb41f93ecc59b1c8

Can you please post the sources used to create this image? I’m not sure I can match everything in this image to the stuff posted at https://github.com/raspberrypi

Publishing the scripts to create the image would be a nice touch, too.

Thanks!

Hi, unable to get with the latest Arch, startx to work, (LXDE), using the latest Arch download. followed update after trying startx, below syntax.
pacman -Syu
pacman -S xf86-video-fbdev lxde xorg-xinit dbus

then
startx
rebooted, now System no longer boots.

Where am I going wrong.

Cheers
Bob

For the debian image, the pi and respberry login info does not work. why?

Comments are closed

News

Latest posts

This massive nose sniffs things then prints a description of the smell

Paragraphica creates "photos" based on your location

Dragonfly Spectral Line Mapper

Refurbished vending machine

Next Post

phpBB forum beta test

Previous Post

Model B schematics

Share this post

117 comments

FirstPlaceFranz

Smulders

William

nicknml

asb

Brakenjan

Bob

Liam

Nathan

Nathan

notthatguy

colin

William

gsh

Joe Black

JamesH

eben

asb

nicknml

JamesH

asb

ukscone

Chris Rowland

Andrew Scheller

Andrew Scheller

ukscone

ukscone

eben

asb

asb

asb

ukscone

Subharo

abc_harold

TopherBrink

asb

TopherBrink

TopherBrink

Ben Ward

M3n747

ian smith

selsinork

rew

Raphael Jacquot

rew

malcolm

rew

malcolm

alan

Jack

rew

rew

JamesH

selsinork

JamesH

Andrew Scheller

selsinork

JamesH

TopherBrink

TopherBrink

selsinork

TopherBrink

TopherBrink

u4ia

TopherBrink

TopherBrink

Steffen

JamesH