Re: random(4) update causes mips compile fail | mips boot fail

2013-09-08 Thread Dag-Erling Smørgrav
Glen Barber g...@freebsd.org writes: The correct workaround (which now I see I should have done before locking head/) is to revert this commit so it can be properly fixed. Glen, to be fair, the mips boot fails because they're trying to use a device before it's ready. It just so happens that

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-08 Thread Mark R V Murray
On 8 Sep 2013, at 01:36, Glen Barber g...@freebsd.org wrote: Either way, I think this commit needs to be reverted until properly fixed and tested. The hyperbole is getting a little thick. How about sysctl kern.random.sys.seeded=1 ?? M -- Mark R V Murray signature.asc Description:

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-08 Thread Mark R V Murray
On 8 Sep 2013, at 01:31, Glen Barber g...@freebsd.org wrote: On Sat, Sep 07, 2013 at 05:27:19PM -0700, Adrian Chadd wrote: ok. So I can work around this for these MIPS AP images by echoing something into /dev/random ? The correct workaround (which now I see I should have done before

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-08 Thread Glen Barber
On Sun, Sep 08, 2013 at 11:00:24AM +0200, Dag-Erling Smørgrav wrote: Glen Barber g...@freebsd.org writes: The correct workaround (which now I see I should have done before locking head/) is to revert this commit so it can be properly fixed. Glen, to be fair, the mips boot fails because

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-08 Thread Mark R V Murray
On 8 Sep 2013, at 18:31, Glen Barber g...@freebsd.org wrote: On Sun, Sep 08, 2013 at 11:00:24AM +0200, Dag-Erling Smørgrav wrote: Glen Barber g...@freebsd.org writes: The correct workaround (which now I see I should have done before locking head/) is to revert this commit so it can be

random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Sean Bruno
with nodevice random I can no longer compile for MIPS --- kernel.debug --- pseudo_rng.o:(.data+0x3c): undefined reference to `random_null_func' pseudo_rng.o:(.data+0x44): undefined reference to `random_null_func' pseudo_rng.o:(.data+0x74): undefined reference to `random_null_func'

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Sean Bruno
On Sat, 2013-09-07 at 18:34 +0100, Mark R V Murray wrote: Configuration file: /etc/cfg/hostapd.wlan0.conf Using interface wlan0 with hwaddr 00:00:88:88:22:22 and ssid TESTBRUNO Entropy device is blocking. Can you please see if you can get the output of sysctl -a | grep random at that

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 17:43, Sean Bruno sean_br...@yahoo.com wrote: with nodevice random I can no longer compile for MIPS --- kernel.debug --- pseudo_rng.o:(.data+0x3c): undefined reference to `random_null_func' pseudo_rng.o:(.data+0x44): undefined reference to `random_null_func'

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 17:43, Sean Bruno sean_br...@yahoo.com wrote: trying to enable random on my DIR-825 kernconf I get this on boot: Configuration file: /etc/cfg/hostapd.wlan0.conf Using interface wlan0 with hwaddr 00:00:88:88:22:22 and ssid TESTBRUNO Entropy device is blocking Please make a

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Sean Bruno
On Sat, 2013-09-07 at 18:39 +0100, Mark R V Murray wrote: On 7 Sep 2013, at 17:43, Sean Bruno sean_br...@yahoo.com wrote: trying to enable random on my DIR-825 kernconf I get this on boot: Configuration file: /etc/cfg/hostapd.wlan0.conf Using interface wlan0 with hwaddr 00:00:88:88:22:22

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Sean Bruno
On Sat, 2013-09-07 at 19:40 +0100, Mark R V Murray wrote: Looks like it does indeed work if that is set to 1. This DIR-825 config, should be loading random as a module, not built into the kernel due to size limitations of the kernel on this board. Hmm. I'll set it back to 1, but

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Sean Bruno
On Sat, 2013-09-07 at 19:56 +0100, Mark R V Murray wrote: Ok. Right now, the mips kernel doesn't build unless I have random built in, we were using it as a module previously. I'm testing a fix, but if you want to help out, please move the random_null_func() from randomdev.c to

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 19:36, Sean Bruno sean_br...@yahoo.com wrote: On Sat, 2013-09-07 at 18:39 +0100, Mark R V Murray wrote: On 7 Sep 2013, at 17:43, Sean Bruno sean_br...@yahoo.com wrote: trying to enable random on my DIR-825 kernconf I get this on boot: Configuration file:

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 19:49, Sean Bruno sean_br...@yahoo.com wrote: On Sat, 2013-09-07 at 19:40 +0100, Mark R V Murray wrote: Looks like it does indeed work if that is set to 1. This DIR-825 config, should be loading random as a module, not built into the kernel due to size limitations of

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Sean Bruno
Nearly there - I saw that too. Proposed fix enclosed. M Compile succeeds, booted up and I still see the blocking message and the machine does not post fully. setting sys/dev/random/randomdev_soft.c .seeded = 1. allows the system to boot properly. Sean signature.asc Description:

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Ian Lepore
On Sat, 2013-09-07 at 19:40 +0100, Mark R V Murray wrote: On 7 Sep 2013, at 19:36, Sean Bruno sean_br...@yahoo.com wrote: On Sat, 2013-09-07 at 18:39 +0100, Mark R V Murray wrote: On 7 Sep 2013, at 17:43, Sean Bruno sean_br...@yahoo.com wrote: trying to enable random on my DIR-825

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Adrian Chadd
Hi! On 7 September 2013 13:38, Ian Lepore i...@freebsd.org wrote: I keep trying to say this, and I keep getting the feeling that it just doesn't register with anyone I say it to, like I'm speaking some language from another planet or something... There may be NO entropy of any sort

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 20:12, Sean Bruno sean_br...@yahoo.com wrote: On Sat, 2013-09-07 at 19:56 +0100, Mark R V Murray wrote: Ok. Right now, the mips kernel doesn't build unless I have random built in, we were using it as a module previously. I'm testing a fix, but if you want to help

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Ian Lepore
On Sat, 2013-09-07 at 22:25 +0100, Mark R V Murray wrote: On 7 Sep 2013, at 21:42, Adrian Chadd adr...@freebsd.org wrote: We discussed this at the dev summit. Mark asked what we'd like to do. Mark - would you mind terribly adding a kernel compile option that controls that blocking

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 21:42, Adrian Chadd adr...@freebsd.org wrote: We discussed this at the dev summit. Mark asked what we'd like to do. Mark - would you mind terribly adding a kernel compile option that controls that blocking default, so we can flip it on for the ARM/MIPS boards that don't

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 21:38, Ian Lepore i...@freebsd.org wrote: I keep trying to say this, and I keep getting the feeling that it just doesn't register with anyone I say it to, like I'm speaking some language from another planet or something... Sorry. I haven't forgotten this. Right now, for

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Mark R V Murray
On 7 Sep 2013, at 22:31, Ian Lepore i...@freebsd.org wrote: Those of us who have to cope with limited systems will fix our config for those systems; that part of it shouldn't be your problem beyond providing us with a knob. If there is NO random number generator, then /dev/random blocks.

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Adrian Chadd
[snip] ok. So I can work around this for these MIPS AP images by echoing something into /dev/random ? -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Glen Barber
On Sat, Sep 07, 2013 at 05:27:19PM -0700, Adrian Chadd wrote: ok. So I can work around this for these MIPS AP images by echoing something into /dev/random ? The correct workaround (which now I see I should have done before locking head/) is to revert this commit so it can be properly fixed.

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Kevin Oberman
I'm sorry. The word is spelled KLUDGE, now KNOB. It works and is better than being dead in the water, but is is still spelled KLUDGE. On Sat, Sep 7, 2013 at 5:31 PM, Glen Barber g...@freebsd.org wrote: On Sat, Sep 07, 2013 at 05:27:19PM -0700, Adrian Chadd wrote: ok. So I can work around

Re: random(4) update causes mips compile fail | mips boot fail

2013-09-07 Thread Glen Barber
On Sat, Sep 07, 2013 at 05:34:14PM -0700, Kevin Oberman wrote: On Sat, Sep 7, 2013 at 5:31 PM, Glen Barber g...@freebsd.org wrote: On Sat, Sep 07, 2013 at 05:27:19PM -0700, Adrian Chadd wrote: ok. So I can work around this for these MIPS AP images by echoing something into /dev/random