Hi Ben, thank you for your fast answer and the very professional completion of my inquiry!
Finally i found the mistake, i installed a 64bit kernel on a 32 bit OS. Best regards Masi -----Ursprüngliche Nachricht----- Von: Ben Hutchings [mailto:b...@decadent.org.uk] Gesendet: Freitag, 2. Februar 2018 17:58 An: Masi Osmani <osm...@mehrkanal.com> Cc: 889...@bugs.debian.org Betreff: Re: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889146 Control: tag -1 moreinfo On Fri, 2018-02-02 at 17:30 +0100, Ben Hutchings wrote: > On Fri, 2018-02-02 at 16:12 +0000, Masi Osmani wrote: > > Hello mr. Hutchings, > > > > i opened the bug > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889146 > > > > The bug tracker was not able to identify the responsible maintainer. > > Oh, it doesn't recognise the new binary package name because that > package is not present in the main archive, only the security archive. > I've reassigned this bug. > > > I saw in this changelog > > https://tracker.debian.org/media/packages/l/linux/changelog-3.2.96-3 > > that you commited the code for the kernel : linux (3.2.96-3) > > wheezy-security > > > > i would appreciate it if you could evaluate my problems. > > Did you build an "out-of-tree" driver for it previously? If so, it > needs to be rebuilt against the new kernel headers. I had a quick look at the source for the driver included in the kernel, and it does not appear to support 32-bit utilities working with a 64- bit kernel. I eventually found the out-of-tree version of the driver (on Broadcom's web site), and that doesn't support any kernel version beyond Linux 2.6.37. So I assume you weren't using this. Did you switch from a 32-bit to a 64-bit kernel package? Ben. -- Ben Hutchings Every program is either trivial or else contains at least one bug