Per Olofsson wrote:
On Tue, Jun 29, 2004 at 21:22 -0300, Robin Blondon wrote:
If I choose to detect network hardware a second time without restarting
cardmgr it still fails to find the card. I need to either restart
cardmgr or reinsert the card.
I think that this problem is specific to be
Package: kernel-image-2.6.6-2-686
Version: 2.6.6-2
Severity: normal
PL2303 USB module oops on unload
usbcore: deregistering driver pl2303
drivers/usb/serial/usb-serial.c: USB Serial deregistering driver PL-2303
PL-2303 ttyUSB0: PL-2303 converter now disconnected from ttyUSB0
usbserial 1-1:1.0: de
On Tue, Jun 29, 2004 at 21:22 -0300, Robin Blondon wrote:
> If I choose to detect network hardware a second time without restarting
> cardmgr it still fails to find the card. I need to either restart
> cardmgr or reinsert the card.
I think that this problem is specific to beta4. Could you try a
Processing commands for [EMAIL PROTECTED]:
> reassign 256374 kernel
Bug#256374: Installation hangs on Compaq Presario 1220 while loading module
'ide-cd' during hardware detection for the CD-ROM drive (beta4, i386, linux26)
Bug reassigned from package `installation-reports' to `kernel'.
> retitle
Am 2004-07-01 13:32:24, schrieb Michal Suchanek:
>Package: kernel-image-2.4.26-1-686
>Version: 2.4.26-2
>Severity: normal
>File: kernel-image-2.4.26
>
>When the kernel boots something says it cannot check root because it is
>not mounted ro, then it continues with errors like
>"No such device: LABEL
On Thu, Jul 01, 2004 at 02:01:24PM +0200, Michal 'hramrach' Suchanek wrote:
> On Thu, Jul 01, 2004 at 07:07:59AM +0200, Sven Luther wrote:
> > On Wed, Jun 30, 2004 at 07:47:12PM +0200, Michal Suchanek wrote:
> > > Package: kernel-image-2.6.6-1-686
> > >
> > > 192:~# mount -t hfsplus /dev/hdc5 /mnt
Hi,
Matthias Urlichs wrote:
> The actual panic message would be helpful.
I've previously hand-dumped the console message, I don't know what's the better
way to do this type of work (kernel debug options, tools, etc..).
At this moment I don't have access to the kernel .config options of the
mac
On Thu, Jul 01, 2004 at 07:32:13PM +0200, Kurt Roeckx wrote:
> I intent to adopt the kernel-patch-usagi package.
>
> I think I will atleast need to split it up in 2 packages, one for
> 2.4 and one for 2.6. So I'd get kernel-patch-usagi-2.4 and and
> kernel-patch-usagi-2.6.
>
> Or should I make a
On Thu, Jul 01, 2004 at 07:32:13PM +0200, Kurt Roeckx wrote:
> I intent to adopt the kernel-patch-usagi package.
>
> I think I will atleast need to split it up in 2 packages, one for
> 2.4 and one for 2.6. So I'd get kernel-patch-usagi-2.4 and and
> kernel-patch-usagi-2.6.
>
> Or should I make a
Your message dated Thu, 1 Jul 2004 19:57:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kernel-image-2.6.6-2-686: kernel will not load file system
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
Accepted:
initrd-tools_0.1.71.dsc
to pool/main/i/initrd-tools/initrd-tools_0.1.71.dsc
initrd-tools_0.1.71.tar.gz
to pool/main/i/initrd-tools/initrd-tools_0.1.71.tar.gz
initrd-tools_0.1.71_all.deb
to pool/main/i/initrd-tools/initrd-tools_0.1.71_all.deb
Announcing to debian-devel-changes@lists
I intent to adopt the kernel-patch-usagi package.
I think I will atleast need to split it up in 2 packages, one for
2.4 and one for 2.6. So I'd get kernel-patch-usagi-2.4 and and
kernel-patch-usagi-2.6.
Or should I make a version for each kernel source package in
debian and then name them for in
Andreas Metzler wrote:
The version of module-init-tools you are running currently has this bug
fixed, but you might still have the old broken version on the initrd
which is generated at installation of the kernel-image package.
Could you try to regenerate initrd either by running
mkinitrd -o /boot/
initrd-tools_0.1.71_i386.changes uploaded successfully to localhost
along with the files:
initrd-tools_0.1.71.dsc
initrd-tools_0.1.71.tar.gz
initrd-tools_0.1.71_all.deb
Greetings,
Your Debian queue daemon
Andreas Metzler wrote:
Is this is a new error or have you experienced it for some time now and
just could not spatre the time to report the bug until now? I am asking
because this sounds like another instance of
http://bugs.debian.org/254950 "module-init-tools complains about read
only filesystem a
Your message dated Thu, 01 Jul 2004 11:32:06 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#252466: fixed in initrd-tools 0.1.71
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 no
Your message dated Thu, 01 Jul 2004 11:32:06 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#252464: fixed in initrd-tools 0.1.71
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 no
compiling radeonfb as a module works just fine for me in 2.6...
I don't see why you need a patch...
> linux-fbdev folk, what is your take on this, would it be possible to
> somehow get a way to have earlier debug messages, or to bring the
> loading of fbdev modules to an earlier point ?
If yo
* Herbert Xu <[EMAIL PROTECTED]> [2004-05-28 20:14]:
> > Mkinitrd does not load the qla2300 module (QLogic FC adapter) from a
> > separate module package.
>
> Does this patch help?
Torsten, can you confirm that this patch fixed the problem?
--
Martin Michlmayr
[EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> tags 252466 + pending
Bug#252466: initrd-tools: mkinitrd fails to add via82cxxx module on
powerpc/pegasos, and thus there is no ide driver loaded.
There were no tags set.
Tags added: pending
> tags 252464 + pending
Bug#252464: initrd-tools: ext2 modul
---
> Hi,
>
> > I'd like to know how a modularized PCI subsystem can be loaded
_AFTER_
> > a PCI dependent FB driver.
>
> Well, duh, obviously you can't do that. :-/
Heh, I has a feeling that wouldn't be that easy ;)
> > What then if the PCI buswalk kills the kernel?
>
> You w
On Thu, Jul 01, 2004 at 10:05:11AM -0400, Martin Michlmayr wrote:
> * Sven Luther <[EMAIL PROTECTED]> [2004-07-01 10:55]:
> > Now a question about these patches. Will you mae a new release, or
> > should i, as part of the new debian-kernel team make the upload with
> > them ?
>
> I intend to make
On Thu, Jul 01, 2004 at 03:50:28PM +0200, Matthias Urlichs wrote:
> Hi,
>
> > I'd like to know how a modularized PCI subsystem can be loaded _AFTER_
> > a PCI dependent FB driver.
>
> Well, duh, obviously you can't do that. :-/
>
> > What then if the PCI buswalk kills the kernel?
>
> You write
* Sven Luther <[EMAIL PROTECTED]> [2004-07-01 10:55]:
> Now a question about these patches. Will you mae a new release, or
> should i, as part of the new debian-kernel team make the upload with
> them ?
I intend to make an upload, but if you want to, just go ahead; check
them into SVN though.
--
http://www.no-l.org/pages/cobalt-patch.html
At the above URL there is a patch against the Debian 2.6.6 kernel to support
Cobalt hardware. I have also uploaded a kernel patch package to Debian with
it. It seems to work OK, and it would be good if we could get it included
upstream...
--
http:
reassign 256374 kernel
retitle 256374 CD problems under 2.6, not under 2.4
thanks
* Robin Blondon <[EMAIL PROTECTED]> [2004-07-01 10:29]:
> I finally got 2.4 to install (with a few PCMCIA/networking snags) and
> was able to upgrade to the kernel package kernel-image-2.6.6-1-386.
> After rebootin
On Thu, Jul 01, 2004 at 03:33:06PM +0200, Matthias Urlichs wrote:
> Hi, Sven Luther wrote:
>
> > And sorry, upto now, your only arguments where dogma, white space and the
> > monolitic nature of the patch.
>
> If you s/dogma/experience with handling kernel patches/, all three points
> are entirel
---
> Hi, Sven Luther wrote:
>
> > This is bullshit. I don't think it is a great idea to modularize
the
> > kernel, and thus lose all the early debugging. We are going to
hurt us if
> > we go that way, especially as the boot process is now more fragile
as it
> > used to be, thanks
Hi,
> I'd like to know how a modularized PCI subsystem can be loaded _AFTER_
> a PCI dependent FB driver.
Well, duh, obviously you can't do that. :-/
> What then if the PCI buswalk kills the kernel?
You write these parts of the kernel defensively so that this doesn't
happen, and/or you test it
Hi, Sven Luther wrote:
> And sorry, upto now, your only arguments where dogma, white space and the
> monolitic nature of the patch.
If you s/dogma/experience with handling kernel patches/, all three points
are entirely valid reasons to reject a patch. (NB: you want "were".)
Split the thing now.
On Thu, Jul 01, 2004 at 03:18:47PM +0200, Matthias Urlichs wrote:
> Hi, Sven Luther wrote:
>
> > This is bullshit. I don't think it is a great idea to modularize the
> > kernel, and thus lose all the early debugging. We are going to hurt us if
> > we go that way, especially as the boot process is
Hi, Sven Luther wrote:
> This is bullshit. I don't think it is a great idea to modularize the
> kernel, and thus lose all the early debugging. We are going to hurt us if
> we go that way, especially as the boot process is now more fragile as it
> used to be, thanks to the initrd thingy,
The worka
On Thu, Jul 01, 2004 at 07:07:59AM +0200, Sven Luther wrote:
> On Wed, Jun 30, 2004 at 07:47:12PM +0200, Michal Suchanek wrote:
> > Package: kernel-image-2.6.6-1-686
> >
> > 192:~# mount -t hfsplus /dev/hdc5 /mnt
> > mount: Not a directory
> >
> > the same thing with mount /dev/hdc /mnt
> >
> >
Package: kernel-image-2.4.26-1-686
Version: 2.4.26-2
Severity: normal
File: kernel-image-2.4.26
When the kernel boots something says it cannot check root because it is
not mounted ro, then it continues with errors like
"No such device: LABEL=Home" while mounting other partitions. When I
boot with
Package: kernel-source-2.4.26
Version: 2.4.26-2
Severity: critical
Justification: breaks the whole system
The IPsec backport have some issues with NFS. Using an NFS export over
an IPsec channel causes an immediate kernel panic.
Scenario:
- 2 hosts, debian kernel 2.4.26, one NFS server, one NFS c
#include
* Andrew Pollock [Wed, Jun 30 2004, 09:17:59AM]:
> Ah yes. Herbert had quite strong views on what should and shouldn't be done
> in the kernel, despite the fact that things existed in the kernel here and
> now, and to implement the equivalent in userspace would require someone to
> actua
On Wed, Jun 30, 2004 at 08:12:20PM +0200, Marco d'Itri wrote:
> On Jun 30, Agustin Martin wrote:
>
> > By the way, mkinitrd complained about /etc/modprobe.conf and the one at lib
> > dir not being present because of the recent changes in module-init-tools.
> > The image built and seems to work, bu
Let's bring linux-fbdev in the loop, as they probably are the best
placed to comment.
On Thu, Jul 01, 2004 at 10:26:18AM +0200, Jens Schmalzing wrote:
> Hi,
>
> the following patch allows some accelerated framebuffers (aty128fb,
> atyfb, radeonfb, and rivafb) and framebuffer console support itsel
On Thu, Jul 01, 2004 at 09:54:48AM +0200, Jens Schmalzing wrote:
> Hi,
>
> Bluefuture writes:
>
> > > The low techie people I came across think that anything beside
> > > graphics are "old computing" or recovery broken things... so a
> > > bootsplash help they to trust the operating system (the c
Alle 09:54, giovedì 01 luglio 2004, Jens Schmalzing ha scritto:
> Psychology aside, there are two technical reasons for not integrating
> this kernel patch.
>
> One: It works exclusively with vesafb and this sucks. But let's
> assume for the moment that we all have nothing but i386 hardware and
>
On Thu, Jul 01, 2004 at 06:15:11PM +1000, Herbert Xu wrote:
> On Tue, Jun 29, 2004 at 03:12:30PM +0200, Sven Luther wrote:
> >
> > Yep, that worked for ext2.
> > Still via82cxxx is missing though, which means no ide driver on
> > powerpc/pegasos,
> > but this is another bug :
> >
> > http://
On 2004-07-01 Jason Dorje Short <[EMAIL PROTECTED]> wrote:
> Package: kernel-image-2.6.6-2-686
> Version: 2.6.6-2
> Severity: important
> When I boot up in this kernel I can not succeed. The eventual problem
> is that none of the modules can be loaded because of a "read-only file
> system".
[.
On Tue, Jun 29, 2004 at 03:12:30PM +0200, Sven Luther wrote:
>
> Yep, that worked for ext2.
> Still via82cxxx is missing though, which means no ide driver on
> powerpc/pegasos,
> but this is another bug :
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252466
Well this is because you'v
Hi,
Bluefuture writes:
> > The low techie people I came across think that anything beside
> > graphics are "old computing" or recovery broken things... so a
> > bootsplash help they to trust the operating system (the computer
> > as whole object from their point of view).
>
> I'm totally agree o
Hi,
Thiemo Seufer writes:
> Everything not needed for boot should already be in modules anyway.
It's not that simple. There are lots of drivers in the vanilla kernel
that nobody bothered to modularize, plain and simple. Herbert has
done a tremenduous amount of this work already, but much remai
On Wed, Jun 30, 2004 at 07:47:12PM +0200, Michal Suchanek wrote:
> Package: kernel-image-2.6.6-1-686
> Version: 2.6.6-1
> Severity: normal
>
> 192:~# mount -t hfsplus /dev/hdc5 /mnt
> mount: Not a directory
>
> the same thing with mount /dev/hdc /mnt
>
> I can mount /dev/hdc5 /mnt but it is moun
Package: kernel-image-2.6.6-2-686
Version: 2.6.6-2
Severity: important
When I boot up in this kernel I can not succeed. The eventual problem
is that none of the modules can be loaded because of a "read-only file
system". But why can't a read-only kernel module be loaded?
I'd give a better rep
On Thu, Jul 01, 2004 at 10:19:20AM +0900, Horms wrote:
> On Wed, Jun 30, 2004 at 04:01:16PM +0200, Sven Luther wrote:
>
> [snip]
>
> > We really need to get 2.6.7 out in the open. How long has it been
> > already, two weeks or three maybe ?
> >
> > Anyway, i am CCing ftpmasters, in hope to get s
48 matches
Mail list logo
