Hopefully someone here can help me, I am trying to install opensuse 11.2 on my Compaq 610 laptop, I have reformatted the hd and done a clean install of 11.2, however when I boot up the first time (before configuration) it hangs, I have tried both the X64 and the i586 distributions and the only difference is that the X64 distro boots up under failsafe mode while the i586 does not.
The problem seems to be at the udev part with the hang up occurring at :
6.002720] b43-pci-bridge 0000:10)00.0: PCI INT A -> Link[C136] - GSI 10 (level, low) -> IRQ 10
6.096894] iTCO_wdt: Intel TCO Watchdog Imer Driver v1.05
6.096159] iTCO_wdt: Found a ICH8M-E TCO device (Version=2, TCOBASE=0x1060)
6.103458] iTCO_wdt: initialized. heartbeat= 30 sec (nowayout=0)
And thereafter nothing further happens.
I tried the kernal option disablemodules=iTCO_wdt which got me to the next problem on the next line:
5.761939] b43-pci-bridge 0000:10:00.0: PCI INT A -> Link[C136] -> GSI 10 (level, low) -> IRQ 10
and it now hangs here
I tried 11.1 and slackware 13 with no problems installs fine and runs fine, on the opensuse site it lists the machine as compatible with 11.2.
Hi
I put these in and it booted straight after, went through the final configuration including updating, machine ran then I rebooted, failed again at the same place in the udevd.
I then tried under failsafe mode and it now also freezes this time though at the following line:
[7.266644] Bluetooth:HCI socket layer initialized
Can you think of any other avenues I should explore?
First, you should use the x86_64 version.
Second, I suggest you download the latest KDE4 live-CD, check md5sum, burn it at lowest speed possible, check burnt media, see if the system boots from it.
I’ve done some installs on Compaq 610’s but the hardware in the machines is different in different countries.
Also check the BIOS for weird protective settings.
Did you actually add all of these boot options at once?
one or possibly two will be what is needed. Run one at a time and see what works.the reason the system was back to its previous behavior after a reboot is that adding boot options this way is only for the current boot.When you find what works you can easily make the changes permanent.
On 03/07/2010 06:46 AM, Faircape wrote:
>
> Hi
> I put these in and it booted straight after, went through the final
> configuration including updating, machine ran then I rebooted, failed
> again at the same place in the udevd.
> I then tried under failsafe mode and it now also freezes this time
> though at the following line:
> [7.266644] Bluetooth:HCI socket layer initialized
>
> Can you think of any other avenues I should explore?
>
> Thanks
> JP
>
>
I agree with Knurpht. You should check your Compaq
bios setting to make sure you’re not using an IRQ for something that’s
conflicts with the installation,
Make sure your OpenSuSe distros pass the media check.
Since the install and now failsafe fail at different points more likely
something’s wrong with the base install instead of a particular
application.
I put these in and it booted straight after, went through the final configuration including updating, machine ran then I rebooted, failed again at the same place in the udevd.
Hi - Thanks for the input, I have managed to get it to boot in failsafe mode reliably by disabling all onboard peripherals in the bios, however no matter what I try I cannot get it to boot in normal mode.
I am going to try a X64 12.1 installation and see what the outcome is there, the media of the 12.2 is good, checksum is ok as is the media check, I’m also going to try install off that media onto another box.
Will keep posted if there is a Eureka moment.
If you compare the “normal mode” boot to the “fail safe” mode boot, you will notice they are identical, with the exception of a bunch of extra boot parameters that are sent in the “fail safe” boot.
A debugging methodology that can be followed here, is to write down what the “fail safe” mode boot parameters might be, and then try various combinations of them in the “normal mode” until you arrive at the “mininum” set of parameters needed in order to properly boot. Once you know this minimum set, you will also have the start of pointing to where the problem may be (as the various parameters do various things).
You can go about this in 2 ways … one way is to simply do reboot after reboot in “failsafe”, each time removing one boot code from the fail safe settings.
The other way is to simply do reboot after reboot in “normal”, each time adding a different boot code (or different combination of boot codes) to the "normal setting.
Eventually you will figure out the minimum code needed.
Just a quick update on this, I installed 11.2 on a desktop using the same media and I ran into problems setting up the network, this convinced me that despite the media checking out fine and the md5 being correct that I had corrupted media. I re-downloaded the iso and cut at 4X speed to a fresh disk.
This installed fine on the desktop but again failed on the laptop so I re-installed 11.1 to the laptop, it installed with absolutely no problem, all that requires configuration now is the wireless part.
As to 11.2 on the laptop I suspect it is something to do with the pci side of things and/or possibly the bluetooth part.
Thank you very much everyone for your assistance
JP
clearly it works on openSUSE-11.1 according to that site, but its also clear other distributions have strugged. I note Fedora-11 adds a boot code: i915.modprobe=0
… and Ubunt 9.10 (which is not recomended to install on linlap) has a work around "to press F6 and Esc to exit the modes menu, and after the ”–” add i195.modprobe=0 (…. i915.modprobe=0 –) " … so its possible there are work arounds for 11.2 on openSUSE.
One may also have to add options to the /etc/modprobe.d/sound file in 11.1 to get sound working ( add "snd-hda-intel model=dell-m4-1” to the file /etc/modprobe.d/sound according to linlap)