I installed Slackware 13 in VirtualBox 3.1 (seehere)When I'm logged in as a normal user, I get a mesage that Intel *** (sound device) doesn't work anymore and I hear no sound.But it works very fine when I'm logged in as root.
View 4 RepliesMy HDA NVidia (VT1708S Digital) doesn't work when I login normal user. It works perfectly when I login root.
View 3 Replies View RelatedI just want to be able to access and modify the files on my usb drive as a normal user. The mount command works perfectly as root but then the files that I end up copying to my home folder can only be modified as root. I only use a window manager and use just bash for file management. I just want to be able to it through the command line.
(using 13.37)
How can I auto login as a normal user in slackware 13.1. I need to auto login in X.
View 6 Replies View RelatedI have recently installed the Slack 13.1 x86_64 on my laptop. It works fine! But I have one trouble with it. I cannot run the installpkg and pkgtool with my normal user. It says to me that there is no command found. Is it a problem with the sudoers file or these commands are not really installed? Maybe my path is incomplete?
View 15 Replies View RelatedI am using Slackware 13.0 and i have managed to work with my USB pen-drive as root but i cannot do it as a normal user.
View 14 Replies View RelatedDoes anyone have a permanent fix for not being able to use USB devices in VirtualBox as a regular user?
View 11 Replies View RelatedI haven't used my VB for a few weeks however all of a sudden it refuses to work for my normal non-root user. It's almost as if it can't find libraries in the /opt/VirtualBox directory. Initially it refused to start completely so I linked the required libs into /usr/lib64 ( yip real hack. Then it started but a vm would not start, and comes up with an error about a missing lib again which is definitely there. My non-root user is in the vb group and nothing besides system updates has changed. vb 3.2.10 slack64-current.
View 14 Replies View RelatedI have just installed VirtualBox on my OpenSuSE 11.1 and created my first VM (Windows XP) - and everything works just fine, but.... I can only run it as user root (if I remember correctly I could only install VirtualBox as root)Anybody know what I need to do so that I can run VirtualBox under a normal user account.
View 2 Replies View RelatedI've got a strange problem: when I run Frozen Bubble from my user account, I get no sound, but the same game has sound with my wife's account and the root account.
EDITED TO ADD: My user account has sound for DVDs through Kaffeine, Mplayer, etc. And the system sounds are working just find.
I've got a custom compiled kernel, just built on Lucid 10.04 from the kernel sources.System works fine, except for sound.When I log in as normal user and try to play a wav file using.The sound file is being played, but I hear no sound.However, when I do "sudo -s" and become root, execute the same mplayer command then I can hear the sound.My Sound preferences shows no input device and only "Dummy Output" as output device.On the generic kernel as came with the Lucid 10.04 CD, sound preferences shows different devices.The strange thing is: when I compiled my custom kernel, I changed nothing to the sound options in the kernel config file.
View 6 Replies View RelatedFor those that use Virtualbox on their slackware host and have a windows (xp) guest running. I have tried various settings for sound (Alsa, PulseAudio), the AC97 drivers are installed in the Windows xp guest os, but there is no sound and there is an unknown audio device (in the windows device manager). If I remove the AC97 drivers and use the soundblaster16 drivers in the Vbox settings there is no unknown sound device, but there's still no sound. why I can't get sound working?
View 13 Replies View Relatedafter update to slackware current 4 days ago i cant get sound working in wine in starcraf 2 i mean i got sound in instalation but not in game and i get error when i wanna configure sound in winecfg
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:wine_snd_pcm_recover underrun occurred
err:alsa:wine_snd_pcm_recover underrun occurred
in game i dont got that error but sound dont work btw my sound card is asus xonar essence stx
I'm currently trying to install unRaid on Slackware following this tutorial :[URL].. I'm new to Linux and after many hours, i finally managed to build the new kernel for unRAID (2.6.32.9). But audio on HDMI port doesn't work I tried alsaconf without success. HDMI sound works when i boot into the old kernel.
My codecs are :
Code:
root@unraid:~# cat /proc/asound/Intel/code* | grep Codec
Codec: Realtek ALC888
Codec: Intel G45 DEVIBX
Code:
lspci -v:
[Code]...
If sound on F12 works as root user but not as a normal user, try this simple fix! I've been struggling to get sound working as a normal (non-root) user since F10. Until now I've had to run X as root user to get any sound out of my machine.
Sound actually works OK now for me as a normal user. Here's how I fixed the problem.
First I uninstalled pulseaudio with:# yum remove pulseaudio Then reboot back to the hardware. You might want to keep pulseaudio, but I have no need for it. PA wasn't running on my system anyway.
Running X as root user, I did the following: As a test I opened a root shell and typed the following:
[root]# alsamixer c0 That started the alsamixer OK, and all the controls were accessible.
[Code]...
i need to install the important pkg for normal use with
what pkg is not important and im on safe if i didnot choose it
a
ab
d
e
[Code]....
I am using the most recent -current (that fixes the libpng "ratness" described in the ChangeLog 8-) and the Intel Framebuffer setup is annoying me. I specify vga=normal in LILO and to my knowledge I am not asking Intel Framebuffer modules to load at boot (and intelfb is blacklisted).
It's annoying because it makes the text microscopic. However, the machine works great in -Current so I can't complain. Graphics work fine and so does X, it's just annoying.
This is my Sony Vaio VGN-C140G detailed here: url
I had tried previously blacklisting inteldrmfb as well (the -Current release right before the libpng fix) and that made no difference.
I found all binaries with "intel" in their name and read the manual pages but didn't find anything useful for possibly manually setting the mode back to something equivalent to vga=normal.
So I've installed a slightly earlier version of -current than is out now and installed the 2.6.38.2-smp kernel on my Asus eeePC. Normally (both on this computer and every other laptop I've used, other than Macs) you scroll by swiping one finger up/down the right side of the trackpad. This installation, however, has made the scroll similar to the Mac scroll (two fingers anywhere on the trackpad, swiping up or down). How do I change it back? I have no xorg.conf file
View 6 Replies View Relatedi have installed Salix 13.1 LXDE version (Salix 13.1 is compatible with Slackware 13.1). I must use various external hard disks formatted with NTFS. The hard disks are automatically recognized and mounted with PCmanFM file manager, but only user root can write on them. How can I allow normal users to write on automounted external ntfs drives?
View 3 Replies View RelatedActually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
View 10 Replies View RelatedI have an ISO of 13.37, I have selected the ISO as the booting medium in the Virtual Box and I do get uptil the screen where one is supposed to select the source media. Because I am installing from an ISO what option I am supposed to select out of the 6 present there?
View 4 Replies View RelatedThe latest release of VirtualBox (3.1.6) corrects most of the problems that I had with Slackware and KDE. If you have been avoiding VirtualBox or KDE because of those issues you might want to take another look.The only problem that I'm having now is that I have to click somewhere on the desktop to get a proper display when switching VirtualBox into "seamless" mode. The rest of the window display issues appear to be fixed and full screen mode also works correctly.
View 2 Replies View RelatedI downgraded a computer a couple of weeks ago from -current to 13.1. At that point in time the USB support in my Virtualbox stopped working. Since then I have installed Virtualbox on my wife's laptop, which also runs 13.1, and the USB support doesn't work there either. So I tried it on yet another 13.1 box that I have lying around no USB support. Then I upgraded the latter box to -current and USB works! Given that sequence of events, I'm pretty sure this is a Slackware 13.1 problem rather than a Virtualbox problem. what might be causing this?
View 8 Replies View RelatedInstalled 13.1 as a guest in VirtualBox with Debian Lenny 5 64bit as host. The mouse, gpm, and the keyboard work alright at the black screen but in the graphical thing, forget its name.....Xsomething, not KDE, there is no mouse or keyboard; for example the screensaver just goes on and on and nothing will stop it.
View 14 Replies View RelatedSince my upgrade to 13.37 + VirtualBox 4.0.4 (from SBo) I'm having trouble with one of my VMs containing a PostgreSQL installation (also from SBo) which has been running fine before on 13.1 + VBox 3.2.10.
This is what happens: I'm starting an I/O heavy job on the DB that should take about an hour but never finishes because the virtual disk stops working after 10 to 40 minutes.
Code:
ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/00:00:e8:11:44/01:00:02:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
lots of these
[Code]...
Just grabbed Slackware64-current and installed on my laptop. Also put Alien Bob's multilib on.need it for my Absoft fortran compiler.The problem I'm having is that VirtualBox-3.1.6 doesn't install. I've looked at other problems on the list related to this and I don't think that any of the ones that I've seen applies to my situation. My feeling is that there is an incompatibility problem with gcc. The stock kernel was compiled with gcc-4.4.3 which comes with Slackware64-current. However, Bob's multilib backdates this to gcc-4.3.3. So, when the Virtualbox installation procedure runs it sees a kernel compiled with a version of gcc that is different from the one that is currently installed and chokes. recompile the kernel with the current gcc. Haven't done a kernel compile in a long time though and I'd like to get it right. So, my question is "Is the stock .config file in the linux source folder the one used to configure the default kernel?". I like the stock kernel and would like to recompile with all the bells 'n whistles in the stock kernel.
View 14 Replies View RelatedI am running Windows XP in VirtualBox. I generally only use it for iTunes and some light browsing occassionally. Downloads only occur on iTunes, but it does have internet access. And my wife will still only use Windows, so if she uses this particular machine it is available to her, and she occassionally goes to facebook on this machine.
Should I install an anti-virus? Is it really necessary? I am pretty certain my Linux install would be unaffected even if a virus or other malware did occur in VirtualBox.
I'm trying to run Slackware 13.37 64-bit in a VirtualBox virtual machine. My VirtualBox version is 3.2.12. I had to disable compositing to keep the X-Server from reporting a segfault.Now the problem is that on logout from KDE I get a completely black screen. I can switch to a console session and type commands to get the login screen again.
telinit 3
telinit 4
I tried editing "kdmrc" to add the line "TerminateServer=true" but it had no effect on the problem.I had this working with Slackware 13.1 at one time, but I can't seem to get it working properly now even without desktop effects.I'm trying to avoid changing my VirtualBox software since each version seems to just introduce new and different bugs. The 4.X versions are not yet very stable.
I am using the 13.1 build scripts from slackbuilds.org. I modified the scripts to build 3.2.12 rather than 3.2.10.
In 13.1 the main VirtualBox 3.2.12 OSE package built and installed without errors. The VirtualBox GUI starts without errors.
Running the virtualbox-kernel-mksrctarball.sh script built a kernel source package without errors.
Yet the VirtualBox kernel module won't build. I receive the following error:
Code:
]*** Building 'vboxdrv' module ***
make[1]: Entering directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33.11-smp-2/build SUBDIRS=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv SRCROOT=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv modules
[Code].....
I'm trying to compile virtualbox 3.2.10 con slackware current 32bit through sbopkg
I get this error (I'll copy only the end part)
Code:
CXX VMMR3 - {C}/src/VBox/VMM/VMMAll/TMAllCpu.cpp
cc1plus: warnings being treated as errors
In file included from /tmp/SBo/VirtualBox-3.2.10_OSE/src/VBox/VMM/VMMAll/PGMAll.cpp:236:0:
[Code].....