[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#219897: hw-detect: destroys debconf/priority up if run after a failed module

Steinar H. Gunderson wrote:
> If one first runs a module that fails (for instance, install LILO on a
> non-existant drive, or install base from network with cable unplugged)
> and then run hw-detect, weird stuff happens:

Can you provide an easier way to reproduce this? hw-detect here does
skip loading a few modules that are not present, but that's the closest
it comes to failing, and I'm pretty sure I've never seen the priority
bumped up to super-critical.

I don't understand how the unplugged network cable is interacting with
hw-detect at all, really.

see shy jo

Attachment: signature.asc
Description: Digital signature

Reply to: