Пользователей онлайн: 465 - Вход  » Поиск  » Индекс форума  

the HAL problem

burninbush
wrote 2 years ago


reply
Can somebody tell me how to fix this? I insert a usbstick, KDE notices it, I respond to open a new window, which comes up empty, and an error box saying 'feature only available with HAL". Think it must be the same for cd and dvd disks.

I have heard somewhere this is due to root user not being part of some groups????

Anyway, this is annoying -- feature works fine in Slack12 and Vector.

FWIW, I see the message during bootup that hal is being loaded as a daemon, but it doesn't stay loaded for whatever reason. A ps -A on Vector shows 9 hald items running.
 
Tomas M
wrote 2 years ago


reply
I heard about this problem many times, but I was never able to reproduce it. It simply works for me all the time. hald should be still running. Would you please try to search in /var/log/* to find out if there are any message why was hald ended?

I am unable to fix this because it doesn't fail on my computer.
 
gusterrapolis
wrote 2 years ago


reply
For me this is working:

Follow this instructions if you have problems with HAL.

HAL is not properly configured over slax6 and can cause problems in certain cases with some mediums like SD or card flash-readers...?

1) Make a module with a folder /media (/media folder is on slackware12 structure)
It,s neccesary to HAL work properly
add in /etc/group user root to groups: Looks like:

root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin,adm
adm::4:root,adm,daemon
tty::5:
disk::6:root,adm
lp::7:lp
mem::8:
kmem::9:
wheel::10:root
floppy::11:root
mail::12:mail
news::13:news
uucp::14:uucp
man::15:
audio::17:
video::18:root
cdrom::19:
games::20:
slocate::21:
utmp::22:
smmsp::25:smmsp
mysql::27:
rpc::32:
sshd::33:sshd
gdm::42:
shadow::43:
ftp::50:
apache:x:80:
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root
pop::90:pop
scanner::93:
nobody::98:nobody
nogroup::99:
users::100:
console::101:

---------
Estructure module is this:

/etc/group
/media

Close your module and put it in /base rename it to 022_HAL_fix.lzm for example.

reboot

:)

--------------
You need edit your /etc/group and add user root to this groups like this:

video::18:root
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root

1) Make a module with a folder /media
It,s neccesary to HAL work properly
add in /etc/group user root to groups:

video::18:root
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root


Estructure module is this:

/etc/group
/media

Close your module and put it in /base rename it to 022_HAL_fix.lzm for example.

reboot

---------
Anyway,someone tells that do all below and don,t work for him,but for me is working.
 
burninbush
wrote 2 years ago


reply
Tomas ... sorry, no mention of 'hal' in any file in /var/log/*

However -- playing with hald, I decided to try invoking it with the added "--retain-privileges" parm, and lo, the problem is gone. It stays loaded, ps -A |grep hal shows

root@slax:~# ps -A |grep hal
8050 ? 00:00:00 hald
8051 ? 00:00:00 hald-runner
8056 ? 00:00:00 hald-addon-inpu
8079 ? 00:00:00 hald-addon-stor
8081 ? 00:00:00 hald-addon-stor
8300 ? 00:00:00 hald-addon-stor
root@slax:~#

and, FWIW, /etc/group on my machine has only one line of text ...

root@slax:~# cat /etc/group
slocate::21:
root@slax:~#

and that one line is likely due to my addition of a homebuilt slocate.lzm module. [got slocate.tgz, installed to a temp dir, and ran dir2lzm on that]
 
jcsoh
wrote 2 years ago


reply
burninbush posted "Can somebody tell me how to fix this? I insert a usbstick, KDE notices it, I respond to open a new window, which comes up empty, and an error box saying 'feature only available with HAL"

Tomas posted "I heard about this problem many times, but I was never able to reproduce it. It simply works for me all the time".

Maybe it a hardware "thing" cos it happen to me every time ('feature only available with HAL) . I just close the box & use Krusader.
 
Tomas M
wrote 2 years ago


reply
Does the suggestion from burninbush help you, jcosh?
 
jcsoh
wrote 2 years ago


reply
Sorry Tomas , I subscribed to "Catworld's " linux philosolpy of "Hey , I can live with that!!!" meaning in spite of HAL "conkyness "( a word used by "Catworld") with poping a "media found window" follow by " feature only available with HAl" every time a removeable media (usb , cd etc) is found , .....I no longer see this as a problem.

Let the window pop open, just close it , I have no problem using Krusader (menu - tool, mountman) to access the media afterward .
It may not solved the hidden problem but at the same time it doesn't create any problem either (for me at least) , unless you want to count the "media found window as a nuisance".

Anyway , to answer your answer , Tomas , I won't be trying any of the fixes above ...heh heh since in my eye I see no problem as far as "Hey , I can live with that" is concerned ....

p.s For those who don't understand basically " "Hey , I can live with that!!!" " approach to Linux means , if you are going to use Linux , expect to make some compromise . If things work well enough for you to say ""Hey , I can live with that!!!" ...then live with it!!

For eg printing work for me in slax6rc 6 . It's good enough , provided I don't compare with the printing speed under the native driver with win xp. So I live with it.... :)
 
pheil
wrote 2 years ago


reply
I tried gusterrapolis' suggestion, but it did not work for me.

http://www.slax.org/forum.php?action=view&parentID=1048&highlight=hal

-PaulH
 
pheil
wrote 2 years ago


reply
I have one hald error in my /var/logI heard about this problem many times, but I was never able to reproduce it. It simply works for me all the time. hald should be still running. Would you please try to search in /var/log/* to find out if there are any message why was hald ended?

I am unable to fix this because it doesn't fail on my computer.


I have one hald error (in syslog):

Feb 25 12:30:52 (none) hald[5032]: 12:30:52.017 [E] hald_dbus.c:5578: dbus_bus_get(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, or the network connection was broken.
 
gusterrapolis
wrote 2 years ago


reply
Now I remember that in the past when I used syslinux.cfg with slaxsave.dat parameter, HAL give me a lot of problems (over slaxRC5 or RC6).I never used slaxsave.dat and I deleted it from syslinux.cfg and HAL works OK.

This is my syslinux.cfg default entrie:

LABEL SLAX-6-fglrx *** TESTING *** sda9
KERNEL /4vmlinuz vmalloc=256MB from=/mnt/sda9/1slax6
APPEND vga=normal initrd=/4initrd.gz ramdisk_size=6666 root=/dev/ram0 rw noload=zberyl* autoexec=xconf;swapon~/dev/sda8;ldconfig;dvb;kdm

Perhaps this helps!

All people with HAL problems use changes=/slax/slaxsave.dat parameter in isolinux.cfg or syslinux.cfg file?

If yes, try delete it and test over a fresh live cd or usb installation with my below solution.
 
pheil
wrote 2 years ago


reply
This is the entry I am using:


LABEL startx
MENU LABEL My LiveCD SAFE mode
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4 changes=/slax/
 
gusterrapolis
wrote 2 years ago


reply
> pheil

Try this:

LABEL startx
MENU LABEL My LiveCD SAFE mode
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw

--------

You need login and then:

mkdir /media

mcedit /etc/group

and add user root to groups:

video::18:root
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root

Save it with F2 and exit with F10

now type:

init 1 (and wait and login) then type init 3 and wait and push intro to see root# then xconf and kdm

And good luck!
 
burninbush
wrote 2 years ago


reply
Just to add to what I wrote above, I have 'solved' this on both my machines by just editing the line in /etc/rc.d/rc.hald that invokes hald ... to add the --retain-privileges parameter. Now, I'm also using a changes=slax6sav.dat file, so it stays fixed. Did not do anything at all to /etc/groups. Be careful when you edit to not just edit the echo statement, the command is on the next line.

Don't ask me why this works. Cuz I don't know.
 
pheil
wrote 2 years ago


reply
> pheil

Try this:

LABEL startx
MENU LABEL My LiveCD SAFE mode
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw

--------

You need login and then:

mkdir /media

mcedit /etc/group

and add user root to groups:

video::18:root
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root

Save it with F2 and exit with F10

now type:

kdm

And good luck!


Same issue as before...
I notice that my "video" group is slightly different. It reads:
"video:x:18:root"
I've tried it with and without the "x" to no effect. Should that make a difference?

Also, I removed the 003-desktop.lzm and 004-kdeapps.lzm base modules and replaced them with 003-xfce-4.4.2.lzm which I created by compiling the XFCE source. (XFCE runs well, so I don't think I have a problem there.) So instead of "kdm" I use "startxfce4".

If I run "lshal" before starting XFCE, I get the error message:

error: dbus_bus_get: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


Thanks
 
gusterrapolis
wrote 2 years ago


reply
Problem can be solved to people that uses changes=/slax/ by this easy way:

THIS IS WRONG:

LABEL startx
MENU LABEL My LiveCD SAFE mode
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4 changes=/slax/

THIS IS OK:

LABEL startx
MENU LABEL My LiveCD SAFE mode
KERNEL /boot/vmlinuz changes=/slax/
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4

Incredible but true!!!!


----------------------------
ONLY FOR PEOPLE THAT DON,T USE changes=/slax/ AND USE from=/dev/where_you_have _slax

To people that don,t use changes=/slax/ (like mine) solution is a little hard.

Test system with this menu entrie: ADAPT from=/dev/where_you_have _slax to your needs

LABEL startx
MENU LABEL My LiveCD SAFE mode
KERNEL /boot/vmlinuz from=/dev/where_you_have _slax
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw

make login and type mkdir /media

mcedit /etc/group and add user root to groups:

video::18:root
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root

Save it with F2 and exit with F10

now type:

init 1 and wait and login again,then init 3 (click intro for see root#)

xconf and finally kdm

Works!!!?????

If works for you, made a module called HAL_fix for example following this guide and make sure any other module overwrites your configuration.

Guide:

1) Make a module with a folder /media (/media folder is on slackware12 structure)
It,s neccesary to HAL work properly
add in /etc/group user root to groups: Looks like:

root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin,adm
adm::4:root,adm,daemon
tty::5:
disk::6:root,adm
lp::7:lp
mem::8:
kmem::9:
wheel::10:root
floppy::11:root
mail::12:mail
news::13:news
uucp::14:uucp
man::15:
audio::17:
video::18:root
cdrom::19:
games::20:
slocate::21:
utmp::22:
smmsp::25:smmsp
mysql::27:
rpc::32:
sshd::33:sshd
gdm::42:
shadow::43:
ftp::50:
apache:x:80:
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root
pop::90:pop
scanner::93:
nobody::98:nobody
nogroup::99:
users::100:
console::101:

---------
Estructure module is this:

/etc/group
/media

Close your module and put it in /base rename it to 022_HAL_fix.lzm for example.

reboot

:)

People that use changes=/slax/ AND USE from=/dev/where_you_have _slax perhaps the best way:

LABEL startx
MENU LABEL My LiveCD SAFE mode
KERNEL /boot/vmlinuz from=/dev/where_you_have _slax changes=/slax/
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4


????????????
-------------------------

It,s a problem with cheatcodes and behaviour HAL daemon.

:)
 
gusterrapolis
wrote 2 years ago


reply
The right sintaxis is this in all cases:

Adapt to your needs:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

LABEL startx
MENU LABEL Slax Graphics mode (KDE)
KERNEL /boot/vmlinuz from=/dev/where_you_have _slax changes=/slax/slaxsave.dat
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

In my case is working (tested over a fresh livecd in HD) without any fix module this:


LABEL SLAX-6 *** TESTING *** sda5
KERNEL /4vmlinuz vmalloc=256MB from=/mnt/sda5/1slax6 changes=/slax/slaxsave.dat
APPEND vga=normal initrd=/4initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=xconf;kdm

(I don,t use slaxsave.dat but is needed in sintaxis to all work OK)

This works for me and must work to all people.No more is needed.

Sintaxis is very important.

:)
 
Tomas M
wrote 2 years ago


reply
This is impossible. How does the syntax of syslinux's configuration relate to HAL?
 
gusterrapolis
wrote 2 years ago


reply
Is not impossible.

Test enviroment:

Tested over a fresh livecd slax6 (spanish, in /mnt/sda5/1slax6 XFS fylesystem) and booting from fresh livecd and usb-card flash reader with CF Sandisk Extreme III (2Gb) plugged.If I use this:

I don,t use any slaxsave.dat (livecd is fresh,intouched)

Inside /mnt/sda5/1slax6/ is /boot and /slax (fresh,spanish version)

/mnt/sda5/1slax6/slax
/mnt/sda5/1slax6/boot


LABEL startx
MENU LABEL Slax Graphics mode (KDE)
KERNEL /boot/vmlinuz from=/dev/sda5/1slax6
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4 changes=/slax/

SD card is not mounted and when I try to mount kde warning says HAL is not possible mount.

Don,t work and create /images,/changes and /xino folders inside /mnt/sda5/1slax6/slax/.I deleted this folders from another system to test all fresh again!! for reason you see a lines after-->

If I use this: OK

LABEL startx
MENU LABEL Slax Graphics mode (KDE)
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4 changes=/slax/

All is OK but I don,t launch slax from I want.Right?

If I use this:

LABEL startx
MENU LABEL Slax Graphics mode (KDE)
KERNEL /boot/vmlinuz from=/dev/sda5/1slax6 changes=/slax/
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4

Don,t work and create /images,/changes and /xino folders inside /mnt/sda5/1slax6/slax/

!!!!!!!Is very dangerous this,because if someone (like me) delete /images,/changes and /xino when slax is running and reboot,XFS filesystem is broken and only can reparate with other system and xfs_repair -L /dev/sda5!!!!!!!!

Finally:OK

LABEL startx
MENU LABEL Slax Graphics mode (KDE)
KERNEL /boot/vmlinuz from=/dev/sda5/1slax6 changes=slaxsave.dat
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4

All works and HAL mount my flash-card reader and CF inside.Don,t create any /images,/changes and /xino folders inside /mnt/sda5/1slax6/slax/ and I don,t use any slaxsave.dat (I usually use a module with mychanges,in this test not used).

----------------------------------

Changes cheatcode is not properly in slax6.For me is not a problem,because I don,t want use it, but for the most people can cause a lot of problems depending how launch slax from.

The best way for people that don,t want use changes parameter is made a module following my instructions below and not use changes parameter in command line, or the other way is using something like this:

LABEL startx
MENU LABEL Slax Graphics mode (KDE)
KERNEL /boot/vmlinuz from=/dev/sda5/1slax6 changes=slaxsave.dat
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4

but not using any slaxsave.dat.

I,m using my HAL_fix module and booting similar this:

LABEL startx
MENU LABEL Slax Graphics mode (KDE)
KERNEL /boot/vmlinuz from=/dev/sda5/1slax6
APPEND initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=telinit~4

Without any problem,but with my HAL_fix module in /base.

I hope this helps you.

I,ll change my partition sda5 XFS to an EXT3.Ext3 is working with slax better than XFS.I don,t know why!
After problem related below XFS is not good for me.I needed booting another system to repair filesystem XFS,no easy way with slax or slackware.EXT3 repairs atomatically and is very more compatible with any system linux.

----------

Tested over EXT3, and same behaviour with EXT3 filesystem in /mnt/sda5/1slax6/.But I choose now EXT3 for my filesystems,in my opinion is more safe and easy recoverable if something goes wrong.

Last note:

If /mnt/sda5/1slax6/ is in EXT3 filesystem I can,t delete folders /images,/changes and /xino folders inside /mnt/sda5/1slax6/slax/ while slax is running.Konqueror tell me ,that is in use.This not sucedeed with XFS.
 
jcsoh
wrote 2 years ago


reply
" burninbush posted "Can somebody tell me how to fix this? I insert a usbstick, KDE notices it, I respond to open a new window, which comes up empty, and an error box saying 'feature only available with hal"

Tomas posted "I heard about this problem many times, but I was never able to reproduce it. It simply works for me all the time".

Maybe it a hardware "thing" cos it happen to me every time ('feature only available with hal) . I just close the box & use Krusader."

My previous post which was true from the time Tomas use HAL until Slax 6 :

Well Slax 6.01 solved it . Now when I plug in a usb thumbdrive , a removeable media found window pop up as normal , but now I am able to open the window and read the media without a "feature only found in HAL" message.

Now I only need to wait for printing to work. Mean while I will start using slax 6.01 on amother partition while keeping slax 6rc6 since I don't print all the time.
 
arnster86
wrote 2 years ago


reply
burninbush wrote:
Just to add to what I wrote above, I have 'solved' this on both my machines by just editing the line in /etc/rc.d/rc.hald that invokes hald ... to add the --retain-privileges parameter. Now, I'm also using a changes=slax6sav.dat file, so it stays fixed. Did not do anything at all to /etc/groups. Be careful when you edit to not just edit the echo statement, the command is on the next line.

Don't ask me why this works. Cuz I don't know.


I'm kind of new at this and I was trying to edit the file but I'm not exactly sure where to put the "--retain-privileges" thing. Is there any way you could tell me where exactly I need to put it? thanks
 
gusterrapolis
wrote 2 years ago


reply
arnster86 wrote:
burninbush wrote:
Just to add to what I wrote above, I have 'solved' this on both my machines by just editing the line in /etc/rc.d/rc.hald that invokes hald ... to add the --retain-privileges parameter. Now, I'm also using a changes=slax6sav.dat file, so it stays fixed. Did not do anything at all to /etc/groups. Be careful when you edit to not just edit the echo statement, the command is on the next line.

Don't ask me why this works. Cuz I don't know.


I'm kind of new at this and I was trying to edit the file but I'm not exactly sure where to put the "--retain-privileges" thing. Is there any way you could tell me where exactly I need to put it? thanks


Do you have tried this?.It,s working to me:I don,t use changes=/slax/ I use a customized module with my changes.

1) Make a module with a folder /media (/media folder is on slackware12 structure)
It,s neccesary to HAL work properly and
add in /etc/group , user root to groups: Looks like:

root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin,adm
adm::4:root,adm,daemon
tty::5:
disk::6:root,adm
lp::7:lp
mem::8:
kmem::9:
wheel::10:root
floppy::11:root
mail::12:mail
news::13:news
uucp::14:uucp
man::15:
audio::17:
video::18:root
cdrom::19:
games::20:
slocate::21:
utmp::22:
smmsp::25:smmsp
mysql::27:
rpc::32:
sshd::33:sshd
gdm::42:
shadow::43:
ftp::50:
apache:x:80:
messagebus:x:81:root
haldaemon:x:82:root
plugdev:x:83:root
power:x:84:root
pop::90:pop
scanner::93:
nobody::98:nobody
nogroup::99:
users::100:
console::101:

---------
Estructure module is this:

/etc/group
/media

Close your module and put it in /base rename it to 022_HAL_fix.lzm for example.

reboot
 
markds
wrote 2 years ago


reply
The /etc/group on a clean, fresh burn of SLAX should have 41 lines in it, not just 1. I would reckon that your /etc/group having 1 line is the problem no? Your slocate.lzm should be appending to /etc/group, not overwriting it.

burninbush wrote:
and, FWIW, /etc/group on my machine has only one line of text ...

root@slax:~# cat /etc/group
slocate::21:
root@slax:~#

and that one line is likely due to my addition of a homebuilt slocate.lzm module. [got slocate.tgz, installed to a temp dir, and ran dir2lzm on that]
 
IceCub
wrote 2 years ago


reply
I have the same problem with hal, but it only appears on one of the two computers I'm using to run Slax. I run Slax from the same USB flash drive on both computers.

Home computer:
CPU: Core2Duo E4300
MB: Gigabyte GA-965P-DS3
HAL runs without any problems

Notebook:
Fujitsu Siemens Lifebook E8310
CPU: Core2Duo T7300
HAL has some problems running on it.

The differences I've noticed:
- on my home computer all the mounted disk drives appear named after their volume name; on my notebook, the disk drives are named as "Hard Disk (sda1)" or "Hard Disk (sda2)";
- on my home computer any USB flash or CD/DVD inserted is automatically mounted and it's content displayed. On my notebook, any USB flash drive or CD/DVD inserted generates the following error: "Feature only available with HAL". I have to manually mount them from the console so they can be used.
- If I try to run Gparted on by notebook I get the following error: "Could not initialize connection to hald. Normally this means the HAL daemon (hald) is not running or not ready." I have no problems running Gparted on my home computer.
 
forum
wrote 1 year ago


reply
i had hal problem

removed /etc/dbus-1/system.conf (actually /etc/dbus-1)
system.conf was the only file in it when i went into the changes dir in my HD (with fresh slax 6.0.9 boot)

i use pendrive for slax

/etc/dbus-1/system.conf was later recreated
 

Post your reply

Your name (Login):

Message:

These HTML tags are allowed: <quote>, <b>, <u>, <i>, <pre>, <code>, <small>, <h1>, <h2>, <h3>, <li>



Visit Tomas M's blog for fun, mostly on religious idiocy.