Welcome! Log In Create A New Profile

Advanced

wireless initramfs problem after upgrade to stretch from jessie

Posted by metric 
wireless initramfs problem after upgrade to stretch from jessie
December 05, 2017 01:34AM
I have a dockstar booting from a USB card reader & 2 GB CF card.

Netconsole shows uboot version as follows.

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709


I was holding out for long time to upgrade from jesie to stretch. I finally gave in. Everything went smooth except following.

My wireless card stopped working. dmesg says

rt2800usb 1-1.4.3.3:1.0: firmware: agent aborted loading rt2870.bin (not found?)

It is supposed to be in firmware-misc-nonfree package according to Debian Wiki

This package is installed but I tried to reinstall it.Then I get the following hook message.

Preparing to unpack .../firmware-misc-nonfree_20161130-3_all.deb ...
Unpacking firmware-misc-nonfree (20161130-3) over (20161130-3) ...
Setting up firmware-misc-nonfree (20161130-3) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-kirkwood
Warning: couldn't identify filesystem type for fsck hook, ignoring.
I: The initramfs will attempt to resume from /dev/sda2

My fstab entry is as follows.
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/root       /               ext4    noatime,nodiratime,errors=remount-ro 0 1

So edited /etc/fstab.

I then tried uuid and fstype as (ext4 and also as auto)

I get

update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-kirkwood
Warning: couldn't identify filesystem type for fsck hook, ignoring.
Press Return to continue, 'q' followed by Return to quit.


How do I fix the hook and the wireless card issue?
Re: wireless initramfs problem after upgrade to stretch from jessie
December 05, 2017 01:47AM
metric,

Which kernel are you running? Please post output of

dmesg
cat /etc/apt/sources.list

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: wireless initramfs problem after upgrade to stretch from jessie
December 05, 2017 11:01AM
Hi Bodhi,

The setup was working fine with Jessie. There is no change in the hardware.

It is a stock kernel that came with the upgrade.
Linux dstar 3.2.0-4-kirkwood #1 Debian 3.2.68-1+deb7u2 armv5tel

sources.list
# deb http://cdn.debian.net/debian jessie main contrib non-free
# deb http://ftp.debian.org/debian jessie-backports main
deb http://mirrors.kernel.org/debian stretch main contrib non-free
deb http://security.debian.org/debian-security stretch/updates main contrib non-free
# deb http://cdn.debian.net/debian jessie main contrib non-free
# deb http://ftp.debian.org/debian jessie-backports main
# deb http://mirrors.kernel.org/debian jessie main contrib non-free
# deb http://security.debian.org/debian-security jessie/updates main contrib non-free

The firmware bin file does exist on the drive at

/lib/firmware/rt2870.bin

Here is the output of lsmod
Module                  Size  Used by
arc4                    1072  2
rndis_wlan             23302  0
snd_usb_audio          74961  0
rt2800usb              11843  0
rt2x00usb               7696  1 rt2800usb
rt2800lib              41408  1 rt2800usb
snd_usbmidi_lib        15427  1 snd_usb_audio
snd_hwdep               5165  1 snd_usb_audio
rt2x00lib              30669  3 rt2800lib,rt2x00usb,rt2800usb
snd_rawmidi            15758  1 snd_usbmidi_lib
mac80211              205687  3 rt2x00lib,rt2800lib,rt2x00usb
snd_pcm                57532  1 snd_usb_audio
snd_page_alloc          4699  1 snd_pcm
rndis_host              5325  1 rndis_wlan
snd_seq                41501  0
snd_seq_device          4683  2 snd_seq,snd_rawmidi
btusb                  10943  0
snd_timer              15155  2 snd_seq,snd_pcm
cdc_ether               3348  1 rndis_host
usbnet                 13267  3 cdc_ether,rndis_host,rndis_wlan
snd                    44456  8 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_rawmidi,snd_hwdep,snd_usbmidi_lib,snd_usb_audio
cfg80211              151548  3 mac80211,rt2x00lib,rndis_wlan
bluetooth             131911  1 btusb
crc_ccitt               1125  1 rt2800lib
rfkill                 14262  3 bluetooth,cfg80211
mii                     3513  1 usbnet
soundcore               4752  1 snd
hmac                    2427  0
sha1_generic            1740  0
mv_cesa                 9361  0
aes_generic            27588  1 mv_cesa
ip_tables               9560  0
x_tables               11483  1 ip_tables
ipv6                  261864  22
autofs4                19478  2
ext4                  377913  1
jbd2                   65937  1 ext4
mbcache                 4464  1 ext4
sg                     18421  0
sd_mod                 31028  3
crc_t10dif              1110  1 sd_mod
usb_storage            35997  2
scsi_mod              149469  3 usb_storage,sd_mod,sg
ehci_hcd               38151  0
usbcore               123016  12 ehci_hcd,usb_storage,usbnet,cdc_ether,btusb,rndis_host,snd_usbmidi_lib,rt2x00usb,rt2800usb,snd_usb_audio,rndis_wlan
usb_common               648  1 usbcore
mv643xx_eth            22806  0
inet_lro                4272  1 mv643xx_eth
libphy                 14472  1 mv643xx_eth


Here is the output of dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.2.0-4-kirkwood (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.2.68-1+deb7u2
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate FreeAgent DockStar
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c0445fbc, node_mem_map c04ad000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32512 pages, LIFO batch:7
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext4 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 118180k/118180k available, 12892k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xfe800000   ( 864 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc03e85b0   (3970 kB)
[    0.000000]       .init : 0xc03e9000 - 0xc040d000   ( 144 kB)
[    0.000000]       .data : 0xc040e000 - 0xc0448d20   ( 236 kB)
[    0.000000]        .bss : 0xc0448d44 - 0xc04ac3d4   ( 398 kB)
[    0.000000] NR_IRQS:114
[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
[    0.000000] Console: colour dummy device 80x30
[   13.251056] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[   13.340941] pid_max: default: 32768 minimum: 301
[   13.341067] Security Framework initialized
[   13.341146] Mount-cache hash table entries: 512
[   13.341481] Initializing cgroup subsys cpuacct
[   13.341506] Initializing cgroup subsys memory
[   13.341531] Initializing cgroup subsys devices
[   13.341541] Initializing cgroup subsys freezer
[   13.341549] Initializing cgroup subsys net_cls
[   13.341558] Initializing cgroup subsys blkio
[   13.341577] Initializing cgroup subsys perf_event
[   13.341670] CPU: Testing write buffer coherency: ok
[   13.342979] devtmpfs: initialized
[   13.344811] print_constraints: dummy: 
[   13.345063] NET: Registered protocol family 16
[   13.345848] Kirkwood: MV88F6281-A0, TCLK=200000000.
[   13.345862] Feroceon L2: Enabling L2
[   13.345898] Feroceon L2: Cache support initialised.
[   13.346490] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
[   13.346512]   final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
[   13.348724] bio: create slab <bio-0> at 0
[   13.349105] vgaarb: loaded
[   13.349631] Switching to clocksource orion_clocksource
[   13.363845] NET: Registered protocol family 2
[   13.374193] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[   13.374810] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[   13.374910] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[   13.374962] TCP: Hash tables configured (established 4096 bind 4096)
[   13.374971] TCP reno registered
[   13.374981] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   13.375002] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   13.375209] NET: Registered protocol family 1
[   13.375240] PCI: CLS 0 bytes, default 32
[   13.375395] Unpacking initramfs...
[   13.949794] Freeing initrd memory: 6940K
[   13.949809] NetWinder Floating Point Emulator V0.97 (double precision)
[   13.950342] audit: initializing netlink socket (disabled)
[   13.950383] type=2000 audit(0.690:1): initialized
[   13.951800] VFS: Disk quotas dquot_6.5.2
[   13.951885] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   13.952005] JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   13.952327] msgmni has been set to 244
[   13.953859] alg: No test for stdrng (krng)
[   13.953976] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[   13.953989] io scheduler noop registered
[   13.953997] io scheduler deadline registered
[   13.954050] io scheduler cfq registered (default)
[   13.954126] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   13.954159] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   13.989700] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   14.029697] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   14.069696] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   14.109696] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   14.110080] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   14.130643] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   14.557531] console [ttyS0] enabled
[   14.561998] ONFI flash detected
[   14.565243] ONFI param page 0 valid
[   14.568753] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08AAD)
[   14.576465] Scanning device for bad blocks
[   14.640664] Bad eraseblock 808 at 0x000006500000
[   14.737348] 4 cmdlinepart partitions found on MTD device orion_nand
[   14.743656] Creating 4 MTD partitions on "orion_nand":
[   14.748826] 0x000000000000-0x000000100000 : "u-boot"
[   14.754666] 0x000000100000-0x000000500000 : "uImage"
[   14.760498] 0x000000500000-0x000002500000 : "rootfs"
[   14.766291] 0x000002500000-0x000010000000 : "data"
[   14.772785] mousedev: PS/2 mouse device common for all mice
[   15.779733] rtc-mv rtc-mv: internal RTC not ticking
[   15.784729] i2c /dev entries driver
[   15.788363] cpuidle: using governor ladder
[   15.792569] cpuidle: using governor menu
[   15.796652] Registered led device: dockstar:green:health
[   15.796754] Registered led device: dockstar:orange:misc
[   15.797513] TCP cubic registered
[   15.800775] NET: Registered protocol family 17
[   15.805249] Registering the dns_resolver key type
[   15.810019] Gating clock of unused units
[   15.810028] before: 0x00dfc3fd
[   15.810035]  after: 0x00c701c9
[   15.810471] registered taskstats version 1
[   15.814964] /build/linux-FLh_5z/linux-3.2.68/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   15.824209] Initializing network drop monitor service
[   15.829939] Freeing init memory: 144K
[   15.890252] udevd[48]: starting version 175
[   15.938706] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   16.040069] mv643xx_eth smi: probed
[   16.066554] usbcore: registered new interface driver usbfs
[   16.098876] mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:10:75:1a:11:40
[   16.111591] usbcore: registered new interface driver hub
[   16.134489] usbcore: registered new device driver usb
[   16.159423] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   16.193977] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   16.199300] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   16.249708] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   16.269673] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   16.275690] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   16.282526] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.289791] usb usb1: Product: Marvell Orion EHCI
[   16.294515] usb usb1: Manufacturer: Linux 3.2.0-4-kirkwood ehci_hcd
[   16.300821] usb usb1: SerialNumber: orion-ehci.0
[   16.306352] hub 1-0:1.0: USB hub found
[   16.310153] hub 1-0:1.0: 1 port detected
[   16.629681] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   16.781092] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   16.787825] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   16.795005] usb 1-1: Product: USB2.0 Hub
[   16.803143] hub 1-1:1.0: USB hub found
[   16.813463] hub 1-1:1.0: 4 ports detected
[   17.089989] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[   17.378216] usb 1-1.2: New USB device found, idVendor=048d, idProduct=1336
[   17.385142] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.392511] usb 1-1.2: Product: Mass Storage Device
[   17.397412] usb 1-1.2: Manufacturer: Generic   
[   17.401974] usb 1-1.2: SerialNumber: 00000000000006
[   17.432735] SCSI subsystem initialized
[   17.441455] Initializing USB Mass Storage driver...
[   17.446654] scsi0 : usb-storage 1-1.2:1.0
[   17.452235] usbcore: registered new interface driver usb-storage
[   17.458267] USB Mass Storage support registered.
[   17.490004] usb 1-1.4: new high-speed USB device number 4 using orion-ehci
[   17.600098] usb 1-1.4: New USB device found, idVendor=0409, idProduct=005a
[   17.607007] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   17.618174] hub 1-1.4:1.0: USB hub found
[   17.628744] hub 1-1.4:1.0: 4 ports detected
[   17.909864] usb 1-1.4.3: new high-speed USB device number 5 using orion-ehci
[   18.040097] usb 1-1.4.3: New USB device found, idVendor=0409, idProduct=005a
[   18.047175] usb 1-1.4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   18.058691] hub 1-1.4.3:1.0: USB hub found
[   18.069494] hub 1-1.4.3:1.0: 3 ports detected
[   18.169886] usb 1-1.4.4: new high-speed USB device number 6 using orion-ehci
[   18.300466] usb 1-1.4.4: New USB device found, idVendor=17ef, idProduct=3033
[   18.307546] usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   18.315077] usb 1-1.4.4: Product: dCute Composite Device
[   18.320449] usb 1-1.4.4: Manufacturer: ST/Lenovo
[   18.429876] usb 1-1.4.3.2: new full-speed USB device number 7 using orion-ehci
[   18.561108] usb 1-1.4.3.2: New USB device found, idVendor=0a12, idProduct=0001
[   18.568369] usb 1-1.4.3.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   18.659876] usb 1-1.4.3.3: new high-speed USB device number 8 using orion-ehci
[   18.805843] usb 1-1.4.3.3: New USB device found, idVendor=148f, idProduct=3070
[   18.813111] usb 1-1.4.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   18.820835] usb 1-1.4.3.3: Product: 802.11 n WLAN
[   18.825556] usb 1-1.4.3.3: Manufacturer: Ralink
[   18.830119] usb 1-1.4.3.3: SerialNumber: 1.0
[   19.261448] scsi 0:0:0:0: Direct-Access     Generic  Storage Device   0.00 PQ: 0 ANSI: 2
[   19.286017] sd 0:0:0:0: [sda] 3940272 512-byte logical blocks: (2.01 GB/1.87 GiB)
[   19.293991] sd 0:0:0:0: [sda] Write Protect is off
[   19.298801] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[   19.299239] sd 0:0:0:0: [sda] No Caching mode page found
[   19.304587] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   19.314360] sd 0:0:0:0: [sda] No Caching mode page found
[   19.319731] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   19.327621]  sda: sda1 sda2
[   19.333365] sd 0:0:0:0: [sda] No Caching mode page found
[   19.338703] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   19.344845] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   19.360491] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   26.407889] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   26.882035] systemd[1]: System time before build time, advancing clock.
[   26.993726] NET: Registered protocol family 10
[   27.010294] ip_tables: (C) 2000-2006 Netfilter Core Team
[   27.042179] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[   27.060649] systemd[1]: Detected architecture arm.
[   27.090712] systemd[1]: Set hostname to <dstar>.
[   27.688530] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[   27.720195] systemd[1]: Listening on Journal Socket.
[   27.740533] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[   27.770506] systemd[1]: user.slice: Failed to set invocation ID on control group /user.slice, ignoring: Operation not supported
[   27.782146] systemd[1]: Created slice User and Session Slice.
[   27.810173] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[   27.840034] systemd[1]: Listening on fsck to fsckd communication Socket.
[   27.870112] systemd[1]: Listening on udev Control Socket.
[   27.899994] systemd[1]: Listening on udev Kernel Socket.
[   27.930293] systemd[1]: Listening on Journal Audit Socket.
[   27.960281] systemd[1]: system.slice: Failed to set invocation ID on control group /system.slice, ignoring: Operation not supported
[   27.972337] systemd[1]: Created slice System Slice.
[   28.000934] systemd[1]: systemd-fsck-root.service: Failed to set invocation ID on control group /system.slice/systemd-fsck-root.service, ignoring: Operation not supported
[   28.018200] systemd[1]: Starting File System Check on Root Device...
[   28.041606] systemd[1]: sys-kernel-debug.mount: Failed to set invocation ID on control group /system.slice/sys-kernel-debug.mount, ignoring: Operation not supported
[   28.066849] systemd[1]: Mounting Debug File System...
[   28.107483] systemd[1]: Reached target Slices.
[   28.129974] systemd[1]: dev-hugepages.mount: Couldn't determine result for ConditionVirtualization=!private-users, assuming failed: No such file or directory
[   28.153679] systemd[1]: systemd-modules-load.service: Failed to set invocation ID on control group /system.slice/systemd-modules-load.service, ignoring: Operation not supported
[   28.172347] systemd[1]: Starting Load Kernel Modules...
[   28.191184] systemd[1]: dev-mqueue.mount: Failed to set invocation ID on control group /system.slice/dev-mqueue.mount, ignoring: Operation not supported
[   28.212737] systemd[1]: Mounting POSIX Message Queue File System...
[   28.250583] systemd[1]: system-getty.slice: Failed to set invocation ID on control group /system.slice/system-getty.slice, ignoring: Operation not supported
[   28.305490] systemd[1]: Created slice system-getty.slice.
[   28.361321] systemd[1]: kmod-static-nodes.service: Failed to set invocation ID on control group /system.slice/kmod-static-nodes.service, ignoring: Operation not supported
[   28.378673] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[   28.410555] systemd[1]: system-serial\x2dgetty.slice: Failed to set invocation ID on control group /system.slice/system-serial\x2dgetty.slice, ignoring: Operation not supported
[   28.433583] systemd[1]: Created slice system-serial\x2dgetty.slice.
[   28.460229] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   28.489966] systemd[1]: Reached target Encrypted Volumes.
[   28.519904] systemd[1]: Reached target Paths.
[   28.540053] systemd[1]: Listening on Journal Socket (/dev/log).
[   28.570907] systemd[1]: systemd-journald.service: Failed to set invocation ID on control group /system.slice/systemd-journald.service, ignoring: Operation not supported
[   28.588267] systemd[1]: Starting Journal Service...
[   28.610188] systemd[1]: Reached target Remote File Systems.
[   28.632531] systemd[1]: Mounted Debug File System.
[   28.669968] systemd[1]: Mounted POSIX Message Queue File System.
[   28.700300] systemd[1]: Started Journal Service.
[   29.033798] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   29.403529] systemd-journald[143]: Received request to flush runtime journal from PID 1
[   30.058486] Bluetooth: Core ver 2.16
[   30.094365] cfg80211: Calling CRDA to update world regulatory domain
[   30.186220] NET: Registered protocol family 31
[   30.190741] Bluetooth: HCI device and connection manager initialized
[   30.197124] Bluetooth: HCI socket layer initialized
[   30.202065] Bluetooth: L2CAP socket layer initialized
[   30.209414] usbcore: registered new interface driver cdc_ether
[   30.224568] Bluetooth: SCO socket layer initialized
[   30.230559] Bluetooth: Generic Bluetooth USB driver ver 0.6
[   30.269826] rndis_host 1-1.4.4:3.0: eth1: register 'rndis_host' at usb-orion-ehci.0-1.4.4, RNDIS device, 00:50:b6:4a:9e:26
[   30.282345] usbcore: registered new interface driver btusb
[   30.362173] usbcore: registered new interface driver rndis_host
[   30.458654] usbcore: registered new interface driver snd-usb-audio
[   30.467564] usbcore: registered new interface driver rndis_wlan
[   30.501758] usb 1-1.4.3.3: reset high-speed USB device number 8 using orion-ehci
[   30.803638] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   30.805940] Registered led device: rt2800usb-phy0::radio
[   30.806045] Registered led device: rt2800usb-phy0::assoc
[   30.806153] Registered led device: rt2800usb-phy0::quality
[   30.806232] usbcore: registered new interface driver rt2800usb
[   30.825493] Adding 130044k swap on /dev/sda2.  Priority:-1 extents:1 across:130044k 
[   31.906131] rt2800usb 1-1.4.3.3:1.0: firmware: agent aborted loading rt2870.bin (not found?)
[   32.008638] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   34.320070] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   34.330128] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   37.660084] rt2800usb 1-1.4.3.3:1.0: firmware: agent aborted loading rt2870.bin (not found?)
Re: wireless initramfs problem after upgrade to stretch from jessie
December 05, 2017 03:41PM
metric,

> It is a stock kernel that came with the upgrade.
> Linux dstar 3.2.0-4-kirkwood #1 Debian
> 3.2.68-1+deb7u2 armv5tel



I see. What is your fstab looks like now? does it have

LABEL=rootfs       /               ext4    noatime,nodiratime,errors=remount-ro 0 1

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: wireless initramfs problem after upgrade to stretch from jessie
December 06, 2017 01:36AM
No it looks as follows.

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/root       /               ext4    noatime,nodiratime,errors=remount-ro 0 1

I changed to LABEL=rootfs / and it became read only. I will fix it in another linux box but that is not working. I even tried putting UUID. The system boots fine but still gives me the original problem.
Re: wireless initramfs problem after upgrade to stretch from jessie
December 06, 2017 02:41AM
metric,

You are not running my latest u-boot:
https://forum.doozan.com/read.php?3,12381

or my latest kernel :
https://forum.doozan.com/read.php?2,12096

So it is a little bit harder for me to help you! But it is OK (I don't mind which software you run :).


The problem is simple to solve. You just need to run the latest initramfs so that the fsck hook is correct.

1. Make sure you have this in fstab

LABEL=rootfs       /               ext4    noatime,nodiratime,errors=remount-ro 0 1

2. Regenerate initramfs

update-initramfs -u


3. Regenerate uInitrd

cd /boot
cp -a uInitrd uInitrd.bak
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.2.0-4-kirkwood -d initrd.img-3.2.0-4-kirkwood uInitrd

4. Reboot

5. After you've logged in to Debian, upgrade to pick up the latest Debian pkgs:

apt-get update
apt-get upgrade

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: wireless initramfs problem after upgrade to stretch from jessie
December 08, 2017 05:36PM
Thanks Bodhi,

Just because you complained... :-), I upgraded the U-Boot. For some reason the boot partition did not have rootfs label. I added that too. I know this is a hacked device to begin with, but I like to keep the kernel in sync with the distribution so that I can update with apt-get. I prefer not to use your kernel for that reason alone. But that is not working either. . I have installed 4.9 but it boots in to 3.2 Do I manually do the same mkimage again? Where is it broken?

linux-image-3.2.0-4-kirkwood/now 3.2.68-1+deb7u2 armel [installed,local]
linux-image-4.9.0-4-marvell/stable,now 4.9.51-1 armel [installed,automatic]
linux-image-kirkwood/stable,now 4.9+80+deb9u2 armel [installed]
linux-image-marvell/stable,now 4.9+80+deb9u2 armel [installed,automatic]


I checked the partition with gparted. It is clean. I also checked the file system. It is also clean. I am not sure about the errors shown by netconsole . I think the unknown partition message is coming from USB multi-card reader. There is one CF card that boots. Other slots are empty.

The system does boot fine. But with the new boot environment, I have lost the ability to boot in to my old rescue partition. How do I add that back? Here is the netconsole output. The env text file is new to me. Do I add my old saved environment commands in /boot/uEnv.txt ?

Starting kernel ...

U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700)
Seagate FreeAgent DockStar
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... ERROR: Invalid USB EP length (9)
ERROR: Invalid USB EP length (9)
8 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

Partition Map for USB device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	62        	3678146   	000661c7-01	83 Boot
  2	3678208   	260096    	000661c7-02	82

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 784 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
1616072 bytes read in 862 ms (1.8 MiB/s)
loading uInitrd ...
9177476 bytes read in 1491 ms (5.9 MiB/s)
loading DTB ...
** No boot file defined **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   kernel 3.2.0-4-kirkwood
   Created:      2015-06-20  18:44:23 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1616008 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.2.0-4-kirkwood
   Created:      2017-12-08  22:25:42 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9177412 Bytes = 8.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Starting kernel ..


Rest of the commands worked and the hook problem went away. I was able to run update re-install firmware package but the wireless card that was working with Jessie has now stopped working with Stretch.

[   32.202263] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   32.204628] Registered led device: rt2800usb-phy0::radio
[   32.204732] Registered led device: rt2800usb-phy0::assoc
[   32.204845] Registered led device: rt2800usb-phy0::quality
[   32.204925] usbcore: registered new interface driver rt2800usb
[   32.242693] Adding 130044k swap on /dev/sda2.  Priority:-1 extents:1 across:130044k 
[   33.204862] rt2800usb 1-1.4.3.3:1.0: firmware: agent aborted loading rt2870.bin (not found?)
[   33.308929] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   35.709357] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   35.719347] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   38.882028] rt2800usb 1-1.4.3.3:1.0: firmware: agent aborted loading rt2870.bin (not found?)

The firmware package is installed and the file does exist.
/lib/firmware/rt2870.bin


The modules are loaded too.
lsmod | grep rt
rt2800usb              11843  0
rt2x00usb               7696  1 rt2800usb
rt2800lib              41408  1 rt2800usb
rt2x00lib              30669  3 rt2800lib,rt2x00usb,rt2800usb
mac80211              205687  3 rt2x00lib,rt2800lib,rt2x00usb
cfg80211              151548  3 mac80211,rt2x00lib,rndis_wlan
crc_ccitt               1125  1 rt2800lib
usbcore               123016  12 ehci_hcd,usb_storage,usbnet,btusb,cdc_ether,rndis_host,rt2x00usb,rt2800usb,rndis_wlan,snd_usbmidi_lib,snd_usb_audio

Re: wireless initramfs problem after upgrade to stretch from jessie
December 08, 2017 07:02PM
metric,

There are a few things need to be corrected here.

> I have
> installed 4.9 but it boots in to 3.2 Do I manually
> do the same mkimage again? Where is it broken?

Whenever you install new kernel, you need to redo mkimage. It is using the old uImage and uInitrd for 3.2.

> I checked the partition with gparted. It is clean.
> I also checked the file system. It is also clean.
> I am not sure about the errors shown by netconsole
>

Those partition errors are OK. New u-boot mainline code just blindly scans everything.

>
> The system does boot fine. But with the new boot
> environment, I have lost the ability to boot in to
> my old rescue partition. How do I add that back?

The rescue envs need to be restored using this saved copy of current_envs.txt you did in Step 3:

Quote

3. Be sure to save your current uBoot image in mtd0, or have a backup image saved somewhere as precaution. And save your current u-boot envs with fw_printenv, or just copy/paste the listing into a text file. Note the nanddump command below allows future restoration to the same box you're backing up, and also can be used to restore a differrent box's mtd0 if needed.

Dumping NAND mtd0:
nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0
Save envs:
fw_printenv > current_envs.txt
or
blparam > current_envs.txt

> Do I add my old saved environment
> commands in /boot/uEnv.txt ?
>

First , use thei uEnv.txt to add the rescue envs back (easy to find them in current_envs.txt, they all have the words "rescue" in their names) . After you have tested it in netconsole, then do them permanently with fw_setenv in Debian.

> loading DTB ...
> ** No boot file defined **

This error is OK when you boot the main line kernel.

> Rest of the commands worked and the hook problem
> went away. I was able to run update re-install
> firmware package but the wireless card that was
> working with Jessie has now stopped working with
> Stretch.

> The firmware package is installed and the file
> does exist.
> /lib/firmware/rt2870.bin
>

In the new Linux versions, the FW bin files are no longer shipped with kernel source. We have to add it manually. I believe Debian takes care of this. So if you have installed the correct firmawre packages, and then upgrade to the latest Debian distribution (i.e. 9.2), you should get it. Try that and see if you get the rt2870.bin back. If not, just copy them from your backup rootfs (if you have it?).

Please let me know about this rt2870.bin issue, if you can or cannot resolve it and how.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: wireless initramfs problem after upgrade to stretch from jessie
December 08, 2017 07:10PM
Ok that was easy.

This version in Debian stretch has the rt2870:
https://packages.debian.org/stretch/firmware-misc-nonfree

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 12/08/2017 07:11PM by bodhi.
Re: wireless initramfs problem after upgrade to stretch from jessie
December 08, 2017 07:57PM
Quote
bodhi
https://packages.debian.org/stretch/firmware-misc-nonfree

The package is installed. I reinstalled it just in case. Did dpkg -a too. The file does exist on the drive, I confirmed it with mlocate. That is why I am confused. Why it says that the file cannot be found.
Re: wireless initramfs problem after upgrade to stretch from jessie
December 08, 2017 08:55PM
metric Wrote:
-------------------------------------------------------
>
Quote
bodhi
> https://packages.debian.org/stretch/firmware-misc-nonfree
>
>
> The package is installed. I reinstalled it just
> in case. Did dpkg -a too. The file does exist on
> the drive, I confirmed it with mlocate. That is
> why I am confused. Why it says that the file
> cannot be found.


Are you running systemd or sysvinit? please post the entire dmesg output.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: wireless initramfs problem after upgrade to stretch from jessie
December 12, 2017 06:20PM
@bodhi I am running systemd. BTW I have taken too much of your time trying to recover. So here is a new plan ;-)

I had backed up the entire boot drive with Jessie on a desktop, so I re-imaged it back and will start upgrade from my Jessie version again. Any pointers to do it properly? Here is what I followed last time.

https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.html

So, first I need to bring back my rescue image. I am little confused. Do I just copy the rescue section to the text file or all of my new boot environment from your post and add pertinent rescue following rescue commands?


rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
Re: wireless initramfs problem after upgrade to stretch from jessie
December 13, 2017 12:05AM
metric,

>
> I had backed up the entire boot drive with Jessie
> on a desktop, so I re-imaged it back and will
> start upgrade from my Jessie version again. Any
> pointers to do it properly? Here is what I
> followed last time.
>
> https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.html
>

See the Wiki thread which contains this specific post:
http://forum.doozan.com/read.php?2,35581


> So, first I need to bring back my rescue image. I
> am little confused. Do I just copy the rescue
> section to the text file or all of my new boot
> environment from your post and add pertinent
> rescue following rescue commands?
>

- Best to go slow. First, test these recue envs using netconsole without saving them. And after it worked save them permanently.

- Boot with without USB drive, Interupt netconsole, and enter rescue envs one by one using setenv

setenv rescue_set_bootargs 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params'
setenv rescue_bootcmd 'if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi'
setenv pogo_bootcmd 'if fsload uboot-original-mtd0.kwb; then go 0x800200; fi'
setenv force_rescue '0'
setenv force_rescue_bootcmd 'if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3'

and then

boot

After verifying it works a few times, you can save them in netconsole.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 5 time(s). Last edit at 12/13/2017 02:39AM by bodhi.
Re: wireless initramfs problem after upgrade to stretch from jessie
December 19, 2017 06:46PM
@bodhi

I followed your instruction, it still fails to boot from rescue. As I have a bootable system image and new uboot, I do not mind trying new rescue. Do you have any recommendations? The LEDE version looks good.

DockStar> setenv rescue_set_bootargs 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params'
setenv rescue_set_bootargs 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params'
DockStar> setenv rescue_bootcmd 'if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi'
setenv rescue_bootcmd 'if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi'
DockStar> setenv pogo_bootcmd 'if fsload uboot-original-mtd0.kwb; then go 0x800200; fi'
setenv pogo_bootcmd 'if fsload uboot-original-mtd0.kwb; then go 0x800200; fi'
DockStar> setenv force_rescue '0'
setenv force_rescue '0'
DockStar> setenv force_rescue_bootcmd 'if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3'
setenv force_rescue_bootcmd 'if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3'
DockStar> boot
boot
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide
Unknown command 'ide' - try 'help'
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
DockStar> 

Re: wireless initramfs problem after upgrade to stretch from jessie
December 20, 2017 01:55AM
metric,

Power up, interrupt serial console and enter the rescue envs, and then

printenv
boot

Post the entire serial console log here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: