[opensuse] PATA interfaces
I have a disk that boots in one machine and not the other (previous post about this a week or so back). I have investigated further and see that on one machine (the original on which it works fine) it is using pata_via. On the system I want to move it to, I see that these are being loaded: ahci ata_piix ata_generic piix ide_pci_generic My question is: could I simply add both sets to the initrd? Then, depending on which system it boots on the drivers will be loaded? When the move is known to work, the pata_via module should go away. But I do not want to remove it before I know the new boot works because it may need to go back in the old machine if the new one fails to boot. Perhaps I should make a copy of the current initrd and make a grub entry that boots with that. And make a new initrd with the new modules and make a grub entry that boots with that instead? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-07-22 at 09:53 +0200, Roger Oberholtzer wrote:
Perhaps I should make a copy of the current initrd and make a grub entry that boots with that. And make a new initrd with the new modules and make a grub entry that boots with that instead?
Bad form to follow my on message. But I could not wait for confirmation on the list. So I made a new initrd for the new system, removing / adding modules as needed. It works. The disk can live in boot hardware systems, selecting the appropriate initrd via grub. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
On Thu, 2010-07-22 at 09:53 +0200, Roger Oberholtzer wrote:
Perhaps I should make a copy of the current initrd and make a grub entry that boots with that. And make a new initrd with the new modules and make a grub entry that boots with that instead?
Bad form to follow my on message.
Not at all - it's only courteous to let others know what you've done and that it worked (or not). -- Per Jessen, Zürich (22.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
On Thu, 2010-07-22 at 09:53 +0200, Roger Oberholtzer wrote:
Perhaps I should make a copy of the current initrd and make a grub entry that boots with that. And make a new initrd with the new modules and make a grub entry that boots with that instead?
Bad form to follow my on message. But I could not wait for confirmation on the list. So I made a new initrd for the new system, removing / adding modules as needed. It works. The disk can live in boot hardware systems, selecting the appropriate initrd via grub.
For simplicity you can just make one initrd with all the modules for both systems, can't you? Then the kernel will determine which ones to use when it configures itself for the hardware. So you only have one build to manage. Or is that not how it works? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-07-22 at 10:46 +0100, Dave Howorth wrote:
For simplicity you can just make one initrd with all the modules for both systems, can't you? Then the kernel will determine which ones to use when it configures itself for the hardware. So you only have one build to manage. Or is that not how it works?
That was an option. But I was concerned that something might get confused. So I kept them separate. I may try a combined one just for kicks. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/07/22 11:54 (GMT+0200) Roger Oberholtzer composed:
On Thu, 2010-07-22 at 10:46 +0100, Dave Howorth wrote:
For simplicity you can just make one initrd with all the modules for both systems, can't you? Then the kernel will determine which ones to use when it configures itself for the hardware. So you only have one build to manage. Or is that not how it works?
That was an option. But I was concerned that something might get confused. So I kept them separate. I may try a combined one just for kicks.
The openSUSE installation puts every conceivable controller module in its. It's simple enough. In a system with only one HD, there's nothing to confuse. If you want both ways, try giving a special name to the one with "everything", such as initrd-2.6.34-12-universal. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-07-22 at 07:49 -0400, Felix Miata wrote:
The openSUSE installation puts every conceivable controller module in its. It's simple enough. In a system with only one HD, there's nothing to confuse. If you want both ways, try giving a special name to the one with "everything", such as initrd-2.6.34-12-universal.
There is a mix of ATA HD and SATA/RAID. Anyway, all is sorted. The system is in a faster box. My next step in a few weeks will be to see about migrating that to a 11.3 partition on this same disk. One step at a time. And no disruption of service. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2010. július 22. 10:45 napon Roger Oberholtzer
On Thu, 2010-07-22 at 09:53 +0200, Roger Oberholtzer wrote:
Perhaps I should make a copy of the current initrd and make a grub entry that boots with that. And make a new initrd with the new modules and make a grub entry that boots with that instead?
Bad form to follow my on message. But I could not wait for confirmation on the list. So I made a new initrd for the new system, removing / adding modules as needed. It works. The disk can live in boot hardware systems, selecting the appropriate initrd via grub.
Could you please write down how to add the required modules to a new initrd image? I know it is mentioned in mkinitrd manual but how does the command look in practice? Could you give the command line(s) you used when you created your initrd? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Istvan Gabor wrote:
Could you please write down how to add the required modules to a new initrd image? I know it is mentioned in mkinitrd manual but how does the command look in practice? Could you give the command line(s) you used when you created your initrd?
Edit /etcv/sysconfig/kernel INITRD_MODULES, then run mkinitrd. -- Per Jessen, Zürich (25.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-07-22 at 11:57 +0200, Istvan Gabor wrote:
2010. július 22. 10:45 napon Roger Oberholtzer
írta: On Thu, 2010-07-22 at 09:53 +0200, Roger Oberholtzer wrote:
Perhaps I should make a copy of the current initrd and make a grub entry that boots with that. And make a new initrd with the new modules and make a grub entry that boots with that instead?
Bad form to follow my on message. But I could not wait for confirmation on the list. So I made a new initrd for the new system, removing / adding modules as needed. It works. The disk can live in boot hardware systems, selecting the appropriate initrd via grub.
Could you please write down how to add the required modules to a new initrd image? I know it is mentioned in mkinitrd manual but how does the command look in practice? Could you give the command line(s) you used when you created your initrd?
I first made a copy of the existing initrd file in /boot (the actual file, not the symlink to it), and made an entry in grub to boot with this file. At that point there is only a name change. I then used YAST: System->/etc/sysconfig Editor. In that, I selected System->Kernel->INITRD_MODULES, and edited as I saw fit. When I saved the change (after a confirmation), yast rebuilt the initrd file. Your original initrd file will be overwritten. Thus the step above. Just be careful you do not remove something that is needed. This is why I made the safety copy and grub entry to access it: just in case I mess up. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2010. július 22. 14:06 napon Roger Oberholtzer
I first made a copy of the existing initrd file in /boot (the actual file, not the symlink to it), and made an entry in grub to boot with this file. At that point there is only a name change.
I then used YAST: System->/etc/sysconfig Editor. In that, I selected System->Kernel->INITRD_MODULES, and edited as I saw fit. When I saved the change (after a confirmation), yast rebuilt the initrd file. Your original initrd file will be overwritten. Thus the step above.
Just be careful you do not remove something that is needed. This is why I made the safety copy and grub entry to access it: just in case I mess up.
Roger, Per: Thank you. I'll add this to my notes. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Dave Howorth
-
Felix Miata
-
Istvan Gabor
-
Per Jessen
-
Roger Oberholtzer