Hosting Provided By

debian-user-digest Digest V2007 #2290

From: <debian-user-digest-request(at)lists.debian.org>
Date: Fri Aug 31 2007 - 22:22:41 EDT

Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 2290

Today's Topics:

  Re: Aptitude behaving strangely       [ Wayne Topa  ]
  hard disk crash                       [ pinniped  ]
  Re: Should /etc/hostname contain the  [ "Douglas A. Tutty"  ]
  Re: New installation - cannot increa  [ Chan Lee  ]

Date: Fri, 31 Aug 2007 18:46:15 -0400
From: Wayne Topa <linuxone@intergate.com> To: debian-user@lists.debian.org
Subject: Re: Aptitude behaving strangely

Message-ID: <20070831224615.GA20850@buddy.mtntop.home>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Celejar(celejar@gmail.com) is reported to have said:
> Hi,
>
> My aptitude (uptodate Sid) has been behaving rather strangely lately. When doing updates, it seems to always hang for long periods of time while displaying the line:
>
> 99% [5 Packages 4308]
>
> or similar. No processor, network or HDD usage seems to be occurring.
> It subsequently generally finishes okay, although I'm not sure it is
> always completing the update successfully (all packages I have manually
> checked against p.d.o seem to be at the latest version, but I haven't
> been very systematic about it). It also seems to be overall more
> sluggish and erratic. I know this is very vague and unhelpful, but I
> was just wondering if anyone has been seeing anything like this. I've
> tried playing with sources.list, but I get similar results no matter
> which mirror I use (I've only tried a few), and even with apt-get.
>

Yes. Started yesterday, here. I tried again then morning and it was still hanging at 12 PM EST when I finally was able to finish the upgrade.

Wayne

-- 
Think of your family tonight.  Try to crawl home after the computer
crashes.
_______________________________________________________

Date: Sat, 1 Sep 2007 01:17:39 +0200 (CEST) From: pinniped <cirilo_bernardo@yahoo.com> To: debian-user@lists.debian.org Subject: hard disk crash Message-Id: <listhandler=2&site=www.debianhelp.org&nid=9982&pid=&cid=35397&uid=76&tid=79&716e5e87edef8a27916c0032404e18ed@www.debianhelp.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable
>somebody out there who can give me a helping hand to repair
>somehow the hd or point me to a method/way or program to
>rescue at least my holiday-photographs from france i put on
>the hd two hours before the crash...?
The most important thing is to avoid using the disk as much as possible (= do not apply power, do not 'spin up' the disk). Then you need to set up to 'rescue' the data. If you have a second compu= ter with Linux then you're off to a good start. You will need to: 1. determine how large a disk you need to create an image of the partitio= ns on your failed drive. Of course you probably need to go out and buy so= me storage... 2. set up tools to: a. copy all readable blocks from the failed drive b. examine the image for the data you want The tools in (a) allow you to power up the bad drive and copy whatever is= possible with the minimum use of the disk. It is not unusual for a disk = to be permanently destroyed during this process or shortly afterwards - n= o fault of the tools, that's just the general way a disk fails. For (a) I would suggest 'ddrescue' which acts like 'dd' but skips bad blo= cks and simply moves on to the next block. This is the behavior you want= - you don't want to attempt a retry at this stage because that can make = matters worse. After your image recovery operation then you may consider = a second image using something like gddrescue to try to get even more dat= a. For (b) I would suggest 'testdisk'. It is generally used when people acc= identally wipe the partition table, but it has good tools for recovering = photos. It is very important that you don't try to hurry things - remember you wi= ll be lucky to have 1 shot at recovering data from a bad disk; you need t= o make absolutely sure that first try goes without a flaw. After setting = up, practise using these tools on another disk - maybe a faulty floppy, o= r even just a good disk. You really don't want to make any mistakes when = you get to the real job; especially not with a 'dd'-like tool. Once you have recovered an image with ddrescue (and maybe a second image = with gddrescue) then you can take your time finding other recovery tools = to extract even more data. Remember to mark these images 'read only' - yo= u don't want to accidentally write to them.

Do you need help?

Date: Fri, 31 Aug 2007 16:55:42 -0700 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: Aptitude behaving strangely Message-ID: <20070831235542.GO9843@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/D3X8sky0X3AmG5" Content-Disposition: inline --W/D3X8sky0X3AmG5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 31, 2007 at 06:46:15PM -0400, Wayne Topa wrote:
> Celejar(celejar@gmail.com) is reported to have said:
> > Hi,
> >=20
> > My aptitude (uptodate Sid) has been behaving rather strangely lately. =
When doing updates, it seems to always hang for long periods of time while = displaying the line:
> >=20
> > 99% [5 Packages 4308]=20
> >=20
> > or similar. No processor, network or HDD usage seems to be occurring.
> > It subsequently generally finishes okay, although I'm not sure it is
> > always completing the update successfully (all packages I have manually
> > checked against p.d.o seem to be at the latest version, but I haven't
> > been very systematic about it). It also seems to be overall more
> > sluggish and erratic. I know this is very vague and unhelpful, but I
> > was just wondering if anyone has been seeing anything like this. I've
> > tried playing with sources.list, but I get similar results no matter
> > which mirror I use (I've only tried a few), and even with apt-get.
> >=20
> Yes. Started yesterday, here. I tried again then morning and it was
> still hanging at 12 PM EST when I finally was able to finish the upgrade.
hmmm... this may explain why my cron-apt bombed last night. In fact I found 2 instances of cron-apt running and an aptitude that appeared to have been in existence for quite a while. note that this is an etch install though. But I wonder if its something on the server side? A --W/D3X8sky0X3AmG5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG2Kp+aIeIEqwil4YRAhNXAKCGgAtKkdqBTMtAg7LHjoyXuJAcSACg0/yU Dr2SVcuWPWgvimAXA6TPo5A= =S/xp -----END PGP SIGNATURE----- --W/D3X8sky0X3AmG5--

Date: Sat, 1 Sep 2007 01:24:52 +0200 From: Florian Kulzer <florian.kulzer+debian@icfo.es> To: debian-user@lists.debian.org Subject: Re: hard disk crash Message-ID: <20070831232452.GA3651@localhost> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 31, 2007 at 23:19:26 +0200, steef wrote:
> hi you all out there,
>
> one of my hd's crashed completely for unknown reasons. i tried several
> solutions without any result. knoppix 5.0 recognized the partition with
> data (/dev/hda1) but refuses to mount it: 'i could not determine the
> filesystem etc. etc. '
[...]
> somebody out there who can give me a helping hand to repair somehow the hd
> or point me to a method/way or program to rescue at least my
> holiday-photographs from france i put on the hd two hours before the
> crash...?
You can try to repair your partition table with TestDisk and/or to recover your photos with PhotoRec; both these tools are available in package "testdisk". The "scalpel" package is another option for trying to extract the files if you cannot restore the partition table. In any case it is probably a good idea to create a backup image of the whole disk first, as Peter Greff has already suggested. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian |

Date: Sat, 1 Sep 2007 01:44:51 +0200 From: Florian Kulzer <florian.kulzer+debian@icfo.es> To: debian-user@lists.debian.org Subject: Re: aptitude full-upgrade - why does it not install Recommended packages? Message-ID: <20070831234450.GB3651@localhost> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 31, 2007 at 20:24:43 +0200, Chris wrote:
> On Friday 31 August 2007 18:42, Sven Joachim wrote:
> > Hello,
> >
> > Chris writes:
> > > sudo aptitude full-upgrade --with-recommends
> > >
> > > can anyone tell me why it still reports (for example):
> > >
> > > The following packages are RECOMMENDED but will NOT be installed:
> > > libjaxp1.3-java-gcj libxalan2-java-gcj
> >
> > The aptitude manual says:
> >
> > -r, --with-recommends
> > Treat recommendations as dependencies when installing new packages
> >
> > Note the *new* here. Recommendations for existing packages are _not_
> > automatically installed, since aptitude presumes that you do not want
> > that; after all you did not install the recommended packages in
> > previous installs of your package.
> >
> > Of course this can be a problem since the recommendations may change
> > over time. This is probably what happened here.
> >
> > Regards,
> > Sven
>
> That at least explains the behavior, and makes sense I guess. But I'd
> actually like it to really install all "recommends", for all packages I have
> installed.
In principle you could run aptitude install '!~i~Rrecommends:~i' to do this. I am not sure, however, how well "OR" recommendations and recommendations of virtual packages will be handled. It is probably safer to start aptitude in interactive mode and use "l" to limit the display to packages matching the same pattern: !~i~Rrecommends:~i Then you can press "+" for each of these packages and use undo immediately for cases in which the installation would have unwanted side effects. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian |

Date: Sat, 01 Sep 2007 00:12:36 +0000 From: "dan baker" <kam2700@hotmail.com> To: debian-user@lists.debian.org Subject: kbuild fouls, trips, and sabotges ipw3945 wireless card installation Message-ID: <BAY123-F21592A6480C811D848BCFEADCF0@phx.gbl> Content-Type: text/plain; format=flowed I have heard from a user on irc #debian that I can use modules to get the ipw3945 wireless card working. I downloaded ipw3945-modules-2.6.22-1-686_2.6.2 2+1.2.1-1_i386.deb and installed it using kpackage. The log from kpackage shows that it installed: <esktop/ipw3945-modules-2.6.18-4-686_2.6.18+1.1.3-4_i386.deb' ;echo RESULT=$? (Reading database ... 150375 files and directories currently installed.) Preparing to replace ipw3945-modules-2.6.18-4-686 2.6.18+1.1.3-4 (using ..../ipw3945-modules-2.6.18-4-686_2.6.18+1.1.3-4_i386.deb) ... Unpacking replacement ipw3945-modules-2.6.18-4-686 ... Setting up ipw3945-modules-2.6.18-4-686 (2.6.18+1.1.3-4) ... RESULT=0 Although Im a bit concerned with the "RESULT=0" I tried detecting the card with KwifiManager but it doesn't recongnise it. It seems there are other parts that need installing. In both the following write ups It says you have to make sure the kernal headers are installed before the other parts. "Ipw3945 driver manual installation for Debian Etch" : 1 Step by step installation 1.1 Downloads 1.2 Install kernel headers 1.3 Complile and install modules 1.4 Init script 1.5 Enable start on boot 1.6 Interface configuration 1.7 Notes "Intel(R) PRO/Wireless 3945ABG Network Connection driver for Linux* in support of: Intel(R) PRO/Wireless 3945ABG Network Connection Adapter Intel(R) PRO/Wireless 3945BG Network Connection Adapter Copyright (C) 2005 - 2006, Intel Corporation INSTALL Version: 1.1.3" "INSTALLING THE BITS The installation requires the compiled kernel sources or headers against the matching kernel. These are typically found in: /lib/modules/\`uname -r\`/build If that directory does not exist, or is empty, you likely need to install the kernel source packages for your distribution. Once you have the kernel sources, you can make and install the ieee80211 subsystem via: % tar zxvf ieee80211-${VERSION} % cd ieee80211-${VERSION} % make So I try installing the header package "linux-headers-2.6.18-4-486_2.6.18.dfsg.1-12_i386" using kpackage But I keep geting the following error: <2.6.18-4-486_2.6.18.dfsg.1-12_i386.deb' ;echo RESULT=$? (Reading database ... 150375 files and directories currently installed.) Preparing to replace linux-headers-2.6.18-4-486 2.6.18.dfsg.1-12 (using ..../linux-headers-2.6.18-4-486_2.6.18.dfsg.1-12_i386.deb) ... Unpacking replacement linux-headers-2.6.18-4-486 ... dpkg: dependency problems prevent configuration of linux-headers-2.6.18-4-486: linux-headers-2.6.18-4-486 depends on linux-headers-2.6.18-4 (= 2.6.18.dfsg.1-12); however: Package linux-headers-2.6.18-4 is not installed. linux-headers-2.6.18-4-486 depends on linux-kbuild-2.6.18; however: Package linux-kbuild-2.6.18 is not installed. dpkg: error processing linux-headers-2.6.18-4-486 (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-2.6.18-4-486 RESULT=1 The key line being "linux-headers-2.6.18-4-486 depends on linux-kbuild-2.6.18; however: Package linux-kbuild-2.6.18 is not installed." So I try to install kbuild. But get this error: cpc3-seve3-0-0-cust864:~# cd /root/Desktop cpc3-seve3-0-0-cust864:~/Desktop# dpkg -i linux-kbuild-2.6.18_2.6.18-1_i386.deb (Reading database ... 150369 files and directories currently installed.) Unpacking linux-kbuild-2.6.18 (from linux-kbuild-2.6.18_2.6.18-1_i386.deb) .... dpkg-deb (subprocess): short read in buffer_copy (failed to write to pipe in copy) dpkg-deb: subprocess paste returned error exit status 2 dpkg: error processing linux-kbuild-2.6.18_2.6.18-1_i386.deb (--install): short read in buffer_copy (backend dpkg-deb during `./usr/src/linux-kbuild-2.6.18/scripts/mod/modpost.real-lsb-64') Errors were encountered while processing: linux-kbuild-2.6.18_2.6.18-1_i386.deb cpc3-seve3-0-0-cust864:~/Desktop# So I have to get kbuild to install. Any ideas greatly welcomed?? ps I able to get the laptop whith the wirless card problem to an internet cafe .. I can connect to his network using a cable but not to the internet. If I cant figure out how to get kbuild to install then Ill need help getting the laptop configured to use the internet cafes network and solve this problem with apt-get. He uses windows xp. _________________________________________________________________ Get Pimped! FREE emoticon packs from Windows Live - http://www.pimpmylive.co.uk

Date: Fri, 31 Aug 2007 20:26:08 -0400 From: "Douglas A. Tutty" <dtutty@porchlight.ca> To: debian-user@lists.debian.org Subject: Re: Should /etc/hostname contain the whole FQDN? Message-ID: <20070901002608.GA11666@titan.hooton> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 31, 2007 at 11:38:01AM -0500, Jonathan Wilson wrote:
> I have been trying to find out the exact and proper way to set the
> host and domain name on Debian and it's clear as mud. Searching the
> internet gives all sorts of conflicting answers.
Of course. Debian changes. UNIX changes. No to *NIX's are alike. The key to knowing the answer comes in understanding the fundamentals. A host is a host. One box, one name. A network is a network. One network, one name. Most hosts are only on one network, however, some hosts are on more than one network and would then possibly have more than one FQDN.
>
> "The host name is usually set once at system startup in
> /etc/rc.d/rc.inet1 or /etc/init.d/boot (normally by reading the
> contents of a file which contains the host name, e.g. /etc/hostname)"
>
> Those first 2 files don't exist on Debian Etch. And thought it says it
> usually gets the hostname from /etc/hostname, that still doesn't tell
> me if that should contain the hostname or the FQDN.
>
> Then it says "The FQDN of the system is the name that the resolver(3)
> returns for the host name."
>
> Ok, so what's the resolver? man 3 resolver returns nothing man
> resolver talks about /etc/resolv.conf. It does talking about setting
> "domain", then it says search and domain are mutually exclusive. So
> while /etc/resolv.conf may have some effect on the hostname, it surely
> isn't THE way the system gets it's FQDN.
The resolver is the code within libc that maps hostnames to IP addresses. That's all.
>
> Back to hostname man page:
>
> "Technically: The FQDN is the name gethostbyname(2) returns for the
> host name returned by gethostname(2). The DNS domain name is the part
> after the first dot."
>
> (where does gethostbyname(2) and gethostname(2) look?)
>
> "Therefore it depends on the configuration (usually in /etc/host.conf)
> how you can change it.
That used to be it, however, with libc6 (or was it 5), that changed to /etc/nsswitch.conf. That's Name Service Switch, and has many options.
> So that's still not where it's set. Manpage for hosts.conf says multi:
> "If set to on, the resolv+ library will return all valid addresses
> for a host that appears in the /etc/hosts file, instead of only the
> first."
>
> So that's how it looks up IP<-> name mappings, but that /still/
> doens't tell me how to set my FQDN.
>
> Can anyone who /knows/ tell me what the proper officially correct ways
> of setting the hostname and the FQDN are, please?
Ok. So you've named the computer. You put this hostname (the name up to but not including the network name(s) to which the box is attached), in /etc/hostname. So now /bin/hostname will give you your hostname. How does hostname -f give the FQDN? It asks the resover what the dommain name is. The resolver consults the /etc/nsswitch.conf file so see where to look. On debian, it tells it that for hosts it should consult files and if it doesn't get an answer, to consult the DNS via a DNS query to the nameserver that is configured with files, in this case /etc/resolv.conf. So, the first place it will look is in /etc/hosts. It will see, e.g. 192.168.1.5 rocky.hooton rocky It will see a FQDN and return rocky.hooton to my hostname -f request. Now, what if you didn't have this host in /etc/hosts? What if the only line was: 127.0.0.1 localhost ? It would then look in /etc/resolve.conf and see: nameserver 192.168.1.1 It will then issue a DNS request to 192.168.1.1 asking what the FQDN is for rocky. It will be told rocky.hooton. --- So to finally answer your question, you configure your FQDN wherever you want names resovled. If you want it in files on the box itself, then it goes in /etc/hosts. If you run your own name server like I do (I run dnsmasq for simplicity) then you only have to record the information in one place. I hope this long-winded answer is of some help. For more clarity, I'd suggest __UNIX_System_Administration_Handbook__ by Evi Nemeth, et. al. Doug.

Date: Fri, 31 Aug 2007 20:31:10 -0400 From: icelinux@icelinux.net To: debian-user@lists.debian.org Subject: re: hard disk crash Message-ID: <20070831203110.ihf811aggsggwg8c@icelinux.net> Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit I do not know what filesystems you are using, but most fileststems have a repair utility. I would try that running that manually on the unmounted partitions first. http://www.adminschoice.com/docs/fsck.htm

Date: Fri, 31 Aug 2007 20:32:14 -0400 From: "Douglas A. Tutty" <dtutty@porchlight.ca> To: debian-user@lists.debian.org Subject: Re: NMI received, likely on the PCI bus Message-ID: <20070901003214.GB11666@titan.hooton> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 31, 2007 at 07:22:21PM +0100, Anthony Campbell wrote:
> "NMI received, likely on the PCI bus ..." together with stuff about a
> hardware problem.
>
> In the last couple of days I've received this worrying message during
> re-awakening from suspend to disk. It doesn't seem to happen in ordinary
> booting. I googled for similar messages and found a few but no very
> clear resolution, although there are some suggestions it could be a
> kernel bug.
>
> I ran memtest86 for 22 hours without errors. I also twice compiled a
> kernel, again without errors.
>
> I'm using a Thinkpad Z61M with Sid, kernel 2.6.20.1-slh-smp-2.
>
> Question: is this a false alarm? If not, what tests to do? The machine
> is still under warranty but I don't know what fault I could report.
Thinkpads have very good advanced diagnostics. If you don't have manuals telling you how to access them, check out IBM's website (even a google site:ibm.com ) using your machine number (the four-digit IBM number not the sales dept's Z61M. You should be able to find the service manual for it which will tell you how to run the advanced diagnostics. It is those diagnostics that IBM will run to determine a warranty claim. The manual tells them which FRUs to swap out until the diagnostics tell them that the machine is good. Good luck. Doug.

Date: Fri, 31 Aug 2007 20:37:43 -0400 From: "Douglas A. Tutty" <dtutty@porchlight.ca> To: debian-user@lists.debian.org Subject: Re: How to bind keys to commands, without requiring login? Message-ID: <20070901003743.GC11666@titan.hooton> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 31, 2007 at 11:32:49PM +0100, Benjamin A'Lee wrote:
> It's also perfectly possible to disable switching to a VT from X11. I
> seem to remember Ubuntu does by default, which I always discover just
> when I have a problem that I need to switch to a terminal for...
>
Untill the X server dies and you end up at a VT. Doug.

Do you need more help?

Date: Fri, 31 Aug 2007 20:50:00 -0400 From: gavron <cga2000@optonline.net> To: debian-user@lists.debian.org Subject: how can I find out if ttf native hinting is enabled? Message-id: <20070901005000.GC2819@turki.gavron.org> Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline Does anyone know how I can figure out if native hinting for truetype fonts is enabled? I've been running etch for a couple months now and I understand that this is the way to go with quality fonts such as Microsoft Verdana. That's the screen font I use wherever I can and it does not render quite as well on debian etch as on a Windows machine. Is there a way I can find out? And if it it turns out it is not enabled, is there a document anywhere that explains how I could enable it on a debian system? Thank you! gavron.

Date: Fri, 31 Aug 2007 18:05:53 -0700 (PDT) From: Chan Lee <chanl@pacbell.net> To: Johannes Wiedersich <johannes@physik.blm.tu-muenchen.de> Cc: debian-user@lists.debian.org Subject: Re: New installation - cannot increase the screen resolution Message-ID: <231512.63063.qm@web80612.mail.mud.yahoo.com> Content-Type: multipart/alternative; boundary="0-1412571887-1188608753=:63063" Content-Transfer-Encoding: 7bit --0-1412571887-1188608753=:63063 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi Johannes, =20 Thanks for your info - I did follow your guide and BINGO ! =20 The screen now looks nice & sharp as it's drawing 1280x1024. =20 I didn't know that it's X config related, as I thought it's GNOME issue - turns out GNOME is based on X stuffs - I'm completely newbie to Debian world, though 've been using Unix for longtime. =20 Thanks ! =20 Chan Johannes Wiedersich <johannes@physik.blm.tu-muenchen.de> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chan Lee wrote:
> Hi,
>=20
> I just installed Debian using DVD set from CheapBytes
> into a new HP Pavilion Slimline s3020n desktop. It has
> Nvidia GeForce 6150LE graphics adaptor driving 1280x1024
> resolution.
>=20
> Thrying to increase the screen resolution using the Screen
> resoultion preference tool, however, I cannot find any extra
> resolution option in the menu - only the basic resolution of
> 640x480 is available. The Samsung 19inch LCD screen can
> display 1280x1024 - how can I increase it ?
I don't know what your 'Screen resolution preference tool' is. You probably have to 'dpkg-reconfigure xserver-xorg' if you haven't tried already. Log out as ordinary user, switch to a console like tty1 and log in as root before doing so. After reconfiguration you'd have to restart the xserver with '/etc/init.d/kdm restart' or gdm, or whatever your X display manager is. You do have xserver-xorg installed, don't you? Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG19NmC1NzPRl9qEURAtt7AJ4u6aX5/2C4H0eQahFPaG42GrKJDQCggKq3 iQkJ7PffpY5RRjmypczc+mM=3D =3Dh1Wi -----END PGP SIGNATURE----- --=20 To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org=20 with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian= .org --0-1412571887-1188608753=:63063 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <div>Hi Johannes,</div> <div> </div> <div>Thanks for your info - I= did follow your guide and BINGO !</div> <div> </div> <div>The scr= een now looks nice & sharp as it's drawing 1280x1024.</div> <div>&nb= sp;</div> <div>I didn't know that it's X config related, as I thought it= 's GNOME</div> <div>issue - turns out GNOME is based on X stuffs - I'm c= ompletely</div> <div>newbie to Debian world, though 've been using Unix = for longtime.</div> <div> </div> <div>Thanks !</div> <div> <= /div> <div>Chan<BR><BR><B><I>Johannes Wiedersich <johannes@physik.blm= .tu-muenchen.de></I></B> wrote:</div> <BLOCKQUOTE class=3Dreplbq styl= e=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"=
>-----BEGIN PGP SIGNED MESSAGE-----<BR>Hash: SHA1<BR><BR>Chan Lee wrote:<=
BR>> Hi,<BR>> <BR>> I just installed Debian using DVD set from C= heapBytes<BR>> into a new HP Pavilion Slimline s3020n desktop. It has<= BR>> Nvidia GeForce 6150LE graphics adaptor driving 1280x1024<BR>> resolution.<BR>> <BR>> Thrying t= o increase the screen resolution using the Screen<BR>> resoultion pref= erence tool, however, I cannot find any extra<BR>> resolution option i= n the menu - only the basic resolution of<BR>> 640x480 is available. T= he Samsung 19inch LCD screen can<BR>> display 1280x1024 - how can I in= crease it ?<BR><BR>I don't know what your 'Screen resolution preference t= ool' is. You<BR>probably have to 'dpkg-reconfigure xserver-xorg' if you h= aven't tried<BR>already. Log out as ordinary user, switch to a console li= ke tty1 and log<BR>in as root before doing so. After reconfiguration you'= d have to restart<BR>the xserver with '/etc/init.d/kdm restart' or gdm, o= r whatever your X<BR>display manager is.<BR><BR>You do have xserver-xorg = installed, don't you?<BR><BR>Johannes<BR>-----BEGIN PGP SIGNATURE-----<BR=
>Version: GnuPG v1.4.6
(GNU/Linux)<BR><BR>iD8DBQFG19NmC1NzPRl9qEURAtt7AJ4u6aX5/2C4H0eQahFPaG42G= rKJDQCggKq3<BR>iQkJ7PffpY5RRjmypczc+mM=3D<BR>=3Dh1Wi<BR>-----END PGP SIGN= ATURE-----<BR><BR><BR>-- <BR>To UNSUBSCRIBE, email to debian-user-REQUEST= @lists.debian.org <BR>with a subject of "unsubscribe". Trouble? Contact l= istmaster@lists.debian.org<BR><BR></BLOCKQUOTE><BR> --0-1412571887-1188608753=:63063-- End of debian-user-digest Digest V2007 Issue #2290 ************************************************** Received on Fri Aug 31 22:16:31 2007

This message: [ Message body ]
Next message: debian-user-digest-request(at)lists.debian.org: "debian-user-digest Digest V2007 #2291"
Previous message: debian-user-digest-request(at)lists.debian.org: "debian-user-digest Digest V2007 #2289"

Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ] [ By messages with attachments ]

This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 07:54:22 EDT