[bts-link] source package linux-2.6

[bts-link-upstream]

#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user [EMAIL PROTECTED]

# remote status report for #360773
#  * http://bugzilla.kernel.org/show_bug.cgi?id=6822
#  * remote status changed: NEW -> CLOSED
#  * remote resolution changed: (?) -> PATCH-ALREADY-AVAILABLE
#  * closed upstream
tags 360773 + fixed-upstream
usertags 360773 - status-NEW
usertags 360773 + status-CLOSED resolution-PATCH-ALREADY-AVAILABLE

thanks

[bts-link] source package linux-2.6

[bts-link-upstream]

#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user [EMAIL PROTECTED]

# remote status report for #383849
#  * http://bugzilla.kernel.org/show_bug.cgi?id=7941
#  * remote status changed: (?) -> NEW
usertags 383849 + status-NEW

# remote status report for #408635
#  * http://bugzilla.kernel.org/show_bug.cgi?id=7952
#  * remote status changed: (?) -> NEW
usertags 408635 + status-NEW

thanks

mkvmlinuz 32 MIGRATED to testing

[Debian testing watch]

FYI: The status of the mkvmlinuz source package
in Debian's testing distribution has changed.

  Previous version: 29
  Current version:  32

-- 
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#410375: network interfaces not autoconfigured for ipv6 after reboot

[Aurelien Jarno]

On Sat, Feb 10, 2007 at 10:40:34AM +0100, Bastian Blank wrote:
> tags 410375 confirmed
> severity 410375 grave
> thanks
> 
> On Sat, Feb 10, 2007 at 10:06:55PM +1300, Amos Jeffries wrote:
> > Booting in 2.6.18-3 after the upgrade shows the correct behavior, so it 
> > looks like it's a build-specific issue.
> 
> There slipped an incomplete patch in which disables the registration of
> the all nodes multicast address.
> 

Please find below the missing part of the patch.


--- a/net/ipv6/addrconf.c   2007-02-13 02:18:13.0 +0100
+++ b/net/ipv6/addrconf.c   2007-02-13 02:34:07.0 +0100
@@ -334,6 +334,7 @@
 static struct inet6_dev * ipv6_add_dev(struct net_device *dev)
 {
struct inet6_dev *ndev;
+   struct in6_addr maddr;
 
ASSERT_RTNL();
 
@@ -404,10 +405,6 @@
if (netif_carrier_ok(dev))
ndev->if_flags |= IF_READY;
 
-   write_lock_bh(&addrconf_lock);
-   dev->ip6_ptr = ndev;
-   write_unlock_bh(&addrconf_lock);
-
ipv6_mc_init_dev(ndev);
ndev->tstamp = jiffies;
 #ifdef CONFIG_SYSCTL
@@ -417,6 +414,15 @@
  NULL);
addrconf_sysctl_register(ndev, &ndev->cnf);
 #endif
+
+   write_lock_bh(&addrconf_lock);
+   dev->ip6_ptr = ndev;
+   write_unlock_bh(&addrconf_lock);
+
+   /* Join all-node multicast group */
+   ipv6_addr_all_nodes(&maddr);
+   ipv6_dev_mc_inc(dev, &maddr);
+
return ndev;
 }
 

-- 
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian developer   | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400752: linux-modules-extra-2.6: include ndiswrapper

[Andres Salomon]

Sam Morris wrote:
> On Mon, 2007-02-12 at 12:45 -0500, Andres Salomon wrote:
>> Daniel Baumann wrote:
>>> Sam Morris wrote:
 Andreas is MIA? Or do I misunderstand?
>>> Andres didn't say something about inclusion so far, only Kel. And Kel
>>> has a bouncing  email address.
>>>
>> Sorry, that's my fault; he has updated packages for me to sponsor, but I
>> just haven't had time.
>>
>> Anyways, try <[EMAIL PROTECTED]>.
> 
> Ah, now I understand. May I suggest you make this relationship more
> explicit in the package metadata, with something like:
> 
>  Maintainer: Kel Modderman <[EMAIL PROTECTED]>
>  Uploaders: Andres Salomon <[EMAIL PROTECTED]>
> 

Well, it was the other way because I was originally maintaining it.  At
some point, I will be removed altogether; I no longer use ndiswrapper.
However, I need to talk to kel about going through NM or finding a new
sponsor.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400752: linux-modules-extra-2.6: include ndiswrapper

[Sam Morris]

On Mon, 2007-02-12 at 12:45 -0500, Andres Salomon wrote:
> Daniel Baumann wrote:
> > Sam Morris wrote:
> >> Andreas is MIA? Or do I misunderstand?
> > 
> > Andres didn't say something about inclusion so far, only Kel. And Kel
> > has a bouncing  email address.
> > 
> 
> Sorry, that's my fault; he has updated packages for me to sponsor, but I
> just haven't had time.
> 
> Anyways, try <[EMAIL PROTECTED]>.

Ah, now I understand. May I suggest you make this relationship more
explicit in the package metadata, with something like:

 Maintainer: Kel Modderman <[EMAIL PROTECTED]>
 Uploaders: Andres Salomon <[EMAIL PROTECTED]>

See

 for more info about the Uploaders field. 

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


signature.asc
Description: This is a digitally signed message part

Bug#410385: same problem

[Jurij Smakov]

On Mon, Feb 12, 2007 at 05:02:06PM -0500, Arnout Boelens wrote:
> My network card stopped working too. Maybe it is the same problem?
> 
> modprobe -r ipw3945 gives:
> 
> 2007-02-12 16:39:23: WARNING: No prior instance running.
> FATAL: Module ipw3945 is in use.
> FATAL: Error running remove command for ipw3945

The first message here comes from the daemon, which means that 
something is running it with the '--kill' switch to try and shut it 
down. Initialization script shipped with ipw3945d package does not do 
that, it just sends the signal directly to the daemon. I think what 
happens is that you still have the old modprobe config file installed, 
which was shipped as a part of ipw3945 before (see bug 399491 for 
details). If you have /etc/modprobe.d/ipw3945-modules, please remove 
it, then it should work as expected.

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#410385: same problem

[Arnout Boelens]

My network card stopped working too. Maybe it is the same problem?

modprobe -r ipw3945 gives:

2007-02-12 16:39:23: WARNING: No prior instance running.
FATAL: Module ipw3945 is in use.
FATAL: Error running remove command for ipw3945

and ps gives:

112   5038  0.0  0.0   1728   376 pts/1S16:42   0:00 /sbin/ipw3945d 
--pid-file=/var/run/ipw3945d/ipw3945d.pid --quiet 
--log-file=/var/log/ipw3945d/ipw3945d.log

There is a file /etc/modprobe.d/ipw3945d which should make sure that ipw3945d is
killed before unnloading the module ipw3945, but it doesn't work.

The contents of /etc/modprobe.d/ipw3945d:

install ipw3945 modprobe --ignore-install ipw3945 && /etc/init.d/ipw3945d 
modprobe-start
remove  ipw3945 /etc/init.d/ipw3945d modprobe-stop && modprobe -r 
--ignore-remove ipw3945


Killing ipw3945d manually and then loading it with "modprobe ipw394", loads the
module and launches ipw3945. However, ps gives

root  5217  0.0  0.0   1724   348 pts/1S16:49   0:00 /sbin/ipw3945d 
--quiet 

and not "/sbin/ipw3945d --pid-file=/var/run/ipw3945d/ipw3945d.pid --quiet
--log-file=/var/log/ipw3945d/ipw3945d.log", as should be the result of 
"/etc/init.d/ipw3945d
modprobe-start" which is the command issued in /etc/modprobe.d/ipw3945d. 

Arnout




smime.p7s
Description: S/MIME cryptographic signature

Initramfstools lvm on raid.

[Centurion Computer Technology (2005) Ltd]

Hi guys,

I have been playing with various scenarios of LVM on top of a raid
partition with the root as an lvm partition.  

The only way I can get it to boot successfully is by hacking initramfs
tools.

The fix seems to be quite simple:

I modified the lvm script so that it calls pvscan (which is just a
symlink I created to vgchange) before doing the vgchange -ay to activate
the lvm volume groups.  

The pvscan seems to make it block access directly to the block devices
if they are already being used as part of a raid array.  This forces
vgchange to correctly use the raid device rather than it's underlying
partitions.  

Without this hack I can't get a root on lvm on raid[456] to boot
successfully at all.

I hope this is helpful to you and all.

Regards,
-- 
Daniel Reurich

Centurion Computer Technology (2005) Limited.
Ph: 021 797 722


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#410697: linux-image-2.6.18-4-amd64: 32-bit iptables doesn't work with xt_limit module from amd64 kernel

[Rafal Kupka]

Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-10
Severity: wishlist
Tags: patch

Hello,

Please consider adding compat code to debian kernel to allow 32bit
iptables work with module limit (-m limit option).

Now, on kernel version 2.6.18-4-amd64 (2.6.18.dfsg.1-10):
# iptables -A FORWARD -m limit --limit 5
iptables: Invalid argument

kernel log fragment:
ip_tables: limit match: invalid size 40 != 28

Using 32-bit userland and amd64 kernel is very useful and quite popular
combination.

Mainline kernel added xt_limit compat code in post-2.6.18 versions,
git patches:
[NETFILTER]: x_tables: simplify compat API
9fa492cdc160cd27ce1046cb36f47d3b2b1efa21

[NETFILTER]: xt_limit: add compat conversion functions
02c63cf777c331121bfb6e9c1440a9835ad2f2a8

Slightly modified versions of those patches I attach.
Modifications are necessary to avoid applying
52d9c42ef2563d2c420eb23b96bf5a4cae9e167b and
4470bbc749e5551cce914529309456f631e25120 which are quite large.

Unfortunately patch "simplify compat API" modifies kernel ABI.

Regards,
Rafał Kupka
--- a/include/linux/netfilter/x_tables.h
+++ b/include/linux/netfilter/x_tables.h
@@ -138,12 +138,6 @@ struct xt_counters_info
 #define ASSERT_WRITE_LOCK(x)
 #include 
 
-#ifdef CONFIG_COMPAT
-#define COMPAT_TO_USER		1
-#define COMPAT_FROM_USER	-1
-#define COMPAT_CALC_SIZE	0
-#endif
-
 struct xt_match
 {
 	struct list_head list;
@@ -176,7 +170,8 @@ struct xt_match
 	void (*destroy)(const struct xt_match *match, void *matchinfo);
 
 	/* Called when userspace align differs from kernel space one */
-	int (*compat)(void *match, void **dstptr, int *size, int convert);
+	void (*compat_from_user)(void *dst, void *src);
+	int (*compat_to_user)(void __user *dst, void *src);
 
 	/* Set this to THIS_MODULE if you are a module, otherwise NULL */
 	struct module *me;
@@ -186,6 +181,7 @@ struct xt_match
 
 	char *table;
 	unsigned int matchsize;
+	unsigned int compatsize;
 	unsigned int hooks;
 	unsigned short proto;
 
@@ -224,13 +220,15 @@ struct xt_target
 	void (*destroy)(const struct xt_target *target, void *targinfo);
 
 	/* Called when userspace align differs from kernel space one */
-	int (*compat)(void *target, void **dstptr, int *size, int convert);
+	void (*compat_from_user)(void *dst, void *src);
+	int (*compat_to_user)(void __user *dst, void *src);
 
 	/* Set this to THIS_MODULE if you are a module, otherwise NULL */
 	struct module *me;
 
 	char *table;
 	unsigned int targetsize;
+	unsigned int compatsize;
 	unsigned int hooks;
 	unsigned short proto;
 
@@ -387,9 +385,18 @@ struct compat_xt_counters_info
 
 extern void xt_compat_lock(int af);
 extern void xt_compat_unlock(int af);
-extern int xt_compat_match(void *match, void **dstptr, int *size, int convert);
-extern int xt_compat_target(void *target, void **dstptr, int *size,
-		int convert);
+
+extern int xt_compat_match_offset(struct xt_match *match);
+extern void xt_compat_match_from_user(struct xt_entry_match *m,
+  void **dstptr, int *size);
+extern int xt_compat_match_to_user(struct xt_entry_match *m,
+   void * __user *dstptr, int *size);
+
+extern int xt_compat_target_offset(struct xt_target *target);
+extern void xt_compat_target_from_user(struct xt_entry_target *t,
+   void **dstptr, int *size);
+extern int xt_compat_target_to_user(struct xt_entry_target *t,
+void * __user *dstptr, int *size);
 
 #endif /* CONFIG_COMPAT */
 #endif /* __KERNEL__ */
diff --git a/net/ipv4/netfilter/ip_tables.c b/net/ipv4/netfilter/ip_tables.c
index 673581d..800067d 100644
--- a/net/ipv4/netfilter/ip_tables.c
+++ b/net/ipv4/netfilter/ip_tables.c
@@ -942,73 +942,28 @@ static short compat_calc_jump(u_int16_t offset)
 	return delta;
 }
 
-struct compat_ipt_standard_target
+static void compat_standard_from_user(void *dst, void *src)
 {
-	struct compat_xt_entry_target target;
-	compat_int_t verdict;
-};
-
-struct compat_ipt_standard
-{
-	struct compat_ipt_entry entry;
-	struct compat_ipt_standard_target target;
-};
+	int v = *(compat_int_t *)src;
 
-#define IPT_ST_LEN		XT_ALIGN(sizeof(struct ipt_standard_target))
-#define IPT_ST_COMPAT_LEN	COMPAT_XT_ALIGN(sizeof(struct compat_ipt_standard_target))
-#define IPT_ST_OFFSET		(IPT_ST_LEN - IPT_ST_COMPAT_LEN)
+	if (v > 0)
+		v += compat_calc_jump(v);
+	memcpy(dst, &v, sizeof(v));
+}
 
-static int compat_ipt_standard_fn(void *target,
-		void **dstptr, int *size, int convert)
+static int compat_standard_to_user(void __user *dst, void *src)
 {
-	struct compat_ipt_standard_target compat_st, *pcompat_st;
-	struct ipt_standard_target st, *pst;
-	int ret;
+	compat_int_t cv = *(int *)src;
 
-	ret = 0;
-	switch (convert) {
-		case COMPAT_TO_USER:
-			pst = target;
-			memcpy(&compat_st.target, &pst->target,
-sizeof(compat_st.target));
-			compat_st.verdict = pst->verdict;
-			if (compat_st.verdict > 0)
-compat_st.verdict -=
-	compat_calc_jump(compat_st.verdict);
-			compat_st.target.u.user.target_size = IPT_ST_COMPAT_LEN;
-			if (copy_to_user(*dstptr, &comp

Bug#400752: linux-modules-extra-2.6: include ndiswrapper

[Andres Salomon]

Daniel Baumann wrote:
> Sam Morris wrote:
>> Andreas is MIA? Or do I misunderstand?
> 
> Andres didn't say something about inclusion so far, only Kel. And Kel
> has a bouncing  email address.
> 

Sorry, that's my fault; he has updated packages for me to sponsor, but I
just haven't had time.

Anyways, try <[EMAIL PROTECTED]>.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#400752: linux-modules-extra-2.6: include ndiswrapper

[Otavio Salvador]

Sam Morris <[EMAIL PROTECTED]> writes:

> It seemed that this bug was being ignored on the pretext that the
> submitter's email address didn't work, which seems like a stupid reason
> not to include ndiswrapper in linux-modules-2.6-extra. I am just a user
> who wants to reduce the amount of pain he has to go through to get his
> stupid wireless networking hardware to work. Of course I would prefer to
> use bcm43xx, but it does not work with my device (14e4:4318).

Would be nice if you could report another bug report about the lack of
support for your adapter to the respective package. That would help
you and others too.

I'm also a supporter for ndiswrapper inclusion on the l-m-2.6-e
package set.

-- 
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]

Bug#400752: linux-modules-extra-2.6: include ndiswrapper

[Sam Morris]

On Mon, 2007-02-12 at 12:50 +0100, Daniel Baumann wrote:
> Sam Morris wrote:
> > Andreas is MIA? Or do I misunderstand?
> 
> Andres didn't say something about inclusion so far, only Kel. And Kel
> has a bouncing  email address.

Right, but who is Kel--just the bug submitter? I would have submitted a
bug myself if I didn't notice this one already in the BTS.

It seemed that this bug was being ignored on the pretext that the
submitter's email address didn't work, which seems like a stupid reason
not to include ndiswrapper in linux-modules-2.6-extra. I am just a user
who wants to reduce the amount of pain he has to go through to get his
stupid wireless networking hardware to work. Of course I would prefer to
use bcm43xx, but it does not work with my device (14e4:4318).

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


signature.asc
Description: This is a digitally signed message part

Bug#400752: linux-modules-extra-2.6: include ndiswrapper

[Daniel Baumann]

Sam Morris wrote:
> Right, but who is Kel--just the bug submitter? I would have submitted a
> bug myself if I didn't notice this one already in the BTS.

Kel is co-maintainer of ndiswrapper and uses his broken email address
not just for reporting bugs but also to maintain his packages.

> It seemed that this bug was being ignored on the pretext that the
> submitter's email address didn't work, which seems like a stupid reason
> not to include ndiswrapper in linux-modules-2.6-extra.

It has been said that the maintainer must agree before his packages are
going to be included. As of now, there is no such sign of agreement,
just a "signal of noice" from a non-working email address.

-- 
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#400752: linux-modules-extra-2.6: include ndiswrapper

[Daniel Baumann]

Sam Morris wrote:
> Andreas is MIA? Or do I misunderstand?

Andres didn't say something about inclusion so far, only Kel. And Kel
has a bouncing  email address.

-- 
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#400752: linux-modules-extra-2.6: include ndiswrapper

[Sam Morris]

On Mon, 2007-02-12 at 12:25 +0100, Daniel Baumann wrote:
> Sam Morris wrote:
> > Re-opening, I would like to see binary packages of the ndiswrapper
> > modules in Debian.
> 
> if the mainainer re-appears, i'll add ndiswrapper.

Andreas is MIA? Or do I misunderstand?

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#410643: linux-image-2.6-amd64: linux fails to read partition table on boot device after upgrade from 2.6.17 to 2.6.18

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 410643 important
Bug#410643: linux-image-2.6-amd64: linux fails to read partition table on boot 
device after upgrade from 2.6.17 to 2.6.18
Severity set to `important' from `critical'

> reassign 410643 linux-2.6
Bug#410643: linux-image-2.6-amd64: linux fails to read partition table on boot 
device after upgrade from 2.6.17 to 2.6.18
Bug reassigned from package `linux-image-2.6-amd64' to `linux-2.6'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400752: linux-modules-extra-2.6: include ndiswrapper

[Daniel Baumann]

Sam Morris wrote:
> Re-opening, I would like to see binary packages of the ndiswrapper
> modules in Debian.

if the mainainer re-appears, i'll add ndiswrapper.

-- 
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#410643: linux-image-2.6-amd64: linux fails to read partition table on boot device after upgrade from 2.6.17 to 2.6.18

[Steve Langasek]

severity 410643 important
reassign 410643 linux-2.6
thanks

On Mon, Feb 12, 2007 at 11:22:05AM +0100, Kuno Woudt wrote:
> Package: linux-image-2.6-amd64
> Version: 2.6.18+5
> Severity: critical
> Justification: breaks the whole system

> I have installed debian using an amd64 etch installer which installs 
> a 2.6.17 kernel (2.6.17-2-amd64).  The setup uses a 256mb boot partition,
> and everything else on a software raid (fdisk output for both disks 
> pasted below).  This all works without problem.

> After upgrading the kernel to the debian packaged 2.6.18-7, the system
> cannot read the partition table on /dev/sda.  A failure to mount /boot
> results in some error messages during boot, booting continues after
> pressing CTRL-D, the root file system (software raid, /dev/md0) is
> mounted fine, the /boot filesystem is not. Note, only the partition
> table of /dev/sda cannot be read, the output of 'fdisk /dev/sdb' is
> the same as when booted with 2.6.17.

This implies that the RAID is also being brought up in degraded mode due to
the missing component on /dev/sda.

Have you verified that under 2.6.18, the disk doesn't get renamed to
something other than /dev/sda, for some unclear reason?  I.e., do you have
any other /dev/sd* device nodes?

-- 
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]

Bug#405232: include rt2400/rt2500/rt2570/rt2x00

[Daniel Baumann]

Sam Morris wrote:
> Is there any progress on this? Will the updated packages enter etch?

2007-01-30 12:45:54 < panthera> aurel32: any nex about the r modules?
2007-01-30 12:46:00 < panthera> s/nex/news/
2007-01-30 13:29:03 < aurel32> panthera: it won't be possible to get the
current version in etch
2007-01-30 13:29:09 < aurel32> panthera: so that will be for lenny
2007-01-30 13:35:40 < panthera> aurel32: too bad :/ nevertheless, thanks
for your efforts.

-- 
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#410643: marked as done (linux-image-2.6-amd64: linux fails to read partition table on boot device after upgrade from 2.6.17 to 2.6.18)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2007 12:11:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line resolved
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)

--- Begin Message ---
Package: linux-image-2.6-amd64
Version: 2.6.18+5
Severity: critical
Justification: breaks the whole system


I have installed debian using an amd64 etch installer which installs 
a 2.6.17 kernel (2.6.17-2-amd64).  The setup uses a 256mb boot partition,
and everything else on a software raid (fdisk output for both disks 
pasted below).  This all works without problem.

After upgrading the kernel to the debian packaged 2.6.18-7, the system
cannot read the partition table on /dev/sda.  A failure to mount /boot
results in some error messages during boot, booting continues after
pressing CTRL-D, the root file system (software raid, /dev/md0) is
mounted fine, the /boot filesystem is not. Note, only the partition
table of /dev/sda cannot be read, the output of 'fdisk /dev/sdb' is
the same as when booted with 2.6.17.

fdisk output for /dev/sda with linux 2.6.18:

--
ico:~# fdisk /dev/sda
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF 
disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.


The number of cylinders for this disk is set to 121576.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x of partition table 4 will be corrected by w(rite)

Command (m for help): p

Disk /dev/sda: 999.9 GB, 99668224 bytes
255 heads, 63 sectors/track, 121576 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System

--

fdisk output with linux 2.6.16:

--
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
   /dev/sda1   1  31  248976   83  Linux
   /dev/sda2  32 274 1951897+  82  Linux swap / Solaris
   /dev/sda3 275   30401   241995127+  fd  Linux raid autodetect


Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
   /dev/sdb1   1  31  248976   83  Linux
   /dev/sdb2  32 274 1951897+  82  Linux swap / Solaris
   /dev/sdb3 275   30401   241995127+  fd  Linux raid autodetect
--


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6-amd64 depends on:
ii  linux-image-2.6.18-3-amd642.6.18-7   Linux 2.6.18 image on AMD64

linux-image-2.6-amd64 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---

Turns out the 2.6.18 kernel includes support for the areca raid 
controller (module arcmsr) installed in this system, whereas 
2.6.17 doesn't.

For some reason the arcmsr driver seems to get loaded first, resulting
in reordered /dev/sd* devices.  If I had done the initial install with
a 2.6.18 based installer, this presumably will not be a problem.

--- End Message ---

Processed: Re: linux-modules-extra-2.6: include ndiswrapper

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reopen 400752 !
Bug#400752: linux-modules-extra-2.6: include ndiswrapper
Bug reopened, originator set to Sam Morris <[EMAIL PROTECTED]>.

> 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#400752: linux-modules-extra-2.6: include ndiswrapper

[Sam Morris]

reopen 400752 !
thanks

Re-opening, I would like to see binary packages of the ndiswrapper
modules in Debian.

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


signature.asc
Description: This is a digitally signed message part

Bug#405232: include rt2400/rt2500/rt2570/rt2x00

[Sam Morris]

Is there any progress on this? Will the updated packages enter etch?

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078



signature.asc
Description: This is a digitally signed message part

Bug#410643: linux-image-2.6-amd64: linux fails to read partition table on boot device after upgrade from 2.6.17 to 2.6.18

[Kuno Woudt]

Package: linux-image-2.6-amd64
Version: 2.6.18+5
Severity: critical
Justification: breaks the whole system


I have installed debian using an amd64 etch installer which installs 
a 2.6.17 kernel (2.6.17-2-amd64).  The setup uses a 256mb boot partition,
and everything else on a software raid (fdisk output for both disks 
pasted below).  This all works without problem.

After upgrading the kernel to the debian packaged 2.6.18-7, the system
cannot read the partition table on /dev/sda.  A failure to mount /boot
results in some error messages during boot, booting continues after
pressing CTRL-D, the root file system (software raid, /dev/md0) is
mounted fine, the /boot filesystem is not. Note, only the partition
table of /dev/sda cannot be read, the output of 'fdisk /dev/sdb' is
the same as when booted with 2.6.17.

fdisk output for /dev/sda with linux 2.6.18:

--
ico:~# fdisk /dev/sda
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF 
disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.


The number of cylinders for this disk is set to 121576.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x of partition table 4 will be corrected by w(rite)

Command (m for help): p

Disk /dev/sda: 999.9 GB, 99668224 bytes
255 heads, 63 sectors/track, 121576 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System

--

fdisk output with linux 2.6.16:

--
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
   /dev/sda1   1  31  248976   83  Linux
   /dev/sda2  32 274 1951897+  82  Linux swap / Solaris
   /dev/sda3 275   30401   241995127+  fd  Linux raid autodetect


Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
   /dev/sdb1   1  31  248976   83  Linux
   /dev/sdb2  32 274 1951897+  82  Linux swap / Solaris
   /dev/sdb3 275   30401   241995127+  fd  Linux raid autodetect
--


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6-amd64 depends on:
ii  linux-image-2.6.18-3-amd642.6.18-7   Linux 2.6.18 image on AMD64

linux-image-2.6-amd64 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#404190: kqemu-modules-2.6.18-3-686: Similar here

[Stephen Pinker]

Package: kqemu-modules-2.6.18-3-686
Followup-For: Bug #404190


The device /dev/kqemu was not auto created and I could not (easily?) find 
info on creating it within the ..share/doc/kqemu.. files. I search on 
google, in vain, for "/dev/kqemu: No such file or directory". I ended up 
going to the qemu website and it told me how to create the node statically:


mknod /dev/kqemu c 250 0
chmod 666 /dev/kqemu

I'm not 100% sure if the node is working correctly or not. Qemu does seem to 
be running with it, but it appeared to lockup when I used the 
'-kernel-kqemu' option. Though, perhaps that may be a bug in kqemu itself...



-- System Information:
Debian Release: 4.0
 APT prefers testing
 APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kqemu-modules-2.6.18-3-686 depends on:
ii  linux-image-2.6.18-3-686 [lin 2.6.18-7   Linux 2.6.18 image on 
PPro/Celeron


kqemu-modules-2.6.18-3-686 recommends no packages.

_
Check out all that glitters with the MSN Entertainment Guide to the Academy 
Awards®   http://movies.msn.com/movies/oscars2007/?icid=ncoscartagline2




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]