tags 394974 - moreinfo
thanks
Please show the breakage.
Oops, forgot to paste some in. Here are examples from 2 boxes:
boot.0:Tue Oct 24 08:16:57 2006: nvidia
boot.0:Tue Oct 24 08:16:57 2006: FATAL: Error inserting nvidia
(/lib/modules/2.6.18-1-686/nvidia/nvidia.ko): Invalid module forma
Richard, you said you were able to build fglrx. Did you make something
special ?
I also tried without module-assistant, but cannot figure out why it is
looking
for Makefile.lib.c file.
That module builds fine for me, in fact so far it's the only one that does
against 2.6.16.
bcm5700 doesn't
This appears to be a duplicate of #330081, but since this one is marked
'confirmed' and has a different urgency, I'll leave it to the
maintainers to combine as they see fit.
Yes, it does seem to be the same problem. As it looks to have been fixed now
they should ideally be merged and closed - u
It appears that this has now been fixed in 2.6.15-3, the localversion file
is now installed with the headers. I have tested it with the zaptel module
and it now installs to the correct location.
Can this bug be closed, or has it been left open for a reason?
Richard.
--
To UNSUBSCRIBE, emai
> Calling 'make -C /lib/modules/2.6.15-1-686/build kernelrelease' shows
the
> kernel release as 2.6.15, but shouldn't this show 2.6.15-1-686, (which
is
> defined for UTS_RELEASE in version.h)?
can you give the output of :
dpkg -l | grep linux-header
[EMAIL PROTECTED]:~$ dpkg -l | grep linu
> KDIR := /lib/modules/$(KVER)/build
> modules: $(patsubst %.o,%.c,$(TP_MODULES))
>$(MAKE) -C $(KDIR) M=$(PWD) modules
> ...
> install: modules
>rm -f /lib/modules/$(KVER)/kernel/$(MDIR)/{tp_base,tp_smapi}.ko
>$(MAKE) -C $(KDIR) M=$(PWD) modules_install
We use $(MAKE) KSRC
Congratulations, you are the first to file a bug report against linux
2.6.15 :)
Yay ;-)
Could you tell us exactly what you do to build the module, and check if
this
is not a bug in m-a or your module ?
The official recomended way of building modules is to build inside the
module
tree with
Package: linux-2.6
Version: 2.6.15
When using make module_install with the makefile that comes with the kernel
(/lib/modules/2.6.15-1-686/build/Makefile) modules are not installed into
the correct location in /lib/modules. They build fine but are then installed
to /lib/modules/2.6.15 instead o
On Tue, 8 Nov 2005 15:34:48 +0100, Sven Luther wrote [typo corrected]:
You can now, just need to add
Recommends: to the arch//defines entry.
Now the capability has been added, any chance you could pop this extra line
in? I'd be happy to do it myself, but of course I can't.
Richard.
--
T
2.6.8 is frozen solid for sarge. IF there is interest in having this
added for the etch kernels, can you please reasign it to linux-2.6
I think it should become a permanent addition to all 686 class kernels going
forward, but I don't mind what point that starts at - unstable would be fine
for
Confirmed fix working. Thanks guys.
Richard.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kernel-images 2.6.x-686 and 2.6.x-k7 shoud recommend libc6-i686,
because libc6-686 improves system performance when running with
2.6.x-686 and 2.6.x-k7 kernel-images.
Thanks for the clarification.
I now agree with your suggestion.
I will get it into the tree, but
my TODO list is rather long tod
As Sven said vesafb isn't a module at 2.6.14. So for >=2.6.14 you need
both,
for <2.6.14 you only need to add fbcon to the conf file.
I'm sure you all spotted it - there is a slight error in the above
statement, so for the record it should read:
"As Sven said vesafb isn't a module at 2.6.14.
Try editing /etc/yaird/Default.cfg and add the following:
MODULE vesafb
Ok, that got the vesafb loaded, but that didn't give me video. Added "MODULE
fbcon" as well and that did the job. This testing was all on the 2.6.12.
As Sven said vesafb isn't a module at 2.6.14. So for >=2.6.14 you need
Nvidia. Ok (or "ok" is perhaps an exageration: problems with this
specific hardware vendor is not really a surprise to me...)
Yeah, but it plays native Linux Quake 4 very nicely!
You did remember to uninstall yaird before regenerating the ramdisk?
Yep, and to confirm it I checked the size of
This could be changes to video drivers in the kernel. Please describe
your graphics card used.
Oops, I did intened to mention that. It's an Nvidia GeForce 6600GT 128MB
(generic unbranded reference board).
Please try the following:
1) add "ramdisk = /usr/sbin/mkinitrd.yaird" to /etc/kernel-im
16 matches
Mail list logo
