udev problems in current
 

So, I updated my machine to the changes from Aug 7th, only to find that when I restarted, it wouldn't boot. Lovely.

The machine was stopping right at the end of rc.S, and not getting any farther. The last thing it printed was "Using /etc/random-seed to initialize /dev/urandom.". I booted to some LiveCDs, checked everything out, and I couldn't find what the problem was. Eventually I realized that it would boot with a 2.4 kernel, but not a 2.6 kernel, and that udev was the problem. So I booted with the Slackware install CD's kernel, got in there, and chmod -x rc.udev. This got the machine started, but obviously my devices that were using udev before are not working.

I will admit, I know almost nothing of udev. With the previous versions of udev, I managed to get it to load up my optical drives and USB headset, and they worked fine. I also had hotplug running, so I think most of the hardware was running though that. Now that udev isn't running, I had to remake the symlinks to my optical drives, and my USB headset doesn't show up in any of my software.

If I try and start udev after the machine boots, the situation just gets worse. My mouse stops working, sound stops working, and I can't start any more VTs. It seems like udev isn't creating all the device files my system needs. It made ones for my video card and drives, but that seemed like it.

So I guess my question is, what exactly do I need to do to get udev working with this new version, and have all of my devices work?

have you do exactly as Pat said? (put all .new files in /etc/rc.d/ into place)

I also have upgraded to latest udev and sysvinit and it's working fine here

Worked ok for me on clean install. You problem is probably being caused by changes to some config files that didn't make it to the right place. Copying the .new files over the original should do the the trick, just make sure you don't lose any custom changes you might have put into the originals.

regards,
...drkstr

All of the .new files have been moved into place as they should be.

I am running a custom compile of 2.6.12, by the way.

EDIT:

I have removed and reinstalled the udev package, and no change. I tried to start udev again after the machine has started up, and again lost my VTs and sound. Mouse seemed to keep working this time though. When doing "/etc/rc.d/rc.udev start" it takes a very long time for it to complete. Something like 3 or 4 minutes. Not sure if that means anything or not.

I believe your kernel is too old.

Install a newer one. :)

***EDIT***

You can see in the ChangeLog that PV uses Piter Punk's changes, http://piterpunk.info02.com.br/extra/ . There you can see that you need min. kernel version of 2.6.15.

Yes, that had occurred to me this morning, so I compiled 2.6.16.

Between that, the newest udev update in current, and some changes to the rules file, things seem to be working properly now.

Would you mind sharing with us the changes you made to the rules file to make it work? Might save some others some time when searching the threads ;)

-Y1

Just for my own specific hardware, the rules worked well enough stock, but things I wanted added like I had in my previous udev setup, like the kqemu module/node, I had to do manually.

IPW2200 modules stop to work with latest UDEV release. Must rollback to 0.71. wainting for a fix

udev is problematic generally. In Debian every now and then udev fails to load on startup. This prevents a lot of device drivers from loading and leaves me to reboot and try again. This is a peculiar issue...

Before using udev, I had none of these problems. discover and hotplug worked fine for me.

It does sound very strange.
Yes. Same here. 2.4 and hotplug were the pinnacle of hardware support for me. Admittedly, that was on older hardware. 2.6 and udev seemed a step backwards at first. Even now there are modules which refuse to auto-load under 2.6 and must be "modprobed" into place. For example: parport_pc and lp. Both of these used to auto-load for me under 2.4 and hotplug...

Ah, today Pat decides to actually say in the changelog that 2.6.15+ is now required. Cute.

yeah. The latest udev (-4) solve problem of network and cdrom . For me, to made work ipw2200 , i've delete the network.rules under /etc/udev/rules.d. After reboot the new version of udev re-create the file but with the entry commented.

Can some please tell me how do I boot from Installation CD. wheever I start it asks me for new installation and I cannot access my drive where I have already installed Slackware. I have got the same problem

jam,

If your root partition is at '/dev/sda1' and you want to use the default kernel 'bare.i' then the command to enter at the first prompt is:

bare.i root=/dev/sda1 noinitrd ro

There is some help available at the prompt using function keys F1 to F5 when you boot with the CD.