1
Zaurus - pdaXrom / pdaXrom 1.1.0 - RC1
« on: August 15, 2004, 12:29:44 pm »
Just wanted to pop in 2p and say these lockups doesn't occur on my 860, to strengthen the 700-only case.
Select language:
News:
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
Zaurus - pdaXrom / pdaXrom 1.1.0 - RC1
« on: August 14, 2004, 02:35:32 pm »
Laze,
Yes, I noticed the clock in the taskbar takes a while to update. I checked in a term with date and it was correct, so I wasn't worried.
I'm going to give xfce4 a whirl shortly, since that was my preferred environment in 1.0.5 - although this matchbox install is actually quite nice
I'm actually trying to find something that's broken, and not having much success
Certainly all the apps that are bundled seem fine, good job
Yes, I noticed the clock in the taskbar takes a while to update. I checked in a term with date and it was correct, so I wasn't worried.
I'm going to give xfce4 a whirl shortly, since that was my preferred environment in 1.0.5 - although this matchbox install is actually quite nice
I'm actually trying to find something that's broken, and not having much success
Certainly all the apps that are bundled seem fine, good job
3
Zaurus - pdaXrom / pdaXrom 1.1.0 - RC1
« on: August 14, 2004, 07:34:19 am »
Well, installed like a peach once I worked out how to format internal flash
Everything works so far. Fiddling around in the options and prefs and it all looks fantastic.
network card works fine. networking works fine.
Do we still have no bluetooth support in kernel? That'd be nice to have, I have a Socket card I'd like to get working.
Just testing that the time doesn't lapse now by setting it then suspending for a while..
Everything works so far. Fiddling around in the options and prefs and it all looks fantastic.
network card works fine. networking works fine.
Do we still have no bluetooth support in kernel? That'd be nice to have, I have a Socket card I'd like to get working.
Just testing that the time doesn't lapse now by setting it then suspending for a while..
4
Zaurus - pdaXrom / pdaXrom 1.1.0 - RC1
« on: August 14, 2004, 06:21:40 am »
:rushes off to try it out:
I'll check back as soon as I have anything more useful to add
I'll check back as soon as I have anything more useful to add
5
Zaurus - pdaXrom / pdaXrom 1.0.5 progress report
« on: July 02, 2004, 06:54:40 pm »
Well from what I can make out, my major problem at the moment is the kernel in pdaXrom 1.0.5 simply doesn't have the required -mh patches to get any bluetooth to work.
I have 2.4.18-rmk7-pxa3-embedix, I presume the same as everyone else?
I can get hciconfig to display my device, along with a MAC, and hcitool scan finds stuff; I can ping bluetooth things and pair, but rfcomm point blank refuses to work with errors such as "rfcomm0: no such device" and occasionally "rfcomm: can't open control channel" and suchlike.
My card (Socket Rev G) also refuses to do anything at all if I take it out and put it back in, or suspend, or even don't boot with it inserted. That I can live with for now, I'd rather get rfcomm working to some degree.
But as I say, I believe the rfcomm problem is simply due to the kernel lacking -mh patches. If that's not the case, I'm very happy to debug with someone on IRC.
I have 2.4.18-rmk7-pxa3-embedix, I presume the same as everyone else?
I can get hciconfig to display my device, along with a MAC, and hcitool scan finds stuff; I can ping bluetooth things and pair, but rfcomm point blank refuses to work with errors such as "rfcomm0: no such device" and occasionally "rfcomm: can't open control channel" and suchlike.
My card (Socket Rev G) also refuses to do anything at all if I take it out and put it back in, or suspend, or even don't boot with it inserted. That I can live with for now, I'd rather get rfcomm working to some degree.
But as I say, I believe the rfcomm problem is simply due to the kernel lacking -mh patches. If that's not the case, I'm very happy to debug with someone on IRC.
6
Zaurus - pdaXrom / pdaXrom 1.0.5 progress report
« on: July 02, 2004, 06:50:11 am »
I made a donation of a couple of hundred dollars a few days ago, so can I get some decent Bluetooth support in the kernel please? Pretty please?
7
Zaurus - pdaXrom / pdaXrom 1.0.5 progress report
« on: June 29, 2004, 04:07:25 am »
That progress report is looking very promising Laze
I see no mention of which kernel you're bundling with this release? Are you going to update it from 1.0.5 - which seems to have very little in the way of BT support? (2.4.18 with no -mh patches)
I see no mention of which kernel you're bundling with this release? Are you going to update it from 1.0.5 - which seems to have very little in the way of BT support? (2.4.18 with no -mh patches)
8
Zaurus - pdaXrom / Help - Bluetooth woes with Socket Rev G
« on: June 24, 2004, 06:11:07 am »
Hello,
I did post this to the Accessories forum, but it's only had 7 views in the last couple of days, so it's not really getting much attention and no hope of any help/reply, so maybe here is better - I think this is probably pdaXrom related after all, anyway.
I have a Socket Bluetooth card, Revision G, and I'm finding that I can't get it to do *anything* after I remove it and put it back in. In fact, I have to boot with the card in the slot to make it work at all - if I subsequently take it out and put it back in, it ceases to do anything.
I know it's not the card, because I have a Bluemonkey that does exactly the same. I have to boot in order to get hciconfig to show me anything.
cardctl status shows the card being [ready] after I reinsert it. I've tried dozens of combinations of bluetooth restarting and cardctl resuming etc with absolutely no joy.
Does anyone have any clues to throw me? And ideas why this happens? I'm quite tempted to reflash (using pdaXrom 1.0.5) and start over, I think it's fairly possible I've broken something quite fundamental sad.gif
I haven't actually got rfcomm to work even when hciconfig shows me output yet, but that's another story for another post once I get this fixed - I think it's because the kernel in pdaXrom 1.0.5 doesn't have any -mh patches? So, has anyone managed to get bluetooth of any form working in pdaXrom with the default kernel?
I'm rather hoping the new release will have an upgraded kernel..
I did post this to the Accessories forum, but it's only had 7 views in the last couple of days, so it's not really getting much attention and no hope of any help/reply, so maybe here is better - I think this is probably pdaXrom related after all, anyway.
I have a Socket Bluetooth card, Revision G, and I'm finding that I can't get it to do *anything* after I remove it and put it back in. In fact, I have to boot with the card in the slot to make it work at all - if I subsequently take it out and put it back in, it ceases to do anything.
I know it's not the card, because I have a Bluemonkey that does exactly the same. I have to boot in order to get hciconfig to show me anything.
cardctl status shows the card being [ready] after I reinsert it. I've tried dozens of combinations of bluetooth restarting and cardctl resuming etc with absolutely no joy.
Does anyone have any clues to throw me? And ideas why this happens? I'm quite tempted to reflash (using pdaXrom 1.0.5) and start over, I think it's fairly possible I've broken something quite fundamental sad.gif
I haven't actually got rfcomm to work even when hciconfig shows me output yet, but that's another story for another post once I get this fixed - I think it's because the kernel in pdaXrom 1.0.5 doesn't have any -mh patches? So, has anyone managed to get bluetooth of any form working in pdaXrom with the default kernel?
I'm rather hoping the new release will have an upgraded kernel..
9
Accessories / Socket BT Rev.G refuses to work after removal
« on: June 23, 2004, 09:49:28 am »
Hello all,
I have a Socket Bluetooth card, Revision G, and I'm finding that I can't get it to do *anything* after I remove it and put it back in. In fact, I have to boot with the card in the slot to make it work at all - if I subsequently take it out and put it back in, it ceases to do anything.
I know it's not the card, because I have a Bluemonkey that does exactly the same. I have to boot in order to get hciconfig to show me anything.
cardctl status shows the card being [ready] after I reinsert it. I've tried dozens of combinations of bluetooth restarting and cardctl resuming etc with absolutely no joy.
Does anyone have any clues to throw me? And ideas why this happens? I'm quite tempted to reflash (using pdaXrom 1.0.5) and start over, I think it's fairly possible I've broken something quite fundamental
I haven't actually got rfcomm to work even when hciconfig shows me output yet, but that's another story for another post once I get this fixed..
I have a Socket Bluetooth card, Revision G, and I'm finding that I can't get it to do *anything* after I remove it and put it back in. In fact, I have to boot with the card in the slot to make it work at all - if I subsequently take it out and put it back in, it ceases to do anything.
I know it's not the card, because I have a Bluemonkey that does exactly the same. I have to boot in order to get hciconfig to show me anything.
cardctl status shows the card being [ready] after I reinsert it. I've tried dozens of combinations of bluetooth restarting and cardctl resuming etc with absolutely no joy.
Does anyone have any clues to throw me? And ideas why this happens? I'm quite tempted to reflash (using pdaXrom 1.0.5) and start over, I think it's fairly possible I've broken something quite fundamental
I haven't actually got rfcomm to work even when hciconfig shows me output yet, but that's another story for another post once I get this fixed..
10
Zaurus - pdaXrom / Date/Time Setting
« on: June 22, 2004, 12:47:13 pm »
I'm making a donation for you now too
You should make some betas available of the rom for those of us willing to reflash a few times, we're a good testing ground honest
You should make some betas available of the rom for those of us willing to reflash a few times, we're a good testing ground honest
12
Zaurus - pdaXrom / BusyBox upgrade broke local login
« on: April 16, 2004, 11:04:24 am »
Hello,
I\'ve just managed to break my pdaXrom install by upgrading BusyBox. I used the latest snapshot from the busybox site, built it using the SDK, and all went well - I got a binary that worked, all the symlinks got created when I ran ./busybox --install -s and I could quite happily use all the utilities it provided.
The only thing that didn\'t work as far as I could see was top didn\'t display the command names. I thought a reboot might solve that, so I rebooted.
Upon coming back up, there was an applet not found error, albeit with no more useful information than that, and the console wouldn\'t accept my root password (or a user account password I\'d previously created.)
the busybox binary was suid root (so passwd and ping etc would work), but I don\'t think that\'d matter for local login since everything is running as root anyway.
Since after my re-flash tonight I\'m going to want to upgrade busybox again (not least because the busybox that comes with the ROM is missing so much), so does anyone have any clues about what I might have done? I quite carefully checked that I wasn\'t missing out any applets, but I guess I must have. Or one of my internal compile options was wrong?
I\'ve just managed to break my pdaXrom install by upgrading BusyBox. I used the latest snapshot from the busybox site, built it using the SDK, and all went well - I got a binary that worked, all the symlinks got created when I ran ./busybox --install -s and I could quite happily use all the utilities it provided.
The only thing that didn\'t work as far as I could see was top didn\'t display the command names. I thought a reboot might solve that, so I rebooted.
Upon coming back up, there was an applet not found error, albeit with no more useful information than that, and the console wouldn\'t accept my root password (or a user account password I\'d previously created.)
the busybox binary was suid root (so passwd and ping etc would work), but I don\'t think that\'d matter for local login since everything is running as root anyway.
Since after my re-flash tonight I\'m going to want to upgrade busybox again (not least because the busybox that comes with the ROM is missing so much), so does anyone have any clues about what I might have done? I quite carefully checked that I wasn\'t missing out any applets, but I guess I must have. Or one of my internal compile options was wrong?
13
Zaurus - pdaXrom / Key Mapping and Mouse Buttons
« on: April 14, 2004, 05:42:33 pm »
zxerx, that works perfectly
In aterm, I do actually have to do Shift-Function-Up/Dn. If I just do Shift-Up, it scrolls up one line. Function-Up does nothing. So I guess that\'s working fine
Coincidentally, it didn\'t work in xterm at all - just as well I don\'t use it anymore
Thanks la lot!
In aterm, I do actually have to do Shift-Function-Up/Dn. If I just do Shift-Up, it scrolls up one line. Function-Up does nothing. So I guess that\'s working fine
Coincidentally, it didn\'t work in xterm at all - just as well I don\'t use it anymore
Thanks la lot!
14
Zaurus - pdaXrom / Key Mapping and Mouse Buttons
« on: April 13, 2004, 07:48:43 am »
Did you get PageUp/Down working with xmodmap? Could you paste the relevant section of config by any chance?
15
Zaurus - pdaXrom / Date/Time Setting
« on: April 11, 2004, 07:20:40 pm »
hwclock hangs on me too, but I can just Ctrl-C it - it doesn\'t lock the OS.