LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 11-28-2005, 12:54 PM   #1
darksmiley
Member
 
Registered: Jan 2004
Location: London, England
Distribution: Usually Linux Mint, Debian, Ubuntu or CentOS
Posts: 233

Rep: Reputation: 30
help! problems after updating udev for a 2.6.14 kernel!


hiya

I was using 2.6.11.12 for a long time until i decided to finally go for it and make the jump to a newer udev for 2.6.14. I had compiled a 2.6.14 kernel from before but it paused for a long time initializing udev and I learnt that it was necessary to update udev.

SO, today, I downloaded udev 0.76 and compiled and installed it while using my 2.6.11.12 then rebooted into my 2.6.14 and got this unfortunate error:

udevsend[XXXX]: main: error sending message: connection refused

hundreds of times on the screen (with the XXXX replaced by a different number every time). Is this something to do with hotplugging? I have an /etc/hotplug and an /etc/hotplug.d directory. I tried recompiling my 2.6.14 but this made little difference. The machine just about boots but doesn't go any further than GDM. The prompt is fully functional though and it has mounted my disks.

By the way, I use Slackware (10.1 I think). What was all this talk about udev rules? Do I need to change anything? I just left it to use its defaults.




...

help!
 
Old 11-28-2005, 02:08 PM   #2
foo_bar_foo
Senior Member
 
Registered: Jun 2004
Posts: 2,553

Rep: Reputation: 51
make sure you have
CONFIG_KOBJECT_UEVENT
enabled in the kernel
http://www.ussg.iu.edu/hypermail/lin...06.2/1088.html
seems the older hotplug hook doesn't work anymore in favor of this
 
Old 11-28-2005, 02:34 PM   #3
darksmiley
Member
 
Registered: Jan 2004
Location: London, England
Distribution: Usually Linux Mint, Debian, Ubuntu or CentOS
Posts: 233

Original Poster
Rep: Reputation: 30
yea, it was built in the last time I built my kernel. I catted the kernel source's .config and found it:

CONFIG_KOBJECT_UEVENT=y

what else should I do?

Last edited by darksmiley; 11-28-2005 at 02:36 PM.
 
Old 11-28-2005, 11:49 PM   #4
foo_bar_foo
Senior Member
 
Registered: Jun 2004
Posts: 2,553

Rep: Reputation: 51
ok this is as far as i understand it
i think the problem is in the bootscripts
old school was udevsend (called by hotplug) automatically started udevd
this is from the kernel today hotplug readme
Quote:
The udevd daemon must be started by an init script to receive netlink
events from the kernel driver core.

- From kernel version 2.6.15 on, the hotplug helper /sbin/hotplug should
be disabled with an init script before the boot scripts are run and
kernel modules are loaded.
so i think your init script needs to start udevd --daemon. It no longer happens magically
through udevsend.

what i would do is find a newer system and look at the udev boot or possibly someone will come along here and show.
 
Old 11-29-2005, 05:37 PM   #5
darksmiley
Member
 
Registered: Jan 2004
Location: London, England
Distribution: Usually Linux Mint, Debian, Ubuntu or CentOS
Posts: 233

Original Poster
Rep: Reputation: 30
ok, i think (i THINK ) it's all ok now! I finally ended up putting that line at the very beginning of rc.S and my system seems to be fairly content. It does throw up a one line error on boot like this:

udevd[XXXX]: add_to_rules: error parsing SYSFS attribute in 'BUS'

but other than that things seem to be fine. Do you know what that is? My m8's pc has done the same actually under similar conditions.

Thanks for your help though m8 - I couldn't have got it working without you! I'm now updating my entire Slackware installation to 10.2 with slapt-get and getting ready to install Gnome (at the moment I use Flux).

Later
 
Old 12-02-2005, 03:14 AM   #6
darksmiley
Member
 
Registered: Jan 2004
Location: London, England
Distribution: Usually Linux Mint, Debian, Ubuntu or CentOS
Posts: 233

Original Poster
Rep: Reputation: 30
ah, one thing. Just before it switches to runlevel 4 I get this:

none on /mnt/ramfs type tmpfs (rw)
mount: none already mounted or /sys busy
mount: according to mtab, sysfs is already mounted on /sys


and that's all it says about the whole ordeal ... I notice no other problems, errors or drops in performance.

seeing as my understanding of /proc and /sys and similar things is fairly limited I wondered if anyone knew what this was about?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Problems with updating LILO for a kernel recompile.. SocialEngineer Slackware 10 03-08-2005 06:05 PM
problems with udev - 2.6.10 kernel akshunj Slackware 8 01-21-2005 10:45 AM
Problems updating Slackware 9.1 2.4.x kernel to 2.6.6 WopMaster8 Slackware 7 06-01-2004 08:32 PM
Problems with updating kernel scoughlin Linux - Newbie 1 07-30-2003 04:21 AM
RH 7.3, Kernel, upgrade problems and updating drivers!!!!!!!!!!!! admedic Linux - Newbie 5 08-18-2002 08:25 PM


All times are GMT -5. The time now is 04:10 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration