I just upgraded from 3.3.8 to 3.5.7 both done with kernel seeds (thanks!).
After upgrading my keyboard and mouse don't work together under X. Usually would think this is a x11 driver issue, but the only thing I changed is the kernel.

My keyboard is PS2 going into a KVM. The KVM connects to the computer via USB.
The mouse is directly connected.
On tty1 keyboard works. I 'startx' and the keyboard still works but the mouse doesn't I unplug the KVM's usb, and the mouse works.

If I plug in a different USB keyboard (which also has a trackball) the USB keyboard and the mouse works (but not the trackball).

At the end of a less than stellar day, I have finally finished up the revamp for the main page. Time to show the almost five years of continuous operation of the site and its mirrors. I have also added another mirror. Please note its full address is listed in my sig below. As if all that wasn't enough, I've just uploaded .configs for 3.0.52, 3.2.34, 3.4.19, and 3.6.7 in both x86 and x86_64 flavors. Enjoy!

For the curious Mirror 4: is hosted by Apache running on Gentoo on a Raspberry Pi, which is in turn, powered from a USB port on a HP Microserver.
About a year ago the site was hosted on a Sun Ultrasparc U10, which failed.

Its now down from 60w to <2.5w._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

We need distinct terms for the input device switcher and the virtual machine platform. I run into this confusion every time I mention it. _________________Gentoo StudioGentoo Studio in open beta. Feedback wanted.

For the curious Mirror 4: is hosted by Apache running on Gentoo on a Raspberry Pi, which is in turn, powered from a USB port on a HP Microserver.
About a year ago the site was hosted on a Sun Ultrasparc U10, which failed.

If it's the kind of KVM that draws power from the USB ports, it is possible that the KVM overloads the USB port electrically. If I'm not mistaken, something of this nature was discussed, and I think we came upon the fact that somehow, the driver for the older kernel provides more current to the USB port.

The best way to know would be to go over the last thread and look for discussion of USB power output.

I've actually been playing with the pf sources, as they continue to use the BFS, and am considering coming out with .configs for them in lieu of zen sources. I am hesitant to do rt sources as I've found them to be tricky to get right. They don't release a lot of source, so it could be possible, but I wouldn't get my hopes up if I were you. Ck sources has a possibility, but I'm not quite sure what their claim to fame is. What is the special trick for that set of sources?

I've also considered doing vmware .configs, but I have yet to get my vmware to start X, which seems to be a requirement. When I get back to playing with that, who knows? I might just expand my operation, so to speak.

sink128,

I figured that would be the issue. I'm not sure how they control the current for the USB via the kernel, but apparently, they can. I'm wondering if they're dialing all that down a bit so they don't blow fuses and such.

If you use vmware, you are probably doing it wrong, unless you need to run a provided vmware image.
My preference is Kernel Virtual Machine (KVM) or VirtualBox. I did use vmware server until it became obsolete.

Anyway - Gentoo is about choice - everyone should use whatever toll that best fits the job at hand._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

I may offer rt .configs in the future, but I'm not so sure about the ck. If I get the BFS in pf-sources, which I do, I don't see a big advantage in going with source that is even more experimental. For now, I'm experimenting with the pf sources just making sure the BFS still works as well as it ever did. I may download the latest ck to see what's up with it.

NeddySeagoon,

I won't doubt I'm doing it wrong. I started with a vmserver-sources kernel, then emerged app-emulation/vmware-workstation. I recently shared that .config with someone who says it looks like I might have missed some options when setting up that particular kernel. I may get back to playing with that some time in the future. For now, I'm still geeking out on the i-Phone I recently acquired. The newest toy sometimes takes attention from the other toys.

I've done well with using a vanilla .config to get my rt-sources going. I just tweak the rt config options, filesystems, and device drivers. It might not be that much more off than that to set up .configs just for rt. _________________Gentoo StudioGentoo Studio in open beta. Feedback wanted.

It was a very dreary day here in Cali; a great day to whip up some kernel seeds. I've just uploaded .configs for 2.6.32-hardened-r141, 3.0.53-gentoo, 3.2.34-hardened-r1, and 3.6.7-hardened-r1 in both x86 and x86_64 flavors. Enjoy!

audiodef,

That's how I did it. I had some serious issues with X not wanting to work properly with the rt. I think I gave up on it before I ever got down to figuring a cause for all the problems. I will take a look at the latest rt and see if I can even get it to want to work properly. If so, there may be hope for doing rt seeds. Of course, you could always whip up some rt seeds and send them on so I can see if your settings work better than the ones I used. That might be an idea there.

Here's my current config. It's not the latest rt-sources, because some later versions ban non-free software from being used (which stops things like broadcom-sta from being installed on my laptop - and thus I don't support those versions for Gentoo Studio), but the basic settings should apply with acknowledgement of the user's specific hardware.

Personally, I do see any problems, but there are post in the forums where this settings causing problems with automount and starting KDE. Just wondering if it would not be better to have audit support on as a default.

Mostly, X was very, very unstable. It crashed easily, which made bringing up ardour the biggest exercise in futility I'd ever undertaken. That was a few years ago, and who knows if this machine will still have fits of contusions like it did the last time. I will take a look at the .config you made, and adapt it to work with this machine to see if the weirdness of X is gone. If so, then there might be hope for rt-source seeds in the near future.

mhodak,

No apologies needed. No, that issue hasn't been addressed. So I will address it now.

While consolekit will function to a lesser degree, the setting in question is more or less mandatory at this time if you're going to use X with consolekit...which means about everyone. Because hal was seen as something akin to Satan here in Gentoo-land, there was a mad rush to get X to work without it. While that has been done, and some might say for the better, it has left us with the reality that in order to be able to have certain things work properly, like automount as you mentioned, yes, we do need that setting.

This machine will not automount without the syscall audit. It just doesn't work. Perhaps others have found ways around this. I have not, as of yet. Unfortunately, sometimes we must accept that the devs have their own agenda, and that sometimes means things get a little weird with the setups and so on. I've become accustomed to it, so I don't bat an eye when some new wrinkle comes down the pipeline that forces me to adapt and change.

I would be very curious to compare the operation of X from the old days with hal, and now, with the consolekit requirement. I get the feeling we'd find that hal worked better, and wasn't so hard on system resources. In the old days, before I moved up to KDE-4.x, X seemed to be a lot smoother, and a lot less resource hungry, especially when it was in a more or less quiescent state. Conky used to show a steady CPU usage in the five to eight percent range with nothing other than X and conky running. Now, with the new X, the CPU usage bounces between twelve and fifteen percent...once again with only X and conky. I'd call that a bit of a difference. The observations were made with XFCE, which worked well with either old or new X. KDE was never a consideration, as it's infamous for being a resource pig.

So, yes. It is one of those things that we must accept. If you don't do a lot of work with optical storage or USB storage, then you can actually get away with not using that kernel setting. If you want to use things other than internal hard drives, then CONFIG_AUDITSYSCALL is a must. If you have a machine that will function properly without it, then I am jealous.

Frankly, I'd rather that hal returned, but that's not going to happen any time in the near future, as far as I can see. While other distros continue to use hal, Gentoo unfortunately does not. So, I just accept the annoyance turning on another setting, and continue on with my computing.