Bug#633024: Same Problem

2014-02-12 Thread Zachary Palmer
I am also experiencing this bug. My system is configured thus: /dev/sd{a,b,c,d}{1,2} are partitions for devices /dev/md1{0,1} are the MD devices for the boot and root, respectively /dev/md10p1 is the PV for the VG vgboot /dev/md11p1 is the PV for the VG vg0 /dev/vgboot/boot

Bug#616689: jessie still not working

2014-02-12 Thread Wido
I just installed a fresh Jessie from mini daily (the image was created on 2/12 which is the latest available). this lvm issue remains, lvm2 package was intalled when I built this machine, so that fix did not work. I was able to get to the system running 'vgchange -ay', but I would appreciate if t

Re: Wheezy (3.6.11+, Raspbeery Pi), no rc-core (lirc) support?

2014-02-12 Thread Ben Hutchings
On Wed, 2014-02-12 at 21:25 +0100, Uwe Kleine-König wrote: > On Wed, Feb 12, 2014 at 07:51:18PM +, Paul Smith wrote: > > Can someone confirm that the wheezy distribution for the raspberry Pi does > > not contain the latest incantation of LIRC i.e. the IR support based on the > > rc-core code

Re: Wheezy (3.6.11+, Raspbeery Pi), no rc-core (lirc) support?

2014-02-12 Thread Uwe Kleine-König
On Wed, Feb 12, 2014 at 07:51:18PM +, Paul Smith wrote: > Can someone confirm that the wheezy distribution for the raspberry Pi does > not contain the latest incantation of LIRC i.e. the IR support based on the > rc-core code found in drivers/media/rc? > > I want to write a driver for a Rasp

Wheezy (3.6.11+, Raspbeery Pi), no rc-core (lirc) support?

2014-02-12 Thread Paul Smith
Can someone confirm that the wheezy distribution for the raspberry Pi does not contain the latest incantation of LIRC i.e. the IR support based on the rc-core code found in drivers/media/rc? I want to write a driver for a Raspberry Pi blaster (IR transmitter) and was going to start from the rc-

Bug#738758: linux-image-3.12-1-amd64: ext4 can't properly handle ext2 filesystems created for GNU/Hurd

2014-02-12 Thread Gabriele Giacone
Package: src:linux Version: 3.12.9-1 Severity: normal Since CONFIG_EXT4_USE_FOR_EXT23 has been enabled, ext4 module can't properly handle ext2 created for Hurd causing data corruption. ext2 module would do its job. Reproducible with: dd if=/dev/zero of=test.fs count=1 echo y|mkfs.ext2 -o hur

Processed: Re: Bug#738707: linux-image-3.12-1-amd64: Failed to symbolic-link /boot/initrd.img-3.12-1-amd64 to initrd.img.

2014-02-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #738707 [src:linux] linux-image-3.12-1-amd64: Failed to symbolic-link /boot/initrd.img-3.12-1-amd64 to initrd.img. Added tag(s) moreinfo. -- 738707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738707 Debian Bug Tracking System Contact ow..

Bug#738707: linux-image-3.12-1-amd64: Failed to symbolic-link /boot/initrd.img-3.12-1-amd64 to initrd.img.

2014-02-12 Thread Ben Hutchings
Control: tag -1 moreinfo On Wed, 2014-02-12 at 10:01 +0100, Ph. Marek wrote: > Package: src:linux > Version: 3.12.9-1 > Severity: normal > > I had the wrong /boot mounted. > After reboot I noticed that, got the correct filesystem on there, and did > "apt- > get install --reinstall" - but that st

Bug#738707: linux-image-3.12-1-amd64: Failed to symbolic-link /boot/initrd.img-3.12-1-amd64 to initrd.img.

2014-02-12 Thread Ph. Marek
Package: src:linux Version: 3.12.9-1 Severity: normal I had the wrong /boot mounted. After reboot I noticed that, got the correct filesystem on there, and did "apt- get install --reinstall" - but that stopped with the error message above. strace showed this: [pid 8236] 09:56:54.538994 symlin