You can install all those three packages at once by specifying the
required version:
sudo apt-get install chromium-browser=65.0.3325.181-0ubuntu1
chromium-codecs-ffmpeg=65.0.3325.181-0ubuntu1
chromium-codecs-ffmpeg-extra=65.0.3325.181-0ubuntu1
Then you can freeze these versions:
sudo apt-mark
You can install all those three packages at once by specifying the
required version:
sudo apt-get install chromium-browser=65.0.3325.181-0ubuntu1
chromium-codecs-ffmpeg=65.0.3325.181-0ubuntu1
chromium-codecs-ffmpeg-extra=65.0.3325.181-0ubuntu1
Then you can freeze these versions:
sudo apt-mark
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481132/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481131/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481130/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "RelatedPackagesPolicy.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481133/+files/RelatedPackagesPolicy.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481134/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481123/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481127/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481129/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481124/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481128/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "DiskUsage.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481125/+files/DiskUsage.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481126/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481134/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921187
Title:
apport information
** Attachment added: "RelatedPackagesPolicy.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481133/+files/RelatedPackagesPolicy.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481132/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481131/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921187
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481130/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481129/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921187
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481128/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481127/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921187
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481126/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921187
Title:
apport information
** Attachment added: "DiskUsage.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481125/+files/DiskUsage.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921187
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481124/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1921187/+attachment/5481123/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected bionic
** Description changed:
From dpkg.log:
2021-03-13 17:56:19 upgrade chromium-browser:i386
87.0.4280.66-0ubuntu0.18.04.1 89.0.4389.82-0ubuntu0.18.04.1
Won't start at all after this upgrade. Downgrading to 65.0.3325.181-0ubuntu1
apport information
** Tags added: apport-collected bionic
** Description changed:
From dpkg.log:
2021-03-13 17:56:19 upgrade chromium-browser:i386
87.0.4280.66-0ubuntu0.18.04.1 89.0.4389.82-0ubuntu0.18.04.1
Won't start at all after this upgrade. Downgrading to 65.0.3325.181-0ubuntu1
Public bug reported:
>From dpkg.log:
2021-03-13 17:56:19 upgrade chromium-browser:i386 87.0.4280.66-0ubuntu0.18.04.1
89.0.4389.82-0ubuntu0.18.04.1
Won't start at all after this upgrade. Downgrading to 65.0.3325.181-0ubuntu1
works. Downgrading to 87.0.4280.66-0ubuntu0.18.04.1 is not possible
Public bug reported:
>From dpkg.log:
2021-03-13 17:56:19 upgrade chromium-browser:i386 87.0.4280.66-0ubuntu0.18.04.1
89.0.4389.82-0ubuntu0.18.04.1
Won't start at all after this upgrade. Downgrading to 65.0.3325.181-0ubuntu1
works. Downgrading to 87.0.4280.66-0ubuntu0.18.04.1 is not possible
2018-11-29 19:54 UTC+02.00, Riccardo Mottola :
> Riccardo Mottola wrote:
>
> Is there a way to list files from OF, just to be sure the device and paths
> are correct?
>
I think there is a 'dir' command with same syntax as 'boot'.
Risto
2017-04-17 23:29 UTC+03.00, Linux User #330250 :
>
> CPU Bus ROM Software ROMWorld
> ---+---+---+---+
> 68k NuBus Mac OS ROM (68k)-- --
>
> PowerPC PCI System ROM
I still have a few powerpc Macs, both OldWorld and NewWorld.
The oldest one (6100/66) has no Open Firmware, the next one (7600/132)
has OF 1.x, then comes Beige G3 with OF 2.x, and the first NewWorld
machine Blue G3 with OF 3.x.
- the 6100 can only run MkLinux on top of Mach microkernel.
- the
2017-04-14 12:20 UTC+03.00, Mathieu Malaterre :
>
> while (Performa)54xx,6400 is reported to have OF 2.0:
>
NewWorld machines have at least OF 3.0.
Risto
Hi Joel,
2017-03-29 17:43 UTC+03.00, Joel Whitehouse :
>
> Is there any way to get dnsmasq to log when it issues a new query to a
> resolver?
>
You can run tcpdump on upstream interface and port 53.
Risto
___
Dnsmasq-discuss
Hi Simon,
2017-03-23 0:04 UTC+02.00, Simon Kelley :
>
> This indicates that dnsmasq has been configured to force the packets to
> the upstream server via eth0. To do that requires an operation on the
> socket which can only be done as root, so the socket has to be
>
Hi Albert,
2017-03-21 22:47 UTC+02.00, Albert ARIBAUD :
>
> I can't see why your dnsmasq would only use one port. This would be the
> behavior for -Q0 (or -Q45807, but your dnsmasq does not have this option
> in its command line.
>
I took in the source package and added
Hi,
2017-03-21 16:23 UTC+02.00, /dev/rob0 :
>
> Did you ever show us the contents of this --conf-dir? It could have
> a file with "query-port".
> --
Good point. I forgot. I did check it, though, and the directory was empty.
Risto
___
Zyxel doesn't have a problem with same source port:
https://www.dropbox.com/s/wxdl480hwr39j12/dns-03.pcap?dl=1
Same commands as in pcap-01.
Risto
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
Hi Albert,
2017-03-21 0:03 UTC+02.00, Albert ARIBAUD :
>
> Source IP is not the same in both pcaps. 1st pcap queries 8.8.8.8 and
> 192.168.1.1 from 192.168.1.33, while 2nd pcap queries are from
> 192.168.1.100. Can you clarify your network setup?
>
IP is differerent, but
Ok, no pcap attachments, here is a link, I hope it gets through:
https://www.dropbox.com/s/3nfx2kr2kxsw0ud/dns-01.pcap?dl=1
Risto
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
Hi Albert,
Thanks for your help so far.
2017-03-20 22:18 UTC+02.00, Albert ARIBAUD :
>
> So, back to the basics: let's start with a capture of DNS traffic. Can
> you run wireshark or tcpdump on your Lubuntu and capture a few requests
> for resolution?
>
Attached a small
This is the pcap against TP-link:
https://www.dropbox.com/s/c1edxlpmar8euvi/dns-02.pcap?dl=1
This time I only did:
1) 'host google.com 192.168.1.1'
2) 'host google.fi 192.168.1.1'
The rest of the requests came through dnsmasq, and received no answer.
They are repeated forever.
Risto
2017-03-20 21:05 UTC+02.00, Albert ARIBAUD :
>
> (I don't see the point of this restruction but hey, that's TP-Link's
> choice.)
>
I might use the word 'bug' instead of 'choice'.
>
> Ok, so the OS is not limiting the ports per se.
>
> You said the command line did not
Hi Albert,
2017-03-20 20:30 UTC+02.00, Albert ARIBAUD :
>
> I don't kow about dnsmasq per se, but the range of ports an application
> can use is controlled by the kernel -- on my 16.04 Xubuntu, that is
> defined by /proc/sys/net/ipv4/ip_local_port_range. Does your system
>
Hi,
I'm running Lubuntu 16.04 with dnsmasq 2.75-1ubuntu0.16.04.1 under
NetworkManager's control.
When forwarding DNS requests, dnsmasq uses same source port (per
interface) every time.
Compared to Ubuntu 14.04 with dnsmasq 2.68-1ubuntu0.1, which used
different ports.
The command line options
Public bug reported:
info: config: failed to parse line, skipping, in
"/etc/spamassassin/mailscanner.cf": use_auto_whitelist 0
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: sa-compile 3.4.0-1ubuntu2.1
ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
Uname: Linux
2016-06-15 23:57 UTC+03.00, Alex Santos :
>
> Section "Monitor"
> Identifier "Configured Monitor"
> HorizSync 58-62
> VertRefresh 75-117
> EndSection
>
Yes, that's it. The file in question is '/etc/X11/xorg.conf'. In
addition to the Monitor section you would probably need at
Hi Alex,
iMac G3's monitor is very sensitive to the sync frequency: you must
create an xorg.conf with correct values for HorizSync and VertRefresh.
I can come later with the details, but they can be found in some old
threads, too.
Risto
Hi,
2016-04-28 0:12 UTC+03.00, Riccardo Mottola :
>
> proven that currently... I can't use the card's firmware (I get the
> warning + doesn't work) but it doesn't work with 9.48 either (no
> warning but it doesn't work)... I don't see many options.
> Perhaps there was
What firmware version did you have before? Looks like the card has
8.70, and Debian loads 9.48. You could try to rename the file
agere_sta_fw.bin, forcing the card to use its own firmware. I have
seen situations where loading 9.48 gives me WPA but takes away WEP.
Risto
I can confirm that it works now in daily build 20160405-3 on both platforms.
Risto
I can confirm that it works now in daily build 20160405-3 on both platforms.
Risto
The corresponding source package number is 3.16.7-ckt20-1+deb8u4.
Risto
The corresponding source package number is 3.16.7-ckt20-1+deb8u4.
Risto
I meant to say that the bug is in version 3.16.0-4 (64k page) and not
in 4.4.0-rc7 (4k page).
Risto
I meant to say that the bug is in version 3.16.0-4 (64k page) and not
in 4.4.0-rc7 (4k page).
Risto
2016-03-30 12:25 UTC+03.00, Mathieu Malaterre :
>
> Which kernel version are you using ?
>
Originally 3.16.0-4-powerpc64 (Jessie)
Now 4.4.0-rc7-powerpc64 (Peter)
Risto
2016-03-30 12:25 UTC+03.00, Mathieu Malaterre :
>
> Which kernel version are you using ?
>
Originally 3.16.0-4-powerpc64 (Jessie)
Now 4.4.0-rc7-powerpc64 (Peter)
Risto
The other reason for using Peter's kernel is the page size. The
official kernels use 64 k pages that do not work with nouveau.
Risto
I don't know the answer, but I doubt it would help because the problem
(those 64k pages) has been there for quite long.
What went wrong with the 4.4.0-rc7-powerpc64 kernel?
Risto
2016-03-23 4:44 UTC+02.00, Steven Grunza :
> Trying to install 4.4.0-rc7.powerpc64 I got:
>
> dpkg: error processing package linux-headers-4.4.0-rc-powerpc64
> (--install):
> dependency problems - leaving unconfigured
> Setting up linux-image-4.4.0-rc7-powerpc64 (2) ...
>
I run successfully 4.4.0-rc7-powerpc64 on my PowerMac G5. (Thanks, Peter.)
https://drive.google.com/folderview?id=0B8pqd5Ots1vfT2puX09CYjEwcFk=sharing
Risto
Hi Steven,
2016-03-17 2:25 UTC+02.00, Steven Grunza :
> Should I expect Debian debian-8.3.0-powerpc-xfce-CD-1 to work on an Apple
> iMac G5?
>
Yes.
>
> I tried installing it and just have a blank screen.
>
> Using Control-Option-F1 I have a text console on the built-in
I am sorry, but I do not understand. For the first, I cannot install
any packages on a cd.
Package: yaboot
Version: 1.3.17-1
Looks like yaboot does not find its conf file any more.
I'm trying to install (CD) Debian on a PowerMac G5 (7,3). Jessie
(yaboot 1.3.16) works.
Stretch (yaboot 1.3.17) does not. It complains:
cd:-1,\install\yaboot.conf: Unable to open file, Invalid device
Or,
Looks like yaboot does not find its conf file any more.
I'm trying to install (CD) Debian on a PowerMac G5 (7,3). Jessie
(yaboot 1.3.16) works.
Stretch (yaboot 1.3.17) does not. It complains:
cd:-1,\install\yaboot.conf: Unable to open file, Invalid device
Or, on a Mac mini G4:
There is a good wiki page on this topic:
https://wiki.debian.org/Keyboard
In worst case you could edit /etc/default/keyboard directly, and then
reboot to be sure that the changes take effect.
Risto
The machine has a PowerPC processor, it cannot run Intel code. You
would need a PowerPC CD image.
Open Firmware understands a Mac style partition table and an HFS file
system. Those are present on the PowerPC Install CD images (hybrid
CDs, they contain an ISO9660 file system as well).
Risto
I don't remember any PowerPC Macs that wouldn't allow me to enter Open
Firmware. (The early beige series machines, G3 and below, sent the
output to serial port, not screen, by default. It was possible to
change once you got there.)
Some machines require accurate timing to get into Open Firmware.
Lubuntu here, too, 14.04.3 LTS, evince 3.10.3-0ubuntu10.2.
Two documents with the problem:
http://www.hel.fi/static/hkr/luvat/ilmoitus_liikennemerkin_asettamisesta.pdf
http://www.hel.fi/static/hkr/luvat/ilmoitus_tyosta_yleisella_alueella.pdf
I can typically fill in two or three fields, then it
Lubuntu here, too, 14.04.3 LTS, evince 3.10.3-0ubuntu10.2.
Two documents with the problem:
http://www.hel.fi/static/hkr/luvat/ilmoitus_liikennemerkin_asettamisesta.pdf
http://www.hel.fi/static/hkr/luvat/ilmoitus_tyosta_yleisella_alueella.pdf
I can typically fill in two or three fields, then it
Lubuntu here, too, 14.04.3 LTS, evince 3.10.3-0ubuntu10.2.
Two documents with the problem:
http://www.hel.fi/static/hkr/luvat/ilmoitus_liikennemerkin_asettamisesta.pdf
http://www.hel.fi/static/hkr/luvat/ilmoitus_tyosta_yleisella_alueella.pdf
I can typically fill in two or three fields, then it
Public bug reported:
There seems to be an error in the file filesystem.squashfs. I thought
flash memory doesn't fail.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
I was brave and tried the installation anew: it went better, it just
hung in the end, restoring previous packages, and I stopped it with
the X in the corner. But the installation seems to be functional, I'm
using it right now.
The difference was that I started the installation from grub menu, not
I also ran the memory test. I had to add the forcepae option before
booting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474505
Title:
Segfault installing 14.04.2 from USB stick
To manage
Ok, I checked the md5sum of filesystem.squashfs against md5sum.txt, and
they were different, so, I assume that, at some stage, an error has
crept in. I downloaded a later release and pushed it into the stick, and
installing gave me a different error, of which I made a new error
report. I guess
Public bug reported:
I have checked the md5sum of the image written to the stick. The stick
is 1 GB.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8.6
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion:
Hi Rick,
2015-04-30 12.49 UTC+03.00, Rick Thomas rbtho...@pobox.com:
Did you ever discover how to fix it without holding back on the kernel level?
No, I didn't. (Sorry for the late reply.)
I'm using X, so the 'disable KMS' solution doesn't sound good.
Risto
--
To UNSUBSCRIBE, email to
Hi,
There is also another, older, driver, snd-powermac. I'm not sure which
one is correct for your hardware. Can you see a message in dmesg that
says something like 'snd-powermac no longer handles machines with
something'?
Risto
--
To UNSUBSCRIBE, email to
Hi,
I checked my PowerBook6,4 running Debian 7.0 with kernel 3.2.0:
- snd-aoa is blacklisted
- snd-powermac is loaded and works
I don't say that snd-aoa cannot be used, but at least snd-powermac used to work.
Risto
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a
Hi Konstantinos,
2015-02-03 22:07 UTC+02.00, Konstantinos Margaritis mar...@freevec.org:
If the offer still stands, I will send you a private message to arrange
this.
Yes, it does.
Risto
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe.
Hi,
2015-02-03 11:38 UTC+02.00, Konstantinos Margaritis mar...@freevec.org:
That would be a nice choice, if it's in a working condition I can
fix/replace the fans, do you know if the system is DDR/DDR2?
It's DDR (400). I'm afraid it cannot be expanded over 2 GB.
Risto
--
To UNSUBSCRIBE,
Hi,
2015-02-02 21:44 UTC+02.00, Konstantinos Margaritis mar...@freevec.org:
I'd like to help on the ppc64 port, I have ppc32 hardware,
ppc64/ppc64el remote VM accounts but no actual ppc64 hardware. I
just lost an extremely low bid for an imac g5 on ebay and am short
on cash for another, but
Hi,
This is probably an old issue, possibly discussed before, even on this list.
I've been holding my linux-image as version 3.2.0-2 to avoid the problem.
So, the problem: after upgrading to 3.2.0-4, X display is not working.
According to Xorg.log everything is as before, but the screen remains
Hi again,
This is another old issue, been there probably since kernel 3...
Airport cannot be used, the relevant dmesg output is following:
[8.093462] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
[8.189942] Registered led device: b43-phy0::tx
[8.189990] Registered led device:
This seems to be kernel related: it used to work with 2.6 kernel.
Risto
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
2014-11-01 17:55 UTC+02.00, Athanasios Anastasiou athanastas...@gmail.com:
If anyone has a working slotloader G3 @400MHz can you please post your
device section?
Driver ati
Option UseFBDev false
Option SWCursor true
Option ForcePCIMode true
Option XAANoOffscreenPixmaps true
Option DRI true
2014-10-30 20:34 UTC+02.00, Athanasios Anastasiou athanastas...@gmail.com:
But this comment about yaboot confused me a bit. Do i have to have matching
settings between yaboot and X (how come?)
I don't think so. Check your Xorg.0.log and send it here.
Risto
--
To UNSUBSCRIBE, email to
iMac G3 is very sensitive to the correct display frequencies. X will
show black screen, unless you put into xorg.conf's Section Monitor:
HorizSync 58-62
VertRefresh 75-117
Risto
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Riccardo,
I've applied similar patches with a recipe resembling the following:
- create a file with the patch: mach64.patch
- install dpkg-dev: apt-get install dpkg-dev
- get and extract the package source: apt-get source xf86-video-mach64
- cd into the directory
- apply the patch: patch -p1
One option you might try in your xorg.conf's Section Device:
Option NoAccel true
I have put it in mine. I don't remember why. This is a 12 PowerBook 1.33 MHz.
lspci.
:00:10.0 VGA compatible controller: NVIDIA Corporation NV34M
[GeForce FX Go5200] (rev a1)
dmesg:
[ 10.305792] [drm]
2014-03-03 2:16 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:
boot: Linux video=DVI-I-1:d video=DVI-I-2:1280x1024:@75 video=TV-1:d
This is basically the same as my solution: unused outputs ADC and TV
are disabled, in addition the screen resolution is specified for DVI.
Risto
--
To
You are right, Aaron. I also have that 'video=TV-1:d' on the kernel
command line.
It comes from /etc/yaboot.conf (so you don't need to write it on every boot):
append= video=TV-1:d
F.ex.:
image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
append=
2014-03-03 18:42 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:
Can you post your xorg.conf?
Here it is:
--
Section Device
Identifier Configured Video Device
BusID PCI:240:16:0
Driver nouveau
Option Monitor-TV-1 Configured Monitor
Option NoAccel
2014-03-02 15:12 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:
This is Debian Wheezy on the Power Mac G5 with GeForce FX 5200 Ultra.
I have exactly the same machine. Kernel is 3.1.0-1-powerpc64.
Which output connector are you using, DVI (DVI-I-2) or ADC (DVI-I-1)?
If you can ssh into the
X Probabl selects wrong output. I'm using DVI, and the following
/etc/X11/xorg.conf makes it work:
--
Section Device
Identifier Configured Video Device
BusID PCI:240:16:0
Driver nouveau
Option Monitor-TV-1 Configured Monitor
Option NoAccel true
2014/1/22, Geoff Down geoffd...@fastmail.net:
From the Debian PPC Install Manual:
'To share information between the Mac OS X and GNU/Linux systems, an
exchange partition is handy. HFS, HFS+ and MS-DOS FAT file systems are
supported by MacOS 9, Mac OS X and GNU/Linux. '
I wouldn't have
2014/1/22, Geoff Down geoffd...@fastmail.net:
I can now boot into the command line and login.
Is there any way to install Gnome now in a way that allows me to debug
any problems - starting it from the command line and being able to
escape back into a shell perhaps?
I would first install
2014/1/22, Geoff Down geoffd...@fastmail.net:
That means I could really do with a way of transferring log files etc
between the Linux drive and the OSX drive. OSX can't access the Linix
filesystem apparently - can I make Linux access the OSX disk?
I wouldn't recommend trying that. In worst
1 - 100 of 318 matches
Mail list logo