diejuse has quit [Quit: Leaving.]
xmn has joined #maemo-leste
Oksana has joined #maemo-leste
l_bratch has quit [Ping timeout: 240 seconds]
l_bratch has joined #maemo-leste
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Changing host]
Danct12 has joined #maemo-leste
mardy has joined #maemo-leste
belcher has quit [Ping timeout: 268 seconds]
belcher has joined #maemo-leste
diejuse has joined #maemo-leste
<mighty17[m]> Sudo in x term doesnt ask for password, is there no root pass (toor acc to wiki)
<parazyd> There is a root password
<parazyd> Try "su"
<parazyd> sudo currently just doesn't ask for a password.
<mighty17[m]> Ah okay sudo not asking pass was concerning
<mighty17[m]> Also what matric client do u suggest to use
<parazyd> Yeah there's a NOPASSWD entry in /etc/sudoers
<parazyd> I don't know, not a matrix user.
<mighty17[m]> I tried nheko but virtual keyboard didn't pop up
<parazyd> You'll want gtk2 for automatic vkb.
<parazyd> Also we should try to set up shortcuts so you can open the vkb anywhere.
<mighty17[m]> Which we don't have?
<mighty17[m]> Yeah like phosh has
<mighty17[m]> also what sets the mAh in battery? dts? rootfs?
<parazyd> So, RaiseVkb=XF86Search
<parazyd> You could try setting this to some key.
<parazyd> For the battery, it can be different from device to device, so I can't give you a correct answer.
<mighty17[m]> yeah, my battery is 4000mah but inidcator says its 2000
<parazyd> Might need calibration?
<parazyd> Usually that's done by making a full charge, and then a full discharge.
<mighty17[m]> didnt know that, thanks
<parazyd> But also the battery applet in Leste could have issues. Wizzup worked on the upower setup so he knows more than I do.
<mighty17[m]> RaiseVkb=XF86Search > umm i dont have any extra keys
<mighty17[m]> just pure screen :D
<parazyd> You could use a volume key
<parazyd> Or you have no buttons at all?
<mighty17[m]> vol key is broken
<parazyd> :o
scops has quit [Quit: Reconnecting]
scops has joined #maemo-leste
diejuse has quit [Quit: Leaving.]
rafael2k has quit [Ping timeout: 244 seconds]
rafael2k has joined #maemo-leste
diejuse has joined #maemo-leste
<sicelo> upower uses /sys/class/power_supply/* ... so 1st, does /sys have correct capacity?
<lel> parazyd created a repository: https://github.com/maemo-leste/ui-fonts
<lel> parazyd edited a repository: https://github.com/maemo-leste/ui-fonts
l_bratch has quit [Quit: Leaving]
l_bratch has joined #maemo-leste
uvos__ has joined #maemo-leste
<mighty17[m]> sicelo ig u need power supply info from maemo as well? :p
diejuse has quit [Quit: Leaving.]
<parazyd> mighty17[m]: Yeah that's what he's asking
diejuse has joined #maemo-leste
<mighty17[m]> parazyd my question is different iirc he wanted pm comparison of Tab2 and droid4 as Tab2 has old uboot so dmesg says pm isn't available (pm = power management)
diejuse has quit [Read error: No route to host]
<uvos__> no he wanted to kown if cat /sys/class/power_supply/*/charge_full_design has the right mAh value
<uvos__> as this is your responsability to set in the battery driver
<uvos__> either by dts bindings or the driver autodetecting it via nvram
diejuse has joined #maemo-leste
Pali has joined #maemo-leste
<parazyd> freemangordon, Wizzup: Is also wpa_supplicant from devel supposed to go to stable?
<Wizzup> no no no
<parazyd> lol ok
<parazyd> Just asking
<parazyd> I'm going to promote what I can today
<uvos__> btw parazyd we should maybe flip on charge-mode for devel
<parazyd> uvos__: ok, let me clean devel up first and then do further tweaks
<uvos__> ok
<parazyd> I don't like it when there's too many packages there.
<Wizzup> parazyd: also do not promote icd stuff
<uvos__> also not mce
<parazyd> Wizzup: ACK, fmg told me about connui
<parazyd> Nothing else
<parazyd> uvos__: ok
<parazyd> sec
<parazyd> This is what we have there atm
<uvos__> imo we can promote mapphone-kexecboot-*
<uvos__> fbkeyboard is fine too
<uvos__> whats the change in hildon-desktop
<uvos__> ?
<parazyd> So I'm thinking: connui (without cellular), kexecboot configs, hildon-meta, fbkeyboard, gtk2, matchbox+hd
<uvos__> ah its a code style change
<uvos__> you can promote that
<parazyd> uvos__: it's built because of matchbox also, your 49fbe681b34794cc6501d2a024870143abe41b21 patch
<parazyd> > Fix fullscreen handling for fullscreen override redirect windows
<uvos__> oh that
<uvos__> yeah we can promote it
<parazyd> Wizzup, uvos__: What about osso-systemui powerkeymenu/splashscreen/tklock ?
<Wizzup> sorry, I can do this later but not right now
<Wizzup> I think those are probably fine, though
<uvos__> parazyd: yes those are needed bugfixes
xmn has quit [Quit: ZZZzzz…]
<uvos__> related to the machbox change
<uvos__> you must promote togehter
<parazyd> uvos__: You mean systemui+matchbox?
<uvos__> yes
<parazyd> ACK
<parazyd> Thanks
<parazyd> uvos__: Are you using dsme on your devel device?
<uvos__> parazyd: yes no
<parazyd> ok, I mean, you haven't noticed any problems or something?
* parazyd hasn't
<uvos__> parazyd: no
<parazyd> ok
<uvos__> parazyd: but i changed several init scripts to remove dsmetool
<uvos__> and i dont load the dsme mce module
<uvos__> so dsme is pretty impotent on my device
<parazyd> ok, this is unrelated
<uvos__> idk if id notice if it breaks
<uvos__> ok
<uvos__> the kerecv change also looks fine
<parazyd> *nod*
<uvos__> byw you might want to keep osso-systemui-splashscreen in devel
<uvos__> no one has tested this yet
<uvos__> and its unfinished afaik
<parazyd> True
<uvos__> but we also dont use it
<uvos__> hildon-input-method is fine
<uvos__> this was just the utf8 change
<uvos__> i thnk thats it
<parazyd> mhm
<mighty17[m]> either by dts bindings or the driver autodetecting it via nvram > okay, i will try a full charge and discharge first to get it calibrated
uvos__ is now known as uvos
<uvos> mighty17[m]: this wont help if dts is wrong
<uvos> probubly
<uvos> any sane driver will reject a cal value so different from charge_full_design
<mighty17[m]> i havent put any info in dts about battery size
<uvos> your driver might not have dts bindigns for this
<uvos> cpcap dosent for instance
<uvos> isntead you might have to add your battery to the driver
<mighty17[m]> max17042 fuel gauge ig
<mighty17[m]> and my charger isnt in mainline :P
<uvos> its about the fule gage
<uvos> max17042 has some way to detect or gain the capacity
<uvos> you have to figure out what it is and add your battery
<uvos> yeah well read the driver source
<mighty17[m]> `cat charge_full_design > 5333500`
<mighty17[m]> idk what unit that is in
<uvos> driver sets it writable then
<uvos> cpcap dose this too but its not nesscarly the right way to do it
<uvos> (might also be the only way .. read the driver)
<uvos> nothing in leste dose this btw
<uvos> 2000000 is likely simply the default
<uvos> on the drivers side
<mighty17[m]> oh so most likely i have to specify it somewhere
diejuse has quit [Quit: Leaving.]
lioh has joined #maemo-leste
<lioh> hi all. I am facing the issue that Maemo Leste boots fine on my N900 (I can see the boot messages) but I don't get a graphical interface.
<lioh> It was working already but currently the screen just stays blank after boot
<parazyd> Do you wait enough time? I tried a fresh flash yesterday and it took me a minute to show up.
<parazyd> Like, actual 60-70 seconds
<lioh> I have waited that time, but battery level is already in the lower part, so maybe it's related to that. I am going to charge now and try again.
<parazyd> It might be. You can also boot to Fremantle and charge it normally.
<lioh> I have flashed uboot so no fermantle anymore I guess
<lioh> also I always have to type run sdboot after startup.
<lioh> One time I got a selection Menu from uboot, but since then I have never seen it again and I don't know how to trigger it
<parazyd> Boot with the keyboard opened
<parazyd> This'll get you to u-boot
<parazyd> If it's closed then it automatically boots to fremantle iirc
<lioh> Which does not seem to be available anymore after running sudo ./0xFFFF -m u-boot-2013.04-2.bin -f
<lioh> Is there a way to flash both? on the internal storage fermantle and leste on the sd-card?
<lioh> Maybe even using 0xFFFF?
<parazyd> Pali: Maybe you know? ^
<parazyd> On mine I installed u-boot through fremantle, not with 0xffff so I'm not sure.
<parazyd> In any case, you might also be able to charge it while it's powered off. It's just that sometimes when you plug in, the phone powers on.
<uvos> its just the appended kernel missing
<parazyd> I don't know if charging works in u-boot
<uvos> so you should be able to somehow append the kernel
<uvos> idk why we dont just have a image for people to install
<uvos> that has the freemantle kernel appended
<parazyd> Because there are different kernels for fremantle
<uvos> sure but the latest/last one should work fine with anything right?
<uvos> or dose pvr get in the way?
<uvos> its static anyhow no?
<lioh> so you thing fermantle is still on the emmc and should still be bootable?
<lioh> hmm if i select internal emmc on uboot menu it is unable to find the relevant partitions
<Wizzup> parazyd: this is the second report of this happening recently I think
<Wizzup> I can test the latest image on mine and see what hapens
<Wizzup> also, we should probably figure out what log files are most relevant
<parazyd> mtg now, bbl
<Wizzup> openrc can also log
<Wizzup> :p
<Wizzup> lioh: I'll try to reproduce this today or tomorrow at latest (also in mtg atm)
venji10[m] has quit [Quit: Bridge terminating on SIGTERM]
ajr has quit [Quit: Bridge terminating on SIGTERM]
mighty17[m] has quit [Quit: Bridge terminating on SIGTERM]
tvall has quit [Quit: Bridge terminating on SIGTERM]
scops has quit [Quit: Bridge terminating on SIGTERM]
tvall has joined #maemo-leste
scops has joined #maemo-leste
ajr has joined #maemo-leste
venji10[m] has joined #maemo-leste
mighty17[m] has joined #maemo-leste
lioh has quit [Remote host closed the connection]
lioh has joined #maemo-leste
<lioh> is there a way to increase screen brightness on boot?
<parazyd> In u-boot? Don't think so.
<parazyd> Booting normally with the power button should enable backlight
<mighty17[m]> `PVRMMapRemoveRegisteredArea: psOffsetStruct 0xdb27724a for memory area 0x0x6051b23f is still mapped; psOffsetStruct->ui32Mapped 1 [1754, rivers/gpu/drm/pvrsgx/1.9.2253347/services4/srvkm/env/linux/mmap.c` hm?
<mighty17[m]> also also `iptables/1.8.2 Failed to initialize nft: Protocol not supported` happened when i installed anbox, ig we need CONFIG_NFT_COMPAT in defconfig
<uvos> the prv problem is known
<uvos> the pvr driver is just broken in 5.11
<uvos> anbox wont work on your device
<uvos> its broken on 32bit
<uvos> and its bronken on pvr
<parazyd> uvos: I think it does work on 32bit, it's just pvr that is the issue.
<parazyd> Could try on Raspberry
<uvos> parazyd: input is broken
<uvos> parazyd: according to the guy who integrated it for pmos
<parazyd> oh
<uvos> also the bugreport on anbox github
<parazyd> Yeah I remember, it was quite a while ago
<parazyd> Didn't check if things changed.
mrgeanie has quit [Quit: The Lounge - https://thelounge.chat]
mrgeanie has joined #maemo-leste
cockroach has joined #maemo-leste
<uvos> i think we should just silence that pvr warning for now
<mighty17[m]> uvos: so anbox will work or not? i can go back to 5.10 or smth
<uvos> no anbox dosent and will likey never work on your device
<uvos> and even if it did
<uvos> it really needs more than 1gb ram
<mighty17[m]> i can give it swap/zram
<mighty17[m]> i dont have a 16gb sd card for nothing :P
<parazyd> It's not a magic bullet
<mighty17[m]> also yeah u have a point with 32 bit so yeah
<uvos> the 32 bit bug can be fixed
<uvos> pvr is the problem
lea_ has joined #maemo-leste
lea_ has quit [Ping timeout: 268 seconds]
<lioh> what is the default screen lock code?
<mighty17[m]> 1234
<sicelo> lioh: flashing u-boot does not touch fremantle rootfs or emmc
<mighty17[m]> 12345
<lioh> mighty17[m], does not work for changing the code (complains it's wrong)
<mighty17[m]> That's the default keycode ^^
<lioh> ahhh
<mighty17[m]> Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.
<lioh> n900
<parazyd> If your device is locked, this might be the reason desktop isn't showing up
<parazyd> Wizzup knows the intricacies of this on Leste
<lioh> desktop is showing again after putting it to charge
<sicelo> If you have lock code issues, you might have easier time if you first fix your Fremantle ... there are ways to recover it. Search tmo (talk.maemo.org)
<lioh> device lock is currently disabled
<sicelo> Ah, ok
<lioh> yes, but if i understood you right, i should only need to add fermantle to the bootloader right?
<lioh> Or does it chain-boot?
<lioh> Loading the Fermantle bootloader from the emmc using u-boot?
<lioh> Because just selecting 'boot from emmc' in the uboot menu does not work as mentioned
<lioh> and reflashing Fermantle is really a mess. At least on a recent x86_64 system. I have already found an old debian live image containing flasher. maybe I could give this one a try
<Wizzup> lioh: so did you manage to make leste rende rok on boot, or is there still a problem with the image?
<uvos> "[13:46] <lioh> desktop is showing again after putting it to charge"
<uvos> not sure why the device would hang somewhere before hildon when the battery is low
<uvos> instead of eg. powering back off
<parazyd> tbh it might be powering off
mrkrisprolls has quit [Remote host closed the connection]
Oksana has quit [Ping timeout: 268 seconds]
diejuse has joined #maemo-leste
mrkrisprolls has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Changing host]
xmn has joined #maemo-leste
Daanct12 has joined #maemo-leste
Daanct12 has quit [Changing host]
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 268 seconds]
_whitelogger has joined #maemo-leste
<sicelo> I don't think reflashing Fremantle is really a big mess :-)
<sicelo> Anyway, since lock code isn't active, you don't have a big need to get into Fremantle
<Wizzup> I think getting an upgraded fremantle with cssu is painful
<Wizzup> tbh
* uvos tried that and failed
<uvos> or gave up anyhow
<sicelo> You don't need cssu to fix lock code though. Anyhow,
<sicelo> Anyone knows if N9 & N950 use cal?
<sicelo> Or it's only N900?
<Pali> lioh: parazyd: you need to generate combined.bin image, not to flash u-boot.bin only
<Pali> use script u-boot-gen-combined to generate combined.bin binary from u-boot.bin and uImage kernel
<Pali> and flash this combined.bin binary
<Pali> look into u-boot/doc/README.nokia file
<Pali> $ sh u-boot-gen-combined u-boot.bin uImage combined.bin
<Pali> and to generate zImage from uImage use:
<Pali> $ mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -n zImage-2.6.28-omap1 -d zImage-2.6.28-omap1 uImage
<Pali> zImage-2.6.28-omap1 kernel take from fremantle kernel
<Pali> zImage packed in fiasco archive packed in deb archive is at: http://repository.maemo.org/pool/maemo5.0/free/k/kernel/kernel_2.6.28-20103103+0m5_armel.deb
<Pali> to unpack deb, use: dpkg -x
<Pali> to unpack fiasco, use: 0xFFFF -M zimage.fiasco -u
<Pali> parazyd: u-boot does not support battery charging
<freemangordon> Pali: do I get it right, that this guy wants me to post an one-liner patch?
<Pali> freemangordon: seems to
<freemangordon> ok :)
<Pali> put it into reply to that email
<freemangordon> sure
<Pali> thx!
<tmlind> uvos: hey cool, looks like on mz609 this works now: sudo fastboot flash utags utags-mz609-32-mmcblk1p6-boots-mmcblk1p18-kexecboot.bin
<freemangordon> Pali: sent
<tmlind> uvos: that is after flashing the allow-mbmloader-flashing-mbm.bin from the "Xoom2 ME.rar" package like you suggested
<uvos> tmlind: yaay :)
<freemangordon> oh, seems I don;t need moderator approval anymore :)
<uvos> tmlind: great now we can avoid to bricking the things
<tmlind> uvos: maybe you forgot to do fastboot reboot bootloader, or your writes were not working
<uvos> my wirtes where not working
<tmlind> uvos: ok
<uvos> i rebooted multiple times after that
<uvos> and its still at the version number from honycomb
<uvos> (fastboot version)
<tmlind> uvos: we can also probably now use some other partition other than cache partition for kexecboot
<uvos> depends on what mbm cares about
<uvos> but now you can expierament without accedentaly bricking the thing
<tmlind> hmm we should try to find the allow-mbmloader-flashing-mbm.bin also for the 10" tablets
<uvos> tmlind: yeah
<uvos> tmlind: btw have a cdt.bin for mz609 or dose it not use that?
<uvos> looks like motoboot.img mentions it
<uvos> looks kinda like motoboot maybe contains a bunch of stuff compressed or soemthing
<tmlind> uvos: did not flash that one, i think that's really only used for boot time checks
<uvos> right but it includes cdt.bin in its header
<uvos> but no cdt.bin
<tmlind> uvos: i believe cdt.bin does not matter for allow-mbmloader-flashing-mbm.bin, it might make a difference after flashing something and rebooting though
<uvos> ok
<tmlind> well that's just my gut feeling based on experiments
<tmlind> so maybe mz615 european model had a different number and we need to search for that firmware?
<uvos> tmlind: maybe
<uvos> its mz616
<tmlind> oh ok
<Wizzup> freemangordon: Pali: looks like tom didn't respond to the point about having to port to dts
<Wizzup> not sure if he got that or not
<Pali> Wizzup: I really do not know... if you think that you can re-phrase freemangordon's email that there is missing response to dts, please do it
<Pali> I'm really lost now :-(
<Wizzup> he wrote an email 7 minutes ago which I think is a bit more clear
<Pali> I see "provide a linkable but not runnable"
<Pali> so just provide fake stubs for those functions which are missing at linker time?
<Pali> so linking step passes?
<Pali> I do not know
crab has quit [Quit: WeeChat 2.3]
diejuse has quit [Quit: Leaving.]
Daanct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Changing host]
<freemangordon> Wizzup: could you please step in as it seems for some reason my explanations about DTS are not clear to Tom.
<Wizzup> ok
<freemangordon> and no, his last mail is not clear to me, in terms that I don;t understand how can I create linkable binary without enabling OF_CONTROL
<freemangordon> well, I can tweak Makefiles here and there, but is it what he wants me to do
belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 244 seconds]
belcher_ is now known as belcher
<Pali> createing empty stubs in rx51 board code for "missing" of functions may produce linkable binary
<Pali> this is probably the easiest way
mardy has quit [Quit: WeeChat 2.8]
diejuse has joined #maemo-leste
<Wizzup> freemangordon: ping
<freemangordon> Wizzup: pong
<Wizzup> freemangordon: just one second, I'd like you to read the email I will send to u-boot ml and confirm
<freemangordon> ok
<freemangordon> in the meanwhile, I was just able to hack uboot to link without OF_CONTROL enabled
<Wizzup> but that is just with stubs, as I mention in my proposed email, right
<freemangordon> not really, I #ifdef-ed some code and linked to the missing lib functions
<freemangordon> lemme try it it will boot
<Wizzup> I see no reason to change my email for it, btw, so I think I'll send it momentarily
<Wizzup> or would you like me to hold off?
<freemangordon> yes, just a sec, I'll read it
<freemangordon> yep, boots, not sure how to check if USB boots
<freemangordon> *USB works
<freemangordon> Wizzup: looks ok, please sent
<freemangordon> I'll do immediate follow-up with what I have so far
<Wizzup> ok
<Wizzup> freemangordon: done
<Wizzup> it's awaiting approval though
<Wizzup> (for the list)
<freemangordon> ok
<freemangordon> you have it (I see the mail)
<Wizzup> you're on cc
<freemangordon> ah, right :)
<freemangordon> Pali: https://pastebin.com/LgizurGs - it compiles with those changes
<freemangordon> any idea what compatible shall I use in the board file?
<freemangordon> for U_BOOT_DRVINFOS() that is
<freemangordon> Pali: also, how to test if USB works?
<freemangordon> oh:
<freemangordon> ttyACM0: USB ACM device
<freemangordon> I guess this means it works?
<Wizzup> freemangordon: try using screen
<Wizzup> freemangordon: like here: https://www.youtube.com/embed/tGGXvguyXWk
<freemangordon> what are the parameters?
<freemangordon> screen -m /dev/ttyACM0 ?
<freemangordon> never used screen, sorry
<Wizzup> screen /dev/ttyACM0 115200
<freemangordon> oh, it needs sudo
<Wizzup> probably, or some unix group membership
<freemangordon> Nokia RX-51 # version
<freemangordon> U-Boot 2021.07-rc4-00026-gc4737cd594-dirty (Jun 16 2021 - 23:46:45 +0300)
<freemangordon> :)
<Wizzup> \o/
<Pali> either screen, minicom or kermit
<freemangordon> screen works
<freemangordon> and usb works it seems
<Pali> every tool should work :-) just choose your favorite
<freemangordon> already did
<Pali> perfect so it works?
<freemangordon> Nokia RX-51 # version
<freemangordon> arm-linux-gnueabi-gcc (Debian 8.3.0-2) 8.3.0
<freemangordon> U-Boot 2021.07-rc4-00026-gc4737cd594-dirty (Jun 16 2021 - 23:46:45 +0300)
<freemangordon> GNU ld (GNU Binutils for Debian) 2.31.1
<Pali> ok, so works!
<freemangordon> yes, it does
<Pali> and is u-boot still showing that deprecation warning during 'make'?
<freemangordon> yes, but this is a matter of changing one script
<freemangordon> in Makefile, CONFIG_OF_CONTROL shall be removed
<freemangordon> the one next to CONFIG_DM_USB
<freemangordon> diff --git a/Makefile b/Makefile
<freemangordon> +++ b/Makefile
<freemangordon> --- a/Makefile
<freemangordon> @@ -1114,8 +1114,7 @@ ifneq ($(CONFIG_DM),y)
<freemangordon> index a73481d18c..e1cf0200b7 100644
<freemangordon> @echo >&2 "See doc/driver-model/migration.rst for more info."
<freemangordon> @echo >&2 "===================================================="
<freemangordon> endif
<freemangordon> - $(call deprecated,CONFIG_DM_USB CONFIG_OF_CONTROL CONFIG_BLK,\
<freemangordon> - USB,v2019.07,$(CONFIG_USB))
<freemangordon> + $(call deprecated,CONFIG_DM_USB CONFIG_BLK,USB,v2019.07,$(CONFIG_USB))
<freemangordon> $(call deprecated,CONFIG_DM_PCI,PCI,v2019.07,$(CONFIG_PCI))
<freemangordon> heh
<freemangordon> my messages were throttled :)
<freemangordon> anyway, have to do some RL work, night, see ya
<Wizzup> gn
<Wizzup> Tom responded btw
inky_ has quit [Remote host closed the connection]
lea_ has joined #maemo-leste
lea_ has quit [Read error: Connection reset by peer]
elastic_dog has quit [Ping timeout: 272 seconds]
elastic_dog has joined #maemo-leste
<uvos> hmm
<uvos> i cant seam to flash the n900
<uvos> so ./0xFFFF -m u-boot-2013.04-2-with-freemantle-kern.bin -f
<uvos> the device is off and i connected it to usb
<uvos> "Found USB device: RX-51/RM-680/RM-696 (0x421:0x106) in Cold flashing mode"
<uvos> and the device starts
<uvos> "Switching to NOLO mode..."
<uvos> "Waiting for USB device..."
<uvos> "Error: Device detection failed"
<uvos> and then 0xFFFF goes back to waiting for device
<uvos> ad infinitum
<uvos> device just ends up sitting at uboot prompt
<Wizzup> uvos: did you compile your own 0xFFFF
<uvos> Wizzup: no i used the one linked in the wiki
<Wizzup> uvos: ok, so it's not libusb 0.1 compat related then
<Wizzup> tried a different cable?
<Wizzup> or maybe running as root?
<uvos> its as root
<uvos> different cable sure
<uvos> sec
<uvos> ah i got it work
<uvos> was low voltage i gues
<uvos> (it worked with external power supply)
<Wizzup> ok
<Wizzup> btw, with the new libicd-network-wpasupplicant I do not get scan failures anymore
<Wizzup> I was seeing them with the previous -devel version
<Wizzup> not sure if it was just me or not, but if anyone can confirm that's nice
<uvos> fremantle hildon-desktop absolutly has the same bug with the app launcher
<Wizzup> heh
* Wizzup zz
uvos has quit [Ping timeout: 268 seconds]
Pali has quit [Ping timeout: 268 seconds]