Bug#501107: firmware-ralink: missing license file
Package: firmware-ralink
When downloading firmware files directly form ralink website
(http://www.ralinktech.com/ralink/Home/Support/Linux.html)
there is a license file included (file attached), which has
to be included everytime firmware is redistributed.
Not sure if this is also true for firmware from other vendors
(other firmware packages).
The license file should also added to the zip-files available from
http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/.
Kind regards
Holger
Copyright (c) 2007, Ralink Technology Corporation
All rights reserved.
Redistribution. Redistribution and use in binary form, without
modification, are permitted provided that the following conditions are
met:
* Redistributions must reproduce the above copyright notice and the
following disclaimer in the documentation and/or other materials
provided with the distribution.
* Neither the name of Ralink Technology Corporation nor the names of its
suppliers may be used to endorse or promote products derived from this
software without specific prior written permission.
* No reverse engineering, decompilation, or disassembly of this software
is permitted.
Limited patent license. Ralink Technology Corporation grants a world-wide,
royalty-free, non-exclusive license under patents it now or hereafter
owns or controls to make, have made, use, import, offer to sell and
sell ("Utilize") this software, but solely to the extent that any
such patent is necessary to Utilize the software alone, or in
combination with an operating system licensed under an approved Open
Source license as listed by the Open Source Initiative at
http://opensource.org/licenses. The patent license shall not apply to
any other combinations which include this software. No hardware per
se is licensed hereunder.
DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
Bug#501107: marked as done (firmware-ralink: missing license file)
Your message dated Sat, 4 Oct 2008 11:15:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#501107: firmware-ralink: missing license file
has caused the Debian Bug report #501107,
regarding firmware-ralink: missing license file
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
501107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501107
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: firmware-ralink
When downloading firmware files directly form ralink website
(http://www.ralinktech.com/ralink/Home/Support/Linux.html)
there is a license file included (file attached), which has
to be included everytime firmware is redistributed.
Not sure if this is also true for firmware from other vendors
(other firmware packages).
The license file should also added to the zip-files available from
http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/.
Kind regards
Holger
Copyright (c) 2007, Ralink Technology Corporation
All rights reserved.
Redistribution. Redistribution and use in binary form, without
modification, are permitted provided that the following conditions are
met:
* Redistributions must reproduce the above copyright notice and the
following disclaimer in the documentation and/or other materials
provided with the distribution.
* Neither the name of Ralink Technology Corporation nor the names of its
suppliers may be used to endorse or promote products derived from this
software without specific prior written permission.
* No reverse engineering, decompilation, or disassembly of this software
is permitted.
Limited patent license. Ralink Technology Corporation grants a world-wide,
royalty-free, non-exclusive license under patents it now or hereafter
owns or controls to make, have made, use, import, offer to sell and
sell ("Utilize") this software, but solely to the extent that any
such patent is necessary to Utilize the software alone, or in
combination with an operating system licensed under an approved Open
Source license as listed by the Open Source Initiative at
http://opensource.org/licenses. The patent license shall not apply to
any other combinations which include this software. No hardware per
se is licensed hereunder.
DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
--- End Message ---
--- Begin Message ---
On Sat, Oct 04, 2008 at 09:23:33AM +0200, Holger Wansing wrote:
> When downloading firmware files directly form ralink website
> (http://www.ralinktech.com/ralink/Home/Support/Linux.html)
> there is a license file included (file attached), which has
> to be included everytime firmware is redistributed.
The license is located in the same location then every other package,
/usr/share/doc/$package/copyright.
> The license file should also added to the zip-files available from
> http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/.
This is not the firmware package.
Bastian
--
There are certain things men must do to remain men.
-- Kirk, "The Ultimate Computer", stardate 4929.4
--- End Message ---
Bug#501118: linux-image-2.6.26-1-686: Thinkpad i1300/1310: kernel panic on boot
Package: linux-image-2.6.26-1-686 Version: 2.6.26-5 Severity: important Several attempts to boot into a newly installed linux-image-2.6.26-1-686 resulted in a screen full of mostly hex gibberish followed by "kernel panic". I would be happy to type in that whole screen of hex if anyone is interested in seeing it. $ lspci 00:00.0 Host bridge: Intel Corporation 82440MX Host Bridge (rev 01) 00:00.1 Multimedia audio controller: Intel Corporation 82440MX AC'97 Audio Controller 00:00.2 Modem: Intel Corporation 82440MX AC'97 Modem Controller 00:02.0 VGA compatible controller: Silicon Motion, Inc. SM712 LynxEM+ (rev a0) 00:03.0 CardBus bridge: O2 Micro, Inc. OZ6812 CardBus Controller (rev 05) 00:07.0 ISA bridge: Intel Corporation 82440MX ISA Bridge (rev 01) 00:07.1 IDE interface: Intel Corporation 82440MX EIDE Controller 00:07.2 USB Controller: Intel Corporation 82440MX USB Universal Host Controller 00:07.3 Bridge: Intel Corporation 82440MX Power Management Controller -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92j tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-13 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii grub 0.97-47GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 (no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501079: marked as done (linux-image-2.6.26-1-686: Huge Memory leak in Debian running 2.6.28-1-686)
Your message dated Sat, 4 Oct 2008 12:29:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#501079: linux-image-2.6.26-1-686: Huge Memory leak in
Debian running 2.6.28-1-686
has caused the Debian Bug report #501079,
regarding linux-image-2.6.26-1-686: Huge Memory leak in Debian running
2.6.28-1-686
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
501079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501079
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-686
Version: 2.6.26-6
Severity: important
I've noticed that with Debian I am using excessive amounts of memory.
Far beyond anything I've noticed before.
For example on my Debian testing machine running the 'free -m' command
gives me this:
total used free sharedbuffers
cached
Mem: 1011965 46 0 25
204
-/+ buffers/cache:734276
Swap: 1608 0 1608
So 734MB of RAM is excessive for a bog standard Gnome desktop, which
should be using about 200MB, if that. No Beagle or Tomboy or anything
like that running, just the default Gnome install.
Running this simple script:
export total=0
ps ax -o rss | while read i
do
let "total = $total + $i"
let "human = $total / 1024"
echo ${human}
done
Yeilds a total of about: 257MB
After logging out of X Windows and shutting GDM down completely I still
get a result of:
48 for that command
and free -m is:
total used free sharedbuffers
cached
Mem: 1011891120 0 26
203
-/+ buffers/cache:662349
Swap: 1608 0 1608
I have two Debian machines I've noticed this on. One is tracking Lenny
and the other is Sid. Both are running Gnome desktops and not really
doing much else. I recently rebooted the Sid machine so I don't have
statistics on that one, but I began to notice excessive memory usage
after several hours uptime.
The uptime for the machine used to generate the above commands is:
17:14:31 up 1 day, 1:30, 1 user, load average: 0.02, 0.07, 0.06
Now there is a third machine running 2.6.26-1-486 that I have that
doesn't seem to have this problem. (it's a Via machine which is
incompatible with 686 kernels) It's running services for me, without
a GUI, and have had several weeks of uptime and is only showing 86MB
memory usage. I am not sure what the deal is on that one; it could be
running a stale kernel version or something.
I am suspecting that it may have something to do with video memory
management as the GUI seems the major difference between the machines,
and my main Sid desktop seems to gather excessive amounts of RAM quite
quickly when running Compiz. (usually I just run Metacity, as I was last
time I noticed this issue coming up).
I don't know this though.. it's just a guess. My main Sid machine has a
Intel X3100 video card, while the Lenny machine is running a old
Geforce4 MX 4 using the open source 'nv' drivers.
cat /proc/meminfo reveals:
MemTotal: 1036040 kB
MemFree:122204 kB
Buffers: 26952 kB
Cached: 209100 kB
SwapCached: 0 kB
Active: 108276 kB
Inactive: 138020 kB
HighTotal: 131008 kB
HighFree:48356 kB
LowTotal: 905032 kB
LowFree: 73848 kB
SwapTotal: 1646620 kB
SwapFree: 1646620 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 10260 kB
Mapped: 9844 kB
Slab: 660208 kB
SReclaimable: 655028 kB
SUnreclaim: 5180 kB
PageTables:584 kB
NFS_Unstable:0 kB
Bounce: 0 kB
WritebackTmp:0 kB
CommitLimit: 2164640 kB
Committed_AS:86320 kB
VmallocTotal: 114680 kB
VmallocUsed: 3232 kB
VmallocChunk: 72 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 4096 kB
cat /proc/slabinfo reveals:
slabinfo - version: 2.1
# name
# : tunables:
# slabdata
fib6_nodes 6113 32 1131 : tunables 120 60
8 : slabdata 1 1 0
ip6_dst_cache 5 15256 151 : tunables 120 60
8 : slabdata 1 1 0
ndisc_cache2 15256 151 : tunables 120 60
8 : slabdata 1 1 0
ip6_mrt_cache 0 0128 301 : tunables 120 60
8 : slabdata 0 0 0
RAWv6 5 576851 : tunables 54 27
8 : slabdata 1 1
Processed: foo
Processing commands for [EMAIL PROTECTED]: > reassign 500992 linux-image-2.6-686 Bug#500992: hylafax-server: hylafax and ELSA USB 56k: modem "crashes" remaining on-hook Bug reassigned from package `hylafax-server' to `linux-image-2.6-686'. > retitle 500992 Communication with USB-Modem (cdc-acm) hangs the modem > (Kernel 2.2.26) Bug#500992: hylafax-server: hylafax and ELSA USB 56k: modem "crashes" remaining on-hook Changed Bug title to `Communication with USB-Modem (cdc-acm) hangs the modem (Kernel 2.2.26)' from `hylafax-server: hylafax and ELSA USB 56k: modem "crashes" remaining on-hook'. > 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#500992: linux-image-2.6-686: further information on my installed packages
Package: linux-image-2.6-686 Version: 2.6.26+16 Followup-For: Bug #500992 This one is only to provide information about the afffected hardware in a well known format. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.26-1-686 2.6.26-5 Linux 2.6.26 image on PPro/Celeron linux-image-2.6-686 recommends no packages. linux-image-2.6-686 suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500992: hylafax-server: hylafax and ELSA USB 56k: modem "crashes" remaining on-hook
I am going to flood the system with more debugging information :-\ Sebastian Niehaus <[EMAIL PROTECTED]> writes: > I am now sure it is *not* a hylafay problem but a kernel problem. When > I booted the box with the 2.6.18 Kernel (Etch) Hylafax worked fine. Since I have two USB controller I tried them both: ,[ lspci -v ] | | [...] | | | 00:04.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) | Flags: bus master, medium devsel, latency 48, IRQ 19 | I/O ports at ff00 [size=32] | Kernel driver in use: uhci_hcd | Kernel modules: uhci-hcd | | | [...] | | | | 00:0f.0 USB Controller: NEC Corporation USB (rev 43) (prog-if 10) | Subsystem: DTK Computer Device 0105 | Flags: bus master, medium devsel, latency 64, IRQ 19 | Memory at f6ef6000 (32-bit, non-prefetchable) [size=4K] | Capabilities: [40] Power Management version 2 | Kernel driver in use: ohci_hcd | Kernel modules: ohci-hcd | | 00:0f.1 USB Controller: NEC Corporation USB (rev 43) (prog-if 10) | Subsystem: DTK Computer Device 0105 | Flags: bus master, medium devsel, latency 64, IRQ 16 | Memory at f6ef7000 (32-bit, non-prefetchable) [size=4K] | Capabilities: [40] Power Management version 2 | Kernel driver in use: ohci_hcd | Kernel modules: ohci-hcd | | 00:0f.2 USB Controller: NEC Corporation USB 2.0 (rev 04) (prog-if 20) | Subsystem: DTK Computer Device 0205 | Flags: bus master, medium devsel, latency 128, IRQ 17 | Memory at f6ef2e00 (32-bit, non-prefetchable) [size=256] | Capabilities: [40] Power Management version 2 | Kernel driver in use: ehci_hcd | Kernel modules: ehci-hcd | | | [...] | ` It does not matter where the modem is plugged in, it keeps crashing. Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Handling of linux-modules-*-2.6 during freeze
Hi folks linux-modules-*-2.6 also produces a source-availability problem, they use source including binary packages from unstable to build binary packages. In unstable this is usualy no problem as we ship the source in at least one variant. For the packages in testing this can be a problem, escpecially during freeze. This problem popped up now because virtualbox-ose got a new upstream version in unstable which is not meant to be included in Lenny. For a short-term fix I only see three solutions: - Continue to upload to unstable, drop virtualbox modules. - Upload to testing-proposed-updates. - Let virtualbox-ose into Lenny. I don't like the variants 2 and 3 but I would use number 2 if the release team agrees. As d-i repacks this packages into udebs, they need to know about that also. Bastian -- Military secrets are the most fleeting of all. -- Spock, "The Enterprise Incident", stardate 5027.4 signature.asc Description: Digital signature
Re: Handling of linux-modules-*-2.6 during freeze
Bastian Blank wrote: > Hi folks > > linux-modules-*-2.6 also produces a source-availability problem, they > use source including binary packages from unstable to build binary > packages. In unstable this is usualy no problem as we ship the source in > at least one variant. For the packages in testing this can be a problem, > escpecially during freeze. > > This problem popped up now because virtualbox-ose got a new upstream > version in unstable which is not meant to be included in Lenny. As this is the problem, this is where it needs to be solved... > For a short-term fix I only see three solutions: > - Continue to upload to unstable, drop virtualbox modules. > - Upload to testing-proposed-updates. > - Let virtualbox-ose into Lenny. None of these look really good to me. Another solution would be a reupload of 1.6.2-dfsg-6 with a higher version than currently in unstable. Cc-ed the maintainers so they can comment. Please let them first the opportunity to react and explain how they see it. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: unblock request for firmware-nonfree_0.13
dann frazier wrote: > hey, > I've just uploaded firmware-nonfree 0.13. It resolves 2 RC bugs: > 494936 - bnx2 fails to load on bootup, succeeds on manul load > 500692 - FTBFS: depends on linux-support-2.6.25-2 > And one 'normal' one (that should be bumped to important, imo): > 494703 - iwl3945: Microcode SW Error detected unblocked Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Handling of linux-modules-*-2.6 during freeze
On Sat, Oct 04, 2008 at 02:58:47PM +0200, Luk Claes wrote: > Bastian Blank wrote: > > For a short-term fix I only see three solutions: > > - Continue to upload to unstable, drop virtualbox modules. > > - Upload to testing-proposed-updates. > > - Let virtualbox-ose into Lenny. > None of these look really good to me. Another solution would be a > reupload of 1.6.2-dfsg-6 with a higher version than currently in unstable. This may produce another bunch of problems with the version generation in the linux-modules-* packages which I currently don't want to find out. It works now, and I'm glad that it works. What I don't want is to introduce another variable like epochs just for fun. Bastian -- Captain's Log, star date 21:34.5... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Handling of linux-modules-*-2.6 during freeze
Otavio Salvador wrote: > Bastian Blank <[EMAIL PROTECTED]> writes: > >> On Sat, Oct 04, 2008 at 02:58:47PM +0200, Luk Claes wrote: >>> Bastian Blank wrote: For a short-term fix I only see three solutions: - Continue to upload to unstable, drop virtualbox modules. - Upload to testing-proposed-updates. - Let virtualbox-ose into Lenny. >>> None of these look really good to me. Another solution would be a >>> reupload of 1.6.2-dfsg-6 with a higher version than currently in unstable. >> This may produce another bunch of problems with the version generation >> in the linux-modules-* packages which I currently don't want to find >> out. It works now, and I'm glad that it works. What I don't want is to >> introduce another variable like epochs just for fun. > > In this case I think t-p-u is the best alternative and I agree that if > the version generation code doesn't this support up to now, this is > too late to add it. t-p-u is not the best alternative IMHO, we're not talking about some package (linux-modules-*2.6) we can easily take out of the release if it breaks without harming lots of users... Either we remove virtualbox-ose from the release or we accept the version in unstable AFAICS, though as I asked before, please let the maintainers comment... Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501134: RAW-pictures break down after copied on a crypted raid5
Package: linux-image-2.6.24-etchnhalf.1-486 Version: ? Hello, I have an extra-ordinary problem or perhaps an Kernel bug: My Server: * Debian Etch (Kernel: Etch-n-half), Samba 3.0.24 * 500gb harddisk with a system and a data partition. Both are crypted with Luks (cipher:serpent-cbc-essiv:sha256) * Raid 5 crypted with Luks (cipher: serpent-cbc-essiv:sha256) * All partitions have the ext3 filesystem Client1: Notebook (Windows XP and Fedora) Client2: Desktop (Fedora) I did all tests from both clients My problem: I tried to copy RAW pictures (*.cr2 files) from a client to the raid5 partition with the following 4 different ways. 1. I exported the raid partition with samba and copied the pictures with Windows XP and the Windows Explorer 2. I copied the pictures through an smb-mount with Fedora with the "cp"-command 3. I copied the pictures with the "scp"-command (first initiiated from the client and then from the server) 4. I copied the pictures with the "rsync"-command (first initiiated from the client and then from the server) I checked the files after I had copied them with "md5sum" and I saw that the values where different to the values of the original files. The pictures where broken. They had lila stribes and where cutted in the half. I tried the same 4 methods and copied the pictures on the 500gb data partition and there where no failures or md5sum differences. Then I copied the pictures in an ssh shell with an normal cp-command from the local-partition to the raid5-partition. The md5sum values where the same, so this worked well. So in my opinion the problem has to do with the crypted raid5. I tried to reproduce this failures with other files but i had this problem only with RAW (*.cr2 Canon) picture files. I tried to repair my system with these 3 Methods: 1. fsck.ext3 -y /dev/mapper/md0_crypt 2. fsck.ext3 -c -p /dev/mapper/md0_crypt 3. server rebooted a few times I couldn't find out any failure messages in the log-files or at the booting. After many hours I found this out: With Kernel 2.6.24-etchnhalf.1-686, Kernel 2.6.24-etchnhalf.1-486 and Kernel 2.6.26-bpo.1-486 I could reproduce my Image-copy-problem. As I booted the older Kernel 2.6.18-6-486 I where able to copy the pictures with any of the methods above and the md5sum values where OK. Because of this I think its an Kernel problem. I absolutly don't know what additional information I should post with this E-Mail, please write me what I should add or where I should post the extra-information. Sorry if I addressed this E-Mail wrong, I don't know where to go with this problem/bug. With bug-buddy I weren't able to make a Bug-Report. Nice regards Daniel ### ### Server Systeminformation : Debian Etch with different Kernels: 2.6.24-etchnhalf.1-686, Kernel 2.6.24-etchnhalf.1-486, Kernel 2.6.26-bpo.1-486, Kernel 2.6.18-6-486 Kernel 2.6.18-6-486 installed with the Installation-setup from the debian stable cd. the others with apt-get install from the source: deb http://www.backports.org/debian etch-backports main contrib non-free # ls -l /lib/libc.so.6 /lib/libc.so.6 -> libc-2.3.6.so # lspci -v 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Subsystem: ASUSTeK Computer Inc. Unknown device 80ac Flags: bus master, 66MHz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) [size=128M] Capabilities: [40] AGP version 3.0 Capabilities: [60] HyperTransport: Host or Secondary Interface 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 0 (rev c1) Subsystem: nVidia Corporation Unknown device 0c17 Flags: 66MHz, fast devsel 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) Subsystem: nVidia Corporation Unknown device 0c17 Flags: 66MHz, fast devsel 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) Subsystem: nVidia Corporation Unknown device 0c17 Flags: 66MHz, fast devsel 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) Subsystem: nVidia Corporation Unknown device 0c17 Flags: 66MHz, fast devsel 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) Subsystem: nVidia Corporation Unknown device 0c17 Flags: 66MHz, fast devsel 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [48] HyperTransport: Slave or Primary Interface 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 0c11 Flags: 66MHz, fast devsel, IRQ 255 I/O ports at c400 [size=32] Capabilities: [44] Power
Re: Handling of linux-modules-*-2.6 during freeze
Bastian Blank <[EMAIL PROTECTED]> writes: > On Sat, Oct 04, 2008 at 02:58:47PM +0200, Luk Claes wrote: >> Bastian Blank wrote: >> > For a short-term fix I only see three solutions: >> > - Continue to upload to unstable, drop virtualbox modules. >> > - Upload to testing-proposed-updates. >> > - Let virtualbox-ose into Lenny. >> None of these look really good to me. Another solution would be a >> reupload of 1.6.2-dfsg-6 with a higher version than currently in unstable. > > This may produce another bunch of problems with the version generation > in the linux-modules-* packages which I currently don't want to find > out. It works now, and I'm glad that it works. What I don't want is to > introduce another variable like epochs just for fun. In this case I think t-p-u is the best alternative and I agree that if the version generation code doesn't this support up to now, this is too late to add it. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - "Microsoft sells you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Handling of linux-modules-*-2.6 during freeze
Luk Claes wrote: > t-p-u is not the best alternative IMHO, we're not talking about some > package (linux-modules-*2.6) we can easily take out of the release if it > breaks without harming lots of users... ack. > Either we remove virtualbox-ose from the release or we accept the > version in unstable AFAICS, though as I asked before, please let the > maintainers comment... it was stupid to upload 1.6.6 to unstable, however, the the only sane thing imho is, to unblock vbox and let that vesion into lenny. the version should be fine. everything else is even more a hassle. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494444: kacpid is in uninteruptible sleep and produces loads >1
On Thu, Oct 02, 2008 at 09:38:22AM +0200, Nicolas Duboc wrote: > Hi, > > I confirm this bug. Upgrading from 2.6.25-2 to 2.6.26-1 caused kacpi > and kacpi_notify processes to use more tha 75% of my CPU. My laptop is a > Dell Precision M70. I made more tests with version 2.6.26-7 of linux-image-2.6.26-1-686. The problem actually only appears after the system is resumed after a suspend-to-ram cycle. The problem doesn't appear if the system is freshly booted from scratch. -- Nicolas Duboc <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Bug#479709: release-notes: Please document kernel 2.6.25+/chrony issue
Hi Can you please provide a proposed text (license: GPL v2) about the issue mentioned in bug #479709 for inclusion in the release notes? Thanks already. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Handling of linux-modules-*-2.6 during freeze
Daniel Baumann wrote: > Luk Claes wrote: >> t-p-u is not the best alternative IMHO, we're not talking about some >> package (linux-modules-*2.6) we can easily take out of the release if it >> breaks without harming lots of users... > > ack. > >> Either we remove virtualbox-ose from the release or we accept the >> version in unstable AFAICS, though as I asked before, please let the >> maintainers comment... > > it was stupid to upload 1.6.6 to unstable, however, the the only sane > thing imho is, to unblock vbox and let that vesion into lenny. the > version should be fine. everything else is even more a hassle. Ok, unblocked. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498021: This problem is common on Eeepc
At least on Asus Eeepc 701, the SD card reader seems not a true SDHC reader. But it works with the default OS. It even has worked on mine two times, I don't know why it suddenly breaks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500265: linux-image-2.6.26-1-686: Hangs after an apparently random uptime (minutes)
Il lunedì 29 settembre 2008 18:48:45 Salvo Isaja ha scritto: > For a couple of days I run my network connection over cable instead > of using the USB dongle. It seems that the system is much stabler > without the rt73usb module: I'm able to run 2.6.26 for much longer > time, but it may be a coincidence. I confirm that was a coincicence: the system hanged the same way independently of the rt73usb module, sorry for the misleading information. > > There are several reports of hangs with 2.6.26. Did you test the > > workarounds mentioned there? (Mostly hpet=disable). > > I'll try to disable the HPET as soon as I check that the problem is > repeatable (so that I can tell whether it is workarounding the HPET > that solves the problem). After a few days of (unfortunately short) testing, I feel rather comfortable to say that hpet=disable workarounds the problem. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Handling of linux-modules-*-2.6 during
Michael Meskes wrote: >> it was stupid to upload 1.6.6 to unstable, however, the the only sane > > Which of course is easy to say in hindsight. I do not remember seeing a > similar > statement before the upload. how suprising is that when the upload was made by patrick without prior discussion/announcement/communication/$whatever on the list. however, as indicated already, past is past. > This btw is also the reason why it > was uploaded to sid. After all it fixes some bugs. for the records: the new upstream version only fixes two bugs: #495028 which is a cosmetic thing and not worth the trouble, and #499623 which is absolutely unimportant - 2.6.27 is post lenny anyway. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Handling of linux-modules-*-2.6 during
> it was stupid to upload 1.6.6 to unstable, however, the the only sane Which of course is easy to say in hindsight. I do not remember seeing a similar statement before the upload. Besides I agree that virtualbox-ose 1.6.6 should move into Lenny because upstream considers this a bugfix release. This btw is also the reason why it was uploaded to sid. After all it fixes some bugs. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Handling of linux-modules-*-2.6 during
On Sat, Oct 04, 2008 at 08:33:01PM +0200, Daniel Baumann wrote: > how suprising is that when the upload was made by patrick without prior > discussion/announcement/communication/$whatever on the list. Right no discussion from noone. So we are all at fault somehow. > however, as indicated already, past is past. Agreed. > > This btw is also the reason why it > > was uploaded to sid. After all it fixes some bugs. > > for the records: the new upstream version only fixes two bugs: #495028 > which is a cosmetic thing and not worth the trouble, and #499623 which > is absolutely unimportant - 2.6.27 is post lenny anyway. Yes, in terms of Debian bugs. But it does close a lot of upstream bugs. Granted they weren't reported for Debian but they were available in Debian too. Therefore I think the release team's decision to unblock 1.6.6 is the best scenarion anyway. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-virtualbox-devel] Handling of linux-modules-*-2.6 during
On Saturday 04 October 2008, Michael Meskes wrote: > > > This btw is also the reason why it > > > was uploaded to sid. After all it fixes some bugs. > > > > for the records: the new upstream version only fixes two bugs: #495028 > > which is a cosmetic thing and not worth the trouble, and #499623 which > > is absolutely unimportant - 2.6.27 is post lenny anyway. > > Yes, in terms of Debian bugs. But it does close a lot of upstream bugs. > Granted they weren't reported for Debian but they were available in Debian > too. Therefore I think the release team's decision to unblock 1.6.6 is the > best scenarion anyway. I strongly agree to Michael, please use 1.6.6 in Lenny if somehow possible. Thanks, Frank -- Dr.-Ing. Frank MehnertSun Microsystemshttp://www.sun.com/ signature.asc Description: This is a digitally signed message part.
Bug#501149: tgt: not fit for release
Package: tgt Version: 20070924-1 Severity: Serious Hello, this package needs a major update from upstream sources, which unfortunately are not in releaseable state yet. Best regards Frederik Schüler -- ENOSIG signature.asc Description: This is a digitally signed message part.
Bug#501152: binary firmware in drivers/net/starfire_firmware.h
Package: linux-2.6
Version: 2.6.26-5
Severity: serious
Hi,
drivers/net/starfire_firmware.h (licensed under GPLv2) is entirely composed
of binary firmware, such as:
static const u32 firmware_rx[] = {
0x010003dc, 0x,
0x04000421, 0x0086,
[...]
It's worth noting that the last chunk is #ifdef'ed out and not actually
used for anything.
Since this file is licensed under GPL, this could make it illegal to
redistribute it.
In either case, the presence of source-less binary code is a violation
of DFSG #2 requirement for source code availability.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501153: binary firmware in drivers/net/tehuti_fw.h
Package: linux-2.6
Version: 2.6.26-5
Severity: serious
Hi,
drivers/net/tehuti_fw.h (licensed under GPLv2+) is entirely composed of
binary firmware, such as:
static u32 s_firmLoad[] = {
0x000f0002,
0x40718000,
[...]
Since this file is licensed under GPL, this could make it illegal to
redistribute it.
In either case, the presence of source-less binary code is a violation
of DFSG #2 requirement for source code availability.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501157: linux-image-2.6.26: New Intel Wifi Link 5100 and 5300.
Package: linux-image-2.6.26-1-686 Version: 2.6.26-5 Severity: wishlist Hello, Intel has a new wireless chipset. Laptops with those chipset are currently hitting the market, and we can assume they will replace the 3965/4965 soon. Are there any plan (and any chance) to have them supported in Lenny ? It seems that the driver is getting merged in upstream kernel 2.6.27. On August 13, 2008 Tomas Winkler Wrote (on linux-kernel[1] ): > Intel would like to announce Linux support for Wifi Link 5000 and > 5100 Series Adapters under iwlwifi driver (iwlagn.ko) > > The Intel(R) WiFi Link 5100 Series and 5300 is a families of IEEE > 802.11a/b/g/Draft-N1 wireless network > adapters that operate in both the 2.4 GHz and 5.0 GHz spectra. These > adapters, available > in both PCIe* Mini Card and Half Mini Card form factor > 5100 1x2 MIMO up to 300Mbps > 5300 3x3 MIMO up to 450Mbps A summary of this discussion will be available in the wiki page : http://wiki.debian.org/iwlwifi Thanks, Franklin -- [1] http://marc.info/?l=linux-wireless&m=121866189316587&w=2 For reference, the models supported by iwl5000: > 8086:4232 Wifi Link 5100 Wireless Adapter > 8086 1201 5100ABGN Mini Card > 8086 1205 5100BG Mini Card > 8086 1206 5100ABG Mini Card > 8086 1301 5100ABGN Half Mini Card > 8086 1305 5100BG Half Mini Card > 8086 1306 5100ABG Half Mini Card > 8086 1321 5100ABGN Half Mini Card Dell > 8086 1326 5100ABG Half Mini Card Dell > 8086:4235 Wifi Link 5300 Wireless Adapter > 8086 1001 5300ABGN Mini Card > 8086 1101 5300ABGN Half Mini Card > 8086 1121 5300ABGN Half Mini Card Dell > 8086:4236 Wifi Link 5300 Wireless Adapter > 8086 1011 5300ABGN Mini Card Lenovo > 8086:4237 Wifi Link 5100 Wireless Adapter > 8086 1211 5100ABGN Mini Card Lenovo > 8086 1216 5100ABG Mini Card Lenovo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
