|
Bugzilla – Full Text Bug Listing |
| Summary: | init=/sbin/sysvinit on cmdline solves kbd service startup failure when using systemd init | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Felix Miata <mrmazda> |
| Component: | Basesystem | Assignee: | Stanislav Brabec <sbrabec> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | fcrozat, freek, gp, jengelh, werner |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /var/log/boot.msg | ||
not related to systemd, we don't touch kbd service (we just ignore it when booting under systemd). /suse/werner> maintainer kbd bugowner of Base:System/kbd -- sbrabec@suse.com ... fixed in sr#87235 This is an autogenerated message for OBS integration: This bug (720486) was mentioned in https://build.opensuse.org/request/show/87235 Factory / kbd *** Bug 721441 has been marked as a duplicate of this bug. *** *** Bug 723069 has been marked as a duplicate of this bug. *** If this fix is on the mirrors I just dup'd from, then there seems to be something wrong with the fix. Now init pauses for several minutes after displaying r8169 0000:03:00.0: eth0: link up, displays a few more messages, clears the screen, displays a few more messages (e.g. "Unknown operation ntptimeset"), and when init actually finishes, /etc/sysconfig/keyboard's KBD_NUMLOCK="yes" setting has been ignored on all VCs, even though no kbd errors seem to have been displayed during init. Without sysvinit-init installed or init=/sbin/sysvinit on cmdline, /etc/sysconfig/keyboard remains ignored in fresh update to whatever flavor was in 12.1 on the mirrors last night. I don't understand what you are saying. do you mean with systemd ? /etc/init.d/kbd is not used at all under systemd, but /etc/sysconfig/kbd is. For KBD_NUMLOCK, it is not supported under systemd. I have no idea how the settings in /etc/sysconfig/keyboard get implemented, nor what /etc/init.d/kbd does or not. All I know is /etc/sysconfig/keyboard is where I've been going to get desired keyboard behavior since first using *S?SE. It's one not inconsequential reason why I selected SuSE as my first choice distro in the first place, and why I only dabble with other distros. As long as NUM, delay & repeat can't automatically be restored to their BIOS states using systemd, then systemd is not compatible with me. If it was up to me, it would be impossible for any keyboard with both a complete set of cursor keys and a complete/separate num pad to _ever_ have NUM in an off state. Why is this bug marked FIXED? this bug is marked fixed, because now, kbd is correctly starting on sysvinit. you are complaining about another diffrerent issue. Feel free to open a bug, better against the kernel which should be able to restore properly BIOS value at startup. |
Created attachment 453116 [details] /var/log/boot.msg To reproduce: 1-install M2 or prior with systemd not installed 2-zypper al systemd 3-do zypper dup on daily or weekly basis until approximately M5 is on mirrors 4-zypper rl systemd 5-include init=/sbin/init on cmdlines of Grub stanza(s) 6-upgrade with zypper dup 7-boot Actual results: 1-Loading console font...failed 2-Loading compose table...failed 3-Failed services in runlevel 3: kbd Expected results: 1-no failed services reports 2-keyboard configured as specified in /etc/sysconfig/keyboard I had all my several systems setup to exclude systemd until about a week ago. Since, I've removed systemd locks and set init=/sbin/init on two of them, one a week ago, another today, and this has happened to both.