[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#265183: marked as done (sarge-rc1 on ASUS laptop L8400-B - pppoe/ADSL networking troubles and other minor stuff)



Your message dated Wed, 08 Sep 2010 03:57:34 +0000
with message-id <E1OtBmw-0003qk-EO@ravel.debian.org>
and subject line Closing old installation report #265183
has caused the Debian Bug report #265183,
regarding sarge-rc1 on ASUS laptop L8400-B - pppoe/ADSL networking troubles and other minor stuff
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
265183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=265183
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal

INSTALL REPORT

Debian-installer-version: sarge rc1 rel 7Aug04, d/l from a mirror off debian.org
uname -a: 
	Linux travel 2.4.26-1-386 #1 Thu Jul 22 12:46:23 JST 2004 i686 GNU/Linux
Date: Thu Aug 12 04:52:41 IDT 2004
Method: 
	booted using the current sid boot.img, then it recognized a memory
	stick I had prepared with the sarge-i386-netinst.iso on it
	Network install then fetched stuff from the Israeli HTTP mirror
	(but see below for tweaks needed to have it work!)

Machine: ASUS L8400-B, BIOS rev 0103
Processor: P/III
Memory: 128Mb
Root Device: /dev/hda
Root Size/partition table:
major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse running use aveq

   8     0     249600 scsi/host1/bus0/target0/lun0/disc 25 1216 2482 3230 4 0 8 20 0 1880 3250
   8     1     132705 scsi/host1/bus0/target0/lun0/part1 0 0 0 0 0 0 0 0 0 0 0
   8     2     116632 scsi/host1/bus0/target0/lun0/part2 24 1213 2474 3220 4 0 8 20 0 1870 3240
   3     0   11789568 ide/host0/bus0/target0/lun0/disc 41522 237454 1999578 744640 30313 341332 2412476 14840280 -1 4207000 11218840
   3     1    4672048 ide/host0/bus0/target0/lun0/part1 0 0 0 0 0 0 0 0 0 0 0
   3     2          1 ide/host0/bus0/target0/lun0/part2 0 0 0 0 0 0 0 0 0 0 0
   3     5    1013008 ide/host0/bus0/target0/lun0/part5 0 0 0 0 0 0 0 0 0 0 0
   3     6      15057 ide/host0/bus0/target0/lun0/part6 26 551 1154 840 8 1 18 20 0 650 860
   3     7    1171768 ide/host0/bus0/target0/lun0/part7 2959 35147 76236 56490 4356 89363 187586 560360 0 59680 616850
   3     8     377968 ide/host0/bus0/target0/lun0/part8 1793 8193 79888 31420 1272 15359 134072 72610 0 29950 104140
   3     9    4535968 ide/host0/bus0/target0/lun0/part9 36738 193545 1842252 655770 24677 236609 2090800 14207290 0 439130 14863070
   3    64     655364 hdb 0 0 0 0 0 0 0 0 -9 4348130 3816632

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda9       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda6       /boot           ext3    defaults        0       2
/dev/hda7       /var            ext3    defaults        0       2
/dev/hda8       none            swap    sw              0       0
/dev/hdb        /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
/dev/sda1       /media/usb0     auto    rw,user,noauto  0       0
/dev/sda        /media/usb1     auto    rw,user,noauto  0       0

Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
0000:00:06.0 Multimedia audio controller: Aureal Semiconductor AU8810 Vortex Digital Audio Processor (rev 03)
0000:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
0000:00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
0000:00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
0000:01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/MX-MV (rev 11)

0000:00:00.0 0600: 8086:7190 (rev 03)
0000:00:01.0 0604: 8086:7191 (rev 03)
0000:00:06.0 0401: 12eb:0003 (rev 03)
0000:00:07.0 0601: 8086:7110 (rev 02)
0000:00:07.1 0101: 8086:7111 (rev 01)
0000:00:07.2 0c03: 8086:7112 (rev 01)
0000:00:07.3 0680: 8086:7113 (rev 03)
0000:00:08.0 0200: 10ec:8139 (rev 10)
0000:00:0a.0 0607: 1180:0476 (rev 80)
0000:00:0a.1 0607: 1180:0476 (rev 80)
0000:01:00.0 0300: 5333:8c10 (rev 11)

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [E]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]

Comments/Problems:
1) Why I didn't boot from the stick directly.
This being a university laptop I borrowed for a travel, I didn't want to get
stuck if smth goes wrong during the flash bios upgrade. Hence I couldn't boot
off the USB memory stick directly, but rather used the boot floppy. Once it
booted, it recognized the plugged in USB drive like a charm.  Maybe it would be
better if d-i didn't ask for pressing enter if the USB drive is already in and
recognized.

2) Weird partition size issues on the USB stick.
The stick image (I used the quick method of dumping the USB stick image
onto /dev/sda1) produced an interesting effect  on my 256Mb stick: df showed
that the partition is 128Mb and near-full, fdisk/cfdisk showed it's 256Mb,
and the partition diagnostic tools never reported any problem with it.

3) Detailed report on the network configuration problem
In my case, the computer correctly recognized the LAN, but the
LAN is actually a duplex link to my ADSL modem, which
gave out the DHCP address to the computer. I then manually
ran pppoeconf. Decided not to enable it on boot, otherwise all
was default. After that, tried pon-dslprovider, as per the package
suggestion. PPPOE link established, but routing broken:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
212.143.208.130 0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         10.0.0.138      0.0.0.0         UG    0      0        0 eth0

.138 is the ADSL modem on the LAN duplex link.

DNS doesn't work as the DNS has been overridden by the pppd to the provider
servers:
	nameserver 212.143.212.143
	nameserver 194.90.1.5
	search lan
The problem was that the route to the cable
modem is via a DHCP-discovered interface, as per the interfaces(5):
	# This file describes the network interfaces available on your system
	# and how to activate them. For more information, see interfaces(5).

	# The loopback network interface
	auto lo
	iface lo inet loopback

	# The primary network interface
	auto eth0
	iface eth0 inet dhcp

So it is no wonder that once the PPP starts, it refuses to remove the default
route:
	Aug 11 23:03:57 localhost pppd[1448]: Couldn't increase MTU to 1500
	Aug 11 23:03:57 localhost pppd[1448]: Couldn't increase MRU to 1500
	Aug 11 23:03:57 localhost pppd[1448]: PAP authentication succeeded
	Aug 11 23:03:57 localhost pppd[1448]: peer from calling number 00:02:3B:02:65:D6 authorized
	Aug 11 23:03:57 localhost pppd[1448]: not replacing default route to eth0 [10.0.0.138]
	Aug 11 23:03:57 localhost pppd[1448]: Cannot determine ethernet address for proxy ARP
	Aug 11 23:03:57 localhost pppd[1448]: local  IP address 212.235.113.82
	Aug 11 23:03:57 localhost pppd[1448]: remote IP address 212.143.208.130
	Aug 11 23:03:57 localhost pppd[1448]: primary   DNS address 212.143.212.143
	Aug 11 23:03:57 localhost pppd[1448]: secondary DNS address 194.90.1.5

As a workaround, used a static address in interfaces(5):
	# This file describes the network interfaces available on your system
	# and how to activate them. For more information, see interfaces(5).

	# The loopback network interface
	auto lo
	iface lo inet loopback

	# The primary network interface
	auto eth0
	#iface eth0 inet dhcp
	iface eth0 inet static
		address 10.0.0.2
		netmask 255.0.0.0

I'll use netenv or one of the other packages in the laptop category to
manage multiple conn-s (this laptop will also be dialing in and directly
connected to real LANs). After later reboot, pon dsl-provider doesn't work,
here's the log
	Aug 12 04:09:31 localhost pppd[965]: Plugin rp-pppoe.so loaded.
	Aug 12 04:09:31 localhost kernel: CSLIP: code copyright 1989 Regents of the University of California
	Aug 12 04:09:32 localhost kernel: PPP generic driver version 2.4.2
	Aug 12 04:09:32 localhost pppd[965]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
	Aug 12 04:09:32 localhost pppd[969]: pppd 2.4.2 started by root, uid 0
	Aug 12 04:09:32 localhost pppd[969]: PPP session is 3179
	Aug 12 04:09:32 localhost pppd[969]: Failed to create PPPoE socket: Address family not supported by protocol

However, if one launches pppoeconf and then says "yes" to whether pppoe
should be started now, everything is OK. 

4) missing packages
I think that anacron should have been suggested by the install routine,
esp. once it noticed that the laptop is dual-boot (it actually mentioned
the fact at the grub configuration stage).

Same with gpm. Especially when I didn't install any X stuff during the
initial installation sequence (later on I did add and configure X,
worked out of the box).

5) Consequences of selecting cyrillic-task:
5.1) console-cyrillic: used defaults all the way. The console
gets garbled once cyrillic is loaded and anything like bold/underline
is attempted, say, when reading a manpage. This comes even before I try
looking at a Cyrillic text! Meanwhile I have disabled console-cyrillic
to load on boot to work it around. Looks specific to UTF-8, in KOI-8 it 
doesn't hapen. NOTE: I don't use the framebuffer.
5.2) mueller7-dict (sugg-ed by the cyrillic task) complained because of the
missing russian UTF-8 locale:
  No UTF-8 locale found!                                                    
                                                                            
  You are installing the German-English dictd(8) dictionary, which is       
  UTF-8 encoded.  To get this working, dictd(8) has to be called with the   
  parameter --locale=ru_RU.UTF-8 (or any other UTF-8 supporting locale).    
  There was no UTF-8 locale found in your /etc/locale.gen and the           
  parameter --locale=xx_YY.UTF-8 was not set in your /etc/defaults/dictd,   
  so after installing this package dictd may stop working.                  
                                                                            
  Install a UTF-8 locale (using "dpkg-reconfigure locales") and add the     
  "--locale=xx_YY.UTF-8" option to DICTD_ARGS in /etc/defaults/dictd by     
  hand!                                                                     
Locales package must get configured ahead of this one!! For some reason,
I never got a prompt to reconfigure locales.  I remember that in beta3 I
did get such a prompt, it was very nice.

6) Sound didn't get configured properly after the installation
routine. The system beeps work, but if I try to bplay a wav, it says
/dev/dsp - no such device. I have seen success reports of people
configuring sound on this hardware manually, so I have no reason
to be pessimistic here - but this is not ready for the end-user of
such hardware IMHO.



--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.



--- End Message ---

Reply to: