Tiny Core Base > Alpha Releases
Tiny Core 16.0 Alpha 1 Testing
Rich:
Hi Knoppix1337
The version which hangs (ser-con-Vx0-tc16-x86.txt) ends here:
--- Code: ---Booting Core 16.0alpha1
Running Linux Kernel 6.12.11-tinycore.
Checking boot options... Done.
Starting udev daemon for hotplug support... Done.
loop: module loaded
usb-storage 3-2:1.0: USB Mass Storage device detected
scsi host2: usb-storage 3-2:1.0
--- End code ---
The "Checking boot ..." and "Starting udev ..." messages come /etc/init.d/tc-config.
"loop: module loaded" is due to tc-config executing "modprobe loop".
The last 2 messages are from the kernel.
The version which completes (ser-con-Vx0-tc16-x86-printk.txt) ends here:
--- Code: ---Booting Core 16.0alpha1
Running Linux Kernel 6.12.11-tinycore.
Checking boot options... Done.
Starting udev daemon for hotplug support... Done.
usb-storage 3-2:1.0: USB Mass Storage device detected
scsi host2: usb-storage 3-2:1.0
loop: module loaded
via-rhine 0000:00:0b.0 eth0: VIA Rhine III at (ptrval), 00:80:64:84:0d:8f, IRQ 19
via-rhine 0000:00:0b.0 eth0: MII PHY found at address 1, status 0x7849 advertising 01e1 Link 0000
input: PC Speaker as /devices/platform/pcspkr/input/input4
cpufreq: CPU0: Fast frequency switching not enabled
cpufreq: Registered transition notifiers:
cpufreq: 0xc01257d0
scsi 2:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 4
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] 15679488 512-byte logical blocks: (8.03 GB/7.48 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 2:0:0:0: [sdb] No Caching mode page found
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
random: crng init done
Adding 227132k swap on /dev/zram0. Priority:-2 extents:1 across:227132k SS
Scanning hard disk partitions to create /etc/fstab
Setting Language to C Done.
Setting Timezone to America/Chicago Done.
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Possible swap partition(s) enabled.
Loading extensions...parport_pc 00:05: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
ppdev: user-space parallel port driver
Done.
Setting keymap to us Done.
Restoring backup files from /mnt/sda1/tce/mydata.tgz Done.
longhaul: Option "enable" not set - Aborting
Setting hostname to box Done.
login[604]: root login on 'tty1'
--- End code ---
Maybe the cpufreq module is hanging the CPU.
Try:
--- Code: ---initcall_blacklist=cpufreq
--- End code ---
You could also try this to reduce udev activity:
--- Code: ---udev.children-max=1
--- End code ---
--- Quote from: Knoppix1337 on February 18, 2025, 03:00:10 AM --- ... The failsafe is the cheatcodes from the Knoppix failsafe boot option containing:
--- Code: ---APPEND lang=en vga=normal atapicd nosound noapic nolapic noacpi pnpbios=off acpi=off nofstab noscsi nodma noapm nousb nopcmcia nofirewire noagp nomce libata.force=noncq hpsa.hpsa_allow_any=1 nonetwork nodhcp xmodule=vesa initrd=/boot/rootfs.gz,/boot/modules.gz ignore_loglevel no3d nofb console=ttyS0,115200n8
--- End code ---
Obviously some parameters are ignored by TC.
--- End quote ---
Parameters that the kernel does not recognize wind up in /proc/cmdline
for use by system scripts. TC uses this mechanism too.
The noacpi code is valid, but not by itself. It should be:
--- Code: ---pci=noacpi
--- End code ---
--- Quote from: Knoppix1337 on February 09, 2025, 03:11:30 PM --- ... I was previously looking through the boot sequence code, and although I used the waitusb=13 cheatcode, the message from the bootcode never showed up showing that it was actually waiting. ...
--- End quote ---
The waitusb=N only executes a sleep N instruction with no message.
It will always wait N seconds.
The waitusb=N:UUID="UUID of device to wait for" will echo a countdown while waiting.
It will wait up to N seconds.
It will continue when the device is ready or N seconds has elapsed, whichever comes first.
Juanito:
Problems with re-drawing window borders using flwm/flwm_topside in x86_64 seem to have been fixed, updated extensions uploaded.
Juanito:
@polikuo - when using labwc-config in x86_64, things seem to work OK, but when I exit to the console I cannot "startx" (Xorg-7.7 flwm aterm wbar), the gui begins to start and then hangs.
I don't see an error in the xorg log - any ideas?
MikeLockmoore:
--- Quote ---Problems with re-drawing window borders using flwm/flwm_topside in x86_64 seem to have been fixed, updated extensions uploaded.
--- End quote ---
Juanito: That is great news! Thanks for helping me get back up to working on FLTK aps and FLWM... looks like I'm getting here too late to help much. I would like to get 16 RC up and running though. The RC files at http://repo.tinycorelinux.net/16.x/x86_64/release_candidates/distribution_files/ don't seem to show today's date. Is that the right place to grab them?
Juanito or anyone... I'm currently booting TC15 on a ThinkPad laptop form a USB stick, I think in "legacy" mode (non UEFI). It modded the boot config to use different boot parameters to use my internal SSD storage as my tce/ home (deleted "cde" from the boot parmeters and added "tce=sda2 restore=sda2")
I'd like to keep the 15 kernel as an option, and setup my USB boot stick to have a new TC 16 RC menu entry.
I think I can do this by copying over the RC vmlinuz64 with a new name to sit next to the TC 15 vmlinuz kernel, then making sure the RC boot menu entry refers to the correct name of the kernel I want.
However, I'm not sure how to set up the modules.gz and rootfs64.gz. is the RC rootfs64 the same as the corepure64.gz that is on my USB boot stick? So I can set up my boot entry like this...
LABEL tc_rc
MENU LABEL Boot TinyCore 16 RC
TEXT HELP
Boot TinyCore version 16 Release Candidate
Boot media is removable. Use TAB to edit options for specific needs.
ENDTEXT
KERNEL /boot/vmlinuz64_16rc
INITRD /boot/rootfs64.gz
APPEND loglevel=3 tce=sda2/tce16 restore=sda2/tce16 vga=791
What do I do with the modules.gz in the release candidates URL? Thanks for any suggestions! -Mike
Juanito:
--- Quote from: MikeLockmoore on February 22, 2025, 10:19:21 AM ---The RC files at http://repo.tinycorelinux.net/16.x/x86_64/release_candidates/distribution_files/ don't seem to show today's date. Is that the right place to grab them?
--- End quote ---
Yes
--- Quote ---I think I can do this by copying over the RC vmlinuz64 with a new name to sit next to the TC 15 vmlinuz kernel, then making sure the RC boot menu entry refers to the correct name of the kernel I want.
--- End quote ---
Yes, you can rename them, for example, modules64_16.gz, rootfs_16.gz and vmlinuz64_16
--- Quote ---However, I'm not sure how to set up the modules.gz and rootfs64.gz. is the RC rootfs64 the same as the corepure64.gz that is on my USB boot stick?
--- End quote ---
corepure64.gz = rootfs64.gz + modules64.gz
--- Quote ---So I can set up my boot entry like this...
--- End quote ---
Using grub you can specify "initrd /boot/rootfs64.gz /boot/modules64.gz"
I'm not sure if your boot loader can do this or not (you can try :) ), otherwise you'd have to concatenate them
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version