Document Actions

Linux on Sony Vaio grt170

I am the happy owner of a brand new Sony Vaio pcg-grt170 laptop.
I will be writing an article here on my over 1 year experience with the gr390 and Linux (and windows, since linux worked BETTER and was easier and had more driver support than every version of Windows except XP Home <gag>).
My gr390 had it's screen destroyed by one of my sons by accident this summer, Sony wanted $950 for a replacement screen (a whole laptop was about the same for that model) and I was in frantic need of a replacement laptop, and I have been very happy with the last two Vaios I've had, happier than any other laptop I've owned (hp, dell, compaq, toshiba (close third), pcnotebook, winbest, ibm (close second)).
Just to be clear, the GRT170 is a portable workstation. It is very large and not for the weak of arms or back. But it's exactly what I need. I have my Jornadas (one I'm trying to put NetBSD on soon) to take care of the ultra-portable side.
This new beauty has a 16.1" screen!
It has the following specs (Since different packages are available for this model):
Model: pcg-grt170 (bottom of laptop says: 8M2L)
CPU: 2.8 Ghz p4 512KB L2 on-die cache
RAM: 512MB DDR SDRAM (And the other 512 is on the way)
HD: 60 GB
Optical: DVD+/-RW and CDRW drive (woohoo burn dvds!)
LCD: 16.1" 1400x1050 SXGA+ TFT
Bus: 533 Mhz
Video: Nvidia GeForce4 FX Go 5600 64MB DDR SGRAM (0x031a)
Modem:??? V.90 winmodem
Ethernet:SiS900
Wifi/wireless 802.11b:AMBit
Memory stick slot:
Battery life is exactly 1 hour 30 minutes unless all power saving features turned on.
PCcard slots.
Audio:Intel 8x0
IEEE Sony iLINK port:
USB: x3 2.0 ports
Ports: VGA out and parallel port.

What I wish it had:
Built-in floppy (have to order usb fd)
Longer battery life
Infrared port (luckily I have an external serial one and a usb to serial adapter so I can synch my casio watch and such).
1 serial port
More USB ports
RCA out
RCA in for analog vid cap since I don't have any ieee based video cameras.

Click "Read More" for all the details on making this work, as well as the gr390 laptop I used for ayear with several versions of linux. It went VERY smoothly out of the box...

Here's some of what I did to get the GRT170 working that I posted on LInuxQuestions.org:
I have two Vaios and have been a Linux user since the 0.9x kernel days.
Started on Slackware.
Used Redhat from 6x to 7.3. Hate RH 8x and 9x
Ok with Debian, though reminiscent of the "early days" in getting everything to work.
I've tried over 20 different distros over the years.
Now trying Suse 8.2 Pro. Slick interface and tools.
My Vaio pcg-gr390 installed redhat 7.3 smoother than any version of windows would. There isn't very good driver support for it under anything except XP home, and I'd rather be hit by a Mac truck than work on crucial client work using that OS. Redhat installed beautifully. The only gotcha was the APM and screen. By adding the sonypi utils, and making sure the kernel (already) had sonpi support, that was resolved in a few minutes.
I just picked up this Vaio PCG-grt170. Been drooling all over the 16.1" screen! :-) But about pulling my hair out trying to get it fully functional under Linux.
Started with Debian, but too much pain, so quit after a few hours.
Next Redhat 7.3. Almost no drivers worked.
Since I had this SuSe CD sitting around paid for, I figured I'd try it.
It installed the easiest, but the following did NOT work with during the install and have to be addressed afterwards:
Detected video for nvidia drivers will blank out and even potentially lock up the system.
Built-in wireless detects butr refuses to load the drivers/module.
Onboard modem not recognized at all.
No DVD playing capability due to the wonderful "patent restrictions" and other bulbous shiittake mushroom legal crap going on these days.
So, I booted into "safe mode" (init 3) command line.
Ran xf86config (text version) and selected VESA Generic and highest res option for screen without going into custom (option 10 I think).
That works well enough at 1280x1024. I found a site where the owner managed to get it to 1400x1050, I have to do that after I'm into X, since I don't have the current frequency ranges for this laptop yet.
I downloaded the nvidia drivers and followed the directions and it supposedly installs without errors. But when I try to run SaX2 as per directions it blanks out the screen and eventually either comes back to command line or hangs the system. Apparently I'm not the only one having this problem and it may require an updated XFree86 compilation newer than what is currently available from teh Suse updates sites which I ran and went through the nvidia steps again to no avail.
Anyone have any luck getting those to work?
I try to patch the orinoco_pci.c with the patch from another site but it keeps failing 1 out of 1 hunks with out any clear reason why, so no wireless still.
Haven't started to tackle the modem or dvd issues yet. DVD is probably just the usual downloads and addons needed. Modem might be resolved by the linmodem addons I used under redhat, don't know for sure yet.
The ethernet works fine, so I'm limping along on that and in VESA mode, sound works out of the box just fine.
This is such a new laptop there isn't much on the web yet.
Anyone had any more luck than I have with this grt170?
Hope that helped give you some useful insight.

THen I followed up with solution for video:
Managed to get the video working at last!
The key was the following entries in XF86Config:
Option "FlatPanel"
Option "CrtcNumber" "1"
In the Nvidia driver section.
Here's what mine looks like:
<snip>
Section "Monitor"
Option "CalcAlgorithm" "CheckDesktopGeometry"
DisplaySize 320 240
HorizSync 28-95
Identifier "Monitor[0]"
ModelName "1400x1050@60HZ"
Option "DPMS"
VendorName "--> LCD"
VertRefresh 40-62
UseModes "Modes[0]"
EndSection

Section "Modes"
Identifier "Modes[0]"
Modeline "1280x1024" 105.64 1280 1296 1552 1736 1024 1024 1034 1070
Modeline "1152x864" 80.14 1152 1168 1384 1568 864 864 872 902
Modeline "1024x768" 63.23 1024 1040 1216 1400 768 768 775 802
Modeline "800x600" 38.69 800 816 928 1072 600 600 605 626
Modeline "640x480" 24.76 640 656 720 864 480 480 484 501
EndSection

Section "Screen"
DefaultDepth 16
SubSection "Display"
Depth 15
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1400x1050"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
Device "Device[0]"
Identifier "Screen[0]"
Monitor "Monitor[0]"
EndSection
Section "Device"
BoardName "0x031a"
BusID "1:0:0"
Driver "nv"
Identifier "Device[0]"
VendorName "NVidia"
Option "FlatPanel"
Option "CrtcNumber" "0"
EndSection
</snip>

This is how I came to this.
Suse 8.2 with updates.
Booted into Linux "Safe" mode, console login.
As root ran xf86config (text version).
Configured VESA driver at 1280x1024x60hz
Saved and booted into X.
Ran SaX2. Configured monitor at LCD1400x1050@60hz
Saved (avoided running test in this mode).
Exited X.
went to /etc/X11
Vi'd XF86Config
Added those above mentioned "options" for the nv driver section.
Saved.
Started X.
Jumped up and down with joy.
:-)
Be careful about not running SaX2 afterwards since it doesn't put in those options on it's own.
Now to tackle:
builtin in WiFI.
DVD playing/burning
Builtin winmodem

Now I want those working. I'll post back and update this article as I make progress.

Here's what working so far on SuSe 8.2 pro with updates as of September 2nd, 2003:
IDE HD: OK
IDE/SD CD Player data cd (mp3):OK
IDE/SD CD Player music cd: NO :-(
IDE/SD DVD Movies, Player: NO (license issues, I'll have to get apps added)
IDE/SD CDR: TBD
IDE/SD CDRW: TBD
IDE/SD DVDR: TBD
IDE/SD DVDRW: TBD
IDE/SD DVDRW+/-:TBD
Video/LCD: YES (with updates and config tweaks)
Video/External: YES (with updates and config tweaks)
Audio Card: OK
Modem Built-in Winmodem: NO
NIC Built-in: YES
Wifi/802.11b builtin: NO
Memory Stick: TBD
Screen Bright control: NO
Sound control buttons: NO
Function keys: NO
ACPI: NO
Battery Monitor (ACPI): NO
Parallel Port: TBD
USB1: TBD
USB2: TBD
USB3: TBD
IEEE iLINK: TBD (they want ridiculous amount for cable)
External USB Floppy drive: TBD (waiting for arrival)

Additional devices I will be trying to get working:
Jornada 720 via USB
USB to Serial Adapter
Jornada 690 via Serial (USB to Serial adapter)
Palm Vx via Serial (USB to Serial Adapter)
GPS 310 Magellan via Serial (USB to Serial Adapter)
Serial IR dongle attached to Serial to USB adapter
Casio PC-Unite Watch via Infrared (USB to Serial to IR Adapters)
Cisco Aironet 350 PC card 802.11b
Orinoco PC card 802.11b
Netgear PC card 802.11b
Dell/Orinoco PC Card 802.11b
Quickcam Pro 3000 USB
Quickcam Home USB
Quickcam Color Parallel (old)
Printer, BJC-70 parallel
Printer, HP1000 USB
Printer, HPLJ4, parallel
Printer, BJC-620, Parallel
Scanner, HP S20, USB
Scanner, 600 II CD
Scanner, 1200LS via SCSI PC Card
Scanner, Paragon ??? via SCSI PC Card
Console access via USB to Serial adapter to Ultra 10 Sparcs
USB Hub, 4 port

Legend:
OK = works with default install
YES = works with extra effort/drivers/software
NO = Not working (yet)
TBD = To be determined, not tested yet
VMWare 3.x
SCSI PC Card adapter
Jaz 2GB drive via SCSI PC Card
Zip 100MB SCSI Drive via SCSI PC Card

This will take a while to get all resolved, and some may not be possible, but I'll keep updating this article as I make progress.
Also, if you have any success with anything I've listed as not working, please email me to tell me how so that I can get it working and tell others that come to this article how to do it. send mail to hawke(at)hawkes-haven.com

UPdate, 2003-09-03.
DVD plays DVD movies now. A LOT of downloads and work.
After i installed everything (links provided shortly), I found I had to manually kill off the ARTSD sound daemon for Ogle to work. It sounds as though, if I get a different ffront end than the default I may be able to configure it to avoid that. But it does work now with liquid smooth video and audio.
Here's the (many) links for al lthe downloads I had to get:
<A href="http://lists.suse.com/archive/suse-multimedia-e/2003-May/0004.html">http://lists.suse.com/archive/suse-multimedia-e/2003-May/0004.html</a>
<a href="http://www.dtek.chalmers.se/groups/dvd/downloads.shtml">http://www.dtek.chalmers.se/groups/dvd/downloads.shtml</a>
<a href="http://packman.links2linux.org/?action=124">http://packman.links2linux.org/?action=124</a>
<a href="http://www.dtek.chalmers.se/groups/dvd/faq.shtml">http://www.dtek.chalmers.se/groups/dvd/faq.shtml</a>
<a href="http://lists.berlios.de/pipermail/ogle-user/2003-February/001269.html">http://lists.berlios.de/pipermail/ogle-user/2003-February/001269.html</a>
<a href="http://lists.berlios.de/pipermail/ogle-user/2003-March/001383.html">http://lists.berlios.de/pipermail/ogle-user/2003-March/001383.html</a>

I have the wifi builtin card detecting and connecting at the wireless level to the AP with encryption, but I can't ping and I'm getting errors.
I used the following patch:
<A href="http://linux.derkeiler.com/Newsgroups/comp.os.linux.portable/2003-07/0238.html">http://linux.derkeiler.com/Newsgroups/comp.os.linux.portable/2003-07/0238.html</a>
I saw a slightly different one somewhere else, so I may track that other down and see what happens. Sooooooo, close.
Well, that's it for tonight, it's 2:20 am. Time to call it a day, at least for a few hours. ;)

On a last hunch, I tried just turning off eth0 (onboard ehternet nic) and voila! Hot and cold running wireless!
Wonder why it was interfering. I'll play with that later.
So that patch DOES work. You just have to patch then compile the module and install it.

NOTES:
Here are links to some others trying to conquer their GRT170 laptops:
<a href="http://www.liquiddatainc.com/grt170.html">http://www.liquiddatainc.com/grt170.html</a>
<a href="http://www.linuxquestions.org/questions/showthread.php?threadid=83304">http://www.linuxquestions.org/questions/showthread.php?threadid=83304</a>
<A href="http://www.well.com/~ralf/linux_on_sony_vaio_grt170.html">http://www.well.com/~ralf/linux_on_sony_vaio_grt170.html</a>
<a href="http://linux.derkeiler.com/Newsgroups/comp.os.linux.x/2003-08/0154.html">http://linux.derkeiler.com/Newsgroups/comp.os.linux.x/2003-08/0154.html</a>

And here's a link to what gave the hint that solved the video issues with X and the nvidia driver: <a href="http://www.xfree86.org/pipermail/forum/2003-March/000896.html">http://www.xfree86.org/pipermail/forum/2003-March/000896.html</a>

Category(s): Nix; Technology

The URL to Trackback this entry is:: http://www.hawkes-haven.com/blahg/linux-on-sony-vaio-grt170/tbping

Linux on Sony Vaio GR390

I have had a Sony Vaio pcg-gr390 since July 2002.
It's been a great, reliable, and rugged laptop.
Alas, I had to replace it with a grt170 (it's awesome though huge) when the screen was destroyed by a my foolishness combined with the actions of a 3 year old boy.
What's most interesting about this model was my experiences with it between versions of Windoze and Linux.
It shipped with <gag> Windows XP Home.
I didn't even bother booting up and setting up XP, I imemdiately wiped it by booting a Redhat 7.3 CD (of course RC Willey would not honor the EULA and give me a refund, same with CompUSA in Tucson, AZ not honoring the EULA either for the grt170, but that's a whole other story).
I was pleasantly surprised when almost everyting worked with just the default install!
The only things in that well loaded laptop that didn't work out of the box was:
ACPI battery and screen brightness features
Winmodem
Music CD playing (data music worked fine).
Everything else worked!!!
The memory stick, USB, Serial, Parallel, video, audio, network, pccard slot and cards, cdrom and burner, hd, even the infrared!
As I ran the Up2Dates these ran even better.
The ACPI, scrool mouse, and screen brightness were resolved with a simple utility added: sonypid.
Linmodem resolved the winmodem, but I never needed it.
Wireless worked once the redhat updates from up2date were in place.
The real irony is that I tried to put w2k server on (for admin and testing reasons) but there was NO driver support for it. And w2k was only marginally better. The same for win9x (For games). Xp Pro almost worked except no scrolling mouse, ACPI, or screen brightness support period (at least with linux there was a solution that could be added. Only XP home was supported. Sheesh. So I spent most of that year using about 98% Linux on it. Yay. It was a wonderful experience. No more crashing, no more inexplicably corrupted or lost files, no viruses (though surely that won't be forever), and many other benefits.
I've used Linux since 1994/5 but it was never this easy on a laptop before. Oh caloo calay, happy day.

Category(s): Nix; Technology

The URL to Trackback this entry is:: http://www.hawkes-haven.com/blahg/linux-on-sony-vaio-gr390/tbping

Linux on Sony Vaio grt170 progress update...modem

So I'm continuing to make progress with Suse 8.2 on this Vaio pcg-grt170.
Now I'm working on the modem (winmodem).
First I went to <a href="http://www.linmodems.org">www.linmodems.org</a> and read a bit and followed links.
Then found the tool they recommended called <a href="http://linmodems.technion.ac.il/packages/scanModem.gz">scanModem</a>.
I downlaoded it, ungzipped it, chmod'd it to execute and voila, lots of information (output in the "read more" section of this article.
It identified it as a SmartLink modem and that they provide excellent Linux support. So I followed the links and went to:
<a href="http://www.smlink.com/main/index1.php?ln=en&main_id=32">here for linux drivers</a> and downloaded the drivers and did a make, make install-amr (see <a href="http://www.smlink.com/main/down/linux_instructions.txt">their instructions</a>).
Did a modprobe slmdm, and voila, detected modem. I can do AT commands and get results, KPPP detects and probes it fine. HOWEVER....
So, using Kppp I setup a dialup account, went to dial and :(
NO DIALTONE.
I verified the line was fine. Did a manual ATDT to the phone number I called (ATDT5554321 fort example) and same result no dialtone. <sigh>
According to the docs this cold be from not having a correct country listing, but I have the following option in modules.conf:
options slmdm country=USA
And did a modprobe slmdm country=USA
ATI7 shows: Country: USA
I will try rebooting. If that fails, I will post to the linmodems mailing list. I will post to this article as soon as I have an update.
See READ MORE linke below for the detailed output from scanModem...
I followed the recommendations of scanModem and tried with version 2.7.10 instead of 2.7.14. But still no luck.
Made sure the ownership and permissions were correct on /dev/ttySL0.
Used minicom and wvdial to try to troubleshoot instead of kppp. Still no joy.
Tried adding the initialization string ATX3 (ignore dialtone) still no luck.
Currently, as of September 9th at 3:15 pm I have the modem module loaded and can perform AT commands successfully, but the modem refuses to pick up the phone line.
I've posted to the discuss@linmodems mailing list and so far no useful suggestions, but I'll keep trying and update this article when there is success. Meanwhile see the detailed output from scanModem and such in the READ MORE link below this article...

cat ModemData.txt

The most recent update of scanmodem accessed at http://linmodems.technion.ac.il/packages/scanModem.gz
should ALWAYS be used before requesting help from discuss@linmodem.org,
URLs to cogent advice are regularly entered and updated, and your problem may be solved therein.
If further help is needed, send a description of your problem to: discuss@linmodems.org
with this ModemData.txt Attached, using the following in the email Subject Line:
 SUBJECT="scanModem, SuSE kernel 2.4.20-4GB

-------------- System information ------------------------
SuSE SuSE Linux 8.2 (i586)
VERSION = 8.2
on system: Linux lnx170 2.4.20-4GB #3 Wed Sep 3 00:26:09 MDT 2003 i686 unknown unknown GNU/Linux"
GCC=3.3
UPDATE=2003 Sept 4

An AC'97 modem codec was not detected

Path to lspci is: /sbin/lspci
--------- lspci scan ----------------
00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0648 (rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 14)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.6 Modem: Silicon Integrated Systems [SiS] Intel 537 [56k Winmodem] (rev a0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 PCI Audio Accelerator (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] SiS7002 USB 2.0
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90)
00:07.0 Network controller: Harris Semiconductor: Unknown device 3872 (rev 01)
00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
00:0a.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 031a (rev a1)
-------------------------------------
Reading more detail for the Device at:
PCI bus
-------
00:02.6 Class 0703: 1039:7013 (rev a0)
 Subsystem 104d:814e
00:02.6 Modem: Silicon Integrated Systems [SiS] Intel 537 [56k Winmodem] (rev a0) (prog-if 00 [Generic])
 Subsystem: Sony Corporation: Unknown device 814e
 Flags: medium devsel, IRQ 10
 I/O ports at 1800 [size=256]
 I/O ports at 1400 [size=128]
 Capabilities: [48] Power Management version 2

-------------------------------------------------------
1039:7013 PCI_ID of the PCI bus with vendor: 1039
104d:814e PCI_ID of Subsystem with vendor: 104d
-------------------------------------------------------
are key Sought Descriptions of your modem firmware.
Have them ready when visiting URLs with service software!!

An AC'97 or MC97 controller cooperates with the modem Subsystem
 1039:7013 SIS 630 + p
Some soft modems under this controller are supported by the
SmartLink slmdm-2.7.10 drivers,
even though an AC'97 modem_codec may not be displayed.

First accessing chipset provider and modem assembler information
for the modem SubSystem under the AC'97 or MC97 Controller.

=== Checking 104d through chipset providers and modem assemblers ====

Vendor 104d is Sony, http://www.sony.com , but without Linux info.
A Sony PCV-RX407 has a SIL39 id, imlpying an Agere Soft modem:
 PCI_ID 1039:7013 ALI 630 Controller,
 SubSys 104d:8129 the soft modem.
 Pending release of Agere support, try the slmdm-2.7.10 driver kit at:
 ftp://ftp.smlink.com/linux/unsupported/ with a report at:
 http://phep2.technion.ac.il/linmodems/archive-third/msg00120.html

Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, the 537 soft modem
and AC'97 and MC97 controllers managing a varierty of non-Intel soft modem subSystems.
These subSystems will in have PCI_IDs assigned by the modem assembler, not Intel.
Download available drivers from: http://developer.intel.com/design/modems/support/drivers.htm
Also check at: http://linmodems.technion.ac.il/resources.html
for early releases and perhaps Already compiled drivers for some Linux distributions

The Intel 537 chipsets are sold to a variety of modem assemblers.
Linux support from Intel is expected by the Fall of 2003.

The soft modem Subsystem: 104d:814e
serving under the controller:
 PCI_ID=1039:7013, Modem: Silicon Integrated Systems [SiS] Intel 537 [56k Winmodem] (rev a0)
may be supported by the SmartLink slmdm-2.7.10 drivers.
For versions after 2.7.10 the drivers may load, but there will be a failure to dial correctly!!
See the related supoort table listing in /tmp/modem/ModemData.txt.2

Vendor 163c is SmartLink, http://www.smlink.com/ with EXCELLENT Linux support!
Downloads from ftp://ftp.smlink.com/linux/unsupported/ with some backups at:
 http://linmodems.technion.ac.il/packages/smartlink/
The slmdm-2.7.10 drivers may support several non-SmartLink chipsets.
Please see the compatibility table within /tmp/modem/ModemData.txt.2

=== Checking 1039 through chipset providers and modem assemblers ====

Vendor 1039 is SiS, Silicon Integrated System.
Some of their modems under AC'97/MC97 Controllers are served by the SmartLink slmdm-2.7.10 drivers,
or preferable the most current version for those "Smart Link HAMR5600 compatible".

Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, the 537 soft modem
and AC'97 and MC97 controllers managing a varierty of non-Intel soft modem subSystems.
These subSystems will in have PCI_IDs assigned by the modem assembler, not Intel.
Download available drivers from: http://developer.intel.com/design/modems/support/drivers.htm
Also check at: http://linmodems.technion.ac.il/resources.html
for early releases and perhaps Already compiled drivers for some Linux distributions

The Intel 537 chipsets are sold to a variety of modem assemblers.
Linux support from Intel is expected by the Fall of 2003.

The soft modem Subsystem: 104d:814e
serving under the controller:
 PCI_ID=1039:7013, Modem: Silicon Integrated Systems [SiS] Intel 537 [56k Winmodem] (rev a0)
may be supported by the SmartLink slmdm-2.7.10 drivers.
For versions after 2.7.10 the drivers may load, but there will be a failure to dial correctly!!
See the related supoort table listing in /tmp/modem/ModemData.txt.2

Vendor 163c is SmartLink, http://www.smlink.com/ with EXCELLENT Linux support!
Downloads from ftp://ftp.smlink.com/linux/unsupported/ with some backups at:
 http://linmodems.technion.ac.il/packages/smartlink/
The slmdm-2.7.10 drivers may support several non-SmartLink chipsets.
Please see the compatibility table within /tmp/modem/ModemData.txt.2

====== PCI_ID checking completed ======

Update=2003 Sept 4
GCCversion=3.3

The following information blocks just query some ppp support items.
====================================================================
 grep ppp /etc/modules.conf
--------------------------------
# ppp over ethernet
# the kernel 2.2 uses pppox
# the kernel 2.4 uses pppoe
alias char-major-144 pppox
post-install pppox insmod mssclampfw
pre-remove pppox rmmod mssclampfw
alias char-major-108 ppp_generic
alias char-major-144 pppoe
alias net-pf-24 pppoe
# the kernel 2.2 uses ppp.o as ppp driver,
# the kernel 2.4 uses ppp_generic.o
alias ppp0 ppp
alias ppp1 ppp
alias tty-ldisc-3 ppp
alias ppp0 ppp_generic
alias ppp1 ppp_generic
alias tty-ldisc-3 ppp_async
alias ppp-compress-18 ppp_mppe
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
--------------------------------
=== ifconfig test ====
eth1 Link encap:Ethernet HWaddr 00:02:8A:94:FE:9A
 inet6 addr: fe80::202:8aff:fe94:fe9a/64 Scope:Link
lo Link encap:Local Loopback

DEVPPP=crw-rw---- 1 root root 108, 0 Mar 14 06:08 /dev/ppp
A /dev/modem symbolic link is not present

No devfsd.conf file sound, indicated absense of the devfsd daemon package
for device file system (devfs) symbolic link support.

DEVFSD=

cat ModemData.txt.2

Do NOT send this common information to discuss@linmodems.org
==============
Several sections are included in this file:
 The rational of scanModem service;
 Summary of modem support under Linux
 Description of the SIL_ID test
 Some output from scanModem specific to your System
 An explanation of the gcc 2.nn compiler warning
 Ethernet interference with DNS (domain name service)
 COMPILING DRIVERS, for Newbies
 Followup actions, to get online.

RATIONAL
This ./scanModem service is sadly necessary because of the precompiled format
(binary, Closed Source) of some modem supporting code. Intellectual property
is protected within the binary component. But this prevents compatibility
assessments/debugging against Linux Open Source code. Skipping many details,
the consequence is that Linux distributions do not deliver Closed Source code,
or tools adequate to fully identify the modem. This script tries to close
this information gap. It will happily be terminated or shortened,
as Linux distributions can host more comprehensive modem diagnostic tools.

USB modems will not be detected UNTIL proper USB support is installed.
See http://www.linux-usb.org/USB-guide/x332.html
 http://www.smlink.com may provide support for
 SmartUSB56 (ST7554) based modems with vendor/product usb ids: 0483:7554

For modems not recognized by ./scanModem, chipset information may be obtained under Microsoft Windows through:
1) Start > Settings > Control Panel > Modem
 Start > Settings > Control Panel > System > Devices > Modem
 Do the modem test is available.
 Try to identify the modem setup file, with name perhaps MODEM.INF
2) Open a COMM console, and send ATI commands to the modem,
 which may elicit chipset and driver information.

Linux SUPPORT SUMMARY - as of 2003 Sept 4
-------------------------------------
Conexant - all modems supported: http://www.linuxant.com
SmartLink - all modems supported: http://www.smlink.com
Intel Inc. - http://developer.intel.com/design/modems/support/drivers.htm
 For early releases check at: http://linmodems.technion.ac.il/resources.html
 the HaM modem is supported, but code is no longer updated and will probably fail under emerging 2.6 kernels
 the 536ep modem is actively supported.
 the 537 AC'97 Link modem subSystem will be supported by Intel soon,
 but the SmartLink slmdm-2.7.10 (and NO later version) drivers are effective for now.
Lucent/Agere
 The Venus chipset modem uses the serial.o driver and is thus supported.
 Modems with digital signal processing (DSP) chipsets are supported: http:/ltmodem.heby.de
 AC'97/MC97 soft modem support is enroute to release,
 but SmartLink slmdm-2.7.10 drivers are effective for now, through only under Some AC'97/MC97 controllers,
 Coding of support for PCI soft modems has not yet begun, and probably will first be available within 2004.
PCTel - http://pctelcompdb.sourceforge.net/
 the pre-compiled binary component is yet to be assembled with the gcc 3.nn used in newer Linux releases,
 so forced (-f) insertions may be necessary:
 insmod -f pctel
 Some of the HSP soft modems are served well by the SmartLink slmdm-2.7.10 drivers.
Broadcom modems in Dell laptops - can be made to function under 2.4 kernels, but code hasn't been updated recently.
ESS - no formal support since 2.2.2 kernels
Motorola - no formal support since 2.4.5 kernels
3Com Winmodems - no support
-------------------------------------------

SUPPORT under 2.6.nn kernels

The proprietary component of winmodem resouces will have to be re-compiled by chipset vendors.
Thus at this time, only the more expensive Controller chip modems,
using the Open Source serial driver, can be expected to function.

-------------------------------------------
COMPILING - Preparing winmodem drivers will generally require compiling.
If you are not familar with this process DEFINITELY read carefully
the section of /tmp/modem/ModemData.txt.2 on "COMPILING DRIVERS, for Linux Newbies"

Silicon chipset (SIL) analysis information
-------------------------------------------
During bootup, kernel diagnostics on the System are stored for later display by:
 dmesg
The scanModem script processes dmesg output to capture AC97 modem information and
parses it into a SIL_id with display of modem manufacturer information.
Guidance to sources of modem supporting software may thus be obtained.

The transfer of the AC97 information to the dmesg buffer requires that modules supporting
both a digital audio card and the ac97_codec had to be loaded during bootup:
 modprobe ac97_codec
 modprobe audio_drivers (such as i810_audio)
This can be checked after bootup with:
 lsmod

This script can also be used by entering a test block with nomenclature:
 ./scanModem SILtest
with SILtest a text file in This Folder
containing a section of a dmesg output or /var/log/messages like:

i810: Intel ICH 82801AA found at IO 0xdc00 and 0xd800, IRQ 11
i810_audio: Audio Controller supports 2 channels.
ac97_codec: AC97 Audio codec, id: 0x4144:0x5340 (Analog Devices AD1881)
i810_audio: AC'97 codec 0 Unable to map surround DAC's (or DAC's not present), total channels = 2
ac97_codec: AC97 Modem codec, id: 0x5349:0x4c22 (Silicon Laboratory Si3036)

which does include a line beginning with: ac97_codec: AC97 Modem codec, id:

---------- End SIL_id section ---------------

==================== AC'97/MC97 summary ==========================
Any of the Controllers in the left most column could support
a variety of subSystem soft modems.
Hence the current ambiguity in possible support by drivers under Linux

VendorID:DeviceID == PCI_ID Controller type
 bus PCI_ID subSystemID AC97 MC97 try drivers from
 ---------- ----------- ---------------- ----------------
 Intel:
 8086:2416 82801AA (ICH) + p c
 8086:2426 82801AB (ICH0) +
 8086:2446 82801BA (ICH2) + p c
 8086:2486 ICH3 + p c
 8086:24c6 INTEL ICH4
 8086:1040 S1724
 8086:7196 ???? +

 1543:3052 1543:3000 SI3052
 1039:7013 SIS 630 + p
 1039:7018 SIS 960 +
 1055:9178 Standard Microsystems +
 1106:3068 VIA + p c
 1022:7446 AMD +
 10b9:5450 ALI 5450
 10b9:5451 ALI 5451
 10b9:5453 ALI p c
 10b9:5457 ALI 5457 + p c
 e159:0001 TigerJet 320
 e159:0001 0359:0003 TJ320 v3.1
 e159:0001 8086:0003 TJ320 v2.0

PCI cards with SmartLink support at least from slmdm-2.7.10
 10b9:5459 ALI 5459 SmartPCI561 ++
 10ec:8197 - SmartLAN56 (RealTek ether/modem combo ++
 1131:3400 - SmartPCI56 (Philips UCB1500) ++
 163c:5459, 10a5:5459 - kinds of SmartPCI561 ++
 4005:0308 - ALS300plus (Avance sound/modem combo ++
--------------------------------------------------------

p http://pctelcompdb.sourceforge.net/
c Conexant - http://www.linuxant.com
+ SmartLink HAMR5600 compatible AMR/CNR/MDC soft modems
++ SmartLink PCI slot modems
 For drivers: ftp://ftp.smlink.com/linux/unsupported/ ,
 EXCEPT for non-SmartLink modems. INSTEAD use version slmdm-2.7.10 also available at
 http://linmodems.technion.ac.il/packages/smartlink/
 Later versions will NOT dialout correctly.
======================================================================

Soft modems under AC'97 or MC97 Controllers
=============================

If a modem_codec SIL_id was not output earlier, please reboot Linux to freshen the
bootup dmesg buffer and then rerun scanModem, to acquire an expected SIL_id.
However

The roughly classified with AC'97 modems may be housed within an
AMR connector, the MDC connector, IBM's CDC connector, or a mini PCI slot.
SmartLink http://www.smlink.com has a readible documentation set on
soft modem rational and technologies. Their common feature is that they
utilize the services of a digital audio card through use of an ac97_codec.
This greatly reduces the cost of the modem and specialization to the
diverse telephone line standards around the world.

Hoever the primary PCI_ID 1039:7013 identifies Only the Controller of the
soft modem Subsystem 104d:814e. This commonly FAILS to designate the chipset!!
Queries under MS windows may be informative, by the following routes:
 Open a COMM console and send ATI commands to the modem,
 which may provide identifying information.
 For a good report see: http://phep2.technion.ac.il/linmodems/archive/msg05099.html
 Get whatever detail information is available through:
 Start > Settings > Control Panel > Modem
 Start > Settings > Control Panel > System > Devices > Modem
 Try to identify the modem setup file, with name perhaps MODEM.INF
 Information therein including driver names may help to identify the chipset.
See complaint to IBM: http://phep2.technion.ac.il/linmodems/archive/msg05076.html

Soft modems serving under AC97 or MC97 Controllers with Lucent/Agere are
is projected for Summer-Fall of 2003. However service by other software may substitute:
 http://phep2.technion.ac.il/linmodems/archive-third/msg00120.html
 with slmdm-2.7.10 available at http://linmodems.technion.ac.il/packages/smartlink/
 Later versions will NOT dial out properly for non-SmartLink modems.

If your modem has an AC'97 or MC97 controller but a an ac97_codec was NOT reported,
there may still be a success with the SmartLink driver.
Get slmdm-2.7.10 driver at http://linmodems.technion.ac.il/packages/smartlink/

The currently available ltmodem drivers
for Digital Signal Processing chipsets are NOT adequate to support ppp under these modems.
They may achieve a dialout, but will fail at ppp initiation.

If the Primary and Subsystem Vendor information was not adeqaute,
it may be useful to download http://www.yourvote.com/pci/vendors.txt
and search it for the Vendor IDs with and without caps, for example: both 114d and 114D

----------------------------------------
Analyzing information for PCMCIA device at PCI Bus 00:0a.0
00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
 Subsystem: Sony Corporation: Unknown device 814e
 Flags: bus master, medium devsel, latency 168, IRQ 5
 Memory at 20000000 (32-bit, non-prefetchable) [size=4K]
 Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
 Memory window 0: 20400000-207ff000 (prefetchable)
 Memory window 1: 20800000-20bff000
 I/O window 0: 00004000-000040ff
 I/O window 1: 00004400-000044ff
 16-bit legacy interface ports at 0001

GREPping for an inserted PCMCIA modem with filter: ommunication
Analyzing information for PCMCIA device at PCI Bus 00:0a.1
00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev aa)
 Subsystem: Sony Corporation: Unknown device 814e
 Flags: bus master, medium devsel, latency 168, IRQ 5
 Memory at 20001000 (32-bit, non-prefetchable) [size=4K]
 Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
 Memory window 0: 20c00000-20fff000 (prefetchable)
 Memory window 1: 21000000-213ff000
 I/O window 0: 00004800-000048ff
 I/O window 1: 00004c00-00004cff
 16-bit legacy interface ports at 0001

GREPping for an inserted PCMCIA modem with filter: ommunication
If a PCMCIA modem is currently inserted and the sockets activated by
 /etc/init.d/pcmcia start
then the PCMCIA bridge is NOT transparent.

If the modem is known to have a Lucent digital signal processing chipset,
then PCMCIA.tar.gz variant assembled by Joern Wustenfeld is necessary,
rather than the standard ltmodem-8.26a9.tar.gz at http://ltmodem.heby.de/

---------------------------------------------------------------------------------------------
The proprietary Binary component of the some current winmodem drivers were compiled with
version 2.9n gcc compiler. Red Hat 8.0 and Mandrake 9.0 releases utilize
version 3.nn gcc compilers. This currently is causing difficulties either
in compiling and/or insertion of updated winmodem drivers.

The gcc compiler version of this System is: 3.3
It will likely be necessary to force (-f) insertion of winmodem drivers, with credit to
Jos Vos: http://phep2.technion.ac.il/linmodems/archive/msg04510.html

For the ltmodem drivers with proprietary binary provided by Agere Systems,
compiling with versions gcc=3.nn is successful.
A minor edit required to compile PCTEL drivers has also been reported:
 http://phep2.technion.ac.il/linmodems/archive/msg04684.html

Simple driver insertion fails in these cases with a message like:
----begin error----
% insmod lt_modem
Using /lib/modules/2.4.18-14/ltmodem/lt_modem.o
/lib/modules/2.4.18-14/ltmodem/lt_modem.o: The module you are trying to
load (/lib/modules/2.4.18-14/ltmodem/lt_modem.o) is compiled with a gcc
version 2 compiler, while the kernel you are running is compiled with
a gcc version 3 compiler. This is known to not work.
-----end error-----

It is necessary as Root to force (-f) loading with commands like:
 insmod -f pctel

respecting the dependency ordering of the drivers.
Then check for insertion with:
 lsmod

If driver insertion is successful, the forcing can be automated
by putting the lines (credit to Bhaskaran Raman) like the following,
 install pctel /sbin/insmod --force pctel

In order of preference depending on your particular Linux installation.
Put these lines into ONLY ONE of the following files,
within any modem loading subsection if present:
 /etc/modutils/ltmodem
 /etc/modutils/aliases
 /etc/modules.conf

Then inform your System of the edit for Debian like Systems with
 update-modules
which rewrites and reads /etc/modules.conf . For other System types
 depmod -a
re-reads the edited /etc/modules.conf .

Thereafter module loading should behave as previously.
For the ltmodem drivers loading,
it should suffice to either start a ppp session or
 modprobe ptserial

-----------------------------------------------------
The System has Ethernet capability. If not expert,
shut down ethernet before initiated modem usage with:
# ifconfig eth0 down

00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90)
 Subsystem: Sony Corporation: Unknown device 814e
 Flags: bus master, medium devsel, latency 173, IRQ 11
 I/O ports at 2000 [size=256]
 Memory at d4004000 (32-bit, non-prefetchable) [size=4K]
 Expansion ROM at <unassigned> [disabled] [size=128K]
 Capabilities: [40] Power Management version 2

================================================================
 COMPILING DRIVERS, for Linux Newbies

This text provides a very minimal introduction to compiling drivers,
particularly WinModem drivers under Linux. Must points are covered in
much more detail in the Linux HOWTO documentation set.

WinModem drivers commonly include:
1) a readible Open Source component, which can be readily debugged by
experts in code. This component provides "wrappers" to common
kernel functions for the binary and a Closed Source component of the modem code.

2) A Closed Source component compiled into BINARY form
in which the original source code is not available
to the public to protect its proprietary information.
The binary format precludes incorporation of the modem
drivers in many Linux distributions (Debian, Mandrake, Red hat, etc.)
for legal reasons, practical reasons, and/or
reasons of principle.

Thus the modem user must commonly COMPILE his own drivers,
and properly install these drivers into their Linux System.
Fully precompiled modem binaries are generally not provided.
The administrative cost is too high, for maintaining drivers for
all the different customized variations to the linux kernel distributions use.
Precompiled binaries are usually only found for
the most common and generic distributions on the market.

Since almost all the newer PCs are now equipped with WinModems, most everyone will have to compile their
own linux modem drivers. Exceptions are the more
expensive modems with Controller chipsets, characteristic of the earliest modems.
They are supported by Open Source serial code included in Linux
distributions (Distros hereafter) . Winmodems are less expensive
because of greatly reduced hardware costs (ie: no DSP and/or no
controller chips). Some of the functions of the older
Controller based chipsets are replaced by a combination of software code and/or other
System hardware. Modems without a controller are referred to as "controllerless
modems" and modems without a DSP and controller are referred to as "soft modems"

With faster central processor units (CPU), some processing tasks are performed
by the CPU for the HCF (host controller free) modems.
For the HSF soft modems serving under AC'97/MC97 controllers,
the digital audio card does some of the signal processing.

COMPILING COMPILING is the process of converting human readable source code
into compact binary code that the Operating System (OS) can process quickly.
For linux softmodems, code components from the modem chipset provider
are combined with KERNEL-HEADERS, thus generating one or
more complementary drivers. They are commonly compiled as Modules and
installed as ModuleNames.o into sub-folders of:
 /lib/modules/kernel-version/
Therefrom they can be dynamically inserted into the boot kernel of the
Operating System (OS) when needed, sometimes with auxiliary instructions from
 /etc/modules.conf
They can be removed from the kernel when no longer serving, thus
economizing on System resources.

The KERNEL-HEADERs have FileNames.h can can be read with a text browser.
Some are installed to
/usr/include/
For systems with RPM package managers, they are provided by a
kernel-headers-SomeVersion.rpm
They specify:
1) code bits to be incorporated by various of your installed programs, and
2) the dependencies within the set of FileNames.h
However the
/usr/include/FileNames.h
Are in general TOO FEW to support compiling. Exceptions to note are
the kernel-header-kernel-version.deb packages of Debian style DISTROs,
which are designed to support compiling.

A KERNEL-SOURCE package must more generally be installed to produce needed kernel headers.
The kernel-source is some 20-30 MB now even in compressed form.
The kernel-source package provided by your Linux Distro SHOULD preferentially be used.
It will usually have some modifications from that initially released at http://www.kernel.org .
Typically the installation process will set a symbolic link:
/usr/src/linux --> PATH_to/kernel-source-version/
Check with:
ls -l /usr/src/linux
Move into it with:
cd /usr/src/linux
Look at the first few lines of the Makefile with:
more Makefile
They will look like:
--------------------
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 21
EXTRAVERSION = -Last.Usage.Extraversion
--------------------
wherein -Last.Usage.Extraversion was that last used by your Linux Distro for
a specialization of the more general kernel-release 2.4.21 .
For Mandrake Linux their will generally be an include an "mdk", such as:
EXTRAVERSION = -3.1mdk
These four makefile lines specify that:
1) the compiled kernel will have a version name like:
vmlinuz-2.4.21-3.1mkd
2) the complementary kernel modules will have an encoded version label: 2.4.21-3.1mkd
3) the modules will be installed by:
make modules-install
to sub-folders of /lib/modules/2.4.21-3.1mkd/

Some kernel-headers from a prior usage may be resident from the Last.Usage of the kernel-source/.
Check with:
ls include/linux/
which may display abundant FileNames.h
The version of these headers will be in the UTS line displayed (for example) by
cat include/linux/version.h
 #define UTS_RELEASE "2.4.21-3.1mdk"
Next, list completely the contents of your current folder /usr/src/linux with:
ls -a
Where the " -a " additionally reveals ".dot-prefixed-confguration-files" such as
 .config .hdepend .depends
which may be left over from the prior usage of the kernel-source.

IMPORTANT: the kernel-source as installed generally WILL NOT
represent your current kernel version as displayed with:
uname -r
even if the kernel-version is the same. For example, in the RedHat Distro kernel-source/
there is a set of kernel-configuration files within
 /usr/src/linux/configs/
Each is specialized for a different CPU (i586, i686, K6, etc),
Yet each will be represented by the VERY SAME version.h and "uname -r" .
!!!! Thus a PROPER CONFIGURATION MUST BE DONE by You, before any usage of kernel-source !!!!

KERNEL-SOURCE configuration is where almost all the Mistakes occur!!!
Here is a way to do it correctly (but read through EXCEPTIONAL CASES below).
1)Within /usr/src/linux
# make mrproper
cleans up leftovers from any previous usage .dot-files and the include/linux/ folder.
Additionally you may need to edit within Makefile, ONLY that 4th line.
If the general source release version is say 2.4.21 and
# uname -r
Displays
 2.4.21-8.1enterprise
2) If necessary to edit, FIRST make a backup:
cp Makefile Makefile.backup
then edit ONLY the 4th line of Makefile to
 EXTRAVERSION = -8.1enterprise
NEVER change anything else within the Makefile.

3) Copy the config file of the current kernel to
# /usr/src/linux/.config
and DO SPECIFY that " . "
But where is it? For many Distros, it will be the file like
 /boot/config-2.4.21-Current.Kernel.Extraversion
Or it may be the target of a symbolic link: /boot/config -->
So
# cp /boot/config-2.4.21-Current.Kernel.Extraversion /usr/src/linux/.config
For SuSE linux it is:
# cp /boot/vmlinuz.config /usr/src/linux/.config

4) Next read .config with
# make oldconfig
which feeds .config through a process specifying
the SAME inter-dependencies previously used in compiling your kernel,
and generating fresh .dot-config files . Check with:
 ls -al

5) Though it may be redundant after "make mrproper", it will do no harm to:
 make clean
5a) If your Linux Distribution is SuSE, there will exist files:
/boot/vmlinuz.autoconf.h -> /usr/src/linux/include/linux/autoconf.h
/boot/vmlinuz.version.h -> /usr/src/linux/include/linux/version.h
They MUST be copied as:
cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h
cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h

6) Now rebuild kernel headers with:
 make dep
7) Check with:
 ls include/linux/
and
 cat include/linux/version.h
to verify the version.

EXCEPTIONAL CASES

For Distros with a Debian style package management system,
a kernel-header-Version.deb package matched with your kernel-version is available.
If may suffice to set a symbolic link:
ln -s /usr/src/kernel-header-Version /usr/src/linux
and then compile the modem drivers. If a custom kernel is to be compiled,
the kernel-package.deb software will GREATLY simplify the task.
Here is a typical command line:
 make-kpkg --revision 2:test.1 --append_to_version -MySpecial --arch_in_name --initrd kernel_headers kernel_image
wherein "--append_to_version -MySpecial" replaces the need for an edit of the Makefile 4th line: EXTRAVERSION =

For the 2.4.nn kernels, a symbolic link is set during initial module installations:
/lib/modules/kernel-version/build --> /usr/src/linux
The driver resources from Intel (and others?) have a Makefile using this build link.
So if your compile fails, check with:
ls -l /lib/modules/kernel-version/build
Then establish the build link if necessary with:
ln -s PATH-To/kernel-source or headers folder/ /lib/modules/kernel-version/build
Do NOT forget the "-s" for symbolic, or you will Duplicate folder contents

As already mentioned above, for the SuSE distribution, there may be files:
version.h autoconfig.h
located in the /boot/ folder. Before beginning a compile,
they should be copied to /usr/src/linux/include/linux/
Someone reported that a critical header file: modversions.h
is written to /usr/src/linux/include/linux ONLY if the
kernel-source package has been installed with the YAST package manager.

COMPILING the MODEM DRIVERS can now finally be done.
Unpack the compiler kit for your modem drivers,
cd into its folder, read any README files,
 make clean
and FINALLY, your modem drivers will compiled by a command like
 make ModuleName
During this process, some of the kernel-header code with be joined
with the supplied modem specific code, and ModemDrivers.o will be produced.
Follow and further instructions in the modem code resource
to install the drives, often with:
 make install

## end COMPILING DRIVERS

===================================================
 FOLLOW UP STEPS.

1) Check for a symbolic link:
 ls -l /dev/modem
which should display something like
 /dev/modem --> /dev/WinModemPort
Some Distros may set a default
 /dev/modem --> /dev/ttyS0 (or 1,2,3)
which are for Controller Chip modems only.
If represent,as Root:
# rm -f /dev/modem
# ln -s /dev/WinModemPort /dev/modem
If may prove necessary to disable a default BOOT UP setup for Controller Chip modems,
to prevent resetting of the unwanted default link.

2) Loading drivers
Depending upon your installation, the modem drivers may/may_not be autoloaded.
Login as Root in a console with:
# su - root
# lsmod
If the modem drivers are not already loaded onto the kernel, insert them with command
# modprobe ModuleDriver

3) Testing drivers.
For a first test of the drivers, it is Very Usefull to have installed the package: wvdial
Do read "man wvdial" and sometime browse the documentation that is written to /usr/share/doc/wvdial/
The first step in setting up wvdial is to run its configuration program as Root.

Below is the output from a System with a Lucent/Agere modem
wvdialconf will either follow a symbolic link /dev/modem --> /dev/ModemPort
or check through ports with name style: /dev/ttyS*
Below ttySLT0 is the modem port name,
replacing /dev/ttyLTO when the Device Files System (devfs) is in use.
%% begun lines below are my added comments.

# wvdialconf /etc/wvdial.conf
Scanning your serial ports for a modem.

ttySLT0<*1>: ATQ0 V1 E1 -- OK
ttySLT0<*1>: ATQ0 V1 E1 Z -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
%% in the AT* tests above Only the lt_modem.o driver is being interrogated
ttySLT0<*1>: Modem Identifier: ATI -- LT V.92 Data+Fax Modem Version 8.26a
%% The ATI test queries the modem firmware, concurrently prompting loading of the lt_serial.o driver
ttySLT0<*1>: Speed 4800: AT -- OK
ttySLT0<*1>: Speed 9600: AT -- OK
ttySLT0<*1>: Speed 19200: AT -- OK
ttySLT0<*1>: Speed 38400: AT -- OK
ttySLT0<*1>: Speed 57600: AT -- OK
ttySLT0<*1>: Speed 115200: AT -- OK
ttySLT0<*1>: Max speed is 115200; that should be safe.
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySLT0.
<Warn>: Can't read config file /etc/wvdial.conf : No such file or directory
Modem configuration written to /etc/wvdial.conf
ttySLT0<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"

%%% This wvdialconf action if successful generates the files:
/etc/ppp/peers/wvdial
/etc/ppp/peers/wvdial-pipe
and for further editing, /etc/wvdial.conf
[Dialer Defaults]
Modem = /dev/ttySLT0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
; Phone = <Target Phone Number>
; Username = <Your Login Name>
; Password = <Your Password>

Note that if your IP is the MicroSoft Network, then use syntax:
Username = MSN/<Your Login Name>
Edit these lines and remove the ";" to activate them.

Many Users prefer to use the dialout utility KPPP. This is fine.
But each User MUST run the configuration process separately.
In principle, different Users on the same Linux System could
have different Internet providers and/or use different modems.

4) Preparation for your first dialout.
Concurrent ethernet capability will compete for
the Domain Name Service (DNS) needed for browser naviagation. So as root:
# /sbin/ifconfig eth0 down
before starting a dialout!
With a Mandrake installation, it will be necessary to:
# /etc/init.d/network stop

5) Internet clients such as Netscape, Mozilla, Explorer etc.
should be CLOSED during your first dial out trials.
Should a URL on the Internet be specifed as the default URL/connect,
then the Client may compete with ppp for connectivity functions.
After PPP functionality has been verified, the effects of opened
or launched browsers can be checked

If you have installed the DIALD (dial on demand) package, stop it for initial tests:
# /etc/init.d/diald stop
Otherwise diald function will be initiated with modem usage,
and could compilate issues. Test diald only after ppp by itself is fine.

If your internet provider assigns DNS dynamically then add to /etc/ppp/options:
usepeerdns

To analyze a dialout attempt, it is useful to display kernel messages with:
# tail -f /var/log/messages &
or to achieve some prefix trimming:
# tail -f /var/log/messages | cut -d: -f4- &
The & puts the commanded process in the "background" allowing recovery of the command prompt.

Some dialer packages (kppp etc) may automate the above steps.

6) A dail out with wvdial will then display like:

# wvdial &
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT3019178111
--> Waiting for carrier.
ATDT3019178111
CONNECT 53333 V42bis
--> Carrier detected. Waiting for prompt.
** APX1.LNH.MD.RCN.NET Terminal Server **
Login:
--> Looks like a login prompt.
--> Sending: marvstod
marvstod
Password:
--> Looks like a password prompt.
--> Sending: (password)
 Entering PPP Session.
 IP address is 66.44.1.6
 MTU is 1006.
--> Looks like a welcome message.
--> Starting pppd at Sat Jul 26 13:59:03 2003
--> pid of pppd: 2404
: pppd 2.4.1 started by root, uid 0
: Using interface ppp0
: Connect: ppp0 <--> /dev/tts/LT0
: kernel does not support PPP filtering
Jul 26 13:59:08 stodolsklap kernel: PPP BSD Compression module registered
Jul 26 13:59:08 stodolsklap kernel: PPP Deflate Compression module registered
: local IP address 66.44.1.6
: remote IP address 208.59.89.132
: primary DNS address 207.172.3.8

7) Note that for some Linux distributions (Mandrake for one),
maintain modules in compressed module.gz format, if modem service was not specified
during the Linux installation. A subsequent installation of any dialer package:
wvdial - PPP dialer with built-in intelligence.
kppp - PPP dialer for KDE
dtmfdial - A DTMF Tone Dialer
gkdial - Gtk-based PPP dial-up configuration tool.
gkdial-gnome - GNOME-based PPP dial-up configuration tool.
masqdialer - daemon for remote control of masqueraded dialup links
will stimulate unpacking of ppp related modules during bootup.

The cogent ppp related modules loaded during such a CONNECT are displayed within the output from:
# lsmod
ppp_deflate 3512 1 (autoclean)
zlib_inflate 18980 0 (autoclean) [ppp_deflate]
zlib_deflate 18648 0 (autoclean) [ppp_deflate]
bsd_comp 4440 0 (autoclean)
ppp_async 7744 1 (autoclean)
ppp_generic 16380 3 (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc 5264 1 (autoclean) [ppp_generic

For ealier 2.4.nn kernels, loading of these modules may be need the following lines within
/etc/module.conf :
### automate ppp modules loading ###
alias /dev/ppp ppp_generic
alias char-major-108 ppp_generic
alias tty-ldisc-3 ppp_async
alias tty-ldisc-14 ppp_synctty
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
### end ppp block ####
For more recent kernels with their modutils,
these lines are no longer needed.

8) For potential causes of a NO DIALTONE failure, read the Post-install.html
at http://linmodems.technion.ac.il/ Not setting the Country Code may be
and additional problem.

COUNTRY CODE Issues
====================
The modem which you purchase locally or abroad may not be preset
with the proper Country Code setting. An incorrect setting can
hinder acquisition of dial tone.
Inclusion of an X3 (dial without wainting) in the modem Init string
of under wvdial, including in /etc/wvdial.conf a line
 Stupid Modem = yes

Dialtone recognition depends on the setting of country
and/or local phone line equipment.

To properly get dialtone for your country phone experiment use
AT+GCI=xx where xx=00..FF hex number
Theoretically there could be 256 different countries but
not all are valid. Tables in manuals are way off date,
you have to write a small script to try all combinations
for yourself if you can't guess by chance.

After country select you can check textual name of the country it represents.
For example:
 at+gci=00
 OK
 ati9
 Japan

If you can't find exact contry, choose the nearest one available.
Nearby countries tend to have similar equipment and compatible dialtones.

These comments from: Emard <emard@softhome.net>
=================

9) After a successful CONNECT, the Domain Name Service (DNS) needed
for Browser navigation can be checked with:
# ping corel.com
PING corel.com (206.47.20.85): 56 data bytes
64 bytes from 206.47.20.85: icmp_seq=0 ttl=52 time=209.1 ms
64 bytes from 206.47.20.85: icmp_seq=1 ttl=52 time=189.9 ms
64 bytes from 206.47.20.85: icmp_seq=2 ttl=52 time=180.0 ms
64 bytes from 206.47.20.85: icmp_seq=3 ttl=52 time=179.9 ms
# Ctrl-C
 aborts ping
--- corel.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 179.9/189.7/209.1 ms

# ping 206.47.20.85
PING 206.47.20.85 (206.47.20.85): 56 data bytes
64 bytes from 206.47.20.85: icmp_seq=0 ttl=52 time=179.8 ms
64 bytes from 206.47.20.85: icmp_seq=1 ttl=52 time=190.0 ms
64 bytes from 206.47.20.85: icmp_seq=2 ttl=52 time=170.0 ms
# Ctrl-C
 aborts ping

Should there be a success with:
# ping 206.47.20.85
BUT a failure with the named address:
ping corel.com
Then DNS has not been acquired.
Note that failure to stop ethernet service
# /sbin/ifconfig eth0 down
before starting a dialout, will commonly block DNS under ppp.

To terminate the wvdial session, bring the action to the foreground (fg):
# fg wvdial
Ctrl-C to terminate:
wvdial
Caught signal #2! Attempting to exit gracefully...
: secondary DNS address 207.172.3.9
: Terminating on signal 15.
: Connection terminated.
: Connect time 7.8 minutes.
--> Disconnecting at Sat Jul 26 14:06:53 2003

10) The Debian distribution provides a utility:
# pppconfig
for setting up a chatscript for ppp initiation.
Most dialers do use chatscripts and will produce similar records.
Below is the record of a dial out initiated by:

# pon
: pppd 2.4.1 started by marv, uid 1000
: abort on (BUSY)
: abort on (NO CARRIER)
: abort on (VOICE)
: abort on (NO DIALTONE)
: abort on (NO DIAL TONE)
: abort on (NO ANSWER)
: abort on (DELAYED)
: send (ATZ^M)
: expect (OK)
: ATZ^M^M
: OK
: -- got it
: send (ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M)
: expect (OK)
: ^M
: ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M^M
: OK
: -- got it
: send (ATDT3019178111^M)
: expect (CONNECT)
: ^M
: ATDT3019178111^M^M
: CONNECT
: -- got it
: send (d)
: Serial connection established.
: Using interface ppp0
: Connect: ppp0 <--> /dev/modem
: kernel does not support PPP filtering
Jul 26 14:08:39 stodolsklap kernel: PPP BSD Compression module registered
Jul 26 14:08:39 stodolsklap kernel: PPP Deflate Compression module registered
: local IP address 66.44.1.195
: remote IP address 208.59.89.132
: primary DNS address 207.172.3.8

11) GENERAL ITEMS

If attemped insertion of a modem driver evokes a complaint like:
 unresolved symbol do_SAK_R9a0bcb74
then the kernel-headers using in compiling the modem drivers
do not match those of your current kernel whose KernelVersion is displayed by:
 uname -r
and whose kernel config file is often located at /boot/config-KernelVersion
The section above "COMPILING DRIVERS, for Newbies" relates how to make corrections.

There are definitely IPs whose login protocols are Linux hostile.
If you cannot achieve a login, try another Internet Provider (IP).
or ask for someone on discuss@linmodems.org to test your IP.

For general upto date advice:
 http://linmodems.technion.ac.il/
 http://linmodems.technion.ac.il/resources.html
for a general PCI_ID database
 http://www.yourvote.com/pci/
 The Vendor listing is http://www.yourvote.com/pci/vendors.txt
 with some Device IDs too.
the original Linux winmodems URL is:
 http://linmodems.org
with a mailing list on Winmodems:
 discuss@linmodems.org
whose archives can be searched at:
 http://linmodems.technion.ac.il/wgindex.html
There is an extensive modem database at:

USB modem information: http://www.linux-usb.org/USB-guide/x332.html
 http://start.at/modem/
If your IP is MSN, the Microsoft Network,
 then for UserName in dialup scripts under Linux, instead use:
 MSN/UserName

---------- end FOLLOW UP STEPS ---------------

Category(s): Nix

The URL to Trackback this entry is:: http://www.hawkes-haven.com/blahg/linux-on-sony-vaio-grt170-progress-update-modem/tbping

Linux on Sony Vaio grt170: Screen and Power mgt

Sony uses a proprietary i/o control interface for it's function keys, scroll wheels, acpi, and screen control.
sonypid handles some of these.
spicctrl is the user space control utility.
sonypid is built into most linux kernels from 2.4.7 on up. You may or may not have to config your kernel to enable it, many (such as Suse 8.2) already have it enabled out of the box, so then all you need is the spicctrl util.
With it I now can control my screen brightness and get readings on the battery/power situation.
<ul>
Here are the links I used (works for most vaios):
<li><a href="http://www.shallowsky.com/vaiotricks.html">Sutpid Vaio Tricks (on Linux)</a></li>
<li><A href="http://spop.free.fr/sonypi/">Sony programmable I/O Control device</a></li>

Category(s): Nix

The URL to Trackback this entry is:: http://www.hawkes-haven.com/blahg/linux-on-sony-vaio-grt170-screen-and-power-mgt/tbping

Linux on Sony Vaio grt170: 2nd Mouse (USB)

I have a nice small (portable) Logitech USB MiniWheel Mouse.
I wanted both the touchpad and it to work simultaneously and to not have to manually switch back and forth when it's not connected.
This is controlled for X under XF86Config. I'm not worried about mouse usage under command line mode (gpm) so I didn't delve into that.
The details are in the READ MORE link at the bottom of this article....

My XF86Config sections that are pertinent:
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Device" "/dev/mouse"
Option "Emulate3Buttons" "on"
Option "Name" "Autodetection"
Option "Protocol" "ps/2"
Option "Vendor" "Sysp"
EndSection

# ADDED BY HAWKE
Section "InputDevice
 Driver "mouse"
 Identifier "Mouse[2]"
 Option "Device" "/dev/input/mice"
 Option "Name" "Autodetection"
 Option "Emulate3Buttons" "off"
 Option "Protocol" "IMPS/2"
 Option "Vendor" "Sysp"
 Option "ZAxisMapping" "4 5"
EndSection

.... ALSO .....

Section "ServerLayout"
Identifier "Layout[all]"
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer" #added by Hawke
 InputDevice "Mouse[2]" "Always Core" #added by Hawke
Option "Clone" "off"
Option "Xinerama" "off"
Screen "Screen[0]"
EndSection

<ul>
Here are links to the sites I used to get this information:
<li><a href="http://www.faqs.org/docs/Linux-mini/XFree86-Second-Mouse.html">Second Mouse in X mini-HOWTO</a></li>
<li><a href="http://www.linuxnetmag.com/en/issue5/m5mouse1.html">Logitech Wheel Mouse under LInux</a></li>
</ul>

Category(s): Nix

The URL to Trackback this entry is:: http://www.hawkes-haven.com/blahg/linux-on-sony-vaio-grt170-2nd-mouse-usb/tbping

Linux on Jornada 720!

Yay! I have Linux running on my Jornada 720!
 
 
 
This is great since it's the best PDA around for flexibility as a mobile administrator's tool.
 
 
 
I used the directions from this link:
 
<a href="http://homepage1.nifty.com/kyou-kyou/jornada/en/howto_install001.html">http://homepage1.nifty.com/kyou-kyou/jornada/en/howto_install001.html</a>
 
I used my Vaio PCG-GRT170 laptop and a Kingston 128MB flash card.
 
I have a 512MB card on the way so that I can add a lot more software.
 
 
 
A couple of gotchas I discovered....

include so far:
 
<li>So, it boots up to X with a background of a photo of the landscape of Mars. But now windows or menu items.</li>
 
<li>By posting to the Jornada Linux mailing list, I was informed to give the following keystrokes to bring up an XTERM window:
 
ALT+SHIFT+X</li>
 
<li>The command line environment seems to have a screwed up keymap, because many keys don't come out right. I think this may be defaulting to German or some other, I'm delving into the corrections</li>
 
<li>So far there is no PM (power Management) this means I can cleanly turn off the device, I have to pull both batteries, but there is a PM kernel in the works.</li>
 
 
 
Luckily this appears to be a living project, so there's hope that it will get better and better. I will be testing the built-in modem, infrared, serial/usb port, sound playback and recod options, and networking and wireless

Category(s): Nix; Technology

The URL to Trackback this entry is:: http://www.hawkes-haven.com/blahg/linux-on-jornada-720/tbping

Gaim 0.71 and SuSE 8.2 ./configure problems with glib 2.x

Since MSN has updated their protocol, I needed to get upgraded from 0.68 to 0.71. But the ./configure stage won't work.
 
I get the following problems:
 
SuSE 8.2 with all the updates full/custom install as of October 16th,2003.
 
2.4.20-4GB #5 i686
 

 
./configure
 

 
checking for GLIB - version >= 2.0.0... no
 
*** Could not run GLIB test program, checking why...
 
*** The test program failed to compile or link. See the file config.log for the
 
*** exact error that occured. This usually means GLIB is incorrectly installed.
 
configure: error:
 
*** GLib 2.0 is required to build Gaim; please make sure you have the GLib
 
*** development headers installed. The latest version of GLib is
 
*** always available at http://www.gtk.org/.
 

 
However glib2 and glib2-devel are installed:
 
#rpm-qa | grep glib
 
glibc-2.3.2-6
 
glib-1.2.10-372
 
glibc-locale-2.3.2-6
 
glib2-devel-2.2.1-18
 
glibc-devel-2.3.2-6
 
glib2-2.2.1-18
 
glibc-html-2.3.2-6
 
glibc-i18ndata-2.3.2-6
 
glibc-info-2.3.2-6
 

 
./configure --disable-glibtest
 
doesn't seem to work, becuase it STILL runs the test and fails.
 
Please help suggest what to do.
 

 
I looked into config.log first thing. Nothing I could see as helpful. Here's the only apparently related part:
 
"|
 
| #include
 
| #include
 
|
 
| int
 
| main ()
 
| {
 
| return ((glib_major_version) || (glib_minor_version) || (glib_micro_version));
 
| ;
 
| return 0;
 
| }
 
configure:13661: error:
 
*** GLib 2.0 is required to build Gaim; please make sure you have the GLib
 
*** development headers installed. The latest version of GLib is
 
*** always available at http://www.gtk.org/.
 
"
 
gaim-0.71.tar.gz
 

 
If you click the "Read More" link at the end of this article you will see the detailed output from config.log.
 
Please send suggestions for resolution to hawke{at]hawkes-haven.com.
 
Thanks,
 
-Hawke

CONSOLE OUTPUT:
 
/mysrc/gaim-0.71 # ./configure --disable-glibtest
 
checking for a BSD-compatible install... /usr/bin/install -c
 
checking whether build environment is sane... yes
 
checking for gawk... gawk
 
checking whether make sets $(MAKE)... yes
 
checking for sed... /usr/bin/sed
 
checking for gcc... gcc
 
checking for C compiler default output... a.out
 
checking whether the C compiler works... yes
 
checking whether we are cross compiling... no
 
checking for suffix of executables...
 
checking for suffix of object files... o
 
checking whether we are using the GNU C compiler... yes
 
checking whether gcc accepts -g... yes
 
checking for gcc option to accept ANSI C... none needed
 
checking for style of include used by make... GNU
 
checking dependency style of gcc... gcc3
 
checking build system type... i686-pc-linux-gnu
 
checking host system type... i686-pc-linux-gnu
 
checking for ld used by GCC... /usr/i486-suse-linux/bin/ld
 
checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld... yes
 
checking for /usr/i486-suse-linux/bin/ld option to reload object files... -r
 
checking for BSD-compatible nm... /usr/bin/nm -B
 
checking for a sed that does not truncate output... /usr/bin/sed
 
checking whether ln -s works... yes
 
checking how to recognise dependent libraries... pass_all
 
checking command to parse /usr/bin/nm -B output... ok
 
checking how to run the C preprocessor... gcc -E
 
checking for egrep... grep -E
 
checking for ANSI C header files... yes
 
checking for sys/types.h... yes
 
checking for sys/stat.h... yes
 
checking for stdlib.h... yes
 
checking for string.h... yes
 
checking for memory.h... yes
 
checking for strings.h... yes
 
checking for inttypes.h... yes
 
checking for stdint.h... yes
 
checking for unistd.h... yes
 
checking dlfcn.h usability... yes
 
checking dlfcn.h presence... yes
 
checking for dlfcn.h... yes
 
checking for ranlib... ranlib
 
checking for strip... strip
 
checking for objdir... .libs
 
checking for gcc option to produce PIC... -fPIC
 
checking if gcc PIC flag -fPIC works... yes
 
checking if gcc static flag -static works... yes
 
checking if gcc supports -c -o file.o... yes
 
checking if gcc supports -c -o file.lo... yes
 
checking if gcc supports -fno-rtti -fno-exceptions... yes
 
checking whether the linker (/usr/i486-suse-linux/bin/ld) supports shared libraries... yes
 
checking how to hardcode library paths into programs... immediate
 
checking whether stripping libraries is possible... yes
 
checking dynamic linker characteristics... GNU/Linux ld.so
 
checking if libtool supports shared libraries... yes
 
checking whether to build shared libraries... yes
 
checking whether to build static libraries... no
 
checking whether -lc should be explicitly linked in... no
 
creating libtool
 
checking for a BSD-compatible install... /usr/bin/install -c
 
checking for msgfmt... /usr/bin/msgfmt
 
checking for gmsgfmt... /usr/bin/msgfmt
 
checking for xgettext... /usr/bin/xgettext
 
checking for msgmerge... /usr/bin/msgmerge
 
checking for ranlib... (cached) ranlib
 
checking for strerror in -lcposix... no
 
checking for an ANSI C-conforming const... yes
 
checking for inline... inline
 
checking for off_t... yes
 
checking for size_t... yes
 
checking for working alloca.h... yes
 
checking for alloca... yes
 
checking for stdlib.h... (cached) yes
 
checking for unistd.h... (cached) yes
 
checking for getpagesize... yes
 
checking for working mmap... yes
 
checking whether we are using the GNU C Library 2.1 or newer... yes
 
checking whether integer division by zero raises SIGFPE... yes
 
checking for inttypes.h... yes
 
checking for stdint.h... yes
 
checking for unsigned long long... yes
 
checking for inttypes.h... yes
 
checking whether the inttypes.h PRIxNN macros are broken... no
 
checking for ld used by GCC... /usr/i486-suse-linux/bin/ld
 
checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld... yes
 
checking for shared library run path origin... ./config.rpath: ./config.rpath: No such file or directory
 
done
 
checking argz.h usability... yes
 
checking argz.h presence... yes
 
checking for argz.h... yes
 
checking limits.h usability... yes
 
checking limits.h presence... yes
 
checking for limits.h... yes
 
checking locale.h usability... yes
 
checking locale.h presence... yes
 
checking for locale.h... yes
 
checking nl_types.h usability... yes
 
checking nl_types.h presence... yes
 
checking for nl_types.h... yes
 
checking malloc.h usability... yes
 
checking malloc.h presence... yes
 
checking for malloc.h... yes
 
checking stddef.h usability... yes
 
checking stddef.h presence... yes
 
checking for stddef.h... yes
 
checking for stdlib.h... (cached) yes
 
checking for string.h... (cached) yes
 
checking for unistd.h... (cached) yes
 
checking sys/param.h usability... yes
 
checking sys/param.h presence... yes
 
checking for sys/param.h... yes
 
checking for feof_unlocked... yes
 
checking for fgets_unlocked... yes
 
checking for getc_unlocked... yes
 
checking for getcwd... yes
 
checking for getegid... yes
 
checking for geteuid... yes
 
checking for getgid... yes
 
checking for getuid... yes
 
checking for mempcpy... yes
 
checking for munmap... yes
 
checking for putenv... yes
 
checking for setenv... yes
 
checking for setlocale... yes
 
checking for stpcpy... yes
 
checking for strcasecmp... yes
 
checking for strdup... yes
 
checking for strtoul... yes
 
checking for tsearch... yes
 
checking for __argz_count... yes
 
checking for __argz_stringify... yes
 
checking for __argz_next... yes
 
checking for iconv... yes
 
checking for iconv declaration...
 
 extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
 
checking for nl_langinfo and CODESET... yes
 
checking for LC_MESSAGES... yes
 
checking for bison... bison
 
checking version of bison... 1.75, ok
 
checking whether NLS is requested... yes
 
checking whether included gettext is requested... no
 
checking for GNU gettext in libc... yes
 
checking for ANSI C header files... (cached) yes
 
checking for sys/wait.h that is POSIX.1 compatible... yes
 
checking fcntl.h usability... yes
 
checking fcntl.h presence... yes
 
checking for fcntl.h... yes
 
checking sys/time.h usability... yes
 
checking sys/time.h presence... yes
 
checking for sys/time.h... yes
 
checking for unistd.h... (cached) yes
 
checking for locale.h... (cached) yes
 
checking signal.h usability... yes
 
checking signal.h presence... yes
 
checking for signal.h... yes
 
checking for an ANSI C-conforming const... (cached) yes
 
checking whether struct tm is in sys/time.h or time.h... time.h
 
checking return type of signal handlers... void
 
checking for strftime... yes
 
checking for strdup... (cached) yes
 
checking for strstr... yes
 
checking for atexit... yes
 
checking for getopt_long... yes
 
checking for inet_aton... yes
 
checking for gethostent in -lnsl... yes
 
checking for socket... yes
 
checking for getaddrinfo... yes
 
checking for socklen_t... yes
 
checking for pkg-config... /usr/local/bin/pkg-config
 
checking for GLIB - version >= 2.0.0... no
 
*** Could not run GLIB test program, checking why...
 
*** The test program failed to compile or link. See the file config.log for the
 
*** exact error that occured. This usually means GLIB is incorrectly installed.
 
configure: error:
 
*** GLib 2.0 is required to build Gaim; please make sure you have the GLib
 
*** development headers installed. The latest version of GLib is
 
*** always available at http://www.gtk.org/.
 

 

 
CONFIG.LOG:
 
This file contains any messages produced by compilers while
 
running configure, to aid debugging if configure makes a mistake.
 

 
It was created by configure, which was
 
generated by GNU Autoconf 2.57. Invocation command line was
 

 
$ ./configure --disable-glibtest
 

 
## --------- ##
 
## Platform. ##
 
## --------- ##
 

 
hostname = lnx170
 
uname -m = i686
 
uname -r = 2.4.20-4GB
 
uname -s = Linux
 
uname -v = #5 Tue Oct 7 15:32:24 MDT 2003
 

 
/usr/bin/uname -p = unknown
 
/bin/uname -X = unknown
 

 
/bin/arch = i686
 
/usr/bin/arch -k = unknown
 
/usr/convex/getsysinfo = unknown
 
hostinfo = unknown
 
/bin/machine = unknown
 
/usr/bin/oslevel = unknown
 
/bin/universe = unknown
 

 
PATH: /sbin
 
PATH: /usr/sbin
 
PATH: /usr/local/sbin
 
PATH: /root/bin
 
PATH: /usr/local/bin
 
PATH: /usr/bin
 
PATH: /usr/X11R6/bin
 
PATH: /bin
 
PATH: /usr/games
 
PATH: /opt/gnome2/bin
 
PATH: /opt/gnome/bin
 
PATH: /opt/kde3/bin
 
PATH: /opt/OpenOffice.org/program
 
PATH: /usr/lib/java/jre/bin
 
PATH: /opt/gnome/bin
 

 

 
## ----------- ##
 
## Core tests. ##
 
## ----------- ##
 

 
configure:1530: checking for a BSD-compatible install
 
configure:1584: result: /usr/bin/install -c
 
configure:1595: checking whether build environment is sane
 
configure:1638: result: yes
 
configure:1671: checking for gawk
 
configure:1687: found /usr/bin/gawk
 
configure:1697: result: gawk
 
configure:1707: checking whether make sets $(MAKE)
 
configure:1727: result: yes
 
configure:1877: checking for sed
 
configure:1895: found /usr/bin/sed
 
configure:1907: result: /usr/bin/sed
 
configure:1961: checking for gcc
 
configure:1977: found /usr/bin/gcc
 
configure:1987: result: gcc
 
configure:2231: checking for C compiler version
 
configure:2234: gcc --version &5
 
gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux)
 
Copyright (C) 2002 Free Software Foundation, Inc.
 
This is free software; see the source for copying conditions. There is NO
 
warranty; not even for MERCHANTABILITY or F

Sections

Personal tools

Document Actions

Nix

Document Actions

Linux on Sony Vaio grt170

Linux on Sony Vaio GR390

Linux on Sony Vaio grt170 progress update...modem

Linux on Sony Vaio grt170: Screen and Power mgt

Linux on Sony Vaio grt170: 2nd Mouse (USB)

Linux on Jornada 720!

Gaim 0.71 and SuSE 8.2 ./configure problems with glib 2.x