lintian warnings [was: kernel-image-2.6.8-amd64_2.6.8-4_i386.changes ACCEPTED]

2004-10-02 Thread maks attems 
cool, 
but your package is generating by far the most lintian warnings,
of the debian kernel team, please run "lintian -i foo.deb"
before uploading your packages:
http://lintian.debian.org/reports/mDebian_Kernel_Team.html

the "native-package-with-dash-version" is harmless,
but most other warnings should be adressed.

a++ maks

Re: lintian warnings [was: kernel-image-2.6.8-amd64_2.6.8-4_i386.changes ACCEPTED]

2004-10-02 Thread maks attems 
On Sat, 02 Oct 2004, maks attems wrote:

> cool, 
> but your package is generating by far the most lintian warnings,
> of the debian kernel team, please run "lintian -i foo.deb"
> before uploading your packages:
> http://lintian.debian.org/reports/mDebian_Kernel_Team.html
> 
> the "native-package-with-dash-version" is harmless,
> but most other warnings should be adressed.

fs wondered the difference between amd and 386 packages.

here the others from the "Debian kernel team" mostly source, i386:
http://lintian.debian.org/reports/mDebian_kernel_team.html

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Re: lintian warnings [was: kernel-image-2.6.8-amd64_2.6.8-4_i386.changes ACCEPTED]

2004-10-02 Thread maks attems 
On Sat, 02 Oct 2004, "Frederik Schüler" wrote:

> > but your package is generating by far the most lintian warnings,
> > of the debian kernel team, please run "lintian -i foo.deb"
> > before uploading your packages:
> > http://lintian.debian.org/reports/mDebian_Kernel_Team.html

any args against unifying the Maintainer names to uppercase?
waiting for feedback before doing this.

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#272029: acknowledged by developer (Re: Bug#272029: FATX filesystem support)

2004-10-06 Thread maks attems 
retitle 272029 xbox: fatx fs support
thanks

On Mon, 04 Oct 2004, Robert Millan wrote:
> [ Delayed due to MTA problems ]
> 
> On Wed, Sep 29, 2004 at 06:53:52PM +0200, maks attems wrote:
> > On Wed, 29 Sep 2004, Robert Millan wrote:
> > > On Wed, Sep 29, 2004 at 05:36:30PM +0200, maks attems wrote:
> > > 
> > > Have you read the bug reports?  I haven't sent ANY patch for Xbox support.
> > > Why do you close bug reports without even reading them to understand what 
> > > the
> > > requests are?  Please read all the bug reports and fix this mess.  I don't
> > > have time for BTS ping-pong games.
> > 
> > it seems you didn't read the response from the debian team.
> > hey calm down.
> 
> Yes.  Here, I'm calmed.  I read the response before and replied to it.  The
> conclussion was that the maintainer team didn't want to provide this feature,
> but they can't close the bug since the request is still valid.  They choosed
> to add a "wontfix" tag instead.  Please read the log, it's all archived
> (bug #272029).

thanks for the pointer, debian-kernel has also the thread, i know it.
anyway ack for not willing to do ping/pong games.
  
> > > #272029: add xbox support to debians kernel
> > >   -- this is actualy FATX filesystem support, please retitle
> > > #272063: support for Xbox partitions
> > >   -- this is not fixed, please reopen
> > > #272067: support for USB devices from Xbox
> > >   -- this is not fixed, please reopen
> > 
> > none of those is in any consideration until any of these patches,
> > is merged upstream!
> 
> Then please reopen and add wontfix tags.  Note, however, that #272063 and
> #272067 (specialy #272067) are unrelated to the first one and a refusal from
> the team to fix #272029 doesn't imply a refusal to fix the latter.  I would
> appreciate an explicit message about them if that is the case.

well i'm also member to the team and the policy is quite clear,
if you want to have a new feature added to the debian kernel,
you must get it included upstreams.
from that position the 3 requests are quite similar.

you could probably open 5 more wishlist bugs for xbox subsystem patches,
please understand that the kernel package has lots of bugs open,
and that for a better overview it's nicer to not have many duplicate bugs
with the the same destiny.

you will find that current debian kernel are quite similar
to vanilla kernel.org versions.
 
> > > FYI, I do have patches for the actual Xbox support and haven't sent them 
> > > yet
> > > because some parts are conflictive and break other functionality.
> > 
> > well the debian bts is not a bookmark collection of random wishes.
> 
> Yes, it is.  Not random though, we archive the wishes of our users in the BTS
> in the form of "wishlist bugs".

again that's great, 
but i don't think that a growing collection of those makes sense.
even more if policy regarding merge of those request is quite clear
for debian kernel.
 
> > please get it right to the MAINTAINERS!
> 
> If you look at lkml archives, you'll see how this is already being worked on.
> It's not easy, though, since Linus has been quite uncooperative with
> Xbox-related patches.  I hope the same situation doesn't duplicate in Debian.

we can't replace the lkml review process,
linus is quite cool regarding ports as he initiated the first one to alpha.
just look what m32r merged. the best thing to do is to get your patches
merged by subsystem maintainers, from there they propagate.
 
> > it would make a _lot_ of sense to close #272029,
> 
> No, you have to keep it open untill either fixed or noone interested in it.

it's not a matter of "interest", but of policy.
 
> > out of sympathy for your work and the possibility to keep track
> > of upstream status there i kept it open.
> 
> Yes, that's one of the points why it should be kept open.
> 
> Now I ask you politely to reopen these bugs and, if you consider it adequate,
> add "wontfix" and/or "upstream" tags to them.  Also please retitle #272029
> to indicate it is about FATX filesystem and not Xbox support.

ok retitled, but leaved the xbox keyword.
i removed the other 2 bugs from cc, as dexcribed above.



--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Re: question about input layer

2004-10-14 Thread maks attems 
On Wed, 06 Oct 2004, Paul Akkermans wrote:

> Hi group,
> 
> I am trying to analyze the input layer of the kernel 2.6.7 but I find it 
> really hard to understand. Mainly this is because there is no commend to the 
> code in the kernel input files. Can anybody help me?
> 
> thanks in advance,
> 
> Paul Akkermans

asking better questions may help.
also you might get more answers on kernelnewbies.
-> http://www.kernelnewbies.org/

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Re: Which 2.4 kernel-source for sarge?

2004-08-21 Thread maks attems 
On Fri, 20 Aug 2004, Thiemo Seufer wrote:

> dann frazier wrote:
> > We need to come to an agreement about which kernel-source we will ship
> > for sarge.  According to http://wiki.debian.net/index.cgi?DebianKernel, 
> > everyone w/ 2.4.26 has 2.4.27 except for powerpc (sparc is building).
> > 
> > 2.4.26 has had more testing time - its used in d-i RC1.  The latest
> > kernel-source-2.4.26 package appears to be in good shape with respect
> > to security.
> > 
> > What arguments are there for moving to 2.4.27 prior to sarge?
> 
> Updated device mapper and IPsec.

important sparse fixes.
and newer libata, acpi, xfs and netdrv.

Bug#234889: gnome-applets: battery monitor on Linux 2.6.5: patch

2004-08-29 Thread maks attems 
tags 234889 moreinfo
thanks


this bugreport has getting far from a sane state,
but i hope it can be resolved in peacefull mind. :)

stan pinte you mentioned a self compiled kernel,
could you please post your .config and dmesg?

you might want also use `acpi_listen` as root to see
if you are getting acpi events, please wait for them
for some time.

on my x86 laptop both kernel and acpid is working.
couldn't test gnome-applets.

thanks for further info.

--
maks
kernel janitor  http://janitor.kernelnewbies.org/


signature.asc
Description: Digital signature

Bug#245668: kernel-source-2.6.5: intel8x0: IEC958 output not working anymore

2004-08-29 Thread maks attems 
On Wed, 07 Jul 2004, Roland Stigge wrote:

> The problem persists for 2.6.7.

bug could be already closed as concerning self-compiled.
please retry with current stock debian kernel-images for 2.6.8
and report back.



--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#268871: Documentation bug

2004-08-29 Thread maks attems 
tags 268871 pending
thanks

On Sun, 29 Aug 2004, Remco Blaakmeer wrote:

> Package: kernel-source-2.6.8
> Version: 2.6.8-5
> Severity: minor
> 
> I found an error in the documentation. Please apply the patch below.
> 
> --- init/Kconfig.orig   2004-08-14 07:37:38.0 +0200
> +++ init/Kconfig2004-08-29 17:16:02.0 +0200
> @@ -123,7 +123,7 @@
>   process and it's parent. Note that this file format is 
>   incompatible
>   with previous v0/v1/v2 file formats, so you will need updated 
>   tools
>   for processing it. A preliminary version of these tools is 
>   available
> - at .
> + at .
> 
>  config SYSCTL
> bool "Sysctl support"
> 

sorry but aboves url doesn't work for me.
upstream has this patch, which i added to yet unreleased
debian kernel source 2.6.8-6:
http://linux.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]|[EMAIL PROTECTED]



--
maks
kernel janitor  http://janitor.kernelnewbies.org/

reassigning bugs from older kernel sources

2004-08-29 Thread maks attems 
reassign #249780 kernel
reassign #250164 kernel
reassign #256486 kernel
reassign #256762 kernel
reassign #257815 kernel
reassign #264482 kernel
reassign #254645 kernel
reassign #257950 kernel
reassign #258676 kernel
reassign #261195 kernel
reassign #261259 kernel
reassign #261706 kernel
reassign #264186 kernel
reassign #264190 kernel
reassign #266839 kernel
thanks

Bug#268899: kernel-image-2.6.8-i386: "the directory /lib/modules/* still exists."

2004-08-29 Thread maks attems 
reassign 268899 kernel-package
thanks

On Sun, 29 Aug 2004, Michael Piefel wrote:

> Package: kernel-image-2.6.8-i386
> Severity: minor
> 
> Everytime I install a kernel, I get the very confusing (long text!)
> message that something possibly dangerous is going on because, say,
> /lib/modules/2.6.8-1-386 "still exists" (already exists is a far better
> description, actually).
> 
> "I can't tell the difference." the message tells me. I beg to differ.
> All that's there is the "build" link that the kernel-headers package
> (from the same source!) installed. This should be fairly easy to spot.
> 
> Rephrased as a wishlist bug: Please try to make the detection a little
> smarter to avoid some of the warnings in more common cases.
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.6-1-k7
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8

well there some messages from kernel-packages may be rephrased
after sarge, therefor reassigning this bug.

what it tells you infact is that you are overwriting your
old kernel modules with the newer ones.

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#245668: kernel-source-2.6.5: intel8x0: IEC958 output not working anymore

2004-08-29 Thread maks attems 
could you please take a look at this debian bug report:
intel8x0: IEC958 digital output (S/PDIF) is said not work
since kernel 2.6.4.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245668

thanks 

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#270451: 3com 3c905x dhcp not working in kernel 2.6.x on debian sarge

2004-09-09 Thread maks attems 
tags 270451 moreinfo
thanks

On Tue, 07 Sep 2004, Kelly, Mark wrote:

> Package: kernel 
> Version: 2.6.7 & 2.6.8
> 
> I cannot get 3com 3c905b or 3c905c network cards to detect dhcp when using
> any version of 2.6.x kernels available in sarge or unstable trees.  Both
> cards are in the same machine and boot correctly into kernel 2.4.26.
> 
> I am using Debian Sarge, kernel 2.6.7 and kernel 2.6.8-1 packages.

your report is confusing.
please provide dmesg of working and non working setup?
which dhcp client are you using?

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#270883: kernel-image-2.6.8-1-686: ATAPI/IDE drives not detected with ICH5/i875

2004-09-09 Thread maks attems 
tags 270883 moreinfo
thanks

On Thu, 09 Sep 2004, J??r??me Dubois wrote:

> Package: kernel-image-2.6.8-1-686
> Version: 2.6.8-2
> Severity: normal
> 
> Helo,
> 
> Since kernel-image-2.6.5 my Atapi drive isn't detected at boot.
> It work perfectly with previous 2.6 (2.6.4).
> Sata drives work perfectly as scsci devices (sda & sdb).
> 
> My Motherboard is an Asus P4C800-E Deluxe with ICH5-R.
> I've tried all modes in the bios (enhanced & compatible) with no result.
> 
> Hardware raid is disabled in the bios.
> Promise chip is disabled to.
> 
> I've tested with two differents atapi drives, a CD-R/RW burner and a
> DVD-ROM reader.
> 
> Thanks in advance for your attention.

please provide at least dmesg of working setup.

 
--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#271396: Kernel help typo

2004-09-15 Thread maks attems 
On Tue, 14 Sep 2004, Matthew Wilcox wrote:

> On Mon, Sep 13, 2004 at 11:10:11PM +0200, maks attems wrote:
> >   Use the CPUFreq governor 'userspace' as default. This allows
> >   you to set the CPU frequency manually or when an userspace 
> > - programm shall be able to set the CPU dynamically without having
> > + programme shall be able to set the CPU dynamically without having
> >   to enable the userspace governor manually.
> 
> In British English, "programme" refers to a television
> schedule, "program" refers to something a computer runs, see:
> http://www.chambersharrap.co.uk/chambers/chref/chref.py/main?query=programme&title=21st
> 
> Americans use "program" for everything, so using programme here is wrong
> for everyone ;-)
 
/me laughing

thanks for the explanation, my french mother tongue probably
agreed to aboves change :-)

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#271780: kernel 2.6.8 only allows root to see cdrw as a cd writer in k3b

2004-09-15 Thread maks attems 
reassign 271780 k3b
thanks


please check if k3b needs upgrade, or if it works with latest fixed
cdrecord and dvd+rw-tools in unstable.

Bug#271396: Kernel help typo

2004-09-13 Thread maks attems 
On Mon, 13 Sep 2004, Gavin Sandie wrote:

> drivers/cpufreq/Kconfig
> 
> The help for CONFIG_CPU_FREQ_GOV_POWERSAVE contains a typo.
> It starts with 'Theis', I think this should be 'This'.
>
> I have found a further two typos in the
> drivers/cpufreq/Kconfig file.
> 
> The help section for CPU_FREQ_DEFAULT_GOV_USERSPACE and
> CPU_FREQ_GOV_USERSPACE both have contain 'programm' when I
> think this should read 'programme'.

belows patch corrects found issues.


--- linux-2.6.9-rc2-orig/drivers/cpufreq/Kconfig2004-09-13 
22:51:22.0 +0200
+++ linux-2.6.9-rc2/drivers/cpufreq/Kconfig 2004-09-13 23:04:56.0 
+0200
@@ -33,7 +33,7 @@ config CPU_FREQ_DEFAULT_GOV_USERSPACE
help
  Use the CPUFreq governor 'userspace' as default. This allows
  you to set the CPU frequency manually or when an userspace 
- programm shall be able to set the CPU dynamically without having
+ programme shall be able to set the CPU dynamically without having
  to enable the userspace governor manually.
 
 endchoice
@@ -51,7 +51,7 @@ config CPU_FREQ_GOV_POWERSAVE
tristate "'powersave' governor"
depends on CPU_FREQ
help
- Theis cpufreq governors set the frequency statically to the
+ This cpufreq governors set the frequency statically to the
  lowest available CPU frequency.
 
  If in doubt, say Y.
@@ -61,7 +61,7 @@ config CPU_FREQ_GOV_USERSPACE
depends on CPU_FREQ 
help
  Enable this cpufreq governor when you either want to set the
- CPU frequency manually or when an userspace programm shall
+ CPU frequency manually or when an userspace programme shall
   be able to set the CPU dynamically, like on LART 
  
 

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#270451: 3com 3c905x dhcp not working in kernel 2.6.x on d ebian sarge

2004-09-13 Thread maks attems 
On Mon, 13 Sep 2004, Kelly, Mark wrote:

> The title of the file is the kernel version each was from.  Yes the kernel
> sees the card in 2.6.8, but it will not assign an ip to it from the dhcp
> server.   I am using the standard dhcp client that installs from the sarge
> distribution cd's.  oh I am using SMP kernel too, if that makes any
> difference.

for 3c59 shouldn't but when speacking of kernel version i meant
full kernel version, the top of dmesg or if you prefer
$ uname -a
also your /boot/config-2.6.8* would help.
 
> I tried to use the debian installer rc1 to install to a new hard drive, but
> it will stop at trying to obtain a dhcp ip address also when I tell it to
> use the 2.6 kernel, it will work fine when using the default 2.4 kernel.  
 
that's no help to narrow your problem down, please post:
dpkg -l "dhcp*" | egrep ^ii

> ps. sorry I dropped the bug number, sending again.

thanks
 

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#273524: kernel-image-2.6.8-1-386: Panics when mounting initrd.

2004-09-27 Thread maks attems 
On Sun, 26 Sep 2004, Bob Hauck wrote:
..
> Fails to boot.  Panics when mounting initrd (cramfs).  Worked fine with
> kernels up to 2.6.8-2.  Reinstalled 2.6.8-2 and it again works fine.
> 
> This machine is fairly old, has an AMD CPU upgrade module, is a desktop
> machine not a laptop.  The info from /proc is:

please send dmesg of your machine.
what was the last message from 2.6.8-3 when trying to mount initrd?
 
--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#268208: Possible solution for smp problem

2004-09-27 Thread maks attems 
On Sun, 26 Sep 2004, Margarita Manterola wrote:

> I've been having the same problem both with 2.6.7 and 2.6.8 images
> (always with 686 smp).
> 
> The problem is directly related to acpi and I was using the parameter
> "acpi=off" at boot time to solve it.  Today, I recompiled the kernel,
> changing as follows:
> 
..

please send dmesg of succesfull boot.

thanks 
maks

Bug#273474: APM broken in image-2.6.8-1 version 2.6.8-3, worked in 2.6.8-1

2004-09-27 Thread maks attems 
On Sun, 26 Sep 2004, Marcus C. Gottwald wrote:
..
> After downgrading back to 2.6.8-1 (the deb was still on my
> disk), everything is working again.

please send dmesg?
 
--
maks

Bug#268208: Possible solution for smp problem

2004-09-27 Thread maks attems 
On Mon, 27 Sep 2004, maks attems wrote:

> On Sun, 26 Sep 2004, Margarita Manterola wrote:
> 
> > I've been having the same problem both with 2.6.7 and 2.6.8 images
> > (always with 686 smp).
> > 
> > The problem is directly related to acpi and I was using the parameter
> > "acpi=off" at boot time to solve it.  Today, I recompiled the kernel,
> > changing as follows:
> > 
> ..
> 
> please send dmesg of succesfull boot.

ahh ups didn't read the hole thread,
it would be great if you tested latest rc from linus.
he has acpi fixes for latest intel boards i guess 2.6.9-rc2
works fine with initial debian config concerning acpi?

 
--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#273673: please enable CONFIG_SCSI_MULTI_LUN

2004-09-27 Thread maks attems 

Package: kernel-image-2.6.8-powerpc
Severity: wishlist
thanks

ppc is build without CONFIG_SCSI_MULTI_LUN that makes a lot 
of card readers not available for ppc folks.
it's enabled on i386, amd, ia64 and even alpha.

 I think we even agreed to kill the config option in mainline


--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#273474: APM broken in image-2.6.8-1 version 2.6.8-3, worked in 2.6.8-1

2004-09-28 Thread maks attems 
On Mon, 27 Sep 2004, Marcus C. Gottwald wrote:
..
> There's a difference in APIC treatment. Here is the part when
> using 2.6.8-1 (APM working fine):
> 
>   Sep 26 13:06:51 lilith kernel: Dell Latitude with broken BIOS detected. 
> Refusing to enable the local APIC.
>   Sep 26 13:06:51 lilith kernel: Built 1 zonelists
>   Sep 26 13:06:51 lilith kernel: Kernel command line: auto 
> BOOT_IMAGE=Debian_default ro root=305 acpi=off
>   Sep 26 13:06:51 lilith kernel: Initializing CPU#0
> 
> Here is the part when using 2.6.8-3:
> 
>   Sep 26 13:01:45 lilith kernel: Built 1 zonelists
>   Sep 26 13:01:45 lilith kernel: Kernel command line: 
> BOOT_IMAGE=Debian_default ro root=305 acpi=off
>   Sep 26 13:01:45 lilith kernel: Local APIC disabled by BIOS -- reenabling.
>   Sep 26 13:01:45 lilith kernel: Found and enabled local APIC!
>   Sep 26 13:01:45 lilith kernel: Initializing CPU#0

i'm a bit confused, but the 2 dmesg that you appended are both
regarding kernel 2.6.8-1.
the difference seems your boot cmdline. in the second case noacpi is not
parsed and therefor acpi enabled. 
AFAIK lilo prepends "auto" before the whole cmdline what happened to the
second?

so your problem doesn't seem 2.6.8-1 specific.
didn't see an apm change when going through the changelog concerning
2.6.8-3 versus 2.6.8-3-1.

what bootloader are using?

a++ maks

Bug#273474: APM broken in image-2.6.8-1 version 2.6.8-3, worked in 2.6.8-1

2004-09-28 Thread maks attems 
On Tue, 28 Sep 2004, Marcus C. Gottwald wrote:

> I never used a "noacpi" command, always "acpi=off". And as far
> as I could see, ACPI was never turned on, only the messages
> regarding (the local?) APIC were different.

could you try to build latest kernel-source-2.6.8
with belows reverted patch and boot that?
save the mail and use 'patch -p1 -R´
 

diff -Nru a/arch/i386/kernel/dmi_scan.c b/arch/i386/kernel/dmi_scan.c
--- a/arch/i386/kernel/dmi_scan.c   2004-08-19 12:35:05 -07:00
+++ b/arch/i386/kernel/dmi_scan.c   2004-08-19 12:35:05 -07:00
@@ -162,26 +162,6 @@
 #define NO_MATCH   { DMI_NONE, NULL}
 #define MATCH  DMI_MATCH
 
-/*
- * Some machines, usually laptops, can't handle an enabled local APIC.
- * The symptoms include hangs or reboots when suspending or resuming,
- * attaching or detaching the power cord, or entering BIOS setup screens
- * through magic key sequences.
- */
-static int __init local_apic_kills_bios(struct dmi_blacklist *d)
-{
-#ifdef CONFIG_X86_LOCAL_APIC
-   extern int enable_local_apic;
-   if (enable_local_apic == 0) {
-   enable_local_apic = -1;
-   printk(KERN_WARNING "%s with broken BIOS detected. "
-  "Refusing to enable the local APIC.\n",
-  d->ident);
-   }
-#endif
-   return 0;
-}
-

 /* 
  * Toshiba keyboard likes to repeat keys when they are not repeated.
@@ -793,30 +773,6 @@
} },
 
/* Machines which have problems handling enabled local APICs */
-
-   { local_apic_kills_bios, "Dell Inspiron", {
-   MATCH(DMI_SYS_VENDOR, "Dell Computer Corporation"),
-   MATCH(DMI_PRODUCT_NAME, "Inspiron"),
-   NO_MATCH, NO_MATCH
-   } },
-
-   { local_apic_kills_bios, "Dell Latitude", {
-   MATCH(DMI_SYS_VENDOR, "Dell Computer Corporation"),
-   MATCH(DMI_PRODUCT_NAME, "Latitude"),
-   NO_MATCH, NO_MATCH
-   } },
-
-   { local_apic_kills_bios, "IBM Thinkpad T20", {
-   MATCH(DMI_BOARD_VENDOR, "IBM"),
-   MATCH(DMI_BOARD_NAME, "264741U"),
-   NO_MATCH, NO_MATCH
-   } },
-
-   { local_apic_kills_bios, "ASUS L3C", {
-   MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."),
-   MATCH(DMI_BOARD_NAME, "P4_L3C"),
-   NO_MATCH, NO_MATCH
-   } },
 
{ broken_acpi_Sx, "ASUS K7V-RM", {  /* Bad ACPI Sx table */
MATCH(DMI_BIOS_VERSION,"ASUS K7V-RM ACPI BIOS Revision 
1003A"),
diff -Nru a/drivers/acpi/bus.c b/drivers/acpi/bus.c
--- a/drivers/acpi/bus.c2004-08-19 12:35:05 -07:00
+++ b/drivers/acpi/bus.c2004-08-19 12:35:05 -07:00
@@ -590,10 +590,9 @@
 }
 
 
-static int __init
-acpi_bus_init (void)
+void __init
+acpi_early_init (void)
 {
-   int result = 0;
acpi_status status = AE_OK;
struct acpi_buffer  buffer = {sizeof(acpi_fadt), &acpi_fadt};
 
@@ -617,7 +616,7 @@
status = acpi_get_table(ACPI_TABLE_FADT, 1, &buffer);
if (ACPI_FAILURE(status)) {
printk(KERN_ERR PREFIX "Unable to get the FADT\n");
-   goto error1;
+   goto error0;
}
 
 #ifdef CONFIG_X86
@@ -640,12 +639,40 @@
}
 #endif
 
-   status = acpi_enable_subsystem(ACPI_FULL_INITIALIZATION);
+   status = acpi_enable_subsystem(~(ACPI_NO_HARDWARE_INIT | 
ACPI_NO_ACPI_ENABLE));
+   if (ACPI_FAILURE(status)) {
+   printk(KERN_ERR PREFIX "Unable to enable ACPI\n");
+   goto error0;
+   }
+
+   return;
+
+error0:
+   disable_acpi();
+   return;
+}
+
+static int __init
+acpi_bus_init (void)
+{
+   int result = 0;
+   acpi_status status = AE_OK;
+   extern acpi_status  acpi_os_initialize1(void);
+
+   ACPI_FUNCTION_TRACE("acpi_bus_init");
+
+   status = acpi_os_initialize1();
+
+   status = acpi_enable_subsystem(ACPI_NO_HARDWARE_INIT | 
ACPI_NO_ACPI_ENABLE);
if (ACPI_FAILURE(status)) {
printk(KERN_ERR PREFIX "Unable to start the ACPI 
Interpreter\n");
goto error1;
}
 
+   if (ACPI_FAILURE(status)) {
+   printk(KERN_ERR PREFIX "Unable to initialize ACPI OS 
objects\n");
+   goto error1;
+   }
 #ifdef CONFIG_ACPI_EC
/*
 * ACPI 2.0 requires the EC driver to be loaded and work before
@@ -693,7 +720,6 @@
/* Mimic structured exception handling */
 error1:
acpi_terminate();
-error0:
return_VALUE(-ENODEV);
 }
 
diff -Nru a/drivers/acpi/osl.c b/drivers/acpi/osl.c
--- a/drivers/acpi/osl.c2004-08-19 12:35:05 -07:00
+++ b/drivers/acpi/osl.c2004-08-19 12:35:05 -07:00
@@ -71,6 +71,12 @

Bug#250123: please try newer kernel

2004-09-28 Thread maks attems 
tags 250123 moreinfo
thanks

do you still experience this with current 2.6.8 kernels in testing?

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#259042: kernel-image-2.6.7-1-686-smp: Refuses keyboard input after some time (esp in vim)

2004-09-28 Thread maks attems 
On Tue, 13 Jul 2004, Cameron Kerr wrote:

> This only affects the SMP package, the uniprocessor is fine (except I'm
> running a P4, so the SMP version would be good to have.
> 
> This bug is most easily found when I run vim. I can no longer type at
> the console with a PS/2 keyboard (actually, a DIN keyboard with a PS/2
> adaptor)

is still happening in current 2.6.8 kernel package?


--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#272029: acknowledged by developer (Re: Bug#272029: FATX filesystem support)

2004-09-29 Thread maks attems 
retitle 272029 add xbox support to debians kernel
thanks

On Sun, 26 Sep 2004, Robert Millan wrote:

> On Sat, Sep 25, 2004 at 12:16:55PM +0900, Horms wrote:
> > tag 272029 +wontfix 
> > 
> > > It's not fixed.  Add a wontfix and/or upstream tags if you like.
> > 
> > This is not a bug in the kernel.
> > It is a random feature request.
> 
> It is a wishlist request and is perfectly legitimate.
> 
> > We have offered the soloution 
> > of getting it merged upstream,
> > or greating a kernel-patch package.
> > But if you want it lying around
> > in the bug tracker, so be it.
> 
> I'll explore the suggested solutions and keep track of this bug.
> 
> Thanks.

well so keep 1 "bug" not 3.
retitled, and i'll close the other 2.
 
--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#272029: acknowledged by developer (Re: Bug#272029: FATX filesystem support)

2004-09-29 Thread maks attems 
On Wed, 29 Sep 2004, Robert Millan wrote:

> On Wed, Sep 29, 2004 at 05:36:30PM +0200, maks attems wrote:
> 
> Have you read the bug reports?  I haven't sent ANY patch for Xbox support.
> Why do you close bug reports without even reading them to understand what the
> requests are?  Please read all the bug reports and fix this mess.  I don't
> have time for BTS ping-pong games.

it seems you didn't read the response from the debian team.
hey calm down.
 
> #272029: add xbox support to debians kernel
>   -- this is actualy FATX filesystem support, please retitle
> #272063: support for Xbox partitions
>   -- this is not fixed, please reopen
> #272067: support for USB devices from Xbox
>   -- this is not fixed, please reopen

none of those is in any consideration until any of these patches,
is merged upstream!

 
> FYI, I do have patches for the actual Xbox support and haven't sent them yet
> because some parts are conflictive and break other functionality.

well the debian bts is not a bookmark collection of random wishes.
please get it right to the MAINTAINERS!

it would make a _lot_ of sense to close #272029,
out of sympathy for your work and the possibility to keep track
of upstream status there i kept it open.

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#273474: APM broken in image-2.6.8-1 version 2.6.8-3, worked in 2.6.8-1

2004-09-29 Thread maks attems 
On Wed, 29 Sep 2004, Marcus C. Gottwald wrote:

> maks attems wrote (Tue 2004-Sep-28 23:09:22 +0200):
> > could you try to build latest kernel-source-2.6.8
> > with belows reverted patch and boot that?
> 
> All right, I did:
..
great thanks!
 
> - dmesg shows "broken BIOS detected" again.
> - Function keys do work again.
> - Resume does work again.
> - vga=773 doesn't work anymore (console remains blank after
>   video mode switch); didn't investigate any further.

as this send patch did not fix the issues concerning compaq laptop.
it will be backed out for next kernel-source.
thanks for your feedback

a++ maks

Re: Is kernel-patch-2.4-kgdb still relevant?

2004-09-29 Thread maks attems 
On Wed, 29 Sep 2004, Jeroen van Wolffelaar wrote:

> Hi,
> 
> | Package: kernel-patch-2.4-kgdb (1.9-1)
> | GDB debugging for the kernel
> | 
> | This package provides the patches for the 2.4.23 kernel (and should
> | apply to other nearby versions) for the i386 and powerpc architectures.
> | It allows you to compile the kernel with debugging symbols for gdb. 
> 
> Is this package still applicable to 2.4.27 or whatever kernel will ship
> with Sarge? If not, it should probably have a RC bug filed on it, if
> yes, it should have an import bug filed regarding the outdated
> description.
> 
> Note that I'm not subscribed here, please CC me, I'm fine filing the bug
> myself, but don't know which of the two cases it is...

patches applies with some fuzz/offset to current kernel-source-2.4.27.
didn't try to run it.
version 1.9 is 9 month old. 

nevertheless people wanting to use a debugger should use -mm trees.
akpm includes up2date kgdb patches.
so i do not see a real value of that patch.
 
--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#260971: Random System Hangs

2004-09-29 Thread maks attems 
tags 260971 moreinfo
thanks

On Thu, 22 Jul 2004, Daniel Burton wrote:
..
> My system stops and becomes completely unresponsive, both locally and 
> over the network at random times, usually within two hours of booting on 
> this kernel version.  It is okay on version 2.6.5-1-k7.  There is no 
> warning and apparently no consistent pattern of what I'm doing when this 
> happens, except that so far, it has always happened on the local 
> terminal (i.e. not an X Window session).  I spend a lot of time on the 
> terminal of this system though, so this is not surprising.

do you still experience this with current debian 2.6.8 images?

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#220688: mouse problems

2004-09-29 Thread maks attems 
do you still experience mouse problems,
if yes this should probably be rassigned to xfree,
or could you fix your XF86Config-4 inbetween?

thanks for feedback.

--
maks
kernel janitor  http://janitor.kernelnewbies.org/

Bug#284221: utter lack of acenic drivers on i386, hppa

2004-12-05 Thread maks attems 
On Sat, 04 Dec 2004, Matthew Wilcox wrote:

> On Sat, Dec 04, 2004 at 01:01:33PM -0500, Kyle McMartin wrote:
> > * ACENIC firwmare, driver disabled:
> > . drivers/net/acenic_firmware.h
> > 
> > So there's a good reason why you're unable to use these cards.
> 
> ITYM "good reason to switch to Ubuntu, Gentoo or Fedora".  HTH.
> 
agreed.

beside debian-legal having no consensus on that issue,
don't latest gr allow to ship those for at least sarge?

--
maks
kernel janitor  http://janitor.kernelnewbies.org/