Peng wrote:
On 01/23/05 17:48, Douglas James Dunn wrote:
um you go into X and load xterm and type glxgears
XD Sorry.
--
gentoo-user@gentoo.org mailing list
ctrl+alt+backspace
--
gentoo-user@gentoo.org mailing list
PK wrote:
Peng wrote:
On 01/23/05 17:48, Douglas James Dunn wrote:
um you go into X and load xterm and type glxgears
XD Sorry.
--
gentoo-user@gentoo.org mailing list
ctrl+alt+backspace
--
gentoo-user@gentoo.org mailing list
If ctrl+alt+backspace isn't working then you could try logging in via
On 01/24/05 20:28, Rick van Hattem wrote:
If ctrl+alt+backspace isn't working then you could try logging in via
ssh to kill X, if it crashes badly then thats usually the only way.
That's rather hard to do without another working computer. Either way, I
can at least do the Alt-SysRq-K-S-U-B
Peng wrote:
On 01/24/05 20:28, Rick van Hattem wrote:
If ctrl+alt+backspace isn't working then you could try logging in via
ssh to kill X, if it crashes badly then thats usually the only way.
That's rather hard to do without another working computer. Either way,
I can at least do the
On 01/24/05 21:04, PK wrote:
Peng wrote:
On 01/24/05 20:28, Rick van Hattem wrote:
If ctrl+alt+backspace isn't working then you could try logging in via
ssh to kill X, if it crashes badly then thats usually the only way.
That's rather hard to do without another working computer. Either way,
I
http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html
a good FAQ on the drivers, might want to take a look through that
On Mon, 2005-01-24 at 17:02 +, Peng wrote:
On 01/24/05 21:04, PK wrote:
Peng wrote:
On 01/24/05 20:28, Rick van Hattem wrote:
If ctrl+alt+backspace isn't
um you go into X and load xterm and type glxgears
On Sun, 2005-01-23 at 02:31 +, Peng wrote:
On 01/22/05 19:16, Douglas James Dunn wrote:
so far you have it completly disabled by having it set to 0 in
xorg.conf. my guess it would either disable it or change it to one x.
what I would
On 01/20/05 17:57, Peng wrote:
On 01/20/05 14:12, Douglas James Dunn wrote:
you try going into your bios and lowering the AGP settings to 4x or 2x?
It worked for me when AGP crashed my box
No, I didn't. Forgot to. I'll try to remember to do it later. :P Don't
feel like rebooting at the moment.
so far you have it completly disabled by having it set to 0 in
xorg.conf. my guess it would either disable it or change it to one x.
what I would do is re-enable it in xorg.conf and and try it disabled in
the bios. but before you do run a glxgears and see if it improves it
any if you disable it
should
On Wed, 2005-01-19 at 19:57 +, Peng wrote:
I finally went and upgraded to kernel 2.6.10-gentoo-r6 (I somehow
managed not to screw everything up, except forgetting to emerge the
nVidia drivers again :D ), and everything still crashes.
Good thing is that the AltGr-K-S-U-B thing
you try going into your bios and lowering the AGP settings to 4x or 2x?
It worked for me when AGP crashed my box
On Wed, 2005-01-19 at 19:57 +, Peng wrote:
I finally went and upgraded to kernel 2.6.10-gentoo-r6 (I somehow
managed not to screw everything up, except forgetting to emerge the
On 01/20/05 14:12, Douglas James Dunn wrote:
you try going into your bios and lowering the AGP settings to 4x or 2x?
It worked for me when AGP crashed my box
No, I didn't. Forgot to. I'll try to remember to do it later. :P Don't
feel like rebooting at the moment. And anyway, turning off NnAGP
I finally went and upgraded to kernel 2.6.10-gentoo-r6 (I somehow
managed not to screw everything up, except forgetting to emerge the
nVidia drivers again :D ), and everything still crashes.
Good thing is that the AltGr-K-S-U-B thing works fine. Thanks for that.
I guess I'll just have to keep
I had some similar problems with that kernel which i solved by using the
noapic and nolapic kernel options. You can turn these on in your grub
config. Make sure /boot is mounted, and edit your /boot/grub/grub.conf file.
Find the line for your current kernel that looks like this:
'kernel
I have made the following expierience with frozen X:
*) Even if normal keyboard doesn't work, the Magic SysRq often stil does
and allows for a clean reboot by holding AltGr and pressing k then s then
u then b -- Kill all processes, Sync all drives, Umount all drives, Boot
the system.
*) the
On 01/16/05 12:29, [EMAIL PROTECTED] wrote:
I have made the following expierience with frozen X:
*) Even if normal keyboard doesn't work, the Magic SysRq often stil
does and allows for a clean reboot by holding AltGr and pressing k
then s then u then b -- Kill all processes, Sync all drives,
On 01/16/05 11:36, Tim Watson wrote:
I had some similar problems with that kernel which i solved by using the
noapic and nolapic kernel options. You can turn these on in your grub
config. Make sure /boot is mounted, and edit your /boot/grub/grub.conf file.
Find the line for your current
I would really suggest trying to switch eventually though it should work
on 2.6.9 but there is a lot of bug fixes on 2.6.10. It shouldnt work
too much different from your kernel you have now you just have to make
sure you have all the correct kernel modules loaded for your hardware.
once you have
you can always change back till you get it to work
On Sun, 2005-01-16 at 12:30 +, Peng wrote:
On 01/16/05 17:23, Douglas James Dunn wrote:
I would really suggest trying to switch eventually though it should work
on 2.6.9 but there is a lot of bug fixes on 2.6.10. It shouldnt work
too
On 01/16/05 17:36, Douglas James Dunn wrote:
you can always change back till you get it to work
True.
Huh... It looks like 'make menuconfig' transferred over my old
configuration... I didn't know it did that. It hadn't in the past.
I have a question: I don't really know how to get sound to work.
first um you have to make sure you delete the linux link in /usr/src
then create a new link from the new kernel source to linux. Ill look
for what you need.
On Sun, 2005-01-16 at 12:44 +, Peng wrote:
On 01/16/05 17:36, Douglas James Dunn wrote:
you can always change back till you get it
On 01/16/05 17:50, Douglas James Dunn wrote:
first um you have to make sure you delete the linux link in /usr/src
then create a new link from the new kernel source to linux. Ill look
for what you need.
I did.
--
gentoo-user@gentoo.org mailing list
you need to know what kind of sound device you use and go look in
device drivers/sound/advanced linux sound architecture
you choose the type of device you use and compile it as a module
On Sun, 2005-01-16 at 12:44 +, Peng wrote:
On 01/16/05 17:36, Douglas James Dunn wrote:
you can always
im not sure it does. I would still go in and check everything you need
to add to make sure its right.
On Sun, 2005-01-16 at 12:54 +, Peng wrote:
On 01/16/05 17:50, Douglas James Dunn wrote:
first um you have to make sure you delete the linux link in /usr/src
then create a new link from
On 01/16/05 17:58, Douglas James Dunn wrote:
im not sure it does. I would still go in and check everything you need
to add to make sure its right.
I am looking around, and many things I remember not being default but I
did change are configured how I had them.
The processor type says
On Sunday, the 16th of January, Peng thusly spake:
Err... AltGr?
a.k.a Right Alt.
Whatever activates the SysRq key on your keyboard, usually PrtSc or
Print on IBM PC keyboards.
You can also configure the key by writing a character to
/proc/sysrq-trigger
See
On 01/16/05 18:13, [EMAIL PROTECTED] wrote:
On Sunday, the 16th of January, Peng thusly spake:
Err... AltGr?
a.k.a Right Alt.
Whatever activates the SysRq key on your keyboard, usually PrtSc or
Print on IBM PC keyboards.
You can also configure the key by writing a character to
On 01/16/05 17:57, Douglas James Dunn wrote:
you need to know what kind of sound device you use and go look in
device drivers/sound/advanced linux sound architecture
you choose the type of device you use and compile it as a module
I'm using a Biostar iDEQ 200N SFF system. :D
im really not sure about onboard audio i always personally stay away
from onboard audio/video/nic, you could try making all the modules in
there and seeing which coldplug uses then you know what works
On Sun, 2005-01-16 at 13:32 +, Peng wrote:
On 01/16/05 17:57, Douglas James Dunn wrote:
On 01/16/05 18:59, Douglas James Dunn wrote:
im really not sure about onboard audio i always personally stay away
from onboard audio/video/nic, you could try making all the modules in
there and seeing which coldplug uses then you know what works
Hmm, for the moment, I think I might just not have
On 01/16/05 14:12, Peng wrote:
On 01/16/05 18:59, Douglas James Dunn wrote:
im really not sure about onboard audio i always personally stay away
from onboard audio/video/nic, you could try making all the modules in
there and seeing which coldplug uses then you know what works
Hmm, for the moment,
On Sunday, the 16th of January, Peng thusly spake:
On 01/16/05 18:13, [EMAIL PROTECTED] wrote:
On Sunday, the 16th of January, Peng thusly spake:
Err... AltGr?
a.k.a Right Alt.
Whatever activates the SysRq key on your keyboard, usually PrtSc or
Print on IBM PC keyboards.
You can also configure
On 01/16/05 20:52, Nick Rout wrote:
On Sun, 16 Jan 2005 13:32:25 +
Peng [EMAIL PROTECTED] wrote:
On 01/16/05 17:57, Douglas James Dunn wrote:
you need to know what kind of sound device you use and go look in
device drivers/sound/advanced linux sound architecture
you choose the type of
On 01/16/05 21:33, Nick Rout wrote:
On Sun, 16 Jan 2005 16:27:14 +
Peng [EMAIL PROTECTED] wrote:
http://www.gentoo.org/doc/en/alsa-guide.xml
Ah! Thank you for the link. Hadn't thought to look at Gentoo's
documentation page for a guide...
It mentions both a Via VT82C686B and the AC97.
what
On Sunday, the 16th of January, Peng thusly spake:
On 01/16/05 19:37, [EMAIL PROTECTED] wrote:
On Sunday, the 16th of January, Peng thusly spake:
On 01/16/05 18:13, [EMAIL PROTECTED] wrote:
On Sunday, the 16th of January, Peng thusly spake:
B means do a hard reboot
O means do a hard poweroff
On Sun, 16 Jan 2005 17:01:03 +
Peng [EMAIL PROTECTED] wrote:
It mentions both a Via VT82C686B and the AC97.
what mentions both a Via VT82C686B and the AC97? the biostar page
doesn't seem to?
The lspci command the Gentoo page you linked says to do does.
do you mean lspci on
On 01/16/05 22:12, Nick Rout wrote:
On Sun, 16 Jan 2005 17:01:03 +
Peng [EMAIL PROTECTED] wrote:
It mentions both a Via VT82C686B and the AC97.
what mentions both a Via VT82C686B and the AC97? the biostar page
doesn't seem to?
The lspci command the Gentoo page you linked says to do does.
do
On Sun, 16 Jan 2005 17:22:45 +, Peng [EMAIL PROTECTED] wrote:
It said it on my system... Oogh. I still can't figure out how to copy
and paste. But it mentions the nForce2 AC97 chip and the VT82C686B.
I bet it looks like this (copied from my nforce board):
:00:05.0 Multimedia audio
On 01/16/05 22:50, Calvin Walton wrote:
On Sun, 16 Jan 2005 17:22:45 +, Peng [EMAIL PROTECTED] wrote:
It said it on my system... Oogh. I still can't figure out how to copy
and paste. But it mentions the nForce2 AC97 chip and the VT82C686B.
I bet it looks like this (copied from my nforce
Since I should have included some details, I'm using version 6.8.0-r3 of
the X.org X server or whatever it's called, and the keyword-masked
1.0.6629-r1 nVidia drivers (would use the not-keyword-masked version,
but it refused to work). Both were installed through Portage. Kernel is
On Sun, 16 Jan 2005 19:33:17 -0500
Dave Nebinger [EMAIL PROTECTED] wrote:
I'm not at all happy with the nvidia card (and have said as much in the
past) so I'm moving on to a newer card with better linux/x support.
Dave
such as?
--
Nick Rout [EMAIL PROTECTED]
--
gentoo-user@gentoo.org
a
working 2.6.10 kernel that matches (more or less) your configure and working
2.6.9 kernel.
-Original Message-
From: Peng [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 16, 2005 7:31 AM
To: [EMAIL PROTECTED]
Subject: Re: [gentoo-user] Any way to kill frozen X/KDE?
On 01/16/05 17:23, Douglas
to probably go with one of the suggested cards.
-Original Message-
From: Nick Rout [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 16, 2005 7:48 PM
To: [EMAIL PROTECTED]
Subject: Re: [gentoo-user] Any way to kill frozen X/KDE?
On Sun, 16 Jan 2005 19:33:17 -0500
Dave Nebinger [EMAIL PROTECTED
On 01/17/05 00:33, Dave Nebinger wrote:
Since I should have included some details, I'm using version 6.8.0-r3 of
the X.org X server or whatever it's called, and the keyword-masked
1.0.6629-r1 nVidia drivers (would use the not-keyword-masked version,
but it refused to work). Both were installed
First all I can say is I hardly ever have it freeze on me unless I have
agp or my video drivers or something missing or configured incorrectly.
I'm not sure if I understand what your are saying here. Can you or cant
you change to a different console.
In theory if you log in and startx in your
I had similar symptoms for a while but it seems to have stopped
happening. The most successful way of fixing it was to ssh in from
another computer, su to root and viciously kill X, using the -9 option
if necessary.
On Sat, 2005-01-15 at 17:11 +, Peng wrote:
Unfortunately, X or KDE (I don't
On 01/16/05 00:06, Nick Rout wrote:
I had similar symptoms for a while but it seems to have stopped
happening. The most successful way of fixing it was to ssh in from
another computer, su to root and viciously kill X, using the -9 option
if necessary.
I, unfortunately, can't do that, since this is
On 01/15/05 23:23, Douglas James Dunn wrote:
First all I can say is I hardly ever have it freeze on me unless I have
agp or my video drivers or something missing or configured incorrectly.
I'm not sure if I understand what your are saying here. Can you or cant
you change to a different console.
On 01/15/05 19:14, Peng wrote:
On 01/16/05 00:06, Nick Rout wrote:
I had similar symptoms for a while but it seems to have stopped
happening. The most successful way of fixing it was to ssh in from
another computer, su to root and viciously kill X, using the -9 option
if necessary.
I,
my first suggestion is to make sure that you have the correct chipset
and drivers installed for video video card, being the correct kernel
module for the chipset and the correct driver via emerge.
On Sat, 2005-01-15 at 19:23 +, Peng wrote:
On 01/15/05 23:23, Douglas James Dunn wrote:
First
it would also help if you could look in your X log for any error
messages it might display. and post them.
On Sun, 2005-01-16 at 01:16 +, Douglas James Dunn wrote:
my first suggestion is to make sure that you have the correct chipset
and drivers installed for video video card, being the
On 01/16/05 01:16, Douglas James Dunn wrote:
my first suggestion is to make sure that you have the correct chipset
and drivers installed for video video card, being the correct kernel
module for the chipset and the correct driver via emerge.
I think it may be irony that it foze while I was typing
On Sat, 15 Jan 2005 17:11:09 +, Peng [EMAIL PROTECTED] wrote:
Unfortunately, X or KDE (I don't know which one...) freezes fairly
often... I can, of course, hit the reset button on the front of the
computer, but that's not good a good thing to do. Is there anyything
else I may be able to
On 01/16/05 02:31, Calvin Walton wrote:
On Sat, 15 Jan 2005 17:11:09 +, Peng [EMAIL PROTECTED] wrote:
Unfortunately, X or KDE (I don't know which one...) freezes fairly
often... I can, of course, hit the reset button on the front of the
computer, but that's not good a good thing to do. Is
that doesnt really fix it though.
I defititly had the same problem when i put in a new nvidia card.
changing NvAGP just disables AGP i would suspect the kernel isnt
compiled right. it definitely looks like an AGP problem. you really cant
render anything graphic intense without it, it basically
55 matches
Mail list logo
