30 Jun
2011
30 Jun
'11
05:48
I am not experienced with Linux and this is my first attempt to load SUSE.
I downloaded the 32 bit version of the full DVD using bit torrent and
burned a DVD. I installed on my old Gateway with P-486 running 3 GHz
with 2 gig of memory. The install used the recommended partitioning and
appeared to run normally except that the re-boot to the hard drive
failed. (Note: The onscreen text did not say to remove the DVD as
stated in step 6 of the installation guide.) It displayed the green
screen with the logo in the center. The system did not respond to any
input. I did not record the time but the green screen was up for more
than 5 minutes before I forced a shutdown. The system was not connected
to my network and the only failures I noted on the BW list was network
connection were not established.
I restarted from the DVD and ran disk validation (100%), then reran the
installation with the same results described above. This time I left
the green screen up for at least 30 minutes to be sure some long running
process could complete. I removed the DVD, forced the shutdown and
re-stared the system. This time YaST2 automatic configuration started
but did not run to completion, ending with the system stalled and not
responding to any input.
So far, I have found no hints in the online information other than to
re-burn the DVD at a slower speed.
I did a re-download of openSUSE-11.4-DVD-i586.iso using FinalTorrent,
validated the both MD5 and sha1 checksum , burned a DVD but could not
control the speed, validated the burn, verified the media before running
a complete install. YaST2 stopped once during package install but
loaded the file after the retry. The system was connected to the
network for this installation. System restart appeared to run normally
up to about 3/4 of the progress bar. I forced the system to power down
after about an hour at this point. I have photos of most of the screens
presented in the installation.
Any additional suggestions or recommendations? Any suggestions on how
to research this issue (search terms)?
--
Jack D. McKinney
Walnut Glenn Systems
5001 Jennie Kate Lane
Lexington, KY 40510
Phone: 859.233.4299
Cell: 859.433.4299
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
30 Jun
30 Jun
06:38
New subject: [opensuse] Re: Initial Boot Failure
On Wed, 29 Jun 2011 23:48:29 -0400, Jack McKinney wrote:
I installed on my old Gateway with P-486 running 3
GHz
with 2 gig of memory.
Are you saying that this CPU is an 80486? If you are, you should be
aware that most of the openSUSE packages (if not all) require at least a
Pentium processor.
Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
07:48
New subject: [opensuse] Re: Initial Boot Failure
On 30/06/11 05:38, Jim Henderson wrote:
On Wed, 29 Jun 2011 23:48:29 -0400, Jack McKinney
wrote:
I would be very impressed with an 80486 clocked at 3GHz :D
Tejas
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I installed on my old Gateway with P-486
running 3 GHz
with 2 gig of memory.
Are you saying that this CPU is an 80486? If you are, you
should be
aware that most of the openSUSE packages (if not all) require at least a
Pentium processor.
Jim
08:29
New subject: [opensuse] Re: Initial Boot Failure
Tejas Guruswamy wrote:
On 30/06/11 05:38, Jim Henderson wrote:
Yup. Add 2Gb of memory to that, what a beast.
--
Per Jessen, Zürich (15.6°C)
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
On Wed, 29 Jun 2011 23:48:29 -0400, Jack McKinney
wrote:
I would be very impressed with an 80486 clocked at 3GHz :D
I installed on my old Gateway with P-486
running 3 GHz
with 2 gig of memory.
Are you saying that this CPU is an 80486? If you are, you
should be
aware that most of the openSUSE packages (if not all) require at
least a Pentium processor.
Jim
16:16
New subject: [opensuse] Re: Initial Boot Failure
On Thu, 30 Jun 2011 06:48:11 +0100, Tejas Guruswamy wrote:
On 30/06/11 05:38, Jim Henderson wrote:
As would I, but given he wrote P-486, clarification is clearly needed. :)
Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
On Wed, 29 Jun 2011 23:48:29 -0400, Jack McKinney
wrote:
I would be very impressed with an 80486 clocked at 3GHz :D I installed on my old Gateway with P-486
running 3 GHz
with 2 gig of memory.
Are you saying that this CPU is an 80486? If you are, you
should be
aware that most of the openSUSE packages (if not all) require at least
a Pentium processor.
Jim
13:18
New subject: [opensuse] Re: Initial Boot Failure
Jim Henderson wrote:
On Wed, 29 Jun 2011 23:48:29 -0400, Jack McKinney
wrote:
I don't think there are many 486 CPUs running at 3 GHz.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I installed on my old Gateway with P-486
running 3 GHz
with 2 gig of memory.
Are you saying that this CPU is an 80486? If you are, you should be
aware that most of the openSUSE packages (if not all) require at least a
Pentium processor.
06:43
On Wed, 29 Jun 2011 23:48:29 -0400
Jack McKinney <jackdmckinney(a)insightbb.com> wrote:
I am not experienced with Linux and this is my first
attempt to load
SUSE.
Hi Jack,
You've selected a great distribution for a first install. Sorry you're
having a bad experience, but these things happen and it shouldn't be too
difficult to troubleshoot what's going on.
Helping you would be a lot easier if you posted more detailed
information about the target hardware; make, model, mainboard #, cpu #,
dvd drive #, graphics card/chipset, hard drive(s) & interfaces, NIC
chipset, etc.
regards,
Carl
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
07:56
On 30/06/11 04:48, Jack McKinney wrote:
I am not experienced with Linux and this is my first
attempt to load
SUSE.
I downloaded the 32 bit version of the full DVD using bit torrent and
burned a DVD. I installed on my old Gateway with P-486 running 3 GHz
with 2 gig of memory. The install used the recommended partitioning
and appeared to run normally except that the re-boot to the hard drive
failed. (Note: The onscreen text did not say to remove the DVD as
stated in step 6 of the installation guide.) It displayed the green
screen with the logo in the center. The system did not respond to any
input. I did not record the time but the green screen was up for more
than 5 minutes before I forced a shutdown. The system was not
connected to my network and the only failures I noted on the BW list
was network connection were not established.
I restarted from the DVD and ran disk validation (100%), then reran
the installation with the same results described above. This time I
left the green screen up for at least 30 minutes to be sure some long
running process could complete. I removed the DVD, forced the
shutdown and re-stared the system. This time YaST2 automatic
configuration started but did not run to completion, ending with the
system stalled and not responding to any input.
So far, I have found no hints in the online information other than to
re-burn the DVD at a slower speed.
I did a re-download of openSUSE-11.4-DVD-i586.iso using FinalTorrent,
validated the both MD5 and sha1 checksum , burned a DVD but could
not control the speed, validated the burn, verified the media before
running a complete install. YaST2 stopped once during package install
but loaded the file after the retry. The system was connected to the
network for this installation. System restart appeared to run
normally up to about 3/4 of the progress bar. I forced the system to
power down after about an hour at this point. I have photos of most
of the screens presented in the installation.
Any additional suggestions or recommendations? Any suggestions on how
to research this issue (search terms)?
On the boot screen (the green screen with the progress bar), before the
system stops responding, press 'Esc' on your keyboard. That should
display some text on the screen describing what's going on in the boot
process.
If the system stops while there is still text on the screen, it means
the boot process stopped, describe the last few lines of output to us
and we should be able to identify the problem.
Otherwise, if you have autologin enabled (you probably do if you
installed with default settings), you might get another green loading
screen, very similar looking but this time with a small white 'K' in the
top right corner. If it reaches this stage, it means loading the desktop
environment is crashing, and we can debug that too.
Regards,
Tejas
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
15:11
Thank you to everyone for the quick support.
I did an escape at boot, selected Failsafe, and now have a running SUSE
system! (This was the second boot.) Everything seems to be working. I
opened a new text document in office. Now running updates.
And it is a P-4. Specs from Gateway site for model 505GR:
Processor Brand Intel®
Processor Class Pentium® 4 Processor with Hyper-Threading Technology 530
Processor Speed 3.0 GHz
Bus Speed 800 MHz
Cache Size 1 MB
System Chipset Intel 915G Express Chipset
Memory 2 gig (I added 1 Gig)
Jack D. McKinney
Walnut Glenn Systems
5001 Jennie Kate Lane
Lexington, KY 40510
Phone: 859.233.4299
Cell: 859.433.4299
On 6/30/2011 1:56 AM, Tejas Guruswamy wrote:
On 30/06/11 04:48, Jack McKinney wrote:
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I am not experienced with Linux and this is my
first attempt to load
SUSE.
I downloaded the 32 bit version of the full DVD using bit torrent and
burned a DVD. I installed on my old Gateway with P-486 running 3
GHz with 2 gig of memory. The install used the recommended
partitioning and appeared to run normally except that the re-boot to
the hard drive failed. (Note: The onscreen text did not say to
remove the DVD as stated in step 6 of the installation guide.) It
displayed the green screen with the logo in the center. The system
did not respond to any input. I did not record the time but the
green screen was up for more than 5 minutes before I forced a
shutdown. The system was not connected to my network and the only
failures I noted on the BW list was network connection were not
established.
I restarted from the DVD and ran disk validation (100%), then reran
the installation with the same results described above. This time I
left the green screen up for at least 30 minutes to be sure some long
running process could complete. I removed the DVD, forced the
shutdown and re-stared the system. This time YaST2 automatic
configuration started but did not run to completion, ending with the
system stalled and not responding to any input.
So far, I have found no hints in the online information other than to
re-burn the DVD at a slower speed.
I did a re-download of openSUSE-11.4-DVD-i586.iso using FinalTorrent,
validated the both MD5 and sha1 checksum , burned a DVD but could
not control the speed, validated the burn, verified the media before
running a complete install. YaST2 stopped once during package
install but loaded the file after the retry. The system was
connected to the network for this installation. System restart
appeared to run normally up to about 3/4 of the progress bar. I
forced the system to power down after about an hour at this point. I
have photos of most of the screens presented in the installation.
Any additional suggestions or recommendations? Any suggestions on
how to research this issue (search terms)?
On the boot screen (the green screen with the progress bar), before
the system stops responding, press 'Esc' on your keyboard. That should
display some text on the screen describing what's going on in the boot
process.
If the system stops while there is still text on the screen, it means
the boot process stopped, describe the last few lines of output to us
and we should be able to identify the problem.
Otherwise, if you have autologin enabled (you probably do if you
installed with default settings), you might get another green loading
screen, very similar looking but this time with a small white 'K' in
the top right corner. If it reaches this stage, it means loading the
desktop environment is crashing, and we can debug that too.
Regards,
Tejas 
16:11
On 2011/06/30 09:11 (GMT-0400) Jack McKinney composed:
I did an escape at boot, selected Failsafe, and now
have a running SUSE
system! (This was the second boot.) Everything seems to be working. I
opened a new text document in office. Now running updates.
And it is a P-4. Specs from Gateway site for model
505GR:
Processor Brand Intel®
Processor Class Pentium® 4 Processor with Hyper-Threading Technology 530
Processor Speed 3.0 GHz
Bus Speed 800 MHz
Cache Size 1 MB
System Chipset Intel 915G Express Chipset
Memory 2 gig (I added 1 Gig)
Is Windows still on it too? And/or some other Linux suspending to swap?
I installed 11.4 multiboot on a pair of 2.8GHz P4HT i915G Dell GX280 systems
with 2G RAM a month ago, and have no recollection of video trouble. Maybe
Jack's CPU is too fast? ;-)
I wonder of bootsplash or splashy could have something to do with his
problem. I always taboo both of them during installation. Another difference
is my cmdlines include noresume & video=1152x864.
If Jack's still running with nomodeset after doing his updates, he'll need to
tweak until that's not necessary for best X performance, especially if he's
not using a 4:3 or 5:4 display device.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
17:25
On 6/30/2011 10:11 AM, Felix Miata wrote:
On 2011/06/30 09:11 (GMT-0400) Jack McKinney
composed:
Still not running.
I ran updates then shutdown. Boot to SUSE after normal shutdown hangs
with a blank screen. Forced power reset and boot with Failsafe also
hangs with the following:
System boot Control: the system has been setup
Skipped Features: boot.cycle
System Boot control: Running /etc/iniy.d/boot.local done
INIT: Entering run level 5
Root logging started on /dev/tty1(dev/console) at Thu Jun 30
11:06:07 2011
Master Resource Control: previous runlevel N, switching to
runlevel: 5
Master Resource Control: Running /etc/init.d/before.local done
blogd: Can not read from fd 0: Input/output error
Starting D-Bus daemon done
Loading basic firewall rules done
I have Windows XP on a drive that is not powered since it is failing. I
had Fedora on the drive where I installed SUSE but I think the
partitioning has wiped that out. I did not install multiboot.
Display is E-Machines E211H 1920x1080.
As a nube, I have to ask how to make the recommended changes?
Jack D. McKinney
Walnut Glenn Systems
5001 Jennie Kate Lane
Lexington, KY 40510
Phone: 859.233.4299
Cell: 859.433.4299
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I did an escape at boot, selected Failsafe, and
now have a running SUSE
system! (This was the second boot.) Everything seems to be working. I
opened a new text document in office. Now running updates.
And it is a P-4. Specs from Gateway site for
model 505GR:
Processor Brand Intel®
Processor Class Pentium® 4 Processor with Hyper-Threading
Technology 530
Processor Speed 3.0 GHz
Bus Speed 800 MHz
Cache Size 1 MB
System Chipset Intel 915G Express Chipset
Memory 2 gig (I added 1 Gig)
Is Windows still on it too? And/or some other Linux suspending to swap?
I installed 11.4 multiboot on a pair of 2.8GHz P4HT i915G Dell GX280
systems with 2G RAM a month ago, and have no recollection of video
trouble. Maybe Jack's CPU is too fast? ;-)
I wonder of bootsplash or splashy could have something to do with his
problem. I always taboo both of them during installation. Another
difference is my cmdlines include noresume & video=1152x864.
If Jack's still running with nomodeset after doing his updates, he'll
need to tweak until that's not necessary for best X performance,
especially if he's not using a 4:3 or 5:4 display device.
18:23
Jack McKinney wrote:
Still not running.
I ran updates then shutdown. Boot to SUSE after normal shutdown hangs
with a blank screen.
As Felix suggested, try booting with "nomodeset" (assuming you haven't
already).
--
Per Jessen, Zürich (21.7°C)
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
18:36
On 2011/06/30 11:25 (GMT-0400) Jack McKinney composed:
Still not running.
I ran updates then shutdown. Boot to SUSE after normal shutdown hangs
with a blank screen. Forced power reset and boot with Failsafe also
hangs with the following:
...
I have Windows XP on a drive that is not powered since
it is failing. I
had Fedora on the drive where I installed SUSE but I think the
partitioning has wiped that out. I did not install multiboot.
Display is E-Machines E211H 1920x1080.
As a nube, I have to ask how to make the recommended
changes?
With the additional info, I recommend starting all over. First decide if WXP
is going to go back onto the system on either the Linux HD, or a separate HD,
old or new. If it's going back, decide where. If you want it on the same HD
as Linux, how to best go about it depends on your available WXP installation
media. Those available in recent years are usually quite belligerent,
restoring the whole HD to OEM status without regard to anything that may be
installed there and working. If that's your only option, then you should do
that first, then back it up, then begin the Linux installation process.
If WXP is going to go back on a separate HD, you need to install Linux while
both HDs are connected in their usual physical configuration. Otherwise
you'll most likely break bootability of one or the other or both.
Whether WXP is going back or not, it's wise to configure the HD Linux goes on
so that at least two Linux versions can be available for boot. Once the first
is installed and operational, the second will eventually be there for testing
the waters prior to choosing that upgrade or switch path, leaving the
original as fallback to at least facilitate repair if and when anything goes
haywire on the second or later.
The openSUSE installer is capable of repartitioning after you've restored or
installed WXP, so I recommend taking advantage of that capability, and set
aside space for at least two Linux distros, plus a separate partition or
logical volume for Linux's /home (user data). Another option available if
you're not stuck with bad WXP restore media is to (wipe and) fully partition
the HD prior to installing _anything_. This is the approach I always use,
always partitioning (with a cross-platform partitioning tool to maximize
compatibility) fully before installing anything whatsoever. I have over 25
multiboot systems (most with at least 4 installed operating systems, many
with more than 10) on the premises here.
Take a look at http://fm.no-ip.com/PC/install-doz-after.html before
proceeding to actually do or decide anything further.
In any event, changing disk count, and particularly changing disk order, can
be, and usually is, a very troubling experience best avoided. So, decide what
you ultimately want before moving forward if you want to minimize future hassles.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
08:36
Jack McKinney wrote:
The install used the recommended partitioning
and appeared to run normally except that the re-boot to the hard drive
failed. (Note: The onscreen text did not say to remove the DVD as
stated in step 6 of the installation guide.)
If the installation DVD is not removed, it will be booted, but then
default to booting from harddisk.
It displayed the green screen with the logo in the
center. The system
did not respond to any input. I did not record the time but the green
screen was up for more than 5 minutes before I forced a shutdown. The
system was not connected to my network and the only failures I noted
on the BW list was network connection were not established.
Wild guess - video problem. Did you try hitting escape by any chance?
It might be worth trying a new boot with "vga=normal" at the grub
command line.
--
Per Jessen, Zürich (15.7°C)
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
12:37
On 2011/06/30 08:36 (GMT+0200) Per Jessen composed:
It might be worth trying a new boot with
"vga=normal" at the grub
command line.
Possibly, but if his gfxchip is supported by KMS and his display's EDID is
valid, the effect would only be temporary. Absent video=preferredmode on
cmdline, KMS chooses mode based upon EDID, not whatever vga= may be found on
cmdline.
More likely he needs to try the failsafe Grub menu option, or try adding
nomodeset to the default Grub kernel line.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
13:06
Felix Miata wrote:
On 2011/06/30 08:36 (GMT+0200) Per Jessen composed:
You're right, I forgot about nomodeset.
--
Per Jessen, Zürich (17.0°C)
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
It might be worth trying a new boot with
"vga=normal" at the grub
command line.
Possibly, but if his gfxchip is supported by KMS and his display's
EDID is valid, the effect would only be temporary. Absent
video=preferredmode on cmdline, KMS chooses mode based upon EDID, not
whatever vga= may be found on cmdline.
More likely he needs to try the failsafe Grub menu option, or try
adding nomodeset to the default Grub kernel line.
3578
days inactive
3578
days old
15 comments
7 participants
participants (7)
-
Carl Hartung -
Felix Miata -
Jack McKinney -
James Knott -
Jim Henderson -
Per Jessen -
Tejas Guruswamy