Re: VM Ware Player under Debian Lenny AMD64 on laptop
C M Reinehr wrote: On Fri 24 July 2009 04:34:05 pm James Brown wrote: C M Reinehr wrote: On Fri 24 July 2009 02:45:31 pm James Brown wrote: C M Reinehr wrote: On Fri 24 July 2009 12:45:18 pm James Brown wrote: Lennart Sorensen wrote: On Fri, Jul 24, 2009 at 09:10:49PM +0400, James Brown wrote: I intend to install on my laptop under Debian Lenny AMD 64 the VM Ware Player 2.5.2 from http://www.vmware.com/download/player/download.html (becouse there is no VMWare Player in the official repositories of the Debian). Which of the packege do I need - rpm or bundle? How do install it on Debian? And what of libraries and etc. do I need install for succesfull using VMWare Player? You do not want the rpm. I don't like the current bundles either. I keep nagging vmware to provide the tar files that worked with make-vmpkg again, but they are too clueless to understand why real admins won't run GUI installer crap in X as root on their systems rather than something the package manager can deal with. Fortunately we now have kvm (on machines with virtualization hardware support) which is in my opinion much better than vmware, free, open source, and maintained and part of stock kernels. I have no need for vmware anymore. Could the kvm boot the Windows from physical disk? (I want to make the virtual machine boot my old Windows from my laptop becouse some programes from my working space don't want to run under Linux). Earlier I tried the Virtualbox but it cannot do it and the Virtualbox from the Debian's repositories don't maintain USB. James, Download VirtualBox from the Sun repository, rather than the Debian repository. You'll get a more current version and USB will work: http://www.virtualbox.org/wiki/Linux_Downloads There are some features of VB that are not available in the open source edition (ose) available from a Debian repository which are available in the version from Sun. HTH cmr I did this installation but now I have something strange: when I gave command virtualbox the bash answered me that this command didn't found. The binary is VirtualBox (/usr/bin/VirtualBox) -- mind the capitalization. cmr Very thanks. It is enough write VirtualBox in the terminal (but when I used virtualvox-ose I wrote virtualbox, not VirtualBox). Now I have a very strange problem: after booting the Windows under my new VirtualBox my system (either Windows under VirtualBox or Debian on my phisical machine, I cannot use Ctl-Alt-Del, Ctl-Alt-Shift, Ctl-Alt-Fn and I cannot do any more than to press poweroff button on my laptop. In the 3rd time after booting Windows under VirtualBox my system (on physical machine) was crash, power was off without any my doing and my phisical machine rebooted. Now I am afraid maybe it was a virus of the BIOS I cached through VirtualBox? Or maybe it is simply becouse I boot my Windows from vmi-disk created on my old virtualbox-ose 1.6? But if is the last why so strange and awful behavior of my computer?! OK, James, please take a deep breath and start over. Are you saying that the Ctl-Alt-whatever key sequences do not work in your virtual Windows environment or that they do not work in your Debian host system? If you are having problems within the virtual Windows environment, have you read the user manual chapter on Typing Special Characters (3.4.1.2)? If you are having problems with your Debian host system, I would think that these are unrelated to VirtualBox and indicative of problems in your Debian system. Is your virtual Windows system crashing rebooting (not unheard of with Windows) or is your Debian host system crashing rebooting? With regard to running a vmi-disk created by virtualbox-ose 1.6 under VirtualBox 3.0, I seriously doubt that it will work. While VBox 3.0 may well be able to work with the vmi-disk, but I doubt that the virtual Windows system will be able to handle the changes in virtual hardware. That is to say, that the new VBox 3.0 will present newer/different hardware devices to the Windows O/S which will not have the correct drivers to run. (I think this was mentione elsewhere in this thread.) I would suggest creating a new virtual Windows system from scratch. Cheers! cmr I probably found what was the couse of my problem. I tried to install into my guest Windows system the skype for Windows version 4.1. It didn't want to work under virtualbox-1.6.6-ose and always closed itself with the reporting about error. But when it tried to run under VirtualBox 3.0.2 of the Sun, that process gave such effect. When I created my new vdi-disk under the VirtualBox 3.0.2 it ran good. But when I had installed the skype into the guest system and have tried to run it, the adove-mentioned problem came again. -- To UNSUBSCRIBE, email to
Re: How to install wine on debian/amd64/sid?
On Tue, Jul 21, 2009 at 08:07:20PM -0300, Cavan Mejias wrote: 2009/7/20 Dean Hamstead d...@fragfest.com.au: If you arent able to fix breaks, you should use 'testing' which is currently 'squeeze' testing is generally solid enough but also bleeding edge enough for desktops. Ya, I agree. Exactly why I use testing. It must be possible to downgrade from sid to lenny, w/out a reinstall. Downgrading has always been a problem in Debian. The slow way is simply to change your sources.list to point to lenny instead of sid. As sid packages drift into lenny by the normal development process, your system will gradually become more lenny than sid. Along the way aptitude will probably have a few conniptions. The answer to that is simply to back out of any upgrade that causes trouble (using control-U in interactive more). The problems will usually sort themselves out in a few weeks. -- hendrik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: How to install wine on debian/amd64/sid?
hend...@topoi.pooq.com wrote: On Tue, Jul 21, 2009 at 08:07:20PM -0300, Cavan Mejias wrote: 2009/7/20 Dean Hamstead d...@fragfest.com.au: If you arent able to fix breaks, you should use 'testing' which is currently 'squeeze' testing is generally solid enough but also bleeding edge enough for desktops. Ya, I agree. Exactly why I use testing. It must be possible to downgrade from sid to lenny, w/out a reinstall. Downgrading has always been a problem in Debian. The slow way is simply to change your sources.list to point to lenny instead of sid. As sid packages drift into lenny by the normal development process, your system will gradually become more lenny than sid. Along the way aptitude will probably have a few conniptions. The answer to that is simply to back out of any upgrade that causes trouble (using control-U in interactive more). The problems will usually sort themselves out in a few weeks. I think you mean Squeeze, don't you? Lenny will not be updated, other than some backported security fixes. You may want to downgrade in stages, first to Squeeze, then to Lenny. As Hendrick pointed out, it can be very trying of your patience to downgrade. Generally, you can do it by downgrading groups of packages, ending with the kernel and the basic system packages. It will be easiest by hand, but also the most dangerous. Creating and installing some dummy packages to resolve dependencies may help, if you stick to apt, aptitude, and Synaptic. (Remove them as soon as possible.) You can create equivalents, packages that supposedly provide some prerequisite. This may be more work than you want to do. You need to do this all at once. That means, once you start, you should not rest until you are finished. Otherwise, the system may self-destruct. This is true for essential packages that modify system files. You might be able to put off downgrading something like the GIMP. It may be desirable to locate backports of newer versions of programs before you start. If it were me, I would just do a fresh install. Good luck! Mark Allums -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: How to install wine on debian/amd64/sid?
On Tue, Jul 28, 2009 at 05:37:58AM -0500, Mark Allums wrote: hend...@topoi.pooq.com wrote: On Tue, Jul 21, 2009 at 08:07:20PM -0300, Cavan Mejias wrote: 2009/7/20 Dean Hamstead d...@fragfest.com.au: If you arent able to fix breaks, you should use 'testing' which is currently 'squeeze' testing is generally solid enough but also bleeding edge enough for desktops. Ya, I agree. Exactly why I use testing. It must be possible to downgrade from sid to lenny, w/out a reinstall. Downgrading has always been a problem in Debian. The slow way is simply to change your sources.list to point to lenny instead of sid. As sid packages drift into lenny by the normal development process, your system will gradually become more lenny than sid. Along the way aptitude will probably have a few conniptions. The answer to that is simply to back out of any upgrade that causes trouble (using control-U in interactive more). The problems will usually sort themselves out in a few weeks. I think you mean Squeeze, don't you? Lenny will not be updated, other than some backported security fixes. Of course. I meant squeeze. -- hendrik You may want to downgrade in stages, first to Squeeze, then to Lenny. Downgrading slowly to Lenny won't work any more with my method. -- henrik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: How to install wine on debian/amd64/sid?
On Tue, Jul 28, 2009 at 06:01:10AM -0400, hend...@topoi.pooq.com wrote: On Tue, Jul 21, 2009 at 08:07:20PM -0300, Cavan Mejias wrote: 2009/7/20 Dean Hamstead d...@fragfest.com.au: If you arent able to fix breaks, you should use 'testing' which is currently 'squeeze' testing is generally solid enough but also bleeding edge enough for desktops. Ya, I agree. Exactly why I use testing. It must be possible to downgrade from sid to lenny, w/out a reinstall. Downgrading has always been a problem in Debian. No actually downgrading has simply always been a problem for everything. After all if a new version of a package converts the configuration to a new format, the old package can not convert it back since the old package has no way of knowing the new format since the new format did not exist at the time the old package was created. Of course since most config formats don't usually change, then downgrading can usually be done with a lot of hard work. The slow way is simply to change your sources.list to point to lenny instead of sid. As sid packages drift into lenny by the normal development process, your system will gradually become more lenny than sid. Along the way aptitude will probably have a few conniptions. The answer to that is simply to back out of any upgrade that causes trouble (using control-U in interactive more). The problems will usually sort themselves out in a few weeks. Yep that works. Well pointing to stable, since lenny won't update. Stable will eventually update. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: How to install wine on debian/amd64/sid?
hend...@topoi.pooq.com writes: On Tue, Jul 28, 2009 at 05:37:58AM -0500, Mark Allums wrote: hend...@topoi.pooq.com wrote: On Tue, Jul 21, 2009 at 08:07:20PM -0300, Cavan Mejias wrote: 2009/7/20 Dean Hamstead d...@fragfest.com.au: If you arent able to fix breaks, you should use 'testing' which is currently 'squeeze' testing is generally solid enough but also bleeding edge enough for desktops. Ya, I agree. Exactly why I use testing. It must be possible to downgrade from sid to lenny, w/out a reinstall. Downgrading has always been a problem in Debian. The slow way is simply to change your sources.list to point to lenny instead of sid. As sid packages drift into lenny by the normal development process, your system will gradually become more lenny than sid. Along the way aptitude will probably have a few conniptions. The answer to that is simply to back out of any upgrade that causes trouble (using control-U in interactive more). The problems will usually sort themselves out in a few weeks. I think you mean Squeeze, don't you? Lenny will not be updated, other than some backported security fixes. Of course. I meant squeeze. -- hendrik You may want to downgrade in stages, first to Squeeze, then to Lenny. Downgrading slowly to Lenny won't work any more with my method. -- henrik Or just verry slowly if by lenny you mean stable. Just would take a year or two. :) MfG Goswin -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: VM Ware Player under Debian Lenny AMD64 on laptop
On Tue, Jul 28, 2009 at 04:57:01AM +0400, James Brown wrote: I received an answer from the technical support of the Acer, they informed me that in all laptops of Acer didn't turn on the vt-support independently of CPU supporting. They write that becouse that it is impossible to turn on it in the BIOS. Are they idiots?! Well somewhat. They apparently decided it wasn't a feature worth supporting. So yes if they don't support it in the BIOS, then it doens't matter what the CPU can do, since the BIOS has to enable it. VT works fine on my thinkpad SL500. Lenovo thinks it is a feature people want. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Poweredge with SAS6/ir
On Mon, Jul 27, 2009 at 04:57:38PM -0700, ozz lioi wrote: I'm having a great deal of difficulty understanding what the problem is so far. The situation is this: I could boot from DVD and install the OS, then it would not load. In the boot up process if I choose the F10 option (Utility Mode) then it boots the OS with the normal mode + single mode option. I can login to the normal option but nothing works, I cannot even start networking, similarly to single mode. I have tried to install Lenny AMD64 and now I will try the i386. Driver support is almost certainly going to be identical between amd64 and i386. It may be that your hardware simply does not work with linux right now, or that you need a newer kernel. Lenny uses 2.6.26, and I certainly have needed a newer kernel for many of the machines we are getting at work now. 2.6.29 seems to work on most of them. So to some extent you can try a daily build of the debian installer to see if it can detect the devices properly, but you would essentially have to install unstable to get a newer kernel. So what kind of machine is it? What model? -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Poweredge with SAS6/ir
It's a Dell PowerEdge 2950. The module is the SAS6/ir. I have managed to get into the OS which now leaves me thinking the problem may lie somewhere else. I did manage that by hitting 'Utility mode' (which I even consulted with Dell and should not happen as it is a utility by Dell) during bootup, I will try to get a transcript of lspci info as I cannot get the machine to connect or even to change any files as the OS seems to not respond to the changes. The previous OS running there was CentOS 5 (I believe, too late to check). I did download Ubuntu to see what drivers it uses but no longer sure if it's a driver issue. The install does see the virtual disk, but after restarting I have to either boot into a mangled OS without much I can do so far or watch the cursor blink at an empty line after the remote access configuration prompt. I think there is possibly a grub issue... Don't know! Ozz Lioi Systems Administrator Light Box Media o...@lightboxmedia.ca Mobile: 778-997-1997 -Original Message- From: Lennart Sorensen [mailto:lsore...@csclub.uwaterloo.ca] Sent: Tuesday, July 28, 2009 6:57 AM To: ozz lioi Cc: debian-amd64@lists.debian.org Subject: Re: Poweredge with SAS6/ir On Mon, Jul 27, 2009 at 04:57:38PM -0700, ozz lioi wrote: I'm having a great deal of difficulty understanding what the problem is so far. The situation is this: I could boot from DVD and install the OS, then it would not load. In the boot up process if I choose the F10 option (Utility Mode) then it boots the OS with the normal mode + single mode option. I can login to the normal option but nothing works, I cannot even start networking, similarly to single mode. I have tried to install Lenny AMD64 and now I will try the i386. Driver support is almost certainly going to be identical between amd64 and i386. It may be that your hardware simply does not work with linux right now, or that you need a newer kernel. Lenny uses 2.6.26, and I certainly have needed a newer kernel for many of the machines we are getting at work now. 2.6.29 seems to work on most of them. So to some extent you can try a daily build of the debian installer to see if it can detect the devices properly, but you would essentially have to install unstable to get a newer kernel. So what kind of machine is it? What model? -- Len Sorensen No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.32/2266 - Release Date: 07/28/09 06:00:00 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
U3 and other firmware USB thumbdrives
Last time I messed with this, there was only U3 - it appears that there are a bunch of different systems now. There was a U3 removal tool at that time - what is the situation today? Is there a particular brand that just provides storage and non of this garbage? I need to find a 32GB USB drive that I can dd copy with - without having troubles with some embedded firmware.. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Truth is mighty and will prevail. There is nothing wrong with this, except that it ain't so. --Mark Twain -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: U3 and other firmware USB thumbdrives
On Tue 28 July 2009 02:22:46 pm Karl Schmidt wrote: Last time I messed with this, there was only U3 - it appears that there are a bunch of different systems now. There was a U3 removal tool at that time - what is the situation today? Is there a particular brand that just provides storage and non of this garbage? I need to find a 32GB USB drive that I can dd copy with - without having troubles with some embedded firmware.. Maybe I'm missing something, but I've never worried about this. I just plug it in and then run mkfs or cfdisk and mkfs, and problem solved. Cheers! cmr --- - Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Truth is mighty and will prevail. There is nothing wrong with this, except that it ain't so. --Mark Twain --- - -- Debian 'Etch' - Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: U3 and other firmware USB thumbdrives
On Tue, Jul 28, 2009 at 02:22:46PM -0500, Karl Schmidt wrote: Last time I messed with this, there was only U3 - it appears that there are a bunch of different systems now. There was a U3 removal tool at that time - what is the situation today? Is there a particular brand that just provides storage and non of this garbage? I need to find a 32GB USB drive that I can dd copy with - without having troubles with some embedded firmware.. The only usb key I have encountered with U3 on it was a sandisk. Every other kind I have is just a plain simple USB key. So I would say most are simply USB keys. If they have U3 or similar they tend to advertise it as if it was an amazing and useful feature. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
