You can subscribe to this list here.
2006 |
Jan
|
Feb
(1) |
Mar
(39) |
Apr
(76) |
May
(63) |
Jun
(56) |
Jul
(45) |
Aug
(112) |
Sep
(65) |
Oct
(115) |
Nov
(114) |
Dec
(100) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(87) |
Feb
(114) |
Mar
(179) |
Apr
(218) |
May
(147) |
Jun
(246) |
Jul
(155) |
Aug
(133) |
Sep
(103) |
Oct
(61) |
Nov
(37) |
Dec
(12) |
2008 |
Jan
(20) |
Feb
(123) |
Mar
(106) |
Apr
(59) |
May
(51) |
Jun
(62) |
Jul
(24) |
Aug
(42) |
Sep
(12) |
Oct
(21) |
Nov
(6) |
Dec
(33) |
2009 |
Jan
(16) |
Feb
(17) |
Mar
(11) |
Apr
(2) |
May
(4) |
Jun
(18) |
Jul
(24) |
Aug
(22) |
Sep
(31) |
Oct
(4) |
Nov
(2) |
Dec
|
2010 |
Jan
(19) |
Feb
(3) |
Mar
(26) |
Apr
(37) |
May
(10) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(3) |
Nov
(1) |
Dec
(2) |
2011 |
Jan
(11) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(8) |
Dec
|
From: Sebastian T. <se...@sm...> - 2011-01-09 18:40:22
|
Hi all, I have an aluminium Macbook Pro (Jan 2008) with a broken internal optical drive. I can boot from the Snow Leopard install DVD using the external optical drive without any problem whatsoever but it simply will not boot from any of the GNU/Linux boot CDs I have at my disposal (Debian Squeeze, Debian Lenny, Ubuntu 9.0, I've even tried a GParted Live CD). The result is always the same - rEFIt identifies the CD as a GNU/Linux boot CD, I select it, hit Enter, smile at Tux in the middle of my screen... but then everything goes black and I'm presented with the depressingly unhelpful error message "Missing operating system". I've synced the partition tables, the EFI firmware is as up-to-date as it can be, I've even tried a bootable USB flash drive or two - again rEFIt identifies the media correctly - but then... nada. Any advice/tips/pointers/suggestions very much appreciated. Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap |
From: Osamu A. <os...@de...> - 2010-12-08 13:56:00
|
On Tue, Oct 26, 2010 at 08:58:02AM -0400, Geoffrey Myers wrote: > I want to add another nic to my macbookpro. I'm guessing my only options > would be an expresscard. Anyone know of one? Google's not been helpful. That is one option. If speed is not the issue, USB-to-Ethernet dongle is another option. My old MacBook does not even have expresscard slot but I could manage this way when I was playing :-) Osamu |
From: mike d. <fl...@po...> - 2010-12-07 04:15:51
|
Hi there, I'm trying to get Debian to work properly on one of the new MacBookAir machines. I've started documenting my steps so it can be of some use to someone eventually: http://dentifrice.poivron.org/laptops/macbookair3,1/ It's a work in progress, quite a lot of things need to be fixed and/or figured out still and I'm running out of time to play with it, so contributions more than are welcome! Cheers, -- mike dentifrice <fl...@po...> |
From: mike d. <fl...@po...> - 2010-11-08 18:20:14
|
Hey there, In spite of some browsing, I haven't been able to find any information regarding the use of GNU/Linux (be it Debian or Ubuntu) on the high-end iMac models which last came out (iMac 11,3; 27"; mid 2010; with either HD 5670 or HD 5750 for graphics). I'm considering getting the iMac 11,3 with an i5 or i7 processor (I don't care much about the graphics chip, provided it works with open source drivers and provides accelerated 2D graphics - 3D not being important for me right now). I'd be glad to read stories, be they successful or not, and/or be pointed towards documentation I may have missed. A thread [1] on ubuntuforums describes a persistent "black screen" issue on the iMac 11,1 model. However, there's no mention of the 11,3 model, which ships with different graphics as stated above. Thanks a lot in advance for your input! 1. http://ubuntuforums.org/showthread.php?t=1476226 -- mike dentifrice <fl...@po...> |
From: Tino K. <tin...@ti...> - 2010-10-26 15:33:43
|
On Tue, Oct 26, 2010 at 08:58:02 -0400, Geoffrey Myers wrote: > I want to add another nic to my macbookpro. I'm guessing my only options > would be an expresscard. Anyone know of one? Google's not been helpful. The page is German, but at least you get the product names: http://geizhals.at/eu/?cat=nwo&asuch=expresscard Regards, Tino |
From: Osamu A. <os...@de...> - 2010-10-26 15:32:53
|
On Tue, Oct 26, 2010 at 08:58:02AM -0400, Geoffrey Myers wrote: > I want to add another nic to my macbookpro. I'm guessing my only options > would be an expresscard. Anyone know of one? Google's not been helpful. I did not do this ... but there are other option. But I have used USB-Ethernet dongle with my macbook without any problem. (Not that I needed it but just checked it when I bought that for my other PC without any expresscard nor PCMCIA. Oh my macbook lacks them too) |
From: Geoffrey M. <li...@se...> - 2010-10-26 13:45:38
|
I want to add another nic to my macbookpro. I'm guessing my only options would be an expresscard. Anyone know of one? Google's not been helpful. -- Until later, Geoffrey "I predict future happiness for America if they can prevent the government from wasting the labors of the people under the pretense of taking care of them." - Thomas Jefferson |
From: Tino K. <tin...@ti...> - 2010-07-09 12:34:20
|
Hi, after playing around with grub-efi, and fixing grub-install in Debian sid, I know have hosed graphics in my Mac mini Core 2 Duo. I don't get a video signal after power on, in the EFI menu, in grub-efi and when booting OS X. There are two ways to restore the video: suspend in OS X and resume, or boot Linux. I was suggested to reset the NVRAM, by using command + option + p + r after power on. However, according to the instructions I should hear two beeps if the reset was successful, and I don't hear the beeps. So I don't know if the reset really happened. I have a PC keyboard, so I use windows + alt + p + r. Should this work? Should I hear the beep on a Mac mini? Any other hints to restore the video? I already pressed the power button after removing the power cord. Regards, Tino |
From: Justin P. M. <jus...@gm...> - 2010-05-14 08:44:15
|
On 05/14/10 01:07, mike dentifrice wrote: > Justin P. Mattock a dit: >> Hmm.. Thought grub2 needs to be compiled with efi support or >> something. >> (standard x86_32 build over here) > > Yes. You need to either compile grub2 with '--with-platform=efi' or use > the grub-efi package if you're using Debian or Ubuntu. See instructions > on http://grub.enbug.org/TestingOnEFI and more Macintosh related details > on http://grub.enbug.org/TestingOnMacbook. > >> If this then is not the case, then(probably) my machine needs to >> have the framebuffer address added to efifb.c > > It would sure be nice to know (and possibly get it fixed upstream). I'm > assuming your machine has 64bit EFI (my Macbook2,1 and Tino's MacMini > use 32bit EFI, AFAIK). > >> From what I read over threads [1], while success has been reached with > some 32bit Macs (especially those with intel graphics), a lot remains to > be done of the more recent Macs so they can boot EFI alright (the latest > models partly implementing UEFI, I think). > > 1. see http://ubuntuforums.org/showthread.php?t=995704 (beware, it's > _very_ long, hence hard to read... > ah.. yep I haven't yet compiled grub2 with efi, (maybe)causing the stuckage with efifb, but then again I tried with nvidiafb, and hit the same green colored stuckage(but could be wrong), leading me to believe just a simple adding of an address but then again In any case I'll try to work this.. (be nice to get some patches sent upstream for this area). Justin P. Mattock |
From: mike d. <fl...@po...> - 2010-05-14 08:20:36
|
Tino Keitel a dit: > I didn't try efifb. I just use the DRM framebuffer along with kernel > mode setting, which is also used by the native Intel driver in Xorg. Oh, I'm gonna give that a try then. > > However, a few questions remain for me: - what are the actual > > advantages and drawbacks from booting in EFI on such a platform? > > You don't have to mess around with gptsync, which is limited to 4 > partitions. And in my setup, it created a dummy partition before the > EFI partition, lowering the limit to 3. Also, there is no delay at > boot time which is caused by the legacy BIOS. Right. The partition limit is not a big deal for me, and I don't mind about the faster bootup procedure, but is there another obvious benefit, or any drawback for that matter? > > - where is it best to put the grub.efi EFI application? is it > > advised to have it sit on the first EFI system partition, within the > > EFI folder? - if not, where? > > I created a small HFS+ partition only for grub. It has no journal, so > I can also write it in Linux to update grub or modify grub.cfg. Ok. So - what is the EFI system partition for? Seemed like a good place to put EFI applications, but when I mount it under Debian, it shows empty, while there's an EFI folder in it when I mount it under MacOS X. Any eplanation for that? Cheers, -- mike dentifrice <fl...@po...> |
From: mike d. <fl...@po...> - 2010-05-14 08:14:24
|
Tino Keitel a dit: > Instructions for what? I just boot an unpatched kernel which uses > kernel mode setting for intel graphics. However, I needed to include > this to my grub.cfg: > > search --set -f /boot/vbios.bin > insmod loadbios > loadbios /boot/vbios.bin /boot/int10.bin Here goes the grub config for my MacBook2,1. I tried to use the BIOS dumps, but it wouldn't work, and it turns out I don't need them to boot, since 'fakebios' is sufficient: menuentry "Debian Squeeze" { fix_video fakebios linux /vmlinuz root=/dev/sda4 video=efifb initrd /initrd.img } AFAIK, fix_video is only used to fix the grambled screen during the boot sequence, and is not necessary if you don't care about the text console. -- mike dentifrice <fl...@po...> |
From: mike d. <fl...@po...> - 2010-05-14 08:07:46
|
Justin P. Mattock a dit: > Hmm.. Thought grub2 needs to be compiled with efi support or > something. > (standard x86_32 build over here) Yes. You need to either compile grub2 with '--with-platform=efi' or use the grub-efi package if you're using Debian or Ubuntu. See instructions on http://grub.enbug.org/TestingOnEFI and more Macintosh related details on http://grub.enbug.org/TestingOnMacbook. > If this then is not the case, then(probably) my machine needs to > have the framebuffer address added to efifb.c It would sure be nice to know (and possibly get it fixed upstream). I'm assuming your machine has 64bit EFI (my Macbook2,1 and Tino's MacMini use 32bit EFI, AFAIK). >From what I read over threads [1], while success has been reached with some 32bit Macs (especially those with intel graphics), a lot remains to be done of the more recent Macs so they can boot EFI alright (the latest models partly implementing UEFI, I think). 1. see http://ubuntuforums.org/showthread.php?t=995704 (beware, it's _very_ long, hence hard to read... -- mike dentifrice <fl...@po...> |
From: Justin P. M. <jus...@gm...> - 2010-05-13 16:33:44
|
> > Hmm.. Thought grub2 needs to be compiled with efi support or > something. (standard x86_32 build over here) If this then is not the case, then(probably) my machine needs to have the framebuffer address added to efifb.c Thanks for the info, Ill have a look, and see.(BTW:threads proably all crapped out cause I don't know how to send from a phone); Justin P. Mattock On May 13, 2010, at 8:51 AM, Tino Keitel <tin...@ti... > wrote: > On Thu, May 13, 2010 at 07:08:09 -0700, Justin P. Mattock wrote: > > [...] >> >> Cool.. was looking into using efifb on >> the iMac9,1 but had no luck. Either >> my grub2 needed to be built with >> efi support and/or I needed to add the device >> address to efifb.c >> >> What/where are the instructions? > > Instructions for what? I just boot an unpatched kernel which uses > kernel mode setting for intel graphics. However, I needed to include > this to my grub.cfg: > > search --set -f /boot/vbios.bin > insmod loadbios > loadbios /boot/vbios.bin /boot/int10.bin > > Regards, > Tino > > --- > --- > --- > --------------------------------------------------------------------- > > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users |
From: Tino K. <tin...@ti...> - 2010-05-13 15:51:34
|
On Thu, May 13, 2010 at 07:08:09 -0700, Justin P. Mattock wrote: [...] > > Cool.. was looking into using efifb on > the iMac9,1 but had no luck. Either > my grub2 needed to be built with > efi support and/or I needed to add the device > address to efifb.c > > What/where are the instructions? Instructions for what? I just boot an unpatched kernel which uses kernel mode setting for intel graphics. However, I needed to include this to my grub.cfg: search --set -f /boot/vbios.bin insmod loadbios loadbios /boot/vbios.bin /boot/int10.bin Regards, Tino |
From: Justin P. M. <jus...@gm...> - 2010-05-13 14:08:22
|
On 05/13/10 05:21, Tino Keitel wrote: > On Thu, May 13, 2010 at 14:05:54 +0200, mike dentifrice wrote: > > [...] > >> >> So far, everything seems to be working : efifb provides a nice >> textmode console, and X.org using the 'intel' driver runs seemingly >> just as fast as when legacy booted (judging by the output of >> glxgears). > > I didn't try efifb. I just use the DRM framebuffer along with kernel > mode setting, which is also used by the native Intel driver in Xorg. > >> However, a few questions remain for me: >> - what are the actual advantages and drawbacks from booting in EFI on >> such a platform? > > You don't have to mess around with gptsync, which is limited to 4 > partitions. And in my setup, it created a dummy partition before the > EFI partition, lowering the limit to 3. Also, there is no delay at > boot time which is caused by the legacy BIOS. > >> - where is it best to put the grub.efi EFI application? is it advised to >> have it sit on the first EFI system partition, within the EFI folder? >> - if not, where? > > I created a small HFS+ partition only for grub. It has no journal, so I > can also write it in Linux to update grub or modify grub.cfg. > > Regards, > Tino > > ------------------------------------------------------------------------------ > > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > Cool.. was looking into using efifb on the iMac9,1 but had no luck. Either my grub2 needed to be built with efi support and/or I needed to add the device address to efifb.c What/where are the instructions? I'd like to see if either it's a simple configuration and/or if a patch needs to be created for efifb.c and pushed upstream for these devices(only a few in there I see now). Justin P. Mattock |
From: Tino K. <tin...@ti...> - 2010-05-13 12:39:37
|
On Thu, May 13, 2010 at 14:05:54 +0200, mike dentifrice wrote: [...] > > So far, everything seems to be working : efifb provides a nice > textmode console, and X.org using the 'intel' driver runs seemingly > just as fast as when legacy booted (judging by the output of > glxgears). I didn't try efifb. I just use the DRM framebuffer along with kernel mode setting, which is also used by the native Intel driver in Xorg. > However, a few questions remain for me: > - what are the actual advantages and drawbacks from booting in EFI on > such a platform? You don't have to mess around with gptsync, which is limited to 4 partitions. And in my setup, it created a dummy partition before the EFI partition, lowering the limit to 3. Also, there is no delay at boot time which is caused by the legacy BIOS. > - where is it best to put the grub.efi EFI application? is it advised to > have it sit on the first EFI system partition, within the EFI folder? > - if not, where? I created a small HFS+ partition only for grub. It has no journal, so I can also write it in Linux to update grub or modify grub.cfg. Regards, Tino |
From: mike d. <fl...@po...> - 2010-05-13 12:06:13
|
Tino Keitel a dit: > To answer myself: when booting with EFI, CONFIG_SATA_AHCI needs to be > enabled in the kernel. CONFIG_ATA_PIIX doesn't work. Now I can boot > my Linux using grub-efi. Everything seems to work, including X. Thanks for sharing that with us. Booting my MacBook2,1 with grub-efi had been on my TODO list for a while (especially since it seems to be the only way to boot from a USB stick, and to allow grub to see and therefore access anything else than the internal hard-disk). So, I finally found a bit of time to try it, and successfully booted Debian with grub-efi installed on a USB stick (using 'fix_video' and 'fakebios' in the grub menu entry) while retaining grub-pc on the hard-disk for now. So far, everything seems to be working : efifb provides a nice textmode console, and X.org using the 'intel' driver runs seemingly just as fast as when legacy booted (judging by the output of glxgears). However, a few questions remain for me: - what are the actual advantages and drawbacks from booting in EFI on such a platform? - where is it best to put the grub.efi EFI application? is it advised to have it sit on the first EFI system partition, within the EFI folder? - if not, where? Cheers, -- mike dentifrice <fl...@po...> |
From: mike d. <fl...@po...> - 2010-05-08 01:15:35
|
Hello, As you may know, some of the latest Macbook Pro models (MacbookPro6,2) carry two graphical chips, one being Intel, the other being Nvidia. While initially rumored to be powered by the Optimus Nvidia technology, Switching between the two is actually done in software. I've been trying to find information on potential Linux support for this, but found nothing yet (other than one report saying the intel graphics didn't even appear in the device list under GNU/Linux). Does anyone have more information, and/or one of these new models? It looks like people at http://linux-hybrid-graphics.blogspot.com/ could use some dumps… Thanks, -- mike dentifrice <fl...@po...> |
From: Geoffrey <li...@se...> - 2010-04-21 19:54:33
|
Justin P. Mattock wrote: > are you sure your not using winxp? > http://www.huffingtonpost.com/2010/04/21/mcafee-windows-xp-update-_n_546422.html No, but I'm not using Mcafee... :))))) > > > (just messn!!) > > Justin P. Mattock > -- Until later, Geoffrey "I predict future happiness for America if they can prevent the government from wasting the labors of the people under the pretense of taking care of them." - Thomas Jefferson |
From: Justin P. M. <jus...@gm...> - 2010-04-21 19:09:41
|
are you sure your not using winxp? http://www.huffingtonpost.com/2010/04/21/mcafee-windows-xp-update-_n_546422.html (just messn!!) Justin P. Mattock |
From: Justin P. M. <jus...@gm...> - 2010-04-21 18:59:58
|
On 04/21/2010 11:35 AM, Geoffrey wrote: > Justin P. Mattock wrote: >> On 04/21/2010 09:57 AM, Geoffrey wrote: >>> Justin P. Mattock wrote: >>>> On 04/21/2010 09:30 AM, Geoffrey wrote: >>>>> Justin P. Mattock wrote: >>>>>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>>>>> Justin P. Mattock wrote: >>>>>>>> On 04/21/2010 06:55 AM, Geoffrey wrote: >>>>>>>>> So I rebuilt my kernel, insuring that I had ext3 support and I >>>>>>>>> still get >>>>>>>>> a panic, although it is a different message: >>>>>>>>> >>>>>>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>>>>>>> unknown-block(0,0) >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> check your /etc/fstab and make sure >>>>>>>> that it's /dev/sda* instead of /dev/hda* >>>>>>>> (if your using the older ati-piix it's should >>>>>>>> be /dev/hda* but using the new ati-piix it's >>>>>>>> /dev/sda*)but could be wrong). >>>>>>> >>>>>>> Actually it's using the LABEL nomenclature, do you think this >>>>>>> could be >>>>>>> my problem? >>>>>>> >>>>>>> LABEL=/ / ext3 defaults 1 1 >>>>>>> >>>>>>> >>>>>> >>>>>> could be.. >>>>>> here's what I have: >>>>>> cat /etc/fstab >>>>>> >>>>>> # file system mount-point type options dump fsck >>>>>> # order >>>>>> >>>>>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>>>>> /dev/sda4 swap swap pri=1 0 0 >>>>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>>>>> proc /proc proc defaults 0 0 >>>>>> sysfs /sys sysfs defaults 0 0 >>>>>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>>>>> tmpfs /dev/shm tmpfs defaults 0 0 >>>>>> #none /selinux selinuxfs defaults 0 0 >>>>>> # End /etc/fstab >>>>>> >>>>>> does changing LABEL=/ to your device do anything? >>>>> >>>>> Just tried that, no difference. >>>>> >>>>>> >>>>>> Justin P. Mattock >>>>>> >>>>> >>>>> >>>> >>>> hm.. I'm wondering if your hitting something >>>> with grub and the kernel i.g. I remember hitting something >>>> similar because I had no bzimage just raw make install >>>> vmlinuz(ended up having to upgrade to grub2 so that grub(*) >>>> was able to read the extra bits and so forth or something >>>> in that area). >>>> >>>> Also hit another issue similar as well with >>>> PCI_MMCONFIG [=y] >>>> (but this could already be fixed). >>> >>> I changed my grub entry for root from: >>> >>> root=LABEL=/ >>> >>> to >>> >>> root=/dev/sda8 >>> >>> Now I get a spontaneous reboot. I tried to snap a photo of it before it >>> reboot, but it's blurred. I'll try again. Weird thing is that it says >>> something about wacom driver and then a reference to reiserfs or some >>> such. I don't know what the wacom driver would have to do with reiserfs, >>> but I'm not using reiserfs anyway. >>> >>> >> >> so changing your grub at-least takes care of the unable to find >> VFS thing?! >> and now the system boots up, and then instantly >> reboot's? I have seen reports of things like that, >> but have never hit something like that(if you can try early debugging >> with a remote machine to grab dmesg) > > Not exactly sure how to go about that. I will try to video the boot > process so I can provide better info. > I usually use the ohci1394_dma=early boot option via firwire. that is if the machine crashes early I can see whats going on. (hopefully) In your case you probably already have dmesg since the machine starts up(if this is the case), and then after done with everything reboots(saving the log file (but could be wrong)). also looking through bugzilla I think your hitting this: https://bugzilla.kernel.org/show_bug.cgi?id=14952 (maybe revert this commit and see if you boot up) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=patch;h=1373411ae4cd0caf2e1a35fb801dd9a00b64dea2 Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 18:36:07
|
Justin P. Mattock wrote: > On 04/21/2010 09:57 AM, Geoffrey wrote: >> Justin P. Mattock wrote: >>> On 04/21/2010 09:30 AM, Geoffrey wrote: >>>> Justin P. Mattock wrote: >>>>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>>>> Justin P. Mattock wrote: >>>>>>> On 04/21/2010 06:55 AM, Geoffrey wrote: >>>>>>>> So I rebuilt my kernel, insuring that I had ext3 support and I >>>>>>>> still get >>>>>>>> a panic, although it is a different message: >>>>>>>> >>>>>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>>>>>> unknown-block(0,0) >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> check your /etc/fstab and make sure >>>>>>> that it's /dev/sda* instead of /dev/hda* >>>>>>> (if your using the older ati-piix it's should >>>>>>> be /dev/hda* but using the new ati-piix it's >>>>>>> /dev/sda*)but could be wrong). >>>>>> >>>>>> Actually it's using the LABEL nomenclature, do you think this >>>>>> could be >>>>>> my problem? >>>>>> >>>>>> LABEL=/ / ext3 defaults 1 1 >>>>>> >>>>>> >>>>> >>>>> could be.. >>>>> here's what I have: >>>>> cat /etc/fstab >>>>> >>>>> # file system mount-point type options dump fsck >>>>> # order >>>>> >>>>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>>>> /dev/sda4 swap swap pri=1 0 0 >>>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>>>> proc /proc proc defaults 0 0 >>>>> sysfs /sys sysfs defaults 0 0 >>>>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>>>> tmpfs /dev/shm tmpfs defaults 0 0 >>>>> #none /selinux selinuxfs defaults 0 0 >>>>> # End /etc/fstab >>>>> >>>>> does changing LABEL=/ to your device do anything? >>>> >>>> Just tried that, no difference. >>>> >>>>> >>>>> Justin P. Mattock >>>>> >>>> >>>> >>> >>> hm.. I'm wondering if your hitting something >>> with grub and the kernel i.g. I remember hitting something >>> similar because I had no bzimage just raw make install >>> vmlinuz(ended up having to upgrade to grub2 so that grub(*) >>> was able to read the extra bits and so forth or something >>> in that area). >>> >>> Also hit another issue similar as well with >>> PCI_MMCONFIG [=y] >>> (but this could already be fixed). >> >> I changed my grub entry for root from: >> >> root=LABEL=/ >> >> to >> >> root=/dev/sda8 >> >> Now I get a spontaneous reboot. I tried to snap a photo of it before it >> reboot, but it's blurred. I'll try again. Weird thing is that it says >> something about wacom driver and then a reference to reiserfs or some >> such. I don't know what the wacom driver would have to do with reiserfs, >> but I'm not using reiserfs anyway. >> >> > > so changing your grub at-least takes care of the unable to find > VFS thing?! > and now the system boots up, and then instantly > reboot's? I have seen reports of things like that, > but have never hit something like that(if you can try early debugging > with a remote machine to grab dmesg) Not exactly sure how to go about that. I will try to video the boot process so I can provide better info. > > Justin P. Mattock > -- Until later, Geoffrey "I predict future happiness for America if they can prevent the government from wasting the labors of the people under the pretense of taking care of them." - Thomas Jefferson |
From: Justin P. M. <jus...@gm...> - 2010-04-21 17:23:30
|
On 04/21/2010 09:57 AM, Geoffrey wrote: > Justin P. Mattock wrote: >> On 04/21/2010 09:30 AM, Geoffrey wrote: >>> Justin P. Mattock wrote: >>>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>>> Justin P. Mattock wrote: >>>>>> On 04/21/2010 06:55 AM, Geoffrey wrote: >>>>>>> So I rebuilt my kernel, insuring that I had ext3 support and I >>>>>>> still get >>>>>>> a panic, although it is a different message: >>>>>>> >>>>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>>>>> unknown-block(0,0) >>>>>>> >>>>>>> >>>>>> >>>>>> check your /etc/fstab and make sure >>>>>> that it's /dev/sda* instead of /dev/hda* >>>>>> (if your using the older ati-piix it's should >>>>>> be /dev/hda* but using the new ati-piix it's >>>>>> /dev/sda*)but could be wrong). >>>>> >>>>> Actually it's using the LABEL nomenclature, do you think this could be >>>>> my problem? >>>>> >>>>> LABEL=/ / ext3 defaults 1 1 >>>>> >>>>> >>>> >>>> could be.. >>>> here's what I have: >>>> cat /etc/fstab >>>> >>>> # file system mount-point type options dump fsck >>>> # order >>>> >>>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>>> /dev/sda4 swap swap pri=1 0 0 >>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>>> proc /proc proc defaults 0 0 >>>> sysfs /sys sysfs defaults 0 0 >>>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>>> tmpfs /dev/shm tmpfs defaults 0 0 >>>> #none /selinux selinuxfs defaults 0 0 >>>> # End /etc/fstab >>>> >>>> does changing LABEL=/ to your device do anything? >>> >>> Just tried that, no difference. >>> >>>> >>>> Justin P. Mattock >>>> >>> >>> >> >> hm.. I'm wondering if your hitting something >> with grub and the kernel i.g. I remember hitting something >> similar because I had no bzimage just raw make install >> vmlinuz(ended up having to upgrade to grub2 so that grub(*) >> was able to read the extra bits and so forth or something >> in that area). >> >> Also hit another issue similar as well with >> PCI_MMCONFIG [=y] >> (but this could already be fixed). > > I changed my grub entry for root from: > > root=LABEL=/ > > to > > root=/dev/sda8 > > Now I get a spontaneous reboot. I tried to snap a photo of it before it > reboot, but it's blurred. I'll try again. Weird thing is that it says > something about wacom driver and then a reference to reiserfs or some > such. I don't know what the wacom driver would have to do with reiserfs, > but I'm not using reiserfs anyway. > > so changing your grub at-least takes care of the unable to find VFS thing?! and now the system boots up, and then instantly reboot's? I have seen reports of things like that, but have never hit something like that(if you can try early debugging with a remote machine to grab dmesg) Justin P. Mattock |
From: Geoffrey <li...@se...> - 2010-04-21 16:57:57
|
Justin P. Mattock wrote: > On 04/21/2010 09:30 AM, Geoffrey wrote: >> Justin P. Mattock wrote: >>> On 04/21/2010 09:11 AM, Geoffrey wrote: >>>> Justin P. Mattock wrote: >>>>> On 04/21/2010 06:55 AM, Geoffrey wrote: >>>>>> So I rebuilt my kernel, insuring that I had ext3 support and I >>>>>> still get >>>>>> a panic, although it is a different message: >>>>>> >>>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>>>> unknown-block(0,0) >>>>>> >>>>>> >>>>> >>>>> check your /etc/fstab and make sure >>>>> that it's /dev/sda* instead of /dev/hda* >>>>> (if your using the older ati-piix it's should >>>>> be /dev/hda* but using the new ati-piix it's >>>>> /dev/sda*)but could be wrong). >>>> >>>> Actually it's using the LABEL nomenclature, do you think this could be >>>> my problem? >>>> >>>> LABEL=/ / ext3 defaults 1 1 >>>> >>>> >>> >>> could be.. >>> here's what I have: >>> cat /etc/fstab >>> >>> # file system mount-point type options dump fsck >>> # order >>> >>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >>> /dev/sda4 swap swap pri=1 0 0 >>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >>> proc /proc proc defaults 0 0 >>> sysfs /sys sysfs defaults 0 0 >>> devpts /dev/pts devpts gid=4,mode=620 0 0 >>> tmpfs /dev/shm tmpfs defaults 0 0 >>> #none /selinux selinuxfs defaults 0 0 >>> # End /etc/fstab >>> >>> does changing LABEL=/ to your device do anything? >> >> Just tried that, no difference. >> >>> >>> Justin P. Mattock >>> >> >> > > hm.. I'm wondering if your hitting something > with grub and the kernel i.g. I remember hitting something > similar because I had no bzimage just raw make install > vmlinuz(ended up having to upgrade to grub2 so that grub(*) > was able to read the extra bits and so forth or something > in that area). > > Also hit another issue similar as well with > PCI_MMCONFIG [=y] > (but this could already be fixed). I changed my grub entry for root from: root=LABEL=/ to root=/dev/sda8 Now I get a spontaneous reboot. I tried to snap a photo of it before it reboot, but it's blurred. I'll try again. Weird thing is that it says something about wacom driver and then a reference to reiserfs or some such. I don't know what the wacom driver would have to do with reiserfs, but I'm not using reiserfs anyway. > > Justin P. Mattock > -- Until later, Geoffrey "I predict future happiness for America if they can prevent the government from wasting the labors of the people under the pretense of taking care of them." - Thomas Jefferson |
From: Justin P. M. <jus...@gm...> - 2010-04-21 16:40:10
|
On 04/21/2010 09:30 AM, Geoffrey wrote: > Justin P. Mattock wrote: >> On 04/21/2010 09:11 AM, Geoffrey wrote: >>> Justin P. Mattock wrote: >>>> On 04/21/2010 06:55 AM, Geoffrey wrote: >>>>> So I rebuilt my kernel, insuring that I had ext3 support and I >>>>> still get >>>>> a panic, although it is a different message: >>>>> >>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>>>> unknown-block(0,0) >>>>> >>>>> >>>> >>>> check your /etc/fstab and make sure >>>> that it's /dev/sda* instead of /dev/hda* >>>> (if your using the older ati-piix it's should >>>> be /dev/hda* but using the new ati-piix it's >>>> /dev/sda*)but could be wrong). >>> >>> Actually it's using the LABEL nomenclature, do you think this could be >>> my problem? >>> >>> LABEL=/ / ext3 defaults 1 1 >>> >>> >> >> could be.. >> here's what I have: >> cat /etc/fstab >> >> # file system mount-point type options dump fsck >> # order >> >> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1 >> /dev/sda4 swap swap pri=1 0 0 >> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 >> proc /proc proc defaults 0 0 >> sysfs /sys sysfs defaults 0 0 >> devpts /dev/pts devpts gid=4,mode=620 0 0 >> tmpfs /dev/shm tmpfs defaults 0 0 >> #none /selinux selinuxfs defaults 0 0 >> # End /etc/fstab >> >> does changing LABEL=/ to your device do anything? > > Just tried that, no difference. > >> >> Justin P. Mattock >> > > hm.. I'm wondering if your hitting something with grub and the kernel i.g. I remember hitting something similar because I had no bzimage just raw make install vmlinuz(ended up having to upgrade to grub2 so that grub(*) was able to read the extra bits and so forth or something in that area). Also hit another issue similar as well with PCI_MMCONFIG [=y] (but this could already be fixed). Justin P. Mattock |