xdevent wrote:
> Ok, so i thing that my problem is a diferent thing instead of kernel.
> Probably some hard disk problem, or something... I will reinstall hardy
> at its final vrsion.
>
> I have no inconvenient, if you want, to change the bug state to fix. But
> i want sam to say if he want or not,
Hardy alpha 3 works for me, no sign of hanging at all, so
Also the upgrade failed and left me stuck on "waiting for root file
system" so I had to fresh-install and I no longer have gutsy to test.
However I am happy for this to be marked as solved in hardy.
I'll make a similar comment on the
Thanks.
I'll get to try hardy this weekend.
I posted more details on the upstream bug.
Sam
-Original Message-
From: Paul Dufresne <[EMAIL PROTECTED]>
Sent: 10 January 2008 06:36
To: [EMAIL PROTECTED]
Subject: [Bug 144030] Re: Gutsy beta hang soon after boot
>> ** Changed in: linux (Ubu
Thanks Leann
The guy who said to try hardy since reported it does hang but takes longer.
I hoe to install hardy this weekend.
Sam
-Original Message-
From: Leann Ogasawara <[EMAIL PROTECTED]>
Sent: 09 January 2008 21:59
To: [EMAIL PROTECTED]
Subject: [Bug 144030] Re: Gutsy beta hang soon
Paul Dufresne wrote:
> ** Also affects: linux (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
>
What is incomplete about this? What more information do you need?
--
Gutsy beta hang soon after boot
https://bugs.laun
Len Brown wrote:
> If you want this fixed,
> please reply to the request for information in the upstream bug report:
> http://bugzilla.kernel.org/show_bug.cgi?id=7598
>
>
Thanks for the tip; doing so now.
I didn't see/get responses from the upstream report, so thanks for
pointing it out.
Sam
Live Hardy CD works for me, thanks for the tip.
I'll try installing the hardy kernel and modules on gutsy and report
back.
Sam
-Original Message-
From: xdevent <[EMAIL PROTECTED]>
Sent: 02 January 2008 23:29
To: [EMAIL PROTECTED]
Subject: [Bug 144030] Re: Gutsy beta hang soon after boot
If you still have gutsy installed, append
init=/bin/bash
to the kernel boot entry (and change the ro to rw)
and then when it boots
mv /lib/modules/`uname -r`/kernel/drivers/acpi /lib/modules/acip.`uname -r`
sync
reboot
and that should sort it for the time being. You may have to do that at
each
No.
That is to say, if I prevent processor.ko from loading, all is well but that
means no cpu scaling, etc.
I'm about to test adding processor.ko to the module blacklist (wherever
that is) which will stop me having to remove processor.ko each time the
kernel is updated.
Sam
-Original Messag
