The Raspberry Pi 3 Model B Q&A thread

[jdb]

Does the WiFi chipset support channel 13 (in regions where it is allowed)? I can't find any clear info on this.

The Linux CRDA framework controls whether you can tune to channels >11. Set this via iw (e.g. iw reg set US).

[Dutch_Master]

Crazy idea perhaps, but...

I'm aware the Foundation has no 64 bit support/OS lined up and that'll not change for a while, as indicated by Eben. I'd like to try my hand at compiling something, here's my line of thought: booting the RPi3 from a 32 bit image, then use distcc and friends to build 64 bit packages on an external x86_64 system (Funtoo in my case). Create bootable image for SD-card, swap SD cards, boot into a 64 bit environment, re-do builds in native environment. Would that work, not having any experience with distcc nor image-making? Or should I just wait for a 64 bit image from either the Foundation or Funtoo?

If it's a viable path, I'd have to order that RPi3 kit PDQ! (otherwise I'd wait for the initial surge to subside, cutting down on delivery times )

I don't mind (it) getting shot down, but be gentle please

[jamesh]

Crazy idea perhaps, but...

I'm aware the Foundation has no 64 bit support/OS lined up and that'll not change for a while, as indicated by Eben. I'd like to try my hand at compiling something, here's my line of thought: booting the RPi3 from a 32 bit image, then use distcc and friends to build 64 bit packages on an external x86_64 system (Funtoo in my case). Create bootable image for SD-card, swap SD cards, boot into a 64 bit environment, re-do builds in native environment. Would that work, not having any experience with distcc nor image-making? Or should I just wait for a 64 bit image from either the Foundation or Funtoo?

If it's a viable path, I'd have to order that RPi3 kit PDQ! (otherwise I'd wait for the initial surge to subside, cutting down on delivery times )

I don't mind (it) getting shot down, but be gentle please

There is a config.txt option to boot the cores in 64 mode, so if you have a 64 bit kernel it might work. It's all the other stuff you need in 64 bit that might be a problem. Pi Cross compiler is available on github.

Orders are being fulfilled pretty quickly - a lot were made up front.

[geev03]

I have some questions about the Raspberry Pi 3:


6. How is YouTube performance?

Thanks for the help.
Kratos

Youtube performance is better than in rpi2 , https://goo.gl/yK5uBt

[GTR2Fan]

Youtube performance is better than in rpi2 , https://goo.gl/yK5uBt

Just for reference, I've launched the same video via Youtube in Epiphany Browser on a Pi2B and it plays back silky smooth here. Not that I'm trying to put you off buying a Pi3B if you want one.

[Dutch_Master]

Many thanks James. Funtoo uses a Debian based kernel (debian-sources-3.19 IIRC) but sadly only 32 bit ARM support for the RPi. The Subarches page for ARM lists several options for the RPi, but I assume I'd need the armv7a image for the A8 core the RPi3 has?

[Fidelius]

When I insert a µ-SD-card into my new Pi3's SD-card slot, it doesn't "click" like it does on the Pi2 when it (the SD-card) snaps-in.

Also I can't snap-out the µ-SD-card from the Pi3 like it does on the Pi2 by pressing it (the SD-card) a little bit more, but I have to pull it out from the Pi3's slot.

Whilst this works, I liked the Pi2 slot with its click for snapping-in and -out better, and I wonder if this is a "feature" of the Pi3 or some problem with my Pi3 ?
Thanks.

Aside it, the Pi3 is an amazingly fast machine and it nicely runs the Pi2's SD-card with its OS installation.

[noggin]

When I insert a µ-SD-card into my new Pi3's SD-card slot, it doesn't "click" like it does on the Pi2 when it (the SD-card) snaps-in.

Also I can't snap-out the µ-SD-card from the Pi3 like it does on the Pi2 by pressing it (the SD-card) a little bit more, but I have to pull it out from the Pi3's slot.

Whilst this works, I liked the Pi2 slot with its click for snapping-in and -out better, and I wonder if this is a "feature" of the Pi3 or some problem with my Pi3 ?
Thanks.

Aside it, the Pi3 is an amazingly fast machine and it nicely runs the Pi2's SD-card with its OS installation.

This was a conscious design change apparently, so it's not a fault on your Pi 3.

The guys at Pimoroni reported that the most common failure on uSD Pis with springy slots was the springy slot failing. Also a lot of people found the uSD card flying out when they were holding the board to change connectors really annoying. They've redesigned the Pibow to provide a larger slot around the uSD card to get your fingers in to remove it.

Looks like from the Pi Zero onwards we're getting non-springy uSD slots.

Not a huge problem for me. I used to get quite annoyed as uSD cards flew across the room if I didn't remove them properly... (They always ended up under the sofa...)

[Fidelius]

Dear Noggin, thank you for this information. I too can live with it, but just wondered.

[PeterO]

Is there any reason why /dev/input would not be properly populated when booting with / mounted from a USB hard disk ?

I've used the same process I've used before to create a root filesystem on a USB harddisk so that the SD card is only only used for the boot partition.

If I mount / from the SD card evey thing works fine.
If I mount / from the USB disk X comes up but the keyboard and mouse don't work. I found a hint in /var/log/Xorg.0.log that lead me to look in /dev/input

When it works:

Code: Select all

$ cat workingDevInput 
pi@raspberrypi:/dev/input $ ls -lR
.:
total 0
drwxr-xr-x 2 root root     120 Mar  1 16:07 by-id
drwxr-xr-x 2 root root     120 Mar  1 16:07 by-path
crw-rw---- 1 root input 13, 64 Mar  1 16:07 event0
crw-rw---- 1 root input 13, 65 Mar  1 16:07 event1
crw-rw---- 1 root input 13, 66 Mar  1 16:07 event2
crw-rw---- 1 root input 13, 63 Mar  1 16:07 mice
crw-rw---- 1 root input 13, 32 Mar  1 16:07 mouse0

./by-id:
total 0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-Logitech_USB_Trackball-event-mouse -> ../event2
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-Logitech_USB_Trackball-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-_USB_Keyboard-event-if01 -> ../event1
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-_USB_Keyboard-event-kbd -> ../event0

./by-path:
total 0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.2:1.0-event-kbd -> ../event0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.2:1.1-event -> ../event1
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.4:1.0-event-mouse -> ../event2
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.4:1.0-mouse -> ../mouse0
pi@raspberrypi:/dev/input $ ls -lR
.:
total 0
drwxr-xr-x 2 root root     120 Mar  1 16:07 by-id
drwxr-xr-x 2 root root     120 Mar  1 16:07 by-path
crw-rw---- 1 root input 13, 64 Mar  1 16:07 event0
crw-rw---- 1 root input 13, 65 Mar  1 16:07 event1
crw-rw---- 1 root input 13, 66 Mar  1 16:07 event2
crw-rw---- 1 root input 13, 63 Mar  1 16:07 mice
crw-rw---- 1 root input 13, 32 Mar  1 16:07 mouse0

./by-id:
total 0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-Logitech_USB_Trackball-event-mouse -> ../event2
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-Logitech_USB_Trackball-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-_USB_Keyboard-event-if01 -> ../event1
lrwxrwxrwx 1 root root 9 Mar  1 16:07 usb-_USB_Keyboard-event-kbd -> ../event0

./by-path:
total 0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.2:1.0-event-kbd -> ../event0
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.2:1.1-event -> ../event1
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.4:1.0-event-mouse -> ../event2
lrwxrwxrwx 1 root root 9 Mar  1 16:07 platform-3f980000.usb-usb-0:1.4:1.0-mouse -> ../mouse0

When it doesn't work

Code: Select all

pi@raspberrypi:dev/input $ ls -lR
.:
total 0
drwxr-xr-x 2 root root      60 Mar  1 16:10 by-id
drwxr-xr-x 2 root root      60 Mar  1 16:10 by-path
crw-rw---- 1 root input 13, 63 Mar  1 16:10 mice
crw-rw---- 1 root input 13, 32 Mar  1 16:10 mouse0

./by-id:
total 0
lrwxrwxrwx 1 root root 9 Mar  1 16:10 usb-Logitech_USB_Trackball-mouse -> ../mouse0

./by-path:
total 0
lrwxrwxrwx 1 root root 9 Mar  1 16:10 platform-3f980000.usb-usb-0:1.4:1.0-mouse -> ../mouse0

It's not a PSU problem, in both cases all the partitions on the USB disk are accessible. No low voltage warnings are seen and the PSU is rated at 2.5A.

PeterO

[lb]

Does the WiFi chipset support channel 13 (in regions where it is allowed)? I can't find any clear info on this.

The Linux CRDA framework controls whether you can tune to channels >11. Set this via iw (e.g. iw reg set US).

Sure, but some hardware isn't physically capable of operating at channels > 11. I assume you want to imply the Broadcom WiFi chipset can do it?

[lb]

As described in viewtopic.php?f=29&t=138120 Bluetooth uses the PL011 UART by default, so only the Mini UART is free for use. However, it unfortunately has various restrictions.

Does Bluetooth need to use the PL011 UART for some special reason, or can we switch it to the Mini UART?

[tvjon]

Gert's VGA666

has ceased to function.

I checked the overlays & thankfully it is present.

Any ideas please?

In the meantime I'll see if I can find a definitive list of used by RPi3 GPIO's.

[Kiefer]

Does the onboard wifi have an activity Led?

Cheers, Harry

Anyone?

[PeterO]

Is there any reason why /dev/input would not be properly populated when booting with / mounted from a USB hard disk ?

I've used the same process I've used before to create a root filesystem on a USB harddisk so that the SD card is only only used for the boot partition.

If I mount / from the SD card evey thing works fine.
If I mount / from the USB disk X comes up but the keyboard and mouse don't work. I found a hint in /var/log/Xorg.0.log that lead me to look in /dev/input

PeterO

There is something odd going on here. I tried recreating the root filesystem on the USB drive, but rather than take it directly from the ".img" file I took it from the partition on the SD card that had already been mounted successfully.
Now it seems to be working. I'll try and work out what had changed .

PeterO

[jamesh]

Does the onboard wifi have an activity Led?

Cheers, Harry

Anyone?

I think I saw a green LED flickering whilst I was trying out the Wifi. Not sure if it is specifically a wireless indicator.

[dom]

Does the onboard wifi have an activity Led?

Cheers, Harry

Anyone?

No.

[fourdee4d]

Awesome. Just noticed the core_freq has been upped from 250mhz to 400mhz:

http://dietpi.com/downloads/misc/core_freq.png

[tdenson]

My understanding from reading this thread is that I should be able to take the Raspbian SD card from a Pi 2 and plug it into a Pi3. However, just tried it and all I get is the rainbow screen.

[mikronauts]

put it back into the RPi2, then:

sudo apt-get update
sudo apt-get upgrade

If that does not work on an RPi3, try:

sudo apt-get dist-upgrade

My understanding from reading this thread is that I should be able to take the Raspbian SD card from a Pi 2 and plug it into a Pi3. However, just tried it and all I get is the rainbow screen.

[fruitoftheloom]

My understanding from reading this thread is that I should be able to take the Raspbian SD card from a Pi 2 and plug it into a Pi3. However, just tried it and all I get is the rainbow screen.

Raspbian Jessie compatible with an update / upgrade as above..

Raspbian Wheezy not compatible...

[tdenson]

My understanding from reading this thread is that I should be able to take the Raspbian SD card from a Pi 2 and plug it into a Pi3. However, just tried it and all I get is the rainbow screen.

Raspbian Jessie compatible with an update / upgrade as above..

Raspbian Wheezy not compatible...

Dumb question, but how do I tell which of the above I am running ?

[rpdom]

My understanding from reading this thread is that I should be able to take the Raspbian SD card from a Pi 2 and plug it into a Pi3. However, just tried it and all I get is the rainbow screen.

Raspbian Jessie compatible with an update / upgrade as above..

Raspbian Wheezy not compatible...

Dumb question, but how do I tell which of the above I am running ?

Like this

Code: Select all

pi@raspi3 ~ $ cat /etc/os-release 
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

[tvjon]

...
Raspbian Jessie compatible with an update / upgrade as above..

Raspbian Wheezy not compatible...

Actually, it's sort of compatible

I'm trying to work out why my vga666 display is a no-show on this RPi3 Jessie.
So, I've booted from my most recent (updated) "bouncing-menu" wheezy µSD card.


pi@p3 ~ $ cat /etc/os-release

PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)"
NAME="Raspbian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=raspbian
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@p3 ~ $

[toadstool]

Hoping someone can help me!?

I've apt-get up(date/grade)d my Raspbian Jessie install on a Raspi 2 then inserted this card in a Raspi 3 and booted only to find the Raspi 3 still thinks it is a Raspi 2.

I'm wondering if the .dtb file isn't being picked up by the kernel perhaps... though I'm clutching at straws here.

Also, I'm suffering appalling wifi performance (perhaps due to Pi thinking it is a v2?). SSH'ing to the new Pi is extremely sluggish with up to 2-10 seconds latency in response to input.

Can anyone shed any light on this please?

vcgencmd version after apt-get upgrade:

Code: Select all

Feb 29 2016 14:23:50 
Copyright (c) 2012 Broadcom
version dea971b793dd6cf89133ede5a8362eb77e4f4ade (clean) (release)

output of vcgencmd measure_clock:

Code: Select all

for src in arm core h264 isp v3d uart pwm emmc pixel vec hdmi dpi; do echo -e "$src:\t$(vcgencmd measure_clock $src)" ;done
arm:	frequency(45)=600000000
core:	frequency(1)=249999000
h264:	frequency(28)=250000000
isp:	frequency(42)=250000000
v3d:	frequency(43)=250000000
uart:	frequency(22)=48000000
pwm:	frequency(25)=0
emmc:	frequency(47)=250000000
pixel:	frequency(29)=148500000
vec:	frequency(10)=0
hdmi:	frequency(9)=163683000
dpi:	frequency(4)=0

content of /boot/config.txt:

Code: Select all

disable_overscan=0
gpu_mem=128
lcd_rotate=2
start_x=0
dtparam=i2c_arm=off
dtparam=spi=off

# Enable audio (added by raspberrypi-sys-mods)
dtparam=audio=on

output of cat /proc/cpuinfo shows the CPU is ARMv7 rather than ARMv8:

Code: Select all

processor	: 0
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 1
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 2
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 3
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

Hardware	: BCM2709
Revision	: a02082
Serial		: 00000000########

I'm guessing that /proc/cpuinfo may be inaccurate due to the 32 bit build of Raspbian? However, the clock frequencies don't measure up do they?