Re: Virtual Managers



On Thursday 20 Aug 2009 12:52, houghi played with alphabet spaghetti and
left this on the plate:

David Bolt wrote:
How is the repair coming along?

Like a bad sore. I was unable to get any repair done. The major issue
was that I had no network.

That could be a bit of a problem.

Have you managed to get X and the network
working again? And do you know just what caused the breakage?

The breakage was cause by doing some update swith the kernel stuff. No
idea what and that is because I know nothing about kernel stuff and that
is why I normaly keep far away with it.

I still think it was an issue of mismatches between the versions of the
various repos you used.

X was broken, because the kernel was new and I run NVidea, so it is a
bit expected to be broken.

You should have been able to still use the nv module instead of the nVidia
module. At least that would give you a working X, even if it's not the same
resolution and/or colour-depth that you're used to.

Updating it would have been possible with
network, which I don't have. See below as where I stand now.

restores from backup did not work.

That's interesting. Have you restored backups created by your backup
system before? Did they work the last time you did a restore? If so, what
was different this time?

I have. As far as I can see no difference.

Does it produce logs when restoring? If so, have you looked to see if it's
listed some errors?

So note to self: if it ain't broke, don't fix it.

The problem was that it was broken, just not quite as broken as it
somehow managed to ended up. Did you sort out the version mismatch with
the repos before doing the repair? If not, that could have broken things
even more than they were.

No, the kernel was not broken. What was broken was that the
kernel-source was not the right version. I won't be able to work out the
mismatch anymore.

The mismatch was because you had the kernel for openSUSE 11.1 but had the
sources for the one in openSUSE 11.0.

Here is where I stand. I was unable to do a repair with the DVD as
nothing seemed to be broken.

Not that it could see. Having said that, I'm not too impressed by the repair
system myself. Upgrading my milestone 4 to milestone 5 broke the boot
loader[0] and, being curious, I tried out the auto-repair on it. It failed
on that job, and also wanted to replace my Sendmail with Postfix as well as
re-installing some packages it thought should be a part of the "minimal"
install. I ended up sorting out the boot loader by mounting /boot, which the
repair system failed to do, and then specifically using the module to repair
the boot loader. Also found out that the "boot installed system" still
doesn't work.

However I did not get any network wich ment
no decent X.

Must be a very new chipset if it isn't recognised. Any idea which one it is?

So I decided on a new 11.0 installation as I was running that before.
Now I get no network with that installation.

I hate it when that happens. I also make sure I have a spare card available
just in case.

No idea why. What happend
in the ast is that I changed mobos and the old network driver did work
with the new onboard card.

I'd have expected there to have been issues with other hardware, the hard
disc controller for a start. That's one of the things that always seems to
break whenever I've had to change motherboards.

However a new installation did not recognise the card, so no network.

Is it seen by lspci? What info do you get return about it?

I then downloaded the 11.1 network CD. At this moment I am in the middle
of the installation

Ah, so at least the network card's working now.

(actually during the software selection) and just
went to tty2 to say hi. :-D

:-)

I have my work cut out now to get the installation working as I want. I
have exported all the files I had installed and also the repos, but they
need to be translated to 11.2 from 11.0.
^^^^
ITYM 11.1.

All in all, still pretty fast. The problem was just that I did not have
the DVD anymore. No idea where it went. OK, on with the installation.

With any luck, you should have a working install by now. As long as you
don't go daft and install almost all the patterns you can.


[0] again :-|

Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 10.3 32b | openSUSE 11.0 32b | |
openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b |
RISC OS 3.6 | RISC OS 3.11 | openSUSE 11.1 PPC | TOS 4.02
.



Relevant Pages

  • Re: Fedora and PCMCIA support - upgrade kernel?
    ... Rebooted and no second kernel listed. ... > not then install it. ... on the network card... ... first no network support. ...
    (comp.os.linux.setup)
  • Re: [opensuse] Cant boot 11.1 system after 2.6.27.19-3.2 kernel update!!
    ... I tried to repair the system with the 11.1 repair option, ... Briliant idea - copy a kernel from another machine and try booting, ... If you have an opensuse disk lying around, select Install> Boot ...
    (SuSE)
  • Re: Win2000 services enabled but stopped...and wont start. Cant connect to LAN.
    ... I had this crash reboot, at which time the lack of dependency between ... symtdi.sys and the DCHP client went into effect, and bango...no network, no ... I have run the Win2000 repair from the original CD (the CD-ROM was ... A full "repair install" doesn't require ...
    (microsoft.public.win2000.networking)
  • Re: [opensuse] Support for Intel Centrino2 wireless chipset in openSUSE 11.00 ?
    ... 0c:00.0 Network controller: Intel Corp. ... SUSEs 2.6.25 kernel is too old to support Intels new 5xxx wifi series. ... You will have to update to kernel with current iwlagn driver and also install the matching firmware for that device. ... Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipientis prohibited. ...
    (SuSE)
  • Re: Win2000 services enabled but stopped...and wont start. Cant connect to LAN.
    ... When I reboot this computer it tries to connect to the network but fails, usually with this error: " Microsoft Windows Network...the requested resource is in use" and sometimes "the network location could not be reached". ... BTW, I have run the Win2000 repair from the original CD (the CD-ROM was working then, now it is flagged in Device Manager and doesn't work). ... A full "repair install" doesn't require anything from the existing OS as far as accessing hardware like the CDROM goes. ...
    (microsoft.public.win2000.networking)