User Tools

Site Tools


ipmi_on_linux

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ipmi_on_linux [2012/02/13 15:13]
adam
ipmi_on_linux [2016/11/25 22:38] (current)
Line 95: Line 95:
 Kernel 2.4 people will have to follow the Debian IPMI instructions,​ as you're living in a world I haven'​t encountered with IPMI. You should note that ipmi_si is called ipmi_si_drv and its regspacings option is called si_regspacings. You may also have to make your own device node if you're not using devfs, as documented in the Debian instructions. After modprobing the relevent modules successfully,​ ''​ls -l /​dev/​ipmi0''​ to see if you have a device node before trying to create one. Kernel 2.4 people will have to follow the Debian IPMI instructions,​ as you're living in a world I haven'​t encountered with IPMI. You should note that ipmi_si is called ipmi_si_drv and its regspacings option is called si_regspacings. You may also have to make your own device node if you're not using devfs, as documented in the Debian instructions. After modprobing the relevent modules successfully,​ ''​ls -l /​dev/​ipmi0''​ to see if you have a device node before trying to create one.
  
-If this works without errors then Fedora/​RH/​Centos people are set, Ubuntu/​Debian people need to add the modules and options to /​etc/​modules.conf or maybe add the modprobe commands to /​etc/​init.d/​local if you have no other way.+If this works without errors then Fedora/​RH/​Centos people are set, Ubuntu/​Debian people need to add the modules and options to /​etc/​modules or maybe add the modprobe commands to /​etc/​init.d/​local if you have no other way.
  
 If you then ''​cat /​proc/​devices'',​ you should see your IPMI device listed and ''​ls -l /​dev/​ipmi0''​ should show your device node. If you then ''​cat /​proc/​devices'',​ you should see your IPMI device listed and ''​ls -l /​dev/​ipmi0''​ should show your device node.
Line 106: Line 106:
 You should have set up your BIOS for console redirection earlier, so now we will do the bootloader and init. You should have set up your BIOS for console redirection earlier, so now we will do the bootloader and init.
  
-To allow your bootloader to redirect over the BMC's serial port, edit /​boot/​grub/​grub.conf,​ sometimes known as /​boot/​grub/​menu.list add the following lines to grub.conf or menu.list:+To allow your bootloader to redirect over the BMC's serial port, for Grub v1, edit /​boot/​grub/​grub.conf,​ sometimes known as /​boot/​grub/​menu.list add the following lines to grub.conf or menu.list:
  
   serial --unit=1 --speed=19200 --word=8 --parity=no --stop=1 ​   serial --unit=1 --speed=19200 --word=8 --parity=no --stop=1 ​
Line 121: Line 121:
   savedefault   savedefault
   boot   boot
 +
 +For Grub2, look [[http://​linux.xvx.cz/​2009/​08/​debian-with-grub2-and-serial-connection/​|here]]
  
 This gives you a serial console on the second serial port, which should be your BMC's serial port, at 19200Kb per second, which should match what you chose in the BIOS. The order of the console options above is important. The last listed will be the system'​s default console which will display the boot messages and kernel errors. This means that after halfway through the boot process, during shutdown and when there are kernel errors, only the serial console will see the messages. As you want to work remotely, this is the way it has to be. You can't have more than one default console. You can however interrupt grub at boot time and edit the kernel line for a single boot with different parameters if you need to see the default console locally but remember that they will persist until you reboot, which means that if you reboot but still want to see them locally, you'll have to interrupt and edit grub at boot time again and also, to see them remotely again, you need to remember to reboot. This gives you a serial console on the second serial port, which should be your BMC's serial port, at 19200Kb per second, which should match what you chose in the BIOS. The order of the console options above is important. The last listed will be the system'​s default console which will display the boot messages and kernel errors. This means that after halfway through the boot process, during shutdown and when there are kernel errors, only the serial console will see the messages. As you want to work remotely, this is the way it has to be. You can't have more than one default console. You can however interrupt grub at boot time and edit the kernel line for a single boot with different parameters if you need to see the default console locally but remember that they will persist until you reboot, which means that if you reboot but still want to see them locally, you'll have to interrupt and edit grub at boot time again and also, to see them remotely again, you need to remember to reboot.
ipmi_on_linux.1329146005.txt.gz ยท Last modified: 2016/11/25 22:38 (external edit)