On Sun, 15 Jul 2007 22:42:43 +0100, Mike Williams wrote:

> On Sunday 15 July 2007 22:00:15 Hendrik Boom wrote:
>> Fixed /etc/fstab so that it now refers to /dev/lovesong/gentoo.  And fstab
>> gets the message, because it now complains that there's no
>> /dev/lovesong/gentoo.  And when I get a shell, I discover that it's
>> right.  There is now no /etc/lovesong at all.  /dev/mapper exists, but it
>> contains only /dev/mapper/control.
>>
>> using your workaround of changing the pass from 1 to 0 in the /etc/fstab
>> file, it boots.  But I still have no access to the other partitions on
>> the disk.  I still have no /dev/lovesong. except of course that
>> /dev/lovesong/gentoo has been mounted.  And /dev/mapper still contains
>> only /dev/mapper/control.
> 
> Hmm, more interesting.
> Sounds like you don't have lvm2 (sys-fs/lvm2) installed. Genkernel pulls it's 
> own version in to build the initrd/ramfs, but the actual install will need it 
> merged separately to "start" LVM at boot.
> If you get Gentoo booted you could try manually "starting" LVM:
> vgscan
> pvscan
> vgchange -ay
> 
> It's vgchange -ay that makes all logical volumes in all volume groups 
> available, the two scans just makes sure device mapper is aware of all 
> devices and volumes.
> 
> -- 
> Mike Williams

It took some trouble -- as of now I only have emerge working in the chroot
from Debian -- but after installing lvm2 it is not cheerfully recognising
all the LVM paritions at boot.

Now for the next problem.  emerge doesn't work because the net connexion
is down.  Presulably it would be OK if I had a local repository, but iI
don't.

If I ping my internet gateway machine, 172.25.1.1. it tells me 

PING 172.25.1.1 (172.25.1.1) 56(84) bytes of data.

--- 172.25.1.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2003ms

whereas when I do the same from Debian, 

PING 172.25.1.1 (172.25.1.1) 56(84) bytes of data.
64 bytes from 172.25.1.1: icmp_seq=1 ttl=255 time=0.811 ms
64 bytes from 172.25.1.1: icmp_seq=2 ttl=255 time=0.364 ms

--- 172.25.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.364/0.587/0.811/0.224 ms

Here's the routing table, obtained with route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
172.25.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         172.25.1.1      0.0.0.0         UG    0      0        0 eth0

And the same from Debian:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
172.25.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth1
0.0.0.0         172.25.1.1      0.0.0.0         UG    0      0        0 eth1

Except for lo (which I can wonder about anon) the most striking difference
is that gentoo uses eth0; whereas Debian uses eth1.

Now as far as I know, there's only one ethernet interface on this machine.
But I could be wrong.  I do know that there's just one place to plug the
cable into the back.

Running ifconfig to find out more, especially to see if the MAC addresses
are different:

On gentoo:

eth0      Link encap:UNSPEC  HWaddr 
00-06-BB-00-16-03-49-D6-00-00-00-00-00-00-00-00  
          inet addr:172.25.1.4  Bcast:172.25.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:288 (288.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:448 (448.0 b)  TX bytes:448 (448.0 b)


and on Debian:

eth1      Link encap:Ethernet  HWaddr 00:0C:6E:50:27:B1
          inet addr:172.25.1.4  Bcast:172.25.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:6eff:fe50:27b1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:33028 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32429 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:26715240 (25.4 MiB)  TX bytes:25032114 (23.8 MiB)
          Interrupt:177 Base address:0xc000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:54 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4468 (4.3 KiB)  TX bytes:4468 (4.3 KiB)

Now that's a surprise.  Quite sone difference!  Debian gives ma an
ordinary 48-bit hardware address.  Gentoo gives a 128-bit hardware
address!  And the bits of the 48-bit address aren't even recognisable
in the 128-bit address.  Now I understand that hardware addresses have been
getting longer, but O haven't been adding ethernet chips to this machine
since I bought it, so they should all be of the same vintage.

What gives?

Here's the output from gentoo-s lspci -v:

00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev 
c1)
        Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
        Flags: bus master, 66MHz, fast devsel, latency 0
        Memory at e8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [40] AGP version 2.0
        Capabilities: [60] HyperTransport: Host or Secondary Interface

00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 0 (rev c1)
        Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
        Flags: 66MHz, fast devsel

00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
        Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
        Flags: 66MHz, fast devsel

00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
        Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
        Flags: 66MHz, fast devsel

00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
        Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
        Flags: 66MHz, fast devsel

00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
        Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
        Flags: 66MHz, fast devsel

00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
        Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
        Flags: bus master, 66MHz, fast devsel, latency 0
        Capabilities: [48] HyperTransport: Slave or Primary Interface

00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
        Subsystem: ASUSTeK Computer Inc. Unknown device 0c11
        Flags: 66MHz, fast devsel, IRQ 11
        I/O ports at e400 [size=32]
        Capabilities: [44] Power Management version 2

00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 
(prog-if 10 [OHCI])
        Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17
        Memory at ef004000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [44] Power Management version 2

00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 
(prog-if 10 [OHCI])
        Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 18
        Memory at ef005000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [44] Power Management version 2

00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 
(prog-if 20 [EHCI])
        Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 16
        Memory at ef000000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [44] Debug port
        Capabilities: [80] Power Management version 2

00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller 
(rev a1)
        Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard onboard nForce2 
Ethernet
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 16
        Memory at ef001000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at d000 [size=8]
        Capabilities: [44] Power Management version 2

00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio 
Controler (MCP) (rev a1)
        Subsystem: ASUSTeK Computer Inc. Unknown device 8095
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17
        I/O ports at d400 [size=256]
        I/O ports at d800 [size=128]
        Memory at ef002000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [44] Power Management version 2

00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) 
(prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, fast devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=32

00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a 
[Master SecP PriP])
        Subsystem: ASUSTeK Computer Inc. Unknown device 0c11
        Flags: bus master, 66MHz, fast devsel, latency 0
        [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] 
[size=8]
        [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] 
[size=1]
        [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] 
[size=8]
        [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] 
[size=1]
        I/O ports at f000 [size=16]
        Capabilities: [44] Power Management version 2

00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) (prog-if 00 [Normal 
decode])
        Flags: bus master, 66MHz, medium devsel, latency 32
        Bus: primary=00, secondary=02, subordinate=03, sec-latency=32
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: ec000000-eeffffff
        Prefetchable memory behind bridge: e0000000-e7ffffff

02:00.0 VGA compatible controller: ATI Technologies Inc R200 BB [Radeon All in 
Wonder 8500DV] (prog-if 00 [VGA])
        Subsystem: ATI Technologies Inc Radeon 8500 AIW DV Edition
        Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 5
        Memory at e0000000 (32-bit, prefetchable) [size=128M]
        I/O ports at c000 [size=256]
        Memory at ee000000 (32-bit, non-prefetchable) [size=128K]
        Memory at ee020000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at ec000000 [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2

02:00.1 PCI bridge: ATI Technologies Inc R200 BC [Radeon All in Wonder 8500] 
(prog-if 00 [Normal decode])
        Flags: bus master, stepping, 66MHz, medium devsel, latency 32
        Bus: primary=02, secondary=03, subordinate=03, sec-latency=32
        Memory behind bridge: ed000000-edffffff
        Capabilities: [50] Power Management version 2

03:00.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 04) (prog-if 10 [OHCI])
        Subsystem: ATI Technologies Inc Unknown device 5811
        Flags: bus master, medium devsel, latency 32, IRQ 19
        Memory at ed000000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [44] Power Management version 2

Only one ethernet controllser visible.  Ans except for a different IRQ,
it's remarkably similar to what Debian says:

......

00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller 
(rev a1)
        Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard onboard nForce2 
Ethernet
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 177
        Memory at ef001000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at d000 [size=8]
        Capabilities: [44] Power Management version 2
......

Evidently something is still wrong.  How do I begin to diagnose this?

-- hendrik

-- 
[EMAIL PROTECTED] mailing list

Reply via email to