Resp.: Resp.: can't start xorg or HAL
LOL, it's good to know that I'm not the only one who feels that way
about xorg *Gnashes teeth*
I was going to simply copy the relevant sections from Debian Sid over
to kfreebsd. Easier said than done though- my Sid has read-only on UFS
partitions, so I might have to re-write xorg.conf by hand. I'll keep
you up-to-date.
2008/11/2, John Knight <jknight@geminimicro.com>:
> Robert Hayes wrote:
>>
>> it gives messages about "no screens found." I'm thinking that maybe it
>> has something to do with
>> "dpkg-reconfigure xserver-xorg". It finishes after the keyboard
>> (NOTHING about anything else), and invariably gives me this as the
>> /etc/X11/xorg.conf (I tried several times):
>>
>> Section "InputDevice"
>> Identifier "Generic Keyboard"
>> Driver "kbd"
>> Option "XkbRules" "xorg"
>> Option "XkbModel" "abnt"
>> Option "XkbLayout" "br"
>> Option "XkbVariant" "abnt"
>> Option "XkbOptions" "br"
>> EndSection
>>
>> Section "InputDevice"
>> Identifier "Configured Mouse"
>> Driver "mouse"
>> EndSection
>>
>> Section "Device"
>> Identifier "Configured Video Device"
>> EndSection
>>
>> Section "Monitor"
>> Identifier "Configured Monitor"
>> EndSection
>>
>> Section "Screen"
>> Identifier "Default Screen"
>> Monitor "Configured Monitor"
>> EndSection
>>
>> could the inability to start HAL have something to do with it- at the
>> end of the boot I get messages
>> that I need to check if "inotify" is enabled in the kernel?
>>
>> 2008/11/2, John Knight <jknight@geminimicro.com>:
>>
>>>
>>> Robert Hayes wrote:
>>>
>>>>
>>>> Like the title says :(
>>>> I installed Debian GNU/kfreebsd amd64, and the only problem was my own
>>>> fault (I didn't remember to configure my network connection). But now
>>>> I can't start xorg (even dpkg-reconfigure-xorg stops after the
>>>> keyboard). During boot I get the message that HAL can't initialize.
>>>> Maybe the two are connected? apt-get says everything is installed
>>>> correctly (or at least xorg, dbus, and hal).
>>>>
>>>>
>>>>
>>>>
>>>
>>> what messages do you get when trying to run '$ startx' ?
>>>
>>> --
>>>
>>> John Knight
>>> phone: +1 706 255-9203
>>> e-mail: jknight@geminimicro.com
>>> website: geminimicro.com
>>>
>>
>>
>
> pretty strange. I've used Debian and Salgix for most computing needs and
> I've managed to break hal during updates and package testing, but the x
> server never had any issues because of it.
>
> I really hate these later versions of xorg that are "configured" for you.
> They seem anything but in my experience.
>
> for the video card, you're going to have best luck using the vesa driver to
> get a frame buffered display up and going (kind of crappy, but it will get a
> gui up one way or the other).
>
> to try and enable the driver, replace the "Device" section of your xorg.conf
> file with the following:
>
> Section "Device"
> Identifier "Configured Video Device"
> Busid "PCI:0:3:0"
> Driver "vesa"
> Screen 0
> EndSection
>
> From our previous discussions, I seem to remember you having debian
> installed on the same machine. I would cat debian's /etc/X11/xorg.conf out
> and perhaps grep "Busid" to see your specific bus settings (mine were
> PCI:0:3:0, but you need to be very specific with your hardware) and then
> change them in the above "Device" section config data.
>
> --
>
> John Knight
> phone: +1 706 255-9203
> e-mail: jknight@geminimicro.com
> website: geminimicro.com
Reply to: