SliTaz Forum

m00dyson

Member

Registered: 2012-04-21

Posts: 14

after updating slitaz 3.0 /stable-repo mouse aren't recognized (just like booting slitaz 4.0)

Where does problem lies in new Xorg? I tried slitaz4.0 LiveCD boot a while ago (7 month ago tbe) in Virtualbox 4.1.20 (and few contemporary before them) and i im left stuckily lying with mouse on center of the screen. And now same thing happened after updating SliTaz 3.0, which previously didnt have those issues, against latest [c]/stable[/c] repository, and writing new [c]rootfs.gz[/c] and after bootup system stuck on desktop.

I have DAMN hardware beneath so is thih VBox issue (shouldn't be) and how come Slitaz 3.0 works perfectly and new builds of xorg/whatever doesnt?

First few times when i just starting with ST3 i thought it could be HW issue but obviously it aint.

btw. where i enter [c]previous.gz[/c] to boot? [Tab] or [c]previous.gz[/c]+[Enter] doesn't work. nor [c]home=/boot/previous.gz[/c]

Trixar_za

Administrator

Registered: 2011-03-29

Posts: 1,506

Re: after updating slitaz 3.0 /stable-repo mouse aren't recognized (just like booting slitaz 4.0)

You DID [c]tazpkg set-release 3.0[/c], right? Otherwise you updated to SliTaz 4's repository...

m00dyson

Member

Registered: 2012-04-21

Posts: 14

Re: after updating slitaz 3.0 /stable-repo mouse aren't recognized (just like booting slitaz 4.0)

I learn yesterday ago about [c]tazpkg set-release[/c] and "trust me. i know what i'm doing" :biggrin: But this aint question here.

After update and until reboot all packages [c]midori[/c], [c]xterm[/c] rolled back [c]gparted[/c] (0.4.6) work fine. But after rebooting newly created SliTaz-3.0-mod stuck in same fashion as with SliTaz-4.0-LiveCD which repo i used ([c]/stable[/c]). So the question is what is so special in new Xorg (wildguess) that same thing having issues to work in Virtualbox (KB, mouse not recognized) nor on HD4650 hardware (gpu driver failed, text mode working). I think that xorg new version shouldnt be so picky about hw on which is running, or even worse to depend on hw (maybe Core i7 vs. K10) on which is built.

btw even [c]spacefm-0.7.0.tazpkg[/c] could be launched (in one version) but desktop stops functioning after that install, all apps except xterm (old [c]xterm[/c] call, before update against [c]/stable[/c]) crashes after SpaceFM install, and nothing can be add to desktop.

So should i recompile xorg myself (if ever) just to have icons and more contemporary desktop like in ST4? Is there some ""easy"" configuration file for xorg that might be reconfigured before rebooting.

And how to mod features in ST3 menu, eg. FatDog uses same OpenBox and all stuff have their own properties on right button menu (not that i like large menus like that) but how else in ST3 can i add-remove menu items and dropmenu aka. right-button features when theres nothing in The Handbook about it?

m00dyson

Member

Registered: 2012-04-21

Posts: 14

Re: after updating slitaz 3.0 /stable-repo mouse aren't recognized (just like booting slitaz 4.0)

I tried boot ST3/ST4 in VMvare Workstation (as Other Linux K2.6x) and SliTaz 4.0 there works :yesss: w/o issues that are in Oracle VirtualBoX (rat+kb arent usable). Everything seems ok except that when i'm inside booted SliTaz machine i cannot escape with my mouse to my host machine, unlike from Win guest, but i must use [Ctrl]+[Alt] keeyboard shortcut to do that.

And everything would be perfect EXCEPT that gparted (neither 0.46 in ST3 that worked in vbox or 0.10 in ST4) doesnt recognize the preallocated disk in .vmdk. There simply are no device to work with. That was in [c]LSI logic (recommeded)[/c] mode (1), then on [c]Bus Logic[/c] (2) and i evn tried [c]LSI Logic SAS[/c] (3) (which needs 3rd party LSI driver) and disk simply wasnt accessible by SliTaz. And under [SysInfo]->[Storage] [c]SCSI Disks[/c] tab was left empty, unlike VBox 4.1.20 where it stands [c]"ATA VBOX HARDISK"[/c]

What should be configured in VMWorkstation for disk to be properly recognized under Linux? Is there a workaround to use options Other Linux K2.4x during VirtualMachinee setup?

Or is this just unknown bug with VM-WS7.1?

It's a bug in WS7.1 ... it all works fine well d-tourly fine if i select [c]IDE HDD[/c] instead of [c]SCSI HDD (recommended by vmware)[/c] and [SysInfo]->[Storage] [c]IDE Disks[/c] tab now show [c]"VMWare Virtual IDE hard Drive"[/c] :woo-hoo: We shuldnnt ask for perfection in this non-free soft which at least works w oldish 2.6.x kernel

But whats wrong with rat'n'kibi suport in VBox w/ newer Xorg in SliTaz4?