WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Core v7.0beta1  (Read 6812 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9365
Core v7.0beta1
« on: January 04, 2016, 05: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.

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: Core v7.0beta1
« Reply #1 on: January 05, 2016, 06:50:31 AM »
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
Code: [Select]
block already free
No idea what that means. Google indicates something related to DRM which I don't understand.

showbootcodes
Code: [Select]
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
Code: [Select]
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
Code: [Select]
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)
Download a copy and keep it handy: Core book ;)

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: Core v7.0beta1
« Reply #2 on: January 05, 2016, 07:23:51 AM »
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:
Code: [Select]
[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
« Last Edit: January 05, 2016, 07:27:01 AM by Misalf »
Download a copy and keep it handy: Core book ;)

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1540
Re: Core v7.0beta1
« Reply #3 on: January 05, 2016, 07:40:45 AM »
Attached  /sys/class/drm/card0/error .
Download a copy and keep it handy: Core book ;)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9514
Re: Core v7.0beta1
« Reply #4 on: January 05, 2016, 12:00:11 PM »
That's still open upstream, nothing we can do:
https://bugs.freedesktop.org/show_bug.cgi?id=90841
The only barriers that can stop you are the ones you create yourself.

Offline dentonlt

  • Sr. Member
  • ****
  • Posts: 307
    • the trombone analog
Re: Core v7.0beta1
« Reply #5 on: January 06, 2016, 05:12:04 PM »
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


Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2475
Re: Core v7.0beta1
« Reply #6 on: January 08, 2016, 02:35:44 AM »
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

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 6897
    • My Community Forum
Re: Core v7.0beta1
« Reply #7 on: January 08, 2016, 02:48:30 AM »
You can use uname -m or uname -acommand to identify architecture.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2475
Re: Core v7.0beta1
« Reply #8 on: January 08, 2016, 03:02:37 AM »
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
« Last Edit: January 08, 2016, 03:10:33 AM by coreplayer2 »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9514
Re: Core v7.0beta1
« Reply #9 on: January 08, 2016, 03:07:02 AM »
See getBuild in tc-functions.
The only barriers that can stop you are the ones you create yourself.

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2475
Re: Core v7.0beta1
« Reply #10 on: January 08, 2016, 03:29:55 AM »
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...
« Last Edit: January 08, 2016, 03:32:29 AM by coreplayer2 »

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2475
Re: Core v7.0beta1
« Reply #11 on: January 08, 2016, 03:40:40 AM »
All my systems run solid and efficient with v7beta1   seems like we have a winner here

:D

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9514
Re: Core v7.0beta1
« Reply #12 on: January 08, 2016, 09:54:25 AM »
@coreplayer2

Yes, that function correctly separates core64 from corepure64?

6.4.1 test:
The only barriers that can stop you are the ones you create yourself.

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2475
Re: Core v7.0beta1
« Reply #13 on: January 08, 2016, 12:20:46 PM »
@ curaga

I hate it when you're right.. :p

core_x86


core64


corepure64


Maybe it was operator error at 4am, on my part..? 
I'm going to use getBuild in future  thanks


Offline Lee

  • Hero Member
  • *****
  • Posts: 636
    • My Core wiki user page
Re: Core v7.0beta1
« Reply #14 on: January 08, 2016, 06:18:13 PM »
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.  :)
32 bit core4.7.7, Xprogs, Xorg-7.6, wbar, jwm  |  - Testing -
PPR, data persistence through filetool.sh          |  32 bit core 8.0 alpha 1
USB Flash drive, one partition, ext2, grub4dos  | Otherwise similar