higher res in Slack 12

amd0freak · 07-14-2007, 02:41 PM

hey i am new to linux but am a fast learner, i switched to linux because i have defected (used to be a .NET programmer) to Java. I got ndiswrapper to work and now im online so i dont have to spend weeks troubleshooting small issues like this.

here are my (albeit simple) frustrating issues

Sound doesn't work - Tried alsamixer, and max volume on all 8 channels (7.1) is 0....so yeah. and lspci recognizes my card, DiamondTek Extremesound 7.1

I cannot get over 1024X768. I have a nVidia GeForce 7600GT and I installed the Linux x86 nVidia drivers; they are loaded into kernel and i know for a fact the nVidia drivers are running; i edited xorg.conf so the ONLY RESLOLUTIONS at my default depth (24 because for some reason 32 didnt work although my video card is VERY capable of it) are 1600X1200 and 1900X1440, both of which i know for a fact work perfectly fine on my 23" CRT at 60-75 Hz. (which i set as the range of refresh rates). I end x with init 3, init 4 back into x and its still at 1024X768 even though thats not even a possibility anymore! i rebooted; same thing. Then i right click desktop in KDE, desktop settings, go to monitor and resolutions vary from 300x400 to 1024X768 and nothing higher
the refresh rate is only 50Hz....WTF?!?!?! so do i have to edit something other than xorg.conf?

How do i get my tv tuner card working in linux? also it has an FM tuner, any hope of getting it working in slack?

lastly, how do i use mono to develop and run .NET apps in Linux? if i use this can i use WinE with Visual Studio or what?

duryodhan · 07-14-2007, 03:27 PM

>hey i am new to linux but am a fast learner, i switched to linux because i have >defected (used to be a .NET programmer) to Java

You know Windows runs Java pretty well , right? (infact for SWT/swing etc. support is much better)

very simple answer ... read the slackbook ... it has the answers for most of your simple albeit frustating issues. I think alsaconf will solve your problems.

There are some things about the nVidia drivers, you have to use the non-smps kernel or something. Read the installation notes with the slack12 DVD.

32bit is actually 24 bit. those 8 bits are just a mirage ... basically you don't need to worry about that ... just know that the linux 24bit is just your 32bit in windows.

I dont have nVidia, but afaik, doesn't it look after the xorg conf etc. on its own?

everything JUST Works in linux ... except nVidia cards .. as they don't want to include their drivers in the kernel. Your TV Tuner card should work out of the box from the huge /generic kernel. If you still have problems , then google for that particular brand and linux.

Eternal_Newbie · 07-14-2007, 04:57 PM

Have you set the HorizSync and VertRefresh values for your monitor in your /etc/X11/xorg.conf?
If you haven't (and sometimes when you have, depending on your driver), XOrg over-rides your Screen settings and tries to auto-detect them, usually getting things wrong :P

This is my Monitor section, yours should look vaguely similar:

Code:

Section "Monitor"
    Identifier  "PV505"
    HorizSync   31.5 - 60.0
    VertRefresh 60-70
    Option "DPMS"
EndSection

Obviously use the values for your monitor, they will be in its manual or available on the 'net.

Perhaps you could post your xorg.conf?

Just to clarify, when you ran alsamixer as root were you able to change the volume levels using the up/down arrow keys, and did you remember to run "alsctl store" afterwards? Or were all the levels stuck at "0<>0"?

PS don't forget pressing "m" unmutes or mutes a channel in alsamixer.

EDIT: The "Slackware LQ Suggestions" thread is full of useful links and info, well worth checking it out.

amd0freak · 07-14-2007, 10:12 PM

Eternal_Newbie
My monitor section is essentially the same; and I KNOW that my refresh rate will work between 60-70 Hz at both 1600X1200 and 1900X1440 (thats what i use in XP) i left horiz sync at 30-50 and i dont think thats a problem
I will post my xorg.conf tomorrow when i boot into Slack(forewarning: sorry for all the commented lines, they are standard and i didn't remove them as i am learning it still LOL)

Or were all the levels stuck at "0<>0"? yeah thats it

i will also follow duryo's advice and yours combined i think i can get sound to work. the main problem is res...i tried everything. again i will post my xorg.conf but right now i need to sleep! thanks all

duryodhan · 07-17-2007, 04:50 AM

you could also try the another mode line calculator

timsoft · 07-18-2007, 07:48 AM

I got the same problem with xwindows limited to 1024x768 even though thr graphics card and monitor can handle higher. i tried hand editing xorg.conf and that didn't work either.
what did work is the following (make sure you back up you existing xorg.conf first)
run /usr/X11R6/bin/xorgsetup
then run startx and low and behold, those higher resolutions were available.
hope it works for you too.

lord-fu · 07-18-2007, 07:55 AM

All that information is available in the slackbook, including how to setup sound cards etc.

http://www.slackbook.org/

Specifically here

http://www.slackbook.org/html/book.html#X-WINDOW-SYSTEM

hitest · 07-18-2007, 08:12 AM

#alsaconf

#alsamixer

#alsactl store

Vincent_Vega · 07-19-2007, 04:59 PM

Once you have the NVidia driver installed, type
nvidia-settings to get to their settings GUI. There you can use the drop-down menu for your resolution. If you do this as root, you can also, once you're happy with everything, have it written to your xorg.conf file. Always seems to be the best way for me.

amd0freak · 07-20-2007, 09:16 PM

Quote:

Originally Posted by xorg.conf

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder3) Sat May 26 01:05:11 PDT 2007

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Sat May 26 01:04:16 PDT 2007
# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me.

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).
# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy!

# -- volkerdi@slackware.com
#
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Server flags section.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# Some examples of extended input devices
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
# ModulePath "/usr/lib/xorg/modules"
RgbPath "/usr/share/X11/rgb"
FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# This loads the GLX module
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
#Load "speedo"
Load "glx"
EndSection

Section "ServerFlags"
Option "Xinerama" "0"
EndSection

Section "InputDevice"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
# Set the keyboard auto repeat parameters. Not all platforms implement
# this.
# Option "AutoRepeat" "500 5"
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
# Option "XkbLayout" "de"
#
# or:
#
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for X.Org
#
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
Identifier "Keyboard1"
Driver "kbd"
EndSection

Section "InputDevice"

# Identifier and driver
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
# Option "Protocol" "Auto"
# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
# which is usually a symbolic link to the real device.
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
# The mouse device. The device is normally set to /dev/mouse,
Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
EndSection

Section "Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
Identifier "My Monitor"
HorizSync 31.5 - 50.0
VertRefresh 40.0 - 90.0
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "CRT-1"
HorizSync 31.5 - 50.0
VertRefresh 40.0 - 90.0
EndSection

Section "Device"

#VideoRam 4096
# Insert Clocks lines here if appropriate
Identifier "VESA Framebuffer"
Driver "nvidia"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7600 GT"
EndSection

Section "Screen"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
# DefaultDepth 8
# DefaultDepth 16
# DefaultDepth 32
# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1600X1200" "1900X1440"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "nvidia-auto-select +0+0"
EndSection

None of your suggestions on the resolution worked, I apologize for the delay in posting this i was busy signing up for college classes and making sure i got all the research opportunities that i wanted

thanks for your help; sound works!!! TV works!!!

and im still at 1024X768; tried EVERYTHING, the xorg.conf file has ONLY 1600X1200 and 1900X1440 as possible res (well you can see lol i dont have to tell you)

anyway here it is

amd0freak · 07-20-2007, 09:18 PM

I just noticed; I have two screen sections. does the second overwrite the first (like a CSS style sheet lol dunno why but that is what it reminded me of) because they refer to the same exact monitor and screen? the second doesnt have res subsections. should i paste in a subsection and see what happens??

amd0freak · 07-21-2007, 01:17 PM

anyone

:-( i pasted in the subsection with depth 24 and resolution choices 1600X1200 and 1900X1440

restarted x, still only up to 1024X768

nvidia-settings only goes up to 1024X768

running xorgsetup takes the nvidia driver out of xorg.conf

so what do i do??

erklaerbaer · 07-21-2007, 01:34 PM

if i had to guess, i'd say it's because you specified the horizsync/vertrefresh values. so let's try auto configuration; it should get things right (at least it does for me)

Code:

(as root, in run level 3)
X -configure
X -config /root/xorg.conf.new
add the "Modes" line (there still is no depth 32 btw)
if it works: cp /root/xorg.conf.new /etc/X11/xorg.conf

if it still doesn't work, have a look at /var/log/Xorg.0.log before posting again.

amd0freak · 07-21-2007, 01:55 PM

Quote:

Originally Posted by erklaerbaer

if i had to guess, i'd say it's because you specified the horizsync/vertrefresh values. so let's try auto configuration; it should get things right (at least it does for me)

Code:

(as root, in run level 3)
X -configure
X -config /root/xorg.conf.new
add the "Modes" line (there still is no depth 32 btw)
if it works: cp /root/xorg.conf.new /etc/X11/xorg.conf

if it still doesn't work, have a look at /var/log/Xorg.0.log before posting again.

so i am creating a new file, containing nothing but the "Modes" line, and replacing xorg.conf with that?

erklaerbaer · 07-21-2007, 01:58 PM

X -configure
creates a new file and you could add an Modes line, if you want.