Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 253979 - on baselayout2 + openrc 0.4 update: ethernet modules not autoloaded and sound not working
Summary: on baselayout2 + openrc 0.4 update: ethernet modules not autoloaded and sound...
Status: VERIFIED DUPLICATE of bug 253396
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: Other documents (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Docs Team
URL: http://www.gentoo.org/doc/en/openrc-m...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-06 14:25 UTC by ray keung
Modified: 2010-03-07 20:58 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ray keung 2009-01-06 14:25:00 UTC
> hi just updated my sytem with new baselayout and openrc-0.4. i followed the nice guide. after reboot a few things were missing (no ethernet driver loaded and no sound working). i did some research online and found the following line to work for me.
> ln -s /etc/init.d/udev /etc/runlevels/sysinit
>
> everything seems normal now. thanks for the guide. i thought this information might be useful to the guide.
> by the way if you know why i get these messages on boot i would greatly appreciate it!
> * Autoloaded 0 module(s)
> *  device-mapper uses addon code which is deprecated
> *  and may not be available in the future.
> *  mdraid uses addon code which is deprecated
> *  and may not be available in the future. 

Reproducible: Didn't try

Steps to Reproduce:
1.dont update gentoo for 6 months
2.update to baselayout 2 and openrc 0.4
3.etc-update
4.reboot

Actual Results:  
received a "Operational error" message in /var/log/rc.log

Expected Results:  
normal boot messages (no error messages)

this line fixed my problems:

ln -s /etc/init.d/udev /etc/runlevels/sysinit
Comment 1 nm (RETIRED) gentoo-dev 2009-01-06 15:05:38 UTC
Adding cardoe for feedback -- are the proposed changes necessary?
Comment 2 Matthias Schwarzott gentoo-dev 2009-01-07 22:01:04 UTC
The question is: why did the update code not add udev to sysinit at openrc emerge time?

1. The code runs only on update/new install of >=openrc-0.4.0
2. udev must be already >=udev-133, there is a blocker to force this.
3. /etc/init.d/udev must exist, as udev-133 and greater install it.
4. in /etc/rc.conf or /etc/conf.d/rc there is set either of these:
* rc_devices="auto"
* rc_devices="udev"
* RC_DEVICES="auto"
* RC_DEVICES="udev"
* or nothing of these.

In all listed cases udev is added to runlevel sysinit.

If your system had udev enabled before, but openrc update did not catch, could  you check if the criterias here match your system.
Comment 3 Matthias Schwarzott gentoo-dev 2009-01-08 09:48:48 UTC

*** This bug has been marked as a duplicate of bug 253396 ***
Comment 4 ray keung 2009-01-09 06:15:47 UTC
(In reply to comment #2)
> The question is: why did the update code not add udev to sysinit at openrc
> emerge time?
> 
> 1. The code runs only on update/new install of >=openrc-0.4.0
> 2. udev must be already >=udev-133, there is a blocker to force this.
> 3. /etc/init.d/udev must exist, as udev-133 and greater install it.
> 4. in /etc/rc.conf or /etc/conf.d/rc there is set either of these:
> * rc_devices="auto"
> * rc_devices="udev"
> * RC_DEVICES="auto"
> * RC_DEVICES="udev"
> * or nothing of these.
> 
> In all listed cases udev is added to runlevel sysinit.
> 
> If your system had udev enabled before, but openrc update did not catch, could 
> you check if the criterias here match your system.
> 

1. i did a new first install of 0.4.1
2. i did upgrade to 153, and remember seeing a block on openrc until my udev was updated.
3. that file exists on my computer
4. i erased my /etc/conf.d/rc and cant tell you that.
my /etc/rc.conf file doesnt have any of those variables