Debian On C3xxx (merged Topics)

[ZDevil]

Along the lines of iceweasel being a good reason to run  debian, has anyone tired NVU/Kompozer?
and, Zdevil, have you tried kde?  3.5 is more useable on a cf in pdaxii13 than it was on the MD--I bet it would be useable in debian run from a CF.

Anyone try an NX client? (is there one for arm?)

sshfs?

I'd be willing to bet that pdaxii13 does video/audio playback way better, and very likely does better game emulation. Pdax, and especially pdaxii13 has a longer history of refinement on the Z--and the iwmmxt/bvd/audio enhancement stuff for the 2.4 kernel hasn't been matched by anything running 2.6 on the Z. 

The advantage of debian is that it is a Z (and apparently already a pretty good one) port of a big, well integrated, developed and maintained distro--arguably much more powerful from a systems stand point---that and some of the software (like the web browser) is newer
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167793\"][{POST_SNAPBACK}][/a][/div]

I have yet to try KDE, but i bet it's gonna be OK in Titchy.
Both sshfs and NX are very interesting possibilities. But I am not such a power user so I hope someone will test them.
I agree that those pdaX packages, especially those using sound and video, run smoother than in Debian (I know because I've packaged dozens of games for Beta3 before). I think overclocking and recompiling with optimization will help a lot here.
Still the completeness of the main system, documentation and the package system are definitely the dream features of a truly mature distro for the Z.
pdaX is very nice, but as I said before, its future is always not very certain to me and there remains a question of sustainability.
Debian/Z will get better and better and won't be more broken. Upgrading does not require building/configuring/tuning the whole thing from the ground up. It is just one simple apt-get command and won't (semi-)brick the Z.

I'm pretty sure the kernel isn't identifying my drive. I'm also pretty sure that it should (other kernels do- this one is a very inconvenient  anomaly), and that with an update or two it will.  Actually I kinda suspect that someone with more of a clue about Z kernels than I have will get curious about improving hardware support in the near future- this is too cool to leave with iffy sound, awkward rotation and a sideways mouse (and mis-Identifying a very common, cost effective card--the current price difference between ZDevel's card and mine is over $100 USD)
 Anyway, since the devopment environment is one of the attractions here, I agree that you should compile something more useful, or quicker, pimwise. Maybe the pimlico stuff would suit?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167796\"][{POST_SNAPBACK}][/a][/div]

Some skilled hands have already started working on the Debian kernel.  So there will be good news in the near future.
PIM stuff run so well already in Debian, and there are far more choices than in pdaX. Latest stuff such as QT4 and GCC4 are already available in the feeds. I may get my hand wet again when I feel comfortable enough with Debian.

[adf]

good news about interest in kernel development.

I don't know that you'd have to such a power user to want sshfs or NX-- being able to mount a remote directory from public wireless securely over sshfs seems like it would be just handy occasionally-- same with using NX; the compression in NX might make it possible to do work on a server/desktop at home over GPRS from about anywhere.  How about this scenario- start a torrent on your home box while on the road someplace, pick up a couple media files from it at the hotel over wifi, securely?

Looking over /var/log/dmesg on pdaxii13, the line that seems to enable my cf card is:
Intel PXA250/210 PCMCIA (CS release 3.1.31)
pxa_pcmcia_init(0)
pxa_pcmcia_init(1)

there doesn't seem to be any need to identify it further in this sytem. in the debian system, cards seem to get identified and named before they are attached--  maybe it is a little too sensitive?

[dlj0]

I tried this and it seems to fix the wifi problem.

1) Just create a separate blacklist file /etc/modprobe.d/blacklist-eth.
2) Then drop the few lines in the quote above into this file.
3) Save and reboot.
4) Now my wifi connection comes back again!
But I am not absolutely sure if it is because of the unpredictable behavior of the kernel module.
Can anyone confirm this?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167778\"][{POST_SNAPBACK}][/a][/div]

There are two sets of modules that can be loaded for wifi cards, the hostap or the orinoco.  If I have this right, older prism cards need the orinoco, and newer ones need the hostap.  Mine, at least, needs the orinoco.

[dlj0]

As to the pimlico suite: dates seems ok, there is a repository if you look on the pimlico site. Contacts seems to want to load some evolution libraries. I decided not to bother for the moment.   

So I'll try the gpe stuff out for now. I was dubious because of the Opie/Angstrom connection. I admit to being prejudiced, but I have found those distros/projects to be a painful waste of time for me.  

Cheers!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167820\"][{POST_SNAPBACK}][/a][/div]

I could not figure out how to properly syncronize files between machines using dates.  The calandar data is buried deep within the .evolution/ tree (why??), and copying the files that have particular data on them sometimes works, and sometimes doesn't.  I want to simply use sftp to update office and home from the Z.  

gpe-calendar pissed me off by changing formats --- no way to migrate existing calendars to the new formats.  Hello?

[Meanie]

I tried this and it seems to fix the wifi problem.

1) Just create a separate blacklist file /etc/modprobe.d/blacklist-eth.
2) Then drop the few lines in the quote above into this file.
3) Save and reboot.
4) Now my wifi connection comes back again!
But I am not absolutely sure if it is because of the unpredictable behavior of the kernel module.
Can anyone confirm this?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167778\"][{POST_SNAPBACK}][/a][/div]

There are two sets of modules that can be loaded for wifi cards, the hostap or the orinoco.  If I have this right, older prism cards need the orinoco, and newer ones need the hostap.  Mine, at least, needs the orinoco.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167843\"][{POST_SNAPBACK}][/a][/div]

This is correct, you only need one or the other depending on which wifi card you have. But the real problem is that there are some cards that have the exact same manfid, but some of those require the hostap module wheras others require the orinoco. The big problem is that both of these cards need to use different modules in order to work but have the exact same manfid and you just cannot preconfigure a correct blacklist to load the appropriate driver/prohibit loading the wrong driver since the manfid for some cards is just plain ridiculous ly conflicting

[Meanie]

I'm pretty sure the kernel isn't identifying my drive. I'm also pretty sure that it should (other kernels do- this one is a very inconvenient  anomaly), and that with an update or two it will.  Actually I kinda suspect that someone with more of a clue about Z kernels than I have will get curious about improving hardware support in the near future- this is too cool to leave with iffy sound, awkward rotation and a sideways mouse (and mis-Identifying a very common, cost effective card--the current price difference between ZDevel's card and mine is over $100 USD)
 Anyway, since the devopment environment is one of the attractions here, I agree that you should compile something more useful, or quicker, pimwise. Maybe the pimlico stuff would suit?

Incidentally, the kdepim will load much more quickly if you are running kde (or maybe some other qt-based desktop?), which benefits hugely from the faster seek rate on a flash card
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167796\"][{POST_SNAPBACK}][/a][/div]

actually, other kernels (prior to 2.6.21) don't identify your drive at all. the kernel only needs to identify your card if it wants to boot off it. it can use and mount it fine otherwise. what you have seen before in pdaxrom is its the kernel  knows nothing about your drive and does not even care because it boots off the nand and it knows about the nand. then your card is just mounted by the pcmcia sybsystem.
the oz 2.6 kernel (which the debian kernel is based on) boots off the microdrive instead of the nand, thus the microdrive's id has been compiled into the kernel so it knows about the microdrive and can boot off it. since you swapped your microdrive, it won't recognise it until the info for your card is also added to the kernel.

[adf]

I'm pretty sure the kernel isn't identifying my drive. I'm also pretty sure that it should (other kernels do- this one is a very inconvenient  anomaly), and that with an update or two it will.  Actually I kinda suspect that someone with more of a clue about Z kernels than I have will get curious about improving hardware support in the near future- this is too cool to leave with iffy sound, awkward rotation and a sideways mouse (and mis-Identifying a very common, cost effective card--the current price difference between ZDevel's card and mine is over $100 USD)
 Anyway, since the devopment environment is one of the attractions here, I agree that you should compile something more useful, or quicker, pimwise. Maybe the pimlico stuff would suit?

Incidentally, the kdepim will load much more quickly if you are running kde (or maybe some other qt-based desktop?), which benefits hugely from the faster seek rate on a flash card
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167796\"][{POST_SNAPBACK}][/a][/div]

actually, other kernels (prior to 2.6.21) don't identify your drive at all. the kernel only needs to identify your card if it wants to boot off it. it can use and mount it fine otherwise. what you have seen before in pdaxrom is its the kernel  knows nothing about your drive and does not even care because it boots off the nand and it knows about the nand. then your card is just mounted by the pcmcia sybsystem.
the oz 2.6 kernel (which the debian kernel is based on) boots off the microdrive instead of the nand, thus the microdrive's id has been compiled into the kernel so it knows about the microdrive and can boot off it. since you swapped your microdrive, it won't recognise it until the info for your card is also added to the kernel.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167846\"][{POST_SNAPBACK}][/a][/div]

then I should probably get the manfid--how would I go about that without pulling it out of the Z?

[Chero]

Hi,
Wanted : X-specialist.
I installed u-boot and pdaXrom r198 after the titchy setup.
I can boot both pdaXrom and debian (debian by pressing "2" while booting).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167816\"][{POST_SNAPBACK}][/a][/div]

Could you show me how to do that, even though I am no X-specialist?  
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167821\"][{POST_SNAPBACK}][/a][/div]

Just install uboot and flash pdaXrom.
Boot into pdaX, copy /lib/modules/2.6.16 to /mnt/ide/lib/modules/2.6.16
Reboot while pressing "2" boots into debian.
Reboot while pressing nothing boots into pdaXrom.

Chero.

[ZDevil]

Great, thanks, Chero.
But I will hold out for X because Debian is no fun at all without X ...

[ZDevil]

Just install uboot and flash pdaXrom.
Boot into pdaX, copy /lib/modules/2.6.16 to /mnt/ide/lib/modules/2.6.16
Reboot while pressing "2" boots into debian.
Reboot while pressing nothing boots into pdaXrom.
Chero.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167853\"][{POST_SNAPBACK}][/a][/div]

Finally I also gave uboot a whirl.
Same problem:

Code: [Select]

xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error
... Besides I also noticed something very strange under /usr/X11R6/bin/X11/X11 and /usr/bin/X11/X11 : everything is linked to itself!  

I remember after installing uboot and pdaXrom r198, when booting into Debian I got a strange fsck error reporting filesystem inconsistencies.
Perhaps the system is messed up...
So I booted into pdaXrom r198 again and copy the kernel modules to a card.
Now doing a NAND backup and installing the whole thing again from the ground up.
Will try to use the pdaXrom kernel in Debian again and see how things go.

[Chero]

Just install uboot and flash pdaXrom.
Boot into pdaX, copy /lib/modules/2.6.16 to /mnt/ide/lib/modules/2.6.16
Reboot while pressing "2" boots into debian.
Reboot while pressing nothing boots into pdaXrom.
Chero.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167853\"][{POST_SNAPBACK}][/a][/div]

Finally I also gave uboot a whirl.
Same problem:

Code: [Select]

xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error
... Besides I also noticed something very strange under /usr/X11R6/bin/X11/X11 and /usr/bin/X11/X11 : everything is linked to itself!  

I remember after installing uboot and pdaXrom r198, when booting into Debian I got a strange fsck error reporting filesystem inconsistencies.
Perhaps the system is messed up...
So I booted into pdaXrom r198 again and copy the kernel modules to a card.
Now doing a NAND backup and installing the whole thing again from the ground up.
Will try to use the pdaXrom kernel in Debian again and see how things go.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167945\"][{POST_SNAPBACK}][/a][/div]

X is started from /opt/kdrive in titchy.

[jpmatrix]

men,

i've just backuped up my working angstrom to install Titchy Linux on my C3000 !

work in progress here :
http://jpmatrix.livejournal.com/9376.html


first good news :  my Asus WL110 CF WIFI card has been recognized out of the box!

[to be continued]

[tux]

 Am I totally off track here?

I have seen howtos for bulding ipks and howtos for building debs. Would it be possible to unpack an ipk and then take the files and build a deb package?

Assuming this could be done and there were the equivalent arm deb library packages would this be a shortcut to getting z apps up and running?  

I know that there are qt libraries out there.

[Meanie]

Am I totally off track here?

I have seen howtos for bulding ipks and howtos for building debs. Would it be possible to unpack an ipk and then take the files and build a deb package?

Assuming this could be done and there were the equivalent arm deb library packages would this be a shortcut to getting z apps up and running?  

I know that there are qt libraries out there.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167979\"][{POST_SNAPBACK}][/a][/div]

deb2ipk does that.

however, the current Debian arm feeds are based on glibc 2.3.x, whereas all SharpROM based distros are glibc 2.2.x including all pdaXrom based distros. This only leaves the OZ/A based distros. In theory, OZ could be mixed with Debian arm and Angstrom with Debian armel

[tux]

Am I totally off track here?

I have seen howtos for bulding ipks and howtos for building debs. Would it be possible to unpack an ipk and then take the files and build a deb package?

Assuming this could be done and there were the equivalent arm deb library packages would this be a shortcut to getting z apps up and running?  

I know that there are qt libraries out there.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167979\"][{POST_SNAPBACK}][/a][/div]

deb2ipk does that.

however, the current Debian arm feeds are based on glibc 2.3.x, whereas all SharpROM based distros are glibc 2.2.x including all pdaXrom based distros. This only leaves the OZ/A based distros. In theory, OZ could be mixed with Debian arm and Angstrom with Debian armel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=167980\"][{POST_SNAPBACK}][/a][/div]

 Thanks Meanie, so I'll have to bite the bullet and get the source code, compile on TitchyLinux and build the deb myself?   Oh well it's never to late too learn!