On Wed, Jul 07, 2004 at 12:26:49AM +0100, Martin Michlmayr wrote:
> wli mentioned that he'll be a bit busy during the next weeks or so.
> Can someone please help him get updated 2.4 packages out?
What needs to be done?
--
Horms
Processing commands for [EMAIL PROTECTED]:
> clone 257970 -1
Bug#257970: debian-installer: vesafb driver in 2.6.7 problem (or VMware?)
Bug 257970 cloned as bug 257996.
> retitle -1 vesafb module successfully loads even if it can't work
Bug#257996: debian-installer: vesafb driver in 2.6.7 problem
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 257970 rootskel
Bug#257970: debian-installer: vesafb driver in 2.6.7 problem (or VMware?)
Bug reassigned from package `kernel-image-2.6.7-i386' to `rootskel'.
>
End of mes
Kenshi Muto wrote:
> Hi,
>
> At Tue, 6 Jul 2004 20:36:56 -0400,
> Joey Hess wrote:
> > Kenshi Muto wrote:
> > > This problem is only happened with 2.6.7. 2.4.26 works correctly. And
> > > I remember 2.6.5 works.
> > > I'll try to clarify who's wrong.
> >
> > I'm not seeing any problem with frameb
On Mon, Jul 05, 2004 at 20:10 -0300, Robin Blondon wrote:
Under 2.6, when I have i82365 and orinoco_cs in /etc/modules, lsmod
shows that yenta_socket is not loaded. "cardctl ident" says:
Socket 0:
cs: unable to map card memory!
cs: unable to map card memory!
no product info available
cs: unabl
Hi,
At Tue, 6 Jul 2004 20:36:56 -0400,
Joey Hess wrote:
> Kenshi Muto wrote:
> > This problem is only happened with 2.6.7. 2.4.26 works correctly. And
> > I remember 2.6.5 works.
> > I'll try to clarify who's wrong.
>
> I'm not seeing any problem with framebuffer and 2.6.7. Of course vga16fb
> is
Kenshi Muto wrote:
> I don't what this problem is from, but report for recording.
>
> When I tried to install to VMware(4.5.2 build8848) with 'linux26',
> framebuffer won't be loaded.
> I know this is because rootskel's problem, but I find another
> (more critical) problem.
>
> When I run "modpro
Processing commands for [EMAIL PROTECTED]:
> reassign 257970 kernel-image-2.6.7-i386
Bug#257970: debian-installer: vesafb driver in 2.6.7 problem (or VMware?)
Bug reassigned from package `debian-installer' to `kernel-image-2.6.7-i386'.
> thanks
Stopping processing here.
Please contact me if you
wli mentioned that he'll be a bit busy during the next weeks or so.
Can someone please help him get updated 2.4 packages out?
--
Martin Michlmayr
[EMAIL PROTECTED]
On Tue, Jul 06, 2004 at 11:52:53PM +0200, Christoph Hellwig wrote:
> On Tue, Jul 06, 2004 at 04:33:09PM -0400, Andres Salomon wrote:
> > I would like to get kernel-source-2.6.7-3 out tomorrow, if possible.
> > Does anyone have anything pressing that needs to go in before -3 is
> > released? I've s
On Tue, Jul 06, 2004 at 10:45:52PM +0200, Jens Schmalzing wrote:
> Hi,
>
> Andres Salomon writes:
>
> > I would like to get kernel-source-2.6.7-3 out tomorrow, if possible.
>
> Go ahead.
Jens, will you upload powerpc 2.6.7-3 too ? -2 will not be buildable
because of the asfs patch move i believ
On Tue, Jul 06, 2004 at 04:33:09PM -0400, Andres Salomon wrote:
> I would like to get kernel-source-2.6.7-3 out tomorrow, if possible.
> Does anyone have anything pressing that needs to go in before -3 is
> released? I've spoken to luther (who wanted me to wait until tomorrow),
> hch, and wli; the
Hi,
Andres Salomon writes:
> I would like to get kernel-source-2.6.7-3 out tomorrow, if possible.
Go ahead.
Regards, Jens.
--
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
On Mon, Jul 05, 2004 at 20:10 -0300, Robin Blondon wrote:
> Under 2.6, when I have i82365 and orinoco_cs in /etc/modules, lsmod
> shows that yenta_socket is not loaded. "cardctl ident" says:
> Socket 0:
> cs: unable to map card memory!
> cs: unable to map card memory!
> no product info available
>
What provides the '/lib/modules/2.6.7/build' directory? My first try was
kernel-headers-2.6.7, but this seems to go into /usr/src.
I want to try to build arla kernel modules without having the full
kernel-source package installed.. I should just need the headers,
correct?
--
Package: kernel-source-2.6.7
Version: 2.6.7-2
Severity: normal
I have two webcam: Creative CPiA-based, and Labtec-branded quickcam
(using the external module). Both work correctly when plugged into the
computer but not when plugged into an hub. Camera are properly detected
and assigned, but any v
I would like to get kernel-source-2.6.7-3 out tomorrow, if possible.
Does anyone have anything pressing that needs to go in before -3 is
released? I've spoken to luther (who wanted me to wait until tomorrow),
hch, and wli; they're all fine w/ tomorrow (early morning, before
dinstall). I built ker
[ CCing to debian-kernel to see what people think. ]
In case this bug gets reassigned to initrd-tools here's a patch for
mkinitrd that also makes sense. It'll now try /dev/fd, then
/proc/self/fd, then bail.
For those just joining us: MAKEDEV doesn't create /dev/fd on sparc,
initrd-tools cries a r
how can I mount the ntfs drives for read write?
This is a problem on the SFS server as well as on the SFS clients.
Package: initrd-tools
Version: 0.1.71
Severity: critical
Justification: breaks the whole system
For starting a root software RAID in an initrd, mkinitrd creates a
command in /script to assemble the RAID on startup. With raidtools2,
this works fine. But with mdadm the line reads (example)
mdadm -
More information :
Same bug on RedHat :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124420
Here is the output in my /var/log/messages :
---
Jul 6 09:55:34 geru-itea kernel: smb_lookup: find //.Trash-did failed,
error=-
close 257822
thanks
> With CONFIG_DEBUG_INFO=y I get an initrd approximately 10x as large as
> without, and the kernel won't use it. Full kernel messages to point
> should follow soon.
>
> 43428 initrd.img-2.6.7-debug
> 4688initrd.img-2.6.7-nodebug
Don't do that, then. The help text for C
Processing commands for [EMAIL PROTECTED]:
> close 257822
Bug#257822: kernel-source-2.6.7: building with debugging symbols results in an
initrd image that can't be loaded
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to [EMAIL P
Hi,
[EMAIL PROTECTED]:
> With CONFIG_DEBUG_INFO=y I get an initrd approximately 10x as large as
> without, and the kernel won't use it. Full kernel messages to point
> should follow soon.
>
IMHO, mkinitrd should strip these symbols.
Something like this ..:
$ find $WHEREVER/lib/modules/*/kernel
Package: kernel-source-2.6.7
Version: 2.6.7-2
Severity: normal
With CONFIG_DEBUG_INFO=y I get an initrd approximately 10x as large as
without, and the kernel won't use it. Full kernel messages to point
should follow soon.
43428 initrd.img-2.6.7-debug
4688initrd.img-2.6.7-nodebug
-- Syst
Package: kernel-source-2.6.7
Version: 2.6.7-2
Severity: important
Hi,
Since 2.6.5, I've met smbfs problem "Bad EIP value" trying to list the content
of mounted directories.
I have still those errors with the 2.6.7 kernel package.
It seems it is a know bug (http://bugme.osdl.org/show_bug.cgi?id=
On Tue, 06 Jul 2004 02:46:49 +0200, Ciro Mattia Gonano wrote:
[...]
> arch/i386/power/built-in.o(.text+0x253): In function `do_magic':
> : undefined reference to `swsusp_pg_dir'
> make[1]: *** [.tmp_vmlinux1] Error 1
> make[1]: Leaving directory `/usr/src/kernel-source-2.6.7'
> make: *** [stamp-bui
28 matches
Mail list logo
