Tiny Core Base > Release Candidate Testing
Core v16.0beta1
GNUser:
Hi Rich. Thank you :)
idk:
A couple of small tweaks to the tce-setup and tce-load scripts in the base initrd:
tce-setup diff:
--- Code: ---63c63
< [ -f "$MOUNTPOINT"/"$TCE_DIR"/"$TARGETLIST"] || touch "$MOUNTPOINT"/"$TCE_DIR"/"$TARGETLIST"
---
> [ -f "$MOUNTPOINT"/"$TCE_DIR"/onboot.lst ] || touch "$MOUNTPOINT"/"$TCE_DIR"/onboot.lst
--- End code ---
tce-load diff:
--- Code: ---99c99
< [ "$THISAPP" != "$EXTENSION" ] || [ "$DOWNLOAD_ONLY" ] || [ "$LOAD_ONLY" ] || echo "$THISAPP" >> "$TCEDIR"/$ONBOOTNAME
---
> [ "$THISAPP" != "$EXTENSION" ] || [ "$DOWNLOAD_ONLY" ] || [ "$LOAD_ONLY" ] || echo "$THISAPP" >> ../$ONBOOTNAME
--- End code ---
I think I got the diff order right - it'll make sense to whoever applies the patches.
These both should correct some file/dir reference issues when a couple of the bootcode-based overrides are used. These have needed tweaking for years. Sorry it took me so long to contribute.
Thanks,
idk
MikeLockmoore:
Maybe this is not the right place to discuss sound issues, but in the RC I have alsa and pulseaudio installed. I have the same issue others have posted where I need to unmute my speakers each time I reboot. I'd like my Flit sound applet be able to control sound without the PAVUcontrol needing to be installed, but as of now, PAVUcontrol is the only way to get sound working for me. I don't see yet anything PAVUcontrol does when unmuting that is different than the amixer and pactl commands I've tried to unmute the speakers form the command line. Any thoughts? Should I repost this issue in another thread?
Rich:
Hi MikeLockmoore
--- Quote from: MikeLockmoore on March 20, 2025, 12:40:41 AM --- ... I don't see yet anything PAVUcontrol does when unmuting that is different than the amixer and pactl commands I've tried to unmute the speakers form the command line. Any thoughts? Should I repost this issue in another thread?
--- End quote ---
Yes, start a new thread in TCE Talk please.
CNK:
TC16 doesn't boot on my 486DX4-100 laptop. After "Decompressing kernel... Parsing ELF...", then someting else which flashes up too quick to see, it reboots. I can try to frame-through a video of it if it would be useful to know the rest of the message. Perhaps there's a chance the kernel just won't start in the laptop's 16MB RAM anymore (rootfs.gz and modules.gz are unpacked to a HDD partition used as root= so they're not in RAM like a normal TC installation), but probably an illegal instruction.
Sorry I'm late with my usual 486 test. On my first attempt I reconnected the HDD wrong and killed it, losing my TC boot configuration in the process. I tested TC15 again though and (eventually) got it booting again. Replacing the TC15 vmlinuz file with the TC16 one causes the above behaviour. The same HDD transplanted into a 1GHz Intel Celeron laptop with 256MB RAM boots TC16 OK.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version