Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 21:56, Frank Griffin wrote: Wow. I was assuming all along that the problem stemmed from a massive upgrade from some MGA2 system. If you installed a 3rd April beta, had it working perfectly, and something uploaded to cauldron in the last week borked your system, I have no clue. And the fact that you've done this repeatedly indicates that it's not just an unstable mirror or some such. I wouldn't bother with the bug report for the /root/drakx stuff, since the install itself worked fine and gave you a working system. It's whatever came after that in the update that did the deed. If you have access to wired internet, is it possible for you to redo the clean install as a network install from a cauldron mirror ? It doesn't have to be a full install, as a minimal system (Custom and uncheck all the heavy stuff, just leave KDE as desktop) should give you an X environment to test. It would be interesting to know if a clean install of current cauldron exhibits the same problems on your hardware. I'm willing to try this, though I've no idea how to do it - it's something I've never attempted before. I think I have to download a boot.iso - is that right? What do you consider heavy stuff? I always disable desktop effects. What is installed by default that I could do without at this stage? If you can give me brief instructions I'll try to do this today. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFmdpkACgkQj93fyh4cnBcYgwCfanz8a49xpHDZX7x4hu/QGYgK uX8Ani4lTWZkDRdl4EvIcxAWiaw79/Ef =/Zmq -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 20:48, Frank Griffin wrote: On 04/08/2013 02:41 PM, Anne Wilson wrote: No, it doesn't. When I ran XFdrake the test did display colours, though at a resolution I wouldn't want to work with :-) However, on reboot I still have a backlit black screen. I'm sure you are on the right track. It's not radeon, though, it's Intel 810 and later. I see that listed in XFdrake, but if I try to use it I'm told that there are no screens. Not sure what that means, though. When booting into rescue, I saw several items listed as Intel Corporation:NM10/ICH7 Family which sounds right to me. So - I need Intel drivers (and firmware). Can I use the same rescue processes to get the Internet working so that I can download them? Odd, though, that even VESA didn't work. Let me get this straight. You ran XFdrake for VESA chrooted to your root partition, got a decent test, and the real boot *still* screws up ? Weird. If you follow the process I gave, you should be able to start the network from within the chroot (provided you were able to start it from the rescue boot), or else it should already be up. You should then be able to run urpmi from within the chroot to install the firmware packages from nonfree. You'll need at least kernel-firmware-nonfree. Here's what else is there: [root@ftgme2 ftg]# cd /mnt/cauldron/x86_64/media/nonfree/release [root@ftgme2 release]# ls *firm* atmel-firmware-1.3-5.mga3.nonfree.noarch.rpm bluez-firmware-1.2-9.mga3.nonfree.noarch.rpm ipw2100-firmware-1.3-5.mga3.nonfree.noarch.rpm ipw2200-firmware-3.1-3.mga3.nonfree.noarch.rpm ivtv-firmware-20080701-1.mga3.nonfree.noarch.rpm kernel-firmware-nonfree-20130307-1.mga3.nonfree.noarch.rpm radeon-firmware-20120322-5.mga3.nonfree.noarch.rpm ralink-firmware-20130307-1.mga3.nonfree.noarch.rpm rtlwifi-firmware-20130307-1.mga3.nonfree.noarch.rpm speedtouch-firmware-0.1-10.mga3.nonfree.noarch.rpm If that doesn't work, then it sounds like your TTY configuration is screwed, and if that's the case, I'm tapped out. Colin would probably be the best one to ask what controls getty under systemd and how it's configured. I went through the following steps again: 1) Boot the rescue system 2) drvinst 3) mount your root as /mnt 4) do a mount --bind /dev /mnt/dev 5) do a chroot /mnt 6) do a mount -t proc none /proc 7) do a mount -t sysfs none /sys 8) do XFdrake 9) choose the x11 VESA or VGA driver (way down at bottom of list) except that this time I chose the Other:VESA (generic) driver. On closing XFdrake I got ioctl EVIOCGBIT failed: Inappropriate ioctl for device Is this to be expected? Anyway, on reboot it was exactly the same as before. Starting afresh, I followed the steps up to running XFdrake (but not running XFdrake yet). I tried 'ifup eth0' but 'Running in chroot. Ignoring request'. After exit this changed to Running in chroot. ignoring request. ./network-functions: line 260: cd: /var/run/netreport: No such file or directory. Incidentally, how do you reboot or shutdown when in chroot - and/or how do you reverse the chroot? So - I'm back in console, without running any of the steps yet. Can you give me the command to add the non-free source and tell me how to get eth0 working? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFlK3wACgkQj93fyh4cnBdNUgCeN1y9uB2DAkfJoueP3Fd9iVG1 Ci8AnidZeNz0E7+YTtxC1OpWPkPPaGwx =Rq2y -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/10/2013 05:06 AM, Anne Wilson wrote: I went through the following steps again: 1) Boot the rescue system 2) drvinst 3) mount your root as /mnt 4) do a mount --bind /dev /mnt/dev 5) do a chroot /mnt 6) do a mount -t proc none /proc 7) do a mount -t sysfs none /sys 8) do XFdrake 9) choose the x11 VESA or VGA driver (way down at bottom of list) except that this time I chose the Other:VESA (generic) driver. On closing XFdrake I got ioctl EVIOCGBIT failed: Inappropriate ioctl for device Is this to be expected? Anyway, on reboot it was exactly the same as before. No idea, sorry. Starting afresh, I followed the steps up to running XFdrake (but not running XFdrake yet). I tried 'ifup eth0' but 'Running in chroot. Ignoring request'. After exit this changed to Running in chroot. ignoring request. ./network-functions: line 260: cd: /var/run/netreport: No such file or directory. I guess just bring up eth0 before entering the chroot Incidentally, how do you reboot or shutdown when in chroot - and/or how do you reverse the chroot? chroot starts a shell. When you exit from that shell, you're out of the chroot. An ls /mnt should indicate where you are: if you see all of your root partition's root directories, you're out of it. Inside it, /mnt will contain whatever it contains on your root partition (if it even exists). So - I'm back in console, without running any of the steps yet. Can you give me the command to add the non-free source and tell me how to get eth0 working? It's urpmi.addmedia', but the exact syntax depends on where your mirror is. Check the man page.
Re: [Mageia-dev] M3 beta - where to report problems?
'Twas brillig, and Frank Griffin at 10/04/13 12:00 did gyre and gimble: Starting afresh, I followed the steps up to running XFdrake (but not running XFdrake yet). I tried 'ifup eth0' but 'Running in chroot. Ignoring request'. After exit this changed to Running in chroot. ignoring request. ./network-functions: line 260: cd: /var/run/netreport: No such file or directory. I guess just bring up eth0 before entering the chroot After entering the chroot, you can also do: mount -t tmpfs none /run systemd-tmpfiles --create rm -f /run/nologin That should initialise all the temporary files you might need for a running system. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 12:00, Frank Griffin wrote: Starting afresh, I followed the steps up to running XFdrake (but not running XFdrake yet). I tried 'ifup eth0' but 'Running in chroot. Ignoring request'. After exit this changed to Running in chroot. ignoring request. ./network-functions: line 260: cd: /var/run/netreport: No such file or directory. I guess just bring up eth0 before entering the chroot ifup: configuration for eth0 not found - I had already tried that. Incidentally, how do you reboot or shutdown when in chroot - and/or how do you reverse the chroot? chroot starts a shell. When you exit from that shell, you're out of the chroot. An ls /mnt should indicate where you are: if you see all of your root partition's root directories, you're out of it. Inside it, /mnt will contain whatever it contains on your root partition (if it even exists). That's what I thought, but still after exit I get the Running in chroot messages :-( So - I'm back in console, without running any of the steps yet. Can you give me the command to add the non-free source and tell me how to get eth0 working? It's urpmi.addmedia', but the exact syntax depends on where your mirror is. Check the man page. As usual, lots of detail if you already understand it, but it seems to rely on you knowing URLs. I thought I could simply copy the URL from this system, adapting the version if it looked necessary, but if I look at Edit on the add-media page of MCC it just says $MIRRORLIST - and echo $MIRRORLIST doesn't tell me anything at all. There's obviously a real problem with the Intel drivers being removed by accident during the update. For everyone's sake, I'd like to try to identify the problem, but I feel as though I'm banging my head against a brick wall. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFlTWoACgkQj93fyh4cnBfiNwCePLNYEFijQJcq7dzH1TUGSOfx G5UAn2x2U3C068Cpvv0F8RzJ1KF6NkPi =DBAF -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/10/2013 07:31 AM, Anne Wilson wrote: ifup: configuration for eth0 not found - I had already tried that. Interesting. I guess you didn't configure eth0 from the Install Summary. You can do it from the chroot (using Colin's suggestion) by running drakconnect. That's what I thought, but still after exit I get the Running in chroot messages :-( It's odd that a rescue system brought up through a network connection doesn't have it at runtime. Maybe try Colin's suggestion from the rescue system ? As usual, lots of detail if you already understand it, but it seems to rely on you knowing URLs. I thought I could simply copy the URL from this system, adapting the version if it looked necessary, but if I look at Edit on the add-media page of MCC it just says $MIRRORLIST - and echo $MIRRORLIST doesn't tell me anything at all. The syntax won't be identical, but you can get an idea of the URL to use by looking in /etc/urpmi/urpmi.cfg on your root partition to see what's being used for core release. There's obviously a real problem with the Intel drivers being removed by accident during the update. For everyone's sake, I'd like to try to identify the problem, but I feel as though I'm banging my head against a brick wall. There are really two issues here. One is getting your system to work again. The other is finding out what went wrong to begin with. For the latter, you should probably open a bug describing exactly what you did in the initial upgrade, and attaching the files from /root/drakx. I've never done a distro upgrade myself, as I install multiple fairly identical systems, and I keep a set of post-install scripts to bring a newly-installed system to the same state as a previous one. So I know virtually nil about the internals of how an upgrade actually works. If all else fails (and after you attach the files to the new bug), you could try re-running the upgrade. If you can get to package selection, Individual Package Selection may get you what you need, and Summary will allow you to configure video and network. But this will overlay the /root/drakx files.
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 13:07, Frank Griffin wrote: On 04/10/2013 07:31 AM, Anne Wilson wrote: I think there may be some misunderstandings, so I'll try to correct them inline. Interesting. I guess you didn't configure eth0 from the Install Summary. I configured it to use dhcp, since netbooks are used in other places (I use the hotel cabled network when in Madeira). You can do it from the chroot (using Colin's suggestion) by running drakconnect. 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 That's what I thought, but still after exit I get the Running in chroot messages :-( It's odd that a rescue system brought up through a network connection doesn't have it at runtime. I'm running the rescue system from the DVD, not through a network. Maybe try Colin's suggestion from the rescue system I did, this time. As usual, lots of detail if you already understand it, but it seems to rely on you knowing URLs. I thought I could simply copy the URL from this system, adapting the version if it looked necessary, but if I look at Edit on the add-media page of MCC it just says $MIRRORLIST - and echo $MIRRORLIST doesn't tell me anything at all. The syntax won't be identical, but you can get an idea of the URL to use by looking in /etc/urpmi/urpmi.cfg on your root partition to see what's being used for core release. OK, if I can get the network up I'll see what I can do along those lines. There's obviously a real problem with the Intel drivers being removed by accident during the update. For everyone's sake, I'd like to try to identify the problem, but I feel as though I'm banging my head against a brick wall. There are really two issues here. One is getting your system to work again. The other is finding out what went wrong to begin with. 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. For the latter, you should probably open a bug describing exactly what you did in the initial upgrade, and attaching the files from /root/drakx. 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've never done a distro upgrade myself, 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. If all else fails (and after you attach the files to the new bug), you could try re-running the upgrade. If you can get to package selection, Individual Package Selection may get you what you need, and Summary will allow you to configure video and network. But this will overlay the /root/drakx files. 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 - http://www.enigmail.net/ iEYEARECAAYFAlFlrYkACgkQj93fyh4cnBfrPQCcCjc1VZZITOie+oPkkejgVAJT 4KQAn1kxdbyQ876yjuXjnRRDhf7lvp/I =V+vZ -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/10/2013 02:21 PM, Anne Wilson wrote: 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. ... 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. OK, so what did you do the clean install from ? From this last bit, it sounds like it was working after the install if you could boot and use MCC to add other media. I'm curious as to the timeframe window of what you installed and what you updated to.
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/13 19:50, Frank Griffin wrote: On 04/10/2013 02:21 PM, Anne Wilson wrote: 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. ... 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. OK, so what did you do the clean install from ? From this last bit, it sounds like it was working after the install if you could boot and use MCC to add other media. I'm curious as to the timeframe window of what you installed and what you updated to. I downloaded the latest beta - and checked the sha1sum before installing. It worked perfectly. I configured eth0 as dhcp, knowing that I'd have to get the wifi drivers later. I did the update immediately after the install - that would be the 3rd April, when I started this thread. I've now got those files from /root/drakx onto a usb stick - should I start the bug report now with those files? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFlvk4ACgkQj93fyh4cnBctCQCgiZZqTXCtTghyuFAB5wu6EeoT XRMAmwYR7dHQTf6fzt/qzIQW7N9MS09e =ksb8 -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/10/2013 03:32 PM, Anne Wilson wrote: I downloaded the latest beta - and checked the sha1sum before installing. It worked perfectly. I configured eth0 as dhcp, knowing that I'd have to get the wifi drivers later. I did the update immediately after the install - that would be the 3rd April, when I started this thread. I've now got those files from /root/drakx onto a usb stick - should I start the bug report now with those files? Wow. I was assuming all along that the problem stemmed from a massive upgrade from some MGA2 system. If you installed a 3rd April beta, had it working perfectly, and something uploaded to cauldron in the last week borked your system, I have no clue. And the fact that you've done this repeatedly indicates that it's not just an unstable mirror or some such. I wouldn't bother with the bug report for the /root/drakx stuff, since the install itself worked fine and gave you a working system. It's whatever came after that in the update that did the deed. If you have access to wired internet, is it possible for you to redo the clean install as a network install from a cauldron mirror ? It doesn't have to be a full install, as a minimal system (Custom and uncheck all the heavy stuff, just leave KDE as desktop) should give you an X environment to test. It would be interesting to know if a clean install of current cauldron exhibits the same problems on your hardware.
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 22:49, Colin Guthrie wrote: 'Twas brillig, and Thomas Backlund at 08/04/13 22:43 did gyre and gimble: Colin Guthrie skrev 9.4.2013 00:31: 'Twas brillig, and Thomas Backlund at 08/04/13 13:20 did gyre and gimble: It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 Or simply add a 3 onto the command line as has been the case for many years :) Of course I should probably discourage that seeing as 3 is pretty meaningless in absolute terms these days! :) Are you sure ? IIRC there has been reports of people doing it and still eneded up at graphical.target ... Hmm, well the code suggests it should... will have to try it :) That was the first thing I tried - with and without removing quiet and splash. It's the way I've always done it in the past, but it didn't work this time. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFj2A4ACgkQj93fyh4cnBdixgCdEavsqTsSqJPXCnB8iJCX3Ydu QzUAniE2Xt53MFY/ZtP0JA4zH9jtZ9Xv =TQG0 -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/13 00:55, David W. Hodgins wrote: On Mon, 08 Apr 2013 12:52:06 -0400, Anne Wilson an...@kde.org wrote: Rebooting, nothing has changed. I get grub, lots of disk activity led flickering, but no output to the screen, with or without Esc. I can boot into Safe moade, which lands me in Rescue Mode - but I haven't a clue what to do next. Try editing the kernel parameters in grub. Remove splash quiet, if present. Add 3 xdriver=vesa. The 3 gets translated by systemd to systemd.unit=multi-user.target, is shorter to type, and easier to remember. That did get a different result. At least this time I can see messages. There are lots that start with '?' including a panic, sys_exit and sysenter_do_call followed by ---[ end trace 09827c16e6de5433 ] Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFj2VsACgkQj93fyh4cnBc9ZACfbwxQg2i2X13vGnCS/Tg1zMLb yZMAn1FIvImMXBjJDVPn/g6hTKoGFP1N =+UJ6 -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 20:48, Frank Griffin wrote: On 04/08/2013 02:41 PM, Anne Wilson wrote: No, it doesn't. When I ran XFdrake the test did display colours, though at a resolution I wouldn't want to work with :-) However, on reboot I still have a backlit black screen. I'm sure you are on the right track. It's not radeon, though, it's Intel 810 and later. I see that listed in XFdrake, but if I try to use it I'm told that there are no screens. Not sure what that means, though. When booting into rescue, I saw several items listed as Intel Corporation:NM10/ICH7 Family which sounds right to me. So - I need Intel drivers (and firmware). Can I use the same rescue processes to get the Internet working so that I can download them? Odd, though, that even VESA didn't work. Let me get this straight. You ran XFdrake for VESA chrooted to your root partition, got a decent test, and the real boot *still* screws up ? Weird. Yes, exactly that. If you follow the process I gave, you should be able to start the network from within the chroot (provided you were able to start it from the rescue boot), or else it should already be up. You should then be able to run urpmi from within the chroot to install the firmware packages from nonfree. You'll need at least kernel-firmware-nonfree. Here's what else is there: [root@ftgme2 ftg]# cd /mnt/cauldron/x86_64/media/nonfree/release [root@ftgme2 release]# ls *firm* atmel-firmware-1.3-5.mga3.nonfree.noarch.rpm bluez-firmware-1.2-9.mga3.nonfree.noarch.rpm ipw2100-firmware-1.3-5.mga3.nonfree.noarch.rpm ipw2200-firmware-3.1-3.mga3.nonfree.noarch.rpm ivtv-firmware-20080701-1.mga3.nonfree.noarch.rpm kernel-firmware-nonfree-20130307-1.mga3.nonfree.noarch.rpm radeon-firmware-20120322-5.mga3.nonfree.noarch.rpm ralink-firmware-20130307-1.mga3.nonfree.noarch.rpm rtlwifi-firmware-20130307-1.mga3.nonfree.noarch.rpm speedtouch-firmware-0.1-10.mga3.nonfree.noarch.rpm If that doesn't work, then it sounds like your TTY configuration is screwed, and if that's the case, I'm tapped out. Colin would probably be the best one to ask what controls getty under systemd and how it's configured. I'll try to get these, though in the light of what I saw a few minutes ago (see reply to David) I'm not sure that this is going to work. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFj2fwACgkQj93fyh4cnBd0NgCffE7eSBv4MOTORIIgiOazkaq5 0HcAmQGJcYh2pKTwOBIyS1Syk4py0YpT =oh3Z -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/07/2013 11:25 AM, Anne Wilson wrote: Sorry to be a pain, Frank, but I've never been able to understand the Rescue mode. Everything I've tried fails. How exactly do you mount your root partition? I went to Console, but every command I tried failed. I then tried the mount under /mnt and messed up the link. For some reason, even after all this time, I never know exactly what it intends me to do. OK, you have two choices. if you have a local cauldron mirror or can do network installs, you can boot isolinux or boot.iso and type rescue at the initial text screen prompt. From there on, you pick a mirror as you would for a network install, and the only difference is that it will load the rescue kernel and run the rescue application rather than the standard install. Or, you can boot the classic install ISO, and one of the GUI choices should be Rescue. Once you get the Rescue panel, select Go to Console. Then type drvinst, since rescue tends to lag modern hardware, and probably won't see SATA disks without the additional drivers. Then mount your root partition. Rescue provides a /mnt node, so you can use mount -t ext4 /dev/sdaX /mnt You can then make the symlink modifications in /mnt/etc/systemd/system and reboot from the root partition.
Re: [Mageia-dev] M3 beta - where to report problems?
Frank Griffin skrev 4.4.2013 19:12: On 04/04/2013 10:59 AM, Anne Wilson wrote: Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Boot a rescue disk and mount your root partition. In /etc/systemd/system you should see a symlink like: lrwxrwxrwx 1 root root 36 Mar 29 11:00 default.target - /lib/systemd/system/runlevel5.target Just remove this and re-symlink to /lib/systemd/system/runlevel3.target and you should get a level 3 boot. It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 -- Thomas
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 13:12, Frank Griffin wrote: Or, you can boot the classic install ISO, and one of the GUI choices should be Rescue. Once you get the Rescue panel, select Go to Console. Then type drvinst, since rescue tends to lag modern hardware, and probably won't see SATA disks without the additional drivers. Then mount your root partition. Rescue provides a /mnt node, so you can use mount -t ext4 /dev/sdaX /mnt You can then make the symlink modifications in /mnt/etc/systemd/system and reboot from the root partition. modprobe: FATAL: Module shpchp not found modprobe: FATAL: Module snd_hda_intel not found How do I get these? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFi3FQACgkQj93fyh4cnBf26QCfVrKaVRZhJFtcZrnHNyKtO/Jr 2e8AnAmDiCkQ6YH2k+GVX9SECj0wcHeP =P0Bp -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 13:20, Thomas Backlund wrote: Frank Griffin skrev 4.4.2013 19:12: On 04/04/2013 10:59 AM, Anne Wilson wrote: Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Boot a rescue disk and mount your root partition. In /etc/systemd/system you should see a symlink like: lrwxrwxrwx 1 root root 36 Mar 29 11:00 default.target - /lib/systemd/system/runlevel5.target Just remove this and re-symlink to /lib/systemd/system/runlevel3.target and you should get a level 3 boot. It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 Noted, for when I get the drivers fixed :-) Thanks Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFi3JEACgkQj93fyh4cnBd0zACePfa3pMuZ0146AYihYtPYsVUp rXIAnjSgncPQ6EiA/OwLnB4kR3bW7X60 =2qAZ -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/08/2013 11:03 AM, Anne Wilson wrote: modprobe: FATAL: Module shpchp not found modprobe: FATAL: Module snd_hda_intel not found How do I get these? I'm not sure why a rescue system would need either of them. I guesss you get these messages from drvinst; I get some sililar ones myself (in my case, snd_intel8x0 and vboxguest), but it doesn't impact the usability of the rescue system. I don't know how drvinst decides what it will try to load versus what is actually available in the rescue module set. I would just ignore these and push on.
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 16:37, Frank Griffin wrote: On 04/08/2013 11:03 AM, Anne Wilson wrote: modprobe: FATAL: Module shpchp not found modprobe: FATAL: Module snd_hda_intel not found How do I get these? I'm not sure why a rescue system would need either of them. I guesss you get these messages from drvinst; I get some sililar ones myself (in my case, snd_intel8x0 and vboxguest), but it doesn't impact the usability of the rescue system. I don't know how drvinst decides what it will try to load versus what is actually available in the rescue module set. I would just ignore these and push on. OK, moving on. Listing /mnt/etc/systemd/system/ I have no default.target link, so I assume I have to make one. Is that ln -s /lib/systemd/system/runlevel3.target /mnt/etc/systemd/system/default.target ? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFi7JsACgkQj93fyh4cnBfUdACfWsJAXJC5rI0y/yxrl85pv3Qc yCAAnjV9tYuc8UeLCkkCeddeTvdzSFlH =acPn -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/08/2013 12:13 PM, Anne Wilson wrote: OK, moving on. Listing /mnt/etc/systemd/system/ I have no default.target link, so I assume I have to make one. Is that ln -s /lib/systemd/system/runlevel3.target /mnt/etc/systemd/system/default.target ? Actually, you probably want to first chroot /mnt and then use ln -s /lib/systemd/system/runlevel3.target /etc/systemd/system/default.target as I can't swear offhand what the effect of linking in the rescue system with the leading /mnt would be. Or, you can equally well edit /mnt/boot/grub/menu.lst and use Thomas' suggestion. But it's odd that you don't have a default link already.
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 17:22, Frank Griffin wrote: On 04/08/2013 12:13 PM, Anne Wilson wrote: OK, moving on. Listing /mnt/etc/systemd/system/ I have no default.target link, so I assume I have to make one. Is that ln -s /lib/systemd/system/runlevel3.target /mnt/etc/systemd/system/default.target ? Actually, you probably want to first chroot /mnt and then use ln -s /lib/systemd/system/runlevel3.target /etc/systemd/system/default.target as I can't swear offhand what the effect of linking in the rescue system with the leading /mnt would be. Or, you can equally well edit /mnt/boot/grub/menu.lst and use Thomas' suggestion. But it's odd that you don't have a default link already. Something very odd is happening, indeed. Remember this was a functioning system before I did the updates. Rebooting, nothing has changed. I get grub, lots of disk activity led flickering, but no output to the screen, with or without Esc. I can boot into Safe moade, which lands me in Rescue Mode - but I haven't a clue what to do next. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFi9bQACgkQj93fyh4cnBeZ8QCcC4epBJgJd4ugK8medhpi4z8h ciQAni276WK4s3YNc+oOHWvvOIUmb1WD =4901 -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/08/2013 12:52 PM, Anne Wilson wrote: Something very odd is happening, indeed. Remember this was a functioning system before I did the updates. Rebooting, nothing has changed. I get grub, lots of disk activity led flickering, but no output to the screen, with or without Esc. I can boot into Safe moade, which lands me in Rescue Mode - but I haven't a clue what to do next. If you don't even get text mode, this sounds like the old problem of radeon drivers which require nonfree firmware not having the firmware available. There was a long stretch where, if you had such a card, you needed to install with the x11 vesa driver, boot, install the firmware, and then use XFdrake to switch to the radeon driver. Do you have a card that uses the radeon driver ? If so, did you enable nonfree during the upgrade ? You can try the following: 1) Boot the rescue system 2) drvinst 3) mount your root as /mnt 4) do a mount --bind /dev /mnt/dev 5) do a chroot /mnt 6) do a mount -t proc none /proc 7) do a mount -t sysfs none /sys 8) do XFdrake 9) choose the x11 VESA or VGA driver (way down at bottom of list) 10) reboot and see if TTY mode now works If it does, then add nonfree as a urpmi repository and install the nonfree radeon firmware package. Then run XFdrake in the real system to set yourself back to the radeon driver that XFdrake should default to. If you're not using radeon, you may want to do (1) - (10) anyway just to see if your system works with the basic driver.
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/13 18:28, Frank Griffin wrote: On 04/08/2013 12:52 PM, Anne Wilson wrote: Something very odd is happening, indeed. Remember this was a functioning system before I did the updates. Rebooting, nothing has changed. I get grub, lots of disk activity led flickering, but no output to the screen, with or without Esc. I can boot into Safe moade, which lands me in Rescue Mode - but I haven't a clue what to do next. If you don't even get text mode, this sounds like the old problem of radeon drivers which require nonfree firmware not having the firmware available. There was a long stretch where, if you had such a card, you needed to install with the x11 vesa driver, boot, install the firmware, and then use XFdrake to switch to the radeon driver. Do you have a card that uses the radeon driver ? If so, did you enable nonfree during the upgrade ? You can try the following: 1) Boot the rescue system 2) drvinst 3) mount your root as /mnt 4) do a mount --bind /dev /mnt/dev 5) do a chroot /mnt 6) do a mount -t proc none /proc 7) do a mount -t sysfs none /sys 8) do XFdrake 9) choose the x11 VESA or VGA driver (way down at bottom of list) 10) reboot and see if TTY mode now works If it does, then add nonfree as a urpmi repository and install the nonfree radeon firmware package. Then run XFdrake in the real system to set yourself back to the radeon driver that XFdrake should default to. If you're not using radeon, you may want to do (1) - (10) anyway just to see if your system works with the basic driver. No, it doesn't. When I ran XFdrake the test did display colours, though at a resolution I wouldn't want to work with :-) However, on reboot I still have a backlit black screen. I'm sure you are on the right track. It's not radeon, though, it's Intel 810 and later. I see that listed in XFdrake, but if I try to use it I'm told that there are no screens. Not sure what that means, though. When booting into rescue, I saw several items listed as Intel Corporation:NM10/ICH7 Family which sounds right to me. So - I need Intel drivers (and firmware). Can I use the same rescue processes to get the Internet working so that I can download them? Odd, though, that even VESA didn't work. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFjD0YACgkQj93fyh4cnBdK/QCfcK0zbk70QoyCrn1TID+OCmLy oiMAn03GaoFmsCIZP4xwfK1NS1bleEQp =zWqb -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/08/2013 02:41 PM, Anne Wilson wrote: No, it doesn't. When I ran XFdrake the test did display colours, though at a resolution I wouldn't want to work with :-) However, on reboot I still have a backlit black screen. I'm sure you are on the right track. It's not radeon, though, it's Intel 810 and later. I see that listed in XFdrake, but if I try to use it I'm told that there are no screens. Not sure what that means, though. When booting into rescue, I saw several items listed as Intel Corporation:NM10/ICH7 Family which sounds right to me. So - I need Intel drivers (and firmware). Can I use the same rescue processes to get the Internet working so that I can download them? Odd, though, that even VESA didn't work. Let me get this straight. You ran XFdrake for VESA chrooted to your root partition, got a decent test, and the real boot *still* screws up ? Weird. If you follow the process I gave, you should be able to start the network from within the chroot (provided you were able to start it from the rescue boot), or else it should already be up. You should then be able to run urpmi from within the chroot to install the firmware packages from nonfree. You'll need at least kernel-firmware-nonfree. Here's what else is there: [root@ftgme2 ftg]# cd /mnt/cauldron/x86_64/media/nonfree/release [root@ftgme2 release]# ls *firm* atmel-firmware-1.3-5.mga3.nonfree.noarch.rpm bluez-firmware-1.2-9.mga3.nonfree.noarch.rpm ipw2100-firmware-1.3-5.mga3.nonfree.noarch.rpm ipw2200-firmware-3.1-3.mga3.nonfree.noarch.rpm ivtv-firmware-20080701-1.mga3.nonfree.noarch.rpm kernel-firmware-nonfree-20130307-1.mga3.nonfree.noarch.rpm radeon-firmware-20120322-5.mga3.nonfree.noarch.rpm ralink-firmware-20130307-1.mga3.nonfree.noarch.rpm rtlwifi-firmware-20130307-1.mga3.nonfree.noarch.rpm speedtouch-firmware-0.1-10.mga3.nonfree.noarch.rpm If that doesn't work, then it sounds like your TTY configuration is screwed, and if that's the case, I'm tapped out. Colin would probably be the best one to ask what controls getty under systemd and how it's configured.
Re: [Mageia-dev] M3 beta - where to report problems?
'Twas brillig, and Thomas Backlund at 08/04/13 13:20 did gyre and gimble: Frank Griffin skrev 4.4.2013 19:12: On 04/04/2013 10:59 AM, Anne Wilson wrote: Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Boot a rescue disk and mount your root partition. In /etc/systemd/system you should see a symlink like: lrwxrwxrwx 1 root root 36 Mar 29 11:00 default.target - /lib/systemd/system/runlevel5.target Just remove this and re-symlink to /lib/systemd/system/runlevel3.target and you should get a level 3 boot. It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 Or simply add a 3 onto the command line as has been the case for many years :) Of course I should probably discourage that seeing as 3 is pretty meaningless in absolute terms these days! :) Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] M3 beta - where to report problems?
Colin Guthrie skrev 9.4.2013 00:31: 'Twas brillig, and Thomas Backlund at 08/04/13 13:20 did gyre and gimble: It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 Or simply add a 3 onto the command line as has been the case for many years :) Of course I should probably discourage that seeing as 3 is pretty meaningless in absolute terms these days! :) Are you sure ? IIRC there has been reports of people doing it and still eneded up at graphical.target ... -- Thomas
Re: [Mageia-dev] M3 beta - where to report problems?
'Twas brillig, and Thomas Backlund at 08/04/13 22:43 did gyre and gimble: Colin Guthrie skrev 9.4.2013 00:31: 'Twas brillig, and Thomas Backlund at 08/04/13 13:20 did gyre and gimble: It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 Or simply add a 3 onto the command line as has been the case for many years :) Of course I should probably discourage that seeing as 3 is pretty meaningless in absolute terms these days! :) Are you sure ? IIRC there has been reports of people doing it and still eneded up at graphical.target ... Hmm, well the code suggests it should... will have to try it :) Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] M3 beta - where to report problems?
On Mon, 08 Apr 2013 12:52:06 -0400, Anne Wilson an...@kde.org wrote: Rebooting, nothing has changed. I get grub, lots of disk activity led flickering, but no output to the screen, with or without Esc. I can boot into Safe moade, which lands me in Rescue Mode - but I haven't a clue what to do next. Try editing the kernel parameters in grub. Remove splash quiet, if present. Add 3 xdriver=vesa. The 3 gets translated by systemd to systemd.unit=multi-user.target, is shorter to type, and easier to remember. Regards, Dave Hodgins
Re: [Mageia-dev] M3 beta - where to report problems?
On Mon, 08 Apr 2013 17:43:38 -0400, Thomas Backlund t...@mageia.org wrote: Colin Guthrie skrev 9.4.2013 00:31: 'Twas brillig, and Thomas Backlund at 08/04/13 13:20 did gyre and gimble: It's actually easier than that. Add systemd.unit=multi-user.target on kernel / grub command line and ith will boot to runlevel 3 Or simply add a 3 onto the command line as has been the case for many years :) Of course I should probably discourage that seeing as 3 is pretty meaningless in absolute terms these days! :) Are you sure ? IIRC there has been reports of people doing it and still eneded up at graphical.target ... I tested with an install from Mageia 3 beta 4, and can confirm it still works. Regards, Dave Hodgins
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/13 17:12, Frank Griffin wrote: On 04/04/2013 10:59 AM, Anne Wilson wrote: Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Boot a rescue disk and mount your root partition. In /etc/systemd/system you should see a symlink like: lrwxrwxrwx 1 root root 36 Mar 29 11:00 default.target - /lib/systemd/system/runlevel5.target Just remove this and re-symlink to /lib/systemd/system/runlevel3.target and you should get a level 3 boot. I finally screwed things up altogether, to the point where it was easier to start afresh. Half way through the install it says An error occurred: ERROR: 'script' failed for dkms-broadcom-wl-5.100.82.112-10.mga3.nonfree.i586 Hitting OK results in the installation appearing to complete (exactly as it happened last time). Last time I updated during the install - this time I didn't. For both occasions, the next step is to go to MCC and install additional sources, then update. On this second occasion I was careful to omit all Testing sources - I had included them the first time. The update appeared to complete satisfactorily, with the expected warning to Reboot. However, the package listing window had remained on screen throughout the process, and briefly showed again the list of packages for updating - after a couple of seconds the package list window showed empty, with Quit available. On rebooting there was a good deal of disk activity light flickering, but a completely black screen. What is the most useful thing, to you, the developers? If you want me to troubleshoot you will need to give me fairly precise instructions. Similarly, if you want me to file a bug report, please indicate which version and package it should be against. If you don't see any value in this, I'll simply re-install M2. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFhc78ACgkQj93fyh4cnBcwOQCfeVJO4KyA9n/6Gxa+XJrS25Un iP4Aniq2XAB8NqrJe0rVMQC/B2rTnypd =H+tA -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/07/2013 09:25 AM, Anne Wilson wrote: On rebooting there was a good deal of disk activity light flickering, but a completely black screen. Follow the instructions to boot into level 3, and then try XFdrake from a root console to see how your video is configured. If everything else seems normal, that's the culprit.
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/04/13 14:48, Frank Griffin wrote: On 04/07/2013 09:25 AM, Anne Wilson wrote: On rebooting there was a good deal of disk activity light flickering, but a completely black screen. Follow the instructions to boot into level 3, and then try XFdrake from a root console to see how your video is configured. If everything else seems normal, that's the culprit. Sorry to be a pain, Frank, but I've never been able to understand the Rescue mode. Everything I've tried fails. How exactly do you mount your root partition? I went to Console, but every command I tried failed. I then tried the mount under /mnt and messed up the link. For some reason, even after all this time, I never know exactly what it intends me to do. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFhj9QACgkQj93fyh4cnBfRXQCbBr9cpIQuiPQHIhd1JZCxISrp 50UAnArVBRslIddxYAwUHq0qR745VXU7 =q+4w -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/13 17:50, Anne Wilson wrote: This is an Acer Aspire One 533, with Intel N550 chipset, everything on-board. I wasn't doing anything unusual, so there does seem to be a real problem. Tomorrow I'll try to get a console login - is there a boot log that I could rename to keep it so that you can see what went wrong? Maybe some other logs too? I don't want to jeopardise the chances of finding the cause of this. Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFdlToACgkQj93fyh4cnBdB+gCfdXhYmJtw/Eo5l79EDlS3yose jUcAnjxI4SnlAsUYqKP+k053NkQVkM4e =c5Ia -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
On 04/04/2013 10:59 AM, Anne Wilson wrote: Not much progress. My usual method of editing the kernel line to get a level 3 boot doesn't work - same blank (but lit) screen. Failsafe appears to be doing better - at least I can see messages. It reaches Reached target Multi-User Reached target Graphical Interface and there it sticks. Does that give any clue as to what is failing, and what I need to do to rescue the system? Boot a rescue disk and mount your root partition. In /etc/systemd/system you should see a symlink like: lrwxrwxrwx 1 root root 36 Mar 29 11:00 default.target - /lib/systemd/system/runlevel5.target Just remove this and re-symlink to /lib/systemd/system/runlevel3.target and you should get a level 3 boot.
Re: [Mageia-dev] M3 beta - where to report problems?
Le 03/04/2013 15:36, Anne Wilson a écrit : I've just come across a bug in the software installer - where should it be reported? Anne ON QA list, which I attached in cc, and on bugs.mageia.org :) -- Sandro Cazzaniga Jabber: kha...@jabber.fr Twitter: @Kharec signature.asc Description: OpenPGP digital signature
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/13 14:37, Sandro CAZZANIGA wrote: Le 03/04/2013 15:36, Anne Wilson a écrit : I've just come across a bug in the software installer - where should it be reported? Anne ON QA list, which I attached in cc, and on bugs.mageia.org :) Thanks. Since writing I've discovered that it's not simply what it appeared to be, so I'll have to get more precise information before I can report it. (I did look at bugs, but wasn't sure whether it should be against Cauldron or not) Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEUEARECAAYFAlFcMrEACgkQj93fyh4cnBdtZgCVHSffgjBl9bMQMc8rb6JzyLnj bQCeN1b5FsKSR1RpzYDUEadKtZh2GXY= =ixGr -END PGP SIGNATURE-
Re: [Mageia-dev] M3 beta - where to report problems?
Le 03/04/2013 15:46, Anne Wilson a écrit : On 03/04/13 14:37, Sandro CAZZANIGA wrote: Le 03/04/2013 15:36, Anne Wilson a écrit : I've just come across a bug in the software installer - where should it be reported? Anne ON QA list, which I attached in cc, and on bugs.mageia.org :) Thanks. Since writing I've discovered that it's not simply what it appeared to be, so I'll have to get more precise information before I can report it. (I did look at bugs, but wasn't sure whether it should be against Cauldron or not) Anne Take your time :) You can also take a look at bugs.mageia.org to see if your bugs is already reported or even known. -- Sandro Cazzaniga Jabber: kha...@jabber.fr Twitter: @Kharec signature.asc Description: OpenPGP digital signature
Re: [Mageia-dev] M3 beta - where to report problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/13 14:48, Sandro CAZZANIGA wrote: Le 03/04/2013 15:46, Anne Wilson a écrit : On 03/04/13 14:37, Sandro CAZZANIGA wrote: Le 03/04/2013 15:36, Anne Wilson a écrit : I've just come across a bug in the software installer - where should it be reported? Anne ON QA list, which I attached in cc, and on bugs.mageia.org :) Thanks. Since writing I've discovered that it's not simply what it appeared to be, so I'll have to get more precise information before I can report it. (I did look at bugs, but wasn't sure whether it should be against Cauldron or not) Anne Take your time :) You can also take a look at bugs.mageia.org to see if your bugs is already reported or even known. I did get that far - but then I probably wasn't searching for the right thing, in the light of what happened later. After installing a couple of apps I did the day's updates, which required a re-start for systemd, and it looks as though the update has taken out the video driver - perhaps it caused the black screens I saw there, though everything had been fine moments before. I can't face fighting this today - I'll have to trawl back through old emails and hope I can find the instructions from last time I lost video (that was removing obsoletes that took it out). This is an Acer Aspire One 533, with Intel N550 chipset, everything on-board. I wasn't doing anything unusual, so there does seem to be a real problem. Tomorrow I'll try to get a console login - is there a boot log that I could rename to keep it so that you can see what went wrong? Maybe some other logs too? I don't want to jeopardise the chances of finding the cause of this. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFcXbgACgkQj93fyh4cnBdIXQCeLQNv2d6d+VHaNSsyP8C0LCQq Ay8An0y1GF/WVIGjwOQATm8XU7Ac2Czx =c+DL -END PGP SIGNATURE-
