Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: mmrr on March 04, 2009, 10:10:14 PM
-
hello all
five tries from iso using target, a pentium 2 , 266mhz, 160mb ram, in a toshiba satellite 4010cds laptop: various boot parameters tried, including 2 unlisted ones
which made the difference with another linux...'acpi=ht' and 'pci=biosirq'...the kernel didn't recognise the first.
i looked in the forum a bit and saw a list of cheatcodes mentioned as been moved to faq's but i couldn't find them there
thanks for any help, mm
-
Boot codes are in the faq here http://www.tinycorelinux.com/faq.html#bootcodes
Many older laptops were not VESA compliant and with tiny X required framebuffer.
Typically they were 800x600. Is yours? If so we can help.
-
thanks re bootcodes, roberts
that was fast; i was just checking the tc iso on another compu--allok!--
you're right, 800x600, xorg or framebuffer have worked before on target compu
i'll have a look at the codes a few hours, cheers, mm
-
xsetup, base, swapfile=hda3 entered at boot,
after display/mouse choice, a blank screen
all boot options not on pages f2 or f3 declined:
image '*'unrecognised by the kernel
now rebooting with no options, crashed
any useful words? any words, cheers, mm
toshiba laptop 4010cds:
p2/mobile[deschutes]/266mhz/160mb-ram/55gb-hd
video summary:
chips&technologies/chip-f65555 hiqvpro gui accelerator/
vesa oem string-chips 6x555 super vga/ 2mb video memory
-
As far as I know the early Chips&Tech graphics cards do not support Vesa 2.0.
First try to boot to text mode: "tinycore 2"
If it works, see what "Xvesa -listmodes" says.
Then, try text mode with the framebuffer: "tinycore vga=788 2"
If you can get a full-screen framebuffer, the Xfbdev server will work for you.
If all these fail, you need the Xorg extension.
-
booting'tinycore 2', cheers, mm
black screen freeze close to end of start up
rebooting with words 'tinycore textmode'
ok, root on tty1
screen full of listmodes
several of 800x600's..do not have '(no linear framebuffer)' beside them
rebooting with words 'tinycore vga=788 2 tiny core textmode'
root on tty1 again, crashed when i entered 'Xvesa'... i wanted to see list of switches...
rebooting with 'tc textmode tc vga=788 2'
back @tty1...what to do???..........cheers, mm
-
I recently setup a bunch of old Thinkpad 240s which only supports 800x600 framebuffer.
This is what I did for a typical frugal PPR mode install.
1. Make a directory on the laptop's hard drive called tce/
Use existing OS or boot tinycore with textmode.
2. Download and copy the extension Xfbdev.tce to the tce directory
---
3. Boot tinycore with vga=788 textmode restore=hda2 (use whatever partition is available)
4. While tinycore boots you should see the Xfbdev extension being loaded.
5. While in text mode, edit .xsession file to change Xvesa to Xfbdev
6. Type startx to test framebuffer mode.
6. Then perform a backup to keep your new .xsession
---
7. Upon subsequent boots you will need only vga=788
Or add it to your bootloader.
-
1. Make a directory on the laptop's hard drive called tce/
target h-drive has ext2 on 2 empty [hda5/6] and 1 occupied partitions
and a linux swapfile [hda3]....tce/ goes where?
Use existing OS or boot tinycore with textmode...i'll need code for tc textmode please.
2. Download and copy the extension Xfbdev.tce to the tce directory
....more textcode, please,,,i have a modern laptop running tc, in ram,,[ i don't turn it off until target can boot tc] and i'm using it now so if need can d-load to this machine, transfer to target by cd,
3. Boot tinycore with vga=788 textmode restore=hda2 (use whatever partition is available)...available how?? is swap available? ext2 hda5 is empty is better? how one 'restore' what was not there befoer?
4. While tinycore boots you should see the Xfbdev extension being loaded.
5. While in text mode, edit .xsession file to change Xvesa to Xfbdev
.....more code i need, i'm sorry, dammit, but you know how it has to be exactly so, when i just typed help on target screen, i got 'can't open display'...i typed 'mkdir tce/ hda5' ...and prompt popped up as if it had done it but what now,,,i type mkdir help, nothing, i type mkdir man, nothing
6. Type startx to test framebuffer mode.
6. Then perform a backup to keep your new .xsession
---
7. Upon subsequent boots you will need only vga=788
Or add it to your bootloader.
ready to enter code, whatever you suggest i read on one type on another, cheers, mm
-
Since you have provided some specifics, lets try an easier way.
At the boot prompt boot:
tinycore vga=788 textmode tce=hda5 restore=hda5
Note that the code tce=hda5 will automatically create a tce directory on hda5 if none existed.
The restore does not actually restore anything yet, it is providing the location for the backup operation. You can see it is set by looking at /opt/.backup_device
Next copy the Xfbdev.tce into the tce directory I don't know your specifics here, from floppy, pendrive, network, etc.
Next You will need to edit the file .xsession file in your /home/tc directory changing Xvesa to Xfbdev
Then do a backup (filetool.sh backup)
then sudo reboot
All we are trying to do here is to preload Xfbdev.tce extension so that it is available before startx occurs.
Upon subsquent rebooting you should only need
tinycore vga=788
The tce directrory will be autoscanned as well as the restore device.
-
specifics re copying are cd burner in compu running tc in ram, xp natively;;cd reader in target compu
booted as told, target says
'mount: you must specify the filesystem type
'chown: /mnt/hda5/tce: no such file or directory
' done.
'mount: you must specify the file system type
'unable to mount device hda5
'press enter to continue: '
what now, please
hda2 is ext2 with puppy linux installed
-
Assuming you know how to use puppy, make a directory on hda2 called tce.
From puppy copy Xfbdev.tce into tce directory.
Boot tinycore with
tinycore textmode tce=hda2 restore=hda2
edit /home/tc.xsession to change Xserver from Xvesa to Xfbdev
startx
Upon shutdown perform a backup.
-
what i think is to do:
am i making a mistake?
end present livecd attempt on target
reboot target to puppy, [puppy not connecting to net],
'mkdir /tce' is that correct?....or by gui...a directory in root named tce which tc will find at startup
using xp compu go to tce place @ tc website, d-load Xfbdev.tce, cp to cd.
using puppy on target compu, cp from cd to directory--/tce
the rest is clearer for me so if i can get to here then fine.
there may be some simpler way than what i've written out above, so i'll wait awhile in case
any thing is mentioned, thanks, mm
-
The tce directory needs to be a leve 1 /tce
Not under /root/ or any other user or directory.
I am not familiar with Puppy. I know some other members are perhaps they can comment here.
-
i think /tce is first level; i'll try it...thanks, mm
so far so good ...when i booted with tc i caught a glimpse of 'fbdev' as lines whizzed past
i'm at root login on tty1,
when i enter 'edit /home/tc.xsession', reply is '-sh: edit: not found'
i need more code please---full code all the way through to working video, ideally, though
i think that is not always/often possible, thanks, cheers, mm
-
OK. Lets try a no edit approach.
I assume that you have booted with Xfbdev now loaded and are at the $ prompt
type the following commands:
echo "Xfbdev -mouse /dev/psaux,5 -nolisten tcp -I 2>&1 > /dev/null &" > .xsession
echo jwm >> .xsession
startx
-
thanks yr patience
when i enter 'startx'.....
i get a blinking cursor at bottom of tinyx device dependent usage list...
then comes---'error: could not open display'
i try again, same result
still at tty1,,,, tcbox: ~$
after i entered sudo su, then entered startx,
which gave resolution and mouse choices,
then crashed
i'm reading about linux command line
i was reading about the xorg extension to see how hard to set up it might be
[where i read about sudo su]
target machine has card and cable connection to a live ethernet,
could that be reached by the command line?
cheers, mm
-
well i was able in textmode to get a look at .xsession, only shows xfbdev,
i guess that's okay, seemed like i had to sudo su to get there and now i'm
stuck in s-user mode, 'root@box' prompt, so i reran:
echo "Xfbdev -mouse /dev/psaux,5 -nolisten tcp -I 2>&1 > /dev/null &" > .xsession
echo jwm >> .xsession
startx
this time i didn't get the list of dependencies after 'startx'
the prompt just returned for next command but i didn't have one...
i'm not too worried about being su in ram
but would like more guidance, is it xorg time?, target machine uses xorg in another os,
[this waiting makes me think the xfbdev process is coming to a close]
i see 3 sizes of xorg file in repository, not clear which to choose
can the tc textmode use the potential internet connection to bring xorg in to play?
cheers,mm
toshiba laptop 4010cds: pentium2/mobile[deschutes]/266mhz/160mb-ram/55gb-hd
video summary: chips&technologies: chip-f65555 hiqvpro gui accelerator
vesa oem string: chips 6x555 super vga/ 2mb video memory
-
well i was able in textmode to get a look at .xsession, only shows xfbdev,
i guess that's okay, seemed like i had to sudo su to get there and now i'm
stuck in s-user mode, 'root@box' prompt, so i reran:
echo "Xfbdev -mouse /dev/psaux,5 -nolisten tcp -I 2>&1 > /dev/null &" > .xsession
echo jwm >> .xsession
startx
You should not run TC as root.
Having root@box is wrong.
Having only Xfbdev in .xsession indicates that you failed to include the quote marks around the first echo command.
You should boot your system as previously discussed:
tinycore vga=788 textmode tce=hda2 restore=hda2
Then at the
tc@box:~$ prompt enter the following two echo commands:
echo "Xfbdev -mouse /dev/psaux,5 -nolisten tcp -I 2>&1 > /dev/null &" > .xsession
echo jwm >> .xsession
You can check if the full Xfbdev command is there by typing:
cat .xsession
If it is then type
startx
-
okay, entered two echo commands
then cat .xsession,
reply is over 2 lines, first line is the part inside the quotes, second line 'jwm'
then the prompt, enter 'startx'
'error: could not open display'
comes at the bottom of a 2page list of switches
ending with about a dozen under the title
'tiny x device dependent usage:' last is 'vtxx'
i've/we've been here at least three times
if you look at the piece you quoted you will see
that the text includes the quote marks you say i've omitted
at prompt...
tell me how to get out of rootbox without rebooting, please
tell me if can access internet in textmode, please
what about me trying xorg?
if you have more code for me to try, i'm willing to enter it
obviously you're busy, it's a great thing happening here,
if there's a more suitable forum, please tell me about it cheers, mm
-
How are you booting to root? How did you "install"?
You must have some persistentcy with .Xauthority not owned by user tc
-
thanks,
not booting to root, to tc@box
only install i know about is installing fbdev file
i lost previous rootbox when i powered off
i'd like to know how to get out su without powering-off
anything i did su in a ram session dies when the session dies
no? unless some form of save function is active...
please give me some answers to my questions
please tell me where to get code to give tc to see if it will access the internet
via the ethernet[d-link dfe-690txd] card and/or the wireless[airlink awlc3026]
i looked on the install cd's--same windos xp driver for both --Mrv8000c.inf--
please tell me why we are not talking about xorg, if i can see it works i'll happily
shut it down to resume this particular piece of problem-solving if you think it
would be useful.
mm