David W Noon wrote:
> On Tuesday 06 May 2008 05:25 in article
> <68a4ukF2qr61eU1@mid.individual.net> of alt.os.linux.gentoo, Vitus
> Jensen(vjensen@gmx.de) wrote:
>
>> Vitus Jensen wrote:
> [snip]
>> It's this kernel bug: http://bugzilla.kernel.org/show_bug.cgi?id=8246
>>
>> I've added ec_intr=0 to my kernel commandline to get reasonable
>> boot/suspend/resume times and this prevents ACPI events. How do I get
>> notified when the mentioned patch made it into the mainline kernel?
>> I'm already in the CC list of that bug.
>
> Hi Vitus,
>
> Long time, no read! [I presume you are the Vitus Jensen who used to post
> on Fidonet. If you aren't, I apologise.]
Well, this is Usenet, you can't know who I am, can you? :-)
But you're right, I'm the same guy. Running OS/2 plus LAN Server from
1991-2007 and now nslu plus gentoo. It's not that different as I started
my career with DOS and Minix 1.3. It was on OS2PROG, right? It's a
familiar feeling here: usenet is starting to get as deserted as fidonet :-(
> If you want to get notified by the Gentoo project you need to add a bug
> record to Gentoo's Bugzilla, or CC yourself onto an existing record for
> that same upstream bug. The URI for Gentoo's Bugzilla is:
> https://bugs.gentoo.org/
OK, so probably I did the right thing when I added myself to
bugzilla.kernel.org.
> An alternative is simply to read the change log of whichever kernel
> sources you are using. This is accessible from Gentoo's home page
> whenever the kernel source code is changed. To ensure the change has
> not rolled off the log, you should emerge --sync fairly frequently and
> read the change log a.s.a.p. after your Portage tree has a new kernel
> available.
Hmm, the Changelog is accessable via
http://packages.gentoo.org/package/s...gentoo-sources so I don't
need to update that often. But as that Changelog is fairly condensed the
best is probably to do a diff.
> [My desktop machines do it twice a day, but that might be a
> little difficult for a laptop.]
Is twice a day OK for gentoo mirrors? I thought syncing should be less
often to keep the bandwith usage down? Or is twice a day seldom?
From bugzilla.kernel.org: "I'm seeing the same problem, which isn't fixed
with noapic: Appending ec_intr=0 does indeed shorten the time taken to load
the modules, but ACPI events are not being detected.
(/proc/acpi/button/lid/LID/state is correct however)"
That bug apperently was already fixed, I can boot without ec_intr=0. But
ACPI still aren't reported :-(
Bye,
Vitus
--
Vitus Jensen, Hannover, Germany, Earth, Milky Way, Universe (current)