Post-install Steps For Debian Eabi With Installer, What to do after installing debian the cortez way! Options

[tux]

What needs doing after a successful installation of cortez-debian. I'm talking about the version of debian and the installer provided by cortez in this thread Debian Eabi With Installer.

Please re-read the first post in that thread because it has been updated. Follow the steps carefully to ensure fewer problems during and post-install.

It is worth remembering that the kernel and modules used in this method, 2.6.23 at the moment, have been produced by cortez using the build system and source tree used by the Poky linux developers. I believe this is based on bitbake and the angstrom work. I think it is worth considering that there may be incompatabilities between this system and the angstrom kernel, modules and packages.

I have successfully installed this system. However I did make an error in allowing the partitioner to format the new / partition. This meant that I had to copy the modules for the kernel across to the microdrive by using the method shown on the TitchyLinux site. I mean I had to mount the SD card and use this command: dpkg-deb -x (pathtofileon SDcard)zaurus_specific.deb . while being in the / directory of the microdrive.


Does it matter if I use keymap.map as in ZDevil's Monster thread or the spitz.gz file from the TitchyLinux files in order to set up the keyboard? Would it be automatically set upif I hadn't let the partitioner format /?

What about the gui/X system? Where do I start looking? cortez says get kdrive from PokyLinux and install it. Then install the window maager of your choice.

One definite plus for this install, the hardware clock is sorted out without needing any clever tricks.

The wifi only had the post-install problem of blacklisting the hostap modules. I have to do this post-install with all methods and varieties of debian, because all my wifi cards work with orinoco and fail with hostap loaded.

The dhcp in the installer works well!

It is much easier to work from the console if you install the openssh-server and login from a terminal on your desktop or use putty. It is vital to work this way when trying to get X to work. It is possible to have a Zaurus which loads X, but a non-working variety, and the only way to mend things is from a remote console.

Hope this thread is of use, especially to me , to people who are testing this convenient way of installing an EABI + EABI debian system on their Z.

This post has been edited by tux: Nov 4 2007, 12:47 AM

[tux]

I have re-installed: but BigZ insists on my choosing to let the partition be formatted. hence I have to dpkg-deb -x on the zaurus-specific.deb to get the modules across. I also had to blacklist hostap and hostap_cs.

As usual, once these debian thingies are installed they are rock solid in the wifi department.

Right dlj0 here is my attempt at uploading the keymap file from ZDevil's Monster method tar.

I'm hoping some clever fellow will give me some hints about the X business. I suppose I could try to use the afterinstall tar ball and scripts from ZDevil? But I'd have to watch out for incompatibilitiies with yongun?

Attached File(s)

 keymap.map.txt ( 5.75K ) Number of downloads: 18

 

[dlj0]

I have re-installed: but BigZ insists on my choosing to let the partition be formatted. hence I have to dpkg-deb -x on the zaurus-specific.deb to get the modules across. I also had to blacklist hostap and hostap_cs.

As usual, once these debian thingies are installed they are rock solid in the wifi department.

Right dlj0 here is my attempt at uploading the keymap file from ZDevil's Monster method tar.

I'm hoping some clever fellow will give me some hints about the X business. I suppose I could try to use the afterinstall tar ball and scripts from ZDevil? But I'd have to watch out for incompatibilitiies with yongun?

Thanks. Keys work now. As soon as I can figure out how to configure either of my wifi cards and get on the net, I will get back to you on the X stuff.

I can get the hostap modules blacklisted, as I did with titchy, but unlike titchy, it didn't automatically work after than. I have to configure the wifi settings somehow, and haven't done that before. I also have to worry about my new card, but that is another day.
How did you configure your wifi settings?

[tux]

Replying to dlj0's post above.

That sounds strange! Obviously it must have worked during install as it did for me. It didn't work for me after install even after I did the dpkg-deb -x trick on the zaurus-specific.deb that cortez provides.

I did depmod and rebooted. The wifi got errors at boot-up because of the hostap v Orinoco conflict. So I edited etc/modprobe.d/blacklist and did the usual. Then I booted again and this time the wifi started up OK.

The interfaces file is the one that the install set up. I just had to do the blacklisting.

Well here it is anyway:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp
# wireless-* options are implemented by the wireless-tools package
wireless-mode managed
wireless-essid any (I will replace this with my routers essid)
wireless-key1 I put this in during install

This is not quite as fancy as I usually use. I use this example that ZDevil posted and edit it to match my router's configuration.

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.111 ## Or any static IP address of your Z
netmask 255.255.255.0
network 192.168.0.0 ## Or your router's IP but change the last number to "0"
broadcast 192.168.0.255
gateway 192.168.0.1 ## Or your router's IP
# wireless-* options are implemented by the wireless-tools package
wireless-mode managed
wireless-essid YouKnowYouAreNotThatStupid
wireless-key1 ComeOnYourKnowIt
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.0.1 ## Or your router's IP, plus any other nameservers addresses found on your router's interface if you like

Here is the reply from ifconfig -a :-

eth0 Link encap:Ethernet HWaddr 00:02:6F:34:4D:6B
inet addr:192.168.1.107 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5989 errors:0 dropped:0 overruns:0 frame:0
TX packets:2537 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6924887 (6.6 MiB) TX bytes:326917 (319.2 KiB)
Interrupt:169

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 TX bytes:560 (560.0

Here is the response to iwconfig :-

lo no wireless extensions.

eth0 IEEE 802.11b ESSID:"*****" Nickname:"Prism I"
Mode:Managed Frequency:2.437 GHz Access Point: 00:12:17:BD:4B:29
Bit Rate:11 Mb/s Sensitivity:1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Encryption key:************************** Security mode:open
Power Management:off
Link Quality=82/92 Signal level=5/153 Noise level=130/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:0 Missed beacon:0

Actually the ***** is just me obscuring the router essid and wep key

I suppose I should emphasise that the wifi is eth0 and not the eth2 that appears to have to be used in ZDevil's monster thread and in jpmatrix's threads on this stuff...


The cards I am using are all Zonet CF1100s under their skin. Working fine.

This post has been edited by tux: Nov 6 2007, 12:48 AM

[dlj0]

Replying to dlj0's post above.

That sounds strange! Obviously it must have worked during install as it did for me. It didn't work for me after install even after I did the dpkg-deb -x trick on the zaurus-specific.deb that cortez provides.

Oddly, when I booted it up today with the wifi card in it worked. But when I hotplugged the card in yesterday, it did not work.

I have an odder problem now. I am adding a package, texlive. It is taking a long, long time. I thought I would do something on the side, but cannot log in to another terminal. My password is not accepted. I think this had something to do with the keymap --- basically, what was typed before the keymap change. But I don't know what that was....

Progress occurs. I will try to re-install cortez' zaurus-specific stuff, which I have not yet done since succeeding in getting a system.

[tux]

....

Progress occurs. I will try to re-install cortez' zaurus-specific stuff, which I have not yet done since succeeding in getting a system.

I suppose I ought to try a dpkg -i on that package too. I may have unpacked the contents to the microdrive but it may very well need the configuring from the package manager,

About the problem with logging in: I presume you are sshing in from your desktop? If this install is a big package you might have done better to ssh in first and do the install from the terminal session. The processing of the package might be taking most of the resources of the system and having no time for trivialities like logging in ssh sessions!

Cheers