Re: [DNG] Help to install LiLo to a GPT HDD.
On Thu, 22 Aug 2019 21:07:42 +0700 Андрей via Dng wrote: > Приветствую. > > > Please help to install LiLo to a GPT HDD. > > Situation: I move installed OS from one drive (DOS partition scheme) > to another (3 TB, GPT partition scheme). The motherboard is old: BIOS, > Athlon 3000+. I have created single 2.7 TiB partition on which did > place the installed OS. Did mount to it /proc, /dev, /sys. > Changed /etc/lilo.conf with boot and root parameters according > to the new drieve IDs. ChRooted to it, typed lilo. LiLo gave only one > warning, that the drive is not the first one. > > Result: BIOS tells me that the drive capasity is 801 GB instead of > 3000. Well, for working as non bootable drive it worked alright. > But booting from the new drive gives me L 99 99 99 ... error. -- The > geometry problem, as i get it. And it halts booting. > > Now. From Slackware site i read, that it is possible to install LiLo > on a GPT-HDD, but is not specified how, and as i remember, even, > without an additional "technical" partition. > > So, how do i install LiLo so that it boots OS from the GPT-drive? If I remember from my LILO days, LILO couldn't reach out 2.7 GB to find a kernel. So what you did, back in the day, was make a small partition right at the front of the disk for /boot. Then you put the real partition(s) in the remaining space. So mount the boot partition and the root partition, then chroot install. I don't think it had as much to do with GPT as the huge /dev/sda1. If I remember correctly, GPT puts a fake MBR right where you'd expect an MBR to be, and that fake MBR has all the right information, so I think LILO should be OK with that. SteveT Steve Litt August 2019 featured book: Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf images for RPi3+?
Great thanks Dimitris.
Is the Rpi4 build working?
ozi
On Fri, Aug 23, 2019 at 8:06 AM Dimitris wrote:
> On 8/23/19 12:39 AM, Ozi Traveller wrote:
> > What changes would be necessary to get the arm-sdk to build for beowulf?
>
> you need all dependencies + libssl-dev package, iirc. git clone repo
> below and make the following changes, before "Initial setup" from
> README. (https://git.devuan.org/sdk/arm-sdk) :
>
>
> 1) had issues with rpi-5.0.y linux branch, so went for 4.20. can pick
> any kernel to test...
>
> diff --git a/boards/raspberry-pi3.sh b/boards/raspberry-pi3.sh
> index 95af74a..69eb3e3 100644
> --- a/boards/raspberry-pi3.sh
> +++ b/boards/raspberry-pi3.sh
> @@ -38,7 +38,7 @@ extra_packages+=()
> custmodules=(snd_bcm2835)
>
> gitkernel="https://github.com/raspberrypi/linux;
> -gitbranch="rpi-4.16.y"
> +gitbranch="rpi-4.20.y"
> rpifirmware="https://github.com/raspberrypi/firmware.git;
>
>
>
> 2) under lib/libdevuansdk/ (https://git.devuan.org/sdk/libdevuansdk) :
>
> diff --git a/config b/config
> index 43ccb4b..0a449df 100644
> --- a/config
> +++ b/config
> @@ -34,9 +34,9 @@ aptcachedir="$LIBPATH/apt-cache"
> aptcachegpg="0xdeadbeefdeadbeef"
>
> os="devuan"
> -release="ascii"
> -version="2.0.0"
> -mirror="http://pkgmaster.devuan.org/merged;
> +release="beowulf"
> +version="3.0.0"
> +mirror="http://deb.devuan.org/merged;
> section="main contrib non-free"
>
> image_name="${os}_${release}_${version}_${arch}"
>
> diff --git a/zlibs/sysconf b/zlibs/sysconf
> index 131690a..10359c0 100644
> --- a/zlibs/sysconf
> +++ b/zlibs/sysconf
> @@ -99,9 +99,9 @@ conf_print_resolvconf() {
> fn conf_print_resolvconf
>
> cat < -## google's nameservers
> -nameserver 8.8.8.8
> -nameserver 8.8.4.4
> +## opennic nameservers
> +nameserver 193.183.98.66
> +nameserver 94.247.43.254
> EOF
> }
>
>
> building an image might take a long time, depending on network speed,
> hardware.. be prepared.
> also i used these a few months ago, so they might not apply exactly as
> above. check output messages for errors.
>
> d.
>
> p.s. last nameservers change is just personal "taste", feel free to
> ignore...
>
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf images for RPi3+?
On 8/23/19 12:39 AM, Ozi Traveller wrote:
> What changes would be necessary to get the arm-sdk to build for beowulf?
you need all dependencies + libssl-dev package, iirc. git clone repo
below and make the following changes, before "Initial setup" from
README. (https://git.devuan.org/sdk/arm-sdk) :
1) had issues with rpi-5.0.y linux branch, so went for 4.20. can pick
any kernel to test...
diff --git a/boards/raspberry-pi3.sh b/boards/raspberry-pi3.sh
index 95af74a..69eb3e3 100644
--- a/boards/raspberry-pi3.sh
+++ b/boards/raspberry-pi3.sh
@@ -38,7 +38,7 @@ extra_packages+=()
custmodules=(snd_bcm2835)
gitkernel="https://github.com/raspberrypi/linux;
-gitbranch="rpi-4.16.y"
+gitbranch="rpi-4.20.y"
rpifirmware="https://github.com/raspberrypi/firmware.git;
2) under lib/libdevuansdk/ (https://git.devuan.org/sdk/libdevuansdk) :
diff --git a/config b/config
index 43ccb4b..0a449df 100644
--- a/config
+++ b/config
@@ -34,9 +34,9 @@ aptcachedir="$LIBPATH/apt-cache"
aptcachegpg="0xdeadbeefdeadbeef"
os="devuan"
-release="ascii"
-version="2.0.0"
-mirror="http://pkgmaster.devuan.org/merged;
+release="beowulf"
+version="3.0.0"
+mirror="http://deb.devuan.org/merged;
section="main contrib non-free"
image_name="${os}_${release}_${version}_${arch}"
diff --git a/zlibs/sysconf b/zlibs/sysconf
index 131690a..10359c0 100644
--- a/zlibs/sysconf
+++ b/zlibs/sysconf
@@ -99,9 +99,9 @@ conf_print_resolvconf() {
fn conf_print_resolvconf
cat <
signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf images for RPi3+?
I'm interested in this too. What changes would be necessary to get the arm-sdk to build for beowulf? ozi On Thu, Aug 22, 2019 at 9:11 PM Dimitris via Dng wrote: > On 8/22/19 1:59 PM, Antony Stone wrote: > > On Thursday 22 August 2019 at 12:53:06, Dr. Nikolaus Klepp wrote: > > > >> hi all! > >> > >> Could somebody please point me to where I can download the latest image > of > >> beowulf for RaspberryPi 3+ ? I searched the webpage, but did not find a > >> hint :( > > > > I didn't think there were any download images of Beowulf yet, for any > > architecture. > > > > It's only an upgrade from Ascii at present. > > > > > > Antony. > > > > there are no beowulf images, but if you like, you can built one yourself > using the instructions in this link : https://git.devuan.org/sdk/arm-sdk > iirc, there are some changes needed for that to work for beowulf. > > d. > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Help to install LiLo to a GPT HDD.
On Thu, 22 Aug 2019 21:07:42 +0700, Андрей wrote in message <20190822170724.7mkco...@smtp4j.mail.yandex.net>: > Приветствую. > > > Please help to install LiLo to a GPT HDD. > > Situation: I move installed OS from one drive (DOS partition scheme) > to another (3 TB, GPT partition scheme). The motherboard is old: BIOS, > Athlon 3000+. I have created single 2.7 TiB partition on which did > place the installed OS. Did mount to it /proc, /dev, /sys. > Changed /etc/lilo.conf with boot and root parameters according > to the new drieve IDs. ChRooted to it, typed lilo. LiLo gave only one > warning, that the drive is not the first one. > > Result: BIOS tells me that the drive capasity is 801 GB instead of > 3000. Well, for working as non bootable drive it worked alright. > But booting from the new drive gives me L 99 99 99 ... error. -- The > geometry problem, as i get it. And it halts booting. > > Now. From Slackware site i read, ..this?: https://docs.slackware.com/howtos:slackware_admin:installing_with_gpt_without_uefi > that it is possible to install LiLo > on a GPT-HDD, but is not specified how, and as i remember, even, > without an additional "technical" partition. > > So, how do i install LiLo so that it boots OS from the GPT-drive? ..https://duckduckgo.com/?q=Slackware+install+LiLo+on+a+GPT-HDD=web came up with the above link and these: https://www.linuxquestions.org/questions/slackware-14/slackware-uefi-lilo-4175656413/ https://www.linuxquestions.org/questions/slackware-14/slackware-uefi-lilo-4175656413/page2.html https://linuxhint.com/install-slackware-linux/ ..credible advice: Whenever a Slackware wizard recommends making a boot usb etc medium, act on that recommendation. https://docs.slackware.com/slackware:install ..this pxe setup recipe wizard is neat: https://docs.slackware.com/slackware:pxe_install ..3 Slackware install play lists that should get you started: https://www.youtube.com/user/mikemurphycs/playlists -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Help to install LiLo to a GPT HDD.
As far as I remember, you have to make sure the bootloader's kernel is at a sector that LILO can access. GPT is too new for LILO. You also have to provide space where the bootloader saves its second stage, always if my assumption that it uses the same mechanism used by legacy GRUB, is correct. So, according to me, you should leave the very first partition next to the initial GPT headers free and unformatted. Use a very small partition space. All this if from memory which often is wrong with the passage of so many years since I last used LILO and installed GRUB. GRUB works on GPT formatted disks under a UEFI system. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Help to install LiLo to a GPT HDD.
Приветствую. Please help to install LiLo to a GPT HDD. Situation: I move installed OS from one drive (DOS partition scheme) to another (3 TB, GPT partition scheme). The motherboard is old: BIOS, Athlon 3000+. I have created single 2.7 TiB partition on which did place the installed OS. Did mount to it /proc, /dev, /sys. Changed /etc/lilo.conf with boot and root parameters according to the new drieve IDs. ChRooted to it, typed lilo. LiLo gave only one warning, that the drive is not the first one. Result: BIOS tells me that the drive capasity is 801 GB instead of 3000. Well, for working as non bootable drive it worked alright. But booting from the new drive gives me L 99 99 99 ... error. -- The geometry problem, as i get it. And it halts booting. Now. From Slackware site i read, that it is possible to install LiLo on a GPT-HDD, but is not specified how, and as i remember, even, without an additional "technical" partition. So, how do i install LiLo so that it boots OS from the GPT-drive? Андрей. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf images for RPi3+?
On 8/22/19 1:59 PM, Antony Stone wrote: > On Thursday 22 August 2019 at 12:53:06, Dr. Nikolaus Klepp wrote: > >> hi all! >> >> Could somebody please point me to where I can download the latest image of >> beowulf for RaspberryPi 3+ ? I searched the webpage, but did not find a >> hint :( > > I didn't think there were any download images of Beowulf yet, for any > architecture. > > It's only an upgrade from Ascii at present. > > > Antony. > there are no beowulf images, but if you like, you can built one yourself using the instructions in this link : https://git.devuan.org/sdk/arm-sdk iirc, there are some changes needed for that to work for beowulf. d. signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf images for RPi3+?
On Thursday 22 August 2019 at 12:53:06, Dr. Nikolaus Klepp wrote: > hi all! > > Could somebody please point me to where I can download the latest image of > beowulf for RaspberryPi 3+ ? I searched the webpage, but did not find a > hint :( I didn't think there were any download images of Beowulf yet, for any architecture. It's only an upgrade from Ascii at present. Antony. -- These clients are often infected by viruses or other malware and need to be fixed. If not, the user at that client needs to be fixed... - Henrik Nordstrom, on Squid users' mailing list Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Beowulf images for RPi3+?
hi all! Could somebody please point me to where I can download the latest image of beowulf for RaspberryPi 3+ ? I searched the webpage, but did not find a hint :( Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Cannot mount android phone via usb
On Wed, Aug 21, 2019 at 10:32:01PM -1000, Joel Roth via Dng wrote: > > According to apt-cache search, udev is a transitional package for > eudev. So does that mean I have an issue with eudev? I don't know about udev and eudev, vut an Android phone is an MTP device -- the Music Transfer Protocol. The only way I succeed in accessing my Android phone (a Nexus 5) is to put it into developer mode, and to use adb on my Linux-based system. That's the Android debgger. Android fiercely protects the data stored on it against even its owner. Gaining root access the official way -- without depending on Android bugs -- deletes all the data on the phone. Whereas developer mode has restrictions, but doesn't delete your data unless you ask it to. > > Grateful for any advice toward diagnosing or resolving this > issue! Hope this helps, and that you don't already know it. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Cannot mount android phone via usb
I previously used jmtpfs to mount an android phone connected via usb. Now having issues mounting a recently acquired nokia 6 with android pie. First issue was missing /lib/udev/mtp-probe in dmesg output. That was resolved by installing libmtp-runtime. Now I get: [ 2501.994664] usb 2-1.5: new high-speed USB device number 5 using ehci-pci [ 2502.104236] usb 2-1.5: New USB device found, idVendor=0489, idProduct=c001, bcdDevice= 3.18 [ 2502.104242] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2502.104245] usb 2-1.5: Product: Android [ 2502.104248] usb 2-1.5: Manufacturer: Android [ 2502.104251] usb 2-1.5: SerialNumber: PLEGAR2812101035 [ 2502.105172] usb-storage 2-1.5:1.0: USB Mass Storage device detected [ 2502.105264] scsi host6: usb-storage 2-1.5:1.0 [ 2503.108002] scsi 6:0:0:0: CD-ROMLinuxFile-CD Gadget 0318 PQ: 0 ANSI: 2 [ 2503.108959] sr 6:0:0:0: Power-on or device reset occurred [ 2503.110700] sr 6:0:0:0: [sr1] scsi-1 drive [ 2503.110909] sr 6:0:0:0: Attached scsi CD-ROM sr1 [ 2503.110984] sr 6:0:0:0: Attached scsi generic sg2 type 5 mount /dev/sr1 /mnt/test fails with mount: no medium found on /dev/sr1 jtmpfs reports "No mtp devices found." file /dev/sr1 reports /dev/sr1: block special (11/1) lsusb -v -s 2:5 Bus 002 Device 005: ID 0489:c001 Foxconn / Hon Hai Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0489 Foxconn / Hon Hai idProduct 0xc001 bcdDevice3.18 iManufacturer 1 Android iProduct2 Android iSerial 3 PLEGAR2812101035 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 4 Mass Storage Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 bInterfaceProtocol 1 iInterface 7 ADB Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) I upgraded from 4.9 kernel to
