Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
On 11/09/14 02:52 AM, Ian Campbell wrote: The new networking related bits seem to be marvell.ko and mvmdio.ko. marvell.ko was already packaged in the right place and I added mvmdio.ko yesterday. I remain hopeful that will have solved your issue. Looks like it. The 20140915 daily boots fine and I just completed a successful installation. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
On Wed, 2014-09-10 at 14:14 -0700, Ryan Tandy wrote: On 10/09/14 10:28 AM, Ian Campbell wrote: In the meantime if you could collect the lsmod with a Wheezy kernel for comparison we can check if there is anything else there which ought to be exposed to the installer. Attaching dmesg and report-hw from wheezy and jessie for completeness. Thanks. The new networking related bits seem to be marvell.ko and mvmdio.ko. marvell.ko was already packaged in the right place and I added mvmdio.ko yesterday. I remain hopeful that will have solved your issue. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
On Mon, 2014-09-08 at 22:35 -0700, Ryan Tandy wrote: Booting a Wheezy image is successful and works. I installed Wheezy on the Linkstation using the 7.6 netboot image and upgraded to Jessie successfully, That includes having successfully booted the Jessie kernel judging from the dmesg below? I can see the corresponding lsmod below and looking at it I'm suspicious of mvmdio which is a new module needed for networking on some platforms. I can see it in the kirkwood udebs (installer pkg) but not the orion5xs one which could explain you issue. I've enabled it in the kernel package svn repo just now, but to test you'd need to wait for a new kernel upload and d-i daily using it. Ian. lsmod: Module Size Used by lsmod: hmac2425 0 lsmod: sha1_generic1692 0 lsmod: sha1_arm3318 0 lsmod: ehci_orion 2718 0 lsmod: ehci_hcd 36707 1 ehci_orion lsmod: marvell 5905 0 lsmod: sg 18802 0 lsmod: orion_wdt 2661 0 lsmod: mv_cesa10745 0 lsmod: mv643xx_eth22134 0 lsmod: mvmdio 3024 0 lsmod: usbcore 137224 2 ehci_hcd,ehci_orion lsmod: usb_common 1266 1 usbcore lsmod: loop 14519 0 lsmod: ipv6 291684 12 lsmod: autofs419744 2 lsmod: ext4 329145 2 lsmod: crc16 1097 1 ext4 lsmod: mbcache 4654 1 ext4 lsmod: jbd2 62684 1 ext4 lsmod: sd_mod 34640 4 lsmod: crc_t10dif 948 1 sd_mod lsmod: crct10dif_generic 1142 1 lsmod: crct10dif_common1110 2 crct10dif_generic,crc_t10dif lsmod: sata_mv24700 3 lsmod: libata145076 1 sata_mv lsmod: scsi_mod 133849 3 sg,libata,sd_mod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
On 10/09/14 02:17 AM, Ian Campbell wrote: I'm suspicious of mvmdio which is a new module needed for networking on some platforms. I can see it in the kirkwood udebs (installer pkg) but not the orion5xs one which could explain you issue. I've enabled it in the kernel package svn repo just now, but to test you'd need to wait for a new kernel upload and d-i daily using it. That makes sense, thanks! I'll keep an eye out for the next kernel upload and report back. thanks, Ryan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
On Wed, 2014-09-10 at 08:56 -0700, Ryan Tandy wrote: On 10/09/14 02:17 AM, Ian Campbell wrote: I'm suspicious of mvmdio which is a new module needed for networking on some platforms. I can see it in the kirkwood udebs (installer pkg) but not the orion5xs one which could explain you issue. I've enabled it in the kernel package svn repo just now, but to test you'd need to wait for a new kernel upload and d-i daily using it. That makes sense, thanks! I'll keep an eye out for the next kernel upload and report back. In the meantime if you could collect the lsmod with a Wheezy kernel for comparison we can check if there is anything else there which ought to be exposed to the installer. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
On 10/09/14 10:28 AM, Ian Campbell wrote: In the meantime if you could collect the lsmod with a Wheezy kernel for comparison we can check if there is anything else there which ought to be exposed to the installer. Attaching dmesg and report-hw from wheezy and jessie for completeness. Differences in loaded modules: -aes_generic +autofs4 crc16 crc_t10dif +crct10dif_common +crct10dif_generic ehci_hcd -ext2 +ehci_orion ext4 hmac -inet_lro ipv6 jbd2 libata loop +marvell mbcache mv643xx_eth mv_cesa +mvmdio +orion_wdt sata_mv scsi_mod sd_mod +sg +sha1_arm sha1_generic usb_common usbcore Not sure what's pulling in autofs4. I don't have any autofs userspace pieces installed that I know of. The presence of orion_wdt is interesting; if it actually supports the watchdog on this board that's news to me. Will have to look into that. cheers, Ryan [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.14-2-orion5x (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 Debian 3.14.15-2 (2014-08-09) [0.00] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: Buffalo Linkstation Pro/Live [0.00] Clearing invalid memory bank 0KB@0x [0.00] Clearing invalid memory bank 0KB@0x [0.00] Clearing invalid memory bank 0KB@0x [0.00] Ignoring unrecognised tag 0x [0.00] Ignoring unrecognised tag 0x [0.00] Ignoring unrecognised tag 0x [0.00] Ignoring unrecognised tag 0x41000403 [0.00] Memory policy: Data cache writeback [0.00] On node 0 totalpages: 32768 [0.00] free_area_init_node: node 0, pgdat c04320f4, node_mem_map c7efb000 [0.00] DMA zone: 256 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 32768 pages, LIFO batch:7 [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [0.00] Kernel command line: console=ttyS0,115200 root=/dev/sda2 rw panic=5 BOOTVER=1.10 [0.00] PID hash table entries: 512 (order: -1, 2048 bytes) [0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Memory: 122744K/131072K available (2871K kernel code, 262K rwdata, 996K rodata, 135K init, 261K bss, 8328K reserved) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xc880 - 0xff00 ( 872 MB) [0.00] lowmem : 0xc000 - 0xc800 ( 128 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .text : 0xc0008000 - 0xc03cee10 (3868 kB) [0.00] .init : 0xc03cf000 - 0xc03f0fd4 ( 136 kB) [0.00] .data : 0xc03f2000 - 0xc04338e0 ( 263 kB) [0.00].bss : 0xc04338e0 - 0xc047501c ( 262 kB) [0.00] NR_IRQS:64 [0.22] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns [ 10.393646] Console: colour dummy device 80x30 [ 10.393696] Calibrating delay loop... 264.70 BogoMIPS (lpj=529408) [ 10.429134] pid_max: default: 32768 minimum: 301 [ 10.429372] Security Framework initialized [ 10.429491] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 10.429525] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 10.430759] Initializing cgroup subsys memory [ 10.430824] Initializing cgroup subsys devices [ 10.430854] Initializing cgroup subsys freezer [ 10.430879] Initializing cgroup subsys net_cls [ 10.430903] Initializing cgroup subsys blkio [ 10.430924] Initializing cgroup subsys perf_event [ 10.431060] CPU: Testing write buffer coherency: ok [ 10.431790] Setting up static identity map for 0x2b5910 - 0x2b5968 [ 10.434481] devtmpfs: initialized [ 10.437419] VFP support v0.3: not present [ 10.438562] NET: Registered protocol family 16 [ 10.439594] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 10.441330] Orion ID: MV88F5182-A2. TCLK=16667. [ 10.441844] initial MPP regs: 55220003 03ff [ 10.441895] final MPP regs: 4403 03ff [ 10.451318] bio: create slab bio-0 at 0 [ 10.454657] Switched to clocksource orion_clocksource [ 10.486808] NET: Registered protocol family 2 [ 10.488337] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [ 10.488409] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 10.488466]
Bug#760904: installation-reports: no network on linkstation pro with jessie d-i
Package: installation-reports Severity: normal Dear debian-boot, When I TFTP-boot my Linkstation Pro using a Jessie D-I image, it appears to boot, but it never requests a DHCP address nor responds on the usual default (for this box) IP of 192.168.11.150. (Does D-I use a different fallback IP, if DHCP fails?) This is a headless box with no serial console, so network-console is my only way of talking to it. I do believe at least some parts of the boot are successful, because the power LED stops flashing, the ready beep is emitted, and the fan speed slows down, all of which lead me to believe that micro-evtd is running and working properly. I tried the Jessie alpha-1 and beta-1 images, and the latest (2014-Sep-07) daily image, and had the same result on all of them. Booting a Wheezy image is successful and works. I installed Wheezy on the Linkstation using the 7.6 netboot image and upgraded to Jessie successfully, and am filing the report from that system. So please note that the installer-related information below may reflect the Wheezy D-I environment. (The report-hw output is fresh; I re-ran it after upgrading to Jessie.) Like I wrote above, I don't have serial access and depend on network-console for performing installations, so I'm not sure how to go about troubleshooting or retrieving more information from the installer environment. Any suggestions for what I should try next? thanks, Ryan -- Package-specific info: Boot method: TFTP Image version: http://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/buffalo/lspro/initrd.buffalo dated 07-Sep-2014 Date: Date and time of the install Machine: Buffalo Linkstation Pro (LS-GL) Partitions: Device Boot Start End Blocks Id System /dev/sda1 *2048 499711 248832 83 Linux /dev/sda2 499712 624408575 311954432 83 Linux /dev/sda3 624410622 625141759 3655695 Extended /dev/sda5 624410624 625141759 365568 82 Linux swap / Solaris Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [E] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7 (wheezy) - installer build 20130613+deb7u2+b1 X_INSTALLATION_MEDIUM=network-console == Installer hardware-summary: == uname -a: Linux xenon 3.14-2-orion5x #1 Debian 3.14.15-2 (2014-08-09) armv5tel GNU/Linux usb-devices: usb-devices: T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1 usb-devices: D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 nusb-devices: P: Vendor=1d6b ProdID=0002 Rev=03.14 usb-devices: S: Manufacturer=Linux 3.14-2-orion5x ehci_hcd usb-devices: S: Product=EHCI Host Controller usb-devices: S: SerialNumber=orion-ehci.0 usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA usb-devices: I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub usb-devices: usb-devices: T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1 usb-devices: D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 usb-devices: P: Vendor=1d6b ProdID=0002 Rev=03.14 usb-devices: S: Manufacturer=Linux 3.14-2-orion5x ehci_hcd usb-devices: S: Product=EHCI Host Controller usb-devices: S: SerialNumber=orion-ehci.1 usb-devices: C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA usb-devices: I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub lsmod: Module Size Used by lsmod: hmac2425 0 lsmod: sha1_generic1692 0 lsmod: sha1_arm3318 0 lsmod: ehci_orion 2718 0 lsmod: ehci_hcd 36707 1 ehci_orion lsmod: marvell 5905 0 lsmod: sg 18802 0 lsmod: orion_wdt 2661 0 lsmod: mv_cesa10745 0 lsmod: mv643xx_eth22134 0 lsmod: mvmdio 3024 0 lsmod: usbcore 137224 2 ehci_hcd,ehci_orion lsmod: usb_common 1266 1 usbcore lsmod: loop 14519 0 lsmod: ipv6 291684 12 lsmod: autofs4
