I just did an upgrade on my sheevaplug running squeeze.
I can't do anything with IPv6 on it now (worked fine before the
upgrade)
When I try modprobe ipv6 I get
FATAL: Error inserting ipv6
(/lib/modules/2.6.32-5-kirkwood/kernel/net/ipv6/ipv6.ko): Unknown symbol
in module, or unknown
Rick Thomas rick.tho...@pobox.com writes:
Hi,
I just did an upgrade on my sheevaplug running squeeze.
I can't do anything with IPv6 on it now (worked fine before the
upgrade)
When I try modprobe ipv6 I get
FATAL: Error inserting ipv6
On Tue, 15 May 2012, Rick Thomas wrote:
I just did an upgrade on my sheevaplug running squeeze.
I can't do anything with IPv6 on it now (worked fine before the upgrade)
When I try modprobe ipv6 I get
FATAL: Error inserting ipv6
On 15/05/12 12:56, Arnaud Patard (Rtp) wrote:
[snip]
Please make sure that the new kernel has been flashed and that you've
rebooted after that.
Seconded.
I find I need to do an explicit flash-kernel on both my SheevaPlugs
after any kind of upgrade involving the kernel.
Despite the name, it
On Tue, May 15, 2012 at 02:28:57PM +0100, John Winters wrote:
On 15/05/12 12:56, Arnaud Patard (Rtp) wrote:
[snip]
Please make sure that the new kernel has been flashed and that you've
rebooted after that.
Seconded.
I find I need to do an explicit flash-kernel on both my SheevaPlugs
after any
On Tue, 15 May 2012, John Winters wrote:
I find I need to do an explicit flash-kernel on both my SheevaPlugs after any
kind of upgrade involving the kernel.
Despite the name, it doesn't actually flash anything on a SheevaPlug; it just
builds new uInitrd and uImage files in the /boot
* Rolf Offermanns r...@offermanns.de [2012-05-11 00:05]:
What happens when you press the power button for more than 5s? Will
you machine power off? Because mine does not but instead goes into the
state described above. The only option I have once it is in this state
is to powercycle. Otherwise
Hi
I have lsmod showing
Module Size Used by
ipv6 262419 18
despite having
Slug# cat /etc/modprobe.d/blacklist.conf
blacklist ipv6
and
Slug# cat /etc/sysctl.d/disableipv6.conf
net.ipv6.conf.all.disable_ipv6=1
and
Slug# sysctl -a | grep disable_ipv6
On 15/05/12 18:46, Alan Snelgrove wrote:
[snip]
I have read that adding ipv6.disable=1 to the kernel
line in the bootloader configuration fixes the problem.
But I don't know how to do that on a NSLU2 or anywhere else.
Can someone please point me in the right direction.
Have you tried
On 15 May 2012, at 21:10, John Winters wrote:
On 15/05/12 18:46, Alan Snelgrove wrote:
[snip]
I have read that adding ipv6.disable=1 to the kernel
line in the bootloader configuration fixes the problem.
But I don't know how to do that on a NSLU2 or anywhere else.
Can someone please
On Tue, 15 May 2012 15:17:59 +0100, Steve McIntyre wrote:
On Tue, May 15, 2012 at 02:28:57PM +0100, John Winters wrote:
On 15/05/12 12:56, Arnaud Patard (Rtp) wrote:
[snip]
Please make sure that the new kernel has been flashed and that
you've
rebooted after that.
Seconded.
I find I need
11 matches
Mail list logo