Hi,
I have recently installed Freespire on a second partition on the hard drive.
When I first installed Windows XP on the first partition last year, I
created the second partition for the purpose of one day installing Linux. It
has been part of a long term plan to become a Linux user, inspired over the
years by articles promoting Linux in the magazine "NZ PC World". It has
taken a long time to reach this point, where I now have a version installed
on the hard drive.
I have been wondering what version to use. I went searching the internet,
hoping to find a suitable 64-bit version of Linux. In the process, I found
Eric Raymond and Rob Landley's article "World Domination 201". I am
fascinated by their analysis and conclusions, as they describe the situation
I find myself in - having a 64-bit AMD Athlon 64 3200+ processor - and
wondering what to do about running a 64-bit operating system. Further to
that, I was impressed by their comment to the effect that the intention
behind Linspire is to enable an OS that is as user friendly as Windows, and
potentially having access to all the types of programmes that my family
currently use in their computing experience. I'm interested to learn about
how a new OS runs, but my family don't. They just want to turn it on and
click on the programme of choice and use it. That includes music players,
photo software, scanner and printer, internet, office and paint software,
etc. Anything more complicated than that leads quickly to frustration. So,
obviously, any new OS that I install and try to make the default OS in our
household must, for the sake of family harmony, be capable of "click and
run", such as the promoters and developers behind Linspire and Freespire
hope to achieve.
As the 64-bit version is not ready yet, I decided to try out the currently
available 32-bit Freespire version. I would buy the 64-bit version of
Linspire when it becomes available as I would want the 64-bit OS, as well as
access to all the programmes and codecs that the family currently take for
granted using Windows.
Further to that, the budget still only allows for a dial-up modem. I
purchased this modem, a D-Link DFM-562I, a couple of years ago, mistakenly
thinking that "controllerless" meant that it would be suitable one day for
using with Linux. I now know that it must also be a Winmodem that I had been
trying to avoid. So, if this moden can function with Linux, I will be
grateful. I hope that in the future my next modem purchase will be a
broad-band modem capable of running under 64-bit Linux. Last week, I was
tempted to go out and buy an external modem that already worked with Linux.
But then I realised that I was missing an opportunity to find out first-hand
how the Linux community works to solve a problem like this, so I decided to
try this approach first.
So that brings me to the point where I am trying to get this modem going
with this installation of Freespire.
Your help to activate the modem running with the Freespire OS will be
gratefully accepted.
Please note that despite intentions to the contrary, I am an almost total
Linux newbie.
With regards,
Lindsay Middleton
Palmerston North, New Zealand
Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List
Server.
Do use the following as the email Subject Line:
SomeName, YourCountry Freespire skipjack-feisty (development
version) ( kernel 2.6.20-16-lowlatency
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
.
Local Linux experts can be found through:
http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686, Freespire skipjack-feisty (development version) (
Linux version 2.6.20-16-lowlatency (root@terranova) (gcc version 4.1.2
(Ubuntu 4.1.2-0ubuntu4)) #2 SMP PREEMPT Wed May 23 01:49:41 UTC 2007
scanModem update of: 2007_Sept_07
There are no blacklisted modem drivers in /etc/modprobe* files
USB modem not detected by lsusb
Several modems are supported by drivers with ALSA, the Advanced Linux Sound
Architecture software.
Copying ALSA diagnostics to Modem/ALSAroot.tgz
ALSAversion = 1.0.13
Modem or candidate host audio card have firmware information and
diagnostics:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:07.0 8086:1040 8086:1000 Communication controller: Intel Corporation
536EP Data Fax Modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 01:07.0 ----
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
For candidate modem in PCI bus: 01:07.0
Class 0780: 8086:1040 Communication controller: Intel Corporation 536EP
Data Fax Modem
Primary PCI_id 8086:1040
Support type needed or chipset: INTEL536EP
In 2006, Intel appears to have ceased updates for Linux.
For the INTEL537 and INTEL536 chipset modems, the most current support is
provided at:
http://phep2.technion.ac.il/linmodems/packages/intel/Philippe.Vouters/
But regular support is not available, see:
http://archives.linmodems.org/24939
:
The outdated official Intel support packages can be accessed through:
http://developer.intel.com/design/modems/support/drivers.htm
Read Intel.txt and Modem/YourSystem.txt for follow through guidance.
Writing Intel.txt
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.1.2
and the compiler used in kernel assembly: 4.1.2
linux-headers-2.6.20-16-lowlatency resources needed for compiling are not
manifestly ready!
If compiling is necessary packages must be installed, providing:
kernel-source-2.6.20-16-lowlatency
For Debian and some related distributions, a package kernel-kbuild-2.6-20
may be needed to support driver compiling
If a driver compilation files with message including some lack of some
FileName.h (stdio.h for example.
Some additional kernel-header files need installation to /usr/include.
For Debian/Ubuntu related distributions, run the following command to
display the needed package list:
$ sudo apt-get -s install linux-kernel-devel
While some of the files may be on the install CD, others may have to be
found through http://packages.ubuntu.com
For Ubuntu Feisty, additional packages required were:
libc6-dev linux-libc-dev
available through http://packages.ubuntu.com/ , if not on the install CD.
Such packages may have different names for other Linux distributions.
Try installing just the libc6-dev, then test the compile again.
Checking pppd properties:
-rwsr-xr-- 1 root dip 269224 2007-04-04 23:41 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
Read Modem/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for the experts
should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to
blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
