You are not logged in.

#1 2005-01-11 18:50:15

Insight_45
Member
Registered: 2004-12-13
Posts: 40

hotplug timout

When the machine is booting, the section for Hotplug seems to take a long time to do.

I just saw in the /var/log/messages file, that there is probably entry for this problem:

hal.hotplug[2812]: timout(10000 ms) waiting for /bus/pci/slots
pci.agent[4010]: Bad PCI agent invocation

I suppose that the system is waiting for 10 seconds before continuing the boot.
I also saw that there is a blacklist for hotplug, maybe an option into this file could skip this timeout

Any help is appreciated. It is not a show stopper though.

Offline

#2 2005-01-11 18:56:04

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: hotplug timout

Do you know all the modules for everything connected to your computer? If so you can remove the hotplug daemon... udev will handle hotplugging of usb devices and such...

Offline

#3 2005-01-11 19:21:45

Insight_45
Member
Registered: 2004-12-13
Posts: 40

Re: hotplug timout

Thanks for the tip.

As a quick try, I removed hotplug form the list of daemons. It was not successful as the system hang at boot. But I will try to find which modules where missing.

Thanks again to you phrakture

Offline

#4 2005-01-11 20:57:28

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: hotplug timout

Insight_45 wrote:

Thanks for the tip.

As a quick try, I removed hotplug form the list of daemons. It was not successful as the system hang at boot. But I will try to find which modules where missing.

Thanks again to you phrakture

Does the system hang have anything to do with the "Updating Shared Library Links" part?

Offline

#5 2005-01-12 01:41:20

Insight_45
Member
Registered: 2004-12-13
Posts: 40

Re: hotplug timout

It seems to hang about when the xserver should start. I had time to see all that I normally see but an error message (too quickly appears and screen goes black) is shown last. Probably something about not being able to create a device for my scanner, a mknod call I have for the usb scanner.

Offline

#6 2005-01-12 01:49:23

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: hotplug timout

Insight_45 wrote:

It seems to hang about when the xserver should start. I had time to see all that I normally see but an error message (too quickly appears and screen goes black) is shown last. Probably something about not being able to create a device for my scanner, a mknod call I have for the usb scanner.

hmmm X takes a bit to start up if you don't have your domain name in yours /etc/hosts file

Offline

#7 2005-01-12 21:12:27

Insight_45
Member
Registered: 2004-12-13
Posts: 40

Re: hotplug timout

Hi, I did check the host file and it seems fine.
#<ip-address>   <hostname.domain.org>   <hostname>
127.0.0.1               localhost.localdomain   localhost

I did a few reboot and checked the diff between the log files. The best one is
in Xorg.0.log where the time of events seems correct and there is a place
where the boot stops. I have put a line indicating where the system stops
when hotplug is not loaded. Here is the section of the file

...FROM LINE NUMBER 480
II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Loading /usr/X11R6/lib/modules/libi2c.a
(II) Module i2c: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.2.0
ABI class: X.Org Video Driver, version 0.7
(II) fglrx(0): I2C bus "DDC" initialized.
(II) fglrx(0): Connector Layout from BIOS --------
(II) fglrx(0): Connector1: DDCType-3, DACType-0, TMDSType--1, ConnectorType-2
(II) fglrx(0): Connector0: DDCType-2, DACType-1, TMDSType-0, ConnectorType-3
(**) fglrx(0): MonitorLayout Option:
Monitor1--Type AUTO, Monitor2--Type AUTO

WHEN THE HOTPLUG DAEMON IS NOT LOADED, THE SYSTEM STOPS HERE
IF HOTPLUG IS PRESENT, THE LINES BELOW CONTINUE THE FILE

(II) fglrx(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) fglrx(0): I2C device "DDC:ddc2" removed.
(II) fglrx(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) fglrx(0): I2C device "DDC:ddc2" removed.
(II) fglrx(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) fglrx(0): I2C device "DDC:ddc2" removed.
(II) fglrx(0): DDC detected on DDCType 2 with Monitor Type 0
(II) fglrx(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) fglrx(0): I2C device "DDC:ddc2" removed.
(II) fglrx(0): DDC detected on DDCType 3 with Monitor Type 1
(II) fglrx(0): Primary head:
Monitor   -- NONE
Connector -- DVI-I
DAC Type  -- TVDAC/ExtDAC
TMDS Type -- Internal
DDC Type  -- DVI_DDC
(II) fglrx(0): Secondary head:
Monitor   -- CRT
Connector -- VGA
DAC Type  -- Primary
TMDS Type -- NONE
DDC Type  -- VGA_DDC

Does that indicate something about a missing daemon for the display driver

I noticed that i2c_core and i2c_i801 are present when I execute lsmod so I did a test with those two added into the module list, but the same thing happened. I guess that the lines saying that it loaded module i2c was correct. It is not this.

Oh well, it does look like it is too complex for a small annoyance.
Thanks for the help !!

Offline

Board footer

Powered by FluxBB