Re: [gentoo-amd64] Upgrading from 2004.3 to 2005.0
I am now getting closer to a successful upgrade. I re-emerged portage and gcc with multilib set in my USE flags. Then I followed the manual upgrade path as described in the upgrade guide. I have reached the point of changing /etc/make.profile to refer to the 2005.0 amd64 profile. I then try to emerge glibc and receive the following error: >>> emerge (1 of 1) sys-libs/glibc-2.3.4.20041102-r1 to / It appears you have switched to the 2005.0 profile without following the upgrade guide. Please see the following URL for more information: http://www.gentoo.org/proj/en/base/amd64/2005.0-upgrade-amd64.xml I've been following the instructions carefully. What's the test that fails and causes the above message? -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Upgrade system from Athlon to Athlon64
Easiest bet is to just install a fresh on the 64 bit box... On Tue, 29 Mar 2005 18:06:47 -0500, Matthew Daubenspeck <[EMAIL PROTECTED]> wrote: > Well, a whole new machine actually. I just kind of paraphrased :) > > And yes, I would prefer running it in 64bit mode, not just 32. > > On Tue, Mar 29, 2005 at 05:09:15PM -0500, Drew Kirkpatrick wrote: > > I assume you got a new motherboard too??? > > > > > > On Tue, 29 Mar 2005 16:46:41 -0500, Matthew Daubenspeck > > <[EMAIL PROTECTED]> wrote: > > > I have a perfectly sane and working system running on an Athlon 1700+ > > > system. I purchased a new Athlon64 processor and would like to move the > > > system to amd64. Is there a doc or how-to on doing such? > > > -- > > > Matthew Daubenspeck > > > http://www.oddprocess.org > > > > > > 16:43:31 up 3 days, 5:42, 1 user, load average: 0.00, 0.08, 0.14 > > > > > > -- > > > gentoo-amd64@gentoo.org mailing list > > > > > > > > > > -- > > gentoo-amd64@gentoo.org mailing list > > > > -- > Matthew Daubenspeck > http://www.oddprocess.org > > 18:06:15 up 3 days, 7:04, 1 user, load average: 0.35, 0.30, 0.18 > > -- > gentoo-amd64@gentoo.org mailing list > > -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Upgrade system from Athlon to Athlon64
Well, a whole new machine actually. I just kind of paraphrased :) And yes, I would prefer running it in 64bit mode, not just 32. On Tue, Mar 29, 2005 at 05:09:15PM -0500, Drew Kirkpatrick wrote: > I assume you got a new motherboard too??? > > > On Tue, 29 Mar 2005 16:46:41 -0500, Matthew Daubenspeck > <[EMAIL PROTECTED]> wrote: > > I have a perfectly sane and working system running on an Athlon 1700+ > > system. I purchased a new Athlon64 processor and would like to move the > > system to amd64. Is there a doc or how-to on doing such? > > -- > > Matthew Daubenspeck > > http://www.oddprocess.org > > > > 16:43:31 up 3 days, 5:42, 1 user, load average: 0.00, 0.08, 0.14 > > > > -- > > gentoo-amd64@gentoo.org mailing list > > > > > > -- > gentoo-amd64@gentoo.org mailing list > -- Matthew Daubenspeck http://www.oddprocess.org 18:06:15 up 3 days, 7:04, 1 user, load average: 0.35, 0.30, 0.18 -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Upgrading from 2004.3 to 2005.0
If you follow the profile update howto exactly you'll get this error about missing libsandbox.so. Between the emerge portage lines and the rm /lib32 /usr/lib32 etc. lines libsandbox gets deleted. Re-emerge portage: emerge -v --oneshot '>=sys-apps/portage-2.0.51-r9' just before you do the rm /lib32 /usr/lib32 step... It's also worthwhile doing all the preliminary emerges in that howto even if an emerge -pv says that its just a re-install - the glibc bootstrap in the new profile needs everything there or it will barf. I hurried it the first time and it didn't work - spent a while diagnosing and basically realised that I needed to do it carefully, along with that extra emerge of portage step. W. Jeremy Huddleston wrote: > On Tue, 2005-03-29 at 20:32 +1000, Jason White wrote: > >>Hello, >> >>I followed the 2005.0 upgrade guide and decided to use the >>Makefile-profile_update-2005.0 method. >> >>The makefile executed properly until it reached the following line: >> >>cp /emul/linux/x86/lib32/libsandbox.so /lib32 >>(no such file or directory) > > > Did you have a multilib portage? If so, you should have that file... > > re-emerge portage with USE=multilib and continue the Makefile. There's > a bash version available here > http://dev.gentoo.org/~eradicator/amd64/2005upgrade.sh , but I haven't > tested it out yet. It looks like it should work. Please give feedback. > > >>I have the full output available and can determine the versions of >>installed packages as required. >> >>I also noticed that after the (still incomplete) upgrade, alsa sound >>drivers are no longer loaded correctly; /etc/init.d/alsasound produces >>a "unable to load necessary drivers" error, but without any more >>specific indication of the cause. >>I've checked the configuration files I recently updated with >>dispatch-conf but can't find the cause. > > > Whatever that is has nothing to do with 2005.0 upgrade. Did you change > kernels? > > >>Suggestions on any of the above would be most welcome. I would like to >>start by fixing the profile update, then work on the alsa problem. >> >> >>-- >>gentoo-amd64@gentoo.org mailing list > > > -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] why is mono masked in default-linux/amd64/use.mask?
mono-1.1.4 and mono-1.1.5 are already masked in package.mask, use mono won't be automatically set. I figure that if a user manually sets USE=mono, then they deserve dependency errors if they don't unmask it, and it would be nice to allow us bleeding-edge people who want it anyway (and mono-1.1.4 seems to work just fine for me) to have the corresponding use flag. So why is it masked? --Andy -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Upgrade system from Athlon to Athlon64
On Tue, 2005-03-29 at 16:46 -0500, Matthew Daubenspeck wrote: > I have a perfectly sane and working system running on an Athlon 1700+ > system. I purchased a new Athlon64 processor and would like to move the > system to amd64. Is there a doc or how-to on doing such? If you don't mind running 32-bit only userland, then you can just put the disk into the new box and be done. If you want to change to 64-bit, you probably have to re-install. They are different architectures to Gentoo, it would be like "migrating" a ppc install to a sparc box. Daniel -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Upgrade system from Athlon to Athlon64
I assume you got a new motherboard too??? On Tue, 29 Mar 2005 16:46:41 -0500, Matthew Daubenspeck <[EMAIL PROTECTED]> wrote: > I have a perfectly sane and working system running on an Athlon 1700+ > system. I purchased a new Athlon64 processor and would like to move the > system to amd64. Is there a doc or how-to on doing such? > -- > Matthew Daubenspeck > http://www.oddprocess.org > > 16:43:31 up 3 days, 5:42, 1 user, load average: 0.00, 0.08, 0.14 > > -- > gentoo-amd64@gentoo.org mailing list > > -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Upgrade system from Athlon to Athlon64
I have a perfectly sane and working system running on an Athlon 1700+ system. I purchased a new Athlon64 processor and would like to move the system to amd64. Is there a doc or how-to on doing such? -- Matthew Daubenspeck http://www.oddprocess.org 16:43:31 up 3 days, 5:42, 1 user, load average: 0.00, 0.08, 0.14 -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] segfaulting tar
I have run into the YP problem myself in the past. I am embarrassed to
say that I didn't file a bug report. As a work around, I changed
nsswitch.conf to remove the nis entries. I think there is a bug in one of
the nis libraries. Once I get past the upgrade, I restore the nis entries.
In normal operation I don't seem to have any more YP related problems.
--
Steve Herber[EMAIL PROTECTED] work: 206-221-7262
Security Engineer, UW Medicine, IT Services home: 425-454-2399
On Tue, 29 Mar 2005, Andreas Vinsander wrote:
> Hi!
>
> Started the installation of 64 bit gentoo yesterday (when I saw that
> 2005.0 was available)... everything went smooth, until I rebooted into
> my new shiny system.
>
> The tar command keeps segfaulting on me when bootin directly into the
> system. The same binary works flawlessly when chrooting from the livecd
> into the system.
>
> Running stable amd64 (with one exception see below)
> * Tried running memtest86+ for 3 hours without any errors
> * Tried kernel gentoo-sources-2.6.11-r4 (gentoo-sources-2.6.9-r14 seems
> a bit old?) but that didn't make tar work
> * Re-emerged glibc and tar (both from amd64 stable), still non-working tar
> * I haven't looked at the core file dumped by tar yet
>
> Now to what I did find out:
> * According to strace (strace dump attached) it seems like tar barely
> gets through loading some libs, bailing out when reaching yp stuff.
> Hmmm... I don't run ypbind when chrooting into the system from the
> livecd, but I do run it on the fully booted system. Might be something
> to investigate a bit more... Yep, turning off ypbind makes tar complete
> unpacking any tar-archive... strange... Re-emergeing ypbind doesn't help...
> What might be the reason for this? I have run out of clues...
>
> Here's my make.conf USE, CFLAGS and CHOST variables:
> USE="-gtk -gnome -ipv6 alsa cdr dvd dvdr jack kde nptl ntplonly qt"
> CFLAGS="-march=k8 -O2 -pipe"
> CXXFLAGS="${CFLAGS}"
> CHOST="x86_64-pc-linux-gnu"
>
>
> /Andreas
>
--
gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] User Mode Linux
> Do I need a full 32-bit chroot to compile a 32-bit guest? Or can I just > pass a SUBARCH=x86 (or something like that) to compile it? SUBARCH does not work (at least not for me) I have cross posted to uml-user ML, in case anyone has a better way of compiling x86 guests on a x86-64 host. Antoine -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] segfaulting tar
On Tue, 2005-03-29 at 19:56 +0200, Andreas Vinsander wrote: > Hi! > > Started the installation of 64 bit gentoo yesterday (when I saw that > 2005.0 was available)... everything went smooth, until I rebooted into > my new shiny system. > > The tar command keeps segfaulting on me when bootin directly into the > system. The same binary works flawlessly when chrooting from the livecd > into the system. ... > Yep, turning off ypbind makes tar complete > unpacking any tar-archive... strange... Re-emergeing ypbind doesn't help... > What might be the reason for this? I have run out of clues... Known bug. It's fixed in the latest glibc. signature.asc Description: This is a digitally signed message part
Re: [gentoo-amd64] Upgrading from 2004.3 to 2005.0
On Tue, 2005-03-29 at 20:32 +1000, Jason White wrote: > Hello, > > I followed the 2005.0 upgrade guide and decided to use the > Makefile-profile_update-2005.0 method. > > The makefile executed properly until it reached the following line: > > cp /emul/linux/x86/lib32/libsandbox.so /lib32 > (no such file or directory) Did you have a multilib portage? If so, you should have that file... re-emerge portage with USE=multilib and continue the Makefile. There's a bash version available here http://dev.gentoo.org/~eradicator/amd64/2005upgrade.sh , but I haven't tested it out yet. It looks like it should work. Please give feedback. > I have the full output available and can determine the versions of > installed packages as required. > > I also noticed that after the (still incomplete) upgrade, alsa sound > drivers are no longer loaded correctly; /etc/init.d/alsasound produces > a "unable to load necessary drivers" error, but without any more > specific indication of the cause. > I've checked the configuration files I recently updated with > dispatch-conf but can't find the cause. Whatever that is has nothing to do with 2005.0 upgrade. Did you change kernels? > Suggestions on any of the above would be most welcome. I would like to > start by fixing the profile update, then work on the alsa problem. > > > -- > gentoo-amd64@gentoo.org mailing list signature.asc Description: This is a digitally signed message part
[gentoo-amd64] segfaulting tar
Hi!
Started the installation of 64 bit gentoo yesterday (when I saw that
2005.0 was available)... everything went smooth, until I rebooted into
my new shiny system.
The tar command keeps segfaulting on me when bootin directly into the
system. The same binary works flawlessly when chrooting from the livecd
into the system.
Running stable amd64 (with one exception see below)
* Tried running memtest86+ for 3 hours without any errors
* Tried kernel gentoo-sources-2.6.11-r4 (gentoo-sources-2.6.9-r14 seems
a bit old?) but that didn't make tar work
* Re-emerged glibc and tar (both from amd64 stable), still non-working tar
* I haven't looked at the core file dumped by tar yet
Now to what I did find out:
* According to strace (strace dump attached) it seems like tar barely
gets through loading some libs, bailing out when reaching yp stuff.
Hmmm... I don't run ypbind when chrooting into the system from the
livecd, but I do run it on the fully booted system. Might be something
to investigate a bit more... Yep, turning off ypbind makes tar complete
unpacking any tar-archive... strange... Re-emergeing ypbind doesn't help...
What might be the reason for this? I have run out of clues...
Here's my make.conf USE, CFLAGS and CHOST variables:
USE="-gtk -gnome -ipv6 alsa cdr dvd dvdr jack kde nptl ntplonly qt"
CFLAGS="-march=k8 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="x86_64-pc-linux-gnu"
/Andreas
tar.strace.bz2
Description: Binary data
--
gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] XFS File system and new partition
Luigi Pinna wrote: > Hello! > I want to create a new partition with a different block size (I want to > use it in a RAID array). > I searched in Internet but I doesn't find an updated guide with the > support size block and all the supported options. > Someone can suggest a link, a guide or can say me what it's supported > now? I use a 2.6.11-r kernel. > Luigi file:///usr/src/linux/Documentation/filesystems/xfs.txt Further details at http://oss.sgi.com/projects/xfs/ regards -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] No /dev/dsp
BTW: I got it working that same day by going with udev. I posted that to the group here. Hopefully my instructions got the other guy that had the same problem up and running :~) -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] No /dev/dsp
Jeremy Huddleston wrote: On Sat, 2005-03-26 at 09:17 +, Sean Sullivan wrote: # Advanced Linux Sound Architecture # CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_HWDEP=y CONFIG_SND_RAWMIDI=y CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_BIT32_EMUL=y You haven't selected any drivers... You just have the base ALSA, AND you've selected to compile it in rather than modularly. Please read through the Gentoo ALSA Handbook. It's recommended to use the media-sound/alsa-driver package rather than the in-kernel ones. --Jeremy Sorry, I left that section out. I assumed everyone would know since I had sound for everything except games... Ooops -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Upgrading from 2004.3 to 2005.0
The script isn't too smart. Anyway, it looks like in this case, your libsandbox.so is missing. The solution is to find the libsandbox.so and copy it to your /lib32 directory, and continue your merry way. Things to try: 1. If your system is already multilib: emerge portage # portage should build a 32bit libsandbox.so for you 2. Do an emerge --sync and then emerge: emul-linux-x86-glibc You should find a libsandbox.so in there. 3. Otherwise, there is definitely a 32bit libsandbox.so in a 2004.3 Stage 3 tarball, so go and extract the stage 3 tarball somewhere and copy that libsandbox into your /lib32 4. Do the upgrade by hand, but put multilib in your make.conf, the instructions tells u at one point to: USE="-sandbox" emerge glibc or gcc # can't remember which ... 5. Get someone to send u a 32bit libsandbox from their amd64 machine. On 29/03/2005, at 8:32 PM, Jason White wrote: Hello, I followed the 2005.0 upgrade guide and decided to use the Makefile-profile_update-2005.0 method. The makefile executed properly until it reached the following line: cp /emul/linux/x86/lib32/libsandbox.so /lib32 (no such file or directory) I have the full output available and can determine the versions of installed packages as required. I also noticed that after the (still incomplete) upgrade, alsa sound drivers are no longer loaded correctly; /etc/init.d/alsasound produces a "unable to load necessary drivers" error, but without any more specific indication of the cause. I've checked the configuration files I recently updated with dispatch-conf but can't find the cause. Suggestions on any of the above would be most welcome. I would like to start by fixing the profile update, then work on the alsa problem. -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Upgrading from 2004.3 to 2005.0
Sorry - fixed the Alsa problem, which turned out to be an error in /etc/modules.d/alsa after all. I still have the profile update to fix. -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Upgrading from 2004.3 to 2005.0
Hello, I followed the 2005.0 upgrade guide and decided to use the Makefile-profile_update-2005.0 method. The makefile executed properly until it reached the following line: cp /emul/linux/x86/lib32/libsandbox.so /lib32 (no such file or directory) I have the full output available and can determine the versions of installed packages as required. I also noticed that after the (still incomplete) upgrade, alsa sound drivers are no longer loaded correctly; /etc/init.d/alsasound produces a "unable to load necessary drivers" error, but without any more specific indication of the cause. I've checked the configuration files I recently updated with dispatch-conf but can't find the cause. Suggestions on any of the above would be most welcome. I would like to start by fixing the profile update, then work on the alsa problem. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] No /dev/dsp
On Sat, 2005-03-26 at 09:17 +, Sean Sullivan wrote: > # Advanced Linux Sound Architecture > # > CONFIG_SND=y > CONFIG_SND_TIMER=y > CONFIG_SND_PCM=y > CONFIG_SND_HWDEP=y > CONFIG_SND_RAWMIDI=y > CONFIG_SND_OSSEMUL=y > CONFIG_SND_MIXER_OSS=y > CONFIG_SND_PCM_OSS=y > CONFIG_SND_BIT32_EMUL=y You haven't selected any drivers... You just have the base ALSA, AND you've selected to compile it in rather than modularly. Please read through the Gentoo ALSA Handbook. It's recommended to use the media-sound/alsa-driver package rather than the in-kernel ones. --Jeremy signature.asc Description: This is a digitally signed message part
Re: [gentoo-amd64] Error: sudo emerge --update --deep --newuse world
me wrote: > Well, since nobody else has chimed in yet... > I don't post often, 'cuz most of this is over my head, but... I had a problem > emerging GCC recently as well, and the answer I got from the web forums, was > it's a bug. I had to do a stage3 install, because I couldn't emerge GCC on > AMD64. I also attempted a --newuse after getting it running, that b0rked at > GCC. Might be able to find more info on bugs.gentoo.org? > Sorry I can't be of more help (but I'm learning!). > Hi, which profile are you using ? If 2005.0, follow the guide. A lot of people had issues with linux-headers and glibc trying to switch from 2004.3 to 2005.0. If 2004.3, did you try to re-emerge linux-headers and then glibc ? Tip 1 : If you know you will not use linux-threads but only nptl, add nptlonly to your use flags too. Tip 2 : post the output of emerge info, it will be easier for people here to help you. -- gentoo-amd64@gentoo.org mailing list
