On Wed, Sep 30, 2009 at 7:54 AM,
<debian-user-digest-request@lists.debian.org> wrote:
Content-Type: text/plain
debian-user-digest Digest Volume 2009 : Issue 1633
Today's Topics:
Re: xorg still locking up for me on [ Michael Pobega <pobega@fuzzydev.org ]
Re: X crashing after upgrade: urgent [ Mark Goldshtein <mark.goldshtein@gm ]
Re: dhclient DHCPREQUEST loop [ Michael Pobega <pobega@fuzzydev.org ]
Re: dhclient DHCPREQUEST loop [ Jerome BENOIT <jgmbenoit@mailsnare. ]
Re: how to get sound back? [ Marc Shapiro <mshapiro_42@yahoo.com ]
Re: how to downgrade and pin package [ "Robert P. J. Day" <rpjday@crashcou ]
Re: X crashing after upgrade: urgent [ mihkel <turakas@gmail.com> ]
Re: Downgrade libxi6 -- HowTo? (Bug [ Klistvud <quotations@aliceadsl.fr> ]
Re: X crashing after upgrade: urgent [ Anthony Campbell <ac@acampbell.org. ]
Re: Building a 2.6.30 kernel that do [ Alex Samad <alex@samad.com.au> ]
Re: X crashing after upgrade: urgent [ Sven Joachim <svenjoac@gmx.de> ]
Re: how to downgrade and pin package [ Andrei Popescu <andreimpopescu@gmai ]
Re: apache on debian [ SergeyNaumov <naumov@ros.panasonic. ]
Re: X crashing after upgrade: urgent [ "Dr. Jennifer Nussbaum" <bg271828@y ]
Re: X crashing after upgrade: urgent [ Rakotomandimby Mihamina <mihamina@g ]
Re: Building a 2.6.30 kernel that do [ Tixy <debianuser@tixy.myzen.co.uk> ]
Date: Tue, 29 Sep 2009 23:58:48 -0400
From: Michael Pobega <pobega@fuzzydev.org>
To: debian-user@lists.debian.org
Subject: Re: xorg still locking up for me on testing
Message-ID: <[🔎] 20090930035848.GA19207@fuzzydev.org">[🔎] 20090930035848.GA19207@fuzzydev.org>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On 0, Frank <debianlist@videotron.ca> wrote:
> I had high hopes this morning when xorg-xserver-video-intel got updated
> but no such luck. Since then my machine has locked up tight (alt-sysreq tight)
> about 5 times.
> [...]
>
What kernel are you running? I remember reading that on Intel video cards there
are a lot of problems with kernels under 2.6.30. So, I advise you upgrade (or
try compiling) 2.6.31 -- it fixed a lot of my problems with the new Xorg.
--
http://fuzzydev.org/~pobega
http://identi.ca/pobega
Date: Wed, 30 Sep 2009 08:11:19 +0400
From: Mark Goldshtein <mark.goldshtein@gmail.com>
To: Debian User Mailing List <debian-user@lists.debian.org>
Subject: Re: X crashing after upgrade: urgent!
Message-ID: <[🔎] 3eb61c3d0909292111j19e1b677i40c81cf8b56cdc5@mail.gmail.com">[🔎] 3eb61c3d0909292111j19e1b677i40c81cf8b56cdc5@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Sep 30, 2009 at 7:11 AM, Dr. Jennifer Nussbaum
<bg271828@yahoo.com> wrote:
> Hi. Im running Sid on a Thinkpad T60, and recently rebooted my machine after having done several updates recently. I now find that X is crashing hard on boot, rendering the system unusabler.
As already mentioned here, you are brave to run Sid on working laptop.
Unfortunately, it is a testing branch of Debian and it is supposed to
be like that.
> But my system doesnt crash randomly, it wont even start in the first place.
So, the 'system wont even start' you mean X.org does not working properly?
> I reinstalled all xorg modules, and the mesa libraries (someone in that thread suggested this) but it still crashes in the same way. Im not using a config file, i just use the automatic one, and i dont want to do anything fancy.
If you are using T60 laptop, probably you have ATI video card. Well,
you have an option to completely change a driver for another one.
There are few drivers for ATI.
> I am supposed to give a presentation tomorrow with this laptop and its the only one i have so Im DESPERATE to get this resolve....
I tnink, first of all, you should secure you work situation. I am
suggesting you to download Ubuntu 9.04. Your laptop should work fine
with that desktop system.
Try it as a LiveCD system first. At least, you may try to make a
bootable USB stick with Ubuntu 9.04 and probably it will have enough
speed to show your presentation even without being Ubuntu installed on
your hard drive. In most cases, you will have an access to your data
on your laptop's hard drive. Mind the permissions.
Or, you may repartition your hard drive and install Ubuntu on it and
have dual boot laptop.
IMHO, for the future, you should have dual boot option, if you want to
play with testing distribution. If you want Debian, you should have
current 'stable' - Lenny and 'testing' - Sid.
Well, Good luck!
--
Sincerely Yours'
Mark Goldshtein
Date: Wed, 30 Sep 2009 00:12:50 -0400
From: Michael Pobega <pobega@fuzzydev.org>
To: debian-user@lists.debian.org
Subject: Re: dhclient DHCPREQUEST loop
Message-ID: <[🔎] 20090930041250.GA31820@fuzzydev.org">[🔎] 20090930041250.GA31820@fuzzydev.org>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On 0, Jerome BENOIT <jgmbenoit@mailsnare.net> wrote:
> Hello List,
>
> on my Lenny box, the message
>
> dhclient: DHCPREQUEST on eth0 to n.n.n.n port 67
>
> is printed continuously on the syslog file.
>
> [...]
>
> Thanks in advance,
> Jerome
>
I get this problem on some networks; it seems to me that some routers just
don't play nicely with dhclient. I've tried multiple times to find the source,
but I've yet to have any luck.
Sorry I couldn't be of more help. If I were you I'd contact your system
administrator.
--
http://fuzzydev.org/~pobega
http://identi.ca/pobega
Date: Wed, 30 Sep 2009 12:38:09 +0800
From: Jerome BENOIT <jgmbenoit@mailsnare.net>
To: debian-user@lists.debian.org
Subject: Re: dhclient DHCPREQUEST loop
Message-ID: <[🔎] 4AC2E0B1.2050400@mailsnare.net">[🔎] 4AC2E0B1.2050400@mailsnare.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hello List,
Michael Pobega wrote:
> On 0, Jerome BENOIT <jgmbenoit@mailsnare.net> wrote:
>> Hello List,
>>
>> on my Lenny box, the message
>>
>> dhclient: DHCPREQUEST on eth0 to n.n.n.n port 67
>>
>> is printed continuously on the syslog file.
>>
>> [...]
>>
>> Thanks in advance,
>> Jerome
>>
>
> I get this problem on some networks; it seems to me that some routers just
> don't play nicely with dhclient. I've tried multiple times to find the source,
> but I've yet to have any luck.
>
> Sorry I couldn't be of more help. If I were you I'd contact your system
> administrator.
I least someone has the same trouble with dhclient.
Concerning my system administrator, let put in this way:
my Company is running Windows stuff, and the system administrator
does not seem very cooperative.
Anyway, in fact, I can refine the description of the trouble:
the request is looping after the lease time (as set by the dhcp server),
and after a while the request is answered, and then no request is done
until the end of the lease time. So it is a kind of periodic behaviour.
As I have no control over the dhcp server,
I wonder if dhclient can manage the bad behaviour of the router
by setting some parameters.
Thanks,
Jerome
>
> --
> http://fuzzydev.org/~pobega
> http://identi.ca/pobega
>
>
--
Jerome BENOIT
jgmbenoit_at_mailsnare_dot_net
Date: Tue, 29 Sep 2009 22:43:39 -0700
From: Marc Shapiro <mshapiro_42@yahoo.com>
To: debian-user@lists.debian.org
Subject: Re: how to get sound back?
Message-ID: <[🔎] 4AC2F00B.4020601@yahoo.com">[🔎] 4AC2F00B.4020601@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hugh Lawson wrote:
> Marc Shapiro <mshapiro_42@yahoo.com> writes:
>
>> My system occasionally loses sound. In my case, it is invariably a
>> runaway firefox process that was trying to play flash and something
>> went wrong. I find the offending process (this is normally an extra
>> process, separate from any currently active firefox process) and kill
>> it and that will generally bring sound back without any more drastic
>> actions.
>
>
> That could have been the problem.
>
> Would you mind explaining a little more how you isolate the offending
> process? Or post a reference URL that covers this issue?
Since, in my case, it is almost alway Firefox that has caused the
problem, I run the following script. All it does is parse the output of
'ps' and lists all Firefox processes that it finds. Usually there
should be three: one each for myself, my wife and my daughter. Anything
beyond that is suspect. If you should only have a single instance of
Firefox then shut it down and run this script. If it finds anything
then it probably needs to be killed. I also use this script to find
which of the three Firefox processes is hogging all of the memory, or
CPU time when the system grinds to a standstill.
#!/usr/bin/perl
&check_ps;
exit();
# Subroutines #
sub check_ps {
@message=`ps -eo pid,uid,%cpu,%mem,comm`;
$message_text='';
foreach (@message) {
($pid, $uid, $cpu, $mem, $comm) = split(' ', $_, 5);
chomp $comm;
if ($uid >= 1000) {
if ($comm eq 'firefox-bin') {
print $_;
}
}
}
}
--
Marc Shapiro
mshapiro_42@yahoo.com
Date: Wed, 30 Sep 2009 02:24:54 -0400 (EDT)
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Niu Kun <haoniukun@gmail.com>
cc: Debian User List <debian-user@lists.debian.org>
Subject: Re: how to downgrade and pin package (durep)?
Message-ID: <[🔎] alpine.LFD.2.00.0909300223420.12307@localhost>
Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1094460917-1254291896=:12307"
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323328-1094460917-1254291896=:12307
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
On Wed, 30 Sep 2009, Niu Kun wrote:
> Robert P. J. Day =E5=86=99=E9=81=93:
> > On Wed, 30 Sep 2009, Niu Kun wrote:
> >
> > > Robert P. J. Day =E5=86=99=E9=81=93:
> > >
> > > > as a followup to an earlier post of mine, i can see now that the
> > > > current durep package (0.9-1) works *very* differently from the
> > > > earlier one, so rather than fight with the new one, i'm happy to
> > > > use the older version. how exactly does one downgrade a package
> > > > to a particular version, then make sure it stays there over
> > > > upgrades? thanks, i've been awake for a day and a half and i'm
> > > > just too tired to go looking for the answer. sorry.
> >
> > > If you're using aptitude, command like this may be of a little help
> > > "aptitude install apt=3D0.3.1". Or you can just download the specific
> > > deb package and try to install it by yourself.
> > then how to pin that version from the command line?
> Here, you'll have to find the specific deb package you're after.
> Maybe from some backport sites. You can find the package version in
> its name.
i already have the earlier package, and have installed it. the
remaining question is how to pin that package at that version so it
won't get re-upgraded at the next upgrade.
rday
--8323328-1094460917-1254291896=:12307--
Date: Wed, 30 Sep 2009 09:25:10 +0300
From: mihkel <turakas@gmail.com>
To: "Dr. Jennifer Nussbaum" <bg271828@yahoo.com>
CC: debian-user@lists.debian.org
Subject: Re: X crashing after upgrade: urgent!
Message-ID: <[🔎] 4AC2F9C6.6090609@gmail.com">[🔎] 4AC2F9C6.6090609@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dr. Jennifer Nussbaum kirjutas:
> I am willing to downgrade X but dont know how to do this. Or if it will help.
I had the same problem yesterday. In order to downgrade X, I booted to single
user mode, purged all X related packages, changed sid to testing in
/etc/apt/sources.list file and installed X again.
Since the problem appeared after upgrading xserver-common, xserver-xephyr and
xserver-xorg-core to version 1.6.4-1, I assume you really don't need to purge
all X related packages, just these three.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkrC+cYACgkQ2jT3PWjFNx6wbwCfZ2XAjykdDMyvk7JEQNog5HBv
84YAn2cEhUSevqziaeI4sQQJ46bHKwt0
=cm7T
-----END PGP SIGNATURE-----
Date: Wed, 30 Sep 2009 09:51:45 +0200
From: Klistvud <quotations@aliceadsl.fr>
To: debian-user@lists.debian.org
Subject: Re: Downgrade libxi6 -- HowTo? (Bug 515734)
Message-Id: <[🔎] 1254297105.6815.0@debian>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Dne, 29. 09. 2009 23:39:28 je Johan Kullstam napisal(a):
> Klistvud <quotations@aliceadsl.fr> writes:
>=20
> > Greetings, fellow Debianites!
> >
> > I've recently installed Debian 5.0.3 on my other machine and am=20
> > experiencing bug=20
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D515734=20
> > (keymaps messed up in X).
> >
> > Now, the suggestion is to downgrade the libxi6 library. I have
> several=20
> > "noob" questions about that:
>=20
> You will want to know the bad version for step 2. Use aptitude show
> <package> to print information. Copy the version string, call it
> <version>.
>=20
> > 1. How do you go about "downgrading" a package in Debian --
> especially=20
> > if it's a fresh system that's never been "upgraded" in the first
> > place?
>=20
> With ftp over to your debian repository and download a past version.=20
> I
> just did this on my sid boxen with xserver-xorg-core and
> xserver-common.
> I just fetched the older testing versions. There is also
> debian-snapshot which will give older versions. Use dpkg -i
> <package...>.deb to install it. The dpkg command will warn you about
> the downgrade.
>=20
> There's probably some fancy way to do the above with aptitude.
>=20
> > 2. Won't the Debian maintainers fix the issue in a future official=20
> > update=20
> > anyway? Wouldn't "downgrading" the package on my own accord
> potentially=20
> > interfere with such official update?
>=20
> This is the trick: forbid the offending version. Do
> aptitude forbid-version <package>=3D<version>
> This says you don't want *that* version, but that future updates are
> acceptable.
>=20
> > 3. How come there still hasn't been such an update? The bug is
> marked=20
> > as "grave" and it probably wouldn't be hard for the maintainer(s)=20
> to
>=20
> > force the reccommended downgrade of the libxi6 library in a regular=20
> > update?
>=20
> Sometimes bug fixes take longer than you'd like. It's a vollonteer
> effort. The maintainer has to be available, find a solution and test
> it, wait for build and then debian seems to release new filesets=20
> twice
> daily.
>=20
> That said, when a clearly broken version gets released, detected and
> acknowledged, there could perhaps be some automated mechanism to
> revert
> to previous.
>=20
> > Forgive my noobness, but I still haven't quite grasped the Debian=20
> > procedures and mechanisms. But I'm doing a lot of reading, so I=20
> hope
>=20
> > I'll catch up in time. I already know how to open a terminal and
> type=20
> > "ls".
> >
> > TIA
> >
> > --=20
> > Certifiable Loonix User 481801
>=20
> --=20
> Johan KULLSTAM
>=20
>=20
> --=20
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org=20
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>=20
>=20
>=20
Many thanx for the exhaustive explanation, it cleared many hazy notions=20
in my head. Now I know how to proceed.
Regards,
Klistvud
--=20
Certifiable Loonix User 481801
Date: Wed, 30 Sep 2009 08:51:43 +0100
From: Anthony Campbell <ac@acampbell.org.uk>
To: debian-user@lists.debian.org
Subject: Re: X crashing after upgrade: urgent!
Message-ID: <[🔎] 20090930075143.GA4017@acampbell.org.uk">[🔎] 20090930075143.GA4017@acampbell.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On 30 Sep 2009, mihkel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dr. Jennifer Nussbaum kirjutas:
> > I am willing to downgrade X but dont know how to do this. Or if it will help.
>
> I had the same problem yesterday. In order to downgrade X, I booted to single
> user mode, purged all X related packages, changed sid to testing in
> /etc/apt/sources.list file and installed X again.
> Since the problem appeared after upgrading xserver-common, xserver-xephyr and
> xserver-xorg-core to version 1.6.4-1, I assume you really don't need to purge
> all X related packages, just these three.
>
A lot of people seem to have been bitten by this one. It hit me
yesterday on my Thinkpad Z61M (quite similar to the T60). I then
remembered that I'd just upgraded xserver-common and xserver-xorg-core.
Fortunately both earlier versions were still in the cache so I
downgraded both (not being sure which was the culprit) and X came back
to life. From another post on this list it seems it would be necessary
to go back to lenny for an earlier version if you no longer have it in
the cache.
Anthony
--
Anthony Campbell - ac@acampbell.org.uk
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk (blog, book reviews,
and sceptical articles)
Date: Wed, 30 Sep 2009 18:23:31 +1000
From: Alex Samad <alex@samad.com.au>
To: debian-user@lists.debian.org
Subject: Re: Building a 2.6.30 kernel that does NOT require initrd
Message-ID: <[🔎] 20090930082331.GC667@samad.com.au">[🔎] 20090930082331.GC667@samad.com.au>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X"
Content-Disposition: inline
--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Sep 29, 2009 at 09:51:12PM -0400, Andrew Perrin wrote:
> On Wed, 30 Sep 2009, Alex Samad wrote:
>=20
> >On Tue, Sep 29, 2009 at 05:46:47PM -0400, Justin Piszcz wrote:
[snip]
> >I was just seeing if I was missing something, it just seems like a pain
> >to have to recompile, although with all the tools thats easy. Maybe it
> >just me getting older, but I tend to stick to the path of least
> >resistance.
> >
>=20
> Ironically I go with no initrd for exactly the same reason - I've
> never learned to build the initrd file, and it seems harder to
> handle the extra step. But given this hurdle I may just have to
> learn!
strange cause you should be able to apt-get linux-image-<flavour> and it
will build the initrd for you nothing more to do, but that means use the
stock debian kernel
>=20
> Andy
--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkrDFYMACgkQkZz88chpJ2NgtwCg8va4pdDjZkwcBNhQPwvnrPoL
s20An3nd+dnYCRyv6SSz5JP2mJ5EMw3t
=5VFx
-----END PGP SIGNATURE-----
--LZvS9be/3tNcYl/X--
Date: Wed, 30 Sep 2009 11:01:06 +0200
From: Sven Joachim <svenjoac@gmx.de>
To: debian-user@lists.debian.org
Subject: Re: X crashing after upgrade: urgent!
Message-ID: <[🔎] 87bpksbyct.fsf@turtle.gmx.de">[🔎] 87bpksbyct.fsf@turtle.gmx.de>
Content-Type: text/plain; charset=us-ascii
On 2009-09-30 09:51 +0200, Anthony Campbell wrote:
> A lot of people seem to have been bitten by this one. It hit me
> yesterday on my Thinkpad Z61M (quite similar to the T60). I then
> remembered that I'd just upgraded xserver-common and xserver-xorg-core.
> Fortunately both earlier versions were still in the cache so I
> downgraded both (not being sure which was the culprit) and X came back
> to life. From another post on this list it seems it would be necessary
> to go back to lenny for an earlier version if you no longer have it in
> the cache.
There is no reason to go back to Lenny, which is quite risky anyway
since it involves downgrading many packages. Just downgrade
xserver-xorg-core to the Squeeze (not Lenny!) version.
Sven
Date: Wed, 30 Sep 2009 12:15:14 +0300
From: Andrei Popescu <andreimpopescu@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: how to downgrade and pin package (durep)?
Message-ID: <[🔎] 20090930091514.GC3151@think.homelan>
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="yVhtmJPUSI46BTXb"
Content-Disposition: inline
--yVhtmJPUSI46BTXb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed,30.Sep.09, 02:24:54, Robert P. J. Day wrote:
=20
> i already have the earlier package, and have installed it. the
> remaining question is how to pin that package at that version so it
> won't get re-upgraded at the next upgrade.
Something like this in /etc/apt/preferences should work, see=20
apt_preferences(5) for more info:
Explanation: keep this package version even if older
Package: durep
Pin: version 0.8.1-7
Pin-Priority: 1001
Check with 'apt-cache policy durep'.
Regards,
Andrei
--=20
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
--yVhtmJPUSI46BTXb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBCAAGBQJKwyGiAAoJEHNWs3jeoi3prGgH/0uTyv5pGqoSNM2CzKMyWT9y
ro1lcb99WrXNsbm0UwhEX87KXZ/nlT+ritEg1o7O29WxgkCQFA54N1U0moWt+Qfw
4Mf9v8xVpb1IdMxym9G1ZKYa8fCjLWtqCz4H07WcTQS9HWU59lEYSf+ECpxBqokC
Z7v6zcnE4rFeI7f11iZLo9DX79rLCJFo84uCtzBQP/67dZtlpW77ehODBhkGlLrt
cMt99LJL6eaPNccGVknObQFARi06DgLGMkMQKJS6mtpKEnU6e4yZ8wl368N9dFkW
UIe9jTYKUhOFq6K1oS/8/EE5zgJ+rB9PI/X2YFBmOHBwPivnPwieXZ+kmhphxLk=
=XXO7
-----END PGP SIGNATURE-----
--yVhtmJPUSI46BTXb--
Date: Wed, 30 Sep 2009 13:18:14 +0400
From: SergeyNaumov <naumov@ros.panasonic.ru>
To: debian-user@lists.debian.org
Subject: Re: apache on debian
Message-ID: <[🔎] 4AC32256.6050601@ros.panasonic.ru">[🔎] 4AC32256.6050601@ros.panasonic.ru>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Rick Pasotto пишет:
>
> 3) When I (re)start apache I get the warning:
>
> apache2: Could not reliably determine the server's fully qualified
> domain name, using niof.net for ServerName
>
> I have several virtual sites installed, including niof.net. This error
> doesn't seem to be causing a problem but I'd like to get rid of the
> message and I don't know which config lines conflict or are wrong.
>
> Can you help?
>
> BTW, I keep up2date using 'testing'.
>
Try to find your problem here
http://www.wallpaperama.com/forums/how-to-fix-could-not-determine-the-servers-fully-qualified-domain-name-t23.html
Naumov Sergey
Date: Wed, 30 Sep 2009 02:59:55 -0700 (PDT)
From: "Dr. Jennifer Nussbaum" <bg271828@yahoo.com>
To: debian-user@lists.debian.org, Anthony Campbell <ac@acampbell.org.uk>
Subject: Re: X crashing after upgrade: urgent!
Message-ID: <[🔎] 399313.63501.qm@web53506.mail.re2.yahoo.com">[🔎] 399313.63501.qm@web53506.mail.re2.yahoo.com>
Content-Type: text/plain; charset=us-ascii
--- On Wed, 9/30/09, Anthony Campbell <ac@acampbell.org.uk> wrote:
> From: Anthony Campbell <ac@acampbell.org.uk>
> Subject: Re: X crashing after upgrade: urgent!
> To: debian-user@lists.debian.org
> Date: Wednesday, September 30, 2009, 12:51 AM
> On 30 Sep 2009, mihkel wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Dr. Jennifer Nussbaum kirjutas:
> > > I am willing to downgrade X but dont know how to
> do this. Or if it will help.
> >
> > I had the same problem yesterday. In order to
> downgrade X, I booted to single
> > user mode, purged all X related packages, changed sid
> to testing in
> > /etc/apt/sources.list file and installed X again.
> > Since the problem appeared after upgrading
> xserver-common, xserver-xephyr and
> > xserver-xorg-core to version 1.6.4-1, I assume you
> really don't need to purge
> > all X related packages, just these three.
> >
>
> A lot of people seem to have been bitten by this one. It
> hit me
> yesterday on my Thinkpad Z61M (quite similar to the T60). I
> then
> remembered that I'd just upgraded xserver-common and
> xserver-xorg-core.
> Fortunately both earlier versions were still in the cache
> so I
> downgraded both (not being sure which was the culprit) and
> X came back
> to life. From another post on this list it seems it would
> be necessary
> to go back to lenny for an earlier version if you no longer
> have it in
> the cache.
Thank you to everyone who responded!!!
To solve this i remove xserver-common and xserver-xorg-core, swittched from Sid back to Testing in my sources.list, and reinstalled.
And it worked right away (not counting another problem that was just my stupidity).
In response to the people who said i shouldnt run Sid on an important system, Id say that its been working fine for me all along.
There have been a few times when Ive messed things up but this has always been because i wasnt paying attention.
But on its own, Sid has been totally stable. And Ive sometimes wanted newer packages....
My big mistake here was to upgrade right before a presentation. Otherwise i would have been able to figure things out without panicing. And I should have been able to figure this out anyway!!!
This time Im bringing an Ubuntu LiveCD with me, Just-In-Case.
Thanks again.
Jen
Date: Wed, 30 Sep 2009 13:16:33 +0300
From: Rakotomandimby Mihamina <mihamina@gulfsat.mg>
To: debian-user@lists.debian.org
Subject: Re: X crashing after upgrade: urgent!
Message-ID: <[🔎] 4AC33001.5010304@gulfsat.mg">[🔎] 4AC33001.5010304@gulfsat.mg>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
09/30/2009 12:59 PM, Dr. Jennifer Nussbaum:
> My big mistake here was to upgrade right before a presentation.
[YES] :-)
--
Architecte Informatique chez Blueline/Gulfsat:
Administration Systeme, Recherche & Developpement
+261 34 29 155 34
Date: Wed, 30 Sep 2009 11:29:25 +0100
From: Tixy <debianuser@tixy.myzen.co.uk>
To: debian-user@lists.debian.org
Subject: Re: Building a 2.6.30 kernel that does NOT require initrd
Message-Id: <[🔎] 1254306565.3699.30.camel@computer2.home>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
On Tue, 2009-09-29 at 17:34 -0400, Justin Piszcz wrote:
> Anyone else with grub2 have any advice for Andrew? Is it normal for grub2
> to show a blank screen when booting a kernel?
When I upgraded to Grub2 last week I was getting a completely blank
screen during kernel boot. Eventually I fixed things by editing the
linux command line at boot to add "vga=795" - this sets the console
screen mode to 1280x1024.
(After boot the change can be made permanent by adding "vga=795" to the
GRUB_CMDLINE_LINUX entry in /etc/default/grub, then running
update-grub.)
I have noticed that running "vbeinfo" under grub2 shows modes that I've
not managed to get the kernel to handle, e.g. widescreen modes. Giving
it one of these modes results in black screens during boot and for my
console afterwards.
--
Tixy