O2 Joggler Forum

roobarb! wrote:

dwl99 wrote:Nope - don't know how to!

You can use the command:

Code: Select all

acpi -V

You'll probably need to install that first, mind.

Code: Select all

sudo apt-get install acpi

I know you can read the temperature by cat -ing something too, but I can't remember what off the top of my head.

That was the problem right enough - I have Chromium running with no extensions on the last.fm website & the cpu temp is 71deg!!! I've increased the limit to 75 deg & will see how that goes. What shocking cooling the Joggler must have.

BuZz wrote:you dont want dwell click. if you switch the trigger secondary click off then on, it should work. try pressing once then again and hold. Personally I recommend you get a wireless usb keyboard or something so you can setup everything

make sure if you unmark it, to click/save the setting, then mark it again. I've seen this glitch before, probably some gnome/ubuntu bug.

Thanks. When I unmark it the window and the top bar changes it´s visual look / "theme" - it looks a bit like old Windows 95 - then I click on Close (there is no save
When I mark it again and click Close there is still NO right-click menu....??

I have tried to restart ubunbu in between the unmark and mark......

In Chromium the webpage jumps a bit up and down when I hold my finger steady on the scroll bar - maybe because the mouse funktion is very sensitive ? Does this affect the non working right-click ??

sounds like your settings are corrupt or some are missing (to get the old gtk look). have you tried a different usb stick with a fresh install ? the right click is sensitive to movement yeh, so you have to be quite still (Also the touchscreen is less accurate at the edges)

dwl99 wrote:That was the problem right enough - I have Chromium running with no extensions on the last.fm website & the cpu temp is 71deg!!! I've increased the limit to 75 deg & will see how that goes. What shocking cooling the Joggler must have.

It is a bit of a weird setup, but sufficient for it's normal use. It's only when we start messing that the problems show up!

I find it amusing that the stock cooling can keep the CPU at a stable temperature that's just above that passive trip point. Like it was perfectly designed to put a stumbling block in the way.

I also installed a CPU usage applet & it looks like Chromium is a real resource hog even when doing nothing very much.

Firefox 4 is now available for Ubuntu. To install it, open a Terminal & enter:

sudo add-apt-repository ppa:mozillateam/firefox-stable
sudo apt-get update && sudo apt-get upgrade

*pst*

http://joggler.exotica.org.uk/img/ubunt ... com.img.gz

Just for those who can't wait. My break didn't last that long heh.

BuZz wrote:Just for those who can't wait. My break didn't last that long heh.

This is alpha 3 ?

it is where they were on the 26th march - so after alpha3 and before the beta

BuZz wrote:*pst*

http://joggler.exotica.org.uk/img/ubunt ... com.img.gz

Just for those who can't wait. My break didn't last that long heh.

Well done that man! Would this be an opportune moment to start a Natty thread?

I was thinking I might just rename this thread to natty when it comes along, but perhaps its better to have a new one. PS. i have another update coming out for all the dists i manage. Using a 2.6.38 kernel - and one thing it has a fix for, is the palette issue on the efi framebuffer. so now we can have glitch free graphical boot screens.

New images were generated early morning on the 3rd april, but I didn't have time to update the news etc yet.

for those that can't wait :

http://joggler.exotica.org.uk/img/ +

ubuntumaverick-v1.9-btrfscom.img.gz
ubuntumaverick-v1.9-btrfs.img.gz
ubuntumaverick-v1.9-ext4.img.gz

jolios1.2-v1.2-btrfscom.img.gz
jolios1.2-v1.2-btrfs.img.gz
jolios1.2-v1.2-ext4.img.gz

linuxmint10-v1.8-btrfscom.img.gz
linuxmint10-v1.8-btrfs.img.gz
linuxmint10-v1.8-ext4.img.gz

I did build some natty images but one failed so I need to redo it.
enjoy kernel 2.6.38 + normal patches etc. jolios runs nicely here. id be interested in feedback (in relevant thread, dumping it all here due to lack of time)

[edit] natty betas (to use unity 2d (still buggy), logout and choose login session to unity 2d - no go with unity 2d on current drivers im afraid)

ubuntunatty-v1.0beta-btrfscom.img.gz
ubuntunatty-v1.0beta-btrfs.img.gz
ubuntunatty-v1.0beta-ext4.img.gz

Ubuntu Natty
v1.0beta (04/04/2011)

* Initial beta release

Ubuntu Maverick
v1.9 (04/04/2011)

* Updated Kernel to 2.6.38.2 - Includes fix for EFI framebuffer palette bug, so graphical boots now look right
* Packaged vendor wireless driver due to reports of improved stability and better wireless N support
* Updated to latest Ubuntu Maverick/Linux Mint packages

1. me and my friends' JOG always crashed in "power off" and "reboot" progress. many many times!

2. cannot work with a hidden wireless network: when i set my router to “not broadcast”, JOG can not connect into the network, and tune to "broadcast", JOG's wireless connection is okay.
* the officially original firmware has no such problem, and your "commenting out the blacklist line in /etc/modprobe.d/joggler.conf" way does not work.

regards!

deathsatan wrote:1. me and my friends' JOG always crashed in "power off" and "reboot" progress. many many times!

2. cannot work with a hidden wireless network: when i set my router to “not broadcast”, JOG can not connect into the network, and tune to "broadcast", JOG's wireless connection is okay.
* the officially original firmware has no such problem, and your "commenting out the blacklist line in /etc/modprobe.d/joggler.conf" way does not work.

regards!

merged your posts here, as you previously were reporting the issues on this thread, so I don't think we need a new topic.

Please let me know what version of the image you are running. reboot issues were much improved recently. as for hidden networks, again knowing what version you are running can help. you also might want to try other methods of managing the wireless other than network-manager, for example wicd.

BuZz wrote:

deathsatan wrote:1. me and my friends' JOG always crashed in "power off" and "reboot" progress. many many times!

2. cannot work with a hidden wireless network: when i set my router to “not broadcast”, JOG can not connect into the network, and tune to "broadcast", JOG's wireless connection is okay.
* the officially original firmware has no such problem, and your "commenting out the blacklist line in /etc/modprobe.d/joggler.conf" way does not work.

regards!

merged your posts here, as you previously were reporting the issues on this thread, so I don't think we need a new topic.

Please let me know what version of the image you are running. reboot issues were much improved recently. as for hidden networks, again knowing what version you are running can help. you also might want to try other methods of managing the wireless other than network-manager, for example wicd.

running version 1.8

I'm not sure how much I can improve the rebooting, but you can try some additional kernel lines to /boot/grub.cfg "reboot="

warm = Don’t set the cold reboot flag
cold = Set the cold reboot flag
bios = Reboot by jumping through the BIOS (only for X86_32)
smp = Reboot by executing reset on BSP or other CPU (only for X86_32)
triple = Force a triple fault (init)
kbd = Use the keyboard controller. cold reset (default)
acpi = Use the RESET_REG in the FADT
efi = Use efi reset_system runtime service
pci = Use the so-called “PCI reset register”, CF9
force = Avoid anything that could hang.

see http://linux.koolsolutions.com/2009/08/ ... -restarts/ for more information

I currently use reboot=acpi which has improved things from earlier releases (its a built in kernel line so not in grub.cfg)

as for hidden wireless, are you using the network-manager option to connect to hidden network? if that doesnt work, try wicd instead of network-manager, or apt-get install rt2870sta-dkms or use my latest image and then try network-manager/wicd etc.

Just wanted to let you know, BuZz, that 802.11n is working straight out of the box with the bundled updated wireless driver on v1.9.

aah good. thanks for letting me know. I don't have wireless N here, so wasn't really able to test so before, you could only connect as G max on the older (in kernel) driver?