Re: vmware and linuxthreads
>> >> Currently running natively under debian amd64 gcc-3.4. That is the >> only reason I don't boot into 32 bit anymore. It can be done, and >> works well. >Really? I only though you were using a chroot because you said so >yourself only a month ago: Well don't exactly remember what I posted but never could get vmware to work in chroot because of module problems. Don't remember the details, but someone posted here that it worked under amd64 (original post is below that I used to setup vmware) and I finally lucked out one day. Below is my /etc/ld.so.conf /emul/ia32-linux/lib /emul/ia32-linux/usr/lib /emul/ia32-linux/usr/X11R6/lib /ia32/lib /ia32/usr/lib /ia32/usr/X11R6/lib /ia32/usr/local/lib I had to place the /emul first in order for the normal upgrading of /emul directory to occur. If the /ia32 directory was first it would not work. >in a chroot and making sure they appear in /etc/ld.so.conf before the >ia32-libs versions of the same libraries. So far this has allowed me to >install Windows XP in vmware. Not sure if it's a good long-term >solution, and if Debian/ia32 every switches to NPTL I'll be up a >creek. I was able to install and run win200 and winxp sp2. win2000 was unstable, so currently using winxp sp2. >APK, what's the output of ldd /usr/local/lib/vmware/bin/vmware? Here's >mine: >linux-gate.so.1 => (0x) >libdl.so.2 => /var/chroot/sid-ia32/lib/tls/libdl.so.2 (0x55583000) >libm.so.6 => /var/chroot/sid-ia32/lib/tls/libm.so.6 (0x55586000) >libX11.so.6 => /emul/ia32-linux/usr/X11R6/lib/libX11.so.6 (0x555aa000) >libXext.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXext.so.6 > (0x55671000) >libXi.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXi.so.6 (0x5567f000) >libgdk_pixbuf.so.2 => not found >libglib-1.2.so.0 => /emul/ia32-linux/usr/lib/libglib-1.2.so.0 > (0x55687000) >libgmodule-1.2.so.0 => /emul/ia32-linux/usr/lib/libgmodule-1.2.so.0 > (0x556a8000) >libgdk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgdk-1.2.so.0 > (0x556ac000) >libgtk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgtk-1.2.so.0 > (0x556e4000) >libpthread.so.0 => /var/chroot/sid-ia32/lib/tls/libpthread.so.0 > (0x5582c000) >libc.so.6 => /var/chroot/sid-ia32/lib/tls/libc.so.6 (0x5583b000) >/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x5000) Here is mine: ldd /usr/local/lib/vmware/bin/vmware linux-gate.so.1 => (0x) libdl.so.2 => /ia32/lib/tls/libdl.so.2 (0x55587000) libm.so.6 => /ia32/lib/tls/libm.so.6 (0x5558b000) libX11.so.6 => /emul/ia32-linux/usr/X11R6/lib/libX11.so.6 (0x555ae000) libXext.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXext.so.6 (0x55675000) libXi.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXi.so.6 (0x55683000) libgdk_pixbuf.so.2 => /emul/ia32-linux/usr/lib/libgdk_pixbuf.so.2 (0x5568b000) libglib-1.2.so.0 => /emul/ia32-linux/usr/lib/libglib-1.2.so.0 (0x556a) libgmodule-1.2.so.0 => /emul/ia32-linux/usr/lib/libgmodule-1.2.so.0 (0x556c2000) libgdk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgdk-1.2.so.0 (0x556c5000) libgtk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgtk-1.2.so.0 (0x556fd000) libpthread.so.0 => /ia32/lib/tls/libpthread.so.0 (0x55845000) libc.so.6 => /ia32/lib/tls/libc.so.6 (0x55854000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x5000) *** So it is using the pthread library. I found the original message from this list that I used to setup my system with vmware. I hope the original author does not mind me reposting. * Start message ** Lennart Sorensen wrote: >On Sun, Oct 31, 2004 at 10:38:52AM -0800, David Liontooth wrote: > > >>Thanks, Len -- I didn't realize the upgrade was free, so that's very >>useful. >>It turns out the problem can't have been vmware after all, however, as the >>same thing happened when I wasn't using it. I reverted the most recent >>change, which was upgrading the hotplug package, and it hasn't happened >>again, but this is not a diagnosis. >> >>I'll upgrade VMware anyway -- if I can run it on the amd64, that would >>be very cool -- >>but it would mean running a 32-bit app within a pure64 environment. My >>guess is >>that VMware 4.5 won't run in our pure64 Debian -- is that correct? >> >> > >Hmm, no idea I haven't tried vmware on 64bit myself, I just read about >some kernel patches/driver patches for vmware related to amd64 support. >I have found 4.5 much better than 4.0 for some things, so it's worth >downloading the new one. VMware seems to always consider any point >releases to be free upgrades. > >I suspect if/when they release a version with full 64bit support (both >host and guest), it will be version 5.x and require an upgrade. :) > >Len Sorensen > > > > Well, good news on that front -- vmware 4.5.2
Re: MySQL on debian amd64
Hi Bob, (B (Byou are right. That wasnt very clever. I start a new topic. Ignore my entry. (B (BBest regards (B (BNils Valentin (B (B> Nils Valentin wrote: (B>> Today I installed and configured MySQL (its not the first time I am (B>> doing this so I am a bit puzzled). (B> (B> I am also puzzled. You replied to a thread where were were discussing (B> the merits of installing software in chroots. (B> (B>> 1) I am unable to set the default-character-set in /etc/my.cnf. (B> (B> Are you installing MySQL in a chroot and having a problem with it? If (B> so could you restate your problem? Because I am at a completely loss (B> to understand in what way you are having chroot problems. (B> (B>> 2)How would I know the full .deb package name (including version number) (B>> containing the mysql server files. Using "dpkg --list mysql-server" just (B>> gives me the version number? (B>> (B>> I am actually looking foran equivalent to "rpm -qi "
Re: vmware problem
OK, I'am downing an pure64 install iso ,then I'll take a try
Re: boot problems with upgrading udev
On Thu, 2004-12-02 at 16:29 -0800, kristian kvilekval wrote: > I just did a normal upgrade and ran into a whole > lot of problems after doing the suggested "reboot". > > The problem where manifested while trying to load > the "usb" devices. The boot process stops and > will not continue until ^C or sometimes fails > completely and requires resetting the system. > > Checking the BTS, it seems the /etc/udev/rules.d > gets an incorrect symlink if the package hal is also > loaded. This should really be documented somewhere > or probably in the package documentation. > I found that cleaning out /etc/udev/rules.d > and then linking >ln -s /etc/udev/udev.rules /etc/udev/rules.d/ > did the trick for most problems, yet I still have > some boot failures (again while loading usb). > > Previously loaded drivers such as network and video > drivers also failed to load automatically. These > had to be added to the /etc/modules before the system > would boot properly. > > Has anybody else run into this also? My system > still fails to come up cleanly. Currently I have > to boot into recovery mode and then exit from that > in order to get X to run correctly. Not exactly > sure why this would matter, but it does. That's interesting. I just did a big Sid upgrade, and installed hal. The symlink exists. # dir /etc/udev/rules.d total 12 drwxr-xr-x 2 root root 4096 2004-11-30 15:07 . drwxr-xr-x 5 root root 4096 2004-12-02 06:48 .. -rw-r--r-- 1 root root 164 2004-11-29 03:43 10-local.rules lrwxrwxrwx 1 root root 13 2004-11-15 17:54 udev.rules -> ../udev.rules lrwxrwxrwx 1 root root 12 2004-11-30 15:07 z_hal-plugdev.rules -> ../hal.rules udev 0.046-4 hal 0.4.1-2 -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. "I personally think we developed language because of our deep need to complain." Lily Tomlin signature.asc Description: This is a digitally signed message part
Re: MySQL on debian amd64
Nils Valentin wrote: > Today I installed and configured MySQL (its not the first time I am > doing this so I am a bit puzzled). I am also puzzled. You replied to a thread where were were discussing the merits of installing software in chroots. > 1) I am unable to set the default-character-set in /etc/my.cnf. Are you installing MySQL in a chroot and having a problem with it? If so could you restate your problem? Because I am at a completely loss to understand in what way you are having chroot problems. > 2)How would I know the full .deb package name (including version number) > containing the mysql server files. Using "dpkg --list mysql-server" just > gives me the version number? > > I am actually looking foran equivalent to "rpm -qi ". 'rpm -qi packagename.rpm' won't work. -p on files. Without -p on installed names of things. So that would be: rpm -qpi packagename.rpm dpkg --info packagename.deb To query installed packages by name. rpm -qi packagename dpkg --status packagename Bob > Any reply would be much appreciated. > > Best regards > > Nils Valentin > > > On Tuesday 30 November 2004 02:47, Goswin von Brederlow wrote: > > [EMAIL PROTECTED] (Bob Proulx) writes: > > > Phil Warrick wrote: > > >> I'm going with the chroot approach then. > > >> > > >> Following the AMD64 HOWTO in section "Running applications inside the > > >> chroot", I followed the instructions and then I wanted to try to run a > > >> 32-bit program. > > >> > > >> First I wanted to try to run some X-based program so I tried openoffice, > > >> which was not yet installed. When I tried to install it in the chroot, > > >> I got the following errors below. > > >> [...] > > >> Can someone indicate what might be wrong? I'm using kernel > > >> 2.6.8-9-amd-k8-smp on a dual Opteron system. > > > > > > Check your /etc/apt/sources.list file *in the chroot* and make sure it > > > can get to the 32-bit archive. Make sure that 'apt-get update' works > > > in the chroot. It looks to me like apt has no package lists at all. > > > > > > If you have 'dchroot' configured you can run the commands like this: > > > > > > dchroot editor /etc/apt/sources.list > > > > > > dchroot apt-get update > > > dchroot apt-get install openoffice.org > > > > > > Bob > > > > Don't forget /etc/hosts, /etc/passwd, /etc/groups, /etc/shadow, > > /etc/mtab, /proc in the chroot. > > > > MfG > > Goswin > > -- > kind regards > > Nils Valentin > Tokyo/Japan > > http://www.be-known-online.com/mysql/ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > signature.asc Description: Digital signature
Re: vmware problem
On Fri, 2004-12-03 at 09:34 +0800, [EMAIL PROTECTED] wrote: > I remove the gcc-3.3 and install gcc-3.4,gcc-3.4-base with synaptic > ,but i don't remove gcc-3.3-base because if i remove it ,many other > pakages will be removed ,like apt... >From these errors, it looks like you are either running a 32-bit kernel, or your are trying to compile 32-bit modules. Are you trying to install vmware from within the chroot? That won't work. You need to install it from your normal 64-bit root, under a running 64-bit kernel. -jwb
Re: vmware problem
I remove the gcc-3.3 and install gcc-3.4,gcc-3.4-base with synaptic ,but i don't remove gcc-3.3-base because if i remove it ,many other pakages will be removed ,like apt... then I "ln -s gcc-3.4 gcc",and run "runme.pl",the results is: -- Building the vmmon module. Building for VMware GSX Server 3.1.0 or VMware Workstation 4.5.2. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config11/vmmon-only' make -C /lib/modules/2.6.8-9-amd64-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' CC [M] /tmp/vmware-config11/vmmon-only/linux/driver.o /tmp/vmware-config11/vmmon-only/linux/driver.c:1: error: code model `kernel' not supported in the 32 bit mode make[2]: *** [/tmp/vmware-config11/vmmon-only/linux/driver.o] éè 1 make[1]: *** [_module_/tmp/vmware-config11/vmmon-only] éè 2 make[1]: Leaving directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' make: *** [vmmon.ko] éè 2 make: Leaving directory `/tmp/vmware-config11/vmmon-only' Unable to build the vmmon module.
Re: boot problems with upgrading udev
Hi Kris, I have similar display problems after running aptitude dist-upgrade this morning. I got the message that after upgrading udev some things were broken and to reboot ASAP. Upon rebooting, the machine would not boot into graphic mode. /var/log/messages winds up with xprint related error messages. The last line in dmesg is Xprt[4500] trap invalid operand rip:4063ee rsp:7fb338 error:0 (I am on another machine now.) If I do pan64:~# gdm gdm already running. Aborting! pan64:~# I tried dpkg-reconfigure xserver-xfree86 but that did not help. I just made the changes in /etc/udev you mentioned and rebooted. The display still does not start. The Xfree86 Dialog box says XFree86 Version 4.3.0.1 and then down below "Module Loader present" and then another box says I will disable this X server for now. Restart GDM when it is configured correctly. I can't see nv or any video modules that I recognise in lsmod. /etc/modules just lists ide-cd ide-generic sd_mod Hope this helps Norv
Re: vmware and linuxthreads
On Thu, 2004-12-02 at 18:49 -0600, A. P. Kennedy wrote: > > "Jeffrey" == Jeffrey W Baker <[EMAIL PROTECTED]> writes: > > Jeffrey> On Wed, 2004-12-01 at 22:38 -0600, A. P. Kennedy wrote: > >> Wow, who said that. Anyway I'm using vmware just fine on AMD64. > >> Take a look a the mail archive for details. This has been > >> discussed in detail. The trick is gettting, and installing the > >> vmware-any-any-update. Make sure you use the latest version. Note > >> some strange error comes up when starting vmware just restart the > >> VM session and it works fine. > > Jeffrey> It seems you are running vmware under the 32-bit chroot. Is > Jeffrey> that correct? I'm trying to run it natively. > > Currently running natively under debian amd64 gcc-3.4. That is the > only reason I don't boot into 32 bit anymore. It can be done, and > works well. Really? I only though you were using a chroot because you said so yourself only a month ago: On Thu, 2004-11-04 18:03:35 -0600, A. P. Kennedy <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>: > kernel is 2.6.8.1 and all needed debs to support vmware are > installed in my chroot directory, and the correct lib directories are > placed in /etc/ld.so.conf So i guess you aren't really in the chroot, but you're using the libs installed there. Is that right? I have temporarily fixed my problem by installing the 32-bit libraries in a chroot and making sure they appear in /etc/ld.so.conf before the ia32-libs versions of the same libraries. So far this has allowed me to install Windows XP in vmware. Not sure if it's a good long-term solution, and if Debian/ia32 every switches to NPTL I'll be up a creek. APK, what's the output of ldd /usr/local/lib/vmware/bin/vmware? Here's mine: linux-gate.so.1 => (0x) libdl.so.2 => /var/chroot/sid-ia32/lib/tls/libdl.so.2 (0x55583000) libm.so.6 => /var/chroot/sid-ia32/lib/tls/libm.so.6 (0x55586000) libX11.so.6 => /emul/ia32-linux/usr/X11R6/lib/libX11.so.6 (0x555aa000) libXext.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXext.so.6 (0x55671000) libXi.so.6 => /emul/ia32-linux/usr/X11R6/lib/libXi.so.6 (0x5567f000) libgdk_pixbuf.so.2 => not found libglib-1.2.so.0 => /emul/ia32-linux/usr/lib/libglib-1.2.so.0 (0x55687000) libgmodule-1.2.so.0 => /emul/ia32-linux/usr/lib/libgmodule-1.2.so.0 (0x556a8000) libgdk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgdk-1.2.so.0 (0x556ac000) libgtk-1.2.so.0 => /emul/ia32-linux/usr/lib/libgtk-1.2.so.0 (0x556e4000) libpthread.so.0 => /var/chroot/sid-ia32/lib/tls/libpthread.so.0 (0x5582c000) libc.so.6 => /var/chroot/sid-ia32/lib/tls/libc.so.6 (0x5583b000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x5000) -jwb
Re: vmware problem
> "Jeffrey" == Jeffrey W Baker <[EMAIL PROTECTED]> writes: Jeffrey> The trick to compiling these vendor modules is to install Jeffrey> kernel-tree-2.6.9 or whatever the corresponding package is Jeffrey> for your kernel. After that's installed you will be able to Jeffrey> compile nvidia, vmware, and other 3rd-party kernel modules. Pretty much having a complete kernel tree installed, and compiled. Jeffrey> But you still won't be able to run vmware, on account of Jeffrey> nptl. I'm totally confused why VMWare s running fine here and others have it running also under debian amd64. Is VMWare using the 32 bit libraries in the /emul directory? Well I not sure how this all works and what libraries and being used, but I do not run VMWare under a 32 bit chroot. It runs fine here under debian amd64. Actually I could not even get VMWare running in a 32 bit chroot. That is why I followed the instructions posted in this maillist on how to setup VMWare under debian amd64. Check out the mail archives for details. Good luck, Alan
Re: vmware and linuxthreads
> "Jeffrey" == Jeffrey W Baker <[EMAIL PROTECTED]> writes: Jeffrey> On Wed, 2004-12-01 at 22:38 -0600, A. P. Kennedy wrote: >> Wow, who said that. Anyway I'm using vmware just fine on AMD64. >> Take a look a the mail archive for details. This has been >> discussed in detail. The trick is gettting, and installing the >> vmware-any-any-update. Make sure you use the latest version. Note >> some strange error comes up when starting vmware just restart the >> VM session and it works fine. Jeffrey> It seems you are running vmware under the 32-bit chroot. Is Jeffrey> that correct? I'm trying to run it natively. Currently running natively under debian amd64 gcc-3.4. That is the only reason I don't boot into 32 bit anymore. It can be done, and works well. Good luck, Alan
boot problems with upgrading udev
I just did a normal upgrade and ran into a whole lot of problems after doing the suggested "reboot". The problem where manifested while trying to load the "usb" devices. The boot process stops and will not continue until ^C or sometimes fails completely and requires resetting the system. Checking the BTS, it seems the /etc/udev/rules.d gets an incorrect symlink if the package hal is also loaded. This should really be documented somewhere or probably in the package documentation. I found that cleaning out /etc/udev/rules.d and then linking ln -s /etc/udev/udev.rules /etc/udev/rules.d/ did the trick for most problems, yet I still have some boot failures (again while loading usb). Previously loaded drivers such as network and video drivers also failed to load automatically. These had to be added to the /etc/modules before the system would boot properly. Has anybody else run into this also? My system still fails to come up cleanly. Currently I have to boot into recovery mode and then exit from that in order to get X to run correctly. Not exactly sure why this would matter, but it does.
Re: AMD64 VS EM64T
Just found out this excellent article about server performance: http://www.samag.com/documents/s=9408/sam0411b/0411b.htm This is the best I read so far and I highly recommend it to everybody considering 64 bit. However, it is still purely from a hardware view. Does anybody knows any reviews from OS softwares, esp Linux? Which platform linux works better with, AMD64 or EM64T? Thanks, Jin Paolo Alexis Falcone wrote: On Thu, 02 Dec 2004 15:41:10 -0600, Jin Zhao <[EMAIL PROTECTED]> wrote: I am currently faced with choosing one of them as our forthcoming 64 bit platform. So far I read a couple of reviews, most of which seems favor AMD64 a little bit. I also did some initial testings on an opteron box with Debian pure64 unstale. So far it looks good. The price differrence is not a big issue. The most important are performance, reliability and compatibility, esp on Linux, most likely Debian. We will use them to run server side java applicaitons. Redhat mentioned this in their realease statement: "Software IOTLB â Intel EM64T does not support an IOMMU in hardware while AMD64 processors do. This means that physical addresses above 4GB (32 bits) cannot reliably be the source or destination of DMA operations. Therefore, the Red Hat Enterprise Linux 3 Update 2 kernel "bounces" all DMA operations to or from physical addresses above 4GB to buffers that the kernel pre-allocated below 4GB at boot time. This is likely to result in lower performance for IO-intensive workloads for Intel EM64T as compared to AMD64 processors." This issue may affect database usage, but probably not a java applicaiton server. There might be other unkown issues as well. I am eager to know what are the Debian team and users' point on these two platforms, esp those who already used them. AMD's original implementation of their AMD64 architecture is gauged as superior engineering-wise by many hardware reviewers. The Intel implementation still suffers from bandwidth starvation as the same bus architecture as of old is still being used. This causes problems when you get more processors and memory, which the AMD implementation solves by making each processor have its own set of memory and resources.
Re: MythTV
Don Montgomery wrote: Dave, I would be very interested to hear any info you have found about HDTV cards that work (or not) under amd64. Thanks, Don Don, it'll take a while -- I looked at the drivers and the 2.6 kernel drivers are built for FedoraCore2 (32-bit version), so we're going to start out with that, and then experiment in a Debian pure 64 chroot. Gentoo people have the driver working for amd64, so I don't think there are any real problems. (I need someone else to handle the project, so I'm recommending an optimal entry point.) Dave On Sun, 28 Nov 2004, David Liontooth wrote: Date: Sun, 28 Nov 2004 21:13:14 -0800 From: David Liontooth <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Subject: MythTV Resent-Date: Sun, 28 Nov 2004 23:13:23 -0600 (CST) Resent-From: debian-amd64@lists.debian.org MythTV compiles on amd64 using the following procedure: * get liblame0 and liblame0-dev from http://debian.freenux.org/debian-marillat-amd64/ * add this to /etc/apt/sources.list and run update: deb-src http://dijkstra.csh.rit.edu/~mdz/debian unstable mythtv * wajig source mythtv * cd mythtv-0.16 * vi debian/control -- add this to dependencies, after liblame-dev: | liblame0-dev * apt-get install libqt3-mt-dev libmysqlclient-dev liblircclient-dev libartsc0-dev (this will also install mysql-common) * fakeroot dpkg-buildpackage I'm doing this just to test the build, to help me decide whether to advice somone else to buy and amd64 for a capture project, so I've not installed it. I've already tested that a bttv capture card works. The second decision is the pcHDTV capture card, which seems to be getting mixed reviews under amd64. Cheers, Dave
Re: sound inside the chroot
> Alexandru> the sound device, whatever that is... I'll try mounting > Alexandru> the /dev also see if that helps. Yes, it does. Success! It should be added to the faq that you need to mount /dev too. Alex.
Re: AMD64 VS EM64T
On Thu, 02 Dec 2004 15:41:10 -0600, Jin Zhao <[EMAIL PROTECTED]> wrote: > I am currently faced with choosing one of them as our forthcoming 64 bit > platform. So far I read a couple of reviews, most of which seems favor > AMD64 a little bit. I also did some initial testings on an opteron box > with Debian pure64 unstale. So far it looks good. > > The price differrence is not a big issue. The most important are > performance, reliability and compatibility, esp on Linux, most likely > Debian. We will use them to run server side java applicaitons. > > Redhat mentioned this in their realease statement: > "Software IOTLB â Intel EM64T does not support an IOMMU in hardware > while AMD64 processors do. This means that physical addresses above 4GB > (32 bits) cannot reliably be the source or destination of DMA > operations. Therefore, the Red Hat Enterprise Linux 3 Update 2 kernel > "bounces" all DMA operations to or from physical addresses above 4GB to > buffers that the kernel pre-allocated below 4GB at boot time. This is > likely to result in lower performance for IO-intensive workloads for > Intel EM64T as compared to AMD64 processors." > > This issue may affect database usage, but probably not a java > applicaiton server. There might be other unkown issues as well. I am > eager to know what are the Debian team and users' point on these two > platforms, esp those who already used them. AMD's original implementation of their AMD64 architecture is gauged as superior engineering-wise by many hardware reviewers. The Intel implementation still suffers from bandwidth starvation as the same bus architecture as of old is still being used. This causes problems when you get more processors and memory, which the AMD implementation solves by making each processor have its own set of memory and resources. -- Paolo Alexis Falcone [EMAIL PROTECTED]
AMD64 VS EM64T
I am currently faced with choosing one of them as our forthcoming 64 bit platform. So far I read a couple of reviews, most of which seems favor AMD64 a little bit. I also did some initial testings on an opteron box with Debian pure64 unstale. So far it looks good. The price differrence is not a big issue. The most important are performance, reliability and compatibility, esp on Linux, most likely Debian. We will use them to run server side java applicaitons. Redhat mentioned this in their realease statement: “Software IOTLB — Intel EM64T does not support an IOMMU in hardware while AMD64 processors do. This means that physical addresses above 4GB (32 bits) cannot reliably be the source or destination of DMA operations. Therefore, the Red Hat Enterprise Linux 3 Update 2 kernel "bounces" all DMA operations to or from physical addresses above 4GB to buffers that the kernel pre-allocated below 4GB at boot time. This is likely to result in lower performance for IO-intensive workloads for Intel EM64T as compared to AMD64 processors.” This issue may affect database usage, but probably not a java applicaiton server. There might be other unkown issues as well. I am eager to know what are the Debian team and users' point on these two platforms, esp those who already used them. Thanks, Jin
Re: Bug#283595: SOLVED: Dual SATA controllers on GA-K8NS Pro
> Should I file a new install report on this successful install? As this is the very same machine, I don't think it's needed. Now we can close the bug report after this successful install.
Re: SOLVED: Dual SATA controllers on GA-K8NS Pro
On Thu, 2004-12-02 at 06:36 +0100, Christian Perrier wrote: > Hmmm, you should have kept the original bug number of your install > report in copy. Doing so, and keeping your whole answer. Sorry for breaking the thread, I am more used to forums than lists... > > > Quoting Norval Watson ([EMAIL PROTECTED]): > > The Gigabyte GA-K8NS Pro motherboard has four points you can plug a SATA > > drive cable. > > They are SATA0_SB and SATA1_SB, both controlled by the onboard nVIDIA > > nForce3 250 chipset. I tried one of these and had no luck with 2.6 > > kernel, sarge i386 or sid-amd64, detecting my Seagate ST380013AS SATA > > drive. > > Then there are SATA0_SII and SATA1_SII, both controlled by the built-in > > Silicon Image Sil3512 chipset. I swapped the cable into SATA0_SII socket > > and rebooted. Straight away the drive was detected: > > scsi3 : sata_sil > > Vendor: ATA Model: ST380013ASRev: 3.18 > > Type: Direct-Access ANSI SCSI revision: 05 > > SCSI device sda: 156299375 512-byte hdwr sectors (80025 MB) > > SCSI device sda: drive cache: write back > > /dev/scsi/host2/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 > > > Attached scsi disk sda at scsi2, channel 0, id 0, lun 0 > > > > I am able to mount the drive. > > > > > > Have you tried "modprobe sata_sil" in console 2 when you're notified > > > > the no hard disk found ? > > > > > > Thanks Christian. Sata_sil module was loading, as was sata_nv, I also > > saw something to do with nv_sata in dmesg.. > > > > > One more thing. There is no need to reinstall your system again (apart > > > from testing if it works). You can go into single user mode and copy > > > (tar | tar or rsync or whatever you prefer) the old system to the new > > > disk, change the bootloader config and mkinitrd config, run mkinitrd > > > and (for lilo) reinstall the bootloader by chrooting to the new disk. > > Thanks Goswin. Does 'single user mode' mean become root? I will have to > > look for a tutorial coz I am almost out of my depth here. > > First up I will copy the boot disk (2GB ATA) to the new SATA disk. I am > > using GRUB. > > Thanks again, > > > However, we still need to know whether the installer automatically > detects your SATA drive with your new hardware layout. Can you at > least try to boot again the installer CD and go up to the disk > partitioning step? > > This is non destructive as the only need is knowing whether the > installer detects a disk or not. I just did a fresh install of sid-amd64-netinst.iso on the SATA disk and it worked well. I had to disconnect the ATA drive as the install wanted to put the MBR on that drive even when I set it to write to the SATA drive. That was the only glitch. When the base-system was installed I reconnected the ATA drive and used that as my apt repository. I had already used dpkg-scanpackages (from dpkg-dev) to make Packages.gz in (old ATA)/var/cache/apt/archives. My sources list: pan64:~# more /etc/apt/sources.list #deb file:///cdrom/ sarge main deb file:/mnt/hda/var/cache/apt archives/ I ran aptitude dist-upgrade which updated the base system and installed the new 2.6.9 kernel Then I ran aptitude install x-window-system gdm gnome-desktop which installed a working desktop. Then aptitude install mozilla-firefox evolution gimp totem , and a few other packages I use. A quick check shows that browser and mail prog work, I can play CDs and DVDs. Should I file a new install report on this successful install? Thanks, Norv > > > >
Re: Re: Re: "GRUB loading" problem with AMD64 install
Just an interesting follow-up: I replaced my Western Digital 80GB hard drive for 2 Seagate 80GB hard drives, and no longer is LBA or no LBA an issue... Everything works properly, no matter how I try to break it... I have no idea why this is fixed now... I am using the same hardware and the same OS... I can only assume that something on that Western Digital hard drive was not programmed properly... Mike (Xyzzy)
Re: vmware and linuxthreads
On Wed, 2004-12-01 at 22:38 -0600, A. P. Kennedy wrote: > Wow, who said that. Anyway I'm using vmware just fine on AMD64. Take a > look a the mail archive for details. This has been discussed in > detail. The trick is gettting, and installing the > vmware-any-any-update. Make sure you use the latest version. Note some > strange error comes up when starting vmware just restart the VM > session and it works fine. It seems you are running vmware under the 32-bit chroot. Is that correct? I'm trying to run it natively. -jwb
Re: vmware problem
On Thu, 2004-12-02 at 08:45 -0600, A. P. Kennedy wrote: > > "vm" == <[EMAIL PROTECTED]> writes: > > vm> Hi, I just installed kernel-image-2.6.8-9-amd64-k8 and > vm> kernel-headers-2.6.8-9-amd64-k8 from Debian/unstable. I also have > vm> gcc 2.95.4 installed and made sure my /usr/bin/gcc was pointing > vm> to gcc-2.95.4 (and the same for g++). > > vm> and I download the vmware-any-any-update84.tar.gz > > vm> then I run the runme.pl in the vmware-any-any-update84 > > > Use gcc-3.4, and you need to compile a complete kernel and modules. > Make sure the new kernel is installed correctly and working. Then > run "runme.pl". I have never tried to compile kernel modules for > a packaged kernel, but suspect this will not work. It should work fine > then. Since I compile the kernel anyway this has never been an issue > for me. So the question is can one compile a kernel module without > actually having compiled the kernel? I don't know the answer to this > question. The trick to compiling these vendor modules is to install kernel-tree-2.6.9 or whatever the corresponding package is for your kernel. After that's installed you will be able to compile nvidia, vmware, and other 3rd-party kernel modules. But you still won't be able to run vmware, on account of nptl. -jwb
openssh bad?
Has anyone else been having segfaulting issues with recent openssh packages in the gcc-3.4 repository? Kyle
Re: Making my desicion between 64bits and 32bits.
> "icamargo" == icamargo <[EMAIL PROTECTED]> writes: icamargo> Hi! So, I have just this question: What would be good on a icamargo> 64bits system over a 32bits one? Ok, I got a Athlon 64 icamargo> (finally), but now I'm just asking myself: Will the time an icamargo> effort of installing a 64bits system serve of anything else icamargo> than telling my friends that I have one?, please note that icamargo> I use this computer as my desktop computer, so I will run icamargo> there: openoffice.org, firefox with plugins (specially icamargo> flash), doom3 (wich somebody told me that will run in icamargo> pure64 without problems), and 32bits versions of: mplayer icamargo> and maybe transcode (if it happends to be slower in the icamargo> 64bits native system). Probably won't make any difference. Besides the fact I don't play doom my requirements are very similiar. I guess the reason I went 64 bits is because I have used alphas for years and this was a natural transition. Looks like the alpha line is dead. The second reason is that it can be done, and that was good enough for me. However, for the average desktop user 64 bit does not give much. I run 32 bit and 64 bit debian and it feels about the same. I have come to the point where I don't even boot into the 32 bit anymore. VMware was the only thing holding me back and that is running well under amd64 now. Yes, I have to use windows in order to login on the work vpn and work has a stupid windows client. icamargo> My guess is that the 64bits binaries (besides being icamargo> larger), should be faster (at least a little faster), is icamargo> this true? I have read about other programs (mplayer, icamargo> transcode) that run slower, due to problems with the icamargo> optimizations (mmx, sse, 3dnow) not working. This is very true, and you hit the nail on the head. Just because it is compiled 64 bits does not mean it is faster. Still needs to be optimized. The more folks start using 64 bit stuff the sooner this will happen. Go 64 bit and ask questions later. My 2 cents I think this port is stable enough to use in production environment, but I personally would not do that until sarge is released offically. That is my opinion. Later, Alan
Re: non-install report
> "Hank" == Hank Barta <[EMAIL PROTECTED]> writes: Hank> I'm testing now with APIC off. But I'm confused a bit by how to Hank> do this. In varrious places I see 'apic=off' or 'noapic' and Hank> 'nolapic' as it is recommended in the Ubuntu boot help for Via Hank> chip sets. The best way to turn it off is in the kernel configuration options. That is if you are compiling a kernel. Otherwise read the documentation that explains all of this in detail. It is in the linux kernel source tree. /usr/src/linux/Documentation/x86_64/boot-options.txt is the correct file. I have had real problems with apic with strange lockups. apci seems more stable in 2.6.10-rc[12] releases. Good luck, Alan
Re: sound inside the chroot
I had to mount /dev because I use udev and my /dev directory in chroot was almost empty, and had no sound information (/dev/dsp, /dev/snd, /dev/mixer, etc). That is the only way sound worked on my system. If you are using devfs or udev, the /dev directory needs to mounted. I suspect this needs to be changed in the howto. Good luck, Alan > "Alexandru" == Alexandru Cabuz <[EMAIL PROTECTED]> writes: >> Make sure you have /dev, /proc and /sys mounted in the chroot >> directory. According to the howto add /home and /tmp also. Alexandru> The howto does not say anything about /dev. So it should Alexandru> also be mounted in the chroot, huh? Cos the chroot has its Alexandru> own /dev and I thought it should be able to get by on Alexandru> that... For example because I can *watch* DVDs, which Alexandru> means it can find the /dev/hdb and /dev/hda devices, which Alexandru> are my two ide DVD drives. But apparently it can't find Alexandru> the sound device, whatever that is... I'll try mounting Alexandru> the /dev also see if that helps. Alexandru> Thanks. Alexandru> Alex.
Re: vmware problem
> "vm" == <[EMAIL PROTECTED]> writes: vm> Hi, I just installed kernel-image-2.6.8-9-amd64-k8 and vm> kernel-headers-2.6.8-9-amd64-k8 from Debian/unstable. I also have vm> gcc 2.95.4 installed and made sure my /usr/bin/gcc was pointing vm> to gcc-2.95.4 (and the same for g++). vm> and I download the vmware-any-any-update84.tar.gz vm> then I run the runme.pl in the vmware-any-any-update84 Use gcc-3.4, and you need to compile a complete kernel and modules. Make sure the new kernel is installed correctly and working. Then run "runme.pl". I have never tried to compile kernel modules for a packaged kernel, but suspect this will not work. It should work fine then. Since I compile the kernel anyway this has never been an issue for me. So the question is can one compile a kernel module without actually having compiled the kernel? I don't know the answer to this question. Good luck, Alan
Re: sound inside the chroot
On Thu, 2004-12-02 at 10:10 +0100, Alexandru Cabuz wrote: > > Make sure you have /dev, /proc and /sys mounted in the chroot > > directory. According to the howto add /home and /tmp also. > > The howto does not say anything about /dev. So it should also be > mounted in the chroot, huh? Cos the chroot has its own /dev and I > thought it should be able to get by on that... For example because I > can *watch* DVDs, which means it can find the /dev/hdb and /dev/hda > devices, which are my two ide DVD drives. But apparently it can't find > the sound device, whatever that is... I'll try mounting the /dev also > see if that helps. You are correct, so long as the permissions are the same in both /dev. Are you using OSS or ALSA? I suggest using ALSA and making sure the module snd_ioctl32 is loaded. -s signature.asc Description: This is a digitally signed message part
Re: non-install report
Hank Barta <[EMAIL PROTECTED]> writes: > On Wed, 01 Dec 2004 11:52:32 +0100, Goswin von Brederlow >> >> Have any spare parts around? Another cpu, different MB. > > Unfortunately this the only XMD64 hardware I have. I've just ordered a > new LAN card (Intel) to replace the ancient Tulip based card. I should > consider Video too. My concern is that old hardware may not perform > correctly with faster processors. I know design specs say it should, > but if the design is marginal, it may depend on CPU behavior that was > typical with hardware 'back in the day', ;) >> >> >> http://debian-amd64.alioth.debian.org/tools/make-cd.sh > > Thank you. > > ./get-packages ??? Uploaded. >> >> Maybe compile your own 2.8.9 or even more recent kernel? I saw some >> reports about APIC bugs getting patches and maybe you have the same >> problem. > > I'm testing now with APIC off. But I'm confused a bit by how to do > this. In varrious places I see 'apic=off' or 'noapic' and 'nolapic' as > it is recommended in the Ubuntu boot help for Via chip sets. Never had to care about it. > thanks, > hank MfG Goswin
Re: sound inside the chroot
> Make sure you have /dev, /proc and /sys mounted in the chroot > directory. According to the howto add /home and /tmp also. The howto does not say anything about /dev. So it should also be mounted in the chroot, huh? Cos the chroot has its own /dev and I thought it should be able to get by on that... For example because I can *watch* DVDs, which means it can find the /dev/hdb and /dev/hda devices, which are my two ide DVD drives. But apparently it can't find the sound device, whatever that is... I'll try mounting the /dev also see if that helps. Thanks. Alex.
Re: vmware problem
then I try the gcc-3.4.4 and ln -s gcc-3.4 gcc the result is: Updating /usr/bin/vmware ... Unknown version Sorry, there is no binary patch available for your version of /usr/bin/vmware. Updating /usr/bin/vmnet-bridge ... VMware Workstation 4.5.2 (build-8848) or VMware GSX Server 3.1.0 (build-9089), already patched Updating /usr/lib/vmware/bin/vmware-vmx ... VMware GSX Server 3.1.0 (build-9089), already patched Updating /usr/lib/vmware/bin-debug/vmware-vmx ... VMware GSX Server 3.1.0 (build-9089), already patched VMware modules in "/usr/lib/vmware/modules/source" has been updated. Before running VMware for the first time after update, you need to configure it for your running kernel by invoking the following command: "/usr/bin/vmware-config.pl". Do you want this script to invoke the command for you now? [yes] Making sure services for VMware GSX Server are stopped. Stopping VMware services: Virtual machine monitor done Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware GSX Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. As of September 2003, the Linux kernel development team does not support gcc version 3 and later. See Documentation/Changes in your kernel source directory for information on installing the correct compiler. Do you want to use the version "3.4.4" of compiler "/usr/bin/gcc"? [no] yes What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.8-9-amd64-generic/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Building for VMware GSX Server 3.1.0 or VMware Workstation 4.5.2. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config11/vmmon-only' make -C /lib/modules/2.6.8-9-amd64-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' CC [M] /tmp/vmware-config11/vmmon-only/linux/driver.o /tmp/vmware-config11/vmmon-only/linux/driver.c:1: error: code model `kernel' not supported in the 32 bit mode make[2]: *** [/tmp/vmware-config11/vmmon-only/linux/driver.o] éè 1 make[1]: *** [_module_/tmp/vmware-config11/vmmon-only] éè 2 make[1]: Leaving directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' make: *** [vmmon.ko] éè 2 make: Leaving directory `/tmp/vmware-config11/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html"; and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";
Re: vmware problem
sorry the result is: Updating /usr/bin/vmware ... Unknown version Sorry, there is no binary patch available for your version of /usr/bin/vmware. Updating /usr/bin/vmnet-bridge ... VMware Workstation 4.5.2 (build-8848) or VMware GSX Server 3.1.0 (build-9089), already patched Updating /usr/lib/vmware/bin/vmware-vmx ... VMware GSX Server 3.1.0 (build-9089), already patched Updating /usr/lib/vmware/bin-debug/vmware-vmx ... VMware GSX Server 3.1.0 (build-9089), already patched VMware modules in "/usr/lib/vmware/modules/source" has been updated. Before running VMware for the first time after update, you need to configure it for your running kernel by invoking the following command: "/usr/bin/vmware-config.pl". Do you want this script to invoke the command for you now? [yes] Making sure services for VMware GSX Server are stopped. Stopping VMware services: Virtual machine monitor done Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware GSX Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. As of September 2003, the Linux kernel development team does not support gcc version 3 and later. See Documentation/Changes in your kernel source directory for information on installing the correct compiler. Do you want to use the version "3.3.4" of compiler "/usr/bin/gcc"? [no] yes What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.8-9-amd64-generic/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Building for VMware GSX Server 3.1.0 or VMware Workstation 4.5.2. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config5/vmmon-only' make -C /lib/modules/2.6.8-9-amd64-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' CC [M] /tmp/vmware-config5/vmmon-only/linux/driver.o cc1: error: code model `kernel' not supported in the 32 bit mode make[2]: *** [/tmp/vmware-config5/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config5/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config5/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html"; and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";. Execution aborted. __
Re: vmware problem
I just installed gcc 3.3.4 (and the same for g++). then i run the runme.pl here is the result: - Updating /usr/bin/vmware ... Unknown version Sorry, there is no binary patch available for your version of /usr/bin/vmware. Updating /usr/bin/vmnet-bridge ... VMware Workstation 4.5.2 (build-8848) or VMware GSX Server 3.1.0 (build-9089), already patched Updating /usr/lib/vmware/bin/vmware-vmx ... VMware GSX Server 3.1.0 (build-9089), already patched Updating /usr/lib/vmware/bin-debug/vmware-vmx ... VMware GSX Server 3.1.0 (build-9089), already patched VMware modules in "/usr/lib/vmware/modules/source" has been updated. Before running VMware for the first time after update, you need to configure it for your running kernel by invoking the following command: "/usr/bin/vmware-config.pl". Do you want this script to invoke the command for you now? [yes] Making sure services for VMware GSX Server are stopped. Stopping VMware services: Virtual machine monitor done Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware GSX Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. As of September 2003, the Linux kernel development team does not support gcc version 3 and later. See Documentation/Changes in your kernel source directory for information on installing the correct compiler. Do you want to use the version "3.3.4" of compiler "/usr/bin/gcc"? [no] yes What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.8-9-amd64-generic/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Building for VMware GSX Server 3.1.0 or VMware Workstation 4.5.2. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config6/vmmon-only' make -C /lib/modules/2.6.8-9-amd64-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' CC [M] /tmp/vmware-config6/vmmon-only/linux/driver.o cc1: error: code model `kernel' not supported in the 32 bit mode make[2]: *** [/tmp/vmware-config6/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config6/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config6/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html"; and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";. Execution aborted. what can i do? thanks
Re: vmware problem
Hello, On Thu, Dec 02, 2004 at 03:07:07PM +0800, [EMAIL PROTECTED] wrote: > I just installed kernel-image-2.6.8-9-amd64-k8 and > kernel-headers-2.6.8-9-amd64-k8 from Debian/unstable. I also have gcc > 2.95.4 installed and made sure my /usr/bin/gcc was pointing to gcc-2.95.4 (and > the same for g++). You need gcc-3.4 in order to compile additional modules for the amd64 kernel. Greetings Frederik Schueler -- ENOSIG pgpWM3yGR1l3f.pgp Description: PGP signature
Re: SOLVED: Dual SATA controllers on GA-K8NS Pro
Hmmm, you should have kept the original bug number of your install report in copy. Doing so, and keeping your whole answer. Quoting Norval Watson ([EMAIL PROTECTED]): > The Gigabyte GA-K8NS Pro motherboard has four points you can plug a SATA > drive cable. > They are SATA0_SB and SATA1_SB, both controlled by the onboard nVIDIA > nForce3 250 chipset. I tried one of these and had no luck with 2.6 > kernel, sarge i386 or sid-amd64, detecting my Seagate ST380013AS SATA > drive. > Then there are SATA0_SII and SATA1_SII, both controlled by the built-in > Silicon Image Sil3512 chipset. I swapped the cable into SATA0_SII socket > and rebooted. Straight away the drive was detected: > scsi3 : sata_sil > Vendor: ATA Model: ST380013ASRev: 3.18 > Type: Direct-Access ANSI SCSI revision: 05 > SCSI device sda: 156299375 512-byte hdwr sectors (80025 MB) > SCSI device sda: drive cache: write back > /dev/scsi/host2/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 > > Attached scsi disk sda at scsi2, channel 0, id 0, lun 0 > > I am able to mount the drive. > > > > Have you tried "modprobe sata_sil" in console 2 when you're notified > > > the no hard disk found ? > > > > Thanks Christian. Sata_sil module was loading, as was sata_nv, I also > saw something to do with nv_sata in dmesg.. > > > One more thing. There is no need to reinstall your system again (apart > > from testing if it works). You can go into single user mode and copy > > (tar | tar or rsync or whatever you prefer) the old system to the new > > disk, change the bootloader config and mkinitrd config, run mkinitrd > > and (for lilo) reinstall the bootloader by chrooting to the new disk. > Thanks Goswin. Does 'single user mode' mean become root? I will have to look > for a tutorial coz I am almost out of my depth here. > First up I will copy the boot disk (2GB ATA) to the new SATA disk. I am > using GRUB. > Thanks again, However, we still need to know whether the installer automatically detects your SATA drive with your new hardware layout. Can you at least try to boot again the installer CD and go up to the disk partitioning step? This is non destructive as the only need is knowing whether the installer detects a disk or not.
vmware problem
Hi,
I just installed kernel-image-2.6.8-9-amd64-k8 and
kernel-headers-2.6.8-9-amd64-k8 from Debian/unstable. I also have gcc
2.95.4 installed and made sure my /usr/bin/gcc was pointing to gcc-2.95.4 (and
the same for g++).
and I download the vmware-any-any-update84.tar.gz
then I run the runme.pl in the vmware-any-any-update84
--
Extracting the sources of the vmmon module.
Building the vmmon module.
Building for VMware GSX Server 3.1.0 or VMware Workstation 4.5.2.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmmon-only'
make -C /lib/modules/2.6.8-9-amd64-generic/build/include/..
SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernel-headers-2.6.8-9-amd64-generic'
CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o
cc1: Invalid option `no-red-zone'
cc1: Invalid option `cmodel=kernel'
cc1: Invalid option `-fno-reorder-blocks'
cc1: Invalid option `-fno-asynchronous-unwind-tables'
In file included from include/linux/bitops.h:4,
from include/linux/thread_info.h:20,
from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from include/linux/module.h:10,
from /tmp/vmware-config3/vmmon-only/linux/driver.c:16:
include/asm/bitops.h: In function `sched_find_first_bit':
include/asm/bitops.h:444: warning: control reaches end of non-void function
In file included from include/linux/timex.h:155,
from include/linux/sched.h:11,
from include/linux/module.h:10,
from /tmp/vmware-config3/vmmon-only/linux/driver.c:16:
include/asm/timex.h: In function `get_cycles':
include/asm/timex.h:29: warning: left shift count >= width of type
In file included from include/linux/string.h:24,
from include/linux/bitmap.h:8,
from include/linux/cpumask.h:77,
from include/linux/sched.h:15,
from include/linux/module.h:10,
from /tmp/vmware-config3/vmmon-only/linux/driver.c:16:
include/asm/string.h: At top level:
include/asm/string.h:50: warning: conflicting types for built-in
function `__builtin_memcmp'
In file included from include/linux/mm.h:30,
from include/linux/poll.h:10,
from /tmp/vmware-config3/vmmon-only/linux/driver.c:29:
include/asm/pgtable.h: In function `pgd_bad':
include/asm/pgtable.h:220: warning: left shift count >= width of type
include/asm/pgtable.h: In function `pgd_offset_k':
include/asm/pgtable.h:328: warning: right shift count >= width of type
include/asm/pgtable.h:329: warning: left shift count >= width of type
include/asm/pgtable.h: In function `current_pgd_offset_k':
include/asm/pgtable.h:338: warning: right shift count >= width of type
include/asm/pgtable.h:339: warning: left shift count >= width of type
include/asm/pgtable.h: In function `pte_modify':
include/asm/pgtable.h:380: warning: left shift count >= width of type
In file included from include/linux/poll.h:10,
from /tmp/vmware-config3/vmmon-only/linux/driver.c:29:
include/linux/mm.h: In function `pmd_alloc':
include/linux/mm.h:587: warning: left shift count >= width of type
In file included from /tmp/vmware-config3/vmmon-only/linux/driver.h:19,
from /tmp/vmware-config3/vmmon-only/linux/driver.c:49:
/tmp/vmware-config3/vmmon-only/include/compat_wait.h: At top level:
/tmp/vmware-config3/vmmon-only/include/compat_wait.h:60: conflicting
types for `poll_initwait'
include/linux/poll.h:44: previous declaration of `poll_initwait'
In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:81:
/tmp/vmware-config3/vmmon-only/include/compat_kernel.h: In function
`compat_exit':
/tmp/vmware-config3/vmmon-only/include/compat_kernel.h:21: unknown
register name `rcx' in `asm'
/tmp/vmware-config3/vmmon-only/include/compat_kernel.h:21: unknown
register name `r11' in `asm'
/tmp/vmware-config3/vmmon-only/linux/driver.c: At top level:
/tmp/vmware-config3/vmmon-only/linux/driver.c:149: warning:
initialization from incompatible pointer type
/tmp/vmware-config3/vmmon-only/linux/driver.c:153: warning:
initialization from incompatible pointer type
/tmp/vmware-config3/vmmon-only/linux/driver.c: In function
`LinuxDriverIoctlAlloc4Gb':
/tmp/vmware-config3/vmmon-only/linux/driver.c:1313: warning: implicit
declaration of function `virt_to_phys'
/tmp/vmware-config3/vmmon-only/linux/driver.c: In function
`LinuxDriver_IoctlV3':
/tmp/vmware-config3/vmmon-only/linux/driver.c:2835: warning: large
integer implicitly truncated to unsigned type
{standard input}: Assembler messages:
{standard input}:576: Error: suffix or operands invalid for `pop'
{standard input}:581: Error: suffix or operands invalid for `push'
{standard input}:648: Error: suffix or operands invalid for `pop'
{standard input}:667: Error: suffix or operands invalid for `push'
{standar
Re: New mirror of Debian-amd64
Hi Goswin, (B (BYes I did this ;-), That would be to obvious ;-) (B (BI was thinking that perhaps its a permission issue etc. on my site, (Bperhaps the script should run as root etc. (B (BBest regards (B (BNils Valentin (B (B (B> Nils Valentin <[EMAIL PROTECTED]> writes: (B> (B>> Hi Leopold, (B>> (B>> I am trying to do the same here in Tokyo, but I cant get the mirror.sh (B>> to work (B>> which Goswin posted 2 days ago. I assume you used that as well ? (B>> (B>> It will say "rsync error; error in rsync protocol data stream (code 12) (B>> at (B>> io.c (359)" (B> (B> You did change the account name from mine to yours (if you have an (B> account). Otherwise you have to use a different source that has (B> anonymouns rsync or a different debmirror method. (B> (B>> Best regards (B>> (B>> Nils Valentin (B>> Tokyo/Japan (B> (B> MfG (B> Goswin (B>
