Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: Juanito on January 04, 2016, 08:29:34 AM
-
Team Tiny Core is pleased to announce that Tiny Core 7.0 Beta1 is available for public testing:
http://repo.tinycorelinux.net/7.x/x86/release_candidates/
http://repo.tinycorelinux.net/7.x/x86_64/release_candidates/
This is an beta level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.
Most extensions have been copied over from the 6.x repo - note that the alsa extensions have been refactored and updated and the Xorg-7.7 extensions have been updated.
We appreciate testing and feedback.
If you use distribution files note that you need a new vmlinuz and core.gz (or rootfs.gz + modules.gz)
Changelog for 7.0 beta1:
* busybox updated to 1.24.1
* kernel updated to 4.2.7
* glibc updated to 2.22
* gcc updated to 5.2.0
* e2fsprogs base libs/apps updated to 1.42.13
* util-linux base libs/apps updated to 2.27
Note that is one pending issue from alpha testing - that "crontab -e" works from the console, but not from a terminal window.
-
I have problems getting 3D to work. 2D works fine.
Netbook: MSI Wind U100
Integrated graphics: Intel 945GME
Doom through Zandronum and Diablo2 through WINE work quite well on 6.4.1 but on 7.0alpha1 and 7.0beta1 I get display errors as shown in attached screenshot.
After closing these programs I get this error in terminal
block already free
No idea what that means. Google indicates something related to DRM which I don't understand.
showbootcodes
logo.nologo splash cron quiet loglevel=3 vga=789 video=inteldrmfb:ywrap,mtrr:3 blacklist=pcmcia,ssb,b43,bcma,rt2860sta,bluetooth,btusb noutc tce=UUID="cb6f8b98-91fd-4c96-b115-3d2bb9cb3e57"/tce-7.x swapfile=sda1 nozswap laptop nodhcp desktop=openbox
I did try removing vga= and video= boot codes without change.
onboot.lst
Xorg-7.7-3d.tcz
Xorg-7.7-bin.tcz
Xorg-7.7-lib.tcz
glxgears.tcz
graphics-KERNEL.tcz
libva-intel-driver.tcz
xf86-video-intel.tcz
alsa-config.tcz
gzip.tcz
glibc_gconv.tcz
aterm.tcz
urxvt.tcz
pppd.tcz
iptables.tcz
vnstat.tcz
conky.tcz
xdg-utils.tcz
shared-mime-info.tcz
hicolor-icon-theme.tcz
gtk-engine-murrine.tcz
wbar.tcz
fbpanel.tcz
idesk.tcz
openbox.tcz
tint2-0.12.3.tcz
volumeicon-gtk2.tcz
xfe.tcz
Xprogs.tcz
I did try without libva-intel-driver.tcz which I think might not even be used on my system but no change.
lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
-
I think Xorg just kind of crashed. While browsing my files in Xfe, the hole display got heavily distorted but could be redrawn by minimizing some windows. Xfe couldn't draw any fonts anymore but Firefox continued to work.
Xorg.log attached containing some error messages.
EDIT:
dmesg might be interesting too:
[drm] stuck on render ring
[drm] GPU HANG: ecode 3:0:0x3cd5f8c1, in Xorg [3228], reason: Ring hung, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
i915: render error detected, EIR: 0x00000010
i915: page table error
i915: PGTBL_ER: 0x01000002
[drm:0xf8d570c1] *ERROR* EIR stuck: 0x00000010, masking
------------[ cut here ]------------
WARNING: CPU: 0 PID: 18654 at drivers/gpu/drm/i915/intel_display.c:3293 0xf8d6f639()
WARN_ON(ret)
Modules linked in: option usb_wwan usbserial ipt_REJECT nf_reject_ipv4 xt_conntrack xt_LOG nf_conntrack_ftp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack cpufreq_conservative cpufreq_stats cpufreq_powersave cpufreq_userspace i915 i2c_i801 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel drm_kms_helper snd_hda_codec drm snd_hwdep snd_hda_core snd_pcm snd_timer snd intel_agp intel_gtt soundcore i2c_algo_bit agpgart ums_realtek msi_wmi sparse_keymap wmi video backlight battery ac squashfs lz4_decompress pcspkr lpc_ich acpi_cpufreq r8169 mii loop
CPU: 0 PID: 18654 Comm: kworker/u4:0 Not tainted 4.2.7-tinycore #1999
Hardware name: MICRO-STAR INTERNATIONAL CO., LTD U90/U100/U90/U100, BIOS 4.6.3 12/01/2009
Workqueue: i915-hangcheck 0xf8d57253
00000000 c053bc01 f8dc0d75 c01392a6 f8d6f639 f48b0000 f5e55034 f5e55000
f48b0000 c01392df 00000009 c2c83dec f8dc0d75 c2c83e04 f8d6f639 f8dbe0ff
00000cdd f8dc0d75 01170000 f0170000 f5ea3ca0 f5e55208 f83040f1 00000000
Call Trace:
[<c053bc01>] ? 0xc053bc01
[<c01392a6>] ? 0xc01392a6
[<f8d6f639>] ? 0xf8d6f639
[<c01392df>] ? 0xc01392df
[<f8d6f639>] ? 0xf8d6f639
[<f83040f1>] ? 0xf83040f1
[<f8d5e436>] ? 0xf8d5e436
[<f8d709a8>] ? 0xf8d709a8
[<f8d5e436>] ? 0xf8d5e436
[<f8d70ac3>] ? 0xf8d70ac3
[<f8d571c7>] ? 0xf8d571c7
[<c01658f4>] ? 0xc01658f4
[<c0165a03>] ? 0xc0165a03
[<f8d5757e>] ? 0xf8d5757e
[<c014f042>] ? 0xc014f042
[<c0147348>] ? 0xc0147348
[<c01477d1>] ? 0xc01477d1
[<c0147628>] ? 0xc0147628
[<c014a8fd>] ? 0xc014a8fd
[<c012fbf7>] ? 0xc012fbf7
[<c053fdc1>] ? 0xc053fdc1
[<c014a881>] ? 0xc014a881
---[ end trace 08ea147f973a608c ]---
drm/i915: Resetting chip after gpu hang
-
Attached /sys/class/drm/card0/error .
-
That's still open upstream, nothing we can do:
https://bugs.freedesktop.org/show_bug.cgi?id=90841
-
Team Tiny Core is pleased to announce that Tiny Core 7.0 Beta1 is available for public testing:
http://repo.tinycorelinux.net/7.x/x86/release_candidates/
http://repo.tinycorelinux.net/7.x/x86_64/release_candidates/
This is an beta level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.
Most extensions have been copied over from the 6.x repo - note that the alsa extensions have been refactored and updated and the Xorg-7.7 extensions have been updated.
We appreciate testing and feedback.
If you use distribution files note that you need a new vmlinuz and core.gz (or rootfs.gz + modules.gz)
Changelog for 7.0 beta1:
* busybox updated to 1.24.1
* kernel updated to 4.2.7
* glibc updated to 2.22
* gcc updated to 5.2.0
* e2fsprogs base libs/apps updated to 1.42.13
* util-linux base libs/apps updated to 2.27
Note that is one pending issue from alpha testing - that "crontab -e" works from the console, but not from a terminal window.
Looking forward to testing!
#underliked
Sent from my HTC_0P6B6 using Tapatalk
-
I boot both tc-7beta1 and tc64pure-7beta1, but when I run "version" the output returns the same for either system
which is always "7.0beta1" Actually the only way i can tell for sure I'm running 64pure and not 64 is by verifying the modules in the repo..
Both systems work great however, thanks
-
You can use uname -m or uname -acommand to identify architecture.
-
Yes you could if you were running tc and tc64 but uname doesn't really help if you have boot options for both tc using 32bit user apps on vmlinuz64 and corepure64 as well as tc32.. then it gets a bit confusing is all.
give me a minute I'll check what version returns in tc6.x
ok I never noticed before but the same dilemma exists in tc-6.x also, I always thought corepure64 version returned something different.. but i was wrong
-
See getBuild in tc-functions.
-
getBuild, that's an interesting function..
However getBuild returns the same "x86_64" whether we are running core64 or corepure64, right..? ( I just tested it)
In scripts I use $(echo $MIRROR | grep -o 'x86_64') to determine if I'm booted to corepure64 or core64, but i'm talking about normal use.. where version nor uname doesn't really help the average tinycore user
I suspected version would provide a hint, but version returns only the version no irrespective if booted to core, core64 or corepure64
just a thought...
-
All my systems run solid and efficient with v7beta1 seems like we have a winner here
:D
-
@coreplayer2
Yes, that function correctly separates core64 from corepure64?
6.4.1 test:
(http://i.imgur.com/EvHVB57.png)
-
@ curaga
I hate it when you're right.. :p
core_x86
(https://db.tt/b2az6n7A)
core64
(https://db.tt/hrj9WNIb)
corepure64
(https://db.tt/pzhvs4vA)
Maybe it was operator error at 4am, on my part..?
I'm going to use getBuild in future thanks
-
Trying out the beta with my normal shtuff. The base looks great so far.
There are a couple of dep issues in the 7.x exttension repo:
qemu-common.tcz.dep references libcap-ng.tcz which is not present
SDL.tcs.dep references libmad.tcz which is not present.
Looks like xautolock-2.2 from the 4.x repo works in 7.x. I suppose it would work in 5.x and 6.x, too. :)
-
The mouse doesn't work in a VMware VM when booting from the ISO image. This appears to be an issue with the Xvesa extension. I can verify that it is available to the system by 'cat'ing /dev/input/event2 in the console, but specifiying the path using startx -- -mouse doesn't have any effect. I have tested this with VMware versions 9 with Nvidia host graphics and version 12 with ATI host graphics. I can't tell if the keyboard works while Xvesa is running, but it does work in the console. There is no X log to give any hints. I ran tc-install.sh from the command line and after rebooting ran tce-load -iw Xorg-7.7-3d to get to a working system so this confirms that the mouse does work with the Xorg extension in the same VM.
-
qemu-common.tcz.dep references libcap-ng.tcz which is not present
libcap-ng copied to tc-7.x repo - thanks.
SDL.tcs.dep references libmad.tcz which is not present.
Maybe I'm missing something, but libmad looks to be present in the tc-7.x repo to me?
Looks like xautolock-2.2 from the 4.x repo works in 7.x. I suppose it would work in 5.x and 6.x, too.
xautolock-2.2 copied to tc-5.x, 6.x and 7.x repos - thanks
-
The mouse doesn't work in a VMware VM when booting from the ISO image. This appears to be an issue with the Xvesa extension.
Is vmware meant to work with Xvesa?
Does vmware work with Xvesa in tc-6.x?
-
Since I don't recall having this same problem with TC 6.4.1, I'll say yes it worked. But now I have another problem. Open-vm-tools won't compile with gcc 5. Something about the new C++ ABI. I've tried setting the "old behavior" macros without success. In the process of building extensions for this new version, did this problem come up and was it successfully resolved?
-
gcc was compiled to support the old and new libstdc++ abi - I suppose the default is to compile for the new abi, but I haven't compiled any extensions yet where this came up...
-
Paldo has a patch for open-vm-tools:
https://www.mail-archive.com/pld-cvs-commit@lists.pld-linux.org/msg376377.html
-
I'm building open-vm-tools 10.x but the patch is for 9.x. Still there were a few hints in the patch that I could use so now I have the extension built and mostly working so thanks for the link. The problem at hand is that open-vm-tools 10.x now uses fuse for hgfs instead of a kernel module. This is good in that now open-vm-tools won't have any modules and should be a little more TC version independent. The bad part is that for a user to mount a shared folder /dev/fuse needs to have something other than 1600 permissions, like 1666. What can I do different (other than sudo) to mount the share without chmod'ing /dev/fuse?
-
The only other way is to have udev do the chmod, which requires remastering the udev rules (backup happens too late).
-
Maybe that's something for beta 2? ;D
-
The udev rules for fuse have it as 0666 but the file comes from the fuse extension. It looks like the fuse module is built into the kernel? If so shouldn't the udev rule already be in the master core.gz?
-
There is a udev rule for fuse in the base? Perhaps it needs to be removed from the extension then. I don't use fuse, would you like to investigate?
-
The udev rule is a link to the extension. I think it should be in the base if fuse is compiled into the kernel. I can't find the kernel config file on this website and there is no /proc/config.gz or module in an extension to create it so I can't say for sure. My hunch is based on fuse being in /proc/filesystems but there is no module in /proc/modules for it.
-
The relevant rules in the base are:
$ grep fuse /etc/udev/rules.d/*rules
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="fuse", ACTION=="add", MODE="0666", OPTIONS+="static_node=fuse", \
/etc/udev/rules.d/50-udev-default.rules: RUN+="/bin/mount -t fusectl fusectl /sys/fs/fuse/connections"
The rule in the fuse extension is: $ cat /usr/local/share/fuse/files/*fuse*
KERNEL=="fuse", MODE="0666"
The kernel config is at:
http://tinycorelinux.net/7.x/x86/release/src/kernel/
..not sure what you mean by "the udev rule is a link to the extension?
-
Thanks for the kernel config. It's post time is 6 and a half hours ahead of my current local time, so it's like looking into the future! ;D I'll need to spin up a clean VM to investigate the fuse issue more.
-
gold linker functionality added to binutils/gcc
To use: CC="gcc -fuse-ld=gold -flto -fuse-linker-plugin -march=i486 -mtune=i686 -Os -pipe" CXX="g++ -fuse-ld=gold -flto -fuse-linker-plugin -march=i486 -mtune=i686 -Os -pipe -fno-exceptions -fno-rtti" ./configure --blah-blah
-
What are the benefits offered by GOLD over LD?
-
It's meant to be faster, especially for large c++ apps
-
Gold also has a unique mode that can reduce size by some %. Add -Wl,--icf=safe to LDFLAGS. It works in addition to LTO.
edit: Added -Wl
-
Hmm - I just tried a test compiling qt5:
with gold
time make -j5 1h 19m 22s
without gold
time make -j5 1h 18m 57s
..not terribly convincing then :P
-
rt61pci fails because of missing rate control algorithm support in mac80211:
ieee80211 phy0: Failed to select rate control algorithm
Enabling "ministrel" in kernel config helps.
-
I'm not sure what was causing the problem with the permissions on /dev/fuse, but it seems to have resolved itself somehow. My current version of the latest open-vm-tools extension seems to be working OK now without having to change any permissions. My question is: if there is some other extension or process which is changing the permissions that I'm not currently seeing, would it still be OK as a matter of "just in case" to have the open-vm-tools startup script set the /dev/fuse permissions a+rw explicitly, or would that be "bad practice"? Once there is agreement then I can submit it.
-
Hi andyj
If another extension is incorrectly setting those permissions, finding the culprit would be the best course of action.
Fixing it in your extension will only serve to hide the problem with the possibility that it crops up under a different
scenario. Even worse would be if someone used the rouge script as a template while creating a new extension
thus propagating the problem.
-
So like I suspected it would be "bad practice". I'm not changing the permissions in the script now, so I'll just call it ready and submit it as is.
-
Hi andyj
If the problem pops up again, go to /usr/local/tce.installed and check any file that has a size greater than zero.
Another possibility might be a .rules file used by udev?
-
rt61pci fails because of missing rate control algorithm support in mac80211:
ieee80211 phy0: Failed to select rate control algorithm
Enabling "ministrel" in kernel config helps.
Thanks for the report. Will do a rebuild for the next version.
-
Am getting a memory error preparing to compile in tc-7 x86
ffmpeg-dev is already downloaded.
+ tce-load -i ffmpeg-dev
x264.tcz: OK
x264-dev.tcz: OK
libogg.tcz: OK
mount: mounting /dev/loop302 on /tmp/tcloop/libogg-dev failed: Cannot allocate memory
While this error appears to indicate an out of memory issue, I'm wondering if there is a limit on loop mount's ? because df -H doesn't show an out of memory issue.
Maybe df is not the right tool.?
tc@box:~$ df -H
Filesystem Size Used Avail Use% Mounted on
rootfs 3.4G 20M 3.3G 1% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
/dev/sda2 236G 8.9G 215G 4% /opt
/dev/loop0 132k 132k 0 100% /tmp/tcloop/aterm
/dev/loop1 95k 95k 0 100% /tmp/tcloop/libpng
/dev/loop2 119k 119k 0 100% /tmp/tcloop/libjpeg-turbo
/dev/loop3 8.2k 8.2k 0 100% /tmp/tcloop/libXdmcp
/dev/loop4 8.2k 8.2k 0 100% /tmp/tcloop/libXau
/dev/loop5 234k 234k 0 100% /tmp/tcloop/libxcb
/dev/loop6 914k 914k 0 100% /tmp/tcloop/libX11
/dev/loop7 25k 25k 0 100% /tmp/tcloop/libXext
/dev/loop8 451k 451k 0 100% /tmp/tcloop/fltk-1.3
/dev/loop9 275k 275k 0 100% /tmp/tcloop/freetype
/dev/loop10 181k 181k 0 100% /tmp/tcloop/imlib2
/dev/loop11 58k 58k 0 100% /tmp/tcloop/imlib2-bin
/dev/loop12 13k 13k 0 100% /tmp/tcloop/libfontenc
/dev/loop13 41k 41k 0 100% /tmp/tcloop/libICE
/dev/loop14 13k 13k 0 100% /tmp/tcloop/libSM
/dev/loop15 107k 107k 0 100% /tmp/tcloop/libXfont
/dev/loop16 25k 25k 0 100% /tmp/tcloop/libXi
/dev/loop17 148k 148k 0 100% /tmp/tcloop/libXt
/dev/loop18 46k 46k 0 100% /tmp/tcloop/libXmu
/dev/loop19 46k 46k 0 100% /tmp/tcloop/libXpm
/dev/loop20 17k 17k 0 100% /tmp/tcloop/libXrender
/dev/loop21 17k 17k 0 100% /tmp/tcloop/libXrandr
/dev/loop22 37k 37k 0 100% /tmp/tcloop/wbar
/dev/loop23 1.3M 1.3M 0 100% /tmp/tcloop/Xlibs
/dev/loop24 115k 115k 0 100% /tmp/tcloop/Xprogs
/dev/loop25 365k 365k 0 100% /tmp/tcloop/Xvesa
/dev/loop26 132k 132k 0 100% /tmp/tcloop/gamin
/dev/loop27 70k 70k 0 100% /tmp/tcloop/xdg-utils
/dev/loop28 8.2k 8.2k 0 100% /tmp/tcloop/libattr
/dev/loop29 25k 25k 0 100% /tmp/tcloop/libcap
/dev/loop30 197k 197k 0 100% /tmp/tcloop/gmp
/dev/loop31 21k 21k 0 100% /tmp/tcloop/attr
/dev/loop32 46k 46k 0 100% /tmp/tcloop/acl
/dev/loop33 1.7M 1.7M 0 100% /tmp/tcloop/coreutils
/dev/loop34 21k 21k 0 100% /tmp/tcloop/libpci
/dev/loop35 271k 271k 0 100% /tmp/tcloop/pci-utils
/dev/loop36 17k 17k 0 100% /tmp/tcloop/libffi
/dev/loop37 1.5M 1.5M 0 100% /tmp/tcloop/glib2
/dev/loop38 37k 37k 0 100% /tmp/tcloop/udev-lib
/dev/loop39 46k 46k 0 100% /tmp/tcloop/libusb
/dev/loop40 246k 246k 0 100% /tmp/tcloop/usbutils
/dev/loop41 148k 148k 0 100% /tmp/tcloop/udev-extra
/dev/loop42 238k 238k 0 100% /tmp/tcloop/ncurses
/dev/loop43 111k 111k 0 100% /tmp/tcloop/readline
/dev/loop44 316k 316k 0 100% /tmp/tcloop/bash
/dev/loop45 74k 74k 0 100% /tmp/tcloop/liblzma
/dev/loop46 680k 680k 0 100% /tmp/tcloop/libxml2
/dev/loop47 467k 467k 0 100% /tmp/tcloop/shared-mime-info
/dev/loop48 8.2k 8.2k 0 100% /tmp/tcloop/hicolor-icon-theme
/dev/loop49 54k 54k 0 100% /tmp/tcloop/desktop-file-utils
/dev/loop50 17k 17k 0 100% /tmp/tcloop/libstartup-notification
/dev/loop51 70k 70k 0 100% /tmp/tcloop/expat2
/dev/loop52 148k 148k 0 100% /tmp/tcloop/fontconfig
/dev/loop53 33k 33k 0 100% /tmp/tcloop/libXft
/dev/loop54 152k 152k 0 100% /tmp/tcloop/harfbuzz
/dev/loop55 4.1k 4.1k 0 100% /tmp/tcloop/libxshmfence
/dev/loop56 17k 17k 0 100% /tmp/tcloop/libpciaccess
/dev/loop57 119k 119k 0 100% /tmp/tcloop/libdrm
/dev/loop58 8.2k 8.2k 0 100% /tmp/tcloop/libXxf86vm
/dev/loop59 8.2k 8.2k 0 100% /tmp/tcloop/libXfixes
/dev/loop60 4.1k 4.1k 0 100% /tmp/tcloop/libXdamage
/dev/loop61 189k 189k 0 100% /tmp/tcloop/libGL
/dev/loop62 50k 50k 0 100% /tmp/tcloop/libEGL
/dev/loop63 267k 267k 0 100% /tmp/tcloop/pixman
/dev/loop64 537k 537k 0 100% /tmp/tcloop/cairo
/dev/loop65 222k 222k 0 100% /tmp/tcloop/pango
/dev/loop66 4.1k 4.1k 0 100% /tmp/tcloop/libXinerama
/dev/loop67 17k 17k 0 100% /tmp/tcloop/libXcursor
/dev/loop68 4.1k 4.1k 0 100% /tmp/tcloop/libXcomposite
/dev/loop69 185k 185k 0 100% /tmp/tcloop/libtiff
/dev/loop70 189k 189k 0 100% /tmp/tcloop/gdk-pixbuf2
/dev/loop71 50k 50k 0 100% /tmp/tcloop/atk
/dev/loop72 2.6M 2.6M 0 100% /tmp/tcloop/gtk2
/dev/loop73 705k 705k 0 100% /tmp/tcloop/spacefm
/dev/loop74 62k 62k 0 100% /tmp/tcloop/libxkbfile
/dev/loop75 8.2k 8.2k 0 100% /tmp/tcloop/libdmx
/dev/loop76 8.2k 8.2k 0 100% /tmp/tcloop/libXxf86dga
/dev/loop77 8.2k 8.2k 0 100% /tmp/tcloop/libXv
/dev/loop78 13k 13k 0 100% /tmp/tcloop/libXvmc
/dev/loop79 8.2k 8.2k 0 100% /tmp/tcloop/libXtst
/dev/loop80 4.1k 4.1k 0 100% /tmp/tcloop/libXss
/dev/loop81 4.1k 4.1k 0 100% /tmp/tcloop/libXres
/dev/loop82 279k 279k 0 100% /tmp/tcloop/libXaw
/dev/loop83 21k 21k 0 100% /tmp/tcloop/libFS
/dev/loop84 369k 369k 0 100% /tmp/tcloop/hackedbox
/dev/loop85 349k 349k 0 100% /tmp/tcloop/libasound
/dev/loop86 111k 111k 0 100% /tmp/tcloop/input-joystick-4.2.7-tinycore
/dev/loop87 2.0M 2.0M 0 100% /tmp/tcloop/alsa-modules-4.2.7-tinycore
/dev/loop88 201k 201k 0 100% /tmp/tcloop/alsa
/dev/loop89 951k 951k 0 100% /tmp/tcloop/alsa-config
/dev/loop90 459k 459k 0 100% /tmp/tcloop/sqlite3
/dev/loop91 136k 136k 0 100% /tmp/tcloop/nspr
/dev/loop92 1.5M 1.5M 0 100% /tmp/tcloop/nss
/dev/loop93 1.9M 1.9M 0 100% /tmp/tcloop/openssl
/dev/loop94 21k 21k 0 100% /tmp/tcloop/libgpg-error
/dev/loop95 402k 402k 0 100% /tmp/tcloop/libgcrypt
/dev/loop96 91k 91k 0 100% /tmp/tcloop/libssh2
/dev/loop97 78k 78k 0 100% /tmp/tcloop/libidn
/dev/loop98 279k 279k 0 100% /tmp/tcloop/curl
/dev/loop99 8.2M 8.2M 0 100% /tmp/tcloop/flash11
/dev/loop100 406k 406k 0 100% /tmp/tcloop/dbus
/dev/loop101 87k 87k 0 100% /tmp/tcloop/at-spi2-core
/dev/loop102 54k 54k 0 100% /tmp/tcloop/at-spi2-atk
/dev/loop103 193k 193k 0 100% /tmp/tcloop/libepoxy
/dev/loop104 2.8M 2.8M 0 100% /tmp/tcloop/gtk3
/dev/loop105 115k 115k 0 100% /tmp/tcloop/l3afpad
/dev/loop106 365k 365k 0 100% /tmp/tcloop/mtd-4.2.7-tinycore
/dev/loop107 1.4M 1.4M 0 100% /tmp/tcloop/filesystems-4.2.7-tinycore
/dev/loop108 29k 29k 0 100% /tmp/tcloop/keyutils
/dev/loop109 1.2M 1.2M 0 100% /tmp/tcloop/krb5
/dev/loop110 66k 66k 0 100% /tmp/tcloop/samba3-libs
/dev/loop111 58k 58k 0 100% /tmp/tcloop/cifs-utils
/dev/loop112 13k 13k 0 100% /tmp/tcloop/NAS-Connect
/dev/loop113 95k 95k 0 100% /tmp/tcloop/dbus-glib
/dev/loop114 62M 62M 0 100% /tmp/tcloop/firefox
/dev/loop115 242k 242k 0 100% /tmp/tcloop/ace-of-penguins
/dev/loop116 4.1k 4.1k 0 100% /tmp/tcloop/solitaire-freecell
/dev/loop117 369k 369k 0 100% /tmp/tcloop/ttf-bitstream-vera
/dev/loop118 54k 54k 0 100% /tmp/tcloop/libglade
/dev/loop119 66k 66k 0 100% /tmp/tcloop/gdbm
/dev/loop120 29k 29k 0 100% /tmp/tcloop/bzip2-lib
/dev/loop121 8.0M 8.0M 0 100% /tmp/tcloop/python
/dev/loop122 29k 29k 0 100% /tmp/tcloop/pycairo
/dev/loop123 13k 13k 0 100% /tmp/tcloop/libffi5
/dev/loop124 2.2M 2.2M 0 100% /tmp/tcloop/gobject-introspection
/dev/loop125 508k 508k 0 100% /tmp/tcloop/pygobject
/dev/loop126 1.2M 1.2M 0 100% /tmp/tcloop/pygtk
/dev/loop127 336k 336k 0 100% /tmp/tcloop/libxslt
/dev/loop128 652k 652k 0 100% /tmp/tcloop/meld
/dev/loop129 988k 988k 0 100% /tmp/tcloop/e2fsprogs
/dev/loop130 775k 775k 0 100% /tmp/tcloop/gcc_libs
/dev/loop131 1.6M 1.6M 0 100% /tmp/tcloop/gettext
/dev/loop132 14M 14M 0 100% /tmp/tcloop/perl5
/dev/loop133 234k 234k 0 100% /tmp/tcloop/perl_xml_parser
/dev/loop134 54k 54k 0 100% /tmp/tcloop/intltool
/dev/loop135 29k 29k 0 100% /tmp/tcloop/popt
/dev/loop136 185k 185k 0 100% /tmp/tcloop/rsync
/dev/loop137 365k 365k 0 100% /tmp/tcloop/file
/dev/loop138 82k 82k 0 100% /tmp/tcloop/grsync
/dev/loop139 3.0M 3.0M 0 100% /tmp/tcloop/glibc_gconv
/dev/loop140 181k 181k 0 100% /tmp/tcloop/mtools
/dev/loop141 58k 58k 0 100% /tmp/tcloop/dosfstools
/dev/loop142 476k 476k 0 100% /tmp/tcloop/ntfsprogs
/dev/loop143 193k 193k 0 100% /tmp/tcloop/pango-gir
/dev/loop144 177k 177k 0 100% /tmp/tcloop/atk-gir
/dev/loop145 91k 91k 0 100% /tmp/tcloop/at-spi2-core-gir
/dev/loop146 54k 54k 0 100% /tmp/tcloop/gdk-pixbuf2-gir
/dev/loop147 2.0M 2.0M 0 100% /tmp/tcloop/gtk3-gir
/dev/loop148 70k 70k 0 100% /tmp/tcloop/libpeas
/dev/loop149 29k 29k 0 100% /tmp/tcloop/libpeas-gir
/dev/loop150 91k 91k 0 100% /tmp/tcloop/libcroco
/dev/loop151 119k 119k 0 100% /tmp/tcloop/librsvg
/dev/loop152 177k 177k 0 100% /tmp/tcloop/lcms2
/dev/loop153 87k 87k 0 100% /tmp/tcloop/libexif
/dev/loop154 132k 132k 0 100% /tmp/tcloop/gsettings-desktop-schemas
/dev/loop155 103k 103k 0 100% /tmp/tcloop/gnome-desktop
/dev/loop156 10M 10M 0 100% /tmp/tcloop/gnome-icon-theme
/dev/loop157 82k 82k 0 100% /tmp/tcloop/dconf
/dev/loop158 320k 320k 0 100% /tmp/tcloop/eog
/dev/loop159 50k 50k 0 100% /tmp/tcloop/eog-gir
/dev/loop160 13k 13k 0 100% /tmp/tcloop/grabber
/dev/loop161 54k 54k 0 100% /tmp/tcloop/xzgv
/dev/loop162 512k 512k 0 100% /tmp/tcloop/netfilter-4.2.7-tinycore
/dev/loop163 459k 459k 0 100% /tmp/tcloop/iptables
/dev/loop164 5.0M 5.0M 0 100% /tmp/tcloop/git
/dev/loop165 58k 58k 0 100% /tmp/tcloop/grep
/dev/loop166 4.1k 4.1k 0 100% /tmp/tcloop/sstrip
/dev/loop167 82k 82k 0 100% /tmp/tcloop/zsync
/dev/loop168 181k 181k 0 100% /tmp/tcloop/wget
/dev/loop169 95k 95k 0 100% /tmp/tcloop/squashfs-tools
/dev/loop170 123k 123k 0 100% /tmp/tcloop/diffutils
/dev/loop171 21k 21k 0 100% /tmp/tcloop/submitqc
/dev/loop172 4.1k 4.1k 0 100% /tmp/tcloop/buildtcz
/dev/loop173 50k 50k 0 100% /tmp/tcloop/xz
/dev/loop174 41k 41k 0 100% /tmp/tcloop/zlib_base-dev
/dev/loop175 8.2k 8.2k 0 100% /tmp/tcloop/util-linux_base-dev
/dev/loop176 1.4M 1.4M 0 100% /tmp/tcloop/linux-4.2.1_api_headers
/dev/loop177 2.6M 2.6M 0 100% /tmp/tcloop/glibc_base-dev
/dev/loop178 50k 50k 0 100% /tmp/tcloop/e2fsprogs_base-dev
/dev/loop179 29k 29k 0 100% /tmp/tcloop/sed
/dev/loop180 50k 50k 0 100% /tmp/tcloop/pkg-config
/dev/loop181 70k 70k 0 100% /tmp/tcloop/patch
/dev/loop182 91k 91k 0 100% /tmp/tcloop/make
/dev/loop183 54k 54k 0 100% /tmp/tcloop/m4
/dev/loop184 164k 164k 0 100% /tmp/tcloop/mpfr
/dev/loop185 41k 41k 0 100% /tmp/tcloop/mpc
/dev/loop186 680k 680k 0 100% /tmp/tcloop/isl
/dev/loop187 82k 82k 0 100% /tmp/tcloop/cloog
/dev/loop188 3.9M 3.9M 0 100% /tmp/tcloop/binutils
/dev/loop189 1.3M 1.3M 0 100% /tmp/tcloop/gcc_libs-dev
/dev/loop190 918k 918k 0 100% /tmp/tcloop/gcc_base-dev
/dev/loop191 29M 29M 0 100% /tmp/tcloop/gcc
/dev/loop192 295k 295k 0 100% /tmp/tcloop/gawk
/dev/loop193 107k 107k 0 100% /tmp/tcloop/flex
/dev/loop194 164k 164k 0 100% /tmp/tcloop/findutils
/dev/loop195 316k 316k 0 100% /tmp/tcloop/bison
/dev/loop196 4.1k 4.1k 0 100% /tmp/tcloop/compiletc
/dev/loop197 4.1k 4.1k 0 100% /tmp/tcloop/libxshmfence-dev
/dev/loop198 13k 13k 0 100% /tmp/tcloop/udev-dev
/dev/loop199 132k 132k 0 100% /tmp/tcloop/libdrm-dev
/dev/loop200 291k 291k 0 100% /tmp/tcloop/libGL-dev
/dev/loop201 8.2k 8.2k 0 100% /tmp/tcloop/libGLESv2
/dev/loop202 50k 50k 0 100% /tmp/tcloop/libGLESv2-dev
/dev/loop203 66k 66k 0 100% /tmp/tcloop/liblzma-dev
/dev/loop204 41k 41k 0 100% /tmp/tcloop/bzip2
/dev/loop205 4.1k 4.1k 0 100% /tmp/tcloop/bzip2-dev
/dev/loop206 590k 590k 0 100% /tmp/tcloop/elfutils
/dev/loop207 345k 345k 0 100% /tmp/tcloop/elfutils-dev
/dev/loop208 4.1k 4.1k 0 100% /tmp/tcloop/libXdmcp-dev
/dev/loop209 435k 435k 0 100% /tmp/tcloop/libxcb-dev
/dev/loop210 70k 70k 0 100% /tmp/tcloop/libX11-dev
/dev/loop211 25k 25k 0 100% /tmp/tcloop/libXext-dev
/dev/loop212 21k 21k 0 100% /tmp/tcloop/libvdpau
/dev/loop213 62k 62k 0 100% /tmp/tcloop/libvdpau-dev
/dev/loop214 2.3M 2.3M 0 100% /tmp/tcloop/ncurses-dev
/dev/loop215 25k 25k 0 100% /tmp/tcloop/libffi-dev
/dev/loop216 5.8M 5.8M 0 100% /tmp/tcloop/llvm-lib
/dev/loop217 1.4M 1.4M 0 100% /tmp/tcloop/llvm-bin
/dev/loop218 2.9M 2.9M 0 100% /tmp/tcloop/llvm-dev
/dev/loop219 37k 37k 0 100% /tmp/tcloop/util-macros
/dev/loop220 701k 701k 0 100% /tmp/tcloop/xorg-proto
/dev/loop221 13k 13k 0 100% /tmp/tcloop/pixman-dev
/dev/loop222 2.1M 2.1M 0 100% /tmp/tcloop/openssl-dev
/dev/loop223 21k 21k 0 100% /tmp/tcloop/expat2-dev
/dev/loop224 218k 218k 0 100% /tmp/tcloop/libepoxy-dev
/dev/loop225 545k 545k 0 100% /tmp/tcloop/freetype-dev
/dev/loop226 25k 25k 0 100% /tmp/tcloop/libXfont-dev
/dev/loop227 29k 29k 0 100% /tmp/tcloop/libEGL-dev
/dev/loop228 2.6M 2.6M 0 100% /tmp/tcloop/xorg-server
/dev/loop229 381k 381k 0 100% /tmp/tcloop/xorg-server-dev
/dev/loop230 70k 70k 0 100% /tmp/tcloop/xtrans
/dev/loop231 29k 29k 0 100% /tmp/tcloop/xbitmaps
/dev/loop232 17k 17k 0 100% /tmp/tcloop/libxkbfile-dev
/dev/loop233 8.2k 8.2k 0 100% /tmp/tcloop/libpciaccess-dev
/dev/loop234 4.1k 4.1k 0 100% /tmp/tcloop/libXxf86vm-dev
/dev/loop235 13k 13k 0 100% /tmp/tcloop/libXxf86dga-dev
/dev/loop236 4.1k 4.1k 0 100% /tmp/tcloop/libXv-dev
/dev/loop237 4.1k 4.1k 0 100% /tmp/tcloop/libXvmc-dev
/dev/loop238 17k 17k 0 100% /tmp/tcloop/libXi-dev
/dev/loop239 13k 13k 0 100% /tmp/tcloop/libXtst-dev
/dev/loop240 8.2k 8.2k 0 100% /tmp/tcloop/libXss-dev
/dev/loop241 4.1k 4.1k 0 100% /tmp/tcloop/libXres-dev
/dev/loop242 8.2k 8.2k 0 100% /tmp/tcloop/libXrender-dev
/dev/loop243 8.2k 8.2k 0 100% /tmp/tcloop/libXrandr-dev
/dev/loop244 8.2k 8.2k 0 100% /tmp/tcloop/libXinerama-dev
/dev/loop245 13k 13k 0 100% /tmp/tcloop/fontconfig-dev
/dev/loop246 8.2k 8.2k 0 100% /tmp/tcloop/libXft-dev
/dev/loop247 13k 13k 0 100% /tmp/tcloop/libXfixes-dev
/dev/loop248 8.2k 8.2k 0 100% /tmp/tcloop/libXdamage-dev
/dev/loop249 25k 25k 0 100% /tmp/tcloop/libXcursor-dev
/dev/loop250 8.2k 8.2k 0 100% /tmp/tcloop/libXcomposite-dev
/dev/loop251 8.2k 8.2k 0 100% /tmp/tcloop/libXpm-dev
/dev/loop252 17k 17k 0 100% /tmp/tcloop/libICE-dev
/dev/loop253 87k 87k 0 100% /tmp/tcloop/libXt-dev
/dev/loop254 29k 29k 0 100% /tmp/tcloop/libXmu-dev
/dev/loop255 127k 127k 0 100% /tmp/tcloop/libXaw-dev
/dev/loop256 33k 33k 0 100% /tmp/tcloop/libFS-dev
/dev/loop257 13k 13k 0 100% /tmp/tcloop/makedepend
/dev/loop258 725k 725k 0 100% /tmp/tcloop/xkeyboard-config
/dev/loop259 13k 13k 0 100% /tmp/tcloop/xf86-video-vesa
/dev/loop260 37k 37k 0 100% /tmp/tcloop/libevdev
/dev/loop261 13k 13k 0 100% /tmp/tcloop/mtdev
/dev/loop262 25k 25k 0 100% /tmp/tcloop/xf86-input-evdev
/dev/loop263 545k 545k 0 100% /tmp/tcloop/xcursor-themes
/dev/loop264 1.7M 1.7M 0 100% /tmp/tcloop/Xorg-fonts
/dev/loop265 451k 451k 0 100% /tmp/tcloop/Xorg-7.7-bin
/dev/loop266 8.9M 8.9M 0 100% /tmp/tcloop/Xorg-7.7-3d
/dev/loop267 62k 62k 0 100% /tmp/tcloop/Xorg-7.7-3d-dev
/dev/loop268 9.3M 9.3M 0 100% /tmp/tcloop/cmake
/dev/loop269 742k 742k 0 100% /tmp/tcloop/autoconf
/dev/loop270 521k 521k 0 100% /tmp/tcloop/automake
/dev/loop271 132k 132k 0 100% /tmp/tcloop/gamin-dev
/dev/loop272 7.2M 7.2M 0 100% /tmp/tcloop/glib2-dev
/dev/loop273 25k 25k 0 100% /tmp/tcloop/libpng-bin
/dev/loop274 66k 66k 0 100% /tmp/tcloop/libpng-dev
/dev/loop275 58k 58k 0 100% /tmp/tcloop/cairo-dev
/dev/loop276 213k 213k 0 100% /tmp/tcloop/harfbuzz-dev
/dev/loop277 316k 316k 0 100% /tmp/tcloop/pango-dev
/dev/loop278 62k 62k 0 100% /tmp/tcloop/libglade-dev
/dev/loop279 1.1M 1.1M 0 100% /tmp/tcloop/tcl
/dev/loop280 771k 771k 0 100% /tmp/tcloop/tk
/dev/loop281 95k 95k 0 100% /tmp/tcloop/tcl-dev
/dev/loop282 50k 50k 0 100% /tmp/tcloop/tk-dev
/dev/loop283 25k 25k 0 100% /tmp/tcloop/readline-dev
/dev/loop284 8.2k 8.2k 0 100% /tmp/tcloop/gdbm-dev
/dev/loop285 615k 615k 0 100% /tmp/tcloop/sqlite3-dev
/dev/loop286 148k 148k 0 100% /tmp/tcloop/python-dev
/dev/loop287 4.1k 4.1k 0 100% /tmp/tcloop/pycairo-dev
/dev/loop288 390k 390k 0 100% /tmp/tcloop/gobject-introspection-dev
/dev/loop289 181k 181k 0 100% /tmp/tcloop/pygobject-dev
/dev/loop290 246k 246k 0 100% /tmp/tcloop/pygtk-dev
/dev/loop291 115k 115k 0 100% /tmp/tcloop/alsa-dev
/dev/loop292 816k 816k 0 100% /tmp/tcloop/libva
/dev/loop293 111k 111k 0 100% /tmp/tcloop/libva-dev
/dev/loop294 1.7M 1.7M 0 100% /tmp/tcloop/libjpeg-turbo-dev
/dev/loop295 107k 107k 0 100% /tmp/tcloop/i2c-4.2.7-tinycore
/dev/loop296 3.1M 3.1M 0 100% /tmp/tcloop/v4l-dvb-4.2.7-tinycore
/dev/loop297 410k 410k 0 100% /tmp/tcloop/libv4l
/dev/loop298 115k 115k 0 100% /tmp/tcloop/libv4l-dev
/dev/loop299 390k 390k 0 100% /tmp/tcloop/x264
/dev/loop300 21k 21k 0 100% /tmp/tcloop/x264-dev
/dev/loop301 13k 13k 0 100% /tmp/tcloop/libogg
tc@box:~$
-
There shouldn't be, and you have 4GB ram too. Fragmentation could cause that, but it's strange with so much free memory. Anything in dmesg? free -m?
-
The udev rules look ok, and I grep'ped for fuse in /etc, tce.installed and some other places but I didn't find any leads. I'm hoping it was something I did while trying to get it built and tested, and I'm not doing it (wrong apparently) anymore.
As for the Xvesa mouse problem, I have confirmed that it does work right off the iso for TC 6.4.1. I've tried about every option I can think of for Xvesa for TC 7 but I can't get a mouse to work. I have determined that it looks like Xvesa is "hunting" for the protocol. In the log file it cycles through "switching to mouse protocol bus" then ps/2, imps/2, exps/2, then it starts over and it does this many times. What I can also confirm is that in both TC 6 and 7 there is an entry in dmesg for "mousedef: PS/2 mouse device is common for all mice". However in TC 6 if I cat /dev/input/mice and move the mouse I get data, whereas in TC 7 I do not. But in TC 7 the mouse works in Xorg, even though /dev/input/mice still doesn't dump anything.
Right now I have four VMs with the same virtual hardware. One is TC 7 beta development where I build and compile. The second is TC 7 beta test where I test extensions. These two are running Xorg and open-vm-tools and the mouse is working fine. A third is booted from the TC 6.4.1 iso (not installed) and Xvesa/mouse are working fine. The fourth has TC 7 beta installed with Xvesa, mouse yet to work. So far I've tried the graphics-KERNEL extension, xf86-input-vmmouse, xf86-input-evdev, different -mouse options, -softCursor, -dumb, different vesa modes, but so far no luck. All ideas welcome at this point.
-
There shouldn't be, and you have 4GB ram too. Fragmentation could cause that, but it's strange with so much free memory. Anything in dmesg? free -m?
Thanks for the quick reply, attempting to mount any extension from this point meets with same reply. I even created a swap partition and the system is no longer configured to ignore one
mount: mounting /dev/loop302 on /tmp/tcloop/dmidecode failed: Cannot allocate memory
tc@box:~$ free -m
total used free shared buffers cached
Mem: 3502 1024 2477 19 88 319
-/+ buffers/cache: 617 2885
Swap: 10007 0 10007
tc@box:~$
-
@ curaga
dmesg is another story, this error repeats each attempt to mount a new extension
vmap allocation for size 49152 failed: use vmalloc=<size> to increase size.
vmalloc: allocation failure: 42284 bytes
mount: page allocation failure: order:0, mode:0xd2
CPU: 6 PID: 16126 Comm: mount Not tainted 4.2.7-tinycore #1999
Hardware name: ASUS All Series/MAXIMUS VI HERO, BIOS 1603 08/15/2014
00000000 c053bc01 00000001 c01a1bab c05d9aa0 e95eaf58 00000000 000000d2
e772de00 c05dbc1f e772ddd8 00000000 000000d2 0000a52c c01be8d4 000000d2
00000000 c05dbc1f 0000a52c 000002d2 00000010 ff7fe000 f7ffe000 e7152e00
Call Trace:
[<c053bc01>] ? 0xc053bc01
[<c01a1bab>] ? 0xc01a1bab
[<c01be8d4>] ? 0xc01be8d4
[<c01be91e>] ? 0xc01be91e
[<f8133568>] ? 0xf8133568
[<c01bea0b>] ? 0xc01bea0b
[<f8133568>] ? 0xf8133568
[<f8133568>] ? 0xf8133568
[<f8133123>] ? 0xf8133123
[<f8132c67>] ? 0xf8132c67
[<f8132792>] ? 0xf8132792
[<c02c35b4>] ? 0xc02c35b4
[<c01d0007>] ? 0xc01d0007
[<f8132434>] ? 0xf8132434
[<f81324f5>] ? 0xf81324f5
[<c01d07dd>] ? 0xc01d07dd
[<c01e1174>] ? 0xc01e1174
[<c01e3194>] ? 0xc01e3194
[<c01e29a0>] ? 0xc01e29a0
[<c01e3455>] ? 0xc01e3455
[<c053ff2e>] ? 0xc053ff2e
Mem-Info:
active_anon:42606 inactive_anon:1732 isolated_anon:0
active_file:26179 inactive_file:21380 isolated_file:0
unevictable:0 dirty:0 writeback:0 unstable:0
slab_reclaimable:6976 slab_unreclaimable:18196
mapped:6442 shmem:4966 pagetables:836 bounce:0
free:740298 free_pcp:2031 free_cma:0
DMA free:6812kB min:36kB low:44kB high:52kB active_anon:0kB inactive_anon:0kB active_file:560kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15972kB managed:9420kB mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB slab_reclaimable:420kB slab_unreclaimable:1196kB kernel_stack:112kB pagetables:60kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 842 3492 3492
Normal free:625076kB min:3552kB low:4440kB high:5328kB active_anon:20848kB inactive_anon:1412kB active_file:53820kB inactive_file:11936kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:892920kB managed:862976kB mlocked:0kB dirty:0kB writeback:0kB mapped:2536kB shmem:1788kB slab_reclaimable:27484kB slab_unreclaimable:71588kB kernel_stack:5864kB pagetables:3284kB unstable:0kB bounce:0kB free_pcp:4200kB local_pcp:536kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 21201 21201
HighMem free:2329304kB min:512kB low:3304kB high:6100kB active_anon:149576kB inactive_anon:5516kB active_file:50336kB inactive_file:73584kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:2713748kB managed:2713748kB mlocked:0kB dirty:4kB writeback:0kB mapped:23228kB shmem:18076kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:3928kB local_pcp:580kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 4*4kB (U) 3*8kB (UEM) 1*16kB (E) 0*32kB 2*64kB (UE) 0*128kB 2*256kB (UM) 2*512kB (UE) 1*1024kB (E) 2*2048kB (UE) 0*4096kB = 6840kB
Normal: 112*4kB (UEM) 194*8kB (UEM) 79*16kB (UEM) 43*32kB (UM) 10*64kB (UM) 6*128kB (UEM) 2*256kB (EM) 1*512kB (U) 2*1024kB (UM) 1*2048kB (U) 150*4096kB (M) = 625568kB
HighMem: 177*4kB (M) 100*8kB (UM) 21*16kB (UM) 6*32kB (UM) 2*64kB (UM) 2*128kB (UM) 2*256kB (UM) 2*512kB (UM) 1*1024kB (M) 1*2048kB (M) 567*4096kB (M) = 2329460kB
52793 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap = 10248188kB
Total swap = 10248188kB
905660 pages RAM
678437 pages HighMem/MovableOnly
9124 pages reserved
SQUASHFS error: Failed to allocate zlib workspace
snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
-
What happens if you set the copy2fs.flg and load them all? It's strange that rootfs only shows 20M used. I have 260+ loops and it shows 500M on my system.
-
I think I've figured out the problem, but the jury is not out yet..
Increased vmalloc to 256MB at the grub2 command line and hopefully that will accommodate the massive video card that appears to be causing the issue.
"UPDATE" this was the fix, I should have looked at dmesg sooner :p problem solved
thanks
-
@coreplayer2:
If you boot without that option, what does "grep -i vmalloc /proc/meminfo" say (after hitting that mount error)? How big a GPU do you have?
edit: On a Qemu boot, there's 900mb reserved.
@andyj
There is a new kernel driver for the VMWare mouse, supposed to enable a better experience, but it requires Xorg and the vmmouse driver. Seems like you need a bootcode, psmouse.proto=imps, to disable the new vmmouse driver.
It's unfortunate this can't be detected at runtime. We can either:
- disable that driver, but then the VMWare mouse experience might suffer in the future, when they remove the userspace mouse sync from xf86-input-vmmouse
- just document that vmware + Xvesa needs that
Adding absolute pointer support (vmmouse, touch screens) to Xvesa would also be possible, but it's not something I'm interested in doing.
-
The boot code fixes the mouse problem with Xvesa, insofar as it now exhibits the behavior of TC 6 where the mouse works but you have to manually ungrab the mouse to move it out of the window. The built in vmmouse driver also explains why manually ungrabbing the mouse in TC 7 wasn't required, even though the mouse wasn't working in Xvesa. I would answer the question this way: If someone is using VMware, then they will probably use Xorg and open-vm-tools to get the video and mouse functionality they need. If not and they stick with Xvesa then they know what they are getting. If they are using ESX then the video driver doesn't really matter because they are either using VNC to see the console, or in my case not running X at all and using SSH. I'm not having any luck changing this after boot, either through sysctl. /proc or /sys. Would adding this bootcode to the command line for the ISO image affect other platforms? Then we could go the documentation route, by pointing out during the "add boot codes" phase of the installation process that this is needed for VMware VM's using Xvesa and not Xorg.
-
Adding the bootcode by default might break others' mice, especially laptop touchpads, so that's not an option. I don't think there's any runtime way, but I asked the VMWare people, maybe they have an idea.
-
I was think along the lines of adding a "boot in a VMware VM" selection to the boot menu on the ISO image with the boot code appended to APPEND, not as a general default for an installed command line. I wouldn't think this would affect anything else.
-
The VMWare people confirmed the userspace support is not going away, so we can disable the kernel vmmouse driver safely, without impacting Xorg users.
Andyj, can you post the contents of /proc/bus/input/devices?
cat /proc/bus/input/devices | nc termbin.com 9999
-
I think the netcat worked, but here is the output since it's kinda short. There does seem to be a lot of mice:
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input1
U: Uniq=
H: Handlers=sysrq kbd leds event1
B: PROP=0
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0011 Vendor=0002 Product=0013 Version=0006
N: Name="VirtualPS/2 VMware VMMouse"
P: Phys=isa0060/serio1/input1
S: Sysfs=/devices/platform/i8042/serio1/input/input4
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=b
B: KEY=70000 0 0 0 0 0 0 0 0
B: ABS=3
I: Bus=0011 Vendor=0002 Product=0013 Version=0006
N: Name="VirtualPS/2 VMware VMMouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input3
U: Uniq=
H: Handlers=mouse0 event3
B: PROP=1
B: EV=7
B: KEY=30000 0 0 0 0 0 0 0 0
B: REL=103
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input5
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0003 Vendor=0e0f Product=0003 Version=0110
N: Name="VMware VMware Virtual USB Mouse"
P: Phys=usb-0000:02:00.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/0003:0E0F:0003.0001/input/input6
U: Uniq=
H: Handlers=mouse1 event5
B: PROP=0
B: EV=17
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
B: MSC=10
-
@coreplayer2:
If you boot without that option, what does "grep -i vmalloc /proc/meminfo" say (after hitting that mount error)? How big a GPU do you have?
edit: On a Qemu boot, there's 900mb reserved.
Sorry got busy...
Tests after booting without the vmalloc=256 boot code
with and without swap partition
withswap
clean after bootup
tc@box:~$ grep -i vmalloc /proc/meminfo
VmallocTotal: 122880 kB
VmallocUsed: 7984 kB
VmallocChunk: 114596 kB
withswap
after running build script
tc@box:~$ grep -i vmalloc /proc/meminfo
VmallocTotal: 122880 kB
VmallocUsed: 8036 kB
VmallocChunk: 114220 kB
tc@box:~$
noswap
clean after bootup
tc@box:~$ grep -i vmalloc /proc/meminfo
VmallocTotal: 122880 kB
VmallocUsed: 5108 kB
VmallocChunk: 117596 kB
noswap
after running build script
tc@box:~$ grep -i vmalloc /proc/meminfo
VmallocTotal: 122880 kB
VmallocUsed: 5160 kB
VmallocChunk: 117556 kB
tc@box:~$
results in 120MB allocation
With vmalloc=256MB bootcodetc@box:~$ grep -i vmalloc /proc/meminfo
VmallocTotal: 262144 kB
VmallocUsed: 52584 kB
VmallocChunk: 196052 kB
tc@box:~$results in 256MB allocation
Since setting the bootcode that one time I haven't been able to reproduce the loop error
even after removing the bootcode, but I'll keep trying
I'm fairly sure the 4GB memory installed on the video card has a lot to do with this issue
VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
Subsystem: eVga.com. Corp. Device 2974
Kernel driver in use: nvidia
-
Thanks. With 4gb RAM + big gpu you really should run a 64-bit kernel, there's not enough address space for everything on a 32-bit one.
-
Under normal conditions I boot to corepure64 and occasionally core64 which do not have this issue, obviously... But there are times when I need to compile something on x86, so I usually configure the boot config capable to boot either one of the three variations. The vmalloc boot code had slipped my mind so I'm thankful to you for reminding me.
Now if I can just get the Nvidia driver to compile on corepure64.. :-\
-
Oh, you can use a 64-bit kernel for that still :)
"linux32 bash" will start a bash shell that claims to be 32-bit in uname -m. This is useful for some configure scripts that check for it.