Hi list,
I have fedora installed on my powerbook G4. I get the message "vt: argh, driver_data is null" which hangs the machine every time I try to do a "shutdown -h now" command.
Any ideas as to what the problem might be .
Thanks Rene
On Mon, 2004-11-01 at 11:09 -0600, Rene Salmon wrote:
I have fedora installed on my powerbook G4. I get the message "vt: argh, driver_data is null" which hangs the machine every time I try to do a "shutdown -h now" command.
Would help if you gave us what kernel version you were running (uname -a output maybe)
Could be related to the console race patch - http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-m...
Opps sorry. Running kernel 2.6.8-1.541 on Fedora "FC3test2" from
http://fedora.linux.duke.edu/fedorappc/FC3test2
Would the 2.6.3 patch be included in 2.6.8? I looked in
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.8.1/2.6.8...
but did not see a console patch for 2.6.8.1.
Thanks for the help
Rene
On Tue, Nov 02, 2004 at 04:23:37AM +1100, Colin Charles wrote:
On Mon, 2004-11-01 at 11:09 -0600, Rene Salmon wrote:
I have fedora installed on my powerbook G4. I get the message "vt: argh, driver_data is null" which hangs the machine every time I try to do a "shutdown -h now" command.
Would help if you gave us what kernel version you were running (uname -a output maybe)
Could be related to the console race patch - http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-m... -- Colin Charles, byte@aeon.com.my http://www.bytebot.net/ "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
On Mon, 2004-11-01 at 12:04 -0600, Rene Salmon wrote:
Would the 2.6.3 patch be included in 2.6.8? I looked in
Try upgrading to the latest rawhide, and seeing if this gets fixed (in fact, so much within Fedora has changed from then, you'd probably want to yum update/upgrade your way thru[1])
[1] - and yes, its a painless upgrade. Just point to a mirror of rawhide latest, yum update (or upgrade) and all the packages install fine in a couple of hours (for an everything install)
Hi,
Though I would report back that upgrading to the latest rawhide (this morning) did fix the problem. I no longer get the "driver_data is null" message when I shutdown.
A couple of things:
1)I did not really upgrade I did a clean new install.
2)After the clean install the machine will not boot it will hang at the very beginning with this message.
"unable to open an initial console" is displayed, then a few SELinux context messages, then it just hangs.
This is a reported bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133684
solution to this that worked for me was to add these lines to the /etc/yaboot.conf file.
sysmap=/boot/System.map-xxxx initrd=/boot/initrd-xxxxx
Now a have a happy Mac running linux.
Thanks for the help.
Rene
On Tue, Nov 02, 2004 at 08:38:50AM +1100, Colin Charles wrote:
On Mon, 2004-11-01 at 12:04 -0600, Rene Salmon wrote:
Would the 2.6.3 patch be included in 2.6.8? I looked in
Try upgrading to the latest rawhide, and seeing if this gets fixed (in fact, so much within Fedora has changed from then, you'd probably want to yum update/upgrade your way thru[1])
[1] - and yes, its a painless upgrade. Just point to a mirror of rawhide latest, yum update (or upgrade) and all the packages install fine in a couple of hours (for an everything install) -- Colin Charles, byte@aeon.com.my http://www.bytebot.net/ "First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
On Thu, 2004-11-04 at 14:39 -0600, Rene Salmon wrote:
1)I did not really upgrade I did a clean new install.
So, today I did a clean install - iMac DV SE
2)After the clean install the machine will not boot it will hang at the very beginning with this message.
"unable to open an initial console" is displayed, then a few SELinux context messages, then it just hangs.
Got that today
This is a reported bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133684
solution to this that worked for me was to add these lines to the /etc/yaboot.conf file.
sysmap=/boot/System.map-xxxx initrd=/boot/initrd-xxxxx
So, my /etc/yaboot.conf file now looks like (and yes, i ybin'ed it):
image=/boot/vmlinuz-2.6.9-1.667 label=Linux initrd=/boot/initrd-2.6.9-1.667.img sysmap=/boot/System.map-2.6.9-1.667 root=/dev/hda2 read-only
Now a have a happy Mac running linux.
It hates me!
On Fri, 2004-11-05 at 16:55 +1100, Colin Charles wrote:
Now a have a happy Mac running linux.
It hates me!
Its worthwhile to say that once I configure udev to work without an initrd, things seem to miraculously work afterward
Booting with selinux=0 helps, to get rid of the avc messages (ah heck, in active targeted mode, it might as well be disabled ;-) )
Hi,
So, my /etc/yaboot.conf file now looks like (and yes, i ybin'ed it):
image=/boot/vmlinuz-2.6.9-1.667 label=Linux initrd=/boot/initrd-2.6.9-1.667.img sysmap=/boot/System.map-2.6.9-1.667 root=/dev/hda2 read-only
It hates me!
Not sure why it worked for me but just to double check here is what my yaboot.conf file looks like.
boot=/dev/hda12 device=/pci@f2000000/mac-io@17/ata-4@1f000/disk@0: init-message=Welcome to Fedora Core! Hit <TAB> for boot options.
partition=9 timeout=30 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot default=Linux defaultos=linux
image=/boot/vmlinuz-2.6.9-1.667 label=Linux root=/dev/hda9 sysmap=/boot/System.map-2.6.9-1.667 initrd=/boot/initrd-2.6.9-1.667.img read-only
macosx=/dev/hda11
----------------------------------------------------------- other thins to check
make sure you have /dev/console
[rsalmon@suma ~]$ ls -l /dev/console crw------- 1 root root 5, 1 Nov 5 21:24 /dev/console
Hope it helps.
Rene
-
Colin Charles -
Rene Salmon