Bug#386500: (no subject)

Hi, apt-get install --reinstall does the trick, too. Regards, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#366291: nvidia-kernel-2.6.16-1-686: same problem on linux-image-2.6.16-1-686 2.6.16-12

Package: nvidia-kernel-2.6.16-1-686 Version: 1.0.8756+1 Followup-For: Bug #366291 Hi, just as some additional info: Same problem appears on my linux-image-2.6.16-1-686 with kernel 2.6.16-12 installed: ~ # modprobe nvidia FATAL: Error inserting nvidia (/lib/modules/2.6.16-1-686/nvidia/nvidia.ko)

Bug#362296: x-ttcidfont-conf: Can't exec "/usr/X11R6/bin/mkfontdir": No such file or directory ...

Package: x-ttcidfont-conf Version: 21 Severity: grave Justification: renders package unusable Hi, after upgrading xserver-xorg to version 7.0.10 yesterday the /usr/X11R6/bin/mkfontdir doesn't exist anymore. I think this is the reason why the following error message appears: orthanc ~ # apt-get -

Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, fails to boot

> Updated today to linux-image-2.6.14-2-686 2.6.14-6 and it booted without > problems. DMA working and everything aparently back to normality. Same over here. Upgrading the Kernel without a modified /etc/yaird/Default.cfg leads to a properly running system. Even after the latest yaird update (0.

Bug#343048: linux-image-2.6.14-2-k7: happens on 2.6.14-2-k7 too

Package: linux-image-2.6.14-2-k7 Version: 2.6.14-5 Followup-For: Bug #343048 Hi, just to add some more (maybe helpful) information: I just upgraded the kernel on my AMD machine and had the same problems. Adding the modules amd74xx, ide-generic and ide-disk to the /etc/yaird/Default.cfg and rebui

Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools (but piix not loaded)

> > > Yes, I added it to the title after finding out :). Michael Setzer > > > wrote, that adding > > > MODULE ide-generic > > > MODULE ide-disk > > > to /etc/yaird/Default.cfg makes it work. I could boot with that, but > > > DMA was disa

Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools

> hdparm /dev/hda > > /dev/hda: > setting using_dma to 1 (on) > HDIO_SET_DMA failed: Operation not permitted > using_dma= 0 (off) > ## > > Any ideas? Saw that already yesterday. Seems to be an issue with the linux-image-2-6-14-2-686 (2.6.14-5). Regards, Michael -- To UNSUBSCRIBE, emai

Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools

Package: linux-image-2.6.14-2-686 Version: 2.6.14-5 Followup-For: Bug #343048 Hi, after being knocked down with the same problem which left my system in an unbootable state I wondered if it wasn't possible to bring the system back to life without removing yaird. This is what I simply did: - boot

Bug#327963: (no subject)

> This problem is actually caused by a problem with libfwbuilder > 2.0.7-4 which is already corrected in 2.0.7-5 which was uploaded last > night as part of the fix for Bug#331575. Yepp, it works. Great. Thank you! Regards, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subjec

Bug#327963: (no subject)

Hi, I just installed the Debian unstable packages: ii fwbuilder 2.0.7-2Firewall administration tool GUI ii fwbuilder-common 2.0.7-2Firewall administration tool GUI (common fil ii fwbuilder-linux 2.0.7-2

Bug#310678: AW: Bug#310678 acknowledged by developer

> Also, did you rebuild your initrd after upgrading ? That's what I forgot. Sorry! After rebuilding the initrd the system works perfect again. Thanks for your help! Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310678: AW: Bug#310678 acknowledged by developer (Bug#310479: fixed in lvm-common 1.5.19)

prüngliche Nachricht- Von: Debian BTS [mailto:[EMAIL PROTECTED] Im Auftrag von Debian Bug Tracking System Gesendet: Mittwoch, 25. Mai 2005 13:03 An: Michael Setzer Betreff: Bug#310678 acknowledged by developer (Bug#310479: fixed in lvm-common 1.5.19) This is an automatic notification regardin

Bug#310678: AW: Bug#310678 acknowledged by developer (Bug#310479: fixed in lvm-common 1.5.19)

prüngliche Nachricht- Von: Debian BTS [mailto:[EMAIL PROTECTED] Im Auftrag von Debian Bug Tracking System Gesendet: Mittwoch, 25. Mai 2005 13:03 An: Michael Setzer Betreff: Bug#310678 acknowledged by developer (Bug#310479: fixed in lvm-common 1.5.19) This is an automatic notification regardin

Bug#310678: latest kernel-image-2.6.8-2-686 left system in unbootable state

Package: kernel-image-2.6.8-2-686 Version: 2.6.8-16 Severity: critical Justification: cannot boot anymore After upgrading my Sid with root on LVM with the latest kernel-image this morning I cannot boot anymore. It gives me messages on the boot console like [...] device-mapper: 4.1.0-ioctl (2003-1

Bug#303148:

Just found out that ejecting and re-inserting the pcmcia-card brings the interface up, too. But not when booting the system. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#303148:

Hmm, even after upgrading ifupdown to 0.6.6 ist still doesn't want to start my hotplug interface eth0 automagically - it is visible in `ifconfig -a` but the dhcp-client doesn't want to start. Only a `ifup eth0` brings up the interface. Regards, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTEC

Bug#303148: hotplugged eth0 won't start anymore

I would like to add some more information that might be helpful: After installing the latest unstable ifupdown 0.6.5 this morning my hotplugged devices won't start at boot time anymore. Even though it is possible to start the interface from the console: orthanc ~ # ifup -vvv eth0=hotplug Running