2014-11-10 13:42 GMT-02:00 Rich Freeman :
> On Mon, Nov 10, 2014 at 10:18 AM, Francisco Ares wrote:
> >
> > So, if I understood something, I will probably have to check this
> > configuration entry every time I build a new kernel from now on, because
> > "menuconfig" will probably set this on bec
On Mon, Nov 10, 2014 at 10:18 AM, Francisco Ares wrote:
>
> So, if I understood something, I will probably have to check this
> configuration entry every time I build a new kernel from now on, because
> "menuconfig" will probably set this on because of its dependencies, is this
> correct?
>
That
2014-11-10 12:37 GMT-02:00 Rich Freeman :
> On Mon, Nov 10, 2014 at 9:20 AM, Tanstaafl
> wrote:
> > On 11/10/2014 8:21 AM, Francisco Ares wrote:
> >> Checking the news (eselect news read), I see that an upgrade to udev-217
> >> might break firmware loading, so the news tagged
> >> "2014-11-07-ud
On Mon, Nov 10, 2014 at 9:20 AM, Tanstaafl wrote:
> On 11/10/2014 8:21 AM, Francisco Ares wrote:
>> Checking the news (eselect news read), I see that an upgrade to udev-217
>> might break firmware loading, so the news tagged
>> "2014-11-07-udev-upgrade" says that a kernel >= 3.7 should be configu
On 11/10/2014 8:21 AM, Francisco Ares wrote:
> Checking the news (eselect news read), I see that an upgrade to udev-217
> might break firmware loading, so the news tagged
> "2014-11-07-udev-upgrade" says that a kernel >= 3.7 should be configured to:
>
> CONFIG_FW_LOADER_USER_HELPER=n
>
> Is it t
Hi,
Checking the news (eselect news read), I see that an upgrade to udev-217
might break firmware loading, so the news tagged "2014-11-07-udev-upgrade"
says that a kernel >= 3.7 should be configured to:
CONFIG_FW_LOADER_USER_HELPER=n
Is it that simple? Trying a new kernel build using "menuconfi
Ok, just read the new news item and the linked udev-guide wiki page, and
the only thing left that I'm unsure/concerned about now is the
persistent net rules changes...
The very last line on the wiki page says:
4. Known problems
Stale 70-persistent-net.rules (or other network rules) in
/etc/u
On Mon, Nov 19, 2012 at 09:54:15AM -0800, Mark Knecht wrote:
>
> Thanks Bruce. That at least goes a long way toward explaining why the
> system is acting the way it's acting. Threw me for a loop I must say.
>
> Interestingly I don't have the elog file you show above. (Not sure I
> should, just sa
On Mon, Nov 19, 2012 at 9:18 AM, Bruce Hill
wrote:
> On Mon, Nov 19, 2012 at 07:59:34AM -0800, Mark Knecht wrote:
>> Anyone else run into this problem with udev-171-r9? I updated
>> yesterday and my CD/DVD, which has been /dev/cdrom1 since I built the
>> machine 2 1/2 years ago, is now called /dev
On Mon, Nov 19, 2012 at 07:59:34AM -0800, Mark Knecht wrote:
> Anyone else run into this problem with udev-171-r9? I updated
> yesterday and my CD/DVD, which has been /dev/cdrom1 since I built the
> machine 2 1/2 years ago, is now called /dev/scd0.
>
> Machine is x86_64, mostly stable.
>
> - Mark
Anyone else run into this problem with udev-171-r9? I updated
yesterday and my CD/DVD, which has been /dev/cdrom1 since I built the
machine 2 1/2 years ago, is now called /dev/scd0.
Machine is x86_64, mostly stable.
- Mark
11 matches
Mail list logo
