Re: PPC64 Image Installation Error
I see. Thank you for the clarity. N On Sat, 2019-02-02 at 17:11 +0100, John Paul Adrian Glaubitz wrote: > > > On Feb 2, 2019, at 1:25 PM, Noah Wolfe wrote: > > The matter is all the more compacted, of course, due to the fact it > > doesn't even have ifconfig OOTB, giving you few usable methods to > > fix network errors. > ifconfig has been replaced by the “ip” command these days on most > Linux distributions. > > It’s a change unrelated to ppc64, every architecture works like this > now. > > Adrian
Re: PPC64 Image Installation Error
Thanks, Rick. I'll need to do that one of these days. I suppose it would be wise. N On Sat, 2019-02-02 at 14:32 -0800, Rick Thomas wrote: > > > > > On Feb 2, 2019, at 8:11 AM, John Paul Adrian Glaubitz > sik.fu-berlin.de> wrote: > > > > > > > > On Feb 2, 2019, at 1:25 PM, Noah Wolfe > > wrote: > > > > > > The matter is all the more compacted, of course, due to the fact > > > it doesn't even have ifconfig OOTB, giving you few usable methods > > > to fix network errors. > > > > > ifconfig has been replaced by the “ip” command these days on most > > Linux distributions. > > > > It’s a change unrelated to ppc64, every architecture works like > > this now. > > > > Adrian > The ifconfig program hasn’t gone away completely. It’s no longer > installed by default, but it is available in the “net-tools” package. > > To install it do: > apt-get net-tools > > > Of course, it would be a good idea to read the man page for ip(8) > sometime soon. Lot’s more useful features, and it seems to be the > wave of the future in network admin these days. > > Enjoy! > Rick >
Re: PPC64 Image Installation Error
> On Feb 2, 2019, at 8:11 AM, John Paul Adrian Glaubitz > wrote: > > > > On Feb 2, 2019, at 1:25 PM, Noah Wolfe wrote: >> The matter is all the more compacted, of course, due to the fact it doesn't >> even have ifconfig OOTB, giving you few usable methods to fix network errors. >> > > ifconfig has been replaced by the “ip” command these days on most Linux > distributions. > > It’s a change unrelated to ppc64, every architecture works like this now. > > Adrian The ifconfig program hasn’t gone away completely. It’s no longer installed by default, but it is available in the “net-tools” package. To install it do: apt-get net-tools Of course, it would be a good idea to read the man page for ip(8) sometime soon. Lot’s more useful features, and it seems to be the wave of the future in network admin these days. Enjoy! Rick
Re: PPC64 Image Installation Error
Hi Adrian, On Sat, 2019-02-02 at 15:21 +0100, John Paul Adrian Glaubitz wrote: > Hello! > > On 2/2/19 1:32 AM, Noah Wolfe wrote: > > > > After reinstalling the system due to an unresolvable networking > > error (A perfectly stable connection would drop without reason, > > something that did not happen in Ubuntu 16.04, at least after > > network-manager was installed. The only fix was to deactivate and > > reactivate the wired connection in nmtui, which itself as a part of > > network-manager had to be manually downloaded from another OS in > > individual package format as it did not come out of the box.) > This could be a kernel bug, a bug in network-manager or flawky > hardware. Without > any more detailed data, is hard to figure out what the problem is. > I know the hardware is fine, so I'd suspect it to be a kernel bug, especially given that the connection was suddenly dropped even before network-manager was installed. How's progress on 4.20 for powerpc/ppc64 machines? > > > > it seems I am not able to fully boot into it via the yaboot from > > Ubuntu 16.04, which works well and recognizes both systems without > > any problems, boots into either without issue, but then Debian > > throws a BusyBox initramfs terminal halfway through booting, > > citing: "Gave up waiting for root device.", "Missing modules (cat > > /proc/modules; ls /dev)", "ALERT! > Well, yes, Yaboot. As I said, I want to get rid of it. GRUB has the > advantage here that > it's much easier to edit the command line and configuration files as > compared to Yaboot. > > Your problem sounds like the root device passed on the kernel command > line with "root=" > is wrong. > Is there a way to properly install GRUB via the terminal from the rescue option? Okay, and would that be fixable by the user? > /dev/disk/by-uuid/ does not exist. Dropping > to a shell!". Absolutely everything is partitioned and configured > exactly the same as before, when I had it > > > > working. The only thing different, however, is perhaps having > > chosen the option to install LXQt in favor of GNOME, which was the > > environment installed when it was able to boot without issue. > Your desktop environment is unrelated to such boot issues. > I know that. All I was saying was that it worked when it chose the default, which was GNOME, and it didn't work when I tried anything else. I was implying that maybe the installer screwed something up, or left some package out when an option it theoretically didn't like was chosen. > > > > The same blockage occurs when LXDE is chosen, as well. I wish it > > would allow you to install your system without needing to choose a > > desktop environment, which just lengthens installation time by a > > great amount. > Huh? You can just install "Standard system utilities" and that's it. > You don't have > to install a desktop at all. > I did not immediately realize this. > > > > From my experiences alone in the last few days, the ppc64 versions > > /really/ put the "unstable" in "Sid". > That's a rather generalizing statement. The ppc64 stuff is actually > known to be pretty > stable because ppc64 support in the kernel and the toolchain > (compiler, linker etc) is > still actively maintained by IBM. > I apologize. I was speaking for myself and my own experiences alone, and it was meant more as an observation than a statement. I wouldn't know the typical stability of ppc64 because this is the first time I've used that version. Like I said in some emails prior, we're always learning. Or, at least, I am. > Once we have GRUB in place, your bootloader problems will go away. > Your display problems > might be related to a buggy driver. I would try using a different > driver but I can't > make any recommendations unless we know your exact hardware specs. > > Adrian Purely out of curiosity, do you believe we could make a rough ballpark of when GRUB integration could take place? Unless I am missing something, how was it the bootloader's fault when the OS was well past the point of displaying "Welcome to Debian GNU/Linux buster/sid!"? It is my understanding that you are at this point already inside the installed system, and past the bootloader. Here is my specs. https://everymac.com/systems/apple/powermac_g5/specs/ powermac_g5_dual_2.0.html I don't believe there are any alternative video drivers besides nouveau for my model. Thank you for all that you do. PS: Quick question, is there a reason why some packages occasionally won't allow you to install them due to unresolvable dependencies that apt claims are not going to be installed? Would there be any cause besides a sources file problem? N
Re: PPC64 Image Installation Error
> On Feb 2, 2019, at 1:25 PM, Noah Wolfe wrote: > The matter is all the more compacted, of course, due to the fact it doesn't > even have ifconfig OOTB, giving you few usable methods to fix network errors. > ifconfig has been replaced by the “ip” command these days on most Linux distributions. It’s a change unrelated to ppc64, every architecture works like this now. Adrian
Re: PPC64 Image Installation Error
Thanks, Rick. I'll give it a shot. Have you had any networking issues, and have you ever needed to install network-manager? I find that if I don't, the system eventually drops connection and does not want to get back online no matter what I do. Not even (correctly) editing /etc/network/interfaces works, which I believe does work on the Raspberry Pi. The matter is all the more compacted, of course, due to the fact it doesn't even have ifconfig OOTB, giving you few usable methods to fix network errors. N On Feb 2, 2019 6:31 AM, Rick Thomas wrote: Hi again Noah, You can install a bare-bones system without any GUI by de-selecting the “Debian Desktop” task (and leaving de-selected all the individual desktops sub-tasks) when it gets to the “Running Tasksel” stage. Use the arrow keys to move the highlight to a line you want to select or de-select. Use the space bar to select (asterisk in the box) or de-select (space in the box) that row. I usually choose to select the “SSH server” and the “basic system”(last line) and leave everything else de-selected. HTH, Rick > On Feb 1, 2019, at 4:32 PM, Noah Wolfe wrote: > > Perhaps I spoke too soon... > > After reinstalling the system due to an unresolvable networking error (A > perfectly stable connection would drop without reason, something that did not > happen in Ubuntu 16.04, at least after network-manager was installed. The > only fix was to deactivate and reactivate the wired connection in nmtui, > which itself as a part of network-manager had to be manually downloaded from > another OS in individual package format as it did not come out of the box.), > it seems I am not able to fully boot into it via the yaboot from Ubuntu > 16.04, which works well and recognizes both systems without any problems, > boots into either without issue, but then Debian throws a BusyBox initramfs > terminal halfway through booting, citing: "Gave up waiting for root device.", > "Missing modules (cat /proc/modules; ls /dev)", "ALERT! > /dev/disk/by-uuid/ does not exist. Dropping to a > shell!". Absolutely everything is partitioned and configured exactly the same > as before, when I had it working. The only thing different, however, is > perhaps having chosen the option to install LXQt in favor of GNOME, which was > the environment installed when it was able to boot without issue. The same > blockage occurs when LXDE is chosen, as well. I wish it would allow you to > install your system without needing to choose a desktop environment, which > just lengthens installation time by a great amount. > > From my experiences alone in the last few days, the ppc64 versions really put > the "unstable" in "Sid". > > In any case, please advise. Thank you. > > From: Noah Wolfe > Sent: Friday, February 1, 2019 2:08 PM > To: Rick Thomas > Cc: PowerPC List Debian; John Paul Adrian Glaubitz > Subject: Re: PPC64 Image Installation Error > > Thanks, Rick. > I got around this issue by simply making the /boot partition (sda2) 1 GB > instead of 1 MB, and the / partition (sda3) doubled to 80 GB. Using this same > method with a reinstall of Ubuntu Server 16.04 (which was giving me the same > error when it was installed in partitions 6, 7, 8, and 9, below Sid) I am > now, as a result, able to dual boot between it and Debian. > So it really goes to show that sometimes the best solutions in life are > usually the easiest ones. > But I still found the 01-27 build to be unable to install the kernel due to > an apparent "lack of space" in whatever configuration I put it in (save for > the aforementioned method), so that still needs to be fixed. > And, a lot of ppc64 packages are experiencing issues unseen in the powerpc > equivalents. Xfwm4 puts out graphical glitches and artifacts when any windows > are moved, or when the cursor moves over any windows, and GNOME 3 hasn't > displayed any color besides pinkish hues since Jessie, if I'm remembering > correctly. > Anyway, thank you for your time. > N > On Jan 31, 2019 5:16 AM, Rick Thomas wrote: > > > > Hi Noah, > > > > Is it possible for you to temporarily replace the hard drive in your > > machine with one you don’t mind experimenting on? > > > > If so, after a clean installation onto the fresh hard disk, what you want > > to finish up your installation with is something that looks kind of like > > this: > > > > > root@msmini:~# mac-fdisk -l /dev/sda > > > /dev/sda > > > #type name length base > > > ( size ) system > > > /dev/sda1 Apple_partition_map Apple 63 @ 1 > > > ( 31.5k) Partition map > > > /dev/sda2 Apple_Bootstrap untitled1954 @ 64 > > > (977.0k) NewWorld bootblock > > > /dev/sda3 Apple_UNIX_SVR2 untitled 51 @ 2018 > > > (244.1M) Linux native > > > /dev/sda4 Linux_LVM untitled 468360060 @ 502019 > > > (223.3G) Unknown > > >
Re: PPC64 Image Installation Error
Hello! On 2/2/19 1:32 AM, Noah Wolfe wrote: > After reinstalling the system due to an unresolvable networking error (A > perfectly stable connection would drop without reason, something that did not > happen in Ubuntu 16.04, at least after network-manager was installed. The > only fix was to deactivate and reactivate the wired connection in nmtui, > which itself as a part of network-manager had to be manually downloaded from > another OS in individual package format as it did not come out of the box.) This could be a kernel bug, a bug in network-manager or flawky hardware. Without any more detailed data, is hard to figure out what the problem is. > it seems I am not able to fully boot into it via the yaboot from Ubuntu > 16.04, which works well and recognizes both systems without any problems, > boots into either without issue, but then Debian throws a BusyBox initramfs > terminal halfway through booting, citing: "Gave up waiting for root device.", > "Missing modules (cat /proc/modules; ls /dev)", "ALERT! Well, yes, Yaboot. As I said, I want to get rid of it. GRUB has the advantage here that it's much easier to edit the command line and configuration files as compared to Yaboot. Your problem sounds like the root device passed on the kernel command line with "root=" is wrong. /dev/disk/by-uuid/ does not exist. Dropping to a shell!". Absolutely everything is partitioned and configured exactly the same as before, when I had it > working. The only thing different, however, is perhaps having chosen the > option to install LXQt in favor of GNOME, which was the environment installed > when it was able to boot without issue. Your desktop environment is unrelated to such boot issues. > The same blockage occurs when LXDE is chosen, as well. I wish it would allow > you to install your system without needing to choose a desktop environment, > which just lengthens installation time by a great amount. Huh? You can just install "Standard system utilities" and that's it. You don't have to install a desktop at all. > From my experiences alone in the last few days, the ppc64 versions /really/ > put the "unstable" in "Sid". That's a rather generalizing statement. The ppc64 stuff is actually known to be pretty stable because ppc64 support in the kernel and the toolchain (compiler, linker etc) is still actively maintained by IBM. Once we have GRUB in place, your bootloader problems will go away. Your display problems might be related to a buggy driver. I would try using a different driver but I can't make any recommendations unless we know your exact hardware specs. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: iBook G4 - Wireless
On 2/2/19 2:23 PM, Riccardo Mottola wrote: > dmesg tells me: > [16259.858142] b43-wlan ERROR: Dual-core devices are not supported > [16259.861747] b43: probe of ssb0:0 failed with error -524 > [16259.878169] Broadcom 43xx driver loaded [ Features: PNLS ] > > my iBook is for sure not Dual-core! would be too nice :) I don't think this error message is related to your CPU but rather to your WiFi chipset. I would try installing the legacy version of the driver. I will be able to test this myself in around a month after I have moved into my new apartment. I will have enough space there to set up all my retro computers, including one iBook G4. Although, I don't know what kind of wireless chipset mine has. I have two iBook G4 though, so maybe we're lucky one of them has the right chipset. If you can wait until then, I will be able to help. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: iBook G4 - Wireless
Hi Adrian, On 2/1/19 4:59 PM, John Paul Adrian Glaubitz wrote: See: http://snapshot.debian.org/package/b43-fwcutter/1%3A019-3/ fine, I downloaded and installed b43-fwcutter using dpkg. Then following this guide: https://wiki.debian.org/bcm43xx#b43-b43legacy I installed apt-get install firmware-b43-installer because I have, according to lspci: 0001:10:12.0 Network controller: Broadcom Limited BCM4306 802.11b/g Wireless LAN Controller (rev 03) Revision 03 and not revision 02, so not the legacy version. Firmware downloaded without apparent errors However, I get no device! dmesg tells me: [16259.858142] b43-wlan ERROR: Dual-core devices are not supported [16259.861747] b43: probe of ssb0:0 failed with error -524 [16259.878169] Broadcom 43xx driver loaded [ Features: PNLS ] my iBook is for sure not Dual-core! would be too nice :) Riccardo
Re: PPC64 Image Installation Error
Hi again Noah, You can install a bare-bones system without any GUI by de-selecting the “Debian Desktop” task (and leaving de-selected all the individual desktops sub-tasks) when it gets to the “Running Tasksel” stage. Use the arrow keys to move the highlight to a line you want to select or de-select. Use the space bar to select (asterisk in the box) or de-select (space in the box) that row. I usually choose to select the “SSH server” and the “basic system”(last line) and leave everything else de-selected. HTH, Rick > On Feb 1, 2019, at 4:32 PM, Noah Wolfe wrote: > > Perhaps I spoke too soon... > > After reinstalling the system due to an unresolvable networking error (A > perfectly stable connection would drop without reason, something that did not > happen in Ubuntu 16.04, at least after network-manager was installed. The > only fix was to deactivate and reactivate the wired connection in nmtui, > which itself as a part of network-manager had to be manually downloaded from > another OS in individual package format as it did not come out of the box.), > it seems I am not able to fully boot into it via the yaboot from Ubuntu > 16.04, which works well and recognizes both systems without any problems, > boots into either without issue, but then Debian throws a BusyBox initramfs > terminal halfway through booting, citing: "Gave up waiting for root device.", > "Missing modules (cat /proc/modules; ls /dev)", "ALERT! > /dev/disk/by-uuid/ does not exist. Dropping to a > shell!". Absolutely everything is partitioned and configured exactly the same > as before, when I had it working. The only thing different, however, is > perhaps having chosen the option to install LXQt in favor of GNOME, which was > the environment installed when it was able to boot without issue. The same > blockage occurs when LXDE is chosen, as well. I wish it would allow you to > install your system without needing to choose a desktop environment, which > just lengthens installation time by a great amount. > > From my experiences alone in the last few days, the ppc64 versions really put > the "unstable" in "Sid". > > In any case, please advise. Thank you. > > From: Noah Wolfe > Sent: Friday, February 1, 2019 2:08 PM > To: Rick Thomas > Cc: PowerPC List Debian; John Paul Adrian Glaubitz > Subject: Re: PPC64 Image Installation Error > > Thanks, Rick. > I got around this issue by simply making the /boot partition (sda2) 1 GB > instead of 1 MB, and the / partition (sda3) doubled to 80 GB. Using this same > method with a reinstall of Ubuntu Server 16.04 (which was giving me the same > error when it was installed in partitions 6, 7, 8, and 9, below Sid) I am > now, as a result, able to dual boot between it and Debian. > So it really goes to show that sometimes the best solutions in life are > usually the easiest ones. > But I still found the 01-27 build to be unable to install the kernel due to > an apparent "lack of space" in whatever configuration I put it in (save for > the aforementioned method), so that still needs to be fixed. > And, a lot of ppc64 packages are experiencing issues unseen in the powerpc > equivalents. Xfwm4 puts out graphical glitches and artifacts when any windows > are moved, or when the cursor moves over any windows, and GNOME 3 hasn't > displayed any color besides pinkish hues since Jessie, if I'm remembering > correctly. > Anyway, thank you for your time. > N > On Jan 31, 2019 5:16 AM, Rick Thomas wrote: > > > > Hi Noah, > > > > Is it possible for you to temporarily replace the hard drive in your > > machine with one you don’t mind experimenting on? > > > > If so, after a clean installation onto the fresh hard disk, what you want > > to finish up your installation with is something that looks kind of like > > this: > > > > > root@msmini:~# mac-fdisk -l /dev/sda > > > /dev/sda > > > #type name length base > > > ( size ) system > > > /dev/sda1 Apple_partition_map Apple 63 @ 1 > > > ( 31.5k) Partition map > > > /dev/sda2 Apple_Bootstrap untitled1954 @ 64 > > > (977.0k) NewWorld bootblock > > > /dev/sda3 Apple_UNIX_SVR2 untitled 51 @ 2018 > > > (244.1M) Linux native > > > /dev/sda4 Linux_LVM untitled 468360060 @ 502019 > > > (223.3G) Unknown > > > /dev/sda5 Apple_Free Extra 49 @ > > > 468862079 ( 24.5k) Free space > > > > > > Block size=512, Number of Blocks=468862128 > > > DeviceType=0x0, DeviceId=0x0 > > > > > > root@msmini:~# lvs > > > LV VGAttr LSize Pool Origin Data% Meta% Move Log > > > Cpy%Sync Convert > > > root msmini-vg -wi-ao <45.61g > > > > > > swap_1 msmini-vg -wi-ao 976.00m > > > > > > > > >
