Apparently, though unproven, at 17:54 on Wednesday 05 January 2011, Peter
Humphrey did opine thusly:
> On Wednesday 05 January 2011 15:32:29 Alan McKinnon wrote:
> > Now we need to figure out *why* it was causing your problems
>
> I could just hand it over to the devs via a bug report, but I oug
On Wednesday 05 January 2011 15:32:29 Alan McKinnon wrote:
> Now we need to figure out *why* it was causing your problems
I could just hand it over to the devs via a bug report, but I ought to
do some detective work first, if only to decide which subsystem to log it
against.
The trouble with t
Apparently, though unproven, at 16:44 on Wednesday 05 January 2011, Peter
Humphrey did opine thusly:
> On Wednesday 05 January 2011 12:43:43 Peter Humphrey wrote:
> > These are the only values set in [/etc/rc.conf]; everything else is
> > comment:
> > rc_interactive="YES"
> > rc_shell=/sbin/sulog
On Wednesday 05 January 2011 12:43:43 Peter Humphrey wrote:
> These are the only values set in [/etc/rc.conf]; everything else is
> comment:
> rc_interactive="YES"
> rc_shell=/sbin/sulogin
> rc_hotplug="!*"
> rc_logger="YES"
> rc_start_wait=100
> unicode="YES"
> rc_tty_number=12
[...]
> Hmm. I'm w
On Tuesday 04 January 2011 21:51:37 Alan McKinnon wrote:
> Do you have
>
> rc_parallel="YES"
>
> in /etc/rc.conf?
Nope. These are the only values set in that file; everything else is
comment:
rc_interactive="YES"
rc_shell=/sbin/sulogin
rc_hotplug="!*"
rc_logger="YES"
rc_start_wait=100
unicode=
Apparently, though unproven, at 12:50 on Tuesday 04 January 2011, Peter
Humphrey did opine thusly:
> On Monday 03 January 2011 14:40:41 walt wrote:
> > I'm wondering if you have some mixture of baselayout versions on that
> > machine from previous updates.
>
> Unlikely: this box has been ~amd64
On 01/04/2011 02:50 AM, Peter Humphrey wrote:
On Monday 03 January 2011 14:40:41 walt wrote:
I'm wondering if you have some mixture of baselayout versions on that
machine from previous updates.
Unlikely: this box has been ~amd64 since before it had a complete
system.
Could your machine be t
On Monday 03 January 2011 14:40:41 walt wrote:
> I'm wondering if you have some mixture of baselayout versions on that
> machine from previous updates.
Unlikely: this box has been ~amd64 since before it had a complete
system.
> Could your machine be trying to start something other than kdm by
>
On 01/03/2011 02:11 AM, Peter Humphrey wrote:
On Sunday 02 January 2011 15:51:24 walt wrote:
On 01/02/2011 03:51 AM, Peter Humphrey wrote:
It looks as though the boot sequence is going wrong somehow,
because when I get my initial blank screen, if I then switch to a
VT and restart xdm, everythin
On Sunday 02 January 2011 15:51:24 walt wrote:
> On 01/02/2011 03:51 AM, Peter Humphrey wrote:
> > It looks as though the boot sequence is going wrong somehow,
> > because when I get my initial blank screen, if I then switch to a
> > VT and restart xdm, everything works as expected.
>
> Just for c
On 01/02/2011 03:51 AM, Peter Humphrey wrote:
On Friday 31 December 2010 12:52:08 Peter Humphrey wrote:
When I start the system, instead of the kdm login screen I get a
blinking cursor in the top-[left] of a blank screen. An emerge of
nvidia-drivers enables me to restart kdm and get a proper sc
On Saturday 01 January 2011 20:26:11 Alan McKinnon wrote:
> Apparently, though unproven, at 12:36 on Saturday 01 January 2011,
> Peter Humphrey did opine thusly:
> > Something is messing about with the nVidia module.
>
> That's how module-rebuild works, it's not broken. It *will* rebuild
> everyth
Apparently, though unproven, at 12:36 on Saturday 01 January 2011, Peter
Humphrey did opine thusly:
> On Friday 31 December 2010 21:00:57 Alan McKinnon wrote:
> > Apparently, though unproven, at 20:54 on Friday 31 December 2010,
> >
> > walt did opine thusly:
> > > So, if you've ever run the NVI
On Friday 31 December 2010 21:00:57 Alan McKinnon wrote:
> Apparently, though unproven, at 20:54 on Friday 31 December 2010,
> walt did opine thusly:
> > So, if you've ever run the NVIDIA install program manually, you
> > probably have two different nvidia.ko files in /lib/modules, and
> > the wron
Apparently, though unproven, at 20:54 on Friday 31 December 2010, walt did
opine thusly:
> On 12/31/2010 04:52 AM, Peter Humphrey wrote:
> > This is weird. When I start the system, instead of the kdm login screen
> > I get a blinking cursor in the top-right of a blank screen. An emerge of
> > nvi
On 12/31/2010 04:52 AM, Peter Humphrey wrote:
This is weird. When I start the system, instead of the kdm login screen
I get a blinking cursor in the top-right of a blank screen. An emerge of
nvidia-drivers enables me to restart kdm and get a proper screen. This
is in spite of not having been ab
16 matches
Mail list logo
