Ok, i'm just posting this, in case someone else runs across this, and maybe someone can explain to me whats happening..
I recently upgraded motherboard from an old Athon to a Athon64 board... With the new MB, of course i needed new drivers. So I boot the machine, set up the drivers in the kernel ...
I happen to use SlickEdit which probably has all of what you are looking for... Emulates several different keybindings (I use Brief), including VI and Emacs.. Hex editing, syntax highlighting, etc.. Availble on Windows, Linux, Mac, and several other Unix..
I know this thread is a couple weeks old, but I just solved this problem on my machine..
It seems that the nvidia-glx ebuild tries to detect which version of glibc you have installed.. It has to do this, to figure out if it uses TLS or not... In my case, I had glibc 2.2.5 and 2.3.5....... And 2.2.5 ...
Some more trips down memory lane tell me that yours is the same model as mine was..
Some more notes: You do not need a specific kernel driver.. I got mine working with the basic stuff in 2.6 (fairly sure I was using 2.6 at the time, but definitly pre-UDEV)..
I have no idea how old your touch screen is, but I had a fairly old ELO USB touchscreen (no clue on the model..).. I have since gotten rid of it (the LCD on it died a beautiful plasma effect death..)
What I recall from getting it to work was that I had to compile in the event interface and USB ...
You could yes.. I actaully did it originally with GDM... But why waste the space, memory, maintenance, and time for having kdelibs, kdebase installed? It makes for a more specialized machine..
Plus, it would not have solved my Xterminal problem.
I have a couple machines that I use for specialize reasons.
Machine 1: Mythtv Machine 2: Xterminal and mpd jukebox.
My problem initially started with machine 2.. I wanted to have an Xterminal, and I was using LTSP to get it. But eventaully, since this Xterminal is near my "good" stereo anyways, I ...
After banging my head for several hours, I finally got sound working on my LTSP client..
My situation: I have a machine with a SBLive card. When the LTSP client would start, I would see the modules for it load automaticly, and the esd server would start. But no sound would come out.
In my case (which I've solved), yes, the chipset driver was compiled into the kernel.
It was because the .devfsd file existed that it kind bombed out before it could setup udev.. After I deleted that file (booting from an install cd), everything went smoothly..
Well, I've fixed my problem.. I don't know if its the same as yours though..
I needed to boot with a install cd (or any other cd I would guess), and mount my root drive, and delete the /dev/.devfsd file, which was for some reason sitting there.
I have the same exact problem on one machine I just tried to convert to udev.. I haven't figured out what happened yet though.. But I did notice one thing.. My root is on /dev/hda3, and that entry was missing in /dev... It had /dev/hda1, 2, 4, 5,6, 7, 8, of which I only have 1,2,3,4..
You're using PVR 350? Are you using the TV-out from the PVR-350 to display on the TV? If so, then you need to use the sound out from the PVR350 also.. Its the PVR thats doing the decoding of the MPEG, so it just naturally uses its own sound device..
Hi folks.. I just attempted the gcc3.3 to gcc3.4 upgrade, and everything went well up to the point I was doing the 2nd emerge system.. I recieved an error when compiling glibc-2.3.4-20041102..
Well, I would say that your CPU is overkill, at least for basic recording.. THe 350 will handle the encoding and if you wanted, it can handle teh decoding on its TV out..
For example, I currently run a Myth box (gentoo based), on a PII 400 w/ the 350, without issue..