Notizia:
  • Rilasciata Precise Pangolin 12.04. Per ottenerla, visitate questa pagina, oppure provate il tour dal vivo con un browser web moderno.
  • Nuovo forum di Ubuntu-it, l'annuncio. È consigliato aggiornare il proprio profilo e controllare la sezione Gruppo Forum per problemi noti.
  • Rilasciata la versione italiana di Precise Pangolin 12.04. Per maggiori informazioni, consultare questa discussione.
  • Il vincitore del Concorso desktop del mese di aprile è Jerico. L'elenco dei precedenti vincitori è qui.
  • È uscito il numero 17 della Newsletter italiana di Ubuntu. Lo trovate a questo indirizzo.
  • È uscito il numero 59 di Full Circle Magazine in italiano. Lo trovate a questo indirizzo.

Asus L3D

Riconoscimento, installazione e configurazione delle periferiche.

Asus L3D

Messaggioda berna » lunedì 11 aprile 2005, 18:55

prima di tutto ciao a tutti sono nuovo
il mio problema ho istallato la versione nuova di ubuntu nel mio portatile asus L3d ma no mi riconosce il modem chi mi spiega come posso fare perfavore. con l'inglese non ci vedo molto daccordo grazie mille alessio
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda twilight » lunedì 11 aprile 2005, 20:09

ti aiutiamo con piacere :)
pero' per farlo..comincia a dirci qualcosa di piu'...di che modem si tratta?
Avatar utente
twilight
Imperturbabile Insigne
Imperturbabile Insigne
 
Messaggi: 3849
Iscrizione: febbraio 2005
Località: L'Aquila

Re:Asus L3D

Messaggioda berna » lunedì 11 aprile 2005, 20:40

non mi riesce trovare il modello del modem comunque è quello integrado dentro il portatile e mi servirebbe una mano per il riconoscimento della porta irda
grazie mille
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda dotcom » lunedì 11 aprile 2005, 20:46

ciao!
prova a dare un'occhiata qui: http://tuxmobil.org/asus.html
dotcom
Prode Principiante
 
Messaggi: 14
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda berna » martedì 12 aprile 2005, 1:26

si grazie mille ci avevo gia guardato in quella guida ma non parlano del modem e della porta irda che sono rimasti i miei ultimi due problemi
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda berna » martedì 12 aprile 2005, 13:02

perfavore nessuno che mi può aiutare.
se gli do la rilevazione automatica del modem non trova niente anche se setto le porte manualmente niente.
perfavore
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda berna » martedì 12 aprile 2005, 13:07

Intel Corp. 82801CA/CAM AC'97 Modem

questo dovrebbe essere il modello del modem
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda crashd » martedì 12 aprile 2005, 13:11

qui http://www.hup.hu/wiki/wiki.phtml?title ... D_laptopra parla sia del modem che dell'irda, ma in ungherese :unsure:
comunque ci puoi trovare i driver del modem
per l'irda da quello che ho capito devi aggiungere dei moduli e fare
apt-get install irda-common irda-utils e fare qualche altra modifica :ermm:
vabbè comunque magari cerca su google visto che ci sono i nomi di entrambi

Post modificato da: crashd, alle: 2005/04/12 14:51
Why drink and drive when you can smoke pot and fly?
crashd
Prode Principiante
 
Messaggi: 50
Iscrizione: febbraio 2005

Re:Asus L3D

Messaggioda Mizar » martedì 12 aprile 2005, 14:24

Prova a dare da terminale il comando:

[code:1]dmesg
[/code:1]
e guarda il risultato ... se il modem viene riconosciuto dovresti trovare qualcosa di simile (posto una parte del mio)

[code:1]ACPI: PCI interrupt 0000:02:04.0[A] -> GSI 5 (level, low) -> IRQ 5
ttySHSF0 at I/O 0x3000 (irq = 5) is a Conexant HSF softmodem (PCI-14f1:2f00-0e11:8d89)
[/code:1]
da cui si evince che il mio modem usa la /dev/ttySHSF0.

Io per semplicità di configurazione ho poi creato il link simbolico tra

[code:1]/dev/modem -> /dev/ttySHSF0[/code:1]
Benjamin
Mizar
Imperturbabile Insigne
Imperturbabile Insigne
 
Messaggi: 3315
Iscrizione: febbraio 2005
Località: Mola di Bari

Re:Asus L3D

Messaggioda berna » martedì 12 aprile 2005, 15:28

non appare niente riguardante il modem
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda berna » martedì 12 aprile 2005, 15:29

alessio@ubuntu:~$ dmesg
Linux version 2.6.10-5-686-smp (buildd@terranova) (gcc version 3.3.5 (Debian 1:3.3.5-8ubuntu2)) #1 SMP Tue Apr 5 12:41:40 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001dffa000 (usable)
BIOS-e820: 000000001dffa000 - 000000001dfff000 (ACPI data)
BIOS-e820: 000000001dfff000 - 000000001e000000 (ACPI NVS)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
479MB LOWMEM available.
On node 0 totalpages: 122874
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 118778 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 ASUS ) @ 0x000f52c0
ACPI: RSDT (v001 ASUS L3H 0x42302e31 MSFT 0x31313031) @ 0x1dffa000
ACPI: FADT (v001 ASUS L3H 0x42302e31 MSFT 0x31313031) @ 0x1dffa080
ACPI: BOOT (v001 ASUS L3H 0x42302e31 MSFT 0x31313031) @ 0x1dffa040
ACPI: DSDT (v001 ASUS L3H 0x20020101 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0xe408
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro quiet splash
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01406000)
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 2422.055 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 478984k/491496k available (1604k kernel code, 11868k reserved, 719k data, 192k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 4800.51 BogoMIPS (lpj=2400256)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: bfebf9ff 00000000 00000000 00000000 00000400 00000000
CPU: After vendor identify, caps: bfebf9ff 00000000 00000000 00000000 00000400 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Hyper-Threading is disabled
CPU: After all inits, caps: bfebf9ff 00000000 00000000 00000080 00000400 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: Looking for DSDT in initrd... not found!
ACPI: setting ELCR to 0200 (from 0a20)
CPU0: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 07
per-CPU timeslice cutoff: 1462.71 usecs.
task migration cache decay timeout: 2 msecs.
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
CPU0:
domain 0: span 01
groups: 01
domain 1: span 01
groups: 01
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
Freeing initrd memory: 4540k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf09c0, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050211
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 *9 11)
ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 *5 6 7 9 11)
ACPI: PCI Interrupt Link [PILC] (IRQs 3 4 5 6 7 9 *11)
ACPI: PCI Interrupt Link [PILD] (IRQs 3 4 5 6 7 9 *11)
ACPI: PCI Interrupt Link [PILE] (IRQs *11)
ACPI: PCI Interrupt Link [PILF] (IRQs *11)
ACPI: PCI Interrupt Link [PILG] (IRQs *11)
ACPI: PCI Interrupt Link [PILH] (IRQs *11)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Uncovering SIS962 that hid as a SIS503 (compatible=1)
Enabling SiS 96x SMBus.
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: Power Resource [PR0] (off)
ACPI: Power Resource [PR1] (off)
ACPI: Power Resource [PR2] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
** workaround, the "pci=routeirq" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.
Simple Boot Flag at 0x3a set to 0x1
audit: initializing netlink socket (disabled)
audit(1113299191.660:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt Link [PILC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI interrupt 0000:00:02.6[C] -> GSI 11 (level, low) -> IRQ 11
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET: Registered protocol family 8
NET: Registered protocol family 20
Restarting tasks... Strange, kswapd0 not stopped
Strange, kseriod not stopped
done
ACPI wakeup devices:
PCI0 SP USB0 USB1 USB2 USB3 ACM
ACPI: (supports S0 S1 S3 S4 S5)
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4540KiB [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 192k freed
ACPI: Fan [FAN0] (off)
ACPI: Fan [FAN1] (off)
ACPI: Fan [FAN2] (off)
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU] (supports 8 throttling states)
ACPI: Thermal Zone [TZ] (45 C)
NET: Registered protocol family 1
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller at PCI slot 0000:00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: IC25N040ATMR04-0, ATA DISK drive
elevator: using anticipatory as default io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: 78140160 sectors (40007 MB) w/1740KiB Cache, CHS=16383/255/63, UDMA(100)
hda: cache flushes supported
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 >
Probing IDE interface ide1...
hdc: TOSHIBA DVD-ROM SD-R2312, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
spurious 8259A interrupt: IRQ7.
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
Stopping tasks: ==|
Freeing memory... done (466 pages freed)
Restarting tasks... done
VFS: Can't find ext3 filesystem on dev hda1.
VFS: Can't find an ext2 filesystem on dev hda1.
ReiserFS: hda1: found reiserfs format "3.6" with standard journal
ReiserFS: hda1: using ordered data mode
ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: Using r5 hash to sort names
Adding 1421712k swap on /dev/hda5. Priority:-1 extents:1
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
lp0: using parport0 (interrupt-driven).
mice: PS/2 mouse device common for all mice
Synaptics Touchpad, model: 1
Firmware: 4.6
180 degree mounted touchpad
Sensor: 18
new absolute packet format
Touchpad has extended capability bits
-> four buttons
-> multifinger detection
-> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
ieee1394: Initialized config rom entry `ip1394'
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins
ts: Compaq touchscreen protocol output
Capability LSM initialized
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: dm-devel@redhat.com
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
cdrom: open failed.
Real Time Clock Driver v1.12
input: PC Speaker
inserting floppy driver for 2.6.10-5-686-smp
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected SiS 650 chipset
agpgart: Maximum main memory to use for agp memory: 409M
agpgart: AGP aperture is 64M @ 0xec000000
cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
i2c-sis96x version 1.0.0
sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0xe800
ACPI: PCI interrupt 0000:00:02.7[C] -> GSI 11 (level, low) -> IRQ 11
intel8x0_measure_ac97_clock: measured 49342 usecs
intel8x0: clocking to 48000
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [PILE] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 11 (level, low) -> IRQ 11
ohci_hcd 0000:00:03.0: Silicon Integrated Systems [SiS] USB 1.0 Controller
ohci_hcd 0000:00:03.0: irq 11, pci mem 0xeb000000
ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [PILF] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:03.1[B] -> GSI 11 (level, low) -> IRQ 11
ohci_hcd 0000:00:03.1: Silicon Integrated Systems [SiS] USB 1.0 Controller (#2)
ohci_hcd 0000:00:03.1: irq 11, pci mem 0xea800000
ohci_hcd 0000:00:03.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [PILG] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:03.2[C] -> GSI 11 (level, low) -> IRQ 11
ohci_hcd 0000:00:03.2: Silicon Integrated Systems [SiS] USB 1.0 Controller (#3)
ohci_hcd 0000:00:03.2: irq 11, pci mem 0xea000000
ohci_hcd 0000:00:03.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
usb 3-1: new low speed USB device using ohci_hcd and address 2
ACPI: PCI Interrupt Link [PILH] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:03.3[D] -> GSI 11 (level, low) -> IRQ 11
ehci_hcd 0000:00:03.3: Silicon Integrated Systems [SiS] USB 2.0 Controller
ehci_hcd 0000:00:03.3: irq 11, pci mem 0xe9800000
ehci_hcd 0000:00:03.3: new USB bus registered, assigned bus number 4
PCI: cache line size of 128 is not supported by device 0000:00:03.3
ehci_hcd 0000:00:03.3: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
usbcore: registered new driver hiddev
usbhid: probe of 3-1:1.0 failed with error -5
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
usb 3-1: USB disconnect, address 2
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
ACPI: PCI Interrupt Link [PILB] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 5 (level, low) -> IRQ 5
Yenta: CardBus bridge found at 0000:00:0a.0 [1043:1695]
usb 3-1: new low speed USB device using ohci_hcd and address 3
Yenta: ISA IRQ mask 0x0418, PCI irq 5
Socket status: 30000006
ACPI: PCI interrupt 0000:00:0a.1[B] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:0a.1 [1043:1695]
input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:03.2-1
Yenta: ISA IRQ mask 0x0418, PCI irq 11
Socket status: 30000006
ohci1394: $Rev: 1223 $ Ben Collins
ACPI: PCI Interrupt Link [PILA] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI interrupt 0000:00:0a.2[C] -> GSI 9 (level, low) -> IRQ 9
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[9] MMIO=[e9000000-e90007ff] Max Packet=[2048]
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp: pci dev 0000:00:0d.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.27
ACPI: PCI Interrupt Link [PILD] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xa000, 00:0c:6e:4a:fd:12, IRQ 11
eth0: Identified 8139 chip type 'RTL-8100'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e01800030a840a]
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0317e40(lo)
IPv6 over IPv4 tunneling driver
Asus Laptop ACPI Extras version 0.29
L3H model detected, supported
ACPI: AC Adapter [AC] (on-line)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Sleep Button (CM) [SLPB]
ibm_acpi: ec object not found
ACPI: Battery Slot [BAT] (battery present)
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
cs: IO port probe 0x0100-0x04ff: excluding 0x480-0x48f 0x4d0-0x4d7
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
eth0: no IPv6 routers present
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present




vi ho riportato il tutto
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda Mizar » martedì 12 aprile 2005, 17:03

Ok ... non lo vede.

Da quello che ho capito, non hai installato il driver per Linux.
Il tuo notebook ha un softmodem ed è necessario installare il driver apposito.
La procedura differisce in base al modem.

Da una veloce ricerca mi sembra che il driver che ti serve lo trovi qui:

http://www.smlink.com

Controlla e segui le istruzioni. Di più non posso dirti.
Benjamin
Mizar
Imperturbabile Insigne
Imperturbabile Insigne
 
Messaggi: 3315
Iscrizione: febbraio 2005
Località: Mola di Bari

Re:Asus L3D

Messaggioda berna » martedì 12 aprile 2005, 17:10

ok grazie mille
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda berna » martedì 12 aprile 2005, 17:35

le istruzioni per istallare i drive del modem sono questa ma io ho provato e riprovato ma dato che con l'inglese non vado molto daccordo chi mi può fare in parole povere quello che dice il file perfavore


Smart Link Ltd.
http://www.smlink.com
Sep 30, 2003


Smart Link Soft Modem for Linux
-------------------------------


Introduction
============

This is Smart Link Soft Modem for Linux version 2.9. It provides
full-featured 56K Voice Fax Modem.
This is implemented as generic application (slmodemd) and set of
hardware specific kernel-space drivers (slamr, slusb).
ALSA modem drivers may be used instead of proprietary ones (see ALSA mode).

Features
========

Modem: V.92, V.90, V.34, V.32bis, V.32, V.23, V.22, V.21, Bell 103/212.
Flow control: V.42.
Compression: V.44, V.42bis.
Fax: Class 1.
Voice: V253 like modem.
Multiple modems are supported.


Supported Hardware
==================

HAMR5600 based AMR/CNR/MDC/ACR modem cards on the following Southbridge
chips:
- Intel ICH0,ICH2, ICH3, ICH4
- Via 686A, 686B, 8231, 8233
- SiS 630
- ALI 1535.
SmartPCI56/561/562/563 based PCI modem cards.
SmartUSB56 based USB modem.



Requirements
============

CPU: Intel Pentium II, Celron. AMD K6, Cyrix 500MHz or higher.
Memory: 64MB.

OS: Linux 2.4. You need the kernel header files at least (or full kernel
source tree) installed and configured.
Linux 2.6. You need the full kernel source tree installed and configured.

Note: Most Linux Distributions have 'ready to use' kernel source package -
be sure that this is installed.


Installation
============

1. Unpack tar.gz package file:

$ gzip -dc slmodem-2.9.X.tar.gz | tar xf -

2. 'cd' to package directory:

$ cd slmodem-2.9.X

3. Review and edit 'Makefile' (if need):

In many cases you will need to correct path to your local kernel
source tree:

KERNEL_DIR=/path/to/linux

Default KERNEL_DIR is '/lib/modules//build'. Many Linux
Distributions use directory '/usr/src/linux-' also.

Note: If you are using Linux kernel 2.4, only header files should be
available for build in $(KERNEL_DIR)/include

Another way to pass right value KERNEL_DIR is to use command line
parameter while running 'make':

$ make KERNEL_DIR=/path/to/linux ...

4. Run 'make' command to compile package:

$ make

5. Install. As 'root' user run:

# make install

It will install:

- application 'slmodemd' under '/usr/sbin' directory

- hardware specific drivers (kernel modules) 'slamr' and 'slusb'
under conventional kernel modules directory

- character device nodes '/dev/slamr0-3' with major number 212
(for pci modems) and '/dev/slusb0-3' with major number 213
(for usb modems).

- config modules for autoloading (by editing file '/etc/modules.conf')
(only with 2.4 kernels)

6. Config modem country.

Use AT+GCI= command to setup country.

Also you can setup default modem country by passing command line
parameter '--country=MY_COUNTRY' to program 'slmodemd'.

See output of 'slmodemd --countrylist' for a list of supported
country names and T.35 country codes (see also 'slmodemd --help').

Note: Command ATI7 shows currently installed country setting.

8. Uninstallation.

In package directory just type:

# make uninstall


Getting Started
===============

After successful installation and configuration:

1. Load modem driver.

Load your modem hardware specific kernel module:

# modprobe slamr

if you are using AMR/CNR/PCI modem, or

# modprobe slusb

if you are using SmartUSB56 Modem.

Note: this will be done automatically when modules were
configured for 'loading on demand'

Note: this is safe to load both 'alamr' and 'slusb' modules.

2. Run soft modem application.

# /usr/sbin/slmodemd [options]

Where device name is appropriate device node for your modem
(look at output of 'dmesg' command).
Run '/usr/sbin/slmodemd --help' for details.

Examples:

# /usr/sbin/slmodemd --country=USA /dev/slamr0

, or for SmartUSB56 Modems:

# /usr/sbin/slmodemd --country=ITALY /dev/slusb0

3. Using the modem.

When 'slmodemd' is running this creates PTY (pseudo-terminal) to
emulate modem port device, also this creates symbolic link
like '/dev/ttySL0' (shown at startup).

Config your application to use this link '/dev/ttySL0' (or PTY node
itself) as modem port.

Note: Some application want 'to know' that they are working with
pseudo-terminal and may require additional configurations.

Known application notes:

- 'wvdial' requires option 'Carrier Check = no' in config file

- some versions of 'kppp' may not work properly with devices named
like '/dev/ttySL0'. To workaround this you may create symbolic link
'/dev/modem' ( # ln -s /dev/ttySL0 /dev/modem ) and use this link
as modem device with 'kppp'

4. Startup automation.

There are examples of startup scripts in 'scripts' directory.


ALSA mode
=========

ALSA has the built-in modem drivers included in 'alsa-driver' >= 1.0.2
and in Linux kernel >= 2.6.5. Currently there is 'intel8x0m' (snd-intel8x0m)
modem driver, which supports ICH based AC97 modems (MC97).

Recent 'alsa-driver' (>=1.0.6) has also support for NVidia NForce
(snd-intel8x0m) and ATI IXP (snd-atiixp-modem) based modems.

1. Configure your kernel and enable ALSA and ICH based modem support
( 'Device Drivers' -> 'Sound' -> 'Advanced Linux Sound Architecture' ->
'PCI devices' -> 'Intel i8x0/MX440; AMD768/8111 modems' ) .

2. Build and install kernel and modules as usual (make , make modules_install,
etc.). ICH modem driver modem module name is 'snd-intel8x0m'
(if was configured as module).

3. Build application 'slmodemd' with ALSA support. For this in
slmodem-2.9.x dir:

$ cd modem
$ make SUPPORT_ALSA=1

This will build 'slmodemd' with ALSA support. If compilation is failed
review Makefile (near ALSA_SUPPORT condition) and define right library
and/or CFLAGS

4. Use option '--alsa' when running 'slmodemd' and ALSA conventional
device name ('hw:0' or 'hw:1' for instance). If modem support in
the kernel was enabled as module module 'snd-intel8x0m' should be loaded.

Note: Recent version of 'alsa-lib' (>= 1.0.6) has built-in "modem" device
name support ('modem:0', 'modem:1', etc). It is recommended to use
those names with modems (mandatory with ATI IXP modems).

Note: When using ALSA modem driver you don't need to load other
modules ('slamr').


Troubleshooting
===============

If you get an error message during installation/configuration or loading
the modules try to see it in FAQ file.

Please report the problem to your modem provider or to us
(linux-support@smlink.com).


Feedback
========

Please send any feedbacks to Smart Link. See the Smart Link
web site for contact information (www.smlink.com) or to
linux-support@smlink.com.
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda pierba » martedì 12 aprile 2005, 20:33

Forse è più semplice se racconti tu dove ti da messaggio di errore; sono molto utili i messaggi di risposta che ti da la shell quando non riesce ad eseguire il comando che tu gli dai.
ciao, Pietro

Post modificato da: pierba, alle: 2005/04/12 20:36
Pietro pagina personale - Avete domande sul forum? Leggendo le FAQ: potreste trovare la risposta.
La conoscenza deve essere collettiva, quindi, come da regolamento (Sez. I punto 18) i messaggi personali contententi richieste di assistenza tecnica verranno ignorati.
Avatar utente
pierba
Moderatore Globale
Moderatore Globale
 
Messaggi: 14359
Iscrizione: febbraio 2005

Re:Asus L3D

Messaggioda Mizar » mercoledì 13 aprile 2005, 11:16

berna scritto:
le istruzioni per istallare i drive del modem sono questa ma io ho provato e riprovato ma dato che con l'inglese non vado molto daccordo chi mi può fare in parole povere quello che dice il file perfavore


In parole povere è un po comlicato, comunque:

- Assicurati di aver installato i source del kernel, fai una ricerca in synaptic di linux-header e linux-source della versione del kernel che hai installato (la vedi dal menu iniziale di grub) e installali.

- Segnati il percorso andandolo a cercare in /lib/modules/tua_versione/build


Installazione
============

1. Apri il terminale e vai nella tua home, scompatta il paccheeto con:

$ gzip -dc slmodem-2.9.X.tar.gz | tar xf -

Sostituisci ovviamente dove opportuno i nomi corretti

2. Spostati col terminale nella directory creata:

$ cd slmodem-2.9.X

3. Modifica il 'Makefile'

$ gedit makefile

Correggendo la linea sotto con il percorso dei sorgenti del Kernel che hai segnato prima

KERNEL_DIR=/lib/modules/tuo_kernel/build

4. Esegui il 'make' per compilare il pacchetto:

$ make

5. Installa:

# sudo make install


Inizio
===============

1. Carica il driver

# sudo modprobe slamr

2. Esegui l'applicazione

# /usr/sbin/slmodemd [options]

Per selezionare la device guarda dmesg

Esempio:

# /usr/sbin/slmodemd --country=ITALY /dev/slamr0

3. Uso

Quando esegui slmodemd dovrebbe apparire un messaggio che ti mostra il nome della device che ha creato per l'uso del modem.
Questa device è quella che devi usare per la configurazione della porta del modem quando ti viene richiesta da pppconfig.



P.S.
Questa traduzione è un sunto del tuo post ..... ho tradotto solo quello che mi è sembrato necessario per farti iniziare, per il resto se hai problemi registrati su freenode al canale ubuntu-it e fatti seguire passo passo, è più semplice.
Per darti informazioni è necessario sapere quello che succede quando esegui i comandi.
Se mi vedi in ubuntu-it (Benjamin64) puoi contattarmi, ma comunque fai la domanda li ... ci sarà sicuramente qualcuno disposto a seguirti.

Ciao.
Benjamin
Mizar
Imperturbabile Insigne
Imperturbabile Insigne
 
Messaggi: 3315
Iscrizione: febbraio 2005
Località: Mola di Bari

Re:Asus L3D

Messaggioda berna » mercoledì 13 aprile 2005, 14:52

questi sono gli errori che mi da


alessio@ubuntu:~$ gzip -dc slmodem-2.9.10.tar.gz | tar xf -
alessio@ubuntu:~$ cd slmodem-2.9.10
alessio@ubuntu:~/slmodem-2.9.10$ gedit makefile
alessio@ubuntu:~/slmodem-2.9.10$ make
make -C modem all
make[1]: Entering directory `/home/alessio/slmodem-2.9.10/modem'
rebuild profile...
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_main.o -c modem_main.c
make[1]: gcc: Command not found
make[1]: *** [modem_main.o] Error 127
make[1]: Leaving directory `/home/alessio/slmodem-2.9.10/modem'
make: *** [modem] Error 2
alessio@ubuntu:~/slmodem-2.9.10$ sudo make install
Password:
make -C modem all
make[1]: Entering directory `/home/alessio/slmodem-2.9.10/modem'
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_main.o -c modem_main.c
make[1]: gcc: Command not found
make[1]: *** [modem_main.o] Error 127
make[1]: Leaving directory `/home/alessio/slmodem-2.9.10/modem'
make: *** [modem] Error 2
alessio@ubuntu:~/slmodem-2.9.10$
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda Mizar » mercoledì 13 aprile 2005, 15:19

Ti manca il compilatore, devi installare il pacchetto build-essential

sudo apt-get install build-essential
Benjamin
Mizar
Imperturbabile Insigne
Imperturbabile Insigne
 
Messaggi: 3315
Iscrizione: febbraio 2005
Località: Mola di Bari

Re:Asus L3D

Messaggioda berna » mercoledì 13 aprile 2005, 15:50

istallato il pacchetto per la compilazione ora mi da questo errore

alessio@ubuntu:~$ cd slmodem-2.9.10
alessio@ubuntu:~/slmodem-2.9.10$ make
make -C modem all
make[1]: Entering directory `/home/alessio/slmodem-2.9.10/modem'
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_main.o -c modem_main.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_cmdline.o -c modem_cmdline.cgcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem.o -c modem.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_datafile.o -c modem_datafile.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_at.o -c modem_at.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_timer.o -c modem_timer.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_pack.o -c modem_pack.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_ec.o -c modem_ec.c
modem_ec.c:689: warning: `t403_timeout' defined but not used
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_comp.o -c modem_comp.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_param.o -c modem_param.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_debug.o -c modem_debug.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o homolog_data.o -c homolog_data.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o dp_sinus.o -c dp_sinus.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o dp_dummy.o -c dp_dummy.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o sysdep_common.o -c sysdep_common.cgcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_test.o -c modem_test.c
gcc -o modem_test modem_test.o modem_cmdline.o modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o
make[1]: Leaving directory `/home/alessio/slmodem-2.9.10/modem'
alessio@ubuntu:~/slmodem-2.9.10$ sudo make install
Password:
make -C modem all
make[1]: Entering directory `/home/alessio/slmodem-2.9.10/modem'
make[1]: Leaving directory `/home/alessio/slmodem-2.9.10/modem'
make -C drivers KERNEL_DIR=lib/modules/2.6.10-5-386
make[1]: Entering directory `/home/alessio/slmodem-2.9.10/drivers'
cc -Ilib/modules/2.6.10-5-386/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.0-test7
make[2]: Entering directory `/home/alessio/slmodem-2.9.10/drivers'
make modules -C lib/modules/2.6.10-5-386 SUBDIRS=/home/alessio/slmodem-2.9.10/drivers
make: *** lib/modules/2.6.10-5-386: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[2]: *** [all] Error 2
make[2]: Leaving directory `/home/alessio/slmodem-2.9.10/drivers'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/alessio/slmodem-2.9.10/drivers'
make: *** [drivers] Error 2
alessio@ubuntu:~/slmodem-2.9.10$ sudo make install
make -C modem all
make[1]: Entering directory `/home/alessio/slmodem-2.9.10/modem'
make[1]: Leaving directory `/home/alessio/slmodem-2.9.10/modem'
make -C drivers KERNEL_DIR=lib/modules/2.6.10-5-386
make[1]: Entering directory `/home/alessio/slmodem-2.9.10/drivers'
cc -Ilib/modules/2.6.10-5-386/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.0-test7
make[2]: Entering directory `/home/alessio/slmodem-2.9.10/drivers'
make modules -C lib/modules/2.6.10-5-386 SUBDIRS=/home/alessio/slmodem-2.9.10/drivers
make: *** lib/modules/2.6.10-5-386: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[2]: *** [all] Error 2
make[2]: Leaving directory `/home/alessio/slmodem-2.9.10/drivers'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/alessio/slmodem-2.9.10/drivers'
make: *** [drivers] Error 2
alessio@ubuntu:~/slmodem-2.9.10$
berna
Prode Principiante
 
Messaggi: 47
Iscrizione: aprile 2005

Re:Asus L3D

Messaggioda Mizar » mercoledì 13 aprile 2005, 16:28

E' sbagliata la KERNEL_DIR

Controlla ...... mi sembra manchi lo / iniziale.
Benjamin
Mizar
Imperturbabile Insigne
Imperturbabile Insigne
 
Messaggi: 3315
Iscrizione: febbraio 2005
Località: Mola di Bari

Successiva

Torna a Driver e periferiche

Chi c’è in linea

Visualizzano questa pagina: Eresia, lupogiampy e 12 ospiti