Installation of aircrack-ng,hashcat,hcxdumptool,hcxpcaptools,reaver

[Sashank999]

Now even the jwm is not opening  . But why ?
In base and norestore, I have loaded all modules one by one with tce-load. I have loaded all firmwares, firmware.tcz, iw.cz, wifi.tcz. I don't know what to do. Please help me.

[Juanito]

Let's start at the beginning..

If you boot with base norestore, load Xvesa, flwm, aterm and wbar and startx, can you start a simple desktop?

If yes, when you exit to the console prompt, load jwm and startx, does the jwm desktop appear?

If yes, when you load the firmware extension for your wifi hardware, then load the wifi extension, does the wifi script run when you double-click on the icon?

[Sashank999]

1)Yes, I see a simple desktop, the one which was default for tinycore.
2)When I previously said jwm, I mistook another window manager that has a "blue colour curling strip" at the bottom left. But, now, jwm loads perfectly.
3)No. When I ran clicked on the icon, xterm opened but gets immediately closed.When I ran sudo wifi.sh in aterm without clicking on wbar, it said no wifi devices found. I ran ifconfig and my wlan0 was not there. Now, I loaded the wireless-5.4.3-tinycore.tcz along with other wifi firmware modules and the wifi works !  .
But still, the normal boot doesn't work.

[Juanito]

When you load the wifi extension, the wireless-5.4.3-tinycore extension should be loaded automatically - if it is not being loaded automatically, it means that the file wifi.tcz.dep is corrupted or missing.

Did you load extensions using the apps gui or tce-load command or did you download them manually with wget, curl or a browser?

If you download extensions manually, which is not recommended, you need to download the *.tcz, *.tcz.dep (where it exists) and *.tcz.md5.txt files.

What do you mean by "the normal boot doesn't work" - do you mean when you boot without base norestore?

[Sashank999]

I always download tcz with app browser only. I don't know how to download them with wget or curl.
Normal boot means with no bootcodes. But only quiet bootcode.

[Sashank999]

Well, in normal mode, when I execute startx, some red and blue colour lines appear and disappear immediately on top of the screen.
Then, xorg says "Server cannot be started(1)."

[Juanito]

Since you machine boots without problems with base norestore, the problem must be with your onboot.lst or your backup.

What do you get from this command:

Code: [Select]

$ cat /etc/sysconfig/tcedir/onboot.lst
Note that you should only have one X server - Xvesa, Xfbdev or Xorg-7.7 - in onboot.lst

[Sashank999]

I only have one -Xvesa on top of onboot.lst. I checked 3 times and confirmed it.

[jazzbiker]

Hi, Sashank999!

Check up Your ~/.xsession. If Xorg rewrote it and it is backed up and restored while every boot, Your startx is trying to start Xorg, despite You have only Xvesa. Check:

Code: [Select]

cat ~/.xsession

If You'll find Xorg in .xsession, simply delete it, then backup, and reboot with Xvesa in onboot.lst

[Sashank999]

There is
"Xvesa -br -screen 1024x768x32 -shadow -2button -mouse /dev/input/mice,5 -nolisten tcp -I >/dev/null 2>&1 &" on top and some other lines.
And hence, I am thinking that startx is launching Xvesa.

[Juanito]

I only have one -Xvesa on top of onboot.lst. I checked 3 times and confirmed it.

I would help if you pasted the contents of onboot.lst

[Sashank999]

I attached it  .
I now did startx.
Then, I saw the core default background and then the background disappeared. Then the wbar appeared. It took some time for the cursor to appear. There are no buttons on the edges of the windows.
I loaded flwm, flwm_topside and also jwm

[Juanito]

good grief 

Make a backup of your original onboot.list:

Code: [Select]

$ cp /etc/sysconfig/tcedir/onboot.lst /etc/sysconfig/tcedir/onboot.lst.orig
..and create a new one containing only:

Code: [Select]

Xvesa.tcz
flwm.tcz
aterm.tcz
wbar.tcz
Then reboot and see what happens.

[Sashank999]

That worked ! 
The wifi is also loaded with some commands in terminal.
Thank you very much. Finally !!!   

[Juanito]

This is a good lesson to only put the absolute minimum of extensions to load "onboot" 

If you always use wifi to connect you can put the relevant firmware extension and wifi "onboot", but the firmware extension must come before the wifi extension in onboot.lst