|
Bugzilla – Full Text Bug Listing |
| Summary: | hwup and hwdown exit successfully if module is not found | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Martin Vidner <mvidner> |
| Component: | Basesystem | Assignee: | Christian Zoz <zoz> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <nld-qa> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 102541 | ||
|
Description
Martin Vidner
2005-09-21 11:12:53 UTC
In NLD (SLES9 and up to 9.3) hwup is also called from pci.agent. And if hwup returned there with !=0 pci.agent will proceed in looking for a matching module and will load that. So with return value == 0 we have no module loaded at boottime and with return value != 0 we might end up with a wrong module. In the second case you won't probably notice the broken hwcfg-file. So i wont fix that for older releases. Since 10.0 we don't have pci.agent anymore and hwup is always called directly. So i will fix that for upcoming releases. Christian: You might have assigned this bug by accident to samba-maintainers. Stefan Scheler (trainee) is currently working on hwup and will fix this. hwup will now return != 0 if modprobe did not succeed. |