I have everything set up as described, I think. I'm getting the following message:

xauth: (argv):1: bad display name localhost:1 in add command

What does this indicate?

I'm able to VNC in and start an ICEWM session, but my phone reboots when I switch back to Android (using the home button). Any tips on what might be causing that?

I have 2GB set up for my debian image (on the fat32 partition). Is that big enough? If I switched over to the ext2 partition as described in the post mentioned above, how much space should I allow for debian?


JF1.5 | apps2sd | 8GB Class 6 SD

sirbobbinhood wrote:

QUOTE:
I don't know if anyone else has tried this but I just installed jesusfreke's cupcake update my phone is rooted and when I try to run the chmod 4577 * command I get unable to chmod bootdeb operation not permitted. I have root access the $ changed to a # and it asked me if I wanted to allow root access. I'm not the most knowledgeable person when it comes to Linux but I do know a little bit.

I am having the same issue, now. I have root and can chmod 777 *, but chmod 4755 * fails for me.

Did anyone find the fix for this?

Other notes: JF 1.5 build. I am trying this after resizing the debian.img to 900MB (just because), but before actually running the installer script. Should the order to avoid this be: Install -> resize, rather than resize -> install -> re-configure -a?

anything new out there? I still want to install debian on my g1 but the chmod 4755 * still doesn't work is there anyway around this that linux champs know about? From what I remember about linux chmod changes what permissions the file has like being able to execute and such, is there anyway to run the chmod command before the folder is loaded on to the phone?

Even knowing better, I've tried chmodding prior to transfer, it doesn't work. The problem is not all of the command, though, as you can chmod to change all permissions except for making the file an executable. For instance chmod 755 works fine.

I am still stuck on this as well, but then again, I haven't had the time to devote to tracking down the problem.

Yeah I know I could probably track it down but my phone just died on me and now I have to wait a week before I get a new one

I've been working on this for a little while, today, and have decided to wipe and go back to JF's 1.42 build as I had before the cupcake upgrade. I'm going to try this all again from the beginning and make sure root works in 1.42 (and Debian installs), then wipe and go to 1.5 and try the install again.

It seems that the newer SU whitelist occasionally breaks root, so I've read. It seems that it wasn't only Debian that was failing for me. Other root commands were denied permissions as well. I'll post back with any news or progress.

UPDATE: No joy! I was able to install Debian under JF 1.42 (US), but after wiping and flashing to JF 1.5 (US or ADP1) there seems to be something that breaks in the new SU Whitelist app (in either version, with or w/o formatting). chmod attempts result in either Operation not permitted or Permission denied.

New question... Would it most likely be a problem with root, the SU app, or busybox? I am torn now, between my love for Cupcake (the ADP1 version was marginally faster and better on battery consumption) and my desire to run Debian. I would love to get this fixed if there is anyone willing to help.