Re: Kernel Configuration Question
On 12/22/06 12:10:41PM -0600, Mike Reinehr wrote: I hate to answer my own posting but it belatedly has occurred to me that perhaps it's not possible to mount a root partition using LVM without an initrd.img. I've booted without an initrd.img before I've used LVM before, but not with the root partition as part of the logical volumes. Yes, no, maybe? That's pretty much it, you need to run the LVM tools (vgchange I think) to scan for and setup the logical volumes. There is no code in the kernel to do that for you so you have to use an initramfs image if your root is on LVM. But why go through all of that trouble to not use one? The only burden it puts on you is to run 'update-initramfs -u -k kernel-version' on of the off chance that you change something that also needs to go in the image, normal updates to things like LVM tools, udev, etc should update it for you. Jim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Configuration Question
On Saturday 23 December 2006 09:35, Jim Crilly wrote: On 12/22/06 12:10:41PM -0600, Mike Reinehr wrote: I hate to answer my own posting but it belatedly has occurred to me that perhaps it's not possible to mount a root partition using LVM without an initrd.img. I've booted without an initrd.img before I've used LVM before, but not with the root partition as part of the logical volumes. Yes, no, maybe? That's pretty much it, you need to run the LVM tools (vgchange I think) to scan for and setup the logical volumes. There is no code in the kernel to do that for you so you have to use an initramfs image if your root is on LVM. But why go through all of that trouble to not use one? The only burden it puts on you is to run 'update-initramfs -u -k kernel-version' on of the off chance that you change something that also needs to go in the image, normal updates to things like LVM tools, udev, etc should update it for you. Jim. Thanks for confirming this. I think I may have read something about this last year when I first researched LVM but then forgot. As for not using an initrd.img, long ago I became a confirmed follower of the KISS theory of operations (Keep It Simple, Stupid) and was just trying to pare my kernel of any unnecessary pieces. But, as you say, it's not that much trouble to maintain an initrd.img. Cheers! cmr -- Debian 'Etch': Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Configuration Question
On 12/23/06 11:25:25AM -0600, Mike Reinehr wrote: On Saturday 23 December 2006 09:35, Jim Crilly wrote: On 12/22/06 12:10:41PM -0600, Mike Reinehr wrote: I hate to answer my own posting but it belatedly has occurred to me that perhaps it's not possible to mount a root partition using LVM without an initrd.img. I've booted without an initrd.img before I've used LVM before, but not with the root partition as part of the logical volumes. Yes, no, maybe? That's pretty much it, you need to run the LVM tools (vgchange I think) to scan for and setup the logical volumes. There is no code in the kernel to do that for you so you have to use an initramfs image if your root is on LVM. But why go through all of that trouble to not use one? The only burden it puts on you is to run 'update-initramfs -u -k kernel-version' on of the off chance that you change something that also needs to go in the image, normal updates to things like LVM tools, udev, etc should update it for you. Jim. Thanks for confirming this. I think I may have read something about this last year when I first researched LVM but then forgot. As for not using an initrd.img, long ago I became a confirmed follower of the KISS theory of operations (Keep It Simple, Stupid) and was just trying to pare my kernel of any unnecessary pieces. But, as you say, it's not that much trouble to maintain an initrd.img. Exactly, it's virtually 0 maintenance unless you're doing really odd, complex things in your initramfs and even then once you set it up and put the files under /etc/initramfs-tools/ it'll keep working. A decent example is this, I setup this box with some dm-crypt block devices and by default the generic aes module is used, to switch to aes_x86_64 all I had to do was put the module name in /etc/modules, update my initramfs and reboot, if they had been compiled in statically I would have been stuck recompiling my kernel for that. And with the kernel people wanting to push more and more device discovery and setup to userland it's going to be unavoidable at some point anyway. Jim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mouse problem
Hi, I use a usb-mouse. Last days are began strange problems with it. It becomes slow until stopping... and so I must change USB port, hoping that it restarts. In /var/log/messages: ... Dec 24 08:35:35 localhost kernel: usb 1-2: new low speed USB device using uhci_hcd and address 17 Dec 24 08:35:35 localhost kernel: usb 1-2: configuration #1 chosen from 1 choice Dec 24 08:35:35 localhost kernel: input: Fellowes Opti mouse3 as /class/input/input7 Dec 24 08:35:35 localhost kernel: input: USB HID v1.10 Mouse [Fellowes Opti mouse3] on usb-:00:10.0-2 Dec 24 08:49:04 localhost -- MARK -- Dec 24 08:57:05 localhost kernel: usb 1-2: reset low speed USB device using uhci_hcd and address 17 Dec 24 08:57:07 localhost last message repeated 3 times Dec 24 08:57:08 localhost kernel: usb 1-2: USB disconnect, address 17 Dec 24 08:57:08 localhost kernel: usb 1-2: new low speed USB device using uhci_hcd and address 18 Dec 24 08:57:09 localhost kernel: usb 1-2: new low speed USB device using uhci_hcd and address 19 Dec 24 08:57:09 localhost kernel: usb 1-2: configuration #1 chosen from 1 choice Dec 24 08:57:09 localhost kernel: input: Fellowes Opti mouse3 as /class/input/input8 Dec 24 08:57:09 localhost kernel: input: USB HID v1.10 Mouse [Fellowes Opti mouse3] on usb-:00:10.0-2 Dec 24 08:58:38 localhost kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 Dec 24 08:58:38 localhost kernel: psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 Dec 24 08:58:38 localhost kernel: psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched. Have you any idea? Thanks, Giulio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
