Bug#484824: initramfs-tools: seems not to build usable initrd, even with MODULES=most in initramfs.conf boot fails (xfs)

severity 484824 normal tags 484824 moreinfo thanks Please include your bug explanation in the body of your message, not just in the subject. On Fri, Jun 06, 2008 at 06:56:08PM +0200, Nikolai Försterling wrote: > Package: initramfs-tools > Version: 0.92a > Severity: critical > Justification: break

Processed: Re: Bug#484824: initramfs-tools: seems not to build usable initrd, even with MODULES=most in initramfs.conf boot fails (xfs)

Processing commands for [EMAIL PROTECTED]: > severity 484824 normal Bug#484824: initramfs-tools: seems not to build usable initrd, even with MODULES=most in initramfs.conf boot fails (xfs) Severity set to `normal' from `critical' > tags 484824 moreinfo Bug#484824: initramfs-tools: seems not to b

Bug#477233: same kernel: sound broke after upgrade to lenny - was ok with Etch!

Hi, I have a (similar/related?) problem. On a Compaq Presario 2700 laptop I was running Etch with 2.6.24 Kernel from Lenny, and had no problem. Then I decided to upgrade to Lenny... and though everything seemed ok (alsa modules loaded, all volumes ok in alsamixer, etc), sound was gone. I could

Bug#484824: initramfs-tools: seems not to build usable initrd, even with MODULES=most in initramfs.conf boot fails (xfs)

Package: initramfs-tools Version: 0.92a Severity: critical Justification: breaks the whole system -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=2.6.25 root=30b splash=verbose -- /proc/filesystems xfs fuseblk -- lsmod Module Size Used by sd_mod

Bug#411499: Further Information on bug 411499

Hi, I'd like to add some additional information on this topic because I have encountered similar problems with my Mustek MFS-6000CX and an Adaptec SCSI ISA controller AHA1542CF. System is a PIII/700 with debian 4.0; 'uname -a' gives this output: 'Linux bulk 2.6.18-5-686 #1 SMP Mon Dec 24 16:41:

Bug#484782: closed by maximilian attems <[EMAIL PROTECTED]> (Re: Bug#484782: PCI: Cannot allocate resource region)

On Fri, Jun 06, 2008 at 03:42:57PM +0300, Nadav Kavalerchik wrote: > obviously :-) it is not a debian bug but a linux/kernel bug. > but, shouldn't i send kernel bugs to debian BTS in the future ? > and go directly upstream ? "bugs" aka feature request are indeed better posted upstream and also dir

Bug#484782: closed by maximilian attems <[EMAIL PROTECTED]> (Re: Bug#484782: PCI: Cannot allocate resource region)

obviously :-) it is not a debian bug but a linux/kernel bug. but, shouldn't i send kernel bugs to debian BTS in the future ? and go directly upstream ? is there a way to turn ALL kernel boot messages off ? (now that i know the system is working fine) thanks :-) 2008/6/6, Debian Bug Tracking Syst

Bug#484783: marked as done (vesafb.ko missing)

Your message dated Fri, 6 Jun 2008 14:27:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#484783: vesafb.ko missing has caused the Debian Bug report #484783, regarding vesafb.ko missing to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#484783: vesafb.ko missing

Package: linux-image-2.6.18-6-686 Architecture: i386 Version: 2.6.18.dfsg.1-18etch5 The module vesafb.ko is missing. I need it because intelfb is not worling on my notebook, see #426714. Regards Olaf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Con

Bug#484782: marked as done (PCI: Cannot allocate resource region)

Your message dated Fri, 6 Jun 2008 14:05:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#484782: PCI: Cannot allocate resource region has caused the Debian Bug report #484782, regarding PCI: Cannot allocate resource region to be marked as done. This means that you claim that

Bug#484782: PCI: Cannot allocate resource region

Package: kernel Severity: minor *** Please type your report below this line *** i am getting these messages: PCI: Cannot allocate resource region 8 of bridge :00:01.0 [0.192500] PCI: Cannot allocate resource region 9 of bridge :00:01.0 [0.192546] PCI: Cannot allocate resource regio

Bug#484779: linux-image-2.6.25-2-amd64: enable access to acpi battery/ac info via (deprecated) /proc files

Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-4 Severity: normal Please, reintroduce (now deprecated) option CONFIG_ACPI_PROCFS_POWER=y as many userspace utilities depends on /proc/acpi/* api, and move to the sys power interface take some time. So please, enable both /proc and /sys interfac

Bug#484467: (no subject)

reassign 484467 cpufreqd severity 484467 serious retitle 484467 query power status in /sys not in /proc stop On Fri, Jun 06, 2008 at 08:11:16AM +0200, LÉVAI Dániel wrote: > It reboots because there is a rule in /etc/cpufreqd.conf which halts the > system when it detects a 0-1% battery charge. c

Processed: Re: Bug#484467: (no subject)

Processing commands for [EMAIL PROTECTED]: > reassign 484467 cpufreqd Bug#484467: [linux-image-2.6.25-2-amd64] system shuts down right after the boot process Bug reassigned from package `linux-image-2.6.25-2-amd64' to `cpufreqd'. > severity 484467 serious Bug#484467: [linux-image-2.6.25-2-amd64