Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should

2005-11-23 Thread Richard Burton
On Tue, 8 Nov 2005 15:34:48 +0100, Sven Luther wrote [typo corrected]: You can now, just need to add Recommends: blah to the arch/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.

Bug#345918: linux-2.6: modules do not install to correct folder in /lib/modules

2006-01-04 Thread Richard Burton
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

Bug#345918: linux-2.6: modules do not install to correct folder in /lib/modu

2006-01-04 Thread Richard Burton
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

Bug#345918: linux-2.6: modules do not install to correct folder in /lib/modu

2006-01-04 Thread Richard Burton
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)

Bug#345918: linux-2.6: modules do not install to correct folder in /lib/modu

2006-01-04 Thread Richard Burton
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

Bug#345918: Possible solution

2006-01-21 Thread Richard Burton
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,

Bug#345918: Duplicate bug (Was: modules do not install to correct folder)

2006-01-24 Thread Richard Burton
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 -

Bug#358580: linux-2.6: cannot build modules against 2.6.16

2006-03-30 Thread Richard Burton
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

Bug#394974: linux-image-2.6.18-1-686: 2.6.18-3 breaks module compatability

2006-10-24 Thread Richard Burton
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

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Richard Burton
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

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Richard Burton
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

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Richard Burton
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

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Richard Burton
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. So

Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should

2005-11-02 Thread Richard Burton
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

Bug#336450: acknowledged by developer (Bug#336450: fixed in yaird 0.0.11-11)

2005-11-05 Thread Richard Burton
Confirmed fix working. Thanks guys. Richard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should

2005-11-07 Thread Richard Burton
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