Tiny Core Linux
Tiny Core Base => TCB News => Final Releases => Topic started by: roberts on January 08, 2012, 12:33:42 AM
-
Core 4.2.1 a minor bug fix and adjustments release is now available at
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release (http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release)
Change Log:
* Updated aterm with patches for dead key issue.
* Updated dhcpd.sh - added timeout of 5 sec to udevadm settle
* Updated tce-setup to capture suppress boot messages as requested,
* Updated CorePlus with latest extensions from repository plus Openbox and more firmware extensions.
Note. Updates to the following X/GUI and widow manage extensions:
Xprogs.tcz, Xlibs.tcz, fltk-1.10.tcz, flwm.tcz, flwm_topside.tcz, fluxbox,tcz, and hackedbox.tcz
-
hi roberts,
with the help of this following line in my .Xdefaults i configured a nice and very readable aterm:
.Xdefaults
aterm*font:*-fixed-*-*-*-20-*
since 4.2.1 this font-configuration has no effect anymore and the font is tiny and hard to read again.
do you see there any way to get the used behavior back!?
thank you in advance for your help and advice.
-
Awesome, thanks for the release robert! Testing w/ Openbox shortly. Thank you for also officially adding the udevadm settle timeout, that was getting annoying.
-
@netnomad
Can't reproduce, I replaced "fixed" in .Xdefaults with your line in 4.2.1 and the font was much bigger.
-
hi curaga,
it was my mistake and i can reproduce it:
in my .Xdefaults were two lines that did not conflict yet, until 4.2.1:
aterm*font:*-fixed-*-*-*-20-*
aterm*font:fixed
up to 4.2 only the first line was used, since 4.2.1 the second line did configure the font.
thank you for your reply.
-
The small updates to flwm are much appreciated :)
-
Second that. After moving to 4.2.1 my mouse wheel suddenly started to work again.
-
I installed today 4.2.1 on a pentium 4 (RAM 1GB, HDD 80GB, nvidia card, Wifi). Here is my experience. And perhaps few wishes.
- I missed a line /xxx/.filetool.lst in .filetool.lst (at the second boot, I discovered my backup was not correctly done because this line was not there)
- I could not use fluxbox because it did not accept the background (flwm_topside is fine with the backgrounds)
- I missed a functionning GPARTED in the muticore.iso (after installing TC on the full HDD, I could not make a SWAP and new home partition because only 1 partition was made and it was locked from the boot sequence). Perhaps create a 2(?)GB maximum partition in case of HDD full install? the (2) GBs could be asked per menu in the TC-install extension?. I know, I should have partitionned with GPARTED before the HDD install, but I forgot it, and in this case I used a knoppix CD because it has GPARTED from the beginning and it was easier for me with an existing knoppix CD I had.
- put a new menu in the CD boot menu? PLOP boot loader would be great.. it would have helped me in starting my SD card from the USB adapter (my BIOS did not recognized my SD on USB adapter). Instead of this, I choosed to boot knoppix, burned a CD with multicore.iso and then started TC from it. Using an USB or a SD/CF on USB in the future could avoid burning CDs. This PLOP boot loader would only take a bit space on the CD. Or perhaps I should have simply used another CD (UBCD?) with PLOP on it. But in any case, all future TCL isos could have plop.
- I started with a PS2 mouse. Later changed to an USB mouse. No issue at all.
- Wifi: perfect recognized
- Boot speed: very very good
The mother of the family will be happy.. she wanted to throw away this slow winXP PC. I convinced her to give it to me for a try. Now, it is very very good. And I give it back for her children (12..17).
-
Recent kernel just moved my laptop's wireless adapter's driver out of the stage sector. Is there a plan for an updated kernel in the near future?
-
Hi Xianwen Chen
You forgot to mention which driver you use.
-
Thank you Rich. I think it is a Broadcom (bcm something) chip. I compiled it when it was in stage one year ago when I was running Gentoo. It seems that Core Linux doesn't have lspci nor lsusb. I cannot get the chip information right now.
-
Hi Xianwen Chen
It seems that Core Linux doesn't have lspci nor lsusb.
I think you always had to download them from the repository.
-
Recent kernel just moved my laptop's wireless adapter's driver out of the stage sector. Is there a plan for an updated kernel in the near future?
Major kernel changes are usually reserved for the major TC versions.
-
Recent kernel just moved my laptop's wireless adapter's driver out of the stage sector. Is there a plan for an updated kernel in the near future?
Major kernel changes are usually reserved for the major TC versions.
Okay. Is there a plan for TC 5?
-
Hi Xianwen Chen
It seems that Core Linux doesn't have lspci nor lsusb.
I think you always had to download them from the repository.
Thank you Rich. Which repository are you referring to?
-
Hi Xianwen Chen
The one AppBrowser uses when it gets an extension for you. You want:
pci-utils.tcz
usb-utils.tcz
-
They are in pci-utils and usb-utils. AppBrowser could have found them for you.
-
Hi Xianwen Chen
The one AppBrowser uses when it gets an extension for you. You want:
pci-utils.tcz
usb-utils.tcz
Thank you Rich.
-
They are in pci-utils and usb-utils. AppBrowser could have found them for you.
That's true. Thank you Gerald. But if you try lsusb and lspci, which were the keywords that I used in AppBrowser, it gives you nothing.
-
You have to change "Search" to "Provides".
-
You have to change "Search" to "Provides".
Never noticed that. Thank you Gerald.
-
"provides" is very usefull type of research, is very interesting because it searches for files in all packages
O.t. I hope that in future there is a keywords field in info file :P
-
Hi Xianwen Chen
You forgot to mention which driver you use.
It is a Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
.
-
As per here:
http://linuxwireless.org/en/users/Drivers/b43#Supported_devices (http://linuxwireless.org/en/users/Drivers/b43#Supported_devices)
..your device is not supported in the tinycore 3.0.3 kernel
But as per here:
http://www.broadcom.com/support/802.11/linux_sta.php (http://www.broadcom.com/support/802.11/linux_sta.php)
..it looks like your device is suported by the "wl" driver in the wl-modules-3.0.3-tinycore extension
-
As per here:
http://linuxwireless.org/en/users/Drivers/b43#Supported_devices (http://linuxwireless.org/en/users/Drivers/b43#Supported_devices)
..your device is not supported in the tinycore 3.0.3 kernel
But as per here:
http://www.broadcom.com/support/802.11/linux_sta.php (http://www.broadcom.com/support/802.11/linux_sta.php)
..it looks like your device is suported by the "wl" driver in the wl-modules-3.0.3-tinycore extension
No, it's not supported by 3.0.3 kernel, as it was a driver in stage and wasn't enabled. It just went out of stage few weeks ago. I'm hoping that when the kernel is updated next time, this driver will be included.
-
In the meantime, you could use the broadcom wl driver or compile the latest compat wireless
-
In the meantime, you could use the broadcom wl driver or compile the latest compat wireless
No, it doesn't work. But I do have USB wireless adapters which old kernels recognize; so I can wait for a new kernel.
-
Did you blacklist b43, bcma and ssb before trying it?
-
Did you blacklist b43, bcma and ssb before trying it?
Maybe no? I did sudo modprobe with the three lines of commands in the info file. How to blacklist modules?
-
Hi Xianwen Chen
Try adding the following boot codes:
blacklist=ssb blacklist=bcma blacklist=b43
-
Hi Xianwen Chen
Try adding the following boot codes:
blacklist=ssb blacklist=bcma blacklist=b43
Thank you Rich and Juanito. My laptop's built-in wireless adapter is now working well.
-
Hii Xianwen Chen
Don't thank me, thank Juanito, that was a cut and paste from one of his recent posts.
-
Hii Xianwen Chen
Don't thank me, thank Juanito, that was a cut and paste from one of his recent posts.
Good point. Original post edited.