I'm doing an autoyast install with a SuSE 10.0 DVD. First I have a problem with booting it up. It stops at setting dhcp. I have three NICs in the box. It will not work with the Intel(e1000) and couple of RTL based.
The only way I managed to boot thing up is trough an RTL based NIC and by NFS based install. I chose NFS server and dir, put the autoyast line and system boots but only after it fails to dhcp on intel NIC.
I'm assuming that you're using PXE to pass the install initrd and everything?
Assuming so, you might try pausing the PXE process when the Intel NIC is trying to get an IP address, by hitting the "Pause/Break" key on your keyboard. Let it sit for about 30-60 seconds, and then hit space to start the process back up.
(This situation -- where the NIC is on a network with DHCP, but doesn't get an address -- can be an indication that negotiation between the NIC and the switch to which it's network is taking a while -- and that the PXE process times out before the link is negotiated and brought up. It's happened with some of my machines, though only in cases where the networking hardware behind them is Cisco)
Marlier, Ian wrote:
I'm doing an autoyast install with a SuSE 10.0 DVD. First I have a problem with booting it up. It stops at setting dhcp. I have three NICs in the box. It will not work with the Intel(e1000) and couple of RTL based.
The only way I managed to boot thing up is trough an RTL based NIC and by NFS based install. I chose NFS server and dir, put the autoyast line and system boots but only after it fails to dhcp on intel NIC.
I'm assuming that you're using PXE to pass the install initrd and everything?
Assuming so, you might try pausing the PXE process when the Intel NIC is trying to get an IP address, by hitting the "Pause/Break" key on your keyboard. Let it sit for about 30-60 seconds, and then hit space to start the process back up.
(This situation -- where the NIC is on a network with DHCP, but doesn't get an address -- can be an indication that negotiation between the NIC and the switch to which it's network is taking a while -- and that the PXE process times out before the link is negotiated and brought up. It's happened with some of my machines, though only in cases where the networking hardware behind them is Cisco)
I'm not booting trough PXE. I'm using DVD. I push F3 button for additional options, then set NFS options up (server + dir) and type in the autoyast=http://... line. This is the only way I get autoyast process started. Without the NFS autoyast will not start. It stops at when dhcp negotiates parameters. Box sends requests and server offers IP but box acts as nothing happened.
Anyway this is kind of secondary problem now. What I would really like to know is why autoyast process freezes up at the end of first stage of installation. What kind of info can I send to the list to make debugging easier. I already attached XML file in my first post.
TIA, I.
On Friday 29 September 2006 09:46, Babarovic Ivica wrote:
Anyway this is kind of secondary problem now. What I would really like to know is why autoyast process freezes up at the end of first stage of installation.
if I understand your first post right, it's not a freeze, because you can still reboot the machine.
What kind of info can I send to the list to make debugging easier. I already attached XML file in my first post.
you can send me the /var/log/YaST2/y2log file.
Uwe Gansert wrote:
On Friday 29 September 2006 09:46, Babarovic Ivica wrote:
Anyway this is kind of secondary problem now. What I would really like to know is why autoyast process freezes up at the end of first stage of installation.
if I understand your first post right, it's not a freeze, because you can still reboot the machine.
No. I actually power off the machine. I would hard reset it but box doesn't have reset button. So it is in the freeze state. :)
What kind of info can I send to the list to make debugging easier. I already attached XML file in my first post.
you can send me the /var/log/YaST2/y2log file.
Ok. I attached the file.
regards, I.
2006-09-28 18:06:53 <1> linux(7313) [liby2] genericfrontend.cc(main):193 Launched YaST2 component 'scr' 2006-09-28 18:06:53 <1> linux(7313) [liby2] genericfrontend.cc(main):482 YAST_IS_RUNNING is yes 2006-09-28 18:06:53 <1> linux(7313) [agent-system] SystemAgent.cc(Execute):1097 mkdir /var/adm/mount 2006-09-28 18:06:53 <3> linux(7313) [bash] ShellCommand.cc(shellcommand):78 sh: /usr/sbin/gen-hwcfg-disk.sh: No such file or directory 2006-09-28 18:06:57 <3> linux(7313) [bash] ShellCommand.cc(shellcommand):78 error: File not found by glob: /tmp/update/[0-9]*/install/*.rpm 2006-09-28 18:06:57 <3> linux(7313) [bash] ShellCommand.cc(shellcommand):78 error: open of 2 failed: No such file or directory 2006-09-28 18:07:02 <1> linux(7313) [Y2Perl] Y2PerlComponent.cc(Y2PerlComponent):35 Creating Y2PerlComponent 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [Bootloader_API] modules/Bootloader_API.pm(Bootloader_API::DumpLog):28 GRUB::new: Created GRUB instance 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [Bootloader_API] modules/Bootloader_API.pm(Bootloader_API::DumpLog):28 GRUB::CreateLines: Embed Stage1.5: 0 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:02 <1> linux(7313) [scr] ../../libscr/src/include/scr/Y2AgentComponent.h(evaluate):108 Evaluating an expression, not SCR builtin 2006-09-28 18:07:04 <1> linux(7313) [agent-system] SystemAgent.cc(Execute):1097 mkdir /var/adm/autoinstall/scripts 2006-09-28 18:07:04 <1> linux(7313) [agent-system] SystemAgent.cc(Execute):1097 mkdir /var/adm/autoinstall/logs 2006-09-28 18:07:04 <1> linux(7313) [liby2] genericfrontend.cc(main):497 Finished YaST2 component 'scr' 2006-09-28 18:07:04 <1> linux(7313) [Y2Perl] YPerl.cc(destroy):163 Shutting down embedded Perl interpreter.
On Friday 29 September 2006 10:44, Babarovic Ivica wrote:
No. I actually power off the machine. I would hard reset it but box doesn't have reset button. So it is in the freeze state. :)
okay, then I misunderstood your first post.
you can send me the /var/log/YaST2/y2log file.
Ok. I attached the file.
hm. That does not help me. Do the installation and then switch to console 4 and look if you see a kernel panic (I think console 4 are kernel messages maybe it's another one - you'll find it)
"Marlier, Ian" ian.marlier@studentuniverse.com writes:
(This situation -- where the NIC is on a network with DHCP, but doesn't get an address -- can be an indication that negotiation between the NIC and the switch to which it's network is taking a while -- and that the PXE process times out before the link is negotiated and brought up. It's happened with some of my machines, though only in cases where the networking hardware behind them is Cisco)
There's a IOS configuration option that will help speed up the initial handshaking -- portfast, IIRC?
hth, john, not the network guy; just hollers at the network guy when the PXE boots start timing out...
Uwe Gansert wrote:
On Friday 29 September 2006 10:44, Babarovic Ivica wrote:
No. I actually power off the machine. I would hard reset it but box doesn't have reset button. So it is in the freeze state. :)
okay, then I misunderstood your first post.
you can send me the /var/log/YaST2/y2log file.
Ok. I attached the file.
hm. That does not help me. Do the installation and then switch to console 4 and look if you see a kernel panic (I think console 4 are kernel messages maybe it's another one - you'll find it)
I already tryed switching to all available consoles but when system "freezes" it's also not respoding to keyboard input. I will look for information on setting up remote logging if possible. Suggestions for other solutions are welcome.
TIA, I.
John SJ Anderson wrote:
There's a IOS configuration option that will help speed up the initial handshaking -- portfast, IIRC?
hth, john, not the network guy; just hollers at the network guy when the PXE boots start timing out...
Can you ask your network guy if there are any such options for bind? :)
Thanks, I.
Babarovic Ivica wrote:
John SJ Anderson wrote:
There's a IOS configuration option that will help speed up the initial handshaking -- portfast, IIRC?
hth, john, not the network guy; just hollers at the network guy when the PXE boots start timing out...
Can you ask your network guy if there are any such options for bind? :)
Thanks, I.
Of course I ment dhcpd not the DNS bind server.
autoinstall@lists.opensuse.org
-
Babarovic Ivica -
John SJ Anderson -
Marlier, Ian -
Uwe Gansert