Jurij,
> The problems you're experiencing sound suspiciously similar to the
> Debian's bug #405109 [0], aka upstream bug #1096 [1]. It should be
> fixed in the latest version of the ipw3945 driver, I'm CC'ing the
> maintainer to see if he might have any insights.
>
> [0] http://bugs.debian.org/cgi
"Christian T. Steigies" <[EMAIL PROTECTED]> writes:
> On Tue, Jan 02, 2007 at 03:15:00PM +0100, Goswin von Brederlow wrote:
>> "Christian T. Steigies" <[EMAIL PROTECTED]> writes:
>>
>> > Ist das mit diesem patch bereits erledigt?
>> >
>> > kpkg_image += --arch '$(firstword $(KPKG_ARCH) $(ARCH))'
#
# 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 #397460
# * http://bugzilla.kernel.org/show_bug.cgi?id=7502
# * remote status changed: NEW -> CLOSED
# *
Processing commands for [EMAIL PROTECTED]:
> #
> # 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]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report
Your message dated Fri, 5 Jan 2007 15:01:39 +0100
with message-id <[EMAIL PROTECTED]>
and subject line No bug
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
linux-modules-nonfree-2.6_2.6.18-3_i386.changes uploaded successfully to
localhost
along with the files:
linux-modules-nonfree-2.6_2.6.18-3.dsc
linux-modules-nonfree-2.6_2.6.18-3.tar.gz
kqemu-modules-2.6.18-3-486_2.6.18+1.3.0~pre9-3_i386.deb
kqemu-modules-2.6-486_2.6.18-3_i386.deb
kqemu-
Accepted:
kqemu-modules-2.6-486_2.6.18-3_i386.deb
to
pool/non-free/l/linux-modules-nonfree-2.6/kqemu-modules-2.6-486_2.6.18-3_i386.deb
kqemu-modules-2.6-686-bigmem_2.6.18-3_i386.deb
to
pool/non-free/l/linux-modules-nonfree-2.6/kqemu-modules-2.6-686-bigmem_2.6.18-3_i386.deb
kqemu-modules-2.6-
linux-modules-contrib-2.6_2.6.18-3_i386.changes uploaded successfully to
localhost
along with the files:
linux-modules-contrib-2.6_2.6.18-3.dsc
linux-modules-contrib-2.6_2.6.18-3.tar.gz
ipw2100-modules-2.6.18-3-486_2.6.18+1.2.1-3_i386.deb
ipw2100-modules-2.6-486_2.6.18-3_i386.deb
ipw2200
Accepted:
ipw2100-modules-2.6-486_2.6.18-3_i386.deb
to
pool/contrib/l/linux-modules-contrib-2.6/ipw2100-modules-2.6-486_2.6.18-3_i386.deb
ipw2100-modules-2.6-686-bigmem_2.6.18-3_i386.deb
to
pool/contrib/l/linux-modules-contrib-2.6/ipw2100-modules-2.6-686-bigmem_2.6.18-3_i386.deb
ipw2100-modu
On Jan 05, dann frazier <[EMAIL PROTECTED]> wrote:
> > > Can you point me to (or explain) how the floppy group is currently
> > > defined and how it is differentiated by plugdev?
> > It's supposed to be used for removable media: floppy disks, memory cards
> > or USB and firewire hard disks.
> > (E
On Fri, Jan 05, 2007 at 03:23:40AM +0100, Marco d'Itri wrote:
> On Jan 05, dann frazier <[EMAIL PROTECTED]> wrote:
>
> > Can you point me to (or explain) how the floppy group is currently
> > defined and how it is differentiated by plugdev?
> It's supposed to be used for removable media: floppy di
> I am not able to reproduce this bug on my Core2 Duo (2GB RAM)
> PC running linux-image-2.6.18-3-xen-amd64 with amd64 etch.
> - linux-image-2.6.18-3-i386 and linux-image-2.6.18-3-k7 (2.6.18-7)
Did you try the -xen-686 flavor?
I have not seen anyone actually explicitly confirm that the debian ker
On Wed, Jan 03, 2007 at 12:17:47PM -0500, Salyzyn, Mark wrote:
> The ips driver, indirectly via Firmware as it spoofs it's own inquiry
> data, reports the Removable bit set in the inquiry response for the
> arrays. The dpt_i2o driver similarly has the firmware constructing the
> bit set. Some of th
Dnia piątek, 5 stycznia 2007 19:30, Knock, Bob napisał:
> > - linux-image-2.6.18-3-i386 and linux-image-2.6.18-3-k7 (2.6.18-7)
>
> Did you try the -xen-686 flavor?
Yes, I meant -xen-686 and -xen-k7 flawours, sorry for my mistake.
Janusz
I have access to quite a few machines currently that run sarge and have
devices like the adaptec 2010s, 2020s, 2200s, and 2230slp. I'm not sure
how to pull the udev info though? If you can let me know how to do this
I can go grab the information quick.
Jay Ellington
--
To UNSUBSCRIBE, email to
Michael Setzer wrote:
> Even if I don't see any soft lockup messages on the console or in my
> syslog/bootlog I agree with you that waiting for the next driver/daemon
> release is a good idea. :)
version 1.1.3 of ipw3945 was uploaded to unstable in the last days, if
you're 'still' using the old
I do not have any close at hand (cleaned out the hardware closet to
hazardous waste) :-(
But, as far as I am concerned :-), if it says 'DPT' or 'Adaptec' as the
manufacturer's name portion of the inquiry field, or has 'RAID' or
'Array' somewhere in the product name inquiry field, you have covered
Hello,
Today Bastian Blank and I finished the preparations to release the next
linux-2.6 package with an orig.tar.gz complying with the GR2006-007.
The following drivers will be completely removed from the next upload,
because they contain legally not distributable components:
dabus
cops
dgrs
3
Frederik Schueler wrote:
> Does this create any trouble, beside the package having to go through
> the NEW queue?
If it's only a renaming of the source package, and not a change to the
form of the binary package names, then I don't see any problem from a d-i
or debian-cd POV.
--
see shy jo
si
* Frederik Schueler:
> As we need to upload a new orig.tar.gz file, we need to rename the
> source package.
Huh? Non sequitur.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Jan 05, 2007 at 03:27:24PM -0800, Jay Ellington wrote:
> I have access to quite a few machines currently that run sarge and have
> devices like the adaptec 2010s, 2020s, 2200s, and 2230slp. I'm not sure
> how to pull the udev info though? If you can let me know how to do this
> I can go gra
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.26
> found 266875 2.6.17-9
Bug#266875: uid= doesn't work on udf filesystems with rock ridge attributes
Bug marked as found in version 2.6.17-9.
>
End of message, stopping processing here.
On Fri, Jan 05, 2007 at 05:20:09PM -0800, Jay Ellington wrote:
> Hi Dann,
>
> Unfortunatly after I looked at our sarge boxes I found out they
> don't have udev installed, and sense these are my production machines
> I'm not about to install it.
Marco: does udev need to be installed for udevin
Hi Dann,
Unfortunatly after I looked at our sarge boxes I found out they
don't have udev installed, and sense these are my production machines
I'm not about to install it. I pulled the udev info off of a machine
with a 2020s zero channel raid card, though the output is from Ubuntu
6.06 LTS (I
On Jan 06, dann frazier <[EMAIL PROTECTED]> wrote:
> Marco: does udev need to be installed for udevinfo to work? In other
> words, could Jay rebuild udevinfo on his sarge box and run it from the
> build tree?
No, just copy it from another box.
--
ciao,
Marco
signature.asc
Description: Digital
On Friday 05 January 2007 22:54, Frederik Schueler wrote:
> As we need to upload a new orig.tar.gz file, we need to rename the
> source package. Among the various possibilities, I think calling it
>
> linux-2.6.18
>
> like we did with linux-2.6.16 seems the best choice, and there will not
> be any
On Fri, Jan 05, 2007 at 08:27:25AM +0100, maximilian attems wrote:
> tags 334104 -wontfix
> tags 334104 pending
> thanks
>
> morning jurij,
>
> On Thu, Jan 04, 2007 at 10:36:12PM -0800, Jurij Smakov wrote:
> > tag 373621 wontfix
> > thanks
> >
> > My attempt to actually do something about this a
For the record, FUSE works on an ARM IXP4xx machine (Linksys NLSU2)
with 2.6.18-9 (subversion revision 8101).
$ encfs /home/gordon/.encrypted /home/gordon/encrypted
EncFS Password:
$ ls -l encrypted/
total 4
-rw-r--r-- 1 gordon gordon 13 2007-01-05 22:40 example.txt
$ cat encrypted/example.txt
So
Hi Andrew,
> Package: linux-image-2.6.18-3-sparc64
> Version: 2.6.18-17
>
> This hangs just after issuing
> "Booting Linux..."
> on a SunBlade100.
>
> appended the secret kernel parameter
> "console=prom"
> and it hung just after showing the two
> "atyfb: "
> lines.
>
> Running silo 1.4.13-1 with
29 matches
Mail list logo
