11.3 x64 DVD Install vs. liveCD

English Install/Boot/Login
#1

A new problem needs a new thread.

Following the latest installation ( see this Partitioning of a (new) Windows 7 HD), a new problem arose after the install completed.

Environment: Gateway NV, i5-430, 4GB, 500GB HD (partitioned), Intel GMA

sda1,2,3 : the normal Windows 7 stuff
sda4: extended, containing openSUSE (sda5 (swap), sda6( / ) and sda7 (/home)

followed by about 115 GB empty.

11.3 x64 fails to boot in normal mode, yielding a black screen. Addition of acpi=off will allow boot to complete successfully ~10% of the time. However, the Intel GMA is not recognized. Research found this Graphics Card Driver for GMA HD Please, but, frankly, this is beyond me.

Failsafe boot completes successfully. However, in every case, the repos are “locked” by /usr/sbin/packagekitd, and never release. (By never, I waited up to 30 minutes).

Needless to say, this is a bit of a problem. However, there is a bright side: the liveCD (Gnome) boots, recognizes the Intel GMA, and works wonderfully. This begs the question: might the DVD install, which experienced some wrinkles during its two (2) attempts, have a problem that the liveCD does not have ?

In absence of any alternatives, I plan to restore the HD to original condition (as shipped), re-partition from the liveCD, and re-install. Any comments on any and all of the above remarks are appreciated.

BTW: I am writing this from the liveCD with Firefox. The sound card and wireless are recognized, but not configured in the liveCD environment.

Sean

PS: I have not had this much fun (seriously) in a few months! rotfl!

#2

Why re-partition

Just re-install over the top if that’s what you want to do

In the live cd, open a terminal, type: su
once root, type: lspci -v

Around the top of the output it should tell you what driver is loaded for the graphics
Don’t post everything here
or paste it all here: SUSE Paste
and link us

#3

(from the liveCD)

00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller])
	Subsystem: Acer Incorporated [ALI] Device 031c
	Flags: bus master, fast devsel, latency 0, IRQ 28
	Memory at d0000000 (64-bit, non-prefetchable) [size=4]
	Memory at c0000000 (64-bit, prefetchable) [size=256]
	I/O ports at 3050 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915

The live CD seems to exercise the above quite well. The desktop effects (OK, I know, it’s only Gnome) are great. Other than the hesitation accessing the DVD-drive periodically, this is not that bad! I am burning a KDE liveCD (I would be doing this anyway, for a complete set).[/size][/size][/size]

#4

Was your install done as KDE or Gnome?
KDE and intel seem to have some issues around the forum. I would plan for Gnome. Why not just try installing Gnome from the Live CD

#5

The install was for a Gnome desktop from the (full) DVD install. I usually install Gnome (I like it), then add KDE when the Gnome environment is stable.

I will re-install, and post back later.

Thanks for the assist.

Sean

#6

Attempting install of liveCD over previous installation hiccup’ed with a “-0007” error. Attempts to boot Windows met with errors, necessitating a Windows recovery. This is not a problem, for the 5 or 6 files were backed up.:slight_smile:

At this point, I restored the partition layout to factory re-partitioned with Windows, and ran the install of the live CD. All went well, until the required boot. After the green logo (large, 1024 x 768, vga-0317), followed by the green logo (small, 1600 x 900), the black screen popped up. The PC was not dead, just blind, as a great deal of HD activity went on.

“Failsafe” boot-mode works correctly. After several test boots of the “normal” config, the resolution comes from either “nomodeset” or “acpi=off”, which allows boot and operation with restricted graphics (1024 x 768).

“Desktop effects” is off. All updates were applied, including the kernel, updated to 2.6.34.7-0.3. The net effect is that the DVD install and liveCD install result in the same environment, although the liveCD was a faster install.

I have found several forums entries re: the Intel GMA, although it seems that I am not the only person experiencing these problems.

As for my earlier post, regarding ~10% successful boot on the previous installation, the liveCD install has yielded exactly ZERO success without “nomodeset”, “acpi=off” or selection of Failsafe mode.

I will be starting the second phase (wireless, USB and external HD testing, and install of KDE 4.5.1) in the next few hours. The net result will be a 64-bit mirror (except for userdata files) of my 32-bit 11.3/KDE 4.5.1 laptops and box.

#7

Check this
openSUSE Graphic Card Practical Theory Guide for Users

#8

I have read that item. Either my eyes or fingers (or brain?) are burned out, but when I do


Run Level 3. Now typically, when reconfiguring a graphic card, it is best to do this NOT in X window, but rather in the full screen terminal run level 3. One boots to run level 3 by pressing "3" (no quotes) when the initial grub boot menu first appears. By pressing "3" one will see the "3" appear in the options line. Then boot normally. That brings one to a full screen text login. Login as a regular user.

I do not get Runlevel 3, just a black screen. Nothing like the scrolling lines I get in Failsafe mode.

As soon as the GRUB menu appears, I press 3, which goes to the “Boot Options” line, I boot and nothing different occurs.

My thoughts keep returning to the question "Why does it work OK with the liveCD (1600 x 900, all graphics features, etc), and fail on the system installed by that same liveCD ? Two differences immediately come to mind: the liveCD uses a different driver or the problem lies in GRUB or the bootloader.

During the install, a message was displayed that


the bootloader is not completely below 128 GB ....
and the ... may not boot properly

Is that problem still valid ? The entries boot Windows, and SUSE with “nomodeset” or “acpi=off”.

#9

the bootloader is not completely below 128 GB … and the … may not boot properly
Don’t worry abut that.

I do not get Runlevel 3, just a black screen. Nothing like the scrolling lines I get in Failsafe mode.

As soon as the GRUB menu appears, I press 3, which goes to the “Boot Options” line, I boot and nothing different occurs.

This is troubling…You should be able to boot to level 3

In the default boot my vga is (vga=0x314)
What is yours

#10

vga=0x317. I will try changing that to 0x314 and see what shakes out.

Just to re-cap: my options line should read

3 vga=0x314

?

#11

Try changing the vga but leave out the 3

If you want to get to level 3 - remove all existing text so it looks like this:
http://dl.dropbox.com/u/10573557/YaST%20level3/2%20Edit%20the%20Boot%20line.png

#12

With only “3” (sans quotes), I see

doing a fast boot
creating device nodes with udev

followed by the black screen. HD indicators show activity for a time.

If I enter “3 nomodeset” (sans quotes), I do get runlevel 3. After login, then “su” and supervisory password, “Xorg -configure” results in


Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault).  Server aborting

followed by “Aborted”

#13

Looks like you have your work cut out
Check this: SDB:Configuring graphics cards - openSUSE

#14

Update to the 11.3 x64 installation problem

Original installation was from the installation DVD. The first and most of the subsequent boots produced a “black screen”. I noted that activity (the HD light) continued, as the “black screen” came staightaway. I noted earlier that ~10% of these boots did, in fact correctly use the display (1600 x 900, full graphics, etc).

All boots in “Failsafe” worked correctly, albeit in degraded (1024 x 768) mode. Testing of “normal” boot, using “nomodeset” and/or “acpi=off” allowed the boot to complete, with the same degraded display.

I burned and ran a Gnome liveCD, which functioned absolutely flawlessly (albeit slowly) with the display, including desktop effects and touchpad-related effects, such as “pinch-zoom”. (When I say “slowly”, I refer to the delays accessing the liveCD). Installation from the liveCD resulted in the same conditions as the DVD install, with the exception that NO boot of the liveCD-install used the display, always resulting in the “black screen”.

Today, I downloaded, burned and ran a “Network” install. Other than taking longer that the DVD install (and, by count, installing more packages), the results were the same as the DVD and liveCD. “Normal” boots fail with “black screen”, and “Failsafe” or “nomodeset” boots run, with the degraded display configuration.

I had downloaded Ubuntu 10.04 LTS. I burned it and installed to the reserved space on the hard drive. The results were a correct display (1600 x 900) and all features tested (as many as Gnome and the Ubuntu distro provide) seem to function correctly.

Currently, I am downloading and burning Fedora 13, which I will install today. I will update this thread forthwith.

In summary, the Intel GMA HD functions correctky under Windows 7 (which is to be expected, as it would never sell without same :wink: ), and Ubuntu 10.04. All three install modes (DVD, Gnome liveCD and network) for openSUSE 11.3 x64 result in the same “black screen” problem. I must re-state that the Gnome liveCD, running in “live” mode, worked correctly.

openSUSE is my preferred distro and environment. I will probably have some Windows flavor around for a while (a few apps), and one or two other distros for my own edification. I reiterate: I want openSUSE to work on the new laptop (as it does so well on my 32-bit laptops and box), but I do not have the Linux expertise to debug this or to perform driver work. I do, however, have a laptop (i5-430, 4GB, 500GB HD and Intel GMA HD available for testing.

One last question: would there be any value in the installation of the 32-bit 11.3 that I have installed on my laptops ?

#15

32/64 with regard to your graphics issue. It’s not likely going to make any difference.

#16

Fedora 13 liveCD fails straightaway. The “Autostart in <n> seconds>” countdown completes, followed by the same “black screen”.

A re-boot of SUSE, first as a normal boot, then “failsafe” shows


Sep 24 21:39:06 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1731" x-info="http://www.rsyslog.com"] exiting on signal 15.
Sep 27 10:40:45 Twilight kernel: imklog 5.4.0, log source = /proc/kmsg started.
Sep 27 10:40:45 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1535" x-info="http://www.rsyslog.com"] start
Sep 27 10:40:45 Twilight kernel:    17.662276] type=1505 audit(1285598441.396:2): operation="profile_load" pid=1425 name=/bin/ping
Sep 27 10:40:45 Twilight kernel:    17.698905] type=1505 audit(1285598441.433:3): operation="profile_load" pid=1426 name=/sbin/klogd
Sep 27 10:40:45 Twilight kernel:    17.770728] type=1505 audit(1285598441.505:4): operation="profile_load" pid=1427 name=/sbin/syslog-ng
Sep 27 10:40:45 Twilight kernel:    17.841098] type=1505 audit(1285598441.575:5): operation="profile_load" pid=1428 name=/sbin/syslogd
Sep 27 10:40:45 Twilight kernel:    17.918648] type=1505 audit(1285598441.653:6): operation="profile_load" pid=1429 name=/usr/sbin/avahi-daemon
Sep 27 10:40:45 Twilight kernel:    17.982339] type=1505 audit(1285598441.717:7): operation="profile_load" pid=1430 name=/usr/sbin/identd
Sep 27 10:40:45 Twilight kernel:    18.051719] type=1505 audit(1285598441.786:8): operation="profile_load" pid=1431 name=/usr/sbin/mdnsd
Sep 27 10:40:45 Twilight kernel:    18.174421] type=1505 audit(1285598441.909:9): operation="profile_load" pid=1432 name=/usr/sbin/nscd
Sep 27 10:40:45 Twilight kernel:    18.327198] type=1505 audit(1285598442.062:10): operation="profile_load" pid=1433 name=/usr/sbin/ntpd
Sep 27 10:40:45 Twilight kernel:    18.434764] type=1505 audit(1285598442.170:11): operation="profile_load" pid=1434 name=/usr/sbin/traceroute
Sep 27 10:40:45 Twilight kernel:    21.684349] ip6_tables: (C) 2000-2006 Netfilter Core Team
Sep 27 10:40:46 Twilight kernel:    22.350027] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 27 10:40:46 Twilight kernel:    22.365894] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 27 10:40:46 Twilight SuSEfirewall2: batch committing...
Sep 27 10:40:48 Twilight SuSEfirewall2: Firewall rules set to CLOSE.
Sep 27 10:40:50 Twilight kernel: Kernel logging (proc) stopped.
Sep 27 10:40:50 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1535" x-info="http://www.rsyslog.com"] exiting on signal 15.
Sep 27 10:40:51 Twilight kernel: imklog 5.4.0, log source = /proc/kmsg started.
Sep 27 10:40:51 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1717" x-info="http://www.rsyslog.com"] start
Sep 27 10:40:52 Twilight auditd[1762]: Started dispatcher: /sbin/audispd pid: 1764
Sep 27 10:40:52 Twilight audispd: priority_boost_parser called with: 4
Sep 27 10:40:52 Twilight audispd: max_restarts_parser called with: 10
Sep 27 10:40:52 Twilight audispd: No plugins found, exiting
Sep 27 10:40:52 Twilight auditd[1762]: Init complete, auditd 2.0.4 listening for events (startup state disable)
Sep 27 10:40:53 Twilight acpid: 1 client rule loaded
Sep 27 10:40:54 Twilight acpid: 1 client rule loaded
Sep 27 10:40:56 Twilight kernel:    32.423005] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 27 10:40:56 Twilight kernel:    32.423007] EDD information not available.
Sep 27 10:40:56 Twilight avahi-daemon[2030]: Found user 'avahi' (UID 102) and group 'avahi' (GID 105).
Sep 27 10:40:56 Twilight avahi-daemon[2030]: Successfully dropped root privileges.
**Sep 27 10:40:56 Twilight avahi-daeSep 27 10:41:54 Twilight kernel: imklog 5.4.0, log source = /proc/kmsg started**.
Sep 27 10:41:54 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1584" x-info="http://www.rsyslog.com"] start
Sep 27 10:41:54 Twilight kernel:    20.989877] type=1505 audit(1285598512.090:2): operation="profile_load" pid=1454 name=/bin/ping
Sep 27 10:41:54 Twilight kernel:    21.044784] type=1505 audit(1285598512.145:3): operation="profile_load" pid=1455 name=/sbin/klogd
Sep 27 10:41:54 Twilight kernel:    21.135112] type=1505 audit(1285598512.236:4): operation="profile_load" pid=1456 name=/sbin/syslog-ng
Sep 27 10:41:54 Twilight kernel:    21.225343] type=1505 audit(1285598512.326:5): operation="profile_load" pid=1457 name=/sbin/syslogd
Sep 27 10:41:54 Twilight kernel:    21.320590] type=1505 audit(1285598512.422:6): operation="profile_load" pid=1458 name=/usr/sbin/avahi-daemon
Sep 27 10:41:54 Twilight kernel:    21.401672] type=1505 audit(1285598512.503:7): operation="profile_load" pid=1459 name=/usr/sbin/identd
Sep 27 10:41:54 Twilight kernel:    21.488418] type=1505 audit(1285598512.590:8): operation="profile_load" pid=1460 name=/usr/sbin/mdnsd
Sep 27 10:41:54 Twilight kernel:    21.586635] type=1505 audit(1285598512.688:9): operation="profile_load" pid=1461 name=/usr/sbin/nscd
Sep 27 10:41:54 Twilight kernel:    21.719416] type=1505 audit(1285598512.821:10): operation="profile_load" pid=1462 name=/usr/sbin/ntpd
Sep 27 10:41:54 Twilight kernel:    21.800551] type=1505 audit(1285598512.903:11): operation="profile_load" pid=1463 name=/usr/sbin/traceroute
Sep 27 10:41:54 Twilight kernel:    23.416085] ip6_tables: (C) 2000-2006 Netfilter Core Team
Sep 27 10:41:54 Twilight kernel:    23.648021] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 27 10:41:54 Twilight kernel:    23.696694] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 27 10:41:54 Twilight SuSEfirewall2: batch committing...
Sep 27 10:41:56 Twilight SuSEfirewall2: Firewall rules set to CLOSE.
Sep 27 10:41:58 Twilight kernel: Kernel logging (proc) stopped.
Sep 27 10:41:58 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1584" x-info="http://www.rsyslog.com"] exiting on signal 15.
Sep 27 10:41:58 Twilight kernel: imklog 5.4.0, log source = /proc/kmsg started.
Sep 27 10:41:58 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1815" x-info="http://www.rsyslog.com"] start
Sep 27 10:41:58 Twilight auditd[1838]: Started dispatcher: /sbin/audispd pid: 1840
Sep 27 10:41:58 Twilight audispd: priority_boost_parser called with: 4
Sep 27 10:41:58 Twilight audispd: max_restarts_parser called with: 10
Sep 27 10:41:58 Twilight audispd: No plugins found, exiting
Sep 27 10:41:58 Twilight auditd[1838]: Init complete, auditd 2.0.4 listening for events (startup state disable)
Sep 27 10:41:59 Twilight acpid: 1 client rule loaded
Sep 27 10:41:59 Twilight acpid: 1 client rule loaded
Sep 27 10:41:59 Twilight kernel:    28.510880] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 27 10:41:59 Twilight kernel:    28.510883] EDD information not available.
**Sep 27 10:42:00 Twilight mcelog: Unsupported new Family 6 Model 25 CPU: only decoding architectural errors
Sep 27 10:42:00 Twilight mcelog: failed to prefill DIMM database from DMI data**
Sep 27 10:42:00 Twilight avahi-daemon[2083]: Found user 'avahi' (UID 102) and group 'avahi' (GID 105).

I have highlighted two areas: the first highlight shows the log output stopped in mid-message (the “dae” of one message truncated by the re-boot). This may or may not be significant.

The second highlight (the same point during boot in failsafe mode), shows the somewhat ominous “mcelog” message(s).

Concerning the first highlight, the booting appeared to continue to run (activity on the HD indicator), though nothing was apparently logged.

So far, everything else (sound, wireless, partition access to non-SUSE partitions, KDE install and operation, etc) seems to be correct, almost flawless. The only apparent component not functioning to par is the display/Intel GMA HD. Of course, this usage occurs either in “failsafe” mode, or the somewhat less-limited “nomodeset” boot.

Re-capping the Intel GMA usage, the display/adaptor functions correctly in the openSUSE 11.3 liveCD (running live), Ubuntu 10.04 and Windows 7. All installed versions of SUSE (installed from DVD, liveCD and network) exhibit exactly the same problem (“black screen”). Fedora 13 liveCD gets the splash screen, countdown and then “black screen”.

I have a “shared data” partition. I will attempt to boot the SUSE liveCD and capture the log info noted above. This should be interesting as that boot works!

(This reminds me of that old sarcasm “other than that, Mrs. Lincoln, how did you like the play?”. :wink: )

#17

The kernel installed from the DVD and network install was “desktop”. I installed and booted kernel “default”. The log shows

Sep 27 11:36:45 Twilight kernel:    18.340045] type=1505 audit(Sep 27 11:42:12 Twilight kernel: imklog 5.4.0, log source = /proc/kmsg started.
Sep 27 11:42:12 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1611" x-info="http://www.rsyslog.com"] start
Sep 27 11:42:12 Twilight kernel:    18.889237] type=1505 audit(1285602127.469:2): operation="profile_load" pid=1507 name=/bin/ping
Sep 27 11:42:12 Twilight kernel:    18.953736] type=1505 audit(1285602127.537:3): operation="profile_load" pid=1508 name=/sbin/klogd
Sep 27 11:42:12 Twilight kernel:    19.024112] type=1505 audit(1285602127.605:4): operation="profile_load" pid=1509 name=/sbin/syslog-ng
Sep 27 11:42:12 Twilight kernel:    19.110047] type=1505 audit(1285602127.693:5): operation="profile_load" pid=1510 name=/sbin/syslogd
Sep 27 11:42:12 Twilight kernel:    19.186289] type=1505 audit(1285602127.769:6): operation="profile_load" pid=1511 name=/usr/sbin/avahi-daemon
Sep 27 11:42:12 Twilight kernel:    19.278485] type=1505 audit(1285602127.861:7): operation="profile_load" pid=1512 name=/usr/sbin/identd
Sep 27 11:42:12 Twilight kernel:    19.347262] type=1505 audit(1285602127.929:8): operation="profile_load" pid=1513 name=/usr/sbin/mdnsd
Sep 27 11:42:12 Twilight kernel:    19.462647] type=1505 audit(1285602128.045:9): operation="profile_load" pid=1514 name=/usr/sbin/nscd
Sep 27 11:42:12 Twilight kernel:    19.576265] type=1505 audit(1285602128.157:10): operation="profile_load" pid=1515 name=/usr/sbin/ntpd
Sep 27 11:42:12 Twilight kernel:    19.693216] type=1505 audit(1285602128.273:11): operation="profile_load" pid=1516 name=/usr/sbin/traceroute
Sep 27 11:42:13 Twilight kernel:    24.560296] ip6_tables: (C) 2000-2006 Netfilter Core Team
Sep 27 11:42:15 Twilight kernel:    26.734778] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 27 11:42:15 Twilight kernel:    26.790947] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 27 11:42:15 Twilight SuSEfirewall2: batch committing...
Sep 27 11:42:15 Twilight SuSEfirewall2: Firewall rules set to CLOSE.
Sep 27 11:42:16 Twilight kernel: Kernel logging (proc) stopped.
Sep 27 11:42:16 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1611" x-info="http://www.rsyslog.com"] exiting on signal 15.
Sep 27 11:42:18 Twilight kernel: imklog 5.4.0, log source = /proc/kmsg started.
Sep 27 11:42:18 Twilight rsyslogd: [origin software="rsyslogd" swVersion="5.4.0" x-pid="1708" x-info="http://www.rsyslog.com"] start
Sep 27 11:42:19 Twilight auditd[1766]: Started dispatcher: /sbin/audispd pid: 1768
Sep 27 11:42:19 Twilight audispd: priority_boost_parser called with: 4
Sep 27 11:42:19 Twilight audispd: max_restarts_parser called with: 10
Sep 27 11:42:19 Twilight audispd: No plugins found, exiting
Sep 27 11:42:19 Twilight auditd[1766]: Init complete, auditd 2.0.4 listening for events (startup state disable)
Sep 27 11:42:21 Twilight acpid: 1 client rule loaded
Sep 27 11:42:22 Twilight acpid: 1 client rule loaded
Sep 27 11:42:22 Twilight kernel:    33.931917] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 27 11:42:22 Twilight kernel:    33.931920] EDD information not available.
Sep 27 11:42:22 Twilight mcelog: Unsupported new Family 6 Model 25 CPU: only decoding architectural errors
Sep 27 11:42:22 Twilight mcelog: failed to prefill DIMM database from DMI data
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Found user 'avahi' (UID 102) and group 'avahi' (GID 105).
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Successfully dropped root privileges.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: avahi-daemon 0.6.25 starting up.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Loading service file /etc/avahi/services/sftp-ssh.service.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Loading service file /etc/avahi/services/ssh.service.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Loading service file /etc/avahi/services/udisks.service.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Network interface enumeration completed.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Registering HINFO record with values 'X86_64'/'LINUX'.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Server startup complete. Host name is Twilight.local. Local service cookie is 3945836593.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Service "Twilight" (/etc/avahi/services/udisks.service) successfully established.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Service "Twilight" (/etc/avahi/services/ssh.service) successfully established.
Sep 27 11:42:22 Twilight avahi-daemon[2089]: Service "SFTP File Transfer on Twilight" (/etc/avahi/services/sftp-ssh.service) successfully established.
Sep 27 11:42:22 Twilight network: Starting the NetworkManager
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Longcheer
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin MotoC
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Huawei
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Option High-Speed
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Ericsson MBM
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin ZTE
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin AnyData
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Nokia
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Option
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Sierra
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Gobi
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Novatel
Sep 27 11:42:22 Twilight modem-manager: Loaded plugin Generic
Sep 27 11:42:23 Twilight kernel:    34.449234]   alloc irq_desc for 29 on node -1
Sep 27 11:42:23 Twilight kernel:    34.449239]   alloc kstat_irqs on node -1
Sep 27 11:42:23 Twilight kernel:    34.449267] tg3 0000:01:00.0: irq 29 for MSI/MSI-X
Sep 27 11:42:23 Twilight kernel:    34.514596] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 11:42:23 Twilight kernel:    34.572167] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Sep 27 11:45:09 Twilight avahi-daemon[2187]: avahi-daemon 0.6.25 starting up.

It appears that startup continued, sans the display, with the “default” kernel. When I attempted to install kernel “pae”, I was greeted with a regression message to inferior architecture, and did not pursue such.

#18

Have you tried a 32 bit install to see how it behaves?
I know it shouldn’t make any difference.
Was your Ubuntu 64 or 32?

#19

Ubuntu 10.04 was 32-bit (the *buntu web site said “not recommended” for the 64-bit.

Just completed the install of openSUSE 11.3 32-bit. Display is correct!!!

Seems that the 64-bit install is not exactly the same. :frowning: I am embarking on the post-install tasks: updates, KDE, etc.

Will post back.

Thanks for the assist!

#20

I knew Ub* recommended 32 hence my asking