WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
1
Micro Core / Re: not loading modules and not loading extension TC 9x x64
« Last post by halma on Today at 11:21:53 AM »
Hi Curaga,

copy2fs is not activated :


and thats my extlinux.conf boot line
Code: [Select]
DEFAULT tinycore
PROMPT 1
TIMEOUT 1

LABEL tinycore
MENU LABEL tinycore
KERNEL /boot/$(basename $BUILDDIR/fs_mount/boot/vmlinu*)
APPEND initrd=/boot/$(basename $BUILDDIR/fs_mount/boot/corepur*) console=tty0 console=ttyS0,57600n8 nozswap waitusb=5 root=$BLKID tce=$BLKID nodhcp noutc syslog tz=Europe/Berlin host=xenbox

hello Halma

  • I'm curious to know what "tce=$BLKID" resolves to?
  • Assuming you have a tce directory what is the outcome of "showapps" boot code?
  • While unrelated, do you really need both noutc and tz= bootcodes?

hi coreplayer2
tce=$BLKID will generate a BlockID alias UUID for the Directory like this ->
Code: [Select]
Command line: BOOT_IMAGE=/boot/vmlinuz64_9.0_4.14.10_xen initrd=/boot/corepure64_9.0_4.14.10_xen.gz console=tty0 console=ttyS0,57600n8 nozswap waitusb=5 root=UUID="ecfb7bd6-79ba-47a0-ba2f-5589f75cf137" tce=UUID="ecfb7bd6-79ba-47a0-ba2f-5589f75cf137" nodhcp noutc syslog tz=Europe/Berlin host=xenbox
showapps is a very good hint, it shows :
Code: [Select]
Loading extensions...
EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/attr: Invalid argument
attr mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/ncursesw: Invalid argument
ncursesw mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/netfilter-4.14.10-tinycore64: Invalid argument
netfilter-4.14.10-tinycore64 mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/bzip2-lib: Invalid argument
bzip2-lib mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libcap: Invalid argument
libcap mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/firmware-amdgpu: Invalid argument
firmware-amdgpu mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/firmware-radeon: Invalid argument
firmware-radeon mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/firmware-rtl_nic: Invalid argument
firmware-rtl_nic mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/pcre: Invalid argument
pcre mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/gmp: Invalid argument
gmp mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/iasl: Invalid argument
iasl mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/iptables: Invalid argument
iptables mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/ipv6-4.14.10-tinycore64: Invalid argument
ipv6-4.14.10-tinycore64 mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libaio: Invalid argument
libaio mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libdb: Invalid argument
libdb mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libffi: Invalid argument
libffi mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libjpeg-turbo: Invalid argument
libjpeg-turbo mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/liblzma: Invalid argument
liblzma mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libpng: Invalid argument
libpng mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/openssl: Invalid argument
openssl mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libvncserver: Invalid argument
libvncserver mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libXdmcp: Invalid argument
libXdmcp mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libXau: Invalid argument
libXau mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libxcb: Invalid argument
libxcb mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libyajl: Invalid argument
libyajl mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/libssh2: Invalid argument
libssh2 mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/ncurses: Invalid argument
ncurses mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/net-bridging-4.14.10-tinycore64: Invalid argument
net-bridging-4.14.10-tinycore64 mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/openssh: Invalid argument
openssh mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/pciutils-dev: Invalid argument
pciutils-dev mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/perl5: Invalid argument
perl5 mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/pixman: Invalid argument
pixman mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/readline: Invalid argument
readline mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/sdl: Invalid argument
sdl mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/slang: Invalid argument
slang mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/udev-lib: Invalid argument
udev-lib mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/util-linux: Invalid argument
util-linux mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/xen4-kernel: Invalid argument
xen4-kernel mount: can't setup loop device: No such device or address
umount: can't unmount /tmp/tcloop/iproute2: Invalid argument
iproute2  Done.
Setting keymap to us Done.
Restoring backup files from /mnt/sda1/tce/mydata.tgz /
Done.
and so far

i will try to recompile the kernel with loop buildin support, something like this: CONFIG_BLK_DEV_LOOP=y
i removed noutc .... lets see that my local time is correct after that ...
thanks so far
2
TCE Corepure64 / Re: gnome 3
« Last post by curaga on Today at 10:32:50 AM »
Great, when can we expect your Gnome-mutter extension?
3
General dCore Talk / Re: dCore-usbinstall
« Last post by Jason W on Today at 09:40:32 AM »
Noticed an issue when running dCore-xenial and using dCore-usbinstall, should be fixed now. 

dCore-wheezy's grub-efi package is too old, so dCore-usbinstall won't work using a running dCore-wheezy session but dCore-wheezy can be installed to usb. 
4
TCE Corepure64 / Re: gnome 3
« Last post by pq5190362 on Today at 08:04:51 AM »
GNOME Mutter 3.29.1 Now Works With Elogind, Allows For Wayland On Non-Systemd Distros

https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Mutter-3.29.1

Quote
Mutter can now be built with elogind. That is the systemd-logind as its own standalone package. This in turn allows using Mutter with its native Wayland back-end on Linux distributions using init systems besides systemd.
5
General TC Talk / Re: Wayland
« Last post by pq5190362 on Today at 08:03:36 AM »
GNOME Mutter 3.29.1 Now Works With Elogind, Allows For Wayland On Non-Systemd Distros

https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Mutter-3.29.1

Quote
Mutter can now be built with elogind. That is the systemd-logind as its own standalone package. This in turn allows using Mutter with its native Wayland back-end on Linux distributions using init systems besides systemd.
6
General dCore Talk / Re: dCore-usbinstall
« Last post by Jason W on Today at 07:48:16 AM »
Hi PDP-8

dCore-usbinstall does not download and iso, only the dCore*.gz and vmlinuz* files, and it saves them in /etc/sysconfig/tcedir/dCoreusbinstall.  If the tce directory is on persistent storage, then those files are saved and used on later runs of dCore-usbinstall.  New md5sum files are downloaded on each run, and if the old dCore*.gz and vmlinuz* files pass md5 check they are used and not re-downloaded.

dCore-usbinstall is posted with an update to support UEFI.  A menu to choose between UEFI and LEGACYBIOS has been added, LEGACYBIOS simply is the previous way the installer worked, creating an ext2 partition that uses the whole usb drive.

The UEFI option creates a fat32 filesystem on a first partition of the usb drive.  The size of that first partition is the size of the dCore*.gz plus the vmlinuz* plus 20MB.  The 20MB is to leave room for the roughly 10MB needed for the grub files.  The size of my first partition created when installing dCore-stretch64 is 41MB, 32MB which was used by the installation.  This way the second ext2 partition created is the maximum possible size, and this second partition is where the TCE directory will be created upon booting the usb. 

Both a 32 and 64 bit grub efi boot files are installed whether the current session is 32 or 64 bit dCore.  I may later make dCore-usbinstall not install 32 bit grub efi files if a 64 bit dCore installation target is chosen as booting the resulting usb on 32 bit is not needed. 

Everything seems to be working as expected, please import and test. 
7
Raspberry Pi / Re: Pi 3B+
« Last post by bmarkus on Today at 03:34:39 AM »
Is that a "no ARMv8 kernel, not this week" or "no, not ever"?


64-bit version of piCore is a low priority task, first new 32-bit must be released.

BTW, which 64-bit distro are you using on RPi?
8
Micro Core / Re: not loading modules and not loading extension TC 9x x64
« Last post by coreplayer2 on April 25, 2018, 05:08:22 PM »
Hi Curaga,

copy2fs is not activated :


and thats my extlinux.conf boot line
Code: [Select]
DEFAULT tinycore
PROMPT 1
TIMEOUT 1

LABEL tinycore
MENU LABEL tinycore
KERNEL /boot/$(basename $BUILDDIR/fs_mount/boot/vmlinu*)
APPEND initrd=/boot/$(basename $BUILDDIR/fs_mount/boot/corepur*) console=tty0 console=ttyS0,57600n8 nozswap waitusb=5 root=$BLKID tce=$BLKID nodhcp noutc syslog tz=Europe/Berlin host=xenbox

hello Halma

  • I'm curious to know what "tce=$BLKID" resolves to?
  • Assuming you have a tce directory what is the outcome of "showapps" boot code?
  • While unrelated, do you really need both noutc and tz= bootcodes?
9
Micro Core / Re: not loading modules and not loading extension TC 9x x64
« Last post by halma on April 25, 2018, 12:17:31 PM »
Hi Curaga,

copy2fs is not activated :


and thats my extlinux.conf boot line
Code: [Select]
DEFAULT tinycore
PROMPT 1
TIMEOUT 1

LABEL tinycore
MENU LABEL tinycore
KERNEL /boot/$(basename $BUILDDIR/fs_mount/boot/vmlinu*)
APPEND initrd=/boot/$(basename $BUILDDIR/fs_mount/boot/corepur*) console=tty0 console=ttyS0,57600n8 nozswap waitusb=5 root=$BLKID tce=$BLKID nodhcp noutc syslog tz=Europe/Berlin host=xenbox


and thats the screen output from my serial connection
8< cut start
Code: [Select]
Booting Core 9.0
Running Linux Kernel 4.14.10-tinycore64.
Checking boot options... Done.
Starting udev daemon for hotplug support... Done.
clocksource: Switched to clocksource tsc
scsi 2:0:0:0: Direct-Access     Sony     Storage Media    0100 PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: [sda] 7864320 512-byte logical blocks: (4.03 GB/3.75 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] No Caching mode page found
sd 2:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 2:0:0:0: [sda] Attached SCSI removable disk
Skipping compressed swap in ram as requested from the boot command line.
Scanning hard disk partitions to create /etc/fstab
Setting Language to C Done.
Setting Timezone to Europe/Berlin Done.
Setting hostname to xenbox Done.
syslog started.
klog started.
Possible swap partition(s) enabled.
Loading extensions...EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
 Done.
Setting keymap to us Done.
Restoring backup files from /mnt/sda1/tce/mydata.tgz /
Done.
Skipping DHCP broadcast/network detection as requested on boot commandline.
Setting hostname to xenbox Done.
fbset: can't open '/dev/fb0': No such device
ifconfig: SIOCSIFADDR: No such device
/opt/bootlocal.sh: line 18: brctl: not found
/opt/bootlocal.sh: line 19: brctl: not found
/opt/bootlocal.sh: line 20: brctl: not found
ifconfig: SIOCGIFFLAG
Core Linux
xenbox login:

8< cut end


copy2fs is not enabled at the moment ....
Code: [Select]
tc@xenbox:~$ sudo find / -name "copy2fs*"
tc@xenbox:~$


and here my complete minicom logfile
https://pastebin.com/7Egvb8y0
10
Micro Core / Re: not loading modules and not loading extension TC 9x x64
« Last post by curaga on April 25, 2018, 11:05:11 AM »
Hard to say with a remaster, but your sudo log at least looks like copy mode/copy2fs.
Pages: [1] 2 3 ... 10