Boot issues
Posts: 12
Hi,
I recently installed a driver for my wireless card using ndiswrapper, following their insructions. It now works perfectly, but when I attempt to boot mepis, it stalls at about 20% of the bar finished, and eventually shows a screen where I can read, about halfway down...
FWH array not found (failed)
and at the bottom, SPLASHY error, timeout after 120sec.
Mepis doesn't seem to be unbootable because after enough tries, it boots (this message was typed in mepis...) but that wireless driver was the only thing I changed, so I'm thinking I fubared my system somehow by doing that, but have no idea how to fix it. Any help would be wonderful ^_^ Here's my lspci info:
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce Go 7600] (rev a1)
04:00.0 Network controller: Intel Corporation Unknown device 4229 (rev 61)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller (rev 01)
06:04.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
06:04.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller
06:04.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)
06:04.3 Generic system peripheral [0805]: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller
The wireless card is an Intel Wifi Link 4965AGN. I'm running mepis 7.0 beta2 on a Toshiba satellite p200.
So, a few days and a lot of
Posts: 12
So, a few days and a lot of effort later, here's the info for any Toshiba laptop users....
-sound works once ALSA is updated and configured correctly - in beta 3 this is set up correctly from the first boot
-wireless works with the 4965AGN card using ndiswrapper and a windows driver
-using automatic networking works (nearby networks are detected and connected properly) but causes errors in HAL that prevent the system from booting, I haven't found a fix
-the article referenced above, while at first appearance a godsend, is actually pretty crappy. Don't depend on it. The author doesn't give accurate instructions for using ndiswrapper (his don't work, whereas the ones on the ndiswrapper wiki do), among other things. Several of the packages he references do not / no longer exist.
Here's the one that's stumped me...
Mepis won't boot until winblows is booted first and then restarted, due (I believe) to this error message on boot...
according to mtab,sysfs is already mounted on /sys
*failed
causing a SPLASHY error and a timeout.
the fix mentioned here: http://www.mepislovers.org/forums/showthread.php?t=9581
doesn't work. Any ideas?
Thanks,
So, a few days
Posts: 2280
Ok what exactly happens when it doesn't boot? Does it just hang at grub or ??? Might help to have a better view of whats happening or not happening, i don't think the error message has anything to do with it not booting.
Also you might try reinstalling grub with Mepis utilities just to be sure that base has been touched, just in case it was a bad write. Very strange you have to boot winders first don't believe i have heard that one before. At a loss at this time , all i know to do is play with it & see what happens .
jim
Grub works fine, what
Posts: 12
Grub works fine, what happens after I launch mepis from there is basically this...
-some script starts telling me it's booting, intel_rng is not detected (supposedly nothing to worry about, based on what I've read, then I can tell something failed but the script goes too fast for me to see, and it launches the mepis loading bar. at 40%, the bar stops - if I booted winblows first, it stalls for about 60 seconds then finishes booting.
If not, it times out there and after waiting 2 mins the page goes to script, where I can see the failure message I described and it tells me that splashy timed out.
I don't think this is an issue with grub because this is my second mepis install, and it seems that if mepis is pissed at you, this is when it decides to crash during boot.
The bug i described with automatic wireless detection causes it to time out with a splashy error at 20%, for a different reason, for example.
wish I knew what bug this one was though ^_^
hopefully this is enough info to help out. Thanks again,
Grub works fine,
Posts: 2280
Ok try booting again without winders first & down at bottom of grub part of the boot string will be visible with flashing cursor ,left arrow to splash word & backspace to remove it. Hit enter to boot without splashy & see if that changes anything. Strange problem wondering if something got borked on install but this should tell if splashy is involved. Only other thing i can think of is check your install cd md5sum with published one. Put cd in drive , don't mount it & issue md5sum /dev/cdrom or what ever its called in /etc/fstab, on my system its called /dev/cdrom & /dev/sdc0.... I just use one drive & dont know whats up with that so you may have to experiment a little to find which to use. I assume one is for music and other is for data let me know how it works if you try it.
jim
splashy
Posts: 516
As soon as splashy starts press the "Esc" key and it will clear the splash screen so you will be able to see where it is getting stuck.
When booting from Windows to Linux it is normal to have problems and the same applies when booting from Linux to Windows or booting from Linux to another Linux distro. I have found that the problem is in the way that the date and time are setup and this will cause errors on your partitions file-system, normally rebooting will work, rebooting and checking your BIOS for the correct date and time is the best thing to do.
------------------------------------------------------------
Registered Linux User #380263
Thanks for the quick
Posts: 12
Thanks for the quick responses guys, really appreciate the help. Tried some things...
-Booting without splashy - script goes as normal, intel_rng FWH not detected as normal, no failure at this point, DHCP checks out and then script just stops, without splashy i don't even get an error message, and I left it alone while I ate dinner so it wasn't simply not timing out - I guess that means the problem is with it?
-Checked my bios and winblows clocks, they are both in line with mepis's clock.
-Tried hitting esc while splashy launched, apparently didnt hit it fast enough, will try again -
-I don't think it's simply a bad install because I had this splashy error and boot crashing when I was running a separate cd (from a separate mirror)'s 7.0 beta 2, it just happened in a different place - you may be right though, I'll check my md5
Thanks again,
Splashy
Posts: 2280
Am i reading you correctly that the boot problem is better or fixed without splashy? Not sure if i am getting it( call me dense).
Not sure why but by removing splash from grub my test rig seems to be outputting a lot less than before, cant say its a faster boot but verbose output is a lot cleaner. Interesting how little things like that seem to affect the way it boots. Dont care too much for that kind of glitz anyhow, i liked 3.3.1 transparent with verbose better , you get to make all happy.
jim
Splashy
Posts: 516
Just use Synaptic and remove "splashy" and "libsplashy1", then you won't have to deal with pressing the "Esc" key any longer.
------------------------------------------------------------
Registered Linux User #380263
Splashy
Posts: 2280
Just use Synaptic and remove "splashy" and "libsplashy1", then you won't have to deal with pressing the "Esc" key any longer.
------------------------------------------------------------
Registered Linux User #380263
Just removing splash from grub line works fine & escape key doesn't work for me nor f1 f2 etc.
jim
Splashy
Posts: 516
jim
Yep, sure, I'm just not one to have files installed that I'm not using. 
As for the "Esc" key it works, you just have to hit it right now, if you wait a second then it won't work.
------------------------------------------------------------
Registered Linux User #380263
I'm not sure quite what the
Posts: 12
I'm not sure quite what the problem was but it seems to be resolved now. Here's what I did:
-Booted again without splashy. Here are the irregular messages I received:
1)-si3045 cannot initialize EXT MID = 0000
2) -intel_rng FWH not detected
3) -failed no MD subsystem loaded
4) -not starting ipw3945 regulatory daemon, driver not loaded
5) -Superblock last write time is in the future ... fixed
6) -wrong chipset detected. 915res only works with intel 800/900 series chipsets.
and the coup d'grace, after 'updating fstab ... done'
7) segmentation fault
Booting ended here, and I was left with dead script until I manually turned off the computer.
Since then I removed splashy using synaptic and have cold booted 3 times. Script goes by fast, but 2, 3, and 4 seem to be the only common themes. I have not had an unsuccessful boot since the one described above. Some of those errors really bewilder me, for example, mepis detected my nvidia graphics card from the very first time I used it (v6.5), and has been one of the few linux distros to recognise my unusual 1440x900 resolution "out of the box." If there is anything in there that indicates what caused my messed up booting, or what I can do to prevent it from happening again, that would be wonderful.
On a side note, after these successful boots I tried using knetworkmanager (caused HAL errors and failure to boot), and the system still boots with it. Case closed, I guess, and thanks so much for the help, both of you
I'm not sure
Posts: 2280
I think most are info messages about the hardware is not found & no big deal, Warren tries to cover as many machines as possible, as time goes by im thinking it may be getting tougher to avoid conflicts. Prime example is splashy and some hardware setups. Hopefully you are set to go and Warren can use some of this to make it better. Hang in there.
jim
timeouts
Posts: 10
I have the same troubles. Mepis 7 beta3, A note comes up on screen about HAL not working. Wireless starts and works excellent. I re-start the computer later, the Mepis blue splashscreen starts, stops with a bit left on the bar and locks up. Control-alt F8 shows a splashy timeout, a hard shutdown and restart to Mepis and Windows and mepis starts ok.
Windows on sata a mepis sata b. HP desktop, Nvidia 7300GT, 2 gig ram.
This is a big deal here. I want mepis to replace xp in my studio, doesn't look like it now. I want to order the big dvd later, maybe this will be fixed?
splash
Posts: 2280
I have the same troubles. Mepis 7 beta3, A note comes up on screen about HAL not working. Wireless starts and works excellent. I re-start the computer later, the Mepis blue splashscreen starts, stops with a bit left on the bar and locks up. Control-alt F8 shows a splashy timeout, a hard shutdown and restart to Mepis and Windows and mepis starts ok.
Windows on sata a mepis sata b. HP desktop, Nvidia 7300GT, 2 gig ram.
This is a big deal here. I want mepis to replace xp in my studio, doesn't look like it now. I want to order the big dvd later, maybe this will be fixed?
Can you try removing splash from grub as described in previous post just to see if it helps and for a little test? I just installed a couple of config updates this morning that may be the solution but you are in a position to add more feedback. A before and after test just to be sure we aren't riding the wrong horse. The splash word in grub is easily replaced before doing the updates and it might help a great deal in the final release.
jim
Sounds great, actually. In
Posts: 12
Sounds great, actually.
In retrospect, my problem isn't really "solved," I got a lucky stream of successful boots after removing splash, now I get no splash errors, which is a definite plus, but I still have a reasonable amount of unsuccessful boots. When it fails to boot it stops right after loading cups, the next line (verified by booting succesfully) is to load dbus, so maybe the problem lies with it somewhere?
If you potentially have a solution, I'd be happy to help test it as well.
Sounds to me that you are
Posts: 516
Sounds to me that you are having the problems when booting from one OS to another, you may need to do a clean shutdown for a few seconds and then do a cold start when you want to change OS's. The only way I can explain it is that the configuration settings or some such stuff from the last OS you ran are being stored in memory and cause errors when booting, this is not uncommon.
I have been seeing this for years. Most people that only run one OS will never see this problem.
Don't get me wrong though cause there are still a lot of bug's to be worked out yet.
------------------------------------------------------------
Mepis User for over 5 years
Registered Linux User #380263
test plan
Posts: 2280
Well right now i wish i had such a plan because i find i have similar but worse problem with a P4 rig with a via chip set. Tried to boot it and check the differences in /etc/apt/sources.list after updates to test rig & error in address 000000 and it froze solid , after reset no bios splash or anything just silence. Don't know at this point whats up, disconnecting hard drive and resetting bios swapping out power supply it finally came up & i installed 4 updates and it died again. Totally crazy but i have had no problem on AMD rig that a reboot from cli couldn't fix(after updates it froze at desktop). Who knows at this point could have two flaky power supplies or board may be junk both are common problems lately.
So its back to the drawing board fer me till i sort out whats with the thing. Will keep you posted on what i find.
jim
Sorry to hear abut your
Posts: 516
Sorry to hear abut your hardware problems, I'm sure it's just a coincidence, I'm running the beta3 on my main desktop and 2 laptops, all are Intel, the oldest is a P3 and it's giving me a weird KDE bug with missing desktop icons and two pop-ups about protocol died unexpectedly, but no hang-ups on the boot, but I have removed all unneeded modules as I do with all my systems.
------------------------------------------------------------
Mepis User for over 5 years
Registered Linux User #380263
Yep just a coincadink
Posts: 2280
Sorry to hear abut your hardware problems, I'm sure it's just a coincidence, I'm running the beta3 on my main desktop and 2 laptops, all are Intel, the oldest is a P3 and it's giving me a weird KDE bug with missing desktop icons and two pop-ups about protocol died unexpectedly, but no hang-ups on the boot, but I have removed all unneeded modules as I do with all my systems.
------------------------------------------------------------
Mepis User for over 5 years
Registered Linux User #380263
After playing musical hardware swapper for a few hours the light came on (memory address :0000000) i reset the memory module & all works well. Then reinstalled all original parts to be sure , all is still well. Nothing quite like being stuck on stupid eh. 
Not a total loss though wasn't a software glitch from Mepis & i got the dust bunnies blown out of two rigs, hardware is all good not to mention i got to brush up on my anger management and cussin. Could have been a lot worse and costly. Now back to original problem.
jim
LOL, I was going to say
Posts: 516
LOL, I was going to say something about the RAM but decided it would be to presumptuous, anyways I'm glad you got it fixed.
As for the KDE bug I mentioned above, I found that if I remove the desktop wallpaper that the problem goes away.
------------------------------------------------------------
Mepis User for over 5 years
Registered Linux User #380263
*Updates*
Posts: 4
Ok, so it's been a little while now, and after running mepis (as well as a handful of other distros), I'm hopefully less of a noob with respect to using linux. I still, however, cannot successfully boot mepis unless I boot winblows first and restart - it doesn't "fail," and I don't get an error, the system simply stops running at a certain random point in startup until splash times out. I am positive (by repeating the problem...several times) that this is caused by a bug having to do with wireless in mepis. I am currently using an ndiswrapper driver to run my card, which is an intel 4965AGN. to my knowledge there is no other way to do this. The weirdest thing is that my wireless is also buggy - it works perfectly for a short period of time after boot (5-15 mins), then claims to still be connected but slowly cuts off aim/ktorrent while firefox infinitely loads the same page. Eventually, it outright cuts off and firefox gives a 404 error. Restarting knetworkmanager / resetting the connection does not resolve the problem. Based on traffic data from it, I'm continuing to receive data but i stop sending it out entirely.
Today on a hunch, I re-modprobed ndiswrapper and did a dmesg. It gave some output which I don't understand at all, but which I think is relevant.
] __alloc_pages+0x5a/0x2a1
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
BUG: scheduling while atomic: modprobe/0x00000001/1605
Call Trace:
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
[
wlan0: ethernet device 00:13:e8:1b:42:cb using NDIS driver: netw4x64, version: 0x1000b, NDIS version: 0x501, vendor: 'Intel(R) Wireless WiFi Link 4965AG Driver', 8086:4229.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
usbcore: registered new interface driver ndiswrapper
fuse init (API version 7.
fuse distribution version: 2.7.0
pcmcia: Detected deprecated PCMCIA ioctl usage from process: discover.
pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (8192 buckets, 65536 max)
ACPI: Battery Slot [BAT1] (battery present)
ACPI: AC Adapter [ACAD] (on-line)
ACPI: SSDT 7FE8851F, 0238 (r1 PmRef Cpu0Ist 3000 INTL 20050624)
ACPI: SSDT 7FE87FD8, 04C2 (r1 PmRef Cpu0Cst 3001 INTL 20050624)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Monitor-Mwait will be used to enter C-3 state
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: SSDT 7FE88757, 00C8 (r1 PmRef Cpu1Ist 3000 INTL 20050624)
ACPI: SSDT 7FE8849A, 0085 (r1 PmRef Cpu1Cst 3000 INTL 20050624)
ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
input: Power Button (FF) as /class/input/input3
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /class/input/input4
ACPI: Lid Switch [LID0]
input: Power Button (CM) as /class/input/input5
ACPI: Power Button (CM) [PWRB]
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
r8169: eth0: link down
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:01:00.0 to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 100.14.11 Wed Jun 13 16:33:22 PDT 2007
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
usb 1-5: new high speed USB device using ehci_hcd and address 4
usb 1-5: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver hiddev
input: Western Digital External HDD as /class/input/input6
input: USB HID v1.11 Device [Western Digital External HDD] on usb-0000:00:1d.7-5
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
usb-storage: device scan complete
scsi 2:0:0:0: Direct-Access WD 5000AAKS Externa 107a PQ: 0 ANSI: 4
sd 2:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 11 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 11 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1 sdb2 < sdb5 >
sd 2:0:0:0: [sdb] Attached SCSI disk
sd 2:0:0:0: Attached scsi generic sg2 type 0
wlan0: no IPv6 routers present
ABORTED IN=wlan0 OUT= MAC=00:13:e8:1b:42:cb:00:0b:fc:a3:e5:fc:08:00 SRC=152.3.232.41 DST=152.3.180.221 LEN=40 TOS=0x00 PREC=0x00 TTL=58 ID=51539 DF PROTO=TCP SPT=443 DPT=2150 SEQ=3385194196 ACK=0 WINDOW=24820 RES=0x00 RST URGP=0
ABORTED IN=wlan0 OUT= MAC=00:13:e8:1b:42:cb:00:0b:fc:a3:e5:fc:08:00 SRC=152.3.232.41 DST=152.3.180.221 LEN=40 TOS=0x00 PREC=0x00 TTL=62 ID=51540 DF PROTO=TCP SPT=443 DPT=2150 SEQ=3385194196 ACK=0 WINDOW=0 RES=0x00 RST URGP=0
ABORTED IN=wlan0 OUT= MAC=00:13:e8:1b:42:cb:00:0b:fc:a3:e5:fc:08:00 SRC=72.55.146.179 DST=152.3.180.221 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=17957 DF PROTO=TCP SPT=53414 DPT=3614 SEQ=3097614414 ACK=2503749547 WINDOW=46 RES=0x00 ACK RST URGP=0
ABORTED IN=wlan0 OUT= MAC=00:13:e8:1b:42:cb:00:0b:fc:a3:e5:fc:08:00 SRC=72.55.146.179 DST=152.3.180.221 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=65523 DF PROTO=TCP SPT=53403 DPT=3679 SEQ=3106693426 ACK=2842020965 WINDOW=46 RES=0x00 ACK RST URGP=0
ABORTED IN=wlan0 OUT= MAC=00:13:e8:1b:42:cb:00:0b:fc:a3:e5:fc:08:00 SRC=72.55.146.179 DST=152.3.180.221 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=11583 DF PROTO=TCP SPT=56323 DPT=3281 SEQ=3104224200 ACK=3064446206 WINDOW=46 RES=0x00 ACK RST URGP=0
ABORTED IN=wlan0 OUT= MAC=00:13:e8:1b:42:cb:00:0b:fc:a3:e5:fc:08:00 SRC=72.55.146.179 DST=152.3.180.221 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=0 DF PROTO=TCP SPT=56323 DPT=3281 SEQ=3104224200 ACK=0 WINDOW=0 RES=0x00 RST URGP=0
Any potential help would be great, sorry to continue spamming here!
Things I can rule out:
1) bad install / bad CD - problem replicated over 3 versions of mepis
2) lack of correlation - boot stops working properly immediately after setting up ndiswrappered wireless driver
Thanks,
Gudo
*Updates*
Posts: 2280
Well you do have a problem. I'm Thinking its time to check in with Toshiba and see if they can shed some light. Also Intel writes a driver for that so might have a look there too. Google around a bit too maybe some one else has been around the block with this , it seems specific to that laptop. Good luck!
jim
thanks for the wisdom jim.
Posts: 12
thanks for the wisdom jim. I'd more or less forgotten about iwlwifi, the intel for linux project that has a driver written specifically for my card, because i'd gotten put off by it in the first place because its installation is so tricky, requiring the mac80211 subsystem before you can even start worrying about loading it. After removing my ndiswrapper driver (so, as I predicted, now mepis boots by itself again, could this have been an issue with the way ndiswrapper loaded itself into the kernel?), I downloaded the iwlwifi packages. The mac subsystem requires you to make its file and insert it into the kernel.
hurdle 1 - "make" from the mac system referenced source files in lib/modules/mepis*version*/source, and they were in reality in mepis*version*/build. A change in its Makefile corrected this. I could then "make patch_kernel".
hurdle 2 - make menuconfig from the lib/build gives this output:
root@Pwner:/usr/src/linux-headers-2.6.22-1-mepis64-smp# make menuconfig
scripts/Makefile.build:17: /usr/src/linux-headers-2.6.22-1-mepis64-smp/scripts/basic/Makefile: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-headers-2.6.22-1-mepis64-smp/scripts/basic/Makefile'. Stop.
make: *** [scripts_basic] Error 2
I'm not sure if this is caused by what i did before or not, but there is definitely a makefile in its target directory, so this output doesn't seem to make sense (pardon the pun). Any idea what's going on?
Thanks,
Possibly Headers
Posts: 2280
You may not have the correct headers. Make sure module-assistant is installed then run module-assistant from konsole as root. Go through the items from top to bottom it will brush you up on commands & prep the system for module compiling eg., it will install all the headers and dependencies for you with a y input. Then select module to compile, it may be able at this point to setup & compile the driver you need, dont know for sure but have a look in there. If it cant make it for you try to remove what you have done and have another go if it doesnt work the first time.
jim
4965AGN
Posts: 2280
Check this out should show you how to do it right.
http://linux.dobeyracing.net/how_to/toshiba_p200_laptop/Linux_on_Toshiba_Satellite_P200.php
luck jim