Prev: Temp fix for failing automount
Next: VirtualBox loses exec. bit after Yast Online or Manual Update.
From: Darrell Stec on 14 May 2010 18:06
Salvatore Uras wrote:

> Il 13/05/2010 10:50, David Bolt ha scritto:
>>> * VirtualBox can't deal with USB.
>>
>> Get the version from Sun. The OSE version of VirtualBox doesn't have
>> USB support, [...]
> Done and installed, thank you, I actually had only the OSE version in
> all repositories. Seems to work better (seen and installed the USB
> dongle), but still no ActiveSync. Fault of Redmond's taste for black
> magic? They always must try to disrupt all standards... It's a precise
> commercial/political choice, IMO. Anyway, I'm starting to seee the light
> :-) Thank you very much for now, if something else happens I'll post the
> good (or bad) news.
>
> Salvatore.

Have you installed Guest Services on VirtualBox?

--
Later,
Darrell
From: Darklight on 15 May 2010 06:47
Salvatore Uras wrote:

> Il 13/05/2010 14:42, Darklight ha scritto:
>> on my windows mobile. i done this
>> go to start menu then settings -> connections ->
>> usb to pc then check disk drive. Then when you
>> connect you mobile to pc it shows up as a usb stick.
>>
>
> Thanks for answering. Unfortunately the damn thing
> (HTC Touch Diamond) won't work, even in USB disk mode.
> Windows 7 automatically installed the network driver it uses to
> interface with the modem, I suppose, but nothing else.
> I'll have to check on my surviving Windows installation
> to see which drivers are loaded and which hardware is seen.
> Thanks again anyway, everythings helps to cut the problem
> down to its real size.
>
> Salvatore.

how much ram do you have in your phone.
From: Salvatore Uras on 15 May 2010 18:12
Il 15/05/2010 21:28, Darklight ha scritto:
> [...]
> How much ram do you have in your phone if any. i believe that the disk option only
> applies to the add ram/ sdd card
>
It does have a 4GB sdd, that today, for the first time, Linux noticed in
USB disk mode. Crazy.
I've been working on my OpenSUSE installation for a week, but only today
I could see the phone's storage, after trying with 4 virtual machines,
ActiveSync software for Linux, USB... Maybe some hardware issue on my
USB ports? Maybe the phone needed to be reset?
Anyway, Linux is able to detect the bloody thing, and... VirtualBox is, too.
Hypothesis: I've been running the OpenSUSE "desktop" kernel. Yesterday
I installed the ATI proprietary drivers, which require the "default"
kernel (the RPM package installs it if necessary), so now I'm running I
different kernel build. I've not compiled a personalized kernel yet, so
I don't know which setting or feature could cause this difference, but
it's the only visible reason for me. A test could be to boot into the
"desktop" and the "xen" kernels and see if the difference is constantly
binded to this choice.
But not now, I'm tired and happy to see things working ;-) Maybe
tomorrow, and I'll post any news.
Thanks for your kind attention,

Salvatore.

From: David Bolt on 15 May 2010 19:23
On Saturday 15 May 2010 23:12, while playing with a tin of spray paint,
Salvatore Uras painted this mural:

> Il 15/05/2010 21:28, Darklight ha scritto:
>> [...]
>> How much ram do you have in your phone if any. i believe that the disk option only
>> applies to the add ram/ sdd card
>>
> It does have a 4GB sdd, that today, for the first time, Linux noticed in
> USB disk mode. Crazy.
> I've been working on my OpenSUSE installation for a week, but only today
> I could see the phone's storage, after trying with 4 virtual machines,
> ActiveSync software for Linux, USB... Maybe some hardware issue on my
> USB ports? Maybe the phone needed to be reset?

Every so often, my Blackberry does that. It'll work find for weeks and
then the auto-mounting system fails to see it and then needs the phone
to be reset to get it working again. And I know that it's something to
do with the phone because it fails to mount on other my systems until
it's been rebooted.

> Anyway, Linux is able to detect the bloody thing, and... VirtualBox is, too.
> Hypothesis: I've been running the OpenSUSE "desktop" kernel. Yesterday
> I installed the ATI proprietary drivers, which require the "default"
> kernel (the RPM package installs it if necessary), so now I'm running I
> different kernel build.

There was a thread a few weeks, or maybe a couple of moths, ago that
asked about the differences between the desktop and default kernels.
While I know what the differences are, I've not really noticed any
effects of the configure changes between them when swapping between
them. After swapping repeatedly between them I've finally settled to
down and am now using the default selected kernel when booting, which
is actually the desktop version.


Regards,
David Bolt

--
Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s
openSUSE 11.0 32b | | | openSUSE 11.3M4 32b
| openSUSE 11.1 64b | openSUSE 11.2 64b |
TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11

From: Salvatore Uras on 16 May 2010 08:02
Il 16/05/2010 01:23, David Bolt ha scritto:
[...]
>
> There was a thread a few weeks, or maybe a couple of moths, ago that
> asked about the differences between the desktop and default kernels.
> While I know what the differences are, I've not really noticed any
> effects of the configure changes between them when swapping between
> them. After swapping repeatedly between them I've finally settled to
> down and am now using the default selected kernel when booting, which
> is actually the desktop version.
[...]
There's a single effect I'm sure of, because it's consistent and easy to
test: if I use the desktop kernel with ATI gfx drivers, my pointer
disappears - still working, but invisible. Switch kernel - voil� -
switch state.

Greetings,
Salvatore.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Temp fix for failing automount
Next: VirtualBox loses exec. bit after Yast Online or Manual Update.