Bug#383582: linux-image-2.6.17-2-686: suspend doesn't work with 2.6.17
Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: normal I upgraded from linux-image-2.6.16-2-686 to linux-image-2.6.17-2-686, and suspend no longer works on my Dell Latitude X1 using echo -n mem /sys/power/state. It worked great with 2.6.16-2-686. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (999, 'testing'), (80, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.73e tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/really-run-bootloader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#242866: updated tg3.c patch
On Thu, Aug 17, 2006 at 08:34:57PM -0700, [EMAIL PROTECTED] wrote: The most recent tg3.c patch posted here (by Herbert Xu on Tue, 11 May 2004) does not apply cleanly to linux-2.6.17. No surprise, a lot has changed in the last two years. I applied it by hand (it wasn't hard), and I can verify that the result (freshened patch attached) compiles without error. I can also set up tg3 files for the firmware-nonfree package, and supply kernel images for i386 and/or amd64. Testers? I could test it. Where can I find the firmware files? I asume they were created with the original patch. I've never used a driver with external firmware before. Anything special I have to take care off? michael signature.asc Description: Digital signature
Processed: tagging 378455
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 tags 378455 pending Bug#378455: ignores panic=timeout bootparam There were no tags set. Tags added: pending End of message, 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: linux-2.6: includes nondistributable and non-free binary firmware
On Aug 18, Sven Luther [EMAIL PROTECTED] wrote: I don't think the project need anymore such vulgarities, please try to stay I do not think the project needs anymore people with no concern for the needs of our users either. polite, reread the social contract, and abide by what you agreed to when you joined debian. When I joined Debian we cared about free software. Not free firmwares. -- ciao, Marco signature.asc Description: Digital signature
Bug#383499: linux-image-2.6.17-2-686: USB Keyboard not recognized anymore
Maks, Here is the output you asked for: [EMAIL PROTECTED]:~$ dpkg -l udev Souhait=inconnU/Install-b/suppRim/Purg/H= garder | tat=Non/Install/fichier-Config/dpaqUet/chec-conFig/H=semi-install |/ Err?=(aucune)/H= garder/besoin Rinstallation/X=les deux (tat,Err: majuscule=mauvais) ||/ Nom Version Description +++-==-==- rc udev 0.086-1 /dev/ and hotplug management daemon If you want i can send 2 parts of the messages file , the first when i boot from the linux-image 2.6.15 where the USB Keybord is recognized and the second when i boot from a linux image 2.6.16 or 17 , do you think it could be useful ? Thanks a lot for looking to this problem maximilian attems a crit: tags 383499 moreinfo severity 383499 normal stop On Thu, Aug 17, 2006 at 06:59:17PM +0200, Michael Henneton wrote: with linux image -2.6.17-2-686 or -2.6.16-2-686 my usb keyboard is not recognized anymore (only the laptop keyboard is recognized), but it does with linux-image-2.6.15-1-686. which version of udev are you using, post the output of dpkg -l udev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
Package: initramfs-tools Version: 0.74 Severity: important I can't pinpoint the exact release but the behaviour of update-initramfs -u has changed recently. update-initramsfs -u is used in several postinst scripts and formerly updated the initrd of all installed kernels. The new behaviour is, to only update the initrd of the latest instlled kernel, which is wrong imho. E.g. you have kernel 2.6.16 and 2.6.17 installed and you are currently running 2.6.16, update-initramfs -u will only update the 2.6.17 initrd. I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. Cheers, Michael -- Package-specific info: -- /proc/cmdline root=/dev/hda6 ro quiet SELINUX_INIT=NO vga=791 -- /proc/filesystems reiserfs ext3 ext2 vfat ntfs -- lsmod Module Size Used by ppp_synctty 7168 1 ppp_generic22996 5 ppp_synctty slhc6208 1 ppp_generic nls_utf81664 1 ntfs 221652 1 radeon113312 1 drm62164 2 radeon binfmt_misc 8712 1 cpufreq_ondemand5344 1 cpufreq_performance 1664 0 cpufreq_powersave 1472 0 speedstep_centrino 6032 1 rfcomm 31000 0 l2cap 18180 5 rfcomm bluetooth 40484 4 rfcomm,l2cap ipv6 229280 12 ppdev 7364 0 parport_pc 24868 1 lp 8324 0 parport19840 3 ppdev,parport_pc,lp thermal10120 0 fan 3076 0 button 4816 0 processor 17216 2 speedstep_centrino,thermal ac 3332 0 battery 7300 0 nls_iso8859_1 3840 1 nls_cp437 5504 1 vfat 10304 1 fat45532 1 vfat dm_mod 46264 0 usbhid 36960 0 fcusb2653336 1 capi 13568 6 capifs 3912 2 capi kernelcapi 35232 2 fcusb2,capi pcmcia 23968 0 snd_intel8x0 28252 4 snd_ac97_codec 92064 1 snd_intel8x0 snd_ac97_bus1856 1 snd_ac97_codec snd_pcm_oss34592 0 snd_mixer_oss 15616 1 snd_pcm_oss ipw210066800 0 ieee80211 29640 1 ipw2100 ieee80211_crypt 4288 1 ieee80211 snd_pcm65864 4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 18244 2 snd_pcm intel_agp 20764 1 firmware_class 7488 2 pcmcia,ipw2100 joydev 8000 0 tsdev 6080 0 evdev 7872 2 yenta_socket 23628 1 rsrc_nonstatic 11136 1 yenta_socket pcmcia_core32848 3 pcmcia,yenta_socket,rsrc_nonstatic agpgart26160 2 drm,intel_agp 8139cp 16512 0 mii 4800 1 8139cp ehci_hcd 26568 0 snd43108 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 6944 1 snd snd_page_alloc 7688 2 snd_intel8x0,snd_pcm uhci_hcd 19464 0 usbcore 109568 5 usbhid,fcusb2,ehci_hcd,uhci_hcd -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.8 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages initramfs-tools depends on: ii busybox 1:1.1.3-2 Tiny utilities for small and embed ii cpio 2.6-17 GNU cpio -- a program to manage ar ii klibc-utils 1.4.11-3 small statically-linked utilities ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii udev 0.097-1/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
#include hallo.h * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]: I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. Why should one update _all_ initramfs images when beeing interested in only single one? This also increases the risk for breaking ALL WORKING initramfs images in the case where a new bug in initramfs-tools appears. I recommend closing this bug report unless you provide a good explanation. Eduard. -- Rhonda Hah! Ich hab das Monster php gebändigt! * Joey . o O ( Rhonda is now known as Siegfried )
Re: linux-2.6: includes nondistributable and non-free binary firmware
On Fri, 18 Aug 2006 00:35:49 +0200 Sven Luther wrote: It was just some way to say, please don't be so harsh on larry, who has good intentions and actually did some work, not compared to others. Sure. And that's great. If only you did not clutter such good intention with whining. Yes, it now only takes small hints to be considered whining - thanks to your massive efforts to make us all aware of it. /me still doesn't understand why you chose not to credit me though, You may not ever understand it. Repeating does not help. - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm pgp97AXe3vfkX.pgp Description: PGP signature
DMA problems VT8237A chipset (msi board)
hello! I can't activate dma (hdparm -d1 /dev) the msi board uses the via VT8237A chipset. linux: debian kernel: 2.6.8-12-amd64-generic messages-log: Aug 18 04:17:15 localhost kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Aug 18 04:17:15 localhost kernel: ide: Assuming 33MHz system bus speed for PIO m odes; override with idebus=xx Aug 18 04:17:15 localhost kernel: VP_IDE: IDE controller at PCI slot :00:0f. 0 Aug 18 04:17:15 localhost kernel: VP_IDE: chipset revision 7 Aug 18 04:17:15 localhost kernel: VP_IDE: not 100%% native mode: will probe irqs later Aug 18 04:17:15 localhost kernel: VP_IDE: Unknown VIA SouthBridge, disabling DMA any ideas? greetings! Virus checked by G DATA AntiVirusKit Version: AVK 16.9186 from 17.08.2006 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Urgent : megaraid and qla2300 modules not found
dann frazier a écrit : On Thu, Aug 17, 2006 at 03:05:35PM +0200, De Leeuw Guy wrote: Hello, I have 2 days to install debian etch on our production server. I download the last daily build of the cdrom (release debian-testing-ia64-netinstall.iso 20060815). But missing the driver megaraid legacy and qla2300 on the cdrom It's my last chance to migrate our redhat to debian could you help me by building a new daily build iso with these 2 modules or minimum with the megaraid_legacy ? Hello Dan I'll fix this for the next build - thanks for reporting it. On the build 20060817 no changes. In the meantime it might be easiest for you to: * grab http://mirrors.kernel.org/debian/pool/main/l/linux-2.6.16/linux-image-2.6.16-2-itanium-smp_2.6.16-17_ia64.deb * extract the contents somewhere: dpkg-deb -x linux-image-2.6.16-2-itanium-smp_2.6.16-17_ia64.deb /tmp/dir * Post the modules you need on an http server somewhere * Once your network is up, drop to a shell and wget the drivers from your server * Use insmod/modprobe to load these modules * return to the installer Does not work, the installer see the new megaraid driver but continue to loop to the no disks message. If you have problems, like you don't have access to an http server, etc, hop on #debian-ia64 i'll try to help you out. Thanks for your help Dan Guy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]: I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. Why should one update _all_ initramfs images when beeing interested in only single one? Why should I be only interested in only a single one? If I install e.g. the uswsusp package (which has to update the initrd because it has to install a resume binary there) I'd expect the package to work with all kernels I have installed not only a single one. In addition only the newest kernel installed is updated, which is very confusing imho. If it all, it should update the initrd of the currently running kernel. This also increases the risk for breaking ALL WORKING initramfs images in the case where a new bug in initramfs-tools appears. As you already said, if it's a bug in initramfs-tools, it should be fixed there and not prevent update-initramfs from doing the right thing. It won't help you anyways if you have only one kernel installed. And your argument can actually be held against you: what if an update of initramfs-tools fixes a (grave/security related) bug. Wouldn't you expect that all installed kernels are updated accordingly. I don't think normal users will know that they have to run update-initramfs -u -k 1.2.3 for all installed kernel versions. We can't expect that more unexperienced users will have to do that manually. So this is even a security related issue. I recommend closing this bug report unless you provide a good explanation. I strongly oppose. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
hello michael, thanks your request made my day. indeed in ubuntu all initrd.img gets updated. On Fri, Aug 18, 2006 at 12:12:28PM +0200, Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]: I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. well for debian we prefer the conservative default to ship the newest and greatest only in the newest one. and even this is sometimes questioned see #358397 or #382808 Why should one update _all_ initramfs images when beeing interested in only single one? This also increases the risk for breaking ALL WORKING initramfs images in the case where a new bug in initramfs-tools appears. if the user wants to do it, he can do it by hand: update-initramfs -u -k all that will update all the initramfs that initramfs-tools generated. although i would not recommed that for udev 0.097-1 best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6: includes nondistributable and non-free binary firmware
On Fri, Aug 18, 2006 at 12:29:56PM +0200, Jonas Smedegaard wrote: On Fri, 18 Aug 2006 00:35:49 +0200 Sven Luther wrote: /me still doesn't understand why you chose not to credit me though, You may not ever understand it. Repeating does not help. I am also slightly (or more) offended by it, and repeating that may some day make you realize it, which is why i will repeat as long as it takes. With some people there is no other way around, see how long and how many repetitions it took you to take the RC bug seriously ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383620: fn key not support on MacBook Pro
Package: linux-2.6 Version: 2.6.17-6 The fn key is not supported on MacBook Pros. To support it, the patch at http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=5c218e3b86510f9685bfae5b0d2d7cc8468056c1;hp=dfbaa7d8a4056436b6a170625d64986ebb648486 should be applied and CONFIG_USB_HIDINPUT_POWERBOOK should be set to y. -- Matt signature.asc Description: Digital signature
Re: linux-2.6: includes nondistributable and non-free binary firmware
On Fri, Aug 18, 2006 at 09:23:43AM +0200, Marco d'Itri wrote: On Aug 18, Sven Luther [EMAIL PROTECTED] wrote: I don't think the project need anymore such vulgarities, please try to stay I do not think the project needs anymore people with no concern for the needs of our users either. There you are again putting words in my mouth i never said. Independently of what you think or say, stay polite about it, especially to outsiders like larry. Also, the social contract says clearly that : 1) we care about our users *AND* free software. 2) we have created the non-free section to put non-free software in it that may be needed for our users. What else do you want ? polite, reread the social contract, and abide by what you agreed to when you joined debian. When I joined Debian we cared about free software. Not free firmwares. and in what world do you live where you could even start to imagine that the firmwares are not software ? They clearly are not hardware, since you cannot directly touch them. Also, i think all of you are taking the wrong discourse, and there is no way you can be right. You should instead try the following discourse : 1) The firmware in question (those that are not plain register dumps) are indeed non-free, since they are clearly software, often assembly software, compiled with some assembler tool, and we lack sources for them (but someone has said source, or at least had it at some time point. 2) But we argue that we should still distribute it in main, for reason such and such. Among those reason, there are a few which come to my mind out of hand : 1) We consider firmware as being part of the hardware, not really the software. 2) If we consider a hardware piece which needs an uploadable firmware, even if the firmware in question is non-free, it is still globally more free than an equivalent piece of hardware where all is hardcoded in silicon. And so on, it is always better to be honest and true to oneself, than to try to argue obvious wrong stuff, like you have been doing, and furthermore, seeing that there is no way you can honestly defend your point, and you know that inside yourself, so you ressort to vulgarities and barkings to get your point accross. Please meditate on this one, and then come back to this discussion with an open and honest mind, and it will be much more fruitful. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
On Fri, Aug 18, 2006 at 01:07:34PM +0200, Michael Biebl wrote: snipp answered stuff In addition only the newest kernel installed is updated, which is very confusing imho. If it all, it should update the initrd of the currently running kernel. this for upgrade reasons. if you install from sarge you want that the hooks work for the new one. the wrong order of the update-initramfs was a big upgrade trouble from breezy to dapper, that got solved quite late in the game. not eager to repeat that here. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DMA problems VT8237A chipset (msi board)
On Fri, Aug 18, 2006 at 12:53:06PM +0200, Radek Oliwa wrote: hello! I can't activate dma (hdparm -d1 /dev) the msi board uses the via VT8237A chipset. linux: debian kernel: 2.6.8-12-amd64-generic messages-log: Aug 18 04:17:15 localhost kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Aug 18 04:17:15 localhost kernel: ide: Assuming 33MHz system bus speed for PIO m odes; override with idebus=xx Aug 18 04:17:15 localhost kernel: VP_IDE: IDE controller at PCI slot :00:0f. 0 Aug 18 04:17:15 localhost kernel: VP_IDE: chipset revision 7 Aug 18 04:17:15 localhost kernel: VP_IDE: not 100%% native mode: will probe irqs later Aug 18 04:17:15 localhost kernel: VP_IDE: Unknown VIA SouthBridge, disabling DMA any ideas? Any chance this is another incarnation of the now infamous ide-generic bug ? It certainly show the right symptoms for that. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
#include hallo.h * Michael Biebl [Fri, Aug 18 2006, 01:07:34PM]: Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]: I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. Why should one update _all_ initramfs images when beeing interested in only single one? Why should I be only interested in only a single one? If I install e.g. Because usualy it gets executed when you install a kernel-image package? the uswsusp package (which has to update the initrd because it has to install a resume binary there) I'd expect the package to work with all kernels I have installed not only a single one. That's orthogonal to the regular usage of mkinitramfs. uswsusp package is the right one to add a call to update ALL initrds. In addition only the newest kernel installed is updated, which is very confusing imho. If it all, it should update the initrd of the currently running kernel. Does not confuse me at all. The package beeing installed cares about its own setup. Not more, not less. No need to touch non-involved packges. This also increases the risk for breaking ALL WORKING initramfs images in the case where a new bug in initramfs-tools appears. As you already said, if it's a bug in initramfs-tools, it should be Don't reintepret my statements to something you like. Risk for a fact != known fact. If there is a known bug in initramfs-tools which is fixed with an upgraded version, then it could and should be executed for all initrds. Eduard. -- Joey umh... zwischen gestern und heute haette eigentlich auch locker noch ein Tag reingepasst... youam Joey: diesen tag nennt man nacht und kennzeichnet ihn durch das fehlen des gelben balls im blauen raum
Processed: your mail
Processing commands for [EMAIL PROTECTED]: reassign 383486 initramfs-tools Bug#383486: update-grub provides broken root boot param for DAC960 Bug reassigned from package `grub' to `initramfs-tools'. retitle 383486 initramfs-tools fails to include DAC960 RAID controller Bug#383486: update-grub provides broken root boot param for DAC960 Changed Bug title. (By the way, that Bug is currently marked as done.) module - patch to follow Unknown command or malformed arguments to command. reopen 383486 Bug#383486: initramfs-tools fails to include DAC960 RAID controller Bug reopened, originator not changed. End of message, 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]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
On Fri, Aug 18, 2006 at 12:12:28PM +0200, Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]: I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. Why should one update _all_ initramfs images when beeing interested in only single one? This also increases the risk for breaking ALL WORKING initramfs images in the case where a new bug in initramfs-tools appears. Well, if you are interested in only 1, you don't use the -u option ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383486: PATCH to /usr/share/initramfs-tools/hook-functions
--- /usr/share/initramfs-tools/hook-functions.orig2006-08-18 13:21:56.0 +0100 +++ /usr/share/initramfs-tools/hook-functions2006-08-18 13:19:46.0 +0100 @@ -169,7 +169,7 @@ scsi) for x in 3w-9xxx 3w- a100u2x aacraid advansys ahci \ aic79xx aic7xxx arcmsr ata_piix atari_scsi atp870u BusLogic \ -cciss ch cpqarray dac960 dc395x dmx3191d dpt_i2o eata fdomain \ +cciss ch cpqarray DAC960 dc395x dmx3191d dpt_i2o eata fdomain \ gdth hptiop ibmvscsic initio ipr ips isp1020 lpfc max_scsi \ mac53c94 megaraid megaraid_mbox megaraid_mm mesh mptfc \ mptscsih mptsas mptspi nsp32 osst qla1280 qla2100 qla2200 \ --- /usr/share/initramfs-tools/hook-functions.orig 2006-08-18 13:21:56.0 +0100 +++ /usr/share/initramfs-tools/hook-functions 2006-08-18 13:19:46.0 +0100 @@ -169,7 +169,7 @@ scsi) for x in 3w-9xxx 3w- a100u2x aacraid advansys ahci \ aic79xx aic7xxx arcmsr ata_piix atari_scsi atp870u BusLogic \ - cciss ch cpqarray dac960 dc395x dmx3191d dpt_i2o eata fdomain \ + cciss ch cpqarray DAC960 dc395x dmx3191d dpt_i2o eata fdomain \ gdth hptiop ibmvscsic initio ipr ips isp1020 lpfc max_scsi \ mac53c94 megaraid megaraid_mbox megaraid_mm mesh mptfc \ mptscsih mptsas mptspi nsp32 osst qla1280 qla2100 qla2200 \
Processed: your mail
Processing commands for [EMAIL PROTECTED]: tags 383486 patch Bug#383486: initramfs-tools fails to include DAC960 RAID controller There were no tags set. Tags added: patch End of message, 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]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: retitle 383486 initramfs-tools fails to include DAC960.ko RAID controller module Bug#383486: initramfs-tools fails to include DAC960 RAID controller Changed Bug title. End of message, 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]
Bug#383629: linux-image-2.6.17-2-686: ipw2200 module cannot load its firmware
Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: normal When I run 'modprobe ipw2200' I have this output in /var/log/messages: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.1.1 ipw2200: Copyright(c) 2003-2006 Intel Corporation ACPI: PCI Interrupt :02:02.0[A] - GSI 18 (level, low) - IRQ 201 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2 ipw2200: Unable to load firmware: -2 ipw2200: failed to register network device ACPI: PCI interrupt for device :02:02.0 disabled ipw2200: probe of :02:02.0 failed with error -5 The ipw2200 firmware 3.0 is installed in /lib/firmware and it was working with linux-image-2.6.17-1-686. Regards, -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.74 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-17 Yet Another mkInitRD Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i686 2.3.6.ds1-2 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: * linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/really-run-bootloader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6: includes nondistributable and non-free binary firmware
On Fri, 18 Aug 2006 13:40:41 +0200 Sven Luther wrote: i will repeat as long as it takes. You are certainly free to do so. And experience (the hard way, rather than just by being told) the consequences of such behaviour. With some people there is no other way around, see how long and how many repetitions it took you to take the RC bug seriously ? Wrong. New info caused new action. Your whining has the opposite effect: Your wrapping of valuable info in big chunks of whining and repetitive noise risk not even noticing your contributions! - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm pgpWiMom1nuQ8.pgp Description: PGP signature
linux-modules-extra-2.6_2.6.17-1_powerpc.changes ACCEPTED
Accepted: linux-modules-extra-2.6_2.6.17-1.dsc to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.17-1.dsc linux-modules-extra-2.6_2.6.17-1.tar.gz to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.17-1.tar.gz redhat-cluster-modules-2.6-powerpc-miboot_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-powerpc-miboot_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6-powerpc-smp_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-powerpc-smp_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6-powerpc_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-powerpc_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6-vserver-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-vserver-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6-vserver-powerpc_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-vserver-powerpc_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6.17-2-powerpc-miboot_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.17-2-powerpc-miboot_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6.17-2-powerpc-smp_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.17-2-powerpc-smp_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6.17-2-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.17-2-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6.17-2-powerpc_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.17-2-powerpc_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6.17-2-vserver-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.17-2-vserver-powerpc64_1.02.00-8+2.6.17-1_powerpc.deb redhat-cluster-modules-2.6.17-2-vserver-powerpc_1.02.00-8+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.17-2-vserver-powerpc_1.02.00-8+2.6.17-1_powerpc.deb squashfs-modules-2.6-powerpc-miboot_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-powerpc-miboot_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6-powerpc-smp_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-powerpc-smp_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6-powerpc64_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-powerpc64_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6-powerpc_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-powerpc_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6-vserver-powerpc64_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-vserver-powerpc64_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6-vserver-powerpc_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-vserver-powerpc_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6.17-2-powerpc-miboot_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6.17-2-powerpc-miboot_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6.17-2-powerpc-smp_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6.17-2-powerpc-smp_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6.17-2-powerpc64_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6.17-2-powerpc64_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6.17-2-powerpc_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6.17-2-powerpc_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6.17-2-vserver-powerpc64_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6.17-2-vserver-powerpc64_3.0-7+2.6.17-1_powerpc.deb squashfs-modules-2.6.17-2-vserver-powerpc_3.0-7+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6.17-2-vserver-powerpc_3.0-7+2.6.17-1_powerpc.deb unionfs-modules-2.6-powerpc-miboot_1.3+debian-3+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/unionfs-modules-2.6-powerpc-miboot_1.3+debian-3+2.6.17-1_powerpc.deb unionfs-modules-2.6-powerpc-smp_1.3+debian-3+2.6.17-1_powerpc.deb to pool/main/l/linux-modules-extra-2.6/unionfs-modules-2.6-powerpc-smp_1.3+debian-3+2.6.17-1_powerpc.deb unionfs-modules-2.6-powerpc64_1.3+debian-3+2.6.17-1_powerpc.deb to
Bug#354203: kernel-source-2.2.25: FTBFS
reassign 354203 ftp.debian.org retitle 354203 please remove dated 2.2 kernel sources stop rationale: 2.2 is not supported since long (dead upstream) d-i removed the last vestiges of it's usage past beta 3 best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: kernel-source-2.2.25: FTBFS
Processing commands for [EMAIL PROTECTED]: reassign 354203 ftp.debian.org Bug#354203: kernel-source-2.2.25: FTBFS with current kernel-package Bug reassigned from package `kernel-source-2.2.25' to `ftp.debian.org'. retitle 354203 please remove dated 2.2 kernel sources Bug#354203: kernel-source-2.2.25: FTBFS with current kernel-package Changed Bug title. stop 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]
Processed: Re: kernel-image-2.4-sparc32 in unstable is not installable
Processing commands for [EMAIL PROTECTED]: reassign 376771 ftp.debian.org Bug#376771: kernel-image-2.4-sparc32 in unstable is not installable Bug reassigned from package `kernel-image-2.4.27-2-sparc32, ftp.debian.org' to `ftp.debian.org'. retitle 376771 please remove unused kernel-image-2.4-sparc32 Bug#376771: kernel-image-2.4-sparc32 in unstable is not installable Changed Bug title. stop 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]
Bug#383499: marked as done (linux-image-2.6.17-2-686: USB Keyboard not recognized anymore)
Your message dated Fri, 18 Aug 2006 16:21:32 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#383499: linux-image-2.6.17-2-686: USB Keyboard not recognized anymore 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) ---BeginMessage--- Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: important -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.17-2-686 depends on: ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-17 Yet Another mkInitRD Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i6862.3.6-19 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/really-run-bootloader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: with linux image -2.6.17-2-686 or -2.6.16-2-686 my usb keyboard is not recognized anymore (only the laptop keyboard is recognized), but it does with linux-image-2.6.15-1-686. ---End Message--- ---BeginMessage--- On Fri, 18 Aug 2006, Michael Henneton wrote: Maks, Here is the output you asked for: [EMAIL PROTECTED]:~$ dpkg -l udev Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé |/ Err?=(aucune)/H=à garder/besoin Réinstallation/X=les deux (État,Err: majuscule=mauvais) ||/ NomVersionDescription +++-==-==- rc udev 0.086-1/dev/ and hotplug management daemon If you want i can send 2 parts of the messages file , the first when i boot from the linux-image 2.6.15 where the USB Keybord is recognized and the second when i boot from a linux image 2.6.16 or 17 , do you think it could be useful ? Thanks a lot for looking to this problem as thought please keep your system up2date before reporting bugs. this long fixed in testing with 0.093-1 you need to upgrade to this. although i wouldn't recommend current udev 0.097-1 in unstable hope it's trouble will be fixed soon. closing -- maks ---End Message---
Bug#383629: linux-image-2.6.17-2-686: ipw2200 module cannot load its firmware
Encolpe DEGOUTE a écrit : Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: normal When I run 'modprobe ipw2200' I have this output in /var/log/messages: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.1.1 ipw2200: Copyright(c) 2003-2006 Intel Corporation ACPI: PCI Interrupt :02:02.0[A] - GSI 18 (level, low) - IRQ 201 ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2 ipw2200: Unable to load firmware: -2 ipw2200: failed to register network device ACPI: PCI interrupt for device :02:02.0 disabled ipw2200: probe of :02:02.0 failed with error -5 The ipw2200 firmware 3.0 is installed in /lib/firmware and it was working with linux-image-2.6.17-1-686. More clues: I'm using udev 0.097-1 and firmware is loaded if you follow these two steps: apt-get install --reinstall linux-image-2.6.17-2-686 apt-get install --reinstall udev It may be an udev bug more than a linux-image bug. Regards, -- Encolpe DEGOUTE http://encolpe.degoute.free.fr/ Logiciels libres, hockey sur glace et autres activités cérébrales
Bug#376771: kernel-image-2.4-sparc32 in unstable is not installable
reassign 376771 ftp.debian.org retitle 376771 please remove unused kernel-image-2.4-sparc32 stop rationale: - Etch will release with 2.6 linux sources only - no longer used in d-i (last usages removed post beta 3) thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of initramfs-tools_0.75_amd64.changes
initramfs-tools_0.75_amd64.changes uploaded successfully to localhost along with the files: initramfs-tools_0.75.dsc initramfs-tools_0.75.tar.gz initramfs-tools_0.75_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DMA problems VT8237A chipset (msi board)
On Fri, Aug 18, 2006 at 01:52:59PM +0200, Sven Luther wrote: Any chance this is another incarnation of the now infamous ide-generic bug ? It certainly show the right symptoms for that. Sven, How could Radek confirm this for us? Radek, Can you send the out put of the following commands? lspci -v lspci -n -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383486: marked as done (initramfs-tools fails to include DAC960.ko RAID controller module)
Your message dated Fri, 18 Aug 2006 08:17:16 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#383486: fixed in initramfs-tools 0.75 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) ---BeginMessage--- Package: installation Version: Etch Beta 3 Following installation of Etch, using the Beta 3 installer (netinst CD image), installation runs to completion without error, on reboot, grub appears fine, and the kernel loads, but during boot hangs with something like waiting for root filesystem. The root partition is on a Mylex DAC960PRL RAID controller, and there is no sign of the relevant module being loaded during boot. PCI vendor ID for the device is: 0x1069 PCI device ID for the device is: 0x0010 I presume the problem lies in the initramfs, but I can't easily get into the system to dig around further... grub boot options are: kernel /boot/vmlinuz-2.6.16-2-686 root=/dev/rd!c0d0p2 ro initrd /boot/initrd.img-2.6.16-2-686 ---End Message--- ---BeginMessage--- Source: initramfs-tools Source-Version: 0.75 We believe that the bug you reported is fixed in the latest version of initramfs-tools, which is due to be installed in the Debian FTP archive: initramfs-tools_0.75.dsc to pool/main/i/initramfs-tools/initramfs-tools_0.75.dsc initramfs-tools_0.75.tar.gz to pool/main/i/initramfs-tools/initramfs-tools_0.75.tar.gz initramfs-tools_0.75_all.deb to pool/main/i/initramfs-tools/initramfs-tools_0.75_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems [EMAIL PROTECTED] (supplier of updated initramfs-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 Aug 2006 15:35:09 +0200 Source: initramfs-tools Binary: initramfs-tools Architecture: source all Version: 0.75 Distribution: unstable Urgency: high Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: maximilian attems [EMAIL PROTECTED] Description: initramfs-tools - tools for generating an initramfs Closes: 378455 383486 Changes: initramfs-tools (0.75) unstable; urgency=high . * hook-functions: Add megaraid_sas to the scsi list. Thanks Kenshi Muto [EMAIL PROTECTED]. . * init: Parse for panic=timeout bootarg. . * hook-functions: Immediately call reboot in the panic function if panic=0 to disallow any console access for secured boxes. (closes: 378455) . * debian/TODO: Update to current state . * update-initramfs: do_bootloader can be set mixed case or upper case. Catch the obvious Yes and YES too. . * hook-functions: Really include DAC960 driver. Thanks Tim Small [EMAIL PROTECTED]. (closes: 383486) 2 module fixes thus urgency high. Files: adc42bb5b99b665afe6b597439021704 623 utils optional initramfs-tools_0.75.dsc 35c44a9a044772776d3bfbc52d41bbc0 46829 utils optional initramfs-tools_0.75.tar.gz 3eafb6fe70da6030f5d048015645a5b8 52158 utils optional initramfs-tools_0.75_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE5dab6n7So0GVSSARAtphAJ9ONv0sdg5mSWWSS8fqAs+omargkwCfbE+u X2+9EGmwwyrR5G2GOE169UI= =d5t/ -END PGP SIGNATURE- ---End Message---
Bug#378455: marked as done (ignores panic=timeout bootparam)
Your message dated Fri, 18 Aug 2006 08:17:16 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#378455: fixed in initramfs-tools 0.75
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)
---BeginMessage---
Package: initramfs-tools
Severity: wishlist
Tags: patch
Here is a patch that adds a new configuration variable PANIC_SHELL
that, when set to no (not the default), disables the fallback to a
shell on panic. (Instead it makes init exit, and thus generates a
kernel panic.)
This is meant to be one link in a chain to secure a system as much as
convenient:
- Configure the BIOS to boot only from the hard drive
- Configure the boot loader not to let the user change boot
parameters
- This step: The boot process does not give a root shell to the
user, ever.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-amd64-k8-smp
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8)
diff -Nru /tmp/uXrcEIMF0w/initramfs-tools-0.69b/conf/initramfs.conf
/tmp/dG2YS5smkE/initramfs-tools-0.69b.0/conf/initramfs.conf
--- /tmp/uXrcEIMF0w/initramfs-tools-0.69b/conf/initramfs.conf 2006-07-07
10:15:42.0 +0200
+++ /tmp/dG2YS5smkE/initramfs-tools-0.69b.0/conf/initramfs.conf 2006-07-16
14:30:43.0 +0200
@@ -45,3 +45,10 @@
NFSROOT=auto
+#
+# PANIC_SHELL: [ yes | no ]
+# Should init give the user a shell on panic?
+#
+
+PANIC_SHELL=yes
+
diff -Nru /tmp/uXrcEIMF0w/initramfs-tools-0.69b/debian/changelog
/tmp/dG2YS5smkE/initramfs-tools-0.69b.0/debian/changelog
--- /tmp/uXrcEIMF0w/initramfs-tools-0.69b/debian/changelog 2006-07-14
00:31:39.0 +0200
+++ /tmp/dG2YS5smkE/initramfs-tools-0.69b.0/debian/changelog2006-07-16
14:36:14.0 +0200
@@ -1,3 +1,9 @@
+initramfs-tools (0.69b.0) unstable; urgency=low
+
+ * Created an option to disable shell invocation on panic.
+
+ -- Lionel Elie Mamane [EMAIL PROTECTED] Sun, 16 Jul 2006 14:32:51 +0200
+
initramfs-tools (0.69b) unstable; urgency=high
* debian/initramfs-tools.preinst: Don't depend upon shipped directories
diff -Nru /tmp/uXrcEIMF0w/initramfs-tools-0.69b/scripts/functions
/tmp/dG2YS5smkE/initramfs-tools-0.69b.0/scripts/functions
--- /tmp/uXrcEIMF0w/initramfs-tools-0.69b/scripts/functions 2006-07-02
19:05:12.0 +0200
+++ /tmp/dG2YS5smkE/initramfs-tools-0.69b.0/scripts/functions 2006-07-16
14:27:33.0 +0200
@@ -59,10 +59,15 @@
if [ -x /sbin/usplash_write ]; then
/sbin/usplash_write QUIT
fi
- modprobe -q i8042
- modprobe -q atkbd
- echo $@
- PS1='(initramfs) ' /bin/sh /dev/console /dev/console 21
+if [ ${PANIC_SHELL} != no ]; then
+ modprobe -q i8042
+ modprobe -q atkbd
+ echo $@
+ PS1='(initramfs) ' /bin/sh /dev/console /dev/console 21
+ else
+ echo $@
+ exit 0
+ fi
}
maybe_break()
---End Message---
---BeginMessage---
Source: initramfs-tools
Source-Version: 0.75
We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:
initramfs-tools_0.75.dsc
to pool/main/i/initramfs-tools/initramfs-tools_0.75.dsc
initramfs-tools_0.75.tar.gz
to pool/main/i/initramfs-tools/initramfs-tools_0.75.tar.gz
initramfs-tools_0.75_all.deb
to pool/main/i/initramfs-tools/initramfs-tools_0.75_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
maximilian attems [EMAIL PROTECTED] (supplier of updated initramfs-tools
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 18 Aug 2006 15:35:09 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.75
Distribution: unstable
Urgency: high
Maintainer: Debian kernel team debian-kernel@lists.debian.org
Changed-By: maximilian attems [EMAIL PROTECTED]
Description:
initramfs-tools - tools for
Bug#383499: linux-image-2.6.17-2-686: USB Keyboard not recognized anymore
On Fri, Aug 18, 2006 at 09:59:30AM +0200, Michael Henneton wrote: !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN Michael, Please resend in plain-text. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
Hi Maks, I can confirm that removing floppy from /etc/initramfs-tools/modules (which still causes a non-bootable system) and inserting cpqarray (which is the only uncommented module in /etc/initramfs-tools/modules) does in fact allow the system to boot. I have attached the dmesg and lsmod. Thanks again, Joshua Rubin Begin dmesg: Linux version 2.6.16-2-686-smp (Debian 2.6.16-17) ([EMAIL PROTECTED]) (gcc version 4.0.4 20060630 (prerelease) (Debian 4.0.3-4)) #1 SMP Sat Jul 15 22:33:00 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f800 (usable) BIOS-e820: 0009f800 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 0fffc000 (usable) BIOS-e820: 0fffc000 - 1000 (ACPI data) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee1 (reserved) BIOS-e820: fff8 - 0001 (reserved) 0MB HIGHMEM available. 255MB LOWMEM available. found SMP MP-table at 000f4ff0 On node 0 totalpages: 65532 DMA zone: 4096 pages, LIFO batch:0 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 61436 pages, LIFO batch:15 HighMem zone: 0 pages, LIFO batch:0 DMI 2.3 present. ACPI: RSDP (v000 COMPAQ) @ 0x000f4f90 ACPI: RSDT (v001 COMPAQ MICRO0x0002 � 0x162e) @ 0x0fffc000 ACPI: FADT (v001 COMPAQ MICRO0x0002 � 0x162e) @ 0x0fffc040 ACPI: MADT (v001 COMPAQ 0083 0x0002 0x) @ 0x0fffc100 ACPI: SSDT (v001 COMPAQ SSDT 0x0001 MSFT 0x010b) @ 0x0800 ACPI: DSDT (v001 COMPAQ DSDT 0x0001 MSFT 0x010b) @ 0x ACPI: PM-Timer IO Port: 0x240 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:8 APIC version 17 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) Processor #3 6:8 APIC version 17 ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) ACPI: IOAPIC (id[0x08] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 8, version 17, address 0xfec0, GSI 0-34 ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 2000 (gap: 1000:eec0) Built 1 zonelists Kernel command line: root=/dev/ida/c0d0p1 ro mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 1024 (order: 10, 16384 bytes) Detected 997.113 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 251936k/262128k available (1505k kernel code, 9532k reserved, 545k data, 176k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2003.87 BogoMIPS (lpj=4007752) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383fbff CPU: After vendor identify, caps: 0383fbff CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: After all inits, caps: 0383fbff 0040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. CPU0: Intel Pentium III (Coppermine) stepping 06 Booting processor 1/0 eip 3000 Initializing CPU#1 Calibrating delay using timer specific routine.. 1993.85 BogoMIPS (lpj=3987713) CPU: After generic identify, caps: 0383fbff CPU: After vendor identify, caps: 0383fbff CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: After all inits, caps: 0383fbff 0040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#1. CPU1: Intel Pentium III (Coppermine) stepping 06 Total of 2 processors activated (3997.73 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 checking TSC synchronization across 2 CPUs: passed. Brought up 2 CPUs migration_cost=4000 checking if image is initramfs... it is Freeing initrd memory: 4287k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0094, last bus=3 PCI: Using configuration type 1 mtrr: your CPUs had inconsistent
Processed: Re: Bug#354203: kernel-source-2.2.25: FTBFS
Processing commands for [EMAIL PROTECTED]: reassign 354203 kernel-source-2.2.25 Bug#354203: RM: kernel-source-2.2.25 -- RoM; obsolete Bug reassigned from package `ftp.debian.org' to `kernel-source-2.2.25'. End of message, 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]
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
Hi Maks, I have confirmed that loading cpqarray first fixes the problem on several systems now. I have also realized that when this is the case, the sym53c8xx driver is not needed or loaded. I thought this was noteworthy. It appears that your presumption was correct that the sym53c8xx and cpqarray modules do not play nicely. Is this something that can be handled in the initramfs automatically instead of forcing everyone running these systems to update their /etc/initramfs-tools/modules file? Thanks again!!! Joshua pgpqbsD1AICDA.pgp Description: PGP signature
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
On Fri, Aug 18, 2006 at 09:05:53AM -0600, Joshua Rubin wrote: I can confirm that removing floppy from /etc/initramfs-tools/modules (which still causes a non-bootable system) and inserting cpqarray (which is the only uncommented module in /etc/initramfs-tools/modules) does in fact allow the system to boot. ok, that pinpoints the coupable quickly scanning http://bugs.debian.org/380272 i noticed that i forgot to ask you: please test 2.6.17 from unstable. is it reporducible there? -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
Hello Joshua,
On Fri, Aug 18, 2006 at 09:59:16AM -0600, Joshua Rubin wrote:
I have confirmed that loading cpqarray first fixes the problem on several
systems now. I have also realized that when this is the case, the sym53c8xx
driver is not needed or loaded. I thought this was noteworthy. It appears
that your presumption was correct that the sym53c8xx and cpqarray modules do
not play nicely.
The problem is because they both claim support for the same PCI Ids:
cpqarray.c,
static const struct pci_device_id cpqarray_pci_device_id[] =
{
{ PCI_VENDOR_ID_NCR, PCI_DEVICE_ID_NCR_53C1510,
0x0E11, 0x4048, 0, 0, 0}, /* LC2 */
{ PCI_VENDOR_ID_NCR, PCI_DEVICE_ID_NCR_53C1510,
0x0E11, 0x4040, 0, 0, 0}, /* Integrated Array */
};
and sym53c8xx_2/sym_glue.c,
static struct pci_device_id sym2_id_table[] __devinitdata = {
{ PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_LSI_53C1510,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL },
{ PCI_VENDOR_ID_LSI_LOGIC, PCI_DEVICE_ID_NCR_53C1510,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL }, /* new */
};
More correctly, the problem is because sym2 is claiming support
for all devices with these PCI device/vendor id.
Can we get the output of lspci -v output from your machine?
If LSI was kind, the PCI class might be different between the two,
or some other clue might be there to differentiate them.
Is this something that can be handled in the initramfs automatically instead
of forcing everyone running these systems to update
their /etc/initramfs-tools/modules file?
The easiest thing to do from the initramfs point of view is to simply
load cpqarray in preference to sym53c8xx.
Regards,
Kyle M.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
remove unused 2.4 images
retitle 376771 RM: kernel-image-2.4.27-2-* -- RoM thanks in accordance with the d-i team any 2.4 kernel-image package can be removed from unstable for all archs except i386 and m68k (both legacy archs :-P) this includes the following list of kernel-images: Package kernel-image-2.4.27-2-s390 Package kernel-image-2.4.27-2-s390-di Package kernel-image-2.4.27-2-s390-tape Package kernel-image-2.4.27-2-s390-tape-di Package kernel-image-2.4.27-2-s390x Package kernel-image-2.4.27-2-sparc32 Package kernel-image-2.4.27-2-sparc32-di Package kernel-image-2.4.27-2-sparc32-smp Package kernel-image-2.4.27-2-sparc64 Package kernel-image-2.4.27-2-sparc64-di Package kernel-image-2.4.27-2-sparc64-smp Package kernel-image-2.4.27-bast Package kernel-image-2.4.27-bast-di Package kernel-image-2.4.27-lart Package kernel-image-2.4.27-lart-di Package kernel-image-2.4.27-netwinder Package kernel-image-2.4.27-netwinder-di Package kernel-image-2.4.27-r3k-kn02 Package kernel-image-2.4.27-r3k-kn02-di Package kernel-image-2.4.27-r4k-ip22 Package kernel-image-2.4.27-r4k-ip22-di Package kernel-image-2.4.27-r4k-kn04 Package kernel-image-2.4.27-r4k-kn04-di Package kernel-image-2.4.27-r5k-cobalt Package kernel-image-2.4.27-r5k-cobalt-di Package kernel-image-2.4.27-r5k-ip22 Package kernel-image-2.4.27-r5k-ip22-di Package kernel-image-2.4.27-r5k-lasat Package kernel-image-2.4.27-riscpc Package kernel-image-2.4.27-riscstation Package kernel-image-2.4.27-sb1-swarm-bn Package kernel-image-2.4.27-sb1-swarm-bn-di Package kernel-image-2.4.27-xxs1500 the following meta packages: Package kernel-image-2.4-generic Package kernel-image-2.4-s390 Package kernel-image-2.4-s390x Package kernel-image-2.4-smp Package kernel-image-2.4-sparc32 Package kernel-image-2.4-sparc32-smp Package kernel-image-2.4-sparc64 Package kernel-image-2.4-sparc64-smp -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
hmm kyle pointed out, i forgot to ask you vital info: lspci info is missing in your bug info, please post lscpi -vv lspci -n thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 01:07:34PM]: Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]: I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. Why should one update _all_ initramfs images when beeing interested in only single one? Why should I be only interested in only a single one? If I install e.g. Because usualy it gets executed when you install a kernel-image package? Just grep for update-initramfs in /var/lib/dpkg/info/*.postinst. I get uswsusp, cryptsetup, mdadm and udev on my machine. They all simply call update-initramfs -u. This means that security updates of these packages are not automatically applied to all installed kernels which is a major security issue imho. If you insist that update-initramfs -u only updates the latest kernel, you should file bug reports against all packages using update-initramfs -u. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
Hi Maks, I tried linux-image-2.6.17-2-686_2.6.17-6_i386.deb from unstable and the problem still exists there. I have attached the outputs of lspci -vv and lspci -n. Thanks, Joshua Rubin # lspci -vv 00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 05) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 64, Cache Line Size: 32 bytes 00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 05) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64, Cache Line Size: 32 bytes 00:01.0 RAID bus controller: LSI Logic / Symbios Logic 53C1510 (rev 02) Subsystem: Compaq Computer Corporation Integrated Array Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 192 (7500ns min, 2000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 177 Region 0: I/O ports at 2000 [size=256] Region 1: Memory at c500 (32-bit, non-prefetchable) [size=16M] Region 2: Memory at c400 (32-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at 2000 [disabled] [size=512K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:03.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] (rev 7a) (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Rage IIC Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2000ns min), Cache Line Size: 32 bytes Region 0: Memory at c200 (32-bit, prefetchable) [size=16M] Region 1: I/O ports at 2400 [size=256] Region 2: Memory at c3fff000 (32-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at 2008 [disabled] [size=128K] Capabilities: [5c] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.0 System peripheral: Compaq Computer Corporation Advanced System Management Controller Subsystem: Compaq Computer Corporation Unknown device b0f3 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 255 Region 0: I/O ports at 1800 [size=256] Region 1: Memory at c3ffef00 (32-bit, non-prefetchable) [size=256] 00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 4f) Subsystem: Broadcom OSB4 South Bridge Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 00:0f.1 IDE interface: Broadcom OSB4 IDE Controller (prog-if 8a [Master SecP PriP]) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 Region 4: I/O ports at 2800 [size=16] 03:04.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) Subsystem: Compaq Computer Corporation NC3163 Fast Ethernet NIC (embedded, WOL) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2000ns min, 14000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 185 Region 0: Memory at c6fff000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at 3000 [size=64] Region 2: Memory at c6e0 (32-bit, non-prefetchable) [size=1M] [virtual] Expansion ROM at 2010 [disabled] [size=1M] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- 03:05.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) Subsystem: Compaq Computer Corporation NC3163 Fast Ethernet NIC (embedded,
Bug#383499: closed by maximilian attems [EMAIL PROTECTED] (Re: Bug#383499: linux-image-2.6.17-2-686: USB Keyboard not recognized anymore)
So i'm running sid :( if i understand you well , i have to wait for udev bug fixing? Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report #383499: linux-image-2.6.17-2-686: USB Keyboard not recognized anymore, which was filed against the linux-image-2.6.17-2-686 package. It has been closed by maximilian attems [EMAIL PROTECTED]. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact maximilian attems [EMAIL PROTECTED] by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) Sujet: Re: Bug#383499: linux-image-2.6.17-2-686: USB Keyboard not recognized anymore Expéditeur: maximilian attems [EMAIL PROTECTED] Date: Fri, 18 Aug 2006 16:21:32 +0200 Destinataire: [EMAIL PROTECTED] Destinataire: [EMAIL PROTECTED] On Fri, 18 Aug 2006, Michael Henneton wrote: Maks, Here is the output you asked for: [EMAIL PROTECTED]:~$ dpkg -l udev Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé |/ Err?=(aucune)/H=à garder/besoin Réinstallation/X=les deux (État,Err: majuscule=mauvais) ||/ NomVersionDescription +++-==-==- rc udev 0.086-1/dev/ and hotplug management daemon If you want i can send 2 parts of the messages file , the first when i boot from the linux-image 2.6.15 where the USB Keybord is recognized and the second when i boot from a linux image 2.6.16 or 17 , do you think it could be useful ? Thanks a lot for looking to this problem as thought please keep your system up2date before reporting bugs. this long fixed in testing with 0.093-1 you need to upgrade to this. although i wouldn't recommend current udev 0.097-1 in unstable hope it's trouble will be fixed soon. closing
Processed: The problem remains with the latest kernel
Processing commands for [EMAIL PROTECTED]: reassign 375194 linux-image-2.6.17-2-powerpc Bug#375194: linux-image-2.6.17-1-powerpc: Unable to boot on G3 (Gossamer) Warning: Unknown package 'linux-image-2.6.17-1-powerpc' Bug reassigned from package `linux-image-2.6.17-1-powerpc' to `linux-image-2.6.17-2-powerpc'. 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]
Bug#354203: kernel-source-2.2.25: FTBFS
On Fri, Aug 18, 2006 at 05:52:55PM +0200, Frans Pop wrote: On Friday 18 August 2006 16:08, maximilian attems wrote: rationale: 2.2 is not supported since long (dead upstream) d-i removed the last vestiges of it's usage past beta 3 This is NOT correct as I have said several times before! m68k Beta3 still uses 2.2. 2.2 kernel source can only be removed _after_ D-I RC1 because it is still used in testing. I'm not sure why that should matter. m68k isn't a release candidate arch right now, and 2.2 isn't going to be used for etch no matter what. But please don't reassign RC bugs to ftp.d.o, please *clone* them instead; we don't want RC-buggy packages leaking back into testing unnecessarily. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 376771 to kernel-image-2.4.27-2-sparc32, cloning 376771, reassign -1 to ftp.debian.org ... ...
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 reassign 376771 kernel-image-2.4.27-2-sparc32 Bug#376771: RM: kernel-image-2.4.27-2-* -- RoM Bug reassigned from package `ftp.debian.org' to `kernel-image-2.4.27-2-sparc32'. clone 376771 -1 Bug#376771: RM: kernel-image-2.4.27-2-* -- RoM Bug 376771 cloned as bug 383685. reassign -1 ftp.debian.org Bug#383685: RM: kernel-image-2.4.27-2-* -- RoM Bug reassigned from package `kernel-image-2.4.27-2-sparc32' to `ftp.debian.org'. severity -1 normal Bug#383685: RM: kernel-image-2.4.27-2-* -- RoM Severity set to `normal' from `grave' retitle 376771 kernel-image-2.4-sparc32 in unstable is not installable Bug#376771: RM: kernel-image-2.4.27-2-* -- RoM Changed Bug title. End of message, 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: DMA problems VT8237A chipset (msi board)
On Fri, 18 Aug 2006 13:52:59 +0200 Sven Luther wrote: On Fri, Aug 18, 2006 at 12:53:06PM +0200, Radek Oliwa wrote: hello! I can't activate dma (hdparm -d1 /dev) the msi board uses the via VT8237A chipset. linux: debian kernel: 2.6.8-12-amd64-generic ^ Any chance this is another incarnation of the now infamous ide-generic bug ? It certainly show the right symptoms for that. Why another incarnation - isn't it simply the same old problem? It looks like a kernel with the problematic Debian-specific patch applied, no? - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm pgp1u7pqlRMcR.pgp Description: PGP signature
initramfs-tools 0.73e MIGRATED to testing
FYI: The status of the initramfs-tools source package in Debian's testing distribution has changed. Previous version: 0.73c Current version: 0.73e -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381844: itramfs-tools doesn't produce working ramdisk on amd64 with MODULES=list
does your system have an: /etc/udev/rules.d/z60_mdadm.rules if yes remove it and regenerate initramfs -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: cloning
Processing commands for [EMAIL PROTECTED]: clone 354203 -1 Bug#354203: RM: kernel-source-2.2.25 -- RoM; obsolete Bug 354203 cloned as bug 383706. severity -1 normal Bug#383706: RM: kernel-source-2.2.25 -- RoM; obsolete Severity set to `normal' from `serious' reassign -1 ftp.debian.org Bug#383706: RM: kernel-source-2.2.25 -- RoM; obsolete Bug reassigned from package `kernel-source-2.2.25' to `ftp.debian.org'. End of message, 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: linux-2.6 - compiler
* Christian T. Steigies wrote: Norbert Tretkowski wrote: * Bastian Blank wrote: At least alpha seems to be in an unmaintained state, and this have to be solved quickly. Aha. Really? No. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DMA problems VT8237A chipset (msi board)
On Fri, Aug 18, 2006 at 09:16:25AM -0600, dann frazier wrote: On Fri, Aug 18, 2006 at 01:52:59PM +0200, Sven Luther wrote: Any chance this is another incarnation of the now infamous ide-generic bug ? It certainly show the right symptoms for that. Sven, How could Radek confirm this for us? Err, this was addressed at the list, since i don't remember all the details of it, and as powerpc didn't even build ide-generic, i was hardly affected. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383707: linux-image-2.6.17-2-amd64: Please enable CONFIG_R8169_VLAN on amd64
Package: linux-image-2.6.17-2-amd64 Version: 2.6.17-6 Severity: minor CONFIG_R8169_VLAN is enabled on all architectures that have the r8169 module, but amd64. Could you please fix that. Thanks. -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.17-2-amd64 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages linux-image-2.6.17-2-amd64 depends on: ii e2fsprogs 1.37-2sarge1 ext2 file system utilities and lib ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool 0.0.12-10Yet Another mkInitRD -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-2.6: includes nondistributable and non-free binary firmware
On Fri, Aug 18, 2006 at 04:28:26PM +0200, Jonas Smedegaard wrote: On Fri, 18 Aug 2006 13:40:41 +0200 Sven Luther wrote: i will repeat as long as it takes. You are certainly free to do so. And experience (the hard way, rather than just by being told) the consequences of such behaviour. With some people there is no other way around, see how long and how many repetitions it took you to take the RC bug seriously ? Wrong. New info caused new action. Your whining has the opposite effect: Your wrapping of valuable info in big chunks of whining and repetitive noise risk not even noticing your contributions! yeah, as opposed to you explaining me in a very strong tone, which i was seriously afraid would degenerate into a RL fist-fight if i persisted, that you should not even look with me at the bug and investigate in erkelenz, right ? It was at that time that i decided that there will be no way i will continue to support yaird as long as you are the main maintainer, because you cannot be thrusthed to fix bugs in a timely fashion. And the info was not new, i had pointed this selfsame thing already in november, but nobody apart me chose to take action and look at the info, while it was your jobs as ramdisk-generator maintainers. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DMA problems VT8237A chipset (msi board)
On Fri, Aug 18, 2006 at 10:30:32PM +0200, Jonas Smedegaard wrote: On Fri, 18 Aug 2006 13:52:59 +0200 Sven Luther wrote: On Fri, Aug 18, 2006 at 12:53:06PM +0200, Radek Oliwa wrote: hello! I can't activate dma (hdparm -d1 /dev) the msi board uses the via VT8237A chipset. linux: debian kernel: 2.6.8-12-amd64-generic ^ Any chance this is another incarnation of the now infamous ide-generic bug ? It certainly show the right symptoms for that. Why another incarnation - isn't it simply the same old problem? It looks like a kernel with the problematic Debian-specific patch applied, no? This report is another manifestation of the same ide-generic bug ? Would this new rephrasing satisfy you, and at the same time respond to your question ? Anyway, thanks for confirming my feelings about this. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383600: behaviour of update-initramfs -u has changed, only updates latest kernel initrd
On Fri, Aug 18, 2006 at 07:03:52PM +0200, Michael Biebl wrote: Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 01:07:34PM]: Eduard Bloch wrote: #include hallo.h * Michael Biebl [Fri, Aug 18 2006, 10:26:53AM]: I suggest to revert to the old behaviour and make -u update all installed kernels. Atm I have to specify each kernel separately vi -k to update them all. Why should one update _all_ initramfs images when beeing interested in only single one? Why should I be only interested in only a single one? If I install e.g. Because usualy it gets executed when you install a kernel-image package? Just grep for update-initramfs in /var/lib/dpkg/info/*.postinst. I get uswsusp, cryptsetup, mdadm and udev on my machine. They all simply call update-initramfs -u. This means that security updates of these packages are not automatically applied to all installed kernels which is a major security issue imho. If you insist that update-initramfs -u only updates the latest kernel, you should file bug reports against all packages using update-initramfs -u. or better yet, make the behaviour configurable, in a system wide debconf setting for example :) Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Fix up kernel bugs
Processing commands for [EMAIL PROTECTED]: reopen 383403 Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Bug reopened, originator not changed. reassign 242866 linux-2.6 Bug#242866: drivers containing firmware blobs Bug#243022: ymfpci_image.h: Sourceless microcode without permission to redistribute Bug reassigned from package `kernel' to `linux-2.6'. reassign 243022 linux-2.6 Bug#243022: ymfpci_image.h: Sourceless microcode without permission to redistribute Bug#242866: drivers containing firmware blobs Bug reassigned from package `linux-2.6' to `linux-2.6'. merge 383493 242866 243022 Bug#242866: drivers containing firmware blobs Bug#243022: ymfpci_image.h: Sourceless microcode without permission to redistribute Bug#383493: Please create /usr/local/etc directory in base-files postinst Mismatch - only Bugs in same state can be merged: Values for `package' don't match: #242866 has `linux-2.6'; #383493 has `base-files' found 383403 2.6.15-8 Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Bug marked as found in version 2.6.15-8. found 383403 2.6.17-6 Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Bug marked as found in version 2.6.17-6. tags 383403 +upstream Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware There were no tags set. Tags added: upstream tags 383403 +etch Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Tags were: upstream Tags added: etch tags 383403 +sid Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Tags were: etch upstream Tags added: sid tags 383403 +d-i Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Tags were: sid etch upstream Tags added: d-i tags 383403 +confirmed Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Tags were: d-i sid etch upstream Tags added: confirmed tags 383403 +help Bug#383403: linux-2.6: includes nondistributable and non-free binary firmware Tags were: confirmed d-i sid etch upstream Tags added: help 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]
Bug#383707: linux-image-2.6.17-2-amd64: Please enable CONFIG_R8169_VLAN on amd64
Hello, On Fri, Aug 18, 2006 at 11:18:49PM +0200, Aurelien Jarno wrote: CONFIG_R8169_VLAN is enabled on all architectures that have the r8169 module, but amd64. Could you please fix that. Thanks. fixed in svn. Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Could someone help me recover my tg3 patch?
I lost my copy. If someone could point me to the last version of Debian's Linux kernel package which shipped with the tg3 firmware loading patch -- I'm not sure which version it was and I can't seem to figure it out -- I would greatly appreciate it. (Heck, if you just sent me a copy of the most recent version of the patch, I would greatly appreciate it.) Thanks in advance. -- Nathanael Nerode [EMAIL PROTECTED] Read it and weep. http://rawstory.com/news/2005/Text_of_Gore_speech_0116.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-2.6.16_2.6.16-18_amd64.changes
linux-2.6.16_2.6.16-18_amd64.changes uploaded successfully to localhost along with the files: linux-2.6.16_2.6.16-18.dsc linux-2.6.16_2.6.16-18.diff.gz linux-doc-2.6.16_2.6.16-18_all.deb linux-manual-2.6.16_2.6.16-18_all.deb linux-patch-debian-2.6.16_2.6.16-18_all.deb linux-source-2.6.16_2.6.16-18_all.deb linux-support-2.6.16-2_2.6.16-18_all.deb linux-tree-2.6.16_2.6.16-18_all.deb linux-headers-2.6.16-2-all_2.6.16-18_amd64.deb linux-headers-2.6.16-2-all-amd64_2.6.16-18_amd64.deb linux-headers-2.6.16-2_2.6.16-18_amd64.deb linux-image-2.6.16-2-amd64-generic_2.6.16-18_amd64.deb linux-headers-2.6.16-2-amd64-generic_2.6.16-18_amd64.deb linux-image-2.6.16-2-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-amd64-k8_2.6.16-18_amd64.deb linux-image-2.6.16-2-amd64-k8-smp_2.6.16-18_amd64.deb linux-headers-2.6.16-2-amd64-k8-smp_2.6.16-18_amd64.deb linux-image-2.6.16-2-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-em64t-p4_2.6.16-18_amd64.deb linux-image-2.6.16-2-em64t-p4-smp_2.6.16-18_amd64.deb linux-headers-2.6.16-2-em64t-p4-smp_2.6.16-18_amd64.deb linux-headers-2.6.16-2-vserver_2.6.16-18_amd64.deb linux-image-2.6.16-2-vserver-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-vserver-amd64-k8_2.6.16-18_amd64.deb linux-image-2.6.16-2-vserver-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-vserver-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen_2.6.16-18_amd64.deb linux-image-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb linux-modules-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb linux-image-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb linux-modules-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-vserver_2.6.16-18_amd64.deb linux-image-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb linux-modules-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-2.6.16_2.6.16-18_amd64.changes ACCEPTED
Accepted: linux-2.6.16_2.6.16-18.diff.gz to pool/main/l/linux-2.6.16/linux-2.6.16_2.6.16-18.diff.gz linux-2.6.16_2.6.16-18.dsc to pool/main/l/linux-2.6.16/linux-2.6.16_2.6.16-18.dsc linux-doc-2.6.16_2.6.16-18_all.deb to pool/main/l/linux-2.6.16/linux-doc-2.6.16_2.6.16-18_all.deb linux-headers-2.6.16-2-all-amd64_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-all-amd64_2.6.16-18_amd64.deb linux-headers-2.6.16-2-all_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-all_2.6.16-18_amd64.deb linux-headers-2.6.16-2-amd64-generic_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-amd64-generic_2.6.16-18_amd64.deb linux-headers-2.6.16-2-amd64-k8-smp_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-amd64-k8-smp_2.6.16-18_amd64.deb linux-headers-2.6.16-2-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-em64t-p4-smp_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-em64t-p4-smp_2.6.16-18_amd64.deb linux-headers-2.6.16-2-em64t-p4_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-vserver-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-vserver-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-vserver-em64t-p4_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-vserver-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-vserver_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-vserver_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen-vserver_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-vserver_2.6.16-18_amd64.deb linux-headers-2.6.16-2-xen_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen_2.6.16-18_amd64.deb linux-headers-2.6.16-2_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2_2.6.16-18_amd64.deb linux-image-2.6.16-2-amd64-generic_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-amd64-generic_2.6.16-18_amd64.deb linux-image-2.6.16-2-amd64-k8-smp_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-amd64-k8-smp_2.6.16-18_amd64.deb linux-image-2.6.16-2-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-amd64-k8_2.6.16-18_amd64.deb linux-image-2.6.16-2-em64t-p4-smp_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-em64t-p4-smp_2.6.16-18_amd64.deb linux-image-2.6.16-2-em64t-p4_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-em64t-p4_2.6.16-18_amd64.deb linux-image-2.6.16-2-vserver-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-vserver-amd64-k8_2.6.16-18_amd64.deb linux-image-2.6.16-2-vserver-em64t-p4_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-vserver-em64t-p4_2.6.16-18_amd64.deb linux-image-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb linux-image-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb linux-image-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb linux-manual-2.6.16_2.6.16-18_all.deb to pool/main/l/linux-2.6.16/linux-manual-2.6.16_2.6.16-18_all.deb linux-modules-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-modules-2.6.16-2-xen-amd64-k8_2.6.16-18_amd64.deb linux-modules-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-modules-2.6.16-2-xen-em64t-p4_2.6.16-18_amd64.deb linux-modules-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb to pool/main/l/linux-2.6.16/linux-modules-2.6.16-2-xen-vserver-amd64-k8_2.6.16-18_amd64.deb linux-patch-debian-2.6.16_2.6.16-18_all.deb to pool/main/l/linux-2.6.16/linux-patch-debian-2.6.16_2.6.16-18_all.deb linux-source-2.6.16_2.6.16-18_all.deb to pool/main/l/linux-2.6.16/linux-source-2.6.16_2.6.16-18_all.deb linux-support-2.6.16-2_2.6.16-18_all.deb to pool/main/l/linux-2.6.16/linux-support-2.6.16-2_2.6.16-18_all.deb linux-tree-2.6.16_2.6.16-18_all.deb to pool/main/l/linux-2.6.16/linux-tree-2.6.16_2.6.16-18_all.deb Override entries for your package: linux-2.6.16_2.6.16-18.dsc - source devel
Re: linux-2.6: includes nondistributable and non-free binary firmware
Sven Luther wrote: On Thu, Aug 17, 2006 at 10:07:42AM -0700, [EMAIL PROTECTED] wrote: Maks - On Thu, Aug 17, 2006 at 06:05:30PM +0200, maximilian attems wrote: Something about [bug #242866] seems broken, however, because RC-buggy linux-2.6 packages keep making it into testing. Is it obvious how to keep this from happening, without starting a new bug attached to linux-2.6? if you feel like it reassign it, Bugs merged and assigned to linux-2.6. I think the kernel pseudo-package is mostly obsolete: it should be reserved for bugs affecting multiple kernels. This bug doesn't affect freebsd, hurd, etc. It does affect linux-2.4 and linux-2.2, but those are scheduled for removal before etch anyway. So actually, I'd like to suggest running through the bugs against 'kernel' and reassigning them to linux-2.6 or closing them as appropriate. Does that seem like a reasonable thing to do when I'm bored and not feeling up to programming, or would there be some complaint about it. snip anyway if you want to improve the legal situtation use: http://wiki.debian.org/KernelFirmwareLicensing dilinger succeeded in various firmware relicensing thanks to his quest to the vendors. feel free to pick up. Broadcom tg3 relicensing alone took over two years. This is a lovely thing to do, and I am *very very* impressed with dilinger's diligence and his success (I tried but failed to contact anyone at Broadcom). dgrs and qla2xxx are the only other drivers he had *any* success with, according to the wiki page. I am afraid we need a shorter-term solution. For each offending file, there are three possible solutions: 1. Get the author to release source code under a DFSG-free license 2. Move the firmware to non-free, patching the driver to use request_firmware() 3. Delete the driver and firmware entirely. 4. Move the whole friver to non-free, without major patching. 5. Reverse engineer the needed firmware, and create a trully free driver. AFAIK, the best outcome yet from the relicensing discussions on http://wiki.debian.org/KernelFirmwareLicensing is to properly permit the redistribution of the binary, without source code. Indeed, but even that was laughed at back then when we started at it, and you should have seen the reaction of LKML when i mentioned it there. Not to mention the reaction I originally got from the netdev maintainers, which was rather more hostile than being 'laughed at'. I think a lot of people genuinely believed that you could license an unsourced binary under the GPL I can't imagine *why* they believed that, though. snip That's fine for debian non-free, and a necessary step for making option (2) above work properly. Until and unless the entire Linux kernel is moved to non-free, such relicensing doesn't solve the fundamental bug. Indeed. I agree that option (3) is bad, but I still recommend it for the short term. It's the quickest path to a legal and For the short term, 4. is a better solution. Right. If a driver really can't build out-of-tree comfortably, (4) may not be feasible and (3) or (2) may be necessary, but let's cross that bridge if we come to it. What can I do to help with (4)? :-) SC-conforming Linux release, and it will bring people out of the closet to volunteer to work on (2). I think (2) is the actual goal, but maybe not one that can be finished before the proposed etch freeze -- especially since most of the blobs need to be relicensed before they can be made part of firmware-nonfree. Indeed, which is because we could also consider : 6. Pass another GR to allow debian/etch to release as is, provided we If the GR includes a commitment to include a statement regarding this violation of the SC in the *release notes*, then I would be satisfied with this from a freeness point of view: at least Debian would be advertising its failure to live up to the SC. If there is no such commitment, I would expect to see the same charade for etch+1. There's also a problem with Sven's analysis of option (6) relative to options (4) and (2). From a legal point of view, distributing the 'undistributable' (mislicensed) blobs in 'main' and distributing them in 'non-free' is equally bad. If it's OK to distribute them in the kernel package, it's OK to distribute them in 'firmware-nonfree'. It is up to the ftpmasters, the release team, and or the DPL to decide whether they are comfortable with it or not. If they are, then the blobs can be put in firmware-nonfree and (4) is perfectly straightforward. If they are not, then the blobs must be removed from the archive. (6) offers no advantage over (4) with regard to this. (This doesn't affect the non-free blobs which are properly licensed.) commit to a real effort to solve this for etch+1, or better yet, with some pro-active wording, which say we will make every effort to solve this issue, but don't provide timelines and schedules, as upstream will
Bug#383725: linux-image-2.6.16-2-686: cannot halt properly Thinkpad T22
Package: linux-image-2.6.16-2-686 Version: 2.6.16-17 Severity: normal Hello, I see a clear regression here after upgrading from 2.6.15 to 2.6.16. The kernel now doesn't shutdown cleanly the power on my laptop, a IBM Thinkpad T22. It used to work real nice on 2.6.15, but now, the machine just sits there after the Shutting down drives: sda (probably not the exact wording, i don't clearly remember, but it's usually the last thing on the console before the shutdown). I can safely poweroff the machine by pressing the power key for 5 seconds, but it's a bit annoying. Usually, i just suspend to disk this machine, using an ugly hack (echo disk /sys/power/state). This is also affect in that I need to poweroff the same way as a shutdown, ie. by pressing the power key. The machine resumes as normal. Available for debugging/testing with right tools/instructions... a. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-686 depends on: ii initramfs-tools [linux-initra 0.73c tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-686/preinst/bootloader-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-system-map-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/failed-to-move-modules-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/overwriting-modules-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-dir-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-initrd-2.6.16-2-686: false linux-image-2.6.16-2-686/postinst/create-kimage-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/bootloader-test-error-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/removing-running-kernel-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-2.6.16-2-686: false linux-image-2.6.16-2-686/preinst/abort-install-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/bootloader-error-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/kimage-is-a-directory: linux-image-2.6.16-2-686/preinst/abort-overwrite-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/would-invalidate-boot-loader-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/already-running-this-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/elilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/initrd-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/old-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-initrd-2.6.16-2-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
On Fri, Aug 18, 2006 at 04:18:58PM -0700, James Bottomley wrote: That's this fix, isn't it? http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=b2b3c121076961333977f485f0d54c22121df920 Yup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
On Fri, 2006-08-18 at 12:39 -0400, Kyle McMartin wrote: The problem is because they both claim support for the same PCI Ids: That's this fix, isn't it? http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=b2b3c121076961333977f485f0d54c22121df920 James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383249: usplash: add support for user input
I've attached a patch which adds user input support to usplash.
This works by creating a second fifo /dev/.initramfs/usplash_outfifo and
two new commands: INPUT and INPUTQUIET.
Both INPUT and INPUTQUIET take a prompt as argument. The prompt is
written to the usplash screen and then one line of user input is read to
a buffer. If INPUTQUIET has been used, the user input is not echoed to
screen (but '*').
usplash then waits for a reader to be ready on the outfifo or until the
timeout time elapses. If a reader is available, the user input is
written to the fifo from the buffer.
In a initramfs script, something like this would be used:
if [ -p /dev/.initramfs/usplash_outfifo ]; then
usplash_write INPUTQUIET Enter password:
PASS=$(cat /dev/.initramfs/usplash_outfifo)
else
echo -n Enter password:
read PASS
echo
fi
I have tried the patch locally with a slightly modified cryptsetup
initramfs script and it seems to work.
Regards,
David
Index: usplash-0.3e-quilt/usplash.c
===
--- usplash-0.3e-quilt.orig/usplash.c 2006-08-17 21:50:39.0 +0200
+++ usplash-0.3e-quilt/usplash.c2006-08-19 01:54:47.0 +0200
@@ -20,6 +20,7 @@
*/
#include linux/vt.h
+#include linux/limits.h
#include sys/select.h
#include sys/time.h
@@ -59,6 +60,7 @@
static void draw_line (const char *string, size_t len);
static void draw_status (const char *string, size_t len, int mode);
+static int handle_input (const char *string, size_t len, int quiet);
/* Default theme, used when no suitable alternative can be found */
extern struct usplash_theme testcard_theme;
@@ -115,6 +117,14 @@
}
}
+ if (mkfifo (USPLASH_OUTFIFO, S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP) 0) {
+ if (errno != EEXIST) {
+ perror (mkfifo);
+ ret = 1;
+ goto exit;
+ }
+ }
+
fifo_fd = open (USPLASH_FIFO, O_RDONLY|O_NONBLOCK);
if (fifo_fd 0) {
perror (open);
@@ -180,6 +190,9 @@
ioctl (fd, VT_ACTIVATE, vt);
ioctl (fd, VT_WAITACTIVE, vt);
close (fd);
+
+ close (STDIN_FILENO);
+ open (vtname, O_RDONLY);
}
static void
@@ -333,6 +346,12 @@
} else if (! strncmp (command, PROGRESS, commandlen)) {
draw_progressbar (atoi (string));
+
+ } else if (! strncmp (command, INPUT, commandlen)) {
+ return handle_input (string, len, 0);
+
+ } else if (! strncmp (command, INPUTQUIET, commandlen)) {
+ return handle_input (string, len, 1);
}
return 0;
@@ -473,3 +492,75 @@
bogl_text (x1, y1, string, len, fg, theme-text_background,
0, theme-font);
}
+
+static int
+handle_input (const char *string, const size_t len, const int quiet)
+{
+ int i;
+ char input;
+ int x1, y1, x2, y2, xpos;
+ ssize_t wlen;
+ int fifo_outfd;
+ char inputbuf[PIPE_BUF] = ;
+
+ /* some variables which we'll need */
+ x1 = left_edge + theme-text_x;
+ x2 = x1 + theme-text_width;
+
+ y2 = top_edge + theme-text_y + theme-text_height;
+ y1 = y2 - theme-line_height;
+
+ /* draw the prompt */
+ draw_line (string, len);
+ xpos = x1 + bogl_metrics (string, len, theme-font);
+
+ /* Get user input */
+ for (i = 0; i PIPE_BUF - 1; i++) {
+ input = getchar ();
+ if (input == '\n' || input == '\r' || input == '\0')
+ break;
+
+ inputbuf[i] = input;
+
+ if (quiet)
+ input = '*';
+
+ /* Make sure the text doesn't overflow */
+ if (xpos + bogl_metrics (input, 1, theme-font) x2) {
+ bogl_move (x1,
+ top_edge + theme-text_y +
theme-line_height,
+ x1,
+ top_edge + theme-text_y,
+ theme-text_width,
+ theme-text_height - theme-line_height);
+ bogl_clear (x1, y1, x2, y2, theme-text_background);
+ xpos = x1;
+ }
+
+ bogl_text (xpos, y1, input, 1,
+ theme-text_foreground, theme-text_background,
+ 0, theme-font);
+ xpos += bogl_metrics (input, 1, theme-font);
+ }
+ inputbuf[i] = '\0';
+
+ /* We wait for timeout seconds for someone to read the user input */
+ for (i = 1; i != timeout + 1; i++) {
+ fifo_outfd = open (USPLASH_OUTFIFO, O_WRONLY|O_NONBLOCK);
+ if (fifo_outfd 0)
+ sleep(1);
+ else
+ break;
+ }
+
+ if
linux-2.6.16_2.6.16-18_i386.changes ACCEPTED
Accepted: linux-headers-2.6.16-2-486_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-486_2.6.16-18_i386.deb linux-headers-2.6.16-2-686-smp_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-686-smp_2.6.16-18_i386.deb linux-headers-2.6.16-2-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-all-i386_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-all-i386_2.6.16-18_i386.deb linux-headers-2.6.16-2-all_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-all_2.6.16-18_i386.deb linux-headers-2.6.16-2-k7-smp_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-k7-smp_2.6.16-18_i386.deb linux-headers-2.6.16-2-k7_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-vserver-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-vserver-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-vserver-k7_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-vserver-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-vserver_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-vserver_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-k7_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-vserver_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen-vserver_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2-xen_2.6.16-18_i386.deb linux-headers-2.6.16-2_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-headers-2.6.16-2_2.6.16-18_i386.deb linux-image-2.6.16-2-486_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-486_2.6.16-18_i386.deb linux-image-2.6.16-2-686-smp_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-686-smp_2.6.16-18_i386.deb linux-image-2.6.16-2-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-686_2.6.16-18_i386.deb linux-image-2.6.16-2-k7-smp_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-k7-smp_2.6.16-18_i386.deb linux-image-2.6.16-2-k7_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-k7_2.6.16-18_i386.deb linux-image-2.6.16-2-vserver-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-vserver-686_2.6.16-18_i386.deb linux-image-2.6.16-2-vserver-k7_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-vserver-k7_2.6.16-18_i386.deb linux-image-2.6.16-2-xen-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-xen-686_2.6.16-18_i386.deb linux-image-2.6.16-2-xen-k7_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-xen-k7_2.6.16-18_i386.deb linux-image-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-image-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb linux-modules-2.6.16-2-xen-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-modules-2.6.16-2-xen-686_2.6.16-18_i386.deb linux-modules-2.6.16-2-xen-k7_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-modules-2.6.16-2-xen-k7_2.6.16-18_i386.deb linux-modules-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb to pool/main/l/linux-2.6.16/linux-modules-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb Override entries for your package: linux-headers-2.6.16-2-486_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-686-smp_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-686_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-all-i386_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-all_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-k7-smp_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-k7_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-vserver-686_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-vserver-k7_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-vserver_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-xen-686_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-xen-k7_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-xen-vserver_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2-xen_2.6.16-18_i386.deb - optional devel linux-headers-2.6.16-2_2.6.16-18_i386.deb - optional devel linux-image-2.6.16-2-486_2.6.16-18_i386.deb - optional base linux-image-2.6.16-2-686-smp_2.6.16-18_i386.deb - optional base
Processing of linux-2.6.16_2.6.16-18_i386.changes
linux-2.6.16_2.6.16-18_i386.changes uploaded successfully to localhost along with the files: linux-headers-2.6.16-2-all_2.6.16-18_i386.deb linux-headers-2.6.16-2-all-i386_2.6.16-18_i386.deb linux-headers-2.6.16-2_2.6.16-18_i386.deb linux-image-2.6.16-2-486_2.6.16-18_i386.deb linux-headers-2.6.16-2-486_2.6.16-18_i386.deb linux-image-2.6.16-2-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-686_2.6.16-18_i386.deb linux-image-2.6.16-2-686-smp_2.6.16-18_i386.deb linux-headers-2.6.16-2-686-smp_2.6.16-18_i386.deb linux-image-2.6.16-2-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-k7_2.6.16-18_i386.deb linux-image-2.6.16-2-k7-smp_2.6.16-18_i386.deb linux-headers-2.6.16-2-k7-smp_2.6.16-18_i386.deb linux-headers-2.6.16-2-vserver_2.6.16-18_i386.deb linux-image-2.6.16-2-vserver-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-vserver-686_2.6.16-18_i386.deb linux-image-2.6.16-2-vserver-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-vserver-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen_2.6.16-18_i386.deb linux-image-2.6.16-2-xen-686_2.6.16-18_i386.deb linux-modules-2.6.16-2-xen-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-686_2.6.16-18_i386.deb linux-image-2.6.16-2-xen-k7_2.6.16-18_i386.deb linux-modules-2.6.16-2-xen-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-k7_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-vserver_2.6.16-18_i386.deb linux-image-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb linux-modules-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb linux-headers-2.6.16-2-xen-vserver-686_2.6.16-18_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383730: initramfs-tools: incompatible with udev 0.097-1
Package: initramfs-tools Version: 0.75 Severity: important well, happy to try out the shiny new ltsp packages, it seems like there may be an incompatibility with initramfs-tools and the new udev: Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/fan.ko): No such device FATAL: Error inserting thermal (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/thermal.ko): No such device udevd[769]: lookup_group: error resolving group 'disk': No such file or directory udevd[769]: lookup_group: error resolving group 'floppy': Illegal seek udevd[769]: lookup_group: error resolving group 'cdrom': Illegal seek udevd[769]: lookup_group: error resolving group 'tape': Illegal seek with many more similar lines. i tested it with udev 0.093-1 from etch, and that seemed to work just fine. thanks for all your work on initramfs-tools! :) oh, you might want to know i booted using: qemu -hda /dev/zero -m 100 -kernel /opt/ltsp/i386/boot/vmlinuz -initrd \ /opt/ltsp/i386/boot/initrd.img \ -nographic \ -append 'nfsroot=10.0.2.2:/opt/ltsp/i386 root=/dev/nfs ip=dhcp console=ttyS0,38400' live well, vagrant Versions of packages initramfs-tools depends on: ii busybox1.1.3-2Tiny utilities for small and embedded systems ii cpio 2.6-17 GNU cpio -- a program to manage archives of files ii klibc-utils1.4.19-1 small statically-linked utilities built with klibc ii module-init-tools 3.2.2-3tools for managing Linux kernel modules ii udev 0.097-1/dev/ and hotplug management daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383730: initramfs-tools: incompatible with udev 0.097-1
Ditto - udev is calling getpwnam and getgrnam and is failing. I tried adding a hook script to copy my /etc/passwd and /etc/group files to $DESTROOT/etc, but that did no good. I tried adding /etc/ nsswitch.conf as well, but it didn't help either. I'm not sure what to try next. Also, not sure if this is related to udev starting up angrily, but kernel.hotplug no longer getting set properly. My firmware for my wireless driver (acx) won't load unless I do: echo /lib/udev/firmware.agent /proc/sys/kernel/hotplug (or use sysctl) That may be specific to the udev package. Running: initramfs-tools 0.75 udev 0.097-1. custom kernel pkg 2.6.17.7 cheers, nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383725: linux-image-2.6.16-2-686: cannot halt properly Thinkpad T22
On Sat, Aug 19, 2006 at 01:41:09AM +0200, The Anarcat wrote: Available for debugging/testing with right tools/instructions... Can you try the 2.6.17 kernel from sid and see if it improves things? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DMA problems VT8237A chipset (msi board)
On Fri, 18 Aug 2006, dann frazier wrote: On Fri, Aug 18, 2006 at 01:52:59PM +0200, Sven Luther wrote: Any chance this is another incarnation of the now infamous ide-generic bug ? It certainly show the right symptoms for that. Sven, How could Radek confirm this for us? Matthew Garrett pointed out on irc (thanks!) that this chipset just does not have an appropriate PCI ID listed in the driver. Relevant LKML discussion including a patch may be found at http://lkml.org/lkml/2006/8/11/196 Ubuntu has this patch applied already. 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]
Bug#383743: pointer doesn't work
Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: important Upgrading to this kernel version on my HP nc6220 notebook left me with a completely non-working pointer in X. Tried various things, didn't really learn anything useful before getting frustrated and falling back to a prior kernel version, which works fine. Looked like there was no input from the mouse driver at all, though? Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
