Mouse integration with Tiny Core Linux.
Mouse integration with Tiny Core Linux.
Hello everyone!
I have a bit of a challenging issue here. I'm attempting to create a Tiny Core Linux guest OS with a openbox / xorg type configuration. So far I've been able to get almost all the guest additions features working, auto-resize, seamless, etc. However, mouse integration isn't working at all. The mouse cursor appears normally as it should when you cross over into the VM window... But when you click something, the X/Y values are different in the guest OS. It's almost like... The mouse area in the guest OS is smaller or larger then it should be, so when you mouse over the guest OS, it doesn't travel as expected. I saw in the virtualbox manual that you have to add a entry to the xorg.conf to get the mouse working properly, but it gives no example, only a example for the monitor settings. The way Tiny Core works is it uses some sort of "conf-less" mode where xorg figures out stuff automatically. You can, however, override this with a custom xorg.conf that contains just the entries you want to change. So that leaves me with two questions. What do I need to add in the xorg.conf? And how do I get virtualbox and /dev/psaux to talk to each other? Any help would be appreciated, this one has left me scratching my head.
I have a bit of a challenging issue here. I'm attempting to create a Tiny Core Linux guest OS with a openbox / xorg type configuration. So far I've been able to get almost all the guest additions features working, auto-resize, seamless, etc. However, mouse integration isn't working at all. The mouse cursor appears normally as it should when you cross over into the VM window... But when you click something, the X/Y values are different in the guest OS. It's almost like... The mouse area in the guest OS is smaller or larger then it should be, so when you mouse over the guest OS, it doesn't travel as expected. I saw in the virtualbox manual that you have to add a entry to the xorg.conf to get the mouse working properly, but it gives no example, only a example for the monitor settings. The way Tiny Core works is it uses some sort of "conf-less" mode where xorg figures out stuff automatically. You can, however, override this with a custom xorg.conf that contains just the entries you want to change. So that leaves me with two questions. What do I need to add in the xorg.conf? And how do I get virtualbox and /dev/psaux to talk to each other? Any help would be appreciated, this one has left me scratching my head.
Re: Mouse integration with Tiny Core Linux.
Bump.
Has anyone pulled this off? I don't understand why it's so hard to get mouse integration working when it works great on all the other major Linux distros.
Has anyone pulled this off? I don't understand why it's so hard to get mouse integration working when it works great on all the other major Linux distros.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Mouse integration with Tiny Core Linux.
I don't know for sure because I don't use tiny core that much but the xorg.conf example is here Howto: Install Linux Guest Additions
Re: Mouse integration with Tiny Core Linux.
Hey Perryg,
That's some great info, but I'm still a little confused about something. It says in the VirtualBox user manual that /dev/psaux needs to be associated with vboxmouse. How do I do that? I've tried adding the xorg entries as described in that guide and it didn't do anything.
That's some great info, but I'm still a little confused about something. It says in the VirtualBox user manual that /dev/psaux needs to be associated with vboxmouse. How do I do that? I've tried adding the xorg entries as described in that guide and it didn't do anything.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Mouse integration with Tiny Core Linux.
Not sure. Normally the xorg entries are what is needed and the association if done after that by the kernel drivers.
I will try to look into this tomorrow if I find a few extra minutes.
Do you meet the requirements of the version numbers in that section?
Also do you know which mouse driver you actually have in /dev, mouse or psaux?
I will try to look into this tomorrow if I find a few extra minutes.
Do you meet the requirements of the version numbers in that section?
Also do you know which mouse driver you actually have in /dev, mouse or psaux?
Re: Mouse integration with Tiny Core Linux.
I would definitely appreciate any help on this. So to answer your question, the driver is for psaux. Tinycore doesn't support dkms, but that shouldn't matter when it comes to getting things working for that particular kernel, right? I'm really interested in learning how the mouse module is created. There must be some manual way of configuring vboxmouse that isn't automated with the installer. What happens in the background OTHER then making changes to the xorg.conf?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Mouse integration with Tiny Core Linux.
Post the xorg.0.log & your custom xorg.conf. (as an attachment)
Be sure to tell me the exact location where these files reside.
Also the results of the following
uname -a
cat /etc/issue
Be sure to tell me the exact location where these files reside.
Also the results of the following
uname -a
cat /etc/issue
Re: Mouse integration with Tiny Core Linux.
Well, the way Tiny Core works is it uses some sort of "confless" mode, where there is no xorg.conf at all. You can override these settings by copying xorg.conf to /etc/X11. I've tried using this xorg.conf from the link you sent:
But nothing happens. I need to figure out how to build the mouse module manually I think. Where is xorg.0.log normally located?
Also, here is the uname and cat you requested:
$ uname -a
Linux box 3.0.21-tinycore #3021 SMP Sat Feb 18 11:54:11 EET 2012 i686 GNU/Linux
$ cat /etc/issue
Core Linux
Code: Select all
Section "Device"
Identifier "Configured Video Device"
Driver "vboxvideo"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
Section "InputDevice"
Identifier "vboxmouse"
Driver "vboxmouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "vboxmouse"
EndSectionBut nothing happens. I need to figure out how to build the mouse module manually I think. Where is xorg.0.log normally located?
Also, here is the uname and cat you requested:
$ uname -a
Linux box 3.0.21-tinycore #3021 SMP Sat Feb 18 11:54:11 EET 2012 i686 GNU/Linux
$ cat /etc/issue
Core Linux
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Mouse integration with Tiny Core Linux.
Normally I would expect to see the xorg.0.log in /var/log, but core does thing differently so I would search if it is not there.
In any regards it is going to be xorg related. VirtualBox uses X for all mouse functions especially concerning integration.
Since the mouse works even if it is not correct It has to be something that VirtualBox does not account for, especially since core is not a supported guest and there are certainly no VirtualBox guest additions for it so to speak.
One thing that might make a difference and could be causing some problems is the absolute mouse in the guest settings. If that is on it causes the OS to see a really old driver until you get the additions installed so the mouse will just work without using the host key to release the mouse. Disable it and see if it helps.
In any regards it is going to be xorg related. VirtualBox uses X for all mouse functions especially concerning integration.
Since the mouse works even if it is not correct It has to be something that VirtualBox does not account for, especially since core is not a supported guest and there are certainly no VirtualBox guest additions for it so to speak.
One thing that might make a difference and could be causing some problems is the absolute mouse in the guest settings. If that is on it causes the OS to see a really old driver until you get the additions installed so the mouse will just work without using the host key to release the mouse. Disable it and see if it helps.
Re: Mouse integration with Tiny Core Linux.
Here is the xorg.0.log you requested. I see the problem but I'm not sure how to fix it. The vboxmouse driver or module appear to be missing. I'm using a vbox package for tiny core, but the mouse drivers appear to be missing. Is there a way to add them manually?
Code: Select all
[ 357.875]
X.Org X Server 1.11.0
Release Date: 2011-08-26
[ 357.875] X Protocol Version 11, Revision 0
[ 357.875] Build Operating System: Linux 3.0.3-tinycore i686
[ 357.875] Current Operating System: Linux box 3.0.21-tinycore #3021 SMP Sat Feb 18 11:54:11 EET 2012 i686
[ 357.875] Kernel command line: initrd=/tce/boot/core.gz quiet tce=sda1 home=sda1 opt=sda1 local=sda1 noswap waitusb=5:UUID="38aed1be-f200-46f8-9cda-8b6476ea5903" tce=UUID="38aed1be-f200-46f8-9cda-8b6476ea5903" BOOT_IMAGE=/tce/boot/vmlinuz
[ 357.875] Build Date: 23 September 2011 05:05:20PM
[ 357.875]
[ 357.875] Current version of pixman: 0.30.0
[ 357.875] Before reporting problems, check www.tinycorelinux.com
to make sure that you have the latest version.
[ 357.875] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 357.875] (==) Log file: "/var/log/Xorg.0.log", Time: Sun May 26 07:21:53 2013
[ 357.875] (==) Using config file: "/etc/X11/xorg.conf"
[ 357.875] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
[ 357.876] (==) ServerLayout "Default Layout"
[ 357.876] (**) |-->Screen "Default Screen" (0)
[ 357.876] (**) | |-->Monitor "Configured Monitor"
[ 357.876] (**) | |-->Device "Configured Video Device"
[ 357.876] (**) |-->Input Device "vboxmouse"
[ 357.876] (==) Not automatically adding devices
[ 357.876] (==) Not automatically enabling devices
[ 357.876] (WW) The directory "/usr/lib/X11/fonts/TTF/" does not exist.
[ 357.876] Entry deleted from font path.
[ 357.876] (WW) The directory "/usr/lib/X11/fonts/OTF/" does not exist.
[ 357.876] Entry deleted from font path.
[ 357.876] (WW) The directory "/usr/lib/X11/fonts/Type1/" does not exist.
[ 357.876] Entry deleted from font path.
[ 357.876] (WW) The directory "/usr/lib/X11/fonts/100dpi/" does not exist.
[ 357.876] Entry deleted from font path.
[ 357.876] (==) FontPath set to:
/usr/lib/X11/fonts/misc/,
/usr/lib/X11/fonts/75dpi/
[ 357.876] (==) ModulePath set to "/usr/local/lib/X11/modules"
[ 357.876] (II) No default mouse found, adding one
[ 357.876] (**) |-->Input Device "<default pointer>"
[ 357.876] (==) |-->Input Device "<default keyboard>"
[ 357.876] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 357.876] (II) Loader magic: 0x818a5d0
[ 357.876] (II) Module ABI versions:
[ 357.876] X.Org ANSI C Emulation: 0.4
[ 357.876] X.Org Video Driver: 11.0
[ 357.876] X.Org XInput driver : 13.0
[ 357.876] X.Org Server Extension : 5.0
[ 357.878] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216
[ 357.878] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 357.878] (II) LoadModule: "extmod"
[ 357.878] (II) Loading /usr/local/lib/X11/modules/extensions/libextmod.so
[ 357.878] (II) Module extmod: vendor="X.Org Foundation"
[ 357.878] compiled for 1.11.0, module version = 1.0.0
[ 357.878] Module class: X.Org Server Extension
[ 357.878] ABI class: X.Org Server Extension, version 5.0
[ 357.878] (II) Loading extension MIT-SCREEN-SAVER
[ 357.878] (II) Loading extension XFree86-VidModeExtension
[ 357.878] (II) Loading extension XFree86-DGA
[ 357.878] (II) Loading extension DPMS
[ 357.878] (II) Loading extension XVideo
[ 357.878] (II) Loading extension XVideo-MotionCompensation
[ 357.878] (II) Loading extension X-Resource
[ 357.878] (II) LoadModule: "dbe"
[ 357.878] (II) Loading /usr/local/lib/X11/modules/extensions/libdbe.so
[ 357.879] (II) Module dbe: vendor="X.Org Foundation"
[ 357.879] compiled for 1.11.0, module version = 1.0.0
[ 357.879] Module class: X.Org Server Extension
[ 357.879] ABI class: X.Org Server Extension, version 5.0
[ 357.879] (II) Loading extension DOUBLE-BUFFER
[ 357.879] (II) LoadModule: "glx"
[ 357.879] (II) Loading /usr/local/lib/X11/modules/extensions/libglx.so
[ 357.879] (II) Module glx: vendor="X.Org Foundation"
[ 357.879] compiled for 1.11.0, module version = 1.0.0
[ 357.879] ABI class: X.Org Server Extension, version 5.0
[ 357.879] (==) AIGLX enabled
[ 357.879] (II) Loading extension GLX
[ 357.879] (II) LoadModule: "record"
[ 357.879] (II) Loading /usr/local/lib/X11/modules/extensions/librecord.so
[ 357.879] (II) Module record: vendor="X.Org Foundation"
[ 357.879] compiled for 1.11.0, module version = 1.13.0
[ 357.879] Module class: X.Org Server Extension
[ 357.879] ABI class: X.Org Server Extension, version 5.0
[ 357.879] (II) Loading extension RECORD
[ 357.879] (II) LoadModule: "dri"
[ 357.879] (II) Loading /usr/local/lib/X11/modules/extensions/libdri.so
[ 357.880] (II) Module dri: vendor="X.Org Foundation"
[ 357.883] compiled for 1.11.0, module version = 1.0.0
[ 357.883] ABI class: X.Org Server Extension, version 5.0
[ 357.883] (II) Loading extension XFree86-DRI
[ 357.883] (II) LoadModule: "dri2"
[ 357.883] (II) Loading /usr/local/lib/X11/modules/extensions/libdri2.so
[ 357.883] (II) Module dri2: vendor="X.Org Foundation"
[ 357.883] compiled for 1.11.0, module version = 1.2.0
[ 357.883] ABI class: X.Org Server Extension, version 5.0
[ 357.883] (II) Loading extension DRI2
[ 357.883] (II) LoadModule: "vboxvideo"
[ 357.884] (II) Loading /usr/local/lib/X11/modules/drivers/vboxvideo.so
[ 357.884] (II) Module vboxvideo: vendor="Oracle Corporation"
[ 357.884] compiled for 1.5.99.901, module version = 1.0.1
[ 357.884] Module class: X.Org Video Driver
[ 357.884] ABI class: X.Org Video Driver, version 11.0
[ 357.885] (**) Load address of symbol "VBOXVIDEO" is 0xb74686a0
[ 357.885] (II) LoadModule: "vboxmouse"
[ 357.885] (WW) Warning, couldn't open module vboxmouse
[ 357.885] (II) UnloadModule: "vboxmouse"
[ 357.885] (II) Unloading vboxmouse
[ 357.885] (EE) Failed to load module "vboxmouse" (module does not exist, 0)
[ 357.885] (II) LoadModule: "mouse"
[ 357.886] (II) Loading /usr/local/lib/X11/modules/input/mouse_drv.so
[ 357.886] (II) Module mouse: vendor="X.Org Foundation"
[ 357.886] compiled for 1.11.0, module version = 1.7.1
[ 357.886] Module class: X.Org XInput Driver
[ 357.886] ABI class: X.Org XInput driver, version 13.0
[ 357.886] (II) LoadModule: "kbd"
[ 357.886] (II) Loading /usr/local/lib/X11/modules/input/kbd_drv.so
[ 357.886] (II) Module kbd: vendor="X.Org Foundation"
[ 357.886] compiled for 1.11.0, module version = 1.6.0
[ 357.886] Module class: X.Org XInput Driver
[ 357.886] ABI class: X.Org XInput driver, version 13.0
[ 357.886] (II) VBoxVideo: guest driver for VirtualBox: vbox
[ 357.886] (--) using VT number 2
[ 357.899] (II) Loading /usr/local/lib/X11/modules/drivers/vboxvideo.so
[ 357.899] (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.1.18_OSE
[ 357.899] (II) Loading sub module "ramdac"
[ 357.899] (II) LoadModule: "ramdac"
[ 357.899] (II) Module "ramdac" already built-in
[ 357.899] (II) Loading sub module "fb"
[ 357.899] (II) LoadModule: "fb"
[ 357.899] (II) Loading /usr/local/lib/X11/modules/libfb.so
[ 357.899] (II) Module fb: vendor="X.Org Foundation"
[ 357.899] compiled for 1.11.0, module version = 1.0.0
[ 357.899] ABI class: X.Org ANSI C Emulation, version 0.4
[ 357.899] (II) Loading sub module "shadowfb"
[ 357.899] (II) LoadModule: "shadowfb"
[ 357.899] (II) Loading /usr/local/lib/X11/modules/libshadowfb.so
[ 357.899] (II) Module shadowfb: vendor="X.Org Foundation"
[ 357.900] compiled for 1.11.0, module version = 1.0.0
[ 357.900] ABI class: X.Org ANSI C Emulation, version 0.4
[ 357.900] (II) Loading sub module "vgahw"
[ 357.900] (II) LoadModule: "vgahw"
[ 357.900] (II) Loading /usr/local/lib/X11/modules/libvgahw.so
[ 357.900] (II) Module vgahw: vendor="X.Org Foundation"
[ 357.900] compiled for 1.11.0, module version = 0.1.0
[ 357.900] ABI class: X.Org Video Driver, version 11.0
[ 357.900] (II) Loading sub module "dri"
[ 357.900] (II) LoadModule: "dri"
[ 357.900] (II) Loading /usr/local/lib/X11/modules/extensions/libdri.so
[ 357.900] (II) Module dri: vendor="X.Org Foundation"
[ 357.900] compiled for 1.11.0, module version = 1.0.0
[ 357.900] ABI class: X.Org Server Extension, version 5.0
[ 357.900] (II) VBoxVideo(0): Creating default Display subsection in Screen section
"Default Screen" for depth/fbbpp 24/32
[ 357.900] (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
[ 357.900] (--) VBoxVideo(0): Virtual size is 32000x32000 (pitch 32000)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBoxInitialMode": 42.0 MHz (scaled from 0.0 MHz), 40.4 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBoxInitialMode"x0.0 42.02 1033 1035 1037 1039 668 670 672 674 (40.4 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 42.0 MHz (scaled from 0.0 MHz), 40.4 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 42.02 1033 1035 1037 1039 668 670 672 674 (40.4 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 42.0 MHz (scaled from 0.0 MHz), 40.4 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 42.02 1033 1035 1037 1039 668 670 672 674 (40.4 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBox-1600x1200": 116.2 MHz (scaled from 0.0 MHz), 72.4 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBox-1600x1200"x0.0 116.21 1600 1602 1604 1606 1200 1202 1204 1206 (72.4 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBox-1440x1050": 91.6 MHz (scaled from 0.0 MHz), 63.4 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBox-1440x1050"x0.0 91.62 1440 1442 1444 1446 1050 1052 1054 1056 (63.4 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBox-1280x960": 74.5 MHz (scaled from 0.0 MHz), 58.0 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBox-1280x960"x0.0 74.54 1280 1282 1284 1286 960 962 964 966 (58.0 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBox-1024x768": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBox-1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBox-800x600": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBox-800x600"x0.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
[ 357.900] (**) VBoxVideo(0): Built-in mode "VBox-640x480": 18.8 MHz (scaled from 0.0 MHz), 29.2 kHz, 60.0 Hz
[ 357.900] (II) VBoxVideo(0): Modeline "VBox-640x480"x0.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
[ 357.900] (II) VBoxVideo(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
[ 357.900] (==) VBoxVideo(0): RGB weight 888
[ 357.900] (==) VBoxVideo(0): Default visual is TrueColor
[ 357.900] (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
[ 357.900] (==) VBoxVideo(0): DPI set to (96, 96)
[ 357.900] (--) Depth 24 pixmap format is 32 bpp
[ 358.387] drmOpenDevice: node name is /dev/dri/card0
[ 358.388] drmOpenDevice: open result is 11, (OK)
[ 358.388] drmOpenDevice: node name is /dev/dri/card0
[ 358.388] drmOpenDevice: open result is 11, (OK)
[ 358.388] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 358.388] drmOpenDevice: node name is /dev/dri/card0
[ 358.388] drmOpenDevice: open result is 11, (OK)
[ 358.388] drmOpenByBusid: drmOpenMinor returns 11
[ 358.388] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 358.388] (II) [drm] DRM interface version 1.4
[ 358.388] (II) [drm] DRM open master succeeded.
[ 358.388] (II) VBoxVideo(0): [drm] Using the DRM lock SAREA also for drawables.
[ 358.388] (II) VBoxVideo(0): [drm] framebuffer handle = 0xe0000000
[ 358.388] (II) VBoxVideo(0): [drm] added 1 reserved context for kernel
[ 358.388] (II) VBoxVideo(0): X context handle = 0x1
[ 358.389] (II) VBoxVideo(0): [drm] installed DRM signal handler
[ 358.389] (II) VBoxVideo(0): visual configurations initialized
[ 358.389] (II) VBoxVideo(0): Requested monitor count: 1
[ 358.389] (II) VBoxVideo(0): Output VBOX0 using monitor section Configured Monitor
[ 358.389] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[ 358.389] (II) VBoxVideo(0): EDID for output VBOX0
[ 358.389] (II) VBoxVideo(0): Manufacturer: VBX Model: 0 Serial#: 43779081
[ 358.389] (II) VBoxVideo(0): Year: 1990 Week: 1
[ 358.389] (II) VBoxVideo(0): EDID Version: 1.3
[ 358.389] (II) VBoxVideo(0): Digital Display Input
[ 358.389] (II) VBoxVideo(0): Indeterminate output size
[ 358.389] (II) VBoxVideo(0): Gamma: 2.20
[ 358.389] (II) VBoxVideo(0): DPMS capabilities: StandBy Suspend Off
[ 358.389] (II) VBoxVideo(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 358.389] (II) VBoxVideo(0): Default color space is primary color space
[ 358.389] (II) VBoxVideo(0): First detailed timing is preferred mode
[ 358.389] (II) VBoxVideo(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 358.389] (II) VBoxVideo(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
[ 358.389] (II) VBoxVideo(0): Manufacturer's mask: 0
[ 358.389] (II) VBoxVideo(0): Supported detailed timing:
[ 358.389] (II) VBoxVideo(0): clock: 42.0 MHz Image Size: 0 x 0 mm
[ 358.389] (II) VBoxVideo(0): h_active: 1033 h_sync: 1035 h_sync_end 1037 h_blank_end 1039 h_border: 0
[ 358.389] (II) VBoxVideo(0): v_active: 668 v_sync: 670 v_sync_end 672 v_blanking: 674 v_border: 0
[ 358.389] (II) VBoxVideo(0): Ranges: V min: 0 V max: 200 Hz, H min: 0 H max: 200 kHz, PixClock max 1005 MHz
[ 358.389] (II) VBoxVideo(0): Monitor name: VBOX monitor
[ 358.389] (II) VBoxVideo(0): EDID (in hex):
[ 358.389] (II) VBoxVideo(0): 00ffffffffffff005858000009049c02
[ 358.389] (II) VBoxVideo(0): 0100010380000078eeee91a3544c9926
[ 358.389] (II) VBoxVideo(0): 0f505400000001010101010101010101
[ 358.389] (II) VBoxVideo(0): 01010101010169100906409c06200202
[ 358.389] (II) VBoxVideo(0): 2200000000000000000000fd0000c800
[ 358.389] (II) VBoxVideo(0): c864000a202020202020000000fc0056
[ 358.389] (II) VBoxVideo(0): 424f58206d6f6e69746f720a00000010
[ 358.389] (II) VBoxVideo(0): 000a202020202020202020202020000a
[ 358.389] (II) VBoxVideo(0): EDID vendor "VBX", prod id 0
[ 358.389] (II) VBoxVideo(0): DDCModeFromDetailedTiming: 1033x668 Warning: We only handle separate sync.
[ 358.389] (II) VBoxVideo(0): Using hsync ranges from config file
[ 358.389] (II) VBoxVideo(0): Using vrefresh ranges from config file
[ 358.389] (II) VBoxVideo(0): Printing DDC gathered Modelines:
[ 358.389] (II) VBoxVideo(0): Modeline "1033x668"x0.0 42.01 1033 1035 1037 1039 668 670 672 674 -hsync -vsync (40.4 kHz)
[ 358.390] (II) VBoxVideo(0): Printing probed modes for output VBOX0
[ 358.390] (II) VBoxVideo(0): Modeline "1033x668"x60.0 42.02 1033 1035 1037 1039 668 670 672 674 (40.4 kHz)
[ 358.390] (II) VBoxVideo(0): Modeline "1600x1200"x60.0 116.21 1600 1602 1604 1606 1200 1202 1204 1206 (72.4 kHz)
[ 358.390] (II) VBoxVideo(0): Modeline "1440x1050"x60.0 91.62 1440 1442 1444 1446 1050 1052 1054 1056 (63.4 kHz)
[ 358.390] (II) VBoxVideo(0): Modeline "1280x960"x60.0 74.54 1280 1282 1284 1286 960 962 964 966 (58.0 kHz)
[ 358.390] (II) VBoxVideo(0): Modeline "1024x768"x60.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 358.390] (II) VBoxVideo(0): Modeline "800x600"x60.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
[ 358.390] (II) VBoxVideo(0): Modeline "640x480"x60.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
[ 358.390] (II) VBoxVideo(0): Output VBOX0 connected
[ 358.390] (II) VBoxVideo(0): Using exact sizes for initial modes
[ 358.390] (II) VBoxVideo(0): Output VBOX0 using initial mode 1033x668
[ 358.390] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 358.390] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 358.391] (==) VBoxVideo(0): DPMS enabled
[ 358.391] (II) VBoxVideo(0): [DRI] installation complete
[ 358.391] (--) RandR disabled
[ 358.391] (II) Initializing built-in extension Generic Event Extension
[ 358.391] (II) Initializing built-in extension SHAPE
[ 358.391] (II) Initializing built-in extension MIT-SHM
[ 358.391] (II) Initializing built-in extension XInputExtension
[ 358.391] (II) Initializing built-in extension XTEST
[ 358.391] (II) Initializing built-in extension BIG-REQUESTS
[ 358.391] (II) Initializing built-in extension SYNC
[ 358.391] (II) Initializing built-in extension XKEYBOARD
[ 358.391] (II) Initializing built-in extension XC-MISC
[ 358.391] (II) Initializing built-in extension XINERAMA
[ 358.391] (II) Initializing built-in extension XFIXES
[ 358.391] (II) Initializing built-in extension RENDER
[ 358.391] (II) Initializing built-in extension RANDR
[ 358.391] (II) Initializing built-in extension COMPOSITE
[ 358.391] (II) Initializing built-in extension DAMAGE
[ 358.399] (II) AIGLX: Screen 0 is not DRI2 capable
[ 358.399] drmOpenDevice: node name is /dev/dri/card0
[ 358.399] drmOpenDevice: open result is 12, (OK)
[ 358.399] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 358.399] drmOpenDevice: node name is /dev/dri/card0
[ 358.399] drmOpenDevice: open result is 12, (OK)
[ 358.399] drmOpenByBusid: drmOpenMinor returns 12
[ 358.399] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 358.399] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 358.403] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
[ 358.403] (II) The file referenced, is *NOT* loaded
[ 358.403] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[ 358.403] (EE) AIGLX error: vboxvideo does not export required DRI extension
[ 358.404] (EE) AIGLX: reverting to software rendering
[ 358.408] (II) AIGLX: Loaded and initialized swrast
[ 358.408] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 358.408] (II) VBoxVideo(0): Setting screen physical size to 273 x 176
[ 358.444] (II) LoadModule: "vboxmouse"
[ 358.445] (WW) Warning, couldn't open module vboxmouse
[ 358.445] (II) UnloadModule: "vboxmouse"
[ 358.445] (II) Unloading vboxmouse
[ 358.445] (EE) Failed to load module "vboxmouse" (module does not exist, 0)
[ 358.445] (EE) No input driver matching `vboxmouse'
[ 358.445] (II) Using input driver 'mouse' for '<default pointer>'
[ 358.445] (II) Loading /usr/local/lib/X11/modules/input/mouse_drv.so
[ 358.446] (**) Option "AlwaysCore"
[ 358.446] (**) <default pointer>: always reports core events
[ 358.446] (WW) <default pointer>: No Device specified, looking for one...
[ 358.448] (II) <default pointer>: Setting Device option to "/dev/input/mice"
[ 358.448] (--) <default pointer>: Device: "/dev/input/mice"
[ 358.448] (==) <default pointer>: Protocol: "Auto"
[ 358.448] (**) <default pointer>: always reports core events
[ 358.448] (**) Option "Device" "/dev/input/mice"
[ 358.469] (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
[ 358.469] (**) <default pointer>: ZAxisMapping: buttons 4 and 5
[ 358.469] (**) <default pointer>: Buttons: 9
[ 358.469] (II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE, id 6)
[ 358.469] (**) <default pointer>: (accel) keeping acceleration scheme 1
[ 358.469] (**) <default pointer>: (accel) acceleration profile 0
[ 358.469] (**) <default pointer>: (accel) acceleration factor: 2.000
[ 358.469] (**) <default pointer>: (accel) acceleration threshold: 4
[ 358.469] (II) <default pointer>: Setting mouse protocol to "ExplorerPS/2"
[ 358.771] (II) <default pointer>: ps2EnableDataReporting: succeeded
[ 358.771] (II) Using input driver 'kbd' for '<default keyboard>'
[ 358.771] (II) Loading /usr/local/lib/X11/modules/input/kbd_drv.so
[ 358.771] (**) Option "CoreKeyboard"
[ 358.771] (**) <default keyboard>: always reports core events
[ 358.771] (**) <default keyboard>: always reports core events
[ 358.771] (**) Option "Protocol" "standard"
[ 358.771] (**) Option "XkbRules" "base"
[ 358.771] (**) Option "XkbModel" "pc105"
[ 358.771] (**) Option "XkbLayout" "us"
[ 358.771] (II) XINPUT: Adding extended input device "<default keyboard>" (type: KEYBOARD, id 7)
[ 358.791] (II) UnloadModule: "mouse"
[ 358.791] (II) Unloading mouse
[ 358.791] (II) UnloadModule: "kbd"
[ 358.791] (II) Unloading kbd
[ 358.797] (II) VBoxVideo(0): [drm] removed 1 reserved context for kernel
[ 358.797] (II) VBoxVideo(0): [drm] unmapping 8192 bytes of SAREA 0xf8464000 at 0xb67e7000
[ 358.797] (II) VBoxVideo(0): [drm] Closed DRM master.
[ 359.261] 1 XSELINUXs still allocated at reset
[ 359.261] SCREEN: 0 objects of 140 bytes = 0 total bytes 0 private allocs
[ 359.261] COLORMAP: 0 objects of 4 bytes = 0 total bytes 0 private allocs
[ 359.261] DEVICE: 0 objects of 64 bytes = 0 total bytes 0 private allocs
[ 359.261] CLIENT: 0 objects of 140 bytes = 0 total bytes 0 private allocs
[ 359.261] WINDOW: 0 objects of 28 bytes = 0 total bytes 0 private allocs
[ 359.261] PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
[ 359.261] GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs
[ 359.261] CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
[ 359.261] CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
[ 359.261] DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
[ 359.261] TOTAL: 1 objects, 8 bytes, 0 allocs
[ 359.261] 1 PIXMAPs still allocated at reset
[ 359.261] PIXMAP: 1 objects of 8 bytes = 8 total bytes 0 private allocs
[ 359.261] GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs
[ 359.261] CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs
[ 359.261] CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs
[ 359.261] DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
[ 359.261] TOTAL: 1 objects, 8 bytes, 0 allocs
[ 359.728] drmOpenDevice: node name is /dev/dri/card0
[ 359.728] drmOpenDevice: open result is 11, (OK)
[ 359.728] drmOpenDevice: node name is /dev/dri/card0
[ 359.728] drmOpenDevice: open result is 11, (OK)
[ 359.728] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 359.728] drmOpenDevice: node name is /dev/dri/card0
[ 359.728] drmOpenDevice: open result is 11, (OK)
[ 359.728] drmOpenByBusid: drmOpenMinor returns 11
[ 359.728] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 359.728] (II) [drm] DRM interface version 1.4
[ 359.728] (II) [drm] DRM open master succeeded.
[ 359.728] (II) VBoxVideo(0): [drm] Using the DRM lock SAREA also for drawables.
[ 359.728] (II) VBoxVideo(0): [drm] framebuffer handle = 0xe0000000
[ 359.728] (II) VBoxVideo(0): [drm] added 1 reserved context for kernel
[ 359.728] (II) VBoxVideo(0): X context handle = 0x1
[ 359.728] (II) VBoxVideo(0): [drm] installed DRM signal handler
[ 359.728] (II) VBoxVideo(0): visual configurations initialized
[ 359.728] (II) VBoxVideo(0): Requested monitor count: 1
[ 359.728] (II) VBoxVideo(0): Output VBOX0 using monitor section Configured Monitor
[ 359.728] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[ 359.728] (II) VBoxVideo(0): EDID for output VBOX0
[ 359.728] (II) VBoxVideo(0): Manufacturer: VBX Model: 0 Serial#: 43779081
[ 359.728] (II) VBoxVideo(0): Year: 1990 Week: 1
[ 359.728] (II) VBoxVideo(0): EDID Version: 1.3
[ 359.728] (II) VBoxVideo(0): Digital Display Input
[ 359.728] (II) VBoxVideo(0): Indeterminate output size
[ 359.728] (II) VBoxVideo(0): Gamma: 2.20
[ 359.728] (II) VBoxVideo(0): DPMS capabilities: StandBy Suspend Off
[ 359.728] (II) VBoxVideo(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 359.728] (II) VBoxVideo(0): Default color space is primary color space
[ 359.728] (II) VBoxVideo(0): First detailed timing is preferred mode
[ 359.728] (II) VBoxVideo(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 359.728] (II) VBoxVideo(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
[ 359.728] (II) VBoxVideo(0): Manufacturer's mask: 0
[ 359.728] (II) VBoxVideo(0): Supported detailed timing:
[ 359.728] (II) VBoxVideo(0): clock: 42.0 MHz Image Size: 0 x 0 mm
[ 359.728] (II) VBoxVideo(0): h_active: 1033 h_sync: 1035 h_sync_end 1037 h_blank_end 1039 h_border: 0
[ 359.728] (II) VBoxVideo(0): v_active: 668 v_sync: 670 v_sync_end 672 v_blanking: 674 v_border: 0
[ 359.728] (II) VBoxVideo(0): Ranges: V min: 0 V max: 200 Hz, H min: 0 H max: 200 kHz, PixClock max 1005 MHz
[ 359.728] (II) VBoxVideo(0): Monitor name: VBOX monitor
[ 359.728] (II) VBoxVideo(0): EDID (in hex):
[ 359.728] (II) VBoxVideo(0): 00ffffffffffff005858000009049c02
[ 359.728] (II) VBoxVideo(0): 0100010380000078eeee91a3544c9926
[ 359.728] (II) VBoxVideo(0): 0f505400000001010101010101010101
[ 359.728] (II) VBoxVideo(0): 01010101010169100906409c06200202
[ 359.728] (II) VBoxVideo(0): 2200000000000000000000fd0000c800
[ 359.728] (II) VBoxVideo(0): c864000a202020202020000000fc0056
[ 359.728] (II) VBoxVideo(0): 424f58206d6f6e69746f720a00000010
[ 359.728] (II) VBoxVideo(0): 000a202020202020202020202020000a
[ 359.728] (II) VBoxVideo(0): EDID vendor "VBX", prod id 0
[ 359.728] (II) VBoxVideo(0): DDCModeFromDetailedTiming: 1033x668 Warning: We only handle separate sync.
[ 359.728] (II) VBoxVideo(0): Using hsync ranges from config file
[ 359.728] (II) VBoxVideo(0): Using vrefresh ranges from config file
[ 359.728] (II) VBoxVideo(0): Printing DDC gathered Modelines:
[ 359.728] (II) VBoxVideo(0): Modeline "1033x668"x0.0 42.01 1033 1035 1037 1039 668 670 672 674 -hsync -vsync (40.4 kHz)
[ 359.729] (II) VBoxVideo(0): Not using built-in mode "1600x1200" (height too large for virtual size)
[ 359.729] (II) VBoxVideo(0): Not using built-in mode "1440x1050" (height too large for virtual size)
[ 359.729] (II) VBoxVideo(0): Not using built-in mode "1280x960" (height too large for virtual size)
[ 359.729] (II) VBoxVideo(0): Not using built-in mode "1024x768" (height too large for virtual size)
[ 359.729] (II) VBoxVideo(0): Printing probed modes for output VBOX0
[ 359.729] (II) VBoxVideo(0): Modeline "1033x668"x60.0 42.02 1033 1035 1037 1039 668 670 672 674 (40.4 kHz)
[ 359.729] (II) VBoxVideo(0): Modeline "800x600"x60.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
[ 359.729] (II) VBoxVideo(0): Modeline "640x480"x60.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
[ 359.729] (II) VBoxVideo(0): Output VBOX0 connected
[ 359.729] (II) VBoxVideo(0): Using exact sizes for initial modes
[ 359.729] (II) VBoxVideo(0): Output VBOX0 using initial mode 1033x668
[ 359.729] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 359.729] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 359.730] (==) VBoxVideo(0): DPMS enabled
[ 359.730] (II) VBoxVideo(0): [DRI] installation complete
[ 359.730] (--) RandR disabled
[ 359.740] (II) AIGLX: Screen 0 is not DRI2 capable
[ 359.740] drmOpenDevice: node name is /dev/dri/card0
[ 359.741] drmOpenDevice: open result is 12, (OK)
[ 359.741] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 359.741] drmOpenDevice: node name is /dev/dri/card0
[ 359.741] drmOpenDevice: open result is 12, (OK)
[ 359.741] drmOpenByBusid: drmOpenMinor returns 12
[ 359.741] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 359.741] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 359.745] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
[ 359.745] (II) The file referenced, is *NOT* loaded
[ 359.745] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[ 359.745] (EE) AIGLX error: vboxvideo does not export required DRI extension
[ 359.745] (EE) AIGLX: reverting to software rendering
[ 359.750] (II) AIGLX: Loaded and initialized swrast
[ 359.750] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 359.750] (II) VBoxVideo(0): Setting screen physical size to 273 x 176
[ 359.784] (II) LoadModule: "vboxmouse"
[ 359.785] (WW) Warning, couldn't open module vboxmouse
[ 359.785] (II) UnloadModule: "vboxmouse"
[ 359.785] (II) Unloading vboxmouse
[ 359.785] (EE) Failed to load module "vboxmouse" (module does not exist, 0)
[ 359.785] (EE) No input driver matching `vboxmouse'
[ 359.785] (II) Using input driver 'mouse' for '<default pointer>'
[ 359.785] (II) Loading /usr/local/lib/X11/modules/input/mouse_drv.so
[ 359.785] (**) Option "AlwaysCore"
[ 359.785] (**) <default pointer>: always reports core events
[ 359.785] (WW) <default pointer>: No Device specified, looking for one...
[ 359.791] (II) <default pointer>: Setting Device option to "/dev/input/mice"
[ 359.791] (--) <default pointer>: Device: "/dev/input/mice"
[ 359.791] (==) <default pointer>: Protocol: "Auto"
[ 359.791] (**) <default pointer>: always reports core events
[ 359.791] (**) Option "Device" "/dev/input/mice"
[ 359.811] (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
[ 359.811] (**) <default pointer>: ZAxisMapping: buttons 4 and 5
[ 359.811] (**) <default pointer>: Buttons: 9
[ 359.811] (**) <default pointer>: (accel) keeping acceleration scheme 1
[ 359.811] (**) <default pointer>: (accel) acceleration profile 0
[ 359.811] (**) <default pointer>: (accel) acceleration factor: 2.000
[ 359.811] (**) <default pointer>: (accel) acceleration threshold: 4
[ 359.811] (II) <default pointer>: Setting mouse protocol to "ExplorerPS/2"
[ 360.113] (II) <default pointer>: ps2EnableDataReporting: succeeded
[ 360.113] (II) Using input driver 'kbd' for '<default keyboard>'
[ 360.113] (II) Loading /usr/local/lib/X11/modules/input/kbd_drv.so
[ 360.113] (**) Option "CoreKeyboard"
[ 360.113] (**) <default keyboard>: always reports core events
[ 360.113] (**) <default keyboard>: always reports core events
[ 360.113] (**) Option "Protocol" "standard"
[ 360.113] (**) Option "XkbRules" "base"
[ 360.113] (**) Option "XkbModel" "pc105"
[ 360.113] (**) Option "XkbLayout" "us"
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Mouse integration with Tiny Core Linux.
Where do you get this package?I'm using a vbox package for tiny core,
Re: Mouse integration with Tiny Core Linux.
It came in the repository for Tiny Core, I assume it was created by someone who maintains Tiny Core. All the modules work "seamless, shared folders, etc" except the mouse, because the mouse module/drivers appear to be missing completely. Apparently disabling mouse intigration was good enough for the person who made the package. Should I focus on compiling a whole new setup? I was hoping there was a way to create just the mouse module/driver and add it to the existing setup I have.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Mouse integration with Tiny Core Linux.
I just did complete my investigation and yes the OSE additions are a port that a core maintainer has created. They would need to finish the rest as the mouse integration is scattered over various areas depending on the version of xorg and xf86 you need to use. Oh and the vboxvideo they have ported is not correct either, but that's another story.
Sorry to say it is between you and the core maintainer if you want to stick with core.
Sorry to say it is between you and the core maintainer if you want to stick with core.
Re: Mouse integration with Tiny Core Linux.
Drat. I was hoping there was something methodical I could do, like swap the different vboxmouse drivers until I found one that worked correctly. Unfortunately, there is little hope of the maintainer making a proper, working guest additions as he has confessed that he doesn't even use Virtualbox. Argh, this is frustrating. Tiny Core is PERFECT for my application. A VM that boots in seconds "Tiny Core" is a lot better then a VM that takes several minutes to boot "Fedora, Ubuntu, etc." when you only need to use 1 application.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Mouse integration with Tiny Core Linux.
Well the reason why the others take so long to boot ( I rarely need to wait more than 15 seconds myself by the way with Debian builds like Mint ) is what it takes to fully build the guest additions. The necessary packages are plenty and I am not even sure you can install all of the ones you would need on tiny core. Once compiled the guest additions could be installed on an original with only a few extra packages.
I will give it this it only takes 1 1/2 seconds to boot but limited with what it does, and I can't tell you how ticked off it makes me when a piece of software tells me I can't do something because it deems it wrong, which is another reason I don't run core.
I will give it this it only takes 1 1/2 seconds to boot but limited with what it does, and I can't tell you how ticked off it makes me when a piece of software tells me I can't do something because it deems it wrong, which is another reason I don't run core.