[patch] SB600/SB700/SB800 use same SMBus controller devID

Greetings: We find that SB700 and SB800 use the same SMBus device ID as SB600, which is 0x4385, instead of the already submitted 0x4395. Please apply the attached new SMBus patch, which can remove the wrong applied SB700 SMBus patch submitted before:

bzImage

what is the diffrence of bzImage with other normal kernel images? Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search

Re: bzImage

[ stripped stupid cc list ] first of all don't cross post. second check the sources. third google. On Wed, Aug 15, 2007 at 01:05:34AM -0700, Sameer Rahmani wrote: what is the diffrence of bzImage with other normal kernel images? fourth ask on kernelnewbies kernel list if you didn't find an

Bug#429622: AMD/ATI SB700 support to Debian

Hi Dann: The Snapshots Status: http://stats.buildserver.net/packages/status.php?email=debian-kernelpac kages=arches=subdist=kernel-dists also marked many Failed to kernel 2.6.18.dfsg.1-14~snapshot.9251 Is there some problem in the kernel version 2.6.18.dfsg.1-14~snapshot.9249 and

Bug#438086: No bigmem support in linux-image-vserver-686

Package: linux-image-vserver-686 Version: 2.6.18+6 Severity: important linux-image-vserver package does not provide bigmem support, hardware with 4G or more RAM are not fully utilized. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture:

Bug#438104: firmware-iwlwifi: Dependencies on 2.6.22 maybe ?

Package: firmware-iwlwifi Version: 0.7 Severity: normal Hello. Maybe I'm wrong, but I think this firmware requires the mac80211 module to be loaded, which in turn is only available in kernel 2.6.22 in Debian. I think the dependencies for this package should then reflect this. Feel free to

Processed: Re: Bug#438086: No bigmem support in linux-image-vserver-686

Processing commands for [EMAIL PROTECTED]: severity 438086 wishlist Bug#438086: No bigmem support in linux-image-vserver-686 Severity set to `wishlist' from `important' reassign 438086 linux-2.6 Bug#438086: No bigmem support in linux-image-vserver-686 Bug reassigned from package

Bug#438086: No bigmem support in linux-image-vserver-686

severity 438086 wishlist reassign 438086 linux-2.6 retitle 438086 linux-2.6 - please support vserver on i386-pae thanks On Wed, Aug 15, 2007 at 02:37:41PM +0300, Enver ALTIN wrote: linux-image-vserver package does not provide bigmem support, hardware with 4G or more RAM are not fully utilized.

Bug#429622: AMD/ATI SB700 support to Debian

On Wed, Aug 15, 2007 at 07:43:47PM +0800, Shane Huang wrote: Hi Dann: The Snapshots Status: http://stats.buildserver.net/packages/status.php?email=debian-kernelpac kages=arches=subdist=kernel-dists also marked many Failed to kernel 2.6.18.dfsg.1-14~snapshot.9251 Is there some

Bug#438144: linux-image-2.6.21-2-686: new kernel does not like my ATI Rage 128 card

Package: linux-image-2.6.21-2-686 Version: 2.6.21-6 Severity: important I normally use a self-compiled kernel, but keep a debian kernel around. After booting into the 2.6.21-2-686 kernel, X wouldn't start (log file below). This problem does not occur with my self-compiled 2.6.21 kernel (from

Bug#438144: linux-image-2.6.21-2-686: new kernel does not like my ATI Rage 128 card

tags 438144 moreinfo stop On Wed, Aug 15, 2007 at 11:11:48AM -0500, Itai Seggev wrote: I normally use a self-compiled kernel, but keep a debian kernel around. After booting into the 2.6.21-2-686 kernel, X wouldn't start (log file below). This problem does not occur with my self-compiled

Processed: Re: Bug#438144: linux-image-2.6.21-2-686: new kernel does not like my ATI Rage 128 card

Processing commands for [EMAIL PROTECTED]: tags 438144 moreinfo Bug#438144: linux-image-2.6.21-2-686: new kernel does not like my ATI Rage 128 card There were no tags set. Tags added: moreinfo stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking

Re: [patch] SB600/SB700/SB800 use same SMBus controller devID

On Wed, Aug 15, 2007 at 02:58:41PM +0800, Shane Huang wrote: Greetings: We find that SB700 and SB800 use the same SMBus device ID as SB600, which is 0x4385, instead of the already submitted 0x4395. Please apply the attached new SMBus patch, which can remove the wrong applied SB700 SMBus

Bug#438165: linux-image-2.6.18-4-vserver-686: NULL pointer dereference in dev_in_nx_info

Package: linux-image-2.6.18-4-vserver-686 Severity: normal The bug looks like this: BUG: unable to handle kernel NULL pointer dereference at virtual address 00ac printing eip: c0132f84 *pde = Oops: [#1] SMP

Bug#438165: patch

This issue is fixed by: http://people.linux-vserver.org/~dhozac/p/k/delta-NULL-dev-fix01.diff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

initramfs-tools_0.85h_i386.changes INSTALLED into stable

Installing: initramfs-tools_0.85h.dsc to pool/main/i/initramfs-tools/initramfs-tools_0.85h.dsc initramfs-tools_0.85h.tar.gz to pool/main/i/initramfs-tools/initramfs-tools_0.85h.tar.gz initramfs-tools_0.85h_all.deb to pool/main/i/initramfs-tools/initramfs-tools_0.85h_all.deb Override

linux-modules-contrib-2.6_2.6.18-4+etch2_sparc.changes INSTALLED into stable

Installing: ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb to

linux-2.6_2.6.18.dfsg.1-13_sparc.changes INSTALLED into stable

Installing: linux-2.6_2.6.18.dfsg.1-13.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-13.diff.gz linux-2.6_2.6.18.dfsg.1-13.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-13.dsc linux-doc-2.6.18_2.6.18.dfsg.1-13_all.deb to

linux-latest-2.6_6etch1_ia64.changes INSTALLED into stable

Installing: kernel-image-2.6-itanium-smp_2.6.18+6etch1_ia64.deb to pool/main/l/linux-latest-2.6/kernel-image-2.6-itanium-smp_2.6.18+6etch1_ia64.deb kernel-image-2.6-itanium_2.6.18+6etch1_ia64.deb to pool/main/l/linux-latest-2.6/kernel-image-2.6-itanium_2.6.18+6etch1_ia64.deb

Bug#412132: marked as done (cacct interface misscalced about 100 TB)

Your message dated Wed, 15 Aug 2007 22:37:44 + with message-id [EMAIL PROTECTED] and subject line Bug#412132: fixed in linux-2.6 2.6.18.dfsg.1-13 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

linux-modules-nonfree-2.6_2.6.18-4etch1_i386.changes INSTALLED into stable

Installing: kqemu-modules-2.6-486_2.6.18-4etch1_i386.deb to pool/non-free/l/linux-modules-nonfree-2.6/kqemu-modules-2.6-486_2.6.18-4etch1_i386.deb kqemu-modules-2.6-686-bigmem_2.6.18-4etch1_i386.deb to

linux-modules-extra-2.6_2.6.18-7+etch3_sparc.changes INSTALLED into stable

Installing: linux-modules-extra-2.6_2.6.18-7+etch3.dsc to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.18-7+etch3.dsc linux-modules-extra-2.6_2.6.18-7+etch3.tar.gz to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.18-7+etch3.tar.gz

Bug#418977: marked as done (initramfs-tools: Missing esp.ko module for SCSI controller on Sparc)

Your message dated Wed, 15 Aug 2007 22:32:17 + with message-id [EMAIL PROTECTED] and subject line Bug#418977: fixed in initramfs-tools 0.85h 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

Bug#412957: marked as done (linux-source-2.6.18: UML ARCH=um compile fails with CONFIG_MODE_TT=y (regression))

Your message dated Wed, 15 Aug 2007 22:37:44 + with message-id [EMAIL PROTECTED] and subject line Bug#412957: fixed in linux-2.6 2.6.18.dfsg.1-13 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

Bug#418624: marked as done (multipath routing broken in etch)

Your message dated Wed, 15 Aug 2007 22:37:44 + with message-id [EMAIL PROTECTED] and subject line Bug#418344: fixed in linux-2.6 2.6.18.dfsg.1-13 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

Bug#417629: marked as done (linux-image-2.6.18-4-sparc32: Missing module for qlogic scsi drivers (qla1280))

Your message dated Wed, 15 Aug 2007 22:37:44 + with message-id [EMAIL PROTECTED] and subject line Bug#417629: fixed in linux-2.6 2.6.18.dfsg.1-13 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

Bug#418344: marked as done (linux-2.6: Please disable CONFIG_IP_ROUTE_MULTIPATH_CACHED as it breaks the multipath route behavior in iproute)

Your message dated Wed, 15 Aug 2007 22:37:44 + with message-id [EMAIL PROTECTED] and subject line Bug#418344: fixed in linux-2.6 2.6.18.dfsg.1-13 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

Processing of linux-2.6_2.6.18.dfsg.1-13etch1_sparc.changes

linux-2.6_2.6.18.dfsg.1-13etch1_sparc.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.18.dfsg.1-13etch1.dsc linux-2.6_2.6.18.dfsg.1-13etch1.diff.gz linux-doc-2.6.18_2.6.18.dfsg.1-13etch1_all.deb linux-manual-2.6.18_2.6.18.dfsg.1-13etch1_all.deb

Bug#429622: AMD/ATI SB700 support to Debian

Hi Dann: Were you able to test this on an SB600 as well? I want to make sure we don't regress that support. The kernel 2.6.18-5-k7 (Debian 2.6.18.dfsg.1-14~snapshot.9304) can also boot on SB600 board. But there are also many ODD error messages when booting up if SATA ODD is connected, we need

Bug#438190: SB600/SB700/SB800 use same SMBus controller devID

Package: linux-2.6 Version: 2.6.18.dfsg.1-13etch1 Severity: important Tags: patch We find that SB700 and SB800 use the same SMBus device ID as SB600, which is 0x4385, instead of the already submitted 0x4395. Please apply the attached new SMBus patch, which can remove the wrong applied SB700 SMBus

RE: [patch] SB600/SB700/SB800 use same SMBus controller devID

Hi Dann: Please submit this as a bug report so that we have a reference for the stable release team. I'd do it myself, but its probably better for you to be the submitter so that you see updates as they come in. You can file this bug so by sending this same e-mail to '[EMAIL PROTECTED]'