Linux - HOWTO (With Stats)

Status
Not open for further replies.
Did some searching and found it.

Before entering the run levels after initial system init:
boot.local

After completing run levels but before loading startup:
after.local

This is in SUSE 10.1. I went through some of the boot scripts and found the references. Was butting heads with google this morning.

Now for my next challenging.... Finding out which scripts run when mounting external USB drives :)

Tazz_Tux said:
Wierd !!!!
From my old redhat days I tend to remember a rc.startup file somewhere....

slocate local.start <-- should find my file
slocate rc.startup <-- might find this one

Laterz !
Click to expand...
 
Hi Tazz_Tux

I really appreciate your help. Sorry for the long delay in replying.
My connection now works, it works with or without these two options. It seems it was just bad reception at the time. I've also since had a "NO CARRIER" response, but this I think is more likely due to bad reception.

Are there any AT commands to check signal strength and things like that?

Fred

Tazz_Tux said:
Hi freds,

Add the following lines to the options file:
Code: 
noccp
nobsdcomp

Let me know !

Laterz !
Click to expand...
 
Huawei E620, Suse 10.1, Cant figure out whats wrong....

Afternoon all

Have been trying to get the huawei e620 card working with suse 10.1
have failed badly :-(

Also downloaded the nozomi driver and tried to compile it and also failed horribly.

I already have an option driver installed, check the following and see if anyone can identify whats happening.

so insert card - /var/log/messages shows
Aug 8 10:13:10 ignition kernel: pccard: CardBus card inserted into slot 0
Aug 8 10:13:10 ignition kernel: yenta EnE: chaning testregister 0xC9, 04 -> 04


lsusb

Bus 003 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 002: ID 0458:0019 KYE Systems Corp. (Mouse Systems)
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

modprobe usbserial & modprobe option (even with vendor & prod ids)

Aug 8 10:21:32 ignition kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Option 3G data card
Aug 8 10:21:32 ignition kernel: usbcore: registered new driver option
Aug 8 10:21:32 ignition kernel: drivers/usb/serial/option.c: Option Card (PC-Card to) USB to Serial Driver: v0.4

lsusb

Bus 003 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 002: ID 0458:0019 KYE Systems Corp. (Mouse Systems)
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

cat /dev/ | grep ttyS

/dev/ttyS0
/dev/ttyS1
/dev/ttyS2
/dev/ttyS3
/dev/ttyS4
/dev/ttyS5
/dev/ttyS6
/dev/ttyS7

So anyone got any idea as to what I am doing wrong?
ok right so this laptop was purchased by my employer (not knowing that I would want to install linux) - its an acer travelmate 5600.
Suse is the only distro that I have been able to get working (semi stable)

Anyways any help here is appreciated.

Later
skrat
 
hi tazz tux,
been right thru this and still stumped if you've got a minute.
everything looks right , wvdial scripts seem to work perfectly,
just can't seem to send or recieve anything.
this is using a u630, with the led going from flashing blue during handshake to solid blue after connection.
following is a script file of everything that i could think of that might show what the problem is....
(in the uk if it matters, btw)

i know the dns are wrong, but i get the same results when they look a bit happier....its hit and miss

Code: 
Script started on Tue Aug  8 11:34:22 2006
tail /var/log/messages 
Aug  8 11:31:51 localhost kernel: [17181199.612000] pccard: card ejected from slot 0
Aug  8 11:31:57 localhost kernel: [17181206.000000] pccard: PCMCIA card inserted into slot 0
Aug  8 11:31:57 localhost kernel: [17181206.000000] pcmcia: registering new device pcmcia0.0
Aug  8 11:31:57 localhost kernel: [17181206.000000] pcmcia: registering new device pcmcia0.1
Aug  8 11:31:57 localhost kernel: [17181206.072000] 0.0: ttyS0 at I/O 0x3f8 (irq = 3) is a 16550A
Aug  8 11:33:56 localhost kernel: [17181325.056000] pccard: card ejected from slot 0
Aug  8 11:34:09 localhost kernel: [17181337.780000] pccard: PCMCIA card inserted into slot 0
Aug  8 11:34:09 localhost kernel: [17181337.780000] pcmcia: registering new device pcmcia0.0
Aug  8 11:34:09 localhost kernel: [17181337.780000] pcmcia: registering new device pcmcia0.1
Aug  8 11:34:09 localhost kernel: [17181337.836000] 0.0: ttyS0 at I/O 0x3f8 (irq = 3) is a 16550A
route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
wvdial novatel &
[1] 12775
--> WvDial: Internet dialer version 1.55
--> Cannot set information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATZ
ATZ
OK
--> Sending: ATE0V1&D2&C1S0=0+IFC=2,2
ATE0V1&D2&C1S0=0+IFC=2,2
OK
--> Modem initialized.
--> Sending: ATDT*99***1#
--> Waiting for carrier.
CONNECT
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Tue Aug  8 11:34:44 2006
--> Pid of pppd: 12779
--> Using interface ppp0
--> local  IP address 10.167.21.118
--> remote IP address 10.64.64.64
--> primary   DNS address 10.11.12.13
--> secondary DNS address 10.11.12.14

route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.64.64.64     *               255.255.255.255 UH    0      0        0 ppp0
default         *               0.0.0.0         U     0      0        0 ppp0
cat /etc/resolv.conf
nameserver 10.11.12.13
nameserver 10.11.12.14
search home
ping -c 4 www.google.co.uk
ping: unknown host www.google.co.uk
Script done on Tue Aug  8 11:35:51 2006

any ideas would be really appreciated,
cheers,
mat
 
Hi,

I am waiting to get my hands on the cards to get it tested etc.

Laterz !

skrat said:
Afternoon all

Have been trying to get the huawei e620 card working with suse 10.1
have failed badly :-(

So anyone got any idea as to what I am doing wrong?
ok right so this laptop was purchased by my employer (not knowing that I would want to install linux) - its an acer travelmate 5600.
Suse is the only distro that I have been able to get working (semi stable)

Anyways any help here is appreciated.

Later
skrat
Click to expand...
 
I am a bit worried about the DNS, since you don't show you pinging an IP. Try and ping a server that you know the IP of and that should normally reply.

Laterz !

poddy said:
hi tazz tux,
been right thru this and still stumped if you've got a minute.
everything looks right , wvdial scripts seem to work perfectly,
just can't seem to send or recieve anything.
this is using a u630, with the led going from flashing blue during handshake to solid blue after connection.
following is a script file of everything that i could think of that might show what the problem is....
(in the uk if it matters, btw)

i know the dns are wrong, but i get the same results when they look a bit happier....its hit and miss

ping -c 4 www.google.co.uk
ping: unknown host www.google.co.uk
Script done on Tue Aug 8 11:35:51 2006

any ideas would be really appreciated,
cheers,
mat
Click to expand...
 
hi tazz,
cheers for help :)

tried again using ip of google.co.uk.....
used kppp to dial as it gives real dns more often than wvdial

Code: 
ifconfig
ppp0      Link encap:Point-to-Point Protocol
          inet addr:10.171.126.202  P-t-P:10.64.64.64  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:108 (108.0 b)  TX bytes:117 (117.0 b)

cat /etc/resolv.conf
nameserver 10.205.65.68
nameserver 10.205.65.68
search home
nameserver 10.205.65.68 #kppp temp entry
nameserver 10.205.65.68 #kppp temp entry

ping -c 4 64.233.161.104 (www.google.co.uk)
PING 64.233.161.104 (64.233.161.104): 56 data bytes
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1

route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.64.64.64     *               255.255.255.255 UH    0      0        0 ppp0
default         *               0.0.0.0         U     0      0        0 ppp0

does the route table look screwy to you?
 
Last edited:
Looks okay.....except for the

"
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1
"
Disable your firewall (just for a test :)) and try again

Laterz !

poddy said:
hi tazz,
cheers for help :)

tried again using ip of google.co.uk.....
used kppp to dial as it gives real dns more often than wvdial

Code: 
ifconfig
ppp0      Link encap:Point-to-Point Protocol
          inet addr:10.171.126.202  P-t-P:10.64.64.64  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:108 (108.0 b)  TX bytes:117 (117.0 b)

cat /etc/resolv.conf
nameserver 10.205.65.68
nameserver 10.205.65.68
search home
nameserver 10.205.65.68 #kppp temp entry
nameserver 10.205.65.68 #kppp temp entry

ping -c 4 64.233.161.104 (www.google.co.uk)
PING 64.233.161.104 (64.233.161.104): 56 data bytes
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1
ping: sendto: Operation not permitted
ping: wrote 64.233.161.104 64 chars, ret=-1

route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.64.64.64     *               255.255.255.255 UH    0      0        0 ppp0
default         *               0.0.0.0         U     0      0        0 ppp0

does the route table look screwy to you?
Click to expand...
 
Doh!
that'll be it then , cheers tazz :)
seems the 10.11.12.13 dns get assigned when 3gonly is specified and there is no 3g in the area.
gprs is working fine
 
And everything else is ok now ? You can open ppp0 for outgoing and incomming must match established and related. Not sure what suse uses to configure the firewall, but I can give you the raw iptables rules if you want :)

You can always just override the DNS in /etc/resolve.conf. If you enter long times when the DNS doesn't work (from the provider) simply tell PPPD not to accept the DNS from them. Simply add two working DNS servers to your /etc/resolv.conf and enjoy !

Anywayz, welcome to 3g and Linux surfing ! :)

poddy said:
Doh!
that'll be it then , cheers tazz :)
seems the 10.11.12.13 dns get assigned when 3gonly is specified and there is no 3g in the area.
gprs is working fine
Click to expand...
 
Tazz_Tux said:
You can always just override the DNS in /etc/resolve.conf. If you enter long times when the DNS doesn't work (from the provider) simply tell PPPD not to accept the DNS from them. Simply add two working DNS servers to your /etc/resolv.conf and enjoy !

Anywayz, welcome to 3g and Linux surfing ! :)
Click to expand...

ta tazz :)
posting from ubuntu dapper @ the mo'
seems card isn't happy on a 686 compiled kernel (or on mepis, which is weird, as its based on ubuntu)
card works fine on 2.6.15-23-386, not on 686 version, and not on 2.6.15-26-x86.
be cool to get it working on mepis without dual booting to ubuntu....
any suggestions where to prod around to spot the difference?

same problem as other people, connects fine, but transfer stops after a few bytes of data, never recovers.

cheers,
mat
 
Howzit,

I already forgot what card you running :( but here is some general tips:

I spotted that the kernel changes a patch version from 23 to 26. Normally with distro that are pre-compiled the patch version isn't changed. It will go from 2.6.15-23-386 to 2.6.15-23-686 etc. Maybe there is a patch that isn't loaded nicely ?

If you are using the new Option card (nomozi) you will have to compile the driver for every kernel you are using - even thought it loads, I generally do it :)

As for the distro based on ubuntu, first get it working 100% on the upstream (ubuntu) and then try lower down. One thing to do would be the post the kernel versions (run "uname -a") along with your card details (make etc)

Laterz !
poddy said:
ta tazz :)
posting from ubuntu dapper @ the mo'
seems card isn't happy on a 686 compiled kernel (or on mepis, which is weird, as its based on ubuntu)
card works fine on 2.6.15-23-386, not on 686 version, and not on 2.6.15-26-x86.
be cool to get it working on mepis without dual booting to ubuntu....
any suggestions where to prod around to spot the difference?

same problem as other people, connects fine, but transfer stops after a few bytes of data, never recovers.

cheers,
mat
Click to expand...
 
Hey Tazz_Tux,

I updated my laptop from Fedora Core 4 to 5, and now my Novatel U740 wont work anymore :(

When I insert the card I get:
Code: 
Aug 14 17:21:28 Hogsmeade kernel: pccard: CardBus card inserted into slot 0
Aug 14 17:21:28 Hogsmeade kernel: yenta EnE: chaning testregister 0xC9, 04 -> 04

And when I insert the usbserial module into the kernel (modprobe usbserial vendor=0x1410 product=0x1400) I get:
Code: 
Aug 14 17:22:55 Hogsmeade kernel: usbcore: registered new driver usbserial_generic
Aug 14 17:22:55 Hogsmeade kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core

It worked perfect on FC4 :confused:
I can't think what's changed in FC5 that it won't work now?
Any ideas?

EDIT:
I also tried inserting the module with: modprobe usbserial vendor=0x1410 product=0x1410 .. no luck
 
Last edited:
New Kernel perhaps :(

The quickest way to fix it is to run "lsusb -v" with the card in. Confirm that the product ID is 1400 (I have seen it as 1410) and adjust your command as needed.

Check for a newly released kernel for FC5 but I am sure that we will get it working !

Laterz !

redarrow said:
Hey Tazz_Tux,

I updated my laptop from Fedora Core 4 to 5, and now my Novatel U740 wont work anymore :(

When I insert the card I get:
Code: 
Aug 14 17:21:28 Hogsmeade kernel: pccard: CardBus card inserted into slot 0
Aug 14 17:21:28 Hogsmeade kernel: yenta EnE: chaning testregister 0xC9, 04 -> 04

And when I insert the usbserial module into the kernel (modprobe usbserial vendor=0x1410 product=0x1400) I get:
Code: 
Aug 14 17:22:55 Hogsmeade kernel: usbcore: registered new driver usbserial_generic
Aug 14 17:22:55 Hogsmeade kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core

It worked perfect on FC4 :confused:
I can't think what's changed in FC5 that it won't work now?
Any ideas?

EDIT:
I also tried inserting the module with: modprobe usbserial vendor=0x1410 product=0x1410 .. no luck
Click to expand...
 
Ooooppppsss - didn't see the edit :)

As wierd as it sounds - restart pcmcia with the card in, and don't boot the machine with the card in.

Let me know ! :)

Tazz_Tux said:
New Kernel perhaps :(

The quickest way to fix it is to run "lsusb -v" with the card in. Confirm that the product ID is 1400 (I have seen it as 1410) and adjust your command as needed.

Check for a newly released kernel for FC5 but I am sure that we will get it working !

Laterz !
Click to expand...
 
Hey Tazz_Tux,

I got the problem fixed up! :o I completely forgot that on my system for some reason I need to pass the kernel the option "pci=assign-busses" this was also true for Fedora Core 4 - in fact I think I already posted it somewhere here :o

On a side note there have been some changes in FC5, from the website:
Fedora Core 5 Website said:
The PCMCIA framework used by laptop and mobile devices has changed. The older pcmcia-cs package using the cardmgr/pcmcia service has been replaced with a new pcmciautils package. With pcmciautils, PCMCIA devices are handled directly and dynamically by the hotplug and udev subsystems. This update increases both efficiency and performance of the system. For more information about these changes, refer to http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html.
Click to expand...

Although this change doesn't seem to make much difference except that there no longer is a pcmcia service in /etc/init.d/ ...
If you follow the link in the quote above it also mentions the "pci=assign-busses" thing..

Thanks! :)

btw.. hows your Linux dash coming on? :D
 
Well done man ! I have been out of the FC loop for a bit now so I don't really track the changes :)

As for DFL....watch this space, been a bit busy

redarrow said:
Hey Tazz_Tux,

I got the problem fixed up! I completely forgot that on my system for some reason I need to pass the kernel the option "pci=assign-busses" this was also true for Fedora Core 4 - in fact I think I already posted it somewhere here :o

On a side note there have been some changes in FC5, from the website:


Although this change doesn't seem to make much difference except that there no longer is a pcmcia service in /etc/init.d/ ...
If you follow the link in the quote above it also mentions the "pci=assign-busses" thing..

Thanks! :)

btw.. hows your Linux dash coming on? :D
Click to expand...
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X