Some times I boot up, and udev has labelled what is usually eth0 as eth1. Of course, my rc.inet1.conf is configured for seeing internet at eth0, so no connection, quite obviously. Then I reboot and the device label is back to "eth0". Actually I'm still not able to get connected, even at eth0, despite my nameservers being OK, and the default route gateway being all OK. PS. I have a static ip address.
View 3 RepliesI like to autohide my panel. But for some reason, it won't show unless I mouse over one of the bottom corners of the screen. The whole bottom edge where the panel hides should summon it if I mouse over, and I have been able to do this before, but now, after a system update, it only appears when I mouse over those bottom two corners. Does anyone else get this, or know how to fix it?
View 9 Replies View RelatedIn the not so distant past, I was able to hide arrays/encrypted arrays from nautilus with udev rules as follows:
Code:
## HIDE Encrypted "dm" partitions from nautilus
SUBSYSTEM=="block", KERNEL=="dm-*", ENV{ID_FS_USAGE}=="crypto", ENV{DKD_PRESENTATION_HIDE}="1"
## NOTE: not needed by Fedora
[code]....
In the not so distant past, I was able to hide arrays/encrypted arrays from nautilus with udev rules as follows:
Code:
## HIDE Encrypted "dm" partitions from nautilus
SUBSYSTEM=="block", KERNEL=="dm-*", ENV{ID_FS_USAGE}=="crypto", ENV{DKD_PRESENTATION_HIDE}="1"
[Code].....
This worked in OpenSUSE 11.2; it does not work in either FC13 or OS11.3
I got a problem with the bar on my desktop. I have WOW installed on my Vista drive, so I just copied the files into my Ubuntu drive. They startup fine, but the bar ( upper bar ) woun't hide when it starts. In windows you don't see the bar when you play a game. This is very annoying. I am, a complete noob in Ubuntu. Is there a simple soulution to this?
View 2 Replies View RelatedI have a Linux server that runs the Sybase DB. Sybase suggests using character devices to access raw devices rather than O_DIRECT to block devices, or cooked FS's. So, I went ahead and configured /etc/sysconfig/rawdevices as such:
/dev/raw/raw1 /dev/vg01/tempdb
/dev/raw/raw2 /dev/vg01/testdb
/dev/raw/raw3 /dev/vg01/fakedb ...
This works fine. I set 'chkconfig rawdevices on' and all is well. I read that this method is deprecated and went about trying to accomplish the same via Udev rules. I already use udev rules in /etc/udev/rules.d/60-raw.rules to set permissions on these devices, i.e.
ACTION=="add", KERNEL=="raw*", OWNER=="sybase", GROUP=="sybase", MODE=="0660"
That works fine. I even set symbolic links:
KERNEL=="raw1", SYMLINK+="vg01/rtempdb"
KERNEL=="raw2", SYMLINK+="vg01/rtestdb1"
KERNEL=="raw3", SYMLINK+="vg01/rfakedb2"
But I cannot seem to get the actual device creation piece to work within udev (it only works using rawdevices). I've tried:
ACTION=="add", KERNEL=="vg01/tempdb", RUN+="/bin/raw /dev/raw/raw1 %N"
No errors, but nothing happens. The device just doesn't create. I've also tried doing it by passing major and minor numbers. Is it possible to get all of this into udev rules or am I stuck with rawdevices? I'm also utterly confused as to the future of rawdevices... the raw man page said it was deprecated, and now at v5.5 it has that piece taken out. Also RHEL 5.3 dropped support for rawdevices in initscripts only to add itback in 5.4. I'm an admin, not a DBA, so I cannot say if this is a bad or good way, only that it is the way the vendor supports and recommends, so it is the way that I must go... just trying to make it work as "un-deprecated" and cleanly as possible.
Having finally made the switch from Windows (7 Professional) to Linux (Fedora 13) on my laptop, I'm now trying to get all my devices working, specifically an Olympus VN-4100PC Digital Voice Recorder. I've installed odvr and it works in root, but not as a normal user. The installation instructions say: odvr *requires* access to the user-space USB interface.
It is recommended to place "41-odvr.rules" into "/etc/udev/rules.d" or setup your own udev rules rather than running odvr as root. After changing udev rules, don't forget to run "udevcontrol reload_rules" and to replugin your DVR. Again, root privileges are required unless udev is properly setup. The file "41-odvr.rules" (designed for Ubuntu) has the following content:
SUBSYSTEM=="usb", SYSFS{idVendor}=="07b4", SYSFS{idProduct}=="020d", ACTION=="add", GROUP="audio", MODE="0664"
I tried just doing what it said and copying it to "/etc/udev/rules.d" but it didn't seem to work. Looking at other files, I then changed it to:
SUBSYSTEM=="usb", ATTR{idVendor}=="07b4", ATTR{idProduct}=="020d", ACTION=="add", GROUP="audio", MODE="0664"
And now if I do "ls -l /dev/bus/usb/002", I get:
crw-rw-r--. 1 root audio 189, 134 Oct 15 01:21 007
Which seems to suggest that it is running the "41-odvr.rules" file, since lsusb gives:
Bus 002 Device 007: ID 07b4:020d Olympus Optical Co., Ltd Digital Voice Recorder VN-240PC
But odvr still doesn't work as a normal user, giving:
Failed to open Olympus device: couldn't claim interface
My touchscreen "LG Display LGD-MultiTouch" will be recognized sometimes as /dev/input/event0 and sometimes as /dev/input/event3. How to hardcode /dev/input/event0 using udev and xorg.conf?
Code:
# cat /proc/bus/input/devices
I: Bus=0003 Vendor=1fd2 Product=0064 Version=0100
N: Name="LG Display LGD-MultiTouch"
P: Phys=usb-0000:00:1d.7-4.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.1/1-4.1:1.0/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: EV=1b
B: KEY=403 0 30000 0 0 0 0 0 0 0 0
B: ABS=700 3f
B: MSC=10
# udevadm info --query=all --path=/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.1/1-4.1:1.0/input/input0
P: /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.1/1-4.1:1.0/input/input0
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4.1/1-4.1:1.0/input/input0
E: PRODUCT=3/1fd2/64/100
E: NAME="LG Display LGD-MultiTouch"
E: PHYS="usb-0000:00:1d.7-4.1/input0"
E: UNIQ=""
E: EV==1b
E: KEY==403 0 30000 0 0 0 0 0 0 0 0
E: ABS==700 3f
E: MSC==10
E: MODALIAS=input:b0003v1FD2p0064e0100-e0,1,3,4,k110,111,140,141,14A,ra0,1,2,3,4,5,28,29,2A,m4,lsfw
E: SUBSYSTEM=input
Is there any way to pipe video from the screen to a video device that can be used as if it came from a webcam? I assume it uses udev somehow...
View 4 Replies View RelatedI need to prevent udev from creating the /dev/v4l/by-path/* and /dev/v4l/by-id/* files upon connecting my webcam. The problem is that Kopete doesn't want to display the video if these files are present. It works fine if I remove them, but I'd rather not have them created in the first place, since they seem to be completely useless anyway.
View 4 Replies View RelatedMy co-workers and I are trying to develop a USB device, which uses an FTDI chip as a USB-serial controller. The thing is, we would ideally like to set a custom idVendor and idProduct on the FTDI chip. The problem occurs that when we set custom idVendor and idProduct values, udev(7) loads the "usb" driver. If we leave the idVendor and idProduct values to their originals, udev(7) loads the "ftdi_sio" driver. The whole reason for the custom idVendor and idProduct values is so that I can (hopefully) write a udev(7) rule to map that particular device to a specific entry in /dev. Is there a way to write a udev(7) rule so that you can forcefully load a particular driver for a device? Is there something else that could be done to get a similar result?
View 2 Replies View RelatedI have just bought a DVB-T usb dongle to watch some TV. The software I'm using is vdr, which has to be started through the /etc/init.d/vdr service. I have created a udev script that executes the service on device insertion. It works nicely, however now when I boot up the computer it takes ages to get to desktop. I believe it is because of the WAIT_FOR part. But without this part, the service starts too soon because the usb dongle has been inserted but the firmware has not finished loading. Can someone point out an alternative way to do it? The script is here [URL].
View 4 Replies View Relatedhow udev rules work to create device files. Following is what I did for that: Up on plugging in my phone (sony w800i), I am getting a device file 'devcdc-wdm0' created. I just tried to figure out the rule which is responsible for the creation of this particular file.
I searched in 'etcudev ules.d' and 'libudev ules.d' for the string 'cdc-wdm' to find that rule. But I am not getting any hits in that search. Could any one help me out in this one.
BTW: I am using Ubuntu 9
On my debian lenny OS I have an external usb hard disk I would like to automount it at boot. So I edited the /etc/fstab file in order to automount /dev/sdb1. It worked without problem. Then I recompiled the kernel and, as consequence, /dev/sdb1 changed to /dev/sdc1. I started playing with udev in order to match the now called /dev/sdc1 and to change its name in /dev/maxtor (being maxtor the brand of the hard disk). Obviously I edited also /etc/fstab: /dev/sdb1 is now /dev/maxtor.
The boot automount doesn't work anymore. On the boot sequence I can read the message "Mounting local filesystem...mount: special device /dev/maxtor does not exist FAILED". But when I log into the system I can run the command "mount /dev/maxtor /mnt/maxtor" and it works! So, IMHO, my udev rule is correct otherwise also the manual mount wouldn't work, right? I have to tell to udev to create /dev/maxtor BEFORE the boot automount process.
I tried to delete my udev rule and to edit /etc/fstab changing /dev/maxtor in /dev/sdc1 (the name udev gave to my hard disk after kernel recompile, before was /dev/sdb1) and it didn't work: on boot process I always see the "Mounting local filesystem...mount: special device /dev/sdc1 does not exist Failed". Then I tried to change /dev/sdc1 in /dev/sdb1 in /etc/fstab and to reboot with the old original kernel and int this way it works. With my compiled kernel, the OS seems to have lost the capacity to detect my device node correctly.
I am using a 3rd party kernel driver that does not support udev properly. When I was using wheezy I placed the required device files in /lib/udev/devices.
The udev in jessie does not appear to support this. Is there any way to have udev create these device files or will I have to create then using a script at boot-up?
UUIDs make fstab hard to read, so.. Is it possible to use udev rules to prevent HDs to change device, instead of using UUID in /etc/fstab?
View 2 Replies View RelatedI've recently updated my Slackware 13.1 system to the Slackware current. Although I have created my "initrd" image without specifying the "-u" option to "mkinitrd" it still starts up "udev".
That is causing me some difficulty because I am using "dmraid" to detect my RAID arrays. I had created my own device names such as "/dev/sdr2" for my root partition. With 13.1 I had no problem, since "udev" was not started by the "initrd" unless the "-u" option was provided. The current version seems to start up "udev" even without that option.
Is there a way to disable "udev" in the "initrd", or is there a way to specify custom "udev" rules for an "initrd"? I tried placing a "10-local.rules" file in the "etc/udev/rules.d" directory of the "initrd-tree" but that file had no effect on the device names generated by "udev" during the "initrd".
Here is my script that creates the "initrd".
Code:
ROOTDEVNAME="/dev/sdr2"# Name of root device
LINUXVER="2.6.35.7-smp"# Linux modules version
CLIBVER="2.12.1"# C library version
ROOTDIR="/boot/initrd-tree"# Location of root filesystm
[code]....
It will be helpful for me to understand "udev" issues related to an "initrd" because I will eventually try to use "mdadm" instead of "dmraid". So far I have only been able to get my system to boot from the RAID array using "dmraid" and I often run into new problems when I update Linux. Still, Slackware has proven to have the best support for booting from my RAID array because of the user community, documentation and flexibility.
Are there any prerequisites which much be met in order for udev to create /dev/usb/hiddev* nodes?
I have two Slack 13.0 systems, each connected to a APC UPS via USB, one of which creates a hiddev0 node and the other doesn't. apcupsd can't find the UPS unless this node is present.
The "working" system has been stable in its current configuration for so long that I honestly can't remember if I had to tweak anything in this regard. I've verified that it doesn't use any local udev rules to create this node, and to the best of my knowledge there are no external scripts or processes which would create it either.
The non-working system has a similar configuration - no local rules and/or scripts which touch usb devices or nodes.
I'm trying to configure gpsd 2.96 to start automatically from udev rule on a Slack 13.37 box.1. I've compiled and installed gpsd from sources and made sure it starts manually.2. I've copied the /lib/udev/gpsd.hotplug and /lib/udev/gpsd.hotplug.wrapper scripts in their places from the source tree and made them executable.3. I've copied the gpsd.rules file from sources into /etc/udev/rules.d4. I renamed it 99-persistent-gpsd.rules to run late in the bootup process.5. I've copied the /etc/default/gpsd file from sources and made sure it has the right settings inside.
Now, for the results. If I plug the gps usb dongle in while the system runs, it starts gpsd if it is not started, and it connects to it just as it should. But if I start the system with the dongle in, gpsd doesn't get started during boot. I can't find any relevant message in /var/log/syslog or /var/log/messages for boot time. There is stuff there from when I plug the dongle in while the system is running though. It's like udev ignores the rules for it at boot time.Is there something in the Slackware boot scripts that would prevent running those scriptssd.hotplug.wrapper which in turn runs /lib/udev/gpsd.hotplug which is a Python script)?Here is the contents of 99-persistent-gpsd.rules (ignore the comments referring to Debian, it was meant for a Debian box). My usb gps adapter is the first one - the Prolific chipset one:
Code:
# udev rules for gpsd
# $Id: gpsd.rules 5861 2009-08-03 13:41:01Z bzed $
[code]....
I have just installed slack-13.1 on an acer aspire one netbook from a usb stick by booting the install kernel with noudev. I was able to do a complete install including lilo but upon rebooting my boot hangs when encountering my webcam.I see enough info to note the id as 0c45:62c0. This is a microdia webcam which I may be able to do something about later but in the first instance I'd like to be able to boot my system. The bios is very basic and there is no way to disable devices.
View 14 Replies View RelatedThe value of envar PATH for processes run by the udev system is "/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.". If peer review (that's you!) agrees it is a poor choice how can I submit an enhancement request? The man pages do not say anything about bug reporting. Here are reasons why it is a bizarre choice:There is no /gnu/bin directory on as-installed Slackware. /usr/local/bin is empty (or very nearly empty?) on as-installed Slackware. Processes running under udev run as root; having "." in PATH is not good practice when running as root. Processes running under udev are likely to be doing "system" work so executables from the sbin directories are likely to be used. For example, udevadm itself is /sbin/udevadm. Presumably this PATH is set by udevd itself; it is not the PATH in effect when udevd is started by rc.M. AFAIK udevd's PATH is not configurable. The workaround is for processes initiated by udev to set a sane PATH for themselves, perhaps "/usr/sbin:/sbin:/usr/bin:/bin". EDIT: seen on Slackware 13.0 32 bit. EDIT2: rc.udev is run from rc.S, not rc.M as stated above
View 7 Replies View RelatedI just bought a USB hard disk and when I plug it in it gets mounted as owner root and group root. I tried writing a udev rule for it based on the following guide:Nothing seems to work, it always mounts as root. Slackware 13.1, KDE, Dell Optiplex GX280, Western Digital Passport USB 320 gig drive.I am a member of the plugdev group, so it seems to me a rule should not even be necessary.
View 14 Replies View RelatedMy OS are installed as follows:
Windows 7 on /dev/sda1 (primary) type=7 (HPFS/NTFS)
WinXP on /dev/sda2 (primary) type=c (W95 FAT32 (LBA))
Linux on /dev/sda6 (logica1)
I'd like to make Win7 hidden (and deactivated) when booting WinXP from lilo (and conversely). Following the lilo manpage I set up the boot items
# Windows bootable partition config begins
other = /dev/sda1
label = Win7
table = /dev/sda
[Code]....
Line 50 is indicated above. I have experimented with variations on the above, but still can't get lilo to accept my syntax.
For those that use Virtualbox on their slackware host and have a windows (xp) guest running. I have tried various settings for sound (Alsa, PulseAudio), the AC97 drivers are installed in the Windows xp guest os, but there is no sound and there is an unknown audio device (in the windows device manager). If I remove the AC97 drivers and use the soundblaster16 drivers in the Vbox settings there is no unknown sound device, but there's still no sound. why I can't get sound working?
View 13 Replies View RelatedNoticed this on boot up the other day, but it doesn't seem to have a negative effect. Everything appears to be running just fine.
"Triggering udev events: /sbin/udevadm trigger --type=failed"
Is this something that needs to be resolved or ignored?
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
To get started playing with Tomoyo on slackware, are any special tools needed? What about SELinux?
If so, why are they not available on the Slackbuilds repository?
I installed slackware 13.1 x86_64 bit with multilib, and its been about a month already, I'm really enjoying slackware but I am being troubled with my nvidia card, and I need to get my 3D acceleration working. And I've been looking around the net for information and kept on trying to make my nvidia card to work but to no avail. I cant get X to start, once I put in a xorg.conf stating to use the nvidia card. After troubleshooting for almost 2 weeks and now at my wits end, I now come humbly looking for help in linuxquestions slackware community forum.I've installed nvidia 64 bit kernel, drivers from slackbuilds (version 256.44). The laptop model I'm trying to get it working is an -ASUS K52J Intel Core i3 2.40Ghz with 2GB RAM and with an Nvidia Geforce 310M with 1GB dedicated VRAM.
View 14 Replies View RelatedI'm a relatively inexperienced with Linux, coming from a Windows background, and I struggling to solve a troublesome issue attempting to set a static ip address to a Live Debian USB Key. I know it is possible to utilise the 'ifconfig' function to set a static ip address and use 'route' to set the gateway, e.g.
ifconfig eth0 10.0.0.40 up
route add default gw 10.0.0.130 eth0
..however in both cases I need to explicitly set the 'eth0' to point at the appropriate adapter. However, this is where my problem is...
I'm creating a persistent USB key using the Debian Live CD, I'm going to create an image and then duplicate that image to a load of other USB keys. Again, not a problem as such but there are cases where I need to specify a static IP address and gateway rather than using DCHP.
And here's where problem raises its head.
Because I've created the key on another machine it has allocated 'eth0' to a specific MAC Address (assigned in /etc/udev/70-persistent-net.rules) but when I place it into machine with a different network adapter it is assigning to 'eth1' (and this increments up).
a) call 'ifconfig' and 'route' without having to identify the adapter or
b) change the script that is creating '/etc/udev/70-persistent-net.rules' so it overwrites the 'eth0' entry with the only applicavle network adapter for the current hardware.
Kernel 2.6.21.5, GNU (slackware 12.0).
KDE 3.5.7.
MPlayer 1.0rc2-4.1.2.
I have a .avi file on the hard (really on a cd-rom, but it's just the same). Being in the GUI (KDE), I do Main Menu>Run Command and then, in the dialog box, I enter 'gmplayer foo.avi'. Gmplayer starts, the picture of a small console is seen on the screen, and the audio from the movie is heard. Just as if I had inserted the CD into a stand alone dvd player but I could not see the image. I compiled and installed mplayer (with GUI support) from the slackbuilds.org sources and script for slackware 12.0, which is the slack version installed in my machine. If I open a terminal (in the GUI) and run gmplayer there I get this:
Code:
VIDEOOUT: [VO_XV] It seems there is no Xvideo support for your video card available.
[VO_XV] Run 'xvinfo' to verify its Xv support and read
[VO_XV] DOCS/HTML/en/video.html#xv!
[VO_XV] See 'mplayer -vo help' for other (non-xv) video out drivers.
[VO_XV] Try -vo x11.
CPLAYER: Error opening/initializing the selected video_out (-vo) device.
I know I could do what is suggested by gmplayer but, before that, perhaps I am simply invoking gmplayer in the wrong way. That is: there are at least to ways: using the Run Command dialog box and opening a terminal and running as a cli command.