Your message dated Sat, 16 Mar 2013 05:00:33 +0000 with message-id <1363410033.3937.182.camel@deadeye.wl.decadent.org.uk> and subject line Re: Bug#703142: Kernel image 3.2.39-2: i915 module will not load. has caused the Debian Bug report #703142, regarding Kernel image 3.2.39-2: i915 module will not load. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 703142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703142 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Kernel image 3.2.39-2: i915 module will not load.
- From: Robert Frazier <robert.frazier@chch.ox.ac.uk>
- Date: Sat, 16 Mar 2013 03:33:11 +0000
- Message-id: <[🔎] 5143E7F7.80308@chch.ox.ac.uk>
- Reply-to: robert.frazier@chch.ox.ac.uk
Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 I'm using a reasonably vanilla "testing" distribution.The i915 module would not load, either at boot or using "modprobe -a i915". The error message on the command line is as follows.FATAL: Error inserting i915 (....): Invalid argument In dmesg it is as follows. [ 3.227711] i915: disagrees about version of symbol i2c_bit_algo [ 3.227766] i915: Unknown symbol i2c_bit_algo (err -22)Consequently, the xorg intel driver (for intel i3 2100, with HD 2000 graphics) wasn't loaded, and X11 fell back to VESA. I reverted to an earlier kernel/modules set and things work fine. Reverting was somewhat of a chore as when the new kernel/modules set was installed it completely replaced the earlier one. I would rather that it had not.Best wishes, Bob -- Robert L. Frazier email: robert.frazier@chch.ox.ac.uk Christ Church Oxford OX1 1DP www: http://kant1.chch.ox.ac.uk UK
--- End Message ---
--- Begin Message ---
- To: 703142-done@bugs.debian.org
- Subject: Re: Bug#703142: Kernel image 3.2.39-2: i915 module will not load.
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Sat, 16 Mar 2013 05:00:33 +0000
- Message-id: <1363410033.3937.182.camel@deadeye.wl.decadent.org.uk>
- In-reply-to: <[🔎] 5143E7F7.80308@chch.ox.ac.uk>
- References: <[🔎] 5143E7F7.80308@chch.ox.ac.uk>
On Sat, 2013-03-16 at 03:33 +0000, Robert Frazier wrote: > Package: linux-image-3.2.0-4-amd64 > Version: 3.2.39-2 > > I'm using a reasonably vanilla "testing" distribution. > > The i915 module would not load, either at boot or using "modprobe -a > i915". The error message on the command line is as follows. > > FATAL: Error inserting i915 (....): Invalid argument > > In dmesg it is as follows. > > [ 3.227711] i915: disagrees about version of symbol i2c_bit_algo > [ 3.227766] i915: Unknown symbol i2c_bit_algo (err -22) > > Consequently, the xorg intel driver (for intel i3 2100, with HD 2000 > graphics) wasn't loaded, and X11 fell back to VESA. I reverted to an > earlier kernel/modules set and things work fine. Reverting was somewhat > of a chore as when the new kernel/modules set was installed it > completely replaced the earlier one. I would rather that it had not. This is not a kernel bug - it indicates that modprobe didn't load all of i915's dependencies first (specifically i2c-algo-bit). Since this works for everyone else, I suspect that modprobe's dependency information got corrupted somehow. But all the evidence of that has almost certainly been wiped out when you reinstalled the old package. So there's nothing useful I can do here. Upgrade again and I bet the package will work fine. If not, reopen this bug and attach /lib/modules/3.2.0-4-amd64/modules.*. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---