Huston i have a big problem

[Goh Lip]

karl.vanwynsberghe at telenet.be wrote:
>> ----- Oorspronkelijk bericht -----
>> Van
> : Goh Lip [mailto:g.lip at gmx.com]
>> Verzonden
> : donderdag
> , september
>  17, 2009 05:36 AM
>> Aan
> : kubuntu-users at lists.ubuntu.com
>> Onderwerp
> : Re: Huston i have a big problem
>> karl.vanwynsberghe at telenet.be wrote:
>>> Hi to all,
>>>
>>> Problems part 2...
>>> I've mailed about my problems with no X after the kubuntu splash.
>>> Today i booted in to recovery with netroot, did an apt-get update and dist-upgrade. And i could boot again and start working...
>>>
>>> After a while...new updates installed... and then when rebooting;
>>>
>>> Damn!
>>> a lot of errors; some of them...
>>> -udev[362] inotify_add_watch (6, (null), 10) failed bad address.
>>> -udev[362] =name="%K" in superflious and breaks kernel supplied names...
>>> -Somthing about a wrong bios for acer...
>>> -system with errors check forced
>>>
>>> But i even can't get a console to do something
>>>
>>>
>>> HELP!
>>>
>>>
>>>
>> If,  after fsck, and you still have same problem,
>> go to /lib/udev/rules.d/40-ppcrules,
>> comment out the lines where you find
>>
>> KERNEL NAME=%k
>> reboot.
>>
> 
> Hi,
> 
> Update...
> I've done the e2fsck -fv for my /dev/sda5 and /dev/sda6.
> No faults detected...
> Changed the /lib/udev/rules.d/40-ppcrules file and rebooted...
> Result: F*...
> Faults like 
> ==>/lib/udev/rules.d/50-udev-default.rules:3
> ==>/lib/udev/rules.d/50-udev-default.rules:4
> ==>acerhdf: unknown (unsupported) Bios version Acer/Aspire 6920/v1.07, please report, aborting!
> ==>/dev/sda5 contains a file system with errors, check forced
> ==>/dev/sda6 contains a file system with errors, check forced
> 
> 
> What to do next?



Okay, good news, you don't have the

-udev[362] inotify_add_watch (6, (null), 10) failed bad address. 
-udev[362] =name="%K" in superflious and breaks kernel supplied names...

errors anymore.


Now, go to /lib/udev/rules.d/50-udev-default.rules

  press F11, at lines 3 and 4, do you see

SUBSYSTEM=="block", SYMLINK{unique}+="block/%M:%m"
SUBSYSTEM!="block", SYMLINK{unique}+="char/%M:%m"

comment out to

#SUBSYSTEM=="block", SYMLINK{unique}+="block/%M:%m"
#SUBSYSTEM!="block", SYMLINK{unique}+="char/%M:%m"

reboot.

Karl, are the above the ONLY reported errors left?
In your first message, you did not mention these errors, (though you 
mentioned 'lots of errors').

If these are the only errors left, I think you should be in the clear.
(however, karmic, being alpha, may bring more surprises with newer 
updates). BTW, I am still on Karmic, and had gone through what you went 
through.

good luck

Goh Lip