Messages

1

Zaurus - pdaXrom / Supported Usb Lan Dongle

« on: June 03, 2007, 10:52:43 am »

"Kathrin" covers many versions. Check theoutput of 'uname -r.' That should tell you if you have the right kernel.

I phrased the question ambiguously. I know I have a 2.4.20 kernel. The question is whether it's the right 2.4.20 kernel - whether the symbol that isn't being found by the module is some option that needed to be compiled into the kernel, but wasn't, or whether it's a dependency that could be satisfied by loading another module first. (uname -r just confirms that it's 2.4.20 - doesn't tell which options it was compiled with or Kathrin version it was packaged with.)

2

Zaurus - pdaXrom / Supported Usb Lan Dongle

« on: May 30, 2007, 12:55:07 pm »

Found that it uses the dm9601  chipset and I downloaded the driver

Where can that driver be found? Thanks!

Oh, I guess at http://www.tyrannozaurus.com/feed/beta3/custom/ - was stumbling around in dead links for awhile, but Google is our friend....

But ...

# insmod ./dm9601.o
./dm9601.o: ./dm9601.o: unresolved symbol crc32_le

Does this mean I don't have the right 2.4.20 kernel, or that there's some other module I need to load first? (My install is Kathryn.)

3

Zaurus - pdaXrom / Supported Usb Lan Dongle

« on: April 10, 2007, 03:37:20 pm »

pdaXii13 5.3.4 has rtl8150, dm9601 and pegasus modules so hopefully this will cover most of the common usblan dongles...

Okay, it finally arrived. The large chip inside says "Zt CKN 0635". Does this make it one of the above, or something else? The only possible clue on the box is "Uses 93C46 to store resource configuration, ID parameter, etc."

I'd plug it in and see if it worked with one driver or the other, but I didn't think through that I'd need an adapter for this adapter, since of course it's a standard rather than mini USB plug on it.  

4

Zaurus - pdaXrom / Supported Usb Lan Dongle

« on: April 03, 2007, 09:57:39 am »

http://www.konsigna.sk/default.asp?mtc=0&c...tem&stiid=20440 is working like charm :-)

Thanks. From the picture it's the same one as Geeks.com -  a bit closer to me.

Is the driver you're using the Davicom 9601 one discussed above?

5

Zaurus - pdaXrom / Supported Usb Lan Dongle

« on: April 02, 2007, 11:48:14 am »

Is that link to the exact adapter you have? Does it work "out-of-the-box," or with little work?

I'm also very curious about this. Any posting specifying what works, with the steps involved, will be much appreciated.

6

Zaurus - pdaXrom / Pdaxrom Rc12 For Sl-c7x0/7500/c860/c1000/c3100

« on: December 12, 2005, 01:34:38 pm »

Just curious to know whether there is a newer RC in the official website, coz I saw "1.1.0 RC12 (Released: 2005-11-28)" right on the first page. 
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106024\"][{POST_SNAPBACK}][/a][/div]

You didn't try clicking that, did you?

7

Zaurus - pdaXrom / Debian On Pdaxrom

« on: December 12, 2005, 10:52:27 am »

Did you make the changes as in the first post of this thread ?

Yes.

Obviously, if you are using another window manager, make sure you change the correct files (it's the most obvious things that people are likely to forget).

Nope. I'm using the stock pdaXrom window manager.

I did some additional things :
1) linked ..../debroot/home/root to ..../debroot/root (debians homedir seems to be the last one)

Well, I created /debroot/home/root and copied .Xauthority to both of them - your solution is obviously better.

2) created a script to start debian :
# .Xauthority changes when restarting X so :
cp /home/root/.Xauthority ..../debroot/home/root/.Xauthority
# I want access to file systems outside chroot :
mount -o bind /mnt/ide2 ...../debroot/mnt/ide2
mount -o bind /mnt/card ..../debroot/mnt/card
# I want my wifi to work :
cp /etc/reslov.conf ..../debroot/etc/resolv.conf
# initialize
/etc/rc.d/init.d/zdebian start

The copying of resolv.conf shouldn't be necessary, if /etc/debroot.conf is being used right, since it has

Code: [Select]

DEB_COPY_INTO_CHROOT="etc/resolv.conf"
Wonder what's going wrong there?

I see that the install has also linked S99zdebian in rc.5 to zdebian, although in the context of the initialization sequence it actually throws an error (which I can't get to right now because I'm waiting to see if Synaptic will actually finish a dist-upgrade begun about 8 hours ago). I suppose if the initialization doesn't work in the startup sequence, it might as well be removed from there since in practice we're running it manually anyway.

Start debian commands with Crd :
# Crd command (e.g. Crd aterm)
Works like a charm every time.

Well, as I noted in another thread, if I:

Code: [Select]

chroot /mnt/ide2/debroot
export DEB_DISPLAY=127.0.0.1:0
aterm
then I'm in (an "xhost +localhost" may have been required before chroot'ing too). But Crd doesn't work, and on initially chroot'ing into debroot DEB_DISPLAY isn't set right, despite DEB_DISPLAY=127.0.0.1:0 being added at the end of /etc/debroot.conf.

Since a lot of other people are running into the same

Code: [Select]

aterm: can't open display 127.0.0.1:0
as I do just following the stock instructions, I have to guess that there's some factor those don't cover, perhaps a small difference between different pdaXrom revisions or platforms or little tweaks users have incidentally given their systems.

8

Zaurus - pdaXrom / Debian On Pdaxrom

« on: December 12, 2005, 01:26:01 am »

when you get to the bash prompt inside the chroot do:

export DISPLAY=127.0.0.1:0

Now that's useful. Get's it to where I can at least invoke an aterm (after a manual chroot). Firefox bombs on an "Illegal instruction," but this is progress - and that step isn't in the instructions elsewhere in this thread and another.

9

Zaurus - pdaXrom / Debian On Pdaxrom

« on: December 12, 2005, 01:02:15 am »

Otherwise, try a brutal "xhost +localhost" from the pdaxrom enviroment (this should open the X server to any connection originated from your own machine, which isn't good as an Xauthority file but for testing purposes it should do...).

Still "connot open display" (this on a 3100 with rc12)

10

Zaurus - pdaXrom / Chrooted Debian Made Easy

« on: December 12, 2005, 12:42:12 am »

Then I run out of the X's and on once more, but this time I didn't write "startx" but "xinit".

Well, xinit hilariously brings up X sideways, and then rotate turns it upside down ... didn't test beyond that that way.

11

Zaurus - pdaXrom / Chrooted Debian Made Easy

« on: December 12, 2005, 12:39:08 am »

chroot /mnt/cf/debroot
and I was in Debian.

Yeah, that works for me as a start. Thanks.

12

Zaurus - pdaXrom / Chrooted Debian Made Easy

« on: December 11, 2005, 11:47:26 pm »

STEP 14:
Finally, give your chrooted Debian environment a test drive.  Try

Code: [Select]

Crd aterm
Then you'll see a different terminal window pop up, with a slightly different prompt as "/#".

Nice guide.  Yet ...

When I get to this point on a 3100 running rc12 I get

aterm: bad option "DISPLAY=127.0.0.1:0"

13

Zaurus - pdaXrom / Not Fstab?

« on: December 11, 2005, 09:57:44 pm »

On a 3100 under pdaX it looks like fstab isn't the controlling file. I went and added instructions to mount swap and put another new hard drive position where I wanted it, but neither happened, and /dev/hda2 ended up at /mnt/ide2 again rather than where I'd assigned it. So I guess fstab is vestigial? Where does the initial mounting sequence take its values from?

14

Zaurus - pdaXrom / 3100 Power Switch & X

« on: December 09, 2005, 09:58:02 am »

Don't use hwclock. It doesn't do anything on the SL series.

hwclock does all the normal things on a 3100.

What seems to be a fix (so far, fingers crossed) I've posted at https://www.oesf.org/forums/index.php?showt...30&#entry106570 - towards the end.

15

Zaurus - pdaXrom / Zaurus Ui Freezes If Suspended Too Long

« on: December 09, 2005, 09:53:22 am »

That worked overnight, except on resume it came up confusing EST with GMT - which must be an incompatibility with the resume scripts and having the hwclock in gmt rather than local? Anyway, much better to have it five hours ahead than four days behind. Pretty sure I can correct this back....

Next morning:

It jumped five hours ahead again when being awoken on a new day. Hmm. What's doing that? Something's making a wrong assumption about the localtime setup.

Ah

hwclock --utc
Off/On Off/On, and now it's got it right, with the hwclock set on Greenwich. I'll see if that lasts.

Later:

The real solution:

In /etc/apd/scripts.d/hwclock change line 20 from:

hwclock --httosys

to:

hwclock --utc --hctosys

This is reflecting that I have an /etc/localtime symlinked to the proper time zone file, and have set the hwclock to utc.

With that change it's keeping very good time - maybe a forward drift of about a minute over 24 hours - much better than I've gotten out of a pdaXrom Z before. The resumes are immaculate.

Note this solution is also in conjunction with the xset file in the note just above.