Kernel 2.6.15.2 + Udev + Slackware 10.2
 

Anybody got this working yet?

I tried and got nowhere at all.
First I couldn't even copy my own files in my own home directory, getting error message that operation not permited.
So then I disabled hotplug and compiled and installed the latest udev.
No way Jose! What a fiasco!
There is more questions arising from the README and FAQ then it answers.

Fscked the system so bad I had to boot from Slackware CD and restore the original Slackware's udev because my root file system got mounted read-only and I couldn't do anything.

On the other hand I have Kernel 2.6.15.1 working on my laptop with Slack 10.2 very nicely but still using hotplug and the default Slackware udev.

What's changed in the latest kernel so much it will not work any more with Slackware.
Any solutions?
Anybody?

Thanks

Have you tried this?

http://piterpunk.info02.com.br/extra/

It didn't work perfectly for me, but I have a tweaked so much stuff on my own system that I can't rule out operator error as the cause. Even so, no real show stoppers.

shilo,

Would you mind posting what you changed from piter punk's blueprint in order to get it working?

I tried following out of the box, and ended up booting my main disk as read-only, causing neither udev nor anything else to work.

-Y1

Ok,I'll give it a try. Are those packages for Slack 10.2 though. It doesn't say anywhere which version of Slack it's for.

I'll post later today how it went.

Slackovado: yes it works on 10.2

Yalla-One: I had the same problem (more or less randomly,I believe mostly due to some additional time required to remove temporary files, since hot reeboot ran flawless). I fixed it by leaving /etc/rcd/rc.udev an extra 3 secs to do his job before starting count events this way: in /etc/rc.d/rc.S added a line as foollows

# Mount sysfs next, if the kernel supports it:
if [ -d /sys ]; then
if cat /proc/filesystems | grep -w sysfs 1> /dev/null 2> /dev/null ; then
if ! cat /proc/mounts | grep -w sysfs 1> /dev/null 2> /dev/null ; then
/sbin/mount -v sysfs /sys -n -t sysfs
fi
if ! grep -w nohotplug /proc/cmdline 1> /dev/null 2> /dev/null ; then
if [ -x /etc/rc.d/rc.udev ]; then
/etc/rc.d/rc.udev start
sleep 3----------------------------------this
/lib/udev/udev.count_events.sh
fi
fi
fi
fi

hope this helps
Ciao

Hmm, I got warning messages about the filesystem being mounted read-only, but later in the boot process everything is remounted.

It seemed to work, I just got error messages that I haven't been abe to sort out yet. Note that I did all this on a clean install. I haven't had much time to play with it though, so it could very well be broken and I just haven't realized it.

As for what I changed from Piter Punk's blueprint, nothing. It is importatnt that you understand the directions well, though. There are a number of config files that need to get fixed up before things will start working.

Just got a mail from Piter Punk - turns out he's made a couple of changes to the scripts as bug-fixes, among them introduced a delay (as urka58 suggested) to udev to prevent the read-only boot.

Have not had a chance to test it yet as I'm using my Slackware laptop for work, but will try later today.

So - for all that want to try 2.6.15.x and newer udevs: make sure you get piter punk's updated packages!

-Y1

I decided to check out my test sytem a little better. It upgraded to the latest Piter Punk packages. I still get the error messages about mounting read-only. Udev appears to be running, but I just noticed that it doesn't seem to be working correctly. :scratch: My /dev is static. It contains all the devices installed by Slackware for 2.4 kernels. I've tried re-starting udev every way possible, but this doesn't seem to change.

Now I am interested in knowing how to get this thing working right.

Hi shilo,

Just tried the same thing myself, both with Piter Punk's latest packages, and inserting the 3 second delay as suggested earlier in this thead, but to no success at my end either.

12 out of 12 times the file system was mounted read-only, and udevd counted down how many instances was running until it ended with 2.

Hard to trouble-shoot, as the system wouldn't even let me log in, and thus couldn't print dmesg or check the logs either...

Have emailed PiterPunk with as detailed report as possible, and hope him or Patrick or someone more experienced than me might fix it.. Seems like there's still a lot going on in udev development, so maybe an even more recent version of udevd might help too...

-Y1

I'm not quite sure I understand the udev problem here, can I ask a few stupid questions? My udev knowledge still stops at udev rules :)

I found a thread said 2.6.15 only works with udev 071 and above, is it true? I have already installed 2.6.15.2 on two boxes (all running slackware-current, which uses udev 064, I believe), many important drivers are compiled into the kernel. It looks like everything is OK. Sound, CD recording etc. all works. Did I miss something? What should I look for to confirm udev works or not? By "working", do your guys mean new feature working or basic feature working?

Thank you very much for your help!

linux-2.6.15.n and Slackware 10.2
 

Here is what Pat Volkerding of Slackware told me:

>>BTW, 2.6.15.x requires plenty of other changes that I'm working on now,
>>such as updates to udev, module init tools, and the addition of
>>sysfsutils. Until you see those things appear in -current, you're
>>going
>>to have to stick to 2.6.14.x or lower, and once the changes are merged
>>all the 2.6.x kernels older than 2.6.15 will be broken. So it might
>>not
>>be the best time to be trying to use a 2.6 kernel... :-)

I am, however, using 2.6.14.7 without problems so far.

No Firebird
you can use kernel 2.6.15+ without problems, (or better, more problems than you would have with kernel 2.6.14 or lower) with udev that comes with Slack 10.2 (0.64).
The problems come if you want to use udev 0.71 (not sure, may be 0.76) with kernels 2.6.14 or lower, since newest releases of udev require some feature available only with 2.6.15+ kernels.
What differs in these new releases of udev, is the possibility not to use hotplug anymore since udev take care of collecting/intercepting "events" and creating device nodes in userspace.
As udev is in continous development, I counted 3 new releases in a week, it is a little difficult to be maintened and work properly on many systems.
I see only two reasons to switch to newer udev,for now, your system is working very bad, but I understand from your post it doesn't, or you want to "explore" new possibilities and features( ie my case).
The main advantage using new udev is your system will boot faster, but the disadvantage is it requires a lot of changes in startup scripts and some extra utilities.
Slackovado has already posted the link where you can find the required packages.
Ciao

These are the things that PV is working on now, but if you checked out the link earlier, they are the EXACT things that this thread is talking about. Piter Punk has already released "updates to udev, module init tools, and the addition of sysfsutils."

There seem to be some problems with them, though. I wonder now, who HAS got UDEV working (with dynamic /dev entries) using the Piter Punk solution?

urka58 and bmccrac02, thanks very much for clearing things up.

I guess I'd better waiting for PV for udev upgrade.

OK, the Piter Punk packages are working for me now. I recompiled my kernel using the Slackware 2.6.15.3 config and that seemed to so the trick.

No hotplug = fast boot. :)

Hi shilo,

Happy you got it working!

Did you make any changes to any of Piter Punk's packages or special provisions in your kernel config?

I remain somewhat confused why I can't get these udev packages to work on my fairly standard slackware-current installation (with 2.6.15.3) without ending in th Read-Only mount-loop...

-Y1

Nope. Just used the newest ones from his sight. Also, make sure you look for the .new files and edit configs accordingly.

The new thing was the kernel compile. Don't know why that would fix it, but it did. I downloaded the source for 2.6.15.4. Then I downloaded the config for 2.6.15.3 from Slackware -current. I copied the config over and used "make oldconfig." No other changes. Finished the compile, and it worked.

After that worked, I did a few more recompiles:

I recompiled for my arch. Still worked.

I recompiled for Desktop stuff (prefetch, 1000 hZ, etc.). Still worked.

I recompiled the ALSA section as modules. Still worked (and I got rid of the error mess. at boot for ALSA. I never use the ALSA driver package provided, and this is what I have found to be the easiest way to always have sound working. :) )

I recompiled the video settings. Still worked.

Somewhat confused? It drove me CRAZY! :) Hopefully it will work for you if you try the method I used.

I'll keep tweaking on the kernel config to see if I can spot what the problem was. It's kinda difficult to spot with diff at this point because my previous config was so different from the stock.

So far, the little issues that I have are:

One time (only once, which is strange), I got an error that addswap didn't work because my swap device didn't exist. Ofter the boot was completed, the swap was active, though, and the logs showed the swap had been activated. Possibly thesleep isn't ALWAYS long enough? I don't know. Kinda hard to troubleshoot, since it only happened once.

Seems to be an issue with the utopia stack and my USB HDD. This could be related to Gnome, though. The USB HDD is recognized in the logs, but doesn't mount. Also, I wonder if there is a conflict with my USB HDD, because using the stock kernel config results in a strange driver being loaded. The yealink driver gets loaded, too, which is apparently a USB VOIP phone driver. Gotta look into that.

I get a message something like, "/dev/pts could not be mounted. Device busy, non existant, or already mounted." Not a big deal, probably just need some tweaking on /etc/fstab. Works, so I'm guessing it was the "already mounted" problem.

I may use the old ldconfig tweak to speed up the boot. The system is booting so much faster that this is the only thing slowing it down at this point.

Hey, i'm having trouble also after installing 2.6.15.3 kernel from Slackware repository. Should i try to disable hotplug since it always stopped when starting the hotplug services??

Hi,
The Piter Punk packages are working also in my test system.
I put bootchart log images below just as an info.

The first image is a log with conventionla Slackware-current udev(064) system.
* boot time = 49 sec
And the second image is a log with the Piter Punk packages (udev-084).
* boot time = 36 sec

http://www.flickr.com/photo_zoom.gne...2106045&size=o
http://www.flickr.com/photo_zoom.gne...2106046&size=o