Debian Configuration :: Udev Warning Messages At Boot After Upgrade?
Apr 23, 2011I've done an upgrade from lenny to squeeze.Now, I'm getting a lot of udev warning messages at the boot time.Knows someone howto remove them?
View 6 RepliesI've done an upgrade from lenny to squeeze.Now, I'm getting a lot of udev warning messages at the boot time.Knows someone howto remove them?
View 6 RepliesAfter yesterdays upgrade of Squeeze, my Synaptics touchpad's udev configuration is ignored on my EeePC. It was working fine before. Are there any changes in how it is supposed to be configured or is it just broken?
View 3 Replies View RelatedJust upgraded (libudev0 and related) and system fails to mount other partitions, gives a lot of errors and drops to single mode.
View 14 Replies View RelatedDebian testing: Kernel: Linux 2.6.32-5-amd64I can now only boot into safemode because I cannot get these 4 packages to upgrade:
udev
media-player-info
xserver-xorg-core
[code]....
i'm heaving the following message at boot time: "Starting udev: udevd[114]: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it
View 6 Replies View RelatedAn issue that has been hassling me for years since I started using Linux (Debian!) is related to the boot messages that quickly scroll on the video during the boot process. The main hassle is related to the fact that I cannot get a log of those messages. The second hassle is due to the fact that with my brand new netbook (Toshiba NB200) I cannot even stop the scroll and go back along the message stream with SHIFT+PageUpDown to understand what's going on. Of course I know that I can get a log of the boot process with 'dmesg' but I get the feeling that the very first lines show some problem I cannot grab at all.
View 2 Replies View RelatedI'm trying to stop all boot time messages from appearing -- basically I'd like to have a simple blank screen from grub to xdm.
I tried everything -- used the "quiet" option in grub's config, added dmesg -n 1 to rc.local, changed console=ttySx, set kernel.printk in sysctl.conf to 4 1 1 7, and even eradicated rsyslogd altogether... to no avail. I still see all sorts of messages on my screen.
Howto configure /boot/grub/menu.lst from Lenny to hide boot text messages during the startup?
View 14 Replies View RelatedMy systemd-udev-settle.service is failing for some reason.
systemctl status systemd-udev-settle.service -a output
Code: Select all● systemd-udev-settle.service - udev Wait for Complete Device Initialization
Loaded: loaded (/lib/systemd/system/systemd-udev-settle.service; static)
[ode]...
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I'm running Debian Testing and since some time ago I'm getting the following messages:Any ideas how to solve this warnings?
(gtk-update-icon-cache:9204): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
Processing triggers for gconf2 ...
[code]....
I have a problem copying my udev rules from other distro to another pc running debian. My box is running debian without any DE and I want my USB disks to be automounted based on the label; I believe udev is the nicest way to do this task.
Anyways : my rules are (copied from archlinux wiki btw)
cat /etc/udev/rules.d/92-my-media-automount.rules
# vim:enc=utf-8:nu:ai:si:et:ts=4:sw=4:ft=udevrules:
# /etc/udev/rules.d/92-my-media-automount.rules
# Only work on sd*
KERNEL!="sd[a-z]*", GOTO="my_media_automount_end"
ACTION=="add", PROGRAM!="/sbin/blkid %N", GOTO="my_media_automount_end" .....
I notice the directory is made successfully up inserting the usb HD, but the mount doesn't succeed. If I manually execute above command, the mount goes ok.
I have SSD drives without SCT support, because of this I want to tune /sys/block/device-name/device/timeout in order to force mdadm put these drives offline. So, I can see my drive like this:
/dev/disk/by-id/ata-OCZ-SABER1000_A22MJ061512000074.
Where can I tune /sys/block/device-name/device/timeout from 30 to 7 sec only for these drive? I don't want to use rc.local.
Can I create right udev rules for it in /etc/udev/rules.d?
I want to avoid any conflict with /lib/udev/rules.d.
Code: Select all# udevadm monitor --environment --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UDEV [9302.549485] add /devices/pci0000:00/0000:00:01.2/0000:03:00.0/host0/target0:0:0 (scsi)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:01.2/0000:03:00.0/host0/target0:0:0
DEVTYPE=scsi_target
SEQNUM=5210
SUBSYSTEM=scsi
[Code] ....
I'm trying to allow non-root account to use avrdude to program mucrocontrollers. There are many articles online about how to do that, but it seems not to work for me. Every time i try to execute avrdude it says "permission denied". Here's "$ udevadm info --name=/dev/bus/usb/002/011 --attribute-walk" says looking at device '/devices/pci0000:00/0000:00:1d.1/usb2/2-1':
KERNEL=="2-1"
SUBSYSTEM=="usb"
DRIVER=="usb"
ATTR{configuration}==""
[code]....
However, after restarting udev, replugging the device, even rebooting the computer I still get "permission denied". The Vendor and Product match, so what's the problem?
I 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 RelatedI've just installed 'Testing' on a VMware server and after I completed the install with no problems, the system booted into the kernel and I noticed the following start up process error:
startpar: service(s) returned failure: udev...failure!
I have not seen this before and am not sure if it's related to the fact that this is a virtual machine and not a physical server or something else.
Here is a Screenshot.
How to hardcode/fix a udev roule for /dev/input/event0?For example my touchscreen device jumped after restart, sometimes will be recognized as input3 and sometimes as input0.
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
[code]....
I have a hp mini 1033cr. Awhile ago I installed ubuntu netbook edition, well I was new to Ubuntu so I clicked upgrade. Well everything was going good and then it restarted. when I came up to the log in page I typed my password and now it won't boot. it goes to the desktop theme but then freezes with three warning messages.
1st could not update ICEauthority file /home/adam/.ICEauthority
2nd There is a problem with the configuration server. (/usr/lib/libgcond-sanity-check-2 exited with status 256)
3rd Nautilus could not create the following required folders: /home/adam/desktop, /home/adam/.nautilus
I have tried a fresh install with a disc I burnt and ran with my external dvd drive. Well guess what it decided to not boot from it. I have also tried several other discs including a windows xp disc. it always boots back to the hard drive.
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?
I have a trayless SATA hotswap bay that is really terrific for quickly attaching and removing SATA hard drives. I'm trying to write a udev rule to create a symbolic link to the device node for the drive that is attached through the hotswap bay (/dev/bay -> /dev/sdX). This eliminates any ambiguity when performing destructive tasks (fdisk, etc). I'm running squeeze amd64. I've read through several tutorials and have it working somewhat. Here's the output of udevadm info for a drive attached via the hotswap bay.
looking at device '/devices/pci0000:00/0000:00:11.0/host7/target7:0:0/7:0:0:0/block/sdb':
KERNEL=="sdb"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="16"
ATTR{ext_range}=="256"
ATTR{removable}=="0"
ATTR{ro}=="0"
ATTR{size}=="156301488"
ATTR{alignment_offset}=="0"
ATTR{capability}=="52" ....
Here is my udev rule
DEVPATH=="/devices/pci0000:00/0000:00:11.0/host7/*", SUBSYSTEM=="block", SYMLINK+="bay%n"
This produces the desired behavior and gives me an fdisk-able device node. The problem I am having is that the "host" component of the DEVPATH varies from bootup to bootup. I'm just using on onboard SATA, host2-7, specifically host7. There is also onboard PATA, host0-1. It seems to just be random which "host"s are assigned to which controller. For example, the next time I boot the system, the onboard SATA will be host0-5 and the onboard PATA will be host6-7. In this simple case, I could just write 2 rules, one for each possibility and it would still be correct because of the different PCI addresses of the two controllers. But on systems with more SCSI (uh... libata, actually) controllers, a "host" file can point to different physical ports between bootstraps. This would be bad. Does anyone know of a way to write a rule to tie a device node to a specific physical SATA port on the motherboard/hba?
A few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
View 5 Replies View RelatedI am on debian jessie. I ran "apt-get update && apt-get upgrade" and midway through the upgrade my computer suddenly rebooted.
I wasn't paying close attention to the upgrade process so I didnt see if there was any error messages right before the reboot. The laptop was plugged in, fully charged and I've never had issues with overheating.
When I boot now I get to a shell with a message that says:
Code: Select allWelcome to emergency mode. After logging in type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
If I try "systemctl default" there's a message that simply says "Hangup", nothing else happens.
Looking through "journalctl -xb" I see this:
Code: Select allFailed to insert module 'autofs4'
Failed to open /dev/autofs: No such file or directory
Failed to initialize automounter: No such file or directory
Failed to set up automount Arbitrary Executable File Formats File System Automount Point.
Failed to start Load Kernel Modules.
If I retry "apt-get upgrade" it says:
Code: Select alldpkg was interrupted, you must maually run dpkg --configure -a to correct the problem
If I run "dpkg --configure -a" stops at the package cups-browsed with message saying "Hangup"
Output of a few commands I saw in another forum thread:
$ lsmod
Code: Select allModule Size Used by
ext4 473802 1
crc16 12343 1 ext4
mbcache 17171 1 ext4
jbd2 82522 1 ext4
[Code] ....
Is this fixable without jumping through too many hoops or should I just reinstall the system? I need the computer for work so Im not gonna spend days trying to fix it without reinstalling.
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:"
"Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
I recently did a fresh install of current and once I had it up and running I compiled a fresh 2.6.33 kernel using my old config file, but now I get this warning durning boot, specifically during module loading WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release. This doesn't seem to be causing any problems but I am curious to know what the message meams? I checked /etc/modprobe but everything looks normal.
View 1 Replies View RelatedI have a small LAN. I am in the process of installing a Debian Lenny/Squeeze system into the LAN. I want to send and receive system messages using rwalld and wall.I can send a system message from my Debian system to another box using rwall. I can send a local message within the Debian box using wall in a console.I cannot send a local message using wall Konsole in KDE 3.5.x. The KDE Write daemon fails to provide any pop-up window./usr/bin/wall is installed from the bsdutils package and is set to -rwxr-sr-x.
The ktalkd package is installed. The KDE control center shows a configuration option in Internet & Network settings called Local Network Chat.When not in X, mesg is set to y at the console. After starting KDE and I open Konsole, mesg is always set to n. I don't know how this setting toggles. Further, setting mesg to y in Konsole has no effect on getting wall to work.mesg is set to y when I run xterm in KDE. Then wall works within that terminal window. However, the KDE Write daemon does not see the message in xterm.When I send a message from another system to the Debian system using rwall, xterm receives the message but not Konsole or the KDE Write daemon.
I am an old Debian user, ho just reinstalled it again to see how it evolved since my las version (3.2). I am sharing it with Arch Linux, And decided to let bot of them. I am using GDM compiled and configured in Arch, and removed GDM2 from Debian (i just like the easy menu.list from the old GDM). The problem is that when i update the kernel, it didn't fing GDM and drops an error message. I tried removing the distro-preconfigured Kernels, as i compiled my own 3.0.0-rc2 Kerenel, but i cant delete the previous ones. Now everytime i do an install or uptgrade, apt-get drops wastes some time, and drops an error message:
[code]...
What can i do? i googled some similar errors, but where just messed up mirror.lists, or similar, i know it isnt the cause of fail.
PHP Warning: mysqli_connect(): (28000/1045): Access denied for user 'root'@'localhost' (using password: YES) in /var/www/..../libraries/database/mysqli_connection.php on line 23
Can't connect to MySQL database (root@mysql).
/var/log/syslog is full of messages
/etc/gdm3/Xsession[3408]: ![1433316153,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] #011ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1
What this means and how to fix it?
On running aptitude update and then aptitude upgrade following warning notedfollowing packages have been kept back:
[code]...
The system crontab (/etc/crontab) uses the same format, except that the username for the command is specified after the time and date fields and before the command.
[code]...
Every hour, I get an e-mail complaining about the first line of the crontab:
[code]...
I get the same complaint from the other entries: It looks to me as if cron, or anacron, is trying to execute the user (root) as a command. Predictably, the shell doesn't like it, so barfs and triggers an e-mail about it. Why is this not doing what the man page says it should do? The 2nd problem I believe is related to exim, not cron. The e-mails I'm getting above are being bounced from my ISP because they are directed to root@myisp.com, rather than my regular e-mail address. When the message bounces, it bounces to my regular e-mail address. In /etc/aliases, I have root: [URL]... and in etc/email-addresses I have root: [URL]... Adding the entry to /etc/email-addresses allowed the bounce to find me because the sender's address is [URL]... but how can I get cron to send these messages to me in the first place, instead of root?
i have the basic knowledge of networking. a week ago i installed debian Lenny version on an old pentium 3. in addition i installed a ddclient configured it according to many tutorials.i searched google a few days but didnt find my case. i ran the folowing command :
ddclient -daemon=0 -debug -verbose -noquiet
output:
debian:~# ddclient -daemon=0 -debug -verbose -noquiet
=== opt ====
opt{cache} : <undefined>
[Code]...
i installed ddclient before installing apache. the 10.0.0.10 address is the server address in my d link router behind NAT.