اين راهشه ديگه
شايد در نظر اول كمي سخت باشه
مثلا شما سورس يه كرنل رو از kernel.orgدانلود كنيد و نصبش كنيد
هم مشكلتون حل مي شه و هم يه تمرين خيلي خوبه (فقط بايد در مورد سخت افزارهاتون اطلاعات كافي داشته باشيد)
ماهان سرور
آکوستیک ، فوم شانه تخم مرغی ، پنل صداگیر ، یونولیت
دستگاه جوجه کشی حرفه ای
فروش آنلاین لباس کودک
خرید فالوور ایرانی
خرید فالوور اینستاگرام
خرید ممبر تلگرام
[ + افزودن آگهی متنی جدید ]
اين راهشه ديگه
شايد در نظر اول كمي سخت باشه
مثلا شما سورس يه كرنل رو از kernel.orgدانلود كنيد و نصبش كنيد
هم مشكلتون حل مي شه و هم يه تمرين خيلي خوبه (فقط بايد در مورد سخت افزارهاتون اطلاعات كافي داشته باشيد)
مودم!
سلام
من یک تازه وارد لینوکس هستم و نمیدونم چجوری باید درایور مربوط به مودم رو در ماندریوا پیدا کنم. اگر ممکنه کمک کنید.
مودم من Lucent Microelectronics هست.
شما بايد در linmodems.org دنبال درايور مودمتون بگرديد
حالا اگر راهنمايي بيشتري مي خواهيد بايد نوع چيپست شما رو بدونم
پست اول همين تاپيك رو بخونيد
خیلی ممنون
من pci32 را اجرا کردم ولی چیزی متوجه نشدم.
ممنون میشم به من کمک کنید.
شما كه لينوكس داري براي چي pci 32؟
دستور lspci --help رو اجرا كنيد و آپشن هاي اونو ببينيد و با آپشنهاي مختلف اطلاعات مورد نظرتون رو بدست بياريد.
اگر هم از pci32 مي خواهيداستفاده كنيد اول از همه اينو بدونيد كه بايد در command prompt اونو اجرا كنيد و بعد خروجي اونو اينجا كپي كنيد كافيه
من چنین چیزهایی رو در لینوکس و ویندوز به دست آوردم:
1. در لینوکس
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] AddressMap
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:07.0 Multimedia controller: Philips Semiconductors SAA7133 Video Broadcast Decoder (rev d0)
01:08.0 Communication controller: Agere Systems 56k WinModem (rev 01)
01:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a 2)
و در ویندوز با همان PCI32 با استفاده از کلیدهای مختلف (با خط فاصله از هم جدا شده اند):
Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
Device 0440h LT WinModem 56k Data+Fax+Voice+Dsvd
Subsystem ID 044011C1h LT WinModem 56k Data+Fax+Voice+Dsvd (Generic ID)
Subsystem Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
System IRQ 18, INT# A
Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
Device 0440h LT WinModem 56k Data+Fax+Voice+Dsvd
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
Revision 01h, Header Type 00h, Bus Latency Timer 00h
Minimum Bus Grant FCh, Maximum Bus Latency 0Eh
Self test 00h (Self test not supported)
PCI Class Simple Communication, type Other
Subsystem ID 044011C1h LT WinModem 56k Data+Fax+Voice+Dsvd (Generic ID)
Subsystem Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
Address 0 is a Memory Address (anywhere in 0-4Gb) : FEAFE000h
Address 1 is an I/O Port : 0000DF00h
Address 2 is an I/O Port : 0000DC00h
System IRQ 18, INT# A
New Capabilities List Present:
Power Management Capability, Version 1.1
Supports low power State D1
Supports low power State D2
Supports PME# signalling from mode(s) D2, D3hot, D3cold
PME# signalling is currently disabled
Current Power State : D0 (Device operational, no power saving)
3.3v AUX Current required : 0mA (Self powered)
Bus 1 (PCI), Device Number 8, Device Function 0
Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
Device 0440h LT WinModem 56k Data+Fax+Voice+Dsvd
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
Revision 01h, Header Type 00h, Bus Latency Timer 00h
Minimum Bus Grant FCh, Maximum Bus Latency 0Eh
Self test 00h (Self test not supported)
PCI Class Simple Communication, type Other
Subsystem ID 044011C1h LT WinModem 56k Data+Fax+Voice+Dsvd (Generic ID)
Subsystem Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
Address 0 is a Memory Address (anywhere in 0-4Gb) : FEAFE000h
Address 1 is an I/O Port : 0000DF00h
Address 2 is an I/O Port : 0000DC00h
System IRQ 18, INT# A
New Capabilities List Present:
Power Management Capability, Version 1.1
Supports low power State D1
Supports low power State D2
Supports PME# signalling from mode(s) D2, D3hot, D3cold
PME# signalling is currently disabled
Current Power State : D0 (Device operational, no power saving)
3.3v AUX Current required : 0mA (Self powered)
Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
Device 0440h LT WinModem 56k Data+Fax+Voice+Dsvd
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
Revision 01h, Header Type 00h, Bus Latency Timer 00h
Minimum Bus Grant FCh, Maximum Bus Latency 0Eh
Self test 00h (Self test not supported)
PCI Class Simple Communication, type Other
Subsystem ID 044011C1h LT WinModem 56k Data+Fax+Voice+Dsvd (Generic ID)
Subsystem Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
Address 0 is a Memory Address (anywhere in 0-4Gb) : FEAFE000h
Address 1 is an I/O Port : 0000DF00h
Address 2 is an I/O Port : 0000DC00h
System IRQ 18, INT# A
New Capabilities List Present:
Power Management Capability, Version 1.1
Supports low power State D1
Supports low power State D2
Supports PME# signalling from mode(s) D2, D3hot, D3cold
PME# signalling is currently disabled
Current Power State : D0 (Device operational, no power saving)
3.3v AUX Current required : 0mA (Self powered)
Hex-Dump of device configuration space follows:
0000 C1 11 40 04 07 00 90 02 01 00 80 07 00 00 00 00 Á.@......€.....
0010 00 E0 AF FE 01 DF 00 00 01 DC 00 00 00 00 00 00 .à¯þ.ß...Ü......
0020 00 00 00 00 00 00 00 00 40 00 00 00 C1 11 40 04 ........@...Á.@.
0030 00 00 00 00 F8 00 00 00 00 00 00 00 12 01 FC 0E ....ø.........ü.
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00F0 00 00 00 00 00 00 00 00 01 00 22 E6 00 00 00 00 .........."æ....
خیلی ببخشید اگر طولانی شد. سایر قسمتهای غیر مرتبط را حذف کردم.
خیلی ممنون میشم راهنمایی کنید.
سلام
2 نوع LTmodem هست ولي فكر مي كنم ايني كه در آدرس زير هستش درست باشه
[ برای مشاهده لینک ، با نام کاربری خود وارد شوید یا ثبت نام کنید ]
ديگه بقيه اش هم خودتون انجام بديد
فايل readme داخل بسته ها يادتون نره
سلام رووت جان
من با نرم افزار listmdm این اطلاعات رو بدست اوردم
NUMBER OF MODEMS FOUND = 1
MODEM #1:
PCI CONFIGURATION INFORMATION READ:
VENDOR ID : 125D
DEVICE ID : 2898
SUBVENDOR ID : 148D
SUBDEVICE ID : 1030
REVISION ID : 03
DEDUCED INFORMATION:
VENDOR NAME : UNKNOWN
DEVICE NAME : UNKNOWN
SUBVENDOR NAME : BROADXENT -- [ برای مشاهده لینک ، با نام کاربری خود وارد شوید یا ثبت نام کنید ]
MODEM TYPE : HSF
WINXP INBUILD SUPPORT : NO
ولی با دستور خود لینوکس جوابش یکمی فرق داشت
اگه میشه لطف کن منو راهنمایی کن
ممنون
با سلام
ببخشید دوباره مزاحم شدم.
من وارد لینک شدم ولی در فایلهای راهنما مطلبی که بفهمم! وجود نداشت!
در واقع دستوراتی که داشت رو نمی دونستم کجا و چگونه باید انجام بدم. برای من تازه کار که اصلا عادت ندارم یکمی مشکله. اگر شما رفرنس خاصی میشناسید که من با مطالعه اون بتونم مشکلاتم رو حل کنم ممنون میشم.
دستورات اون فایل به این صورت بود. اگر میدونید با یک اقدام کوچیک میشه ا.نها رو امجام داد بفرمایید:
README for 2.6 kernel series port
of Lucent/Agere linmodem driver.
1. Requirements
- Linux kernel 2.6.x (up to 2.6.10 tested at the moment of writing)
- Configured kernel headers or source (read section 6 on this)
- serial_core enabled in kernel configuration
(Device Drivers/Character Devices/Serial Drivers/"8250/16550..."
in menuconfig to "Yes" or "Module")
(most vendor supplied kernels enable this)
- See chapter 4 for state of SMP support
2. HOWTO build
You may need to create /dev/ttyLTM0 if you haven't used 2.4 version
of driver or if you don't use udev. Just do:
a. mknod --mode=0660 /dev/ttyLTM0 c 62 64
b. Change owner and group owner to match /dev/ttyS0
(Debian users: set group to dialout)
c. Create symlink /dev/modem to it ('ln -s /dev/ttyLTM0 /dev/modem')
If you use udev, than read docs/udev-setup and skip this step.
NOTE: previous versions of this driver used device name /dev/ttyLT0. If you upgrade
from previous version, than you may leave old name. But if you plan to switch to udev,
than new name may be more preferable.
Edit KERNEL_DIR variable in Makefile to reflect your 2.6 kernel dir or leave Makefile intact.
In later case driver will be compiled (or miscompiled) against
currently running kernel. Then just run make.
You will get ltmodem.ko & ltserial.ko.
Copy them to /lib/modules/`uname -r`/other/ dir and
run depmod -a.
NOTE: installing to /lib/modules/`uname -r`/other is somewhat bad practice,
'cause if you recompile your kernel with different options ltmodem modules
placed to .../other will remain there, but will likely conflict
with new kernel configuration. If that happens you must recompile (make clean; make)
and reinstall driver. Please, be aware of that. For more safety you
may install modules to more apropriate place e.g. /lib/modules/`uname -r`/kernel/serial/.
In that case new kernel modules installation will erase old ltmodem modules,
and you will easily notice it.
I actually prefer .../other approach, because often new config will be compatible with
previous.
Edit your modprobe.conf to load ltserial (not lt_serial)
for /dev/ttyLTM0.
My modprobe.conf contains following lines:
alias /dev/modem ltserial
alias char-major-62 ltserial
alias /dev/tts/LT0 ltserial
NOTE: there were reports that devfs (which is deprecated) creates /dev/ttyLT0, not /dev/tts/LT0.
If this is true and you still use devfs, than you will need to change last line to
alias /dev/ttyLT0 ltserial.
3. Report any problems to [ برای مشاهده لینک ، با نام کاربری خود وارد شوید یا ثبت نام کنید ]
4. State of SMP support
8.31 core which is supposed to support SMP does not work on my system,
so default core is old one (I dont remember what).
I have also included 8.31 core which seems to work on some (probably many)
systems. Old core also contains some fixes for SMP, I dont remember
if I did them (on top of 8.26 for example) or it is 8.30 core which
should contain that fixes.
Some code to support SMP is there since revision 6,
but because largest part of driver is closed-source
it is very hard to ensure that SMP support is correct. I believe that
driver should work fine on SMP systems with both cores.
Please, report SMP success/fail reports to me (alk@tut.by).
5. How to use 8.31 core
Just change ltmdmobj.o symlink to point to ltmdmobj-8.31.
E.g.:
ln -sf ltmdmobj.o-8.31 ltmdmobj.o
Be carefull to actually rebuild driver with new ltmdmobj.o.
'make clean' followed by 'make' should suffice.
6. Typical build problems
Many novice users report build problems.
All of them were about building kernel modules against precompiled kernels. Which is
sometimes tricky process (depending on your distro).
This is what FUSE project recomments
(taken from [ برای مشاهده لینک ، با نام کاربری خود وارد شوید یا ثبت نام کنید ]
Building the kernel module needs a configured kernel source tree matching the running kernel.
If you build your own kernel this is no problem.
On the other hand if a precompiled kernel is used, the kernel headers used by the FUSE build process
must first be prepared. There are two possibilities:
1. A package containing the kernel headers for the kernel binary is available in the distribution
(e.g. on Debian it's the kernel-headers-X.Y.Z package for kernel-image-X.Y.Z)
2. The kernel source must be prepared:
o Extract the kernel source to some directory
o Copy the running kernel's config (usually found in /boot/config-X.Y.Z)
to .config at the top of the source tree
o Run make menuconfig, then make dep at the top of the source tree (only needed on 2.4 kernels)
If using the 2.6 kernel, then write access is needed to some files in the kernel source tree.
Usually it is enough if you make .tmp_versions and .__modpost.cmd writable.
Also see docs/Example.txt section KERNEL SOURCE PREPARATION.
به اين سادگي توضيح داده كه چطور نصب مي شه
چيز خاصي نداره فقط اينكه بايد kernel-sourece يا kernel-headers بايد نصب باشه
دوست من مودم شما winmodem هست و در لينوكس ساپورت نمي شونداگر شما رفرنس خاصی میشناسید که من با مطالعه اون بتونم مشکلاتم رو حل کنم ممنون میشم.
اينها هم درايور هاي خود lucent هست
اون آدرسي كه دادم براي كرنلهاي 2.6 بود و آدرس زير هم براي كرنلهاي قبل 2.6
من چيز ديگه اي پيدا نكردم ؟؟!!
هم اکنون 1 کاربر در حال مشاهده این تاپیک میباشد. (0 کاربر عضو شده و 1 مهمان)
قوانين ايجاد تاپيک در انجمن
جواب بصورت نقل قول
نوشته شده توسط rootnt
