Bug#779546: Further information

2015-04-17 Thread Ben Hutchings
On Fri, 2015-04-17 at 19:29 +0200, Cyril Brulebois wrote: > Cyril Brulebois (2015-03-04): > > Ben Hutchings (2015-03-03): > > > Yes, that's right. The problem is that we now detect missing firmware > > > by scraping the kernel log, and we still pick up old ones after > > > installing firmware an

Bug#779546: Further information

2015-04-17 Thread Cyril Brulebois
Cyril Brulebois (2015-03-04): > Ben Hutchings (2015-03-03): > > Yes, that's right. The problem is that we now detect missing firmware > > by scraping the kernel log, and we still pick up old ones after > > installing firmware and poking the driver. > > > > I think we could solve this by noting

Bug#779546: Further information

2015-03-03 Thread Cyril Brulebois
Ben Hutchings (2015-03-03): > Yes, that's right. The problem is that we now detect missing firmware > by scraping the kernel log, and we still pick up old ones after > installing firmware and poking the driver. > > I think we could solve this by noting the timestamp at the bottom of the > kernel

Bug#779546: Further information

2015-03-03 Thread Ben Hutchings
On Tue, 2015-03-03 at 19:52 +0100, Jon Jahren wrote: > After trying to install the system again to see if I could replicate it the > issue, I made a usb key where the firmware-iwlwifi package contained only the > 1000-5.ucode file. Initially the interface > asks about 1000-5.ucode, however when

Bug#779546: Further information

2015-03-03 Thread Jon Jahren
After trying to install the system again to see if I could replicate it the issue, I made a usb key where the firmware-iwlwifi package contained only the 1000-5.ucode file. Initially the interface asks about 1000-5.ucode, however when I try to load the non-free firmware it seems like the driver