After update Udev rule ignored: loading firmware of HP LJ 1020

Hi all
After one of the latest updates I have a problem with the udev rules. It worked some weeks ago perfectly. But after some updates of the past weeks it seems, that the rules in /etcudev/rules.d/11-hp-lj1020.rules are not triggered anymore. I cannot tell you the precise date as I update my mom's computer via ssh from another country and my mom told me weeks after that the printer is not working any more.
Was there any update of the udev package which is causing problems?
I read some threads and had also the problem, that renaming my network adapters does not work any more.
Issue was that "name" is deprecated in udev.
Best regards
Martin

Potomac wrote:
check these bugreports :
https://bugs.archlinux.org/task/42505
https://bugs.archlinux.org/task/42353
it seems that this bug related to i915 chip ( or intel graphic card ) is fixed in kernel 3.18rc3 mainline ( we can find this kernel package in AUR )
there is also another and complete different bug when we use a kernel 3.17 and even 3.18 ( it's a random bug ) but with a similar effect : boot can hang ( the boot process suddenly stops ) :
https://bbs.archlinux.org/viewtopic.php?id=189622
https://bbs.archlinux.org/viewtopic.php?id=189324
downgrading to kernel 3.16.x is the workaround
I assume my computer is affected by one of these bugs. While I can get to the point where my window manager is loaded, everything almost immediately hangs (but doesn't freeze). Terminal windows become non-responsive and Chromium will refuse input. It's very weird. This happens with both of the 3.17 kernel updates but not in any of the 3.16 releases (including 3.16.7).
This is on an AMD system (cpu/gpu w/ open source driver). Overall 3.17 seems rather buggy.

Similar Messages

  • After update udev mounts all partitions automatically (but shoudn`t)

    Here goes: after updating udev from 167-2 to 168-1, it started mounting all partition at boot. No rules (the list and the rules are the default ones) seem to include this, and google said automounting MUST be set up by user.
    Downgrading fixes the issue, but I try to keep the system up to date, so this is not an option. Also I do not want to disable udisk mounting by polkit, since I want to keep the option of mounting them via KDE.
    Can anyone help please?
    P.S. arch x68_64
    Last edited by levantis (2011-05-17 16:05:35)

    same here...
    i changed the 'pass' value in the /etc/fstab to "0" for the mounted devices - this works temporarily for me so i can boot up the system.
    excuse me for my bad english

  • Can't get the right contacts and photos back on my phone after updating software, it has loaded my old iPhone 3GS contacts and apps that we're in the iTunes library , how can I get my new stuff back

    How do I get my contacts and photos back for my iPhone 4 , after updating to ios5 it loaded my old phones info so I lost contacts messages and photos an video

    Hello johnohuk,
    Thanks for the question. It sounds like most of your music was purchased from the iTunes Store. If your country supports iTunes in the Cloud, you can download your past purchases using this article:
    Downloading past purchases from the App Store, iBookstore, and iTunes Store
    http://support.apple.com/kb/HT2519
    Thanks,
    Matt M.

  • After update, Itunes can't load. I get error message R6034, attempt to load the C runtime library incorrectly. I have repeatedly removed and reinstalled Itunes and still have the same problem!!!

    After update, Itunes can't load. I get error message R6034, attempt to load the C runtime library incorrectly.
    I also get error code 7 (Windows error 1114), saying itunes wasn't installed correctly. It appears that I am not the only one with this issue. what is wrong with the latest update?? I tried removing Itunes and all of its components and installing it again, but get same errors and i have also tried doing a system restore with the same results

    Doublechecking. Have you also tried the following user tip?
    Troubleshooting issues with iTunes for Windows updates

  • After updating Firefox does not Load all it says XU.DLL not found

    after updating Firefox does not Load all it says XU.DLL not found

    xul.dll
    look here:
    https://support.mozilla.com/en-US/questions/754567
    https://support.mozilla.com/en-US/questions/756149
    thank you

  • Udev update: udev.rules file contains errors [was: dbus+hal update]

    I am aware of the fact that there are already a few topics and a bug report (http://bugs.archlinux.org/task/6351) concerning the recent dbus & hal upgrades. However, my case seems different and more complex. I am not even sure if this is directly related to the others' issues.
    Since the update to dbus-1.0.2-2 my system does not follow some dbus rules any more. The recent follow-up update to dbus-1.0.2-3 did not remedy my problems, either.
    I think that this is due to the /etc/udev/rules.d/udev.rules file having become corrupted with the recent updates. Under the sections
    #pty and tty legacy devices
    and
    #vc devices
    several KERNEL=[...] lines have errors, at least the final double quotation marks are missing!
    So far my problems are as follows:
    - Intel i810 video driver fails to load: "No matching device [...] found".
    - Thinkpad's nvram is not get created in /dev
    - no pty devices / no ttyp devices are created in /dev. Therefore, none of my X-based consoles will start. Konsole, for example, exits with "Konsole is unable to open a PTY [...]".
    I will investigate further and report. Anyone eslse experiencing similar problems?
    Btw., contrary to the experience of others, removable devices are recognized and mounted.
    Last edited by mutlu_inek (2007-02-07 02:52:34)

    Those errors I found were actually introduced a few days ago by udev-105-1! The /etc/udev/rules.d/udev.rules provided by that package has errors!
    Correcting those errors brought back my beloved pseudo teletypes in /dev/pts/X. But the nvram device is still not created.
    Update:
    Here is the diff output of udev-105-1's udev.rules compared with what it should be:
    --- udev.rules 2007-02-06 21:20:06.000000000 -0500
    +++ udev.rules_corrected 2007-02-06 21:16:36.000000000 -0500
    @@ -143,8 +143,8 @@
    SUBSYSTEMS=="scsi", KERNEL=="sg[0-9]*", ATTRS{type}=="6", GROUP="scanner"
    # pty and tty legacy devices
    -KERNEL=="pty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule
    -KERNEL=="tty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule
    +KERNEL=="pty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule"
    +KERNEL=="tty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule"
    # md block devices
    KERNEL=="md[0-9]*", NAME="md%n", SYMLINK+="md/%n"
    @@ -166,8 +166,8 @@
    KERNEL=="vcs[0-9]*", NAME="vcc/%n", OPTIONS="last_rule"
    KERNEL=="vcsa", NAME="vcc/a0", OPTIONS="last_rule"
    KERNEL=="vcsa[0-9]*", NAME="vcc/a%n", OPTIONS="last_rule"
    -KERNEL=="ptmx", MODE="0666", OPTIONS="last_rule
    -KERNEL=="tty", MODE="0666", OPTIONS="last_rule
    +KERNEL=="ptmx", MODE="0666", OPTIONS="last_rule"
    +KERNEL=="tty", MODE="0666", OPTIONS="last_rule"
    # video devices
    SUBSYSTEM=="video4linux", GROUP="video"
    Last edited by mutlu_inek (2007-02-07 02:44:24)

  • Macbook 2.4 2008 after update 10.6.8 and firmware, won't fully boot

    Weird problem after updating to 10.6.8 from 10.6.0 (fresh install).
    I went thru Software Update, it downloaded 10.6.8 and the other updates. It also found that I needed a Firmware Update, which I also choose to install.
    The updates went thru okay, including the Firmware. Everything went exactly as it should. The machine booted as per normal.
    Afterwards, I checked that it had updated normally to 10.6.8 and everything checked out okay. 
    I left the Macbook plugged in and in Sleep. It was like this for probably 24 hours. NO BATTERY INSTALLED (don't know if this could be a problem, but I don't see how). I just came back now to find that I can't get back to the desktop from Sleep, nor can I boot to the desktop.
    Specifically, here's what I see:
    - first, on trying to Wake from Sleep, the screen remained black. The Superdrive spun up, the white light at the front of the Macbook was pulsing. But no desktop.
    - I then held the Power button till it shut down. Then rebooted. And here's what I got:
    a) no startup chime
    b) I could Superdrive and fans and HD spin up
    c) the display turned on, but didn't show the startup screen, no Apple logo, etc. It just went to the Desktop in about 10-15 seconds.
    d) on the Desktop I can see:
    - the Desktop background
    - the Disk Utility window open to Repair Permissions, which was the last thing I'd done on the Macbook (permissions checked out okay)
    - and THIS: I've never seen it before, but the Desktop is a bit "fuzzy", I can see the background and the Disk Utility window though, as well as a NUMBER OF SHORT BARS towards the bottom of the screen, and there's a BAR BY BAR PROGRESS from left to right (the first bar is filled in, then the second, etc.), BUT the progress DOESN'T make it to the last bar before the SCREEN GOES BLACK AGAIN  (*sorry for the caps, but I'm trying to highlight the salient parts).
    Any ideas?
    Is this somehow related to the Firmware update? I remember that the Macbook booted fine after the Firmware update, the long horizontal progress bar was filled in as normal and got to the end; IIRC the Macbook then booted fine. I believe it was at this point that I repaired Permissions. Then left the Macbook, only to return to find it as it is now.
    Any help much appreciated.

    Update:
    Installed 10.6 and did all the updates, am now using it with an external monitor. Working fine as a Mini, but a real bummer re. the black or blue screen.
    Without external monitor connected, I get this:
    - I can boot, with startup chime, from DVD or external hard disk, after holding Option at startup and choosing bootable volume on screen; I can also boot from the DVD by holding down C key
    - When I boot, the startup chime doesn't sound right away, as there's a short delay; in that time (a few seconds), the LED light at the front of the Macbook FLASHES 5 TIMES; there are NO error beep sounds
    - The boot screen starts up, I get Apple logo and spinning wheel, and at about the usual point where the screen goes blue for a couple seconds, before the Macbook boots to the desktop, the screen goes black
    - The Macbook seems to go to Sleep, with the screen black; the front light pulses
    - I can wake the Macbook from Sleep by pressing a key
    - Previously, after waking from Sleep, the Macbook went to the desktop -> in other words, the Macbook completed startup with the black screen;
    - When the Macbook woke from Sleep, there was a slight delay of a few seconds before the Trackpad and Keyboard became active; I then had a few seconds to use the Trackpad before the screen went black again, and the Macbook went back to Sleep
    - Now, though, when I wake it from Sleep, I get a Blue Screen, and the screen stays blue; i.e., doesn't turn black and the Macbook doesn't sleep
    All of this refers to booting the Macbook without an external monitor connected.
    When booting with an external monitor, everything works normally.
    POINTS OF PARTICULAR INTEREST:
    1) all of this happened from the time I updated the Firmware, as per Software Update
    2) the screen works during the boot process, then goes black
    3) boot completes even with black screen
    4) the screen works for a 10 seconds when Macbook wakes from Sleep, then goes black again
    5) now, the screen goes blue - and stays there - when the Macbook wakes from Sleep
    6) Macbook works normally with external monitor; the Macbook's internal display is not recognized when an external monitor is connected; the iSight camera is not recognized
    So, what the heck happened?
    I can understand the internal display and/or onboard video getting broken, but then it should simply not work at all, right? How is it that it works "partially" or "temporarily", during boot and when waking from Sleep, before going black?
    What is with the 5 flashing LEDs at boot or when waking from Sleep? (I can't find any info concerning the Macbook and 5 flashing LEDs, but only concerning the Macbook Air, and it refers to a battery problem).

  • After updating the MACBOOK AIR SMC FIRMWARE UPDATE 1.9 so many times still can see update? How to get rid of this one please help.

    After updating OS X Mavericks MacBook Air SMC Firmware Update 1.9 so many times (restarted more than 10times) but then still cannot update? Please help.

    Here it is...
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *121.3 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS MACintosh HD            120.5 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    do I need to disable the FlieVault?

  • After update, firefox doesn't load any site, not even home page. tried older version, same . what's wrong

    auto update to FF5. no home page displayed(about blank), won't load any page from bookmarks. I un-installed and re-installed FF3.6. still won't load any web sites, bookmarked, homepage or others typed in. Chrome and IE still work so not connection or PC fault. I have tried changing proxy, and all other suggestions in your help pages, no effect.
    HP Pavillion6300UK running Win XP sp3.5 all updates in place, drivers etc up to date.

    It seems that '''every'''solution want to begin with "start Firefox in safe mode" and then check your addons/plugins one at a time. This is extremely time consuming and irritating. I'm almost at the point of looking for other browsers.

  • Iphone not working after update to 3.1.3 firmware

    Can someone help?I purchased iphone in USA (I live in U.K.)Got it to work in U.K. on O2 using correct sim, etc. Updated to firmware 3.1.3 now all I get when I enter iTunes is a message "The sim card inserted in this iphone does not appear to be supported" Can anyone help resolve this issue so I can use my beloved iphone again?

    The iPhone is sold in the U.S. as carrier locked with AT&T only. If you are using an O2 SIM card with the iPhone, this means your iPhone was hacked to be unlocked. Installing a firmware update on a carrier locked iPhone that has been hacked to be unlocked re-locks the iPhone to the designate carrier the iPhone was sold as carrier locked with - in this case with AT&T, and the same applies when restoring such an iPhone with iTunes if wanted or needed.
    Hacking a carrier locked iPhone to unlock it or for any reason is against Apple's license agreement for the iPhone, is not supported by Apple directly or indirectly via these discussions, and voids the warranty.

  • After updating flash player, youtube loads very slow

    Youtube videos load very slowly since I updated flash player.  Once they are loaded, they play ok, but I cannot skip ahead, etc.

    Andy..
    Keep in mind, you can't "skip ahead" any farther then the video has buffered but try the following since it loads slow.
    Uninstall your current copy of the Flash plugin then reinstall then restart your Mac  >  Troubleshoot Flash Player | Mac OS
    And if you haven't done so, empty the Safari cache. From your Safari menu bar click Safari > Empty Cache
    You can also try resetting Safari. Back to the menu bar click Safari > Reset Safari
    Select the top 5 buttons, click Reset.
    Quit then relaunch Safari... try a video.
    And make sure your system software is up to date. Click your Apple menu > Software Update...

  • After updating to Mavericks imac loads but nothing opens

    I have loaded Mavericks and followed the details exactly. Now when I boot up my computer may open fully or only partially. When open clicking on any application or function: eg drive, setup, mail etc. they do not open. Force quit is not available. I have booted up and used the emergency drive and scanned my HD with no errors.I have also reloaded a fresh download with no success, I am now at a loss.
    Les

    Both of those need to be removed.
    MacKeeper is just plain crap. Avoid at all costs.
    Kaspersky is okay (not great), when it comes to detecting Mac malware, but the company has had some issues with their Mac software in the recent past, including one tool that locked people out of their user accounts. I would bet it isn't compatible with Mavericks.
    Of course, if you can't actually start up the computer anymore, removing them may be tricky. Try restarting in safe mode. If you can do that, then try uninstalling from there. The disk image file containing the Kaspersky installer also contains an uninstaller... if you no longer have that disk image file, you'll need to re-download Kaspersky. MacKeeper should delete itself when dragged to the trash, but that won't work in safe mode, so I would wait and uninstall MacKeeper once you have restarted normally (if possible).

  • UDev rules not working for MidiSport 2x2 usb midi device

    I installed arch a couple of months ago and am loving it so far.  Any problems I've had so far have already been solved in the forums, but this one's really got me.  I have a MidiSport 2x2 that I want the firmware to be loaded on everytime I plug it in.  I installed (there's not an arch package) a package that is supposed to do just that.  (It's called midisport-firmware-1.2.tar.gz).  However, the package seems to be out of date (2006) and I even had to modify a couple places in the configure script to get it to work with current program revisions.  However, once installed, it does nothing.  It installed firmware files and udev rules for the device into a couple of directories.  When I run the command that is supposed to load the firmware, it works fine.  But for some reason, (I even checked the udev kernel log) it's like the event isn't even being triggered.  Here's part of the original file that came with the package that's supposed to load the firmware:
    # midisport-firmware.rules - udev rules for loading firmware into MidiSport devices
    # DEVPATH=="/*.0" selects interface 0 only
    # (some udev versions don't work with SYSFS{bInterfaceNumber})
    # MidiSport 2x2
    ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1001/*", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport2x2.ihx"
    # vim: ft=conf
    And here's what I modified it to in an attempt to make it work:
    # MidiSport 2x2
    ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0763", ATTR{idProduct}=="1001", RUN+="/sbin/fxload -D /dev/%k -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport2x2.ihx"
    I would really appreciate help from anyone who knows about this kind of thing, as I can't figure out what's going wrong.  If it's something wrong with the config, please let me know.  Actually, some HAL events popped up when I was testing this out.  Is it possible HAL is blocking  the udev event somehow?

    Hi,
    The firmware files must be put in /lib/firmware so they can be found by the kernel. Are they being put there?

  • Udev-182 cannot find firmware (even long after boot)

    Hello.
    After upgrading to kernel v3.3.2 with udev 182, I began experiencing issues with my video card and WiFi adapter.
    The cause seems to be similar in both cases: udev can not load firmware at boot time, returning –2 (ENOENT, file not found).
    These issues cannot be worked around by blacklisting the corresponding drivers and modprobe`ing them manually after login.
    Well, I`m okay with WiFi not working, since I don`t use it, but the video card is really a trouble.
    How can I make udev do its job?
    [UPD:] Last configuration known to be working is kernel 3.1.6 + udev 175.
    Last edited by hidefromkgb (2012-04-22 10:19:05)

    Got the logs.
    udev-175, loading successful:
    monitor will print the received events for:
    UDEV - the event which udev sends out after rule processing
    KERNEL - the kernel uevent
    KERNEL[137.359168] add /module/drm (module)
    UDEV [137.360121] add /module/drm (module)
    KERNEL[137.360329] add /class/drm (class)
    UDEV [137.360766] add /class/drm (class)
    KERNEL[137.369536] add /module/ttm (module)
    UDEV [137.370098] add /module/ttm (module)
    KERNEL[137.370199] add /devices/virtual/drm/ttm (drm)
    UDEV [137.370657] add /devices/virtual/drm/ttm (drm)
    KERNEL[137.386391] add /module/drm_kms_helper (module)
    UDEV [137.386674] add /module/drm_kms_helper (module)
    KERNEL[137.389947] add /module/i2c_algo_bit (module)
    UDEV [137.390197] add /module/i2c_algo_bit (module)
    KERNEL[137.429511] add /module/radeon (module)
    UDEV [137.429875] add /module/radeon (module)
    KERNEL[137.431450] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/controlD64 (drm)
    UDEV [137.432063] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/controlD64 (drm)
    KERNEL[137.432289] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [137.435090] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[137.440187] add /devices/platform/radeon_cp.0 (platform)
    KERNEL[137.440515] add /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    UDEV [137.443355] add /devices/platform/radeon_cp.0 (platform)
    KERNEL[137.474411] remove /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    KERNEL[137.474433] remove /devices/platform/radeon_cp.0 (platform)
    UDEV [137.474823] remove /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    KERNEL[137.474993] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-1 (i2c)
    KERNEL[137.475045] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-2 (i2c)
    KERNEL[137.475087] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-3 (i2c)
    KERNEL[137.475133] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-4 (i2c)
    KERNEL[137.475182] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-5 (i2c)
    KERNEL[137.476059] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-6 (i2c)
    KERNEL[137.476110] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-7 (i2c)
    KERNEL[137.476189] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-VGA-1 (drm)
    KERNEL[137.476212] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[137.476245] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1 (drm)
    KERNEL[137.476266] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[137.476302] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-SVIDEO-1 (drm)
    KERNEL[137.476322] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[137.476362] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-HDMI-A-1 (drm)
    KERNEL[137.476382] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [137.478088] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-1 (i2c)
    UDEV [137.478404] add /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    UDEV [137.478664] remove /devices/platform/radeon_cp.0 (platform)
    UDEV [137.479559] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-7 (i2c)
    UDEV [137.479953] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-VGA-1 (drm)
    UDEV [137.480315] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-6 (i2c)
    UDEV [137.480807] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-5 (i2c)
    UDEV [137.481700] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-3 (i2c)
    UDEV [137.482415] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-2 (i2c)
    UDEV [137.483656] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-4 (i2c)
    UDEV [137.485911] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [137.485934] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1 (drm)
    UDEV [137.487808] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [137.488516] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-SVIDEO-1 (drm)
    UDEV [137.490963] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [137.491547] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-HDMI-A-1 (drm)
    UDEV [137.494345] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[137.876104] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/graphics/fb0 (graphics)
    KERNEL[137.876185] add /devices/virtual/vtconsole/vtcon1 (vtconsole)
    UDEV [137.876973] add /devices/virtual/vtconsole/vtcon1 (vtconsole)
    UDEV [137.877776] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/graphics/fb0 (graphics)
    KERNEL[138.299777] add /bus/pci/drivers/radeon (drivers)
    UDEV [138.300324] add /bus/pci/drivers/radeon (drivers)
    udev-182, loading failed:
    monitor will print the received events for:
    UDEV - the event which udev sends out after rule processing
    KERNEL - the kernel uevent
    KERNEL[56.109948] add /module/drm (module)
    UDEV [56.111092] add /module/drm (module)
    KERNEL[56.111109] add /class/drm (class)
    UDEV [56.111425] add /class/drm (class)
    KERNEL[56.127481] add /module/ttm (module)
    KERNEL[56.128096] add /devices/virtual/drm/ttm (drm)
    UDEV [56.128654] add /devices/virtual/drm/ttm (drm)
    UDEV [56.128670] add /module/ttm (module)
    KERNEL[56.141079] add /module/drm_kms_helper (module)
    UDEV [56.141589] add /module/drm_kms_helper (module)
    KERNEL[56.144582] add /module/i2c_algo_bit (module)
    UDEV [56.145047] add /module/i2c_algo_bit (module)
    KERNEL[56.182954] add /module/radeon (module)
    UDEV [56.183397] add /module/radeon (module)
    KERNEL[56.184921] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/controlD64 (drm)
    UDEV [56.185548] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/controlD64 (drm)
    KERNEL[56.185782] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[56.191614] add /devices/platform/radeon_cp.0 (platform)
    KERNEL[56.191645] add /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    UDEV [56.193681] add /devices/platform/radeon_cp.0 (platform)
    UDEV [56.193701] add /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    UDEV [56.207714] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[116.533562] remove /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    KERNEL[116.533590] remove /devices/platform/radeon_cp.0 (platform)
    UDEV [116.534923] remove /devices/platform/radeon_cp.0/firmware/radeon_cp.0 (firmware)
    KERNEL[116.534947] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-1 (i2c)
    KERNEL[116.534965] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-2 (i2c)
    KERNEL[116.534982] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-3 (i2c)
    KERNEL[116.535040] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-4 (i2c)
    KERNEL[116.535297] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-5 (i2c)
    KERNEL[116.535387] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-6 (i2c)
    KERNEL[116.535481] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-7 (i2c)
    KERNEL[116.535615] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-VGA-1 (drm)
    KERNEL[116.535690] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[116.535774] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1 (drm)
    KERNEL[116.535846] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[116.535927] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-SVIDEO-1 (drm)
    KERNEL[116.535996] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[116.536087] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-HDMI-A-1 (drm)
    KERNEL[116.536155] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [116.536212] remove /devices/platform/radeon_cp.0 (platform)
    UDEV [116.538030] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-3 (i2c)
    UDEV [116.538419] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-4 (i2c)
    UDEV [116.539242] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-5 (i2c)
    UDEV [116.539424] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-1 (i2c)
    UDEV [116.542050] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-VGA-1 (drm)
    UDEV [116.542591] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-2 (i2c)
    UDEV [116.542923] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-7 (i2c)
    UDEV [116.543318] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/i2c-6 (i2c)
    UDEV [116.545169] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [116.545739] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-LVDS-1 (drm)
    UDEV [116.548464] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [116.549043] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-SVIDEO-1 (drm)
    UDEV [116.551679] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    UDEV [116.552250] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-HDMI-A-1 (drm)
    UDEV [116.554882] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 (drm)
    KERNEL[116.939188] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/graphics/fb0 (graphics)
    KERNEL[116.939233] add /devices/virtual/vtconsole/vtcon1 (vtconsole)
    UDEV [116.939712] add /devices/virtual/vtconsole/vtcon1 (vtconsole)
    UDEV [116.940369] add /devices/pci0000:00/0000:00:01.0/0000:01:00.0/graphics/fb0 (graphics)
    KERNEL[117.357796] add /bus/pci/drivers/radeon (drivers)
    UDEV [117.358492] add /bus/pci/drivers/radeon (drivers)

  • [SOLVED] udev rule no longer working

    I have a udev rule set up to automatically mount an ext4 filesystem when I plug a certain thumb drive in.  It was working fine until yesterday (probably due to updates).  Here is the rule, in file /etc/udev/rules.d/99-gfk.rules:
    KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", SYMLINK+="gfshare"
    ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mkdir /media/gfshare"
    ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mount -t ext4 -o ro,nosuid,nodev,noexec,noatime /dev/gfshare /media/gfshare"
    The symlink and the mkdir command are both working fine, but the mount command is not being run for some reason.  If I manually run the mount command it works fine.  Some possibly helpful output:
    # pacman -Qo $(which udevadm)
    /usr/bin/udevadm is owned by systemd 212-1
    # dmesg |tail -16
    [26458.120628] usb 7-1.3: new high-speed USB device number 7 using ehci-pci
    [26458.223059] usb-storage 7-1.3:1.0: USB Mass Storage device detected
    [26458.223825] scsi10 : usb-storage 7-1.3:1.0
    [26459.311607] scsi 10:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 4
    [26460.834081] sd 10:0:0:0: [sdd] 15240576 512-byte logical blocks: (7.80 GB/7.26 GiB)
    [26460.834931] sd 10:0:0:0: [sdd] Write Protect is off
    [26460.834935] sd 10:0:0:0: [sdd] Mode Sense: 23 00 00 00
    [26460.835617] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.835621] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.839455] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.839460] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.860579] sdd: sdd1 sdd2
    [26460.867111] sd 10:0:0:0: [sdd] No Caching mode page found
    [26460.867115] sd 10:0:0:0: [sdd] Assuming drive cache: write through
    [26460.867118] sd 10:0:0:0: [sdd] Attached SCSI removable disk
    [26461.041982] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: (null)
    # udevadm test /sys/bus/usb/devices/7-1.3
    calling: test
    version 212
    This program is for debugging only, it does not run any program
    specified by a RUN key. It may show incorrect results, because
    some values may be different, or not available at a simulation run.
    load module index
    timestamp of '/etc/systemd/network' changed
    timestamp of '/usr/lib/systemd/network' changed
    Parsed configuration file /usr/lib/systemd/network/99-default.link
    Created link configuration context
    timestamp of '/etc/udev/rules.d' changed
    Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
    read rules file: /usr/lib/udev/rules.d/10-dm.rules
    read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
    read rules file: /etc/udev/rules.d/12-android.rules
    read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
    read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
    read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
    read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
    read rules file: /usr/lib/udev/rules.d/50-firmware.rules
    read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
    read rules file: /usr/lib/udev/rules.d/51-android.rules
    read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
    read rules file: /usr/lib/udev/rules.d/60-drm.rules
    read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
    read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
    read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules
    read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
    read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
    read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
    read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
    read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
    read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
    read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
    read rules file: /usr/lib/udev/rules.d/70-infrared.rules
    read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
    read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
    read rules file: /usr/lib/udev/rules.d/71-seat.rules
    read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
    read rules file: /usr/lib/udev/rules.d/75-net-description.rules
    read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
    read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
    read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
    read rules file: /usr/lib/udev/rules.d/80-drivers.rules
    read rules file: /etc/udev/rules.d/80-net-setup-link.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
    read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
    read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
    read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
    read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
    read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
    read rules file: /etc/udev/rules.d/99-gfk.rules
    read rules file: /usr/lib/udev/rules.d/99-systemd.rules
    read rules file: /usr/lib/udev/rules.d/kino.rules
    rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
    10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
    IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/50-udev-default.rules:9
    IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:9
    MODE 0664 /usr/lib/udev/rules.d/50-udev-default.rules:37
    GROUP 1002 /usr/lib/udev/rules.d/51-android.rules:387
    MODE 0660 /usr/lib/udev/rules.d/51-android.rules:387
    RUN '/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass} vboxusers' /usr/lib/udev/rules.d/60-vboxdrv.rules:6
    PROGRAM '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' /usr/lib/udev/rules.d/69-libmtp.rules:1204
    starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'
    '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'(out) '0'
    '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' [24644] exit with return code 0
    IMPORT builtin 'path_id' /usr/lib/udev/rules.d/71-seat.rules:43
    RUN 'uaccess' /usr/lib/udev/rules.d/73-seat-late.rules:15
    handling device node '/dev/bus/usb/007/007', devnum=c189:774, mode=0660, uid=0, gid=1002
    preserve permissions /dev/bus/usb/007/007, 020660, uid=0, gid=1002
    preserve already existing symlink '/dev/char/189:774' to '../bus/usb/007/007'
    ACTION=add
    BUSNUM=007
    DEVNAME=/dev/bus/usb/007/007
    DEVNUM=007
    DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3
    DEVTYPE=usb_device
    DRIVER=usb
    ID_BUS=usb
    ID_DRIVE_THUMB=1
    ID_FOR_SEAT=usb-pci-0000_00_1a_7-usb-0_1_3
    ID_MODEL=DataTraveler_2.0
    ID_MODEL_ENC=DataTraveler\x202.0
    ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    ID_MODEL_ID=6545
    ID_PATH=pci-0000:00:1a.7-usb-0:1.3
    ID_PATH_TAG=pci-0000_00_1a_7-usb-0_1_3
    ID_REVISION=0100
    ID_SERIAL=Kingston_DataTraveler_2.0_1C6F654E4041ED601910053F
    ID_SERIAL_SHORT=1C6F654E4041ED601910053F
    ID_USB_INTERFACES=:080650:
    ID_VENDOR=Kingston
    ID_VENDOR_ENC=Kingston
    ID_VENDOR_FROM_DATABASE=Toshiba Corp.
    ID_VENDOR_ID=0930
    MAJOR=189
    MINOR=774
    PRODUCT=930/6545/100
    SUBSYSTEM=usb
    TAGS=:seat:uaccess:
    TYPE=0/0/0
    USEC_INITIALIZED=26452326568
    adb_user=yes
    run: '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 774 00 vboxusers'
    run: 'uaccess'
    unload module index
    Unloaded link configuration context
    # udevadm test /sys/bus/usb/devices/7-1.3:1.0
    calling: test
    version 212
    This program is for debugging only, it does not run any program
    specified by a RUN key. It may show incorrect results, because
    some values may be different, or not available at a simulation run.
    load module index
    timestamp of '/etc/systemd/network' changed
    timestamp of '/usr/lib/systemd/network' changed
    Parsed configuration file /usr/lib/systemd/network/99-default.link
    Created link configuration context
    timestamp of '/etc/udev/rules.d' changed
    Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
    read rules file: /usr/lib/udev/rules.d/10-dm.rules
    read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
    read rules file: /etc/udev/rules.d/12-android.rules
    read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
    read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
    read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
    read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
    read rules file: /usr/lib/udev/rules.d/50-firmware.rules
    read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
    read rules file: /usr/lib/udev/rules.d/51-android.rules
    read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
    read rules file: /usr/lib/udev/rules.d/60-drm.rules
    read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
    read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
    read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
    read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules
    read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
    read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
    read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
    read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
    read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
    read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
    read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
    read rules file: /usr/lib/udev/rules.d/70-infrared.rules
    read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
    read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
    read rules file: /usr/lib/udev/rules.d/71-seat.rules
    read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
    read rules file: /usr/lib/udev/rules.d/75-net-description.rules
    read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
    read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
    read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
    read rules file: /usr/lib/udev/rules.d/80-drivers.rules
    read rules file: /etc/udev/rules.d/80-net-setup-link.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks.rules
    read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
    read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
    read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
    read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
    read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
    read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
    read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
    read rules file: /etc/udev/rules.d/99-gfk.rules
    read rules file: /usr/lib/udev/rules.d/99-systemd.rules
    read rules file: /usr/lib/udev/rules.d/kino.rules
    rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
    10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
    IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:11
    RUN 'kmod load $env{MODALIAS}' /usr/lib/udev/rules.d/80-drivers.rules:5
    ACTION=add
    DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3/7-1.3:1.0
    DEVTYPE=usb_interface
    DRIVER=usb-storage
    ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    ID_VENDOR_FROM_DATABASE=Toshiba Corp.
    INTERFACE=8/6/80
    MODALIAS=usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00
    PRODUCT=930/6545/100
    SUBSYSTEM=usb
    TYPE=0/0/0
    USEC_INITIALIZED=452326811
    run: 'kmod load usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00'
    unload module index
    Unloaded link configuration context
    Last edited by bentglasstube (2014-04-03 20:51:36)

    I see.  That is somewhat aggravating but I will find another way to achieve what I wanted I suppose.
    Thank you.  Should I mark this is solved or unsolvable or something?  Sorry, I'm new to posting on these forums.
    Edit:  I was able to achieve what I wanted with udevil as recommended by the wiki.
    Last edited by bentglasstube (2014-04-03 20:55:45)

Maybe you are looking for

  • Changing time stamp format in the file receiver adapter file name

    Hi all, How can we change the standard date time stamp from filename_yyyymmdd-hhmmss-mil to filename_yymmdd_hhmmss i.e.,  I want "underscores" instead of "hyphens" and also I do not want the MilliSeconds. I read in the forums that I have to use the c

  • Events on iPod calendar off by 1 hour

    I just started syncing my iCal to my 5G iPod. All the events on the iPod calendar show up one hour early. I verified my iPod time is set to Pacific timezone & that Daylight Savings Time is off. I verified my computer time is set to PST. I tried setti

  • Populate choice component  with   2 primary key  in table

    There are 2 primary key in table. When I create my uix with jheadstart, the UIXs don't populate choice component. How can I create automatically populate choice component, with 2 PK in table?

  • Using java to retrieve windows password

    Is there any way to get Java to retrieve the windows password?

  • Linux 1Z0-100 (OCA) and 1Z0-105 (OCP) beta

    I think to take beta OCA 1Z0-100. I worked several years with Linux, but my know how not up2date (6 years break). Are there any objectives or example questions? Is the exams comparable with OCA Solaris (the same simple?)? Second question: will there