search for: autoprob

...s to lie in the open-source "nv" video driver and my card. The proprietary "nvidia" driver works fine (once it is installed). With the install disks, I am stuck with a text install (and thus locked out of some of the LVM options I need). I have not found a way to override the autoprobed video driver except to use "noprobe", and I have no idea what drivers I need to install to do the install correctly. Wish list for fixes: 1. Fix (or update) "nv" driver so it works right with all 6200 cards. 2. Fix the autoprobe so it uses the "vesa" driver for my...

....f/driver/unbind > 2) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/new_id > 3) echo ssss:bb:dd.f > /sys/bus/pci/drivers/vfio-pci/bind > 4) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/remove_id > > There are actually a number of ways you can do this and the default > autoprobe behavior really makes step 3) unnecessary as the driver core > will probe any unbound devices as soon as a new_id is added to vfio-pci. > That can be changed by: > > # echo 0 > /sys/bus/pci/drivers_autoprobe > > But then we have to worry about races from any devices that mig...

....f/driver/unbind > 2) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/new_id > 3) echo ssss:bb:dd.f > /sys/bus/pci/drivers/vfio-pci/bind > 4) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/remove_id > > There are actually a number of ways you can do this and the default > autoprobe behavior really makes step 3) unnecessary as the driver core > will probe any unbound devices as soon as a new_id is added to vfio-pci. > That can be changed by: > > # echo 0 > /sys/bus/pci/drivers_autoprobe > > But then we have to worry about races from any devices that mig...

...filesystem driver or anything else in the list of directories compiled into it as long as its name matches the "interface-name" parameter. Corollary: Any module in /lib/modules can be loaded into kernel memory by any user at any time. There are potential denial-of-service attacks from autoprobes and device initialization all kinds of other goo that I wish I didn''t have to think about here. Here are four alternative fixes: Fix 1: Add a keyword to /etc/modules.conf that puts kerneld Into a mode where nothing that wasn''t explicitly listed in /etc/modules could be loaded...

-----BEGIN PGP SIGNED MESSAGE----- The autodetection routines for some linux modules can tie up the machine for several seconds at a time. By trying to open devices not present on the machine, a local user can disrupt service considerably. A very simple exploit is victim$ ls /dev/*/* repeatedly. A suggested fix is to remove or chmod 0 device nodes for hardware not installed on the

...to install CentOs 4 onto and am having problems getting the darn thing to recognize the hard drives. (it's worth noting that it's running RAID 0 and the RAID bios recognizes both drives as being in "optimal" state). I start the installation process and all is going well until it autoprobes. All other hardware is found except for the hard drives. The install subsequently fails because there the drives can't be found. I have been googling my brain out over the last week and this seems to be an issue with installing linux on this particular server model. (surrounding the megaraid...

...all downloads the kernel, boots, a VNC window for the new VM appears, but it just stops dead, after "mounting /sys filesystem ... done". (Unfortunately I cannot copy paste from that window ...) This is what is in /var/log/xen/xend-debug.log : Running with no password 12/02/2008 14:17:10 Autoprobing TCP port 12/02/2008 14:17:10 Autoprobing selected port 5900 12/02/2008 14:17:10 other clients: 12/02/2008 14:17:10 Client Protocol Version 3.8 12/02/2008 14:17:10 Protocol version sent 3.8, using 3.8 12/02/2008 14:17:10 rfbProcessClientSecurityType: executing handler for type 1 12/02/2008 14:1...

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that it now handles the specified PCI ID. But

...ormat qemu driver + phy:[/dev/]<device> phy raw image bdrv_raw + file:<filename> file raw image bdrv_raw + tap:aio:<filename> tap raw image bdrv_raw + tap:qcow:<image> tap not raw autoprobe + tap:<cow-fmt>:<image> tap named format bdrv_<cow-fmt> + It is still necessary to autoprobe when the image is specified as + `tap:qcow:<image>', because qemu distinguishes `qcow' and `qcow2' + whereas blktap doesn't; `qcow' in xenstor...

Antonio, thank you for reply. On 06/16/2015 12:22 PM, Antonio S. Martins Jr. wrote: > ----- "g" <geleem at bellsouth.net> escreveu: <<>> >> greetings, >> >> i want to sync my desktop home directory to my laptop home >> directory. i am using KDE for desktop. >> >> a problem that i foresee is the different screens between the 2.

Dear All, I have a following query: - My initrd image is created using ext2 filesystem. - The filesystem type of / is specified as ext3 in /etc/fstab file. - I dont mount the real root during execution of linuxrc because I referred some documents saying that if you dont mount real root from linuxrc the kernel will mount it after linuxrc is finished. - The system boots up successfully, mount

...and files should not be copied so that configs for >> desktop/laptop do not corrupt configs for laptop/desktop screen? > > Maybe you need to be clearer. The screen's configuration is not > really configured in your home directory, but by X (although these > days it's all autoprobed). > > Are you talking about what icons appear? The configuration for KDE? . also, thank you for kicking my chemo brain in the butt. ;-) yes, i forgot about X being the wise and wondrous now. iirc, there used to be a file under /etc/X11 that had specs for keyboard, mouse, graphics card, m...

I'm trying to set up a VNC server using the instructions at http://www.techrepublic.com/blog/linux-and-open-source/linux-101-easy-vnc-server-setup/ . I am up to step 6: Step 6: Edit iptables In order for the VNC connections to get through, you must allow them with iptables. To do this, open up the file /etc/sysconfig/iptables and add the line: -A INPUT -m state --state NEW -m tcp -p tcp -m

...: > what directories and files should not be copied so that configs for > desktop/laptop do not corrupt configs for laptop/desktop screen? Maybe you need to be clearer. The screen's configuration is not really configured in your home directory, but by X (although these days it's all autoprobed). Are you talking about what icons appear? The configuration for KDE? -- Jonathan Billings <billings at negate.org>

...d so that configs > for > >> desktop/laptop do not corrupt configs for laptop/desktop screen? > > > > Maybe you need to be clearer. The screen's configuration is not > > really configured in your home directory, but by X (although these > > days it's all autoprobed). > > > > Are you talking about what icons appear? The configuration for > KDE? > . > also, thank you for kicking my chemo brain in the butt. ;-) > > yes, i forgot about X being the wise and wondrous now. > > iirc, there used to be a file under /etc/X11 that ha...

...sys/bus/pci/devices/ssss:bb:dd.f/driver/unbind 2) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/new_id 3) echo ssss:bb:dd.f > /sys/bus/pci/drivers/vfio-pci/bind 4) echo vvvv dddd > /sys/bus/pci/drivers/vfio-pci/remove_id There are actually a number of ways you can do this and the default autoprobe behavior really makes step 3) unnecessary as the driver core will probe any unbound devices as soon as a new_id is added to vfio-pci. That can be changed by: # echo 0 > /sys/bus/pci/drivers_autoprobe But then we have to worry about races from any devices that might have been hotplugged in the...

I have already a running automated Deployment system using pxelinux and tftd and a 1,44 floppy image (memdisk) with ms-dos and 3-com undi drivers. The whole thing is working good, and i am not unhappy about it. But, the dos image solution has a few disadvanatages, because i cannot find a mtftp client for ms-dos to deploy a lot of system at the same time. Under linux such client exists, but i

...> and am having problems getting the darn thing to recognize the hard > drives. (it's worth noting that it's running RAID 0 and the RAID > bios recognizes both drives as being in "optimal" state). I start > the > installation process and all is going well until it autoprobes. All > other hardware is found > except for the hard drives. The install subsequently fails because > there the drives can't be found. > > I have been googling my brain out over the last week and this seems > to be an issue with installing linux > on this particular serve...

...(IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: thor at math.tu-berlin.de QA Contact: xorg-team at lists.x.org If autoprobing outputs fails - probably because the monitor sits behind a KVM - neither the xorg driver nor the nouveau kernel module can force-enable an output. Details are as possible: I have here an old GForce FX 5200 card whose DVI-I ouptut is connected to a monitor behind a KVM switch (an ATEN CS22D)....