Hi guys,

Up and running with a fresh 13.37 (x64) install after a couple years away from using linux on the regular with just a couple minor but annoying issues at the moment.

Firstly, during my boot process there are several verrrry slow moments. The biggest is starting the HAL Daemon which hangs for probably at least 30 seconds sometimes (almost always). Is anyone aware of any issues that slow this down that I can address somehow?

Prior to starting HALD, it also hangs a bit doing what I guess is initializing usb drivers or devices while outputting something that looks about like

USB 1-3 device descriptor read /64 -error 110

a few times in a row.



The second problem atm is that I have to manually iwconfig my wireless info and dhcpcd wlan0 each time I boot.
I installed wicd as soon as I installed, but when I try to configure just using wicd it can never successfully get an ip address for some reason. After that I put in the info into inet1.conf and I can see the attempt at the end of booting to dhcpcd wlan0 but it times out. Once I've been booted for a minute I can ifconfig wlan0 up, iwconig my essid and key, and dhcpcd wlan0 and it get online (which is how I'm posting now) but its rather annoying, particularly since it seems that if I can run dhcpcd on the interface myself the scripts should be able to do it equally well :s

Interface is a belkin usb wifi key if that matters, again it works fine with the kernel drivers once I configure it myself.


Anyways, if anyone has any intuitions about either of those of if theres any further info I need to give, thanks in advance!

For the hald hang, how about what this person found?

For the wireless bit, could you provide the logs between when the USB device initializes (or identified by udev) and the end of rc.inet1's boot? rc.inet1.conf might be useful too, but make sure you elide any password stuff before you post it.

1 members found this post helpful.

I didn't have a DVD in, but adding the --verbose flag to the HALD start command seems to have removed all the hangups for some reason, hopefully it stays that way, its an impressively fast boot without the hangups.


I'll grab the inet logs. Its just strange to me because after im booted up , I can manually change the settings and run dhcpcd and it seems like wicd at least should be trying to do exactly that, even using the same external scripts afaik, but always fails to get an ip

I /think/ I got the wifi boot process working, I removed wicd and reinstated what I had put in inet1.conf awhile back,but I think I didn't put a value for the default gateway originally, I changed so much stuff back and forth trying to get it to work that I'm not entirely sure what fixed it though, and its only worked through one boot so hopefully it stays working.


The boot hangups are came back on successive boots though,

it hangs significantly with:

the usb error -110's here:

and staring hal, messages log has a couple errors that look related to hal

USB errors : Do you have an external USB hard drive or USB key?
The read errors can happen when you have a broken USB device where the contacts aren't making a proper connection.
I had a cracked wifi dongle one time which I tried resolder the contacts and it never worked right.

What file-system did you use for your partitions?
[ 4.784857] EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
[ 4.785752] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)

* You may be seeing hald but it may also be the next thing after hald that is hanging.

Sometimes the previous file system types and partition table might even still be read although you've specified a different configuration. They tell you to reboot if you have manipulated the partition table. I've had to do it in the past.

It looks like you may need to reinstall. Boot with the slack cd and back up your data. Then wipe the partition table.

1 members found this post helpful.

Oi, *facepalm* important info that I should have included in the first post: I am dual booting with win7 between two seperate disks btw. Slack install and lilo are on the first disk

I have a USB (NTFS( hdd attached but it actually mounts and functions fine, I've been playing music/videos from it without a problem. Hmm.

Linux disk is two ext4 and one swap parition


Edit: Just rebooted from win7 into slack, boot was quick this time,same devices attached. Hmm.


Edit: Rebooted to check alsaconfig, another hang free one...weird. Last time I booted my windows disk chkdsk ran and I wasnt sure why, could a disk error on the windows hd have been slowing things down? (I do have slack mount my windows drive). Thats the only thing I can think that happened since last boot - but it did boot quick another time then went back to slow so we'll see if this holds up. Hopefully it does because after all the little configurations I've had to do I'd hate to have to reinstall

Well seems to be solved even if I'm not positive why, heh.

It seems to be caused by mounting corrupted ntfs drives, ie if I have to do a hard reboot or anything it seems to crop back up. ntfsfix or chkdisk under windows might take care of it. Unfortuatly suspending in slackware seems to cause problems for my ntfs drives.

Yeah just made the USB hdd read only except by root, tried to do a pm-utils script but it couldn't remount on resume correctly since it was run as my user account I guess. This is probably safer anyways for now.

Concerning the wifi issue and having to iwconfig and dhcpd manually, i recently ran into the same issue in 13.37.
I had to edit the wlan section in /etc/rc.d/rc.inet1.conf. The whole section is commented out, you have to uncomment a few lines and put a few things in. Here's mine:

## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]=""
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
DHCP_IPADDR[4]="192.168.1.1"
WLAN_ESSID[4]=mynetworkid
WLAN_MODE[4]="Managed"
##WLAN_RATE[4]="54M auto"
WLAN_CHANNEL[4]="auto"
#WLAN_KEY[4]=""
WLAN_IWPRIV[4]="set AuthMode=WPA2PSK | set EncrypType=AES |
set WPA2PSK="my64digithexkey""
WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"

After you edit the rc.inet1.conf file, if you use WPA encryption, you must also edit the /etc/wpa_supplicant.conf file. Relevant section from my wpa_supplicant.conf:

# WPA protected network, supply your own ESSID and WPAPSK here:
network={
scan_ssid=0
ssid="mynetworkid"
proto=WPA RSN
key_mgmt=WPA-PSK WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
#psk=mypassphrase
psk=my64digithexkey
priority=10
}

After you edit these files run these commands and you should be good to go
$ sudo /etc/rc.d/rc.inet1 wlan0_restart
$ sudo /usr/sbin/wpa_supplicant -iwlan0 -Dwext -c/etc/wpa_supplicant.conf

Hopefully this helps you out, since this is my first post.