Package: src:linux
Version: 3.19-1~exp1
Severity: normal
Dear Maintainer,
I have these mounts
/dev/sdd2 on /disks/stuart type btrfs
(rw,nosuid,noatime,ssd,discard,space_cache)
/home/stuart on /home/stuart type ecryptfs
checksum is invalid, remainder is 34
May 1 12:27:02 kooka kernel: : [ 45.087196]
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
May 1 12:27:02 kooka kernel: : [ 45.087209]
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
thanks again
Stuart
On 01/05/11 22:26, Thibaut Girka wrote:
Anyway, I'd be really interested to hear from Stuart Pook: his story
sounds exactly like mine.
I'm not sure exactly what to say. My screen/PC died on about 23 February. At that time it
would not even show BIOS messages. I started to try and understand
Package: linux-2.6
Version: 2.6.38-3
Severity: normal
Every 10 seconds I get the messages at the end of my bug report in
/var/log/kern.log. My /var/log/kern.log is very big! Why is the kernel
telling me what I already know every 10 seconds?
I have a Benq Product Name FP241W manufactured February
This problem seems to have been solved in the kernel 2.6.30-rc2.
When using this kernel hald starts without any problems.
Can someone indicate where I can find a howto for compiling an
official kernel using Debian? kernel-package 12.009 says in
/usr/share/doc/kernel-package/NEWS.Debian.gz we no
I didn't notice that dpkg had truncated the version of hal that I'm using.
:; dpkg -l hal | sed -ne '$s/ */ /gp'
ii hal 0.5.12~git20090406.46dc48-1 Hardware Abstraction Layer
--
If the From address bounces, please see http://www.pook.it/.
--
To UNSUBSCRIBE, email to
Hi
I have just installed linux-image-2.6.21-1-686 on my Sony Vaio
PCG-Z600LEK and it hangs during boot. The messages are
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd9ae, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter
Package: linux-image-2.6.20-1-686
Version: 2.6.20-2
Severity: normal
My Canon USB scanner has been working fine for ages but does not work
with linux-image-2.6.20-1-686. xsane detects the scanner and when asked
to scan thinks that the scanner is working however the scanner does not
react and
Libsane bug number 419197 is interesting here as scanimage does in fact
work even with 2.6.20-1-686. Perhaps the problem is in libsane but
upgrading libsane to 1.0.19~cvs20070421-1 has not corrected the problem.
% scanimage -L
device `plustek:libusb:004:003' is a Canon CanoScan
On 16/02/07 19:00, dann frazier wrote:
Can you try the latest trunk snapshot (2.6.20-based) and see if the
problem has gone away?
Hi Dann
The problem certainly seems to have gone away as my machine boots every
time now. Thanks.
I'm using linux-image-2.6.20-1-686 version
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-10
Severity: important
All the versions of linux-image-2.6.18-*-686 that I have tried normally
hang when booting on my Sony Vaio PCG-Z600LEK. Last time I had to boot
4 times before the machine booted correctly. I have to poweroff between
11 matches
Mail list logo