Re: Bug#341738: linux-image-2.6.14-2-686: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)
Erik van Konijnenburg <[EMAIL PROTECTED]> writes:
| On Fri, Dec 02, 2005 at 06:36:41PM +0200, Jari Aalto wrote:
|
| > Setting up linux-image-2.6.14-2-686 (2.6.14-4) ...
| > Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
| > Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd
/usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.
| > yaird error: Could not read output for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 auto (fatal)
|
| Could you post the output of yaird -d -o /tmp/junk.img 2.6.14-2-686?
| and dpkg -l yaird?
Sure. Thanks for looking into this.
Jari
---
[EMAIL PROTECTED]:~# dpkg -l yaird
[EMAIL PROTECTED]:~# dpkg -l yaird
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii yaird 0.0.11-12 Yet Another mkInitRD
---
[EMAIL PROTECTED]:~# yaird -d -o /tmp/junk.img 2.6.14-2-686
yaird: goal: template, prologue (/usr/lib/yaird/conf/Default.cfg:52)
yaird: action: prologue, {}
yaird: goal: module, fbcon (/usr/lib/yaird/conf/Default.cfg:56)
yaird: goal: input, -- (/usr/lib/yaird/conf/Default.cfg:73)
yaird:D: addInput: consider AT Translated Set 2 keyboard is
isa0060/serio0/input0 at platform/i8042/serio4 [event0,kbd] [LED,KEY,EV,MSC]
(KBD)
yaird:D: addOneModule: modprobe psmouse
yaird:D: runCmd - doing /sbin/modprobe -v -n --show-depends --set-version
2.6.14-2-686 psmouse
yaird:D: runCmd - result '1' for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 psmouse
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/input/mouse/psmouse.ko {optionList=-- }
yaird: hardware: completed platform/i8042/serio4
yaird:D: addInput: consider Logitech Optical USB Mouse is
usb-:00:07.2-1/input0 at pci:00/:00:07.2/usb1/1-1/1-1:1.0
[event1,mouse0,ts0] [KEY,REL,EV]
yaird:D: addInput: skipping
yaird:D: addInput: consider PC Speaker is isa0061/input0 at -- [event2,kbd]
[EV,SND]
yaird:D: addInput: skipping
yaird:D: addInput: consider PS/2 Generic Mouse is isa0060/serio4/input0 at
platform/i8042/serio3 [ts1,mouse1,event3] [KEY,REL,EV]
yaird:D: addInput: skipping
yaird:D: addInput: end
yaird: goal: module, mousedev (/usr/lib/yaird/conf/Default.cfg:103)
yaird:D: addOneModule: modprobe mousedev
yaird:D: runCmd - doing /sbin/modprobe -v -n --show-depends --set-version
2.6.14-2-686 mousedev
yaird:D: runCmd - result '1' for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 mousedev
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/usr/lib/yaird/conf/Default.cfg:104)
yaird:D: addOneModule: modprobe evdev
yaird:D: runCmd - doing /sbin/modprobe -v -n --show-depends --set-version
2.6.14-2-686 evdev
yaird:D: runCmd - result '1' for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 evdev
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko
{optionList=-- }
yaird: goal: mountdir, / (/usr/lib/yaird/conf/Default.cfg:143)
yaird:D: addOneModule: modprobe piix
yaird:D: runCmd - doing /sbin/modprobe -v -n --show-depends --set-version
2.6.14-2-686 piix
yaird:D: runCmd - result '1' for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 piix
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko
{optionList=-- }
yaird:D: addOneModule: modprobe generic
yaird:D: runCmd - doing /sbin/modprobe -v -n --show-depends --set-version
2.6.14-2-686 generic
yaird:D: runCmd - result '1' for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 generic
yaird:D: redundant action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko {optionList=-- }
yaird:D: addOneModule: modprobe ide-generic
yaird:D: runCmd - doing /sbin/modprobe -v -n --show-depends --set-version
2.6.14-2-686 ide-generic
yaird:D: runCmd - result '1' for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 ide-generic
yaird:D: redundant action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-generic.ko {optionList=-- }
yaird:D: addOneModule: modprobe ide-disk
yaird:D: runCmd - doing /sbin/modprobe -v -n --show-depends --set-version
2.6.14-2-686 ide-disk
yaird:D: runCmd - result '1' for /sbin/modprobe -v -n --show-depends
--set-version 2.6.14-2-686 ide-disk
yaird:D: redundant action: insmod,
/lib/modules/2.6.14-2-686/k
Bug#341801: skge hardware error; hangs w/ hardware memory hole
Package: linux-image-2.6.14-2-amd64-k8-smp Version: 2.6.14-4 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a Asus A8V with 4GB of RAM. When I turn on the hardware memory hole in the BIOS, the skge driver prints out this message: skge hardware error detected (status 0xc00) and then does not work. Setting debug=16 doesn't really show anything. Also, sometimes it causes the kernel to panic (noticed during a raid rebuild; a sata error followed a second later by one or more panics) with messages which scroll by way to fast to catch, and shift-pagup doesn't work. I'm pretty sure this is related to the skge thing; it doesn't happen until ifup eth0. - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (130, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-amd64-k8-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.14-2-amd64-k8-smp depends on: ii e2fsprogs 1.38-2 ext2 file system utilities and lib ii module-init-tools 3.2-pre9-4 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.11-12 Yet Another mkInitRD linux-image-2.6.14-2-amd64-k8-smp recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDkTyg+z+IwlXqWf4RAiDKAJ9MYeynSJRo9S0HUDT9PaCVTbXAxwCeKAS1 ws4mEpX9W4DULqYhuMfhxNY= =Gnji -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341800: VIA 82xx Audio: probe of 0000:00:11.5 failed with error -12
Package: linux-image-2.6.14-2-amd64-k8-smp Version: 2.6.14-4 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Under 2.6.12-1-amd64-k8-smp my via82xx sound works fine (on-board sound on Asus A8V). Under 2.6.14, I get: kernel: cannot find the slot for index 0 (range 0-0) kernel: VIA 82xx Audio: probe of :00:11.5 failed with error -12 Under 2.6.12, I think these are the kernel messages from it loading: kernel: ACPI: PCI Interrupt :00:11.5[C] -> GSI 22 (level, low) -> IRQ 22 kernel: PCI: Via IRQ fixup for :00:11.5, from 5 to 6 kernel: PCI: Setting latency timer of device :00:11.5 to 64 - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (130, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-amd64-k8-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.14-2-amd64-k8-smp depends on: ii e2fsprogs 1.38-2 ext2 file system utilities and lib ii module-init-tools 3.2-pre9-4 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.11-12 Yet Another mkInitRD linux-image-2.6.14-2-amd64-k8-smp recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDkTuf+z+IwlXqWf4RAhpoAJ40wF1pIgywVs5KA+CGDRgf3jirzgCeNTcG a0TfUScghiiWeS477uzRmqk= =FqLU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: kernel
Processing commands for [EMAIL PROTECTED]: > reassign 341800 linux-2.6 Bug#341800: VIA 82xx Audio: probe of :00:11.5 failed with error -12 Warning: Unknown package 'linux-image-2.6.14-2-amd64-k8-smp' Bug reassigned from package `linux-image-2.6.14-2-amd64-k8-smp' to `linux-2.6'. > reassign 341801 linux-2.6 Bug#341801: skge hardware error; hangs w/ hardware memory hole Warning: Unknown package 'linux-image-2.6.14-2-amd64-k8-smp' Bug reassigned from package `linux-image-2.6.14-2-amd64-k8-smp' to `linux-2.6'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#341744: usbutils: mounting usb key problems in AMD64 unstable
reassign 341744 linux-2.6 thanks Please do not blindly reassing bugs to udev, it's quite obvious that this is either a broken media or a kernel bug: /dev/scsi/host7/bus0/target0/lun0:<3>ldm_parse_privhead(): Cannot find PRIVHEAD structure. LDM database is corrupt. Aborting. ldm_validate_privheads(): Cannot find PRIVHEAD 1. unable to read partition table Linux fast 2.6.12-1-amd64-k8 #1 Wed Sep 28 02:31:26 CEST 2005 x86_64 GNU/Linux -- ciao, Marco signature.asc Description: Digital signature
Processed: Re: Bug#341744: usbutils: mounting usb key problems in AMD64 unstable
Processing commands for [EMAIL PROTECTED]: > reassign 341744 linux-2.6 Bug#341744: usbutils: mounting usb key problems in AMD64 unstable Bug reassigned from package `udev' to `linux-2.6'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Graphical installer - invitation to get involved
On Sun, Dec 04, 2005 at 12:07:06AM +1100, Julien Goodwin wrote: > These are my notes/ideas after having done a test installation using the > graphical d-i beta. (Under a VMware install using ftp.us.debian.org as > the mirror) > > I'm not subscribed to the list so please cc me on anything you'd like my > comment on. I'm happy to test any betas etc to see how things may have > improved. > > As it stands it seems to only be a graphical frontend to debconf, given > some of the decisions taken this causes it to be less usable then the > console version. > > Graphical D-I boot notes: > > 1. Can you use ubuntu's bootsplash or something to hide/pretty up kernel > messages. Well, we would need to have the bootsplash thingy patch included in the debian kernel, and this with current policies means it should be ready to be submitted upstream. I think it would be nice though, but needs discussing with the kernel team, CCing there. > 4. Would be nice to have a download speed monitor at the bottom of the > screen for those with slow connections, also a calculated ETA. Yeah. > 5. A graphical partitioner is probably the biggest missing peice, I > didn't really test how the partitioner came through, just did a "wipe > entire disk" and it was still a pain. Xavier Oswald is working on first doing a gparted .udeb, which will allow to fall back to a graphical partitioner instead of plain old parted, and then modifying it to be able to serve-as/replace partman, at least in its gross functionality, there is still work to be done there though. > 6. Pages with just one checkbox (eg the "write changes to disk" page > should probably have just "Yes/No" buttons instead of the checkbox and > go back/continue buttons (also install grub to mbr) Yes, this is a big usability issue, i believe, and also increase the chance of an accidental erasal of unwanted partitions. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Graphical installer - invitation to get involved
Sven Luther <[EMAIL PROTECTED]> writes: > On Sun, Dec 04, 2005 at 12:07:06AM +1100, Julien Goodwin wrote: >> These are my notes/ideas after having done a test installation using the >> graphical d-i beta. (Under a VMware install using ftp.us.debian.org as >> the mirror) >> >> I'm not subscribed to the list so please cc me on anything you'd like my >> comment on. I'm happy to test any betas etc to see how things may have >> improved. >> >> As it stands it seems to only be a graphical frontend to debconf, given >> some of the decisions taken this causes it to be less usable then the >> console version. >> >> Graphical D-I boot notes: >> >> 1. Can you use ubuntu's bootsplash or something to hide/pretty up kernel >> messages. > > Well, we would need to have the bootsplash thingy patch included in the debian > kernel, and this with current policies means it should be ready to be > submitted upstream. I think it would be nice though, but needs discussing with > the kernel team, CCing there. No. Current uplash is in userspace. I work on Splashy that's another alternative and it works well. We'll probably move it from experimental to sid soon. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Graphical installer - invitation to get involved
On Sat, Dec 03, 2005 at 12:05:25PM -0200, Otavio Salvador wrote: > Sven Luther <[EMAIL PROTECTED]> writes: > > Well, we would need to have the bootsplash thingy patch included in the > > debian > > kernel, and this with current policies means it should be ready to be > > submitted upstream. I think it would be nice though, but needs discussing > > with > > the kernel team, CCing there. > > No. Current uplash is in userspace. > > I work on Splashy that's another alternative and it works well. We'll > probably move it from experimental to sid soon. Oh, then it was the x86/vesa only thingy ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Graphical installer - invitation to get involved
Sven Luther <[EMAIL PROTECTED]> writes: > On Sat, Dec 03, 2005 at 12:05:25PM -0200, Otavio Salvador wrote: >> Sven Luther <[EMAIL PROTECTED]> writes: >> > Well, we would need to have the bootsplash thingy patch included in the >> > debian >> > kernel, and this with current policies means it should be ready to be >> > submitted upstream. I think it would be nice though, but needs discussing >> > with >> > the kernel team, CCing there. >> >> No. Current uplash is in userspace. >> >> I work on Splashy that's another alternative and it works well. We'll >> probably move it from experimental to sid soon. > > Oh, then it was the x86/vesa only thingy ? I don't know about usplash but Splashy works fine in PPC in major of cases. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#341738: linux-image-2.6.14-2-686: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)
On Sat, Dec 03, 2005 at 10:18:53AM +0200, Jari Aalto wrote: > Erik van Konijnenburg <[EMAIL PROTECTED]> writes: > | On Fri, Dec 02, 2005 at 06:36:41PM +0200, Jari Aalto wrote: > | > Setting up linux-image-2.6.14-2-686 (2.6.14-4) ... > | > Using /usr/sbin/mkinitrd.yaird to build the ramdisk. > | > Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd > /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. > | > yaird error: Could not read output for /sbin/modprobe -v -n > --show-depends --set-version 2.6.14-2-686 auto (fatal) > | > | Could you post the output of yaird -d -o /tmp/junk.img 2.6.14-2-686? > | and dpkg -l yaird? > ii yaird 0.0.11-12 Yet Another mkInitRD OK, that's the most recent. > [EMAIL PROTECTED]:~# yaird -d -o /tmp/junk.img 2.6.14-2-686 Output that follows looks correct: it seems you have fstype 'auto' in your /etc/fstab entry for root, and yaird determines that the filesystem is reisrfs. Versions prior to 0.0.11-12 had the problem you show in parsing auto in fstab. That suggests the problem is in how yaird is invoked. Perhaps the kernel install script invokes a broken copy of yaird? Things to check: -- debsums -a yaird if it says a anything other than ok ok ok, reinstall yaird. -- hack /usr/sbin/mkinitrd.yaird to echo the yaird command line and its own arguments to some scratch file, then do dpkg-reconfigure linux-image-2.6.14-2-686 and see if there's a difference from the yaird call you did just now. Or, if getting the new kernel running is more interesting to you than finding out the cause, replace the 'auto' keyword in your fstab with the appropriate file system type. Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Graphical installer - invitation to get involved
On Sat, Dec 03, 2005 at 03:26:30PM +0100, Sven Luther wrote: > On Sat, Dec 03, 2005 at 12:05:25PM -0200, Otavio Salvador wrote: > > No. Current uplash is in userspace. > > > > I work on Splashy that's another alternative and it works well. We'll > > probably move it from experimental to sid soon. > > Oh, then it was the x86/vesa only thingy ? usplash works fine on x86/vga16fb, x86/vesafb, and powerpc/offb at least. It just uses bogl (like d-i) so it should be straightforward to port nearly anywhere. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Graphical installer - invitation to get involved
On Saturday 03 December 2005 18:18, Colin Watson wrote: > usplash works fine on x86/vga16fb, x86/vesafb, and powerpc/offb at > least. It just uses bogl (like d-i) so it should be straightforward to > port nearly anywhere. What happens on sercon installations? pgpGJjcoEh2vp.pgp Description: PGP signature
Re: Graphical installer - invitation to get involved
Colin Watson wrote: On Sat, Dec 03, 2005 at 03:26:30PM +0100, Sven Luther wrote: On Sat, Dec 03, 2005 at 12:05:25PM -0200, Otavio Salvador wrote: No. Current uplash is in userspace. I work on Splashy that's another alternative and it works well. We'll probably move it from experimental to sid soon. Oh, then it was the x86/vesa only thingy ? usplash works fine on x86/vga16fb, x86/vesafb, and powerpc/offb at least. It just uses bogl (like d-i) so it should be straightforward to port nearly anywhere. i am just an outsider, but ... splashy was made by debian users, for debian. It uses simple techlogy and their effort was to be as light as it could be to be included in debian installer. I know that it must have qualities ... i think it has. So ... Why don't the d-i team contact them and include splashy? just my thoughts Best regards Luis Matos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341273: Doesn't understand install and remove directives in modprobe.conf
On Tue, Nov 29, 2005 at 01:57:32PM -0500, Norbert Veber wrote: > yaird error: modprobe psmouse requires install /sbin/modprobe mousedev > && /sbin/modprobe --ignore-install psmouse (fatal) > Failed to create initrd image. > > from my modprobe configuration: > alias /dev/psaux psmouse > install psmouse /sbin/modprobe mousedev && /sbin/modprobe --ignore-install > psmouse > remove psmouse /sbin/modprobe -r --ignore-remove psmouse && /sbin/modprobe -r > mousedev Thanks for reporting this. Now for the bad news: this is not a bug, this is a feature. The reason is that install lines in the modprobe configuration are complete shell scripts: they can invoke every executable, access every file. That makes it impossible to find out what should be included on the initial boot image to make the install line successful. Rather than silently ignoring the line and producing an image that may or may not boot, we throw an error, so that you can clean up the configuration. In your situation, you can clean up by removing psmouse from your modprobe configuration: if you have a mouse, the default yaird configuration will load mousedev anyway. If you need backward compatibility with old kernels, consider adding mousedev to /etc/modules; it will be loaded unconditionally then. The error message you got sucks though. The development version has a reworded message (bzr revision nr 15). Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341871: linux-2.6 2.6.14-4 pool timestamps a year off
Package: linux-2.6 Version: 2.6.14-4 Severity: important While manually getting the debian-patches package, I noticed that all of the 2.6.14-4 packages have timestamps a year off (11/26/04 - should be 11/26/05), while the 2.6.12-10 packages are fine (09/27/05). I don't know if this would cause any problems (unless there's date verification of the files), but someone's clock is off by a year ;) Ryan Thoryk Unix and Network Specialist [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Graphical installer - invitation to get involved
On Sat, Dec 03, 2005 at 06:35:33PM +0100, Frans Pop wrote: > On Saturday 03 December 2005 18:18, Colin Watson wrote: > > usplash works fine on x86/vga16fb, x86/vesafb, and powerpc/offb at > > least. It just uses bogl (like d-i) so it should be straightforward to > > port nearly anywhere. > > What happens on sercon installations? It only activates if you put 'splash' on the kernel command line; we've set up *-installer to avoid that if debian-installer/framebuffer is false. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341744: usbutils: mounting usb key problems in AMD64 unstable
Hello, can you please upgrade to linux-2.6 version 2.6.14-4 and verify this bug is still present? Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Bug#341871: linux-2.6 2.6.14-4 pool timestamps a year off
Hello, On Sat, Dec 03, 2005 at 01:18:03PM -0600, Ryan Thoryk wrote: > While manually getting the debian-patches package, I noticed that all of > the 2.6.14-4 packages have timestamps a year off (11/26/04 - should be > 11/26/05), while the 2.6.12-10 packages are fine (09/27/05). Which timestamps are wrong: The files in tha package, or the packages files itself? Where did you get the files from? Looks like your mirror's clock is wrong. If the files IN the packages have wrong timestamps: Which packages exactly? at least for amd64 and i386 this is not reproducible. Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Bug#268621: marked as done (kernel-source-2.6.8: breaks CDDA extraction.)
Your message dated Sat, 03 Dec 2005 18:32:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#268621: fixed in cdrtools 4:2.01+01a03-4 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 28 Aug 2004 13:04:36 + >From [EMAIL PROTECTED] Sat Aug 28 06:04:36 2004 Return-path: <[EMAIL PROTECTED]> Received: from server.logic.univie.ac.at [131.130.190.41] ([MemTOKupzZf/XFN1U2OiL/YxzvzNoalf]) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C12sm-0007Gu-00; Sat, 28 Aug 2004 06:04:36 -0700 Received: from m-134-246.adsl.univie.ac.at ([131.130.134.246]) by server.logic.univie.ac.at with asmtp (Exim 4.34) id 1C12sj-0001at-GS; Sat, 28 Aug 2004 15:04:35 +0200 Received: from ametzler by downhill.univie.ac.at with local (Exim 4.34) id 1C12sj-du-2R; Sat, 28 Aug 2004 15:04:33 +0200 Date: Sat, 28 Aug 2004 15:04:32 +0200 From: Andreas Metzler <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.8: breaks CDDA extraction. Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 2.63 X-GPG-Fingerprint: BCF7 1345 BE42 B5B8 1A57 EE09 1D33 9C65 8B8D 7663 User-Agent: Mutt/1.5.6+20040722i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-source-2.6.8 Version: 2.6.8-5 Severity: normal Apart from the solved problems with cd-writing in 2.6.8 (memory leak and requiring root permissions) there is another one: It breaks cdda2wav quite heavily cdda2wav -t 1 dev=ATA:1,0,0 (or dev=/dev/hdc) results in a heavily distorted audiofile. Repeating the same command with the same CD under 2.6.7 produces a correct file (no audible errors). It does not matter whether cdda2wav is run as root or as user. cdda2wav -paranoia seems to produce correct files even under 2.6.8 but it is also severly broken, it takes about 20 times as long as under 2.6.7 (i.e. almost realtime) and CPU usage stays at 90% while this is happening (instead of 20% under 2.6.7.) cu andreas -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7.fb Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.14.90.0.7-8 The GNU assembler, linker and bina ii bzip2 1.0.2-1 A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2 The GNU core utilities -- no debconf information -- "See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in "Snow Crash" --- Received: (at 268621-close) by bugs.debian.org; 4 Dec 2005 02:41:10 + >From [EMAIL PROTECTED] Sat Dec 03 18:41:10 2005 Return-path: <[EMAIL PROTECTED]> Received: from katie by spohr.debian.org with local (Exim 4.50) id 1Eijfa-0004p5-Hv; Sat, 03 Dec 2005 18:32:06 -0800 From: Steve McIntyre <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.60 $ Subject: Bug#268621: fixed in cdrtools 4:2.01+01a03-4 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Sat, 03 Dec 2005 18:32:06 -0800 X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-CrossAssassin-Score: 3 Source: cdrtools Source-Version: 4:2.01+01a03-4 We believe that the bug you reported is fixed in the latest version of cdrtools, which is due to be installed in the Debian FTP archive: cdda2wav_2.01+01a03-4_i386.deb to pool/main/c/cdrtools/cdda2wav_2.01+01a03-4_i386.deb cdrecord_2.01+01a03-4_i386.deb to pool/main/c/cdrtools/cdrecord_2.01+01a03-4_i386.deb cdrtools-doc_2.01+01a03-4_all.deb to pool/main/c/cdrtools/cdrtools-doc_2.01+01a03-4_all.deb cdrtools_2.01+01a03-4.diff.gz to pool/main/c/cdrtools/cdrtools_2.01+01a03-4.diff.gz cdrtools_2.01+01a03-4.dsc to pool/main/c/cdrtools/cdrtools_2.01+01a0
Bug#340486: Unable to compile modules, fixdep.c required
Hi, After a discussion with kernel-package maintainer, we came to the conclusion that it's a kernel-package problem. It was trying to run oldconfig target for the kernel in the linux-headers directory, which does not contain enough files for this to succeed. The fixed kernel-package (10.012) has appeared in unstable today, and should take care of the problems you are encountering. Please give it a spin and post the results to the bug trail. Thanks and best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: base-installer - enabling initramfs-tools ?
On Sat, Dec 03, 2005 at 11:41:38PM +0100, Frans Pop wrote: > I've tested a new base-installer with Colin's initramfs-tools patch > enabled again. As such the patch works, but I cannot see much point in > committing it currently. > > Reason is that, even if initramfs-tools is already installed, 'apt-install > ' will still pull in yaird and thus yaird will be used to > create the initrd. > > Reason is that the kernel images currently list the following > dependencies: > Depends: yaird | initramfs-tools | linux-initramfs-tool, module-init-tools Ok, this should not happen, if initramfs-tools is installed, then it should satisfy that dependency, so there must be something else going on. > I think we have 5 options: > - forget about using initramfs-tools as default for d-i I feel that this is a decision which you need to take together with the kernel team, and not do your own stuff in your corner, especially as the kernel team has been evaluating both tools since over a month. Especially as initramfs-tools/yaird is known not to work on some architectures. > - install both even if initramfs-tools will probably not be used This is probably best, and i would say leave the choice to the user in expert mode even :). In particular, the plan is to have the kernel postinst chose the more refined detection of working use-cases, and disable the tool which is known not to work, as such there may be some use-case where having initramfs-tools and not yaird will fail (at runtime sadly as this is how initramfs-tools is designed, contrary to yaird which will fail at ramdisk build time). I am toying with the idea of modifying the dependency to pull in both of them, but a Recommend for initramfs-tools was proposed also, not sure if the way packages are installed in d-i will do the right thing in how it handles Recommends. > - add code to edit the config file force the use of initramfs-tools; > yaird will probably still be installed though > - convince the kernel team to list initramfs-tools first instead of yaird, > effectively changing the default initrd generator > - file a bug against apt-get (?) to not pull in a first dep if an > alternative "ORed" dep is already satisfied Yeah, this sounds very much like an arrogant "we have decided to use initramfs-tools and the kernel team are just morrons" kind of speach, and then you wonder why i get pissed at you for this kind of things. What about doing the sane thing, and both discuss this with the kernel team, and second deferring to the kernel teams decision on this, as the kernel team is the one which will in the end have to deal with bug reports due to your choices. > From a d-i standpoint initramfs-tools has the advantage that its > dependencies and total size are lighter than yaird, especially now that > python is no longer required. Yeah, only klibc which is still not building fine on all arches. Speak about informed decision. > Extract from the installations syslog: > base-installer: info: Installing initrd-tools. > apt-install: The following extra packages will be installed: > apt-install: cramfsprogs dash > apt-install: The following NEW packages will be installed: > apt-install: cramfsprogs dash initrd-tools Why in hell are you installing initrd-tools ? > base-installer: info: Installing kernel 'linux-image-2.6-686'. > apt-install: The following extra packages will be installed: > apt-install: libhtml-template-perl libparse-recdescent-perl >linux-image-2.6.14-2-686 perl perl-modules yaird > apt-install: Suggested packages: > apt-install: libipc-sharedcache-perl linux-doc-2.6.14 >linux-source-2.6.14 lilo grub > apt-install: fdutils libterm-readline-gnu-perl >libterm-readline-perl-perl doc-base > apt-install: Recommended packages: > apt-install: perl-doc > apt-install: The following NEW packages will be installed: > apt-install: libhtml-template-perl libparse-recdescent-perl >linux-image-2.6-686 > apt-install: linux-image-2.6.14-2-686 perl perl-modules yaird > > apt-install: Setting up linux-image-2.6.14-2-686 (2.6.14-4) ... > apt-install: Using /usr/sbin/mkinitrd.yaird to build the ramdisk. > apt-install: Full list of probed ramdisk generating tools : > /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird > /usr/sbin/mkinitramfs. Ah, well, these two lines show that initramfs-tools are not installed, or it would be listed as Possible other candidate in an additional line between the Using ... and Full list ..., so i think you just messed up the installing of initramfs-tools, and are looking for far-fetched conclusions out of some stupid mistake, oh well. CCing the kernel team, as this is where you should have posted in the first place. Note to Frans: i took the effort to remove you explicitly from the recipients, and would have trimmed this, except i am cross posting to debian-kernel, and there was not really much to trim, as you see, i make effort, and i hope
Re: base-installer - enabling initramfs-tools ?
On Sat, Dec 03, 2005 at 10:03:16PM -0800, Steve Langasek wrote: > On Sat, Dec 03, 2005 at 11:41:38PM +0100, Frans Pop wrote: > > Reason is that, even if initramfs-tools is already installed, 'apt-install > > ' will still pull in yaird and thus yaird will be used to > > create the initrd. > > I've never seen apt-get behave this way: the expected behavior is indeed > that if initramfs-tools is installed, apt-get will not automatically pull in > yaird for this ORed dependency. Can you reproduce this behavior outside of > d-i? No, he made a mistake somewhere, and initramfs-tools is clearly not installed, as is shown by the log output he posted. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: base-installer - enabling initramfs-tools ?
On Sun, Dec 04, 2005 at 08:21:16AM +0100, Sven Luther wrote: > I feel that this is a decision which you need to take together with the kernel > team, and not do your own stuff in your corner, especially as the kernel team > has been evaluating both tools since over a month. Especially as > initramfs-tools/yaird is known not to work on some architectures. Err, obviously i meant initramfs-tools/klibc here, and to stop any flames, this is the current situation, i am not saying that this will (and should) not change in the (near?) future. Still a new libc is clearly more fragile and in need of maturation than any other dependency, especially the perl dependencies of python. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341871: marked as done (linux-2.6 2.6.14-4 pool timestamps a year off)
Your message dated Sun, 4 Dec 2005 01:41:12 -0600 (CST) with message-id <[EMAIL PROTECTED]> and subject line Bug#341871: linux-2.6 2.6.14-4 pool timestamps a year off has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 3 Dec 2005 19:18:05 + >From [EMAIL PROTECTED] Sat Dec 03 11:18:05 2005 Return-path: <[EMAIL PROTECTED]> Received: from mail.cyberonic.com ([4.17.179.4]) by spohr.debian.org with esmtp (Exim 4.50) id 1EictY-0005dG-S9 for [EMAIL PROTECTED]; Sat, 03 Dec 2005 11:18:05 -0800 Received: from europa.tliquest.net (node-40241c9a.mdw.onnet.us.uu.net [64.36.28.154]) by mail.cyberonic.com (8.12.8/8.12.8) with SMTP id jB3JYDKN032144 for <[EMAIL PROTECTED]>; Sat, 3 Dec 2005 14:34:14 -0500 Received: (qmail 20406 invoked by uid 500); 3 Dec 2005 19:18:03 - Received: from localhost ([EMAIL PROTECTED]) by localhost with SMTP; 3 Dec 2005 19:18:03 - Date: Sat, 3 Dec 2005 13:18:03 -0600 (CST) From: Ryan Thoryk <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: linux-2.6 2.6.14-4 pool timestamps a year off Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: linux-2.6 Version: 2.6.14-4 Severity: important While manually getting the debian-patches package, I noticed that all of the 2.6.14-4 packages have timestamps a year off (11/26/04 - should be 11/26/05), while the 2.6.12-10 packages are fine (09/27/05). I don't know if this would cause any problems (unless there's date verification of the files), but someone's clock is off by a year ;) Ryan Thoryk Unix and Network Specialist [EMAIL PROTECTED] --- Received: (at 341871-done) by bugs.debian.org; 4 Dec 2005 07:41:14 + >From [EMAIL PROTECTED] Sat Dec 03 23:41:14 2005 Return-path: <[EMAIL PROTECTED]> Received: from mail.cyberonic.com ([4.17.179.4]) by spohr.debian.org with esmtp (Exim 4.50) id 1EioUj-0003Q4-Qt for [EMAIL PROTECTED]; Sat, 03 Dec 2005 23:41:14 -0800 Received: from europa.tliquest.net (node-40241c9a.mdw.onnet.us.uu.net [64.36.28.154]) by mail.cyberonic.com (8.12.8/8.12.8) with SMTP id jB47vWKN029543 for <[EMAIL PROTECTED]>; Sun, 4 Dec 2005 02:57:32 -0500 Received: (qmail 1567 invoked by uid 500); 4 Dec 2005 07:41:12 - Received: from localhost ([EMAIL PROTECTED]) by localhost with SMTP; 4 Dec 2005 07:41:12 - Date: Sun, 4 Dec 2005 01:41:12 -0600 (CST) From: Ryan Thoryk <[EMAIL PROTECTED]> To: Frederik Schueler <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: Bug#341871: linux-2.6 2.6.14-4 pool timestamps a year off In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 Just looked over the files, and it's just the other mirror I'm getting the files from and nothing else (so everything's fine then). I'll close the bug. Ryan Thoryk Unix and Network Specialist [EMAIL PROTECTED] On Sun, 4 Dec 2005, Frederik Schueler wrote: > Hello, > > On Sat, Dec 03, 2005 at 01:18:03PM -0600, Ryan Thoryk wrote: >> While manually getting the debian-patches package, I noticed that all of >> the 2.6.14-4 packages have timestamps a year off (11/26/04 - should be >> 11/26/05), while the 2.6.12-10 packages are fine (09/27/05). > > Which timestamps are wrong: The files in tha package, or the > packages files itself? > > Where did you get the files from? Looks like your mirror's clock is wrong. > If the files IN the packages have wrong timestamps: Which packages > exactly? at least for amd64 and i386 this is not reproducible. > > Best regards > Frederik Schueler > > -- > ENOSIG > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
