Discussion:
(unknown)
(too old to reply)
saurabh khanna
2003-01-31 18:46:05 UTC
Permalink
Problem: My xwindows did not open and my sound card don't work.

Xwindows:
I am a novice. I am using redhat linux 8. It detects my graphics
card
correctly but when i tried to open xwindows, my system hangs.

Sound:
Linux has detected my sound card once but not configured it and
after
that nor it is working nither it is detected by my linux.

GRUB:
Also, i can boot my linux through LILO only. GRUB wont work, it
gives
error "Not enough memory".

I have re-installed linux on my computer but the problem
remains.
All other detailes are follows.

Kernel version:
Linux version 2.4.18-14 (***@astest.test.redhat.com)
(gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7))
#1 Wed Sep 4 12:13:11 EDT 2002


Commond which triggers the problem:
startx

Processor information:
processor : 0

vendor_id : AuthenticAMD

cpu family : 6

model : 6

model name : AMD Athlon(TM) XP 1700+

stepping : 2

cpu MHz : 1469.861

cache size : 256 KB

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 1

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow

bogomips : 2920.57



Module information:
nls_iso8859-1 3516 1 (autoclean)

nls_cp437 5116 1 (autoclean)

vfat 13084 1 (autoclean)

fat 38744 0 (autoclean)
[vfat]
autofs 13348 0 (autoclean) (unused)

ipt_REJECT 3736 2 (autoclean)

iptable_filter 2412 1 (autoclean)

ip_tables 14840 2 [ipt_REJECT iptable_filter]

mousedev 5524 0 (unused)

keybdev 2976 0 (unused)

hid 22244 0 (unused)

input 5888 0 [mousedev keybdev hid]

usb-ohci 21288 0 (unused)

usbcore 77056 1 [hid usb-ohci]

ext3 70400 1

jbd 52212 1 [ext3]



Loaded driver and hardware information:
0000-001f : dma
1
0020-003f : pic
1
0040-005f : timer

0060-006f : keyboard

0070-007f : rtc

0080-008f : dma page reg

00a0-00bf : pic
2
00c0-00df : dma
2
00f0-00ff : fpu

01f0-01f7 : ide
0
02f8-02ff : serial(auto)

03c0-03df : vga+

03f6-03f6 : ide
0
03f8-03ff : serial(auto)

0cf8-0cff : PCI conf
1
5000-500f : PCI device 10de:01b4 (nVidia Corporation)

5100-511f : PCI device 10de:01b4 (nVidia Corporation)

5500-550f : PCI device 10de:01b4 (nVidia Corporation)

a800-a80f : nVidia Corporation nForce IDE

a800-a807 : ide0

a808-a80f : ide1

b000-bfff : PCI Bus #01

b800-b807 : Rockwell International HCF 56k Data/Fax/Voice/Spkp
(w/Handset) Modem

d800-d807 : PCI device 10de:01c3 (nVidia Corporation)

e000-e07f : PCI device 10de:01b1 (nVidia Corporation)

e100-e1ff : PCI device 10de:01b1 (nVidia Corporation)

00000000-0007ffff : System RAM

0009fc00-0009ffff : reserved

000a0000-000bffff : Video RAM area

000c0000-000c7fff : Video ROM

000f0000-000fffff : System ROM

00100000-06febfff : System RAM

00100000-00247f2e : Kernel code

00247f2f-0033ed03 : Kernel data

06fec000-06feefff : ACPI Tables

06fef000-06ffefff : reserved

06fff000-06ffffff : ACPI Non-volatile Storage

eb000000-ec7fffff : PCI Bus #02

eb000000-ebffffff : nVidia Corporation GeForce2 Integrated GPU

ec800000-ecffffff : PCI Bus #01

ec800000-ec80ffff : Rockwell International HCF 56k
Data/Fax/Voice/Spkp (w/Handset) Modem

ed000000-ed000fff : PCI device 10de:01b1 (nVidia Corporation)

ed800000-ed87ffff : PCI device 10de:01b0 (nVidia Corporation)

ee000000-ee0003ff : PCI device 10de:01c3 (nVidia Corporation)

ee800000-ee800fff : PCI device 10de:01c2 (nVidia Corporation)

ee800000-ee800fff : usb-ohci
e
f000000-ef000fff : PCI device
10de:01c2 (nVidia Corporation)

ef000000-ef000fff : usb-ohci
e
ff00000-f7ffffff : PCI Bus #02

f0000000-f7ffffff : nVidia Corporation GeForce2 Integrated GPU

f8000000-fbffffff : PCI device
10de:01a4 (nVidia Corporation)

fec00000-fec00fff : reserved

fee00000-fee00fff : reserved

ffff0000-ffffffff : reserved


PCI information:
00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev
b2)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [40] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2,x4
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=x1
Capabilities: [60] #08 [2001]

00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory
Controller (rev b2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory
Controller (rev b2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

00:00.3 RAM memory: nVidia Corporation: Unknown device 01aa (rev
b2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev
c3)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [50] #08 [01e1]

00:01.1 SMBus: nVidia Corporation nForce PCI System Management
(rev c1)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at 5000 [size=16]
Region 1: I/O ports at 5500 [size=16]
Region 2: I/O ports at 5100 [size=32]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.0 USB Controller: nVidia Corporation: Unknown device 01c2
(rev c3) (prog-if 10 [OHCI])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ef000000 (32-bit, non-prefetchable)
[size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:03.0 USB Controller: nVidia Corporation: Unknown device 01c2
(rev c3) (prog-if 10 [OHCI])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ee800000 (32-bit, non-prefetchable)
[size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:04.0 Ethernet controller: nVidia Corporation: Unknown device
01c3 (rev c2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ee000000 (32-bit, non-prefetchable)
[size=1K]
Region 1: I/O ports at d800 [size=8]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:05.0 Multimedia audio controller: nVidia Corporation: Unknown
device 01b0 (rev c2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 3000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ed800000 (32-bit, non-prefetchable)
[size=512K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:06.0 Multimedia audio controller: nVidia Corporation nForce
Audio (rev c2)
Subsystem: nVidia Corporation: Unknown device 8384
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e100 [size=256]
Region 1: I/O ports at e000 [size=128]
Region 2: Memory at ed000000 (32-bit, non-prefetchable)
[disabled] [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge
(rev c2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: ec800000-ecffffff
Prefetchable memory behind bridge: f8000000-f7ffffff
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-

00:09.0 IDE interface: nVidia Corporation nForce IDE (rev c3)
(prog-if 8a [Master SecP PriP])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Region 4: I/O ports at a800 [size=16]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge
(rev b2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000a000-00009fff
Memory behind bridge: eb000000-ec7fffff
Prefetchable memory behind bridge: eff00000-f7ffffff
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

01:08.0 Communication controller: Rockwell International HCF 56k
Data/Fax/Voice/Spkp (w/Handset) Modem (rev 01)
Subsystem: Rockwell International HCF 56k Data/Fax/Voice/Spkp
(w/Handset) Modem
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ec800000 (32-bit, non-prefetchable)
[size=64K]
Region 1: I/O ports at b800 [size=8]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable+ DSel=0 DScale=0 PME-

02:00.0 VGA compatible controller: nVidia Corporation NV15
[GeForce2 - nForce GPU] (rev b1) (prog-if 00 [VGA])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at eb000000 (32-bit, non-prefetchable)
[size=16M]
Region 1: Memory at f0000000 (32-bit, prefetchable)
[size=128M]
Expansion ROM at efff0000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 2.0
Status: RQ=31 SBA- 64bit- FW+ Rate=x1,x4
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>



XF86Config:

# File generated by anaconda.

Section "ServerLayout"
Identifier "Anaconda Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# The location of the RGB database. Note, this is the name of
the
# file minus the extension (like ".txt" or ".db"). There is
normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (they are concatenated
together)
# By default, Red Hat 6.0 and later now use a font server
independent of
# the X server to render fonts.

FontPath "unix/:7100"

EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "dri"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"

# Option "AutoRepeat" "500 5"

# when using XQUEUE, comment out the above line, and uncomment
the
# following line
# Option "Protocol" "Xqueue"

# Specify which keyboard LEDs can be user-controlled (eg, with
xset(1))
# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify
the
# lines below (which are the defaults). For example, for a
non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
#Option "XkbVariant" ""
#Option "XkbOptions" ""
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection


Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection


Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-55
VertRefresh 50-120
Option "dpms"


EndSection

Section "Device"
# no known options
Identifier "NVIDIA GeForce 2 MX (generic)"
Driver "nv"
VendorName "NVIDIA GeForce 2 MX (generic)"
BoardName "NVIDIA GeForce 2 MX (generic)"

#BusID
EndSection

Section "Screen"
Identifier "Screen0"
Device "NVIDIA GeForce 2 MX (generic)"
Monitor "Monitor0"
DefaultDepth 16

Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

Section "DRI"
Mode 0666
EndSection

cmdline:
auto BOOT_IMAGE=linux ro BOOT_FILE=/boot/vmlinuz-2.4.18-14
root=LABEL=/


dma:
4: cascade


intrrupts:
CPU0
0: 337647 XT-PIC timer
1: 2694 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC usb-ohci, usb-ohci
8: 1 XT-PIC rtc
12: 20 XT-PIC PS/2 Mouse
14: 27338 XT-PIC ide0
NMI: 0
ERR: 2


partitions:
major minor #blocks name rio rmerge rsect ruse wio wmerge
wsect wuse running use aveq

3 0 39121488 hda 2567 4181 52107 22201 1417 1941 26952
45880 -2 329576 7788488
3 1 5245191 hda1 9 43 104 109 0 0 0 0 0 109 109
3 2 1 hda2 0 0 0 0 0 0 0 0 0 0 0
3 5 10490413 hda5 9 43 104 95 0 0 0 0 0 95 95
3 6 11695288 hda6 50 43 145 214 7 1 8 95 0 230 310
3 7 8104761 hda7 9 43 104 132 0 0 0 0 0 132 132
3 8 3277228 hda8 2475 3966 51498 21527 1410 1940 26944
45785 0 22394 67314
3 9 305203 hda9 9 25 104 56 0 0 0 0 0 56 56



My e-mail addresses are: ***@yahoo.com and
***@rediff.com
My postel address: 80, Ahilya Nagar Ext. Annapurna Road, Indore,
M.P.,
India. PIN 452009
please answer me soon.
Thanking you.
Saurabh Khanna.
Alexander Kellett
2003-02-03 12:53:52 UTC
Permalink
hiya,

unfortunately this list isn't for such problems and it
would be better to contact your distribution or the various
forums it has. try google.

/me wonders again why this list isn't called linux-kernel-***@...

Alex
Post by saurabh khanna
Problem: My xwindows did not open and my sound card don't work.
I am a novice. I am using redhat linux 8. It detects my graphics
card
correctly but when i tried to open xwindows, my system hangs.
Linux has detected my sound card once but not configured it and
after
that nor it is working nither it is detected by my linux.
Also, i can boot my linux through LILO only. GRUB wont work, it
gives
error "Not enough memory".
I have re-installed linux on my computer but the problem
remains.
All other detailes are follows.
(gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7))
#1 Wed Sep 4 12:13:11 EDT 2002
startx
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(TM) XP 1700+
stepping : 2
cpu MHz : 1469.861
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 2920.57
nls_iso8859-1 3516 1 (autoclean)
nls_cp437 5116 1 (autoclean)
vfat 13084 1 (autoclean)
fat 38744 0 (autoclean)
[vfat]
autofs 13348 0 (autoclean) (unused)
ipt_REJECT 3736 2 (autoclean)
iptable_filter 2412 1 (autoclean)
ip_tables 14840 2 [ipt_REJECT iptable_filter]
mousedev 5524 0 (unused)
keybdev 2976 0 (unused)
hid 22244 0 (unused)
input 5888 0 [mousedev keybdev hid]
usb-ohci 21288 0 (unused)
usbcore 77056 1 [hid usb-ohci]
ext3 70400 1
jbd 52212 1 [ext3]
0000-001f : dma
1
0020-003f : pic
1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic
2
00c0-00df : dma
2
00f0-00ff : fpu
01f0-01f7 : ide
0
02f8-02ff : serial(auto)
03c0-03df : vga+
03f6-03f6 : ide
0
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf
1
5000-500f : PCI device 10de:01b4 (nVidia Corporation)
5100-511f : PCI device 10de:01b4 (nVidia Corporation)
5500-550f : PCI device 10de:01b4 (nVidia Corporation)
a800-a80f : nVidia Corporation nForce IDE
a800-a807 : ide0
a808-a80f : ide1
b000-bfff : PCI Bus #01
b800-b807 : Rockwell International HCF 56k Data/Fax/Voice/Spkp
(w/Handset) Modem
d800-d807 : PCI device 10de:01c3 (nVidia Corporation)
e000-e07f : PCI device 10de:01b1 (nVidia Corporation)
e100-e1ff : PCI device 10de:01b1 (nVidia Corporation)
00000000-0007ffff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-06febfff : System RAM
00100000-00247f2e : Kernel code
00247f2f-0033ed03 : Kernel data
06fec000-06feefff : ACPI Tables
06fef000-06ffefff : reserved
06fff000-06ffffff : ACPI Non-volatile Storage
eb000000-ec7fffff : PCI Bus #02
eb000000-ebffffff : nVidia Corporation GeForce2 Integrated GPU
ec800000-ecffffff : PCI Bus #01
ec800000-ec80ffff : Rockwell International HCF 56k
Data/Fax/Voice/Spkp (w/Handset) Modem
ed000000-ed000fff : PCI device 10de:01b1 (nVidia Corporation)
ed800000-ed87ffff : PCI device 10de:01b0 (nVidia Corporation)
ee000000-ee0003ff : PCI device 10de:01c3 (nVidia Corporation)
ee800000-ee800fff : PCI device 10de:01c2 (nVidia Corporation)
ee800000-ee800fff : usb-ohci
e
f000000-ef000fff : PCI device
10de:01c2 (nVidia Corporation)
ef000000-ef000fff : usb-ohci
e
ff00000-f7ffffff : PCI Bus #02
f0000000-f7ffffff : nVidia Corporation GeForce2 Integrated GPU
f8000000-fbffffff : PCI device
10de:01a4 (nVidia Corporation)
fec00000-fec00fff : reserved
fee00000-fee00fff : reserved
ffff0000-ffffffff : reserved
00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev
b2)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [40] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2,x4
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=x1
Capabilities: [60] #08 [2001]
00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory
Controller (rev b2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory
Controller (rev b2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
00:00.3 RAM memory: nVidia Corporation: Unknown device 01aa (rev
b2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev
c3)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [50] #08 [01e1]
00:01.1 SMBus: nVidia Corporation nForce PCI System Management
(rev c1)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at 5000 [size=16]
Region 1: I/O ports at 5500 [size=16]
Region 2: I/O ports at 5100 [size=32]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:02.0 USB Controller: nVidia Corporation: Unknown device 01c2
(rev c3) (prog-if 10 [OHCI])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ef000000 (32-bit, non-prefetchable)
[size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:03.0 USB Controller: nVidia Corporation: Unknown device 01c2
(rev c3) (prog-if 10 [OHCI])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ee800000 (32-bit, non-prefetchable)
[size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:04.0 Ethernet controller: nVidia Corporation: Unknown device
01c3 (rev c2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ee000000 (32-bit, non-prefetchable)
[size=1K]
Region 1: I/O ports at d800 [size=8]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:05.0 Multimedia audio controller: nVidia Corporation: Unknown
device 01b0 (rev c2)
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (250ns min, 3000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ed800000 (32-bit, non-prefetchable)
[size=512K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:06.0 Multimedia audio controller: nVidia Corporation nForce
Audio (rev c2)
Subsystem: nVidia Corporation: Unknown device 8384
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e100 [size=256]
Region 1: I/O ports at e000 [size=128]
Region 2: Memory at ed000000 (32-bit, non-prefetchable)
[disabled] [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge
(rev c2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: ec800000-ecffffff
Prefetchable memory behind bridge: f8000000-f7ffffff
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
00:09.0 IDE interface: nVidia Corporation nForce IDE (rev c3)
(prog-if 8a [Master SecP PriP])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Region 4: I/O ports at a800 [size=16]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge
(rev b2) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000a000-00009fff
Memory behind bridge: eb000000-ec7fffff
Prefetchable memory behind bridge: eff00000-f7ffffff
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
01:08.0 Communication controller: Rockwell International HCF 56k
Data/Fax/Voice/Spkp (w/Handset) Modem (rev 01)
Subsystem: Rockwell International HCF 56k Data/Fax/Voice/Spkp
(w/Handset) Modem
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 5
Region 0: Memory at ec800000 (32-bit, non-prefetchable)
[size=64K]
Region 1: I/O ports at b800 [size=8]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
02:00.0 VGA compatible controller: nVidia Corporation NV15
[GeForce2 - nForce GPU] (rev b1) (prog-if 00 [VGA])
Subsystem: nVidia Corporation: Unknown device 0c11
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at eb000000 (32-bit, non-prefetchable)
[size=16M]
Region 1: Memory at f0000000 (32-bit, prefetchable)
[size=128M]
Expansion ROM at efff0000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 2.0
Status: RQ=31 SBA- 64bit- FW+ Rate=x1,x4
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
# File generated by anaconda.
Section "ServerLayout"
Identifier "Anaconda Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of
the
# file minus the extension (like ".txt" or ".db"). There is
normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated
together)
# By default, Red Hat 6.0 and later now use a font server
independent of
# the X server to render fonts.
FontPath "unix/:7100"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "dri"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
# Option "AutoRepeat" "500 5"
# when using XQUEUE, comment out the above line, and uncomment
the
# following line
# Option "Protocol" "Xqueue"
# Specify which keyboard LEDs can be user-controlled (eg, with
xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify
the
# lines below (which are the defaults). For example, for a
non-U.S.
# Option "XkbModel" "pc102"
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# Option "XkbLayout" "de"
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# Option "XkbOptions" "ctrl:swapcaps"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
#Option "XkbVariant" ""
#Option "XkbOptions" ""
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-55
VertRefresh 50-120
Option "dpms"
EndSection
Section "Device"
# no known options
Identifier "NVIDIA GeForce 2 MX (generic)"
Driver "nv"
VendorName "NVIDIA GeForce 2 MX (generic)"
BoardName "NVIDIA GeForce 2 MX (generic)"
#BusID
EndSection
Section "Screen"
Identifier "Screen0"
Device "NVIDIA GeForce 2 MX (generic)"
Monitor "Monitor0"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
EndSection
Section "DRI"
Mode 0666
EndSection
auto BOOT_IMAGE=linux ro BOOT_FILE=/boot/vmlinuz-2.4.18-14
root=LABEL=/
4: cascade
CPU0
0: 337647 XT-PIC timer
1: 2694 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC usb-ohci, usb-ohci
8: 1 XT-PIC rtc
12: 20 XT-PIC PS/2 Mouse
14: 27338 XT-PIC ide0
NMI: 0
ERR: 2
major minor #blocks name rio rmerge rsect ruse wio wmerge
wsect wuse running use aveq
3 0 39121488 hda 2567 4181 52107 22201 1417 1941 26952
45880 -2 329576 7788488
3 1 5245191 hda1 9 43 104 109 0 0 0 0 0 109 109
3 2 1 hda2 0 0 0 0 0 0 0 0 0 0 0
3 5 10490413 hda5 9 43 104 95 0 0 0 0 0 95 95
3 6 11695288 hda6 50 43 145 214 7 1 8 95 0 230 310
3 7 8104761 hda7 9 43 104 132 0 0 0 0 0 132 132
3 8 3277228 hda8 2475 3966 51498 21527 1410 1940 26944
45785 0 22394 67314
3 9 305203 hda9 9 25 104 56 0 0 0 0 0 56 56
My postel address: 80, Ahilya Nagar Ext. Annapurna Road, Indore,
M.P.,
India. PIN 452009
please answer me soon.
Thanking you.
Saurabh Khanna.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
mvg,
Alex
--
"[...] Konqueror open source project. Weighing in at less than
one tenth the size of another open source renderer"
Apple, Jan 2003 (http://www.apple.com/safari/)
seth
2003-02-04 05:44:23 UTC
Permalink
subscribe linux-kernel
Frank Davis
2003-02-07 17:05:28 UTC
Permalink
Hello all,
The following patch addresses buzilla bug # 312, and removes an
offending semicolon. Please review for inclusion.

Regards,
Frank

--- linux/drivers/net/tokenring/smctr.c.old 2003-01-16 21:22:09.000000000 -0500
+++ linux/drivers/net/tokenring/smctr.c 2003-02-07 03:10:50.000000000 -0500
@@ -3064,7 +3064,7 @@
__u8 r;

/* Check if node address has been specified by user. (non-0) */
- for(i = 0; ((i < 6) && (dev->dev_addr[i] == 0)); i++);
+ for(i = 0; ((i < 6) && (dev->dev_addr[i] == 0)); i++)
{
if(i != 6)
{
Rusty Russell
2003-02-10 00:20:02 UTC
Permalink
Post by Frank Davis
Hello all,
The following patch addresses buzilla bug # 312, and removes an
offending semicolon. Please review for inclusion.
Regards,
Frank
--- linux/drivers/net/tokenring/smctr.c.old 2003-01-16 21:22:09.000000000 -
0500
Post by Frank Davis
+++ linux/drivers/net/tokenring/smctr.c 2003-02-07 03:10:50.000000000 -
0500
Post by Frank Davis
@@ -3064,7 +3064,7 @@
__u8 r;
/* Check if node address has been specified by user. (non-0) */
- for(i = 0; ((i < 6) && (dev->dev_addr[i] == 0)); i++);
+ for(i = 0; ((i < 6) && (dev->dev_addr[i] == 0)); i++)
{
if(i != 6)
{
NAK, I believe this is the way the code is supposed to work.

Of course, opening a new block after the for is completely gratuitous
and designed to fool the reader.

Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
torsten
2003-02-10 23:38:41 UTC
Permalink
unsubscribe
b***@themail.com
2003-02-12 13:55:57 UTC
Permalink
om,***@ccs.covici.com,***@lycos.com,***@mx4.mail.lycos.com,***@lycos.com,***@uwo.ca,***@uwo.ca,***@uwo.ca,***@frru.utcru.sk,***@ns.telnet.sk,***@ahoj.sk,***@ns.telnet.sk,***@pop.sao.terra.com.br,***@ns.telnet.sk,***@twister.nyc.rr.com,***@mail.alinoe.com,***@netscape.net,15622.65368.231099.881374@
cc,***@mail.alinoe.com,***@alinoe.com,***@alinoe.com,***@alinoe.com,***@mail.alinoe.com,***@111.ac,***@alinoe.com,***@alinoe.com
From: ***@themail.com
Subject: DO YOU GET MY MAIL?
X-Priority: 3
Authorized-User: ***@themail.com
IP-Address: 66.178.47.93
Reply-To: ***@themail.com
MIME-Version: 1.0
Content-type: text/plain
Message-Id: <***@mail.TheMail.com>
Date: Wed, 12 Feb 2003 09:13:55 -0500

Dear Sir ,
My name is Mr. Fudah Sanko the rebel leader in Sierra-Leone. You might have heard my problems with the Sierra-Leone present regime.
If you wish to hear more, you can listen to BBC network Africa that is where you can follow my case up with Justice Harmoty who is planning to condemn me during the finalprosecution or trial. Our problem in Africa is that no President will like to relinquish power to another person of another party unless by violence or struggle which must emenate forcefully.
I arranged with my wife and wrote this mail during her visit to me with a small laptop computer. My wife got your contact through the GOOGLE website and brought it to me, after reading your profile she chooses you. Incase government decide to kill me, please for further existence of my family, I kept the sum of$20.5m which I intend to use for importation of arms and ammunitions, also I kept some reasonable quantity of diamond in safe place which my LAWYER know about it before my problem arises.Presently, my LAWYER is in position of the fund and
diamond, also i told him not to keep this morney with our family
name,for security reasons. As a matter of urgency contact him on his e-mail address: ***@lawyer.com OR ***@mail.co.za arrange with him on how you will receive the fund and invest it in your
country for further existence of my family.
Please make sure you give my son resident permit in your country. My son may like to move with my wife if they kill me. Don't fail to help my family for God sake. For your information, the fund has moved out of Sierra-Leone for security reasons.Contact my LAWYER for immediate actions. My LAWYER'S name is Mr. DAVID NKOSI.my son email address
is:***@email.it


Best regards,


Mr. Fudah Sanko

__________________________________________________________________
TheMail.com - Full featured premium email you can count on.
Sign-up today at http://www.themail.com/
Liu, Yanqing
2003-02-12 15:43:47 UTC
Permalink
Here's a question about SCSI driver module loading.

There's Qlogic2200 HBA inserted in my machine.
I want to establish some dependency relationship between qlogic driver and
my SCSI driver (like scsi_debug) so that they can be loaded/unloaded
together. Basically, I want my SCSI driver (say, scsi_debug) loaded after
sd/sg driver and before all other low level SCSI HBA drivers(like qla
driver). In modules.conf file, I added

alias scsi_hostadapter qla2200

add above scsi_hostadapter scsi_debug

I didn't make initrd since the Qlogic driver is not essential to the system
boot.

Anyway, Qlogic driver is loaded, but scsi_debug is not.

In the shell, if I type
modprobe scsi_hostadapter
it will load scsi_debug module.
If I type
modprobe qla2200,
it will not. (Why??)

And, if I modified modules.conf like the following:

alias scsi_hostadapter qla2200

add above qla2200 scsi_debug

Kernel will panic!

My questions are:

1. When and how ia the alogic driver loaded in boot time (my machine has the
qlogic card).

2. How can I modify modules.conf (or possibly other way, e.g. rc script or
depmod) so that I can establish some dependency relationship between qlogic
driver and other SCSI drivers so that they can be loaded/unloaded together?

3. Do I need to load qlogic driver and my scsi_debug with initrd?

Thanks.

Yanqing
Neil Brown
2003-02-15 01:53:53 UTC
Permalink
Subject: Re: Routing problem with udp, and a multihomed host in 2.4.20
In-Reply-To: message from Herbert Xu on Saturday February 15
References: <***@notabene.cse.unsw.edu.au>
<E18jpaa-0007Rc-***@gondolin.me.apana.org.au>
X-Mailer: VM 7.07 under Emacs 20.7.2
FCC: ~/.mail/linux
X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D<ml'fY1Vw+@XfR[fRCsUoP?K6bt3YD\ui5Fh?f
LONpR';(ql)VM_TQ/<l_^D3~B:z$\YC7gUCuC=sYm/80G=$tt"98mr8(l))QzVKCk$6~gldn~*FK9x
8`;pM{3S8679sP+MbP,72<3_PIH-$I&iaiIb|hV1d%cYg))BmI)AZ
--text follows this line--
It turns out that the problem occurs when send_msg is used to send a
UDP packet, and the control information contains
struct in_pktinfo {
unsigned int ipi_ifindex; /* Interface index */
struct in_addr ipi_spec_dst; /* Local address */
struct in_addr ipi_addr; /* Header Destination address */
};
specifying the address and interface of the message that we are
replying to.
So your application is forcing the packet to go out on a specific
interface bypassing the routing table...
No.
My application (which is just using standard rpc server libraries) is
saying
"This is in reply to a request that came in through a given
interface".

It is not reasonable to treat that statement as equivalent to:
"This packet must go out that interface"

which is what appears to be happening.

NeilBrown
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
David S. Miller
2003-02-18 07:10:37 UTC
Permalink
Post by Neil Brown
No.
My application (which is just using standard rpc server libraries) is
saying
"This is in reply to a request that came in through a given
interface".
"This packet must go out that interface"
which is what appears to be happening.
You misunderstand what this control message knob means during
a sendmsg() then, it means "send this over interface X"

There is no other valid expectation.

I'm curious where you read something that would suggest otherwise
for sendmsg() behavior wrt. ip_pktinfo
Neil Brown
2003-02-18 11:00:37 UTC
Permalink
Post by David S. Miller
Post by Neil Brown
No.
My application (which is just using standard rpc server libraries) is
saying
"This is in reply to a request that came in through a given
interface".
"This packet must go out that interface"
which is what appears to be happening.
You misunderstand what this control message knob means during
a sendmsg() then, it means "send this over interface X"
There is no other valid expectation.
I'm curious where you read something that would suggest otherwise
for sendmsg() behavior wrt. ip_pktinfo
man 7 ip

on debian (unstable).

I quote:

IP_PKTINFO
Pass an IP_PKTINFO ancillary message that contains a pktinfo
structure that supplies some information about the incoming
packet. This only works for datagram oriented sockets. The
argument is a flag that tells the socket whether the IP_PKTINFO
message should be passed or not. The message itself can only be
sent/retrieved as control message with a packet using recvmsg(2)
or sendmsg(2).

struct in_pktinfo {
unsigned int ipi_ifindex; /* Interface index */
struct in_addr ipi_spec_dst; /* Local address */
struct in_addr ipi_addr; /* Header Destination address */
};

ipi_ifindex is the unique index of the interface the packet was
received on. ipi_spec_dst is the local address of the packet
and ipi_addr is the destination address in the packet header.
If IP_PKTINFO is passed to sendmsg(2) then the outgoing packet
will be sent over the interface specified in ipi_ifindex with
the destination address set to ipi_spec_dst


Note that the in_pktinfo is described as "some information about the
incoming packet". In particular ipi_ifindex is "the unique index of
the interface the packets was received on".

i.e. it is more about the incoming than the outgoing packet.

It does go on to say that the outgoing packet will be sent over the
same interface, however I feel that is an illogical conclusion given
the description of the meaning of the field.

So yes, the current behaviour seems to match part of the
documentation. However I argue that the documented behaviour is
irrational.
A more rational behaviour is
"the outgoing packet will be sent over the interface specified in
ipi_ifindex if that interface has a valid route to the packets
destination. Otherwise normal rouing rules apply".

I further argue that this is not only more rational, but is actually
more useful (which is a more telling point).

NeilBrown
k***@ms2.inr.ac.ru
2003-02-18 16:06:34 UTC
Permalink
Hello!
Post by Neil Brown
So yes, the current behaviour seems to match part of the
documentation.
Good. :-)
Post by Neil Brown
"the outgoing packet will be sent over the interface specified in
ipi_ifindex if that interface has a valid route to the packets
destination. Otherwise normal rouing rules apply".
I further argue that this is not only more rational, but is actually
more useful (which is a more telling point).
Either you rely on routing tables, or you do not, which is used
when routing tables are still not set up, or setup ambiguously,
or use of them just do not make sense which happens for multicasts/
limited/broadcasts/link local addresses. It is the thing which ifi_ifindex
does.

I do no see how it is possible to classify a middle way as "rational".
Well, and frankly speaking I do not see how it could be useful.

Alexey
Neil Brown
2003-02-18 23:35:14 UTC
Permalink
Post by k***@ms2.inr.ac.ru
Hello!
Post by Neil Brown
So yes, the current behaviour seems to match part of the
documentation.
Good. :-)
Post by Neil Brown
"the outgoing packet will be sent over the interface specified in
ipi_ifindex if that interface has a valid route to the packets
destination. Otherwise normal rouing rules apply".
I further argue that this is not only more rational, but is actually
more useful (which is a more telling point).
Either you rely on routing tables, or you do not, which is used
when routing tables are still not set up, or setup ambiguously,
or use of them just do not make sense which happens for multicasts/
limited/broadcasts/link local addresses. It is the thing which ifi_ifindex
does.
Presumably in these "don't rely on routing" cases the application
would set SO_DONTROUTE or MSG_DONTROUTE.
If this flag were set, I wouldn't argue with insisting that the
message goes out the interface specified in ifi_ifindex.

But if not, what then...

There remains the fact that the only documentation I can find about
this(*) describes ifi_ifindex as the interface that a message
*arrived* on, and when specified in a sendmsg call, it is information
about the message that we are replying to. Interpreting this to mean
that the reply *must* go out that interface still seems wrong to me.

Do you agree which that definition of IP_PKTINFO? If not, can you
show me some documentation which supports your position?

(*) I looked in the Single Unix Specification and it doesn't mention
PKTINFO at all. I looked in the RFC's mentioned at the bottom of
"man 7 ip"
(RPC1122 and 1812) and they don't say anything about specifying an
interface for outgoing messages - only specifying a source address.
Post by k***@ms2.inr.ac.ru
I do no see how it is possible to classify a middle way as "rational".
Well, and frankly speaking I do not see how it could be useful.
The "middle way" is that we do want to rely on routing tables (as we
have not set MSG_DONTROUTE) but that the routing tables do not give a
unique route to some addresses - as is certainly possible and even
encouraged by RFC1122 (end of discussion of Strong ES model in
section 3.3.4.2).

With reliable routing that provides multiple routes in some cases, it
seems reasonable, even rational, to accept hints from the application
as to which interface to use.

As for "useful", it is more that I cannot see how the current
behaviour is useful - i.e. how can be used meaningfully by an
application.

The particular behaviour is:
If MSG_DONTROUTE is not set, but a non-zero ifi_ifindex is given
then:
If there is a known route to the destination address through that
interface, then use that route.
If there is no route through that interface to the destination
address, then treat it as a link-local address.

When would an application actually want that behaviour?

My current approach to 'fixing' what I perceive as the 'problem' would
be one of:

1/ if no route is found out the interface, return ENETUNREACH (not
that ENETUNREACH is listed in the man page for sendmsg :-( )
Also change to documentation to make the intent more explicit.
This would make my current problem clearly an application error and
I could take it to the maintainers of glibc.

2/ If MSG_DONTROUTE is not set, then ignore the value passed in
ifi_ifindex.
This would slightly weaken the applications options for
controlling routing, but I don't think the weakening would be
significant.

3/ Treat the ifi_ifindex as a hint if MSG_DONTROUTE isn't set. This
would be much more invasive to the code, and it is not clear that
the extra control it provides is needed in practice.


Thank you for your frankness,

NeilBrown
David S. Miller
2003-02-18 23:56:51 UTC
Permalink
All you are showing us Neil is that the documentation
is inaccurate. That snippet you showed me from manual
pages is wrong about sendmsg semantics.

The ifindex you specify does mean "send out this interface".

It is very surprising that this documentation is wrong since
the likely author (Andi Kleen) is smart enough to read the
actual implementation when he writes these things.

And yes, this means, no accurate documentation exists currently.
David S. Miller
2003-02-19 03:52:05 UTC
Permalink
From: Neil Brown <***@cse.unsw.edu.au>
Date: Tue, 18 Feb 2003 22:00:37 +1100

It does go on to say that the outgoing packet will be sent over the
same interface, however I feel that is an illogical conclusion given
the description of the meaning of the field.

So yes, the current behaviour seems to match part of the
documentation. However I argue that the documented behaviour is
irrational.

Alexey and myself totally disagree. We have described for you
the intended purpose of this feature. Please do not try to use
it in some other way, it may prove to be painful :-)
Neil Brown
2003-02-19 04:13:48 UTC
Permalink
Post by David S. Miller
Date: Tue, 18 Feb 2003 22:00:37 +1100
It does go on to say that the outgoing packet will be sent over the
same interface, however I feel that is an illogical conclusion given
the description of the meaning of the field.
So yes, the current behaviour seems to match part of the
documentation. However I argue that the documented behaviour is
irrational.
Alexey and myself totally disagree. We have described for you
the intended purpose of this feature. Please do not try to use
it in some other way, it may prove to be painful :-)
Thankyou for making that clear.

I am currently working towards testing a patch that will fix the
behaviour of glibc.

Currently the sunrpc/svc_udp.c code asks for an IP_PKTINFO from
recvmsg, and passes it verbatim down through sendmsg.
My patch checks that the returned data looks believable and, if it
does, zeros the ipi_ifindex field.

NeilBrown



--- sunrpc/svc_udp.c.orig 2003-02-19 11:25:20.000000000 +1100
+++ sunrpc/svc_udp.c 2003-02-19 14:28:46.000000000 +1100
@@ -256,8 +256,26 @@
mesgp->msg_controllen = sizeof(xprt->xp_pad)
- sizeof (struct iovec) - sizeof (struct msghdr);
rlen = recvmsg (xprt->xp_sock, mesgp, 0);
- if (rlen >= 0)
- len = mesgp->msg_namelen;
+ if (rlen >= 0) {
+ struct cmsghdr *cmsg;
+ len = mesgp->msg_namelen;
+ cmsg = CMSG_FIRSTHDR(mesgp);
+ if (cmsg == NULL ||
+ CMSG_NXTHDR(mesgp, cmsg) != NULL ||
+ cmsg->cmsg_level != SOL_IP ||
+ cmsg->cmsg_type != IP_PKTINFO ||
+ cmsg->cmsg_len != sizeof(struct in_pktinfo)) {
+ /* Not a simple IP_PKTINFO, ignore it */
+ mesgp->msg_control = NULL;
+ mesgp->msg_controllen = 0;
+ } else {
+ /* it was a simple IP_PKTIFO as we expected,
+ * Discard the interface field
+ */
+ struct in_pktinfo *pkti = CMSG_DATA(cmsg);
+ pkti->ipi_ifindex = 0;
+ }
+ }
}
else
#endif
David S. Miller
2003-02-19 04:03:53 UTC
Permalink
From: Neil Brown <***@cse.unsw.edu.au>
Date: Wed, 19 Feb 2003 15:13:48 +1100
Post by David S. Miller
Alexey and myself totally disagree. We have described for you
the intended purpose of this feature. Please do not try to use
it in some other way, it may prove to be painful :-)
Thankyou for making that clear.

You're very welcome, thank you for tracking all of this down.

Currently the sunrpc/svc_udp.c code asks for an IP_PKTINFO from
recvmsg, and passes it verbatim down through sendmsg.

And yes, this is buggy.

My patch checks that the returned data looks believable and, if it
does, zeros the ipi_ifindex field.

Please note also that ipi_addr is ignored on sendmsg().

You don't have to zero it, this is just a reminder about
what the kernel will do with this thing.
Julian Anastasov
2003-02-18 19:57:01 UTC
Permalink
Hello,
Post by Neil Brown
Note that the in_pktinfo is described as "some information about the
incoming packet". In particular ipi_ifindex is "the unique index of
the interface the packets was received on".
i.e. it is more about the incoming than the outgoing packet.
Yes, because when set as socket option you can receive
pktinfo with recvmsg. But IP_PKTINFO can be used also with sendmsg.
Just forget about interfaces, i.e. use something like this in cmsg:

.ipi = {
.ipi_ifindex = 0,
.ipi_spec_dst = local_ip,
},

Such code is needed when your UDP socket is not
connected (preferred) nor bound (with bind). In such case
it is essential to provide sendmsg with the local IP address
used for proper routing. Playing with interfaces should be
avoided if possible. If is a common error UDP users not to
provide the routing with local IP address.

Regards

--
Julian Anastasov <***@ssi.bg>
Neil Brown
2003-02-18 23:39:22 UTC
Permalink
Post by Julian Anastasov
Hello,
Post by Neil Brown
Note that the in_pktinfo is described as "some information about the
incoming packet". In particular ipi_ifindex is "the unique index of
the interface the packets was received on".
i.e. it is more about the incoming than the outgoing packet.
Yes, because when set as socket option you can receive
pktinfo with recvmsg. But IP_PKTINFO can be used also with sendmsg.
.ipi = {
.ipi_ifindex = 0,
.ipi_spec_dst = local_ip,
},
Certainly IP_PKTINFO can be used with sendmsg. The doesn't change the
fact that the documentation clearly says that the information is
information about an incoming packet.

Also, th only documentation I can find does not specify that a value
of 0 means "no specific interface is selected". So while I can see
from the code that what you suggest would work in practice, it would
be nice if this were clearly documented somewhere.

NeilBrown
Andi Kleen
2003-02-19 08:17:58 UTC
Permalink
Post by David S. Miller
All you are showing us Neil is that the documentation
is inaccurate. That snippet you showed me from manual
pages is wrong about sendmsg semantics.
Yes, it's wrong I agree. Here is a patch. Please check
and if nobody complains Andries can apply.
Post by David S. Miller
The ifindex you specify does mean "send out this interface".
It is very surprising that this documentation is wrong since
the likely author (Andi Kleen) is smart enough to read the
actual implementation when he writes these things.
There was no serious technical review of these manpages ever, so
I wouldn't be surprised if there are more such technical errors (hint ;)

-Andi

--- ip.7~ 2003-02-19 08:50:48.000000000 +0100
+++ ip.7 2003-02-19 09:09:36.000000000 +0100
@@ -260,12 +260,16 @@
.I IP_PKTINFO
is passed to
.BR sendmsg (2)
-then the outgoing packet will be sent over the interface
-specified in
-.B ipi_ifindex
-with the destination address set to
+and
+.\" This field is grossly misnamed
.B ipi_spec_dst
-.
+is not zero then it is used as the local source address for the routing
+table lookup and for setting up IP source route options.
+When
+.B ipi_ifindex
+is not zero the primary local address of the interface specified by the index overwrites
+.I ipi_spec_dst
+for the routing table lookup.

.TP
.B IP_RECVTOS
David S. Miller
2003-02-19 08:06:24 UTC
Permalink
From: Andi Kleen <***@suse.de>
Date: 19 Feb 2003 09:17:58 +0100

Here is a patch. Please check
and if nobody complains Andries can apply.

Looks good.
Neil Brown
2003-02-21 03:51:07 UTC
Permalink
Post by Andi Kleen
Post by David S. Miller
All you are showing us Neil is that the documentation
is inaccurate. That snippet you showed me from manual
pages is wrong about sendmsg semantics.
Yes, it's wrong I agree. Here is a patch. Please check
and if nobody complains Andries can apply.
Thanks. This helps, but I was imagining something a bit
wider-ranging. In particular I though a "Control Messages" section
would be nice, which enumerated separately all the control messages
that can be recieved, and all those that can be sent.

As far as I can tell, control message are currently defined for:
IPv4,
IPv6,
SOL_HCI - some bluetooth thing
SOL_SOCKET (which don't seem to be clearly documented in socket(7))

I might try and draft some changes to ip.7 and maybe socket.7 next
week sometime.

NeilBrown
David S. Miller
2003-02-21 04:17:49 UTC
Permalink
From: Neil Brown <***@cse.unsw.edu.au>
Date: Fri, 21 Feb 2003 14:51:07 +1100

As far as I can tell, control message are currently defined for:
IPv4,
IPv6,
SOL_HCI - some bluetooth thing
SOL_SOCKET (which don't seem to be clearly documented in socket(7))

Also, control messages are used for AF_UNIX to pass file descriptors
around.
patrizio
2003-02-21 03:41:18 UTC
Permalink
unsubstribe linux-kernel
News Admin
2003-02-21 13:43:29 UTC
Permalink
From news Fri Feb 21 14:43:28 2003
Received: (from ***@localhost)
by nimloth.ics.muni.cz (8.11.6+Sun/8.10.0.Beta12) id h1LDhSm13508
for newsmaster; Fri, 21 Feb 2003 14:43:28 +0100 (MET)
Newsgroups: cz.muni.redir.linux-kernel
Path: news
From: Zdenek Kabelac <***@i.am>
Subject: SMP kernel 2.4 and gcc-3.2
Message-ID: <***@i.am>
Sender: ***@decibel.fi.muni.cz
Date: Fri, 21 Feb 2003 13:43:24 GMT
X-Nntp-Posting-Host: decibel.fi.muni.cz
Content-Transfer-Encoding: 7bit
X-Accept-Language: cs, en
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.19-rc3-ac3 i686)
Organization: unknown

Hello

As I've so far not noticed any such post - maybe it's just me.

But I simply can not build usable SMP 2.4.2x kernel
with gcc-3.2

Whenever I use gcc-3.2 - the compiled kernel just immediately
reboots machine - Exactly the same kernel with same configuration
compiled with gcc-2.95 works normaly.
The box is Abit BP6/256MB Ram/Matrox G400 with 2xCelerons

I've just seen slightly different behavior with various
versions - sometime it just locked the box (i.e. GRUB screen
has stayed on the screen and I had to press 'reset' button
myself)

Ok - what should I do to help fix this problem - as I've said
I've tried various configuration - I don't think there
is something special in there (http://www.fi.muni.cz/~kabi/.config)

$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.3/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared
--with-system-zlib --enable-nls --without-included-gettext
--enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm
--enable-objc-gc i386-linux
Thread model: posix
gcc version 3.2.3 20030210 (Debian prerelease)


please Cc: me
--
.''`.
: :' : Zdenek Kabelac kabi@{debian.org, users.sf.net, fi.muni.cz}
`. `' Debian GNU/Linux maintainer - www.debian.{org,cz}
`-
Alan Cox
2003-02-21 15:01:46 UTC
Permalink
Post by News Admin
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.3/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared
--with-system-zlib --enable-nls --without-included-gettext
--enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm
--enable-objc-gc i386-linux
Thread model: posix
gcc version 3.2.3 20030210 (Debian prerelease)
How about using a released gcc compiler not a snapshot. gcc 3.2.1
and 3.2.2 appear to work fine. According to the FSF there is no
gcc 3.2.3 yet, so it isn't suprising a snapshot would have bugs
b***@softhome.net
2003-02-21 21:13:32 UTC
Permalink
subscribe
b***@softhome.net
2003-02-21 21:29:59 UTC
Permalink
subscribe linux-kernel

Continue reading on narkive:
Loading...