You are not logged in.
Pages: 1
Have just been trying out the SliTaz Cooking20110329 Live CD and i really liked what i saw. But when i for instance opened the Midori browser i was unable to type in the url of a site i wanted to visit? The same thing thing happened when i opened a terminal and attempted to type: tazpkg recharge and failed?
Could not even consider installing SliTaz to the hard drive unless i could resolve the problem mentioned above.
Offline
what ethernet card do you have?
brand and modell
Is this what you mean?
moldy@dough-ubuntu-linux-uk:~$ dmesg | grep etho
[ 0.185370] i2c-core: driver [adp5520] using legacy suspend method
[ 0.185373] i2c-core: driver [adp5520] using legacy resume method
[ 12.399273] i2c-core: driver [tuner] using legacy suspend method
[ 12.399278] i2c-core: driver [tuner] using legacy resume method
moldy@dough-ubuntu-linux-uk:~$
Offline
The problem is when you type with the keyboard in midori address bar,or xterm the cursor just sits there ?
No letters,numbers, or symbols appear ?
When you boot are you presented with keyboard preferences dialog?
If this is correct kill X and see if you can drop to console with Ctrl+Alt+bkspace
If keyboard won't allow this reboot after adding screen=text to boot code so X won't start.
Does the keyboard display what you type correctly in console?
If this is not the problem be more specific.
Offline
This is exactly what happens, when i type with the keyboard in midori address bar or xterm the cursor just sits there and no letters, numbers or symbols appear?
How would i go about killing X?
Offline
Known Problem: http://labs.slitaz.org/issues/366
Solution described is not something I would recommend for a slitaz newbie.
My suggestion is to use slitaz-3.0 stable which doesn't have this problem.
It's not clear to me what if anything has been done yet to fix the problem on cooking.
Offline
Shall do as you suggest and have a look at SliTaz-3.0 stable. Thanks mojo
Offline
Let remember that "cooking" is beta software...
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]