|
|
|
|
|
|
| Author |
Message |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Thu Jan 05, 2006 9:15 am Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
I had compiled pnpbios into the kernel... just, it didn't worked
properly :)
my own problem isn't really about removing XFree, but installing
x.org... i tought it would have been better if i first removed xfree :)
bye! |
|
| Back to top |
|
 |
Joel Reicher *nix forums beginner
Joined: 15 Nov 2005
Posts: 29
|
Posted: Wed Jan 04, 2006 10:34 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
"Alberto" <santini.alberto@gmail.com> writes:
| Quote: | Joel! You were absolutely right! It was a PnP+BIOS problem!
In my BIOS there was an option with a description such this:
"If your OS isn't PnP capable you should turn this option off to have
your non-bootable devices configured by the BIOS" .. i disabled it
and.. IT WORKS! wow!
|
There is also the pnpbios driver in NetBSD that might allow you to
keep that option turned on if you want. I don't know if you already
had it compiled in.
| Quote: | p.s. last little question... how to remove X11 that had been installed
when i installed netbsd? pkg_delete says he knows nothing about it
|
X11 isn't a pkgsrc package, it is part of the NetBSD distribution. The
installation program allows you to select "distribution sets" if you
do a custom installation rather than a full install. I don't know if
there's a program for removing distribution sets, but you could remove
the files by hand. From memory, a few of the other distribution sets
have files in /usr/X11R6. Find out which files, and then remove all of
/usr/X11R6 except for those.
Cheers,
- Joel |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Wed Jan 04, 2006 6:31 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
Joel! You were absolutely right! It was a PnP+BIOS problem!
In my BIOS there was an option with a description such this:
"If your OS isn't PnP capable you should turn this option off to have
your non-bootable devices configured by the BIOS" .. i disabled it
and.. IT WORKS! wow!
i'm very happy i finally put NetBSD at work!
Thanks 1,000 times :)
p.s. last little question... how to remove X11 that had been installed
when i installed netbsd? pkg_delete says he knows nothing about it :D
Bye!! |
|
| Back to top |
|
 |
Joel Reicher *nix forums beginner
Joined: 15 Nov 2005
Posts: 29
|
Posted: Tue Jan 03, 2006 11:38 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
"Alberto" <santini.alberto@gmail.com> writes:
| Quote: | Jan 3 14:55:48 folgore /netbsd: pci_intr_map: no mapping for pin A
(line=ff)
|
Messages like that one are the key, I believe. They're from
x86/pci/pci_machdep.c and the comments there read
/*
* Section 6.2.4, `Miscellaneous Functions', says that 255 means
* `unknown' or `no connection' on a PC. We assume that a device with
* `no connection' either doesn't have an interrupt (in which case the
* pin number should be 0, and would have been noticed above), or
* wasn't configured by the BIOS (in which case we punt, since there's
* no real way we can know how the interrupt lines are mapped in the
* hardware).
*
* XXX
* Since IRQ 0 is only used by the clock, and we can't actually be sure
* that the BIOS did its job, we also recognize that as meaning that
* the BIOS has not configured the device.
*/
So it seems my guess about the BIOS might be right. I don't know why
the other OSes are working. Perhaps it's a PNP thing. If it's possible
to specify the IRQs for each PCI slot in the BIOS setup, do that. I
suspect this might be some autoconblatheration problem.
Cheers,
- Joel |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Tue Jan 03, 2006 2:17 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
| Quote: | That is *not* normal. I'm thinking BIOS problems, or perhaps something
else misconfigured in your kernel. Perhaps you should post the
complete dmesg output?
BIOS problems should happen with all OSs, i think! |
ok.. this is zcat /var/log/messages.0.gz | grep "Jan 3 14:55"
Jan 3 14:55:48 folgore syslogd: restart
Jan 3 14:55:48 folgore /netbsd: NetBSD 3.0 (alberto) #7: Tue Jan 3
14:53:32 CET 2006
Jan 3 14:55:48 folgore /netbsd:
root@folgore:/usr/src/sys/arch/i386/compile/alberto
Jan 3 14:55:48 folgore /netbsd: total memory = 383 MB
Jan 3 14:55:48 folgore /netbsd: avail memory = 372 MB
Jan 3 14:55:48 folgore /netbsd: BIOS32 rev. 0 found at 0xf0ad0
Jan 3 14:55:48 folgore /netbsd: PCI BIOS rev. 2.1 found at 0xf0cd0
Jan 3 14:55:48 folgore /netbsd: PCI IRQ Routing Table rev. 1.0 found
at 0xf1280, size 160 bytes (8 entries)
Jan 3 14:55:48 folgore /netbsd: PCI Interrupt Router at 000:04:0 (VIA
Technologies VT82C586 PCI-ISA Bridge compatible)
Jan 3 14:55:48 folgore /netbsd: mainbus0 (root)
Jan 3 14:55:48 folgore /netbsd: cpu0 at mainbus0: (uniprocessor)
Jan 3 14:55:48 folgore /netbsd: cpu0: Intel Pentium III (686-class),
999.80 MHz, id 0x68a
Jan 3 14:55:48 folgore /netbsd: cpu0: features
383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR>
Jan 3 14:55:48 folgore /netbsd: cpu0: features
383f9ff<PGE,MCA,CMOV,PAT,PSE36,MMX>
Jan 3 14:55:48 folgore /netbsd: cpu0: features 383f9ff<FXSR,SSE>
Jan 3 14:55:48 folgore /netbsd: cpu0: I-cache 16 KB 32B/line 4-way,
D-cache 16 KB 32B/line 4-way
Jan 3 14:55:48 folgore /netbsd: cpu0: L2 cache 256 KB 32B/line 8-way
Jan 3 14:55:48 folgore /netbsd: cpu0: ITLB 32 4 KB entries 4-way, 2 4
MB entries fully associative
Jan 3 14:55:48 folgore /netbsd: cpu0: DTLB 64 4 KB entries 4-way, 8 4
MB entries 4-way
Jan 3 14:55:48 folgore /netbsd: cpu0: 8 page colors
Jan 3 14:55:48 folgore /netbsd: pci0 at mainbus0 bus 0: configuration
mode 1
Jan 3 14:55:48 folgore /netbsd: pci0: i/o space, memory space enabled,
rd/line, rd/mult, wr/inv ok
Jan 3 14:55:48 folgore /netbsd: pchb0 at pci0 dev 0 function 0
Jan 3 14:55:48 folgore /netbsd: pchb0: VIA Technologies VT82C691
(Apollo Pro) Host-PCI (rev. 0xc4)
Jan 3 14:55:48 folgore /netbsd: agp0 at pchb0: aperture at 0xfc000000,
size 0x10000000
Jan 3 14:55:48 folgore /netbsd: ppb0 at pci0 dev 1 function 0: VIA
Technologies VT82C598 (Apollo MVP3) CPU-AGP Bridge (rev. 0x00)
Jan 3 14:55:48 folgore /netbsd: pci1 at ppb0 bus 1
Jan 3 14:55:48 folgore /netbsd: pci1: i/o space, memory space enabled
Jan 3 14:55:48 folgore /netbsd: vga1 at pci1 dev 0 function 0: Nvidia
GeForce2 MX (rev. 0xa1)
Jan 3 14:55:48 folgore /netbsd: wsdisplay0 at vga1 kbdmux 1: console
(80x25, vt100 emulation)
Jan 3 14:55:48 folgore /netbsd: wsmux1: connecting to wsdisplay0
Jan 3 14:55:48 folgore /netbsd: wsdisplay0: screen 1-5 added (80x25,
vt100 emulation)
Jan 3 14:55:48 folgore /netbsd: pcib0 at pci0 dev 4 function 0
Jan 3 14:55:48 folgore /netbsd: pcib0: VIA Technologies VT82C686A
PCI-ISA Bridge (rev. 0x40)
Jan 3 14:55:48 folgore /netbsd: viaide0 at pci0 dev 4 function 1
Jan 3 14:55:48 folgore /netbsd: viaide0: VIA Technologies VT82C686A
(Apollo KX133) ATA100 controller
Jan 3 14:55:48 folgore /netbsd: viaide0: bus-master DMA support
present
Jan 3 14:55:48 folgore /netbsd: viaide0: primary channel configured to
compatibility mode
Jan 3 14:55:48 folgore /netbsd: viaide0: primary channel interrupting
at irq 14
Jan 3 14:55:48 folgore /netbsd: atabus0 at viaide0 channel 0
Jan 3 14:55:48 folgore /netbsd: viaide0: secondary channel configured
to compatibility mode
Jan 3 14:55:48 folgore /netbsd: viaide0: secondary channel
interrupting at irq 15
Jan 3 14:55:48 folgore /netbsd: atabus1 at viaide0 channel 1
Jan 3 14:55:48 folgore /netbsd: uhci0 at pci0 dev 4 function 2: VIA
Technologies VT83C572 USB Controller (rev. 0x16)
Jan 3 14:55:48 folgore /netbsd: uhci0: interrupting at irq 5
Jan 3 14:55:48 folgore /netbsd: usb0 at uhci0: USB revision 1.0
Jan 3 14:55:48 folgore /netbsd: uhub0 at usb0
Jan 3 14:55:48 folgore /netbsd: uhub0: VIA Technologies UHCI root hub,
class 9/0, rev 1.00/1.00, addr 1
Jan 3 14:55:48 folgore /netbsd: uhub0: 2 ports with 2 removable, self
powered
Jan 3 14:55:48 folgore /netbsd: uhci1 at pci0 dev 4 function 3: VIA
Technologies VT83C572 USB Controller (rev. 0x16)
Jan 3 14:55:48 folgore /netbsd: uhci1: interrupting at irq 5
Jan 3 14:55:48 folgore /netbsd: usb1 at uhci1: USB revision 1.0
Jan 3 14:55:48 folgore /netbsd: uhub1 at usb1
Jan 3 14:55:48 folgore /netbsd: uhub1: VIA Technologies UHCI root hub,
class 9/0, rev 1.00/1.00, addr 1
Jan 3 14:55:48 folgore /netbsd: uhub1: 2 ports with 2 removable, self
powered
Jan 3 14:55:48 folgore /netbsd: pchb1 at pci0 dev 4 function 4
Jan 3 14:55:48 folgore /netbsd: pchb1: VIA Technologies VT82C686A
SMBus Controller (rev. 0x40)
Jan 3 14:55:48 folgore /netbsd: eap0 at pci0 dev 9 function 0: Ensoniq
CT5880 CT5880-C (rev. 0x02)
Jan 3 14:55:48 folgore /netbsd: pci_intr_map: no mapping for pin A
(line=ff)
Jan 3 14:55:48 folgore /netbsd: eap0: couldn't map interrupt
Jan 3 14:55:48 folgore /netbsd: ohci0 at pci0 dev 10 function 0: Acer
Labs M5237 USB 1.1 Host Controller (rev. 0x03)
Jan 3 14:55:48 folgore /netbsd: pci_intr_map: no mapping for pin B
(line=ff)
Jan 3 14:55:48 folgore /netbsd: ohci0: couldn't map interrupt
Jan 3 14:55:48 folgore /netbsd: ohci1 at pci0 dev 10 function 1: Acer
Labs M5237 USB 1.1 Host Controller (rev. 0x03)
Jan 3 14:55:48 folgore /netbsd: pci_intr_map: no mapping for pin C
(line=ff)
Jan 3 14:55:48 folgore /netbsd: ohci1: couldn't map interrupt
Jan 3 14:55:48 folgore /netbsd: ohci2 at pci0 dev 10 function 2: Acer
Labs M5237 USB 1.1 Host Controller (rev. 0x03)
Jan 3 14:55:48 folgore /netbsd: pci_intr_map: no mapping for pin D
(line=ff)
Jan 3 14:55:48 folgore /netbsd: ohci2: couldn't map interrupt
Jan 3 14:55:48 folgore /netbsd: ehci0 at pci0 dev 10 function 3: Acer
Labs M5239 USB 2.0 Host Controller (rev. 0x01)
Jan 3 14:55:48 folgore /netbsd: pci_intr_map: no mapping for pin A
(line=ff)
Jan 3 14:55:48 folgore /netbsd: ehci0: couldn't map interrupt
Jan 3 14:55:48 folgore /netbsd: vr0 at pci0 dev 11 function 0: VIA
VT6105 (Rhine III) 10/100 Ethernet
Jan 3 14:55:48 folgore /netbsd: vr0: interrupting at irq 11
Jan 3 14:55:48 folgore /netbsd: vr0: Ethernet address:
00:40:f4:8e:06:8c
Jan 3 14:55:48 folgore /netbsd: OUI 0x0002c6 model 0x0034 rev 9 at vr0
phy 1 not configured
Jan 3 14:55:48 folgore /netbsd: isa0 at pcib0
Jan 3 14:55:48 folgore /netbsd: lpt0 at isa0 port 0x378-0x37b irq 7
Jan 3 14:55:48 folgore /netbsd: com0 at isa0 port 0x3f8-0x3ff irq 4:
ns16550a, working fifo
Jan 3 14:55:48 folgore /netbsd: com1 at isa0 port 0x2f8-0x2ff irq 3:
ns16550a, working fifo
Jan 3 14:55:48 folgore /netbsd: pckbc0 at isa0 port 0x60-0x64
Jan 3 14:55:48 folgore /netbsd: pckbd0 at pckbc0 (kbd slot)
Jan 3 14:55:48 folgore /netbsd: pckbc0: using irq 1 for kbd slot
Jan 3 14:55:48 folgore /netbsd: wskbd0 at pckbd0: console keyboard,
using wsdisplay0
Jan 3 14:55:48 folgore /netbsd: pms0 at pckbc0 (aux slot)
Jan 3 14:55:48 folgore /netbsd: pckbc0: using irq 12 for aux slot
Jan 3 14:55:48 folgore /netbsd: wsmouse0 at pms0 mux 0
Jan 3 14:55:48 folgore /netbsd: pcppi0 at isa0 port 0x61
Jan 3 14:55:48 folgore /netbsd: midi0 at pcppi0: PC speaker
Jan 3 14:55:48 folgore /netbsd: sysbeep0 at pcppi0
Jan 3 14:55:48 folgore /netbsd: isapnp0 at isa0 port 0x279: ISA Plug
'n Play device support
Jan 3 14:55:48 folgore /netbsd: npx0 at isa0 port 0xf0-0xff: using
exception 16
Jan 3 14:55:48 folgore /netbsd: fdc0 at isa0 port 0x3f0-0x3f7 irq 6
drq 2
Jan 3 14:55:48 folgore /netbsd: isapnp0: no ISA Plug 'n Play devices
found
Jan 3 14:55:48 folgore /netbsd: fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2
head, 18 sec
Jan 3 14:55:48 folgore /netbsd: wd0 at atabus0 drive 0: <Maxtor
6Y080L0>
Jan 3 14:55:48 folgore /netbsd: wd0: drive supports 16-sector PIO
transfers, LBA addressing
Jan 3 14:55:48 folgore /netbsd: wd0: 78167 MB, 158816 cyl, 16 head, 63
sec, 512 bytes/sect x 160086528 sectors
Jan 3 14:55:48 folgore /netbsd: wd0: 32-bit data port
Jan 3 14:55:48 folgore /netbsd: wd0: drive supports PIO mode 4, DMA
mode 2, Ultra-DMA mode 6 (Ultra/133)
Jan 3 14:55:48 folgore /netbsd: wd1 at atabus0 drive 1: <Maxtor
6Y080L0>
Jan 3 14:55:48 folgore /netbsd: wd1: drive supports 16-sector PIO
transfers, LBA addressing
Jan 3 14:55:48 folgore /netbsd: wd1: 78167 MB, 158816 cyl, 16 head, 63
sec, 512 bytes/sect x 160086528 sectors
Jan 3 14:55:48 folgore /netbsd: wd1: 32-bit data port
Jan 3 14:55:48 folgore /netbsd: wd1: drive supports PIO mode 4, DMA
mode 2, Ultra-DMA mode 6 (Ultra/133)
Jan 3 14:55:48 folgore /netbsd: wd0(viaide0:0:0): using PIO mode 4,
Ultra-DMA mode 5 (Ultra/100) (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1(viaide0:0:1): using PIO mode 4,
Ultra-DMA mode 5 (Ultra/100) (using DMA)
Jan 3 14:55:48 folgore /netbsd: atapibus0 at atabus1: 2 targets
Jan 3 14:55:48 folgore /netbsd: cd0 at atapibus0 drive 0: <RICOH
DVD+RW MP5240, , 1.11> cdrom removable
Jan 3 14:55:48 folgore /netbsd: cd0: 32-bit data port
Jan 3 14:55:48 folgore /netbsd: cd0: drive supports PIO mode 4, DMA
mode 2, Ultra-DMA mode 2 (Ultra/33)
Jan 3 14:55:48 folgore /netbsd: cd1 at atapibus0 drive 1: <CD-RW
BCE1610IM, , VER 0.1> cdrom removable
Jan 3 14:55:48 folgore /netbsd: cd1: 32-bit data port
Jan 3 14:55:48 folgore /netbsd: cd1: drive supports PIO mode 4, DMA
mode 2, Ultra-DMA mode 2 (Ultra/33)
Jan 3 14:55:48 folgore /netbsd: cd0(viaide0:1:0): using PIO mode 4,
Ultra-DMA mode 2 (Ultra/33) (using DMA)
Jan 3 14:55:48 folgore /netbsd: cd1(viaide0:1:1): using PIO mode 4,
Ultra-DMA mode 2 (Ultra/33) (using DMA)
Jan 3 14:55:48 folgore /netbsd: ugen0 at uhub0 port 2
Jan 3 14:55:48 folgore /netbsd: ugen0: Canon CanoScan, rev 1.10/0.07,
addr 2
Jan 3 14:55:48 folgore /netbsd: wd0: transfer error, downgrading to
Ultra-DMA mode 4
Jan 3 14:55:48 folgore /netbsd: wd0(viaide0:0:0): using PIO mode 4,
Ultra-DMA mode 4 (Ultra/66) (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1(viaide0:0:1): using PIO mode 4,
Ultra-DMA mode 5 (Ultra/100) (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd0d: error reading fsbn 0 (wd0 bn 0;
cn 0 tn 0 sn 0), retrying
Jan 3 14:55:48 folgore /netbsd: wd0: (aborted command, interface CRC
error)
Jan 3 14:55:48 folgore /netbsd: wd0: transfer error, downgrading to
Ultra-DMA mode 3
Jan 3 14:55:48 folgore /netbsd: wd0(viaide0:0:0): using PIO mode 4,
Ultra-DMA mode 3 (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1(viaide0:0:1): using PIO mode 4,
Ultra-DMA mode 5 (Ultra/100) (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd0d: error reading fsbn 0 (wd0 bn 0;
cn 0 tn 0 sn 0), retrying
Jan 3 14:55:48 folgore /netbsd: wd0: (aborted command, interface CRC
error)
Jan 3 14:55:48 folgore /netbsd: wd0: soft error (corrected)
Jan 3 14:55:48 folgore /netbsd: wd1: transfer error, downgrading to
Ultra-DMA mode 4
Jan 3 14:55:48 folgore /netbsd: wd0(viaide0:0:0): using PIO mode 4,
Ultra-DMA mode 3 (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1(viaide0:0:1): using PIO mode 4,
Ultra-DMA mode 4 (Ultra/66) (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1d: error reading fsbn 0 (wd1 bn 0;
cn 0 tn 0 sn 0), retrying
Jan 3 14:55:48 folgore /netbsd: wd1: (aborted command, interface CRC
error)
Jan 3 14:55:48 folgore /netbsd: wd1: transfer error, downgrading to
Ultra-DMA mode 3
Jan 3 14:55:48 folgore /netbsd: wd0(viaide0:0:0): using PIO mode 4,
Ultra-DMA mode 3 (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1(viaide0:0:1): using PIO mode 4,
Ultra-DMA mode 3 (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1d: error reading fsbn 0 (wd1 bn 0;
cn 0 tn 0 sn 0), retrying
Jan 3 14:55:48 folgore /netbsd: wd1: (aborted command, interface CRC
error)
Jan 3 14:55:48 folgore /netbsd: wd1: soft error (corrected)
Jan 3 14:55:48 folgore /netbsd: boot device: wd1
Jan 3 14:55:48 folgore /netbsd: root on wd1g dumps on wd1b
Jan 3 14:55:48 folgore /netbsd: root file system type: ffs
Jan 3 14:55:48 folgore /netbsd: wd1: transfer error, downgrading to
Ultra-DMA mode 2
Jan 3 14:55:48 folgore /netbsd: wd0(viaide0:0:0): using PIO mode 4,
Ultra-DMA mode 3 (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1(viaide0:0:1): using PIO mode 4,
Ultra-DMA mode 2 (Ultra/33) (using DMA)
Jan 3 14:55:48 folgore /netbsd: wd1g: error writing fsbn 16 of 16-18
(wd1 bn 99265651; cn 98477 tn 13 sn 16), retrying
Jan 3 14:55:48 folgore /netbsd: wd1: (aborted command, interface CRC
error)
Jan 3 14:55:48 folgore /netbsd: wd1: soft error (corrected)
Jan 3 14:55:48 folgore savecore: /dev/wd1b: Device not configured
| Quote: | Check to see if there's an upgrade for your BIOS too. Maybe you're
having general PCI weirdness.
've upgraded my bios 6 or 7 months ago.. and never had any problem with |
other OSs :(
Bye!
--- you should stop reading here for you're heart's sake ---
P.S. ok, i know i should stop tainting the kernel... but while i have
nothing better to do... i made some progress:
o) dmesg | grep vr0
vr0 at pci0 dev 11 function 0: VIA VT6105 (Rhine III) 10/100 Ethernet
vr0: interrupting at irq 11
vr0: Ethernet address: 00:40:f4:8e:06:8c
OUI 0x0002c6 model 0x0034 rev 9 at vr0 phy 1 not configured
o) ifconfig -a
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:40:f4:8e:06:8c
media: Ethernet none (none)
inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
o) route show
Routing tables
Internet:
Destination Gateway Flags
default 192.168.0.1 UG
loopback 127.0.0.1 UGR
localhost 127.0.0.1 UH
192.168.0.0/24 link#1 U
192.168.0.1 link#1 UH
192.168.0.2 00:40:f4:8e:06:8c UH
("link#1" what's this???)
o) ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: Host is down
----192.168.0.1 PING Statistics----
11 packets transmitted, 0 packets received, 100.0% packet loss
(maybe i get this bad result because it tries to route towards
"link#1"?) |
|
| Back to top |
|
 |
Joel Reicher *nix forums beginner
Joined: 15 Nov 2005
Posts: 29
|
Posted: Tue Jan 03, 2006 1:51 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
"Alberto" <santini.alberto@gmail.com> writes:
| Quote: | Jan 2 21:34:56 folgore /netbsd: vr0: interrupting at irq 255
irq 225? argh! i didn't noticed this before! this isn't right too! :(
ok, it didn't worked
i can try to force interrupting at irq 11... but will this work?
*mumble*
|
Worth a try, but stop messing with the kernel code. Uncomment those
lines. You should be able to put "irq 11" in the kernel config, just
like everything else.
Cheers,
- Joel |
|
| Back to top |
|
 |
Joel Reicher *nix forums beginner
Joined: 15 Nov 2005
Posts: 29
|
Posted: Tue Jan 03, 2006 1:48 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
"Alberto" <santini.alberto@gmail.com> writes:
| Quote: | p.s. this interrupt mapping issue is *very* common on my machine:
Jan 2 21:34:56 folgore /netbsd: eap0: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ohci0: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ohci1: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ohci2: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ehci0: couldn't map interrupt
i don't think that tricky solution will work for everything!
|
That is *not* normal. I'm thinking BIOS problems, or perhaps something
else misconfigured in your kernel. Perhaps you should post the
complete dmesg output?
Check to see if there's an upgrade for your BIOS too. Maybe you're
having general PCI weirdness.
Cheers,
- Joel |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Tue Jan 03, 2006 12:43 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
IFCONFIG
| Quote: | vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
this is right |
| Quote: | address: 00:40:f4:8e:06:8c
this is right too |
| Quote: | media: Ethernet none (none)
this obviously isn't |
| Quote: | inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
neither is this |
DMESG
| Quote: | Jan 2 21:34:56 folgore /netbsd: vr0: interrupting at irq 255
irq 225? argh! i didn't noticed this before! this isn't right too!  |
ok, it didn't worked
i can try to force interrupting at irq 11... but will this work?
*mumble*
bye! |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Tue Jan 03, 2006 12:35 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
p.s. this interrupt mapping issue is *very* common on my machine:
Jan 2 21:34:56 folgore /netbsd: eap0: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ohci0: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ohci1: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ohci2: couldn't map interrupt
Jan 2 21:34:56 folgore /netbsd: ehci0: couldn't map interrupt
i don't think that tricky solution will work for everything!  |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Mon Jan 02, 2006 8:51 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
ok, prepare yourself... this is what i did after trying for hours
without any result:
1) cd /usr/src/sys/dev/pci
2) study something about pci
3) vi if_vr.c
4) change it:
/*
** Alberto is bypassing this... what will happen??
**
** if (pci_intr_map(pa, &intrhandle)) {
** printf("%s: couldn't map interrupt\n",
** sc->vr_dev.dv_xname);
** return;
** }
*/
/*
** Now, to complete the trick...
*/
intrhandle = pa->pa_intrline;
5) recompile
6) reboot
7) ifconfig vr0 192.168.0.2 ; ifconfig -a
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:40:f4:8e:06:8c
media: Ethernet none (none)
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
8) route add default 192.168.0.1 ; route show
Routing tables
Internet:
Destination Gateway Flags
0.0.0.0/8 link#1 U
default 192.168.0.1 UG
loopback 127.0.0.1 UGR
localhost 127.0.0.1 UH
9) ping 192.168.0.1
It says... "No route to host"
I say... "Argh!"
ok, now there is only this *little* issue to solve! Any suggestion?
p.s. Happy new year!
p.p.s. Brute force sometimes wins  |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Mon Jan 02, 2006 11:35 am Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
thanks joel.. i'll try asap  |
|
| Back to top |
|
 |
Joel Reicher *nix forums beginner
Joined: 15 Nov 2005
Posts: 29
|
Posted: Sun Jan 01, 2006 1:08 am Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
"Alberto" <santini.alberto@gmail.com> writes:
| Quote: | My kernel config says:
mainbus0 at root
pci0 at mainbus0 bus 0
vr0 at pci0 dev 11 function 0
no reference about IRQs.
I have this machine quite far from here... but if you think it would
help i'll change netcard's pci slot and see what dmesg will say,
booting with GENERIC.
|
My only other suggestion is to check in the BIOS setup that the IRQ
allocations for the PCI slots are OK, but that requires going to the
computer as well.
Good luck!
Cheers,
- Joel |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Sat Dec 31, 2005 8:23 am Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
My kernel config says:
mainbus0 at root
pci0 at mainbus0 bus 0
vr0 at pci0 dev 11 function 0
no reference about IRQs.
I have this machine quite far from here... but if you think it would
help i'll change netcard's pci slot and see what dmesg will say,
booting with GENERIC.
Bye! |
|
| Back to top |
|
 |
Joel Reicher *nix forums beginner
Joined: 15 Nov 2005
Posts: 29
|
Posted: Fri Dec 30, 2005 11:58 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
"Alberto" <santini.alberto@gmail.com> writes:
| Quote: | thanks for interesting Joel.. here is the output of "dmesg | grep -i
irq":
viaide0: primary channel interrupting at irq 14
viaide0: secondary channel interrupting at irq 15
uhci0: interrupting at irq 5
uhci1: interrupting at irq 5
lpt0 at isa0 port 0x378-0x37b irq 7
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0: using irq 1 for kbd slot
pckbc0: using irq 12 for aux slot
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
anything useful?
|
Unfortunately not. That all looks quite normal. What does your
kernel config say for vr, by the way? Did you hardcode an irq?
Cheers,
- Joel |
|
| Back to top |
|
 |
Alberto *nix forums beginner
Joined: 10 Mar 2005
Posts: 45
|
Posted: Fri Dec 30, 2005 8:20 pm Post subject:
Re: VIA VT6105 on NetBSD 2.0.2
|
|
|
thanks for interesting Joel.. here is the output of "dmesg | grep -i
irq":
viaide0: primary channel interrupting at irq 14
viaide0: secondary channel interrupting at irq 15
uhci0: interrupting at irq 5
uhci1: interrupting at irq 5
lpt0 at isa0 port 0x378-0x37b irq 7
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0: using irq 1 for kbd slot
pckbc0: using irq 12 for aux slot
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
anything useful?
bye! |
|
| Back to top |
|
 |
Google
|
|
| Back to top |
|
 |
|
|
The time now is Tue Jan 06, 2009 8:36 pm | All times are GMT
|
|
Loans | McDonalds | Debt Consolidation | Guitar Lessons | 0 Credit Cards
|
|
Copyright © 2004-2005 DeniX Solutions SRL
|
|
|
|
Other DeniX Solutions sites:
Unix/Linux blog |
electronics forum |
medicine forum |
science forum |
|
|
Privacy Policy
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|