Hello,
On Sat, Jan 23, 2010 at 8:21 AM, N James Bridge wrote:
> On Fri, 2010-01-22 at 15:38 -0500, Oliver Ruebenacker wrote:
>> Hello,
>>
>> On Fri, Jan 22, 2010 at 5:30 AM, N James Bridge
>> wrote:
>> > On Thu, 2010-01-21 at 15:34 -0500, Oliver Ruebenacker wrote:
>> >> Hello,
>> >>
>> >>
On Thursday 28 January 2010 10:38:24 Harald Hoyer wrote:
> On 01/28/2010 11:34 AM, Tony Molloy wrote:
> > On Thursday 28 January 2010 09:45:44 Harald Hoyer wrote:
> >> On 01/28/2010 10:36 AM, Tony Molloy wrote:
> >>> On Thursday 28 January 2010 09:07:13 Harald Hoyer wrote:
> On Fri, Jan 22, 20
On 01/28/2010 11:34 AM, Tony Molloy wrote:
> On Thursday 28 January 2010 09:45:44 Harald Hoyer wrote:
>> On 01/28/2010 10:36 AM, Tony Molloy wrote:
>>> On Thursday 28 January 2010 09:07:13 Harald Hoyer wrote:
On Fri, Jan 22, 2010 at 9:36 AM, Tony Molloy wrote:
> When I boot I get as far
On Thursday 28 January 2010 09:45:44 Harald Hoyer wrote:
> On 01/28/2010 10:36 AM, Tony Molloy wrote:
> > On Thursday 28 January 2010 09:07:13 Harald Hoyer wrote:
> >> On Fri, Jan 22, 2010 at 9:36 AM, Tony Molloy wrote:
> >>> When I boot I get as far as the cursor flashing on the top left hand
> >
On 01/28/2010 10:36 AM, Tony Molloy wrote:
> On Thursday 28 January 2010 09:07:13 Harald Hoyer wrote:
>> On Fri, Jan 22, 2010 at 9:36 AM, Tony Molloy wrote:
>>> When I boot I get as far as the cursor flashing on the top left hand
>>> corner of the screen and then the following error.
>>>
>>> Trace
On Thursday 28 January 2010 09:07:13 Harald Hoyer wrote:
> On Fri, Jan 22, 2010 at 9:36 AM, Tony Molloy wrote:
> > When I boot I get as far as the cursor flashing on the top left hand
> > corner of the screen and then the following error.
> >
> > Traceback (most recent call last):
> > File ""/init
On Fri, Jan 22, 2010 at 9:36 AM, Tony Molloy wrote:
> When I boot I get as far as the cursor flashing on the top left hand corner of
> the screen and then the following error.
>
> Traceback (most recent call last):
> File ""/init", line 157 in
> if __name__=='__main__': main()
> File "/init",line
>>> When a few weeks ago the new auto-updated kernel would not boot,
>>> used an older kernel, waiting for the next update. This was today, and
>>> now the two latest kernels don't work. Booting stops after the Fedora
>>> logo fills up white, after which it says (copying manually from
>>> scree
>>> When a few weeks ago the new auto-updated kernel would not boot,
>>> used an older kernel, waiting for the next update. This was today, and
>>> now the two latest kernels don't work. Booting stops after the Fedora
>>> logo fills up white, after which it says (copying manually from
>>> screen,
On Fri, 2010-01-22 at 15:38 -0500, Oliver Ruebenacker wrote:
> Hello,
>
> On Fri, Jan 22, 2010 at 5:30 AM, N James Bridge
> wrote:
> > On Thu, 2010-01-21 at 15:34 -0500, Oliver Ruebenacker wrote:
> >> Hello,
> >>
> >> When a few weeks ago the new auto-updated kernel would not boot,
> >> used a
Hello,
On Fri, Jan 22, 2010 at 5:30 AM, N James Bridge wrote:
> On Thu, 2010-01-21 at 15:34 -0500, Oliver Ruebenacker wrote:
>> Hello,
>>
>> When a few weeks ago the new auto-updated kernel would not boot,
>> used an older kernel, waiting for the next update. This was today, and
>> now the
Hello,
On Thu, Jan 21, 2010 at 8:29 PM, Tom H wrote:
>> When a few weeks ago the new auto-updated kernel would not boot,
>> used an older kernel, waiting for the next update. This was today, and
>> now the two latest kernels don't work. Booting stops after the Fedora
>> logo fills up white,
On Thu, 2010-01-21 at 15:34 -0500, Oliver Ruebenacker wrote:
> Hello,
>
> When a few weeks ago the new auto-updated kernel would not boot,
> used an older kernel, waiting for the next update. This was today, and
> now the two latest kernels don't work. Booting stops after the Fedora
> logo fills
On Thursday 21 January 2010 20:34:01 Oliver Ruebenacker wrote:
> Hello,
>
> When a few weeks ago the new auto-updated kernel would not boot,
> used an older kernel, waiting for the next update. This was today, and
> now the two latest kernels don't work. Booting stops after the Fedora
> log
On Thursday 21 January 2010 20:38:25 Oliver Ruebenacker wrote:
> Hello,
>
> Sorry, attached grub.conf was missing (GMail simply ignored it after
> it could not read it as a normal user). Here it should be.
>
> Take care
> Oliver
>
> On Thu, Jan 21, 2010 at 3:34 PM, Oliver Rueben
> When a few weeks ago the new auto-updated kernel would not boot,
> used an older kernel, waiting for the next update. This was today, and
> now the two latest kernels don't work. Booting stops after the Fedora
> logo fills up white, after which it says (copying manually from
> screen, whitespace
Hello,
Sorry, attached grub.conf was missing (GMail simply ignored it after
it could not read it as a normal user). Here it should be.
Take care
Oliver
On Thu, Jan 21, 2010 at 3:34 PM, Oliver Ruebenacker wrote:
> Hello,
>
> When a few weeks ago the new auto-updated kernel
17 matches
Mail list logo
