asandford
Posts: 1998
Joined: Mon Dec 31, 2012 12:54 pm
Location: Waterlooville

Re: Linux kernel is now 4.4

Tue May 17, 2016 4:44 pm

dom wrote: Are you trying to boot from remote SCSI device? If /lib/modules are on the remote device then the modules won't help you.
If you are just mounting the remote SCSI device after booting, then the module should be fine. Did you add it to /etc/modules?
The /root partition is on a remote device attached via iscsi, the pi boots from the sdcard but has nothing apart from /boot partition.

On a brand new install of jessie, i've put the (i think) required modules in /etc/modules, installed open-iscsi and rebooted:

Code: Select all

[email protected]:~# lsmod | grep -i scsi
iscsi_tcp               9263  0
libiscsi_tcp           12716  1 iscsi_tcp
libiscsi               35610  2 libiscsi_tcp,iscsi_tcp
[email protected]:~#
I defined a disk on the NAS, but it can't see it:

Code: Select all

[email protected]:~# iscsiadm --mode discovery --type sendtargets --portal 192.168.0.30
iscsiadm: No portals found
[email protected]:~#
dmesg shows it isn't fully up before open-iscsi is kicked off:

Code: Select all

[email protected]:~# dmesg | grep -i scsi
[    0.144655] SCSI subsystem initialized
[    0.260800] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    1.183420] Loading iSCSI transport class v2.0-870.
[    2.465570] systemd-sysv-generator[98]: Ignoring creation of an alias umountiscsi.service for itself
[    2.647682] systemd[1]: Found dependency on open-iscsi.service/start
[    2.668901] systemd[1]: Breaking ordering cycle by deleting job open-iscsi.service/start
[    2.673193] systemd[1]: Job open-iscsi.service/start deleted to break ordering cycle starting with basic.target/start
[    3.213170] iscsi: registered transport (tcp)
[email protected]:~#
So, the service is dead, but binary is still running:

Code: Select all

[email protected]:~# service open-iscsi status
● open-iscsi.service - LSB: Starts and stops the iSCSI initiator services and logs in to default targets
   Loaded: loaded (/etc/init.d/open-iscsi)
  Drop-In: /lib/systemd/system/open-iscsi.service.d
           └─fix-systemd-deps.conf
   Active: inactive (dead)

Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
[email protected]:~# ps -ef | grep iscsi
root        74     2  0 16:27 ?        00:00:00 [iscsi_eh]
root      1057  1047  0 16:30 pts/0    00:00:00 grep iscsi
[email protected]:~#

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5408
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Linux kernel is now 4.4

Tue May 17, 2016 5:45 pm

asandford wrote: The /root partition is on a remote device attached via iscsi, the pi boots from the sdcard but has nothing apart from /boot partition.
So the module for supporting iscsi is on the iscsi device. That's not going to work.
I'm afraid a custom kernel build with the module is the best option for you.

Unfortunately there are dozen of devices and file systems that could potentially be useful for booting from,
but as you have seen, these are often quite large, so building them all into kernel is not a good option.

asandford
Posts: 1998
Joined: Mon Dec 31, 2012 12:54 pm
Location: Waterlooville

Re: Linux kernel is now 4.4

Tue May 17, 2016 6:20 pm

dom wrote:[
So the module for supporting iscsi is on the iscsi device. That's not going to work.
I'm afraid a custom kernel build with the module is the best option for you.

Unfortunately there are dozen of devices and file systems that could potentially be useful for booting from,
but as you have seen, these are often quite large, so building them all into kernel is not a good option.
OK, thanks - I'll have to wait for pxe boot then.

Got iscsi working now (it is confirmed broken on systemd, but works with the init scripts):

Code: Select all

[email protected]:~#  /etc/init.d/open-iscsi start
[....] Starting open-iscsi (via systemctl): open-iscsi.service
. ok
[email protected]:~#
[email protected]:~# service open-iscsi status
● open-iscsi.service - LSB: Starts and stops the iSCSI initiator services and logs in to default targets
   Loaded: loaded (/etc/init.d/open-iscsi)
  Drop-In: /lib/systemd/system/open-iscsi.service.d
           └─fix-systemd-deps.conf
   Active: active (running) since Tue 2016-05-17 17:57:39 UTC; 10s ago
  Process: 1195 ExecStop=/etc/init.d/open-iscsi stop (code=exited, status=0/SUCCESS)
  Process: 1188 ExecStop=/etc/init.d/umountiscsi.sh stop (code=exited, status=0/SUCCESS)
  Process: 1260 ExecStart=/etc/init.d/open-iscsi start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/open-iscsi.service
           ├─1272 /usr/sbin/iscsid
           └─1273 /usr/sbin/iscsid
May 17 17:57:39 raspberrypi iscsid[1271]: iSCSI logger with pid=1272 started!
May 17 17:57:39 raspberrypi open-iscsi[1260]: Starting iSCSI initiator service: iscsidln: failed to create symbolic link ‘/run/sendsigs.omi…ile exists
May 17 17:57:39 raspberrypi open-iscsi[1260]: .
May 17 17:57:39 raspberrypi open-iscsi[1260]: Setting up iSCSI targets:
May 17 17:57:39 raspberrypi open-iscsi[1260]: iscsiadm: No records found
May 17 17:57:39 raspberrypi open-iscsi[1260]: .
May 17 17:57:39 raspberrypi open-iscsi[1260]: Mounting network filesystems:.
May 17 17:57:39 raspberrypi open-iscsi[1260]: Enabling network swap devices:.
May 17 17:57:39 raspberrypi systemd[1]: Started LSB: Starts and stops the iSCSI initiator services and logs in to default targets.
May 17 17:57:40 raspberrypi iscsid[1272]: iSCSI daemon with pid=1273 started!
Hint: Some lines were ellipsized, use -l to show in full.
[email protected]:~# 
[email protected]:~# iscsiadm --mode discovery --type sendtargets --portal 192.168.0.30
192.168.0.30:3260,1 iqn.1991-05.com.microsoft:winnas-tt1-target
192.168.134.1:3260,1 iqn.1991-05.com.microsoft:winnas-tt1-target
192.168.235.1:3260,1 iqn.1991-05.com.microsoft:winnas-tt1-target
[email protected]:~#

User avatar
AikonCWD
Posts: 180
Joined: Mon Jun 09, 2014 3:50 pm
Location: Barcelona

Re: Linux kernel is now 4.4

Tue May 17, 2016 10:03 pm

It is posible to overclock the SD card with the new firmware? I found 2 different commands:

Code: Select all

dtoverlay=sdhost,overclock_50=100
dtparam=sd_overclock=100
Which command should I use? Thanks
My e-mail = [email protected]

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5408
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Linux kernel is now 4.4

Tue May 17, 2016 10:20 pm

AikonCWD wrote:It is posible to overclock the SD card with the new firmware? I found 2 different commands:

Code: Select all

dtoverlay=sdhost,overclock_50=100
dtparam=sd_overclock=100
Which command should I use? Thanks
The latter is the recommended one. The former shouldn't be used.

Duncb82
Posts: 7
Joined: Tue May 21, 2013 6:22 am

Re: Linux kernel is now 4.4

Wed May 18, 2016 8:31 am

To expand on my wifi issue a bit, it seems it can connect but the connection only holds for around 10 seconds

If I do an ifup --force wlan0 then ping google, it will run for around 10 seconds before the network becomes unreachable

I tried an edimax dongle I had lying around (Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]) and it worked perfectly, so it seems its just an issue with the official adapter

I dont thinks it's a hardware fault, as dropping back to 4.1 it works perfectly

I've tried turning power management off, and also tried the 2 cmdline.txt additions mentioned at the start of the thread here:

viewtopic.php?f=29&t=130429

Neither made a difference

Aydan
Posts: 710
Joined: Fri Apr 13, 2012 11:48 am
Location: Germany, near Lake Constance

Re: Linux kernel is now 4.4

Wed May 18, 2016 11:19 am

asandford wrote:
dom wrote: Are you trying to boot from remote SCSI device? If /lib/modules are on the remote device then the modules won't help you.
If you are just mounting the remote SCSI device after booting, then the module should be fine. Did you add it to /etc/modules?
The /root partition is on a remote device attached via iscsi, the pi boots from the sdcard but has nothing apart from /boot partition.
Have you tried putting the module into an initramsf?
I did that on one of my SD cards for lvm.
You just have to be careful with kernel updates, or copy kernel.img to e.g. kernel-4.1.19-456.img and specify this kernel + the corresponding initramfs in config.txt so apt can't screw up booting by replacing the kernel.

Regards
Aydan

humke
Posts: 1
Joined: Mon May 23, 2016 8:33 am

Re: Linux kernel is now 4.4

Mon May 23, 2016 8:40 am

The first line of hash-signs should have one # added ;)

Code: Select all

 
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
#############################################################
This update bumps to rpi-4.4.y linux tree
Be aware there could be compatibility issues with some drivers
Discussion here:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=144087
##############################################################

asandford
Posts: 1998
Joined: Mon Dec 31, 2012 12:54 pm
Location: Waterlooville

Re: Linux kernel is now 4.4

Tue May 24, 2016 12:33 am

Aydan wrote: Have you tried putting the module into an initramsf?
I did that on one of my SD cards for lvm.
You just have to be careful with kernel updates, or copy kernel.img to e.g. kernel-4.1.19-456.img and specify this kernel + the corresponding initramfs in config.txt so apt can't screw up booting by replacing the kernel.

Regards
Aydan
Yes I have, and it only works if the iscsi modules are 'baked' into the kernel. As you say, any update to the kernel then breaks it all. I didn't know that a specific img could by loaded in the config.txt though - thanks for the 'heads-up' and I'll look into that.

gardar
Posts: 1
Joined: Wed May 25, 2016 1:55 pm

Re: Linux kernel is now 4.4

Wed May 25, 2016 2:02 pm

After updating the kernel I see that TXD0 has been mapped on GPIO 32 where as previously it was mapped at GPIO 14.

Is this expected?

cjan
Posts: 777
Joined: Sun May 06, 2012 12:00 am

Re: Linux kernel is now 4.4

Sun May 29, 2016 1:18 am

4.4.11-v7+ #888, what is drm-vc4-next improve?

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5408
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Linux kernel is now 4.4

Sun May 29, 2016 3:59 pm

cjan wrote:4.4.11-v7+ #888, what is drm-vc4-next improve?
You can see the changes here: https://github.com/raspberrypi/linux/pull/1463

Basically bringing raspberry pi kernel closer to the upstream kernel branch where the experimental graphics driver work occurs.
I can't give you details, but it should have no effect if you are not using the experimental graphics driver.
If you are, then I guess it's stability and performance improvements...

User avatar
algorithm
Posts: 185
Joined: Mon Nov 25, 2013 9:09 pm
Location: Flatland

Re: Linux kernel is now 4.4

Mon May 30, 2016 7:44 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?
Has this been re-reversed in the latest kernel(s)? I just burned a new image from the newest download at raspberrypi.org, did dist-upgrade and rpi-update. This is on a RPi3. So firmware is 2b9c0bfacfc11ee8bb9b30dc9cdb36289698f8a8 from 7 days ago, vcgencmd version is faf071dd4885c5ac1a89483d35a5326e7f69495f, kernel 4.4.11-v7+ #888. There's no "ipv6" in /etc/modules but ipv6 is enabled & functional. So it's built-in?

User avatar
DougieLawson
Posts: 37488
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Linux kernel is now 4.4

Mon May 30, 2016 9:31 pm

It's back as a module on 4.4.11+ & 4.4.11-v7+ #888

Code: Select all

[email protected] /lib/modules # find . -name "*ipv6*"
./4.4.11+/kernel/net/6lowpan/nhc_ipv6.ko
./4.4.11+/kernel/net/ipv6
./4.4.11+/kernel/net/ipv6/ipv6.ko
./4.4.11+/kernel/net/ipv6/netfilter/nf_nat_ipv6.ko
./4.4.11+/kernel/net/ipv6/netfilter/nf_dup_ipv6.ko
./4.4.11+/kernel/net/ipv6/netfilter/ip6t_ipv6header.ko
./4.4.11+/kernel/net/ipv6/netfilter/nf_defrag_ipv6.ko
./4.4.11+/kernel/net/ipv6/netfilter/nf_conntrack_ipv6.ko
./4.4.11+/kernel/net/ipv6/netfilter/nf_nat_masquerade_ipv6.ko
./4.4.11+/kernel/net/ipv6/netfilter/nf_reject_ipv6.ko
./4.4.11+/kernel/net/ipv6/netfilter/nf_log_ipv6.ko
./4.4.11-v7+/kernel/net/6lowpan/nhc_ipv6.ko
./4.4.11-v7+/kernel/net/ipv6
./4.4.11-v7+/kernel/net/ipv6/ipv6.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/nf_nat_ipv6.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/nf_dup_ipv6.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/ip6t_ipv6header.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/nf_defrag_ipv6.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/nf_conntrack_ipv6.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/nf_nat_masquerade_ipv6.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/nf_reject_ipv6.ko
./4.4.11-v7+/kernel/net/ipv6/netfilter/nf_log_ipv6.ko
[email protected] /lib/modules #
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
algorithm
Posts: 185
Joined: Mon Nov 25, 2013 9:09 pm
Location: Flatland

Re: Linux kernel is now 4.4

Tue May 31, 2016 12:03 pm

DougieLawson wrote:It's back as a module on 4.4.11+ & 4.4.11-v7+ #888
OK, great, but somehow it is also loaded by default and enabled on the network interfaces, except it's not in /etc/modules. So now I don't know where to disable it if I want that. Is use of /etc/modules deprecated? But "i2c-dev" is still in it.

Edit: so according to https://wiki.debian.org/DebianIPv6 the way to disable ipv6 is to add these lines to /etc/sysctl.conf

Code: Select all

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1
net.ipv6.conf.wlan0.disable_ipv6 = 1
That's not at all easy to remember (or find without googling) and does not seem to me like an improvement from using /etc/modules :-(

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5408
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Linux kernel is now 4.4

Tue May 31, 2016 2:11 pm

Open /etc/modprobe.d/ipv6.conf (or create it) and add:

Code: Select all

blacklist ipv6

User avatar
algorithm
Posts: 185
Joined: Mon Nov 25, 2013 9:09 pm
Location: Flatland

Re: Linux kernel is now 4.4

Tue May 31, 2016 6:06 pm

dom wrote:Open /etc/modprobe.d/ipv6.conf (or create it) and add:

Code: Select all

blacklist ipv6
Thanks. On a fresh install (dist-upgraded) it exists and contains:

Code: Select all

# Don't load ipv6 by default
alias net-pf-10 off
#alias ipv6 off
I don't get it :/ but I fear this is out of scope of the Advanced forum ... I mean, doesn't "alias net-pf-10 off" already mean to disable ipv6? What would "alias ipv6 off" add, or how does it differ from "blacklist ipv6"?

For me personally, this is all academic as usually the first thing I do is ENable ipv6 :) but I do wish to understand the changes. Thanks for your patience.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 6194
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: Linux kernel is now 4.4

Tue May 31, 2016 6:56 pm

algorithm wrote:
dom wrote:Open /etc/modprobe.d/ipv6.conf (or create it) and add:

Code: Select all

blacklist ipv6
Thanks. On a fresh install (dist-upgraded) it exists and contains:

Code: Select all

# Don't load ipv6 by default
alias net-pf-10 off
#alias ipv6 off
I don't get it :/ but I fear this is out of scope of the Advanced forum ... I mean, doesn't "alias net-pf-10 off" already mean to disable ipv6? What would "alias ipv6 off" add, or how does it differ from "blacklist ipv6"?

For me personally, this is all academic as usually the first thing I do is ENable ipv6 :) but I do wish to understand the changes. Thanks for your patience.
I believe it is baggage from the wheezy days. From what I gather, it used to disable ipv6 on wheezy, but doesn't do anything on jessie. I am reluctant to touch it until that's confirmed and I understand what it's meant to do and why it doesn't.

User avatar
DougieLawson
Posts: 37488
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Linux kernel is now 4.4

Tue May 31, 2016 7:14 pm

algorithm wrote:
DougieLawson wrote:It's back as a module on 4.4.11+ & 4.4.11-v7+ #888
OK, great, but somehow it is also loaded by default and enabled on the network interfaces, except it's not in /etc/modules.
Good, great choice of default action for those of us who want to embrace the twenty year old improvements to IP networks that should have been rolled out Worldwide at least ten years ago. IPv4 needs to die.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
bstrobl
Posts: 97
Joined: Wed Jun 04, 2014 8:31 pm
Location: Germany

Re: Linux kernel is now 4.4

Tue May 31, 2016 7:30 pm

DougieLawson wrote: Good, great choice of default action for those of us who want to embrace the twenty year old improvements to IP networks that should have been rolled out Worldwide at least ten years ago. IPv4 needs to die.
Going to have to agree here, the default should be enabled unless explicitly disabled. IPv4 is heavily broken at this stage with all the CGNAT and lack of addresses complicating things.

It's important to have and document a clean way of disabling it though for those who really don't want it.

User avatar
algorithm
Posts: 185
Joined: Mon Nov 25, 2013 9:09 pm
Location: Flatland

Re: Linux kernel is now 4.4

Tue May 31, 2016 10:08 pm

DougieLawson wrote:
algorithm wrote:
DougieLawson wrote:It's back as a module on 4.4.11+ & 4.4.11-v7+ #888
OK, great, but somehow it is also loaded by default and enabled on the network interfaces, except it's not in /etc/modules.
Good, great choice of default action for those of us who want to embrace the twenty year old improvements to IP networks that should have been rolled out Worldwide at least ten years ago. IPv4 needs to die.
I'm not disagreeing! Just wondering, if not in /etc/modules, where it IS enabled. And what the "official" way to disable it is (probably what Dom wrote, except then what are those other directives in that file..)

Massi
Posts: 1691
Joined: Fri May 02, 2014 1:52 pm
Location: Italy

Re: Linux kernel is now 4.4

Wed Jun 01, 2016 10:03 am

DougieLawson wrote:Good, great choice of default action for those of us who want to embrace the twenty year old improvements to IP networks that should have been rolled out Worldwide at least ten years ago. IPv4 needs to die.
:lol:
i NEED the possibility of putting a like to Dougie's posts

Aydan
Posts: 710
Joined: Fri Apr 13, 2012 11:48 am
Location: Germany, near Lake Constance

Re: Linux kernel is now 4.4

Sun Jun 12, 2016 5:13 pm

OffTopic, but for clarification:
asandford wrote:
Aydan wrote: Have you tried putting the module into an initramsf?
I did that on one of my SD cards for lvm.
You just have to be careful with kernel updates, or copy kernel.img to e.g. kernel-4.1.19-456.img and specify this kernel + the corresponding initramfs in config.txt so apt can't screw up booting by replacing the kernel.

Regards
Aydan
Yes I have, and it only works if the iscsi modules are 'baked' into the kernel. As you say, any update to the kernel then breaks it all. I didn't know that a specific img could by loaded in the config.txt though - thanks for the 'heads-up' and I'll look into that.
Short story: Pi3 can boot from iSCSI with stock kernel (tried with 4.1.19 & 4.4.9) by using initramfs-tools
Long story here

asandford
Posts: 1998
Joined: Mon Dec 31, 2012 12:54 pm
Location: Waterlooville

Re: Linux kernel is now 4.4

Sun Jun 12, 2016 5:45 pm

Aydan wrote: Short story: Pi3 can boot from iSCSI with stock kernel (tried with 4.1.19 & 4.4.9) by using initramfs-tools
Long story here
Interesting, thanks. FWIW, here is the way that I and another forum member hacked a solution.

Will be great once the pxe boot gets sorted out (heard in the Pi Podcast (~24:50 - 26:35, but the whole thing is worth a listen) that it should be just around the corner).

tony power
Posts: 33
Joined: Tue Mar 08, 2016 9:07 pm

Re: Linux kernel is now 4.4

Wed Jul 06, 2016 4:47 am

my rpi 3.
raspistill stopped working after kernel upgrade
but raspivid still works

Code: Select all

sudo rpi-update
reboot
here is error message.

Code: Select all

# raspistill -o img.jpg
raspistill: error while loading shared libraries: libbrcmGLESv2.so: cannot open shared object file: No such file or directory
I want to fix this issue please.

Return to “Advanced users”