On Thu, 30 Sep 2004 11:03, Lance Blackler wrote: > Thanks for that - I will try it and see how it goes. I'll let you know > what progress I make if any. > > Lance B > > -----Original Message----- > From: dave G <[EMAIL PROTECTED]> > Sent: Thu, 30 Sep 2004 22:59:38 +1200 > To: [EMAIL PROTECTED] > Subject: Re: Set serial problem in 2.6.7 (Mepis Debian) > > On Thu, 30 Sep 2004 9:46, Lance Blackler wrote: > > Hi Cluggers. > > > > I have rejoined the list for a while 'cause I am having a problem with > > setting up my modem for the 2.6.7 kernel. > > > > Running Simple Mepis (Debian stable/unstable) on a PIII 800. > > Modem is an Actiontec hardware PCI56K type (same as your one Yuri). > > > > It works fine on the 2.4.24 (I think - but not too important) kernel when > > I run the following commands (got them down pat now :)) > > > > cd /dev > > MKDEV ttyS4 > > ln -s ttyS4 modem > > chmod 666 ttyS4 > > chmod 666 modem > > > > setserial modem autoconfig > > > > But when I try that in the 2.6 kernel, it fails with the error mentioning > > incorrect parameter for setserial. I havn't been able to find anything > > about it on google or elsewhere, any ideas about this most welcome. > > > > Does setserial run differently in 2.6 or am I doing something wrong? > > > > Alternatively, can anyone suggest a good modem setup tool for Debian. > > Xandros must have one as it autodetects the modem and sets it up > > correctly (with the 2.4 kernel though) - but I don't know what it is as > > it is called by the 1st run wizard. > > > > I have used other tools such as modemedit and modemtool in RPM distros > > (Lycoris and ELX for example) and they worked well. I think I may have > > used kudzu on another box successfully as well, but it won't run on this > > box (seg faults). > > > > Thanks in advance for any feedback. > > > > Lance Blackler > > Hi Lance > > I have been struggling with my XH1154 internal modem on Simply Mepis kernel > 2.6.7 (which uses the Intel536 chipset I think) > > I haven't had much of a result for this yet but have had it running > previously (but not currently) on 2.4.26, but I was unable to get it to > remain during reboot > > I gather there are some issues with the 2.6.7 kernel on Simply Mepis I have > been trawling the mepis sites but as yet had no luck > > anyway one thing I have found out is Simply Mepis doesn't install the > kernel headers during the install and these had to be obtained separately > with apt-get, despite this I still got errors when compiling etc. etc. > > I have attache d the reply on this from Ross Hamblin at Dick Smith > below.... > > cheers................dave G > > Mail to: "[EMAIL PROTECTED]" > > ____________________________________________ > > KMail 1.7 & Kontact - KDE Desktop 3.3.0 > SimplyMEPIS Linux - Kernel 2.6.7 (i686) > ____________________________________________ > > FW: XH1154 which will build on 2.6. kernel > > > From: > "Ross Hamblin" <[EMAIL PROTECTED]> > > > To: > [EMAIL PROTECTED] > > > Date: > 26/08/04 3:07 > > > Further to below, I found someone with the same symptoms as you on a Mepis > Linux forum. You do need to install kernel source, use something like > apt-get install kernel-source-2.6.7 to install the kernel source. > > Regards, > Ross. > > -----Original Message----- > From: Ross Hamblin > Sent: Thursday, 26 August 2004 14:49 > To: 'Dave G' > Subject: RE: XH1154 which will build on 2.6. kernel > > > Hi Dave, > > <snip> > > > I have tried recompiling the driver again following the > > instructions you > > emailed however I'm still getting errors:- > > > > [EMAIL PROTECTED] make 536 > > Module precompile check > > Current running kernel is: 2.6.7 > > /lib/modules... autoconf.h exists > > autoconf.h matches running kernel > > version.h matches running kernel > > uname -r|grep "2.6" && > > cd coredrv && make 536core_26 && > > cp Intel536.ko .. && cd .. && > > strip --strip-debug Intel536.ko && > > exit; > > ls Intel536.ko >/dev/null 2>&1 || uname -r | grep "2.6" && > > echo "Failed to > > build driver" && exit; > > if [ ]; then > > cd coredrv; make TARGET=TARGET_SELAH KERNEL_SOURCE_PATH= > > "PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; > > else > > cd coredrv; make TARGET=TARGET_SELAH > > KERNEL_INCLUDES=/lib/modules/`uname > > -r`/build/include > > "PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; > > fi ; > > cp Intel536.o .. ; > > if [ -a /boot/vmlinuz.version.h ]; then > > cp /boot/vmlinuz.version.h /lib/modules/`uname > > -r`/build/include/linux/version.h; > > fi > > 2.6.7 > > make[1]: Entering directory `/tmp/intel-536EP-2.56.76.0/coredrv' > > make -C /lib/modules/2.6.7/build > > SUBDIRS=/tmp/intel-536EP-2.56.76.0/coredrv > > modules > > make[2]: Entering directory `/usr/src/linux-2.6.7' > > Makefile:450: /usr/src/linux-2.6.7/arch/i386/Makefile: No > > such file or > > directory > > make[2]: *** No rule to make target > > `/usr/src/linux-2.6.7/arch/i386/Makefile'.Stop. > > make[2]: Leaving directory `/usr/src/linux-2.6.7' > > make[1]: *** [536core_26] Error 2 > > make[1]: Leaving directory `/tmp/intel-536EP-2.56.76.0/coredrv' > > 2.6.7 > > Failed to build driver > > [EMAIL PROTECTED] > > > > from the errors above I figured the problem was the missing > > simlink/ or file > > (I don't have a ..../arch/i386/ directory in /usr/src/linux-2.6.7):- > > > > "Makefile:450: /usr/src/linux-2.6.7/arch/i386/Makefile: No > > such file or > > directory" > > > > so i tried creating a simlink to:- > > > > "/usr/src/linux-2.6.7/Makefile" but this didn't work either?? > > [RH] Ok, this indicates to me that you may not have the (complete) kernel > source installed, the arch tree is where the hardware specific (arch is > short for architecture) portions of source code are stored, the source tree > will not work without it - it is also where the kernel binary is written to > after compilation. Each directory off /usr/src/linux will have it's own > makefile which is why the symlink you made did not work - it needed the > correct makefile for the arch directory/tree. Did you ever build a kernel > on this system? It maybe that you have installed a binary kernel and kernel > headers instead of the full kernel source. If you have the full source an > dhave previously built a kernel, there should be a file called .config > in /usr/src/linux, if that is not there, you will need to obtain the full > source, then configure it (you should be able to find a default config file > in /boot/config-2.6.7 or similar). If you need help with configuring and > building the kernel, get back to me.
Lance yep I would be keen to hear how you get on... cheers................dave G Mail to: "[EMAIL PROTECTED]" ____________________________________________ KMail 1.7 & Kontact - KDE Desktop 3.3.0 SimplyMEPIS Linux - Kernel 2.6.7 (i686) ____________________________________________
