Kernel...

Yeah well i installed mandrake 9.1 yesterday, and im a btinternet ADSL 576k user, with an alcatel speedtouch modem.. now i installed redhat 9 a while ago an i couldnt get it to work, im having a *bit* more luck this time, and i saw on This Page in the 'News' bit it says..

'The just-released 2.4.22 kernel contains the speedtouch kernel module. Thanks Marcello! '

Now im guessing this means if i install this kernel i should be able to plug in my modem and surf the net... but my question (as a linux n00b)... is how do i install the 2.4.22 kernel? i have it downloaded and extracted in my 'home' area, i just dont have a clue what to do with it now... any help would be greatly appreciated... sorry if this has been posted before, i had a quick search but yeah....

thanks loads in advance, i'd really appreciate any help!

(P.S... i downloaded the mgmt.o file, and put it in /usr/share/speedtouch and it seems to like... accept my driver, and it does something when i press 'connect' but there must be something wrong cause it never 'keeps' the connection... it says 'transferring' etc.. and connecting an theres activity... do i need to enter the btinternet DNS? and if so... does anybody know where i could find it?... if the kernel compilings an easier process than this one, then i'd appreciate any help getting it to work, cause im clueless so yeah... cheers loads)...

check the thread:
http://www.linuxquestions.org/questi...threadid=97130
it's not really the same problem, but you might find useful information - let me know if you do!

******EDIT*******
as requested there was wanting the instructions on how to apply patches to your kernel.
****END EDIT*****/

This step comes after untaring your kernel source.
When you download the patch place it in the folder that you untarred you new kernel.
Then typed:
patch -E -p1 < sound_patch
Purely an example and you would type whatever the file name is in replace of sound_patch.

hmmm im downloading the full source for 4.2.22, but... i had the bz2 patch lol, an i did that... and i didnt have the full source, so now its asking me which file to patch...

jesus i dont have a clue what im doing lol... should i just extract the source where the patch is an type in the filename? (which filename?) then will it be done? christ lol im in way over my head :$

http://www.linuxquestions.org/questi...ight=athlon+64

^^ link to thread

by Kiada
Now im guessing this means if i install this kernel i should be able to plug in my modem and surf the net...

uhh, no. the kernel that comes with red hat or mandrake will already have support for your modem, that is not the problem, installing a new kernel wont really get you any further than you are now, only more confused.

first thing to check is if the firmware is being loaded when you plug the modem in(does the ADSL light go orange for about 5 seconds then flash green for about 20)

if that works you then need to watch your syslogs as it dials - in a terminal type tail -f /var/log/mesages before you connect.

and report back. btw if you think its hard now you should have tried to set it up 18 months ago

nah i checked the mandrake compatibility list, my modem was there but not known to be supported, an elsewhere on the not theres loadsa how to's etc.. but no, it just stays green like it does with windows, it dials an displays like transfer speeds.. i even got a 'connected' once for a about 10 seconds but a page didnt load up or anything.. so the driver seems to be working, its the configuration (im guessing)... do i need to input the DNS in the draknet bit for the ADSL modem connection configuration bit?

by Kiada
but no, it just stays green like it does with windows

are we talking about the same modem, the alcatel speedtouch usb green frog, because in both windows, linux, and bsd at some point the firmware has to be loaded(makes lights flash as i described) iirc in win2k it does it on boot up shortly after it goes into the first graphics screen.

you shouldnt type any dns servers in, it should get them automatically

if you reckon it is connecting then open up a root shell and type ifconfig if it talks about ppp0 then it is, if it doesnt then it isnt

ahhh yeah sorry, yeah it loads the firmware

but it only connected once an disconnected straight away, so something must be wrong.. hmmm soz bout this :$ anyways ive nearly finished installing the 2.4.22 kernel, so ill see if this helps!

good luck with your kernel but im 99% sure that this is a ppp configuration problem, so if/when it still doesnt work, open up a terminal and type tail -f /var/log/messages then attempt to connect and tell us the output.

hmmm ok so doin the kernel didnt make a blind bit of difference lol.... damn, hmmm i made a screenshot if anybody wants to help me :$ it kinda shows what i mean... if you look at the connection status it says 'connection complete' then after a few seconds it disconnects.. an during the time its 'complete' it doesnt load any pages or anything anyways... hmmm.... hope this helps... soz about the filesize...

http://www.beatsnrhymes.net/blah1.jpg

ahhh soz kev, just saw your post, yeah ill give it a go :$

by me
if that works you then need to watch your syslogs as it dials - in a terminal type tail -f /var/log/mesages before you connect.

again by me
so if/when it still doesnt work, open up a terminal and type tail -f /var/log/messages then attempt to connect and tell us the output.

gui's are useless in diagnosing problems(imho they are useless for most things) we need your syslog when your attempting to connect, without that we cant do anything

sorry i had to go out, im back now an ive tried it... the logs quite long but this is what it came up with...

[root@main kiada]# tail -f /var/log/messages Sep 27 17:28:29 main modprobe: modprobe: Can't locate module tr0 Sep 27 17:28:29 main modprobe: modprobe: Can't locate module tr1 Sep 27 17:28:29 main modprobe: modprobe: Can't locate module tr2 Sep 27 17:28:29 main modprobe: modprobe: Can't locate module tr3 Sep 27 17:28:29 main modprobe: modprobe: Can't locate module fddi0 Sep 27 17:28:29 main modprobe: modprobe: Can't locate module fddi1 Sep 27 17:28:29 main modprobe: modprobe: Can't locate module fddi2 Sep 27 17:28:29 main modprobe: modprobe: Can't locate module fddi3 Sep 27 17:29:00 main CROND[3121]: (mail) CMD (/usr/bin/python -S /var/lib/mailma n/cron/qrunner) Sep 27 17:29:01 main su(pam_unix)[3111]: session opened for user root by kiada(u id=501) Sep 27 17:29:25 main drakconnect[2322]: running: /etc/sysconfig/network-scripts/ net_cnx_pg & Sep 27 17:29:25 main net_monitor.real[3237]: ### Program is starting ### Sep 27 17:29:38 main net_monitor.real[3237]: launched command: /etc/sysconfig/network-scripts/net_cnx_up & Sep 27 17:29:44 main modem_run[3284]: modem_run version 1.2-beta1 started by root uid 0 Sep 27 17:29:46 main kernel: usb_control/bulk_msg: timeout Sep 27 17:29:46 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:29:48 main kernel: usb_control/bulk_msg: timeout Sep 27 17:29:48 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:29:48 main modem_run[3284]: BLOCK1 Sep 27 17:29:50 main kernel: usb_control/bulk_msg: timeout Sep 27 17:29:50 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:29:52 main kernel: usb_control/bulk_msg: timeout Sep 27 17:29:52 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:29:52 main modem_run[3284]: BLOCK1 Sep 27 17:29:54 main kernel: usb_control/bulk_msg: timeout Sep 27 17:29:54 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:29:56 main kernel: usb_control/bulk_msg: timeout Sep 27 17:29:56 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:29:56 main modem_run[3284]: BLOCK1 Sep 27 17:29:58 main kernel: usb_control/bulk_msg: timeout Sep 27 17:29:58 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:30:00 main CROND[3301]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner) Sep 27 17:30:00 main CROND[3302]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/gate_news) Sep 27 17:30:00 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:00 main modem_run[3284]: BLOCK1 Sep 27 17:30:00 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:30:02 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:02 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:30:04 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:04 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:30:04 main modem_run[3284]: BLOCK1 Sep 27 17:30:06 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:06 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:30:08 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:08 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:30:08 main modem_run[3284]: BLOCK1 Sep 27 17:30:10 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:10 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:30:12 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:12 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:30:12 main modem_run[3284]: BLOCK1 Sep 27 17:30:14 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:14 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:30:16 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:16 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:30:16 main modem_run[3284]: BLOCK1 Sep 27 17:30:18 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:18 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:30:20 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:20 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:30:20 main modem_run[3284]: BLOCK1 Sep 27 17:30:22 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:22 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Sep 27 17:30:24 main kernel: usb_control/bulk_msg: timeout Sep 27 17:30:24 main kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x5 len 991 ret -110 Sep 27 17:30:24 main modem_run[3284]: BLOCK1 Sep 27 17:31:00 main CROND[3360]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner) Sep 27 17:32:01 main CROND[3414]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner) Sep 27 17:32:18 main dhclient: DHCPREQUEST on eth0 to 192.168.0.1 port 67 Sep 27 17:32:18 main dhclient: DHCPACK from 192.168.0.1 Sep 27 17:32:28 main dhclient: bound to 192.168.0.162 -- renewal in 237 seconds.

Hmmm does this help you at all?

all the modem_run stuff is the uploading of the firmware and all those fails are normal, however it should start dialing using pppd, instead it seems to be configuring your network card via dhcp, this is quite confusing, i would guess the gui configurator has got itsself into a mess.

my suggestion is you go to the site you linked to in your first post, goto the documentation, skip to step 9 - configuring pppoa and follow what it says, see how far you get (it will muck up normal modem configuration though)

ok thanks for the help ill have a go though i aint too confident with it all lol, cheers

any luck?