PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2439
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 12:21 pm

That driver was dropped from the upstream kernel in the move from 3.18 to 3.19 .

You could contact the author (Jan M. Hochstein <[email protected]>) to find out what happened, but otherwise your options are:
1) Build it yourself (you may need to alter it to run on the current kernel). Unfortunately you will need to do that for every kernel build you use.
2) Look for an alternative LIRC setup. Many people use an IR sensor hooked up to a GPIO pin, and there are lots of tutorials available.
3) Stick to a 3.18 kernel.

Energia
Posts: 15
Joined: Mon Oct 06, 2014 12:47 pm

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 12:54 pm

Camera video stream doesn't work on 4.0 with this method (but raspivid works):

Code: Select all

sudo modprobe bcm2835-v4l2
cvlc v4l2:///dev/video0 --v4l2-width 1024 --v4l2-height 768 --v4l2-chroma h264 --sout '#standard{access=http,mux=ts,dst=0.0.0.0:12345}'
Vlc doesn't close, but I get kernel messages right in console that I didn't get on v3. Nothing is on when I try to view the stream on PC with vlc player, open network -> http://IP_ADDRESS:12345

Works on kernel v3.

remkolodder
Posts: 11
Joined: Thu Jul 16, 2015 8:01 am
Contact: Website

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 12:58 pm

There is no /dev/video0 on my machine.

For the other questions:

$ vcgencmd get_mem gpu
gpu=16M
$ vcgencmd get_camera
supported=0 detected=0

The camera is properly seated on both active PI's that have a camera. It worked till the upgrade so I would rule out that issue :)
Best regards,

Remko

remkolodder
Posts: 11
Joined: Thu Jul 16, 2015 8:01 am
Contact: Website

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 1:10 pm

remkolodder wrote:There is no /dev/video0 on my machine.

For the other questions:

$ vcgencmd get_mem gpu
gpu=16M
$ vcgencmd get_camera
supported=0 detected=0

The camera is properly seated on both active PI's that have a camera. It worked till the upgrade so I would rule out that issue :)
I need to mention that I took the wrong pi for this output previously;

pi3$ sudo vcdbg log msg
Unable to determine the value of __LOG_START
Unable to read logging_header from 0x00000000

That is the correct output from pi3

The other output is from the correct pi..
Best regards,

Remko

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2439
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 2:32 pm

Good - that makes sense then (well, almost).

With gpu_mem=16 is only enough to run the cutdown firmware (start_cd.elf). This does not start the camera service, and does not include logging.

On my Pi, if I ask for gpu_mem=16 and start_x=1, I get the expanded firmware with 128M of GPU memory. I don't understand why yours is different.

After updating to the most recent firmware you should see the following md5sums:

Code: Select all

d3d0e6db59438446436f8dfe2241c8ea  bcm2708-rpi-b.dtb
4469348e1cf3a8a53f14a5540154e1c2  bcm2708-rpi-b-plus.dtb
3465851308048da3566010e88ad9c946  bcm2708-rpi-cm.dtb
7555faa3b7d65934c32c46330e405847  bcm2709-rpi-2-b.dtb
06e8e69c96e73bbf66403e1229d3f151  bootcode.bin
72547a34c898ea7c3e25a1640a70486b  fixup_cd.dat
b34a79bd89d76c7b9a94abdc8943a050  fixup.dat
a56b335cd27826b5ee731990a5146cfc  fixup_db.dat
604f1e37b2a2405352c554bcb4fc6e28  fixup_x.dat
bbd6710c4cfc5eb5b1eb0b9318c670eb  kernel7.img
02193f7c5e24f415472022b4a6cd8b25  kernel.img
3b0c4c685aa624a35fd20718234eecea  start_cd.elf
2a63c7398117cd48d8e06286c2a63129  start_db.elf
5cba501303a86ce543de68e1baa0f7d0  start.elf
002f31282b8c5b47209088ad19b1f42b  start_x.elf
Run:

Code: Select all

cd /boot
md5sum *
and make sure yours match.

You should also decide how much GPU memory you really need - start by setting gpu_mem to 128MB and verify that your camera starts working again.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2439
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 2:34 pm

@energia Go through the same steps as @remkolodder, starting with your config.txt and making sure you have enough GPU memory.

remkolodder
Posts: 11
Joined: Thu Jul 16, 2015 8:01 am
Contact: Website

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 6:58 pm

@PhilE:
[ 11.868459] Linux video capture interface: v2.00
[ 12.001140] : bcm2835-v4l2: error -1 while loading driver
Those are the lines from dmesg now, after changing it to 128mb, which is a better line than before.
$ vcgencmd get_camera
supported=0 detected=0
$ vcgencmd get_mem gpu
gpu=128M
No /dev/video0 yet :)

edit:

Just checked the checksums and they are the same for the files mentioned :-)
Best regards,

Remko

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2439
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 7:46 pm

And what about sudo vcdbg log msg?

remkolodder
Posts: 11
Joined: Thu Jul 16, 2015 8:01 am
Contact: Website

Re: Linux kernel is now 4.0

Fri Jul 17, 2015 9:15 pm

Both on the rasp-B and the rasp-B2 the same results now:
$ sudo vcdbg log msg
000682.553: HDMI:EDID error reading EDID block 0 attempt 0
000683.817: HDMI:EDID error reading EDID block 0 attempt 1
000685.076: HDMI:EDID error reading EDID block 0 attempt 2
000686.335: HDMI:EDID error reading EDID block 0 attempt 3
000687.594: HDMI:EDID error reading EDID block 0 attempt 4
000688.852: HDMI:EDID error reading EDID block 0 attempt 5
000690.111: HDMI:EDID error reading EDID block 0 attempt 6
000691.369: HDMI:EDID error reading EDID block 0 attempt 7
000692.628: HDMI:EDID error reading EDID block 0 attempt 8
000693.886: HDMI:EDID error reading EDID block 0 attempt 9
000694.908: HDMI:EDID giving up on reading EDID block 0
000697.039: HDMI:Setting property pixel encoding to Default
000697.059: HDMI:Setting property pixel clock type to PAL
000697.078: HDMI:Setting property content type flag to No data
000697.100: HDMI:Setting property fuzzy format match to enabled
000708.437: gpioman: gpioman_get_pin_num: pin LEDS_RUNNING not defined
000708.461: gpioman: gpioman_get_pin_num: pin LEDS_NAND_ACTIVITY not defined
000708.483: gpioman: gpioman_get_pin_num: pin LEDS_USB_ACTIVITY not defined
000708.504: gpioman: gpioman_get_pin_num: pin LEDS_FATAL_ERROR not defined
000708.526: gpioman: gpioman_get_pin_num: pin LEDS_APP_OK not defined
000708.548: gpioman: gpioman_get_pin_num: pin LEDS_APP_FAILED not defined
000708.568: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_AUTH not defined
000708.591: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_UNAUTH not defined
000708.613: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_ON not defined
000708.635: gpioman: gpioman_get_pin_num: pin LEDS_DVI_ON not defined
000708.657: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_HPD_UP not defined
000708.678: gpioman: gpioman_get_pin_num: pin LEDS_REMOTE_CONTROL not defined
000708.699: gpioman: gpioman_get_pin_num: pin LEDS_ARM_CONTROLLED not defined
000714.264: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
000714.290: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<<
000714.676: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
000715.944: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
000717.207: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
000718.471: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
000719.734: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
000720.998: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
000722.261: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
000723.524: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
000724.789: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
000726.053: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
000727.079: hdmi: HDMI:EDID giving up on reading EDID block 0
000727.108: hdmi: HDMI: No lookup table for resolution group 0
000727.125: hdmi: HDMI: hotplug attached with DVI support
000727.184: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
000727.548: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
000728.809: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
000730.071: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
000731.332: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
000732.594: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
000733.855: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
000735.117: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
000736.378: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
000737.639: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
000738.901: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
000739.925: hdmi: HDMI:EDID giving up on reading EDID block 0
000739.984: hdmi: HDMI: hotplug deassert
000739.999: hdmi: HDMI: HDMI is currently off
000740.013: hdmi: HDMI: changing mode to unplugged
000740.036: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
000740.769: *** Restart logging

000741.889: Read command line from file 'cmdline.txt'
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait

000742.655: Loading 'kernel.img' from SD card
000979.590: Kernel trailer DTOK property says yes
000979.610: Kernel trailer DDTK property says no
000979.696: Loading 'bcm2708-rpi-b.dtb' from SD card
001005.292: dtparam: cache_line_size=32
001032.959: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
002624.840: vchiq_core: vchiq_init_state: slot_zero = 0x57c80000, is_master = 1
002628.556: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
002632.505: gpioman: gpioman_get_pin_num: pin LEDS_RUNNING not defined
002632.531: gpioman: gpioman_get_pin_num: pin LEDS_NAND_ACTIVITY not defined
002632.552: gpioman: gpioman_get_pin_num: pin LEDS_USB_ACTIVITY not defined
002632.573: gpioman: gpioman_get_pin_num: pin LEDS_FATAL_ERROR not defined
002632.595: gpioman: gpioman_get_pin_num: pin LEDS_APP_OK not defined
002632.618: gpioman: gpioman_get_pin_num: pin LEDS_APP_FAILED not defined
002632.642: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_AUTH not defined
002632.665: gpioman: gpioman_get_pin_num: pin LEDS_HDCP_UNAUTH not defined
002632.688: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_ON not defined
002632.711: gpioman: gpioman_get_pin_num: pin LEDS_DVI_ON not defined
002632.733: gpioman: gpioman_get_pin_num: pin LEDS_HDMI_HPD_UP not defined
002632.755: gpioman: gpioman_get_pin_num: pin LEDS_REMOTE_CONTROL not defined
002632.777: gpioman: gpioman_get_pin_num: pin LEDS_ARM_CONTROLLED not defined
013597.912: mmal: mmal_ril_component_create: could not create RIL component 'camera'
013597.945: mmal: mmal_component_create_core: could not create component 'ril.camera' (1)
013597.985: mmalsrv: mmal_server_do_component_create: could not create component: 1
Best regards,

Remko

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

Re: Linux kernel is now 4.0

Sat Jul 18, 2015 4:45 pm

remkolodder wrote: $ vcgencmd get_camera
supported=0 detected=0
$ vcgencmd get_mem gpu
gpu=128M
This suggests you are not using start_x.elf. Can you post the exact contents of config.txt?

remkolodder
Posts: 11
Joined: Thu Jul 16, 2015 8:01 am
Contact: Website

Re: Linux kernel is now 4.0

Sat Jul 18, 2015 7:59 pm

Hi dom,

Yes ofcourse:
$ cat /boot/config.txt
# For more options and information see
# http://www.raspberrypi.org/documentatio ... fig-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

start_x=0
gpu_mem=128
disable_camera_led=1
Best regards,

Remko

ThatGuy39123
Posts: 4
Joined: Wed Jul 15, 2015 2:23 pm

Re: Linux kernel is now 4.0

Sat Jul 18, 2015 9:13 pm

Greetings Dom,

You're correct - dm_mod is all good. I updated to the new kernel and updated initramfs and got caught without the module. Looks like I missed it in /etc/initramfs-tools/modules.

ThatGuy

Habitat
Posts: 1
Joined: Sun Jul 19, 2015 1:18 am

Re: Linux kernel is now 4.0

Sun Jul 19, 2015 1:48 am

Massi wrote:anyone testing the new kernel can check if finalyi r8188eu dongles are working "out of the box"? :)
I have a DWA-131 WiFi dongle that worked fine on 3.18, once I installed one of Mr Engmans fixes that is. I have just updated to 4.0 and everything appears to work fine, except now I am unable to use my dongle. How do I access Mr Engmans patch?

Thanks to Dougie Lawson hints and to Mr Engmans patch., I managed to get my WiFi working again. For those that might be interested I used...

wget https://dl.dropboxusercontent.com/u/802 ... 805.tar.gz
tar xzf 8192eu-4.0.5-v7-805.tar.gz
sudo install -p -m 644 8192eu.ko /lib/modules/4.0.8-v7+/kernel/drivers/net/wireless
sudo depmod 4.0.8-v7+
and then rebooted
Last edited by Habitat on Mon Jul 20, 2015 10:07 am, edited 1 time in total.

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

Re: Linux kernel is now 4.0

Sun Jul 19, 2015 9:02 am

4.0.8 #805 (latest rpi-update version) is working just fine with Mr Engman's 8188eu driver (installed using his install-wifi script).

The driver that's built in to the kernel does NOT work for more than a minute without disconnecting/reconnecting. There's something badly borked with that version.
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.

Online_ID
Posts: 2
Joined: Mon Jul 20, 2015 4:51 am

Re: Linux kernel is now 4.0

Mon Jul 20, 2015 4:54 am

chronyd no longer starts with syslog entry.

Jul 19 23:22:11 chronyd[2838]: Linux kernel major=4 minor=0 patch=8
Jul 19 23:22:11 chronyd[2838]: Fatal error : Kernel's major version not supported yet, sorry

Thanks,

Joey

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2439
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Linux kernel is now 4.0

Mon Jul 20, 2015 10:37 am

What does "chronyd -v" report? I've just installed it (on 4.0) and got 1.24. If you have an earlier version:

Code: Select all

sudo apt-get update
sudo apt-get install chrony

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

Re: Linux kernel is now 4.0

Mon Jul 20, 2015 11:27 am

remkolodder wrote: start_x=0
gpu_mem=128
disable_camera_led=1
You have start_x=0, so no camera support. You need start_x=1 for camera support.

remkolodder
Posts: 11
Joined: Thu Jul 16, 2015 8:01 am
Contact: Website

Re: Linux kernel is now 4.0

Mon Jul 20, 2015 11:30 am

Ah, is that what start_x means. I thought that meant starting the X-window system. Let me retry. I'll report back in a few minutes ;)
Best regards,

Remko

remkolodder
Posts: 11
Joined: Thu Jul 16, 2015 8:01 am
Contact: Website

Re: Linux kernel is now 4.0

Mon Jul 20, 2015 11:32 am

Yes you are right. Thank you! (could have figured that out myself, bwah :))

cheers
Remko
Best regards,

Remko

Online_ID
Posts: 2
Joined: Mon Jul 20, 2015 4:51 am

Re: Linux kernel is now 4.0

Tue Jul 21, 2015 5:37 am

@PhilE - Chrony version Question

$ chronyd -v
chronyd (chrony) version 1.24

When I issue the following commands I get the following responses:

$ sudo invoke-rc.d chrony restart
Restarting time daemon: Starting /usr/sbin/chronyd...
chronyd is running and offline.
$

but if I look at 'ps -auxw' I do not see anything releated to chrony and I see the following in the syslog 'tail -f /var/log/syslog':

Jul 20 23:00:10 chronyd[3335]: chronyd version 1.24 starting
Jul 20 23:00:10 chronyd[3335]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Jul 20 23:00:10 chronyd[3335]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Jul 20 23:00:10 chronyd[3335]: Linux kernel major=4 minor=0 patch=8
Jul 20 23:00:10 chronyd[3335]: Fatal error : Kernel's major version not supported yet, sorry

If you google 'chrony Kernel's major version not supported yet, sorry' then you will see some kernel 3.0 bug reported from 2011... I suspect this is the same case statement 'feature' that we saw back in 2011. (Bug Report # 628919 and 638252)

Frankly, (and ignorance may be a factor here), I don't see how version 1.24 works with kernel 3.0 let alone 4.0. The fix in the file sys_linux.c for kernel 3.0 was not until version 1.26 according to the files I found in here -> https://github.com/mlichvar/chrony/releases?after=1.30

I was originally going to submit a bug report but I can see that it was already fixed and the problem now seems to be either 1. I don't under stand (which is likely) or 2. Raspian needs to update to a newer version. (Version 2.1).

Thanks,

Joey.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2439
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Linux kernel is now 4.0

Tue Jul 21, 2015 8:15 am

You're right. I spend so much time at the kernel level I didn't check syslog - I get the same failure. I suspect that very few people use chrony since ntp is installed by default.

The best course of action is probably to raise it with the Raspbian developers via the bug tracking system here. That way it will get tracked and dealt with.

Bensay
Posts: 1
Joined: Fri Jul 24, 2015 1:21 pm

Re: Linux kernel is now 4.0

Fri Jul 24, 2015 1:26 pm

Hi all RPI techies,

Is any plan to upgrade to Ker,el 4.1.3 branch according to the 4.0.9 EOL ?

Thanks for all
Bensay

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

Re: Linux kernel is now 4.0

Fri Jul 24, 2015 3:35 pm

Bensay wrote:Is any plan to upgrade to Ker,el 4.1.3 branch according to the 4.0.9 EOL ?
4.1 seems stable (used by forthcoming OpenELEC and OSMC releases) so I imagine we'll move to it pretty soon.

azbest_hu
Posts: 8
Joined: Thu Sep 20, 2012 9:18 am

Re: Linux kernel is now 4.0

Sat Aug 01, 2015 11:52 am

Hi,

Is there a build config file placed somewhere in the system while using kernel 4.0?
It seems /proc/config.gz is missing from 4.0. Maybe a configuration option is not set to be enabled:

/proc/config.gz isn't available in Debian, because the config is provided in /boot/config-*, no need for the in-memory variant (Kernel configuration CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC).
- https://wiki.debian.org/KernelFAQ


Return to “Advanced users”