Hi,

I really want to move from a 2.4.x to a 2.6.x kernel. I installed the new module init tools, and also compiled the new kernel with hotplugging enabled. I then installed the hotplugging scripts, and when i boot, and i get to the hotplug startup script, i get an unforseen error.


which: no usbmodules in (/sbin:/bin:/usr/sbin:/usr/bin)
** can't sythesize root hub events
touch: cannot touch '/var/lock/subsys/hotplug': No such file or directory

I was wondering if i need usbmodules to get hotplugging to work, if scrolled off the screen, but i think it said the same for pci modules, so i was wondering if i need those. I was wondering why it needs to touch that file. I looked, and there is nothing under my /var/lock directory. Has anyone else got hotplugging to work with 2.6.x and lfs?

thanx, joe

http://lfs.crash404.com/hints/downlo...s/2.6-udev.txt and http://lfs.oregonstate.edu/hints/dow...-detection.txt

Hi, i think i have a problem with usbutils. My output for lspci is

00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
00:0a.0 Multimedia audio controller: IC Ensemble Inc ICE1712 [Envy24] (rev 02)
00:0c.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
00:0f.0 RAID bus controller: Promise Technology, Inc. PDC20276 IDE (rev 01)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 23)
00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:14.0 USB Controller: VIA Technologies, Inc. USB (rev 50)
00:14.1 USB Controller: VIA Technologies, Inc. USB (rev 50)
00:14.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti200] (rev a3)

and for ls usb

Unknown line at line 1809
Duplicate HUT Usage Spec at line 2650
Bus 001 Device 001: ID 0000:0000 Virtual Hub

so what is wrong, i'm not sure do i need to compile something in the kernel i forgot?

thanx, joe

Which USB host controller drivers did you enable on the USB menu? I would suggest that you set
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_PRINTER=y
CONFIG_USB_STORAGE=y

But obviously I'm biased by the hardware I'm used to working with. Really, it's up to you to try different options and see what works. If the EHCI/UHCI combination doesn't make an improvement, try setting them to not set and CONFIG_USB_OHCI_HCD=y. Good luck.

HI,

I found the problem i didn't compile udci into the kernel i did it now it works alright, but i have a new problem. what are the default names of the device nodes udev creates for ide harddrives i can't boot. I used the udev startup script from the udev025 package, because it has one written for lfs. Do i need any static device nodes so it will boot?

thanx joe

I'm not an expert on udev, I'm still learning as I go, but from what I've seen so far it is way more trouble than it's worth. It's given me loads of problems which I've only been able to fix with crude hacks to the bootscripts and I've yet to see any benefits to udev. Static device nodes worked with much less trouble. I'm in favour of progress but udev doesn't seem like progress to me as I can't see any benefit. It seems it works by creating nodes to correspond to and support entries the kernel makes in the /sys filesystem. If udev isn't making nodes for your IDE hard drive that suggests to me that the kernel isn't making /sys filesystem entries for your IDE hard drive, perhaps you need to enable something important in your kernel and then recompile? Udev is about hotpluging. It shouldn't be giving you problems with the core of your system.
Next time I rebuild my system it won't be with udev, though I will probably use it eventually. Just my tuppence worth.

Hi,

Well thanx for your help i think i'll just go with a static /dev tree. i used to use devfs, and i liked the very managble tree, but this udev business seems to be crude at best. i guess i'll check back every once and a while and eventually use it. My main objective was to get hotplugging to work so i guess it will work with a static tree.

thanx, joe