diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2013-April/024345.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2013-April/024345.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-April/024345.html | 172 |
1 files changed, 172 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-April/024345.html b/zarb-ml/mageia-dev/2013-April/024345.html new file mode 100644 index 000000000..0609e98ee --- /dev/null +++ b/zarb-ml/mageia-dev/2013-April/024345.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] M3 beta - where to report problems? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20M3%20beta%20-%20where%20to%20report%20problems%3F&In-Reply-To=%3C5165AD92.90509%40kde.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="024340.html"> + <LINK REL="Next" HREF="024346.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] M3 beta - where to report problems?</H1> + <B>Anne Wilson</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20M3%20beta%20-%20where%20to%20report%20problems%3F&In-Reply-To=%3C5165AD92.90509%40kde.org%3E" + TITLE="[Mageia-dev] M3 beta - where to report problems?">annew at kde.org + </A><BR> + <I>Wed Apr 10 20:21:06 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="024340.html">[Mageia-dev] M3 beta - where to report problems? +</A></li> + <LI>Next message: <A HREF="024346.html">[Mageia-dev] M3 beta - where to report problems? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#24345">[ date ]</a> + <a href="thread.html#24345">[ thread ]</a> + <a href="subject.html#24345">[ subject ]</a> + <a href="author.html#24345">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA1 + +On 10/04/13 13:07, Frank Griffin wrote: +><i> On 04/10/2013 07:31 AM, Anne Wilson wrote: +</I> +I think there may be some misunderstandings, so I'll try to correct them +inline. + +><i> Interesting. I guess you didn't configure eth0 from the Install +</I>><i> Summary. +</I> +I configured it to use dhcp, since netbooks are used in other places (I +use the hotel cabled network when in Madeira). + +><i> You can do it from the chroot (using Colin's suggestion) by running +</I>><i> drakconnect. +</I>><i> +</I>Drakconnect ran, I saw the "waiting for network to be up" followed by +OK. If I now offer "ifup eth0" I get + +"Running in a chroot. ignoring request +bind: Cannot assign requested address +RTNETLINK answers: Network is unreachable +ERROR: [etc/sysconfig/network-scripts/ifup-eth] Error adding default +gateway 192.168.0.1 for eth0 +NETLINK: Error: File exists +and "sbin/ifup: configuration for eth. Ping tells me that the network +is unreachable. +Running in a chroot. ignoring request" + +>><i> That's what I thought, but still after "exit" I get the "Running +</I>>><i> in chroot" messages :-( +</I>><i> +</I>><i> It's odd that a rescue system brought up through a network +</I>><i> connection doesn't have it at runtime. +</I> +I'm running the rescue system from the DVD, not through a network. + +><i> Maybe try Colin's suggestion from the rescue system +</I>><i> +</I>I did, this time. + +>><i> +</I>>><i> As usual, lots of detail if you already understand it, but it +</I>>><i> seems to rely on you knowing URLs. I thought I could simply copy +</I>>><i> the URL from this system, adapting the version if it looked +</I>>><i> necessary, but if I look at Edit on the add-media page of MCC it +</I>>><i> just says $MIRRORLIST - and "echo $MIRRORLIST" doesn't tell me +</I>>><i> anything at all. +</I>><i> +</I>><i> The syntax won't be identical, but you can get an idea of the URL +</I>><i> to use by looking in /etc/urpmi/urpmi.cfg on your root partition to +</I>><i> see what's being used for "core release". +</I>><i> +</I>OK, if I can get the network up I'll see what I can do along those lines. + +>><i> There's obviously a real problem with the Intel drivers being +</I>>><i> removed by accident during the update. For everyone's sake, I'd +</I>>><i> like to try to identify the problem, but I feel as though I'm +</I>>><i> banging my head against a brick wall. +</I>><i> +</I>><i> There are really two issues here. One is getting your system to +</I>><i> work again. The other is finding out what went wrong to begin +</I>><i> with. +</I> +I was hoping that we would be able to find some trace of what went +wrong as we are working with this,l but by now maybe any relevant logs +will be destroyed. + +><i> For the latter, you should probably open a bug describing exactly +</I>><i> what you did in the initial upgrade, and attaching the files from +</I>><i> /root/drakx. +</I> +I had intended to, but hoped to have more information before I do +that. I have copied /root/drakx to /root/drakx-sav - hopefully this +will preserve all we need. + +><i> I've never done a distro upgrade myself, +</I> +Out of curiosity I tried the distro upgrade. It appeared to complete, +but booted to a blank screen, so I didn't waste any more time on it. +I started afresh and did a clean install (though keeping /home). + +Something occurred to me today that may or may not be relevant. This +problem with the Intel drivers being removed may not be a very new +problem. I was running Cauldron successfully on this netbook for a +long time, up to early January. Then I went away for three weeks. +When I returned near the end of January I switched on and did a big +update. After that I had a black screen, much like the current one. + +I thought it might be because something important had happened while I +was away so that I had not made a necessary change at the right time, +so I waited for the opportunity to do this install. It may be, then, +that this was my first experience of this same bug. + +><i> If all else fails (and after you attach the files to the new bug), +</I>><i> you could try re-running the upgrade. If you can get to package +</I>><i> selection, "Individual Package Selection" may get you what you +</I>><i> need, and Summary will allow you to configure video and network. +</I>><i> But this will overlay the /root/drakx files. +</I> +As I said earlier, it was a clean install, not an upgrade, and it +completed perfectly. I then rebooted as usual, and immediately used +MCC to add all other media sources, and did the big update. This is +when it went pear-shaped. + +Anne +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) +Comment: Using GnuPG with Thunderbird - <A HREF="http://www.enigmail.net/">http://www.enigmail.net/</A> + +iEYEARECAAYFAlFlrYkACgkQj93fyh4cnBfrPQCcCjc1VZZITOie+oPkkejgVAJT +4KQAn1kxdbyQ876yjuXjnRRDhf7lvp/I +=V+vZ +-----END PGP SIGNATURE----- +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="024340.html">[Mageia-dev] M3 beta - where to report problems? +</A></li> + <LI>Next message: <A HREF="024346.html">[Mageia-dev] M3 beta - where to report problems? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#24345">[ date ]</a> + <a href="thread.html#24345">[ thread ]</a> + <a href="subject.html#24345">[ subject ]</a> + <a href="author.html#24345">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |