[Bug 24029] Re: HAL Fails to initilize at startup

2006-12-18 Thread qburn
Thank you for help , kernel 2.6.19 seems to solve the problem , however my poor linux skills did not let me install in it porperly he he ... so system starts 8 min and there is no network interfaces, however hald runs ... have you installed something more than kernel image and restricted

Re: [Bug 24029] Re: HAL Fails to initilize at startup

2006-12-18 Thread petersalo
No that was all, there were a few additional dependencies when upgrading the kernel (I chose the linux-image-generic package) - such as libc etc. But they should be automatic if you choose the generic package. On Monday 18 December 2006 10:19, qburn wrote: Thank you for help , kernel 2.6.19

[Bug 24029] Re: HAL Fails to initilize at startup

2006-12-16 Thread qburn
Here the same problem , upgrade to 6.10 , and HAl fail to initilaize at startup , dbus is running , it dies with : 00:08:53.544 [I] hald.c:82: Added device to GDL; udi=/org/freedesktop/Hal/devices/platform_serial8250 00:08:53.544 [I] hotplug.c:205: /sys/class/tty/ttyS53 is a class device

Re: [Bug 24029] Re: HAL Fails to initilize at startup

2006-12-16 Thread petersalo
I added the feisty repositories to my sources.list and installed the kernel-image + dependencies (restricted-modules) only. The 2.6.19 kernel seems to fix this issue.. On Sunday 17 December 2006 00:10, qburn wrote: Here the same problem , upgrade to 6.10 , and HAl fail to initilaize at

[Bug 24029] Re: HAL Fails to initilize at startup

2006-12-13 Thread demagogue
I'm running a desktop, so that laptop thing doesn't apply. -- HAL Fails to initilize at startup https://launchpad.net/bugs/24029 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 24029] Re: HAL Fails to initilize at startup

2006-12-12 Thread Martin Pitt
Closing unrelated edgy task. ** Changed in: hal (Ubuntu Edgy) Status: Unconfirmed = Rejected -- HAL Fails to initilize at startup https://launchpad.net/bugs/24029 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 24029] Re: HAL Fails to initilize at startup

2006-12-12 Thread demagogue
I'm having the same problem and I have no idea where to begin with starting to try to fix it. -- HAL Fails to initilize at startup https://launchpad.net/bugs/24029 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 24029] Re: HAL Fails to initilize at startup

2006-12-12 Thread petersalo
Hi, I'm not experienced in kernel module programming - but I know this used to work on 6.06 (Dapper). I've heard that it's probably fixed in a later kernel than the one used in EDGY today. Without going into any code, I've found that this only happens when my laptop is powered - and also

[Bug 24029] Re: HAL Fails to initilize at startup

2006-11-19 Thread petersalo
I have a ASUS A6KM (AMD64) laptop and what I have noticed is that if I don't plug in the AC adapter, HAL seems to work, and I don't get this message. I can also run commands such as lshal. However when I plug in the AC adapter, or if I boot with the AC adapter, I'll get this message Failed to

[Bug 24029] Re: HAL Fails to initilize at startup

2006-11-03 Thread encompass
I know what I did before getting this error... I was fiddling with the services-admin program... After click on, if I remember, the printer servers, it stalled for a moment and killed on me. I then got this... When I try to start the services-admin again... I have tried running it at sudo and

[Bug 24029] Re: HAL Fails to initilize at startup

2006-11-03 Thread encompass
And as with other posts here... I get the no hal now too... I am not upgrading... this is a fairly clean install. -- HAL Fails to initilize at startup https://launchpad.net/bugs/24029 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com

[Bug 24029] Re: HAL Fails to initilize at startup

2006-11-03 Thread encompass
Think I fixed it... had to do with the dbus... some how it got unchecked and gnome and other what nots in ubuntu couldn't handle the situation without paniking. (I guess I would freak too if I lost one of my vitals, like an arm or leg :P ) Anyway, started up the service manually... you know