Got 2008.1, Installed, Now What? - Mandriva

This is a discussion on Got 2008.1, Installed, Now What? - Mandriva ; I finally got around to installing the 2008.1 Beta I
downloaded a week ago. Installation was interesting.
Details below, if interested.
Questions:
I got nothing in updates via the installed update
routines, but when I added cooker repositories from
the ...

Got 2008.1, Installed, Now What?

I finally got around to installing the 2008.1 Beta I
downloaded a week ago. Installation was interesting.
Details below, if interested.

Questions:

I got nothing in updates via the installed update
routines, but when I added cooker repositories from
the usc mirror, almost everything on the system has
an update. Should I install all these updates? Or
should I keep the Beta and just update things I am
interested in?

One main reason for trying the Beta is because it is
supposed to have support for some multimedia keyboards.
I have a Logitech Internet Pro, but choosing the
Logitech Internet or Internet Navigator results in
no functionality for the multimedia keys. Is this
keyboard just not yet supported, or is there something
else I must do? I have looked around in mcc and KDE
control center, but found nothing of value.

What is the threshhold on reporting problems? I have
run into a bunch of problems that seem to appear and
disappear as I change things. So far, I have not set
up an easy way to mail from the Beta, so I am not
reporting, but guidelines on reporting threshholds
would be appreciated.

Details on Installation:
(Verbose. Please ignore if you prefer otherwise.)

I decided to install the Gnome desktop to start with,
and that yielded an error message re
lib64readlines5-5.2-7mdv2008.1.x86_64.

Shifted to KDE and had a problem installing
lib64scim-input-pad0.1.1-3mdv2008.x86_64.
Rolled past that, and installation completed but
I don't think the multi-language input routines
will work.

An attempt to run rpm -qa died; error message not
written down and forgotten (dgi ?).

avahi and beagle are now removed. I hope this will
allow the machine to boot in reasonable time.

The real interesting bits resulted from my fat-fingering
or failure to remember the final digit on the name of
the partition I intended to install to. Instead of
the Beta going where intended, it went into the one-up
partition where all current backups were stored.
New backups are now in place, and I definitely remember
why keeping a few backups of everything vital on
removable media is a good idea.

It may be time to burn another dvd of user files...

The installer decided that my disks should be identified
in fstab by UUID number rather than the conventional
/dev/sd.. and my system claimed it was booting from
the cdrom rather than from the hard disk, even though
there was nothing in the cdrom. I changed fstab names
back to the familiar /dev/.... and ignored the claim
regarding where it was booting from. Tinkering with
fstab, and grub's menu.lst, and some other things took
a bit of time, but all is well that ends...

For the first time ever (since Mandrake 8.1) I have
had to put myself in the audio group for sound to work.
I do not know why it always worked before, nor why it
failed to work this time until I was a proper member
of audio, but such is life.

Cheers!

jim b.

--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.

Re: Got 2008.1, Installed, Now What?

On Sun, 10 Feb 2008 01:14:51 GMT, Jim Beard wrote:
> I finally got around to installing the 2008.1 Beta I
> downloaded a week ago. Installation was interesting.
> Details below, if interested.
>
> Questions:
>
> I got nothing in updates via the installed update
> routines, but when I added cooker repositories from
> the usc mirror, almost everything on the system has
> an update.

Yep, 2008.1 is cooker
> Should I install all these updates?

If you want fixes, and plan on reporting bugs, yes.

> Or should I keep the Beta and just update things I am interested in?

As long as you are not going to be reporting problems it is your call.
I think it is abusive to have the bug hunter looking into a problem
might not exist if your system had all updates.
> One main reason for trying the Beta is because it is
> supposed to have support for some multimedia keyboards.

Yes, and my HP multimedia keyboard is not working as I thought the
"feature list" indicated.

> What is the threshhold on reporting problems?

A problem should get fixed if reported and is reproducible.
> I have run into a bunch of problems that seem to appear and
> disappear as I change things.

You better have all updates in before reporting from what I gather
from your problems so far.

> So far, I have not set up an easy way to mail from the Beta, so I
> am not reporting,

# These munge headers so mail from users on wm81.home.test to outside
# world get changed to my junk accounts at yahoo and hotmail.com
sender_canonical_maps = hash:/etc/postfix/canonical_sender
smtp_generic_maps = hash:/etc/postfix/generic

Via cron,
You can use fetchyahoo to pull yahoo email into an account on your system.
You can use getlive to pull hotmail email into an account on your system.

> I decided to install the Gnome desktop to start with,
> Shifted to KDE and had a problem installing

I installed both and run KDE via startx at runlevel 3 default install
security level. Been pretty stable. Have not tried gnome.
> An attempt to run rpm -qa died; error message not
> written down and forgotten (dgi ?).
> avahi and beagle are now removed. I hope this will
> allow the machine to boot in reasonable time.

Hmmm, I did not install beagle/kerry but I only disabled the avahi deamon.
Too many packages seemed to want avahi.
> The real interesting bits resulted from my fat-fingering
> or failure to remember the final digit on the name of
> the partition I intended to install to.

Hehehe, been there, done that. Glad it was my hot backup partition.

What I have done is use "e2label" to label all my partitions.
Prior to install, I format the target partition then label it.
During partition phase of install, I toggle to expert mode.
Now I can click the partition, label, cut, Ok, Mount, /(paste)
I leave the install partition for last and unchecked format to preserve
the label.

> The installer decided that my disks should be identified
> in fstab by UUID number rather than the conventional
> /dev/sd.. and my system claimed it was booting from
> the cdrom rather than from the hard disk, even though
> there was nothing in the cdrom. I changed fstab names
> back to the familiar /dev/....

Fought that battle in the alpha 1 testshot.
As you have seen, I now use labels if fstab.
> For the first time ever (since Mandrake 8.1) I have
> had to put myself in the audio group for sound to work.
> I do not know why it always worked before, nor why it
> failed to work this time until I was a proper member
> of audio, but such is life.

I noticed sound does not work on a startx login but will come up later.
/var/log/messages has some reasons and I have not been back to see if
they fixed the problem yet or not. I did check at the time and it had
not been reported.

As usual you need to read all the bug reports to see if your problems
exists, you have updated your system and can recreate the problem.

Main difference I seen with your install and mine,
I did the 32 bit install from iso on HD not from cdrom and I picked
all groups except LSB and installed KDE and GNOME.

Re: Got 2008.1, Installed, Now What?

Bit Twister wrote:
> Yep, 2008.1 is cooker
> As usual you need to read all the bug reports to see if your problems
> exists, you have updated your system and can recreate the problem.
>
> Main difference I seen with your install and mine,
> I did the 32 bit install from iso on HD not from cdrom and I picked
> all groups except LSB and installed KDE and GNOME.

Looks like I need to update the system, and set up a means
to send mail, and then see how things go. My problem with
reproducible is twofold -- what to do when the problem(s)
seems to come and go as you make frequent changes to other
things? what to do when it is possible things are not
correctly installed & configured? Well, I'll deal with that
when I get to it. If I get to it.

And oddly enough, despite problems with GNOME aborting
my first attempt to install, after an install that
was supposed to provide KDE both are available. Everything
on the DVD installed, whether I asked for it or not.

Of course, life can never go so simply. A hard drive has
started making unh,unh,unh,unh scratchy sounds. I have my
main install and user files on one hard drive, with the
Beta and backup files on another. I may be moving to the
other, despite my preferences to keep things as they are.

And of course it is income tax time, and I still do my own
on my machine. Time to back up that directory again!

Cheers!

jim b.

--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.

Re: Got 2008.1, Installed, Now What?

On Sun, 10 Feb 2008 17:20:54 GMT, Jim Beard wrote:
> Looks like I need to update the system, and set up a means
> to send mail, and then see how things go. My problem with
> reproducible is twofold -- what to do when the problem(s)
> seems to come and go as you make frequent changes to other
> things?

Pretty sure it will only get fixed if you can provide the
steps to reproduce the problem.

> what to do when it is possible things are not
> correctly installed & configured?

Those should be reproducible assuming it is not some unique hardware gotcha.

> And oddly enough, despite problems with GNOME aborting
> my first attempt to install, after an install that
> was supposed to provide KDE both are available. Everything
> on the DVD installed, whether I asked for it or not.

I'm back from a 2008_1 update. 344 packages.
Noticed beagle was installed.

FlighGear still does not work.
>
> And of course it is income tax time, and I still do my own
> on my machine. Time to back up that directory again!

Yes, played with my taxes Friday. I have an old 900mhz box to run
turbo tax. Makes it nicer if you can point to last years tax file.

Re: Got 2008.1, Installed, Now What?

On Sat, 09 Feb 2008 20:14:51 -0500, Jim Beard wrote:
> One main reason for trying the Beta is because it is
> supposed to have support for some multimedia keyboards.
> I have a Logitech Internet Pro, but choosing the

Just fyi. I'm using the same keyboard, and in 2008.0, it is supported
directly by xorg.

To get these keys to work in kde, run kcontrol. Select "Regional &
Accessibility", then "Input actions". Expand the entry for "Mentor Office
Wireless Keyboard" (I know, that's not the right keyboard, but it has the
desired actions defined.). Select "Decrease Volume". Click on the
"Keyboard Shortcut" tab, and press the - volume key. Click on the
"DCOP Call settings". Change the arguments to 2 (that's the pcm mixer
channel). Click on apply, open the kmix mixer window, and try the
volume - key. Then apply the same changes for the Increase volume.
The other keys work in a similar manner, you just have to decide which
application to associate, with each key.

While 2008.1 may be supposed to do the above automatically, it can't
hurt to try the above, and see if it still works.

The keyboard models available are listed in
/usr/share/X11/xkb/rules/base.lst

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

Re: Got 2008.1, Installed, Now What?

David W. Hodgins wrote:
> On Sat, 09 Feb 2008 20:14:51 -0500, Jim Beard wrote:
>
>> One main reason for trying the Beta is because it is
>> supposed to have support for some multimedia keyboards.
>
> Just fyi. I'm using the same keyboard, and in 2008.0, it is supported
> directly by xorg.
>
> In /etc/X11/xorg.conf, I have
> Option "XkbModel" "logiik"
>
> Running xev, and selecting the + volume key shows the key identified as
> keysym 0x1008ff13, XF86AudioRaiseVolume, while the - volume shows as
> keysym 0x1008ff11, XF86AudioLowerVolume.
>
> To get these keys to work in kde, run kcontrol. Select "Regional &
> Accessibility", then "Input actions". Expand the entry for "Mentor Office
> Wireless Keyboard" (I know, that's not the right keyboard, but it has the
> desired actions defined.). Select "Decrease Volume". Click on the
> "Keyboard Shortcut" tab, and press the - volume key. Click on the
> "DCOP Call settings". Change the arguments to 2 (that's the pcm mixer
> channel). Click on apply, open the kmix mixer window, and try the
> volume - key. Then apply the same changes for the Increase volume.
> The other keys work in a similar manner, you just have to decide which
> application to associate, with each key.
>
> While 2008.1 may be supposed to do the above automatically, it can't
> hurt to try the above, and see if it still works.
>
> The keyboard models available are listed in
> /usr/share/X11/xkb/rules/base.lst

I have not yet tried it in 2008.1, but it definitely works in 2008.0.
I have the two eight-notes launching Amarok, the envelope launching
Thunderbird, home locking the screen, and the increase volume,
decrease volume, and mute keys working. That leave the play/pause
key not mapped to anything, but I will leave that for later.

The odd feature is that if I have the kmix speaker in the toolbar
and bring it up, it blocks the keys from working. Also, changes made
using the keys do not affect the toolbar kmix slider, but do change
the volume level. If you put the slider to top, then lower the
volume with the key while the slider is minimized, when you bring the
slider up again it will be at the top and you cannot increase the
volume.

Cheers!

jim b.

--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.

Re: Got 2008.1, Installed, Now What?

Jim Beard wrote:
>> Questions:
>>
>> I got nothing in updates via the installed update
>> routines, but when I added cooker repositories from
>> the usc mirror, almost everything on the system has
>> an update.
>
>> Should I install all these updates?

My first bug report is filed, Nr 36760. rpm returns an
error message upon each attempt to use it, and then
disappears. I tried using gftp to get an update
package and install with rpm, but no joy.

If I get real enthusiastic, I may copy over rpm
from 2008.0 and see if it will run.

Using mcc, at one point, I had 1507 updates listed, with a
notice that none could be installed. AT other points, mcc
and urpmi both told me my system was all up to date. I have
my doubts about the accuracy of the long list, but something
is definitely not working as expected.

Incidentally, booting 2008.1 is still taking several minutes.
Shorewall loads, and the machine then sits there and
contemplates its naval or something for a few minutes before
something times out and it goes on to finish booting. Any
idea what it might be? With beagle and avahi removed,
the choices seem to be:

> I have
> my doubts about the accuracy of the long list, but something
> is definitely not working as expected.

I am going to have to guess it is 64 bit install gotcha.
> Incidentally, booting 2008.1 is still taking several minutes.
> Shorewall loads, and the machine then sits there and
> contemplates its naval or something for a few minutes before
> something times out and it goes on to finish booting. Any
> idea what it might be? With beagle and avahi removed,
> the choices seem to be:

If I had to guess, avahi not installed is causing the grief.
Then again, it can be the 64 bit install. I installed 32 bit.

Of course maybe your bad disk is helping you into the ditch.

I did have one big pause but come to find out it was a full check on my
84 gig partition.

If I were you, I would have to do a 32 bit install to prove it is a 64
bit problem.

Due to a problem found in alpha release, my admin install diary now has
the following:

Re: Got 2008.1, Installed, Now What?

Jim Beard writes:
>Jim Beard wrote:
> >> Questions:
> >>
> >> I got nothing in updates via the installed update
> >> routines, but when I added cooker repositories from
> >> the usc mirror, almost everything on the system has
> >> an update.
> >
> >> Should I install all these updates?
>Bit Twister wrote:
>> If you want fixes, and plan on reporting bugs, yes.
>My first bug report is filed, Nr 36760. rpm returns an
>error message upon each attempt to use it, and then
>disappears. I tried using gftp to get an update
>package and install with rpm, but no joy.
>If I get real enthusiastic, I may copy over rpm
>from 2008.0 and see if it will run.
>Using mcc, at one point, I had 1507 updates listed, with a
>notice that none could be installed. AT other points, mcc
>and urpmi both told me my system was all up to date. I have
>my doubts about the accuracy of the long list, but something
>is definitely not working as expected.
>Incidentally, booting 2008.1 is still taking several minutes.
>Shorewall loads, and the machine then sits there and
>contemplates its naval or something for a few minutes before
>something times out and it goes on to finish booting. Any
>idea what it might be? With beagle and avahi removed,
>the choices seem to be:

Uh, you can see what is next. It is probably shorewall doing some external
address search which is timing out.
Note that postfix is often the culprit, since it does do address
resolution, but it is too late in the sequence, unless you were really not
watching the screen to see what had finished running before the hangup.

Re: Got 2008.1, Installed, Now What?

Well, the copy of the Beta I have is not Beta-ready.
I cannot update, and I am abandoning the effort.

Yesterday, much of my home directory stuff had been
reassigned to owner nobody. Still group jim. I changed
that back yesterday, but today many of them had gone back.
Not nice. With the directory owned by nobody, I could
not load KDE due to inability to set the .auth* file.
Changed all that stuff to owner/group jim.

I mounted my partions with the 2008.0 system commands,
and the old rpm works, at least enough to do a rpm -qa.
Hoping that would allow me to updata, I tried urpmi
and then mcc. I still cannot get an update for anything.

Given that BitTwister thought removing Avahi might have
had negative effects, I decided to reinstall. When the
splash came up and asked me if I wanted to install or
to update 2008.0 or 2008.1, I decided that I would avail
myself of this nifty shortcut, and went for the upgrade
2008.1.

The installer ran for a while and then gave me an estimated
time to completion of over 3 hours, installing from the DVD.
I let it run a while, to see if it was just miscalibrated,
but progress on the progress bar over time suggested that
would be about right. I hit the soft reboot button, and
went back to my normal 2008.0.

Only to find that the installer had somehow mucked with
my 2008.0. 2008.1 was on partition sda6, 2008.0 scattered
across a half dozen partitions on sdb. The installer should
not have touched sdb, with the possible exception of
/boot/grub/menu.lst on sdb1. End of story.

Except, to get everything back operating smoothly, I had
to do a full system restore.

I am not inclined to dedicate a second machine to Beta
testing (it would have to be a Pentium 4, or buy another
64-bit machine -- neither is attractive to me) nor do a
complete backup each time I want to try the Beta and
expect to do a complete restore after tinkering with it.
That is more than I feel like these days. Maybe when I
am retired, but that may be some time away.

No cheers.

jim b.

--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.

Re: Got 2008.1, Installed, Now What?

On Tue, 12 Feb 2008 01:01:57 GMT, Jim Beard wrote:
> Well, the copy of the Beta I have is not Beta-ready.
> I cannot update, and I am abandoning the effort.
>
> I am not inclined to dedicate a second machine to Beta
> testing (it would have to be a Pentium 4, or buy another
> 64-bit machine -- neither is attractive to me) nor do a
> complete backup each time I want to try the Beta and
> expect to do a complete restore after tinkering with it.

Dang, all I can say is my 2008.1 32 bit is without all the problems
you have indicated.

After seeing your post, I booted 2008.1 and did another 96 package
update and checked junk to verify uid/gid was still 500/500.

I never do the update, always pick custom clean install.

Doing the install from Hard Drive is faster than from DVD.

I started the 64 bit beta download and will try it to see if I have
your problems.

Re: Got 2008.1, Installed, Now What?

Bit Twister wrote:
> On Tue, 12 Feb 2008 01:01:57 GMT, Jim Beard wrote:
>> Well, the copy of the Beta I have is not Beta-ready.
>> I cannot update, and I am abandoning the effort.
> I never do the update, always pick custom clean install.

Yes, but since all I was really after was the two packages
I had removed, I thought it might go faster. The initial
install was to a clean partition. Of course, the installer
decided to overwrite everything....
> Doing the install from Hard Drive is faster than from DVD.

Yes, but I had not bothered to make a bootable cd to start
things off with.
> I started the 64 bit beta download and will try it to see if I have
> your problems.

Part of the problem may be I had (note past tense) a week-old
copy. If the updated packages are now in the Beta download,
all may go well.

I'll be waiting to see how your's goes.

Cheers!

jim b.

--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.

Re: Got 2008.1, Installed, Now What?

On Tue, 12 Feb 2008 02:23:15 GMT, Jim Beard wrote:
> Part of the problem may be I had (note past tense) a week-old
> copy.

ISOs are released only once. They are not updated until next iso build.
No idea if we bet beta 2 or it will be rc1.

I assume I downloaded the same iso image as you. Time stamp set same
as found on carrol mirror.

Partition formatted and labeled under 2008.0 then unchecked "format" in
partition phase install to keep label mounting for /.

fstab has label mounting not UID partition ID.
Everything is under /.
Swap is shared across all installs.

Default Security level: High.

Initial package install took about 23 minutes using a Hard Drive install.
All package groups selected except LSB, and only picked KDE, GNOME desktops.
Went through and added a bunch of stuff plus all games and database.
Disabled avahi-daemon during Configuration phase of install. See list
of active daemon/service set on boot end of reply.

On first boot, KDE desktop, checked rpm -qa, it worked.

Did my usual manual wget, rpm, urpmi, perl-URPM, rpmdrake, rpm-helper package
pre-update then did the full auto update with
urpmi --wget --auto-select --auto
517 package updates were installed.
One missing package. Same thing on 32 bit today.
One Gnome package failure because of a package bug.

Checked rpm -qa again, still worked.
No apparent corruption on other partitions.

Have not executed all cron jobs, yet, to check for your nobody and partition
corruption problems.

I am going to assume you md5 checked your iso download before burn and
md5 after iso burn.

If so, first guess is heat problem on your system which is odd because
I would have assumed your disk restore would heat up the cpu more so
than normal operation.

Based on that assumption, that would leave some instruction or one of
the daemon/services dinked up your system. Here is my daemon list:
Forgot to set runlevel 5 so system booted at 5.

xinetd based services:
cups-lpd: off
cvs: off
proftpd-xinetd: off
rsync: off
sshd-xinetd: off

Final WAG, you have some Spooky Dooky going on in your hardware.

Do consider closing the bug reports you opened.

Re: Got 2008.1, Installed, Now What?

On Tue, 12 Feb 2008 06:55:02 +0000 (UTC), Bit Twister wrote:

Ok, finished the 2008.1 beta 64 bit install.

Ran all /etc/cron.* jobs and no disk partition corruption and
/home accounts did not flip over to nobody ownership.

No abnormal pauses during boot at runlevel 3.

After sleeping, I thought maybe you have hardware problems with
dvd/sata drive interference or something.

But, if your restore was from same media hardware used during iso
install I have no good guess as to where to look for the problems
you had.

Re: Got 2008.1, Installed, Now What?

Bit Twister wrote:
> On Tue, 12 Feb 2008 02:23:15 GMT, Jim Beard wrote:
>
>> Part of the problem may be I had (note past tense) a week-old
>> copy.
>
> ISOs are released only once. They are not updated until next iso build.
> No idea if we bet beta 2 or it will be rc1.

Initially, I had the installer format sda6. I did have to tinker
with fstab inconsequence.
>
> fstab has label mounting not UID partition ID.
> Everything is under /.
> Swap is shared across all installs.

I don't know where the installer put swap for 2008.1. It is
sdb5 for 2008.0.
> Default Security level: High.

I dropped this to standard on my system.
>
> Initial package install took about 23 minutes using a Hard Drive install.
> All package groups selected except LSB, and only picked KDE, GNOME desktops.
> Went through and added a bunch of stuff plus all games and database.
> Disabled avahi-daemon during Configuration phase of install. See list
> of active daemon/service set on boot end of reply.

Installed from a DVD. md5sum checked for the iso file on disk
before burning and again for the dvd burned.
>
> On first boot, KDE desktop, checked rpm -qa, it worked.
>
> Did my usual manual wget, rpm, urpmi, perl-URPM, rpmdrake, rpm-helper package
> pre-update then did the full auto update with
> urpmi --wget --auto-select --auto
> 517 package updates were installed.
> One missing package. Same thing on 32 bit today.
> One Gnome package failure because of a package bug.

My first attempt was to install Gnome, and that aborted due
to package failure. Second attempt, with KDE selected, also
had a package failure, but I don't think that was significant.
>
> Checked rpm -qa again, still worked.
> No apparent corruption on other partitions.

Unscrambling fstab for 2008.1 was a chore. Unfamiliarity with
labels/UUIDs did not help.
>
> Have not executed all cron jobs, yet, to check for your nobody and partition
> corruption problems.
>
> I am going to assume you md5 checked your iso download before burn and
> md5 after iso burn. Yep.
>
> If so, first guess is heat problem on your system which is odd because
> I would have assumed your disk restore would heat up the cpu more so
> than normal operation.
>
> Based on that assumption, that would leave some instruction or one of
> the daemon/services dinked up your system. Here is my daemon list:
> Forgot to set runlevel 5 so system booted at 5.
>
> $ cat chkconfig.list_orig
> acpi 0ff 1ff 2n 3n 4n 5n 6ff

I no longer have 2008.1 on the system, but changes were first to
disable avahi and beagle, and later to remove them. Not long
before I removed 2008.1 totally, error messages complained that
Console-kit could not be found.
>
> Final WAG, you have some Spooky Dooky going on in your hardware.

Always possible, but 2008.0 seems to work fine. And, I cannot see
how dinking up fstab would have messed up things without making
it totally obvious. The OS was finding the correct partitions and
programs (after I got fstab straightened out).
>
> Do consider closing the bug reports you opened.

The only thing opened was the rpm problem 36760 I think it was.
That was a problem from the git-go, and copying over and running
rpm for 2008.0 under 2008.1 worked, so I am inclined to leave it.
It is possible that the 2008.1 rpm was corrupted somehow, or the lib
file that contained the symbol missing could have been corrupted,
but this seems unlikely.

I may take another try at it this coming weekend.

Cheers!

jim b.

--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.

Dang, misremembered start of thread, thought you installed on sdb.
>
> Initially, I had the installer format sda6. I did have to tinker
> with fstab inconsequence.

Good chance for setting wrong one there unless you cut/pasted comment
above UUID.
>
> I don't know where the installer put swap for 2008.1. It is
> sdb5 for 2008.0.

I never have had to set swap location except day-one install.
Custom always found/set it for me.
>
>> Default Security level: High.
>
> I dropped this to standard on my system.

Hehehe, you sure are making it hard on re-creating your problem.

>
> My first attempt was to install Gnome, and that aborted due
> to package failure. Second attempt, with KDE selected, also
> had a package failure, but I don't think that was significant.

I had no package until update. On next test shot, try picking both KDE,GNOME
>
> Unscrambling fstab for 2008.1 was a chore. Unfamiliarity with
> labels/UUIDs did not help.

Did you dink with fstab before updates?
Did you reboot after fstab changes?

> I no longer have 2008.1 on the system, but changes were first to
> disable avahi and beagle, and later to remove them. Not long
> before I removed 2008.1 totally, error messages complained that
> Console-kit could not be found.

Recommend install, updates, reboot, then start dinking around.
>>
>> Final WAG, you have some Spooky Dooky going on in your hardware.
>
> Always possible, but 2008.0 seems to work fine.

Yes, but could be a dual-core bug in 2008.1

> And, I cannot see
> how dinking up fstab would have messed up things without making
> it totally obvious. The OS was finding the correct partitions and
> programs (after I got fstab straightened out).

I will agree, ONLY if fstab changes were done with unmounted partitions.

>
> The only thing opened was the rpm problem 36760 I think it was.
> That was a problem from the git-go, and copying over and running
> rpm for 2008.0 under 2008.1 worked, so I am inclined to leave it.

What can I say, it worked after boot for me. I do remember two rpm
updates from cooker so you might have snagged a bad one.

> I may take another try at it this coming weekend.

My suggestion, use e2label to label your partitions prior to install
to bypass the UUID setup.

I recommend my type install to reduce differences so that you might
get a known starting point for troubleshooting.

Cut/paste 2008.0 stanza into menu.lst, and reboot just to keep
everyone honest.

At this point your install would look pretty close to mine and should work.
That assumes the dual-core and Murphy did not get together.

Now you start dinking with fstab and whatnot.

Re: Got 2008.1, Installed, Now What?

On Wed, 13 Feb 2008 00:46:47 +0000 (UTC), Bit Twister wrote:
>
> At this point your install would look pretty close to mine and should work.
> That assumes the dual-core and Murphy did not get together.

2008.0 is on sdb. 2008.1 went onto sda6. XP on sda1
>
>> Initially, I had the installer format sda6. I did have to tinker
>> with fstab inconsequence.
>
> Good chance for setting wrong one there unless you cut/pasted comment
> above UUID.

I simply reentered from old fstab entries (backup) since I had not
changed any partitions, other than formatting sda6.
>
>> I don't know where the installer put swap for 2008.1. It is
>> sdb5 for 2008.0.
>
> I never have had to set swap location except day-one install.
> Custom always found/set it for me.
>
>>> Default Security level: High.
>> I dropped this to standard on my system.
>
> Hehehe, you sure are making it hard on re-creating your problem.
>
>
>> My first attempt was to install Gnome, and that aborted due
>> to package failure. Second attempt, with KDE selected, also
>> had a package failure, but I don't think that was significant.
>
> I had no package until update. On next test shot, try picking both KDE,GNOME

This is odd, as I was not given an option to select both. When
things started installing, I likewise did not have any choice about
what installed. The installer just went to work, without so much as
a by-your-leave.
>
>> Unscrambling fstab for 2008.1 was a chore. Unfamiliarity with
>> labels/UUIDs did not help.
>
> Did you dink with fstab before updates?

Yes, but I do not see how that could have caused rpm -qa
(actually, any invocation of rpm) to be unable to find a
symbol.
> Did you reboot after fstab changes?

Yes.
>
>> I no longer have 2008.1 on the system, but changes were first to
>> disable avahi and beagle, and later to remove them. Not long
>> before I removed 2008.1 totally, error messages complained that
>> Console-kit could not be found.
>
> Recommend install, updates, reboot, then start dinking around.

I have cleaned sda6 out, formatted it ext3 (installer set it to
native Linux, ext2).

Should I try the mirrors listed in 2008.1 or go to
easyurpmi.zarb.org? 2008.1 listed gatech, while easyurpmi gave
usc. Neither would work for me.
>
>>> Final WAG, you have some Spooky Dooky going on in your hardware.
>> Always possible, but 2008.0 seems to work fine.
>
> Yes, but could be a dual-core bug in 2008.1
>
>
>> And, I cannot see
>> how dinking up fstab would have messed up things without making
>> it totally obvious. The OS was finding the correct partitions and
>> programs (after I got fstab straightened out).
>
> I will agree, ONLY if fstab changes were done with unmounted partitions.

Point. Changes were to partitions not in use, but they were
mounted. Made changes. rebooted.
>
>> The only thing opened was the rpm problem 36760 I think it was.
>> That was a problem from the git-go, and copying over and running
>> rpm for 2008.0 under 2008.1 worked, so I am inclined to leave it.
>
> What can I say, it worked after boot for me. I do remember two rpm
> updates from cooker so you might have snagged a bad one.
>
>
>> I may take another try at it this coming weekend.
>
> My suggestion, use e2label to label your partitions prior to install
> to bypass the UUID setup.

I'll have to man e2label on that. I labeled hda6 2008beta in mcc.
Guess I will change that.
>
> I recommend my type install to reduce differences so that you might
> get a known starting point for troubleshooting.
>
> Go ahead and create/format your 2008.1 partition sda6 and then label it.
> e2label /dev/sda6 2008_1
>
> I picked cooker 2008.1 main, contrib non-free from easyurpm and saved
> results into mm in a 2008.0 partition and chmod +x mm
>
>
> If your iso is still on hard drive, loop mount the iso and
> burn the ~12M /cdrom/x86_64/install/images/boot.iso to cd.

Hmmm. I mounted the DVD and copied the boot.iso to my hard drive.
Then I simply used k3b to burn it to cd. K3b asked if I wanted to
burn it direct as an ISO, and I gave it a yes. Three times k3b
complained that the original and the burned copy differed, but
md5sum for boot.iso and for /dev/hda matched, so I assume the
copy was good. Will it boot? Or was copoying boot.iso from the
DVD illegit? Guess I will find out.

I think I remember instructions on how to loop mount an iso,
some months ago I think but Google archives will have it if needed.
> I have Pocket CD-RW cds for those small burns. (186 MB/21 MINUTE)
> burns quick.

Burning 11 MB or whatever it was took 2 or 3 minutes, K3B quits
adding to the CD when it runs out of bytes.
>
> On boot, pick Hard drive
> pick drive where iso resides.
> pick partition where iso resides.
> If in sub-directory, enter sub-directory name.
> pick iso from list.
>
> If not, use DVD.
> I just wanted you to be able to rule out DVD and it's hardware.
>
> Pick Install, and Custom in partition phase.
> Leave 2008.1 partition for last.
> At bottom of gui partition tool, click Toggle Expert mode.
> Now you click each formatted partition,
> click label, and control c to copy each label, OK
> click mount point, click in box, control v to paste label.

Re: Got 2008.1, Installed, Now What?

Hmmm, Under Memory, I clicked on Memory Module (A0)
Speed: was towards bottom.

>> I had no package until update. On next test shot, try picking both KDE,GNOME
>
> This is odd, as I was not given an option to select both. When
> things started installing,

First package screen has Radio selections
KDE
GNOME
Custom Install, I picked last one,
>> Did you dink with fstab before updates?
>
> Yes, but I do not see how that could have caused rpm -qa
> (actually, any invocation of rpm) to be unable to find a
> symbol.

Was thinking about crap spread into other partitions problem you had.
> I have cleaned sda6 out, formatted it ext3 (installer set it to
> native Linux, ext2).

Check that format pick list and set it Journalised FS: ext3

Click sda6 to reformat that 2008.1 partition
Click Toggle to Expert mode.
Click Type.
Select Journalised FS: ext3
Set label
Then format it.
>
> Should I try the mirrors listed in 2008.1 or go to
> easyurpmi.zarb.org? 2008.1 listed gatech, while easyurpmi gave
> usc. Neither would work for me.

I make it a habit when changing fstab entry to umount first, make
change, mount it to verify change works.
No need to find a problem during boot.
> I'll have to man e2label on that. I labeled hda6 2008beta in mcc.
> Guess I will change that.

label text will not matter as long as it does not start with /

Since I have all install commands in my admin diary the command line
cut/paste is faster than mcc.

> Hmmm. I mounted the DVD and copied the boot.iso to my hard drive.
> Then I simply used k3b to burn it to cd. K3b asked if I wanted to
> burn it direct as an ISO, and I gave it a yes. Three times k3b
> complained that the original and the burned copy differed, but
> md5sum for boot.iso and for /dev/hda matched, so I assume the
> copy was good. Will it boot? Or was copoying boot.iso from the
> DVD illegit? Guess I will find out.