uClibc cli rootfs

A uClibc rootfs that you can mount and chroot into, and compile cli packages. Mostly useful for creating small static executables. See my previous post:
http://bkhome.org/blog/?viewDetailed=02188

Buildroot has a bug, it left out /usr/lib/crt0.o, crti.o, crtn.o, and libc.so. I have put those in and I did a test compile of udev-151 source, works.

I have re-uploaded the working rootfs here (27.5MB):
http://distro.ibiblio.org/quirky/developer/uclibc-rootfs/rootfs-uclibc-201103.ext2.gz

Instructions:
http://distro.ibiblio.org/quirky/developer/uclibc-rootfs/rootfs-uclibc-readme


Posted on 19 Mar 2011, 17:57 - Category: Quirky - Comments - href="?edit=02189">Edit - Delete

zzz: usb-modeswitch fixed for JimTcl

I reported recently that I am using JimTcl (a tiny Tcl interpreter) to run the usb_modeswitch_dispatcher script in the usb-modeswitch package:

http://bkhome.org/blog/?viewDetailed=01988

It did seem to work, however I have been communicating with Josua Dietze, the author of usb-modeswitch, and he found a few little bugs:

I just checked the latest version (1.1.5) of the tcl wrapper with jimsh. It turned out that the only problems were in fact caused by the code adding the "gsmmodem" symlink. JimTcl seems to have problems with the "\d" shorthand for digits in regular expressions. Also I had to replace a "file link" command with "file readlink".

This is great news, and I have put the modified script into my 'zzz' package.

Josua is very pleased that I have introduced him to JimTcl, as he has been asked by other cut-down distro developers to rewrite the script in something else. He did make a start with Python, but didn't like the extra libraries needed just to do simple things, so he stopped that effort (thank goodness ).

Josua is even thinking that he might include JimTcl in his package, configured to compile with just enough features to run his script.


Posted on 7 Dec 2010, 7:34 - Category: Quirky - Comments - href="?edit=02020">Edit - Delete

Hso modem driver

While developing my 'zzz' 3G modem support, I was puzzled that I do not have the 'hso.ko' module in the 2.6.31.14 kernel that I am using for Wary 098 and Quirky 1.4.

This site http://www.pharscape.org/hso.html states that the hso driver is in kernel 2.6.27 and later.

I looked in my kernel PET packages, and yes, it is in my 2.6.27.47 PET, It is also in the 2.6.30.5 kernel PET. However it is missing from 2.6.31 and later kernel PETs.

Oh, i see why. I have configured 2.6.31 and later with 'rfkill' turned off, which hso requires: in kernel source drivers/net/usb/Kconfig:

config USB_HSO
tristate "Option USB High Speed Mobile Devices"
depends on USB && RFKILL


However, I have found a Hso source package that is a backport from 2.6.33 to 2.6.31 kernel, and it does compile:

http://www.pharscape.org/forum/index.php/topic,827.0.html

It states that it is version 1.2, but the changelog shows that the author Paul has backported lots of things from the 1.14 release.

The big question is though, will it actually work with my kernel that has rfkill disabled? 'depmod' reports no missing symbols, but perhaps the internal code in the module expects some functionality that rfkill provides.

Request to test hso.ko
Anyone reading this who has a 3G modem that uses this driver? Like for example this AT&T Velocity modem with GPS: http://www.pharscape.org/att-velocity-gps-and-linux.html
The main Hso page http://www.pharscape.org/hso.html lists all the devices supported by the hso.ko module.
If so, would you be prepared to help me, test a special build of Quirky with this driver included? Let me know and I will built it an upload it.

Well, I guess that I could just upload the module, and if you have Wary 098 or Quirky 1.4, that use the 2.6.31.14 kernel, you could give it a try. Gunzip it and place it somewhere in /lib/modules/2.6.31.14 -- the official location is /lib/modules/2.6.31.14/kernel/drivers/net/wwan/hso.ko. Then run 'depmod'.
You might have to blacklist the 'option.ko' module -- quickest way to do this is create a file /etc/modprobe.d/option.conf with just one line in it: "blacklist option" (without the quotes).
Reboot, with modem plugged in. No go, try replugging it. After hso.ko has loaded, you should see /dev/ttyHS* ports. Any failure will probably be reported in /var/log/messages.
...it might load ok, but will it actually work without the rfkill subsystem? Let me know!

I have uploaded the module here:
http://distro.ibiblio.org/pub/linux/distributions/quirky/test/hso.ko.gz


Posted on 4 Dec 2010, 16:47 - Category: Quirky - Comments - href="?edit=02012">Edit - Delete

zzz: 3G: request: test /dev/ttyUSB* ports

I have been investigating if PupDial can do a good guess at the correct port to use.

If usb_modeswitch successfully switches the 3G modem from memory mode to modem mode, you may see more than one /dev/ttyUSB[n] entry.

My Optus Huawei E160E modem has four ports:
/dev/ttyUSB0, ttyUSB1, ttyUSB2, ttyUSB3

...and ttyUSB0 is the correct one to use.

Now, I found something very interesting. If I do this in a terminal:

# modem-stats -c "ATZ" /dev/ttyUSB0

OK


...that is, it returns a blank line and an "OK".

ttyUSB1 and ttyUSB2 do not respond.

However:
# modem-stats -c "ATZ" /dev/ttyUSB3


^BOOT:37673864,0,0,0,77

^BOOT:37673864,0,0,0,77

^BOOT:37673864,0,0,0,77

^BOOT:37673864,0,0,0,77

^BOOT:37673864,0,0,0,77

^BOOT:37673864,0,0,0,77

NO CARRIER

OK


...this is great! I can use the "NO CARRIER" response to determine that ttyUSB3 is not the one to use. Also, the non-response of ttyUSB1 and ttyUSB2 to rule them out.

I currently only have the Optus 3G modem to play with, so I have a request to you guys who have a 3G modem:

Feedback request
If it has switched to modem mode, look in /dev to see how many ttyUSB[n] ports you have, then try the above test on each port. Let me know if this method finds the correct port for you!

Please do this test before using PupDial (or any other method) to connect to the Internet.

I am eagerly awaiting feedback! Try this on any Puppy, not just Quirky.


Posted on 4 Dec 2010, 8:17 - Category: Quirky - Comments - href="?edit=02011">Edit - Delete

zzz: pupdial_init_hotpluggable

Very heavy development work continuing...

pupdial_init_hotpluggable
In /usr/sbin, this is a new script called from PupDial, that probes for the external hot-pluggable devices. This replaces what were previously scripts in /etc/init.d.

Easy switching internal<->external
A problem that I have had with my laptop is I sometimes want to use the internal dialup modem, at other times the 3G modem. I have made switching between these simpler. Also now PupDial is no longer confused which one to detect.

3G modems work-in-progress
I have been testing with my Optus E160E 3G modem (which works great, plugged in at bootup or hot-plugged), but tomorrow I will make a quick trip to Perth and pickup my Vodafone Z3571-Z 3G modem -- currently being used by a relative. I have another relative who has a Telstra 3G modem, that she doesn't use (too expensive), and I will borrow that too.


Posted on 3 Dec 2010, 18:48 - Category: Quirky - Comments - href="?edit=02010">Edit - Delete

zzz: modem handling

I am doing further work on my 'zzz' package, totally rethinking everything.

I have modified my /sbin/pup_event_backend_modprobe script so that now the 'option' module loads for my Optus E160E 3G modem, for both cases of plugged in at bootup, and hotplug. The particular problem I tackled was that the 'usb_storage' had made a prior claim on the USB 12d1:140c interface, but the 'option' module uses the same interface.

I have modified /usr/sbin/pupdial so that it ignores /dev/modem (for now). Instead, pupdial deletes it if it exists, so wvdialconf won't use it either.

I have removed the firmware tarballs 'Cdcacm', 'Hso', 'Nozomi', 'usbserial'.
These install scripts into /etc/init.d, however a fundamental problem is that USB devices are hot-pluggable, and it is not sufficient to have these scripts run only at bootup.
I will in future move any required detection of these devices into the 'pupdial' script.

Note, so that Woof can build a Puppy with any kernel PET, that may have these firmware tarballs, I have put code into /etc/rc.d/rc.sysinit (in my zzz pkg) that deletes them. This is a hack, for now.


Posted on 2 Dec 2010, 8:18 - Category: Quirky - Comments - href="?edit=02009">Edit - Delete

Pburn 3.3.0 issues

Pburn hangs
I am using Pburn to copy some audio CDs, in Quirky 1.4. Works great, except when I clicked the "Retrieve CD-text from disc or Internet" button, another window popped up, but then the application hung. In fact, I had to kill X to stop all the processes running.

Cannot make multiple copies
A usage detail. There doesn't seem to be any way to make multiple copies. After making a copy, there is a button that seems to be for that purpose, but it isn't. I only have one drive, so a temp storage is used. After making one copy, that temp storage is deleted, there is no way (or no way that is obvious) to make multiple copies from that same temp storage.

To make a second copy, I had to go through the entire process of copying off the original.

Do-nothing window
Although CD-copying works, there is something puzzling. Why does a little window appear top-left of screen:

...it doesn't seem to do anything.


Posted on 27 Nov 2010, 9:32 - Category: Quirky - Comments - href="?edit=01998">Edit - Delete

Quirky 1.4 released

Yes, this is an official public release! Short announcement:

The main purpose of releasing Quirky 1.4 is to test my experimental simplified module loading and interface configuration boot scripts (codename 'zzz').
This is supposed to improve the detection and setup of sound, analog modems and 3G modems, and maybe more peripherals. Note, this complements the considerable earlier and ongoing development by Richard Erwin.

1.4 differs from 1.3 in that it is built from the Wary5 PET packages, of which the main feature is Xorg 7.3. Also an older kernel is used, 2.6.31.14 and the live-CD includes the complete collection of analog modem drivers as used in Wary, plus SCSI drivers. Thus, 1.4 will behave almost the same as Wary except for the 'zzz' component.

There are some new features in Woof that are debuting here for testing. In particular, a "heavy duty" file downloader backend for the Puppy Package Manager and Video Upgrade Wizard (for now), which should fix any problems with downloading packages.

Something new in Wary that has not yet been officially released, so is also being debuted in 1.4, is support for developing BaCon BASIC programs.

Another thing inherited from Wary is the excellent multimedia support. For details on the applications in the as-yet-unreleased Wary, read my blog


Full announcement and release notes:
http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-1.4/release-Quirky-140.htm

Live-CD ISO file (123.7MB):
http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-1.4/qrky-140.iso
md5sum: 87ed57f47fd3f782f9897cc2d3a3bcee

'devx' C/C++/Vala/Genie/BaCon compiling support SFS file (100.2MB):
http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-1.4/qrky_devx_140.sfs
md5sum: 4adce6f0cda46d42309c1dba42871c26

What is Quirky all about? Read my Quirky intro:
http://bkhome.org/quirky/


Posted on 27 Nov 2010, 8:47 - Category: Quirky - Comments - href="?edit=01997">Edit - Delete

Quirky 1.4 coming soon

Real soon. Just to let you know.

Quirky 1.4 will be based upon the Wary5 PET packages, and in fact will seem identical in every respect to Wary5.

The only difference is the underlying 'zzz' package, which handles module loading and detection of 3G modems. The purpose of this Quirky will be to evaluate (and maybe debug) zzz -- for example:

1. does your sound come up unmuted at first boot?
2. does sound stay unmuted after a reboot?
3. network connection still work after a reboot?
4. analog modem detected and usable?
5. 3G modem detected and usable?

Apart from that it is the same as Wary5, even the same 2.6.31.14 kernel.


Posted on 26 Nov 2010, 15:30 - Category: Quirky - Comments - href="?edit=01995">Edit - Delete

Quirky 1.3 released

This is built from the "forked" Woof that I have been discussing recently, and is an opportunity to evaluate the changes in Puppy files and streamlined searching in the 'init' script.

Note that there have been some application upgrades since 1.2, but not much, as I have been working on Slackpup, Wary and Woof in the interim. I expect that most, maybe all, apps in Wary will work in Quirky.

1.3 is built with the 2.6.33.2 kernel and also has the commercial Nvidia Xorg driver. The .iso file is 111MB -- note, if I had built without the Nvidia driver it would have been 106MB.

Release announcement and release-notes:

http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-1.3/release-Quirky-130.htm

Download the live-CD (111.4MB):
http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-1.3/qrky-130.iso
Md5sum: 8fc6617b307f6e28c38cd0d162cb5dc3

Download the development .sfs (104.8MB):
http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-1.3/devx_130.sfs
Md5sum: 1ec9790e29e9f559206daa1888bf643e

I have not built a "retro" Quirky this time, as I am targeting Wary for that purpose.


Posted on 22 Sep 2010, 16:57 - Category: Quirky - Comments - href="?edit=01822">Edit - Delete

Pages: [1] [2] [3] [4] [5] [6] ...