I used the 64bit graphics install on debian-6.0.0-amd64-i386-netinst.iso
which I downloaded from debian.org.  Of course, I had a recent backup
available because the install cleaned the HD.

Robin

On Tue, Feb 8, 2011 at 12:41 PM, Mel Walters <[email protected]> wrote:

> Hi Robin,
>
> Which installer did you use? What was your impression of the installers?
> I think the version X.0 's tend to be the most "fun filled" :)
>
> I want to do an install soon, but have to look at some hardware issues
> first. As soon as I can acquire
> some spare time. From the sound of things, I think acing my data backup
> will lead to a more auspicious
> adventure.
>
> Mel
>
>
>
> On Tue, Feb 8, 2011 at 7:10 AM, Richard Carter <[email protected]>wrote:
>
>> Thanks for all the help.  Last night I took the bit in my teeth and did a
>> fresh install of debian 6.0.0 amd6.  KDE now starts ok but I still have some
>> fine tuning to do.
>>
>> Robin
>>
>>
>> On Mon, Feb 7, 2011 at 8:10 PM, Rick Johnson <[email protected]> wrote:
>>
>>> and... according to the specs on that mobo, you have a Radeon HD 4250
>>> which should work just fine with the xorg-radeon driver. Its included with
>>> Debian so there's no need to mess with the proprietary stuff.
>>>
>>>
>>> On Mon, Feb 7, 2011 at 3:15 PM, Rick Johnson <[email protected]>wrote:
>>>
>>>> Ok, thats weird. startx should be there as long as xorg is installed.
>>>> Anyways, lets go with the original problem... $DISPLAY is an environment
>>>> variable which you should not need to deal with unless the upgrade mussed 
>>>> up
>>>> some of the config somewhere. Try this: log in as your normal user and 'mv
>>>> ~/.xinitrc ~/.xinitrc.old' and 'mv ~/.xsession  ~/.xsession.old'. This will
>>>> get these files out of the way for the time being (and back them up if case
>>>> we need to put them back) and hopefully, kde can now start and create new
>>>> versions of them. Kaboom is a migration wizard to go from kde3 to kde4 and 
>>>> i
>>>> suspect it may have caused the problem.
>>>>
>>>> On Mon, Feb 7, 2011 at 12:01 PM, Richard Carter <[email protected]
>>>> > wrote:
>>>>
>>>>>
>>>>> Thanks for the tips.  I have tried "startx" but got "command not
>>>>> found".  The version of debian testing I'm using is amd64.  I believe the
>>>>> video card is embodied in the motherboard; Gigabyte GA880-GM-UD2H.
>>>>>
>>>>> Robin
>>>>>
>>>>>
>>>>> On Mon, Feb 7, 2011 at 1:29 PM, Rick Johnson <[email protected]>wrote:
>>>>>
>>>>>> and btw, i also am using testing and ran a dist-upgrade last night.
>>>>>> Xorg was upgraded so i had to re-do the nvidia drivers. very likely this 
>>>>>> is
>>>>>> your problem.
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 7, 2011 at 11:16 AM, Rick Johnson <[email protected]>wrote:
>>>>>>
>>>>>>> Btw, i see you're running a 64-bit processor but are you also running
>>>>>>> 64-bit Debian? Here's some instructions for building the nvidia driver:
>>>>>>> http://wiki.debian.org/NvidiaGraphicsDrivers If i remember right,
>>>>>>> there's some differences with the 64-bit procedure which you'll have to
>>>>>>> google if thats what you need.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Feb 7, 2011 at 11:07 AM, Rick Johnson 
>>>>>>> <[email protected]>wrote:
>>>>>>>
>>>>>>>> The kernel headers are required to re-compile the kernel module but
>>>>>>>> but in the upgrade, only the source packages are upgraded. you still 
>>>>>>>> need to
>>>>>>>> go through the process of building the module.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Feb 7, 2011 at 10:58 AM, Joseph Hume 
>>>>>>>> <[email protected]>wrote:
>>>>>>>>
>>>>>>>>>  On my daughters Kubuntu 10.10 laptop if there is a kernel update
>>>>>>>>> I just need to install the matching kernel headers to allow the
>>>>>>>>> nvidia video driver to properly install before I reboot.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 2/7/2011 9:35 AM, Rick Johnson wrote:
>>>>>>>>>
>>>>>>>>> did you try 'startx'? And btw, upgrades or dist-upgrades should be
>>>>>>>>> done without kde running (or gnome etc.). '/etc/init.d/kdm stop', log 
>>>>>>>>> in as
>>>>>>>>> root and then 'apt-get update && apt-get dist-upgrade'. Otherwise you 
>>>>>>>>> are
>>>>>>>>> going to upgrade packages that are running at the time and you can 
>>>>>>>>> often
>>>>>>>>> break things this way. Also, if you are using a ATI or nvidia card 
>>>>>>>>> with
>>>>>>>>> proprietary drivers, you will need to re-install the driver if X or 
>>>>>>>>> the
>>>>>>>>> kernel is upgraded.
>>>>>>>>>
>>>>>>>>> On Mon, Feb 7, 2011 at 10:17 AM, Richard Carter <
>>>>>>>>> [email protected]> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Folks,
>>>>>>>>>>
>>>>>>>>>>  I have been running debian 6.0 testing on a desktop with an
>>>>>>>>>> amd64 processor.  Before shutting down last night I used synaptic to 
>>>>>>>>>> check
>>>>>>>>>> for and install upgrades: many were installed.
>>>>>>>>>>
>>>>>>>>>>  This morning kde won't start.  When I boot the system goes into
>>>>>>>>>> what I interpret as "terminal mode".  When I type in "startkde" as 
>>>>>>>>>> user I
>>>>>>>>>> get "DISPLAY is not set or cannot to the X server".  When I type 
>>>>>>>>>> "startkde"
>>>>>>>>>> as su I get:
>>>>>>>>>> ------ Kaboom Settings Dump------
>>>>>>>>>>   kdehome - "/root/.kde" - exists? YES
>>>>>>>>>>   kde4 - "/root/kde4" - exists? NO
>>>>>>>>>>   kdebackup - "/root/kde3-backup" exists? NO
>>>>>>>>>>   kdestamp = "/root/.local/kaboom" exists? NO
>>>>>>>>>>   kaboom log - "/root/.kaboom.log"
>>>>>>>>>> ---------------------------------------------------
>>>>>>>>>> kaboom cannot connect to X server
>>>>>>>>>>
>>>>>>>>>>  I tried using apt-get to install kde but was told the newest
>>>>>>>>>> version was all ready installed.
>>>>>>>>>>
>>>>>>>>>>  Fortunately I already have a recent backup.  I have downloaded
>>>>>>>>>> debian 6.0.0-amd64-i386-netinst.iso and I'm considering 
>>>>>>>>>> re-installing.  Does
>>>>>>>>>> anyone have a better idea?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> clug-talk mailing list
>>>>>>>>>> [email protected]
>>>>>>>>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>>>>>>>>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>>>>>>>>>> **Please remove these lines when replying
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> clug-talk mailing 
>>>>>>>>> [email protected]http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>>>>>>>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>>>>>>>>> **Please remove these lines when replying
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> clug-talk mailing list
>>>>>>>>> [email protected]
>>>>>>>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>>>>>>>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>>>>>>>>> **Please remove these lines when replying
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> clug-talk mailing list
>>>>>> [email protected]
>>>>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>>>>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>>>>>> **Please remove these lines when replying
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> clug-talk mailing list
>>>>> [email protected]
>>>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>>>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>>>>> **Please remove these lines when replying
>>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> clug-talk mailing list
>>> [email protected]
>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>>> **Please remove these lines when replying
>>>
>>
>>
>> _______________________________________________
>> clug-talk mailing list
>> [email protected]
>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
>> **Please remove these lines when replying
>>
>
>
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to