-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
-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
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
'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.
-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.
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,
-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
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
-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
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
-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
-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.
-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
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
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
-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,
-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)
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
-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
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
-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
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
-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
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
'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
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
'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
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
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
-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
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
-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
-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
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
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:
-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 :)
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 :)
-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
38 matches
Mail list logo
