My old gateway laptop became unstable. So I bought a new dell, and restored my 3
working Linux distros from backup tarballs:
Code
tar --numeric-owner -xzf tarball.tgz mountpoint
After carefully editing the grub and fstab entries to reflect the new unique
LABEL={label} of the {somewhat larger} partitions on the new laptop I was able
to get all three Linux working.
antiX took a long time trying to resolve the incorrect UUID references in
the initrd before it let me boot normally. But once booted it had no
problem creating a new one, and works well. {including moc, except it
sometimes doesn’t honor the “shuffle” “off” toggle.} And I had to use F6 in
the alsamixer to select “1 HDA Intel PCH” instead of the default. before I
could change the volume… Otherwise that copy of moc is working perfectly.
Mageia gave me a hard time with the initrd. But since I still had a copy of
the fstab it’s installer made, I was able to grep an unzipped copy of it’s
initrd for the files to edit, and rename with the values from
/dev/disk/by-uuid of the live-cd I was using to restore and edit the
filesystems with… Then with the new initrd it booted normally and everything
worked. {including moc, with the only exception that again I had to first
select the “1 HDA Intel PCH” soundcard - wish I could remember how to change
the default to “1”}
Opensuse on the other hand booted so close to normally on the first time that
I almost didn’t remember to generate a new initrd. Everything worked just fine
except moc. Which prompted me to create a new initrd, moc still failed. I then
tried reinstalling moc.
Code:
zypper ref
zypper rm moc
zypper in moc
No change.
Then I did an:
Code:
zypper up
Which updated my kernel and initrd… But moc still exits with the same error.
Code:
mocp
Running the server…
Trying JACK…
Trying ALSA…
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Trying OSS…
FATAL_ERROR: No valid sound driver
FATAL_ERROR: Server exited
BTW: I CAN play my music with Kaffeine, but I much prefer moc’s clean mc like
interface…
It would appear that on Jul 22, malcolmlewis did say:
> Hi
> Have you checked in YaST to ensure the sound card has been
> re-configured?
Good idea… didn’t work!
> If you going to re-install an app, you need to use the -f option to
> force and install.
>
> Code:
> --------------------
>
> zypper in -f moc
>
> --------------------
So, what does “force” do for a re-install? {possibly overwrite any existing
settings with first-run defaults??}
Anyway. it didn’t work.
> Sure it’s not a setting in your ~/ (home) directory? To check, create a
> test user and see if it works as required
That was something I already tried. No Joy…
I’m discovering though that I’m not as happy with the rest of the migrated
opensuse as I thought. Turns out that some other apps having a problem with the
sound too. Well restoring a running Linux from an AMD system to Intell
hardware was a long shot at best…
I just really didn’t want to start over with a new install, but it may be necessary
after all. I try to avoid that because I can’t even remember all the environmental
tweaks I had to do to get it working the way I want… Nor all the packages I
installed (and from which vendor etc…) <sigh>
Does opensuse have a method to extract a list of user installed packages that
can be used to {automatically?} install the same packages on another computer?
It would appear that on Jul 23, malcolmlewis did say:
> jtwdyp;2655455 Wrote:
> > Does opensuse have a method to extract a list of user installed packages
> > that
> > can be used to {automatically?} install the same packages on another
> > computer?
> Hi
> You could look at AutoYaST, pkgenpack (create a service pack) may be
> another, check the man page for some examples.
>
> You can export the repo list with zypper.
Thanks. I’ll have to look into those.
In the meantime, I’ve had a thought. I think all my problems are soundcard related.
But I don’t believe advanced users with actual (not built-in) sound cards, need to reinstall from
scratch if they buy a new sound card. Yet I’m pretty sure that pulsaudio and/or alsa keep crib
notes on sound card setup info.
Is there a way to purge all sound card configs {and possibly drivers} replacing them with new ones
based on auto-detection of the current sound card???
Preferably by some method that doesn’t automatically uninstall half my software due to temporarily
unresolved dependencies?
Boot your system to init 3
Remove /etc/modprobe.d/50-sound* files
Reboot
Boot to init 3, run **yast2 sound **and use the “Quick Configuration” option. Then try mocp or boot to init 5.
> Aww to hell with it, it’s worth suggesting anyway
>
> Boot your system to init 3
> Remove /etc/modprobe.d/50-sound* files
> Reboot
> Boot to init 3, run *yast2 sound *and use the “Quick Configuration”
> option. Then try mocp or boot to init 5.
It’s certainly worth a try before giving up and installing from scratch…
I’ll let you know how it works out.
But, if I don’t get around to it before tomorrow afternoon, it may be a week
before I’ll be where I can connect to the internet to send the reply. So don’t
give up on me when I drop off the grid. Which it seems like I’ll be doing
every other week for a while…
Thanks
