Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on December 22, 2011, 07:50:24 AM
-
The third release candidate of Core 4.2 is ready for public testing:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release_candidates (http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release_candidates)
Main theme for 4.2 release is to focus on the Core.
With the Core Project one starts with the kernel (vmlinuz) and the core.
MicroCore is simply the kernel + core.gz - this is the foundation for user created desktops.
TinyCore is simply the kernel + core.gz + Xvesa.tcz|Xorg.tcz + Xprogs + (user's choice of Window Manager) + (optionally wbar.tcz).
The original TinyCore becomes simply an example of what the Core Project can produce, an 11MB desktop.
4.2 also intoduces CorePlus a simple way to get started using the Core philosophy in allowing easy
embedded frugal or pendrive installation of the user's choice of supported desktop, while maintaining the
Core principal of mounted extensions with full package management.
RC1 Change log:
* Updated tce-setup to use /tmp/builtin for embedded initrd extensions. Changed from /opt/tce
* Updated cpanel to only activate Xvesa button if Xvesa is loaded.
* Updated exittc default focus on OK button for quicker use from keyboard.
* Updated mntttol to call rebuildfstab.
* Updated base for move of /opt/.tce_dir to a link at /etc/sysconfig/tcedir which includes the following:
tce-load, tce-run, tce-setdrive, tce-size, tce-audit, filetool.sh, tce-setup, ondemand, tce-update,
.profile, tc-config, rc.shutdown, appbrowser, appsaudit, exittc, flwm_topside_ondemand,
.setbackground, wbarconf, wbar_update.sh, wbar_setup.sh.
* Updated the following system X/GUI extensions:
Xvesa,tcz, Xlibs.tcz, Xprogs,tcz, fltk-1.10.tcz, flwm_topside.tcz, flwm.tcz, and wbar.tcz.
* Updated tce-setup to write cde info to /etc/sysconfig.
* Updated startx to better support desktop boot code.
* Updated tc-config and tce-setup.sh for refined definition of the base boot code.
base will now only ignore "user" extensions. Builtins and cde extensions always load as they have become by their very nature part of the base system. See CorePlus.iso for how it is being used.
xbase.lst is implemented via our standard lst boot option. But now lst is supported in the cde directory.
Hence by using xbase.lst a simple standard list file containing only the base X/GUI extensions to be loaded.
See CorePlus iso for how it is being deployed.
* Updated interface files for supported window manager extensions:
flwm_topside.tcz, flwm.tcz, fluxbox.tcz, hackedbox.tcz, icewm.tcz, icewm-full.tcz, jwm-snapshot.tcz, jwm.tcz
Files likely in your backup that will need to be updated:
.setbackground
.profile
.xsession
Note: You must recreate all ondemand items. Use AppsAudit OnDemand Maintenance.
CorePlus replaces MultiCore:
CorePlus now sports a boot menu so that the user can easily see the window managers and boot options available.
* Dropped tc-grub4dos
* Dropped tinycore.gz
* Added flwm, jwm, icewm, fluxbox, and hackedbox; plus their dependencies.
* Updated tc-install.sh & tc-install GUI now installs running desktop and detects CorePlus with user selectable options,
frugal now installs embedded, i.e., self contained in the tce directory with option to skip the boot loader install.
* Updated ezremaster to support the new Core foundation.
==================================================================
RC2 Change Log:
* Clean up of some full paths, adjusted /opt/.filetool.lst and /opt/.xfiletool.lst
* New refactored Xlibs.tcz, Xprogs.tcz so that now Xprogs.tcz contains only FLTK GUI programs. Xprogs is now optional.
* New fltk-1.10.tcz contains only FLTK libraries, required by any FLTK GUI programs.
* New /usr/bin/exittc script to allow exiting WM when no Xprogs are used.
* New /usr/bin/backup script useful when no Xprogs are used.
* Updated .xsession to store X pid.
* Updated tc-config more adjustments for new tce specifications.
Files likely in your backup:
.xsession /opt/.filetool.lst /opt/.xfiletool.lst
==================================================================
RC3 Change log:
* New setupdesktop factored out of startx in Xlibs.tcz
* Updated startx to call setupdesktop
* New startup script for Xprogs.tcz to support after X/GUI desktop loading.
* Updated tce-update fixed TCEDIR bug as reported.
* Updated tce-setup for better detection of cde when not found on cdrom.
You are now be able to use for example, JWM, and no Xprogs.tcz. You would have to use CLI utilities for Core extensions.
* Updated .dep files to include fltk-1.10 libs. You can now use any supported window manager without Xprogs,
Note: With all the structural changes, the required extensions are currently with the release candidate.
Once 4.2 is released the extensions will be moved into the repository.
-
I loaded Xprogs after starting X.
Instead of adding the Xprogs icons to wbar, it doubled up the icons for the installed apps ( mc and Opera9 ).
-
Thanks! Found and corrected. Reposted Xlibs.tcz with correction.
Please be sure to have all the latest X/GUI extensions from the release candidate area.
-
Ok. Loading Xprogs now updates wbar correctly.
AppsAudit does not allow you to add Xprogs.tcz to onboot or ondemand.
-
I have updated Xprogs.tcz as its startup scipt was running as root. Corrected.
All this only applies to those who are trying to load Xprogs after X/GUI has already been established.
It does not affect regular use.
-
OK. Working now as expected.
-
Thanks for testing and feedback. Very much appreciated. Going forward Core is much more modular. Which is the goal of the 4.2 release.
-
I luv the continuing modular approach, which must surely be close to being complete with this release.
Today I created a remastered core iso from a coreplus frugal install simply by removing the X and wm related extensions from the remaster, the result a cli core ISO.
Thanks a million, this is so cool. And a big thanks to all those who helped make this release possible.T
-
Finally I got it up and running from USB stick after many trials and discussing with Robert. The key point is, that you can't use the same partition for tce directory and cde. With other words it means, that single FAT partitioned setup is not supported, you need a second LINUX partition for tce. tce= boot option to this partition will create tce and its sub directories and will be found automatically at next boot.
There is one bug still, onboot.lst is not created automatically. If you create an empty onboot.lst in /tce with
sudo chmod 755 onboot.lst
sudo chown tc.staff onboot.lst
It appears to work as expected (aka as TC 4.1)
-
AppsAudit / OnBoot / Maintenance:
Extension can be added to the onboot list, but can!t be removed.
-
Installed Xorg-7.6 It doesn't work, at least do not see any video card. I see still the Xvesa screen. No log file, nothing related in syslog.
lxrandr reports empty list which means it can communicate to Xorg.
In 4.1 it works, Xorg starts properly in confless on same machine.
-
Edit I guess I should read what RobertS told in the intro but I usually
fail to read and get text when there is much to read though.
I only see a black screen with a prompt.
okay I know more now. One should have this in the code?
lst=xbase.lst waitusb=5
And RobertS says it should be /boot/ and not /core/boot/
okay but that means that all the other Linux distros need to hide their /boot/
just for me testing Core?
I use this code for frugal boot.
title Core 4.2RC3 /tce/boot/ntfs-3g.gz fluff kmap=qwerty/fi-latin9 tce=sda3
find --set-root --ignore-floppies /core/boot/vmlinuz
kernel /core/boot/vmlinuz showapps noswap syslog vga=792
initrd /core/boot/core.gz
Should I change to this one to get ntfs ability?
initrd /core/boot/ore.gz /core/boot/ntfs-3g.gz
or is the ntfs-3g.gz built in now or does it still need to be added manually?
-
Installed Xorg-7.6 It doesn't work, at least do not see any video card. I see still the Xvesa screen. No log file, nothing related in syslog.
lxrandr reports empty list which means it can communicate to Xorg.
In 4.1 it works, Xorg starts properly in confless on same machine.
my experience: xorg76 works on my desktop (with conf) with the 4.2rc2 (I loaded ALL files of the rc directory in particularly the DEP files which were updated).
update.. confless rc2 => works for me
update.. rc3 => conf or confless.. it works
-
So if I get it at all which I am not sure of?
From the announcement post:
Quote
...
TinyCore is simply the kernel + core.gz + Xvesa.tcz|Xorg.tcz + (user's choice of Window Manager) + (optionally wbar.tcz)
Obviously tcz extensions are located in the tce directory.
So should I download these then and put them in the core directory?
Xvesa.tcz
Xorg.tcz
Xprogs (is that Xprogs.tcz ?)
Window Manager (okay I chose one? When does one do that?)
wbar.tcz
And Xprogs and Window Manager I can chose among those at the download list?
So would them get included automatically or does one call them from the prompt or what?
-
Edit I guess I should read what RobertS told in the intro but I usually
fail to read and get text when there is much to read though.
I only see a black screen with a prompt.
okay I know more now. One should have this in the code?
lst=xbase.lst waitusb=5
And RobertS says it should be /boot/ and not /core/boot/
okay but that means that all the other Linux distros need to hide their /boot/
just for me testing Core?
I use this code for frugal boot.
title Core 4.2RC3 /tce/boot/ntfs-3g.gz fluff kmap=qwerty/fi-latin9 tce=sda3
find --set-root --ignore-floppies /core/boot/vmlinuz
kernel /core/boot/vmlinuz showapps noswap syslog vga=792
initrd /core/boot/core.gz
Should I change to this one to get ntfs ability?
initrd /core/boot/ore.gz /core/boot/ntfs-3g.gz
or is the ntfs-3g.gz built in now or does it still need to be added manually?
I think you are doing too much at the same time:
- testing unstable version
- in frugal environment
- with NTFS
One of the would be enough to play with. My advise just take an USB stick and stable TC 4.1 to play with and learn TC. Next go for NTFS and frugal. When you are familiar with these, for fun play with actual RC.
-
Thanks Markus, I've read now your struggles with RC1
so I have much more to read before I get what one are supposed to do.
You give a good advice but I already have TCL 4.0 going on NTFS
on my Acer D250 Netbook so wanted to test the newest thing.
But I found this very important text by or from RobertS
...NTFS support is deprecated starting with 4.2
core.gz is not able to mount cde on NTFS to continue loading.
However. the cde directory should only reside on iso and not be copied to any hard drive.
Adding the X/GUI extensions to where your normal TCE directory resides will solve your issue,
and is the expected location. This way individual updates to the X/GUI will occur as for any regular extension.
I fail to get this part
"Adding the X/GUI extensions to where your normal TCE directory resides will solve your issue, "
So typical of me I get the first part. NTFS support is deprecated starting with 4.2
The word deprecated? hm have to look up.
1. to express earnest disapproval of.
2. to urge reasons against; protest against (a scheme, purpose, etc.).
3. to depreciate; belittle.
So does that mean that it is impossible or just looked down upon?
That one are on ones own. One should not ask in forum about it
or does it mean that it is impossible?
I would love that somebody who know how to do tell how I get core
with a desktop going even on NTFS.
Your "(go for a) stable TC 4.1 to play with and learn TC. Next go for NTFS"
To learn TC is impossible for me I am not on that level. I just want to use it.
But what you write here "Next go for NTFS " seems to contradict what RobertS told us.
That it can not boot on NTFS "NTFS support is deprecated starting with 4.2"
But deprecated maybe means discouraged but do work if one really want to?
so if you did get it going on frugal install on NTFS then I would love to know the
menu.lst code
-
Finally I got it up and running from USB stick after many trials and discussing with Robert. The key point is, that you can't use the same partition for tce directory and cde. With other words it means, that single FAT partitioned setup is not supported, you need a second LINUX partition for tce. tce= boot option to this partition will create tce and its sub directories and will be found automatically at next boot.
There is one bug still, onboot.lst is not created automatically. If you create an empty onboot.lst in /tce with
sudo chmod 755 onboot.lst
sudo chown tc.staff onboot.lst
It appears to work as expected (aka as TC 4.1)
Very interesting outcome. Thanks for tracking this down. I wonder why the system must operate this way?
-
Good that you remind me of that change.
So from version TCL 4.2 one need two partitions?
Even if using frugal install? Why was that needed.
I got so happy when RobertS included frugal install on NTFS
and a single partition too because I felt a renewed hope for
many Linux distros being usuable for us noobs. So 4.1 is
the latest usable for us then? Will the repo include tcz files
for 4.1 then?
-
So if I get it at all which I am not sure of?
From the announcement post:
Quote
...
TinyCore is simply the kernel + core.gz + Xvesa.tcz|Xorg.tcz + (user's choice of Window Manager) + (optionally wbar.tcz)
Obviously tcz extensions are located in the tce directory.
So should I download these then and put them in the core directory?
Xvesa.tcz
Xorg.tcz
Xprogs (is that Xprogs.tcz ?)
Window Manager (okay I chose one? When does one do that?)
wbar.tcz
And Xprogs and Window Manager I can chose among those at the download list?
So would them get included automatically or does one call them from the prompt or what?
Put the files in the extension directory of your pc:
Xvesa.tcz OR Xorg7.4.tcz OR Xorg7.6.tcz
Xlibs.tcz
flwm-topside.tcz (one windows manager.. or fluxbox.tcz?)
Xprogs.tcz (or not.. in any case only from the testing 4.2rc3 directory)
wbar.tcz (or not)
fltk..tcz (see the file in the 4.2rc3 directory)
I would put these files names in an _42rc3.lst in the tce directory and boot with the code lst=_42rc3.lst
For the reason I never used ntfs and dont know this frugal environment, Im not sure where to put these all extensions files (create a /mnt/sdax/tc_ext/ and ../optional/ where the ..lst is in the tc_ext and all extensions are in the ../optional/ ? just a guess).
-
Thanks floppy, I am booted in TCL 4.1 Stable now and it accepted the files
from 4.0 so that was a good thing indeed.
Thanks for the description. I have to read it again and again because
I am not so good structured things. Very good advices and much appreciated
you took time to help me out.
Now all depends on two things. What the word "deprecated" really means.
Does it means impossible even with nfs-3g.tcz or just discouraged to avoid
that people ask about it on the forum. Does it mean that it works very well but
that RobertS and the team don't want questions about it on the forum so that one
are on ones own and get no help but that it do work as good as in 4.1 which
my post show due to I am able to write this.
Or is core so changed that it is totally impossible to boot? What would be needed
then to get it to boot apart from formatting a partition or using USB? For how long will
TCL 4.1 be supported with repo?
-
Hi newbody
The word deprecated? hm have to look up.
Here is my definition:
Deprecated - A term used to describe something that is considered obsolete and will no
longer be supported or available.
-
Hi newbody
The word deprecated? hm have to look up.
Here is my definition:
Deprecated - A term used to describe something that is considered obsolete and will no
longer be supported or available.
Thanks Rich
But that still to me not being a native speaker does mean that it do work if one stand the disapproval
that it do work if somebody tell how to do it but that it is not supported in that one should not expect
to get official help but maybe would get help from otehrs who also ahve NTFS HD and still love TCL
for it's unique approach and not want to give up on it?
Do you remember if somebody has written that them do boot Core 4.2RC3 on NTFS?
It works so well now when I am in 4.1 so can I not borrow files from 4.1?
-
Does it means impossible even with nfs-3g.tcz or just discouraged to avoid
that people ask about it on the forum. Does it mean that it works very well but
that RobertS and the team don't want questions about it on the forum so that one
are on ones own and get no help but that it do work as good as in 4.1 which
my post show due to I am able to write this.
Or is core so changed that it is totally impossible to boot? What would be needed
then to get it to boot apart from formatting a partition or using USB? For how long will
TCL 4.1 be supported with repo?
I personally dont participate for a discussion of NTFS or not: one time, I helped a colleague for installing TCL on a lenovo netbook with a hdd with ntfs/FAT partitions.
a) we created a linux boot partition for TCL 1GB if I remember (with gparted from tcl on usb)
b) a FAT32 partition for exchanging files between XP/Linux
So, we implemented a multiboot XP/Linux with grub4dos. No need for TCL on ntfs (so, no reson for me to push here..).
A usb is a very clean thing: since you create one (or a sd card on an usb adapter), you can carry your usb (or your sd card) anywhere in the world and boot any (nearly) computer with it! (and your pc)
example: ff somebody is at work and want to read its private mails in the lunch time, it can reboot its pc with the USB (and tcl on it) and connect via usb modem to the net (not via the company network).
The same in internet cafe if the owner accept it.
Or one time I was in a computer shop here in Germany: I wanted to see the internet prices for a samsung N150. I changed the bios setup of the samsung N150 netbook. I booted it with the usb stick. I goes into the internet via my usb modem and could see the internet prices of it (5 minutes for it). Nobody asked for something in the big shop. Nobody complained. I used a shop PC to compare prices.
So, as per bmarkus advice, make a usb.. you will have no regrets.
Personally, I often boot the ubuntu 10.04 notebook from my wife with a tcl on SD card. Its much quicker.
But, why not, I understand you would like to migrate your tcl/nfts system with only few efforts.
-
This statement by bmarkus
Finally I got it up and running from USB stick after many trials and discussing with Robert. The key point is, that you can't use the same partition for tce directory and cde. With other words it means, that single FAT partitioned setup is not supported, you need a second LINUX partition for tce. tce= boot option to this partition will create tce and its sub directories and will be found automatically at next boot.
Indicates a mis-understanding is still present.
You can have a single FAT partition on a USB boot with boot files and tce dir. Just use the tc-install program as provided on CorePlus
On the other hand using third party installation tools is not and cannnot be automatic.
bmarkus insteads chooses to use unetbootin. Obviously unetbootin does not "know" about our distribution, i.e., not listed in the drop choices. Therefore using unetbootin simply copies the entire iso to target.
Obviously on a cdrom we cannot have a tce dir. It would be READ_ONLY and nothing would work insofar as adding extensions. That is why there is a cde directory in the iso! It is also a fact that one cannot have two tce directores in the same partition. Nothing new about that,
It should be obvious that one can use the TinyCore CD or the CorePlus CD READ_ONLY devices to process and access any tce directory on a writable store, i.e., works as expected.
Therefore if one insists on using a third party installation tool and one that does not officially support Core and thereby copies the entirety of the TinyCore iso then you are faced with manual setup of either creating a second partition for your tce dir, or renaming the cde to tce thus indicating that this is not a CD and editing the syslinux.cfg changing cde to waitusb=5 to indicate that is a pendrive.
Then all works as expected.
It is not recommended to have a cde directory on any live working system. The whole point of modularity is the ability to easily upgrade the X/GUI extension separate from the base Core. As witnessed by my recent reposts of Xlibs and Xprogs individually.
Therefore in the case of unetbootin renaming cde to tce is recommended.
Of course it is highly recommended to use CorePlus, much work has gone into this to make an easy and effortless installation with whatever window manager you prefer.
-
floppy I am not here to talk NTFS at all. I hate it too.
I am here to get TCL 4.2RC3 booting and working
on a computer that happen to have NTFS on it and
TCL 4.1 does boot from NTFS so I wanted to know
how do I get this new one to boot despite it is discouraged.
I do have a nfs-3g.tcz that allow that to happen in 4.1 and
some few versions back? 4.0 and maybe even older???
So RobertS does deprecated mean physically and software
impossible or just that you don't want to deal with it anymore.
Can I not borrow files from 4.1 to get it going on 4.2?
-
I'm using 4.2rc3 in much the same way as I used all the previous versions - on a USB stick (*) that already has grub4dos on it with the "distribution files" for both tiny core and micro core grabbed from the repo - so I haven't had occasion to try any installation method other than just updating menu.lst. But I have been following the discussion in this thread and I find that roberts' latest post really cleared things up for me - I may have missed some bits earlier but some of that info was not obvious (or not remembered) before.
If I understand it correctly now, you -can- have a cde directory on media other than a CD but that's not really the point of it and...
You cannot have a cde directory and a tce directory on the same partition.
By the way - 42rc3 is working very well for me in day-to-day tasks.
(*) I'd have sworn that USB stick was still formatted FAT but it turns out to be ext2 - I guess it -has- been a while since I looked at it on a Windows box!
-
Obviously unetbootin does not "know" about our distribution, i.e., not listed in the drop choices. Therefore using unetbootin simply copies the entire iso to target.
Additionally I'd like to add that unetbootin doesn't allays copy structures it's not familiar with, at least this has been our experience. However if creating a USB thumbdrive from a windows pc the Universal Pendrivelinux (http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/) will preserve all functionality when selecting the other Linux option (one of the last entries in the list of distro's).
-
It should be obvious that one can use the TinyCore CD or the CorePlus CD READ_ONLY devices to process and access any tce directory on a writable store, i.e., works as expected.
This feature works reliably. Maybe I should not have been surprised to find extensions loaded from a hdd installed tce directory when booting from an ISO, works great and works consistently.
-
There is one bug still, onboot.lst is not created automatically. If you create an empty onboot.lst in /tce with
Thanks for the heads up, I thought the unusual behavior was a result of something I did wrong, i've been adding missing entries manually, meaning this anomaly is not consistent however exists in my installs.
-
floppy I am not here to talk NTFS at all. I hate it too.
I am here to get TCL 4.2RC3 booting and working
on a computer that happen to have NTFS on it and
TCL 4.1 does boot from NTFS so I wanted to know
how do I get this new one to boot despite it is discouraged.
I do have a nfs-3g.tcz that allow that to happen in 4.1 and
some few versions back? 4.0 and maybe even older???
So RobertS does deprecated mean physically and software
impossible or just that you don't want to deal with it anymore.
Can I not borrow files from 4.1 to get it going on 4.2?
I don't want to deal with the installation of it anymore. XP is near end of life.
I have no desire to get Vista or Win7 or soon to be Win8. I tried my best to use grub4dos to be helpful for XP installs. But still some want nt boot loader mods and not grub4dos. That is too windows specific for me. I have not been a regular user of Windows since 2000. If anyone wants to take over the tcgrub4dos install program please feel free or the creation of an alternate install program. I have even contacted Svolli, a known master of NTFS, to see if he would want to take over the extension. Otherwise I will be withdrawing that particular installation extension.
While I am not purposefully trying to cripple existing NTFS installations of Core. I did find an anomaly which I will correct before final release of 4.2.
Still it will mean manual setup:
1. Copying of X/GUI extensions into existing tce directory.
2. Add them to the beginning of the existing onboot.lst.
3. Copying the core.gz to replace tinycore.gz.
4. And finally adjusting the boot loader, menu.lst, if using grub4dos, to load core.gz instead of tinycore.gz.
-
RobertS thanks for that generous way to deal with it.
I do my best to accomplish that then. It does boot
a long way so I only need to add that lst thing and the
needed tcz files in the right places then it should boot.
When I write
sudo reboot then it know what to do so to my naive take
some kind of OS is booted but seems to not know things
like ls or cd.. so that is surprising. But the splash do thell
that a lot of things work. It set up thongs like network if I get it.
Then it just wait for more things so that is what you talk about
that I need to add.
It is way above my poor grasp but it all looks promising.
I look into it tomorrow late at night here now. So thanks!
-
bmarkus wrote:
There is one bug still, onboot.lst is not created automatically.
Found. Fixed. Thanks!
-
I wrote earlier:
While I am not purposefully trying to cripple existing NTFS installations of Core. I did find an anomaly which I will correct before final release of 4.2.
Found. Fixed. I can now run Core 4.2 booted from existing tinycore NTFS grub4dos setup as per manually copying files explained earlier.
-
Thanks, I hope it helps somebody else because I am not smart enough
to understand it. I will follow the advice and stay with 4.1 and not take
the leap to 4.2
So thanks for answering my naive questions. It was fun while it lasted
but now I have failed so many times that my stamina has run out. Exhausted
and dreary or what word express it best. 4.1 works so no need for 4.2 on my part.
-
core + Xvesa + Xlibs + Xprogs + flwm is working fine for me now
-
Thanks, I hope it helps somebody else because I am not smart enough
to understand it. I will follow the advice and stay with 4.1 and not take
the leap to 4.2
So thanks for answering my naive questions. It was fun while it lasted
but now I have failed so many times that my stamina has run out. Exhausted
and dreary or what word express it best. 4.1 works so no need for 4.2 on my part.
head up.
according roberts post, you can move with 4.2 ahead?
-
oops my English are not that good at grasping too few words.
you can move with 4.2 ahead?
Only if I grasp how to do it?
I ahve tested some 5 times now and at or on each test
I cahnged boot codes and what was in the .lst and so on.
It always ends up with a black screen with a prompt
so it is not loading the needed files.
Sure I should download them from the link but I don't
understand where to put them so I tried to reuse things
from the 4.1 that works well.
Me being on NTFS I would need nfs-3g.tcz don't I?
I simply know too little of what is required of me.
Lack the details. So not sure what you say with these words
you can move with 4.2 ahead? Nope I can not but many others
can most likely grasp what RobertS and others here tell them to do.
I have no idea. Now I go to bed :)
-
Issue with wifi.tcz and xorg76 confless on an asus bicore booting from SD card only in RAM:
the wifi extension dont start (the wifi icon is in the wbar; but by clicking on it nothing happens; nothing in dmesg). Any idea what happens here?
-
@floppy: please post console output from "wifi.sh".
-
@floppy: please post console output from "wifi.sh".
First I had sh no wifi.sh
Then by putting the wifi.tcz out of ondemand and again into the ondemand menue, it is ok.
This is the same behaviour as per minefield.. and opera I am working from now. So, issue solved. a ondemand refresh seems to be necessary