Re: Large font when booting into linux when using NVIDIA card

2006-08-26 Thread thunder7
From: Adam D <[EMAIL PROTECTED]>
Date: Fri, Aug 25, 2006 at 06:14:31PM -0700
> Ever since I have built my first x86 box (AMD64) I have not been able to get 
> my initial font size down from the about 1" size.  I have included in my grub 
> the following line
> 
> ..root=/dev/hda1 ro video=nvidiafb:vmode:22 quiet splash
> 
> Using 'video=nvidiafb:vmode:22' does not make a difference with the
> video.  I would love to use the TTYs more but with such large text on
> the terminal it becomes very annoying.
> 
from my menu.lst:

kernel  /boot/vmlinuz-2618rc4mm2 root=/dev/md2 video=nvidiafb:[EMAIL 
PROTECTED]
kernel  /boot/vmlinuz-2618rc4mm2 root=/dev/md2 video=nvidiafb:[EMAIL 
PROTECTED]

There's no need to search for modes - just define what resolution you
want, what depth (32 bits) and what refresh rate.

By the way, even if you have a very large screen, a line length of about
72 characters is recommended, instead of your very long lines.

HTH,
Jurriaan
-- 
Miranda said,"I am totally confused."
"You are not alone," said Pug.
   Raymond E Feist - Rage of a Demon King
Debian (Unstable) GNU/Linux 2.6.18-rc4-mm2 4423 bogomips load 1.33


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: how to setup KDE or Gnome

2006-08-26 Thread A.E.Lawrence
Jo Shields wrote:
> A.E.Lawrence wrote:
> 
>> Nobody has mentioned /etc/inittab in this thread so far.
>>
>> ISTR that I just had to assign a run level to include kde/gdm/whatever.
>>
>> Runlevel 2 is usually  kept for text alone which is very useful indeed
>> when your GUI goes belly up.
>>
>> ael
> 
> 
> That's a redhatism. Debian runs at runlevel 2 by default, including
> graphical stuff.

That is what I expected, but not what seemed to have been installed.
Perhaps a broken package. But a small adjustment on inittab and the
right links in the /etc/rcn.d directories fixed the problems which
others seem to be reporting...

Since the GUI does seem to get broken rather often, I value a text only
runlevel ...

ael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: apt/dpkg always upgrade still upgraded packages

2006-08-26 Thread Peter Stoehr
Hi,

Goswin von Brederlow wrote:
> Remove the unofficial repository if you use the official one now. They
> contain the same packages but different builds of them, which confuses
> apt-get.

the problem was, that I had the official "testing" repository in my
/etc/apt/sources.list (to get the stuff for backporting)

Only the official and my unoffical "stable" repositories => it works
fine. Never thought that the solution is so quiet simple.

Thanks Goswin,
rgds Peter
-- 
Unofficial repository for AMD64:
PHP 5.1 - Postfix 2.2 - VNSTAT 1.4
deb http://peter.st/debian-amd64/ sarge main


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: how to setup KDE or Gnome

2006-08-26 Thread Viktor Tsyrennikov
  Hi,

  finally I am writing this email from KDE under AMD64 Etch b3. Here is how it 
worked:
  1. Clean network install
  2. Install kde-core and kdm (by suggestion of Scott Lair)

  Everything works well. Just installed KDevelop and compiled a test C++ code.

  Thanks for all your input!
  Victor

P.S. before I tried '/etc/init.d/kdm stop;startkde' -- it said 'could not 
connect to xserver' even though I could start x server manually.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: how to setup KDE or Gnome

2006-08-26 Thread Jo Shields

A.E.Lawrence wrote:

Nobody has mentioned /etc/inittab in this thread so far.

ISTR that I just had to assign a run level to include kde/gdm/whatever.

Runlevel 2 is usually  kept for text alone which is very useful indeed
when your GUI goes belly up.

ael


That's a redhatism. Debian runs at runlevel 2 by default, including 
graphical stuff.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: how to setup KDE or Gnome

2006-08-26 Thread Scott Lair
Viktor Tsyrennikov wrote:
>  Hi again,
> 
>  here is my lspci output:
> 
> 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller
> (rev a3)
> 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
> 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
> 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
> 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
> 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97
> Audio Controller (rev a2)
> 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
> 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller
> (rev f3)
> 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller
> (rev f3)
> 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
> 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
> 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
> 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
> 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
> 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> HyperTransport Technology Configuration
> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Address Map
> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Miscellaneous Control
> 01:00.0 VGA compatible controller: nVidia Corporation GeForce 6200
> TurboCache(TM) (rev a1)
> 05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
> IEEE-1394a-2000 Controller (PHY/Link)
> 05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001
> Gigabit Ethernet Controller (rev 13)
> 
>  Victor
> 
> 
> 
> 
try this

apt-get install kde-core kdm

taken from 

http://www.linuxquestions.org/questions/showthread.php?t=460096

worked for me

scott


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: how to setup KDE or Gnome

2006-08-26 Thread A.E.Lawrence
Nobody has mentioned /etc/inittab in this thread so far.

ISTR that I just had to assign a run level to include kde/gdm/whatever.

Runlevel 2 is usually  kept for text alone which is very useful indeed
when your GUI goes belly up.

ael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Large font when booting into linux when using NVIDIA card

2006-08-26 Thread Jo Shields

Jo Shields wrote:

Adam D wrote:

Daniel Foote wrote:
 

Ever since I have built my first x86 box (AMD64) I have not been able
to get my initial font size down from the about 1" size.  I have
included in my grub the following line

..root=/dev/hda1 ro video=nvidiafb:vmode:22 quiet splash

Using 'video=nvidiafb:vmode:22' does not make a difference with the
video.  I would love to use the TTYs more but with such large text on
the terminal it becomes very annoying.
  

I've just been using vga=795 on the grub command line. That jumps the
display into 1280x1024 mode, and fits as much text as possible. A bit
of googling will find you other values that you might be able to use.

See if that solves the problem for you.

Have fun...
Daniel Foote.





Thank you for the input.  I would not have figured to use vga=.  I 
did a google for a vga of 1600x1200 but the system hung and after a 
while went through the startup.  Using vga=795 works just fine and I 
can actually work on the ttys.


-Thanks for your input

Adam


Modes above 1280x1024 are non-standard, and vary from graphics card to 
graphics card. The package "hwinfo" can work out your valid modes, 
from "hwinfo --framebuffer" - I seem to recall it gives output in Hex 
though, so you will need to convert to Decimal for putting in your 
menu.lst


No output at all suggests an uncooperative graphics card (in which 
case you should stick with 795 as a maximum)


Also worth noting is that the behaviour may be different on graphics 
cards with multiple outputs - I cannot use a mode over 1280 on one of my 
card's DVI connections (and get nothing from hwinfo) but it's partially 
fine on the other one (screen is blank until X loads, if i switch to a 
VT then i have a 1600x1200 framebuffer)



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Large font when booting into linux when using NVIDIA card

2006-08-26 Thread Jo Shields

Adam D wrote:

Daniel Foote wrote:
  

Ever since I have built my first x86 box (AMD64) I have not been able
to get my initial font size down from the about 1" size.  I have
included in my grub the following line

..root=/dev/hda1 ro video=nvidiafb:vmode:22 quiet splash

Using 'video=nvidiafb:vmode:22' does not make a difference with the
video.  I would love to use the TTYs more but with such large text on
the terminal it becomes very annoying.
  

I've just been using vga=795 on the grub command line. That jumps the
display into 1280x1024 mode, and fits as much text as possible. A bit
of googling will find you other values that you might be able to use.

See if that solves the problem for you.

Have fun...
Daniel Foote.





Thank you for the input.  I would not have figured to use vga=.  I did a google 
for a vga of 1600x1200 but the system hung and after a while went through the 
startup.  Using vga=795 works just fine and I can actually work on the ttys.

-Thanks for your input

Adam


Modes above 1280x1024 are non-standard, and vary from graphics card to 
graphics card. The package "hwinfo" can work out your valid modes, from 
"hwinfo --framebuffer" - I seem to recall it gives output in Hex though, 
so you will need to convert to Decimal for putting in your menu.lst


No output at all suggests an uncooperative graphics card (in which case 
you should stick with 795 as a maximum)



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: how to setup KDE or Gnome

2006-08-26 Thread Thierry Chatelet

Chris Wakefield wrote:

On Friday 25 August 2006 10:06 pm, Viktor Tsyrennikov wrote:
  

  Hi,

  here is more description of the problem.
  It is a clean Etch beta 3 (AMD64) system (network) installed on
Opteron 170 system. During installation I chose 'Desktop' so after
reboot it should have loaded me into Gnome. However none of that
happened. After reboot I got only command line interface, but I can
start X server and get gray window with terminal window in 1600x1200
which means graphic card is not a problem (see lspci output below).
Mouse works too. I ran aptitude to see that I got both KDM and GDM
installed but at no point I am asked to choose one of them. xserver-xorg
is installed too.
  By suggestion of sigi I ran 'dkpg-reconfigure xserver-xorg' which failed.
  Next I removed and installed again xserver-xorg, (went through a long
list of boring questions), rebooted and again command line, but this
time it says that KDM has been started (which I didn't ask it to).

  Question: how to get graphic interface up and start working?
  My own guess: repository (I used ftp.debian.org) is broken -- but I do
not know how to check this (netinstall went smoothly). Other mirrors
known to work well?

  Thanks,
  Victor


I you have kdm installed it will execute normally without you having to *ask*.

OK, try this: 


 /etc/init.d/kdm stop;startkde

this kills kdm and starts kde manually.

send a report.  the mirror *could* be broken, but until you hear from others 
that it is happening, we try whatever we can.


chris w.


  
As far as I know, since about last Chrismass, I could not get any 
graphical interface on fresh install with Etch on amd64. I went to Sid 
for all new install. There seems to be for broken packages. To know wich 
one, runs, say apt-get install kde, it will tell you which meta package 
is not installable, then run again apt-get install instalable>, it will tell you with package is not installable in that 
metapackage, and so on until you can pinpoint which base package is broken.

Thierry


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]