Custom Query (16363 matches)
Results (895 - 897 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10067 | obsolete | PCManFM-MOD & Thunar Under Slackware Guest Don't Automout USB | ||
| Description |
Hi, I'm running Slackware 13.37 x86 with only OpenBox 3.4.11.2 as my desktop and I use the PCManFM-Mod file manager which is a port from PCManFM. I also use this as my file manager on my actual box, which also runs Slackware with only OpenBox, so I use pretty much the same setup in VirtualBox as I do on my hard drive. I noticed when plugging in a USB drive it does show it connected under the 'Devices' - 'USB Devices' but the file manager does not show it. I also tried using the Thunar file manger and the same thing, it would not auto detect the file manager. The PCManFM-MOD file manager is very simple and straight forward, it doesn't require any complicated setup to make USB drives to appear in them. Also the filesystem does not appear under VirtualBox. I'm attaching 3 screen shots, 2 for the host, so you can see that my file system appears and the usb drive when plugged in and 1 screen shot under the guest without the file system or usb drive. I know this file manager works as you can see in the host screen shots and I know the way I have it installed in VirtualBox is the same way as in the host. THANKS |
|||
| #10077 | worksforme | APIC Bug? | ||
| Description |
I'm running Slackware 13.37 as a Guest in VB 4.1.4 and I noticed in /var/log/dmesg this: weird, boot CPU (#0) not listed by the BIOS. SMP motherboard not detected. Enabling APIC mode: Flat. Using 0 I/O APICs ------------[ cut here ]------------ WARNING: at arch/x86/kernel/apic/apic.c:1299 setup_local_APIC+0x22c/0x2e2() Hardware name: VirtualBox Modules linked in: Pid: 1, comm: swapper Not tainted 3.1.5 #1 Call Trace: [<c102fb37>] warn_slowpath_common+0x6a/0x7f [<c13119c9>] ? setup_local_APIC+0x22c/0x2e2 [<c102fb60>] warn_slowpath_null+0x14/0x18 [<c13119c9>] setup_local_APIC+0x22c/0x2e2 [<c148fb2c>] APIC_init_uniprocessor+0x94/0xe9 [<c148db9f>] native_smp_prepare_cpus+0x1d1/0x3b8 [<c148569b>] ? start_kernel+0x2e3/0x2e3 [<c14856d7>] kernel_init+0x3c/0xfd [<c13163fe>] kernel_thread_helper+0x6/0x10 ---[ end trace a7919e7f17c0a725 ]--- APIC calibration not consistent with PM-Timer: 145ms instead of 100ms APIC delta adjusted to PM-Timer: 6289924 (9125077) So between also this 'weird, boot CPU' and the APIC warning I wanted to know if this is a bug? I also don't like using the standard kernel in Linux, to make things that are not supported that you have to weed through all the messages to figure out what is going on, so I compile my own kernel. These are some of the options I compiled in below. Also are there any other options I need to make sure I have support for in the kernel for VirtualBox, specific to it? <*> Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)
<*> EHCI HCD (USB 2.0) support
<*> USB Mass Storage support
[*] ISA support
Processor type and features --->
[*] Tickless System (Dynamic Ticks)
[ ] High Resolution Timer Support
[X] Symmetric multi-processing support (keep this enabled for multiple cores, too!)
Subarchitecture Type (PC-compatible) --->
[ ] Machine Check / overheating reporting
[X] SMT (Hyperthreading) scheduler support (This too, for i7's)
Power management and ACPI options --->
[*] Power Management support
[ ] Suspend to RAM and standby
[ ] Hibernation (aka 'suspend to disk')
[*] ACPI (Advanced Configuration and Power Interface) Support --->
Device Drivers --->
< > ATA/ATAPI/MFM/RLL support
<*> Serial ATA and Parallel ATA drivers
<*> AHCI SATA Support
[*] ATA SFF support
<*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
[*] Network device support --->
[*] Ethernet (10 or 100Mbit) --->
[*] EISA, VLB, PCI and on board controllers
<M> AMD PCnet32 PCI support
[*] Ethernet (1000 Mbit) --->
<M> Intel(R) PRO/1000 Gigabit Ethernet support
[ ] Ethernet (10000 Mbit) --->
Input device support --->
[*] Mice --->
<*> PS/2 mouse
Graphics support --->
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
< > all options can be empty
<M> Sound card support --->
<M> Advanced Linux Sound Architecture --->
[*] PCI sound Devices --->
<M> Intel/SiS/nVidia/AMD/ALi AC97 Controller
THANKS |
|||
| #10165 | invalid | Unix/Linux Systems Can't Resize Console Windows -> guest system configuration issue | ||
| Description |
Since VirtualBox has supported Unix/Linux I'm not sure why support for being able to resize the console has not been made available, since the size of the console screen can be as big as the monitor you are using on your host system. Most people might be using Unix/Linux under X, but there are many times with these systems and in many situations where X might not be used. Right now as it stands if you are not using X and you are just using the console you are stuck with a very small screen size, somewhere around 300x300 big and this is just to small to be functional to use in many situations. I truly hope this project will please look into this situation to see what can be done to be able to make the screen size larger. Today with High Definition leading the way, many people are using larger sized monitors and we come to expect being able to use something like this with a bigger view to it. If Unix/Linux systems can certainly display the console to whatever sized monitor you are running on the actual host system, then there certainly must be a way to have this work in VirtualBox also. I've attached a screen shot taken on a 15" laptop to give you an idea of how small we are talking about. So please imagine that this is how big of a monitor you have on a computer, that's probably a 5"-6" screen, then you get an idea of how difficult that probably is to try and work with and let me tell you it is and it's not fun at all. It also doesn't matter what version of Unix/Linux you run, when it comes to the console they all give the same sized screen, I've run several versions of Linux and Unix guests on VirtualBox all with this small sized console screen. Scaling the screen is not an option I like at all, it makes the fonts look warped and distorted. Changing the resolution on a screen size this big is not a good option either, we are talking extremely small text size to then read, I've tried this and it's not good. We just need the developers to figure out a way to be able to have the screen size larger is all. I hope there is a way the VirtualBox team can make this happen sometime this year, I can't tell you how bad I need this support for the work I do with VirtualBox and how difficult it's making things, having this size to work with. Thank you for your time and I look forward to hearing the thoughts of the developers on this. |
|||

