4:50 p.m.
i just installed fedora9 on this computer/shuttle
( http://us.shuttle.com/barebone/Models/SN68SG2.html : using the onboard
video [NVIDIA 7025])
and all went well until the first re-boot and the monitor displayed
'*out of range*'; however, the gui worked fine for the install
process... any ideas?
barclay
4:56 p.m.
check the resolution of the card, it might be set higher than the
maximum resolution supported by the monitor
--
Test <test(a)remedial-teacher.nl>
5:13 p.m.
it's an 'onboard' (motherboard) vga-out, and the bios has no video
settings that i can see; any other ideas? i guess i could check for
motherboard jumpers or the like? any ideas?
Test wrote:
check the resolution of the card, it might be set higher than the
maximum resolution supported by the monitor
5:17 p.m.
i meant checking the settings of your X-windows...
Your X-windows settings are probably set incorrect. (too high a
resolution for your monitor...)
Don't have the details at hand, do some googling for X-windows and
resolution settings..
--
Test <test(a)remedial-teacher.nl>
5:31 p.m.
i have not even got the the point of executing xwindows, i only get out
of the bios, into lilo or the like, how do i get to the xwindows
settings from lilo?
barclay
Test wrote:
i meant checking the settings of your X-windows...
Your X-windows settings are probably set incorrect. (too high a
resolution for your monitor...)
Don't have the details at hand, do some googling for X-windows and
resolution settings..
5:40 p.m.
On Sun, 2008-10-19 at 18:31 -0400, barclay982 wrote:
i have not even got the the point of executing xwindows, i only get
out
of the bios, into lilo or the like, how do i get to the xwindows
settings from lilo?
barclay
Test wrote:
> i meant checking the settings of your X-windows...
>
> Your X-windows settings are probably set incorrect. (too high a
> resolution for your monitor...)
>
> Don't have the details at hand, do some googling for X-windows and
> resolution settings..
----
boot screen where it counts down before it boots is not lilo but rather
grub.
If you press the letter 'a' in grub, it allows you to 'append' arguments
to kernel for booting.
If you add the number one (1) to the boot line, press 'Enter' and press
'b', you will then boot with the option 1 which means boot to runlevel 1
at that point, try executing the command...
system-config-display --reconfig
and see if you can configure the display settings appropriately. Once
you changed your settings, click OK to save the changes and exit. You
can test by running the command 'startx'
If all works well, type 'init 5' to get to normal runlevel or just
reboot by typing 'shutdown now -r'
Craig
5:54 p.m.
On Sun, 2008-10-19 at 18:31 -0400, barclay982 wrote:
i have not even got the the point of executing xwindows, i only get
out of the bios, into lilo or the like, how do i get to the xwindows
settings from lilo?
Are you actually using lilo? GRUB's the default with Fedora, and if you
are using it, you can hit the "e" key when the menu appears to
temporarily edit how the computer will boot.
1. e to edit the menu
2. cursor down to the cursor line
3. e to edit that line, append a blank space and the number 3 to
the end of the line
4. enter
5. enter (it should now boot in text-only mode)
6. log in as root
7. run "system-config-display --reconfig"
8. reconfigure your display
9. repeat from step 7, configuring differently if it fails
10. run "telinit 5", when you succeed, to continue on into graphical
mode.
--
[tim@localhost ~]$ uname -r
2.6.26.5-45.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
4:39 p.m.
i just tried you idea and it seemed to work, the append args; but it
ended up telling me, after i ran system-config-display --reconfig this
message: "no video cards were found on this machine"
any idea(s)?
thanks much,
barclay
Craig White wrote:
On Sun, 2008-10-19 at 18:31 -0400, barclay982 wrote:
> i have not even got the the point of executing xwindows, i only get out
> of the bios, into lilo or the like, how do i get to the xwindows
> settings from lilo?
>
> barclay
>
> Test wrote:
>
>> i meant checking the settings of your X-windows...
>>
>> Your X-windows settings are probably set incorrect. (too high a
>> resolution for your monitor...)
>>
>> Don't have the details at hand, do some googling for X-windows and
>> resolution settings..
>>
----
boot screen where it counts down before it boots is not lilo but rather
grub.
If you press the letter 'a' in grub, it allows you to 'append' arguments
to kernel for booting.
If you add the number one (1) to the boot line, press 'Enter' and press
'b', you will then boot with the option 1 which means boot to runlevel 1
at that point, try executing the command...
system-config-display --reconfig
and see if you can configure the display settings appropriately. Once
you changed your settings, click OK to save the changes and exit. You
can test by running the command 'startx'
If all works well, type 'init 5' to get to normal runlevel or just
reboot by typing 'shutdown now -r'
Craig
4:44 p.m.
Tim suggested runlevel 3 and I may have led you down the wrong path on
runlevel 1.
either change the 1 to a 3 in my instructions or if you are already on
the computer, type 'init 3' to switch to runlevel 3. Then try to run
'startx'
Craig
On Mon, 2008-10-20 at 17:39 -0400, barclay982 wrote:
i just tried you idea and it seemed to work, the append args; but it
ended up telling me, after i ran system-config-display --reconfig this
message: "no video cards were found on this machine"
any idea(s)?
thanks much,
barclay
Craig White wrote:
> On Sun, 2008-10-19 at 18:31 -0400, barclay982 wrote:
>
>> i have not even got the the point of executing xwindows, i only get out
>> of the bios, into lilo or the like, how do i get to the xwindows
>> settings from lilo?
>>
>> barclay
>>
>> Test wrote:
>>
>>> i meant checking the settings of your X-windows...
>>>
>>> Your X-windows settings are probably set incorrect. (too high a
>>> resolution for your monitor...)
>>>
>>> Don't have the details at hand, do some googling for X-windows and
>>> resolution settings..
>>>
> ----
> boot screen where it counts down before it boots is not lilo but rather
> grub.
>
> If you press the letter 'a' in grub, it allows you to 'append'
arguments
> to kernel for booting.
>
> If you add the number one (1) to the boot line, press 'Enter' and press
> 'b', you will then boot with the option 1 which means boot to runlevel 1
>
> at that point, try executing the command...
>
> system-config-display --reconfig
>
> and see if you can configure the display settings appropriately. Once
> you changed your settings, click OK to save the changes and exit. You
> can test by running the command 'startx'
>
> If all works well, type 'init 5' to get to normal runlevel or just
> reboot by typing 'shutdown now -r'
>
> Craig
>
>
5:09 p.m.
i got to the 'setup' menu and could only choose 800x600 or 640x480, and
tried to choose generic lcd as opposed to generic crt; it the seemed to
save some changes but when i rebooted it went to 'out of range' after
grub/boot;
barclay
Craig White wrote:
Tim suggested runlevel 3 and I may have led you down the wrong path
on
runlevel 1.
either change the 1 to a 3 in my instructions or if you are already on
the computer, type 'init 3' to switch to runlevel 3. Then try to run
'startx'
Craig
On Mon, 2008-10-20 at 17:39 -0400, barclay982 wrote:
> i just tried you idea and it seemed to work, the append args; but it
> ended up telling me, after i ran system-config-display --reconfig this
> message: "no video cards were found on this machine"
> any idea(s)?
>
> thanks much,
>
> barclay
>
> Craig White wrote:
>
>> On Sun, 2008-10-19 at 18:31 -0400, barclay982 wrote:
>>
>>
>>> i have not even got the the point of executing xwindows, i only get out
>>> of the bios, into lilo or the like, how do i get to the xwindows
>>> settings from lilo?
>>>
>>> barclay
>>>
>>> Test wrote:
>>>
>>>
>>>> i meant checking the settings of your X-windows...
>>>>
>>>> Your X-windows settings are probably set incorrect. (too high a
>>>> resolution for your monitor...)
>>>>
>>>> Don't have the details at hand, do some googling for X-windows and
>>>> resolution settings..
>>>>
>>>>
>> ----
>> boot screen where it counts down before it boots is not lilo but rather
>> grub.
>>
>> If you press the letter 'a' in grub, it allows you to 'append'
arguments
>> to kernel for booting.
>>
>> If you add the number one (1) to the boot line, press 'Enter' and press
>> 'b', you will then boot with the option 1 which means boot to runlevel 1
>>
>> at that point, try executing the command...
>>
>> system-config-display --reconfig
>>
>> and see if you can configure the display settings appropriately. Once
>> you changed your settings, click OK to save the changes and exit. You
>> can test by running the command 'startx'
>>
>> If all works well, type 'init 5' to get to normal runlevel or just
>> reboot by typing 'shutdown now -r'
>>
>> Craig
>>
>>
>>
5:34 p.m.
You probably need to configure the video card first. If that is
configured, then your choices for display types should expand.
Craig
On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
i got to the 'setup' menu and could only choose 800x600 or
640x480, and
tried to choose generic lcd as opposed to generic crt; it the seemed to
save some changes but when i rebooted it went to 'out of range' after
grub/boot;
barclay
Craig White wrote:
> Tim suggested runlevel 3 and I may have led you down the wrong path on
> runlevel 1.
>
> either change the 1 to a 3 in my instructions or if you are already on
> the computer, type 'init 3' to switch to runlevel 3. Then try to run
> 'startx'
>
> Craig
>
> On Mon, 2008-10-20 at 17:39 -0400, barclay982 wrote:
>
>> i just tried you idea and it seemed to work, the append args; but it
>> ended up telling me, after i ran system-config-display --reconfig this
>> message: "no video cards were found on this machine"
>> any idea(s)?
>>
>> thanks much,
>>
>> barclay
>>
>> Craig White wrote:
>>
>>> On Sun, 2008-10-19 at 18:31 -0400, barclay982 wrote:
>>>
>>>
>>>> i have not even got the the point of executing xwindows, i only get out
>>>> of the bios, into lilo or the like, how do i get to the xwindows
>>>> settings from lilo?
>>>>
>>>> barclay
>>>>
>>>> Test wrote:
>>>>
>>>>
>>>>> i meant checking the settings of your X-windows...
>>>>>
>>>>> Your X-windows settings are probably set incorrect. (too high a
>>>>> resolution for your monitor...)
>>>>>
>>>>> Don't have the details at hand, do some googling for X-windows
and
>>>>> resolution settings..
>>>>>
>>>>>
>>> ----
>>> boot screen where it counts down before it boots is not lilo but rather
>>> grub.
>>>
>>> If you press the letter 'a' in grub, it allows you to
'append' arguments
>>> to kernel for booting.
>>>
>>> If you add the number one (1) to the boot line, press 'Enter' and
press
>>> 'b', you will then boot with the option 1 which means boot to
runlevel 1
>>>
>>> at that point, try executing the command...
>>>
>>> system-config-display --reconfig
>>>
>>> and see if you can configure the display settings appropriately. Once
>>> you changed your settings, click OK to save the changes and exit. You
>>> can test by running the command 'startx'
>>>
>>> If all works well, type 'init 5' to get to normal runlevel or just
>>> reboot by typing 'shutdown now -r'
>>>
>>> Craig
>>>
>>>
>>>
>
>
5:36 p.m.
On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
i got to the 'setup' menu and could only choose 800x600 or
640x480, and
tried to choose generic lcd as opposed to generic crt; it the seemed to
save some changes but when i rebooted it went to 'out of range' after
grub/boot;
----
also, you might want to post the output of 'lspci -v' to the list so we
can help with configuring your video card settings
Craig
5:40 p.m.
it's on-board (motherboard, it's a shuttle pc)
Craig White wrote:
On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
> i got to the 'setup' menu and could only choose 800x600 or 640x480, and
> tried to choose generic lcd as opposed to generic crt; it the seemed to
> save some changes but when i rebooted it went to 'out of range' after
> grub/boot;
>
----
also, you might want to post the output of 'lspci -v' to the list so we
can help with configuring your video card settings
Craig
5:41 p.m.
can you instruct me on the "lspci -v" 'specifics'?
Craig White wrote:
On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
> i got to the 'setup' menu and could only choose 800x600 or 640x480, and
> tried to choose generic lcd as opposed to generic crt; it the seemed to
> save some changes but when i rebooted it went to 'out of range' after
> grub/boot;
>
----
also, you might want to post the output of 'lspci -v' to the list so we
can help with configuring your video card settings
Craig
9:54 p.m.
On Mon, 2008-10-20 at 18:40 -0400, barclay982 wrote:
it's on-board (motherboard, it's a shuttle pc)
Craig White wrote:
> On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
>
>> i got to the 'setup' menu and could only choose 800x600 or 640x480, and
>> tried to choose generic lcd as opposed to generic crt; it the seemed to
>> save some changes but when i rebooted it went to 'out of range' after
>> grub/boot;
>>
> ----
> also, you might want to post the output of 'lspci -v' to the list so we
> can help with configuring your video card settings
----
I too am using a Shuttle...something like an SN41G2 which has built-in
nvidia but as far as I know, nvidia has yet to release a proprietary
blob binary driver for it (9600).
Therefore, I just set my vidia card to the xorg 'nv' driver
(system-config-display) and then higher resolutions (1280x1024) display
options are available.
Craig
10:25 p.m.
Craig White wrote:
On Mon, 2008-10-20 at 18:40 -0400, barclay982 wrote:
> it's on-board (motherboard, it's a shuttle pc)
>
> Craig White wrote:
>
>> On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
>>
>>
>>> i got to the 'setup' menu and could only choose 800x600 or 640x480,
and
>>> tried to choose generic lcd as opposed to generic crt; it the seemed to
>>> save some changes but when i rebooted it went to 'out of range' after
>>> grub/boot;
>>>
>>>
>> ----
>> also, you might want to post the output of 'lspci -v' to the list so we
>> can help with configuring your video card settings
>>
----
I too am using a Shuttle...something like an SN41G2 which has built-in
nvidia but as far as I know, nvidia has yet to release a proprietary
blob binary driver for it (9600).
GeForce 9600 GT 0x0622
GeForce 9600 GS 0x0623
is supported in 173.14.05.
Therefore, I just set my vidia card to the xorg 'nv' driver
(system-config-display) and then higher resolutions (1280x1024) display
options are available.
Craig
--
What a strange game. The only winning move is not to play. -- WOP, "War
Games"
10:46 p.m.
On Tue, 2008-10-21 at 11:25 +0800, Ed Greshko wrote:
Craig White wrote:
> On Mon, 2008-10-20 at 18:40 -0400, barclay982 wrote:
>
>> it's on-board (motherboard, it's a shuttle pc)
>>
>> Craig White wrote:
>>
>>> On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
>>>
>>>
>>>> i got to the 'setup' menu and could only choose 800x600 or
640x480, and
>>>> tried to choose generic lcd as opposed to generic crt; it the seemed to
>>>> save some changes but when i rebooted it went to 'out of range'
after
>>>> grub/boot;
>>>>
>>>>
>>> ----
>>> also, you might want to post the output of 'lspci -v' to the list so
we
>>> can help with configuring your video card settings
>>>
> ----
> I too am using a Shuttle...something like an SN41G2 which has built-in
> nvidia but as far as I know, nvidia has yet to release a proprietary
> blob binary driver for it (9600).
>
GeForce 9600 GT 0x0622
GeForce 9600 GS 0x0623
is supported in 173.14.05.
----
you may be right...the last time I checked, it just flat didn't work.
from lspci...
02:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX
- nForce GPU] (rev a3) (prog-if 00 [VGA controller])
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
Memory at ec000000 (32-bit, non-prefetchable) [size=16M]
Memory at e4000000 (32-bit, prefetchable) [size=64M]
Memory at e8000000 (32-bit, prefetchable) [size=512K]
[virtual] Expansion ROM at e8080000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0
Kernel modules: rivafb, nvidiafb
yum install kmod-nvidia...
================================================================================
Package Arch Version
Repository Size
================================================================================
Installing:
kmod-nvidia i686 173.14.12-5.lvn9 livna
23 k
Installing for dependencies:
kmod-nvidia-2.6.26.5-45.fc9.i686 i686 173.14.12-5.lvn9 livna
2.5 M
xorg-x11-drv-nvidia i386 173.14.12-1.lvn9 livna
2.7 M
xorg-x11-drv-nvidia-libs i386 173.14.12-1.lvn9 livna
5.5 M
Transaction Summary
================================================================================
Install 4 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 11 M
I'll take another rip at it but I don't know when I will be able to
reboot to test it.
Thanks
Craig
11:01 p.m.
Craig White wrote:
>> ----
>> I too am using a Shuttle...something like an SN41G2 which has built-in
>> nvidia but as far as I know, nvidia has yet to release a proprietary
>> blob binary driver for it (9600).
>>
>>
> GeForce 9600 GT 0x0622
> GeForce 9600 GS 0x0623
>
> is supported in 173.14.05.
>
----
you may be right...the last time I checked, it just flat didn't work.
from lspci...
02:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX
- nForce GPU] (rev a3) (prog-if 00 [VGA controller])
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
Memory at ec000000 (32-bit, non-prefetchable) [size=16M]
Memory at e4000000 (32-bit, prefetchable) [size=64M]
Memory at e8000000 (32-bit, prefetchable) [size=512K]
[virtual] Expansion ROM at e8080000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0
Kernel modules: rivafb, nvidiafb
I'm a bit confused....
At the top you seem to be talking about the "GeForce 9600" but the
output of your lspci seems to show "GeForce4 MX". The GeForce4 MX is no
longer supported in the latest releases from nVidia. One needs to use
the legacy drivers.
What am I missing?
11:20 p.m.
On Tue, 2008-10-21 at 12:01 +0800, Ed Greshko wrote:
Craig White wrote:
>>> ----
>>> I too am using a Shuttle...something like an SN41G2 which has built-in
>>> nvidia but as far as I know, nvidia has yet to release a proprietary
>>> blob binary driver for it (9600).
>>>
>>>
>> GeForce 9600 GT 0x0622
>> GeForce 9600 GS 0x0623
>>
>> is supported in 173.14.05.
>>
> ----
> you may be right...the last time I checked, it just flat didn't work.
>
> from lspci...
> 02:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX
> - nForce GPU] (rev a3) (prog-if 00 [VGA controller])
> Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
> Memory at ec000000 (32-bit, non-prefetchable) [size=16M]
> Memory at e4000000 (32-bit, prefetchable) [size=64M]
> Memory at e8000000 (32-bit, prefetchable) [size=512K]
> [virtual] Expansion ROM at e8080000 [disabled] [size=128K]
> Capabilities: [60] Power Management version 2
> Capabilities: [44] AGP version 2.0
> Kernel modules: rivafb, nvidiafb
>
>
I'm a bit confused....
At the top you seem to be talking about the "GeForce 9600" but the
output of your lspci seems to show "GeForce4 MX". The GeForce4 MX is no
longer supported in the latest releases from nVidia. One needs to use
the legacy drivers.
What am I missing?
----
on F8, I used the 9600 driver without issue.
Craig
11:24 p.m.
Craig White wrote:
On Tue, 2008-10-21 at 12:01 +0800, Ed Greshko wrote:
> Craig White wrote:
>
>>>> ----
>>>> I too am using a Shuttle...something like an SN41G2 which has built-in
>>>> nvidia but as far as I know, nvidia has yet to release a proprietary
>>>> blob binary driver for it (9600).
>>>>
>>>>
>>>>
>>> GeForce 9600 GT 0x0622
>>> GeForce 9600 GS 0x0623
>>>
>>> is supported in 173.14.05.
>>>
>>>
>> ----
>> you may be right...the last time I checked, it just flat didn't work.
>>
>> from lspci...
>> 02:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX
>> - nForce GPU] (rev a3) (prog-if 00 [VGA controller])
>> Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
>> Memory at ec000000 (32-bit, non-prefetchable) [size=16M]
>> Memory at e4000000 (32-bit, prefetchable) [size=64M]
>> Memory at e8000000 (32-bit, prefetchable) [size=512K]
>> [virtual] Expansion ROM at e8080000 [disabled] [size=128K]
>> Capabilities: [60] Power Management version 2
>> Capabilities: [44] AGP version 2.0
>> Kernel modules: rivafb, nvidiafb
>>
>>
>>
> I'm a bit confused....
>
> At the top you seem to be talking about the "GeForce 9600" but the
> output of your lspci seems to show "GeForce4 MX". The GeForce4 MX is no
> longer supported in the latest releases from nVidia. One needs to use
> the legacy drivers.
>
> What am I missing?
>
----
on F8, I used the 9600 driver without issue.
Craig
Sorry, I don't follow....what is a "9600" driver?
I only know the nvidia.ko driver and "nv" driver.
--
Electrocution, n.: Burning at the stake with all the modern improvements.
11:31 p.m.
On Tue, 2008-10-21 at 12:24 +0800, Ed Greshko wrote:
Craig White wrote:
> On Tue, 2008-10-21 at 12:01 +0800, Ed Greshko wrote:
>
>> Craig White wrote:
>>
>>>>> ----
>>>>> I too am using a Shuttle...something like an SN41G2 which has
built-in
>>>>> nvidia but as far as I know, nvidia has yet to release a
proprietary
>>>>> blob binary driver for it (9600).
>>>>>
>>>>>
>>>>>
>>>> GeForce 9600 GT 0x0622
>>>> GeForce 9600 GS 0x0623
>>>>
>>>> is supported in 173.14.05.
>>>>
>>>>
>>> ----
>>> you may be right...the last time I checked, it just flat didn't work.
>>>
>>> from lspci...
>>> 02:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX
>>> - nForce GPU] (rev a3) (prog-if 00 [VGA controller])
>>> Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
>>> Memory at ec000000 (32-bit, non-prefetchable) [size=16M]
>>> Memory at e4000000 (32-bit, prefetchable) [size=64M]
>>> Memory at e8000000 (32-bit, prefetchable) [size=512K]
>>> [virtual] Expansion ROM at e8080000 [disabled] [size=128K]
>>> Capabilities: [60] Power Management version 2
>>> Capabilities: [44] AGP version 2.0
>>> Kernel modules: rivafb, nvidiafb
>>>
>>>
>>>
>> I'm a bit confused....
>>
>> At the top you seem to be talking about the "GeForce 9600" but the
>> output of your lspci seems to show "GeForce4 MX". The GeForce4 MX is
no
>> longer supported in the latest releases from nVidia. One needs to use
>> the legacy drivers.
>>
>> What am I missing?
>>
> ----
> on F8, I used the 9600 driver without issue.
>
> Craig
>
>
Sorry, I don't follow....what is a "9600" driver?
I only know the nvidia.ko driver and "nv" driver.
----
http://livna-dl.reloumirrors.net/fedora/8/i386/
note, there are separate packages for [kmod-] 96XX and legacy as well as
the current nvidia drivers. I suppose they all would install the
nvidia.ko which is why you only install 1 of them.
Craig
11:45 p.m.
Craig White wrote:
> Sorry, I don't follow....what is a "9600" driver?
>
> I only know the nvidia.ko driver and "nv" driver.
>
----
http://livna-dl.reloumirrors.net/fedora/8/i386/
note, there are separate packages for [kmod-] 96XX and legacy as well as
the current nvidia drivers. I suppose they all would install the
nvidia.ko which is why you only install 1 of them.
I see what is confusing me....
The OP said he has a Shuttle SN68SG2 and it has an onboard NVIDIA®
GeForce 7025 while you have a SN41G2
(or something like that) with a "GeForce4 MX" on it.
So, you need the legacy drivers while the OP would probably be served
better by the latest drivers.
I don't know why you would install kmod-nvidia version 173.14.12-5.lvn9
on you system since that is not the legacy nvidia driver.
But, what do I know.... I only use the stock nVidia stuff....
I have one system here with "GeForce 7300 GT" running "Kernel Module
173.14.05" and the other system with "GeForce4 MX 420" running
"Kernel
Module 1.0-7185" and everything works fine.
--
Love is like the measles; we all have to go through it. -- Jerome K. Jerome
6:11 a.m.
craig/other:
how do i do this?
>>
I too am using a Shuttle...something like an SN41G2 which has built-in
nvidia but as far as I know, nvidia has yet to release a proprietary
blob binary driver for it (9600).
Therefore, I just set my vidia card to the xorg 'nv' driver
(system-config-display) and then higher resolutions (1280x1024) display
options are available.
Craig
>>
Craig White wrote:
On Mon, 2008-10-20 at 18:40 -0400, barclay982 wrote:
> it's on-board (motherboard, it's a shuttle pc)
>
> Craig White wrote:
>
>> On Mon, 2008-10-20 at 18:09 -0400, barclay982 wrote:
>>
>>
>>> i got to the 'setup' menu and could only choose 800x600 or 640x480,
and
>>> tried to choose generic lcd as opposed to generic crt; it the seemed to
>>> save some changes but when i rebooted it went to 'out of range' after
>>> grub/boot;
>>>
>>>
>> ----
>> also, you might want to post the output of 'lspci -v' to the list so we
>> can help with configuring your video card settings
>>
----
I too am using a Shuttle...something like an SN41G2 which has built-in
nvidia but as far as I know, nvidia has yet to release a proprietary
blob binary driver for it (9600).
Therefore, I just set my vidia card to the xorg 'nv' driver
(system-config-display) and then higher resolutions (1280x1024) display
options are available.
Craig
2:54 p.m.
ed/craig/other- i can get logged in as root command line only; what file
(and path to file) do i edit to make change for the 'out of range'
message i get from fedora boot-up on my lcd monitor?
Ed Greshko wrote:
Craig White wrote:
>> Sorry, I don't follow....what is a "9600" driver?
>>
>> I only know the nvidia.ko driver and "nv" driver.
>>
>>
> ----
> http://livna-dl.reloumirrors.net/fedora/8/i386/
>
> note, there are separate packages for [kmod-] 96XX and legacy as well as
> the current nvidia drivers. I suppose they all would install the
> nvidia.ko which is why you only install 1 of them.
>
>
>
I see what is confusing me....
The OP said he has a Shuttle SN68SG2 and it has an onboard NVIDIA®
GeForce 7025 while you have a SN41G2
(or something like that) with a "GeForce4 MX" on it.
So, you need the legacy drivers while the OP would probably be served
better by the latest drivers.
I don't know why you would install kmod-nvidia version 173.14.12-5.lvn9
on you system since that is not the legacy nvidia driver.
But, what do I know.... I only use the stock nVidia stuff....
I have one system here with "GeForce 7300 GT" running "Kernel Module
173.14.05" and the other system with "GeForce4 MX 420" running
"Kernel
Module 1.0-7185" and everything works fine.
4:39 p.m.
On Tue, 2008-10-21 at 15:54 -0400, barclay982 wrote:
ed/craig/other- i can get logged in as root command line only; what
file
(and path to file) do i edit to make change for the 'out of range'
message i get from fedora boot-up on my lcd monitor?
----
I don't understand.
if after going into runlevel 3, logging on as root, setting your display
configuration with the command 'system-config-display --reconfig',
saving your settings and satisfied with X settings by running startx,
you simply type 'init 5' and you should be good to go.
Those settings should persevere through reboots.
Craig
8:57 a.m.
On Tue, 2008-10-21 at 14:39 -0700, Craig White wrote:
On Tue, 2008-10-21 at 15:54 -0400, barclay982 wrote:
> ed/craig/other- i can get logged in as root command line only; what file
> (and path to file) do i edit to make change for the 'out of range'
> message i get from fedora boot-up on my lcd monitor?
----
I don't understand.
if after going into runlevel 3, logging on as root, setting your display
configuration with the command 'system-config-display --reconfig',
saving your settings and satisfied with X settings by running startx,
you simply type 'init 5' and you should be good to go.
I think there iws some confusion here. One you type startx, typing init
5 will be hard to do. Typing init 5 should be sufficient,
Those settings should persevere through reboots.
Craig
--
=======================================================================
Seattle is so wet that people protect their property with watch-ducks.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
5657
days inactive
5660
days old
26 comments
6 participants
participants (6)
-
Aaron Konstam -
barclay982 -
Craig White -
Ed Greshko -
Test -
Tim