Bingo: Lucent v.92 dualchipset hardw modem now works great!

Discussion regarding the installation and configuration of Linux distributions.

Postby outstream » Mon Sep 29, 2003 9:01 pm

AoA
Mr Faraz Fazil sir

First of all thanks a lot for replying, actually I got kinda confused when I didn’t get any reply earlier cuz u know I had been trying to get some help from international forums and oh well u know ppl there mostly don’t use modems, they got lan cards etc and even if sum of em use modems, they use external ones and well truly, right now I cant afford the external modem, I think its more good to get sum p-1 or early p-2 machine for rs 5000 rather than spending 5000 bucks on external usr modem.

Any ways lets get to the point, I read the post that u suggested me to read and there u said for newbies its good to use rpm method to compiler kernel rather than using source method to do the job. Well I am just a newbie, no much experience on Linux platform so I am confused what do u want me to do? Compile it from rpm or from source?..but I guess the source method is more like a thrill, ok i`ll go for that, but again there are some confusions from ur post that I would like to mention:

As u said in step 12
“12. Donot issue a make install yet ,which makes the new kernel the default
Instead edit /etc/grub.conf or /etc/lilo.conf to add a new tab image with the name like Linux New kernel testing and add a proper reference to the new kernel.YOu may do that easily by copying an existing reference of an old kernel and paste the text in new lines...and in those new lines, add the new reference”

for me, in step12, I have dual boot system so i`ll use grub right? Cuz I remember I selected to boot using grub when I installed Linux initially… ok but at this time when i`ll be editing /etc/grub.conf …how will I add a new tab image? And how will I add the proper refrence to new kernel? I didn’t understand what did u mean by “copying and existing refrence of an old kernel and paste the text in new lines and in those new lines add the new refrence”…would u elaborate it please?

Ok now again in step 12 u said “if u use grub, u may need to create a initrd image.to do that:

mkinitrd 2.4.22 /boot/newkernelinitrd.img”

I use grub so Now again I am confused what does that means? Does that means I don’t have to edit /etc/grub.conf and just write
mkinitrd 2.4.22 /boot/newkernelinitrd.img instead of writing edit /etc/grub.conf

ok now lets move to step 13 and 14

“13.Boot using the new kernel.

14.Once everything is well, you can make the new kernel the default one using the make install command after cd to /usr/src/linux directory”

does that means first I have to reboot and when linux will load again after restarting I have to type make install after cd to /usr/src/linux…?

I know I am being pretty much dumb here, and may be that’s pretty annoying for u, I`ll be really greatful if u ignore my foolish behaviour. I am just new to the stuff and I want to know about it before I start messing up with kernel itself.

Thanks for your precious time
Good Day
Testing?What's that? If it compiles, its good, if it boots up it is perfect.
----------------------------------------------------
Imran
Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Tue Sep 30, 2003 6:54 am

1:

First of all installing/upgrading the kernel from rpms wont work in your case, since those rpms are basically precompiled versions of the kernel...compiled by 3rd party persons...obviously having different specification than you.and that would most probably not have ppp in modules.
Hence you will have to recompile the kernel from the sources.

2:

IN step 12 when i said Instead edit /etc/grub.conf or /etc/lilo.conf to add a .......

that obviously meant that you should edit /etc/grub.conf with a text editor like joe or gedit or emacs etc...copy an existing kernel's section lines and paste them into new empty lines...then replace appropriate references in the new copied lines to point to the new kernel and initrd image.So that you will have two sections...one the old one and a new one...

For instance if you currently have two os'es like windows 98/xp and linux, the grub.conf would contain two sections.One for linux and one for windows.ONce u edit the file and add the new section, it would end up having three total sections.I hope u get my point.

Now lets make it more clearier:

Suppose, you have completed the make bzImage part.
Now it would create a new kernel image under /usr/src/linux/arch/boot/i386/bzImage or /usr/src/linux/arch/i386/bzImage

bzImage is the actual kernel image that we have just created.

By default it is called bzImage....make install renames it to vmlinuz-someversion and copied it to /boot but since your questions revolved around how to add the reference here goes:

Suppose originally the grub.conf looks like:

(note this is just an excerpt from my grub.conf ...not the complete grub.conf.....only edit the parts that look similar to the ones i have mentioned below.Let other parts remain unchanged.

==========================

title Red Hat Linux 9 (2.4.20-8)
root (hd0,6)
kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /boot/initrd-2.4.20-8.img

title Windows Xp
rootnoverify (hd0,0)
chainloader +1

===========================

Then after the kernel recompile make it look something like:

title Red Hat Linux 9 New kernel (2.4.22)
root (hd0,6)
kernel /usr/src/linux/arch/boot/i386/bzImage
initrd /boot/initrd-2.4.22.img

title Red Hat Linux 9 old kernel(2.4.20-8)
root (hd0,6)
kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /boot/initrd-2.4.20-8.img

title Windows Xp
rootnoverify (hd0,0)
chainloader +1

So you notice that you now have three sections and you have three options at boot time:

1.To run linux with old kernel
2.To run linux with new kernel
3.To run windows

So your old kernel remains untouched.

Also note that you need an initrd image called initrd-2.4.22.img in /boot

To do that , once u have completed the make bzImage part , issue this command:

mkinitrd 2.4.22 /boot/initrd-2.4.22.img

( this command has to be issued while still running the old kernel, otherwise you will get a loopback error.For this reason execute this command in terminal immediately after the make bzImage has completed)
this will create a file /boot/initrd-2.4.22

NOte that both the grub.conf needs to be edited and also the mkinitrd needs to be executed.So dont get confused that if u issue mkinitrd then u dont need to edit grub.conf

3:

for the make install part, it becomes optional if you have added both the references manually as i already told u how to do by editing grub.conf.....make install does the same thing that we just did i.e it edits grub.conf and auto adds all the new references and created an initrd image...but it sets the new kernel to default.So if you are a newbie and the new kernel gives problems then you may have a tough time figuring out how to start linux with old kernel.this is why i told u how to preserve both old and new kernels.hence if u add the references correctly then u need not use make install

Also if you cant do the editing in grub.conf then u can issue a make bzlilo after make install...but it may make things only worse for you since you are a newbie and if anything goes wrong during the kernel recompile, you will have to face many problems.

Hence use the manual grub.conf editing method.

Good luck!
Linux for Life!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Tue Sep 30, 2003 10:52 pm

AoA
Mr Faraz.Fazil sir

I did it all, I followed the steps that u have told me and all went fine until the bzImage part.

I got some good success in
Make bzImage

After doing this when I came across the next step, i.e to edit /etc/grub.conf
It looked like some thing like

---------------------------


# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,7)
# kernel /vmlinuz-version ro root=/dev/hdc9
# initrd /initrd-version.img
#boot=/dev/hdc
default=1
timeout=10
splashimage=(hd0,7)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
root (hd0,7)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /initrd-2.4.20-8.img
title DOS
rootnoverify (hd0,0)
chainloader +1
-----------------------------

after editing it, it looked sumthing like

--------------------------

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,7)
# kernel /vmlinuz-version ro root=/dev/hdc9
# initrd /initrd-version.img
#boot=/dev/hdc
default=1
timeout=10
splashimage=(hd0,7)/grub/splash.xpm.gz
title Red Hat Linux 9 New Kernel (2.4.22)
root (hd0,7)
kernel /usr/src/linux-2.4.22/arch/i386/boot/bzImage
initrd /boot/initrd-2.4.22.img
title Red Hat Linux (2.4.20-8)
root (hd0,7)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /initrd-2.4.20-8.img
title DOS
rootnoverify (hd0,0)
chainloader +1

----------------------------------

after editing was completed, i ran the mkinitrd command
by the way sir, with all due respect here i would like to mention that the command that u told it didnt run for mkinitrd, there was just a minor error in it, u told me to run

mkinitrd 2.4.22 /boot/initrd-2.4.22.img

it didnt run, when i ran that it told me that /lib/modules..../boot/initrd-2.4.22.img directory doesnot exist

then i tried

mkinitrd /boot/initrd-2.4.22.img 2.4.22

and it ran successfully

any how after this i rebooted and after rebooting, bingo , it gave me 3 options

red hat kernel (2.4.22)
red hat kernel (2.4.20.8)
dos

now the problem starts again
when i chose it to boot from new kernel that is 2.4.22, it gave me the following error

==============================================
Booting 'Red Hat Linux 9 New Kernel (2.4.22)'
root(hd0,7)
Filesystem type is ext2fs, partition type 0*83
kernel /usr/src/linux-2.4.22/arch/i386/boot/bzImage
Error15: File not found
Press any key to continue...
==============================================


i wasnt sure in root(hd0,7), if its alphabetical letter "o" or if its zero (0), i tried it with both "o" and "0" but it gave me the same error both times.

and also i would like to mention here that u said it`ll be
/usr/src/linux/arch/boot/i386/bzImage
or
/usr/src/linux/arch/i386/bzImage

in my case, however its not that...in my case the path is
/usr/src/linux-2.4.22/arch/i386/boot/bzImage

u note the difference? in my case boot directory is a sub directory of i386 directory and in ur case i386 is a sub directory of boot
directory
is this normal?

and one other thing that i would like u to know is
when i open my root`s home and in address bar i type it like
/usr/src
now in src when i double click linux and go more into arch directory
the path in address bar should be like
/usr/src/linux/arch
but somehow, the operating system itself does it like
/usr/src/linux-2.4.22/arch

do u think its normal?


i`ll be desperately waiting for ur reply
Thanks for ur precious time
Good Day
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Tue Sep 30, 2003 11:07 pm

1.First of all, for that mkinitrd, I ,in a hurry by mistake typed 2.4.22 before the path , although it should have been after the path like

mkinitrd /boot/initrd-2.4.22.img 2.4.22

2.NOw for that linux / linux2.4.22 thingy....let me make it clear.Basically /usr/src/linux is a symbolic link/short cut that points to /usr/src/linux-2.4.22

If you are paraniod like me, you can check it by giving command :

ls -l /usr/src/linux

It would show that /usr/src/linux points to /usr/src/linux-2.4.22

3.NOw for that error file not found, thats strange.If a kernel image bzImage exists in that path, grub should be able to use/load it.Make sure the path u entered to the bzImage is correct.Do a locate bzImage in terminal to find all files with name bzImage and their paths.Note: locate will show old kernel bzImages too.SO make sure u enter the correct path.

If that doesnot work then use the name linux instead of linux-2.4.22 in the kernel line.

so that it reads:

kernel /usr/src/linux/arch/i386/boot/bzImage

or enter the appropriate path.
Also note that there is a space between the kernel and the next word i.e:

kernel(space)/usr/src/linux/arch/i386/boot/bzImage

(replace (space) with empty space by pressing space bar key on the keyboard)


Good luck!
Linux for Life!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Wed Oct 01, 2003 2:55 am

AoA

mr Faraz.Fazil Sir

hope ur doing good

I checked that path again and again and again...and it was OKAY all the times, i didnt know why it was giving me error in that path when i tried to run new kernel. then i again went to /etc/grub.conf and there i noticed something..let me show you the starting of grub.conf...it goes like

---------------------------------------------------------------
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,7)
# kernel /vmlinuz-version ro root=/dev/hdc9
# initrd /initrd-version.img
#boot=/dev/hdc
default=1
timeout=10
splashimage=(hd0,7)/grub/splash.xpm.gz
-------------------------------------------------------------

do u notice what does it says?...we dont have to give there full path like
kernel /usr/src/linux/arch/i386/boot/bzImage
and
initrd /boot/initrd-2.4.22.img


infact it makes some file named as vmlinuz-kernelversion in /boot
we have to give path of that, and also just /initrd-2.4.22.img, by default it knows that /initrd-2.4.22.img has to be in /boot

any how... i went to /boot and there i saw two files by that name

1. vmlinuz-2.4.20-8
2. vmlinuz

now vmlinuz-2.4.20-8 is of kernel 2.4.20-8, as the name suggests, but vmlinuz was supposed to be there by name vmlinuz-2.4.22, but its there with name just vmlinuz.

i thought may be its of new kernel so i went to grub.conf again and i edited it and this time i made it sumthing like

--------------------------------------------------------
title Red Hat Linux 9 New Kernel (2.4.22)
root (hd0,7)
kernel /vmlinuz ro root=LABEL=/
initrd /initrd-2.4.22.img
title Red Hat Linux (2.4.20-8)
root (hd0,7)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /initrd-2.4.20-8.img
title DOS
rootnoverify (hd0,0)
chainloader +1
-----------------------------------------------------

after rebooting, i chose the option to boot from new kernel
and as expected, it started to boot up, while doing all those configuration checks and bla bla bla, whatever it does in starting, it got hung at some point. that was the screen like ummm dos screen so i couldnt copy and paste lines of error from that screen, but i did something else. i took a paper and wrote down all things that i could see on screen at that time, may be u`ll get a good idea of problem when u see it, so here it goes

--------

RAMDISK: Compressed image found at block 0

Freeing initrd memory: 83k freed

VFS: Mounted root(ext2 filesystem).

Red Hat nash version 3.4.42 starting

Mounting /proc filesystem

creating block devices

creating root device

Mounting root filesystem

Mount: error19 mounting ext3

Pivotroot: pivot_root(/sysroot, /sysroot/initrd) failed: 2

umount /initrd/proc failed: 2

Freeing unused kernel memory: 132k freed

kernel panic: No init found. Try passing init = option to kernel

--------------------------------------------

these r the last lines i could see there, and at this point...my caps lock and scroll lock lights started to blink and computer got hanged up...even ctrl+alt+del didnt work when i wanted to restart it, so i had to do it manually by that reset button.

i hope u can suggest some way outta this problem.
thanks for ur precious time
Good Day
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Wed Oct 01, 2003 10:01 am

Hehe u seem to be very confused and u seem not to be reading my
previous replies.

I bet u are making a mistake at some point

As i stated before, vmlinuz-version is just a renamed version of
bzImage ...created by the make install

If the bzImage file does exist in the

/usr/src/linux-2.4.22/arch/i386/boot/ then it is sure that this

is the new kernel image we just created.

As for the /vmlinuz file it may or may not be an old kernel image.
You may experiment and try booting with it.

Ok now do this:
=================
Since u are a newbie and are having trouble doing the config
yourself..therefore now we can let make install do it automatically.

1.Backup your /etc/grub.conf in case anything goes wrong.
Make sure u do a backup!

cp /etc/grub.conf /etc/grubbackup

This will create a backup grubbackup.

2.run linux with the old kernel 2.4.20-8

cd to /usr/src/linux-2.4.22

and do a make install


It will do all the configuration by itself.It will create the vmlinuz-version file and the initrd file itself and will also add the reference in the grub.conf by itself.

Also make install will make the new kernel the default and may
remove the reference to the old kernel.

So just after make install has completed, open grub.conf and check the contents.It will have added the new kernel references by itself.So dont do anything.Just check if the old kernel reference is still there, so that we may be able to run both the old and the new kernel and not only the new kernel.
If the old kernel reference is still there, then good.If the old 2.4.20-8 kernel reference is missing then open that backup text
file(/etc/grubbackup) you created and copy the old 2.4.20-8 reference from there to the grub.conf file.Save it and reboot

Now try the new kernel.
It may well be that the new kernel may give a message like VFS: panic couldnt mount root partition.

If u encounter such a message, then do this:

reboot the system , on the grub screen, highlight the new kernel
line.Press e to edit. Highlight the kernel line and press e to edit, remove the ro root=something part in the end of the kernel line so that it just contains something like kernel pathtovmlinuz and nothing at the end of it
But donot remove any lines before or after that kernel line.

I have recompiled my kernel a million times with this source method and it works.SO if u follow my instructions carefully and correctly, you will indeed get your kernel to work.

Next time also post a screenshot.

Also during the make xconfig part, did u select your options by
yourself or did u use the defaults, and did u set ppp stuff to modules or not?

If things still dont work, contact me on msn.

Also note that when a person makes such lenghty posts with such lengthy answers, some typo errors may occur.
Linux for Life!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Wed Oct 01, 2003 10:23 pm

AoA

mr Faraz.Fazil sir

man...u are ma man...u made it done...yeah yeah yeah...it booted from my new kernel...well actually when i tried to edit the kernel 2.4.22 and changes the path there, i.e removed ro root and label thingy...it didnt save it..it just booted at the time and next time again it gave same error...so i booted from old kernel and edited grub.conf manually again and removed those entries of ro root...n then it worked.

but man...aaap meray sey kasam ley lo...maein kasam khanay ko tayar hoon ke wo pehlay wala path bhii sehi thiii...bzImage did exist in /usr/src/.../boot/bzImage.............it was all righttttttttt....but i dont know why didnt it work...that was strange...but any how at last we made it work...but i guess its not the end yet...cuz i am getting some errors when its booting...errors like on boot screen...the time when it does those TESTS...it FAILS some of them....any how i have added u to my msn by ex_pilot@hotmail.com...as u allowed me to contact u on msn if any new problem comes. so i hope to see u there and then i`ll discuss those errors with u and also the future policy..like do i have to install modem drivers again in this kernel?...and yeah i dont remember if i configured ppp manually...but yeah i didnt go for default configuration...cuz in default configuration..mounting of vfat was disabled...i said "y" to it

any how thanks for all ur help

Good day
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Thu Oct 02, 2003 5:58 am

Ok good to hear that u can atleast boot from the new kernel.
Try to catch me on msn and let me know of the error details.

I hope that u did set ppp support to module (m) during the xconfig part.
Linux for Life!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Thu Oct 02, 2003 3:17 pm

AoA
mr Faraz.Fazil sir

I hope ur doing good

I wanna tell u sumthing and may be after knowing that u`ll think that i am such a big pagal and crackhead...
actually i thought it was such a mess....first i installed modem drivers in old kernel...then i recompiled new kernel..edited grub.conf..bla bla bla...i thought its being such a mess now...so i thought may be i should re install linux and then compile kernel 2.4.22 again...i thought that way i`ll learn things more good...u know practice makes a man perfect...so i formatted every thing and i have re installed linux, i.e red hat 9 again...i think earlier when i compiler kernel 2.4.22, i did some mistakes in configuring it after make xconfig command ...

now before compiling kernel 2.4.22 i want to know how to configure it after giving make xconfig command..i mean what do u recommend? shall i go for defaults there or shall i change some thing manually in that configuration? and if i have to change any thing in configuration manually, would u please guide me step wise what to change? last time i remember that in configuration, by default, that was set to "n" in mounting vfat..so i set it to "y"...and also how to configure ppp in xconfig graphical configuration?

i read the kernel-howto at www.tldp.org but i didnt understand it, ur way of guidance is more cool...thats y i m asking for u.

i had been waiting for u on msn, but didnt see u on there...so thats y i am posting this on discussion forum and also mailing u...i hope u wont mind me mailing u?


thanks for ur precious time
Good day
Imran
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Thu Oct 02, 2003 10:01 pm

Well, that is quite a childish question...just joking...

You see there are hundreds of options /values for you to select in the xconfig part.
Basically xconfig is the utility through which u select all the options like what to enable, what to disable and what values to be set.Its is through xconfig that a .cfg file is generated which is used by the later make bzImage and even make modules scripts etc .

There are several options/values to be set in xconfig...those options depend and vary from machine to machine.Some are common but some are not.For instance if i have an isa slot , i would set isa support to yes...but a person who does not have isa support would set it to no.SO u see you have to select the options yourself.
If i start explaining all the options in xconfig , a complete book would be printed and many would still be left.
Each option in xconfig has a descrtiption.To see the description of what an option is and what it does , you can click on the ? box to the right of the option label.It will show you the details.Make your selection based on that.

To enable something to be built directly into the kernel, you set it to "y"
To enable something as module , u set it to "m"
TO disable something u set it to "n"

Also you can get more info about the options from the official kernel guide also available at tdlp.

The best method is to review the defaults, and edit them in accordance to your needs and requirements and based on your system specification.

The question you asked was something similar to a question like "Teach me everything about computers "

Also if you are still unsure of what a particular option does , you can post it here and i may give a few details on that.But simply asking describe each and every option in details is absurd and doesnt make sense.

outstream wrote:AoA

now before compiling kernel 2.4.22 i want to know how to configure it after giving make xconfig command..i mean what do u recommend? shall i go for defaults there or shall i change some thing manually in that configuration? and if i have to change any thing in configuration manually, would u please guide me step wise what to change? last time i remember that in configuration, by default, that was set to "n" in mounting vfat..so i set it to "y"...and also how to configure ppp in xconfig graphical configuration?

thanks for ur precious time
Good day
Imran
Linux for Life!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Fri Oct 03, 2003 1:40 am

AoA

mr Faraz.Fazil sir

sir ji good news...i recompiled the kernel again after fresh installation of rh9 and bingo..its all up and running good.. :lol: though i am getting some messages like...."bla bla bla test ..........Failed", during boot time but i guess may be that is because of new kernel configuration

well as u said to configure ppp as in form of modules...so i set "m" in ppp configuration..and i also took the screen shot. please visit the following link to see it

http://us.f1f.yahoofs.com/bc/3f7c7b9d_f ... _AbOqbQhLZ

and also i took the screen shot of help of ppp in that configuration tool, where it says to check "m" if i want to run it as modules. following link goes for that


http://us.f1f.yahoofs.com/bc/3f7c7b9d_f ... _AZAuCFNkJ


actually i uploaded files in yahoo briefcase, i hope they dont generate it dynamically and expire session after some time...i hope those links will work.

by giving a look at first link specially, u`ll get the idea of the options i set in ppp configuration.

so now please guide me through the following steps

1. please check and tell me if i have configured ppp correctly.

2. please tell me the next step now, i mean do i just have to install that driver rpm of modem and try to connect through ppp now...or is there something else i have to do to ppp before i install the driver and go for establishing some connection there.


thanks for ur precious time
Good Day
Imran
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Fri Oct 03, 2003 2:42 am

Yup checked the screen shots that u emailed me.
From the info in the screenshtos and from what u told me on msn, Seems like u selected the correct ppp support options.

Now that everything else is running fine on the new kernel, its time to install the ltmodem rpms that i previously provided you.

Install those rpms, save any messages, create a connection in kppp and try connecting.
Inshallah it should work.

Post the result here.

Wil wait for your reply.

Good luck!
Linux for Life!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Fri Oct 03, 2003 2:48 pm

AoA

mr Faraz.Fazil sir

I installed the lucent modem rpm, and still the problem seems to be there.
before continuing i would like to ask one more thing. when u posted the link of the driver rpm for the lucent modem, u said that driver is for kernel 2.4.08 i.e the default kernel for red hat 9 and u said if i have different kernel, u`ll post the link for that kernel. well previosuly i had that default kernel but now after compiling kernel 2.4.22, aint it changed? i mean the driver will work on this new kernel too?.

any ways lets get to the problem. when i clicked the query modem button the problem was the same "unable to open the modem"

u may see the screen shots at

http://briefcase.yahoo.com/imransalim2 .. there will be folder named as "modem" and image file name is screenshot-1.jpg.

after this i tried to dialout my connection anyways and again i got the same error. screen shot to this error is located at

http://briefcase.yahoo.com/imransalim2 ........ -->modem-->screenshot-3.jpg.


also u said to me, if nothing works then i should post contents of /etc/modules.conf, so here they are

-----------------------------------------------------

alias char-major-81 bttv
alias usb-controller usb-uhci
alias sound-slot-0 via82cxxx_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :

# lt_drivers: autoloading and insertion parameter usage
alias char-major-62 lt_serial
alias /dev/tts/LT0 lt_serial
alias /dev/modem lt_serial
# The next two lines are syntax examples, only Rarely Needed, to automate parameter usage during lt_drivers insertion. See documentation for details.
# options lt_modem vendor_id=0x115d device_id=0x0420
# options lt_modem Forced=3,0x130,0x2f8,0
# section for lt_drivers ends

----------------------------------------------------------

at the end therez another thing, u said me to type "sndconfig" in terminal to check if sound is working. when i typed "sndconfig" in terminal, it said sumthing like "bash : error: sndconfig command not found" sumthing like that.

i hope to get some good instructions from u again.

Thanks for ur precious time

Good Day
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby outstream » Sun Oct 05, 2003 1:58 am

O bhaiooo kahan ho saray...koi tow reply ker dey yaaaar
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Sun Oct 05, 2003 8:30 am

Well thats strange.
There is no reason for the modem to not work properly now.
The only reason may be that ofcourse u now need to use the ltmodem rpm for the 2.4.22 kernel...or the other reason may be that u did something wrong.
Also ur /etc/modules.conf doesnt contain any related alias-char-major entry , nor does it indicate that ppp support is in modules.

As a first step:

Go to: http://www.physcip.uni-stuttgart.de/heby/ltmodem/

and download the ltmodem rpm for 2.4.22 kernel.
Install it as before.

See if it works...also save and post any messages here.

Also are u sure u carried out the make modules and make modules_install part during the kernel recompile.

Also type pppd in terminal and see what output does it give.
Linux for Life!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe


Return to “%s” Installation

Who is online

Users browsing this forum: No registered users and 2 guests

cron