* james wirel...@tampabay.rr.com [130102 16:02]:
[..]
Well is all works automatically, but udev did not create the
files I thought it would upon reboot:
rules.d # ls -alg
total 12
drwxr-xr-x 2 root 192 Jan 2 14:37 .
drwxr-xr-x 4 root 152 Dec 9 23:26 ..
-rw-r--r-- 1 root 1896 Sep
. Not a single machine has /dev/cdrom anymore, nor /dev/dvd
or any of the other incantations that have existed forever.
First, this is udev doing (or not doing) this, correct?
As shown below hwinfo see the cdrom drive, and there are long
existing udev rules that appear to want to create
https://bugs.gentoo.org/show_bug.cgi?id=451266
udev = crap
On 01/10/2013 01:52 PM, Stefan G. Weichinger wrote:
Am 10.01.2013 12:49, schrieb Stefan G. Weichinger:
Does anyone else see boot problems as well?
I re-configured my kernel and rebooted ... system stops/waits at
Setting up
off box and chose an older kernel to get things running
again, but it stops there even with other untouched kernels.
Maybe it is related to the latest udev update?
Downgraded to udev-196-r1, system boots again.
Gotta check what to re-emerge after upgrading to udev-197.
S
After
On Mon, 21 Jan 2013 21:56:00 -0600, »Q« wrote:
Here's /etc/udev/rules.d/12-opticaldrive.rules, just one line:
KERNEL==sr0, SUBSYSTEM==block, NAME=opticaldrive, SYMLINK+=%k,
SYMLINK+=cdrom, SYMLINK+=cdrw, SYMLINK+=dvd, SYMLINK+=dvdrom,
SYMLINK+=dvdrw
ISTR a change in udev that prevented
Am Tue, 22 Jan 2013 14:23:57 +
schrieb Neil Bothwick n...@digimed.co.uk:
On Mon, 21 Jan 2013 21:56:00 -0600, »Q« wrote:
Here's /etc/udev/rules.d/12-opticaldrive.rules, just one line:
KERNEL==sr0, SUBSYSTEM==block, NAME=opticaldrive, SYMLINK+=%k,
SYMLINK+=cdrom, SYMLINK+=cdrw
So, I botched the upgrade to udev-191. I thought I'd followed the
steps, but I apparently only covered them for one machine, not both.
The news item instructions specified that I had to remove
udev-postmount from my runlevels. I didn't have udev-postmount in my
runlevels, so I didn't remove
I've booted into udev-197 but my network interfaces are named the same
as ever and I've read that the new naming scheme is deactivated by
default. Do you think the new naming scheme will stick?
In the discussion in [1] the consensus seems to be that they actually
solve a real problem
Am 28.01.2013 00:00, schrieb Allan Gottlieb:
Thanks for all the suggestions. I did the following, which worked.
1. Built and installed kernel with CONFIG_DEVTMPFS=y
2. Moved udev-postmount back to /etc/init.d (I had moved it to /tmp).
rc-update add udev-postmount default.
3. Reboot
Just found that I have a blocking situation ... systemd and udev don't
like each other right now ;-)
Tried various maskings ... and found some hints in the Changelog here:
http://gentoo-portage.com/sys-fs/udev/ChangeLog#ptabs
this lead me to this bugreport:
https://bugs.gentoo.org
On Wed, Mar 27, 2013 at 11:17 AM, Tanstaafl tansta...@libertytrek.org wrote:
Hi all,
Just a question...
Can I replace module-init-tools with kmod and stay with udev-171-r10 for the
time being?
Asked another way - is kmod fully supported by older releases of udev like
171-r10?
If you
On 2013-04-06 8:31 AM, kwk...@hkbn.net kwk...@hkbn.net wrote:
Almost, except you should not specify a name that is also eth[0-9]+
(what you called 'traditional' name), since it can cause a race
condition where the kernel and udev fight for the name. While it used
to be the case (i.e. udev-197
On 2013-04-05 4:11 PM, William Hubbs willi...@gentoo.org wrote:
On Fri, Apr 05, 2013 at 02:38:21PM -0500, Bruce Hill wrote:
Just dealing with one server and my Linux router, they've been updated to
sys-fs/udev-200 and are both still using the same
/etc/udev/rules.d/70-persistent-net.rules file
Ooops I should have been more specific the net cards are not esp5s0
and esp6s0. And the drivers for the network cards are built as
modules.
N
On 4/7/13, Tanstaafl tansta...@libertytrek.org wrote:
On 2013-04-07 1:48 PM, Nick Khamis sym...@gmail.com wrote:
I just did got udev updated. Did
...@libertytrek.org wrote:
On 2013-04-07 1:48 PM, Nick Khamis sym...@gmail.com wrote:
I just did got udev updated. Did all the steps in the news:
1. tempfs in kernel
2. nothing in /etc/udev/rules.d
3. removed udev-postmount from runlevel
4) check fstab for the /tmp
And it changed!
WHAT
that retrieves these monikers called GetEthernetNames?
What you CANNOT do with udev is eg switch the names eth0 and eth1 around
after the kernel has named them. That was tried for years, it doesn't
work. So now udev never interferes with kernel namespace, it create it's
own namespace
Okay
Samuli Suominen wrote:
sys-fs/udev-197, 200, 204. --- will install to / instead of /usr so it
will work with sep. /usr just like eudev does, or just like udev-171
used to
basically the only thing to look out for is the network interface
names, you can add extra entry to grub that boots
On 06/28/2013 03:06 PM, Denis Shcherbakov wrote:
openpty failed: 'out of pty devices'
There was a news item corresponding to the udev upgrade.
1. udev-postmount init script:
Remove the udev-postmount init script from your runlevels.
2. devtmpfs support:
You need at least version 2.6.32
On 2013-08-01 5:41 PM, Dale rdalek1...@gmail.com wrote:
When the version of udev came out that was said to require a init thingy
or /usr on /, that is when I switched to eudev. I haven't used the
newer versions of udev. I do have this in my kernel config tho:
root@fireball / # cat /usr/src
On 05/08/13 13:27, Marc Stürmer wrote:
Why is was forked you ask? Because of the predictable Name stuff and
some People disliked the attitude of the udev programmer which was
either my way or the high way. aside choice is always Good to have so
in the end IT was bound to happen sooner or later
On 2013-08-10 2:57 AM, Samuli Suominen ssuomi...@gentoo.org wrote:
On 05/08/13 23:18, Neil Bothwick wrote:
On Mon, 05 Aug 2013 10:24:27 -0400, Tanstaafl wrote:
But there's not a lot of point as eudev isn't that different to udev
now, AFAICT, and a recent update forced me to switch back to udev
On 02/04/2014 01:58 PM, Joseph wrote:
Is it possible to go from systemd to udev?
I don't like the way systemd works. I have a problem with mounting USB
sick (it mounts as root:root) and I can not even change the permission.
I am receiving Hylafax fax transmission reports (email) on all
On Tue, Feb 04 2014, Daniel Campbell wrote:
On 02/04/2014 01:58 PM, Joseph wrote:
Is it possible to go from systemd to udev?
I don't like the way systemd works. I have a problem with mounting USB
sick (it mounts as root:root) and I can not even change the permission.
I am receiving
Am Sonntag, 2. März 2014, 17:14:54 schrieb Skippy:
Hi y'all. I've lost my interwebz and can't view cat pictures. Major
crisis here.
Hey Skippy,
dont worry the lolcats are all still there. udev-210 is the culprit. See [1,2]
for details. For a quick workaround, add
net.ifnames=0
to your
On Friday 09 May 2014 23:25:06 Neil Bothwick wrote:
On Fri, 9 May 2014 21:56:45 +0100, Mick wrote:
What is the meaning of this change?
[ebuild U ] sys-fs/udev-212-r1 [208] USE=acl firmware-loader
gudev introspection kmod -doc (-selinux) -static-libs (-openrc%*)
2,660 kB
On 14/05/14 03:18, Grant wrote:
I'm having a problem starting the USB network interfaces properly on
one of my systems. I brought the problem to the udev list and they're
indicating that it's a Gentoo problem:
https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg18840.html
for sys-fs/udev, specifically the entry on 03 Apr 2014.
Since udev (and openrc vs systemd) is such a huge topic lately, I think this
should be clearly explained, possibly even warranting a news item.
We don't need news items for every little change to
udev/openrc/systemd, especially when no action
,
but it doesn't own that file... But, doing an emerge -C openocd
removed the file /lib64/udev/rules.d/99-openocd.rules.
udev rules get installed to /lib/udev/rules.d, not /lib64/udev/rules.d.
Most Gentoo systems have a symlink at /lib pointing at /lib64, but
equery does not look at this. It only looks
On Mon, Apr 20, 2015 at 8:56 AM, Alan McKinnon alan.mckin...@gmail.com wrote:
On 20/04/2015 14:51, Stefan G. Weichinger wrote:
Another 5 yr server that needs some care.
sys-fs/udev-151-r4 and a kernel without CONFIG_DEVTMPFS set.
The old udev blocks openrc etc etc ...
Aside from: install
On Tue, Jun 07, 2016 at 05:05:47PM -0500, Dale wrote
> I switched mine back when eudev was new and not even stable yet. It was
> as simple as unmerge udev and emerge eudev. I don't recall even doing a
> reboot, which I rarely do here anyway.
*** WARNING *** After unmerging
On 12/21/2016 06:59 AM, Matthias Hanft wrote:
> Corbin Bird wrote:
>> The "sys-fs/eudev" package is the Gentoo fork of "sys-fs/udev" for
>> people who don't want systemd.
> Ehm... I still use "sys-fs/udev" (not eudev) without systemd.
>
Mick wrote:
> On Wednesday, 27 February 2019 13:50:58 GMT Dale wrote:
>
>> Little info here. I don't run systemd here but I also have that file.
> I checked on a non-gentoo systemd based distro and this file is not there.
> It
> seems it is related to sys-fs/udev-init-
With the demise of xf86-input-mouse and xf86-input-keyboard,
xf86-input-libinput is put forward as a replacement.
But it (or rather libinput) has udev as a hard dependency.
I have a ps2 keyboard and a 3-button serial mouse, so there is frankly
no use for udev here, nor would it help anything
On Sun, 19 Dec 2021 at 17:36, wrote:
>
> Updating 3-months old system.
> What should I watch for when it comes to updating from eudev to udev
>
> from the news file:
> "If you DO NOT want the "predictable interface naming" of newer versions
> of udev and inst
On Wed, 1 Dec 2021 17:27:32 -0600, Dale wrote:
> What made this affect me, I think the method is different to disable it
> in udev than it is in eudev.
net.ifnames=0 works on both udev and eudev, I've had it in my GRUB config
for years and it needed no changes when switching from eudev t
]
[blocks B ] sys-fs/udev-186 (sys-fs/udev-186 is blocking
sys-fs/udev-init-scripts-23)
[blocks B ] sys-apps/sysvinit-2.88-r4
(sys-apps/sysvinit-2.88-r4 is blocking sys-apps/util-linux-2.22.2)
Total: 126 packages (91 upgrades, 12 new, 6 in new slots, 17
reinstalls, 1 uninstall), Size
.
;-) Here goes again.
I rebooted today after almost three months of uptime. I noticed these
messages when booting:
Mar 16 01:55:54 smoker udevd[1275]: BUS= will be removed in a future
udev version, please use SUBSYSTEM= to match the event device, or
SUBSYSTEMS= to match a parent device, in
/lib
to the issue the news item
is about.
Further, that news item *claims* that booting with a separate /usr will
break with =udev-181. So far, *nobody* was able to explain why that
would happen, not even that news item. The only thing people have been
able to do on this mailing list regarding this news
, 12. September 2011 14:37:24 Canek Peláez Valdés wrote:
No fixable, in reality. The flexibility of udev is in part in that
the
userspace can (and actually do) run arbitrary scripts and binaries
from udev rules. You can fix the ones that require binaries in
/usr
*NOW*, but not forever
-events referencing those devices won't appear untill after
the networking is brought up.
The scripts that udev starts are run *after* a device-event is created. If
the device itself has not been spotted by the kernel (for instance, the
networking doesn't exist yet), the event won't be triggered yet
to these devices. For example, is the
systemcall that retrieves these monikers called GetEthernetNames?
http://www.kernel.org/doc/htmldocs/device-drivers/API-device-rename.html
and top of this file will tell how the names calculate:
http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev
On 02/08/13 06:14, Dale wrote:
Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed, not a
single valid bug filed about them
:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed, not a
single valid bug filed about them.
Stop spreading FUD.
Looking forward to lastrite sys-fs/eudev just like
sys-apps/module-init-tools already
On Wed, Oct 29, 2008 at 1:03 PM, Rafael Barrera Oro [EMAIL PROTECTED] wrote:
Thank you both for your responses, i will try dealing with QT first and then
emerge udev separately, without any mercilless barbaric
running-around-barely-dressed-waving-an-axe-around unmerging.
It'll be faster do do
On Mon, Sep 12, 2011 at 1:17 PM, Alan Mackenzie a...@muc.de wrote:
On Mon, Sep 12, 2011 at 05:33:34PM +0200, Michael Schreckenbauer wrote:
On Monday, 12. September 2011 15:02:48 Alan Mackenzie wrote:
Hope nobody minds me starting a new thread with an accurate name.
Which version of udev
On Thursday, September 15, 2011 09:47:34 AM Michael Mol wrote:
The main purpose of udev is to populate the /dev-tree.
The running of scripts based on /dev-tree events should be in a seperate
tool that starts later in the boot-process.
I'm not entirely convinced this is the case, because
This revision makes 2 changes...
A) The removal of udev is now standard instead of optional. udev-181
and higher will be pulling in kmod, and anything else that kmod depends
on. Removing udev will avoid unnecessary cruft on your machine.
B) Splitting up step 3) into 3a) and 3b) for greater
Correcting a typo pointed out in the earlier post today.
This revision makes 2 changes...
A) The removal of udev is now standard instead of optional. udev-181
and higher will be pulling in kmod, and anything else that kmod depends
on. Removing udev will avoid unnecessary cruft on your
I think we also ought to contact Linus, to have some input on what the
forked-udev (vdev? gdev? nlpdev?) *shouldn't* be. Lest we tread the same
path that led to him calling udev 'stupid'.
Just my 2 cents. Probably worthless :-|
Rgds,
--
On Nov 13, 2012 4:26 PM, Dale rdalek1...@gmail.com wrote
Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed, not a
single valid bug filed about them.
Stop spreading FUD.
Looking
On Fri, Aug 2, 2013 at 6:14 AM, Dale rdalek1...@gmail.com wrote:
Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed
On Fri, Aug 2, 2013 at 6:17 AM, William Kenworthy bi...@iinet.net.au wrote:
On 02/08/13 11:01, Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface
On 05/17/2015 10:59 PM, Raffaele BELARDI wrote:
walt wrote:
On 05/14/2015 10:56 PM, Raffaele BELARDI wrote:
I have an amd64 system with an old 3.3.x kernel. Recently (I think after
last udev update to 217) the boot process became very slow due to udev
waiting for uevents to populate /dev
On 06/09/2016 10:00 AM, Dale wrote:
> waltd...@waltdnes.org wrote:
>> On Thu, Jun 09, 2016 at 08:16:57AM -0500, Dale wrote
>>> k...@aspodata.se wrote:
>>>> Dale:
>>>> ...
>>>>> Can a system even boot without udev?
>>&
Jc García gmail.com> writes:
> > [blocks B ] sys-fs/eudev ("sys-fs/eudev" is blocking
> > sys-apps/gentoo-systemd-integration-4, sys-apps/systemd-226-r2)
> > [blocks B ] sys-apps/gentoo-systemd-integration
> > ("sys-apps/gentoo-systemd-integra
On Sun, Sep 3, 2017 at 6:41 PM, Grant <emailgr...@gmail.com> wrote:
>>>>> My new laptop uses /dev/nvme0n1 instead of /dev/sda which conflicts
>>>>> with the script I use to manage about 12 similar laptops running
>>>>> Gentoo. Is there a udev met
L!
I think this is nothing special and not your fault. I vaguely remember
having broken symlinks in runlevels too – was it also tmpfiles.dev or
udev-mount? I cannot recall it but I’m sure about those in folder
/etc/ssl/certs or regarded to the packages media-libs/mesa and
x11-libs/libXvMC for e
for mounting.
Think it is an issue with udev.
kos
--
Respectfully,
Konstantin V. Gavrilenko
Arhont Ltd - Information Security
web:http://www.arhont.com
http://www.wi-foo.com
e-mail: [EMAIL PROTECTED]
tel: +44 (0) 870 44 31337
fax: +44 (0) 117 969 0141
PGP: Key ID - 0xE81824F4
PGP: Server
Dr. Canek Peláez Valdés:
> On Mon, Aug 23, 2021 at 11:07 AM wrote:
...
> > Regarding udev, it has never
> > supported serial mice, so it doesn't help me.
> What are you talking about? Udev doesn't "support" any hardware; as the
> manual page states[1], it
2008/6/21 dhk [EMAIL PROTECTED]:
I looked in /etc/udev/rules.d but I not sure how all that's used. What are
the rules suppose to be?
Here you can find everything about udev rules:
http://reactivated.net/writing_udev_rules.html
You should look for a rule that with SYMLINK=/dev/fb or something
hi,
I've just upgraded the gentoo (2007.0, 64bit kernel for ps3, 64bit userland)
on PS3 today (portage is 20070815) and got a new udev 114 from orignal 104.
then after rebooting, the new udev (114) will handle my NIC as such manner:
1) if there is no /etc/udev/rules.d/70-persistent-net.rules
Elias Probst mail at eliasprobst.eu writes:
I just cannot find what to remove
or re-initiate to get the sequence of nic assignments to be
eth0, eth1, eth2, eth3.
I looked at net.examples but somehow I've missed something else.
Take a look at /etc/udev/rules.d/70-persistent-net.rules
Grant Edwards wrote:
And the most recent version of sys-apps/hotplug is over three
years old?
I could be wrong, but if I remember correctly udev is supposed to
replace cold/hotplug. Perhaps you should try to find a way to do what
you are doing using udev?
--
Randy Barlow
http
On Tue, 2 Jun 2009 06:31:20 +0100, Mick wrote:
My log shows that wlan0 is renamed to wlan1:
Not sure why this happens. Any ideas?
It's udev, you probably used another wireless device, with a different
MAC address, as wlan0 in the past. Edit or
delete /etc/udev/rules.d/70-persistent
Grant wrote:
Ok, does anyone run a udev system without hotplug and coldplug?
Pretty much all my 1U/2U servers are setup that way. I think I installed
hotplug and coldplug as prereqs to udev, but never run them. Anything
with multiple SCSI drives is plugged into a RAID card so it's hidden
On 2/1/06, Richard Fish [EMAIL PROTECTED] wrote:
On 2/1/06, Franta [EMAIL PROTECTED] wrote:
There have been a _lot_ of changes in udev, and most likely your
Oh, forgot to mention...man udev.
-Richard
--
gentoo-user@gentoo.org mailing list
Robin Atwood schreef:
I need a device /dev/net/tun to use with hercules. tun is defined in
the kernel and the traditional mknode method works fine but I loose
it after a reboot. After a bit of research I added:
# tun device for hercules KERNEL==tun, NAME=net/tun
to /etc/udev/50
Did you raise the
master and PCM sliders in alsamixer -c 1?
What does that have to do with udev not creating the special device
files?
Nothing, just the default answer if there's no audio output.
Best regards
ce
--
gentoo-user@gentoo.org mailing list
Sounds like this is related to the bug that's in an earlier thread.
Do as root:
# ebuild `equery which udev` digest
This will update the digest for now. The changes will be overwritten the
next time you sync portage, but it won't matter til the next time you
emerge udev. At which time, hopefully
Helmut Jarausch a gentiment tapote:
Hi,
I have a recent GenToo system (udev-130-r1) but I cannot
find the utility 'udevinfo'
Which package contains it?
Many thanks for a hint,
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
Thank you both for your responses, i will try dealing with QT first and then
emerge udev separately, without any mercilless barbaric
running-around-barely-dressed-waving-an-axe-around unmerging.
I'm gonna miss the sledgehammer though...
Seroiusly, thanks very much for your help
PD: As soon as i
On Mon, 15 Dec 2008 21:37:06 -0500
Willie Wong ww...@princeton.edu wrote:
Is there any way of making udev recognize that the sda1 device is a
child of the actual hardware?
Yes. You can use attributes from the device itself and from any single
parent device. What you can't do is use
Hi,
Recently saw that i have a udev-tarball enabled setup and think of
disabling it.
Wanna make a backup of the tarball before doing that, but can't find
where it is located/saved.
TIA. Rumen
smime.p7s
Description: S/MIME Cryptographic Signature
On Sat, 22 Oct 2005, Jonathan Wright wrote:
Date: Sat, 22 Oct 2005 15:24:01 +0100
From: Jonathan Wright [EMAIL PROTECTED]
Reply-To: gentoo-user@lists.gentoo.org
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USB problem(maybe related to udev)
Tamas Sarga wrote:
I'm affraid
Alexander Skwar wrote:
[EMAIL PROTECTED] ~ $ epm -q dbus udev hal ivman pmount
dbus-0.50-r1
downgrade to 0.36.2
udev-073
hal-0.5.4
ivman-0.6.5
downgrade to 0.6.4
--
gentoo-user@gentoo.org mailing list
Norberto Bensa schrieb:
Alexander Skwar wrote:
[EMAIL PROTECTED] ~ $ epm -q dbus udev hal ivman pmount
dbus-0.50-r1
downgrade to 0.36.2
udev-073
hal-0.5.4
ivman-0.6.5
downgrade to 0.6.4
Done. Still no automount.
Alexander Skwar
--
gentoo-user@gentoo.org mailing list
world update. Avg. download speed ~ 2.9k/s. Took about
36hrs. Phew! Thankfully there was only 61 pkges to do.
Ouch.
Now I'm looking for advice on setting up udev. A
message in one of the logs says to be sure and start
udev on boot but there's no such thing in the
/etc/init scripts.
-mw
udev system, kernel 2.6.24-something.
serial is a module, as is lirc_serial.
How do I change the order of module loading, so that lirc_serial is
loaded first, and grabs the ttyS0 serial port?
I suspect that coldplug or something is loading the serial module quite
early in the boot procedure
Hello,
I've got a couple of older Pundit-R machines that we use as MythTV
frontend machines around the house. I was trying to get ready to do an
update on MythTV so I started working on both machines. In the process
I updated a lot of the basic system stuff on both machines but only
got udev
. I was trying to get ready to do an
update on MythTV so I started working on both machines. In the process
I updated a lot of the basic system stuff on both machines but only
got udev updated on one box before I noticed a problem on that
machine. When booting it now scrolls a bunch of messages
On 4/12/06, Kenton Groombridge [EMAIL PROTECTED] wrote:
What I can do to ensure that it associates the correct module with the
correct eth?
Your best choice is to write udev rules for them.
A google for udev ethernet rules should get you started.
-Richard
--
gentoo-user@gentoo.org mailing
On 5/30/06, Leandro Melo de Sales [EMAIL PROTECTED] wrote:
Richard,
when I change any rules, should I have to execute a command in order
to update the udev rules?
Usually you can run udevstart to get the new nodes activated
immediately. But if you are just going to reboot
On 5/30/06, Leandro Melo de Sales [EMAIL PROTECTED] wrote:
Richard,
You said that one rule can override other, but if you read udev
manual ( http://www.reactivated.net/writing_udev_rules.html ), you'll
realize that what you said I think is incorrect.
That is _not_ the udev manual. I've
I haven't been able to figure out how to prevent that the new udev (090) loads
the ipw2100 (wireless lan) during boot. I don't use it very often, and I have
set the button that enables/disables the transmitter to also load/unload the
kernel module. Any hints or pointers appreciated?
--
Bo
I noticed this:
sys-fs/udev-089 and later takes over the responsibility of
coldplugging. Therefore sys-apps/coldplug is no longer needed.
here:
http://gentoo-wiki.com/HOWTO_Installing_USB_Scanner
Is udev-089 a replacement for coldplug in all cases?
- Grant
--
gentoo-user@gentoo.org mailing
On Thursday 09 November 2006 10:01, Arnau Bria [EMAIL PROTECTED] wrote
about '[gentoo-user] Semi OT: hotplug / coldplug / udev ...':
I have some doubts about the way hotplug / coldplug / udev work.
What really happen when you plug a (again,
i.e.) pendrive in your computer? Which programs take
I switched to udev-103 recently, and now when I boot I find that ipw3945d
is not getting started, which causes my wireless card to not appear at
all. rmmod ipw3945; modprobe ipw3945 once the system has started works.
Any advice?
-Daniel
*This .sig left intentionally blank*
--
gentoo
Hello!
I have updated my gentoo box by typing emerge --update world. This also
updated udev and now I don't get any network on startup. If I want to
get a network connection, I'll have to first delete
/var/run/dhcpcd-eth0.pid and then run 'dhcpcd eth0'.
On startup I get some udev related
Hi,
Mark Knecht wrote:
which would have made the device. Is the fact that the device isn't
created a problem with the ebuild? Even if it was, how should this
really be created for a udev system? A rule somewhere in some
udev.conf file?
Its a kernel bug which is fixed in 2.6.12. If you upgrade
I used the steps on the Gentoo docs. They also link to some udev site.
Essentially
1. Set up kernel not to autostart devfs (when everything is okay you can
remove devfs from the kernel)
2. emerge udev
3. I modified /etc/conf.d/rc (I think it was) to have a devfs and a udev
version
On Thursday 28 July 2005 20:59, Zac Medico wrote:
Volker Armin Hemmann wrote:
Hi,
On Thursday 28 July 2005 08:51, Zarick Lau wrote:
Hi,
I switched from devfs to udev 10 days ago, and since then every
nth boot will hang at 'initializing random number generator'
It try to read a /dev
On Tue, 9 Aug 2005, Joe Rizzo wrote:
Thanks for the response. I think I'm having an issue unrelated to udev.
3ware tech support said the driver included with the kernel was old and
suggested to build the latest driver as a module.
Why not do away with initrd and just build the driver intyo
Hello,
is anyone using a Palm Tungsten T5 under Gentoo and Udev ? I tried
google up and down, read tons of docs and howtos, but I can get it
to work. Any real life experience would be very helpful.
cu
stonki
--
www.stonki.de
www.krename.net
www.kbarcode.net
www.proftpd.de
--
gentoo-user
udevd doesn't create's device file, but when i manualy copy it from static dev
tree my cdrom works fine, and sometimes udevd even creates symlinks on it
(i.e. cdrom and cdrw), but this is not restore's after reboot. What's going
wrong with it? I'm running 2.6.12 kernel whith udev version 068
in /dev/cdroms/cdrom. May be...?
I didn't see the beginning of this thread so my question may be
redundant. Did you (the OP) verify that the drive is still detected by
the BIOS?
having done some research yesterday on udev, specifically the gentoo udev
howto, it was my understanding that udev did
Michal Kurgan schreef:
Hello!
Recently (after udev update) i spotted that hald do not create mount points
in
fstab so kde media kio slave doesn't work...
http://gentoo-wiki.com/HOWTO_D-BUS%2C_HAL%2C_KDE_media:/
HTH,
Holly
--
gentoo-user@gentoo.org mailing list
Willie Wong wwong at Princeton.EDU writes:
On Wed, Jun 28, 2006 at 03:04:55AM +, Penguin Lover James squawked:
Well I put udev in my /etc/portage/package.keyworks to get the latest
version, thinking that might fix the problem. It do not.
I don't think that's necessary. It works
On Sunday 02 August 2009 10:45:46 John covici wrote:
on Sunday 08/02/2009 Alan McKinnon(alan.mckin...@gmail.com) wrote
On Sunday 02 August 2009 00:59:22 John covici wrote:
Hi. On my latest update attempt, I get the following message: !!! All
ebuilds that could satisfy =sys-fs/udev
Dale wrote:
Philip Webb wrote:
090910 Dale wrote:
I noticed I now have a udev in /etc/init.d/.
I checked, it is not running but udevd is not running either:
r...@smoker / # /etc/init.d/udev status
* status: stopped
r...@smoker / # ps aux | grep udev
root 30451
Hi
rkhunter showed a warning because there is a
/dev/.udev
directory on my machine. qfile didn't find any 'owner'.
Is it safe to remove that directory?
Many thanks for a hint,
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
501 - 600 of 8452 matches
Mail list logo
