WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
Extension requests / Re: xf86-video-nouveau.tcz -> missing nouveau.ko module
« Last post by Rich on November 09, 2019, 11:43:14 AM »
Hi madmax
I think I figured out the  Unknown symbol drm_legacy_mmap  issue.

Short answer:
Follow Juanitos directions. Then, when you run  make menuconfig , go to  Device Drivers->Graphics support->Nouveau (NVIDIA) cards.
Select  m , then save and exit. Then run  make .  When  make  finishes (several hours) you need to replace your kernel (32 or 64 bit)
with the one that was just built (arch/x86/boot/bzImage  or  arch/ia64/boot/bzImage).

Long answer:
When you enable  Device Drivers->Graphics support->Nouveau (NVIDIA) cards , it adds  CONFIG_DRM_VM=y  to the kernel config
file. This enables  drm_vm.c  to be compiled so the  drm_legacy_mmap  symbol can be resolved.  CONFIG_DRM_VM  is listed as
a  bool  (y or n) which means it can't be compiled as a module. It has to be compiled into the kernel. Since it's not compiled into
your kernel, the  nouveau  driver can't be loaded.

CONFIG_DRM_LEGACY  is not required.
32
Off-Topic - Tiny Core Lounge / Re: Starting out with Tinycore Linux
« Last post by vinceASPECT on November 09, 2019, 08:02:58 AM »
Hello  the Forum,

Right.  So the new user named  starts with machine.

That will include a drive.  True. 

1) Boots  Tinycore  and that is corect until power recycle  (The system hasn't done any useful computing or retained services or data.

2)  The user follows forum advice , but machine in question warns "don't partition drives or re-size them particularly when it's a C  drive of M___t.

3)  The points above in 2 and 1  .   Compiound the issue of said situation.

Essentially  TinyC  won't  go onto  existing  Msoft machines.  without very great risk to existing systems.

what has occurred  to me is having  extra storage Physical devices...........is a way forward.
The  optical drives are burners and shame that the incremental state of Tinycore (itself)  could not be snap shotted forward(s) burned onto a CD disc and read back. (on each new subsequent boot--up )

There  isn't  a big deal  with  any systems  other  than the competition to take complete control over.....of the said hardware.

The systems here are multiples there-of.  They are sort of block chained and run many live instances of Virtual machines off the same single  hardware ......a Bare-metal  Level  ONE .........hypervisor

Amazing to find here that  GPU chips.... system(s)  for many of the the worlds Laptops are designed in my city.

THere could be an APP that can remember TinyC states to the cloud.  Then on power down---and back up, of TCL that APP retrieves the last snap shot and populates TCL  settings to recent state..... It's just a file isn't it.

Can't  TCL put things into an NTFS  partition.....it won't  in any way affiliate with global existing EN-MASS systems.......? 
Whike TCL  is amazing with the totally sterile clean states of it's repeated population of hardware upon start up  (  no viruses are possible)  ..........imho ........it's nothing short of amazing.

Thx again.  Still trying........thanks

V


 

`














33
Off-Topic - Tiny Core Lounge / Re: Starting out with Tinycore Linux
« Last post by vinceASPECT on November 09, 2019, 06:27:06 AM »
Hello  there Forum members.

Your last pos  (reply)  is indeed a good help.  There is a "anomali"  for me in understanding (Dyslexia).

Somehow then the "Universal" storage system is indeed acting a dual  role. WHere-upon it is executing a live operating system's  snapshotted remembered state (ongoing).....

while also it is performing a memory service for GUI top level  user APPS interactions and DATA project files which users create with apps (Saving them in the Universal USB drive)


Most  appreciated the forum has bothered to reply.   

There are some  pen drives at work.    Many of you  forum members may relate to often keeping masses of "information and data"  with just a "what if"  paradigm.   That can result in, ........... what if there are no devices available because they are all filled  with  what i just previously mentioned.

Partitioning and such  can sort of be very intrusive to computing systems.  It's just  a shame there is a simple way that existing media devices can just "mount" tinycore in a protected sort of  virtual thing while everything remaining stays  safe on the existing machine. 

The best thing is "perhaps"  as  recommended  that  "Into the Core" is easiest understanding......well sure.

While it's with reference to general  usefulness of a desktop comp for  opening and creating projects with Tools and saving the data.  Ability to return to that point .

While  Information exists.  It's valuable , Right.
 
The idea that TiCL would do an auxiliary  extra  (extra)  mirroring of data and states.......well .
(my earlier correspondence will point you to the global flaw with all domicile and office based computer system in existence ........ they don't contain any  second physical mirrored drive.
(it's economy really......reason why)

core2usb    great  Title.  (freemium)

While  there is a means..........there is a way.

Thx

V







 



34
TCB Talk / Re: Booting 32bit TC from 64bit efi boots to blank screen with underscore
« Last post by labeas on November 09, 2019, 02:15:52 AM »
After/during a sleep I realized that the "conv=fdatasync" for the `dd` cmnd may be
essential. I found that TC [ash-based] can't do it; so I used another installation.
The resulting `dd` of the *.iso to the unPartitioned USBstik lists as a nice DirTree;
but I still can't find how to use it to boot the RedHat6.2.
With the 2 laptops: W8.1 & W10; both can't read the stik & want to reformat it.
At boot time they both show the USBstik in the menu, but jump to "PXE".
---
I'm wondering if my original TC64-ver7 was installed via a *.iso ;
and how to debug this <boot via *.iso on a USBstik> ?

35
Off-Topic - Tiny Core Lounge / Re: Starting out with Tinycore Linux
« Last post by NewUser on November 08, 2019, 10:23:22 PM »
Hi there, cast-fish. As you are a Windows user, as am I, search Sourceforge.net for core2usb. Once on your PC core2usb-1.6.exe allows you to write any Tiny Core iso to a USB device. Boot to the thumbdrive. Any applications you install will install to the thumbdrive and be on the thumbdrive when you boot to it again (provided you shut down with the GUI and leave Backup selected.
36
TCB Q&A Forum / Re: how to skip custom extensions during tce-update
« Last post by GNUser on November 08, 2019, 09:25:20 PM »
Ah, that explains why some custom extensions were causing errors but not others.
Yes, I can confirm that if md5sum file is missing, the extension doesn't get checked for update. No need for the blacklist file :D
Thanks, juanito.
37
TCB Q&A Forum / Re: how to skip custom extensions during tce-update
« Last post by Juanito on November 08, 2019, 09:02:28 PM »
As I recall, customised extensions will be ignored if they do not have an associated md5sum file.
38
TCB Talk / Re: Booting 32bit TC from 64bit efi boots to blank screen with underscore
« Last post by labeas on November 08, 2019, 03:11:10 PM »
I just hooked into this thread by finding mention of * YUMI  *, not about screens.
My aim is to run some apps-from-the-90s; eg. poplog & mulinux.
Several of us are trying & failing to get poplog running again.
It seems, the easiest way would be to use an OLD linux installation.
So I fetched <Redhat6,2>.rar, which was popular in the 90s.
That expanded to <Rehat6.2>.iso. And a <how2> claimed that:
 `dd if=<redhat.iso> <other args> of=/dev/<USBstik!notApartn?>
would make a USBstik:Installer. Which seems absurd and failed.
Of course the MBR was destroyed ?!
Then I ran the latest YUMI on Win10.; but the GUI/Panel has 2 entries
for the <*iso> :-
1. Select which installation, and Win10 will fetch the *.iso;
2. location of *.iso in your dirTree.
I entered item 2 , of course.
The installer-progress-bar looped at  30% and searching  errorMesgs
 showed it failed to find some strangeNamed file.
Can you confirm & comment on the 2 entries to ID the *.iso ?
Either one would suffice ?
Isn't installing TC to a USBstik from the *.iso CENTRAL KNOWLEDGE
which I lack ?!

39
TCB Q&A Forum / Re: how to skip custom extensions during tce-update
« Last post by GNUser on November 08, 2019, 11:55:31 AM »
Never mind. More sleuthing led me to $TCEDIR/tcz-black.lst
http://forum.tinycorelinux.net/index.php?topic=21445.15
40
TCB Q&A Forum / how to skip custom extensions during tce-update
« Last post by GNUser on November 08, 2019, 11:48:03 AM »
I have some custom extensions that cause tce-update to complain ("Error Could not verify <extension_name>.tcz").
It's just a cosmetic issue, but I was wondering: Is there a way to specify extensions that should be ignored during an update?
Pages: 1 2 3 [4] 5 6 ... 10