w1-gpio not working on Pi Zero W

[DrRob]

I added dtoverlay=w1-gpio to the end of /mnt/mmcblk0p1/config.txt (in the [ALL] section), then I installed w1-4.9.22-piCore.tcz, added it to /mnt/mmcblk0p2/tce/onboot.lst, ran filetool.sh -b and rebooted.

However:

tc@box:~$ sudo modprobe w1-gpio
modprobe: can't load module wire (kernel.tclocal/drivers/w1/wire.ko): unknown symbol in module, or unknown parameter

Is it broken, or have I don't something wrong?

Thanks,
Rob.

[Juanito]

modprobe: can't load module wire (kernel.tclocal/drivers/w1/wire.ko): unknown symbol in module, or unknown parameter

That message means that wire.ko is missing a kernel module on which it depends.

Look at the output of "modinfo wire" to find out which other modules it requires.

[DrRob]

Seems it needs module "cn", but I can't find a package that has that in it.  Help...

[DrRob]

I think the "w1-4.9.22-piCore" package ought to include the "lib/modules/4.9.22-piCore/kernel/drivers/connector/cn.ko" file from http://tinycorelinux.net/9.x/armv6/releases/RPi/src/kernel/4.9.22-piCore_modules.tar.xz

Next to work out how to make that so.

[DrRob]

OK, I made it work by the following steps (performed in Ubuntu):

• wget http://ftp.nluug.nl/os/Linux/distr/tinycorelinux/9.x/armv6/tcz/w1-4.9.22-piCore.tcz
• wget http://tinycorelinux.net/9.x/armv6/releases/RPi/src/kernel/4.9.22-piCore_modules.tar.xz
• unsquashfs w1-4.9.22-piCore.tcz
• cd squashfs_root/usr/local
• tar -xz -xvf ../../../4.9.22-piCore_modules.tar.xz lib/modules/4.9.22-piCore/kernel/drivers/connector/cn.ko
• cd ../..
• mksquashfs . ../w1-4.9.22-piCore-cn.tcz
• cd ..
• md5sum w1-4.9.22-piCore-cn.tcz > w1-4.9.22-piCore-cn.tcz.md5.txt
• scp w1-4.9.22-piCore-cn.* pi:/mnt/mmcblk0p2/tce/optional
• ssh pi
• mv w1-4.9.22-piCore-cn.* /mnt/mmcblk0p2/tce
• edit the "w1-4.9.22-piCore.tcz" I had in /mnt/mmcblk0p2/tce/onboot.lst to "w1-4.9.22-piCore-cn.tcz"
• sudo reboot

(Note: I have a "pi" entry in my .ssh/config and I've installed my public key to the pi so that I can scp and ssh to it without username/password)

[DrRob]

Step 14 should have been "sudo exitcheck.sh reboot" (I'm learning...)

[polikuo]

tar -xz -xvf ../../../4.9.22-piCore_modules.tar.xz lib/modules/4.9.22-piCore/kernel/drivers/connector/cn.ko

Weird 
I believe to untar a *.tar.xz file, one should do

Code: [Select]

tar Jxf file.tar.xz

BTW, each option of tar has a meaning.
-  in linux, the dash usually starts at the beginning of the options. (However, for tar command, it can be omitted)
x  extract the file
c  compress files
z  extract/compress files by gzip
j  bzip2
J  any thing hat has xz in it
v  verbose output

I've heard that modern tar recognizes the format by itself. 
Not sure if that's the case for "busybox tar" (default for TC).

[DrRob]

Oops, sorry - typo: I meant to type "tar --xz -tvf ..." 

"--xz" is equivalent to "-J", so your "tar Jxf ..." is the neater option.

[bmarkus]

Seems it needs module "cn", but I can't find a package that has that in it.  Help...

Update to 9.0.1

http://forum.tinycorelinux.net/index.php/topic,21141.0.html

[bmarkus]

I've heard that modern tar recognizes the format by itself. 
Not sure if that's the case for "busybox tar" (default for TC).

Code: [Select]

tar xf file.tar.xz
works for BusyBox

[DrRob]

Update to 9.0.1

That's odd, I was already using 9.0.1, downloaded on June 11th, but now I see that 9.0.1 was released on June 12th, and the zipfile is different to the one I already had.  I think I must have slipped into a parallel universe for a while there... 

Thanks for the update.

Rob.