Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: Factory restore Dockstar - Help needed - Today
Zasshi, With serial console connected, power up and interrupt the count down. At u-boot prompt, printenv If you have saved the envs previously then go ahead, boot. If not, repeat what you done to prepare the envs for booting, and then boot. boot Post the entire serial console log here. Don't post excerpt, I need to see the whole log (what you entered at u-boot prompt, and the logby bodhi - Rescue System
Re: Factory restore Dockstar - Help needed - 2 days ago
Zasshi, > I managed to recover the "dead unit" bootloader > and now I can boot to Linux. > How should I proceed to re-install the original > firmware? You reinstall the original firmware in the steps below. The boot loader is apparently fine if you can do these steps. > > I found these steps on the Goflexnet Openwrt > wiki: > > #set goflex neby bodhi - Rescue System
Re: Debian on AK Systems Thin client rev 1.3 - 2 days ago
Vadim_Boev Wrote: ------------------------------------------------------- > QuoteNo. u-boot is the boot loader. You are not > writing > the u-boot commands to the Debian rootfs. In the > instruction > > I'm sorry, apparently I didn't express myself > correctly. I mean, I need the right instructions > for working with a USB flash drive, maybe I wrote >by bodhi - Debian
Re: Debian on AK Systems Thin client rev 1.3 - 3 days ago
> Okay, as soon as I find the SanDisk USB stick, > I'll start. I would like to know what size a usb > flash drive should be? 2 GB? 4 GB? 8 GB? 16 GB? I would use 16GB, because Debian tends to growth. 16 GB will be good for a while before you need to migrate to larger disk. > And also, since I'm not at all sure that I wrote > the data to U-Boot correctly, could yoby bodhi - Debian
Re: Debian on AK Systems Thin client rev 1.3 - 3 days ago
> U-Boot 2011.06 (Jan 03 2013 - 16:19:06) > Promwad-ThinClient > Marvell>> usb start > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... 3 USB Device(s) found > scanning bus for storage devices... EHCI > timed out on TD - token=0x248d80 > EHCI timed out on TD - token=0x80008d80 > 1 Storage Deby bodhi - Debian
Re: Debian on AK Systems Thin client rev 1.3 - 4 days ago
Vadim_Boev, Loading file "/boot/uImage" from usb device 0:1 (usbda1) ** File not found /boot/uImage Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) ** File not found /boot/uInitrd These errors mean u-boot could not find the kernel images. This usually happens if the USB partition was formatted as Ext4 and not "finalized". But you have verified thaby bodhi - Debian
Re: Debian on AK Systems Thin client rev 1.3 - 4 days ago
Vadim_Boev, QuoteI tried to update the u-boot and Debian firmware based on these instructions: 1. Linux Kernel 6.9.6 Kirkwood package and Debian rootfs (Updated 01 Nov 2023:) 2. Boot Kirkwood rootfs with stock u-boot If you have kept the log of what you did in creating the rootfs (1), and also the u-boot booting (2), including all setenvs commands, please post them here. QuoteI do notby bodhi - Debian
Re: Really good deal on this Linksys LN1301 at Woot! $15, ARM Cortex-A53 (Quad Core), 2GB memory, 1GB flash, u-boot - 4 days ago
Indeed a good deal. Hope it is still in stock when I can get to it. Thanks David!by bodhi - Off-Topic
Re: Kernel upgrade question - 5 days ago
These are the kernel files, so they have the build date, except for initrd file. They were generated by dpkg -i linux-image-6.9.6-kirkwood-tld-1_1_armel.deb -rwxr-xr-x 1 root root 6.0M Jun 21 15:33 vmlinuz-6.9.6-kirkwood-tld-1 -rw-r--r-- 1 root root 197K Jun 21 15:33 config-6.9.6-kirkwood-tld-1 -rw-r--r-- 1 root root 4.4M Jun 21 15:33 System.map-6.9.6-kirkwood-tld-1 -rw-r--r-- 1 roby bodhi - Debian
Re: Factory restore Dockstar - Help needed - 6 days ago
Cont. 5. And then after logging to Debian, flash stock Dockstar firmware. It is also possible to do the flashing while in serial console, and at u-boot prompt.by bodhi - Rescue System
Re: Factory restore Dockstar - Help needed - 6 days ago
There are 4 possible unbrick steps (1 is easiest). 1. Take your USB rootfs to another Linux and run e2fsck to check for errors and fix it. Bring it back to the dockstar and try booting it. 2. If you remmember what u-boot was installed, and what Debian rootfs is on the USB, (or what procedure you used to install), then we could try booting a rootfs that matches what this u-boot expects. 3by bodhi - Rescue System
Re: Factory restore Dockstar - Help needed - 8 days ago
Zasshi, How "bricked" is your Dockstar? do you have serial console, and if you do when you power up do you see u-boot booting activities? Post the boot log.by bodhi - Rescue System
Re: Debian on HP Thin Client T5335z - 8 days ago
> Bodhi, what kernel do you use? I think the latest, but not sure. I'll check in a couple weeks when I can access my T5335z.by bodhi - Debian
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.9.6) - 8 days ago
Adrien, At the moment, WOL does not work on the RN102/104. We have not worked very hard on this topic, though. I might revisit this issue, if there is interest and volunteer testers.by bodhi - Debian
Re: Kernel upgrade question - 9 days ago
cdlenfert, > I am stuck at not understanding if I should clear > anything out of the /boot directory before I > extract the tarball. I assume it should be > downloaded to, and extracted within /boot, but > that will leave all of the old 6.5.7 files in > /boot if I don't manually remove them (which was > not mentioned in the steps). > > It feels like aby bodhi - Debian
Re: Debian on HP Thin Client T5335z - 9 days ago
AnSa & petruchito, It seems like either something has changed in the mainline kernel. Or your box uses a different SPI flash chip. My very old log shows (I don't have access to my T5335z at the moment): [ 26.481994] orion_spi orion_spi.0: use polling mode [ 26.486969] m25p80 spi0.0: sst25vf080b (1024 Kbytes) [ 26.491932] 4 cmdlinepart partitions found on MTD device spiby bodhi - Debian
Re: Debian on HP Thin Client T5335z - 10 days ago
This is what we need to confirm [ 2.856695] 4 cmdlinepart partitions found on MTD device spi0.0 [ 2.863498] Creating 4 MTD partitions on "spi0.0": [ 2.868978] 0x000000000000-0x0000000c0000 : "u-boot" [ 2.876219] 0x0000000c0000-0x0000000c2000 : "uboot_env" [ 2.883469] 0x0000000c2000-0x0000000c4000 : "pu_env" [ 2.890339] 0x0000000cby bodhi - Debian
Re: Debian on HP Thin Client T5335z - 10 days ago
AnSa , > These are logs of 'serial' and 'dmesg'. USB with > working Debian is attached. > Boots stock OS. The logs you posted did not help. I need to see the Debian boot logs.by bodhi - Debian
Re: Netgear Stora - Kernel panic - 10 days ago
lre, OK. So try booting the rootfs on the HDD. - Take the HDD to another Linux box. Copy files that you need to save (or back up the drive). - Reformat the HDD to have a single Ext3 partition (ideally 100 GB). - And follow the same procedure in the release thread when you create the USB Debian rootfs using Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2. - Since you are going to bootby bodhi - Debian
Re: Netgear Stora - Kernel panic - 10 days ago
> I tested with ~10 differents USB drives, formated > in ext2, ext3, ext4 and Fat32 : never detected by > u-boot. > Have you tried to plug in a power USB hub?by bodhi - Debian
Re: Debian on HP Thin Client T5335z - 11 days ago
AnSa, > I enter:fw_setenv set_bootargs 'setenv > bootargs console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 ${mtdparts} > earlyprintk=serial' Usually, this problem is related to the mtdparts in the bootargs. But I can pinpoint to the problem and explain it better if you also post tthe serial boot log, or at least the dmesg log. Please post the entire serial bby bodhi - Debian
Re: Netgear Stora - Kernel panic - 11 days ago
Try: Plug your USB drive into another port. If it is still not detected by u-boot, use another USB drive. There should be 2 USB devices detected. One is the USB hub, the other is USB storage drive.by bodhi - Debian
Re: Netgear Stora - Kernel panic - 12 days ago
Ire, Try to use another USB flash drive. The kernel does not recognize your current drive. ================== Here is the basic installation steps in Wiki thread: https://forum.doozan.com/read.php?2,23630 QuoteKirkwood plugs Basic steps to install Debian and new u-boot on Kirkwood boxes Basically, you need to create a USB rootfs using the latest rootfs tarball in the releaseby bodhi - Debian
Re: UART Booting HowTo for Selected Kirkwood Devices - 13 days ago
uLumia, QuoteI can try buy other TTL>USB, and also my PL2303 when plugged to USB for long gets hot and doesn't work anymore, plus Windows drivers dropped support for Pl2303HXA You can buy the CP2102. It's 2-3 USD on eBay shipped from China (if you can wait 2-3 weeks). Works pretty well.by bodhi - uBoot
Re: UART Booting HowTo for Selected Kirkwood Devices - 13 days ago
> Also your Debian rootfs will work on GuruPlug > Server Plus? Its was after SheevaPlug, but before > DreamPlug. Yes, it will work. Use this DTB to create uImage and boot with stock u-boot: /boot/dts/kirkwood-guruplug-server-plus.dtbby bodhi - uBoot
Re: Readynas duo V2 wakealarm missing - 13 days ago
AndreaCipcino. As I mentioned above, QuoteI think there must have been RTC changes in the kernel. Unfortunately, I'm away from my Zyxel NSA325 box for about 4 weeks. I can only track down kernel code. So it might take a while. Looks like there was a significant change in the Linux mainline kernel in the RTC alarm area. So far I only have some idea what to do for the NSA325, but hby bodhi - Debian
Re: Debian on HP Thin Client T5335z - 13 days ago
AnSa, > Bodhi, display still not working yet for this > board? Right, it is not working. The graphics card is too old, and its Marvell Dove driver is not well tested in mainline Linux. I hope to have some free time in the furture to try out the Linux kernel Dove DRM, it might work with some basic settings. However, there is not much of a motivation since this box is low in RAM andby bodhi - Debian
Re: UART Booting HowTo for Selected Kirkwood Devices - 13 days ago
uLumia, Check that the power cord is away from the 3 serial wires. Try vary the timing when you run kwboot and power up (or reboot) the box. - Run kwboot, and immediately apply power (cold start). - Run kwboot and reboot the box. - Apply power and immediately run kwboot. - Reboot and immediately run kwbot. Also, try using my kwboot binary: https://forum.doozan.com/read.php?3by bodhi - uBoot
Re: Debian on HP Thin Client T5335z - 13 days ago
AnSa Wrote: ------------------------------------------------------- > Yep. It works. > 6.6.2 rootfs and 6.9.6 kernel. Cool!by bodhi - Debian
Re: Debian on HP Thin Client T5335z - 14 days ago
AnSa, Try the latest kernel from the release thread: QuoteLatest released kernel: linux-6.9.6-mvebu-tld-1-bodhi.tar.bz2 (27 Jun 2024)by bodhi - Debian