Siduction Forum
Siduction Forum => Installation - Support => Topic started by: Runaway1956 on 2015/07/20, 20:44:59
-
You don't have an idle chit-chat corner, nor an "introduce yourself" subforum. This looks like the best place to post a "thank you" post, I guess.
I've noticed Siduction a few times. I knew it was a Debian derivative, but didn't give it much thought, really. Well - several things combined with a Google search led me here today. Most specifically, I was searching for a combination of up-to-date kernels and an Nvidia card driver that would work on my specific hardware.
I didn't see a lot that seemed useful during my search, but I DID grab the Thunderstruck ISO, and installed it into a VM. Nice. It's not my preferred desktop, but very, very nice. I proceeded to install the VBox guest additions, then to upgrade Thunderstruck.
Oh, my, what is this? KERNELS!! I see kernels that I've never seen before! WHOOT! Siduction - Debian - Siduction - Debian - YES! I proceeded to comment out my sources.list, and copied all of the sources.list.d into my host's /etc/apt/ folder. apt-get update then apt-cache search linux-image. Oh yes - sweet!
Well, I'll stop babbling here:
$ inxi -F
System: Host: awesome Kernel: 4.1.2-towo.2-siduction-amd64 x86_64 (64 bit)
Desktop: Enlightenment 0.19.99.19943 Distro: Sparky 4 Tyche
Machine: Mobo: Supermicro model: H8DM8-2 v: 1234567890
Bios: American Megatrends v: 080014 date: 10/22/2009
CPU(s): 2 Hexa core Six-Core AMD Opteron 2425 HEs (-HT-MCP-SMP-) cache: 6144 KB
Clock Speeds: 1: 1100 MHz 2: 800 MHz 3: 1100 MHz 4: 1100 MHz 5: 800 MHz
6: 800 MHz 7: 2100 MHz 8: 800 MHz 9: 1100 MHz 10: 1100 MHz 11: 800 MHz
12: 800 MHz
Graphics: Card-1: Advanced Micro Devices [AMD/ATI] ES1000
Card-2: NVIDIA GK208 [GeForce GT 630 Rev. 2]
Display Server: X.Org 1.17.2 driver: nvidia
Resolution: 1024x768@60.00hz, 1280x1024@75.02hz
GLX Renderer: GeForce GT 630/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 346.82
Audio: Card-1 NVIDIA Device 0e0f driver: snd_hda_intel
Card-2 Plantronics driver: USB Audio
Sound: Advanced Linux Sound Architecture v: k4.1.2-towo.2-siduction-amd64
Network: Card-1: NVIDIA MCP55 Ethernet driver: forcedeth
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:30:48:c8:16:72
Card-2: NVIDIA MCP55 Ethernet driver: forcedeth
IF: eth1 state: down mac: 00:30:48:c8:16:73
Card-3: Realtek RTL8187 Wireless Adapter driver: rtl8187
IF: wlan0 state: down mac: 00:e0:4c:91:8b:9c
Drives: HDD Total Size: 800.2GB (44.3% used)
ID-1: /dev/sda model: MKNSSDCR240GB size: 240.1GB
ID-2: /dev/sdb model: MKNSSDCR240GB size: 240.1GB
ID-3: /dev/sdc model: WDC_WD3200AUDX size: 320.1GB
Partition: ID-1: / size: 28G used: 6.1G (24%) fs: ext4 dev: /dev/sda2
ID-2: /home size: 185G used: 27G (16%) fs: ext4 dev: /dev/sda3
ID-3: swap-1 size: 11.21GB used: 0.00GB (0%) fs: swap dev: /dev/sdc1
ID-4: swap-2 size: 4.91GB used: 0.00GB (0%) fs: swap dev: /dev/sdb3
ID-5: swap-3 size: 8.80GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 248 Uptime: 36 min Memory: 916.8/22164.9MB
Client: Shell (bash) inxi: 2.1.28
I believe that my next step will be to fire up my Thunderstruck VM, and see about installing E19 Enlightenment. THAT is my first choice in desktops!
If things work out, I may move Siduction onto the metal, and move Sparky into a VM . . . .
-
You will have to use Sparky repo's to use e19 (I myself have done this before) as debian is still on e17 or you can compile it ;)
-
Yes, that's what I had in mind. My first attempt, inside the VM seems to have been a flop. But - oddly enough, the VM itself is messed up now. Maybe I need to step back and look at VirtualBox and VBGuest additions. Something wrong somewhere - changing desktop environments shouldn't make the mouse go all funky . . .
-
Runaway1956: a good choice might be to setup a siduction xorg, install the siduction-dev-package, get the source packages from sparky linux and recompile the packages in the right order™
-
The funky mouse problem I mentioned above can be attributed to VirtualBox. I clicked a whole bunch of links, and it seems that VBox does weird things on random hardware. VBox has problems reproducing those problems, so they haven't yet solved the problem.
I don't believe that Siduction is at fault, nor do I believe the updates caused any problems. It's all related to VBox. I may have to switch off to VMWare. Ehhh - I prefer open source, but when open source doesn't work very well, I'll use proprietary.
-
I may have to switch off to VMWare.
Not until VMWare fixes their code to compile the kernel modules with gcc 5.1: http://forum.siduction.org/index.php?topic=5622.msg45894#new
-
Hmmm - they sure make things hard on us.
Further reading on my end suggests that the problem centers around USB mouse. I went in search of a PS2 mouse, but it seems that my dear children have dragged them all off. Target practice, or to drag them through the mud, or whatever. I hate to buy a new PS2 mouse just to test that theory, but I may do so.
-
give kvm a try
-
There are very cheap USB to PS/2 mouse adapters, for example on Amazon.com. The shipping is more than the item, actually. Make sure you get green (mouse) not purple (keyboard).
-
give kvm a try
I started down that path when vmware broke. But converting a .vmdk virtual disk image to the format for kvm turned out to be quite a complex series of dance moves and (being a lazy sort) I resorted to dual booting with Debian Jessie, on which VMWare's player was quick and easy to install and set up. And of course lurking at the end of the conversion to kvm process is the 99% likelihood that Windows 8 will puke up a "non genuine" error and I'll be screwed one more time by MS. Maybe I'll give it another shot one of these days, by setting up a new replacement Windows 10 environment on KVM. VMWare's code seems fragile and brittle -- I wouldn't mind getting away from it.
-
Hello,
give kvm a try
Why not giving siduction a try on a separate partition? I'm familar with linux since 1998, vbox or kvm gives possibitlity to get a first impression of new linux stuff. But when I want to know more then I spend new distributions seperate partitions.
And it seems, @Runaway1956, that you want to know more about siduction :-)
Kind regards,
Holger
-
Why not giving siduction a try on a separate partition?
Thanks holger. I have a really fine siduction Indian Summer installation on a fast PCI bus SSD, so I'm staying with that one. I just added another hard drive to the box and installed Jessie + VMWare on that one, then booted siduction and ran update-grub and let it pick up the Debian OS. So when I need to do my genealogy work I boot Jessie -- otherwise I stay with siduction/Plasma 5.
But, I think KVM is probably a better way to go in the longer term. I will test the free Windows 10 update on a Win 8 VM, and if my genealogy tools run OK, then I will probably buy a Win 10 license and install it on a KVM VM, and reinstall my windows software on that.
-
VMWare Workstation Technical Preview 2015 runs great here ;), no problems with gcc 5.
Windows 10 works like a charm, i play asphalt 8 airborn daily in the vm.
-
Ahhhh --- good tip towo`! Does VMWare charge a price for the Workstation Technical Preview?
-
Ahhhh --- good tip towo`! Does VMWare charge a price for the Workstation Technical Preview?
Download is free - but the license expires in December. So, if you use it, don't get to attached to it. Consider it to ONLY be a test bed.
https://communities.vmware.com/thread/515356?start=0&tstart=0 (https://communities.vmware.com/thread/515356?start=0&tstart=0)
https://communities.vmware.com/community/vmtn/workstation/vmware-workstation-technology-preview-2015 (https://communities.vmware.com/community/vmtn/workstation/vmware-workstation-technology-preview-2015)
You have to sign in before you can download. I wasn't sure if I had an account, so I tried a couple of my generic logins, and it worked. Obviously, I've registered in the past.
NOTE: The software installs just fine on Jessie - but when you try to start it, it wants the path to GCC 5.1.1 so that it can build modules.
I'm going off the deep end here - I've re-enabled the Siduction repositories so that I can install GCC5 (and dependencies). I my house burns down, and a super earthquake obliterates the Central US, I'll blame it all on siduction forums and Towo . . . .
-
Tried the VMware Workstation Technical Preview on a fully updated siduction system, with headers and build-essential installed. Didn't end well -- I obviously don't know something important.
root@Hibiscus:/# vmware-modconfig --console --install-all
Failed to get gcc information.
-
I don't know, what's wrong on your side:
http://paste.debian.net/285221/ (http://paste.debian.net/285221/)
Maybe you have to set gcc-5 as standard-gcc.
-
Tried the VMware Workstation Technical Preview on a fully updated siduction system, with headers and build-essential installed. Didn't end well -- I obviously don't know something important.
root@Hibiscus:/# vmware-modconfig --console --install-all
Failed to get gcc information.
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 100
-
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-5 100
Yep, THAT'S the important thing I did not know. Thank you very much!
-
OK - I got VMWare installed and working - and experienced problems with the mouse. VMWare documentation seems to be a little better than VirtualBox' documentation. With a couple of searches, I found that disabling, then re-enabling the USB controller for the VM (from within VMWare's control panel) often fixed the problem with erratic mouse.
I've restarted VBox, went into controls, and removed the USB controller, started up the VM, and I had no mouse at all. Shut it down, went into the VBox control screen, and re-enabled the USB controller. I have normal mouse control now.
That is somewhat encouraging - BUT - I did have normal mouse control within this particular VM until recently.
I think that I'm ready to try Siduction within a VBox VM again. I've got my fingers crossed . . .
Errrrr - no. Within several minutes, my VMBox VM has a funky mouse again. Can't click anything. The mouse moves around within the VM, and I can highlight stuff under the mouse. I click the mouse, the cursor kinda blinks, and nothing happens. Hmmmm - apparently common problems in both VM environments.
I'll get to the bottom of this yet. Wonder if it's my hardware?
-
As said by towo`, the preview VMWare is working well here with a Win 8.1 VM. But that ends in December. I need a longer term solution, for sure. I have a Win 8.1 VM set up to do the "free" upgrade to Win 10, which will come after 29 JUL. If my required Windows apps run correctly on Win 10, which I expect they will, then I will take the plunge to buy a Win 10 license and figure out how to make a KVM virtual machine to run it. If I can get that working, then I think I'll have a good solution for the duration .... (I'm 64 -- it doesn't need to run forever .....) :)
-
Heh. I'm only 59, but I expect Win7 to last for as long as I'll need to worry about Windows applications.
Fact is, I seldom use Windows for anything. For me - Windows is something of an obfuscation tool. If I can masquerade as a Windows user on the internet, then I'm more anonymous. Anonymity can be a valuable commodity, sometimes.
I presume that everyone is up to date with NSA spying, and the Five Eyes, etc etc?
Aside from that, there are many corporate entities out there that specialize in tracking users. I like to throw monkey wrenches into their machinery.
-
I'll get to the bottom of this yet. Wonder if it's my hardware?
I would think "yes". I have both Linux and Windows VMs on two different hardware systems, one an older Intel mobo and this one is a newish Asus, and I have never seen an issue with a USB mouse on either platform. I favor the MS optical mouse -- the cheapest 3-button model I can find.