OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: leland on September 05, 2006, 10:29:40 pm
-
rc2 is out, and the lousy berlioz server is down, so no wiki
I installed the bootstrap image on my tosa, but the console was in all caps, and I couldn't get usbd0 to operate.
So, I installed the gpe-image, had to login, but there is no startx command.
Now off to try opie
-
I installed the bootstrap image on my tosa, but the console was in all caps, and I couldn't get usbd0
to operate.
And you'll never will, since that doesn't exist in 2.6, try usb0 instead (after checking wether g_ether is loaded)
So, I installed the gpe-image, had to login, but there is no startx command
[div align=\"right\"][a href=\"index.php?act=findpost&pid=140813\"][{POST_SNAPBACK}][/a][/div]
Correct, X is started automagically by gpe-dm
-
I installed the bootstrap image on my tosa, but the console was in all caps, and I couldn't get usbd0
to operate.
And you'll never will, since that doesn't exist in 2.6, try usb0 instead (after checking wether g_ether is loaded)
So, I installed the gpe-image, had to login, but there is no startx command
[div align=\"right\"][a href=\"index.php?act=findpost&pid=140813\"][{POST_SNAPBACK}][/a][/div]
Correct, X is started automagically by gpe-dm
[div align=\"right\"][a href=\"index.php?act=findpost&pid=140821\"][{POST_SNAPBACK}][/a][/div]
usbctl is giving me a "No such file or directory error" when I send it paramaters, such as status 0.
if I just enter /sbin/usbctl it returns a help line.
-
usbctl has no usage under 2.6 kernel - I will remove it in rc3
-
Poodle is better than RC1
No horrible sound glitches on startup, although I've yet to try and make it play sounds.
Suspend/Resume still doesn't work in OZ/GPE. . Did anyone ever file a bugreport in the end? If not, how do I? ^^
Either the record/Play memo programs are busted, or there's no sound. . .
Fiddled around in Alsamixer. . . No luck.
Well, It's the end of summer and I need my Z back, So I'm off back to Sharprom, but keep it up. . I'll see if i can catch up with OZ again a few releases onward. ^^
-
Suspend/Resume still doesn't work in OZ/GPE. . Did anyone ever file a bugreport in the end? If not, how do I? ^^
http://bugs.openembedded.org/ (http://bugs.openembedded.org/)
Si
-
just flashed my 6000L to opie/oz/3.5.4.2-rc2 and it's really pretty good (if only my Z were more reliable, sigh)... the default size of the icons is so much better than previous rc, and it seems, well, just smoother especially compared to Sharp & Sharp-derived roms.
I still get the faint orange trails/lines when an image moves across the screen, but that's no disaster.
Kudos to OZ people for taking care of us 6000L users!
-
Has anyone else tried this with bluetooth CF card on a 6000? Whilst "hciconfig -a" shows a working device, and all the usual daemons running, I can't actually DO anything:
* hcitool scan - reports nothing found
* scanning from another box doesn't discover the zaurus
* l2ping from another box won't find the zaurus if I use the mac address of the Z
I can suspend/eject/resume the card exactly as expected, so it's very weird, it's as if the radio in the CF card has been turned off and it's not transmitting or receiving RF.
-
Has anyone else tried this with bluetooth CF card on a 6000? Whilst "hciconfig -a" shows a working device, and all the usual daemons running, I can't actually DO anything
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143623\"][{POST_SNAPBACK}][/a][/div]
after investigation I've found that it will work, but it's very fussy about booting up the Z with the cf card in it... my cf bt card config is set to remain in suspend on insertion. So, I reset/boot Z without CF BT card, when it's up, insert the card, resume it, and then "hciconfig -a" will report the device name (whereas before it would fail and report it couldn't connect to the service)... and then "hcitool scan" will find things.
I didn't find /etc/init.d/bluetooth stop & start solved the problem; I also tried turning off authentication and encryption in hcid.conf.
Maybe an OZ/Opie developer with a 6000 can try and reproduce?