Linux kernel is now 4.4

Mon Apr 11, 2016 6:34 pm

The default firmware branch has been updated to use the 4.4 kernel.
The source tree has been available for a few months and is being used by OSMC and OpenELEC, as well as "BRANCH=next rpi-update".

Update with:

Code: Select all

sudo rpi-update

Ideally nothing much will change. The newer kernel tree does support more devices (e.g. USB devices like wifi and dvb) as well all supporting dynamic device tree.

Please report if there are any regressions compared to the 4.1 kernel. If testing is positive it will appear in "apt-get upgrade" and on new raspbian images in the near future.

The default source tree on https://github.com/raspberrypi/linux is now rpi-4.4.y. This tree is now considered the stable kernel source tree and will merge in minor bumps to the kernel version, rather than rebase.
There is now a 4.5 kernel tree where more experimental kernel commits may go (in general moving closer to upstream).

Notes:
Device tree is required for 4.4 kernel. Settings like "dtoverlay=" to disable device tree will cause failure to boot.
Device tree is now assumed if a kernel doesn't have a trailer. If you are using latest firmware with a different kernel that doesn't use device tree,
then use mkknlimg to indicate you aren't using device tree, or add "device_tree=" to config.txt to disable it.

MrEngman · Tue Apr 12, 2016 12:26 am

I have just upgraded the kernel on 4 Pi's, B+, 2 B, 3 B and Zero using rpi-update to kernel 4.4.6(-v7)+ #874 and am now seeing something odd on the B+ and 2 B. The B+ and 3 B have wired and wifi connected. The 2 B and Zero have only wifi connected. I am connected to all my Pi's via SSH from a W7 laptop.

Command ifconfig on the B+ and 2 B is showing a device sit0. I've had a search on the internet and it appears to be a IPv6 to IPv4 tunnel or something like that. I've also looked at trying to remove it but all suggestions reference editing files that do not appear to exist on the Pi's. There is a file /etc/modprobe.d/ipv6.conf containing

Code: Select all

# Don't load ipv6 by default
alias net-pf-10 off
alias ipv6 off

and suggestions I've found for stopping sit0 running say alias net-pf-10 off should stop it, although they reference a different file that is not on the Pi, but it obviouly has no effect on my Pi's.

I have disabled IPv6 on all Pi's by adding to following to the end of file /etc/sysctl.conf

Code: Select all

# IPv6 disabled
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.br0.disable_ipv6 = 1

Why is it suddenly showing up, as I have previously run older versions of 4.4.x and have not seen this before? How can I remove it if necessary?

Not sure if it's relevant but the two Pi's I am seeing this on, the B+ and 2 B, are using wheezy. The 3 B and Zero are using Jessie.

MrEngman

lbog · Tue Apr 12, 2016 7:37 am

MrEngman wrote: Why is it suddenly showing up, as I have previously run older versions of 4.4.x and have not seen this before?

Because in the kernel 4.4, those modules (ipv6, sit) are built-in:

Code: Select all

:~ $ sudo modprobe -rv ipv6
modprobe: FATAL: Module ipv6 is builtin.

Code: Select all

:~ $ sudo modprobe -rv sit 
modprobe: FATAL: Module sit is builtin.

Code: Select all

:~ $ modinfo ipv6
filename:       /lib/modules/4.1.21-v7+/kernel/net/ipv6/ipv6.ko
alias:          net-pf-10
license:        GPL
description:    IPv6 protocol stack for Linux
author:         Cast of dozens
srcversion:     1AD9E2E1FAFF22B833A8CBD
depends:        
intree:         Y
vermagic:       4.1.21-v7+ SMP mod_unload modversions ARMv7 
parm:           disable:Disable IPv6 module such that it is non-functional (int)
parm:           disable_ipv6:Disable IPv6 on all interfaces (int)
parm:           autoconf:Enable IPv6 address autoconfiguration on all interfaces (int)

Code: Select all

:~ $ modinfo sit 
filename:       /lib/modules/4.1.21-v7+/kernel/net/ipv6/sit.ko
alias:          netdev-sit0
alias:          rtnl-link-sit
license:        GPL
srcversion:     BFC2743FEC2FEFFDA219D8E
depends:        ip_tunnel,tunnel4,ipv6
intree:         Y
vermagic:       4.1.21-v7+ SMP mod_unload modversions ARMv7 
parm:           log_ecn_error:Log packets received with corrupted ECN (bool)

MrEngman · Tue Apr 12, 2016 10:49 am

OK, but in that case why does it show on only two of the Pi's I updated, the B+ and 2 B, and not on the 3 B and Zero?

MrEngman

atkjoin · Tue Apr 12, 2016 12:16 pm

Good Morning!

Alsamixer stops working after upgrading.

How to solve this problem?

lbog · Tue Apr 12, 2016 12:23 pm

MrEngman wrote:..., but in that case why does it show on only two of the Pi's I updated, the B+ and 2 B, and not on the 3 B and Zero?

Are your 4 PI's in the same LAN, or in different LAN's?

Tue Apr 12, 2016 12:46 pm

atkjoin wrote:Alsamixer stops working after upgrading.

Do you have "dtparam=audio=on" in your config.txt? The board support code in the 4.4 kernel is minimal, so we have to rely on Device Tree much more.

Massi · Tue Apr 12, 2016 12:59 pm

atkjoin wrote:Good Morning!

Alsamixer stops working after upgrading.

How to solve this problem?

maybe this?
viewtopic.php?f=29&t=130429#p895402

as PhilE says, you have to enable it with config.txt dtparam (read the following posts in the reported topic)

MrEngman · Tue Apr 12, 2016 1:17 pm

lbog wrote:
MrEngman wrote:..., but in that case why does it show on only two of the Pi's I updated, the B+ and 2 B, and not on the 3 B and Zero?
Are your 4 PI's in the same LAN, or in different LAN's?

They are all on the same network, 192.168.16.0/24, and all using dhcp.

Pi B+ ifconfig

Code: Select all

pi@Pi-B-plus /mnt/home/pi $ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:9e:f7:5a
          inet addr:192.168.16.52  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7611 errors:0 dropped:2 overruns:0 frame:0
          TX packets:2359 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6227068 (5.9 MiB)  TX bytes:243820 (238.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sit0      Link encap:IPv6-in-IPv4
          UP RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:e0:4c:18:c3:81
          inet addr:192.168.16.64  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3125 errors:0 dropped:1 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:653179 (637.8 KiB)  TX bytes:2100 (2.0 KiB)

Pi 2 B ifconfig

Code: Select all

pi@Pi-2B-a ~ $ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:29:06:64
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:1104 (1.0 KiB)  TX bytes:1104 (1.0 KiB)

sit0      Link encap:IPv6-in-IPv4
          UP RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 74:da:38:2a:d3:86
          inet addr:192.168.16.79  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:46920 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1571 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9077530 (8.6 MiB)  TX bytes:230706 (225.2 KiB)

Pi 3 B ifconfig

Code: Select all

pi@Pi-3B-b:~ $ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:1f:8e:6a
          inet addr:192.168.16.30  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:110 errors:0 dropped:11 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12955 (12.6 KiB)  TX bytes:12923 (12.6 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11472 (11.2 KiB)  TX bytes:11472 (11.2 KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:4a:db:3f
          inet addr:192.168.16.40  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:122 errors:0 dropped:109 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:51638 (50.4 KiB)  TX bytes:4079 (3.9 KiB)

Pi Zero ifconfig

Code: Select all

pi@Pi-0a:~ $ ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr e8:de:27:a1:e0:8d
          inet addr:192.168.16.63  Bcast:192.168.16.255  Mask:255.255.255.0
          inet6 addr: fe80::d2d3:27b:ba3d:6f45/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:48940 errors:0 dropped:20241 overruns:0 frame:0
          TX packets:1624 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7924946 (7.5 MiB)  TX bytes:225290 (220.0 KiB)

MrEngman

lbog · Tue Apr 12, 2016 1:37 pm

MrEngman wrote: They are all on the same network, 192.168.16.0/24, and all using dhcp.

Pi B+ ifconfig

OK. Maybe it's the ifconfig command. Try with

Code: Select all

ip a

, instead of ifconfig.

MrEngman · Tue Apr 12, 2016 1:58 pm

lbog wrote:
MrEngman wrote: They are all on the same network, 192.168.16.0/24, and all using dhcp.

Pi B+ ifconfig
OK. Maybe it's the ifconfig command. Try with
Code: Select all
ip a
, instead of ifconfig.

OK. One difference - sit0 shows in ip a for the Pi zero, but still no sign of it for the for the Pi 3 B.

EDIT: just checked version of ifconfig and it is the same on all 4 Pi's, net-tools 1.60, ifconfig 1.42 (2001-04-13)

Pi B +

Code: Select all

pi@Pi-B-plus /mnt/home/pi $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN qlen 1
    link/sit 0.0.0.0 brd 0.0.0.0
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether b8:27:eb:9e:f7:5a brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.52/24 brd 192.168.16.255 scope global eth0
       valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:e0:4c:18:c3:81 brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.64/24 brd 192.168.16.255 scope global wlan0
       valid_lft forever preferred_lft forever

Pi 2 B

Code: Select all

pi@Pi-2B-a ~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN qlen 1
    link/sit 0.0.0.0 brd 0.0.0.0
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether b8:27:eb:29:06:64 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 74:da:38:2a:d3:86 brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.79/24 brd 192.168.16.255 scope global wlan0
       valid_lft forever preferred_lft forever

Pi 3 B

Code: Select all

pi@Pi-3B-b:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:1f:8e:6a brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.30/24 brd 192.168.16.255 scope global eth0
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:4a:db:3f brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.40/24 brd 192.168.16.255 scope global wlan0
       valid_lft forever preferred_lft forever

Pi Zero

Code: Select all

pi@Pi-0a:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
    link/sit 0.0.0.0 brd 0.0.0.0
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether e8:de:27:a1:e0:8d brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.63/24 brd 192.168.16.255 scope global wlan0
       valid_lft forever preferred_lft forever
pi@Pi-0a:~ $

lbog · Tue Apr 12, 2016 2:25 pm

MrEngman wrote: ..., but still no sign of it for the for the Pi 3 B.

What is the output of:

Code: Select all

systemctl list-units | grep -i sit0

and

Code: Select all

systemctl status sys-subsystem-net-devices-sit0.device

on your PI 3B?

MrEngman · Tue Apr 12, 2016 3:00 pm

lbog wrote:
MrEngman wrote: ..., but still no sign of it for the for the Pi 3 B.
What is the output of:
Code: Select all
systemctl list-units | grep -i sit0
and
Code: Select all
systemctl status sys-subsystem-net-devices-sit0.device
on your PI 3B?

Pi 3 B -

Code: Select all

pi@Pi-3B-b:~ $ systemctl list-units | grep -i sit0
pi@Pi-3B-b:~ $ systemctl status sys-subsystem-net-devices-sit0.device
● sys-subsystem-net-devices-sit0.device
   Loaded: loaded
   Active: inactive (dead)

Pi Zero -

Code: Select all

pi@Pi-0a:~ $ systemctl list-units | grep -i sit0
sys-devices-virtual-net-sit0.device                                                             loaded active plugged   /sys/devices/virtual/net/sit0
sys-subsystem-net-devices-sit0.device                                                           loaded active plugged   /sys/subsystem/net/devices/sit0
pi@Pi-0a:~ $ systemctl status sys-subsystem-net-devices-sit0.device
● sys-subsystem-net-devices-sit0.device - /sys/subsystem/net/devices/sit0
   Loaded: loaded
   Active: active (plugged) since Tue 2016-04-12 14:47:06 BST; 1h 8min ago
   Device: /sys/devices/virtual/net/sit0

MrEngman

coding · Tue Apr 12, 2016 4:33 pm

Just curious, because I believe by default Kernel 4.4 does include the open source VC4 driver: Does that mean that driver is now active by default?

Tue Apr 12, 2016 4:35 pm

coding wrote:Just curious, because I believe by default Kernel 4.4 does include the open source VC4 driver: Does that mean that driver is now active by default?

Nope, exactly the same as 4.1 kernel - you enable it with a dtoverlay (or using raspi-config).

lbog · Tue Apr 12, 2016 6:44 pm

MrEngman wrote: Pi 3 B -

Code: Select all

pi@Pi-3B-b:~ $ systemctl list-units | grep -i sit0
pi@Pi-3B-b:~ $ systemctl status sys-subsystem-net-devices-sit0.device
● sys-subsystem-net-devices-sit0.device
   Loaded: loaded
   Active: inactive (dead)

What is the output of:

Code: Select all

modinfo sit
ls -la /lib/modules
uname -a
dmesg -T | grep -i 'linux version'

on your PI 3 B?

atkjoin · Tue Apr 12, 2016 7:03 pm

PhilE wrote:
atkjoin wrote:Alsamixer stops working after upgrading.
Do you have "dtparam=audio=on" in your config.txt? The board support code in the 4.4 kernel is minimal, so we have to rely on Device Tree much more.

Tank you PhilE and Massi. I add "dtparam=audio=on" in /boot/config.txt now it's working!!

MaxK1 · Tue Apr 12, 2016 7:29 pm

It seems to run a few degrees cooler (Or the reporting has changed)

Tue Apr 12, 2016 7:53 pm

MaxK1 wrote:It seems to run a few degrees cooler (Or the reporting has changed)

We've removed the io_is_busy flag, and handle the turbo/non-turbo changes dynamically in sdcard driver which means we should spend less time in turbo mode.

Tue Apr 12, 2016 7:54 pm

lbog wrote: Because in the kernel 4.4, those modules (ipv6, sit) are built-in:

That wasn't intentional. I've pushed an update where IPV6 is a module again.
@MrEngman does that make a difference to the behaviour you see?

MrEngman · Tue Apr 12, 2016 8:39 pm

lbog wrote:

MrEngman wrote: Pi 3 B -

Code: Select all

pi@Pi-3B-b:~ $ systemctl list-units | grep -i sit0
pi@Pi-3B-b:~ $ systemctl status sys-subsystem-net-devices-sit0.device
● sys-subsystem-net-devices-sit0.device
   Loaded: loaded
   Active: inactive (dead)

What is the output of:

Code: Select all

modinfo sit
ls -la /lib/modules
uname -a
dmesg -T | grep -i 'linux version'

on your PI 3 B?

Sorry, looks like I screwed up the Pi 3 B and it hadn't been updated to 4.4.6-v7 #874. Just updated it and output of commands are

Code: Select all

pi@Pi-3B-b:~ $ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:1f:8e:6a
          inet addr:192.168.16.30  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:138 errors:0 dropped:27 overruns:0 frame:0
          TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16517 (16.1 KiB)  TX bytes:13477 (13.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:11472 (11.2 KiB)  TX bytes:11472 (11.2 KiB)

wlan0     Link encap:Ethernet  HWaddr b8:27:eb:4a:db:3f
          inet addr:192.168.16.40  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:155 errors:0 dropped:136 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:56750 (55.4 KiB)  TX bytes:4017 (3.9 KiB)

pi@Pi-3B-b:~ $
pi@Pi-3B-b:~ $
pi@Pi-3B-b:~ $ systemctl list-units | grep -i sit0
sys-devices-virtual-net-sit0.device                                                                     loaded active plugged   /sys/devices/virtual/net/sit0
sys-subsystem-net-devices-sit0.device                                                                   loaded active plugged   /sys/subsystem/net/devices/sit0
pi@Pi-3B-b:~ $ systemctl status sys-subsystem-net-devices-sit0.device
● sys-subsystem-net-devices-sit0.device - /sys/subsystem/net/devices/sit0
   Loaded: loaded
   Active: active (plugged) since Tue 2016-04-12 21:25:58 BST; 2min 55s ago
   Device: /sys/devices/virtual/net/sit0
pi@Pi-3B-b:~ $ modinfo sit
modinfo: ERROR: Module sit not found.
pi@Pi-3B-b:~ $ ls -la /lib/modules
total 52
drwxr-xr-x 13 root root 4096 Apr 12 21:13 .
drwxr-xr-x 20 root root 4096 Feb 23 10:36 ..
drwxr-xr-x  3 root root 4096 Mar  3 08:27 4.1.17-v7+
drwxr-xr-x  3 root root 4096 Mar  4 20:39 4.1.18+
drwxr-xr-x  3 root root 4096 Mar  4 20:42 4.1.18-v7+
drwxr-xr-x  3 root root 4096 Mar 15 19:51 4.1.19+
drwxr-xr-x  3 root root 4096 Mar 21 22:08 4.1.19-v7+
drwxr-xr-x  3 root root 4096 Apr  5 20:13 4.1.20+
drwxr-xr-x  3 root root 4096 Mar 24 11:23 4.1.20-v7+
drwxr-xr-x  3 root root 4096 Apr  7 03:57 4.1.21+
drwxr-xr-x  3 root root 4096 Apr  9 01:15 4.1.21-v7+
drwxr-xr-x  3 root root 4096 Apr 12 21:22 4.4.6+
drwxr-xr-x  3 root root 4096 Apr 12 21:22 4.4.6-v7+
pi@Pi-3B-b:~ $ uname -a
Linux Pi-3B-b 4.4.6-v7+ #874 SMP Mon Apr 11 19:20:24 BST 2016 armv7l GNU/Linux
pi@Pi-3B-b:~ $ dmesg -T | grep -i 'linux version'
[Tue Apr 12 21:26:00 2016] Linux version 4.4.6-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #874 SMP Mon Apr 11 19:20:24 BST 2016
pi@Pi-3B-b:~ $ 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"

which is probably what you expected.

Just going to update my 4 Pi's to the new update to see what happens to sit0.

MrEngman

lbog · Tue Apr 12, 2016 8:53 pm

MrEngman wrote: which is probably what you expected.

Well, you updated it to late.

EDIT:

Code: Select all

firmware was updated to a087e80dd5316763fb7b6738f5428122a36e2a45

Code: Select all

cat /boot/.firmware_revision

MrEngman · Tue Apr 12, 2016 10:32 pm

dom wrote:
lbog wrote: Because in the kernel 4.4, those modules (ipv6, sit) are built-in:
That wasn't intentional. I've pushed an update where IPV6 is a module again.
@MrEngman does that make a difference to the behaviour you see?

Updated the four Pi's and things look OK. No sit0 in ifconfig on the B+ and 2 B.

Although I have ipv6 disable, using info from https://wiki.debian.org/DebianIPv6, on all four Pi's ipv6 shows in lsmod on the Pi 3 B and Zero so a bit of a waste of memory.

MrEngman

RonR · Tue Apr 12, 2016 10:36 pm

Anyone know why the bcm2708_rng module is not included in the new 4.4 kernel?

Tue Apr 12, 2016 10:59 pm

RonR wrote:Anyone know why the bcm2708_rng module is not included in the new 4.4 kernel?

We use the upstream driver and it's built in, so loading the modules isn't required (/dev/hwrng exists by default):
CONFIG_HW_RANDOM_BCM2835=y

Linux kernel is now 4.4

Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4

Re: Linux kernel is now 4.4